nexus peer-keepalive fails after reload

[seegomaa]

Hi All,

 I'm facing a strange issue!. I have a pair of nexus 5548 running vpc. Everything work fine but when i reload one 5k, the vpc peer link remains suspended. I investigated and found that the svi i used for keepalive remains down after the reboot.

DR1-ACC-5K-B1-2# sh vpc peer-keepalive

vPC keep-alive status             : peer is not reachable through peer-keepalive
--Send status                   : Success
--Last send at                  : 2009.03.02 10:27:34 272 ms
--Sent on interface             :
--Receive status                : Failed
--Last update from peer         : (2538) seconds, (448) msec

vPC Keep-alive parameters
--Destination                   : 20.20.20.1
--Keepalive interval            : 1000 msec
--Keepalive timeout             : 5 seconds
--Keepalive hold timeout        : 3 seconds
--Keepalive vrf                 : VPC-KEEPALIVE
--Keepalive udp port            : 3200
--Keepalive tos                 : 192
DR1-ACC-5K-B1-2#

____________________________________________________

DR1-ACC-5K-B1-2# sh inter vlan 900
Vlan900 is down, line protocol is down
  Hardware is EtherSVI, address is  8c60.4f19.1f7c
  Internet Address is 20.20.20.2/30
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec

i tried shut no shut but no success.

[Vasilii Mikhailovskii]

Hello.

Do you enable VL 900 on peer-link?

[seegomaa]

Hi Vasili,

Yes i didn't do any restrictions on the vpc link trunk ( allowed all vlans including keepalive vlan)

[Vasilii Mikhailovskii · Accepted solution]

Hello.

That is the issue.

Peer-keepalive should be either a direct cable between the boxes, or go via some other (external) switch. It must not flow via peer-link.

PS just in case: dynamic L3-routing over VPC-enabled VLANs are not supported as well.

[seegomaa]

You are right,

I just removed vlan 900 from peer-link trunk and now keep-alive is fine!.

Thank you very much!