The secondary NSX Manager displays the universal segment ID pool, which is synchronized from the primary NSX Manager. Additionally, you can create a segment ID pool that is local to the secondary NSX Manager, which is used to create logical switches that are local to that NSX Manager. If you will create only universal logical switches, you do not need to add a segment ID pool local to the secondary NSX Manager.
For details on prerequisites and guidance for planning segment ID pools and multicast addresses see Assign a Segment ID Pool and Multicast Address for the Primary NSX Manager.
- Using the vSphere Web Client, log in to the vCenter Server system registered with the NSX Manager you want to modify.
If the vCenter Server systems in your cross-vCenter NSX environment are in Enhanced Linked Mode, you can access any associated NSX Manager from any linked vCenter Server system by selecting it from the NSX Manager drop-down menu.
- Navigate to Segment ID tab. and select the
- Verify the correct NSX Manager is selected in the NSX Manager drop-down menu.
- Enter a range for local segment IDs, such as 20000-29999.
The specified ranges for local and universal segment IDs must not overlap.
- (Optional) : If any of your transport zones will use multicast or hybrid replication mode, check Enable multicast addressing and enter a multicast address or a range of multicast addresses.
Verify that the multicast address specified does not conflict with any other multicast addresses assigned on any NSX Manager in the cross-vCenter NSX environment.
The secondary NSX Manager now has both imported universal segment IDs provided by the primary NSX Manager and local segment IDs.