Enhanced VPC doubt

Hi,
I was going through the documentation for enhanced VPC and had some doubts
A FEX can be:-
1) Single homed to N5K/N7K
2) Dual homed to N5K/N7K
If scenario 1, Do i have to create a VPC just to connect a server that has 2 NICs homed to FEX1 and FEX2 with active/active?
If scenario 2, Do i have to create a VPC just to connect a server that has 2 NICs homed to FEX1 and FEX2 with active/active?
If scenario 1, Do i have to create a VPC just to connect a server that has 2 NICs homed to FEX1 and FEX2 with active/standy?
If scenario 2, Do i have to create a VPC just to connect a server that has 2 NICs homed to FEX1 and FEX2 with active/standy?
What is the condition that must be met in order to call a VPC an 'enhanced VPC'?
Regards

1) It is not EvPC in this set up. Just a regular vPC since the FEX is straight through.
2) It is true for the N5K but not N7K. N7K doesn't support vPC FEX.
Q1. On the server, it is a regular PO. on the FEX 1 and FEX 2, it will be vPC.
Q2. This will consider EvPC on the N5K ONLY. You will need to configure vPC for the FEXs and regular PO toward the server.
Q3. This is not EvPC. Just regular connections.
Q4. This is not EvPC, just regular connections.
To simiply vPC vs EvPC. vPC is also known as single-layer vPC, meaning the followings:
or
EvPC also known as dual-layer vPC and it looks like the following:
HTH,
jerry

Similar Messages

Nexus 5548 enhanced VPC capability

does the nexus 5548up running 5.0(3)N2(2b) support enhanced VPC? fabric VPC to the fex and vPC from the fex down to the host? if not, what minimum code version supports it? Thanks

You need NX-OS 5.1(3)N1(1) to run enhanced VPC.
Link:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/mkt_ops_guides/513_n1_1/n5k_enhanced_vpc.html
HTH

Enhanced VPC

Folks,
I do not have a 2232 in my lab to test this but do we need VPC1 in the below sample config? I think this is an error:
The sample config is for enhanced vpc with active-active fex senario.
nexus5500-sanA(config)#interface eth 101/1/1
nexus5500-sanA(config-if)# channel-group 1 mode active
nexus5500-sanA(config-if)# interface port-channel 1
nexus5500-sanA(config-if)# vpc 1
nexus5500-sanB(config)#interface eth 101/1/1
nexus5500-sanB(config-if)# channel-group 1 mode active
nexus5500-sanB(config-if)# interface port-channel 1
nexus5500-sanB(config-if)# vpc 1
I think the command in bold is not needed in a active-active Fex Senario. The Nexus switches will automatically find out if they are connected to the same host by the channel-group number.
Any assistance would be highly appreciated.

1) It is not EvPC in this set up. Just a regular vPC since the FEX is straight through.
2) It is true for the N5K but not N7K. N7K doesn't support vPC FEX.
Q1. On the server, it is a regular PO. on the FEX 1 and FEX 2, it will be vPC.
Q2. This will consider EvPC on the N5K ONLY. You will need to configure vPC for the FEXs and regular PO toward the server.
Q3. This is not EvPC. Just regular connections.
Q4. This is not EvPC, just regular connections.
To simiply vPC vs EvPC. vPC is also known as single-layer vPC, meaning the followings:
or
EvPC also known as dual-layer vPC and it looks like the following:
HTH,
jerry

Enhanced vpc with ucs 6248up

I got 2 6248up FI going to 2 N7k.
can i stup enhanced vpc using both FI as active uplinks or can only 1 be active at one time?
in ucsm, I am only seeing 1 pot channel on fabric A - with 4 uplinks 17-20
but on fabric B i see 1 port channel with no links

If your FI's are in endhost mode, they should act like access ports and not disable a connectino via STP. If that is happening maybe you are in Switch mode?
Craig

Vpc and enhanced Vpc

Hi,
I need to check if my nexus 5548UP is running Vpc or enhanced Vpc. Is there a command to verify that
I have NXOS 5.1(3)N2(1) running on this switch
Thanks
raj

As far as I know, there is no such a command to verify if you are running VPC or eVPC. The show commands for vpc are just "show vpc" or "show vpc keep-alive" etc..

NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX

Hi All,
Please tell me how to do "NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX" without downtime for FEX.
The Server are connected to FEX.
Attached the diagram.

Hi,
If the 5500s are layer-2 with vPC running between them than you can use ISSU to upgade.
here is doc to follow:
ISSU Support for vPC Topologies
An ISSU is completely supported when two switches are paired in a vPC configuration. In a vPC configuration, one switch functions as a primary switch and the other functions as a secondary switch .They both run the complete switching control plane, but coordinate forwarding decisions to have optimal forwarding to devices at the other end of the vPC. Additionally, the two devices appear as a single device that supports EtherChannel (static and 802.3ad) and provide simultaneously data forwarding services to that device.
While upgrading devices in a vPC topology,you should start with the switch that is the primary switch. The vPC secondary device should be upgraded after the ISSU process completes successfully on the primary device. The two vPC devices continue their control plane communication during the entire ISSU process (except when the ISSU process resets the CPU of the switch being upgraded).
This example shows how to determine the vPC operational role of the switch:
link:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/upgrade/513_N1_1/n5k_upgrade_downgrade_513.html
HTH

Double sided VPC/enhanced VPC and MST

Hello,
I have some doubts/clarifications regarding MST with VPC--
There are two N7K core switches and four N5K switches and eight N2K.
there will be double sided VPC between N5K and N7K.
there will be enhanced vpn between N5k and n2k.
N7Ks will be connected to fifteen 4500.
Each 4500 will be in a VPC with N7k.
Each 4500 is single homed to 15 catalyst edge switches
Assume MST needs be configured in this network.
1) On MST instance - on N7K as per cisco design guide
2) Map all vlans (1-3967,4048-4093) in this instance N7K as per cisco design guide
3) No need to hard code root as peer switch command will be used
Now the concern that i have is regarding MSt configuration on all 4500.
1) 4500 number 1 may have vlans 2,3,4,5,6,7 and 4500 number 2 may have vlans 2,11,12,13,14,15,16
so can i just map all vlans to the single instance like instance 1 vlan 1-4094 on all catalysts 4500?
2) catalyst edge switches all run PVST+, i believe 4500 mst will interoperate with edge switch pvst+.
Is there any othe things that need tobe taken care of in this scenario?
Regards

1) If you are using MST with single region, I don't see the point. It can be done with RPVST+ without any interop worries.
2) Same as 1.
3) This is not true, with peer-switch feature, it is a BP to hard code the N7K as STP root with the same priority value, otherwise, the smallest switch ID will be the root. In you case, most likely the oldest switch will become the root if you don't hard code it.
To your second set of questions:
1) Yes, you need to match all your region(s) with the same VLANs, otherwise, you will have MST inconsistency.
2) Yes.
HTH,
jerry

Cisco Nexus 5548UP - Enhanced vPC

Hello,
We will be deploying a new Cisco Nexus 5K environment with 2248 FEX's.
The firewall in the environment (non-Cisco), only supports static Port-channels - i.e "ON" configuration and not LACP.
For redundancy we will be patching it into the environment in a topology where VLAN's are trunked and connected to two FEX modules as on page 2 of this document:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/mkt_ops_guides/513_n1_1/n5k_enhanced_vpc.pdf
Every example I've seen online uses LACP instead of a static Port-channel. My questions are:
Will this cause any issues in the event of port failure?
Is this best practice?
Are there any "gotchas" or caveats with this design?
Many thanks in advance.
Jacob

I always like to use LACP where and when I can. Some devices, like your firewall and vmware do not support LACP. As long as both devices are configured correctly and using mode-on, there should be no issues with this. I do not like mode-on for this reason, as it does not negotiate anything before bringing up the port-channel. Therefore just confirm it is configured as mode-on on both sides and you should be fine. This should not cause any disruption if one link fails, but I would test the configuration before putting this into production.

VPC N5k Switch Failure causes connectivity disruption

Hello,
I have configured enhanced vPC on 2 n5k and B22 FEXs (vPC from 5k to B22, and vPC from B22 to blade servers).
Everything is running smoothly, except when I power off one of the 5k, the connectivity to the blade servers is lost, comes back up for a short while, loses connectivity again, and after a few minutes comes back up for good.
From the logs I can see that all the port-channels (peer-link, to the FEXs and port-channels to other switches in network) get in down state, then fizical interfaces start coming backup in fabric mode, then port-channels, see FEXs starting to get online then all the port-channels go down again and then whole thing starts again.(all of this is hapenig with one of the 5k powerd off, same thing hapens with promary and secondary vpc).
Connectivity is lost in the same way when the 5k is started again, but just once.
I am running NX OS version 5.2.1N1.3.
I have no idea what could cause this behavior.
Any help would be appreciated.
Regards,
Bogdan

Hi Reza,
Below you can find my run-config.
version 5.2(1)N1(3)
feature fcoe
install feature-set virtualization
feature-set virtualization
logging level feature-mgr 0
hostname N5k_1
feature npiv
feature telnet
cfs eth distribute
feature udld
feature interface-vlan
feature lacp
feature vpc
feature lldp
feature vtp
feature fex
fex 107
pinning max-links 1
description "FEX0107"
fcoe
fex 108
pinning max-links 1
description "FEX0108"
slot 1
port 31-32 type fc
vpc domain 1
role priority 1000
peer-keepalive destination 1.1.1.2
auto-recovery
vsan database
vsan 50 name "VSAN_A"
fcdomain fcid database
interface port-channel100
description Po Synch N5k
switchport mode trunk
spanning-tree port type network
logging event port link-status
logging event port trunk-status
speed 10000
vpc peer-link
interface port-channel107
switchport mode fex-fabric
fex associate 107
vpc 107
interface port-channel108
switchport mode fex-fabric
fex associate 108
vpc 108
interface port-channel111
switchport mode trunk
interface vfc111
bind interface Ethernet107/1/1
no shutdown
vsan database
vsan 50 interface vfc111
vsan 50 interface fc1/31
vsan 50 interface fc1/32
interface fc1/31
no shutdown
interface fc1/32
no shutdown
interface Ethernet1/1
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/2
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/3
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/4
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/5
switchport mode fex-fabric
fex associate 107
channel-group 107
interface Ethernet1/6
switchport mode fex-fabric
fex associate 107
channel-group 107
interface Ethernet1/7
switchport mode fex-fabric
fex associate 108
channel-group 108
interface Ethernet1/8
switchport mode fex-fabric
fex associate 108
channel-group 108
interface Ethernet107/1/1
switchport mode trunk
channel-group 111 mode active
interface Ethernet108/1/1
switchport mode trunk
channel-group 111 mode active
version 5.2(1)N1(3)
feature fcoe
install feature-set virtualization
feature-set virtualization
logging level feature-mgr 0
hostname N5k_2
feature npiv
feature telnet
cfs eth distribute
feature udld
feature interface-vlan
feature lacp
feature vpc
feature lldp
feature vtp
feature fex
fex 107
pinning max-links 1
description "FEX0107"
fex 108
pinning max-links 1
description "FEX0108"
fcoe
slot 1
port 31-32 type fc
vpc domain 1
role priority 1000
peer-keepalive destination 1.1.1.1
auto-recovery
vsan database
vsan 51 name "VSAN_B"
fcdomain fcid database
interface port-channel100
description Po Synch N5k
switchport mode trunk
spanning-tree port type network
logging event port link-status
logging event port trunk-status
speed 10000
vpc peer-link
interface port-channel107
switchport mode fex-fabric
fex associate 107
vpc 107
interface port-channel108
switchport mode fex-fabric
fex associate 108
vpc 108
interface port-channel111
switchport mode trunk
interface vfc111
bind interface Ethernet108/1/1
no shutdown
vsan database
vsan 51 interface vfc111
vsan 51 interface fc1/31
vsan 51 interface fc1/32
interface fc1/31
no shutdown
interface fc1/32
no shutdown
interface Ethernet1/1
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/2
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/3
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/4
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/5
switchport mode fex-fabric
fex associate 107
channel-group 107
interface Ethernet1/6
switchport mode fex-fabric
fex associate 107
channel-group 107
interface Ethernet1/7
switchport mode fex-fabric
fex associate 108
channel-group 108
interface Ethernet1/8
switchport mode fex-fabric
fex associate 108
channel-group 108
interface Ethernet107/1/1
switchport mode trunk
channel-group 111 mode active
interface Ethernet108/1/1
switchport mode trunk
channel-group 111 mode active

VPC on Nexus 2Ks

So my setup is a VPC with 5Ks and with each 2K with uplinks to only one 5K. Is it possible for servers to port-channel to both 2Ks for a VPC? Or is that only possible if the 2Ks have a VPC back to the 5Ks?

I think that would work. depending on the fex type.
From NX-OS 4.2(1)N1(1), it is posible to connect a server with vpc to two fexes that are single attached.
From NX-OS 5.1(3)N1(1), it is posible to connect a server with vpc to two fexes that are dual attached with vpc, this is called enhanced vpc.
see this for example
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/layer2/521_n1_3/b_5k_Layer2_Config_521N13/b_5k_Layer2_Config_521N13_chapter_0110.html#concept_4DB9D39D3A2E4C2DBA631257BC6A5C5E
/Mikael

Vpc on storage

Hi All
Can i deploy VPC on storage traffic(FCoE)?
If not, why? Kindly help

Hi Rishav,
FCoE must have a single defined path, unlike ethernet over a VPC. Please see the following document for FCoE used with VPC.
FCoE Configuration with Enhanced vPC
Best regards,
Jim

Fex and VPC

I'm am new to the whole datacenter design and I've recently taken over a data center set up. I'm trying to determine if my vPCs and port-channels are set up correctly. I've attached a drawing of the network set up. It seems pretty straight forward:
NIC teamed server with each NIC going to a separate FEX.
The FEX are straight through to the 5596s.
Using LACP on the switches and servers.
NX-OS 5.0(3)
My questions are 1) Is the FEX number only locally significant to the 5596 it's attached to? Should this number be the same or different on each 5596 or does it not matter? I haven't been able to find anything specifiying what this is supposed to be for this setup.
2) How can I verify the vPCs/portchannels are working properly?
Doing a 'show vpc' shows up/success on both switches.
'show port-channel summary' shows my channel as SU and my port as P.
Doing a 'show interface pXXX' shows my port-channel and vPC if I run the command on both 5596s but they each only show one member in the channel, which is the locally connected interface. I would think I'm supposed to see both interfaces channled together here.
If I take one interface down I don't get any messages on the other switch that the other side of the port-channel has dropped. It also seems like traffic isn't being equally distributed.
I hope this makes sense. I've been trying to figure this environment out for weeks. Just when I think I've got it, it doesn't act the way I'm expecting it to.

1) It does not matter if you have same FEX number on both switches. However, This will be a problem when you decide to implement Enhanced vpC where both FEX connected to both 5596 and servers are also connected to both FEXes.
2) show vpc is perfact command to verify. Another usefull command is show vpc consistancy-paramenter vpc 1902. If you have port down on any switch then you will see consitency parameter failed here.

Single Homed or Dual Homed FEX

With the ability to do enhanced VPCs now on the FEXs is there any benefit to have a mixture of having of single attached FEXs and dual homed FEXs?
Here are some benefits as I see them
Single homed FEX is easier to trouble shoot as the topology is not as complex.
A dual homed FEX will support both dual attached hosts and a single attached host. So this means we only have one topology to deal with (everything dual homed)
Any other pros or cons?
Thanks

If you have any servers with only one uplink, you want dual homed FEXes for redundancy.
Also, it depend on the number of FEXes you are connecting to the same set of switches. For example: the max number of FEXes that can be uplinked to a set of 6k switches is 24 if you are dual homed, but if you are single homed the max is 48 (24 per switch).
HTH

Cisco 2811 Connected to FEX

Hi All,
We are planning on connecting a Cisco 2811 router that will be acting as a voice gateway to a pair of Cisco FEX 2248s that are connected to a parent Nexus 5548s. Each FEX is connected to Each 5548 so that we can use Enhanced vPC.
Are there any issues with connecting a voice gateway to the FEXs? As the FEX can support Enhanced vPC is it ok to port-channel the 2811 to the FEX for redundancy?
Thanks

related link
https://supportforums.cisco.com/discussion/11425491/nexus-2000-fex-connected-cisco-2800-router

Dual homed server to dual homed Nexus fabric extenders

I don't see anything in Cisco docs that explicitly say that this is a supported setup so I just wanted to see if anyone here has any insight on this.
Is it supported to dual home a server via etherchannel to a pair of Nexus fabric extenders that are themselves dual homed two a pair of Nexus 5Ks?
Thanks!

If i understand correctly i think what you are referring to is Enhanced vPC. See this link for details -
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/mkt_ops_guides/513_n1_1/n5k_enhanced_vpc.html
Jon

Enhanced VPC doubt

Similar Messages

Maybe you are looking for