Server Network Teaming; Creating Host-Side Vpc For Server Links With Lacp - Cisco Nexus B22HP Design And Deployment Manual

Server Network Teaming

Server NIC teaming provides an additional layer of redundancy to servers. It allows multiple links to be available,
for redundancy. In the blade server environment, server network teaming was typically limited to active-standby
configurations and could not provide active-active links, because active-active links required EtherChannel or Link
Aggregation Control Protocol (LACP) connection to a single switch. Since the Cisco Nexus B22HP fabric extender
is an extension of the parent switch, EtherChannel or LACP connections can be created between the blade server
and the virtual chassis. Dual Cisco Nexus 5000 Series switches can be used with vPC for additional switch
redundancy while providing active-active links to servers, thus enabling aggregate 40-Gbps bandwidth with dual
links (Figure 4).
Figure 4.

Creating Host-Side vPC for Server Links with LACP

1. Enable LACP on both parent switches.
5548-Bottom (config)# feature lacp
2. Create the blade server vPC and add the member interface.
nexus-5548-Bottom# configure terminal
Enter configuration commands, one per line.
5548-Bottom(config)# interface port-channel 201
5548-Bottom(config-if)# vpc 201
5548-Bottom(config-if)# switchport mode access
5548-Bottom(config-if)# no shutdown
5548-Bottom(config-if)# interface ethernet 103/1/1
5548-Bottom(config-if)# channel-group 201 mode active
nexus-5558-Top# configure terminal
Enter configuration commands, one per line.
5548-Top(config)# interface port-channel 201
5548-Top(config-if)# vpc 201
5548-Top(config-if)# switchport mode access
5548-Top(config-if)# no shutdown
5548-Top(config-if)# interface ethernet 104/1/1
5548-Top(config-if)# channel-group 201 mode active
© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Fabric Link and Server Topologies
End with CNTL/Z.
End with CNTL/Z.
Page 13 of 41