Solved: Hi,

opnineopnine · ‎10-22-2015

Hi all,

I have 2 7000 series, I have created peer-link and peer-keepalive between them, I will connect this device to my MDS 9000 series, this ones have differente server connected to there ports.

What I don't understand is, I created the peer-link and keepalive between the 7000, when I connect from the 9000 to the 7000 do I have to use VPC per each server I have in the 9000 or I justa have to ues port-channles?

Thanks.

Steve Fuller · ‎10-23-2015

Hi,

I think this was why there was confusion. In the original post you stated MDS 9000.

So the answer is yes. The Nexus 7700 and 9000 both support vPC and so you can build a double sided vPC between them.

The Quick Start Guide :: Virtual Port Channel (vPC) is an excellent reference and has an example on slide 19.

Regards

View solution in original post

Reza Sharifi · ‎10-22-2015

Hi,

You can simply connect the servers to the 9000 using Portchannels. There is no need for VPC.

HTH

opnineopnine · ‎10-23-2015

Hi all,

If I have this diagram and not shure if this is ok.

7700 <-vpc / peer-link and keepalive / domain id 1-->7700

9000 <-vpc / peer-link and keepalive / domain id 2 -->9000

Now I want to conect with vpc from 9000 to 7700, should I make a new vpc with new domain or just a port channel?

thanks.

Steve Fuller · ‎10-23-2015

Hi,

When you say "9000" do you mean Cisco MDS 9000 i.e., a SAN switch or do you mean Cisco Nexus 9000 as you stated in your original post?

If you mean MDS 9000 series switch, then as per the previous comments, you would need to use a standard port-channel as vPC is not supported on this platform.

If you mean Nexus 9000, these do support vPC and so you could connect the Nexus 9000 vPC domain to the Nexus 7700 vPC domain using the "double side" vPC.

Regards

opnineopnine · ‎10-23-2015

Hello Steve,

My 9000 are the C9372PX chassis, here I can use a peer-link to the 7700, with differet domain Id.?

thanks.

Reza Sharifi · ‎10-23-2015

As Steve said, you can connect each of the C9372PX switches to both 7700 switches. This would be a double sided VPC.

HTH

opnineopnine · ‎10-23-2015

So if I apply this will be ok ? this is from the 9000 to 7700

int e2/27 -28
channel-group 100 mode active

int po100
switchport
switchport mode trunk
spanning-tree port type normal
vpc 100

Steve Fuller · ‎10-23-2015

Correct. As I said, slide 19 of the quick start guide I linked to previously has a working example.

Regards

opnineopnine · ‎10-23-2015

Hi all

I just did the configuration recommended and now have this error.

vPC status
----------------------------------------------------------------------
id   Port      Status Consistency Reason                  Active vlans
--   ----      ------ ----------- ------                  ------------
20   Po20      down* failed      vpc port channel           -
                                  mis-config due to vpc
                                  links in the 2 switches
                                  connected to different
                                  partners

Any ideas?

Steve Fuller · ‎10-24-2015

Hi,

It's not clear which switch you ran this command from, but essentially it's telling you that the Link Aggregation (LAG) System ID being received from the two devices connected to the interfaces that are members of port-channel 20 is different on each interface. As you have port-channel 20 configured as a vPC, then it expects the ID to the same.

If you run the command show lacp neighbor interface port-channel 20, the Partner System ID see on all the physical interfaces should be same.

In my setup I have a vPC domain formed from switch1 and switch2 connected via eth1/1 and eth1/2 to a second vPC domain formed from switch3 and switch4. In the following you can see the LAG Partner System ID is the same on eth1/1 and eth1/2 of both switch1 and switch2:

switch1# sh lacp nei int po11
Flags:  S - Device is sending Slow LACPDUs F - Device is sending Fast LACPDUs
        A - Device is in Active mode       P - Device is in Passive mode
port-channel11 neighbors
Partner's information
            Partner                Partner                     Partner
Port        System ID              Port Number     Age         Flags
Eth1/1      32667,0-23-4-ee-be-b   0x101           835         SA

            LACP Partner           Partner                     Partner
            Port Priority          Oper Key                    Port State
            32768                  0x800b                      0x3d

Partner's information
            Partner                Partner                     Partner
Port        System ID              Port Number     Age         Flags
Eth1/2      32667,0-23-4-ee-be-b   0x4101          768         SA

            LACP Partner           Partner                     Partner
            Port Priority          Oper Key                    Port State
            32768                  0x800b                      0x3d

switch2# sh lacp nei int po11
Flags:  S - Device is sending Slow LACPDUs F - Device is sending Fast LACPDUs
        A - Device is in Active mode       P - Device is in Passive mode
port-channel11 neighbors
Partner's information
            Partner                Partner                     Partner
Port        System ID              Port Number     Age         Flags
Eth1/1      32667,0-23-4-ee-be-b   0x102           879         SA

            LACP Partner           Partner                     Partner
            Port Priority          Oper Key                    Port State
            32768                  0x800b                      0x3d

Partner's information
            Partner                Partner                     Partner
Port        System ID              Port Number     Age         Flags
Eth1/2      32667,0-23-4-ee-be-b   0x4102          812         SA

            LACP Partner           Partner                     Partner
            Port Priority          Oper Key                    Port State
            32768                  0x800b                      0x3d

The Partner System ID should match the System MAC address of the downstream devices, and if those devices are also running vPC, the System ID should be the MAC address seen when you run the show vpc role command on those downstream devices. For example:

switch3#  sh vpc role

vPC Role status
----------------------------------------------------
vPC role                        : primary
Dual Active Detection Status    : 0
vPC system-mac                  : 00:23:04:ee:be:0b
vPC system-priority             : 32667
vPC local system-mac            : 54:7f:ee:0c:18:3c
vPC local role-priority         : 1

switch4# sh vpc role

vPC Role status
----------------------------------------------------
vPC role                        : secondary
Dual Active Detection Status    : 0
vPC system-mac                  : 00:23:04:ee:be:0b
vPC system-priority             : 32667
vPC local system-mac            : 54:7f:ee:10:ce:7c
vPC local role-priority         : 2

Are you able to post a diagram of the setup showing the interfaces that connect between the four switches? Also can you post the output of the following commands from all four switches i.e., both the Nexus 7700 and Nexus 9000

show run vpc
show port-ch summary
show cdp nei

Regards

Steve Fuller · ‎10-23-2015

Hi,

I think this was why there was confusion. In the original post you stated MDS 9000.

So the answer is yes. The Nexus 7700 and 9000 both support vPC and so you can build a double sided vPC between them.

The Quick Start Guide :: Virtual Port Channel (vPC) is an excellent reference and has an example on slide 19.

Regards

Masoud Pourshabanian · ‎10-23-2015

Please check the link below. You are able to config all switches in one VPC domain..

You can find all cautions related to one VPC domain or and two VPC domains.
.

http://www.cisco.com/c/dam/en/us/td/docs/switches/datacenter/sw/design/vpc_design/vpc_best_practices_design_guide.pdf

Masoud Pourshabanian · ‎10-22-2015

You need to configure a VPC on 7000-1 and 7000-2 for MDS connection( suppose MDS has one link connected to each 7000)

Configuration looks like this.

7000-1
int po100
switch mode trunk
vpc 100
int e1/3 [ connected to MDS]
channel-group 30 mode active

7000-2
int po100
switch mode trunk
vpc 100 [Connected to MDS]
int e1/3
channel-group 30 mode active

On MDS, you need to create just a regular port-channel for 7000-1 and 7000-2 connection

and some other regular port-channels for your server connections . ( one for each server)

As you can see the term of VPC is only used on 7000. Your MDS sees VPC peers as a single device.

Hope it helps.

Masoud

Ganesh Hariharan · ‎10-22-2015

Hi all,


I have 2 7000 series, I have created  peer-link and peer-keepalive between them, I will connect this device to my MDS 9000 series, this ones have differente server connected to there ports.

What I don't understand is, I created the peer-link and keepalive between the 7000, when I connect from the 9000 to the 7000 do I have to use VPC per each server I have in the 9000 or I justa have to ues port-channles?


Thanks.

Hi,

As suggested , Create vPC domain for two N7k and you can create Multi chasis ether channel with MDS to N7k switches for uplink connectivity.

Considering you have single MDS switch then from server to MDS you can go with simple port channel.

Check out the below link on vPC design which can be helpful for your implementation.

http://www.cisco.com/c/en/us/products/collateral/switches/nexus-9000-series-switches/guide-c07-733228.html

Hope it Helps..

-GI

Rate if it Helps

Understaning VPC