Cisco Nexus 5000 Series Operation Manual page 32

Dedicated VRF For a Keepalive Interface
S e n d d o c u m e n t a t i o n c o m m e n t s t o n 5 k d o c f e e d b a c k @ c i s c o . c o m
We recommend that you use an out-of-band management interface (mgmt0) as a vPC keepalive interface
although you have the option to use the front-panel data port as a vPC keepalive interface. When you
choose to use the front panel 10-Gigabit Ethernet port as the vPC keepalive interface, you should create
a separate VRF for vPC keepalive packets when Layer 3 is enabled with vPC. This process eliminates
the possibility of disrupting the vPC keepalive link by the wrong routes learned by a dynamic routing
protocol.
This example shows how to configure a new VRF named vpc_keepalive for the vPC keepalive link and
how to display the vPC peer keepalive configuration:
vrf context vpc_keepalive
interface Ethernet1/31
switchport access vlan 123
interface Vlan123
vrf member vpc_keepalive
ip address 123.1.1.2/30
no shutdown
vpc domain 1
peer-keepalive destination 123.1.1.1 source 123.1.1.2 vrf vpc_keepalive
layer3-switch# show vpc peer-keepalive
vPC keep-alive status
--Peer is alive for
--Send status
--Last send at
--Sent on interface
--Receive status
--Last receive at
--Received on interface
--Last update from peer
vPC Keep-alive parameters
--Destination
--Keepalive interval
--Keepalive timeout
--Keepalive hold timeout
--Keepalive vrf
--Keepalive udp port
--Keepalive tos
The services provided by the Cisco Nexus 5500 Platform switch, such as Ping, SSH, Telnet, and
RADIUS, are VRF-aware. You must specify the VRF name in the CLI in order to use the correct routing
table.
layer3-switch# ping 123.1.1.1 vrf vpc_keepalive
PING 123.1.1.1 (123.1.1.1): 56 data bytes
64 bytes from 123.1.1.1: icmp_seq=0 ttl=254 time=3.234 ms
64 bytes from 123.1.1.1: icmp_seq=1 ttl=254 time=4.931 ms
64 bytes from 123.1.1.1: icmp_seq=2 ttl=254 time=4.965 ms
64 bytes from 123.1.1.1: icmp_seq=3 ttl=254 time=4.971 ms
64 bytes from 123.1.1.1: icmp_seq=4 ttl=254 time=4.915 ms
--- 123.1.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 3.234/4.603/4.971 ms
Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
2-8
Chapter 2 Cisco Nexus 5500 Platform Layer 3 and vPC Operations
: peer is alive
: (154477) seconds, (908) msec
: Success
: 2011.01.14 19:02:50 100 ms
: Vlan123
: Success
: 2011.01.14 19:02:50 103 ms
: Vlan123
: (0) seconds, (524) msec
: 123.1.1.1
: 1000 msec
: 5 seconds
: 3 seconds
: vpc_keepalive
: 3200
: 192