article Unable to Add ESX Server to up.time 5.x

There are several possible reasons why you may be experiencing this issue.  To help identify the root cause, take the following steps:

  • Try using Root credentials to add the ESX host by its hostname or IP address.
  • Port 443 (SSL) needs to be open for communication between up.time and the ESX server you are trying to add.  To check this connectivity, open a command line prompt and run a telnet command using port 443 from the up.time monitoring station to the ESX host.  If the connection fails, this will need to be resolved before the host can be added.
  • Ensure that Lockdown Mode is not enabled.
  • Ensure that the Hostd service is running on the ESX host.
  • Verify that the ESX host is not being managed by multiple, stale or non-existent vCenter / vSphere hosts and that all of the hosts are online.  Remove any offline host(s) from the ESX host management console.
  • All ESX versions have a Managed Object Browser (MOB) that provides ESX server details and can be used to test user credentials.  Browse to https:///mob/ from up.time and log in using the appropriate credentials.  If you are able to navigate through the MOB, use the same credentials to log into up.time using the auto-discovery option under the My Infrastructure tab.
  • If the system is an ESXi server, confirm that it is managed by vSphere/vCenter.

If you are still unable to add the ESX server to up.time after following the above steps, please contact [email protected] and provide the following information:

  • Screen capture of the error message.
  • ESX version and build number.
  • up.time and monitoring station Operating System version.
  • Send the uptime.log file from the uptime_install dir\Logs folder after completing the following steps:
    • Change the logging level from INFO to DEBUG in the uptime.conf file, which is located in the up.time installation directory.
    • Try adding the ESX server to up.time so the exception is captured in the uptime log.

Related Articles

Unable to access up.time from a web browser


By: uptime Support | Date Created: 10-25-2005 | Last Modified: 7-14-2011 | Index: 030


Running up.time with an MS SQL Server database


The up.time DataStore can run on a MS SQL Server database to leverage existing SQL Server installations and take advantage of SQL Server's advanced replication, recovery and archiving options.

By: uptime Support | Date Created: 7-10-2006 | Last Modified: 6-19-2014 | Index: 087


Unable to access up.time after changing hostname


After changing the hostname of a system, you may not be able to access the up.time UI due to the hard coded hostname configuration in the uptime.conf file. To resolve this issue, ensure that the...

By: uptime Support | Date Created: 7-28-2011 | Last Modified: 7-31-2014 | Index: 553


Unable to browse MIB using the up.time SNMP monitor


When configuring the SNMP Monitor, you are able to add OID manually but can't browse the MIB by loading it. This can happen for a few reasons, but the most common is that the MIB you are trying to...

By: uptime Support | Date Created: 10-14-2009 | Last Modified: 8-13-2011 | Index: 438


Unable to fully load vendor-supplied MIBs into up.time 7


How to resolve MIB dependencies (load order) with custom MIBs. The following symptoms in the up.time MIBBrowser are signs that there is an issue with the order that custom MIBs are being loaded...

By: uptime Support | Date Created: 7-19-2012 | Last Modified: 7-20-2012 | Index: 580


User Comments

No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement