You can add two kinds of segments: overlay-backed segments and VLAN-backed segments.
Segments are created as part of a transport zone. There are two types of transport zones: VLAN transport zones and overlay transport zones. A segment created in a VLAN transport zone is a VLAN-backed segment, and a segment created in an overlay transport zone is an overlay-backed segment.
- Starting with NSX-T Data Center 3.1.1, version 4 DHCP relay is supported on a VLAN-backed segment through the Service Interface. Only one DHCP v4 relay or service is supported on a segment.
- For a standalone segment that is not connected to a gateway, only local DHCP server is supported.
- For a VLAN segment requiring DHCP server, only local DHCP server is supported. Gateway DHCP is not supported on VLAN.
- From your browser, log in with admin privileges to an NSX Manager at https://<nsx-manager-ip-address>.
- Select .
- Click Add Segment.
- Enter a name for the segment.
- Select the type of connectivity for the segment.
Connectivity Description None Select this option when you do not want to connect the segment to any upstream gateway (tier-0 or tier-1). Typically, you want to add a standalone segment in the following scenarios:
- When you want to create a local testing environment for users that are running workloads on the same subnet.
- When east-west connectivity with users on the other subnets is not necessary.
- When north-south connectivity to users outside the data center is not necessary.
- When you want to configure layer 2 bridging or guest VLAN tagging.
Select this option when you want to connect the segment to a tier-1 gateway.
Select this option when you want to connect the segment to a tier-0 gateway.Note: You can change the connectivity of a gateway-connected segment from one gateway to another gateway (same or different gateway type). In addition, you can change the connectivity of segment from "None" to a tier-0 or tier-1 gateway. The segment connectivity changes are permitted only when the gateways and the connected segments are in the same transport zone. However, if the segment has DHCP configured on it, some restrictions and caveats apply on changing the segment connectivity. For more information, see Scenarios: Impact of Changing Segment Connectivity on DHCP.
- Enter the Gateway IP address of the subnet in a CIDR format. A segment can contain an IPv4 subnet, or an IPv6 subnet, or both.
- If a segment is not connected to a gateway, subnet is optional.
- If a segment is connected either to a tier-1 or tier-0 gateway, subnet is required.
Subnets of one segment must not overlap with the subnets of other segments in your network. A segment is always associated with a single virtual network identifier (VNI) regardless of whether it is configured with one subnet, two subnets, or no subnet.
- Select a transport zone, which can be an overlay or a VLAN.
To create a VLAN-backed segment, add the segment in a VLAN transport zone. Similarly, to create an overlay-backed segment, add the segment in an overlay transport zone.
- (Optional) To configure DHCP on the segment, click Set DHCP Config.
For a detailed information about DHCP configuration, see Configure DHCP Service.
- If the transport zone is of type VLAN, specify a list of VLAN IDs. If the transport zone is of type Overlay, and you want to support layer 2 bridging or guest VLAN tagging, specify a list of VLAN IDs or VLAN ranges
- (Optional) Select an uplink teaming policy for the segment.
This drop-down menu displays the named teaming policies, if you have added them in the VLAN transport zone. If no uplink teaming policy is selected, the default teaming policy is used.
- Named teaming policies are not applicable to overlay segments. Overlay segments always follow the default teaming policy.
- For VLAN-backed segments, you have the flexibility to override the default teaming policy with a selected named teaming policy. This capability is provided so that you can steer the infrastructure traffic from the host to specific VLAN segments in the VLAN transport zone. Before adding the VLAN segment, ensure that the named teaming policy names are added in the VLAN transport zone.
- (Optional) Enter the fully qualified domain name.
DHCPv4 server and DHCPv4 static bindings on the segment automatically inherit the domain name from the segment configuration as the Domain Name option.
- If you want to use Layer 2 VPN to extend the segment, click the L2 VPN text box and select an L2 VPN server or client session.
You can select more than one.
- In VPN Tunnel ID, enter a unique value that is used to identify the segment.
- In the Metadata Proxy field, select a metadata proxy from the dropdown list, or click the menu icon (3 dots) to create one.
- Click Save.
- To add segment ports, click Yes when prompted if you want to continue configuring the segment.
- Click Ports and Set.
- Click Add Segment Port.
- Enter a port name.
- For ID, enter the VIF UUID of the VM or server that connects to this port.
- Select a type: Child, or Static.
Leave this text box blank except for use cases such as containers or VMware HCX. If this port is for a container in a VM, select Child. If this port is for a bare metal container or server, select Static.
- Enter a context ID.
Enter the parent VIF ID if Type is Child, or transport node ID if Type is Static.
- Enter a traffic tag.
Enter the VLAN ID in container and other use cases.
- Select an address allocation method: IP Pool, MAC Pool, Both, or None.
- Specify tags.
- Apply address binding by specifying the IP (IPv4 address, IPv4 subnet, IPv6 address, or IPv6 subnet) and MAC address of the logical port to which you want to apply address binding. For example, for IPv6, 2001::/64 is an IPv6 subnet, 2001::1 is a host IP, whereas 2001::1/64 is an invalid input. You can also specify a VLAN ID.
Manual address bindings, if specified, override the auto discovered address bindings.
- Select segment profiles for this port.
- To select segment profiles, click Segment Profiles .
- (Optional) To bind a static IP address to the MAC address of a VM on the segment, expand DHCP Static Bindings, and then click Set.
Both DHCP for IPv4 and DHCP for IPv6 static bindings are supported. For detailed steps on configuring static binding settings, see Configure DHCP Static Bindings on a Segment.
- Click Save.
If NSX Federation is configured, this feature of reconfiguring a segment by clicking on an entity is applicable to segments created by the Global Manager (GM) as well. Note that from the Local Manager, you can create ports for a GM-created segment because you cannot create segment ports from the Global Manager.