VCP on Nexus C93108TC-FX

[marine253]

Hello ,

I a new to nexus.

I've been tasked to put two nexus switches (C93108TC-FX) into VCP.

I am more a VSS guy.

I  have the following concerns :

1) how many physical ports will be required to bring up the VCP ( i am being confused between  VCP peer link and VCP keepalive link)

2) can any ports be used as VCP ports?

3) is an orphan port required?

Thanks

[cassiolange]

Hello,

1) vPC peer link: The vPC peer link is the link used to synchronize states between the vPC peer devices. The vPC peer link carries control traffic between two vPC switches and also multicast, broadcast data traffic. In some link failure scenarios, it also carries unicast traffic. 

You can create a vPC peer link by configuring a port channel on one Cisco Nexus 9000 Series chassis by using two or more 10-Gigabit Ethernet ports or 40-Gigabit Ethernet ports. 

 vPC peer keepalive link: The peer keepalive link monitors the vitality of a vPC peer switch. The peer keepalive link sends periodic keepalive messages between vPC peer devices. The vPC peer keepalive link can be a management interface or switched virtual interface (SVI). No data or synchronization traffic moves over the vPC peer keepalive link; the only traffic on this link is a message that indicates that the originating switch is operating and running vPC.

For Nexus 9300 (Single SUP), best practices uses MGMT0 for keepalive. 

2) To ensure that you have the correct hardware to enable and run a vPC, enter the show hardware feature-capability command. If you see an X across from the vPC in your command output, your hardware cannot enable the vPC feature.

3) A non-vPC port, also known as an orphaned port, is a port that is not part of a vPC.

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/9-x/interfaces/configuration/guide/b_cisco_nexus_9000_series_nx-os_interfaces_configuration_guide_9x/b_cisco_nexus_9000_series_nx-os_interfaces_configuration_guide_9x_chapter_0100...

https://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/configuration_guide_c07-543563.html

Regards, 

[marine253]

Hello Cassiolange,

Thank you.

Would you recommend the following:

2 x 40Gbs LACP for vPC peer link and 2 x 40Gbps for Keepalive link? Thus using 4 x 40Gbps interfaces per switch..

[cassiolange]

Hello Marine, 

For VPC keepalive uses interface MGMT0. Just heartbeat.

2 X 10G LACP for vpc peer-link.

Design and configure your network, to avoid the frames or packet to utilize the peer-link. There is no problem doing this, but try to connect all device to the both nexus. Think a nexus like one layer 2 switch (when VPC is enable) and two routers. Avoid orphan ports. Again there is no problem, but when you need reach a orphan device maybe you need cross the vpc peer-link.

This documment is for N7K, but you could use as reference for your configuration.
https://www.cisco.com/c/dam/en/us/td/docs/switches/datacenter/sw/design/vpc_design/vpc_best_practices_design_guide.pdf

Regards, 

[marine253]

Thanks , will look at the document.

If the keepalives will be sent via the MGT port, the 2 ports should have ip connectivity.But then, both ports should be connected to a 3rd switch?? Is there any other way around this , without implicating a third device?  How would you physically connect the mgt ports otherwise? loop them back to the switch?

[cassiolange]

Hello,

No problem, you could connect Mgmt ports directly. This ports are layer 3 ports on the VRF MGMT.

In this cenario you will lost out-of-band managemnt and you will need access the switch thought a in-band interface (SVI or Layer 3 port).

Regards, 

[marine253]

Great then. Yeah in-band management is not an issue here.

Thanks

[marine253]

Hello Cassiolange,

The document you provided suggests that i use a dedicated port for the vPV peer-keepalive link.

I think that i am going to run 2 x 10Gbps links directly between the firepower. What do you think?

[cassiolange]

Hello,

This recommendation is for N7K, because N7K has 2 SUPs. 

Below the recommendation for all nexus family.

Regards,