Kamuthiking
Enthusiast
Enthusiast

Cross Vcenter Unable to add Secondary NSX manager

Jump to solution

HI

setup is  2 vcenter 6.0

NSX 6.4.2

while adding the Secondary  nsx manager getting error certification verification fails Note ( For testing i have tried with wrong password ) that time also getting the same error

ip reachable  is there . and vcenter 1 displayed both the NSX manager .

Tshoot tried

NSx node id are different

VXlan is same on both  .

Please can some one help

regards

Raja  

1 Solution

Accepted Solutions
bayupw
Leadership
Leadership

The KB in the first link in my earlier reply shows what would be the error message on vsm.log if there are port issues on 443 or UDP VXLAN port mismatch.

The second links has similar issue but has different error which also showing on the NSX Manager log

You may want to check the NSX Manager/vsm log and see if the log entries point to something.

If you don't mind, you can also share the NSX Manager/vsm.log here.

Else, you would need to open a case to VMware Support

Bayu Wibowo | VCIX6-DCV/NV Author of VMware NSX Cookbook http://bit.ly/NSXCookbook https://github.com/bayupw/PowerNSX-Scripts https://nz.linkedin.com/in/bayupw | twitter @bayupw

View solution in original post

0 Kudos
4 Replies
bayupw
Leadership
Leadership

Hi, do you mean NSX 6.2.4?

Could you share what is the error message?

Check these links if any of those are helpful:

Adding a Secondary NSX Manager to the Primary NSX Manager fails (2145937) | VMware KB

error when join secondary nsx manager to Master Nsx manager

If you need to review the cross-vcenter install you can review the guide here:

VMware NSX for vSphere 6.2 Documentation Center-Cross-vCenter Installation Guide

VMware NSX for vSphere 6.2 Documentation Center-Add a Secondary NSX Manager

Prerequisites

  • There should be at least two NSX Managers, one with the primary role and one with the standalone or transit role.
  • The version of the NSX Managers (the primary NSX Manager and NSX Managers that will be assigned the secondary role) must match.
  • The node IDs of the primary NSX Manager and the NSX Managers that will be assigned the secondary role must be present and different. NSX Manager instances deployed from OVA files have unique node IDs. An NSX Manager deployed from a template (as in when you convert a virtual machine to a template) will have the same node ID as the original NSX Manager used to create the template, and these two NSX Managers cannot be used in the same cross-vCenter NSX installation.
  • Each NSX Manager must be registered with a separate and unique vCenter Server.
  • The UDP ports used for VXLAN must be the same for all NSX Managers.
  • When assigning the secondary role to a NSX Manager, the vCenter linked to it must not have any deployed NSX Controllers.
  • The segment ID pool of the NSX Manager being assigned the secondary role must not overlap with the segment ID pools of the primary NSX Manager or the segment ID pool of any other secondary NSX Manager .
  • The NSX Manager being assigned the secondary role must have the standalone or transit role.
Bayu Wibowo | VCIX6-DCV/NV Author of VMware NSX Cookbook http://bit.ly/NSXCookbook https://github.com/bayupw/PowerNSX-Scripts https://nz.linkedin.com/in/bayupw | twitter @bayupw
Kamuthiking
Enthusiast
Enthusiast

HI

Please find  attached screen shot

i have went through the guide looks i have followed all .error.jpg

bayupw
Leadership
Leadership

The KB in the first link in my earlier reply shows what would be the error message on vsm.log if there are port issues on 443 or UDP VXLAN port mismatch.

The second links has similar issue but has different error which also showing on the NSX Manager log

You may want to check the NSX Manager/vsm log and see if the log entries point to something.

If you don't mind, you can also share the NSX Manager/vsm.log here.

Else, you would need to open a case to VMware Support

Bayu Wibowo | VCIX6-DCV/NV Author of VMware NSX Cookbook http://bit.ly/NSXCookbook https://github.com/bayupw/PowerNSX-Scripts https://nz.linkedin.com/in/bayupw | twitter @bayupw

View solution in original post

0 Kudos
bayupw
Leadership
Leadership

Hi Raja, did you found the problem and the resolution?

Bayu Wibowo | VCIX6-DCV/NV Author of VMware NSX Cookbook http://bit.ly/NSXCookbook https://github.com/bayupw/PowerNSX-Scripts https://nz.linkedin.com/in/bayupw | twitter @bayupw