-
Cisco IOS XR IP Addresses and Services Command Reference, Release 3.5
-
Preface
-
Access List Commands on Cisco IOS XR Software
-
ARP Commands on Cisco IOS XR Software
-
Cisco Express Forwarding Commands on Cisco IOS XR Software
-
DHCP Commands on Cisco IOS XR Software
-
Host Services and Applications Commands on Cisco IOS XR Software
-
HSRP Commands on Cisco IOS XR Software
-
LPTS Commands on Cisco IOS XR Software
-
Network Stack IPv4 and IPv6 Commands on Cisco IOS XR Software
-
Prefix List Commands on Cisco IOS XR Software
-
Transport Stack Commands Cisco IOS XR Software
-
VRRP Commands on Cisco IOS XR Software
-
Index
-
Table Of Contents
Cisco Express Forwarding Commands on Cisco IOS XR Software
clear cef ipv4 interface bgp-policy-statistics
clear cef ipv4 interface rpf-statistics
clear cef ipv6 interface bgp-policy-statistics
clear cef ipv6 interface rpf-statistics
ipv4 verify unicast source reachable-via
ipv6 verify unicast source reachable-via any
show cef ipv4 adjacency hardware
show cef ipv4 external hardware
show cef ipv4 interface bgp-policy-statistics
show cef ipv6 adjacency hardware
show cef ipv6 external hardware
show cef ipv6 interface bgp-policy-statistics
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.
clear adjacency ipv4
To clear the IPv4 CEF adjacency table, use the clear adjacency ipv4 command in EXEC mode.
clear adjacency statistics ipv4 [location node-id]
Syntax Description
location node-id
(Optional) Clears the IPv4 CEF adjacency 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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When you issue the clear adjacency statistics ipv4 command, entries in the adjacency table that reside on the route processor (RP) are removed and then repopulated.
If you do not specify a node with the location keyword and node-id argument, this command clears the CEF adjacency table on the interface on the route processor on which the command is issued.
Task ID
Examples
The following example shows how to clear the IPv4 CEF adjacency table on the RP:
RP/0/RP0/CPU0:router# clear adjacency statistics ipv4Related Commands
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
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
This 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.
Task ID
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-------------------------------------------------------------------------------0/RP1/CPU0-------------------------------------------------------------------------------Interface Address Version Refcount ProtocolMgmtEth0/RP1/CPU0/0 (src mac only) 1 1 ipv4000000000000001193efe8fe0800mtu: 1500, flags 1 0 10 packets, 0 bytesMgmtEth0/RP1/CPU0/0 (interface) 2 1(interface entry)flags 1 0 40 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.77 29 2 ipv4001193efe8e2001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.105 19 2 ipv4001b2a4e53e5001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.241 18 2 ipv4001819d18c38001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.173 15 2 ipv40015c75f09f8001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.81 9 2 ipv4001a6c40d89c001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.1 6 2 ipv40030f2f21038001193efe8fe0800mtu: 1500, flags 1 0 01 packets, 60 bytesMgmtEth0/RP1/CPU0/0 172.29.52.201 3 2 ipv400107b3c6847001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.96 23 2 ipv40018ba800c80001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.168 22 2 ipv400503ee3dd80001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.152 21 2 ipv400503ee3df40001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.180 16 2 ipv40015c75f0800001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.28 12 2 ipv400127fd6ba09001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.76 7 2 ipv4001193efe8ea001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.200 4 2 ipv400107b3c689f001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.83 26 2 ipv4001a6c40d89c001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.151 25 2 ipv4000a41052e01001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.91 17 2 ipv40018742c5f40001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.127 14 2 ipv40013c4cba200001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.27 11 2 ipv400127fd6ba08001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.75 8 2 ipv4001193efe8e2001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.182 27 2 ipv40015c75f0800001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.150 24 2 ipv4000a41052da1001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.90 20 2 ipv4001874163f80001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.70 13 2 ipv45a5900000201001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.82 10 2 ipv400127fd6bc36001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP1/CPU0/0 172.29.52.126 5 2 ipv40013c4cba548001193efe8fe0800mtu: 1500, flags 1 0 00 packets, 0 bytes-------------------------------------------------------------------------------0/RP0/CPU0-------------------------------------------------------------------------------Interface Address Version Refcount ProtocolMgmtEth0/RP0/CPU0/0 (src mac only) 2 1 ipv40000000000005a59000002010800mtu: 1500, flags 1 0 10 packets, 0 bytesMgmtEth0/RP0/CPU0/0 (interface) 1 1(interface entry)flags 1 0 40 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.77 38 2 ipv4001193efe8e25a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.105 29 2 ipv4001b2a4e53e55a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.241 28 2 ipv4001819d18c385a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.173 24 2 ipv40015c75f09f85a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.81 19 2 ipv4001a6c40d89c5a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.13 16 2 ipv4001079e960385a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.153 15 2 ipv400e0b0552cc45a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.121 13 2 ipv40012da0b97ff5a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.1 6 2 ipv40030f2f210385a59000002010800mtu: 1500, flags 1 0 0257909 packets, 9246567 bytesMgmtEth0/RP0/CPU0/0 172.29.52.201 4 2 ipv400107b3c68475a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.96 32 2 ipv40018ba800c805a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.168 31 2 ipv400503ee3dd805a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.152 30 2 ipv400503ee3df405a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.180 25 2 ipv40015c75f08005a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.28 22 2 ipv400127fd6ba095a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.76 17 2 ipv4001193efe8ea5a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.52 14 2 ipv40090929c88485a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.148 12 2 ipv400b064fce0bb5a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.120 10 2 ipv400042892c7ff5a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.200 5 2 ipv400107b3c689f5a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.83 35 2 ipv4001a6c40d89c5a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.151 34 2 ipv4000a41052e015a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.91 27 2 ipv40018742c5f405a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.127 23 2 ipv40013c4cba2005a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.27 21 2 ipv400127fd6ba085a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.75 18 2 ipv4001193efe8e25a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.51 11 2 ipv400e04f5fe0685a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.71 3 2 ipv4001193efe8fe5a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.182 36 2 ipv40015c75f08005a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.150 33 2 ipv4000a41052da15a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.90 26 2 ipv4001874163f805a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.82 20 2 ipv400127fd6bc365a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.50 9 2 ipv40090929cf8685a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.190 8 2 ipv400000c4775e05a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytesMgmtEth0/RP0/CPU0/0 172.29.52.126 7 2 ipv40013c4cba5485a59000002010800mtu: 1500, flags 1 0 00 packets, 0 bytes-------------------------------------------------------------------------------0/6/CPU0-------------------------------------------------------------------------------Interface Address Version Refcount ProtocolGigabitEthernet0/6/5/7 (src mac only) 4 1 ipv400000000000000000c07fa5e0800mtu: 1500, flags 1 0 10 packets, 0 bytesPOS0/6/4/0 (interface) 27 1(interface entry)flags 1 0 40 packets, 0 bytesPOS0/6/0/0 (interface) 26 1(interface entry)flags 1 0 40 packets, 0 bytesGigabitEthernet0/6/5/7 (interface) 25 1(interface entry)flags 1 0 447 packets, 1974 bytesGigabitEthernet0/6/5/1 (src mac only) 6 1 ipv400000000000000000c015cb80800mtu: 1500, flags 1 0 1222195 packets, 19973644 bytesGigabitEthernet0/6/5/2 (src mac only) 5 1 ipv400000000000000000c02c9d60800mtu: 1500, flags 1 0 1222251 packets, 19978582 bytesGigabitEthernet0/6/5/6 (interface) 24 1(interface entry)flags 1 0 40 packets, 0 bytesGigabitEthernet0/6/5/5 (interface) 23 1(interface entry)flags 1 0 40 packets, 0 bytesGigabitEthernet0/6/5/4 (interface) 22 1(interface entry)flags 1 0 40 packets, 0 bytesGigabitEthernet0/6/5/3 (interface) 21 1(interface entry)flags 1 0 40 packets, 0 bytesGigabitEthernet0/6/5/2 (interface) 20 1(interface entry)flags 1 0 412001 packets, 2155986 bytesGigabitEthernet0/6/5/1 (interface) 19 1(interface entry)flags 1 0 410803 packets, 1717298 bytesGigabitEthernet0/6/5/0 (interface) 18 1(interface entry)flags 1 0 40 packets, 0 bytesPOS0/6/0/3 (interface) 32 1(interface entry)flags 1 0 40 packets, 0 bytesPOS0/6/4/2 (interface) 31 1(interface entry)flags 1 0 40 packets, 0 bytesPOS0/6/0/1 (src mac only) 43 1 ipv40f000800mtu: 4470, flags 1 0 1222207 packets, 17752538 bytesPOS0/6/0/1 point to point 42 2 ipv40f000800mtu: 4470, flags 1 0 00 packets, 0 bytesPOS0/6/0/1 point to point 41 2 mpls0f008847mtu: 4470, flags 1 0 00 packets, 0 bytesPOS0/6/0/2 (interface) 30 1(interface entry)flags 1 0 40 packets, 0 bytesPOS0/6/4/1 (interface) 29 1(interface entry)flags 1 0 40 packets, 0 bytesPOS0/6/0/1 (interface) 28 1(interface entry)flags 1 0 473519 packets, 3019532 bytesPOS0/6/4/6 (src mac only) 48 1 ipv40f000800mtu: 4470, flags 1 0 1222198 packets, 17751798 bytesPOS0/6/4/6 point to point 47 2 ipv40f000800mtu: 4470, flags 1 0 00 packets, 0 bytesPOS0/6/4/6 point to point 46 2 mpls0f008847mtu: 4470, flags 1 0 00 packets, 0 bytesPOS0/6/4/7 (interface) 40 1(interface entry)flags 1 0 40 packets, 0 bytesPOS0/6/4/6 (interface) 39 1(interface entry)flags 1 0 472915 packets, 2918638 bytesPOS0/6/4/5 (src mac only) 45 1 ipv40f000800mtu: 4470, flags 1 0 10 packets, 0 bytesPOS0/6/4/5 point to point 44 2 ipv40f000800mtu: 4470, flags 1 0 00 packets, 0 bytesPOS0/6/4/4 (src mac only) 51 1 ipv40f000800mtu: 4470, flags 1 0 1222198 packets, 17751852 bytesPOS0/6/4/4 point to point 50 2 ipv40f000800mtu: 4470, flags 1 0 00 packets, 0 bytesPOS0/6/4/4 point to point 49 2 mpls0f008847mtu: 4470, flags 1 0 00 packets, 0 bytesPOS0/6/4/5 (interface) 35 1(interface entry)flags 1 0 466317 packets, 1458970 bytesPOS0/6/4/4 (interface) 34 1(interface entry)flags 1 0 472306 packets, 2799786 bytesPOS0/6/4/3 (interface) 33 1(interface entry)flags 1 0 40 packets, 0 bytesGigabitEthernet0/6/5/2 10.16.8.6 11 2 mpls0013c4cba4a200000c02c9d68847mtu: 1500, flags 1 0 00 packets, 0 bytesGigabitEthernet0/6/5/2 10.16.8.6 10 2 ipv40013c4cba4a200000c02c9d60800mtu: 1500, flags 1 0 019693 packets, 1143510 bytesGigabitEthernet0/6/5/1 10.12.20.2 8 2 mpls00156358bc6c00000c015cb88847mtu: 1500, flags 1 0 00 packets, 0 bytesGigabitEthernet0/6/5/1 10.12.20.2 7 2 ipv400156358bc6c00000c015cb80800mtu: 1500, flags 1 0 019806 packets, 1153348 bytesGigabitEthernet0/6/5/7 10.12.40.2 9 2 ipv400156358bc7200000c07fa5e0800mtu: 1500, flags 1 0 00 packets, 0 bytes-------------------------------------------------------------------------------0/4/CPU1-------------------------------------------------------------------------------Interface Address Version Refcount ProtocolSBC2 3 2 ipv6::00000000mtu: 1500, flags 1 0 00 packets, 0 bytes(externally managed adj)Client id : 0x985Client dll : libsvii_adj_pd.dllClient completion function : svii_adj_cmpl_adjSBC2 point to point 2 2 ipv400000000mtu: 1500, flags 1 0 00 packets, 0 bytes(externally managed adj)Client id : 0x985Client dll : libsvii_adj_pd.dllClient completion function : svii_adj_cmpl_adjMgmtEth0/4/CPU1/0 (interface) 1 1(interface entry)flags 1 0 40 packets, 0 bytes-------------------------------------------------------------------------------0/4/CPU0-------------------------------------------------------------------------------Interface Address Version Refcount ProtocolSBC1 8 2 ipv6::00000000mtu: 1500, flags 1 0 00 packets, 0 bytes(externally managed adj)Client id : 0x985Client dll : libsvii_adj_pd.dllClient completion function : svii_adj_cmpl_adjSBC1 point to point 9 2 ipv400000000mtu: 1500, flags 1 0 00 packets, 0 bytes(externally managed adj)Client id : 0x985Client dll : libsvii_adj_pd.dllClient completion function : svii_adj_cmpl_adjMgmtEth0/4/CPU0/0 (interface) 1 1(interface entry)flags 1 0 40 packets, 0 bytes-------------------------------------------------------------------------------0/1/CPU0-------------------------------------------------------------------------------Interface Address Version Refcount ProtocolBundle-POS24 point to point 119 2 mpls0f008847mtu: 4470, flags 80000001 0 500000000 packets, 0 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-Ether28.1 (src mac only) 149 1 ipv4000000000000001563c0b0f68100001d0800mtu: 1500, flags 80000001 0 500000010 packets, 0 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-Ether28.2 (src mac only) 148 1 ipv4000000000000001563c0b0f68100001e0800mtu: 1500, flags 80000001 0 500000010 packets, 0 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-Ether28.3 (src mac only) 147 1 ipv4000000000000001563c0b0f68100001f0800mtu: 1500, flags 80000001 0 500000010 packets, 0 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-Ether28 (src mac only) 146 1 ipv4000000000000001563c0b0f60800mtu: 1500, flags 80000001 0 500000010 packets, 0 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-POS24 (src mac only) 121 1 ipv40f000800mtu: 4470, flags 80000001 0 5000000134 packets, 2712 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-POS24 point to point 120 2 ipv40f000800mtu: 4470, flags 80000001 0 500000002 packets, 106 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjGigabitEthernet0/1/5/1 (src mac only) 13 1 ipv4000000000000001563c0b0f10800mtu: 1500, flags 1 0 1310470 packets, 27909626 bytesGigabitEthernet0/1/5/2 (src mac only) 12 1 ipv4000000000000001563c0b0f20800mtu: 1500, flags 1 0 1310468 packets, 27909354 bytesBundle-Ether28.1 (interface) 139 1(interface entry)flags 80000001 0 5000100466 packets, 3036 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-Ether28.2 (interface) 142 1(interface entry)flags 80000001 0 5000100466 packets, 3036 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-Ether28.3 (interface) 145 1(interface entry)flags 80000001 0 5000100466 packets, 3036 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-Ether28 (interface) 136 1(interface entry)flags 80000001 0 50001004264 packets, 11880 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-POS24 (interface) 118 1(interface entry)flags 80000001 0 5000100410627 packets, 2210404 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjGigabitEthernet0/1/5/7 (interface) 31 1(interface entry)flags 1 0 431063 packets, 3851812 bytesGigabitEthernet0/1/5/6 (interface) 30 1(interface entry)flags 1 0 431327 packets, 3863692 bytesGigabitEthernet0/1/5/5 (interface) 29 1(interface entry)flags 1 0 40 packets, 0 bytesGigabitEthernet0/1/5/4 (interface) 28 1(interface entry)flags 1 0 40 packets, 0 bytesGigabitEthernet0/1/5/3 (interface) 27 1(interface entry)flags 1 0 40 packets, 0 bytesGigabitEthernet0/1/5/2 (interface) 26 1(interface entry)flags 1 0 411579 packets, 2315638 bytesGigabitEthernet0/1/5/1 (interface) 25 1(interface entry)flags 1 0 417686 packets, 3081588 bytesGigabitEthernet0/1/5/0 (src mac only) 14 1 ipv400000000000000000c00393a0800mtu: 1500, flags 1 0 10 packets, 0 bytesGigabitEthernet0/1/5/0 (interface) 24 1(interface entry)flags 1 0 465 packets, 2730 bytesPOS0/1/0/0 (interface) 19 1(interface entry)flags 1 0 40 packets, 0 bytesPOS0/1/4/0 (interface) 18 1(interface entry)flags 1 0 4134452 packets, 7791702 bytesPOS0/1/4/3 (interface) 7 1(interface entry)flags 1 0 40 packets, 0 bytesPOS0/1/0/2 (interface) 22 1(interface entry)flags 1 0 40 packets, 0 bytesPOS0/1/0/1 point to point 95 2 mpls0f008847mtu: 4470, flags 1 0 00 packets, 0 bytesPOS0/1/0/1 (src mac only) 97 1 ipv40f000800mtu: 4470, flags 1 0 136 packets, 2874 bytesPOS0/1/0/1 point to point 96 2 ipv40f000800mtu: 4470, flags 1 0 00 packets, 0 bytesPOS0/1/4/2 (src mac only) 110 1 ipv4ff030021mtu: 4470, flags 1 0 10 packets, 0 bytesPOS0/1/4/2 point to point 109 2 ipv4ff030021mtu: 4470, flags 1 0 00 packets, 0 bytesPOS0/1/4/2 (interface) 3 1(interface entry)flags 1 0 4191172 packets, 2294213 bytesPOS0/1/0/1 (interface) 21 1(interface entry)flags 1 0 4103403 packets, 4243616 bytesPOS0/1/4/1 (interface) 20 1(interface entry)flags 1 0 4123823 packets, 5581162 bytesPOS0/1/0/3 (interface) 23 1(interface entry)flags 1 0 40 packets, 0 bytesGigabitEthernet0/1/5/1 10.14.8.4 56 2 mpls0012da0b9600001563c0b0f18847mtu: 1500, flags 1 0 00 packets, 0 bytesGigabitEthernet0/1/5/1 10.14.8.4 17 2 ipv40012da0b9600001563c0b0f10800mtu: 1500, flags 1 0 035523 packets, 2247965 bytesGigabitEthernet0/1/5/2 10.16.4.6 54 2 mpls0013c4cba4a1001563c0b0f28847mtu: 1500, flags 1 0 00 packets, 0 bytesGigabitEthernet0/1/5/2 10.16.4.6 15 2 ipv40013c4cba4a1001563c0b0f20800mtu: 1500, flags 1 0 035502 packets, 2244864 bytesBundle-Ether28.2 10.12.30.2 152 2 ipv400156358b9f6001563c0b0f68100001e0800mtu: 1500, flags 80000001 0 500000000 packets, 0 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-Ether28.3 10.12.31.2 151 2 ipv400156358b9f6001563c0b0f68100001f0800mtu: 1500, flags 80000001 0 500000000 packets, 0 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-Ether28 10.12.28.2 150 2 ipv400156358b9f6001563c0b0f60800mtu: 1500, flags 80000001 0 500000000 packets, 0 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjBundle-Ether28.1 10.12.29.2 153 2 ipv400156358b9f6001563c0b0f68100001d0800mtu: 1500, flags 80000001 0 500000000 packets, 0 bytes(externally managed adj)Client id : 0x5eeClient dll : libbundlemgr_cmpl_pi.dllClient completion function : bma_cmpl_adjGigabitEthernet0/1/5/0 10.12.16.2 16 2 ipv400156358b9f000000c00393a0800mtu: 1500, flags 1 0 00 packets, 0 bytesRP/0/RP0/CPU0:router# clear adjacency statistics ipv4Related Commands
clear cef ipv4 drops
To clear 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
(Optional) 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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following example shows how to clear IPv4 CEF drop counters for location 0/1/CPU0:
RP/0/RP0/CPU0:router# clear cef ipv4 drops location 0/1/CPU0Node: 0/1/CPU0Clearing CEF Drop StatisticsRelated Commands
clear cef ipv4 exceptions
To clear IPv4 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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following example shows how to clear IPv4 CEF exception packets for all nodes:
RP/0/RP0/CPU0:router# clear cef ipv4 exceptions location 0/1/CPU0Node: 0/1/CPU0Clearing CEF Exception StatisticsRelated Commands
clear cef ipv4 interface bgp-policy-statistics
To clear CEF IPv4 interface BGP policy statistics, use the clear cef ipv4 interface bpg-policy-statistics command in EXEC mode.
clear cef ipv4 interface type instance bpg-policy-statistics
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
This command clears the Border Gateway Protocol (BGP) policy accounting counters for the specified interface.
Task ID
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-statisticsRelated Commands
clear cef ipv4 interface rpf-statistics
To clear CEF IPv4 interface 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
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The clear cef ipv4 interface rpf-statistics command clears the reverse path forwarding (RPF) counters for the specified interface.
Task ID
Examples
The following example shows how to clear IPv4 CEF RPF statistics for location 0/1/CPU0:
RP/0/RP0/CPU0:router# clear cef ipv4 interface pos 0/1/0/0 rpf-statistics location 0/1/CPU0clear cef ipv6 drops
To clear 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
(Optional) 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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following example shows how to clear IPv6 CEF drop counters for all nodes:
RP/0/RP0/CPU0:router# clear cef ipv6 dropsRelated Commands
clear cef ipv6 exceptions
To clear IPv6 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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following example shows how to clear IPv6 CEF exception packets for all nodes:
RP/0/RP0/CPU0:router# clear cef ipv6 exceptionsRelated Commands
clear cef ipv6 interface bgp-policy-statistics
To clear CEF IPv6 interface BGP policy statistics, use the clear cef ipv6 interface bpg-policy-statistics command in EXEC mode.
clear cef ipv6 interface type instance bpg-policy-statistics
Syntax Description
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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-statisticsclear cef ipv6 interface rpf-statistics
To clear 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 instance rpf-statistics [location node-id]
Syntax Description
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The clear cef ipv6 interface rpf-statistics command clears the reverse path forwarding (RPF) counters for the specified interface.
Task ID
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-statisticsipv4 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
Defaults
There is no BGP policy accounting.
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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-accountingSee 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.
Task ID
Examples
The following example shows how to configure BGP policy accounting:
RP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0RP/0/RP0/CPU0:router(config-if)# ipv4 bgp policy accounting output source-accountingRelated Commands
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
Defaults
IPv4 unicast RPF is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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/0RP/0/RP0/CPU0:router(config-if)# ipv4 verify unicast source reachable-via rxThe 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/1RP/0/RP1/CPU0:ios(config-if)# ipv4 verify unicast source reachable-via anyRelated 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
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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-accountingSee 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.
Task ID
Examples
The following example shows how to configure BGP policy accounting:
RP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0RP/0/RP0/CPU0:router(config-if)# ipv6 bgp policy accounting output source-accountingRelated Commands
ipv6 verify unicast source reachable-via any
To enable loose IPv6 unicast Reverse Path Forwarding (RPF) checking, use the ipv6 verify unicast source reachable-via any command in interface configuration mode. To disable loose 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
Defaults
Loose IPv6 unicast RPF is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
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/0RP/0/RP0/CPU0:router(config-if)# ipv6 verify unicast source reachable-via anyRelated 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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
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 forwardingshow adjacency
To display 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
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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/CPU0Interface Address Version Refcount ProtocolPOS0/0/1/2 (src mac only) 6 1 ipv4POS0/0/1/2 point to point 7 100004POS0/0/1/2 (interface) 3 1The 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/CPU0Interface Address Version Refcount ProtocolPOS0/0/0/2 point to point 7 100004 ipv40f000800mtu: 4470, flags 0 0 400000000 packets, 0 bytes0xffffffffThe 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/CPU0Interface Address Version Refcount ProtocolPOS0/3/1/0 10.10.10.1 11 6 ipv4000c86f33d330800453a21c10800mtu: 1500, flags 0 0 400000000 packets, 0 bytes0xffffffffTable 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
•
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.
1 MTU = maximum transmission unit
Related Commands
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
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following sample output is from the show cef ipv4 command:
RP/0/RP0/CPU0:router# show cef ipv4Prefix Next Hop Interface0.0.0.0/0 12.25.0.1 MgmtEth0/RP1/CPU0/00.0.0.0/32 broadcast12.25.0.0/16 attached MgmtEth0/RP1/CPU0/012.25.12.10/32 receive MgmtEth0/RP1/CPU0/012.25.13.12/32 12.25.13.12 MgmtEth0/RP1/CPU0/012.25.16.11/32 12.25.16.11 MgmtEth0/RP1/CPU0/012.25.22.10/32 12.25.22.10 MgmtEth0/RP1/CPU0/012.25.26.10/32 12.25.26.10 MgmtEth0/RP1/CPU0/012.25.41.2/32 12.25.41.2 MgmtEth0/RP1/CPU0/012.25.41.5/32 12.25.41.5 MgmtEth0/RP1/CPU0/012.25.42.5/32 12.25.42.5 MgmtEth0/RP1/CPU0/012.25.44.15/32 12.25.44.15 MgmtEth0/RP1/CPU0/012.25.55.2/32 12.25.55.2 MgmtEth0/RP1/CPU0/012.25.255.255/32 12.25.255.255 MgmtEth0/RP1/CPU0/0224.0.0.0/4 0.0.0.0224.0.0.1/32 0.0.0.0255.255.255.255/32 broadcastTable 10 describes the significant fields shown in the display.
Table 10 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/CPU010.10.10.0/24, version 0, attached, connected, internal 0x40000c01[2] 0x0, (0x59a4fd4c)local adjacency point2pointPrefix 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 0local adjacencyLoad distribution: 0 (refcount 0)Hash OK Interface Address0 Y POS0/2/0/0 point2pointRelated Commands
show cef ipv4 adjacency
To display IPv4 CEF 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]
Syntax Description
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from show cef ipv4 adjacency command:
RP/0/RP1/CPU0:ios# show cef ipv4 adjacency MgmtEth 0/RP1/CPU0/0Display protocol is ipv4Interface Address Type RefcountMg0/RP1/CPU0/0Prefix: 12.25.0.3/32 local 2Adjacency: PT:0x782a2900 12.25.0.3/32Interface: Mg0/RP1/CPU0/0MAC: 00.d0.02.75.ab.fd.00.11.93.ef.e3.50.08.00Interface Type: 0x8, Base Flags: 0x1Dependent adj type: remoteDependent adj intf: Mg0/RP1/CPU0/0Mg0/RP1/CPU0/0Prefix: 0.24.0.32/32 remote 6Adjacency: PT:0x782a2b58Interface: Mg0/RP1/CPU0/0MAC: 28.4e.4f.4e.45.29Interface Type: 0x8, Base Flags: 0x0Table 11 describes the significant fields shown in the display.
Related Commands
show cef ipv4 adjacency hardware
To display IPv4 CEF 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 | remote]}
Syntax Description
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show cef ipv4 adjacency hardware command:
RP/0/RP0/CPU0:router# show cef ipv4 adjacency hardwareInterface Address Type RefcountMg0/RP0/CPU0/0 special 4Interface: Mg0/RP0/CPU0/0 Type: gleanInterface Type: 0x8, Base Flags: 0x4400Dependent adj type: remoteDependent adj intf: Mg0/RP0/CPU0/0Mg0/RP0/CPU0/0Prefix: 64.102.12.47/32 local 3Adjacency: PT:0x78f5c708 64.102.12.47/32Interface: Mg0/RP0/CPU0/0MAC: 00.30.f2.f2.10.38.00.11.93.ef.e8.e6.08.00Interface Type: 0x8, Base Flags: 0x1Dependent adj type: remoteDependent adj intf: Mg0/RP0/CPU0/0Table 12 describes the significant fields shown in the display.
Related Commands
show cef ipv4 drops
To display IPv4 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
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from the show cef ipv4 drops for location command:
RP/0/RP0/CPU0:router# show cef ipv4 dropsCEF Drop StatisticsNode: 0/0/CPU0Unresolved drops packets : 0Unsupported drops packets : 0Null0 drops packets : 0No route drops packets : 0No Adjacency drops packets : 0Checksum error drops packets : 0RPF drops packets : 0RPF suppressed drops packets : 0RP destined drops packets : 0Table 13 describes the significant fields shown in the display.
Table 13 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.
1 RPF = Reverse Path Forwarding
Related Commands
show cef ipv4 exact-route
To display an IPv4 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} [detail | location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output 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 detail0.0.0.0/0, version 432, proxy default, internal 0x2000201[1]Prefix Len 0, traffic index 0, precedence routine (0)via MgmtEth0/RP1/CPU0/0Table 14 describes the significant fields shown in the display.
Table 14 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
Related Commands
show cef ipv4 exceptions
To display IPv4 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
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from the show cef ipv4 exceptions command:
RP/0/RP0/CPU0:router# show cef ipv4 exceptionsCEF Exception StatisticsNode: 0/0/CPU0Slow encap packets : 0Redirect packets : 0Receive packets : 306404Broadcast packets : 0IP options packets : 0TTL expired packets : 0Fragmented packets : 0Node: 0/1/CPU0Slow encap packets : 0Redirect packets : 0Receive packets : 0Broadcast packets : 0IP options packets : 0TTL expired packets : 0Fragmented packets : 0Node: 0/2/CPU0Slow encap packets : 0Redirect packets : 0 Receive packets : 0Broadcast packets : 0IP options packets : 0TTL expired packets : 314Fragmented packets : 0Node: 0/3/CPU0Slow encap packets : 0Redirect packets : 0Receive packets : 0Broadcast packets : 0IP options packets : 0TTL expired packets : 0Fragmented packets : 0Table 15 describes the significant fields shown in the display.
Table 15 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.
1 ICMP = internet control message protocol
2 TTL = time to live
Related Commands
Clears IPv4 CEF exception packet counters.
Clears IPv6 CEF exception packet counters.
show cef ipv4 external hardware
To display information related to IPv4 CEF external clients, use the show cef ipv4 external hardware command in EXEC mode.
show cef [vrf vrf-name] ipv4 external hardare {ingress | detail} location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The show cef ipv4 external hardware command displays every prefix that an external client is interested in as well as the hardware information from the platform.
Task ID
Examples
The following is sample output for the show cef ipv4 external hardare command:
RP/0/RP0/CPU0:router# show cef vrf_1 external hardare ingress location 0/1/0Client Name : l2fib_mgrInterest type : EOS0 LDI updatesPrefix : 3.3.3.3/32Number of notifs : 1State : resolved, mismatch, cached plat context, in retryVia : dropLoad distribution: 0 (refcount 0)Hash OK Interface Address0 Y Unknown dropINGRESS External CLient Load info:Total Recursive Paths 0TLU1 0x00004610 nexthop: 0.0.0.0TLU1 ENTRY 0SW: 0x00000002 00010000 00000000 00000100HW: 0x00000002 00010000 00000000 00000100local: 0x0 drop: 0x1next ptr: 0x00010000num of entries: 1Recursive next-hop: 0.0.0.0Table 16 describes the significant fields shown in the display.
Related Commands
show cef ipv4 hardware
To display IPv4 CEF 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
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show cef ipv4 hardware egress command:
RP/0/RP0/CPU0:router# show cef ipv4 hardware egressPrefix Next Hop Interface0.0.0.0/0 172.29.52.1 <recursive>0.0.0.0/32 broadcast10.1.1.1/32 receive Loopback010.2.2.2/32 10.12.24.2 Bundle-POS2410.6.6.6/32 10.16.8.6 GigabitEthernet0/6/5/210.7.7.7/32 10.12.24.2 Bundle-POS2410.11.11.11/32 10.12.8.2 POS0/1/0/110.12.4.0/24 attached POS0/6/4/510.12.4.0/32 broadcast POS0/6/4/510.12.4.1/32 receive POS0/6/4/510.12.4.255/32 broadcast POS0/6/4/510.12.8.0/24 attached POS0/1/0/110.12.8.0/32 broadcast POS0/1/0/110.12.8.1/32 receive POS0/1/0/110.12.8.255/32 broadcast POS0/1/0/110.12.12.0/24 attached POS0/6/0/1Table 17 describes the significant fields shown in the display.
Related Commands
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] [rpf-statistics] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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/0MgmtEth0/0/CPU0/0 is up (if_handle 0x01000100)Forwarding is enabledICMP redirects are never sentIP MTU 1500, TableId 0xe0000000Reference count 2Table 18 describes the significant fields shown in the display.
Table 18 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 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.
1 ICMP = internet control message protocol
2 MTU = maximum transmission unit
Related Commands
show cef ipv4 interface bgp-policy-statistics
To display IPv4 Cisco Express Forwarding (CEF)-related 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 instance bgp-policy-statistics
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
This command displays all the configured BGP policy counters for the specified interface.
Task ID
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-statisticsTenGigE0/2/0/4 is upInput BGP policy accounting on src IP address enabledbuckets packets bytes0 184054 101577536 65688590 42040697607 65688590 42040697608 65688654 42040738569 65688656 420407398410 65688655 420407392030 32844290 151083734031 32844291 151083738632 32844294 151083752433 32844296 151083761634 32844298 151083770835 32844302 151083789236 32844302 151083789237 32844303 151083793838 32844305 151083803039 32844307 1510838122Output BGP policy accounting on dst IP address enabledbuckets packets bytes0 754 43878Output BGP policy accounting on src IP address enabledbuckets packets bytes0 857 51706Table 19 describes the significant fields shown in the display.
Related Commands
show cef ipv4 non-recursive
To display the IPv4 nonrecursive prefix entries in the IPv4 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
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from the show cef ipv4 non-recursive command:
RP/0/RP0/CPU0:router# show cef ipv4 non-recursivePrefix Next Hop Interface0.0.0.0/0 12.8.0.10.0.0.0/32 broadcast12.8.0.0/16 attached MgmtEth0/0/CPU0/012.8.0.0/32 broadcast MgmtEth0/0/CPU0/012.8.0.1/32 12.8.0.1 MgmtEth0/0/CPU0/012.8.0.2/32 12.8.0.2 MgmtEth0/0/CPU0/012.8.0.3/32 12.8.0.3 MgmtEth0/0/CPU0/012.8.16.10/32 12.8.16.10 MgmtEth0/0/CPU0/012.8.16.30/32 12.8.16.30 MgmtEth0/0/CPU0/012.8.16.40/32 12.8.16.40 MgmtEth0/0/CPU0/012.8.28.8/32 12.8.28.8 MgmtEth0/0/CPU0/012.8.28.101/32 12.8.28.101 MgmtEth0/0/CPU0/012.8.28.103/32 12.8.28.103 MgmtEth0/0/CPU0/012.8.28.104/32 12.8.28.104 MgmtEth0/0/CPU0/012.8.28.106/32 receive MgmtEth0/0/CPU0/012.8.29.113/32 12.8.29.113 MgmtEth0/0/CPU0/012.8.29.118/32 12.8.29.118 MgmtEth0/0/CPU0/012.8.29.140/32 12.8.29.140 MgmtEth0/0/CPU0/012.8.33.101/32 12.8.33.101 MgmtEth0/0/CPU0/012.8.33.103/32 12.8.33.103 MgmtEth0/0/CPU0/012.8.33.105/32 12.8.33.105 MgmtEth0/0/CPU0/012.8.33.110/32 12.8.33.110 MgmtEth0/0/CPU0/012.8.57.1/32 12.8.57.1 MgmtEth0/0/CPU0/012.8.255.255/32 broadcast MgmtEth0/0/CPU0/012.29.31.2/32 12.29.31.2 MgmtEth0/0/CPU0/0223.255.0.0/16 attached MgmtEth0/0/CPU0/0223.255.254.254/32 223.255.254.254 MgmtEth0/0/CPU0/0224.0.0.0/4 0.0.0.0224.0.0.0/24 receiveTable 20 describes the significant fields shown in the display.
Related Commands
show cef ipv4 resources
To display IPv4 CEF resource availability status, use the show cef ipv4 resources command in EXEC mode.
show cef ipv4 resources [detail] [location node-id]
Syntax Description
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from the show cef ipv4 resource command:
RP/0/RP0/CPU0:router# show cef ipv4 resource detailCEF resource availability summary state: GREENipv4 shared memory resource:CurrMode GREEN, CurrUtil 0%CurrAvail 1874526208 bytes, MaxAvail 1875693568 bytesipv6 shared memory resource:CurrMode GREEN, CurrUtil 0%CurrAvail 1874591744 bytes, MaxAvail 1875365888 bytesmpls shared memory resource:CurrMode GREEN, CurrUtil 0%CurrAvail 1874407424 bytes, MaxAvail 1875038208 bytescommon shared memory resource:CurrMode GREEN, CurrUtil 0%CurrAvail 1873215488 bytes, MaxAvail 1874972672 bytesTABLE hardware resource: GREENLEAF hardware resource: GREENLOADINFO hardware resource: GREENNHINFO hardware resource: GREENLABEL_INFO hardware resource: GREENIDB hardware resource: GREENFRR_NHINFO hardware resource: GREENLDSH_ARRAY hardware resource: GREENRSRC_MON hardware resource: GREENTable 21 describes the significant fields shown in the display.
Related Commands
show cef ipv4 summary
To display a summary of the IPv4 CEF table, use the show cef ipv4 summary command in EXEC mode.
show cef [vrf vrf-name] ipv4 summary [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from the show cef ipv4 summary command:
RP/0/RP0/CPU0:router# show cef ipv4 summaryRouter ID is 0.0.0.0IP CEF with switching (Table Version 43)tableid 0xe0000000, vrfid 0x60000000, vrfname unknown, vrid 0x20000000, flags0x134 routes, 0 reresolve, 0 unresolved (0 old, 0 new)0 load sharing elements, 0 bytes, 0 references0 CEF route update drops, 9 revisions of existing leavesResolution Timer: 15s9 prefixes modified in placeAdjacency Table has 26 adjacencies2 incomplete adjacenciesTable 22 describes the significant fields shown in the display.
Related Commands
show cef ipv4 unresolved
To display unresolved routes in the IPv4 CEF table, use the show cef ipv4 unresolved command in EXEC mode.
show cef [vrf vrf-name] ipv4 unresolved [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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 unresolvedPrefix Next Hop Interface3.3.3.3 2.2.2.2 ?Table 23 describes the significant fields shown in the display.
Related Commands
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
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following sample output is from the show cef ipv6 command:
RP/0/RP0/CPU0:router# show cef ipv6::/0::/128drop::1/128loopback66::4/128receive Loopback02222::/64connected POS0/4/0/02222::1/128receive POS0/4/0/03333::/64connected POS0/3/0/03333::2/128receive POS0/3/0/05656::2/128recursive fe80::3031:48ff:fe53:5533, POS0/3/0/07777::/64connected POS0/0/0/07777::2/128receive POS0/0/0/09999::1/128recursive fe80::205:5fff:fe1d:7600, POS0/4/0/0ff00::/8dropff02::1/128receiveff02::2/128receiveff02::5/128receiveff02::6/128receiveff02::1:ff00:0/104receiveTable 24 describes the significant fields shown in the display.
The following sample output is from the show cef ipv6 with the detail keyword:
RP/0/RP0/CPU0:router# show cef ipv6 detail::/0flags: source_ribLoadinfo owner: <this route>fast adj: gleanpath 1:flags :next hop : ::interface : POS0/0/0/0::/128flags: drop, source_fibLoadinfo owner: <this route>fast adj: droppath 1:flags :next hop : ::interface : <not specified>::1/128flags: loopback, source_fibLoadinfo owner: <this route>fast adj: loopbackpath 1:flags :next hop : ::interface : <not specified>66::4/128flags: receive, source_ribLoadinfo owner: <this route>fast adj: receivepath 1:flags : point-to-pointnext hop : ::interface : Loopback0Table 25 describes the significant output fields shown in the display.
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/CPU0101: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, recursivevia 22:6:1::9, 0 dependencies, recursivenext hop 22:6:1::9 via 22:6:1::9/128Load distribution: _ _ _ (refcount 1)Hash OK Interface Address- Y GigabitEthernet0/1/2/1 fe80::250:e2ff:fe8f:8381- Y POS0/1/0/2 ::- Y GigabitEthernet0/1/2/2 fe80::250:e2ff:fe8f:8382Related Commands
show cef ipv6 adjacency
To display IPv6 CEF 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
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from show cef ipv6 adjacency command:
RP/0/RP1/CPU0:ios# show cef ipv6 adjacency MgmtEth 0/RP1/CPU0/0Display protocol is ipv6Interface Address Type RefcountMg0/RP1/CPU0/0Prefix: 12.25.0.3/32 local 2Adjacency: PT:0x782a2900 12.25.0.3/32Interface: Mg0/RP1/CPU0/0MAC: 00.d0.02.75.ab.fd.00.11.93.ef.e3.50.08.00Interface Type: 0x8, Base Flags: 0x1Dependent adj type: remoteDependent adj intf: Mg0/RP1/CPU0/0Mg0/RP1/CPU0/0Prefix: 0.24.0.32/32 remote 6Adjacency: PT:0x782a2b58Interface: Mg0/RP1/CPU0/0MAC: 28.4e.4f.4e.45.29Interface Type: 0x8, Base Flags: 0x0Table 26 describes the significant fields shown in the display.
Related Commands
show cef ipv6 adjacency hardware
To displayIPv6 CEF 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
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show cef ipv6 adjacency hardware command:
RP/0/RP0/CPU0:router# show cef ipv6 adjacency hardwareInterface Address Type RefcountMg0/RP0/CPU0/0 special 4Interface: Mg0/RP0/CPU0/0 Type: gleanInterface Type: 0x8, Base Flags: 0x4400Dependent adj type: remoteDependent adj intf: Mg0/RP0/CPU0/0Mg0/RP0/CPU0/0Prefix: 64.102.12.47/32 local 3Adjacency: PT:0x78f5c708 64.102.12.47/32Interface: Mg0/RP0/CPU0/0MAC: 00.30.f2.f2.10.38.00.11.93.ef.e8.e6.08.00Interface Type: 0x8, Base Flags: 0x1Dependent adj type: remoteDependent adj intf: Mg0/RP0/CPU0/0Table 27 describes the significant fields shown in the display.
Related Commands
show cef ipv6 drops
To display IPv6 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
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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
Task ID
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/CPU0IPv6 CEF Drop StatisticsLine status down ingress : 0 egress : Not ApplicablePacket sanity fail ingress : 0 egress : 0PLU set to drop ingress : 0 egress : 0Unknown type,plu drop ingress : 0 egress : 0Packet length err ingress : 0 egress : 0TCAM src-comp err ingress : 0 egress : 0Table 28 describes the significant fields shown in the display.
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} [detail | location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show cef ipv6 exact-route command:
RP/0/RP0/CPU0:router# show cef ipv6 exact-route 222::2 9999::6751 location0/3/CPU0 source address: 222::2 destination address: 9999::6751interface : TenGigE0/3/0/3 non local interface
Note
Related Commands
Displays the path an IPv4 flow comprising a source and destination address will take.
show cef ipv6 exceptions
To display IPv6 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
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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/CPU0IPv6 CEF Exception StatisticsNode: 0/3/CPU0TTL err ingress : 0 egress : Not ApplicableLink-local dst addr ingress : 0 egress : 0Hop-by-Hop header ingress : 0 egress : 0PLU entry set to punt ingress : 0 egress : 0Packet too big ingress : Not Applicable egress : 0Med priority punt ingress : 0 egress : Not ApplicableTable 29 describes the significant fields shown in the display.
Table 29 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.
1 TTL = time to live
2 MTU = maximum transmission unit
Related Commands
show cef ipv6 external hardware
To display CEF information related to CEF external clients, use the show cef ipv6 external hardware command in EXEC mode.
show cef [vrf vrf-name] ipv6 external hardare {ingress | detail} location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The show cef ipv6 external hardware command displays every prefix that an external client is interested in as well as the hardware information from the platform.
Task ID
Examples
The following is sample output for the show cef ipv6 external hardare command:
RP/0/RP0/CPU0:router# show cef ipv6 vrf_1 external hardare ingress location 0/1/0Client Name : l2fib_mgrInterest type : EOS0 LDI updatesPrefix : 3.3.3.3/32Number of notifs : 1State : resolved, mismatch, cached plat context, in retryVia : dropLoad distribution: 0 (refcount 0)Hash OK Interface Address0 Y Unknown dropINGRESS External CLient Load info:Total Recursive Paths 0TLU1 0x00004610 nexthop: 0.0.0.0TLU1 ENTRY 0SW: 0x00000002 00010000 00000000 00000100HW: 0x00000002 00010000 00000000 00000100local: 0x0 drop: 0x1next ptr: 0x00010000num of entries: 1Recursive next-hop: 0.0.0.0Table 30 describes the significant fields shown in the display.
Related Commands
show cef ipv6 hardware
To display IPv6 CEF 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
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show cef ipv6 hardware egress command:
RP/0/RP0/CPU0:router# show cef ipv6 hardware egressPrefix Next Hop Interface0.0.0.0/0 172.29.52.1 <recursive>0.0.0.0/32 broadcast10.1.1.1/32 receive Loopback010.2.2.2/32 10.12.24.2 Bundle-POS2410.6.6.6/32 10.16.8.6 GigabitEthernet0/6/5/210.7.7.7/32 10.12.24.2 Bundle-POS2410.11.11.11/32 10.12.8.2 POS0/1/0/110.12.4.0/24 attached POS0/6/4/510.12.4.0/32 broadcast POS0/6/4/510.12.4.1/32 receive POS0/6/4/510.12.4.255/32 broadcast POS0/6/4/510.12.8.0/24 attached POS0/1/0/110.12.8.0/32 broadcast POS0/1/0/110.12.8.1/32 receive POS0/1/0/110.12.8.255/32 broadcast POS0/1/0/110.12.12.0/24 attached POS0/6/0/1Table 31 describes the significant fields shown in the display.
Related Commands
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 instance bgp-policy-statistics
Syntax Description
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from the show cef ipv4 interface bgp-policy-statistics command:
RP/0/RP0/CPU0:router# show cef ipv6 interface TenGigE 0/2/0/4 bgp-policy-statisticsTenGigE0/2/0/4 is upInput BGP policy accounting on src IP address enabledbuckets packets bytes0 184054 101577536 65688590 42040697607 65688590 42040697608 65688654 42040738569 65688656 420407398410 65688655 420407392030 32844290 151083734031 32844291 151083738632 32844294 151083752433 32844296 151083761634 32844298 151083770835 32844302 151083789236 32844302 151083789237 32844303 151083793838 32844305 151083803039 32844307 1510838122Output BGP policy accounting on dst IP address enabledbuckets packets bytes0 754 43878Output BGP policy accounting on src IP address enabledbuckets packets bytes0 857 51706Table 32 describes the significant fields shown in the display.
Related Commands
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 instance [detail] [rpf-statistics] [location node-id]
Syntax Description
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from the show cef ipv6 interface command:
RP/0/RP0/CPU0:router# show cef ipv6 interface MgmtEth 0/RP0/CPU0/0MgmtEth0/0/CPU0/0 is up (if_handle 0x01000100)Forwarding is enabledICMP redirects are never sentIP MTU 1500, TableId 0xe0000000Reference count 2Table 33 describes the significant fields shown in the display.
Table 33 show cef ipv6 interface Field Descriptions
MgmtEth 0/RP0/CPU0/0 is up
Status of the interface.
if_handle
Internal interface handle.
Forwarding is enabled
Indicates that 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.
1 ICMP = internet control message protocol
2 MTU = maximum transmission unit
Related Commands
show cef ipv6 non-recursive
To display the nonrecursive prefix entries in the IPv6 CEF table, use the show cef ipv6 non-recursive command in EXEC mode.
show cef [vrf vrf-name] ipv6 non-recursive [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from the show cef ipv6 non-recursive command:
RP/0/RP0/CPU0:router# show cef ipv6 non-recursive::/0::/128drop::1/128loopback66::4/128receive Loopback02222::/64connected POS0/4/0/02222::1/128receive POS0/4/0/03333::/64connected POS0/3/0/03333::2/128receive POS0/3/0/07777::/64connected POS0/0/0/07777::2/128receive POS0/0/0/0ff00::/8dropff02::1/128receiveff02::2/128receiveff02::5/128receiveff02::6/128receiveff02::1:ff00:0/104receiveTable 34 describes the significant fields shown in the display.
Related Commands
show cef ipv6 resources
To display IPv6 CEF resource availability status, use the show cef ipv6 resources command in EXEC mode.
show cef ipv6 resources [ detail ] [location node-id]
Syntax Description
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from the show cef ipv6 resource command:
RP/0/RP0/CPU0:router# show cef ipv6 resourceCEF resource availability summary state: GREENipv4 shared memory resource: GREENipv6 shared memory resource: GREENmpls shared memory resource: GREENcommon shared memory resource: GREENTABLE hardware resource: GREENLEAF hardware resource: GREENLOADINFO hardware resource: GREENNHINFO hardware resource: GREENLABEL_INFO hardware resource: GREENIDB hardware resource: GREENFRR_NHINFO hardware resource: GREENLDSH_ARRAY hardware resource: GREENRSRC_MON hardware resource: GREEN
Note
Related Commands
show cef ipv6 summary
To display a summary of the IPv6 CEF table, use the show cef ipv6 summary command in EXEC mode.
show cef [vrf vrf-name] ipv6 summary [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from the show cef ipv6 summary command:
RP/0/RP0/CPU0:router# show cef ipv6 summaryIPv6 CEF with switching (Table Version 0)9 routes, 0 background, 0 pending, 0 unresolved paths9 load sharing elements, 324 bytes, 9 references3384 bytes fib leaf memoryRouter ID is 0.0.0.0Adjacency Table has 15 adjacencies2 incomplete adjacenciesTable 35 describes the significant fields shown in the display.
Related Commands
show cef ipv6 unresolved
To display the unresolved routes in the IPv6 CEF table, use the show cef ipv6 unresolved command in EXEC mode.
show cef [vrf vrf-name] ipv6 unresolved [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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 unresolved9999::/64unresolvedTable 36 describes the significant fields shown in the display.
Table 36 show cef ipv6 unresolved Field Descriptions
xxxx::/xx
Detected unresolved route.
Related Commands
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] [location node-id]
Syntax Description
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
This following is sample output from show cef mpls adjacency command:
RP/0/RP0/CPU0:router# show cef mpls adjacencyDisplay protocol is mplsInterface Address Type RefcountBP24 Prefix: 0/0 local 10no next-hop adjInterface: NoneMac-length is 0incompleteInterface Type: 0x1d, Base Flags: 0x100Dependent adj type: remoteDependent adj intf: BP24Related 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
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
This following is sample output from show cef mpls unresolved command:
RP/0/RP0/CPU0:router# show cef mpls unresolvedLabel/EOS Next Hop InterfaceRelated 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
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
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 0Prefix Next Hop Interface0.0.0.0/0 drop default handler0.0.0.0/32 broadcast224.0.0.0/24 receive255.255.255.255/32 broadcastTable 37 describes the significant fields shown in the display.
Table 37 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.
