Reply to Message

View discussion in a popup

Replying to:
lukasrueckerl
Enthusiast
Enthusiast

Hi,

I had the chance to test this in my demo deployment. 

Please check under System > System Overview in the Capacity tab how many Compute Managers are supported. In my demo it was deployed as Medium and i have a 2 system capacity.

I encountered the same error as you and could only add the second vCenter by deleting the VcLink Computer Manager. After that I added the original vCenter again and could add the second one.

Note that this won't work if you already have a existing Transport Node Configuration applied to hosts on this vCenter and after this you won't get the NSX plugin in the vCenter(s).

My best guess is that NSX is hard-coded and bound to the originating vCenter when deployed directly, based on the fact that in the default state the construct doesn't even use the built-in Service User function. 

I'll open a case with VMware as this is unexpected behaviour and isn't documented properly.

Sorry that I can't help you any further.

Regards,
Lukas

-------------------------------------------
VCIX-NV + VCIX-DCV 2023
Please mark resolved issues as such. Kudos are appreciated.
Reply
0 Kudos