cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
13370
Views
11
Helpful
5
Replies

consistency check is successful but vpc peer link is down ? why ?

kthned
Level 3
Level 3

Hi

I am unable to make the vPC peer link up between N7K. The consistency seems fine between the two N7K.

When I shut and no shut the vpc peer link, the vpc links come alive for very short period (==3 sec) and then go down again with following log in red.

%VPC-3-VPC_PEER_LINK_BRINGUP_FAILED: vPC peer-link bringup failed (vPC peer is not reachable over cfs)

%ETHPORT-3-IF_ERROR_VLANS_SUSPENDED: VLANs 2100-2101,2104-2149,2200-2249 on Interface port-channel10 are being suspended. (Reason: vPC peer is not reachable over cfs)

Sh vpc below

gw01-vdc01(config)# sh vpc

Legend:

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

vPC domain id                     : 10

vPC+ switch id                    : 112

Peer status                       : peer link is down

vPC keep-alive status             : peer is alive

vPC fabricpath status             : peer is reachable through fabricpath

Configuration consistency status  : success

Per-vlan consistency status       : success

Type-2 consistency status         : success

vPC role                          : primary

Number of vPCs configured         : 0

Peer Gateway                      : Disabled

Dual-active excluded VLANs        : -

Graceful Consistency Check        : Enabled

Auto-recovery status              : Disabled

Fabricpath load balancing         : Disabled

Port Channel Limit                : limit to 244

vPC Peer-link status

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

id   Port   Status Active vlans

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

1    Po10   down   -

gw01-vdc01(config-if)# sh running-config vpc all

!Command: show running-config vpc all

!Time: Thu Jun 13 14:59:56 2013

version 6.1(3)

feature vpc

logging level vpc 5

vpc domain 10

  role priority 32667

  system-priority 32667

  peer-keepalive destination 172.18.10.5 source 172.18.11.5 udp-port 3200 vrf management interval 1000 timeout 5 precedence 6  hold-timeout 3

  delay restore 30

  no dual-active exclude interface-vlan

  no peer-gateway

  no Layer3 peer

  graceful consistency-check

  no auto-recovery

  delay restore interface-vlan 10

  fabricpath switch-id 112

  no fabricpath multicast load-balance

  port-channel limit

interface port-channel10

  vpc peer-link

Can some expert help me in this.

Thanks

//Umair

2 Accepted Solutions

Accepted Solutions

Kyle McKay
Level 1
Level 1

May I please see the VPC configuration on both switches?

View solution in original post

ASAK Syed,

Glad to hear that. As you got the solution can you mark this post as answered so that others may be benifited with this in future rather than leaving this thread as unanswered?

Thanks in advance.

Regards

Inayath

*Plz rate all usefull posts and mark the thread as closed if answerd your query.

View solution in original post

5 Replies 5

Kyle McKay
Level 1
Level 1

May I please see the VPC configuration on both switches?

Hi Kyle,

Its exactly the same except the keep-alive IP addresses are just reverse. Anyway I can update you tommorow.

Regards,

Umair

Hi,

Few things to check:

1- Management interfaces up? Able to ping mgmt-ip address from devices respectively.

2- STP issue?

3- show fcs peers ( to see cdf recognized the local and remote)?

4- did you try reloading the devices?

5- Outputs required: show ver, show vpc brief, show vpc in-consistency check, show ip int br, ping result of mgmt-interface, show spanning tree, sh fcs peers.

HTH

Regards

Inayath

*Plz rate all usefull posts.

kthned
Level 3
Level 3

Hi

Actually it was an issue in the switch ids. Switch ID conflict with the other pair of leaf switches. Unfortunately it was not visible on the sh logging, which i think it should . Anyway the issue is resolved by changing switch id.

The following command helped me identifying the problem and the output below

gw01-vdc01# sh system internal vpcm event-history errors

8) Event:E_DEBUG, length:106, at 309237 usecs after Fri Jun 14 09:00:09 2013

    [102] Failed to registerfabricpath switch id  (peer-link,1). Err: ES switch-id n

ot available for allocation

Regards,

Umair

ASAK Syed,

Glad to hear that. As you got the solution can you mark this post as answered so that others may be benifited with this in future rather than leaving this thread as unanswered?

Thanks in advance.

Regards

Inayath

*Plz rate all usefull posts and mark the thread as closed if answerd your query.

Review Cisco Networking products for a $25 gift card