Can build up the secondary NSX manager but cannot build up cross vcenter

[3back]

Dear All

I found the below screen problem. How can I fix it?

Can find the secondary NSX manager in the list. But the interconnection are worked

Best Regards

[SureshKumarMuth]

Are you able to see both vCenter s in the inventory when you launch webclient?

Looks like the connection between two VCs are broken, thats why you are getting the error as unable to connect to one or more VC, you have to work on that first to resolve this. Unless, both VCs talk each other, inventory will not show all objects on single instance of webclient

[3back]

Dear Sureshkumar

Thanks for your reply. I cannot found both Vcenter in the inventory. By the way! Let say I have two datacenter in using separate Vcenter and PSC. How to combine that and build up cross vcenter? I want to deploy Vmotion between two site.

Best Regards

[Sreec]

Ensure that PSC are in same SSO domain -Frwd/Rvrs DNS with NTP should be working flawlessly - no compromise on that

Configure respective PSC url (Lookupservice) for each site NSX manager and register the solution with its own VC .

This is the starting step for Cross VC NSX integration.

[SureshKumarMuth]

As SreeC said, you have to deploy PSC in same SSO domain. Based on the error message, looks like the other VC IP is in the SSO db but both are unable to connect.

1. Login to webclient using your SSO admin account to both VCs

2. Goto SSO users and groups

3. Check if solution users on both SSO are same

VC is one of the solution user for PSC if it is missing there then there is a problem. If both sides are intact, reboot all the nodes on both sites (PSC + VC) and check if that works.

[3back]

I found the root cause. Thanks so much!

[SureshKumarMuth]

Were you able to resolve the issue ? what was the cause of the issue ?

[3back]

Each Vcenter installed in different SSO server