jbotsford

Every now and then I have challenges getting a host (Windows and ESX) to register in Navisphere by name. Typically this can be attributed to multihomed (multiple NICs) hosts causing the issue. Pretty simple fix:

Windows Servers:

1.) Stop the Navisphere Agent Service.

2.) Drill down to C:\Program Files\EMC\Navisphere Agent\

3.) Create a text file called agentID.txt (case sensitive). Should look as follows:

Line 1: Fully qualified host name.
Line 2: IP address that you want the Naviagent to use.

Example:

servername.mydomain.local
192.168.12.123

4.) Start the Navisphere Agent service.

5.) Login to Navisphere and do an "Update Now". Your Windows host should now self register by hostname.

ESX Servers:

1.) Stop the naviagent service.

2.) Create the agentID.txt file(same as above) in /root.

3.) Delete the HostIdFile.txt in /var/log.

4.) Start the naviagent service.

5.) Check the new HostIdFile.txt in /var/log and verify that it is using the proper IP address.

6.) Log into Navisphere and do an "Update Now". The ESX host should self register by host name.

NOTE: Navisphere can take some time to update so be patient.