Dell Force10 C150 Manual page 24

Deploying the Dell Force10 MXL into a Cisco Nexus Network Environment
Enable Per-VLAN Spanning Tree on the MXL
Most Cisco Nexus networks run per-VLAN spanning tree and the MXL is capable of natively participating
in the version of the spanning tree protocol. Here are the commands required to enable it.
MXL1#configure
MXL1(conf)#protocol spanning-tree pvst
MXL1(conf-pvst)#no disable
MXL1(conf-pvst)#exit
MXL1(conf)#exit
MXL1#
Configure the MXL Uplink Port-Channel Links
On the MXL side of the Nexus vPC multi-chassis LAG, there is only a single LAG configured for uplink on
both top-of-rack switches. Here are the commands used to configure the uplink LAG on MXL1 in the
example network.
MXL1#configure
MXL1(conf)#interface port-channel 20
MXL1(conf-po-20)#switchport
MXL1(conf-po-20)#exit
MXL1(conf)#interface range tengigabitethernet 0/33 - 36
MXL1(conf-if-range-te-0/33-36)#port-channel-protocol lacp
MXL1(conf-if-range-te-0/33-36-lacp)#port-channel 20 mode active
MXL1(conf-if-range-te-0/33-36-lacp)#exit
MXL1(conf-if-range-te-0/33-36)#exit
MXL1(conf)#exit
MXL1#
Note that on the MXL using the 10Gb links 33 – 36 as in the example network requires splitting the 40Gb
port 33 into four 10Gb links as covered in the Initial Deployment section.
Configure Tagged VLANs for the Trunk Port Uplinks
A substantial difference between the MXL's FTOS CLI and the Nexus CLI is that VLAN port membership
is configured inside the VLAN interface (instead of inside the Ethernet interface). Here are the
commands run to establish vlan membership for the uplink LAG on MXL1 in the example network.
MXL1#configure
MXL1(conf)#interface range vlan 11 - 13
MXL1(conf-if-range-vl-11-13)#tagged Port-channel 20
MXL1(conf-if-range-vl-11-13)#exit
MXL1(conf)#exit
MXL1#
Note that the VLANs are only added to the port-channel interface and not to the individual link
member interfaces. On the MXL, individual links in a port-channel do not switch traffic when not
attached to the port channel.
24