Table Of Contents
Cisco Express Forwarding Commands on Cisco IOS XR Software
cef load-balancing fields
clear adjacency statistics
clear cef ipv4 drops
clear cef ipv4 exceptions
clear cef ipv4 interface bgp-policy-statistics
clear cef ipv4 interface rpf-statistics
clear cef ipv6 drops
clear cef ipv6 exceptions
clear cef ipv6 interface bgp-policy-statistics
clear cef ipv6 interface rpf-statistics
ipv4 bgp policy accounting
ipv4 bgp policy propagation
ipv4 verify unicast source reachable-via
ipv6 bgp policy accounting
ipv6 verify unicast source reachable-via
rp mgmtethernet forwarding
show adjacency
show cef
show cef summary
show cef ipv4
show cef ipv4 adjacency
show cef ipv4 adjacency hardware
show cef ipv4 drops
show cef ipv4 exact-route
show cef ipv4 exceptions
show cef ipv4 hardware
show cef ipv4 interface
show cef ipv4 interface bgp-policy-statistics
show cef ipv4 non-recursive
show cef ipv4 resource
show cef ipv4 summary
show cef ipv4 unresolved
show cef ipv6
show cef ipv6 adjacency
show cef ipv6 adjacency hardware
show cef ipv6 drops
show cef ipv6 exact-route
show cef ipv6 exceptions
show cef ipv6 hardware
show cef ipv6 interface
show cef ipv6 interface bgp-policy-statistics
show cef ipv6 interface rpf-statistics
show cef ipv6 non-recursive
show cef ipv6 resource
show cef ipv6 summary
show cef ipv6 unresolved
show cef mpls adjacency
show cef mpls adjacency hardware
show cef mpls interface
show cef mpls unresolved
show cef vrf
Cisco Express Forwarding Commands on Cisco IOS XR Software
This chapter describes the commands used to configure and monitor Cisco Express Forwarding (CEF) on Cisco IOS XR software.
For detailed information about CEF concepts, configuration tasks, and examples, see Cisco IOS XR IP Addresses and Services Configuration Guide.
cef load-balancing fields
To select the hashing algorithm that is used for load balancing during forwarding, use the cef load-balancing fields command in global configuration mode. To undo a configuration and to default to the load balancing option of L3, use the no form of this command.
cef load-balancing fields {L3 | L4}
no cef load-balancing fields {L3 | L4}
Syntax Description
L3
|
Specifies the Layer 3 load-balancing for the hash algorithm that is based on the following fields:
• Source IP address—Specifies the source IP address field in the IP packet header.
• Destination IP address—Specifies the destination IP address in the IP packet header.
• Router ID—Specifies the unique IP address that is assigned to the router.
Since L3 is configured as the default value, you do not need to use the cef load-balancing fields command unless you want to configure Layer 4.
|
L4
|
Specifies the Layer 3 and Layer 4 load-balancing for the hash algorithm that is based on the following fields:
• Source IP address—Specifies the source IP address field in the IP packet header.
• Destination IP address—Specifies the destination IP address in the IP packet header.
• Source port—Specifies the value of the source port field in the TCP, UDP, or SCP packet header for Layer 4.
• Destination port—Specifies the value of the destination port field in the TCP, UDP, or SCP packet header for Layer 4.
• Router ID—Specifies the unique IP address that is assigned to the router.
• Protocol—Specifies the value of the protocol field as specified in the IP packet header for Layer 4.
• Ingress interface—Specifies the interface that is received from the packet for Layer 4.
|
Defaults
When the router ID, source, and destination IP address fields are selected for load balancing, the default value is L3.
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 3.6.0
|
This command was introduced on the Cisco CRS-1.
|
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.
You can undo only a Layer 4 configuration.
Per-flow load-balancing allows incoming data traffic on a router to be evenly distributed over multiple equal-cost connections. On the Cisco CRS-1, per-flow load-balancing is the only load-balancing algorithm that is used to perform Layer 2 and Layer 3 load-balancing decisions on IPv4, IPv6, and Multiprotocol Label Switching (MPLS) flows in the system.
The existing 3-tuple hash provides good-balancing for packet flows with different Layer 3 information (for example, source and destination IP addresses). However, this hash algorithm performs well for cases in which different packet flows, which are identified by Layer 4 content, contain the same Layer 3 packet information. For example, a network, which uses Port Address Translation (PAT) on one end of the network, distributes traffic to a content provider on the other end of the network that supports redundant access using the same IP address. With the Cisco CRS-1 router in the core network, the existing 3-tuple hash causes the packet flow to always flow through one path in the system; therefore, poor load-balancing across the equal cost paths occurs.
A new hash algorithm, which uses additional Layer 4 information from the Layer 3 packet, is needed to provide improved load-balancing support in the system. On the Cisco CRS-1, the 7-tuple hash algorithm is implemented to provide improved load-balancing. The following inputs are processed:
•
Layer 3 information
•
Source IP address
•
Destination IP address
•
Protocol
•
Layer 4 information
•
Source port
•
Destination port
•
Cisco CRS-1 router-related information
•
Router ID
•
Ingress interface bundle
Note
The treatment is different for IPv4 and IPv6 fragmented packets that are fragmented on the router for various reasons. For example, the fragmented packets can originate at the router or they can arrive at the router with a size larger than the maximum transmission unit (MTU). Therefore, the 7-tuple load balancing is done on the whole packet, and fragmentation is done later so that all fragments can go on the same interface.
Task ID
Task ID
|
Operations
|
ipv4
|
read, write
|
Examples
The following example shows how to configure Layer 3 and Layer 4 load-balancing for the hash algorithm from the cef load-balancing fields command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# cef load-balancing fields L4
The following example shows sample output that displays summary information for the CEF table from the show cef summary command:
RP/0/RP0/CPU0:router# show cef summary
IP CEF with switching (Table Version 0) for node0_RP0_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286242
286122 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20600784 bytes
11124 load sharing elements, 3014696 bytes, 297064 references
8 shared load sharing elements, 3008 bytes
11116 exclusive load sharing elements, 3011688 bytes
0 CEF route update drops, 3900571 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 15 adjacencies
The following example shows sample output that displays summary information for all locations from the show cef summary command:
RP/0/RP0/CPU0:router# show cef summary location all
IP CEF with switching (Table Version 0) for node0_0_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286202
286110 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20599920 bytes
11112 load sharing elements, 3012008 bytes, 297064 references
8 shared load sharing elements, 3008 bytes
11104 exclusive load sharing elements, 3009000 bytes
0 CEF route update drops, 2864666 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 1 adjacency
IP CEF with switching (Table Version 0) for node0_0_CPU1
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286202
286110 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20599920 bytes
11112 load sharing elements, 3012008 bytes, 297064 references
8 shared load sharing elements, 3008 bytes
11104 exclusive load sharing elements, 3009000 bytes
0 CEF route update drops, 2864666 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 1 adjacency
IP CEF with switching (Table Version 0) for node0_1_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286228
286112 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20600064 bytes
11114 load sharing elements, 3590384 bytes, 297064 references
8 shared load sharing elements, 3424 bytes
11106 exclusive load sharing elements, 3586960 bytes
0 CEF route update drops, 4076380 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 77 adjacencies
22 incomplete adjacencies
IP CEF with switching (Table Version 0) for node0_2_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286202
286110 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20599920 bytes
11112 load sharing elements, 3012008 bytes, 297064 references
8 shared load sharing elements, 3008 bytes
11104 exclusive load sharing elements, 3009000 bytes
0 CEF route update drops, 2864666 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 1 adjacency
IP CEF with switching (Table Version 0) for node0_2_CPU1
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286202
286110 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20599920 bytes
11112 load sharing elements, 3012008 bytes, 297064 references
8 shared load sharing elements, 3008 bytes
11104 exclusive load sharing elements, 3009000 bytes
0 CEF route update drops, 2864666 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 1 adjacency
IP CEF with switching (Table Version 0) for node0_3_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286204
286110 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20599920 bytes
11111 load sharing elements, 3589556 bytes, 297062 references
7 shared load sharing elements, 3148 bytes
11104 exclusive load sharing elements, 3586408 bytes
0 CEF route update drops, 4076376 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 21 adjacencies
12 incomplete adjacencies
IP CEF with switching (Table Version 0) for node0_RP0_CPU0
Tableid 0xe0000000, Vrfid 0x60000000, Vrid 0x20000000, Flags 0x301
Vrfname default, Refcount 286242
286122 routes, 0 reresolve, 0 unresolved (0 old, 0 new), 20600784 bytes
11124 load sharing elements, 3014696 bytes, 297064 references
8 shared load sharing elements, 3008 bytes
11116 exclusive load sharing elements, 3011688 bytes
0 CEF route update drops, 4075013 revisions of existing leaves
0 prefixes modified in place
0 prefixes with label imposition, 11032 prefixes with label information Adjacency Table
has 15 adjacencies
Related Commands
Command
|
Description
|
bundle-hash
|
Displays the path a bundle flow that comprises a source and destination address would take. For more information, see Cisco IOS XR Interface and Hardware Component Command Reference.
|
show cef
|
Displays information about packets forwarded by Cisco Express Forwarding (CEF).
|
show cef summary
|
Displays summary information for the Cisco Express Forwarding (CEF) table.
|
show cef ipv4 exact-route
|
Displays an IPv4 Cisco Express Forwarding (CEF) exact route.
|
show cef ipv4 summary
|
Displays a summary of the IPv4 Cisco Express Forwarding (CEF) table
|
show cef ipv6 exact-route
|
Displays the path an IPv6 flow comprising a source and destination address would take.
|
show cef ipv6 summary
|
Displays a summary of the IPv6 Cisco Express Forwarding (CEF) table.
|
show mpls forwarding exact-route
|
Displays the path an MPLS flow that comprises a source and destination address would take. For more information, see Cisco IOS XR Multiprotocol Label Switching Command Reference.
|
clear adjacency statistics
To clear adjacency packet and byte counter statistics, use the clear adjacency statistics command in EXEC mode.
clear adjacency statistics [ipv4 [nexthop ipv4-address] | mpls | ipv6] [interface-type
interface-instance | location node-id]
Syntax Description
ipv4
|
(Optional) Clears only IPv4 adjacency packet and byte counter statistics.
|
nexthop ipv4-address
|
(Optional) Clears adjacency statistics that are destined to the specified IPv4 nexthop.
|
mpls
|
(Optional) Clears only MPLS adjacency statistics.
|
ipv6
|
(Optional) Clears only IPv6 adjacency statistics.
|
interface-type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
(Optional) Either a physical interface instance or a virtual interface instance:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash mark between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
location node-id
|
(Optional) Clears detailed adjacency statistics for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
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
Task ID
|
Operations
|
basic-services
|
read, write
|
cef
|
read, write
|
Examples
The following example displays sample output of the Cisco Express Forwarding (CEF) adjacency table information, and clears the IPv4 CEF adjacency statistics:
RP/0/RP0/CPU0:router# show adjacency detail
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
MgmtEth0/RP1/CPU0/0 (src mac only) 1 1 ipv4
000000000000001193efe8fe0800
MgmtEth0/RP1/CPU0/0 (interface) 2 1
MgmtEth0/RP1/CPU0/0 172.29.52.77 29 2 ipv4
001193efe8e2001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.105 19 2 ipv4
001b2a4e53e5001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.241 18 2 ipv4
001819d18c38001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.173 15 2 ipv4
0015c75f09f8001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.81 9 2 ipv4
001a6c40d89c001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.1 6 2 ipv4
0030f2f21038001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.201 3 2 ipv4
00107b3c6847001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.96 23 2 ipv4
0018ba800c80001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.168 22 2 ipv4
00503ee3dd80001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.152 21 2 ipv4
00503ee3df40001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.180 16 2 ipv4
0015c75f0800001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.28 12 2 ipv4
00127fd6ba09001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.76 7 2 ipv4
001193efe8ea001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.200 4 2 ipv4
00107b3c689f001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.83 26 2 ipv4
001a6c40d89c001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.151 25 2 ipv4
000a41052e01001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.91 17 2 ipv4
0018742c5f40001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.127 14 2 ipv4
0013c4cba200001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.27 11 2 ipv4
00127fd6ba08001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.75 8 2 ipv4
001193efe8e2001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.182 27 2 ipv4
0015c75f0800001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.150 24 2 ipv4
000a41052da1001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.90 20 2 ipv4
001874163f80001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.70 13 2 ipv4
5a5900000201001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.82 10 2 ipv4
00127fd6bc36001193efe8fe0800
MgmtEth0/RP1/CPU0/0 172.29.52.126 5 2 ipv4
0013c4cba548001193efe8fe0800
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
MgmtEth0/RP0/CPU0/0 (src mac only) 2 1 ipv4
0000000000005a59000002010800
MgmtEth0/RP0/CPU0/0 (interface) 1 1
MgmtEth0/RP0/CPU0/0 172.29.52.77 38 2 ipv4
001193efe8e25a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.105 29 2 ipv4
001b2a4e53e55a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.241 28 2 ipv4
001819d18c385a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.173 24 2 ipv4
0015c75f09f85a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.81 19 2 ipv4
001a6c40d89c5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.13 16 2 ipv4
001079e960385a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.153 15 2 ipv4
00e0b0552cc45a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.121 13 2 ipv4
0012da0b97ff5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.1 6 2 ipv4
0030f2f210385a59000002010800
257909 packets, 9246567 bytes
MgmtEth0/RP0/CPU0/0 172.29.52.201 4 2 ipv4
00107b3c68475a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.96 32 2 ipv4
0018ba800c805a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.168 31 2 ipv4
00503ee3dd805a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.152 30 2 ipv4
00503ee3df405a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.180 25 2 ipv4
0015c75f08005a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.28 22 2 ipv4
00127fd6ba095a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.76 17 2 ipv4
001193efe8ea5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.52 14 2 ipv4
0090929c88485a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.148 12 2 ipv4
00b064fce0bb5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.120 10 2 ipv4
00042892c7ff5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.200 5 2 ipv4
00107b3c689f5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.83 35 2 ipv4
001a6c40d89c5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.151 34 2 ipv4
000a41052e015a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.91 27 2 ipv4
0018742c5f405a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.127 23 2 ipv4
0013c4cba2005a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.27 21 2 ipv4
00127fd6ba085a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.75 18 2 ipv4
001193efe8e25a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.51 11 2 ipv4
00e04f5fe0685a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.71 3 2 ipv4
001193efe8fe5a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.182 36 2 ipv4
0015c75f08005a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.150 33 2 ipv4
000a41052da15a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.90 26 2 ipv4
001874163f805a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.82 20 2 ipv4
00127fd6bc365a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.50 9 2 ipv4
0090929cf8685a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.190 8 2 ipv4
00000c4775e05a59000002010800
MgmtEth0/RP0/CPU0/0 172.29.52.126 7 2 ipv4
0013c4cba5485a59000002010800
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
GigabitEthernet0/6/5/7 (src mac only) 4 1 ipv4
00000000000000000c07fa5e0800
POS0/6/4/0 (interface) 27 1
POS0/6/0/0 (interface) 26 1
GigabitEthernet0/6/5/7 (interface) 25 1
GigabitEthernet0/6/5/1 (src mac only) 6 1 ipv4
00000000000000000c015cb80800
222195 packets, 19973644 bytes
GigabitEthernet0/6/5/2 (src mac only) 5 1 ipv4
00000000000000000c02c9d60800
222251 packets, 19978582 bytes
GigabitEthernet0/6/5/6 (interface) 24 1
GigabitEthernet0/6/5/5 (interface) 23 1
GigabitEthernet0/6/5/4 (interface) 22 1
GigabitEthernet0/6/5/3 (interface) 21 1
GigabitEthernet0/6/5/2 (interface) 20 1
12001 packets, 2155986 bytes
GigabitEthernet0/6/5/1 (interface) 19 1
10803 packets, 1717298 bytes
GigabitEthernet0/6/5/0 (interface) 18 1
POS0/6/0/3 (interface) 32 1
POS0/6/4/2 (interface) 31 1
POS0/6/0/1 (src mac only) 43 1 ipv4
222207 packets, 17752538 bytes
POS0/6/0/1 point to point 42 2 ipv4
POS0/6/0/1 point to point 41 2 mpls
POS0/6/0/2 (interface) 30 1
POS0/6/4/1 (interface) 29 1
POS0/6/0/1 (interface) 28 1
73519 packets, 3019532 bytes
POS0/6/4/6 (src mac only) 48 1 ipv4
222198 packets, 17751798 bytes
POS0/6/4/6 point to point 47 2 ipv4
POS0/6/4/6 point to point 46 2 mpls
POS0/6/4/7 (interface) 40 1
POS0/6/4/6 (interface) 39 1
72915 packets, 2918638 bytes
POS0/6/4/5 (src mac only) 45 1 ipv4
POS0/6/4/5 point to point 44 2 ipv4
POS0/6/4/4 (src mac only) 51 1 ipv4
222198 packets, 17751852 bytes
POS0/6/4/4 point to point 50 2 ipv4
POS0/6/4/4 point to point 49 2 mpls
POS0/6/4/5 (interface) 35 1
66317 packets, 1458970 bytes
POS0/6/4/4 (interface) 34 1
72306 packets, 2799786 bytes
POS0/6/4/3 (interface) 33 1
GigabitEthernet0/6/5/2 10.16.8.6 11 2 mpls
0013c4cba4a200000c02c9d68847
GigabitEthernet0/6/5/2 10.16.8.6 10 2 ipv4
0013c4cba4a200000c02c9d60800
19693 packets, 1143510 bytes
GigabitEthernet0/6/5/1 10.12.20.2 8 2 mpls
00156358bc6c00000c015cb88847
GigabitEthernet0/6/5/1 10.12.20.2 7 2 ipv4
00156358bc6c00000c015cb80800
19806 packets, 1153348 bytes
GigabitEthernet0/6/5/7 10.12.40.2 9 2 ipv4
00156358bc7200000c07fa5e0800
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
Client dll : libsvii_adj_pd.dll
Client completion function : svii_adj_cmpl_adj
SBC2 point to point 2 2 ipv4
Client dll : libsvii_adj_pd.dll
Client completion function : svii_adj_cmpl_adj
MgmtEth0/4/CPU1/0 (interface) 1 1
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
Client dll : libsvii_adj_pd.dll
Client completion function : svii_adj_cmpl_adj
SBC1 point to point 9 2 ipv4
Client dll : libsvii_adj_pd.dll
Client completion function : svii_adj_cmpl_adj
MgmtEth0/4/CPU0/0 (interface) 1 1
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Address Version Refcount Protocol
Bundle-POS24 point to point 119 2 mpls
mtu: 4470, flags 80000001 0 50000000
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28.1 (src mac only) 149 1 ipv4
000000000000001563c0b0f68100001d0800
mtu: 1500, flags 80000001 0 50000001
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28.2 (src mac only) 148 1 ipv4
000000000000001563c0b0f68100001e0800
mtu: 1500, flags 80000001 0 50000001
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28.3 (src mac only) 147 1 ipv4
000000000000001563c0b0f68100001f0800
mtu: 1500, flags 80000001 0 50000001
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28 (src mac only) 146 1 ipv4
000000000000001563c0b0f60800
mtu: 1500, flags 80000001 0 50000001
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-POS24 (src mac only) 121 1 ipv4
mtu: 4470, flags 80000001 0 50000001
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-POS24 point to point 120 2 ipv4
mtu: 4470, flags 80000001 0 50000000
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
GigabitEthernet0/1/5/1 (src mac only) 13 1 ipv4
000000000000001563c0b0f10800
310470 packets, 27909626 bytes
GigabitEthernet0/1/5/2 (src mac only) 12 1 ipv4
000000000000001563c0b0f20800
310468 packets, 27909354 bytes
Bundle-Ether28.1 (interface) 139 1
flags 80000001 0 50001004
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28.2 (interface) 142 1
flags 80000001 0 50001004
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28.3 (interface) 145 1
flags 80000001 0 50001004
Client dll : libbundlemgr_cmpl_pi.dll
Client completion function : bma_cmpl_adj
Bundle-Ether28 (interface