cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1632
Views
5
Helpful
9
Replies

VPC failed between 5548 and 2232

Pete89
Level 2
Level 2

Hello,

This is my first stab at VPCs. Here is what we are working with for hardware:

2 5548s

2 2232s

Twinax for 5k to 5k VPC

FET-10g fro 2k to 5k VPC

HP Servers with dual port CNAs

And here is a drawing of the topology:

photo.JPG

The 5k to 5k VPC looks good:

bottomSW# sh vpc br

Legend:

                (*) - local vPC is down, forwarding via vPC peer-link

vPC domain id                   : 1

Peer status                     : peer adjacency formed ok

vPC keep-alive status           : peer is alive

Configuration consistency status: success

Per-vlan consistency status     : success

Type-2 consistency status       : success

vPC role                        : secondary

Number of vPCs configured       : 1

Peer Gateway                    : Disabled

Dual-active excluded VLANs      : -

Graceful Consistency Check      : Enabled

vPC Peer-link status

---------------------------------------------------------------------

id   Port   Status Active vlans

--   ----   ------ --------------------------------------------------

1    Po1    up     1,101

vPC status

----------------------------------------------------------------------------

id     Port        Status Consistency Reason                     Active vlans

------ ----------- ------ ----------- -------------------------- -----------

10     Po10        down*  failed      Consistency Check Not      -

                                      Performed

But as you can see VPC 10 which is the 2k to 5k VPC is down.

When I do a show interface ethernet 100/1/1

I get this:

Ethernet100/1/1 is down (SFP not inserted)

Which is pretty interesting since I can mange the 2k from the 5k. Here is the whole config for one 5k:

bottomSW# sh run

!Command: show running-config

!Time: Wed Sep  7 17:46:29 2011

version 5.0(3)N2(1)

feature telnet

cfs eth distribute

feature interface-vlan

feature lacp

feature vpc

feature lldp

feature vtp

feature fex

username admin password 5 $1$zrjRKCYM$rQilwKQUCG4t.HMK4nmd/1  role network-admin

no password strength-check

ip domain-lookup

hostname bottomSW

class-map type qos class-fcoe

class-map type queuing class-fcoe

  match qos-group 1

class-map type queuing class-all-flood

  match qos-group 2

class-map type queuing class-ip-multicast

  match qos-group 2

class-map type network-qos class-fcoe

  match qos-group 1

class-map type network-qos class-all-flood

  match qos-group 2

class-map type network-qos class-ip-multicast

  match qos-group 2

fex 100

  pinning max-links 1

  description "FEX0100"

snmp-server user admin network-admin auth md5 0x03400bbb1e9f6a9774fdd375c4d30349

priv 0x03400bbb1e9f6a9774fdd375c4d30349 localizedkey

vrf context management

  ip route 0.0.0.0/0 10.3.0.13

vpc domain 1

  peer-keepalive destination 10.3.0.13

interface Vlan1

  no shutdown

interface port-channel1

  switchport mode trunk

  vpc peer-link

  switchport trunk allowed vlan 1,101

  spanning-tree port type network

interface port-channel10

  vpc 10

  switchport access vlan 101

interface port-channel100

  switchport mode fex-fabric

  fex associate 100

interface Ethernet1/15

  switchport mode fex-fabric

  fex associate 100

  channel-group 100

interface Ethernet1/16

  description VPC peer link

  switchport mode trunk

  switchport trunk allowed vlan 1,101

  channel-group 1 mode active

interface Ethernet1/31

  switchport mode fex-fabric

  fex associate 100

  channel-group 100

interface Ethernet1/32

  description VPC peer link

  switchport mode trunk

  switchport trunk allowed vlan 1,101

  channel-group 1 mode active

interface mgmt0

  description keep alive to topSW

  ip address 10.3.0.12/27

interface Ethernet100/1/1

  switchport access vlan 101

  channel-group 10

interface Ethernet100/1/2

  switchport access vlan 101

  channel-group 10

line console

line vty

boot kickstart bootflash:/n5000-uk9-kickstart.5.0.3.N2.1.bin

boot system bootflash:/n5000-uk9.5.0.3.N2.1.bin

bottomSW#

Thanks for any advice or help!!!

P.

9 Replies 9

Jerry Ye
Cisco Employee
Cisco Employee

Where is the server connected to on the FEX?

I am seeing you did a port-channel on the same FEX

interface port-channel10

  vpc 10

  switchport access vlan 101

interface Ethernet100/1/1

  switchport access vlan 101

  channel-group 10

interface Ethernet100/1/2

  switchport access vlan 101

  channel-group 10

Your server has 4 ethernet interfaces? 2 to N5K-1 and 2 to N5K-2? Can you show the other switch's configuration?

Regards,

jerry

Hi Jerry,

There are no servers attached yet to the 2ks. All I am trying to do now are the VPCs between the 5k and the 2ks. In the drawing the red circles represent the VPCs.

So, in my case I am trying to create a VPC with two member interfaces on the 2k to one upstream 5k

If you do two member interfaces on a N2K to one upstream N5K, it is not a vPC. It is a regular port-channel. vPC means port-channel touch both switches.

Regards,

jerry

Ok, now I am confused. Arent the yellow labled ports on the right side of the 2232 the uplink ports that should go to the 5ks? Where do I configure them?

According from your topology, the FEX/N2K connection to the N5K is not a vPC. It is a regular port-channel.

The connection between to N5K to the 4507(?) is a vPC.

The cross link between (peer-link) is not a vPC.

The server connection to the FEX if they are attaching to both N2K, it is a vPC. If you are only attach to 1 FEX, it is a port-channel.

HTH,

jerry

OK I bought all this gear because Cisco told me that I could get VPCs and get rid of STP. Now I am back to using port channels again? I showed this drawing to a data center designer. I asked him everywhere you see a red circle is a VPC right? I was told yes by him.

So let me ask again. In my drawing the only VPC is down where the CNAs and 2ks meet? Everything else has to be port channel?

The devil is in the details for sure.

Thank you,

P.

First of all, port-channel (802.1ad) is not spanning-tree (802.1w - rapid spanning-tree), port-channel is bundling multiple physical interfaces into 1 logical interface.

Yes the only vPCs are the servers connected to two different N2Ks.

The only explaination I can give you is, you have to set up a vPC domain in both N5K. Maybe this is why he said it is a vPC(???).

Regards,

jerry

OK Jerry,

I enjoyed the crash course in vPC and port channel. I believe you are right, I think I confused the use of the terms vPC domain and vPC at the port level.

I found this which helps out , bui it never explains that the uplink ports on the 2ks have no configuration on thier own. The ports on the 5k that go to 2ks get:

switchport mode fex-fabric

  fex associate number

  channel-group number

http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/configuration_guide_c07-543563.html

I appreciate the time you took to explain!!

P.

Here is another example you can take a look (Basic Configuration - No Port Profile):

http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/operations/n5k_config_sync_ops.html#wp1080810

You have to do the same configuration on both N5Ks.

Regards

jerry