To display Cisco
Express Forwarding (CEF) adjacency table information, use the
show adjacency
command in
XR EXEC mode.
show
adjacency
[
ipv4
[
nexthop
ipv4-address
]
| mpls
| ipv6
]
[
interface
type
interface-instance
]
[summary]
[internal]
[remote]
[detail]
[
location
node-id
]
Syntax Description
ipv4
|
(Optional)
Displays only IPv4 adjacencies.
|
nexthop
ipv4-address
|
(Optional)
Displays adjacencies that are destined to the specified IPv4 nexthop.
|
mpls
|
(Optional)
Displays only MPLS adjacencies.
|
ipv6
|
(Optional)
Displays only IPv6 adjacencies.
|
interface-type
|
(Optional)
Interface type. For more information, use the question mark (?) online help
function.
|
interface-instance
|
Either a
physical interface instance or a virtual interface instance:
- Physical interface instance.
Naming notation is
rack/slot/module/port and a slash mark between values is
required as part of the notation.
-
rack: Chassis number of the rack.
-
slot: Physical slot number of the line card.
-
module: Module number. A physical layer interface module
(PLIM) is always 0.
-
port: Physical port number of the interface.
Note
|
In references to a Management Ethernet interface located on a
route processor card, the physical slot number is alphanumeric (
RP0 or RP1
)
and the module is CPU0. Example: interface MgmtEth0/
RP1
/CPU0/0.
|
- Virtual interface instance.
Number range varies depending on interface type.
For more
information about the syntax for the router, use the question mark (?) online
help function.
|
summary
|
Displays summary of CEF IPv4, IPv6, MPLS adjacency counts for complete and incomplete entries in the adjacency table. |
internal
|
Displays interfaces with internal HEX adjacencies and their hash values. |
remote
|
(Optional)
Displays only remote adjacencies. A remote adjacency is an internal adjacency
used to forward packets between line cards.
|
detail
|
(Optional)
Displays detailed adjacency information, including Layer 2 information.
|
location
node-id
|
(Optional)
Displays detailed CEF information for the designated node. The
node-id
argument is entered in the
rack/slot/module notation.
|
Command Default
No default
behavior or values
Command History
Release
|
Modification
|
Release 5.0.0
|
This command was introduced.
|
Usage Guidelines
This command is
used to verify that an adjacency exists for a connected device, that the
adjacency is valid, and that the MAC header rewrite string is correct.
If you do not
specify a node with the
location
keyword and
node-id
argument, this command displays the CEF adjacency table for the node on which
the command is issued.
Task ID
Task ID
|
Operations
|
cef
|
read
|
Examples
The following is
sample output from
show
adjacency
command with the
location
keyword specified:
RP/0/RP0/CPU0:router# show adjacency location 0/0/CPU0
Interface Address Version Refcount Protocol
/0/1/2(src mac only) 6 1 ipv4
/0/1/2 point to point 7 100004
/0/1/2 (interface) 3 1
The following is sample output from
show
adjacency command with the
ipv4 and summary
keywords specified:
RP/0/RSP0/CPU0:ios#show adjacency ipv4 HundredGigE0/0/0/0 summary
Mon Feb 13 09:00:29.953 UTC
-------------------------------------------------------------------------------
0/RSP0/CPU0
-------------------------------------------------------------------------------
Adjacency table (version 1) has 1 adjacency:
-------------------------------------------------------------------------------
0/0/CPU0
-------------------------------------------------------------------------------
Adjacency table (version 4) has 4 adjacencies:
The following is sample output from
show
adjacency command with the
ipv4 and detail
keywords specified:
RP/0/RSP0/CPU0:ios#show adjacency ipv4 HundredGigE0/0/0/0 detail
Mon Feb 13 09:05:22.086 UTC
-------------------------------------------------------------------------------
0/RSP0/CPU0
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
-------------------------------------------------------------------------------
0/0/CPU0
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
The following is sample output from
show
adjacency command with the
internal and location
keywords specified:
RP/0/RSP0/CPU0:ios#show adjacency internal location 0/RSP0/CPU0
Mon Feb 13 09:08:27.292 UTC
Interface Address Entry Protocol HashIndex
Mg0/RSP0/CPU0/0 (interface) 0x7791d0a8 4447
The following is sample output from
show
adjacency command with the
internal detail and location
keywords specified:
RP/0/RSP0/CPU0:ios#show adjacency internal detail location 0/RSP0/CPU0
Mon Feb 13 09:13:05.279 UTC
Mg0/RSP0/CPU0/0, (interface)
Version: 1, references: 1, transient lock: 0
MTU: 1500
Adjacency pointer is: 0x7791d0a8
Platform adjacency pointer is: 0x79d790a8
Last updated: Feb 13 08:33:30.765
Adjacency producer: dot1q (prod_id: 10)
Flags: interface adjacency, incomplete adj,
(Base-flag: 0x1, Entry-flag: 0x4, Status-flag: 0x0)
Netio idb pointer not cached
Cached interface type: 8
Adjacency references:
aib (JID 323, PID 6272), 1 reference
This table
describes the significant fields shown in the display.
Table 1.
show adjacency
Command
Field
Descriptions
Field
|
Description
|
Interface
|
Outgoing
interface associated with the adjacency.
|
Address
|
Address
can represent one of these addresses:
- Next hop IPv4 or IPv6
address
- Point-to-Point address
Information in parentheses indicates different types of
adjacency.
|
Version
|
Version
number of the adjacency. Updated whenever the adjacency is updated.
|
Refcount
|
Number of
references to this adjacency.
|
Protocol
|
Protocol
for which the adjacency is associated.
|
0f000800
and 000c86f33d330800453a21c10800
|
Layer 2
encapsulation string.
|
mtu
|
Value of
the maximum transmission unit (MTU).
|
flags
|
Internal
field.
|
packets
|
Number of
packets going through the adjacency.
|
bytes
|
Number of
bytes going through the adjacency.
|