You can add an NSX Edge VM to the NSX-T Data Center fabric and proceed to configure it as a NSX Edge transport node VM.
- Transport zones must be configured. See Create Transport Zones.
- Verify that compute manager is configured. See Add a Compute Manager.
- An uplink profile must be configured or you can use the default uplink profile for NSX Edge nodes. See Create an Uplink Profile.
- An IP pool must be configured or must be available in the network deployment. See Create an IP Pool for Tunnel Endpoint IP Addresses.
- From a browser, log in with admin privileges to an NSX Manager at https://<nsx-manager-ip-address>.
- Select .
- Type a name for the NSX Edge.
- Type the Host name or FQDN from vCenter Server.
- For an optimal performance, reserve memory for the NSX Edge appliance.
Set the reservation to ensure that NSX Edge has sufficient memory to run efficiently. See NSX Edge VM System Requirements.
- Specify the CLI and the root passwords for the NSX Edge.
Your passwords must comply with the password strength restrictions.
- At least 12 characters
- At least one lower-case letter
- At least one upper-case letter
- At least one digit
- At least one special character
- At least five different characters
- Default password complexity rules are enforced by the Linux PAM module
- Enter the NSX Edge details.
Option Description Compute Manager Select the compute manager from the drop-down menu.
The compute manager is the vCenter Server registered in the Management Plane.
Cluster Designate the cluster the NSX Edge is going to join from the drop-down menu. Resource Pool or Host Assign either a resource pool or a specific host for the NSX Edge from the drop-down menu. Datastore Select a datastore for the NSX Edge files from the drop-down menu.
- Enter the NSX Edge interface details.
Option Description IP Assignment
It is the IP address assigned to NSX Edge node which is required to communicate with NSX Manager and NSX Controller.Select DHCP or Static IP.If you select Static, enter the values for:
- Management IP: Enter IP address of NSX Edge in the CIDR notation.
- Default gateway: Enter the gateway IP address of NSX Edge.
Management Interface Select the management network interface from the drop-down menu. This interfaces must either be reachable from NSX Manager or must be in the same management interface as NSX Manager and NSX Controller.
The NSX Edge management interface establishes communication with the NSX Manager management interface.
- Select the transport zones that this transport node belongs to.
An NSX Edge transport node belongs to at least two transport zones, an overlay for NSX-T Data Center connectivity and a VLAN for uplink connectivity.Note: NSX Edge Nodes support multiple overlay tunnels (multi-TEP) when the following prerequistes are met:
- TEP configuration must be done on one N-VDS only.
- All TEPs must use same transport VLAN for overlay traffic.
- All TEP IPs must be in same subnet and use same default gateway.
- Enter the N-VDS information.
Option Description Edge Switch Name Select a VLAN or Overlay switch from the drop-down menu. Uplink Profile Select the uplink profile from the drop-down menu.
The available uplinks depend on the configuration in the selected uplink profile.
IP address is assigned to the NSX Edge switch that is configured. It is used to route packets on an overlay or VLAN network.Select Use IP Pool or Use Static IP List for the overlay N-VDS.
- If you select Use Static IP List, specify:
- Static IP List: Enter a list of comma-separated IP addresses to be used by the NSX Edge switch.
- Gateway: Enter the default gateway IP address, which is used to route packets between NSX Edge transport nodes in an overlay network.
- Subnet mask: Enter the subnet mask for the configured gateway.
- If you selected Use IP Pool for IP assignment, specify the IP pool name.
DPDK Fastpath Interfaces / Virtual NICs Select the data path interface name for the uplink interface.Note: If the uplink profile applied to the Edge node is using a Named Teaming policy, ensure the following condition is met:
- All uplinks in the Default Teaming policy must be mapped to the physical network interfaces on the Edge VM for traffic to flow through a logical switch that uses the Named Teaming policies.
- LLDP profile is not supported on an NSX Edge VM appliance.
- Uplink interfaces are displayed as DPDK Fastpath Interfaces if the NSX Edge is installed using NSX Manager or on a Bare Metal server.
- Uplink interfaces are displayed as Virtual NICs if the NSX Edge is installed manually using vCenter Server.
- If you select Use Static IP List, specify:
- View the connection status on the Transport Nodes page.
After adding the NSX Edge as a transport node, the connection status changes to Up in 10-12 minutes.
- (Optional) View the transport node with the GET https://<nsx-manager>/api/v1/transport-nodes/<transport-node-id> API call.
- (Optional) For status information, use the GET https://<nsx-mgr>/api/v1/transport-nodes/<transport-node-id>/status API call.
- If you see inaccurate resource configuration details, such as compute, datastore, or network details that were configured when you installed the NSX Edge node, refresh the configuration details by running the API command.
POST api/v1/transport-nodes/<transport-node-id>?ction=refresh_node_configuration&resource_type=EdgeNodeNSX Manager displays inaccurate or stale NSX Edge node details if one of these conditions are true:
- On the NSX Edge node, if you change settings such as SSH, NTP, DNS and so from the NSX Edge command line interface.
- If the NSX Edge VM appliance is moved to another host using vCenter, the NSX Manager may have stale values of compute, datastore, and network configuration based on the configuration of the new host.
What to do next
Add the NSX Edge node to an NSX Edge cluster. See Create an NSX Edge Cluster.