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

book

Article ID: 35055

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES

Issue/Introduction

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:

<Please see attached file for image>

User-added image


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



 


 

Cause

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

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.

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:

 

<Please see attached file for image>

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.

<Please see attached file for image>

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:

 

<Please see attached file for image>

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:
 

<Please see attached file for image>

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:
 

<Please see attached file for image>

User-added image

 
 

Attachments

1558690096209000035055_sktwi1f5rjvs16g5z.jpeg get_app
1558690094429000035055_sktwi1f5rjvs16g5y.jpeg get_app
1558690092637000035055_sktwi1f5rjvs16g5x.jpeg get_app
1558690090851000035055_sktwi1f5rjvs16g5w.jpeg get_app
1558690088343000035055_sktwi1f5rjvs16g5v.jpeg get_app
1558690086592000035055_sktwi1f5rjvs16g5u.jpeg get_app
1558690084826000035055_sktwi1f5rjvs16g5t.jpeg get_app
1558690082849000035055_sktwi1f5rjvs16g5s.jpeg get_app
1558690081155000035055_sktwi1f5rjvs16g5r.jpeg get_app
1558690079381000035055_sktwi1f5rjvs16g5q.jpeg get_app
1558690077512000035055_sktwi1f5rjvs16g5p.jpeg get_app
1558690074284000035055_sktwi1f5rjvs16g5o.jpeg get_app