The secondary NSX Manager will display the universal segment ID pool, which is synced from the primary NSX Manager. Additionally, you can create a segment ID pool that is local to the secondary NSX Manager, which will be used to create logical switches that are local to that NSX Manager.

Before you begin

For details on prerequisites and guidance for planning segment ID pools see Assign a Segment ID Pool to the Primary NSX Manager.

Procedure

  1. Log in to the vCenter linked to the secondary NSX Manager and navigate to Home > Networking & Security > Installation > Logical Network Preparation and select the Segment ID tab.

    If your vCenters are in Enhanced Linked Mode, you can configure the secondary NSX Manager from any linked vCenter. Navigate to the Segment ID tab, and select the secondary NSX Manager from the drop-down menu.

  2. Enter a range for local segment IDs, such as 20000-29999.
    Caution:

    The specified ranges for local and universal segment IDs must be unique and not overlap.

  3. If any of your transport zones will use multicast or hybrid replication mode, check Enable multicast addressing and type a multicast address or a range of multicast addresses.
    Caution:

    In a cross-vCenter NSX environment, if you select hybrid mode, you must ensure that the multicast address specified does not conflict with any other multicast addresses assigned on any NSX Manager in the environment.

    Having a range of multicast addresses spreads traffic across your network, prevents the overloading of a single multicast address, and better contains BUM replication. The recommended multicast address range starts at 239.0.1.0/24 and excludes 239.128.0.0/24.

    Do not use 239.0.0.0/24 or 239.128.0.0/24 as the multicast address range, because these networks are used for local subnet control, meaning that the physical switches flood all traffic that uses these addresses. For more information about unusable multicast addresses, see https://tools.ietf.org/html/draft-ietf-mboned-ipv4-mcast-unusable-01.

Results

The secondary NSX Manager now has both imported universal segment IDs provided by the primary NSX Manager and local segment IDs.