Create Nodes continued
In System, Fabric, Nodes, Edge Clusters, add an edge cluster object used later as a container for the edge transport nodes. Choose a name and keep the default profile which contains settings for high availability checks for BFD (Bidirectional Forwarding Detection).
Edge Cluster
An Edge Cluster is used to balance services like Service Routers (SRs) and Distributed Routers (DRs) later.
Edge Transport Node
Here, we are in the management network VLAN 3011, in which the NSX-T Manager is located and from the same subnet, IPs will be used for the Edge Transport Nodes. A FQDN for the node is required, so create a DNS entry first.
You could go with Form Factor Small, but I will continue to play and create a Load Balancer as well and use Medium Form Factor. Check Advanced Resource Reservations in which you could remove the memory reservation (please do not change in production environment), if needed.
Enter credentials – for learning and/or troubleshooting purposes, you could activate SSH and Root SSH Login.
For the deployment of the Edge Node, choose the Edge Cluster.
In Configure Node Settings, the IP addresses entered here are from the management network in which the NSX-T manager is located as well.
In this step, please see the information about the Edge Switch Name in the white box of the screenshot:
First, configure the Overlay Transport Zone:
We use the default “nsx-edge-single-nic-uplink-profile” here with IP addresses from the pool created earlier for VLAN 3010.
Second, configure the Vlan Transport Zone for the uplink to the VyOS router:
We use the default “nsx-edge-single-nic-uplink-profile” here. The port group of VLAN 3009 is used as the connection to the outside world. Once, the Edge has been deployed, it needs to be added to the Edge-Cluster object:
In this overview, the assignment of the vnics of the Edge VM to the “fastpath” is visible, eth0 is always the management NIC.
You should add a second Edge Transport Node and add it to the Edge-Cluster object as well.
mhvmw.wordpress.com 