Cisco IOS XR Troubleshooting, Release 3.4
Troubleshooting Forwarding
Downloads: This chapterpdf (PDF - 291.0KB) The complete bookPDF (PDF - 1.93MB) | Feedback

Troubleshooting Forwarding

Table Of Contents

Troubleshooting Forwarding

Troubleshooting IPv4 CEF Information

Troubleshooting Adjacency Information

Examples

Troubleshooting Control Plane Information

Examples


Troubleshooting Forwarding


Cisco Express Forwarding (CEF) is the mechanism that enables packet forwarding. CEF information is examined when data forwarding is not occurring as expected. Troublshooting CEF involves comparing the Routing Information Base (RIB) information to the software Forwarding Information Base (FIB), verifying that the hardware is programmed correctly, verifying that the adjacencies are built correctly, verifying that the control plane is built correctly, and gathering any necessary trace information.

The only prerequisite for CEF is a valid route in the RIB.

This chapter describes techniques that you can use to troubleshoot router forwarding. It includes the following sections:

Troubleshooting IPv4 CEF Information

Troubleshooting Adjacency Information

Troubleshooting Control Plane Information

Troubleshooting IPv4 CEF Information

CEF is an advanced, Layer 3 IP switching technology optimizing network performance and scalability for networks with large and dynamic traffic patterns, such as the Internet, on networks characterized by intensive web-based applications, or interactive sessions.

Information conventionally stored in a route cache is stored in several data structures for CEF switching. The data structures provide optimized lookup for efficient packet forwarding. The two main components of CEF operation are forwarding information base (FIB) and adjacency tables:

CEF uses a FIB to make IP destination prefix-based switching decisions. FIB maintains a mirror image of the forwarding information contained in the IP routing table. When routing or topology changes occur in the network, the IP routing table is updated, and those changes are reflected in the FIB. The FIB maintains next hop address information based on the information in the IP routing table. There is a one-to-one correlation between FIB entries and routing table entries, therefore FIB contains all known routes and eliminates the need for route cache maintenance that is associated with switching paths such as fast switching and optimum switching.

Nodes in the network are said to be adjacent if they can reach each other with a single hop across a link layer. In addition to the FIB, CEF uses adjacency tables to prepend Layer 2 addressing information. The adjacency table maintains Layer 2 next-hop addresses for all FIB entries.

Figure 1 provides an overview of the components involved in contributing information to the CEF process and displays the interaction between the software and hardware elements of the CEF process.

Figure 1 CEF Process

To troubleshoot IPv4 CEF information on Cisco IOS XR software, perform the following procedure.

SUMMARY STEPS

1. show route ipv4 prefix mask

2. show cef ipv4 prefix mask detail

3. show cef ipv4 prefix mask detail location node-id (on ingress line card)

4. show cef ipv4 prefix mask detail location node-id (on egress line card)

5. show cef ipv4 prefix mask hardware ingress detail location node-id

6. show cef ipv4 prefix mask hardware egress detail location node-id

7. show cef ipv4 interface type instance location node-id

8. show cef ipv4 summary location node-id

9. show cef ipv4 trace location node-id

10. show cef platform trace ipv4 all location node-id

11. Contact Cisco Technical Support if the problem is not resolved

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show route ipv4 prefix mask

Example:

RP/0/RP0/CPU0:router# show route 192.168.2.0 255.255.255.0

Displays the current routes in the Routing Information Base (RIB).

Check the prefix and mask, as well as the next hop and outgoing interface, to ensure that they are what is expected.

Note the timer value that shows how long the route has been in the routing table. If the timer value is low the route may be flapping.

A lower timer value is present when a route is installed in the RIB for a short period of time. A low timer value may indicate flapping. For example, if a BGP route was being installed and removed from the RIB table every sixty seconds, then the route is flapping.

Look for routes that have not been installed in the routing table for very long. The route will either be stable or flapping. If the route is flapping, contact contact Cisco Technical Support. For Cisco Technical Support contact information, see the "Obtaining Technical Assistance" section in the Preface.

Check that route is learned via the routing protocol you are expecting it to be known via, and that the metric is what you expect.

Step 2 

show cef ipv4 prefix mask detail

Example:

RP/0/RP0/CPU0:router# show route ipv4 192.168.2.0 255.255.255.0 detail

Displays the IPv4 Cisco Express Forwarding (CEF) table detailed entry information.

Compare the prefix, mask, next hop ip, and outgoing interface information with the information in the RIB. The information in the RIB is displayed using the show route ipv4 prefix mask command.

Check that the adjacency is valid or the expected type of adjacency. For example, if it is a remote adjacency, then the adjacency information exists on another node.

Check that the expected hash (load balance) and egress interfaces are listed.

Step 3 

show cef ipv4 prefix mask detail location node-id

Example:

RP/0/RP0/CPU0:router# show cef ipv4 192.168.2.0 255.255.255.0 detail location 0/14/cpu0

Displays the IPv4 CEF table for the designated ingress node.

Compare the prefix, mask, next hop ip, and outgoing interface information with the information in the RIB. The information in the RIB is displayed using the show route ipv4 prefix mask command.

Check that the adjacency is valid or the expected type of adjacency. For example, if it is a remote adjacency, then the adjacency information exists on another node.

Check that the expected hash (load balance) and egress interfaces are listed.

Step 4 

show cef ipv4 prefix mask detail location node-id

Example:

RP/0/RP0/CPU0:router# show cef ipv4 192.168.2.0 255.255.255.0 detail location 0/13/cpu0

Displays the IPv4 CEF table for the designated egress node.

Compare the prefix, mask, next hop ip, and outgoing interface information with the information in the RIB. The information in the RIB is displayed using the show route ipv4 prefix mask command.

Check that the adjacency is valid or the expected type of adjacency. For example, if it is a remote adjacency, then the adjacency information exists on another node.

Check that the expected hash (load balance) and egress interfaces are listed.

Step 5 

show cef ipv4 prefix mask hardware ingress detail location node-id

Example:

RP/0/RP0/CPU0:router# show cef ipv4 192.168.2.0 255.255.255.0 hardware ingress detail location 0/14/cpu0

Displays the IPv4 CEF table for the designated ingress node.

Check that the prefix and mask are valid.

Check the nexthop IP address is as expected

Check that the entry type is set to forward.

Check that the hardware and software representations in hex format match. For example:

SW: 0x0c000000 00000020 00000000 00000000
HW: 0x0c000000 00000020 00000000 00000000

Step 6 

show cef ipv4 prefix mask hardware egress detail location node-id

Example:

RP/0/RP0/CPU0:router# show cef ipv4 192.168.2.0 255.255.255.0 hardware detail egress location 0/13/cpu0

Displays the IPv4 CEF table for the designated egress node.

Check that the prefix and mask are valid.

Check the nexthop IP address is as expected

Check that the entry type is set to forward.

Check that the hardware and software representations in hex format match. For example:

SW: 0x0c000000 00000020 00000000 00000000
HW: 0x0c000000 00000020 00000000 00000000

Step 7 

show cef ipv4 interface type instance location node-id

Example:
RP/0/RP0/CPU0:router# show cef ipv4 interface 
tengige 1/3/0/7 location 1/3/cpu0

Displays IPv4 CEF-related information for an interface.

Verify that the interface handle "interface is marked" is as expected. The command output also shows how many references there are to the interface in the CEF table and the IPv4 maximum transmission unit (MTU).

Use this command for the ingress and egress interfaces.

Step 8 

show cef ipv4 summary location node-id

Example:
RP/0/RP0/CPU0:router# show cef ipv4 summary 
location 0/3/cpu0

Displays a summary of the IPv4 CEF table. Check the VPN routing and forwarding (VRF) names associated with the node, the route update drops, and that there are the expected number of incomplete adjacencies.

Note the number of routes that CEF has entries for, the number of load sharing elements, and the number of references to this node.

Use this command for the ingress and egress line cards and route processor (RP).

Step 9 

show cef ipv4 trace location node-id

Example:
RP/0/RP0/CPU0:router# show cef ipv4 trace 
location 0/3/cpu0

Displays IPv4 CEF trace table information.

Use this command for the RP, and ingress and egress interfaces for the local line card.

Step 10 

show cef platform trace ipv4 all location node-id

Example:
RP/0/RP0/CPU0:router# show cef platform trace 
ipv4 all location 0/3/cpu0

Displays CEF IPv4 hardware status and configuration trace table information.

Use this command for the ingress and egress interfaces for the local line card.

Step 11 

Contact Cisco Technical Support.

If the problem is not resolved, contact Cisco Technical Support. For Cisco Technical Support contact information, see the "Obtaining Technical Assistance" section in the Preface.

Troubleshooting Adjacency Information

To troubleshoot adjacency information on Cisco IOS XR software, perform the following procedure.

SUMMARY STEPS

1. show arp location node-id

2. show arp traffic location node-id

3. show adjacency interface-type interface-instance remote detail location node-id

4. show adjacency interface-type interface-instance remote detail hardware location node-id

5. show adjacency ipv4 nexthop ipv4-address detail location node-id

6. show adjacency interface-type interface-instance detail location node-id

7. show adjacency ipv4 nexthop ipv4-address detail hardware location node-id

8. show adjacency interface-type interface-instance detail hardware location node-id

9. show adjacency trace location node-id

10. show adjacency trace client aib-client location node-id

11. show adjacency hardware trace location node-id

12. Contact Cisco Technical Support if the problem is not resolved

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show arp location node-id

Example:
RP/0/RP0/CPU0:router# show arp location 
0/12/cpu0

Displays the Address Resolution Protocol (ARP) for an egress line card with a broadcast interface.

Verify that the Layer 2 address of the next-hop IP address and the Layer 2 address of the interface are correct in the MAC layer rewrite in the adjacency for Ethernet interfaces.

Step 2 

show arp traffic location node-id

Example:
RP/0/RP0/CPU0:router# show arp traffic location 
0/12/cpu0

Displays ARP traffic statistics for an egress line card with a broadcast interface.

Step 3 

show adjacency interface-type interface-instance remote detail location node-id

Example:
RP/0/RP0/CPU0:router# show adjacency pos 
0/13/0/2 remote detail location 0/14/cpu0

Displays detailed CEF adjacency table information for a remote ingress line card.

Ensure that the output shows IPv4 adjacency information and that an adjacency exists.

Step 4 

show adjacency interface-type interface-instance remote detail hardware location node-id

Example:
RP/0/RP0/CPU0:router# show adjacency pos 
0/13/0/2 remote detail hardware location 
0/14/cpu0

Displays adjacency information for a remote ingress line card.

Check that the prefix and mask are valid.

Check that the table lookup (TLU) pointers match the TLU pointers in the show cef ipv4 prefix mask hardware ingress detail location node-id command.

Step 5 

show adjacency ipv4 nexthop ipv4-address detail location node-id

Example:
RP/0/RP0/CPU0:router# show adjacency ipv4 
nexthop 192.168.2.0 detail location 0/12/cpu0

Displays adjacencies on an egress line card with a broadcast interface that are destined to the specified IPv4 next hop.

When an egress interface is broadcast, use the show adjacency ipv4 nexthop command to display the adjacency information.

Compare the MAC layer rewrite information that shows the destination Layer 2 address in the first part followed by the source Layer 2 address, and the Ethernet value with the output from the show arp location node-id command.

Step 6 

show adjacency interface-type interface-instance detail location node-id

Example:
RP/0/RP0/CPU0:router# show adjacency pos 
0/13/0/2 detail location 0/13/cpu0

Displays CEF adjacency table information for an egress line card with a point to point interface.

There should be two IPv4 entries in the command output. Ensure both entries exist.

The src mac only entry is used for multicast switching

The point to point entry is used for unicast switching.

On broadcast interfaces you will have a src mac only and one for each nexthop IP address. Please note the MTU is for the Ipv4 minus the layer 2 header. Use the show im chains command to display MTU details.

Step 7 

show adjacency ipv4 nexthop ipv4-address detail hardware location node-id

Example:
RP/0/RP0/CPU0:router# show adjacency ipv4 
nexthop 192.168.2.0 detail hardware location 
0/12/cpu0

Displays the hardware programming associated with the adjacency. Verify that the packets are being switched in the hardware.

Step 8 

show adjacency interface-type interface-instance detail hardware location node-id

Example:
RP/0/RP0/CPU0:router# show adjacency pos 
0/13/0/2 detail hardware location 0/13/cpu0

Displays the hardware programming information for a point-to-point interface such as the Packet-over-SONET/SDH (POS) interface. The rewrite information is slightly different, because there is no MAC rewrite string as there is in Ethernet.

Verify that the rewrite is appropriate for the encapsulation on the interface.

Step 9 

show adjacency trace location node-id

Example:
RP/0/RP0/CPU0:router# show adjacency trace 
location 0/13/cpu0

Displays CEF adjacency trace table information.

Use this command for the egress interfaces for the local line card.

Step 10 

show adjacency trace client aib-client location node-id

Example:
RP/0/RP0/CPU0:router# show adjacency trace 
client ipv4_fib_mgr location 0/13/cpu0

Displays CEF adjacency trace table information for a specified Adjacency Information Base (AIB) client.

Use this command for the egress interfaces for the local line card.

Step 11 

show adjacency hardware trace location node-id

Example:
RP/0/RP0/CPU0:router# show adjacency hardware 
trace location 0/13/cpu0

Displays CEF adjacency hardware trace table information.

Use this command for the egress interfaces for the local line card.

Step 12 

Contact Cisco Technical Support.

If the problem is not resolved, contact Cisco Technical Support. For Cisco Technical Support contact information, see the "Obtaining Technical Assistance" section in the Preface.

Examples

The following example shows that the TLU pointers match. The TLU pointers are indicated in bold.

RP/0/RP0/CPU0:router# show cef 192.168.36.224/30 hardware ingress location 0/0/CPU0 
 
   
192.168.36.224/30, version 1536, internal 0x42040001[1] 
.
.
.
TLU2 0x0101041d
       TLU2 ENTRY        0
        SW: 0x00000000 00000000 00000000 00a22800
        HW: 0x00000000 00000000 00000000 00a22800
       label1:            0    label2:            0
       num of labels:     0    next ptr: 0x0000a228
 
   
RP/0/RP0/CPU0:router# show adjacency pos 0/4/0/15 remote detail hardware location 0/0/CPU0
.
.
.
ingress adjacency
  TLU3            : 0x200a228
  [HW: 0x00400000 0x00000000 0x00000000 0x00082800]
    num. entries  : 1
    num. labels   : 0
    label 1       : 0
    label 2       : 0
    next ptr      : 0x828
  TLU4            : 0x3000828
    Entry[0]
    [HW: 0x00000000 0x11410000 0x01480600 
 
   

The following example shows that the address information matches. The addresses are indicated in bold.

RP/0/RP0/CPU0:router# show arp location 0/1/cpu0
 
   
Address         Age        Hardware Addr   State      Type  Interface
192.168.50.157   02:08:34   0016.c761.f509  Dynamic    ARPA  TenGigE0/1/0/2
                                            
RP/0/RP0/CPU0:router# show adjacency ipv4 nexthop 212.27.50.157 detail loccation 0/1/cpu0
 
   
Interface                   Address                 Version  Refcount  Protocol
TenGigE0/1/0/2              192.168.50.157                41         2     ipv4
                           0016c761f5090015fa9959890800
                           mtu: 1500, flags 0 0 0
                           2894 packets, 156876 bytes
                           0xffffffff

Troubleshooting Control Plane Information

To troubleshoot control plane information on Cisco IOS XR software, perform the following procedure.

SUMMARY STEPS

1. show netio idb interface-type interface-instance location node-id

2. show uidb index

3. show uidb data interface-type interface-instance location node-id

4. show im chains interface-type interface-instance location node-id

5. show imds interface brief

6. show tbm hardware ipv4 unicast dual detail location node-id

7. Contact Cisco Technical Support if the problem is not resolved

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show netio idb interface-type interface-instance location node-id

Example:
RP/0/RP0/CPU0:router# show netio idb 
tengige0/0/0/0 location 0/0/cpu0

Displays control plane information for the software switching path. The output provides useful statistics for determining software forwarding issues.

Verify the encap and decap paths.

Ensure that all of the appropriate steps in the chain are shown for all the features that may be enabled on the interface.

Note Fixup is a direct pointer to a routine in the output path after a CEF rewrite. this is an optimized path if a CEF rewrite exists and can be used.

Verify that the ifhandle and global uidb values are correct.

Use this command for the ingress and egress interfaces for the local line card.

Step 2 

show uidb index

Example:

RP/0/RP0/CPU0:router# show uidb index

Displays the micro-interface descriptor block (IDB) index assigned by the software.

Check that the interface and the universal interface descriptor block (UIDB) value are what is expected.

Compare the IDB index to the UIDB index value in the show adjacency ipv4 interface-type interface-instance detail hardware location node-id command output.

Step 3 

show uidb data interface-type interface-instance location node-id

Example:
RP/0/RP0/CPU0:router# show uidb data tengige 
1/3/0/0 location 0/3/cpu0

Displays, from a software perspective, features that are enabled on a selected interface.

Check the UIDB value.

Check which flags are enabled for the UIDB.

Check the ifhandle in the UIDB to make sure that it is correct.

Compare the output to the configuration of the interface and expected features.

Use this command for the ingress and egress interfaces for the local line card.

Step 4 

show im chains interface-type interface-instance location node-id

Example:
RP/0/RP0/CPU0:router# show im chains pos 
0/14/0/0 location 0/14/cpu0

or

RP/0/RP0/CPU0:router# show im chains pos 
0/13/0/2 location 0/13/cpu0

Displays the output of the control plane encapsulations for data plane forwarding.

Check the different layers for the interface, the status (up or down) of each layer, and the maximum transmission unit (MTU) at each layer.

Verify the ifhandle value that the ingress line card will use to forward packets that are destined out of the interface.

Compare the output to the expected encapsulations on the interface, the correct MTU values, and the correct ifhandle value from the show cef ipv4 interface command output.

Use this command for the ingress interface on the ingress line card and the egress interface on egress line card.

Step 5 

show imds interface brief

Example:
RP/0/RP0/CPU0:router# show imds interface brief

Displays interface manager distribution server (IMDS) interface information.

Note This is just a partial output not full output.

Check the state, MTU, encapsulation being used, and the ifhandle for each interface.

Step 6 

show tbm hardware ipv4 unicast dual detail location node-id

Example:
RP/0/RP0/CPU0:router# show tbm hardware ipv4 
unicast dual detail location 0/13/cpu0

or

RP/0/RP0/CPU0:router# show tbm hardware ipv4 
unicast dual detail location 0/14/cpu0

Displays tree bitmap hardware-related ingress and egress information.

Check if there have been any failures in the different stages of the lookup.

Use this command for the ingress and egress interfaces for the local line card.

Step 7 

Contact Cisco Technical Support.

If the problem is not resolved, contact Cisco Technical Support. For Cisco Technical Support contact information, see the "Obtaining Technical Assistance" section in the Preface.

Examples

The following example displays the control plane information for the software switching path:

RP/0/RP0/CPU0:router# show netio idb tenGigE 0/1/1/0 location 0/1/cpu0 
 
   
TenGigE0/1/1/0 (handle: 0x01180020, nodeid:0x11) netio idb:
---------------------------------
name:                    TenGigE0_1_1_0
interface handle:        0x01180020
interface global index:  2
physical media type:     30
dchain ptr:              <0x482ae8e0>
echain ptr:              <0x482d791c>
fchain ptr:              <0x482d79b8>
driver cookie:           <0x4824ad58>
driver func:             <0x4824ad44>
number of subinterfaces: 4096
subblock array size:     3
DSNCNF:                  0x00000000
interface stats info: 
   IN  unknown proto pkts:  0
   IN  unknown proto bytes: 0
   IN  multicast pkts:      0
   OUT multicast pkts:      0
   IN  broadcast pkts:      0
   OUT broadcast pkts:      0
   IN  drop pkts:           0
   OUT drop pkts:           0
   IN  errors pkts:         0
   OUT errors pkts:         0
 
   
Chains
--------------------
Base decap chain: 
     ether                <30>  <0xfd7aef88, 0x48302824>  <       0,        0>
 
   
Protocol chains:
---------------
<Protocol number> (name)  Stats
  Type  Chain_node       <caps num>  <function, context> <drop pkts, drop bytes>
<7> (arp)   Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes
    Encap: 
     l2_adj_rewrite       <86>  <0xfcec7a88, 0x4834efec>  <       0,        0>
     queue_fifo           <56>  <0xfcedda68, 0x482dbee4>  <       0,        0>
     txm_nopull           <60>  <0xfcea2a5c, 0x482dc11c>  <       0,        0>
    Decap: 
     queue_fifo           <56>  <0xfcedda4c, 0x482dbee4>  <       0,        0>
     arp                  <24>  <0xfd1082cc, 0x00000000>  <       0,        0>
    Fixup: 
     l2_adj_rewrite       <86>  <0xfcec745c, 0x00000000>  <       0,        0>
     queue_fifo           <56>  <0xfcedda68, 0x482dbee4>  <       0,        0>
     txm_nopull           <60>  <0xfcea2a5c, 0x482dc11c>  <       0,        0>
<12> (ipv4)   Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes
    Encap: 
     ipv4                 <26>  <0xfd10f41c, 0x482d7724>  <       0,        0>
     ether                <30>  <0xfd7aeb44, 0x48302824>  <       0,        0>
     l2_adj_rewrite       <86>  <0xfcec7a88, 0x4834f104>  <       0,        0>
     queue_fifo           <56>  <0xfcedda68, 0x482dbee4>  <       0,        0>
     txm_nopull           <60>  <0xfcea2a5c, 0x482dc11c>  <       0,        0>
    Decap: 
     queue_fifo           <56>  <0xfcedda4c, 0x482dbee4>  <       0,        0>
     ipv4                 <26>  <0xfd10f474, 0x00000000>  <       0,        0>
    Fixup: 
     l2_adj_rewrite       <86>  <0xfcec745c, 0x00000000>  <       0,        0>
     queue_fifo           <56>  <0xfcedda68, 0x482dbee4>  <       0,        0>
     txm_nopull           <60>  <0xfcea2a5c, 0x482dc11c>  <       0,        0>
<22> (ether_sock)   Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes
    Encap: 
     ether_sock           <98>  <0xfd7b1630, 0x48302824>  <       0,        0>
     l2_adj_rewrite       <86>  <0xfcec7a88, 0x48304c1c>  <       0,        0>
     queue_fifo           <56>  <0xfcedda68, 0x482dbee4>  <       0,        0>
     txm_nopull           <60>  <0xfcea2a5c, 0x482dc11c>  <       0,        0>
    Decap: 
     queue_fifo           <56>  <0xfcedda4c, 0x482dbee4>  <       0,        0>
     ether_sock           <98>  <0xfd7b1874, 0x48302824>  <       0,        0>
    Fixup: 
     l2_adj_rewrite       <86>  <0xfcec745c, 0x00000000>  <       0,        0>
     queue_fifo           <56>  <0xfcedda68, 0x482dbee4>  <       0,        0>
     txm_nopull           <60>  <0xfcea2a5c, 0x482dc11c>  <       0,        0>
 
   
Protocol SAFI counts:
--------------------
 
   
       Protocol        SAFI       Pkts In    Bytes In    Pkts Out   Bytes Out
---------------  ----------    ----------  ----------  ----------  ----------
           ipv4     Unicast             0           0           0           0
           ipv4   Multicast             0           0           0           0
           ipv4   Broadcast             0           0           0           0
           ipv6     Unicast             0           0           0           0
           ipv6   Multicast             0           0           0           0
 
   

The following example shows that the micro-idb index value is 12:

RP/0/RP0/CPU0:router# show uidb index tengige1/3/0/6.30 location 1/3/cpu0 
 
   
------------------------------------------------------------------------------
  Location Interface-name      Interface-Type   Ingress-index  Egress-index
---------------------------------------------------------------------------
  1/3/CPU0 TenGigE1_3_0_6.30   Sub-interface       20               12
 
   

Comparing the IDB index value of 12 in the show uidb index command to the UIDB index value in the following command output shows that the values are the same.

RP/0/RP0/CPU0:router# show adjacency ipv4 tengige1/3/0/6.30 detail hardware location 
1/3/cpu0 
 
   
Interface                   Address                 Version  Refcount  Protocol
TenGigE1/3/0/6.30           (src mac only)               90         1     ipv4
                           000000000000001243602d8b8100001e0800
                           mtu: 1500, flags 1 0 1
                           453 packets, 42582 bytes
                           453 hw-only-packets, 42582 hw-only-bytes
 ether egress adjacency
  TLU1            : 0x4407
  [HW: 0x00401862 0xc4170800 0x8100001e 0x01060700]
    num. entries  : 1
    uidb index    : 12
    counter msb   : 0x2
    counter lsb   : 0xc417
    vlan e or len : 0x800
    ether len     : 0x8100 (33024)
    vlan info     : 30
    next ptr      : 0x10607
 
   

The following example displays, from a software perspective, features that are enabled on a selected interface. Compare the output to the configuration of the interface and expected features.

RP/0/RP0/CPU0:router# show uidb data tengige 0/1/1/0 location 0/1/cpu0 
 
   
--------------------------------------------------------------------------
  Location = 0/1/CPU0
  Ifname/Ifhandle = TenGigE0_1_1_0
  Index = 2
  Pse direction = INGRESS
 
   
  General 16 bytes:
  -----------------
  IFHANDLE: 0x118002
  STATUS: 1
  IPV4 ENABLE: 1
  IPV6 ENABLE: 0
  MPLS ENABLE: 0
  STATS POINTER: 0x2c408
  SPRAYER QUEUE: 33
  IPV4 MULTICAST: 0
  IPV6 MULTICAST: 0
  USE TABLE ID IPV4: 0
  USE TABLE ID IPV6: 0
  USE TABLE ID MPLS: 0
  TABLE ID: 0
  QOS ENABLE: 0
  QOS ID: 0
  NETFLOW SAMPLING PERIOD: 0
  L2 PKT DROP: 0
  L2 QOS ENABLE: 0
  SRC FWDING: 0
  *BUNDLE IFHANDLE: 0
  *TUNNEL IFHANDLE: 0
  *L2 ENCAP: 3
 
   
  * Not programmed in hardware
 
   
  IPv4 and MPLS 16 bytes:
  -----------------------
  IPV4 ICMP PUNT: 1
  IPV4 NETFLOW SAMPLING ENABLE: 0
  IPV4 BGP POLICY ACCOUNTING: 0
  IPV4 BGP POLICY ACCOUNTING SRC: 0
  IPV4 BGP POLICY ACCOUNTING DST: 0
  IPV4 BGP POLICY ACCOUNTING STATS POINTER: 0x0
  IPV4 ACL COUNT: 0
  IPV4 ACL ENABLE: 0
  IPV4 ACL ID: 0
  IPV4 ACL TTL PRESENT: 0
  IPV4 RPF CHECK: 0
  IPV4 RPF ALLOW SELF PING: 0
  IPV4 RPF ALLOW DEFAULT: 0
  IPV4 RPF STRICT: 0
  IPV4 SRC LOOKUP NEEDED: 0
  MPLS NETFLOW SAMPLING ENABLE: 0
  IPV4 MPLS UIDB TLU EXTENSION: 0
  TLU POINTER TO UTI HDR: 0
 
   
  IPv6 16 bytes:
  --------------
  IPV6 ICMP PUNT: 1
  IPV6 NETFLOW SAMPLING ENABLE: 0
  IPV6 BGP POLICY ACCOUNTING: 0
  IPV6 BGP POLICY ACCOUNTING SRC: 0
  IPV6 BGP POLICY ACCOUNTING DST: 0
  IPV6 BGP POLICY ACCOUNTING STATS POINTER: 0x0
  IPV6 ACL COUNT: 0
  IPV6 ACL ENABLE: 0
  IPV6 ACL ID: 0
  IPV6 MULTICAST BOUNDARY ACL: 0
  IPV6 RPF CHECK: 0
  IPV6 RPF ALLOW SELF PING: 0
  IPV6 RPF ALLOW DEFAULT: 0
  IPV6 RPF STRICT: 0
  IPV6 SRC LOOKUP NEEDED: 0
  IPV6 EFFECTIVE UIDB INDEX: 0
 
   
  IPV4 MCAST EXTN 16 bytes:
  -------------------------
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff 
--------------------------------------------------------------------------
  Location = 0/1/CPU0
  Ifname/Ifhandle = TenGigE0_1_1_0
  Index = 2
  Pse direction = EGRESS
 
   
  General 16 bytes:
  -----------------
  IFHANDLE: 0x118002
  LINE STATUS DOWN: 0
  STATS POINTER: 0x2c401
  USE TABLE ID IPV4: 0
  USE TABLE ID IPV6: 0
  USE TABLE ID MPLS: 0
  TABLE ID: 0
  L2 QOS ENABLE: 0
  QOS ENABLE: 0
  QOS ID: 0
  NETFLOW SAMPLING PERIOD: 0
  STATUS: 1
  *BUNDLE IFHANDLE: 0
  *TUNNEL IFHANDLE: 0
 
   
  * Not programmed in hardware
 
   
  IPv4 and MPLS 16 bytes:
  -----------------------
  IPV4 ICMP PUNT: 1
  IPV4 NETFLOW SAMPLING ENABLE: 0
  IPV4 BGP POLICY ACCOUNTING: 0
  IPV4 BGP POLICY ACCOUNTING SRC: 0
  IPV4 BGP POLICY ACCOUNTING DST: 0
  IPV4 BGP POLICY ACCOUNTING STATS POINTER: 0x0
  IPV4 ACL COUNT: 0
  IPV4 ACL ENABLE: 0
  IPV4 ACL ID: 0
  IPV4 ACL TTL PRESENT: 0
  IPV4 MULTICAST BOUNDARY ACL: 0
  IPV4 MULTICAST TTL: 0
  MPLS NETFLOW SAMPLING ENABLE: 0
  IPV4 MPLS UIDB TLU EXTENSION: 0
  SRC MAC: 0015.6358.b99c
 
   
  IPv6 16 bytes:
  --------------
  IPV6 ICMP PUNT: 1
  IPV6 NETFLOW SAMPLING ENABLE: 0
  IPV6 BGP POLICY ACCOUNTING: 0
  IPV6 BGP POLICY ACCOUNTING SRC: 0
  IPV6 BGP POLICY ACCOUNTING DST: 0
  IPV6 BGP POLICY ACCOUNTING STATS POINTER: 0x0
  IPV6 ACL COUNT: 0
  IPV6 ACL ENABLE: 0
  IPV6 ACL ID: 0
  IPV6 MULTICAST BOUNDARY ACL: 0
  IPV6 MULTICAST TTL: 0
  SRC MAC: 0015.6358.b99c