HP V Cisco Integr Technica Table o Introductio Cisco Nex Cisco Virtu vPC Topol vPC Limita Scenari Scenari Extende Scenari Extende Scenari For more i irtual Co o Nexus ration al white paper f contents on .................. xus Fabric Exte ual Port Chann logy............... ations ............. io 1: Lab Desig io 2a: Lab Desi er Topology .... io 2b: Lab Desi er Topology .... io 3: Lab Desig information ..... onnect F 5000 & r ..................... nders 2000 se el (vPC) .......... ..................... ..................... gn and Configu ign and Config ..................... ign based on C ..................... gn and Configu ..................... lex-10 & & 2000 ...................... ries ................ ...................... ...................... ...................... ration based o guration based ...................... Cisco Virtual Po ...................... ration based o ...................... & FlexFa series ..................... ..................... ..................... ..................... ..................... on Cisco EtherC on Cisco Ether ..................... ort Channel (vPC ..................... on Cisco Virtual ..................... abric ..................... ..................... ..................... ..................... ..................... Channel Feature r Channel Featu ..................... C) Feature in a ..................... Port Channel ( ..................... ..................... ..................... ..................... ..................... ..................... e ................... ure in a Dual H ..................... Single Homed ..................... (vPC) Feature.. ..................... ................ 2 ................ 2 ................ 3 ................ 4 ................ 4 ................ 5 omed Fabric ................ 9 Fabric ................ 9 .............. 10 .............. 20
20
Embed
HP V irtual Connect Flex-10 & FlexFabric Cisco Nexus 5000 ...
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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 up to 8 H EtherCha4.2(1)N1you cannInterface The CiscoGigabit Ehost internot perfoforwardinFabric Ex
NI2iwaCb44p
CiscoStarting f5000 ser vPC Ter
vd
vE
rc
v H v
aav
vC
that might paHost Interfaces
annel Host Inte1(1). Bridge Pnot disable it. as BPDU Guao Nexus 2232Ethernet host irfaces for one orm any local ng, even incluxtender.
NOTE: t is very impo2232PP Fabrin some of thewhich in someand Nexus 22CSCtf22871 bugs were firs4.2(1)N1(0.24.2(1)N2(1) isprovides more
o Virtual from Cisco NXries switches t
rminology vPC—The comdevice. vPC peer deEtherChannel vPC peer linrecommendedchecks againsvPC membeHost vPC povPC domainand all of the associated to vPC domain IDvPC peer-keCisco Nexus 5
articipate in a s.
erface was adProtocol Data Based on thaard will put th2PP Fabric Exinterfaces. In t fabric interfaswitching. All
uding host-to-h
ortant to upgrac Extender to
e NX-OS softwe cases preven232PP Fabric Bug Details, Cst discovered 69), 4.2(1)Ns the latest ane stability to th
Port ChX-OS release that are direct
mbined EtherC
evice—One o known as thenk—The link
d that you use st a configurater port—Inteort—Fabric En—This doma port channelsthe configuraD must be theeepalive lin5000 Series d
logical bund
dded to the FaUnit (BPDU) Gt you cannot
he Host Interfaxtender has eithe best case
ace) or higherl traffic is senthost communic
ade the Nexus the latest NX
ware branchesnt establishing Extender. SoCSCte09024 in NXOS rele1(0.284), 4.2
nd first releasehe LACP port.
annel (v4.1(3)N1(1),tly connected
Channel betw
of a pair of dee vPC peer lin used to synch LACP on the tion mismatchrfaces that bextender host iin includes bos in the vPC cotion mode tha same on bot
nk—The peer-device and it
le called Ethe
abric ExtendeGuard is enabconnect a sw
ace in error-disight 10-Gigab scenario, you. The Cisco Nt to the parencations betwe
s 5000 seriesX-OS release 4s in processing a LACP portme of these N Bug Details, aeases 4.1(3)N2(1)N1(0.323e to support LA
vPC) you can conf to Cisco Nex
ween the vPC p
evices that ark hronize states peer-link, bech on the EtherCelong to the vPinterfaces thatoth vPC peer onnected to that you must ush switches. -keepalive linkmust be differ
erChannel Hos
r from Cisco Nbled by defau
witch or a bridgsabled state wbit Ethernet fau can have a
Nexus Fabric Et switch that p
een two system
s switches tha4.2(1)N2(1). g LACP PDU wt channel betw
NX-OS bugs aand CSCtf22
N1(0.164), 4.3), and 4.0(1ACP PDU with
figure vPC bexus 2000 seri
peer devices
re connected w
s between the cause LACP pChannel. PCs. t belong to a devices, the vhe downstrease to assign v
k monitors therent than the v
st Interface tha
NX-OS Releaslt in all Host Ige to a Host when a BPDU bric interface 4 to 1 oversuExtender 200provides centrms connected
t manage the Cisco had diwith 1 secondween HP Virtu
are covered un871 Bug Deta2(1)N1(0.267a)N2(1a). NXh 1 second tim
etween Cisco es Fabric Exte
and the down
with the speci
vPC peer devprovides config
vPC. vPC peer-keepm devices. It PC global pa
e vitality of a vvPC peer link.
3
at can group
se nterfaces and
is received. s and 32 10-
ubscription (4 0 Series doesral to the same
Nexus ifferent bugs d timeout ual Connect nder ails. These 7), X-OS meout which
Nexus enders.
nstream
ial
vices. It is guration
palive link, isalso rameters. The
vPC peer. . The peer-
3
d
s
4
kNtYsr
NIau/t
vPC TThere areDual Hombe able tHomed Smechanisseries sw
NsESEiI
vPC LvPC featupeer linksynchron vPCs canswitch vPEtherCha Plan to coconfiguri
keepalive link No data or syhis link is a mYou must havesystem cannotrunning.
NOTE: You cn case you wa VLAN Interfaunique Layer 3/30) to avoid he vPC keepa
Topologye 2 different vmed Fabric Exo support Dua
Server commusm to manage
witches that wa
NOTE: It is vseries switchesExtender vPC Server Edge CExtender utilizn the Cisco Nnterface vPC
Limitationure and vPC p. Also You muized between
n only have EtPC topology), annel host inte
onfigure vPC ng vPCs.
sends configynchronizationmessage that ie Layer 3 cont bring up the
can use eitherwant to use the
ace to carry t3 IP address s any IP addrealive commun
y vPC topology xtender vPC Tal Homed Sernication in Du
e a single Ciscas introduced
very importants and Cisco N Topology. ONCommunicatiozing vPC featuNexus 2000 Ftopology or a
ns peer-keepaliveust configure bn the vPC pee
herChannels. on an EtherCerface (host in
in the mainten
urable, periodn traffic movesndicates that nectivity betw vPC peer link
r managemene default VRF, he vPC peer-ksubnet with 30esses conflict iication.
configurationsopology. In Srver communicual Homed Faco Nexus Fab in NX-OS rel
t to configure Nexus 2000 sNLY in this top
on between HPure as shown abric Extende
a Fabric Exten
e link must be both vPC peer devices.
A vPC can bChannel fabric
terface vPC to
nance time w
dic keepalive s over the vPCthe originatin
ween the peer k unless a pee
nt VRF or defa then you havkeepalive mes0 network bitsn your netwo
s, Single HomSingle Homed cation. You wabric Extenderbric Extender ease 4.1(3).
your vPC topseries Fabric Epology you wP Virtual Connlater in scenaer as a Fabricnder vPC topo
enabled andr switches as
be configured c interface (fabopology).
indow as you
messages beC peer-keepalg switch is op switches to trerkeepalive lin
ult VRF for theve to configuressages. Also is subnet mask
ork and assure
med Fabric Ex Fabric Extend
will be only allr vPC Topologfrom 2 differe
pology betweeExtenders usin
will be able to nect and Cisc
ario 3. The reac Extender canology but not b
d configured b the configura
on a normal bric extender
u may experie
etween vPC pelive link; the operating and ransmit these nk is already
e vPC peer-kee a dedicatedt is important k (255.255.2e the highest r
xtender vPC Toder vPC Topolowed to suppgy which utilizent Cisco Nex
en Cisco Nexung Single Hom support DUAco Nexus 200ason is due ton be a membeboth simultane
before configuation is not aut
EtherChannel vPC topology
ence traffic dis
eer devices. only traffic on running vPCs.messages; theup and
eepalive link. d VLAN, and to use a 55.252 or
reliability to
opology and ology you will port Single zing the xus 5000
us 5000 med Fabric
AL Homed 00 Fabric o a limitation er of a Host eously
uring vPC tomatically
l (switchto-y), and on an
sruption while
. e
e
ScenarFeatureAs shownConnect and Bay22232PP-2 In this labvPC Fabr
rio 1: Labe n in the belowFlex-10 Interc2 are connect2 to support u
b design archric Extender T
b Design a
w diagram (diaconnect moduted using a toup to 40GbE u
itecture we wopology and
and Config
agram1), the les in Bay1 atal of four 10uplink bandw
will configure C a Dual Home
guration b
first HP c700nd Bay2. HP
0GbE uplink pwidth to the en
Cisco EtherChed Server Edg
based on C
00 enclosure h Virtual Conneports to Nexusnclosure.
hannel featurege communica
Cisco Ethe
has two HP Viect Flex-10 in s 2232PP-1 an
e using a Singation Setup.
5
erChanne
irtual Bay1 nd Nexus
gle Homed
5
l
6
Nexus-5020-1(config)# feature lacp Enable lacp feature Nexus-5020-1(config)# interface port-channel11 Create EtherChannel 11 Nexus-5020-1(config-if)# description connection to Enc1-Flex10-Bay1 Nexus-5020-1(config-if)# switchport mode trunk Enable Trunk Nexus-5020-1(config-if)# switchport trunk allowed vlan 101-109 Allow required VLANs Nexus-5020-1(config-if)# spanning-tree port type edge trunk Consider the interface as edge port (enable
portfast) even in trunk mode 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 Enable LACP Fast Timeout Nexus-5020-1(config-if)# switchport mode trunk add physical interfaces to the EtherChannel 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 Same Configuration for N5020-2 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