In the article Configuring Scalable Low Latency L2 Leaf-Spine Network Fabrics with Dell Networking Switches I wrote about the general set up of the leaf spine architecture in my Nutanix performance lab with Dell Force 10 switches. Then in VMware Distributed vSwitch LACP Configuration with Dell Force10 and Cumulus Linux I wrote about the VMware vDS and Cumulus Linux configuration on Dell Force 10 networks switches. This article will cover the port-channel configuration for hosts connected to Dell Force 10 switches running the Force 10 OS (FTOS).
As with the configuration of the previous articles each host is configured with 2 x 10GbE Ports and each port is connected to a different Top of Rack (ToR) or Middle of Rack (MoR) switch that is part of a MLAG/CLAG/VLT pair.
Below is the physical port configuration, which is similar to a standard port, other than having the additional port-channel specification. It should refer to the same port-channel number on both ToR/MoR switches.
interface TenGigabitEthernet 0/0 description Node-ntnx3450a1 no ip address mtu 9216 flowcontrol rx on tx off ! port-channel-protocol LACP port-channel 1 mode active no shutdown
The port-channel config should be the same for each host on both ToR/MoR switches. The parameter vlt-peer-lag port-channel 1 specifies that this port is the same as port-channel 1 on the peer switch.
interface Port-channel 1 description Node-ntnx3450a1 no ip address mtu 9216 portmode hybrid switchport spanning-tree rstp edge-port bpduguard shutdown-on-violation spanning-tree 0 portfast bpduguard shutdown-on-violation lacp fast-switchover vlt-peer-lag port-channel 1 no shutdown
It is fairly simple to set up port-channels for redundant LACP configurations from hosts to VLT/MLAG ToR/MoR Dell Force 10 switches and FTOS. Although this does mean additional configuration is required for every single host port on every switch. The main use case for this is where you are likely to run something like VMware NSX and wish to be able to utilize multiple links, as NSX does not support load based teaming. For most normal enterprise virtualization use cases Load Based Teaming provides the best balance, best utilization and simplest configuration of both the vSphere Distributed Switch and the physical switches as well.
This post first appeared on the Long White Virtual Clouds blog at longwhiteclouds.com. By Michael Webster +. Copyright © 2012 – 2015 – IT Solutions 2000 Ltd and Michael Webster +. All rights reserved. Not to be reproduced for commercial purposes without written permission.