Hi everyone, today we're going to configure a basic vPC topology
With two Nexus 9000 switches
Two network cables in a port channel will make up the peer-link
The keep alive will be a single link using the management interfaces
The configuration is a four step process
We'll enable the needed features, configure the keepalive link
the vPC domain, and finally the peer-link
When that's done, we'll have a brief look at member ports and orphan ports
Now, on to the configuration
The first step is to enable the vpc and LACP features
LACP is required for the peer link port channel
Also the switches still have to negotiate the port channel with the connected device
even though it's a vPC
Next, we're going to configure the keep alive link using the management ports
The management ports are already in a VRF, so we don't need to create one
The management ports are routed, so you can connect them to a management network if you want
In this example, we're using a direct connection from one Nexus to another
We can test this by running a ping from one switch to another
We're going to use vPC domain 10 in this example
Switch 1 will be the primary switch, with a priority of 10
When configuring the keep alive link, use the management VRF
If normal ports were used, you would need to create VRFs for the keepalive
Switch 2 has a mirrored config
The priority is set higher, to make this switch the secondary
Here we can verify that both peers are up
The vPC domain is in a failed state, because the peer link has not been configured yet
We're going to use two 40G ports for the peer-link. They'll be in a normal port channel
This config is the same on both switches
Just to make sure this is in layer 2 mode, I'll enter the switchport command
and enable trunking
The vpc peer link command is entered directly on the port channel
Not in the vPC global configuration
Member ports are easy to configure
just start with a regular port channel, configured on both switches
then, enter the vpc command to associate it with a vPC number
The vpc number doesn't have to match the port channel number
But it is a good idea, it will make your life easier in the long run
We can see here that vpc 20 has successfully been configured
The status is still showing down, as nothing has been connected yet
Let's have a look at orphan ports
An orphan port is just a normal port that has no vPC configuration
To show this, we'll bring up ethernet 1/11 with no special config
The show vpc orphan ports command now lists this interface
And that's the end of the config
If you like this video, please leave a comment on youtube or on the site
If you'd like to be notified of new videos or articles, please follow me on twitter