cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
200
Views
0
Helpful
3
Replies
Highlighted
Beginner

vPC & non vPC VLANs

Hello,

I know that best practices is to have a dedicated port-channel for non vPC VLANs and not to allow those VLANs in the peer link. My question is, will it still valid to allow vPC and non vPC VLANs in the peer link? Will that have impact on the performance, traffic flow ..etc?

Noting that some non vPC VLANs are configured in HSRP.

 

Regards,

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Hall of Fame Expert

Hi,

There should not be any performance issue but it is recommended to use the exclude command "dual-active exclude interface-vlan <non-vPC vlans list>" 

From the vPC design dpocument:

On the Cisco Nexus 7000 Series, when carrying vPC and non-vPC VLANs on the peer link, you may want to
exclude the orphaned ports SVIs from the default behavior by using the command dual-active exclude
interface-vlan <non-vPC vlans list>. Alternatively, you can use different VLANs for vPC-connected devices and
single-port attached devices (orphaned ports), and put the non-vPC VLANs and the peer link on different trunks.

 

Link:

https://www.cisco.com/c/dam/en/us/products/collateral/switches/nexus-7000-series-switches/C07-572830-00_Agg_Dsgn_Config_DG.pdf

HTH

View solution in original post

3 REPLIES 3
Highlighted
Hall of Fame Expert

Hi,

There should not be any performance issue but it is recommended to use the exclude command "dual-active exclude interface-vlan <non-vPC vlans list>" 

From the vPC design dpocument:

On the Cisco Nexus 7000 Series, when carrying vPC and non-vPC VLANs on the peer link, you may want to
exclude the orphaned ports SVIs from the default behavior by using the command dual-active exclude
interface-vlan <non-vPC vlans list>. Alternatively, you can use different VLANs for vPC-connected devices and
single-port attached devices (orphaned ports), and put the non-vPC VLANs and the peer link on different trunks.

 

Link:

https://www.cisco.com/c/dam/en/us/products/collateral/switches/nexus-7000-series-switches/C07-572830-00_Agg_Dsgn_Config_DG.pdf

HTH

View solution in original post

Highlighted

Hello,
Thanks for the reference, based on the information listed in it, I can say it's fine in my case to trunk the non-vPC VLANs in the peer link even without exclude them. The reason is, In my case I have two FWs Active/Standby are connected to the vPC domain so I have the below configuration;
On vPC primary;
vlan 10
ip address 10.10.10.2
hsrp 10.10.10.1
on the vPC secondary;
vlan 10
ip address 10.10.10.3
hsrp 10.10.10.1


What do you think about this?
Highlighted

Hi,

This should work fine. I would just give a higher priority to hsrp on the primary vPC, so that it is the active HSRP. It is usually good practice to have the one device the primary for HSRP, STP root and vPC.

HTH

Content for Community-Ad