Cisco Express Forwarding Commands on Cisco IOS XR Software
This chapter describes the commands used to configure and monitor Cisco Express Forwarding (CEF) on Cisco IOS XR software.
For detailed information about CEF concepts, configuration tasks, and examples, see Cisco IOS XR IP Addresses and Services Configuration Guide.
cef load-balancing fields
To select the hashing algorithm that is used for load balancing during forwarding, use the cef load-balancing fields command in global configuration mode. To undo a configuration and to default to the load balancing option of L3, use the no form of this command.
cef load-balancing fields {L3 | L4}
no cef load-balancing fields {L3 | L4}
Syntax Description
L3 |
Specifies the Layer 3 load-balancing for the hash algorithm that is based on the following fields: •Source IP address—Specifies the source IP address field in the IP packet header. •Destination IP address—Specifies the destination IP address in the IP packet header. •Router ID—Specifies the unique IP address that is assigned to the router. Since L3 is configured as the default value, you do not need to use the cef load-balancing fields command unless you want to configure Layer 4. |
L4 |
Specifies the Layer 3 and Layer 4 load-balancing for the hash algorithm that is based on the following fields: •Source IP address—Specifies the source IP address field in the IP packet header. •Destination IP address—Specifies the destination IP address in the IP packet header. •Source port—Specifies the value of the source port field in the TCP, UDP, or SCP packet header for Layer 4. •Destination port—Specifies the value of the destination port field in the TCP, UDP, or SCP packet header for Layer 4. •Router ID—Specifies the unique IP address that is assigned to the router. •Protocol—Specifies the value of the protocol field as specified in the IP packet header for Layer 4. •Ingress interface—Specifies the interface that is received from the packet for Layer 4. |
Defaults
When the router ID, source, and destination IP address fields are selected for load balancing, the default value is L3.
Command Modes
Global configuration
Command History
|
|
Release 3.6.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
You can undo only a Layer 4 configuration.
Per-flow load-balancing allows incoming data traffic on a router to be evenly distributed over multiple equal-cost connections. On the Cisco CRS-1, per-flow load-balancing is the only load-balancing algorithm that is used to perform Layer 2 and Layer 3 load-balancing decisions on IPv4, IPv6, and Multiprotocol Label Switching (MPLS) flows in the system.
The existing 3-tuple hash provides good-balancing for packet flows with different Layer 3 information (for example, source and destination IP addresses). However, this hash algorithm performs well for cases in which different packet flows, which are identified by Layer 4 content, contain the same Layer 3 packet information. For example, a network, which uses Port Address Translation (PAT) on one end of the network, distributes traffic to a content provider on the other end of the network that supports redundant access using the same IP address. With the Cisco CRS-1 router in the core network, the existing 3-tuple hash causes the packet flow to always flow through one path in the system; therefore, poor load-balancing across the equal cost paths occurs.
A new hash algorithm, which uses additional Layer 4 information from the Layer 3 packet, is needed to provide improved load-balancing support in the system. On the Cisco CRS-1, the 7-tuple hash algorithm is implemented to provide improved load-balancing. The following inputs are processed:
•Layer 3 information
•Source IP address
•Destination IP address
•Protocol
•Layer 4 information
•Source port
•Destination port
•Cisco CRS-1 router-related information
•Router ID
•Ingress interface bundle
Note The treatment is different for IPv4 and IPv6 fragmented packets that are fragmented on the router for various reasons. For example, the fragmented packets can originate at the router or they can arrive at the router with a size larger than the maximum transmission unit (MTU). Therefore, the 7-tuple load balancing is done on the whole packet, and fragmentation is done later so that all fragments can go on the same interface.
Examples
The following example shows how to configure Layer 3 and Layer 4 load-balancing for the hash algorithm from the cef load-balancing fields command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# cef load-balancing fields L4
The following example shows sample output that displays summary information for the CEF table from the show cef summary command:
RP/0/RP0/CPU0:router# show cef summary
IP CEF with switching (Table Version 0) for node0_RP0_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286242
286122 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20600784 bytes
11124 load sharing elements, 3014696 bytes, 297064 references
8 shared load sharing elements, 3008 bytes
11116 exclusive load sharing elements, 3011688 bytes
0 CEF route update drops, 3900571 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 15 adjacencies
The following example shows sample output that displays summary information for all locations from the show cef summary command:
RP/0/RP0/CPU0:router# show cef summary location all
IP CEF with switching (Table Version 0) for node0_0_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286202
286110 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20599920 bytes
11112 load sharing elements, 3012008 bytes, 297064 references
8 shared load sharing elements, 3008 bytes
11104 exclusive load sharing elements, 3009000 bytes
0 CEF route update drops, 2864666 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 1 adjacency
IP CEF with switching (Table Version 0) for node0_0_CPU1
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286202
286110 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20599920 bytes
11112 load sharing elements, 3012008 bytes, 297064 references
8 shared load sharing elements, 3008 bytes
11104 exclusive load sharing elements, 3009000 bytes
0 CEF route update drops, 2864666 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 1 adjacency
IP CEF with switching (Table Version 0) for node0_1_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286228
286112 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20600064 bytes
11114 load sharing elements, 3590384 bytes, 297064 references
8 shared load sharing elements, 3424 bytes
11106 exclusive load sharing elements, 3586960 bytes
0 CEF route update drops, 4076380 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 77 adjacencies
22 incomplete adjacencies
IP CEF with switching (Table Version 0) for node0_2_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286202
286110 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20599920 bytes
11112 load sharing elements, 3012008 bytes, 297064 references
8 shared load sharing elements, 3008 bytes
11104 exclusive load sharing elements, 3009000 bytes
0 CEF route update drops, 2864666 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 1 adjacency
IP CEF with switching (Table Version 0) for node0_2_CPU1
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286202
286110 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20599920 bytes
11112 load sharing elements, 3012008 bytes, 297064 references
8 shared load sharing elements, 3008 bytes
11104 exclusive load sharing elements, 3009000 bytes
0 CEF route update drops, 2864666 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 1 adjacency
IP CEF with switching (Table Version 0) for node0_3_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286204
286110 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20599920 bytes
11111 load sharing elements, 3589556 bytes, 297062 references
7 shared load sharing elements, 3148 bytes
11104 exclusive load sharing elements, 3586408 bytes
0 CEF route update drops, 4076376 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 21 adjacencies
12 incomplete adjacencies
IP CEF with switching (Table Version 0) for node0_RP0_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286242
286122 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20600784 bytes
11124 load sharing elements, 3014696 bytes, 297064 references
8 shared load sharing elements, 3008 bytes
11116 exclusive load sharing elements, 3011688 bytes
0 CEF route update drops, 4075013 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 15 adjacencies
Related Commands
|
|
bundle-hash |
Displays the path a bundle flow that comprises a source and destination address would take. For more information, see Cisco IOS XR Interface and Hardware Component Command Reference. |
show cef |
Displays information about packets forwarded by Cisco Express Forwarding (CEF). |
show cef summary |
Displays summary information for the Cisco Express Forwarding (CEF) table. |
show cef ipv4 exact-route |
Displays an IPv4 Cisco Express Forwarding (CEF) exact route. |
show cef ipv4 summary |
Displays a summary of the IPv4 Cisco Express Forwarding (CEF) table |
show cef ipv6 exact-route |
Displays the path an IPv6 flow comprising a source and destination address would take. |
show cef ipv6 summary |
Displays a summary of the IPv6 Cisco Express Forwarding (CEF) table. |
show mpls forwarding exact-route |
Displays the path an MPLS flow that comprises a source and destination address would take. For more information, see Cisco IOS XR Multiprotocol Label Switching Command Reference. |
clear adjacency statistics
To clear adjacency packet and byte counter statistics, use the clear adjacency statistics command in EXEC mode.
clear adjacency statistics [ipv4 [nexthop ipv4-address] | mpls | ipv6] [interface-type interface-instance | location node-id]
Syntax Description
ipv4 |
(Optional) Clears only IPv4 adjacency packet and byte counter statistics. |
nexthop ipv4-address |
(Optional) Clears adjacency statistics that are destined to the specified IPv4 nexthop. |
mpls |
(Optional) Clears only MPLS adjacency statistics. |
ipv6 |
(Optional) Clears only IPv6 adjacency statistics. |
interface-type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
interface-instance |
(Optional) 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. |
location node-id |
(Optional) Clears detailed adjacency statistics for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The clear adjacency statistics command is useful for troubleshooting network connection and forwarding problems.
If you do not specify any of the optional keywords, all adjacency statistics are cleared for the node on which the command is issued.
|
|
basic-services |
read, write |
cef |
read, write |
Examples
The following example displays sample output of the Cisco Express Forwarding (CEF) adjacency table information, and clears the IPv4 CEF adjacency statistics:
RP/0/RP0/CPU0:router# show adjacency detail
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
MgmtEth0/RP1/CPU0/0 (src mac only) 1 1 ipv4
000000000000001193efe8fe0800
MgmtEth0/RP1/CPU0/0 (interface) 2 1
MgmtEth0/RP1/CPU0/0 172.29.52.77 29 2 ipv4
001193efe8e2001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.105 19 2 ipv4
001b2a4e53e5001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.241 18 2 ipv4
001819d18c38001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.173 15 2 ipv4
0015c75f09f8001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.81 9 2 ipv4
001a6c40d89c001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.1 6 2 ipv4
0030f2f21038001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.201 3 2 ipv4
00107b3c6847001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.96 23 2 ipv4
0018ba800c80001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.168 22 2 ipv4
00503ee3dd80001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.152 21 2 ipv4
00503ee3df40001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.180 16 2 ipv4
0015c75f0800001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.28 12 2 ipv4
00127fd6ba09001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.76 7 2 ipv4
001193efe8ea001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.200 4 2 ipv4
00107b3c689f001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.83 26 2 ipv4
001a6c40d89c001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.151 25 2 ipv4
000a41052e01001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.91 17 2 ipv4
0018742c5f40001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.127 14 2 ipv4
0013c4cba200001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.27 11 2 ipv4
00127fd6ba08001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.75 8 2 ipv4
001193efe8e2001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.182 27 2 ipv4
0015c75f0800001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.150 24 2 ipv4
000a41052da1001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.90 20 2 ipv4
001874163f80001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.70 13 2 ipv4
5a5900000201001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.82 10 2 ipv4
00127fd6bc36001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.126 5 2 ipv4
0013c4cba548001193efe8fe0800
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
MgmtEth0/RP0/CPU0/0 (src mac only) 2 1 ipv4
0000000000005a59000002010800
MgmtEth0/RP0/CPU0/0 (interface) 1 1
MgmtEth0/RP0/CPU0/0 172.29.52.77 38 2 ipv4
001193efe8e25a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.105 29 2 ipv4
001b2a4e53e55a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.241 28 2 ipv4
001819d18c385a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.173 24 2 ipv4
0015c75f09f85a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.81 19 2 ipv4
001a6c40d89c5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.13 16 2 ipv4
001079e960385a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.153 15 2 ipv4
00e0b0552cc45a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.121 13 2 ipv4
0012da0b97ff5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.1 6 2 ipv4
0030f2f210385a59000002010800
257909 packets, 9246567 bytes
MgmtEth0/RP0/CPU0/0 172.29.52.201 4 2 ipv4
00107b3c68475a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.96 32 2 ipv4
0018ba800c805a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.168 31 2 ipv4
00503ee3dd805a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.152 30 2 ipv4
00503ee3df405a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.180 25 2 ipv4
0015c75f08005a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.28 22 2 ipv4
00127fd6ba095a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.76 17 2 ipv4
001193efe8ea5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.52 14 2 ipv4
0090929c88485a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.148 12 2 ipv4
00b064fce0bb5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.120 10 2 ipv4
00042892c7ff5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.200 5 2 ipv4
00107b3c689f5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.83 35 2 ipv4
001a6c40d89c5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.151 34 2 ipv4
000a41052e015a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.91 27 2 ipv4
0018742c5f405a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.127 23 2 ipv4
0013c4cba2005a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.27 21 2 ipv4
00127fd6ba085a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.75 18 2 ipv4
001193efe8e25a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.51 11 2 ipv4
00e04f5fe0685a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.71 3 2 ipv4
001193efe8fe5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.182 36 2 ipv4
0015c75f08005a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.150 33 2 ipv4
000a41052da15a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.90 26 2 ipv4
001874163f805a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.82 20 2 ipv4
00127fd6bc365a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.50 9 2 ipv4
0090929cf8685a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.190 8 2 ipv4
00000c4775e05a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.126 7 2 ipv4
0013c4cba5485a59000002010800
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
GigabitEthernet0/6/5/7 (src mac only) 4 1 ipv4
00000000000000000c07fa5e0800
POS0/6/4/0 (interface) 27 1
POS0/6/0/0 (interface) 26 1
GigabitEthernet0/6/5/7 (interface) 25 1
GigabitEthernet0/6/5/1 (src mac only) 6 1 ipv4
00000000000000000c015cb80800
222195 packets, 19973644 bytes
GigabitEthernet0/6/5/2 (src mac only) 5 1 ipv4
00000000000000000c02c9d60800
222251 packets, 19978582 bytes
GigabitEthernet0/6/5/6 (interface) 24 1
GigabitEthernet0/6/5/5 (interface) 23 1
GigabitEthernet0/6/5/4 (interface) 22 1
GigabitEthernet0/6/5/3 (interface) 21 1
GigabitEthernet0/6/5/2 (interface) 20 1
12001 packets, 2155986 bytes
GigabitEthernet0/6/5/1 (interface) 19 1
10803 packets, 1717298 bytes
GigabitEthernet0/6/5/0 (interface) 18 1
POS0/6/0/3 (interface) 32 1
POS0/6/4/2 (interface) 31 1
POS0/6/0/1 (src mac only) 43 1 ipv4
222207 packets, 17752538 bytes
POS0/6/0/1 point to point 42 2 ipv4
POS0/6/0/1 point to point 41 2 mpls
POS0/6/0/2 (interface) 30 1
POS0/6/4/1 (interface) 29 1
POS0/6/0/1 (interface) 28 1
73519 packets, 3019532 bytes
POS0/6/4/6 (src mac only) 48 1 ipv4
222198 packets, 17751798 bytes
POS0/6/4/6 point to point 47 2 ipv4
POS0/6/4/6 point to point 46 2 mpls
POS0/6/4/7 (interface) 40 1
POS0/6/4/6 (interface) 39 1
72915 packets, 2918638 bytes
POS0/6/4/5 (src mac only) 45 1 ipv4
POS0/6/4/5 point to point 44 2 ipv4
POS0/6/4/4 (src mac only) 51 1 ipv4
222198 packets, 17751852 bytes
POS0/6/4/4 point to point 50 2 ipv4
POS0/6/4/4 point to point 49 2 mpls
POS0/6/4/5 (interface) 35 1
66317 packets, 1458970 bytes
POS0/6/4/4 (interface) 34 1
72306 packets, 2799786 bytes
POS0/6/4/3 (interface) 33 1
GigabitEthernet0/6/5/2 10.16.8.6 11 2 mpls
0013c4cba4a200000c02c9d68847
GigabitEthernet0/6/5/2 10.16.8.6 10 2 ipv4
0013c4cba4a200000c02c9d60800
19693 packets, 1143510 bytes
GigabitEthernet0/6/5/1 10.12.20.2 8 2 mpls
00156358bc6c00000c015cb88847
GigabitEthernet0/6/5/1 10.12.20.2 7 2 ipv4
00156358bc6c00000c015cb80800
19806 packets, 1153348 bytes
GigabitEthernet0/6/5/7 10.12.40.2 9 2 ipv4
00156358bc7200000c07fa5e0800
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
Client dll : libsvii_adj_pd.dll
Client completion function : svii_adj_cmpl_adj
SBC2 point to point 2 2 ipv4
Client dll : libsvii_adj_pd.dll
Client completion function : svii_adj_cmpl_adj
MgmtEth0/4/CPU1/0 (interface) 1 1
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
Client dll : libsvii_adj_pd.dll
Client completion function : svii_adj_cmpl_adj
SBC1 point to point 9 2 ipv4
Client dll : libsvii_adj_pd.dll
Client completion function : svii_adj_cmpl_adj
MgmtEth0/4/CPU0/0 (interface) 1 1
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
Bundle-POS24 point to point 119 2 mpls
mtu: 4470, flags 80000001 0 50000000
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28.1 (src mac only) 149 1 ipv4
000000000000001563c0b0f68100001d0800
mtu: 1500, flags 80000001 0 50000001
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28.2 (src mac only) 148 1 ipv4
000000000000001563c0b0f68100001e0800
mtu: 1500, flags 80000001 0 50000001
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28.3 (src mac only) 147 1 ipv4
000000000000001563c0b0f68100001f0800
mtu: 1500, flags 80000001 0 50000001
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28 (src mac only) 146 1 ipv4
000000000000001563c0b0f60800
mtu: 1500, flags 80000001 0 50000001
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-POS24 (src mac only) 121 1 ipv4
mtu: 4470, flags 80000001 0 50000001
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-POS24 point to point 120 2 ipv4
mtu: 4470, flags 80000001 0 50000000
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
GigabitEthernet0/1/5/1 (src mac only) 13 1 ipv4
000000000000001563c0b0f10800
310470 packets, 27909626 bytes
GigabitEthernet0/1/5/2 (src mac only) 12 1 ipv4
000000000000001563c0b0f20800
310468 packets, 27909354 bytes
Bundle-Ether28.1 (interface) 139 1
flags 80000001 0 50001004
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28.2 (interface) 142 1
flags 80000001 0 50001004
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28.3 (interface) 145 1
flags 80000001 0 50001004
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28 (interface) 136 1
flags 80000001 0 50001004
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-POS24 (interface) 118 1
flags 80000001 0 50001004
10627 packets, 2210404 bytes
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
GigabitEthernet0/1/5/7 (interface) 31 1
31063 packets, 3851812 bytes
GigabitEthernet0/1/5/6 (interface) 30 1
31327 packets, 3863692 bytes
GigabitEthernet0/1/5/5 (interface) 29 1
GigabitEthernet0/1/5/4 (interface) 28 1
GigabitEthernet0/1/5/3 (interface) 27 1
GigabitEthernet0/1/5/2 (interface) 26 1
11579 packets, 2315638 bytes
GigabitEthernet0/1/5/1 (interface) 25 1
17686 packets, 3081588 bytes
GigabitEthernet0/1/5/0 (src mac only) 14 1 ipv4
00000000000000000c00393a0800
GigabitEthernet0/1/5/0 (interface) 24 1
POS0/1/0/0 (interface) 19 1
POS0/1/4/0 (interface) 18 1
134452 packets, 7791702 bytes
POS0/1/4/3 (interface) 7 1
POS0/1/0/2 (interface) 22 1
POS0/1/0/1 point to point 95 2 mpls
POS0/1/0/1 (src mac only) 97 1 ipv4
POS0/1/0/1 point to point 96 2 ipv4
POS0/1/4/2 (src mac only) 110 1 ipv4
POS0/1/4/2 point to point 109 2 ipv4
POS0/1/4/2 (interface) 3 1
191172 packets, 2294213 bytes
POS0/1/0/1 (interface) 21 1
103403 packets, 4243616 bytes
POS0/1/4/1 (interface) 20 1
123823 packets, 5581162 bytes
POS0/1/0/3 (interface) 23 1
GigabitEthernet0/1/5/1 10.14.8.4 56 2 mpls
0012da0b9600001563c0b0f18847
GigabitEthernet0/1/5/1 10.14.8.4 17 2 ipv4
0012da0b9600001563c0b0f10800
35523 packets, 2247965 bytes
GigabitEthernet0/1/5/2 10.16.4.6 54 2 mpls
0013c4cba4a1001563c0b0f28847
GigabitEthernet0/1/5/2 10.16.4.6 15 2 ipv4
0013c4cba4a1001563c0b0f20800
35502 packets, 2244864 bytes
Bundle-Ether28.2 10.12.30.2 152 2 ipv4
00156358b9f6001563c0b0f68100001e0800
mtu: 1500, flags 80000001 0 50000000
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28.3 10.12.31.2 151 2 ipv4
00156358b9f6001563c0b0f68100001f0800
mtu: 1500, flags 80000001 0 50000000
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28 10.12.28.2 150 2 ipv4
00156358b9f6001563c0b0f60800
mtu: 1500, flags 80000001 0 50000000
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28.1 10.12.29.2 153 2 ipv4
00156358b9f6001563c0b0f68100001d0800
mtu: 1500, flags 80000001 0 50000000
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
GigabitEthernet0/1/5/0 10.12.16.2 16 2 ipv4
00156358b9f000000c00393a0800 mtu: 1500, flags 1 0 0
RP/0/RP0/CPU0:router# clear adjacency statistics ipv4
Related Commands
clear cef ipv4 drops
To clear Cisco Express Forwarding (CEF) IPv4 packet drop counters, use the clear cef ipv4 drops command in EXEC mode.
clear cef ipv4 drops {location node-id}
Syntax Description
location node-id |
Clears IPv4 packet drop counters for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command will clear IPv4 CEF drop counters only for the node on which the command is issued.
|
|
basic-services |
read, write |
cef |
read, write |
Examples
The following example displays sample output for the IPv4 Cisco Express Forwarding (CEF) table packet drop counters, and clears IPv4 CEF drop counters for location 0/1/CPU0:
RP/0/RP0/CPU0:router# show cef ipv4 drops
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
RPF suppressed drops packets : 0
RP destined drops packets : 0
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
RPF suppressed drops packets : 0
RP destined drops packets : 0
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
RPF suppressed drops packets : 0
RP destined drops packets : 0
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
RPF suppressed drops packets : 0
RP destined drops packets : 0
RP/0/RP0/CPU0:router# clear cef ipv4 drops location 0/1/CPU0
Clearing CEF Drop Statistics
Related Commands
clear cef ipv4 exceptions
To clear IPv4 Cisco Express Forwarding (CEF) exception packet counters, use the clear cef ipv4 exceptions command in EXEC mode.
clear cef ipv4 exceptions {location node-id}
Syntax Description
location node-id |
Clears IPv4 CEF exception packet counters for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command will clear IPv4 CEF exception packet counters for all nodes.
|
|
basic-services |
read, write |
cef |
read, write |
Examples
The following example displays sample output for the IPv4 Cisco Express Forwarding (CEF) exception packet counters, and clear s IPv4 CEF exception packets node 0/1/CPU0:
RP/0/RP0/CPU0:router# show cef ipv4 exceptions
Broadcast packets : 23648
Broadcast packets : 22656
RP/0/RP0/CPU0:router# clear cef ipv4 exceptions location 0/1/CPU0
Clearing CEF Exception Statistics
Related Commands
clear cef ipv4 interface bgp-policy-statistics
To clear Cisco Express Forwarding (CEF) IPv4 interface Border Gateway Protocol (BGP) policy statistics, use the clear cef ipv4 interface bpg-policy-statistics command in EXEC mode.
clear cef ipv4 interface type interface-path-id bpg-policy-statistics
Syntax Description
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
This command clears the Border Gateway Protocol (BGP) policy accounting counters for the specified interface.
|
|
basic-services |
read, write |
cef |
read, write |
Examples
The following example shows how to clear IPv4 CEF BGP policy statistics:
RP/0/RP0/CPU0:router# clear cef ipv4 interface MgmtEth 0/RP1/CPU0/0 bgp-policy-statistics
Related Commands
clear cef ipv4 interface rpf-statistics
To clear Cisco Express Forwarding (CEF) IPv4 interface unicast reverse path forwarding (RPF) statistics, use the clear cef ipv4 interface rpf-statistics command in EXEC mode.
clear cef ipv4 interface {type instance} rpf-statistics [location node-id]
Syntax Description
type |
Interface type. For more information, use the question mark (?) online help function. |
instance |
Either a physical interface instance or a virtual interface instance as follows: •Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation. –rack: Chassis number of the rack. –slot: Physical slot number of the modular services card or 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. |
location node-id |
(Optional) Clears IPv4 unicast reverse path forwarding (RPF) counters for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.6.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The clear cef ipv4 interface rpf-statistics command clears the unicast reverse path forwarding (RPF) counters for the specified interface.
Examples
The following example shows how to clear IPv4 CEF RPF statistics:
RP/0/RP0/CPU0:router# clear cef ipv4 interface MgmtEth 0/RP1/CPU0/0 rpf-statistics
clear cef ipv6 drops
To clear Cisco Express Forwarding (CEF) IPv6 packet drop counters, use the clear cef ipv6 drop command in EXEC mode.
clear cef ipv6 drops {location node-id}
Syntax Description
location node-id |
Clears IPv6 packet drop counters for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command clears IPv6 CEF drop counters for all nodes.
|
|
basic-services |
read, write |
cef |
read, write |
Examples
The following example displays sample output for the IPv6 Cisco Express Forwarding (CEF) table packet drop counters, and clears IPv6 CEF drop counters for location 0/1/CPU0:
RP/0/RP0/CPU0:router# show cef ipv6 drops
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
RPF suppressed drops packets : 0
RP destined drops packets : 0
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
RPF suppressed drops packets : 0
RP destined drops packets : 0
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
RPF suppressed drops packets : 0
RP destined drops packets : 0
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
RPF suppressed drops packets : 0
RP destined drops packets : 0
RP/0/RP0/CPU0:router# clear cef ipv6 drops location 0/1/CPU0
Clearing CEF Drop Statistics
Related Commands
clear cef ipv6 exceptions
To clear IPv6 Cisco Express Forwarding (CEF) exception packet counters, use the clear cef ipv6 exceptions command in EXEC mode.
clear cef ipv6 exceptions {location node-id}
Syntax Description
location node-id |
Clears IPv6 CEF exception packet counters for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The location keyword was made mandatory. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command clears IPv6 CEF exception packet counters for all nodes.
|
|
basic-services |
read, write |
cef |
read, write |
Examples
The following example displays sample output for the IPv6 Cisco Express Forwarding (CEF) exception packet counters, and clears the IPv6 CEF exception packets for location:
RP/0/RP0/CPU0:router# show cef ipv6 exceptions
RP/0/RP0/CPU0:router# clear cef ipv6 exceptions location 0/1/CPU0
Clearing CEF Exception Statistics
Related Commands
clear cef ipv6 interface bgp-policy-statistics
To clear Cisco Express Forwarding (CEF) IPv6 interface Border Gateway Protocol (BGP) policy statistics, use the clear cef ipv6 interface bpg-policy-statistics command in EXEC mode.
clear cef ipv6 interface type interface-path-id bpg-policy-statistics
Syntax Description
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The clear cef ipv6 interface bgp-policy-statistics command clears the Border Gateway Protocol (BGP) policy accounting counters for the specified interface.
|
|
basic-services |
read, write |
cef |
read, write |
Examples
The following example shows how to clear IPv4 CEF BGP policy statistics:
RP/0/RP0/CPU0:router# clear cef ipv6 interface MgmtEth 0/RP1/CPU0/0 bgp-policy-statistics
clear cef ipv6 interface rpf-statistics
To clear Cisco Express Forwarding (CEF) IPv6 interface reverse path forwarding (RPF) statistics, use the clear cef ipv6 interface rpf-statistics command in EXEC mode.
clear cef ipv6 interface type interface-path-id rpf-statistics [location node-id]
Syntax Description
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
location node-id |
(Optional) Clears IPv6 unicast reverse path forwarding (RPF) counters for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The clear cef ipv6 interface rpf-statistics command clears the unicast reverse path forwarding (RPF) counters for the specified interface.
Examples
The following example shows how to clear IPv4 CEF RPF statistics:
RP/0/RP0/CPU0:router# clear cef ipv6 interface MgmtEth 0/RP1/CPU0/0 rpf-statistics
ipv4 bgp policy accounting
To enable Border Gateway Protocol (BGP) policy accounting, use the ipv4 bgp policy accounting command in interface configuration mode. To disable BGP policy accounting, use the no form of this command.
ipv4 bgp policy accounting {input | output {destination-accounting [source-accounting] | source-accounting [destination-accounting]}}
no ipv4 bgp policy accounting {input | output {destination-accounting [source-accounting] | source-accounting [destination-accounting]}}
Syntax Description
input |
Enables BGP policy accounting policy on the ingress IPv4 unicast interface. |
output |
Enables BGP policy accounting policy on the egress IPv4 unicast interface. |
{destination-accounting [source-accounting] | source-accounting [destination-accounting]} |
When you specify the ingress or egress interface, you must specify one of the following keywords: •destination-accounting—Enables accounting policy on the basis of the destination address. •source-accounting—Enables accounting policy on the basis of the source address. After specifying destination-accounting you can optionally specify source-accounting, or after specifying source-accounting, you can optionally specify destination-accounting. |
Defaults
There is no BGP policy accounting.
Command Modes
Interface configuration
Command History
|
|
Release 3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When you use the no form of the command, accounting is disabled for both the source and destination. To change accounting on either the destination or source address, reconfigure the ipv4 bgp policy accounting command specifying the destination-accounting or source-accounting keyword. In the following example, you want BGP policy accounting disabled on the source address after enabling source and destination address accounting earlier:
RP/0/RP0/CPU0:router(config-if)# ipv4 bgp policy accounting output destination-accounting
See the Cisco IOS XR Routing Configuration Guide for information about configuring a BGP policy. BGP accounting policy is based on community lists, autonomous system numbers, or autonomous system paths.
For BGP policy propagation to function, you must enable BGP.
To specify the accounting policy, the proper route policy configuration must be in place, matching specific BGP attributes using the set traffic-index command. In BGP router configuration mode, use the table-policy command to modify the accounting buckets when the IP routing table is updated with routes learned from BGP. To display accounting policy information, use the show cef ipv4 interface bgp-policy-statistics, show bgp policy, and show route bgp commands.
Examples
The following example shows how to configure BGP policy accounting:
RP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0
RP/0/RP0/CPU0:router(config-if)# ipv4 bgp policy accounting output source-accounting
Related Commands
|
|
route-policy (BGP) |
Defines a route policy. For more information, see Cisco IOS XR Routing Command Reference. |
show bgp policy |
Displays information about BGP advertisements under a proposed policy. For more information, see Cisco IOS XR Routing Command Reference. |
show cef ipv4 interface bgp-policy-statistics |
Displays IPv4 CEF BGP policy statistics. |
show route |
Displays the current routes for BGP in the RIB. For more information, see Cisco IOS XR Routing Command Reference. |
table-policy |
Applies a routing policy to routes being installed into the routing table. For more information, see Cisco IOS XR Routing Command Reference. |
ipv4 bgp policy propagation
To enable QoS Policy Propagation on BGP (QPPB) on an interface, use the ipv4 bgp policy propagation command in interface configuration mode. To disable QoS policy propagation on BGP, use the no form of this command.
ipv4 bgp policy propagation {input} {ip-precedence | qos-group} {destination | source)
no ipv4 bgp policy propagation {input} {ip-precedence | qos-group} {destination | source)
Syntax Description
input |
Enables QPPB on the ingress IPv4 unicast interface. |
ip-precedence |
Specifies that the QoS policy is based on the IP precedence. |
qos-group |
Specifies that the QoS policy is based on the QoS group ID. |
destination |
Specifies that the IP precedence bit or QoS group ID from the destination address entry is used in the route table. |
source |
Specifies that the IP precedence bit or QoS group ID from the source address entry is used in the route table. |
Defaults
The default is disabled.
Command Modes
Interface configuration
Command History
|
|
Release 3.6.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
For the QPPB feature to work, you must enable BGP and CEF. In addition, the proper route-map configuration must be in place to specify the IP precedence or QoS group ID (for example, set precedence command).
If you specify both source and destination on the interface, the software looks up the source address in the routing table and classifies the packet based on the source address first; then the software looks up the destination address in the routing table and reclassifies it based on the destination address.
|
|
ipv4 |
read, write, |
network |
read, write |
Examples
The following example shows how to enable QPPB on the Packet-over-SONET/SDH (POS) interface:
RP/0/RP0/CPU0:router(config)# interface pos 0/1/1/0
RP/0/RP0/CPU0:router(config-if)# ipv4 address 192.3.1.1 255.255.255.252
RP/0/RP0/CPU0:router(config-if)# ipv4 bgp policy propagation input ip-precedence
destination
Related Commands
|
|
route-policy (BGP) |
Defines a route policy. For more information, see Cisco IOS XR Routing Command Reference. |
show bgp policy |
Displays information about BGP advertisements under a proposed policy. For more information, see Cisco IOS XR Routing Command Reference. |
show cef ipv4 interface bgp-policy-statistics |
Displays IPv4 CEF BGP policy statistics. |
show route |
Displays the current routes for BGP in the RIB. For more information, see Cisco IOS XR Routing Command Reference. |
table-policy |
Applies a routing policy to routes being installed into the routing table. For more information, see Cisco IOS XR Routing Command Reference. |
ipv4 verify unicast source reachable-via
To enable IPv4 unicast Reverse Path Forwarding (RPF) checking, use the ipv4 verify unicast source reachable-via command in interface configuration mode. To disable unicast RPF, use the no form of this command.
ipv4 verify unicast source reachable-via {any | rx} [allow-default] [allow-self-ping]
no ipv4 verify unicast source reachable-via {any | rx} [allow-default] [allow-self-ping]
Syntax Description
any |
Enables loose unicast RPF checking. If loose unicast RPF is enabled, a packet is not forwarded unless its source prefix exists in the routing table. |
rx |
Enables strict unicast RPF checking. If strict unicast RPF is enabled, a packet is not forwarded unless its source prefix exists in the routing table and the output interface matches the interface on which the packet was received. |
allow-default |
(Optional) Enables the matching of default routes. This option applies to both loose and strict RPF. |
allow-self-ping |
(Optional) Enables the router to ping out an interface.This option applies to both loose and strict RPF. |
Defaults
IPv4 unicast RPF is disabled.
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The strict option information was added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Use the ipv4 verify unicast source reachable-via interface command to mitigate problems caused by malformed or forged (spoofed) IP source addresses that pass through a router. Malformed or forged source addresses can indicate denial-of-service (DoS) attacks based on source IP address spoofing.
When strict unicast RPF is enabled on an interface, the router examines all packets received on that interface. The router checks to make sure that the source address appears in the routing table and matches the interface on which the packet was received.
When loose unicast RPF is enabled on an interface, the router examines all packets received on that interface. The router checks to make sure that the source address can be reached through any of the router interfaces.
|
|
ipv4 |
read, write, |
network |
read, write |
Examples
The following example shows how to configure strict RPF on POS interface 0/1/0/0:
RP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0
RP/0/RP0/CPU0:router(config-if)# ipv4 verify unicast source reachable-via rx
The following example shows how to configure loose RPF on POS interface 0/0/0/1.
RP/0/RP1/CPU0:ios(config)# interface pos 0/0/0/1
RP/0/RP1/CPU0:ios(config-if)# ipv4 verify unicast source reachable-via any
Related Commands
ipv6 bgp policy accounting
To enable Border Gateway Protocol (BGP) policy accounting, use the ipv6 bgp policy accounting command in interface configuration mode. To disable BGP policy accounting, use the no form of this command.
ipv6 bgp policy accounting {input | output {destination-accounting [source-accounting] | source-accounting [destination-accounting]}}
no ipv6 bgp policy accounting {input | output {destination-accounting [source-accounting] | source-accounting [destination-accounting]}}
Syntax Description
input |
Enables BGP policy accounting policy on the ingress IPv6 unicast interface. |
output |
Enables BGP policy accounting policy on the egress IPv6 unicast interface. |
{destination-accounting [source-accounting] | source-accounting [destination-accounting]} |
When you specify the ingress or egress interface, you must specify one of the following keywords: •destination-accounting—Enables accounting policy on the basis of the destination address. •source-accounting—Enables accounting policy on the basis of the source address. After specifying destination-accounting, you can optionally specify source-accounting or, after specifying source-accounting, you can optionally specify destination-accounting. |
Defaults
There is no BGP policy accounting.
Command Modes
Interface configuration
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When you use the no form of the command, accounting is disabled for both the source and destination. To change accounting on either the destination or source address, reconfigure the ipv6 bgp policy accounting command, specifying the destination-accounting or source-accounting keyword. In the following example, you want BGP policy accounting disabled on the source address after enabling source and destination address accounting earlier:
RP/0/RP0/CPU0:router(config-if)# ipv6 bgp policy accounting output destination-accounting
See the Cisco IOS XR Routing Configuration Guide for information about configuring a BGP policy. BGP accounting policy is based on community lists, autonomous system numbers, or autonomous system paths.
For BGP policy propagation to function, you must enable BGP.
To specify the accounting policy, the proper route policy configuration must be in place matching specific BGP attributes using the set traffic-index command. In BGP router configuration mode, use the table-policy command to modify the accounting buckets when the IP routing table is updated with routes learned from BGP. To display accounting policy information, use the show cef ipv4 interface bgp-policy-statistics, show bgp policy, and show ip route bgp commands.
Examples
The following example shows how to configure BGP policy accounting:
RP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0
RP/0/RP0/CPU0:router(config-if)# ipv6 bgp policy accounting output source-accounting
Related Commands
|
|
route-policy (BGP) |
Defines a route policy. For more information, see Cisco IOS XR Routing Command Reference. |
show bgp policy |
Displays information about BGP advertisements under a proposed policy. For more information, see Cisco IOS XR Routing Command Reference. |
show cef ipv6 interface bgp-policy-statistics |
Displays IPv6 CEF BGP policy statistics. |
show route |
Displays the current routes for BGP in the RIB. For more information, see Cisco IOS XR Routing Command Reference. |
table-policy |
Applies a routing policy to routes being installed into the routing table. For more information, see Cisco IOS XR Routing Command Reference. |
ipv6 verify unicast source reachable-via
To enable IPv6 unicast Reverse Path Forwarding (RPF) checking, use the ipv6 verify unicast source reachable-via command in interface configuration mode. To disable IPv6 unicast RPF checking, use the no form of this command.
ipv6 verify unicast source reachable-via {any | rx} [allow-default] [allow-self-ping]
no ipv6 verify unicast source reachable-via {any | rx} [allow-default] [allow-self-ping]
Syntax Description
any |
Enables loose unicast RPF checking. If loose unicast RPF is enabled, a packet is not forwarded unless its source prefix exists in the routing table. |
rx |
Enables strict unicast RPF checking. If strict unicast RPF is enabled, a packet is not forwarded unless its source prefix exists in the routing table and the output interface matches the interface on which the packet was received. |
allow-default |
(Optional) Enables the matching of default routes. This option applies to both loose and strict RPF. |
allow-self-ping |
(Optional) Enables the router to ping out an interface.This option applies to both loose and strict RPF. |
Defaults
Loose IPv6 unicast RPF is disabled.
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The keywords any, rx, allow-default, and allow-self-ping were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
|
|
network |
read, write |
ipv6 |
read, write |
Examples
The following example shows how to enable loose RPF checking on POS interface 0/1/0/0:
RP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0
RP/0/RP0/CPU0:router(config-if)# ipv6 verify unicast source reachable-via any
Related Commands
rp mgmtethernet forwarding
To enable switching from the line card to the route processor Management Ethernet interfaces, use the rp mgmtethernet forwarding command in global configuration mode. To disable switching from the modular services card to the route processor Management Ethernet interfaces, use the no form of this command.
rp mgmtethernet forwarding
no rp mgmtethernet forwarding
Syntax Description
This command has no arguments or keywords.
Defaults
Switching is disabled.
Command Modes
Global configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
This command is not supported on the Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Note If enabled, the RP CPU is used to forward packets because the RP does not have a packet processing engine like the line cards.
Examples
The following example shows how to enable switching from the modular services card to the RP Management Ethernet interfaces:
RP/0/RP0/CPU0:router(config)# rp mgmtethernet forwarding
show adjacency
To display Cisco Express Forwarding (CEF) adjacency table information, use the show adjacency command in EXEC mode.
show adjacency [ipv4 [nexthop ipv4-address] | mpls | ipv6] [interface-type interface-instance] [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. |
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. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
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.
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
POS0/0/1/2 (src mac only) 6 1 ipv4
POS0/0/1/2 point to point 7 100004
POS0/0/1/2 (interface) 3 1
The following is sample output from the show adjacency command with the detail and location keywords specified:
RP/0/RP0/CPU0:router# show adjacency ipv4 POS 0/0/0/2 detail location 0/0/CPU0
Interface Address Version Refcount Protocol
POS0/0/0/2 point to point 7 100004 ipv4
mtu: 4470, flags 0 0 40000000
The following is sample output from the show adjacency ipv4 nexthop command with the detail and location keywords specified:
RP/0/RP0/CPU0:router: show adjacency ipv4 nexthop 10.10.10.1 detail location 0/3/CPU0
Interface Address Version Refcount Protocol
POS0/3/1/0 10.10.10.1 11 6 ipv4
000c86f33d330800453a21c10800
mtu: 1500, flags 0 0 40000000
Table 9 describes the significant fields shown in the display.
Table 9 show adjacency Field Descriptions
|
|
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 MTU1 . |
flags |
Internal field. |
packets |
Number of packets going through the adjacency. |
bytes |
Number of bytes going through the adjacency. |
Related Commands
show cef
To display information about packets forwarded by Cisco Express Forwarding (CEF), use the show cef command in EXEC mode.
show cef [prefix [mask]] [hardware {egress | ingress} | detail] [location {node-id | all}]
Syntax Description
prefix |
(Optional) Longest matching CEF entry for the specified IPv4 destination prefix. |
mask |
(Optional) Exact CEF entry for the specified IPv4 prefix and mask. |
hardware |
(Optional) Displays detailed information about hardware. |
egress |
Displays information from the egress packet switch exchange (PSE) file. |
ingress |
Displays information from the ingress packet switch exchange (PSE) file. |
detail |
(Optional) Displays full details. |
location node-id |
(Optional) Displays detailed CEF information for the designated node. The node-id argument is entered in the rack/slot/module notation. |
all |
(Optional) Displays all locations. |
Defaults
When the prefix is not explicitly specified, this command displays all the IPv4 prefixes that are present in CEF. When not specified, the location defaults to the active Route Processor (RP) node.
Command Modes
EXEC
Command History
|
|
Release 3.6.0 |
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following sample output shows the load information flag from the show cef command for both hardware and ingress keywords:
RP/0/RP0/CPU0:router# show cef 1.1.3.0/24 hardware ingress location 0/3/CPU0
1.1.3.0/24, version 0, internal 0x40000001 (0x598491e8) [1], 0x0 (0x0),
local adjacency 10.0.101.2
Prefix Len 24, traffic index 0, precedence routine (0)
BGP Attribute: id: 8, Local id: 6, Origin AS: 1003, Next Hop AS: 4
via 10.0.101.2, 2 dependencies, recursive
next hop 10.0.101.2 via 10.0.101.2/32
Mnode 0 HW Location: 0x00080404 HW Value
[ 0x0081a600 00000000 00000000 00000000 ]
Leaf Mnode 1 HW Location: 0x040d3030
Hardware Leaf: PLU Leaf Value
[ 0x8000d800 028842c6 00000000 1fff2000 ]
FCR 2 TLU Address 0x00210b19 TI 0 AS 6
************* IGP LoadInfo *****************
PBTS Loadinfo Attached: No
LI Path [ 0] HFA Info: 0x10204028 FCR: 4
********************************************
------------------------------------------------
HW Rx Adjacency 0 Detail:
------------------------------------------------
Rx Adj HW Address 0x02040280 (ADJ)
HFA Bits 0x80 gp 16 mtu 9248 (Fabric MTU) TAG length 0
OI 0x409 (Tx uidb 0 PPindex 1033)
OutputQ 0 Output-port 0x0 local-outputq 0x8000
[ 0x80181040 00002420 00000409 00008000 ]
[ 0x00000000 00000000 00000000 00000000 ]
[ 0x00000000 00000000 00000000 00000000 ]
The following sample output shows the load information flag from the show cef command for both hardware and egress keywords from the Cisco CRS-1:
RP/0/RP0/CPU0:router# show cef 1.53.0.0/16 hardware egress detail location 0/2/cpu0
1.53.0.0/16, version 0, attached, connected, internal 0xc0000c01 (0x7d2faaf0) [3], 0x0
(0x7c0d6a64), 0x0 (0x0)
remote adjacency to MgmtEth0/RP0/CPU0/0
Prefix Len 16, traffic index 0, precedence routine (0)
gateway array (0x0) reference count 1, flags 0x0, source 3,
[0 type 3 flags 0x101000 (0x7d1b466c) ext 0x0 (0x0)]
LW-LDI[type=3, refc=1, ptr=0x7c0d6a64, sh-ldi=0x7d1b466c]
via MgmtEth0/RP0/CPU0/0, 0 dependencies, weight 0, class 0
SW: 0x04000000 00010010 00000000 00459400
HW: 0x04000000 00010010 00000000 00459400
entry_type: FWD vpn key: 0x00000000
num entries: 1 next ptr: 0x00004594
SW: 0x00000001 00010400 00000000 00000100
HW: 0x00000001 00010400 00000000 00000100
Recursive next-hop: 0.0.0.0
Load distribution: 0 (refcount 0)
Hash OK Interface Address
0 Y MgmtEth0/RP0/CPU0/0 remote
If both the QoS group and IP precedence are set for a prefix, both values are printed. If only one of them is set, only one is printed. The following sample output is set for both the QoS group and IP precedence:
RP/0/RP0/CPU0:router# show cef 55.55.55.0
55.55.55.0/24, version 0, internal 0x40000001[1] 0x0, (0x0) local adjacency point2point
Prefix Len 24, traffic index 0, precedence routine (0) QoS Group: 20, IP Precedence: 3
via 56.56.56.1, 0 dependencies, recursive
next hop 56.56.56.1 via 56.56.56.0/24
The following sample output is set for a QoS group:
RP/0/RP0/CPU0:router# show cef 55.55.55.0
55.55.55.0/24, version 0, internal 0x40000001[1] 0x0, (0x0) local adjacency point2point
Prefix Len 24, traffic index 0, precedence routine (0) QoS Group: 20
via 56.56.56.1, 0 dependencies, recursive
next hop 56.56.56.1 via 56.56.56.0/24
The following sample output is set for an IP precedence:
RP/0/RP0/CPU0:router# show cef 55.55.55.0
55.55.55.0/24, version 0, internal 0x40000001[1] 0x0, (0x0) local adjacency point2point
Prefix Len 24, traffic index 0, precedence routine (0) IP Precedence: 3
via 56.56.56.1, 0 dependencies, recursive
next hop 56.56.56.1 via 56.56.56.0/24
show cef bgp-attribute
To display Border Gateway Protocol (BGP) attributes for Cisco Express Forwarding (CEF), use the show cef bgp-attribute command in EXEC mode.
show cef bgp-attribute [attribute-id index-id] [local-attribute-id index-id] [location node-id]
Syntax Description
attribute-id index-id |
(Optional) Displays FIB attribute index. |
local-attribute-id index-id |
(Optional) Displays FIB local attribute index. |
location node-id |
(Optional) Displays BGP information for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
The default location is active RP.
Command Modes
EXEC
Command History
|
|
Release 3.7.0 |
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to use the show cef bgp-attribute command:
RP/0/5/CPU0:router# show cef bgp-attribute
Total number of entries: 75742
BGP Attribute ID: 0x2058a, Local Attribute ID: 0x1
Origin AS: 195, Next Hop AS: 195
BGP Attribute ID: 0x20583, Local Attribute ID: 0x2
Origin AS: 22, Next Hop AS: 22
BGP Attribute ID: 0x20582, Local Attribute ID: 0x3
Origin AS: 21, Next Hop AS: 21
BGP Attribute ID: 0x20585, Local Attribute ID: 0x4
Origin AS: 28, Next Hop AS: 28
BGP Attribute ID: 0x20584, Local Attribute ID: 0x5
Origin AS: 27, Next Hop AS: 27
BGP Attribute ID: 0x2057f, Local Attribute ID: 0x6
Origin AS: 86, Next Hop AS: 86
BGP Attribute ID: 0x2058b, Local Attribute ID: 0x7
Origin AS: 196, Next Hop AS: 196
BGP Attribute ID: 0x20589, Local Attribute ID: 0x8
Origin AS: 194, Next Hop AS: 194
Table 10 describes the significant fields shown in the display.
Table 10 show cef bgp-attribute Command Field Descriptions
|
|
BGP Attribute ID |
Displays the id assigned by BGP. |
Local Attribute ID |
Displays the id assigned by FIB. |
Origin AS |
Displays the origin AS of the prefix that carries this attribute id. |
Next Hop AS |
Displays the AS that contains the BGP nexthop for this prefix. |
Related Commands
|
|
show cef |
Displays information about packets forwarded by Cisco Express Forwarding (CEF). |
show cef external
To display Cisco Express Forwarding (CEF) external client dependency information, use the show cef external command in EXEC mode.
show cef external [hardware {ingress | egress}] [prefix] {ifhandle | tunnel-id | client-name} {6vpe | 6pe-ipvpn | eos0-ldi | ip-reachability} [detail] [location node-id]
Syntax Description
hardware |
(Optional) Displays hardware information. |
ingress |
Displays hardware information programmed in ingress packet forwarding hardware. |
egress |
Displays hardware information programmed in egress packet forwarding hardware. |
prefix |
(Optional) Displays external client information for a specific prefix. |
ifhandle |
Specifies interface handle. |
tunnel-id |
Specifies the tunnel identifier. |
client-name |
Name of a particular client. The dependency information for the given client name is displayed. |
6vpe |
Displays 6VPE (IPv6 VPN Provide Edge) dependency information. |
6vpe-ipvpn |
Displays 6VPE over IP-VPN dependency information. |
eos0-ldi |
Displays Multiprotocol Label Switching (MPLS) end of stack 0 (EOS0) load balancing dependency information. |
ip-reachability |
Displays Internet Protocol (IP) reachability information. |
detail |
Displays the dependency information in detail. |
location node-id |
Displays external client dependency information for the specified node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.5.0 |
This command was enhanced to show 6VPE external client dependency. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following sample output is from the show cef external command:
RP/0/8/CPU0:router# show cef external detail
Interest type : IP reachability notify
Prefix : 123.123.123.123/32
Interest type : EOS0 LDI updates
Prefix : 122.122.122.122/32
Load distribution: 0 (refcount 0)
Hash OK Interface Address
Interest type : 6VPE MPLS nexthop reachability
Load distribution: 0 1 (refcount 0)
Hash OK Interface Address
Related Commands
|
|
show cef |
Displays information about packets forwarded by Cisco Express Forwarding (CEF). |
show cef recursive-nexthop
To display Cisco Express Forwarding (CEF) recursive next-hop information, use the show cef recursive-nexthop command in EXEC mode.
show cef recursive-nexthop [hardware] [location node-id]
Syntax Description
hardware |
(Optional) Displays hardware information related to the recursive next hop. |
location node-id |
(Optional) Displays recursive next-hop information for the specified node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.5.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following sample output is from the show cef recursive-nexthop command:
RP/0/0/CPU0:router# sh cef recursive-nexthop
Recursive nexthop database:
Recursive nexthop is resolved
Resolving route is 50.1.1.1/32
* Tunnel endpoint, tunnel id 1, flags 0x3, ref count 5
Tunnel endpoint is resolved
Tunnel Encap - ifhandle=0x6000180, type=L2TPv3, Params=[Session-id=0x15994B8A,
Cookielen=8, Cookie=0x816F92F069D17173]
Number of recursive nexthops: 1
Resolved recursive nexthops: 1
Unresolved recursive nexthops: 0
Recursive nexthops not tracked: 0
Number of tunnel endpoints: 1
Number of resolved tunnel endpoints: 1
Number of unresolved tunnel endpoints: 0
RP/0/0/CPU0:12406-PE3-MTBF#
RP/0/0/CPU0:12406-PE3-MTBF#sh cef recursive-nexthop hardware
Recursive nexthop database:
Recursive nexthop is resolved
Resolving route is 50.1.1.1/32
* Tunnel endpoint, tunnel id 1, flags 0x3, ref count 5
Tunnel endpoint is resolved
Tunnel Encap - ifhandle=0x6000180, type=L2TPv3, Params=[Session-id=0x15994B8A,
Cookielen=8, Cookie=0x816F92F069D17173]
Number of recursive nexthops: 1
Resolved recursive nexthops: 1
Unresolved recursive nexthops: 0
Recursive nexthops not tracked: 0
Number of tunnel endpoints: 1
Number of resolved tunnel endpoints: 1
Number of unresolved tunnel endpoints: 0
Related Commands
|
|
show cef |
Displays information about packets forwarded by Cisco Express Forwarding (CEF). |
show cef summary
To display summary information for the Cisco Express Forwarding (CEF) table, use the show cef summary command in EXEC mode.
show cef summary [location {node-id | all}]
Syntax Description
location node-id |
(Optional) Displays detailed CEF information for the designated node. The node-id argument is entered in the rack/slot/module notation. |
all |
(Optional) Displays all locations. |
Defaults
The show cef summary command assumes the IPv4 CEF table and the active RP node as the location.
Command Modes
EXEC
Command History
|
|
Release 3.6.0 |
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following sample output is from the show cef summary command for the Cisco CRS-1:
RP/0/RP0/CPU0:router# show cef summary location 0/1/CPU0
IP CEF with switching (Table Version 0) for node0_1_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 318
170 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 12240 bytes
183 load sharing elements, 57292 bytes, 184 references
19 shared load sharing elements, 7036 bytes
164 exclusive load sharing elements, 50256 bytes
0 CEF route update drops, 10 revisions of existing leaves
0 prefixes modified in place
21 prefixes with label imposition, 60 prefixes with label information
Adjacency Table has 49 adjacencies
25 incomplete adjacencies
Table 11 describes the significant fields shown in the display.
Table 11 show cef summary Field Descriptions
|
|
Load balancing |
Current load-balancing mode that is configured using the cef load-balancing fields command. The default value is L3. |
Table Version |
Version of the CEF table. |
tableid |
Table identification number. |
vrfname |
VRF name. |
flags |
Option value for the table |
routes |
Total number of routes. |
reresolve |
Total number of routes being reresolved. |
unresolved (x old, x new) |
Number of routes not yet resolved. |
load sharing elements |
Total number of internal load-sharing data structures. |
bytes |
Total memory used by internal load sharing data structures. |
references |
Total reference count of all internal load sharing data structures. |
CEF resets |
Number of CEF table resets. |
revisions of existing leaves |
Number of updates to existing prefixes. |
Exponential (currently xs, peak xs) |
Currently not used. |
prefixes modified in place |
Prefixes modified in place. |
Adjacency Table has x adjacencies |
Total number of adjacencies. |
x incomplete adjacency |
Total number of incomplete adjacencies. |
Related Commands
|
|
cef load-balancing fields |
Selects the hashing algorithm that is used for load balancing during forwarding. |
show cef |
Displays information about packets forwarded by Cisco Express Forwarding (CEF). |
show cef ipv4
To display the IPv4 Cisco Express Forwarding (CEF) table, use the show cef ipv4 command in EXEC mode.
show cef [vrf vrf-name] ipv4 [prefix [mask] | interface-type interface-instance] [detail] [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
prefix |
(Optional) Longest matching CEF entry for the specified IPv4 destination prefix. |
mask |
(Optional) Exact CEF entry for the specified IPv4 prefix and mask. |
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. |
detail |
(Optional) Displays full CEF entry information. |
location node-id |
(Optional) Displays the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
If the location is not specified, the command defaults to the active RP node.
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
The sample output for the detail keyword is modified for a specific prefix. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays the CEF table on the node in which the command is issued. Otherwise, the command is effective on the node specified by the location node-id keyword and argument.
Examples
The following sample output is from the show cef ipv4 command:
RP/0/RP0/CPU0:router# show cef ipv4
Prefix Next Hop Interface
0.0.0.0/0 12.25.0.1 MgmtEth0/RP1/CPU0/0
12.25.0.0/16 attached MgmtEth0/RP1/CPU0/0
12.25.12.10/32 receive MgmtEth0/RP1/CPU0/0
12.25.13.12/32 12.25.13.12 MgmtEth0/RP1/CPU0/0
12.25.16.11/32 12.25.16.11 MgmtEth0/RP1/CPU0/0
12.25.22.10/32 12.25.22.10 MgmtEth0/RP1/CPU0/0
12.25.26.10/32 12.25.26.10 MgmtEth0/RP1/CPU0/0
12.25.41.2/32 12.25.41.2 MgmtEth0/RP1/CPU0/0
12.25.41.5/32 12.25.41.5 MgmtEth0/RP1/CPU0/0
12.25.42.5/32 12.25.42.5 MgmtEth0/RP1/CPU0/0
12.25.44.15/32 12.25.44.15 MgmtEth0/RP1/CPU0/0
12.25.55.2/32 12.25.55.2 MgmtEth0/RP1/CPU0/0
12.25.255.255/32 12.25.255.255 MgmtEth0/RP1/CPU0/0
255.255.255.255/32 broadcast
Table 12 describes the significant fields shown in the display.
Table 12 show cef ipv4 Field Descriptions
|
|
Prefix |
Prefix in the IPv4 CEF table. |
Next Hop |
Next hop of the prefix. |
Interface |
Interface associated with the prefix. |
The following sample output is from the show cef ipv4 command for the detail keyword, 10.10.10.0/24 as the IPv4 prefix mask, and the location is 0/3/CPU0:
RP/0/RP0/CPU0:router# show cef ipv4 10.10.10.0/24 detail location 0/3/CPU0
10.10.10.0/24, version 0, attached, connected, internal 0x40000c01[2] 0x0, (0x59a4fd4c)
local adjacency point2point
Prefix Len 24, traffic index 0, precedence routine (0)
gateway array reference count 1, flags 0x0, source 3, [0, type 3 flags 0x101000,
(0x5990efc4)]
via POS0/2/0/0, 0 dependencies, class 0, weight 0
Load distribution: 0 (refcount 0)
Hash OK Interface Address
0 Y POS0/2/0/0 point2point
show cef ipv4 adjacency
To display Cisco Express Forwarding (CEF) IPv4 adjacency status and configuration information, use the show cef ipv4 adjacency command in EXEC mode.
show cef [vrf vrf-name] ipv4 adjacency [interface-type interface-instance] [location node-id] [detail] [discard] [glean] [null] [punt] [remote] [protected]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
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. |
location node-id |
(Optional) Displays detailed CEF information for the designated node. The node-id argument is entered in the rack/slot/module notation. |
detail |
(Optional) Displays the detailed adjacency information. |
discard |
(Optional) Filters out and displays only the discarded adjacency information. |
glean |
(Optional) Filters out and displays only the glean adjacency information. |
null |
(Optional) Filters out and displays only the adjacency information. |
punt |
(Optional) Filters out and displays only the punt adjacency information. |
remote |
(Optional) Filters out and displays only the remote adjacency information. |
protected |
(Optional) Filters out and displays only the IP-Fast Reroute (FRR) protected adjacency information. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
The protected keyword was added on the Cisco CRS-1 and Cisco XR 12000 Series Router to support IP-FRR. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, the show cef ipv4 adjacency command displays the CEF adjacency table for the node on which the command is issued.
Examples
The following sample output is from show cef ipv4 adjacency command for the Cisco CRS-1:
RP/0/RP1/CPU0:ios# show cef ipv4 adjacency MgmtEth 0/RP1/CPU0/0
Interface Address Type Refcount
Mg0/RP1/CPU0/0Prefix: 12.25.0.3/32 local 2
Adjacency: PT:0x782a2900 12.25.0.3/32
Interface: Mg0/RP1/CPU0/0
MAC: 00.d0.02.75.ab.fd.00.11.93.ef.e3.50.08.00
Interface Type: 0x8, Base Flags: 0x1
Dependent adj type: remote
Dependent adj intf: Mg0/RP1/CPU0/0
Mg0/RP1/CPU0/0Prefix: 0.24.0.32/32 remote 6
Interface: Mg0/RP1/CPU0/0
Interface Type: 0x8, Base Flags: 0x0
Table 13 describes the significant fields shown in the display.
Table 13 show cef ipv4 adjacency Field Descriptions
|
|
Interface |
Interface associated with the prefix. |
Address |
Prefix address information. |
Type |
Type of adjacency, can be either local or remote. |
Refcount |
Number of times the adjacency is referenced by other routers. |
show cef ipv4 adjacency hardware
To display Cisco Express Forwarding (CEF) IPv4 adjacency hardware status and configuration information, use the show cef ipv4 adjacency hardware command in EXEC mode.
show cef [vrf vrf-name] ipv4 adjacency hardware {egress | ingress} [detail | discard | drop | glean | location node-id | null | punt | protected | remote]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
egress |
Displays information from the egress packet switch exchange (PSE) file. |
ingress |
Displays information from the ingress packet switch exchange (PSE) file. |
detail |
(Optional) Displays full details. |
discard |
(Optional) Displays the discard adjacency information. |
drop |
(Optional) Displays the drop adjacency information. |
glean |
(Optional) Displays the glean adjacency 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. |
null |
(Optional) Displays the null adjacency information. |
punt |
(Optional) Displays the punt adjacency information. |
protected |
(Optional) Filters out and displays only the IP-Fast Reroute (FRR) protected adjacency information. |
remote |
(Optional) Displays the remote adjacency information. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
The following enhancements were added: •The TE flag value was added to the sample output for both ingress and egress keywords to display the load information flag. •The protected keyword was added for IP-FRR. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following sample output shows the load information flag from the show cef ipv4 adjacency hardware command for the ingress keyword on the Cisco CRS-1:
RP/0/RP0/CPU0:router# show cef ipv4 adjacency hardware ingress detail location 0/2/CPU0
Interface Address Type Refcount
tt0 Prefix: 0.0.0.0/32 local 5
Interface Type: 0x24, Base Flags: 0x2001
Dependent adj type: remote
[HW: 0x01000000 0x00000000 0x00000000 0x00040200]
[HW: 0x00000000 0x08402000 0x01280040 0x00020000]
Interface: Te0/2/0/1 Type: glean
Interface Type: 0x1e, Base Flags: 0x4400
Dependent adj type: remote
Dependent adj intf: Te0/2/0/1
[HW: 0x01000000 0x00000000 0x00000000 0x00040200]
[HW: 0x00000000 0x08402000 0x01280040 0x00020000]
Te0/2/0/1 Prefix: 110.2.6.1/32 local 6
Adjacency: PT:0x7d716a30 110.2.6.1/32
MAC: 00.13.c4.8f.88.0b.00.13.c3.93.96.07.08.00
Interface Type: 0x1e, Base Flags: 0x1
Dependent adj type: remote
Dependent adj intf: Te0/2/0/1
[HW: 0x01000000 0x00000000 0x00000000 0x00040200]
[HW: 0x00000000 0x08402000 0x01280040 0x00020000]
The following sample output shows the load information flag from the show cef ipv4 adjacency hardware command for the egress keyword:
RP/0/RP0/CPU0:router# show cef ipv4 adjacency hardware egress detail location 0/2/CPU0
Interface Address Type Refcount
tt0 Prefix: 0.0.0.0/32 local 5
Interface Type: 0x24, Base Flags: 0x2001
Dependent adj type: remote
[HW: 0x00000001 0x20020000 0x08000000 0x00080000]
encapsulation : unknown (0x8000000)
[HW: 0x00000080 0x0013c48f 0x880b05ea 0x00580000]
Interface: Te0/2/0/1 Type: glean
Interface Type: 0x1e, Base Flags: 0x4400
Dependent adj type: remote
Dependent adj intf: Te0/2/0/1
Table 14 describes the significant fields shown in the display.
Table 14 show cef ipv4 adjacency hardware Field Descriptions
|
|
Interface |
Interface associated with the prefix. |
Address |
Prefix address information. |
Type |
Type of adjacency, can be either local or remote. |
Refcount |
Number of times the adjacency is referenced by other routers. |
show cef ipv4 drops
To display IPv4 Cisco Express Forwarding (CEF) table packet drop counters, use the show cef ipv4 drops command in EXEC mode.
show cef [vrf vrf-name] ipv4 drops [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
location node-id |
(Optional) Displays IPv4 CEF table packet drop counters for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
A packet might be dropped from the IPv4 CEF table because of unresolved CEF entries, unsupported features, absence of route information, absence of adjacency information, or an IP checksum error.
If you do not specify a node with the location keyword and node-id argument, this command displays IPv4 CEF packet drop counters for all nodes.
Examples
The following is sample output from the show cef ipv4 drops for location command:
RP/0/RP0/CPU0:router# show cef ipv4 drops
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
RPF suppressed drops packets : 0
RP destined drops packets : 0
Table 15 describes the significant fields shown in the display.
Table 15 show cef ipv4 drop Field Descriptions
|
|
Unresolved drops |
Drops due to unresolved routes. |
Unsupported drops |
Drops due to an unsupported feature. |
No route drops |
Number of packets dropped because there were no routes to the destination. |
No Adjacency drops |
Number of packets dropped because there were no adjacencies established. |
Checksum error drops |
Drops due to IPv4 checksum error. |
RPF drops |
Drops due to IPv4 unicast RPF1 . |
RPF suppressed drops |
Drops suppressed due to IPv4 unicast RPF. |
RP destined drops |
Drops destined for the router. |
Related Commands
show cef ipv4 exact-route
To display an IPv4 Cisco Express Forwarding (CEF) exact route, use the show cef ipv4 exact-route command in EXEC mode.
show cef [vrf vrf-name] ipv4 exact-route {source-address destination-address} [protocol protocol name] [source-port source-port] [destination-port destination-port] [ingress-interface type interface-path-id] [policy-class value] [detail | location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
source-address |
The IPv4 source address in x.x.x.x format. |
destination-address |
The IPv4 destination address in x.x.x.x format. |
protocol protocol name |
(Optional) Displays the specified protocol for the route. |
source-port source-port |
(Optional) Sets the UDP source port. The range is from 0 to 65535. |
destination-port destination-port |
(Optional) Sets the UDP destination port. The range is from 0 to 65535. |
ingress-interface |
(Optional) Sets the ingress interface. |
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
policy-class value |
(Optional) Displays the class for the policy-based tunnel selection. The range for the tunnel policy class value is from 1 to 7. |
detail |
(Optional) Displays full CEF entry information. |
location node-id |
(Optional) Displays the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
The following keywords were added so that the Layer 4 information can be specified for the exact route: •protocol •source-port •destination-port •ingress-interface The policy-class keyword was added to tunnel policy. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If the Layer 4 information is enabled, the source-port, destination-port, protocol, and ingress-interface fields are required. Otherwise, the output of the show cef ipv4 exact-route command is not correct.
Examples
The following sample output is from the show cef ipv4 exact-route command:
RP/0/RP0/CPU0:router# show cef ipv4 exact-route 10.1.1.1 10.1.1.2 detail
0.0.0.0/0, version 432, proxy default, internal 0x2000201[1]
Prefix Len 0, traffic index 0, precedence routine (0)
Table 16 describes the significant fields shown in the display.
Table 16 show cef ipv4 exact-route Field Descriptions
|
|
Prefix |
Prefix in the IPv4 CEF table. |
Next Hop |
Next hop of the prefix |
Interface |
Interface associated with the prefix |
The following sample output shows the exact route for the Layer 4 information:
RP/0/RP0/CPU0:router# show cef ipv4 exact-route 20.6.1.9 22.6.1.9 protocol udp source-port
1 destination-port 1 ingress-interface GigabitEthernet 0/1/0/4
22.6.1.9/32 version 0, internal 0x40040001 (0x78439fd0) [3], 0x0 (0x78aaf928), 0x4400
(0x78ed62d0)
remote adjacency to POS0/1/4/4
Prefix Len 32, traffic index 0, precedence routine (0)
Related Commands
|
|
bundle-hash |
Displays the path a bundle flow that comprises a source and destination address would take. For more information, see Cisco IOS XR Interface and Hardware Component Command Reference. |
cef load-balancing fields |
Selects the hashing algorithm that is used for load balancing when forwarding. |
show mpls forwarding exact-route |
Displays the path an MPLS flow that comprises a source and destination address would take. For more information, see Cisco IOS XR Multiprotocol Label Switching Command Reference. |
show cef ipv4 exceptions
To display IPv4 Cisco Express Forwarding (CEF) exception packet counters, use the show cef ipv4 exceptions command in EXEC mode.
show cef [vrf vrf-name] ipv4 exceptions [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
location node-id |
(Optional) Displays CEF exception packet counters for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
CEF exception packets are those packets that have been sent from the hardware to the software because they require additional handling. The types of IPv4 CEF exception packets are displayed in the command's output and are defined.
If you do not specify a node with the location keyword and node-id argument, this command displays IPv4 CEF exception packet counters on all nodes.
Examples
The following is sample output from the show cef ipv4 exceptions command:
RP/0/RP0/CPU0:router# show cef ipv4 exceptions
Redirect packets : 0 Receive packets : 0
TTL expired packets : 314
Table 17 describes the significant fields shown in the display.
Table 17 show cef ipv4 exceptions Field Descriptions
|
|
Slow encap |
Number of packets requiring special processing during encapsulation. |
Redirect |
Number of ICMP1 redirect messages sent. |
Receive |
Number of packets destined to the router. |
Broadcast |
Number of broadcasts received. |
IP options |
Number of IP option packets. |
TTL expired |
Number of packets with expired TTLs2 . |
Fragmented |
Number of packets that have been fragmented. |
Related Commands
show cef ipv4 hardware
To display Cisco Express Forwarding (CEF) IPv4 hardware status and configuration information, use the show cef ipv4 hardware command in EXEC mode.
show cef [vrf vrf-name] ipv4 hardware {egress | ingress [detail | location node-id]}
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
egress |
Displays information from the egress packet switch exchange (PSE) file. |
ingress |
Displays information from the ingress packet switch exchange (PSE) file. |
detail |
(Optional) Displays full details. |
location node-id |
(Optional) Displays detailed CEF information for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show cef ipv4 hardware egress command:
RP/0/RP0/CPU0:router# show cef ipv4 hardware egress
Prefix Next Hop Interface
0.0.0.0/0 172.29.52.1 <recursive>
10.1.1.1/32 receive Loopback0
10.2.2.2/32 10.12.24.2 Bundle-POS24
10.6.6.6/32 10.16.8.6 GigabitEthernet0/6/5/2
10.7.7.7/32 10.12.24.2 Bundle-POS24
10.11.11.11/32 10.12.8.2 POS0/1/0/1
10.12.4.0/24 attached POS0/6/4/5
10.12.4.0/32 broadcast POS0/6/4/5
10.12.4.1/32 receive POS0/6/4/5
10.12.4.255/32 broadcast POS0/6/4/5
10.12.8.0/24 attached POS0/1/0/1
10.12.8.0/32 broadcast POS0/1/0/1
10.12.8.1/32 receive POS0/1/0/1
10.12.8.255/32 broadcast POS0/1/0/1
10.12.12.0/24 attached POS0/6/0/1
Table 18 describes the significant fields shown in the display.
Table 18 show cef ipv4 hardware egress Field Descriptions
|
|
Prefix |
Nonrecursive prefixes detected on the node. |
Next Hop |
Routing next hop. |
Interface |
Interface associated with the nonrecursive prefix. |
show cef ipv4 interface
To display IPv4 Cisco Express Forwarding (CEF)-related information for an interface, use the show cef ipv4 interface command in EXEC mode.
show cef [vrf vrf-name] ipv4 interface {type instance} [detail] [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
type |
Interface type. For more information, use the question mark (?) online help function. |
instance |
Either a physical interface instance or a virtual interface instance as follows: •Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation. –rack: Chassis number of the rack. –slot: Physical slot number of the modular services card or 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. |
detail |
(Optional) Displays detailed CEF information for all the interfaces on the node in which the command is issued. |
location node-id |
(Optional) Displays IPv4 CEF-related information for an interface. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, the show cef ipv4 interface rpf-statistics command displays the CEF-related information for the interface on the route processor.
Examples
The following is sample output from the show cef ipv4 interface command:
RP/0/RP0/CPU0:router# show cef ipv4 interface MgmtEth 0/RP0/CPU0/0
MgmtEth0/0/CPU0/0 is up (if_handle 0x01000100)
ICMP redirects are never sent
IP MTU 1500, TableId 0xe0000000
Table 19 describes the significant fields shown in the display.
Table 19 show cef ipv4 interface Field Descriptions
|
|
MgmtEth 0/RP0/CPU0/0 is up |
Status of the interface. |
if_handle |
Internal interface handle. |
Forwarding is enabled |
Indicates that Cisco Express Forwarding (CEF) is enabled. |
ICMP redirects are always sent or never sent |
Indicates whether ICMP1 redirect messages should be sent. By default, ICMP redirect messages are always sent. |
IP MTU |
Value of the IPv4 MTU2 size set on the interface. |
Reference count |
Internal reference counter. |
show cef ipv4 interface bgp-policy-statistics
To display IPv4 Cisco Express Forwarding (CEF)-related Border Gateway Protocol (BGP) policy statistics information for an interface, use the show cef ipv4 interface bgp-policy-statistics command in EXEC mode.
show cef [vrf vrf-name] ipv4 interface type interface-path-id bgp-policy-statistics [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
location node-id |
(Optional) Displays IPv4 CEF-related information for an interface. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
The location keyword was added. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
This command displays all the configured BGP policy counters for the specified interface.
Examples
The following is sample output from the show cef ipv4 interface bgp-policy-statistics command:
RP/0/RP0/CPU0:router# show cef ipv4 interface TenGigE 0/2/0/4 bgp-policy-statistics
Input BGP policy accounting on src IP address enabled
Output BGP policy accounting on dst IP address enabled
Output BGP policy accounting on src IP address enabled
Table 20 describes the significant fields shown in the display.
Table 20 show cef ipv4 interface bgp-policy-statistics Field Descriptions
|
|
TenGigE 0/2/0/4 is up |
Status of the interface. |
Input BGP policy accounting on src IP address enabled |
Enabled BGP policy accounting features. |
buckets |
Traffic index. |
packets |
Number of packets counted in the bucket. |
bytes |
Number of bytes counted in the bucket. |
show cef ipv4 non-recursive
To display the IPv4 nonrecursive prefix entries in the IPv4 Cisco Express Forwarding (CEF) table, use the show cef ipv4 non-recursive command in EXEC mode.
show cef [vrf vrf-name] ipv4 non-recursive [detail] [hardware {egress | ingress}] [interface-type interface-instance] [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
detail |
(Optional) Displays detailed information about nonrecursive prefix entries in the IPv4 CEF table. |
hardware |
(Optional) Displays detailed information about hardware. |
egress |
(Optional) Displays egress packet switch exchange (PSE). |
ingress |
(Optional) Displays ingress packet switch exchange (PSE). |
interface-type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
interface-instance |
(Optional) 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. |
location node-id |
(Optional) Displays the IPv4 nonrecursive prefix entries in the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, the output displays the IPv4 CEF nonrecursive routes for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv4 non-recursive command:
RP/0/RP0/CPU0:router# show cef ipv4 non-recursive
Prefix Next Hop Interface
12.8.0.0/16 attached MgmtEth0/0/CPU0/0
12.8.0.0/32 broadcast MgmtEth0/0/CPU0/0
12.8.0.1/32 12.8.0.1 MgmtEth0/0/CPU0/0
12.8.0.2/32 12.8.0.2 MgmtEth0/0/CPU0/0
12.8.0.3/32 12.8.0.3 MgmtEth0/0/CPU0/0
12.8.16.10/32 12.8.16.10 MgmtEth0/0/CPU0/0
12.8.16.30/32 12.8.16.30 MgmtEth0/0/CPU0/0
12.8.16.40/32 12.8.16.40 MgmtEth0/0/CPU0/0
12.8.28.8/32 12.8.28.8 MgmtEth0/0/CPU0/0
12.8.28.101/32 12.8.28.101 MgmtEth0/0/CPU0/0
12.8.28.103/32 12.8.28.103 MgmtEth0/0/CPU0/0
12.8.28.104/32 12.8.28.104 MgmtEth0/0/CPU0/0
12.8.28.106/32 receive MgmtEth0/0/CPU0/0
12.8.29.113/32 12.8.29.113 MgmtEth0/0/CPU0/0
12.8.29.118/32 12.8.29.118 MgmtEth0/0/CPU0/0
12.8.29.140/32 12.8.29.140 MgmtEth0/0/CPU0/0
12.8.33.101/32 12.8.33.101 MgmtEth0/0/CPU0/0
12.8.33.103/32 12.8.33.103 MgmtEth0/0/CPU0/0
12.8.33.105/32 12.8.33.105 MgmtEth0/0/CPU0/0
12.8.33.110/32 12.8.33.110 MgmtEth0/0/CPU0/0
12.8.57.1/32 12.8.57.1 MgmtEth0/0/CPU0/0
12.8.255.255/32 broadcast MgmtEth0/0/CPU0/0
12.29.31.2/32 12.29.31.2 MgmtEth0/0/CPU0/0
223.255.0.0/16 attached MgmtEth0/0/CPU0/0
223.255.254.254/32 223.255.254.254 MgmtEth0/0/CPU0/0
255.255.255.255/32 broadcast
Table 21 describes the significant fields shown in the display.
Table 21 show cef ipv4 non-recursive Field Descriptions
|
|
Prefix |
Nonrecursive prefixes detected on the node. |
Next Hop |
Routing next hop. |
Interface |
Interface associated with the nonrecursive prefix. |
show cef ipv4 resource
To display the IPv4 nonrecursive prefix entries in the IPv4 Cisco Express Forwarding (CEF) table, use the show cef ipv4 resource command in EXEC mode.
show cef ipv4 resource [detail] [hardware {egress | ingress}] [location node-id]
Syntax Description
detail |
(Optional) Displays detailed information resources listed in the IPv4 CEF table. |
hardware |
(Optional) Displays detailed information about hardware. |
egress |
(Optional) Displays egress packet switch exchange (PSE). |
ingress |
(Optional) Displays ingress packet switch exchange (PSE). |
location node-id |
(Optional) Displays the IPv4 resource entries in the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
The hardware keyword was added. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, the output displays the IPv4 CEF nonrecursive routes for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv4 resource command:
RP/0/RP0/CPU0:router# show cef ipv4 resource detail
CEF resource availability summary state: GREEN
ipv4 shared memory resource:
CurrMode GREEN, CurrUtil 0%
CurrAvail 1874526208 bytes, MaxAvail 1875693568 bytes
ipv6 shared memory resource:
CurrMode GREEN, CurrUtil 0%
CurrAvail 1874591744 bytes, MaxAvail 1875365888 bytes
mpls shared memory resource:
CurrMode GREEN, CurrUtil 0%
CurrAvail 1874407424 bytes, MaxAvail 1875038208 bytes
common shared memory resource:
CurrMode GREEN, CurrUtil 0%
CurrAvail 1873215488 bytes, MaxAvail 1874972672 bytes
TABLE hardware resource: GREEN
LEAF hardware resource: GREEN
LOADINFO hardware resource: GREEN
NHINFO hardware resource: GREEN
LABEL_INFO hardware resource: GREEN
IDB hardware resource: GREEN
FRR_NHINFO hardware resource: GREEN
LDSH_ARRAY hardware resource: GREEN
RSRC_MON hardware resource: GREEN
show cef ipv4 summary
To display a summary of the IPv4 Cisco Express Forwarding (CEF) table, use the show cef ipv4 summary command in EXEC mode.
show cef [vrf vrf-name] ipv4 summary [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
location node-id |
(Optional) Displays a summary of the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
The sample output was modified to display the load-balancing field for either Layer 3 or Layer 4. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays a summary of the IPv4 CEF table for the node on which the command is issued.
Examples
The following sample output is from the show cef ipv4 summary command:
RP/0/RP0/CPU0:router# show cef ipv4 summary
IP CEF with switching (Table Version 0)
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 367
193 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 13896 bytes
204 load sharing elements, 51904 bytes, 154 references
17 shared load sharing elements, 5536 bytes
187 exclusive load sharing elements, 46368 bytes
0 CEF route update drops, 175 revisions of existing leaves
0 prefixes modified in place
16 prefixes with label imposition, 51 prefixes with label information
Adjacency Table has 44 adjacencies
Table 22 describes the significant fields shown in the display.
Table 22 show cef ipv4 summary Field Descriptions
|
|
Load balancing |
Current load-balancing mode that is configured using the cef load-balancing fields command. The default value is L3. |
Table Version |
Version of the CEF table. |
tableid |
Table identification number. |
vrfid |
VPN routing and forwarding (VRF) identification (vrfid) number. |
vrfname |
VRF name. |
vrid |
Virtual router identification (vrid) number. |
flags |
Option value for the table |
routes |
Total number of routes. |
reresolve |
Total number of routes being reresolved. |
unresolved (x old, x new) |
Number of routes not yet resolved. |
load sharing elements |
Total number of internal load-sharing data structures. |
bytes |
Total memory used by internal load sharing data structures. |
references |
Total reference count of all internal load sharing data structures. |
CEF resets |
Number of CEF table resets. |
revisions of existing leaves |
Number of updates to existing prefixes. |
Exponential (currently xs, peak xs) |
Currently not used. |
prefixes modified in place |
Prefixes modified in place. |
Adjacency Table has x adjacencies |
Total number of adjacencies. |
x incomplete adjacency |
Total number of incomplete adjacencies. |
Related Commands
|
|
bundle-hash |
Displays the path a bundle flow that comprises a source and destination address would take. For more information, see Cisco IOS XR Interface and Hardware Component Command Reference. |
cef load-balancing fields |
Selects the hashing algorithm that is used for load balancing when forwarding. |
show mpls forwarding exact-route |
Displays the path an MPLS flow that comprises a source and destination address would take. For more information, see Cisco IOS XR Multiprotocol Label Switching Command Reference. |
show cef ipv4 unresolved
To display unresolved routes in the IPv4 Cisco Express Forwarding (CEF) table, use the show cef ipv4 unresolved command in EXEC mode.
show cef [vrf vrf-name] ipv4 unresolved [detail] [hardware {egress | ingress}] [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
detail |
(Optional) Displays detailed information unresolved routes listed in the IPv4 CEF table. |
hardware |
(Optional) Displays detailed information about hardware. |
egress |
(Optional) Displays egress packet switch exchange (PSE). |
ingress |
(Optional) Displays ingress packet switch exchange (PSE). |
location node-id |
(Optional) Displays the unresolved routes in the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
Both the detail and hardware keywords were added. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, the output displays the unresolved routes for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv4 unresolved command when an unresolved route is detected:
RP/0/RP0/CPU0:router# show cef ipv4 unresolved
Prefix Next Hop Interface
Table 23 describes the significant fields shown in the display.
Table 23 show cef ipv4 unresolved Field Descriptions
|
|
Prefix |
Prefix of the unresolved CEF. |
Next Hop |
Next hop of the unresolved CEF. |
Interface |
Next hop interface. A question mark (?) indicates that the interface has not been resolved. |
show cef ipv6
To display the IPv6 Cisco Express Forwarding (CEF) table, use the show cef ipv6 command in EXEC mode.
show cef [vrf vrf-name] ipv6 [interface-type interface-number | ipv6-prefix/prefix-length] [detail] [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
interface-type interface-number |
(Optional) IPv6 prefixes going through the specified next hop interface. |
ipv6-prefix/prefix-length |
(Optional) Longest prefix entry in the CEF table matching the specified IPv6 prefix and prefix length. |
detail |
(Optional) Displays detailed IPv6 CEF table information. |
location node-id |
(Optional) Displays the IPv6 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
The sample output for the detail keyword is modified for a specific prefix. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays the IPv6 CEF table for the node on which the command is issued.
Examples
The following sample output is from the show cef ipv6 command:
RP/0/RP0/CPU0:router# show cef ipv6
recursive fe80::3031:48ff:fe53:5533, POS0/3/0/0
recursive fe80::205:5fff:fe1d:7600, POS0/4/0/0
Table 24 describes the significant fields shown in the display.
Table 24 show cef ipv6 Field Descriptions
|
|
drop |
Indicates that packets sent to the destination prefix are dropped. |
loopback |
Indicates that the prefix points to a loopback address. Packets sent to loopback addresses are dropped. |
receive |
Indicates that the prefix is configured on one of the router interfaces. Packets sent to those prefixes are received by the router. |
connected |
Indicates that the prefix points to a directly connected next-hop interface. |
recursive |
Indicates that the prefix is not directly connected but is reachable through the next-hop prefix displayed. |
The following sample output is from the show cef ipv6 with the detail keyword:
RP/0/RP0/CPU0:router# show cef ipv6 detail
Loadinfo owner: <this route>
Loadinfo owner: <this route>
interface : <not specified>
flags: loopback, source_fib
Loadinfo owner: <this route>
interface : <not specified>
flags: receive, source_rib
Loadinfo owner: <this route>
Table 25 describes the significant output fields shown in the display.
Table 25 show cef ipv6 detail Field Descriptions
|
|
flags: |
Properties of the indicated prefix. |
Loadinfo owner: |
Owner of the Loadinfo used by the prefix for forwarding. The Loadinfo owner is the prefix that owns the array of pointers to adjacencies. |
fast adj: |
Cached adjacency used for forwarding. |
path 1: |
The following three items are displayed below path 1: •flags-Properties of the path. •next hop-Next-hop prefix if the packet is being forwarded. •interface-Next-hop interface if the packet is being forwarded. |
The following sample output is from the show cef ipv6 command for the detail keyword, with 101:1:1::/64 as the ipv6-prefix/prefix-length argument and a location of 0/1/CPU0:
RP/0/RP0/CPU0:router# show cef ipv6 101:1:1::/64 detail location 0/1/CPU0
101:1:1::/64, version 262, internal 0x42000001[1]
Prefix Len 64, traffic index 0, precedence routine (0)
gateway array reference count 1, flags 0x0, [0, flags 0x4900]
Level 1 - Load distribution: 0
[0] via 22:6:1::9, recursive
via 22:6:1::9, 0 dependencies, recursive
next hop 22:6:1::9 via 22:6:1::9/128
Load distribution: _ _ _ (refcount 1)
Hash OK Interface Address
- Y GigabitEthernet0/1/2/1 fe80::250:e2ff:fe8f:8381
- Y GigabitEthernet0/1/2/2 fe80::250:e2ff:fe8f:8382
show cef ipv6 adjacency
To display Cisco Express Forwarding (CEF) IPv6 adjacency status and configuration information, use the show cef ipv6 adjacency command in EXEC mode.
show cef [vrf vrf-name] ipv6 adjacency [interface-type interface-instance] [location node-id] [detail] [discard] [glean] [null] [punt] [remote]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
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. |
location node-id |
(Optional) Displays detailed CEF information for the designated node. The node-id argument is entered in the rack/slot/module notation. |
detail |
(Optional) Displays the detailed adjacency information. |
discard |
(Optional) Filters out and displays only the discarded adjacency information. |
glean |
(Optional) Filters out and displays only the glean adjacency information. |
null |
(Optional) Filters out and displays only the null adjacency information. |
punt |
(Optional) Filters out and displays only the punt adjacency information. |
remote |
(Optional) Filters out and displays only the remote adjacency information. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
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.
Examples
The following sample output is from the show cef ipv6 adjacency command:
RP/0/RP0/CPU0:router# show cef ipv6 adjacency
show cef ipv6 adjacency hardware
To display Cisco Express Forwarding (CEF) IPv6 adjacency hardware status and configuration information, use the show cef ipv6 adjacency hardware command in EXEC mode.
show cef [vrf vrf-name] ipv6 adjacency hardware {egress | ingress} [detail | discard | drop | glean | location node-id | null | punt | remote]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
egress |
Displays information from the egress packet switch exchange (PSE) file. |
ingress |
Displays information from the ingress packet switch exchange (PSE) file. |
detail |
(Optional) Displays full details. |
discard |
(Optional) Displays the discard adjacency information. |
drop |
(Optional) Displays the drop adjacency information. |
glean |
(Optional) Displays the glean adjacency 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. |
null |
(Optional) Displays the null adjacency information. |
punt |
(Optional) Displays the punt adjacency information. |
remote |
(Optional) Displays the remote adjacency information. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following sample output is from the show cef ipv6 adjacency hardware command:
RP/0/RP0/CPU0:router# show cef ipv6 adjacency hardware
show cef ipv6 drops
To display IPv6 Cisco Express Forwarding (CEF) table packet drop counters, use the show cef ipv6 drops command in EXEC mode.
show cef [vrf vrf-name] ipv6 drops [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
location node-id |
(Optional) Displays IPv6 CEF table packet drop counters for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
A packet might be dropped by the IPv6 CEF table because of unresolved CEF entries, unsupported features, absence of route information, absence of adjacency information, or an IP checksum error.
If you do not specify a node with the location keyword and node-id argument, this command displays the packet drops for all nodes.
Note Because no hardware forwarding occurs on the route processor (RP), no packet drop information is displayed for that node.
Examples
The following is sample output from the show cef ipv6 drops command:
RP/0/RP0/CPU0:router# show cef ipv6 drops location 0/2/CPU0
Line status down ingress : 0 egress : Not Applicable
Packet sanity fail ingress : 0 egress : 0
PLU set to drop ingress : 0 egress : 0
Unknown type,plu drop ingress : 0 egress : 0
Packet length err ingress : 0 egress : 0
TCAM src-comp err ingress : 0 egress : 0
Table 26 describes the significant fields shown in the display.
Table 26 show cef ipv6 drop Field Descriptions
|
|
Line status down |
Packet drops due to the line protocol of the incoming interface being down. |
Packet sanity fail |
Packet drops due to the prefix failing the IPv6 sanity test. The sanity test verifies that the IPv6 packet is valid. |
PLU set to drop |
Packet drops due the IPv6 destination prefix being set to drop. |
Unknown type, plu drop |
Packet drops due to the prefix being of an unknown type. |
Packet length errs |
Length specified in the header does not match the actual length of the packet received. |
TCAM src-comp err |
Packet drops due to source compression errors that have occurred in the hardware. |
Related Commands
show cef ipv6 exact-route
To display the path an IPv6 flow comprising a source and destination address would take, use the show cef ipv6 exact-route command in EXEC mode.
show cef [vrf vrf-name] ipv6 exact-route {source-address destination-address} [protocol protocol name] [source-port source-port] [destination-port destination-port] [ingress-interface type interface-path-id] [policy-class value] [detail | location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
source-address |
The IPv6 source address in x:x::x format. |
destination-address |
The IPv6 destination address in x:x::x format. |
protocol protocol name |
(Optional) Displays the specified protocol for the route. |
source-port source-port |
(Optional) Sets the UDP source port. The range is from 0 to 65535. |
destination-port destination-port |
(Optional) Sets the UDP destination port. The range is from 0 to 65535. |
ingress-interface |
(Optional) Sets the ingress interface. |
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
policy-class value |
(Optional) Displays the class for the policy-based tunnel selection. The range for the tunnel policy class value is from 1 to 7. |
detail |
(Optional) Displays full CEF entry information. |
location node-id |
(Optional) Displays the IPv6 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
The following keywords were added so that the Layer 4 information can be specified for the exact route: •protocol •source-port •destination-port •ingress-interface The policy-class keyword was added to tunnel policy. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If the Layer 4 information is enabled, the source-port, destination-port, protocol, and ingress-interface fields are required. Otherwise, the output of the show cef ipv6 exact-route command is not correct.
Examples
The following sample output is from the show cef ipv6 exact-route command:
RP/0/RP0/CPU0:router# show cef ipv6 exact-route 222::2 9999::6751 location
0/3/CPU0 source address: 222::2 destination address: 9999::6751
interface : TenGigE0/3/0/3 non local interface
The following sample output shows the exact route for the Layer 4 information:
RP/0/RP0/CPU0:router# show cef ipv6 exact-route 20:6:1::9 22:6:1::9 protocol udp
source-port 1 destination-port 1 ingress-interface GigabitEthernet 0/1/0/4
22:6:1::/64, version 0, internal 0x40000001 (0x7846c048) [3], 0x0 (0x78aea3d0), 0x0 (0x0)
remote adjacency to POS0/1/4/4
Prefix Len 64, traffic index 0, precedence routine (0)
Related Commands
|
|
bundle-hash |
Displays the path a bundle flow that comprises a source and destination address would take. For more information, see Cisco IOS XR Interface and Hardware Component Command Reference. |
cef load-balancing fields |
Selects the hashing algorithm that is used for load balancing when forwarding. |
show mpls forwarding exact-route |
Displays the path an MPLS flow that comprises a source and destination address would take. For more information, see Cisco IOS XR Multiprotocol Label Switching Command Reference. |
show cef ipv6 exceptions
To display IPv6 Cisco Express Forwarding (CEF) exception packet counters, use the show cef ipv6 exceptions command in EXEC mode.
show cef [vrf vrf-name] ipv6 exceptions [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
location node-id |
(Optional) Displays IPv6 CEF exception packet counters for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
CEF exception packets are those packets that have been sent from the hardware to the software because they require additional handling. The types of IPv6 CEF exception packets are displayed in the output of show cef ipv6 exceptions.
If you do not specify a node with location keyword and node-id argument, this command displays IPv6 CEF exception packet counters for all nodes.
Examples
The following is sample output from the show cef ipv6 exceptions command:
RP/0/RP0/CPU0:router: show cef ipv6 exceptions location 0/3/CPU0
IPv6 CEF Exception Statistics
TTL err ingress : 0 egress : Not Applicable
Link-local dst addr ingress : 0 egress : 0
Hop-by-Hop header ingress : 0 egress : 0
PLU entry set to punt ingress : 0 egress : 0
Packet too big ingress : Not Applicable egress : 0
Med priority punt ingress : 0 egress : Not Applicable
Table 27 describes the significant fields shown in the display.
Table 27 show cef ipv6 exceptions Field Descriptions
|
|
TTL err |
Packets sent to software for processing because the packet header of the IPv6 prefix had a TTL1 error. |
Link-local dst addr |
Packets sent to the software for processing because the destination address of the IPv6 prefix is link local. |
Hop-by-Hop header |
Packets sent to the software for processing because the IPv6 packet has a hop-by-hop header. |
PLU entry set to punt |
Packets sent to software for processing because the IPv6 prefix is set to punt. |
Packet too big |
Packets sent to the software for processing because the packet size exceeded the MTU2 . |
Med priority punt |
Field used internally for troubleshooting. |
Related Commands
show cef ipv6 hardware
To display Cisco Express Forwarding (CEF) IPv6 hardware status and configuration information, use the show cef ipv6 hardware command in EXEC mode.
show cef [vrf vrf-name] ipv6 hardware {egress | ingress [detail | location node-id]}
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
egress |
Displays information from the egress packet switch exchange (PSE) file. |
ingress |
Displays information from the ingress packet switch exchange (PSE) file. |
detail |
(Optional) Displays full details. |
location node-id |
(Optional) Displays detailed CEF information for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following sample output displays the full details from the show cef ipv6 hardware command:
RP/0/RP0/CPU0:router# show cef ipv6 hardware egress detail
::/0, version 0, proxy default, default route handler, drop adjacency, internal
Prefix Len 0, traffic index 0, precedence routine (0)
gateway array (0x0) reference count 1, flags 0x4000, source 4,
[0 type 3 flags 0x109000 (0x7895114c) ext 0x0 (0x0)]
LW-LDI[type=3, refc=1, ptr=0x78a7d0dc, sh-ldi=0x7895114c]
via point2point, 0 dependencies, weight 0, class 0
Load distribution: 0 (refcount 0)
Hash OK Interface Address
ff02::/16, version 0, receive
ff02::2/128, version 0, receive
ff02::1:ff00:0/104, version 0, receive
show cef ipv6 interface
To display IPv6 Cisco Express Forwarding (CEF)-related information for an interface, use the show cef ipv6 interface command in EXEC mode.
show cef [vrf vrf-name] ipv6 interface type interface-path-id [detail] [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
detail |
(Optional) Displays detailed CEF information for all the interfaces on the node in which the command is issued. |
location node-id |
(Optional) Displays IPv4 CEF-related information for an interface. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, the show cef ipv6 interface command displays the CEF-related information for the interface on the route processor.
Examples
The following sample output is from the show cef ipv6 interface command:
RP/0/RP0/CPU0:router# show cef ipv6 interface
show cef ipv6 interface bgp-policy-statistics
To display IPv6 Cisco Express Forwarding (CEF)-related BGP policy statistics information for an interface, use the show cef ipv6 interface bgp-policy-statistics command in EXEC mode.
show cef [vrf vrf-name] ipv6 interface type interface-path-id bgp-policy-statistics [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
location node-id |
(Optional) Displays detailed CEF information for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
The location keyword was added. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The show cef ipv6 interface bgp-policy-statistics command displays all the configured BGP policy counters for the specified interface.
Examples
The following sample output is from the show cef ipv6 interface bgp-policy-statistics command:
RP/0/RP0/CPU0:router# show cef ipv6 interface bgp-policy-statistics
show cef ipv6 interface rpf-statistics
To display IPv6 Cisco Express Forwarding (CEF)-related Unicast Reverse Path Forwarding (RPF) statistics information for an interface, use the show cef ipv6 interface rpf-statistics command in EXEC mode.
show cef [vrf vrf-name] ipv6 interface {type instance} rpf-statistics [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
type |
Interface type. For more information, use the question mark (?) online help function. |
instance |
Either a physical interface instance or a virtual interface instance as follows: •Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation. –rack: Chassis number of the rack. –slot: Physical slot number of the modular services card or 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. |
location node-id |
(Optional) Displays detailed CEF information for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.6.0 |
This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following sample output is from the show cef ipv6 interface rpf-statistics command:
RP/0/RP0/CPU0:router# show cef ipv6 interface POS 0/1/0/0 rpf-statistics
show cef ipv6 non-recursive
To display the IPv6 nonrecursive prefix entries in the IPv6 Cisco Express Forwarding (CEF) table, use the show cef ipv6 non-recursive command in EXEC mode.
show cef [vrf vrf-name] ipv6 non-recursive [hardware {egress | ingress}] [detail] [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
hardware |
(Optional) Displays Cisco Express Forwarding (CEF) IPv6 hardware status and configuration information. |
egress |
(Optional) Displays information from the egress packet switch exchange (PSE) file. |
ingress |
(Optional) Displays information from the ingress packet switch exchange (PSE) file. |
detail |
(Optional) Displays full details. |
location node-id |
(Optional) Displays the nonrecursive prefix entries in the IPv6 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
Both the hardware and detail keywords were added. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays the nonrecursive routes for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv6 non-recursive command:
RP/0/RP0/CPU0:router# show cef ipv6 non-recursive
Table 28 describes the significant fields shown in the display.
Table 28 show cef ipv6 non-recursive Field Descriptions
|
|
drop |
Indicates that packets sent to the destination prefix are dropped. |
loopback |
Indicates that the prefix points to a loopback address. Packets sent to loopback addresses are dropped. |
receive |
Indicates that the prefix is configured on one of the router interfaces. Packets sent to those prefixes are received by the router. |
connected |
Indicates that the prefix points to a directly connected next-hop interface. |
show cef ipv6 resource
To display the IPv6 nonrecursive prefix entries in the IPv6 Cisco Express Forwarding (CEF) table, use the show cef ipv6 resource command in EXEC mode.
show cef ipv6 resource [detail] [hardware {egress | ingress}] [location node-id]
Syntax Description
detail |
(Optional) Displays detailed information resources listed in the IPv6 CEF table. |
hardware |
(Optional) Displays Cisco Express Forwarding (CEF) IPv6 hardware status and configuration information. |
egress |
(Optional) Displays information from the egress packet switch exchange (PSE) file. |
ingress |
(Optional) Displays information from the ingress packet switch exchange (PSE) file. |
location node-id |
(Optional) Displays the IPv6 resource entries in the IPv6 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
The hardware keyword was added. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, the output displays the IPv6 CEF nonrecursive routes for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv6 resource command:
RP/0/RP0/CPU0:router# show cef ipv6 resource
CEF resource availability summary state: GREEN
ipv4 shared memory resource: GREEN
ipv6 shared memory resource: GREEN
mpls shared memory resource: GREEN
common shared memory resource: GREEN
TABLE hardware resource: GREEN
LEAF hardware resource: GREEN
LOADINFO hardware resource: GREEN
NHINFO hardware resource: GREEN
LABEL_INFO hardware resource: GREEN
IDB hardware resource: GREEN
FRR_NHINFO hardware resource: GREEN
LDSH_ARRAY hardware resource: GREEN
RSRC_MON hardware resource: GREEN
show cef ipv6 summary
To display a summary of the IPv6 Cisco Express Forwarding (CEF) table, use the show cef ipv6 summary command in EXEC mode.
show cef [vrf vrf-name] ipv6 summary [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
location node-id |
(Optional) Displays a summary of the IPv6 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
The sample output was modified to display the load-balancing field for either Layer 3 or Layer 4. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays a summary of the IPv6 CEF table for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv6 summary command:
RP/0/RP0/CPU0:router# show cef ipv6 summary
IP CEF with switching (Table Version 0)
Tableid 0xe0800000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 12
4 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 288 bytes
0 load sharing elements, 0 bytes, 0 references
0 shared load sharing elements, 0 bytes
0 exclusive load sharing elements, 0 bytes
0 CEF route update drops, 0 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 0 prefixes with label information
Adjacency Table has 44 adjacencies
Table 29 describes the significant fields shown in the display.
Table 29 show cef ipv6 summary Field Descriptions
|
|
Load balancing |
Current load-balancing mode that is configured using the cef load-balancing fields command. The default value is L3. |
Table Version |
Version of the CEF table. |
routes |
Total number of routes. |
unresolved (x old, x new) |
Number of routes not yet resolved. |
load sharing elements |
Total number of internal load-sharing data structures. |
bytes |
Total memory used by internal load sharing data structures. |
references |
Total reference count of all internal load sharing data structures. |
CEF resets |
Number of CEF table resets. |
revisions of existing leaves |
Number of updates to existing prefixes. |
Exponential (currently xs, peak xs) |
Currently not used. |
prefixes modified in place |
Prefixes modified in place. |
Router ID |
Router identification. |
Adjacency Table has x adjacencies |
Total number of adjacencies. |
x incomplete adjacency |
Total number of incomplete adjacencies. |
Related Commands
|
|
bundle-hash |
Displays the path a bundle flow that comprises a source and destination address would take. For more information, see Cisco IOS XR Interface and Hardware Component Command Reference. |
cef load-balancing fields |
Selects the hashing algorithm that is used for load balancing when forwarding. |
show mpls forwarding exact-route |
Displays the path an MPLS flow that comprises a source and destination address would take. For more information, see Cisco IOS XR Multiprotocol Label Switching Command Reference. |
show cef ipv6 unresolved
To display the unresolved routes in the IPv6 Cisco Express Forwarding (CEF) table, use the show cef ipv6 unresolved command in EXEC mode.
show cef [vrf vrf-name] ipv6 unresolved [detail] [hardware {egress | ingress}] [location node-id]
Syntax Description
vrf |
(Optional) Displays VPN routing and forwarding (VRF) instance information. |
vrf-name |
(Optional) Name of a VRF. |
hardware |
(Optional) Displays Cisco Express Forwarding (CEF) IPv6 hardware status and configuration information. |
egress |
(Optional) Displays information from the egress packet switch exchange (PSE) file. |
ingress |
(Optional) Displays information from the ingress packet switch exchange (PSE) file. |
detail |
(Optional) Displays full details. |
location node-id |
(Optional) Displays the unresolved routes in the IPv6 CEF table for the specified node. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3.0 |
The vrf keyword and vrf-name argument were added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
Both the hardware and detail keywords were added. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays the unresolved routes for the node on which the command is issued.
Examples
This following is sample output from show cef ipv6 unresolved command when an unresolved route is detected:
RP/0/RP0/CPU0:router# show cef ipv6 unresolved
Table 30 describes the significant fields shown in the display.
Table 30 show cef ipv6 unresolved Field Descriptions
|
|
xxxx::/xx |
Detected unresolved route. |
show cef mpls adjacency
To display the Multiprotocol Label Switching (MPLS) adjacency table, use the show cef mpls adjacency command in EXEC mode.
show cef mpls adjacency [interface-type interface-instance] [detail | discard | drop | glean | null | punt | remote] [location node-id]
Syntax Description
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. |
detail |
(Optional) Displays full details. |
discard |
(Optional) Displays the discard adjacency information. |
drop |
(Optional) Displays the drop adjacency information. |
glean |
(Optional) Displays the glean adjacency information. |
null |
(Optional) Displays the null adjacency information. |
punt |
(Optional) Displays the punt adjacency information. |
remote |
(Optional) Displays the remote adjacency 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. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
The following keywords were added: •detail •discard •drop •glean •null •punt •remote |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, the show cef mpls adjacency command displays the MPLS adjacency table for the node in which the command is issued.
Examples
This following is sample output from show cef mpls adjacency command:
RP/0/RP0/CPU0:router# show cef mpls adjacency
Related Commands
show cef mpls adjacency hardware
To display the Multiprotocol Label Switching (MPLS) adjacency hardware status and configuration information, use the show cef mpls adjacency hardware command in EXEC mode.
show cef mpls adjacency hardware {egress | ingress} [detail | discard | drop | glean | location node-id | null | punt | remote]
Syntax Description
egress |
Displays information from the egress packet switch exchange (PSE) file. |
ingress |
Displays information from the ingress packet switch exchange (PSE) file. |
detail |
(Optional) Displays full details. |
discard |
(Optional) Displays the discard adjacency information. |
drop |
(Optional) Displays the drop adjacency information. |
glean |
(Optional) Displays the glean adjacency 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. |
null |
(Optional) Displays the null adjacency information. |
punt |
(Optional) Displays the punt adjacency information. |
remote |
(Optional) Displays the remote adjacency information. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.6.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
This following is sample output from show cef mpls adjacency hardware command:
RP/0/RP0/CPU0:router# show cef mpls adjacency hardware
Related Commands
show cef mpls interface
To display the Multiprotocol Label Switching (MPLS) Cisco Express Forwarding (CEF)-related information for an interface, use the show cef mpls interface command in EXEC mode.
show cef mpls interface {type instance} [detail] [location node-id]
Syntax Description
type |
Interface type. For more information, use the question mark (?) online help function. |
instance |
Either a physical interface instance or a virtual interface instance as follows: •Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation. –rack: Chassis number of the rack. –slot: Physical slot number of the modular services card or 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. |
detail |
(Optional) Displays detailed CEF information for all the interfaces on the node in which the command is issued. |
location node-id |
(Optional) Displays IPv4 CEF-related information for an interface. The node-id argument is entered in the rack/slot/module notation. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.6.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, the show cef mpls interface command displays the CEF-related information for the interface on the route processor.
Examples
The following sample output is from the show cef mpls interface command:
RP/0/RP0/CPU0:router# show cef mpls interface
Related Commands
show cef mpls unresolved
To display the Multiprotocol Label Switching (MPLS) unresolved routes, use the show cef mpls unresolved command in EXEC mode.
show cef mpls unresolved [detail] [location node-id]
Syntax Description
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. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following sample output is from the show cef mpls unresolved command:
RP/0/RP0/CPU0:router# show cef mpls unresolved
Label/EOS Next Hop Interface
Table 31 describes the significant fields shown in the display.
Table 31 show cef mpls unresolved Command Field Descriptions
|
|
Label/EOS |
MPLS forwarding label/End of Stack (EOS) bit. |
Next Hop |
Next hop of the prefix. |
Interface |
Interface associated with the prefix. |
Related Commands
show cef vrf
To display the contents of the VPN routing and forwarding (VRF) instance, use the show cef vrf command in EXEC mode.
show cef vrf [vrf-name]
Syntax Description
vrf-name |
Name of the VRF instance. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
To display unresolved routes, you must use the unresolved keyword explicitly.
Examples
This following is sample output from show cef vrf command when an unresolved route is detected:
RP/0/RP0/CPU0:router# show cef vrf 0
Prefix Next Hop Interface
0.0.0.0/0 drop default handler
255.255.255.255/32 broadcast
Table 32 describes the significant fields shown in the display.
Table 32 show cef vrf Field Descriptions
|
|
Prefix |
Prefix in the IPv4 CEF table. |
Next Hop |
Next hop of the prefix. |
Interface |
Interface associated with the prefix. |