Triggering The Layer 3 Consistency Checker - Cisco Nexus 3000 Series Configuration Manual

Chapter 10 Managing the Unicast RIB and FIB
S e n d d o c u m e n t c o m m e n t s t o n e x u s 3 k - d o c f e e d b a c k @ c i s c o . c o m
Command
show ip route [ route-type | interface
int-type number | next-hop]
Example:
switch# show ip route
show ip adjacency [ prefix |
interface-type number [summary]|
non-best] [detail] [vrf vrf-id ]
Example:
switch# show ip adjacency
show ip routing [ route-type |
interface int-type number | next-hop
| recursive-next-hop | summary |
updated {since | until} time ]
Example:
switch# show routing summary
This example displays the unicast route table:
switch# show ip route
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
192.168.0.2/24, ubest/mbest: 1/0, attached
192.168.0.32/32, ubest/mbest: 1/0, attached
This example shows the adjacency information:
switch# show ip adjacency
IP Adjacency Table for VRF default
Total number of entries: 2
Address
10.1.1.1
10.1.1.253

Triggering the Layer 3 Consistency Checker

You can manually trigger the Layer 3 consistency checker.
To manually trigger the Layer 3 consistency checker, use the following commands in global
configuration mode:
*via 192.168.0.32, Eth1/5, [0/0], 22:34:09, direct
*via 192.168.0.32, Eth1/5, [0/0], 22:34:09, local
Age MAC Address
02:20:54 00e0.b06a.71eb
00:06:27 0014.5e0b.81d1
Cisco Nexus 3000 Series NX-OS Unicast Routing Configuration Guide, NX-OS Release 5.0(3)U1(1)
Purpose
Displays the unicast route table. The route-type argument
can be a single route prefix, direct, static, or a dynamic
route protocol. Use the ? command to see the supported
interfaces.
Displays the adjacency table. The argument ranges are as
follows:
prefix—Any IPv4 prefix address.
•
interface-type number—Use the ? command to see
•
the supported interfaces.
vrf-id—Any case-sensitive, alphanumeric string up
•
to 32 characters.
Displays the unicast route table. The route-type argument
can be a single route prefix, direct, static, or a dynamic
route protocol. Use the ? command to see the supported
interfaces.
Pref Source Interface
50 arp mgmt0
50 arp mgmt0
Managing the Unicast RIB and FIB
Best
Yes
Yes
10-7