HP Virtual Co onnect Flex-10 & FlexFa abric Cisco Nexus 5000 & 2000 series o Integr ration

Technica white paper al r Table of contents

Introductio ....................................... on ...................... .......................................... ..................................... 2 Cisco Nex Fabric Extenders 2000 series ................ xus ..................................... 2 .......................................... .......................................... Cisco Virtu Port Channel (vPC) .......... ual ...................... ..................................... 3 vPC Topol logy.................................... ...................... ..................................... 4 .......................................... vPC Limita ations .................................. ...................... ..................................... 4 .......................................... Scenari 1: Lab Desig and Configuration based o Cisco EtherC io gn on Channel Feature ................................... 5 e Scenari 2a: Lab Desi and Config io ign guration based on Cisco Ether Channel Featu in a Dual Homed Fabric r ure Extende Topology ......................... er ...................... .......................................... ..................................... 9 Scenari 2b: Lab Desi based on Cisco Virtual Po Channel (vPC Feature in a Single Homed Fabric io ign C ort C) Extende Topology ......................... er ...................... .......................................... ..................................... 9 Scenari 3: Lab Desig and Configuration based o Cisco Virtual Port Channel ( io gn on (vPC) Feature................ 10 For more information .......................... i ...................... .......................................... ................................... 20

Introduction
This document will cover how to configure Cisco Nexus 5000 series switches, and Cisco Nexus 2000 series Fabric Extender specifically Cisco Nexus 2232PP Fabric Extender based on two logical architecture lab designs shown in a later section. The purpose of this document is to highlight Cisco Ether Channel and Cisco Virtual Port Channel (vPC) features to easily interoperate with HP Virtual Connect Flex-10 Interconnect Module and HP Virtual Connect FlexFabric Interconnect Module. This document does not recommend or try to present by any way the general network best practice design architecture for any of HP or Cisco products including the products specifically used in this document. This document was produced based on the behaviour of different lab designs architecture utilizing the below mentioned hardware list of equipment in a test lab environment. It is totally up to the reader to change the architecture and the configuration as per the mentioned product support feature list and business need requirements. The terminologies and definitions of Cisco technologies are all based on Cisco definitions from the public information published in www.cisco.com. This document covers some of the Cisco Nexus 2000 series Fabric Extender definitions to familiarise the reader with Cisco terminologies that are used later in the lab. It does not cover how to add Cisco Nexus Fabric Extender 2000 series to its parent Cisco Nexus 5000 series switch. It assumes that you know how to add a Cisco Nexus 2000 Fabric Extender to its parent Cisco Nexus 5000 series switch in a Single Homed vPC Topology. The lab design architecture components used in this document are: HP c7000 series Enclosure HP Virtual Connect Flex-10 Cisco Nexus 5020 switch Cisco Nexus 2232PP Fabric Extender

This Document will cover design scenario 1 and design scenario 3 in more details including Cisco NX-OS CLI configuration and verification commands. For more technical information about HP Virtual Connect please visit http://www.HP.com/go/VirtualConnect

Cisco Nexus Fabric Extenders 2000 series

As described in Cisco Systems website, Cisco Nexus Fabric Extenders 2000 series integrates with its parent switch, Cisco Nexus 5000 series, to get its configuration from the settings of the parent switch. There is no software included in the Fabric Extenders 2000 series and it gets its operating system from its parent switch. Cisco Fabric Extenders 2000 series connect to its parent switch using a Fabric Interface. Fabric Interface is a 10-Gigabit Ethernet uplink port designated for connection from the Fabric Extender to its parent switch. A fabric interface cannot be used for any other purpose. It must be directly connected to the parent switch. You can combine Fabric Interfaces together to form a logical bundle called EtherChannel Fabric Interface to communicate between Fabric Extenders 2000 series and its parent switch. End host or server connectivity should be connected to Cisco Nexus Fabric Extender 2000 series through a Host

Interface that might pa articipate in a logical bund le called Ethe erChannel Hos Interface tha can group st at up to 8 Host Interfaces H s. annel Host Inte erface was ad dded to the Fa abric Extender from Cisco N NX-OS Releas se EtherCha 4.2(1)N1 1(1). Bridge Protocol Data Unit (BPDU) G P Guard is enab bled by default in all Host Interfaces and d you cann disable it. Based on that you cannot connect a sw not witch or a bridg to a Host ge Interface as BPDU Gua will put th Host Interfa in error-dis ard he ace sabled state w when a BPDU is received. The Cisco Nexus 2232 Fabric Ex o 2PP xtender has ei ight 10-Gigab Ethernet fabric interfaces and 32 10bit Gigabit Ethernet host interfaces. In the best case scenario, you can have a 4 to 1 oversu E i t u ubscription (4 host inter rfaces for one fabric interfa ace) or higher . The Cisco N Nexus Fabric E Extender 2000 Series does s not perfo any local switching. All traffic is sent to the parent switch that p orm l t provides centr ral forwardin even inclu ng, uding host-to-h communic host cations betwe two system connected to the same een ms Fabric Ex xtender. NOTE: N It is very impo ortant to upgra the Nexus 5000 series switches that manage the Nexus ade s s 2232PP Fabric Extender to the latest NX 2 X-OS release 4 4.2(1)N2(1). Cisco had di ifferent bugs in some of the NX-OS softw e ware branches in processing LACP PDU w 1 second timeout s with d which in some cases preven establishing a LACP port channel betw w e nt g t ween HP Virtu Connect ual and Nexus 22 a 232PP Fabric Extender. So me of these N NX-OS bugs a covered un are nder CSCtf22871 Bug Details, CSCte09024 Bug Details, a CSCtf22871 Bug Deta C C and ails. These bugs were firs discovered in NXOS rele b st eases 4.1(3)N N1(0.164), 4.2(1)N1(0.267 7), 4.2(1)N1(0.269), 4.2(1)N1(0.284), 4.2 4 2(1)N1(0.323 and 4.0(1a)N2(1a). NX 3), X-OS 4.2(1)N2(1) is the latest an first release to support LA 4 s nd e ACP PDU with 1 second tim h meout which provides more stability to th LACP port. p e he

Cisco Virtual Port Channel (v o vPC)

Starting from Cisco NX f X-OS release 4.1(3)N1(1), you can conf figure vPC be etween Cisco Nexus 5000 ser switches that are direct connected to Cisco Nex 2000 series Fabric Exte ries t tly xus enders. vPC Ter rminology vPCThe com v mbined EtherC Channel betw ween the vPC p peer devices and the down nstream device. d vPC peer de v eviceOne of a pair of de o evices that ar connected w the speci re with ial EtherChannel known as the vPC peer lin k E e vPC peer lin nkThe link used to synch hronize states between the vPC peer dev s vices. It is recommended that you use LACP on the peer-link, bec r d cause LACP p provides config guration checks agains a configurat c st tion mismatch on the EtherC h Channel. vPC membe portInterfaces that be v er elong to the vP PCs. Host vPC po H ortFabric Extender host i interfaces that belong to a vPC. t vPC domain v nThis domain includes bo vPC peer devices, the v oth vPC peer-keep palive link, and all of the port channels in the vPC co a s he onnected to th downstream devices. It isalso associated to the configuration mode tha you must us to assign vPC global parameters. The a at se vPC domain ID must be the same on bot h switches. v D vPC peer-ke v eepalive lin nkThe peer--keepalive link monitors the vitality of a v k e vPC peer. Cisco Nexus 5000 Series device and it must be differ C 5 d rent than the v vPC peer link. The peer.

keepalive link sends configurable, period keepalive messages be k dic etween vPC pe devices. eer No data or sy N ynchronization traffic moves over the vPC peer-keepal n s C live link; the o only traffic on this link is a message that indicates that the originating switch is op m perating and running vPCs. . You must have Layer 3 connectivity betw Y e ween the peer switches to tr ransmit these messages; the e system cannot bring up the vPC peer link unless a pee s t k erkeepalive lin is already up and nk running. r

NOTE: You can use either managemen VRF or default VRF for the vPC peer-ke N c r nt e eepalive link. In case you want to use the default VRF, then you hav to configure a dedicated VLAN, and w e ve e d a VLAN Interfa to carry the vPC peer-k ace keepalive mes ssages. Also it is important to use a unique Layer 3 IP address subnet with 30 network bits subnet mask (255.255.255.252 or u s 0 s k /30) to avoid any IP addre / esses conflict i n your netwo and assure the highest r ork e reliability to the vPC keepa alive communication.

vPC Topology T y
There are 2 different vPC topology configurations Single Hom Fabric Ex e v s, med xtender vPC To opology and Dual Hom Fabric Ex med xtender vPC Topology. In S Single Homed Fabric Extend vPC Topo der ology you will be able to support Dua Homed Ser al rver communic cation. You w be only all will lowed to supp Single port Homed Server communication in Du Homed Fa S ual abric Extender vPC Topolog which utiliz r gy zing the mechanis to manage a single Cisc Nexus Fab Extender from 2 differe Cisco Nex 5000 sm e co bric ent xus series sw witches that wa introduced in NX-OS rel ease 4.1(3). as

NOTE: It is very important to configure your vPC top N v t pology betwee Cisco Nexu 5000 en us series switches and Cisco Nexus 2000 s s s N series Fabric E Extenders usin Single Hom Fabric ng med Extender vPC Topology. ON in this top E NLY pology you w be able to support DUA Homed will AL Server Edge Communicatio between HP Virtual Conn S C on P nect and Cisc Nexus 200 Fabric co 00 Extender utiliz E zing vPC featu as shown later in scena 3. The rea ure ario ason is due to a limitation o in the Cisco Nexus 2000 Fabric Extende as a Fabric Extender can be a membe of a Host N er c n er nder vPC topo ology but not b both simultane eously Interface vPC topology or a Fabric Exten

vPC Limitation L ns
vPC featu and vPC peer-keepalive link must be enabled and configured b ure p e d before configu uring vPC peer link. Also You mu configure both vPC pee r switches as the configura ust b ation is not aut tomatically n synchronized between the vPC peer devices. n be l vPCs can only have EtherChannels. A vPC can b configured on a normal EtherChannel (switchtoswitch vP topology), on an EtherC PC Channel fabric interface (fab extender vPC topology and on an c bric y), EtherCha annel host inte erface (host interface vPC to opology). onfigure vPC in the mainten nance time w indow as you may experie u ence traffic dis sruption while e Plan to co configuring vPCs.

Scenar 1: Lab Design and Config rio b a guration b based on C Cisco Ethe erChannel Feature e
As shown in the below diagram (dia n w agram1), the first HP c700 enclosure h two HP Vi 00 has irtual Connect Flex-10 Interc connect modules in Bay1 a nd Bay2. HP Virtual Conne Flex-10 in Bay1 ect 2 ted 0GbE uplink p ports to Nexus 2232PP-1 an Nexus s nd and Bay2 are connect using a total of four 10 2232PP-2 to support up to 40GbE uplink bandw 2 u u width to the en nclosure. b w Cisco EtherCh hannel feature using a Sing Homed e gle In this lab design architecture we will configure C vPC Fabr Extender Topology and a Dual Home Server Edg communica ric ed ge ation Setup.

Nexus-5020-1(config)# feature lacp Nexus-5020-1(config)# interface port-channel11 Nexus-5020-1(config-if)# description connection to Enc1-Flex10-Bay1 Nexus-5020-1(config-if)# switchport mode trunk Nexus-5020-1(config-if)# switchport trunk allowed vlan 101-109 Nexus-5020-1(config-if)# spanning-tree port type edge trunk Nexus-5020-1(config)# interface Ethernet100/1/1, Ethernet100/1/2 Nexus-5020-1(config-if)# description connection to Enc1-Flex10-Bay1 Nexus-5020-1(config-if)# lacp rate fast Nexus-5020-1(config-if)# switchport mode trunk Nexus-5020-1(config-if)# switchport trunk allowed vlan 101-109 Nexus-5020-1(config-if)# channel-group 11 mode active Nexus-5020-2(config)# feature lacp Nexus-5020-2(config)# interface port-channel12 Nexus-5020-2(config-if)# description connection to Enc1-Flex10-Bay1 Nexus-5020-2(config-if)# switchport mode trunk Nexus-5020-2(config-if)# switchport trunk allowed vlan 101-109 Nexus-5020-2(config-if)# spanning-tree port type edge trunk Nexus-5020-2(config)# interface Ethernet101/1/1, Ethernet101/1/2 Nexus-5020-2(config-if)# description connection to Enc1-Flex10-Bay2 Nexus-5020-2(config-if)# lacp rate fast Nexus-5020-2(config-if)# switchport mode trunk Nexus-5020-2(config-if)# switchport trunk allowed vlan 101-109 Nexus-5020-2(config-if)# channel-group 12 mode active ! Verification some output is filtered to only highlight used interfaces Nexus-5020-1(config)# show run interface po11 !Command: show running-config interface port-channel11 !Time: Sun Sep 5 19:19:47 2010 version 4.2(1)N2(1) interface port-channel11 switchport mode trunk switchport trunk allowed vlan 101-109 spanning-tree port type edge trunk

Enable lacp feature Create EtherChannel 11 Enable Trunk Allow required VLANs Consider the interface as edge port (enable portfast) even in trunk mode

Enable LACP Fast Timeout add physical interfaces to the EtherChannel

Same Configuration for N5020-2

Nexus-5020-2# show run int po12 !Command: show running-config interface port-channel12 !Time: Mon Sep 6 01:18:27 2010 version 4.2(1)N2(1) interface port-channel12 switchport mode trunk switchport trunk allowed vlan 101-109 spanning-tree port type edge trunk

Nexus-5020-1(config)# show interface status up Port Name Status Vlan Duplex Speed Type ----------------------------------------------------------------------------------------------------------Po11 connection to Enc1 up trunk full 10G -Eth100/1/1 connection to Enc1 up trunk full 10G -Eth100/1/2 connection to Enc1 up trunk full 10G --

Nexus-5020-1# show int trunk -------------------------------------------------------------------------------------------Port Native Vlan Status Port Channel --------------------------------------------------------------------------------------------

Po11 1 trunking -Eth100/1/1 1 trnk-bndl Po11 Eth100/1/2 1 trnk-bndl Po11 -------------------------------------------------------------------------------------------Port Vlans Allowed on Trunk -------------------------------------------------------------------------------------------Po11 101-109 Eth1100/1/1 101-109 Eth100/1/2 101-109 -------------------------------------------------------------------------------------------Port Vlans Err-disabled on Trunk -------------------------------------------------------------------------------------------Po11 none Eth100/1/1 none Eth100/1/2 none -------------------------------------------------------------------------------------------Port STP Forwarding -------------------------------------------------------------------------------------------Po11 101-108 Eth100/1/1 none Eth100/1/2 none

Nexus-5020-2(config)# show interface status up ---------------------------------------------------------------------------------------------------Port Name Status Vlan Duplex Speed Type ---------------------------------------------------------------------------------------------------Po12 connection to Enc1 up trunk full 10G -Eth101/1/1 connection to Enc1 up trunk full 10G -Eth101/1/2 connection to Enc1 up trunk full 10G --

Nexus-5020-2# show int trunk ------------------------------------------------------------------------------------Port Native Vlan Status Port Channel Po12 1 trunking -Eth101/1/1 1 trnk-bndl Po12 Eth101/1/2 1 trnk-bndl Po12 ------------------------------------------------------------------------------------Port Vlans Allowed on Trunk ------------------------------------------------------------------------------------Po12 101-109 Eth101/1/1 101-109 Eth101/1/2 101-109 ------------------------------------------------------------------------Port Vlans Err-disabled on Trunk ------------------------------------------------------------------------Po12 none Eth101/1/1 none Eth101/1/2 none ------------------------------------------------------------------------Port STP Forwarding ------------------------------------------------------------------------Po12 101-108 Eth101/1/1 none Eth101/1/2 none

Nexus-5020-1# show spanning-tree interface po11 Vlan --------VLAN0101 VLAN0102 VLAN0103 VLAN0104 VLAN0105 VLAN0106 VLAN0107 Role ---Desg Desg Desg Desg Desg Desg Desg Sts --FWD FWD FWD FWD FWD FWD FWD Cost --------1 1 1 1 1 1 1 Prio.Nbr -------128.4196 128.4196 128.4196 128.4196 128.4196 128.4196 128.4196 Type ----------------------------------------------Edge P2p Edge P2p Edge P2p Edge P2p Edge P2p Edge P2p Edge P2p

VLAN0108 Desg FWD 1

128.4196 Edge P2p

Nexus-5020-2# show spanning-tree interface po12 Vlan --------VLAN0101 VLAN0102 VLAN0103 VLAN0104 VLAN0105 VLAN0106 VLAN0107 VLAN0108 Role ---Desg Desg Desg Desg Desg Desg Desg Desg Sts --FWD FWD FWD FWD FWD FWD FWD FWD Cost --------1 1 1 1 1 1 1 1 Prio.Nbr -------128.4196 128.4196 128.4196 128.4196 128.4196 128.4196 128.4196 128.4196 Type ----------------------------------------------Edge P2p Edge P2p Edge P2p Edge P2p Edge P2p Edge P2p Edge P2p Edge P2p

Scenar 2a: Lab Design and Conf rio figuration based on Cisco Eth n her Chann Feature in a Dua Homed Fabric Ex nel e al xtender To opology
As shown in the below diagram (dia n w agram2A), th first HP c70 he 000 enclosure has two HP V e Virtual Connect Flex-10 Interc connect modules in Bay1 a nd Bay2. HP Virtual Conne Flex-10 in Bay1 and ect e f to 32PP-1 and N Nexus 2232PPBay2 are connected using a total of four 10GbE uplink ports t Nexus 223 2 to supp up to 40G uplink ba port GbE andwidth to th enclosure. he b w Cisco EtherCh hannel and Ci isco Virtual Po ort In this lab design architecture we will configure C Channel (vPC) features using a Dua Homed vPC Fabric Extender Topology and a Dual H s al C y Homed Server Edge com mmunication Setup. S from the FOU connected physical inter NE sical link will be available f UR rfaces to Only ON active phys HP Virtua Connect Fle al ex-10 in Bay1 and HP Virtu Connect Fe ual elx-10 in Bay2 as a result f Cisco for vPC Dual Home Topology limitation The other T ns. THREE physica interfaces w be in stan al will ndby state. d hitecture in not recomm n mend due to Cisco vPC Dual Home o ed Below design arch Topolog limitation gy ns

Scenar 2b: Lab Design based on Cisco Virtual Port Channel ( rio n (vPC) Feature in a Single Home Fabric E e ed Topology Extender T
As shown in the below diagram (dia n w agram2B), the first HP c70 e 000 enclosure has two HP V e Virtual

Connect Flex-10 Interc connect modules in Bay1 a nd Bay2. HP Virtual Conne Flex-10 in Bay1and ect e f to 32PP-1 and N Nexus 2232PPBay2 are connected using a total of four 10GbE uplink ports t Nexus 223 2 to supp up to 40G uplink ba port GbE andwidth to th enclosure. he b w Cisco EtherCh hannel and Ci isco Virtual Po ort In this lab design architecture we will configure C Channel (vPC) features using a Sing Homed vP Fabric Exte s gle PC ender Topolog and a Dual Homed gy Server Ed communic dge cation Setup. NE cal nnel link will b available f be from the TWO connected in O nterfaces to Only ON active logic EtherChan HP Virtua Connect Fle al ex-10 in Bay1 and HP Virtu Connect Fe ual elx-10 in Bay2 as a result f Cisco vPC for feature limitations. d hitecture in not recomm n mend due to Cisco vPC feature lim o mitations. Below design arch

Scenar 3: Lab Design and Config rio b a guration b based on C Cisco Virt tual Port Chann (vPC) Feature nel F
As shown in the below diagram (dia n w agram3), the first HP c700 enclosure h two HP Vi 00 has irtual Connect Flex-10 Interc connect modules in Bay1 a nd Bay2. HP Virtual Conne Flex-10 in Bay1and ect e f to 32PP-1 and N Nexus 2232PPBay2 are connected using a total of four 10GbE uplink ports t Nexus 223 2 to supp up to 40G uplink ba port GbE andwidth to th enclosure. he b w vPC using a S Single Homed vPC Fabric Extender In this lab design architecture we will configure v Topology and a Dual Homed Serve Edge comm y er munication Set tup. You must configure step 2 before step 3 as it is a vPC lim s mitation requirement.

10

g AN rface Step 1. Configuring vPC keepalive L2 VLA and L3 VLAN inter

Nexus-5020-1(config)# feat ture interface-v vlan Nexus-5020-1(config)# vlan 1000 n Nexus-5020-1(config-vlan)# name vPCkeepal # live Nexus-5020-1(config-if)# interface vlan 1000 i 1 Nexus-5020-1(config-if)# ip address 192.1 i 168.255.253/30 Nexus-5020-2(config)# feat ture interface-v vlan Nexus-5020-2(config)# vlan 1000 n Nexus-5020-2(config-vlan)# name vPCkeepal # live Nexus-5020-2(config-if)# interface vlan 1000 i 1 Nexus-5020-2(config-if)# ip address 192.1 i 168.255.254/30 Nexus-5020-1(config)# show ip interface brief | inc Vlan w b n1000 Vlan1000 19 92.168.255.253 protocol-up/link p k-up/admin-up Nexus-5020-2(config)# show ip interface brief | inc Vlan w b n1000 Vlan1000 19 92.168.255.254 protocol-up/link p k-up/admin-up Verification Enable Interfa vlan feature ace Dedicated vla 1000 for vPC an keepalive messa aging Dedicated L3 vlan interface to 3 support vPC kee epalive configurat tion

g ain C e Step 2. Configuring vPC Doma and vPC Keepalive Link

Nexus-5020-1(config)# feat ture vpc Nexus-5020-1(config)# vpc domain 1000 Nexus-5020-1(config-vpc-do omain)# peer-kee epalive destinat ion 192.168.255. .254 source 192.168.255 5.253 vrf defaul lt Nexus-5020-2(config)# feat ture vpc Nexus-5020-2(config)# vpc domain 1000 Nexus-5020-2(config-vpc-do omain)# peer-kee epalive destinat ion 192.168.255. .253 source Enable vPC fe eature Create vPC domain 1000 L3 vPC Peer IP address

Configure Ne exus 5020-2

11 1

192.168.255.254 vrf default Nexus-5020-1(config)# show vpc peer-keepalive vPC keep-alive status : peer is alive Nexus-5020-1(config-vpc-domain)# show vpc Legend: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id : Peer status : vPC keep-alive status : Configuration consistency status: Configuration consistency reason: vPC role : Number of vPCs configured : Peer Gateway : Dual-active excluded VLANs : 1000 peer link not configured peer is alive failed vPC peer-link does not exists none established 0 Disabled Verify vPC peer status

Step 3. Configuring vPC Peer Link

Nexus-5020-1(config)# interface port-channel1000 Nexus-5020-1(config-if)# description Connection to Nexus-5020-2 Nexus-5020-1(config-if)# switchport mode trunk Nexus-5020-1(config-if)# vpc peer-link Nexus-5020-1(config-if)# spanning-tree port type network Nexus-5020-1(config-if)# speed 10000 Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# interface Ethernet1/1 description Connection to Nexus-5020-2 switchport mode trunk channel-group 1000 mode active interface Ethernet1/2 description Connection to Nexus-5020-2 switchport mode trunk channel-group 1000 mode active Configure Nexus 5020-2 Create Ether Channel 1000

Configure EtherChannel as a vPC Peer Link

Add E1/1 and E1/2 to the EtherChannel

Nexus-5020-2(config)# interface port-channel1000 Nexus-5020-2(config-if)# description Connection to Nexus-5020-1 Nexus-5020-2(config-if)# switchport mode trunk Nexus-5020-2(config-if)# vpc peer-link Nexus-5020-2(config-if)# spanning-tree port type network Nexus-5020-2(config-if)# speed 10000 Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# ! Verification switch 1 Nexus-5020-1(config)# Nexus-5020-1(config)# show vpc consistency-parameters global Legend: Type 1 : vPC will be suspended in case of mismatch Name ------------QoS Network QoS (MTU) Network Qos (Pause) Input Queuing (Bandwidth) Type ---1 1 1 1 Local Value ---------------------([], [3], [], [], [], (1538, 2240, 0, 0, 0) (F, T, F, F, F, F) (50, 50, 0, 0, 0, 0) interface Ethernet1/1 description Connection to Nexus-5020-1 switchport mode trunk channel-group 1000 mode active interface Ethernet1/2 description Connection to Nexus-5020-1 switchport mode trunk channel-group 1000 mode active

Peer Value -------------------------------------------------([], [3], [], [], [], []) []) (1538, 2240, 0, 0, 0, 0) 0) (F, T, F, F, F, F) (50, 50, 0, 0, 0, 0)

12

Input Queuing (Absolute Priority) Output Queuing (Bandwidth) Output Queuing(Absolute Priority) STP Mode STP Disabled STP MST Region Name STP MST Region Revision STP MST Region Instance to VLAN Mapping STP Loopguard STP Bridge Assurance STP Port Type, Edge BPDUFilter, Edge BPDUGuard STP MST Simulate PVST Allowed VLANs Local suspended VLANs

1 1 1 1 1 1 1 1 1 1 1 1 -

(F, F, F, F, F, F) (50, 50, 0, 0, 0, 0) (F, F, F, F, F, F) Rapid-PVST None "" 0

(F, F, F, F, F, F) (50, 50, 0, 0, 0, 0) (F, F, F, F, F, F) Rapid-PVST None "" 0

Disabled Enabled Normal, Disabled, Disabled Enabled -

Disabled Enabled Normal, Disabled, Disabled Enabled -

Nexus-5020-1(config)# Nexus-5020-1(config)# show vpc consistency-parameters interface po1000 Note: **** Global type-1 parameters will be displayed for peer-link ***** Legend: Type 1 : vPC will be suspended in case of mismatch Name Type Local Value Peer Value -------------------------------------------------------------------------------------QoS 1 ([], [3], [], [], [], ([], [3], [], [], [],[]) []) Network QoS (MTU) 1 (1538, 2240, 0, 0, 0, 0) (1538, 2240, 0, 0, 0,0) Network Qos (Pause) 1 (F, T, F, F, F, F) (F, T, F, F, F, F) Input Queuing (Bandwidth) 1 (50, 50, 0, 0, 0, 0) (50, 50, 0, 0, 0, 0) Input Queuing (Absolute 1 (F, F, F, F, F, F) (F, F, F, F, F, F) Priority) Output Queuing (Bandwidth) 1 (50, 50, 0, 0, 0, 0) (50, 50, 0, 0, 0, 0) Output Queuing (Absolute 1 (F, F, F, F, F, F) (F, F, F, F, F, F) Priority) STP Mode 1 Rapid-PVST Rapid-PVST STP Disabled 1 None None STP MST Region Name 1 "" "" STP MST Region Revision 1 0 0 STP MST Region Instance to 1 VLAN Mapping STP Loopguard 1 Disabled Disabled STP Bridge Assurance 1 Enabled Enabled STP Port Type, Edge 1 Normal, Disabled Normal, Disabled, BPDUFilter, Edge BPDUGuard Disabled Disabled STP MST Simulate PVST 1 Enabled Enabled Allowed VLANs Local suspended VLANs Nexus-5020-1(config)# Nexus-5020-1(config)# show vpc Legend: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id Peer status vPC keep-alive status Configuration consistency status vPC role Number of vPCs configured Peer Gateway Dual-active excluded VLANs : : : : : : : : 1000 peer adjacency formed ok peer is alive success primary 0 Disabled -

vPC Peer-link status -------------------------------------------------------------------------------id Port Status Active vlans -- ---- ------ --------------------------------------------------------------1 Po1000 up -

13

! Verification switch 2 Nexus-5020-2(config)# Nexus-5020-2(config)# show vpc consistency-parameters global Legend: Type 1 : vPC will be suspended in case of mismatch Name ------------QoS Network QoS (MTU) Network Qos (Pause) Input Queuing (Bandwidth) Input Queuing (Absolute 1 Priority) Output Queuing (Bandwidth) Output Queuing (Absolute Priority) STP Mode STP Disabled STP MST Region Name STP MST Region Revision1 STP MST Region Instance to VLAN Mapping STP Loopguard STP Bridge Assurance STP Port Type, Edge BPDUFilter, Edge BPDUGuard STP MST Simulate PVST 1 Allowed VLANs Local suspended VLANs Type ---1 1 1 1 Local Value ---------------------([], [3], [], [], [] (1538, 2240, 0, 0, 0, 0) (F, T, F, F, F, F) (50, 50, 0, 0, 0, 0) (F, F, F, F, F, F) (50, 50, 0, 0, 0, 0) (F, F, F, F, F, F) Rapid-PVST None "" 0 Peer Value ----------------------([], [3], [], [], [], []) []) (1538, 2240, 0, 0, 0, 0) (F, T, F, F, F, F) (50, 50, 0, 0, 0, 0) (F, F, F, F, F, F) (50, 50, 0, 0, 0, 0) (F, F, F, F, F, F) Rapid-PVST None "" 0

1 1 1 1 1 1 1 1 1

Disabled Enabled Normal, Disabled Disabled Enabled -

Disabled Enabled Normal, Disabled Disabled Enabled -

Nexus-5020-2(config)# Nexus-5020-2(config)# show vpc consistency-parameters interface po1000 Note: **** Global type-1 parameters will be displayed for peer-link ***** Legend: Type 1 : vPC will be suspended in case of mismatch Name ------------QoS Network QoS (MTU) Network Qos (Pause) Input Queuing (Bandwidth) Input Queuing (Absolute Priority) Output Queuing (Bandwidth) Output Queuing (Absolute Priority) STP Mode STP Disabled STP MST Region Name 1 STP MST Region Revision1 STP MST Region Instance to VLAN Mapping STP Loopguard STP Bridge Assurance STP Port Type, Edge BPDUFilter, Edge BPDUGuard STP MST Simulate PVST 1 Allowed VLANs Local suspended VLANs Type ---1 1 1 1 1 1 1 Local Value ---------------------([], [3], [], [], [],[]) (1538, 2240, 0, 0, 0, 0) (F, T, F, F, F, F) (50, 50, 0, 0, 0, 0) (F, F, F, F, F, F) (50, 50, 0, 0, 0, 0) (F, F, F, F, F, F) Peer Value ----------------------([], [3], [], [], [],[]) (1538, 2240, 0, 0, 0,0) (F, T, F, F, F, F) (50, 50, 0, 0, 0, 0) (F, F, F, F, F, F) (50, 50, 0, 0, 0, 0) (F, F, F, F, F, F)

1 1

Rapid-PVST None "" 0

Rapid-PVST None "" 0

1 1 1 1 Disabled Enabled Normal, Disabled Disabled Enabled Disabled Enabled Normal, Disabled, Disabled Enabled -

Nexus-5020-2(config)# Nexus-5020-2(config)# show vpc Legend:

14

(*) - local vPC is down, forwarding via vPC peer-link vPC domain id : 1000 Peer status :peer adjacency formed ok vPC keep-alive status : peer is alive Configuration consistency status : success vPC role : secondary Number of vPCs configured : 0 Peer Gateway :Disabled Dual-active excluded VLANs : vPC Peer-link status -------------------------------------------------------------------------------------------id Port Status Active vlans -- ---- ------ ----------------------------------------------------------------------------1 Po1000 up -

Step 4. Configuring vPC EtherChannel Host Interface

! Create Po11 and add it to vPC 11 on Nexus 5020-1 and Nexus 5020-2 Nexus-5020-1(config)# interface port-channel11 Nexus-5020-1(config-if)# description Connection to Enc1-Flex10-Bay1 Nexus-5020-1(config-if)# switchport mode trunk Nexus-5020-1(config-if)# switchport trunk allowed vlan 101-109 Nexus-5020-1(config-if)# spanning-tree port type edge trunk Nexus-5020-1(config-if)# vpc 11 Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# interface Ethernet100/1/1 description Connection to Enc1-Flex10-Bay1 lacp rate fast switchport mode trunk switchport trunk allowed vlan 101-109 spanning-tree port type edge trunk channel-group 11 mode active Create EtherChannel 11

Consider the interface as edge port Create vPC 11 Add Eth100/1/1 interface to Po11 Enable LACP Fast Timeout

Nexus-5020-2(config)# interface port-channel11 Nexus-5020-2(config-if)# description Connection to Enc1-Flex10-Bay1 Nexus-5020-2(config-if)# switchport mode trunk Nexus-5020-2(config-if)# switchport trunk allowed vlan 101-109 Nexus-5020-2(config-if)# spanning-tree port type edge trunk Nexus-5020-2(config-if)# vpc 11 Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# interface Ethernet101/1/1 description Connection to Enc1-Flex10-Bay1 lacp rate fast switchport mode trunk switchport trunk allowed vlan 101-109 spanning-tree port type edge trunk channel-group 11 mode active

Configure Nexus 5020-2

! Create Po12 and add it to vPC 12 on Nexus 5020-1 and Nexus 5020-2 Nexus-5020-1(config)# interface port-channel12 Nexus-5020-1(config-if)# description Connection to Enc1-Flex10-Bay2 Nexus-5020-1(config-if)# switchport mode trunk Nexus-5020-1(config-if)# switchport trunk allowed vlan 101-109 Nexus-5020-1(config-if)# spanning-tree port type edge trunk Nexus-5020-1(config-if)# vpc 12 Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# Nexus-5020-1(config-if)# interface Ethernet100/1/2 description Connection to Enc1-Flex10-Bay2 lacp rate fast switchport mode trunk switchport trunk allowed vlan 101-109 spanning-tree port type edge trunk channel-group 12 mode active Create EtherChannel 12

Consider the interface as edge Port Create vPC 12 Add Eth100/1/2 interface to Po12 Enable LACP Fast Timeout

15

Nexus-5020-2(config)# feature lacp Nexus-5020-2(config)# interface port-channel12 Nexus-5020-2(config-if)# description Connection to Enc1-Flex10-Bay2 Nexus-5020-2(config-if)# switchport mode trunk Nexus-5020-2(config-if)# switchport trunk allowed vlan 101-109 Nexus-5020-2(config-if)# spanning-tree port type edge trunk Nexus-5020-2(config-if)# vpc 12 Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# Nexus-5020-2(config-if)# interface Ethernet101/1/2 description Connection to Enc1-Flex10-Bay2 lacp rate fast switchport mode trunk switchport trunk allowed vlan 101-109 spanning-tree port type edge trunk channel-group 12 mode active

Configure Nexus 5020-2

! Verification on Nexus 5020-1: EtherChannel Po11, vPC 11 and Po12, vPC 12 Nexus-5020-1(config-if)# show run interface po12 !Command: show running-config interface port-channel12 !Time: Mon Sep 6 13:19:35 2010 version 4.2(1)N2(1) interface port-channel12 switchport mode trunk vpc 12 switchport trunk allowed vlan 101-109 spanning-tree port type edge trunk Nexus-5020-1(config-if)# show run interface po11 !Command: show running-config interface port-channel11 !Time: Mon Sep 6 13:19:43 2010 version 4.2(1)N2(1) interface port-channel11 switchport mode trunk vpc 11 switchport trunk allowed vlan 101-109 spanning-tree port type edge trunk Nexus-5020-1(config-if)# show run interface e100/1/1 !Command: show running-config interface Ethernet100/1/1 !Time: Mon Sep 6 13:19:56 2010 version 4.2(1)N2(1) interface Ethernet100/1/1 description connection to Enc1-Flex10-Bay1 lacp rate fast switchport mode trunk switchport trunk allowed vlan 101-109 channel-group 11 mode active Nexus-5020-1(config-if)# show run interface e100/1/2 !Command: show running-config interface Ethernet100/1/2 !Time: Mon Sep 6 13:20:13 2010 version 4.2(1)N2(1) interface Ethernet100/1/2 description connection to Enc1-Flex10-Bay2 lacp rate fast switchport mode trunk switchport trunk allowed vlan 101-109 channel-group 12 mode active Nexus-5020-1(config-if)# show run int po1000 !Command: show running-config interface port-channel1000 !Time: Mon Sep 6 13:36:14 2010

16

version 4.2(1)N2(1) interface port-channel1000 description Connection to Nexus 5020-2 switchport mode trunk vpc peer-link switchport trunk allowed vlan none spanning-tree port type network Nexus-5020-1(config-if)# show vpc Legend: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id : Peer status : vPC keep-alive status : Configuration consistency status: vPC role : Number of vPCs configured : Peer Gateway : Dual-active excluded VLANs : 1000 peer adjacency formed ok peer is alive success primary 2 Disabled -

vPC Peer-link status --------------------------------------------------------------------------id Port Status Active vlans ---------- ------------------------------------------------1 Po1000 up vPC status ---------------------------------------------------------------------------------------id Port Status Consistency Reason Active vlans --------------------- ----------- -----------------------------------11 Po11 up success success 12 Po12 up success success -

Nexus-5020-1(config-if)# show run interface po1000 !Command: show running-config interface port-channel1000 !Time: Mon Sep 6 13:38:44 2010 version 4.2(1)N2(1) interface port-channel1000 description Connection to Nexus 5020-2 switchport mode trunk vpc peer-link switchport trunk allowed vlan 101-109 spanning-tree port type network

Nexus-5020-1(config-if)# show vpc Legend: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id : 1000 Peer status : peer adjacency formed ok vPC keep-alive status : peer is alive Configuration consistency status: success vPC role : primary Number of vPCs configured : 2 Peer Gateway : Disabled Dual-active excluded VLANs : -

vPC Peer-link status --------------------------------------------------------------------id Port Status Active vlans -- ---- ------ -------------------------------------------------1 Po1000 up 101-108

17

vPC status ---------------------------------------------------------------------------id Port Status Consistency Reason ------ ----------- ------ ----------- -------------------------- ----------11 Po11 up success success 12 Po12 up success success

Active vlans 101-108 101-108

! Verification on Nexus 5020-2: EtherChannel Po11, vPC 11 and Po12, vPC 12 Verification on Nexus 5020-2 Nexus-5020-2(config)# show run interface po12 !Command: show running-config interface port-channel12 !Time: Mon Sep 6 18:57:30 2010 version 4.2(1)N2(1) interface port-channel12 switchport mode trunk vpc 12 switchport trunk allowed vlan 101-109 spanning-tree port type edge trunk

Nexus-5020-2(config)# show run interface po11 !Command: show running-config interface port-channel11 !Time: Mon Sep 6 18:57:38 2010 version 4.2(1)N2(1) interface port-channel11 switchport mode trunk vpc 11 switchport trunk allowed vlan 101-109 spanning-tree port type edge trunk

Nexus-5020-2(config)# show run interface e100/1/1 !Command: show running-config interface Ethernet100/1/1 !Time: Mon Sep 6 18:57:47 2010 version 4.2(1)N2(1) interface Ethernet101/1/1 description connection to Enc1-Flex10-Bay2 lacp rate fast switchport mode trunk switchport trunk allowed vlan 101-109 channel-group 12 mode active

Nexus-5020-2(config)# show run interface e101/1/2 !Command: show running-config interface Ethernet101/1/2 !Time: Mon Sep 6 18:58:00 2010 version 4.2(1)N2(1) interface Ethernet101/1/2 description connection to Enc1-Flex10-Bay1 lacp rate fast switchport mode trunk switchport trunk allowed vlan 101-109 channel-group 11 mode active

Nexus-5020-2(config)# show run interface po1000 !Command: show running-config interface port-channel1000

18

!Time: Mon Sep 6 19:10:17 2010 version 4.2(1)N2(1) interface port-channel1000 description Connection to Nexus 5020-1 switchport mode trunk vpc peer-link switchport trunk allowed vlan 101-109 spanning-tree port type network

Nexus-5020-2(config)# show vpc Legend: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id : Peer status : vPC keep-alive status : Configuration consistency status: vPC role : Number of vPCs configured : Peer Gateway : Dual-active excluded VLANs : 1000 peer adjacency formed ok peer is alive success secondary 2 Disabled -

vPC Peer-link status --------------------------------------------------------------------id Port Status Active vlans -- ---- ------ -------------------------------------------------1 Po1000 up 101-108 vPC status --------------------------------------------------------------------------------------------id Port Consistency Reason Active vlans ------ ----------- ------ ----------- -------------------------- --------------------------11 Po11 up success success 101-108 12 Po12 up success success 101-108

Status

19

For more info m ormation n

For more technical info ormation about HP Virtual C Connect please visit http://ww ww.HP.com/g go/VirtualConnect

Cop pyright 2010 Hewle ett-Packard Develop pment Company, L.P The information contained herein is subject to P. c change without notice. Th only warranties for HP products and services are set fo in the express w e he f d orth warranty stateme accompanying such products and services. Nothing herein should be co ents g d onstrued as constitu uting an additio onal warranty. HP shall not be liable fo technical or edito s or orial errors or omiss sions contained her rein. c0265 56171, Created December 2010