12-17-2010 11:20 PM - edited 03-06-2019 02:36 PM
Hello,
We are trying to configure a pair of Nexus 5K's and setup vpc peer link between them. When I issue the show vpc brief command,
WE-SSIPL-NX1# show vpc brief
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 1
Peer status : peer link is down
(peer-keepalive not operational,
peer never alive)
vPC keep-alive status : Suspended (Destination IP not reachable)
Configuration consistency status: failed
Configuration consistency reason: Consistency Check Not Performed
vPC role : none established
Number of vPCs configured : 0
Peer Gateway : Disabled
Dual-active excluded VLANs : -
vPC Peer-link status
---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ --------------------------------------------------
1 Po20 up -
WE-SSIPL-NX1# show port-channel summary
Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
S - Switched R - Routed
U - Up (port-channel)
--------------------------------------------------------------------------------
Group Port- Type Protocol Member Ports
Channel
--------------------------------------------------------------------------------
10 Po10(SU) Eth LACP Eth101/1/27(P) Eth101/1/28(P)
20 Po20(SU) Eth LACP Eth1/9(P) Eth1/10(P)
51 Po51(SU) Eth NONE Eth1/19(P) Eth1/20(P)
101 Po101(SU) Eth NONE Eth1/1(P) Eth1/2(P)
102 Po102(SD) Eth NONE Eth1/3(D) Eth1/4(D)
103 Po103(SD) Eth NONE Eth1/5(D) Eth1/6(D)
104 Po104(SD) Eth NONE Eth1/7(D) Eth1/8(D)
105 Po105(SD) Eth NONE --
WE-SSIPL-NX1# show version
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS: version 1.2.0
loader: version N/A
kickstart: version 4.2(1)N1(1)
system: version 4.2(1)N1(1)
power-seq: version v1.2
BIOS compile time: 06/19/08
kickstart image file is: bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin
kickstart compile time: 4/29/2010 19:00:00 [04/30/2010 08:08:04]
system image file is: bootflash:/n5000-uk9.4.2.1.N1.1.bin
system compile time: 4/29/2010 19:00:00 [04/30/2010 09:21:47]
Hardware
cisco Nexus5010 Chassis ("20x10GE/Supervisor")
Intel(R) Celeron(R) M CPU with 2074284 kB of memory.
Processor Board ID JAF1422DRAC
Device name: WE-SSIPL-NX1
bootflash: 1003520 kB
Kernel uptime is 9 day(s), 14 hour(s), 28 minute(s), 32 second(s)
Last reset
Reason: Unknown
System version: 4.2(1)N1(1)
Service:
plugin
Core Plugin, Ethernet Plugin
the peer-keepalive link is not working fine and the vpc peer relationship isn't coming active. I'm following the Cisco N5K config guide and have both sides of the 5K's config'd the same (except for the peer keepalive IP addresses) but can't seem to bring the vpc peer link active. Are there any vpc setup guides that anybody has found helpful? Thanks in advance for any suggestions,
I am having 2 peer-links and 1 peer-keepalive directly connecting to my other N5k.
Mangesh...
12-18-2010 08:27 AM
The VPC peer link was suspended because the destination peer keep-alive is not reachable. This is from your output provided:
WE-SSIPL-NX1# show vpc brief
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 1
Peer status : peer link is down
(peer-keepalive not operational,
peer never alive)
vPC keep-alive status : Suspended (Destination IP not reachable)
Configuration consistency status: failed
Configuration consistency reason: Consistency Check Not Performed
vPC role : none established
Number of vPCs configured : 0
Peer Gateway : Disabled
Dual-active excluded VLANs : -
You will need to get the keep-alive working for VPC to come up. The vPC peer-keepalive can be carried either in the management or default VRF on the Cisco Nexus 5000 Series switch. When you configure the switches to use the management VRF, the source and destination for the keepalive messages are the mgmt 0 interface IP addresses. When you configure the switches to use the default VRF, an SVI must be created to act as the source and destination addresses for the vPC peer-keepalive messages. Ensure that both the source and destination IP addresses used for the peer-keepalive messages are unique in your network and these IP addresses are reachable from the VRF associated with the vPC peer-keepalive link.
If you require further assistance please provide show run vpc from each switch to review the configurations.
Thanks,
Dale
04-22-2017 08:02 AM
I have the same problem,,
Can u help in that plz,,
thanks
---------------------
vPC domain id : 100
Peer status : peer link is down
vPC keep-alive status : Suspended (Destination IP not reachable)
Configuration consistency status : failed
Per-vlan consistency status : success
Configuration inconsistency reason: Consistency Check Not Performed
Type-2 inconsistency reason : Consistency Check Not Performed
vPC role : none established
Number of vPCs configured : 0
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Disabled (due to peer configuration)
Auto-recovery status : Disabled
Delay-restore status : Timer is off.(timeout = 30s)
Delay-restore SVI status : Timer is off.(timeout = 10s)
vPC Peer-link status
---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ --------------------------------------------------
1 Po100 up -
----------------------------
100 Po100(SU) Eth LACP Eth1/47(P) Eth1/48(P)
04-22-2017 09:00 AM
Hello,
vPC keep-alive status : Suspended (Destination IP not reachable),
Which interface did you use for keep alive? Can you ping the destination peer through keep-alive link?
Masoud
04-22-2017 09:25 AM
Hello too Masoud,
N9K-1:
vrf context AYTB
vrf context management
vpc domain 100
role priority 4000
peer-keepalive destination 10.1.1.65 source 10.1.1.66 vrf AYTB
interface port-channel100
switchport
switchport mode trunk
spanning-tree port type network
vpc peer-link
interface Ethernet1/46
description *** VRF link ***
vrf member AYTB
ip address 10.1.1.65/24
no shutdown
interface Ethernet1/47
switchport
switchport mode trunk
channel-group 100 mode active
no shutdown
interface Ethernet1/48
switchport
switchport mode trunk
channel-group 100 mode active
no shutdown
-----------------------------------
N9K-2:
vrf context AYTB
vrf context management
vpc domain 100
role priority 4000
peer-keepalive destination 10.1.1.65 source 10.1.1.66 vrf AYTB
interface port-channel100
switchport
switchport mode trunk
spanning-tree port type network
vpc peer-link
interface Ethernet1/46
description ** VRF link ***
vrf member AYTB
ip address 10.1.1.66/24
no shutdown
interface Ethernet1/47
switchport
switchport mode trunk
channel-group 100 mode active
no shutdown
interface Ethernet1/48
switchport
switchport mode trunk
channel-group 100 mode active
no shutdown
I will go to the DC to cheq the PING again..
04-22-2017 09:55 AM
Its working now,,,,
there was wrong IP..
many thanks ya Masoud.
04-22-2017 10:06 AM
I am glad your problem was solved.
03-05-2018 04:52 AM
Hello Mangesh,
VPC not successful over 2 N5k
Usually a vPC peer-link is down either due to a link failure or when the peer switch is completely down
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide