Installed Remote Hub with Static Route from Primary But Still Can't See Remote Hub in IM

Document ID : KB000035055
Last Modified Date : 13/02/2019
Show Technical Document Details
Issue:

When prompted on the new hub for the name of the domain during installation, I enter the name of my primary domain, PrimHubVMDom.  Then after installation completes, I set up a static link to my new hub in the hub probe of the primary hub as shown here:

User-added image


But I still can't see my new hub show up in my domain in Infrastructure Manager.



 


 

Environment:

Installation for new hub on different subnet network that you need to specify the static hub on the name services on the primary hub probe.

Cause:

Duplicate domain, one with upper case and other with lower case.

Resolution:

From the View menu in Infrastructure Manager, choose Show All Domains.  It is possible that you have entered the value of your Domain with non-matching case as shown here:

 

User-added image


Note the two values for domains:

PrimHubVMdom
PrimHubVMDom


Since domain names are case sensitive, by entering uppercase D in PrimHubVMDom, you now have two domains. 

To see both domains appear in the left navigation area of Infrastructure Manager, you may have to launch the hub GUI and from the Hubs tab perform an Alive Check by right clicking on the remote hub and choosing the Alive Check action.

User-added image


To correct this situation, follow these steps:
 

1- Modify the hub.cfg on the secondary hub to use the correct domain name. 
Here, the changed version with PrimHubVMdom for the domain name is shown:

 

User-added image

2. Restart the server on the secondary hub using the Nimsoft Service Controller.
3. Modify the hub.cfg on the primary hub to use the correct domain name for the secondary hub as shown here:
 
User-added image
 
 
4. Restart the server on the secondary hub using the Nimsoft Service Controller.
 
Both of your hubs should now appear under the same domain in Infrastructure manager:
 
User-added image