Over the past few weeks, I feel like I have been doing nothing except virtual port channels (vPC), because of that it seems right to review what they are and what they are not.
Port-Channels? What are they and how do they apply to vPC?
In order to talk about vPC we first need to have a good understanding of Port Channels. For those who have completed their CCNA you should remember a term called EtherChannel. Well EtherChannel = Port-Channel and they allow us to take multiple physical interfaces and combine them together to increase bandwidth or redundancy. Port-Channels are also seen and treated as a single switch port with Spanning Tree (STP). This part of the reason why we can see a bandwidth increase because the traffic is split between all active links since there is no loop.
Virtual Port Channels Overview
vPC expand on the functionality of Port-Channels including some features that are present in VSS or Virtual Switch System. While Port-Channels are tied down to a single switch chassis, Virtual Port Channels are able to span multiple chassis. a feature that is present with VSS on the Catalyst line of switches. vPC configuration will create a single control plane that handles the communication of between the primary and secondary switch. All of this will live with a single vPC Domain.
These communications are sent over the “Peer-Link”. The “Peer-Link” is typically 2-4 high speed links that are configured in a Port-Channel between switches. You have the ability to use up to 16 links for the “Peer-Link” but in my experiences, the “peer-links” have been configured with 2 x 40GB DAC or 2 x 100GB DAC.
Alongside of the “Peer-Link” there is also a “KeepAlive” link. This link can be configured as a port-channel, single routed port or the out of band management interface. If you have the ports it is best practice to configure it using a port-channel. The purpose of the KeepAlive is to assist in the event of an Active-Active vPC Peer as well as monitor the peer switch for failure.
Management? How does that change?
While switches in a vPC configuration act as a single logical switch, they are not physically managed as a single switch like a VSS setup. vPC peers have independent management planes so you will need to mirror your configuration on both switches.
This one has caused me trouble before. Missing a simple value like an allowed vlan on a Port-Channel can cause the vPC to go to an inconsistent state which can and will prevent the port-channel from coming up and up.
What devices support vPC?
vPC is primarily a datacenter feature and will be present on the Cisco Nexus platform. This includes the Nexus 2000, 3000 5000, 7000, and 9000 series. You should always check the documentation on your switch before setting up vPC. Certain topologies are not supported on all switch models and firmware versions.
Nexus vPC configuration:
We will look at this in the next post. Stay tuned!