Enable network redundancy across NDC and PCIe Ports

Enable network redundancy after the VxRail deployment. Migrate the VxRail network traffic on a node from the NDC port to
both NDC and PCIe ports.
You must be able to configure the adjacent ToR switches to complete this task.

Review the network redundancy options and select the option that fits your requirements. ( see vxrail 8.0-x admin guide, section)

1. Verify that the VxRail version supports network redundancy
   • Home > Hosts and Clusters >Configure > VxRail > System.
2. Verify that the VxRail cluster is healthy
   • select the VxRail cluster >Monitor tab> VxRail > Physical View > Health State
3. Verify the VxRail physical network compatibility and the unused physical adapters
   • Home > Hosts and Clusters > VxRail Cluster > Configure > Networking > Physical adapters.
4. Repeat these steps for each node in the VxRail cluster.
5. Verify the physical switch port configuration
   • To discover the VxRail node connections, your switch operating system must support the LLDP neighbor functionality.
   • ssh to Tor switches
     • verify the ports that are connected to the VxRail nodes and VMNIC assignment
       • show lldp neighbors | grep vmnic

18KK-TOR-A# show lldp neighbors | grep vmnic
ethernet1/1/3 mrm-md-nl.mrmvxa... e4:43:4b:5e:04:f0 vmnic0
ethernet1/1/4 mrm-md-nl.mrmvxa... e4:43:4b:5e:04:f2 vmnic2
ethernet1/1/5 mrm-md-n3.mrmvxa... e4:43:4b:5e:07:90 vmnic0
ethernet1/1/6 mrm-md-n3.mrmvxa... e4:43:4b:5e:07:92 vmnic2
ethernet1/1/7 mrm-md-n2.mrmvxa... e4:43:4b:5f:84:50 vmnic0
ethernet1/1/8 mrm-md-n2.mrmvxa... e4:43:4b:5f:84:52 vmnic2

18KK-TOR-A# show lldp neighbors | grep vmnic
ethernet1/1/3 mrm-md-nl.mrmvxa... e4:43:4b:5e:04:f0 vmnic0
ethernet1/1/4 mrm-md-nl.mrmvxa... e4:43:4b:5e:04:f2 vmnic2
ethernet1/1/5 mrm-md-n3.mrmvxa... e4:43:4b:5e:07:90 vmnic0
ethernet1/1/6 mrm-md-n3.mrmvxa... e4:43:4b:5e:07:92 vmnic2
ethernet1/1/7 mrm-md-n2.mrmvxa... e4:43:4b:5f:84:50 vmnic0
ethernet1/1/8 mrm-md-n2.mrmvxa... e4:43:4b:5f:84:52 vmnic2

18KK-TOR-B# show lldp neighbors | grep vmnic
ethernet1/1/3 mrm-md-nl.mrmvxa... e4:43:4b:5e:04:f1 vmnic1
ethernet1/1/4 mrm-md-nl.mrmvxa... e4:43:4b:5e:04:f3 vmnic3
ethernet1/1/5 mrm-md-n3.mrmvxa... e4:43:4b:5e:07:91 vmnic1
ethernet1/1/6 mrm-md-n3.mrmvxa... e4:43:4b:5e:07:93 vmnic3
ethernet1/1/7 mrm-md-n2.mrmvxa... e4:43:4b:5f:84:51 vmnic1
ethernet1/1/8 mrm-md-n2.mrmvxa... e4:43:4b:5f:84:53 vmnic3

18KK-TOR-B# show lldp neighbors | grep vmnic
ethernet1/1/3 mrm-md-nl.mrmvxa... e4:43:4b:5e:04:f1 vmnic1
ethernet1/1/4 mrm-md-nl.mrmvxa... e4:43:4b:5e:04:f3 vmnic3
ethernet1/1/5 mrm-md-n3.mrmvxa... e4:43:4b:5e:07:91 vmnic1
ethernet1/1/6 mrm-md-n3.mrmvxa... e4:43:4b:5e:07:93 vmnic3
ethernet1/1/7 mrm-md-n2.mrmvxa... e4:43:4b:5f:84:51 vmnic1
ethernet1/1/8 mrm-md-n2.mrmvxa... e4:43:4b:5f:84:53 vmnic3

6. Identify a switch port that supports VxRail Network traffic.

7. Identify an unused switch port that is planned as target port to enable network redundancy.

8. To ensure the switch port that supports the VxRail network traffic after migration has a compatible configuration, perform
the following:
a. Verify that the VLANs used for VxRail networks (external management, internal management, VMware vSphere vMotion,
VMware vSAN, and guest networks) are compatible on both the switch ports.
b. Verify that the other switch port settings are compatible on both the switch ports.
c. If your final configuration reduces the number of uplinks, verify that the VLANs, and the other switch port settings are
consolidated into the target switch ports.
The following is a sample switch configuration for a source NDC port and a target PCIe port.

• interface ethernet1/1/3

interface ethernet1/1/3
 description VxRail-NDC-Port
 no shutdown
 switchport mode trunk
 switchport access vlan 1386
 switchport trunk allowed vlan 100-103,3939
 mtu 9216
 flowcontrol receive on
 flowcontrol transmit off
 spanning-tree port type edge
exit

interface ethernet1/1/3
 description VxRail-NDC-Port
 no shutdown
 switchport mode trunk
 switchport access vlan 1386
 switchport trunk allowed vlan 100-103,3939
 mtu 9216
 flowcontrol receive on
 flowcontrol transmit off
 spanning-tree port type edge
exit

9. Verify active uplink on the VMware VDS port groups post migration

• Review the planning grid table that is populated with the starting and ending network configuration to identify any uplinks that are disconnected as part of the uplink reassignment process.
  • Networking> VMware HCIA Distributed Switch > t Distributed Port Group > Manage Distributed Port Groups > Teaming and Failover
  • Select all the VMware VDS port groups.
  • Verify at least one of the active uplinks in the failover order is not disconnected during the migration task
  • If there is an uplink under Active uplinks, that uplink gets disconnected during the migration. Modify the failover order to
  • move an uplink that might not get disconnected during the migration to Active uplinks.

10. Add uplinks to the VMware VDS

• From the VMware vSphere Web Client, select Networking inventory view.
• Right-click the VMware HCIA Distributed Switch and select Settings > Edit Settings.
• Click Uplinks to display the existing uplinks.
• Click ADD to add the uplinks according to the planning grid table populated in Enable network redundancy across NDC and PCIe ports and click OK