IP Addresses and Services Configuration Guide for Cisco NCS 6000 Series Routers, Release 5.0.x

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

IP Addresses and Services Configuration Guide for Cisco NCS 6000 Series Routers, Release 5.0.x

Chapter Title

Implementing Cisco Express Forwarding

Results

Updated:
December 1, 2017

Chapter: Implementing Cisco Express Forwarding

Implementing Cisco Express Forwarding

Cisco Express Forwarding (CEF) is advanced, Layer 3 IP switching technology. CEF optimizes 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.


Note

For complete descriptions of the CEF commands listed in this module, refer to the Related Documents section of this module. To locate documentation for other commands that might appear in the course of executing a configuration task, search online in the master command index.

Feature History for Implementing CEF

Release

Modification

Release 5.0.0

This feature was introduced.

Release 5.0.1

Support for Loose and Strict uRPF was added.

Prerequisites for Implementing Cisco Express Forwarding

The following prerequisites are required to implement Cisco Express Forwarding:

  • You must be in a user group associated with a task group that includes the proper task IDs. The command reference guides include the task IDs required for each command. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Information About Implementing Cisco Express Forwarding Software

To implement Cisco Express Forwarding features in this document you must understand the following concepts:

Key Features Supported in the Cisco Express Forwarding Implementation

The following features are supported for CEF on Cisco IOS XR software:

  • Multipath support

  • High availability features such as packaging, restartability, and Out of Resource (OOR) handling

  • OSPFv2 SPF prefix prioritization

  • BGP attributes download

Benefits of CEF

CEF offers the following benefits:

  • Improved performance—CEF is less CPU-intensive than fast-switching route caching. More CPU processing power can be dedicated to Layer 3 services such as quality of service (QoS) and encryption.

  • Scalability—CEF offers full switching capacity at each line card.

  • Resilience—CEF offers an unprecedented level of switching consistency and stability in large dynamic networks. In dynamic networks, fast-switched cache entries are frequently invalidated due to routing changes. These changes can cause traffic to be process switched using the routing table, rather than fast switched using the route cache. Because the Forwarding Information Base (FIB) lookup table contains all known routes that exist in the routing table, it eliminates route cache maintenance and the fast-switch or process-switch forwarding scenario. CEF can switch traffic more efficiently than typical demand caching schemes.

CEF Components

Cisco IOS XR softwareCEF always operates in CEF mode with two distinct components: a Forwarding Information Base (FIB) database and adjacency table—a protocol-independent adjacency information base (AIB).

CEF is a primary IP packet-forwarding database for Cisco IOS XR software. CEF is responsible for the following functions:

  • Software switching path

  • Maintaining forwarding table and adjacency tables (which are maintained by the AIB) for software and hardware forwarding engines

The following CEF forwarding tables are maintained in Cisco IOS XR software:

  • IPv4 CEF database

  • IPv6 CEF database

  • MPLS LFD database

  • Multicast Forwarding Table (MFD)

The protocol-dependent FIB process maintains the forwarding tables for IPv4 and IPv6 unicast in the ( ) and each MSC.

The FIB on each node processes Routing Information Base (RIB) updates, performing route resolution and maintaining FIB tables independently in the and each MSC. FIB tables on each node can be slightly different. Adjacency FIB entries are maintained only on a local node, and adjacency entries linked to FIB entries could be different.

Reverse Path Forwarding (Strict and Loose)

Unicast IPv4 and IPv6 Reverse Path Forwarding (uRPF), both strict and loose modes, help mitigate problems caused by the introduction of malformed or spoofed IP source addresses into a network by discarding IP packets that lack a verifiable IP source address. Unicast RPF does this by doing a reverse lookup in the CEF table. Therefore, Unicast Reverse Path Forwarding is possible only if CEF is enabled on the router.


Note

Unicast RPF allows packets with 0.0.0.0 source addresses and 255.255.255.255 destination addresses to pass so that Bootstrap Protocol and Dynamic Host Configuration Protocol (DHCP) will function properly.

When strict uRPF is enabled, the source address of the packet is checked in the FIB. If the packet is received on the same interface that would be used to forward the traffic to the source of the packet, the packet passes the check and is further processed; otherwise, it is dropped. Strict uRPF should only be applied where there is natural or configured symmetry. Because internal interfaces are likely to have routing asymmetry, that is, multiple routes to the source of a packet, strict uRPF should not be implemented on interfaces that are internal to the network.


Note

The behavior of strict RPF varies slightly by platform, number of recursion levels, and number of paths in Equal-Cost Multipath (ECMP) scenarios. A platform may switch to loose RPF check for some or all prefixes, even though strict RPF is configured.

When loose uRPF is enabled, the source address of the packet is checked in the FIB. If it exists and matches a valid forwarding entry, the packet passes the check and is further processed; otherwise, it is dropped.

Loose and strict uRPF supports two options: allow self-ping and allow default. The self-ping option allows the source of the packet to ping itself. The allow default option allows the lookup result to match a default routing entry. When the allow default option is enabled with the strict mode of the uRPF, the packet is processed further only if it arrived through the default interface.

Route Processor Management Ethernet Forwarding

Forwarding from the MSC interface to the RP Management Ethernet is disabled by default. The rp mgmtethernet forwarding command is used to enable forwarding from the MSC interface to RP Management Ethernet.

Forwarding from the RP Management Ethernet to the MSC interface, and from the RP Management Ethernet to RP Management Ethernet, is enabled by default.

Per-Flow Load Balancing

Load balancing describes the functionality in a router that distributes packets across multiple links based on Layer 3 (network layer) and Layer 4 (transport layer) routing information. If the router discovers multiple paths to a destination, the routing table is updated with multiple entries for that destination.

Per-flow load balancing performs these functions:

  • Incoming data traffic is evenly distributed over multiple equal-cost connections within a bundle interface.

  • Layer 2 bundle and Layer 3 (network layer) load balancing decisions are taken on IPv4, IPv6, which are supported for the 7-tuple hash algorithm.

  • A 7-tuple hash algorithm provides more granular load balancing than the existing 3-tuple hash algorithm.

  • The same hash algorithm (3-tuple or 7-tuple) is used for load balancing over multiple equal-cost Layer 3 (network layer) paths. The Layer 3 (network layer) path is on a physical interface or on a bundle interface. In addition, load balancing over member links can occur within a Layer 2 bundle interface.

  • The cef load-balancing fields command allows you to select either the 3-tuple hash algorithm (default) or the 7-tuple hash algorithm.

Layer 3 (Network Layer) Routing Information

The 3-tuple load-balance hash calculation contains these Layer 3 (Network Layer) inputs:

  • Source IP address

  • Destination IP address

  • Router ID

The 7-tuple load-balance hash calculation contains 3-tuple inputs and these additional following Layer 4 (Transport Layer) inputs:

Layer 4 (Transport Layer) Routing Information

The 5-tuple load-balance hash calculation contains 3-tuple inputs and these additional following Layer 4 (Transport Layer) inputs:

  • Source port

  • Destination port

  • Protocol


Note

In load-balancing scenarios, a line card may not use all output paths downloaded from routing protocols. This behavior varies with platform, number of recursion levels, and the fact whether MPLS is involved, or not.

BGP Attributes Download

The BGP Attributes Download feature enables you to display the installed BGP attributes in CEF. Configure the show cef bgp-attribute command to display the installed BGP attributes in CEF. You can use the show cef bgp-attribute attribute-id command and the show cef bgp-attribute local-attribute-id command to look at specific BGP attributes by attribute ID and local attribute ID.

GTP Tunnel Load Balancing

GPRS Tunneling Protocol (GTP) is used mainly to deliver mobile data on wireless networks via Cisco NCS Router as core router. When two routers carrying GTP traffic are connected with link bundling, the traffic is required to be distributed evenly between all bundle members. You can use the bundle-hash command in XR EXEC mode to verify that the interface selected within the bundle for load balancing matches with the output from the bundle-hash command.

When two routers carrying GTP traffic are connected with equal-cost multi-path (ECMP) between them, you can use the sh cef exact-route command in XR EXEC mode to verify the interface selected for load balancing.

To achieve load balancing, Cisco NCS router uses 7-tuple load balancing mechanism which takes account of source IP, destination IP, router-id, ingress interface, protocol, L4 source and destination port (if traffic is TCP or UDP) fields from the packet. But for GTP traffic, limited number of unique values for these fields restrict the equal distribution of traffic load on tunnel.

In order to avoid the polarization for GTP traffic in load balancing, a tunnel endpoint identifier (TEID) in GTP header is used instead of UDP port number. Since TEID is unique per tunnel, traffic can be evenly load balanced across multiple links in the bundle.

GTP tunnel load balancing feature adds support for:

  • GTP with IPv4/IPv6 transport header on physical interface

  • GTP traffic over TE tunnel

  • GTPv1-U with UDP port 2152

The cef load-balancing fields L4 command enables the GTP tunnel load balancing.

To know the egress interface for GTP traffic after load balancing, use show cef {ipv4 | ipv6} exact-route command with TEID in place of L4 protocol source and destination port number. Use 16MSBist of TEID in source port and 16LSBits of TEID in destination port.

How to Implement CEF

This section contains instructions for the following tasks:

Verifying CEF

This task allows you to verify CEF.

SUMMARY STEPS

    1.    show cef {ipv4 | ipv6}

    2.    show cef {ipv4 | ipv6} summary

    3.    show cef {ipv4 | ipv6} detail

    4.    show adjacency detail


DETAILED STEPS
     Command or ActionPurpose
    Step 1 show cef {ipv4 | ipv6}


    Example: 
    RP/0/RP0/CPU0:router# show cef ipv4
     

    Displays the IPv4 or IPv6 CEF table. The next hop and forwarding interface are displayed for each prefix.

    Note   

    The output of the show cef command varies by location.

     
    Step 2 show cef {ipv4 | ipv6} summary


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

    Displays a summary of the IPv4 or IPv6 CEF table.

     
    Step 3 show cef {ipv4 | ipv6} detail


    Example: 
    RP/0/RP0/CPU0:router# show cef ipv4 detail
     

    Displays detailed IPv4 or IPv6 CEF table information.

     
    Step 4 show adjacency detail


    Example: 
    RP/0/RP0/CPU0:router# show adjacency detail
     

    Displays detailed adjacency information, including Layer 2 information for each interface.

    Note   

    The output of the show adjacency command varies by location.

     

    Configuring a Route Purge Delay

    This task allows you to configure a route purge delay. A purge delay purges routes when the RIB or other related process experiences a failure.

    SUMMARY STEPS

      1.    configure

      2.    cef purge-delay seconds

      3.    commit


    DETAILED STEPS
       Command or ActionPurpose
      Step 1 configure
              		 
      Step 2 cef purge-delay seconds


      Example: 
      RP/0/RP0/CPU0:router(config)# cef purge-delay 180
       

      Configures a delay in purging routes when the Routing Information Base (RIB) or other related processes experience a failure.

       
      Step 3 commit
              		 

      Configuring Unicast RPF Checking

      This task allows you to configure unicast Reverse Path Forwarding (uRPF) checking. Unicast RPF checking allows you 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.

      SUMMARY STEPS

        1.    configure

        2.    interface type interface-path-id

        3.    ipv4 verify unicast source reachable-via {any | rx} [allow-default] [allow-self-ping]

        4.    commit


      DETAILED STEPS
         Command or ActionPurpose
        Step 1 configure
                  		 
        Step 2 interface type interface-path-id


        Example: 
        RP/0/RP0/CPU0:router(config)# interface TenGigE 0/1/0/0
         

        Enters interface configuration mode.

         
        Step 3 ipv4 verify unicast source reachable-via {any | rx} [allow-default] [allow-self-ping]


        Example: 
        RP/0/RP0/CPU0:router(config-if)# ipv4 verify unicast source reachable-via rx
         

        Enables IPv4 uRPF checking.

        • The rx keyword enables strict unicast RPF checking. If strict unicast RPF is enabled, a packet is not forwarded unless its source prefix exists in the routing table and the output interface matches the interface on which the packet was received.

        • The allow-default keyword enables the matching of default routes. This option applies to both loose and strict RPF.

        • The allow-self-ping keyword enables the router to ping out an interface. This option applies to both loose and strict RPF.

         
        Step 4 commit
                  		 

        Configuring Modular Services Card-to-Route Processor Management Ethernet Interface Switching

        This task allows you to enable MSC-to-RP management Ethernet interface switching.

        SUMMARY STEPS

          1.    configure

          2.    rp mgmtethernet forwarding

          3.    commit


        DETAILED STEPS
           Command or ActionPurpose
          Step 1 configure
                      		 
          Step 2 rp mgmtethernet forwarding


          Example: 
          RP/0/RP0/CPU0:router(config)# rp mgmtethernet forwarding
           

          Enables switching from the MSC to the route processor Management Ethernet interfaces.

           
          Step 3 commit
                      		 

          Configuring Per-Flow Load Balancing

          This section describes the following tasks to configure per-flow load balancing:

          Configuring a 7-Tuple Hash Algorithm

          This task allows you to configure per-flow load balancing for a 7-tuple hash algorithm.

          SUMMARY STEPS

            1.    configure

            2.    cef load-balancing fields {L3 | L4}

            3.    commit

            4.    show cef {ipv4 | ipv6} summary [location node-id]


          DETAILED STEPS
             Command or ActionPurpose
            Step 1 configure
                          		 
            Step 2 cef load-balancing fields {L3 | L4}


            Example: 
            RP/0/RP0/CPU0:router(config)# cef load-balancing fields L4
             

            Configures the hashing algorithm that is used for load balancing during forwarding. The example shows that the L4 field is selected.

            • Use the L3 keyword to specify the Layer 3 load-balancing for the hash

              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.

            • Use the L4 keyword to specify the Layer 3 and Layer 4 load-balancing for the hash algorithm.

            For a list of the inputs for Layer 3 and Layer 4, see Per-Flow Load Balancing.

             
            Step 3 commit
                          		 
            Step 4 show cef {ipv4 | ipv6} summary [location node-id]


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

            Displays the load balancing field for the IPv4 or IPv6 CEF table.

            • (Optional) Use the location keyword display a summary of the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation

             

            Verifying the CEF Exact Route with 7-Tuple Parameters

            The following 7-tuple parameters are specified to obtain the CEF exact route for both IPv4 and IPv6:

            • Source address

            • Destination address

            • Source port and range of destination ports

            • Protocol

            • Ingress interface

            • Router ID

            To display the path an MPLS flow would take, use the

            SUMMARY STEPS

              1.    Configure parallel interfaces between back-to-back routers.

              2.    Create route traffic streams so that there is a stream placed onto each configured interface.

              3.    Use the show cef ipv4 exact-route command in XR EXEC mode to verify that the interface selected for load balancing matches with the output from this command. The following example shows the exact route for the Layer 4 information:

              4.    Configure Equal Cost Multipath Protocol (ECMP) interfaces, for example, between back-to-back routers.

              5.    Create route traffic streams so that there is a stream placed onto each configured interface.

              6.    Use the show cef ipv6 exact-route command in XR EXEC mode to verify that the interface selected for load balancing matches with the output from this command. The following example shows the exact route for the Layer 4 information:


            DETAILED STEPS
              Step 1   Configure parallel interfaces between back-to-back routers.
              Step 2   Create route traffic streams so that there is a stream placed onto each configured interface.
              Step 3   Use the show cef ipv4 exact-route command in XR EXEC mode to verify that the interface selected for load balancing matches with the output from this command. The following example shows the exact route for the Layer 4 information:

              Example: 
              RP/0/RP0/CPU0:router# show cef ipv4 exact-route 20 .6.1.9 22.6.1.9 protocol udp source-port 1 destination-port 1 ingress-interface HundredGigE 0/1/0/4


22.6.1.9/32 version 0, internal 0x40040001 (0x78439fd0) [3], 0x0 (0x78aaf928), 0x4400 (0x78ed62d0)  remote adjacency to HundredGigE0/1/4/4  Prefix Len 32, traffic index 0, precedence routine (0)
   via HundredGigE0/1/4/4

              To verify the IPv6 7-tuple parameters, perform the following steps:

              Step 4   Configure Equal Cost Multipath Protocol (ECMP) interfaces, for example, between back-to-back routers.
              Step 5   Create route traffic streams so that there is a stream placed onto each configured interface.
              Step 6   Use the show cef ipv6 exact-route command in XR EXEC mode to verify that the interface selected for load balancing matches with the output from this command. The following example shows the exact route for the Layer 4 information:

              Example: 
              RP/0/RP0/CPU0:router# show cef ipv6 exact-route 20:6:1::9 22:6:1::9 protocol udp source-port 1 destination-port 1 ingress-interface HundredGigE 0/1/0/4 


22:6:1::/64, version 0, internal 0x40000001 (0x7846c048) [3], 0x0 (0x78aea3d0), 0x0 (0x0)  remote adjacency to HundredGigE0/1/4/4  Prefix Len 64, traffic index 0, precedence routine (0)
   via HundredGigE0/1/4/4

              Configuring BGP Attributes Download

              This task allows you to configure the BGP Attributes Download feature.

              Configuring BGP Attributes Download

              SUMMARY STEPS

                1.    configure

                2.    cef bgp attribute {attribute-id | local-attribute-id }

                3.    commit


              DETAILED STEPS
                 Command or ActionPurpose
                Step 1 configure
                                  		 
                Step 2 cef bgp attribute {attribute-id | local-attribute-id }


                Example: 
                RP/0/RP0/CPU0:router(config)# cef bgp attribute
                 

                Configures a CEF BGP attribute.

                 
                Step 3 commit
                                  		 

                Configuration Examples for Implementing CEF on Routers Software

                This section provides the following configuration examples:

                Configuring Unicast RPF Checking: Example

                The following example shows how to configure unicast RPF checking: 

                configure
interface TenGigE 0/0/0/1
ipv4 verify unicast source reachable-via rx
end

                Configuring the Switching of Modular Services Card to Management Ethernet Interfaces on the Route Processor: Example

                The following example shows how to configure the switching of the MSC to Management Ethernet interfaces on the route processor:

                configure
rp mgmtethernet forwarding
end

                Configuring Per-Flow Load Balancing: Example

                The following examples show how to configure Layer 3 and Layer 4 load-balancing for the hash algorithm from the cef load-balancing fields command, and how to verify summary information for the CEF table from the show cef summary command:

                Configuring Layer 3 load-balancing 

                configure
 cef load-balancing fields L3 
 end
 !
show cef summary
Router ID is 10.6.6.6

IP CEF with switching (Table Version 0) for node0_RP0_CPU0

  Load balancing: L3
  Tableid 0xe0000000 (0x9cbb51b0),  Flags 0x2031
   Refcount 577
  300 routes, 0 protected, 0 reresolve, 0 unresolved (0 old, 0 new), 21600 bytes
  212 load sharing elements, 62576 bytes, 324 references
  19 shared load sharing elements, 5388 bytes
  193 exclusive load sharing elements, 57188 bytes
  0 route delete cache elements
  622 local route bufs received, 1 remote route bufs received,  0 mix bufs received
  176 local routes, 0 remote routes
  4096 total local route updates processed
  0 total remote route updates processed 
  0 pkts pre-routed to cust card

  0 pkts received from core card
  0 CEF route update drops, 96 revisions of existing leaves
  0 CEF route update drops due to version mis-match
  Resolution Timer: 15s
  0 prefixes modified in place
  0 deleted stale prefixes
  82 prefixes with label imposition, 107 prefixes with label information
 95 next hops
  0 incomplete next hops

0 PD backwalks on LDIs with backup path

                Configuring Layer 4 load-balancing 

                Router ID is 1.10.10.10

IP CEF with switching (Table Version 0) for node0_RP0_CPU0

  Load balancing: L4
  Tableid 0xe0000000 (0x89bba258), Flags 0x2031
  Refcount 16
  5 routes, 0 protected, 0 reresolve, 0 unresolved (0 old, 0 new), 680 bytes
  5 load sharing elements, 1860 bytes, 0 references
  0 shared load sharing elements, 0 bytes
  5 exclusive load sharing elements, 1860 bytes
  0 route delete cache elements
  0 local route bufs received, 1 remote route bufs received,  0 mix bufs received
  0 local routes, 0 remote routes
  0 total local route updates processed
  0 total remote route updates processed
  0 pkts pre-routed to cust card
  0 pkts received from core card
  0 CEF route update drops, 0 revisions of existing leaves
  0 CEF route update drops due to version mis-match
  Resolution Timer: 15s
  0 prefixes modified in place
  0 deleted stale prefixes
  0 prefixes with label imposition, 0 prefixes with label information
 0 next hops
  0 incomplete next hops

0 PD backwalks on LDIs with backup path

                Configuring BGP Attributes Download: Example

                The following example shows how to configure the BGP Attributes Download feature:

                router configure
show cef bgp attribute {attribute-id| local-attribute-id}

                Configuring GTP Tunnel Load Balancing: Example

                The following example shows how to enable GTP tunnel load balancing by configuring Layer 4 load-balancing for the 7-tuple hash algorithm: 

                RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# cef load-balancing fields L4
RP/0/RP0/CPU0:router(config)# commit

                The following example shows how to verify summary information for the IPv4 or IPv6 CEF table: 

                RP/0/RP0/CPU0:router# show cef ipv4 summary

Router ID is 10.2.2.2

IP CEF with switching (Table Version 0) for node0_RP0_CPU0

  Load balancing: L4
  Tableid 0xe0000000 (0x9cdbc1dc),  Flags 0x21
   Refcount 527
  293 routes, 0 protected, 0 reresolve, 0 unresolved (0 old, 0 new), 23440 bytes
  222 load sharing elements, 64376 bytes, 85 references
  14 shared load sharing elements, 4064 bytes
  208 exclusive load sharing elements, 60312 bytes
  0 route delete cache elements
  2036 local route bufs received, 1264 remote route bufs received,  0 mix bufs d
  117 local routes, 0 remote routes
  8762 total local route updates processed
  0 total remote route updates processed 
  0 pkts pre-routed to cust card

  0 pkts received from core card
  0 CEF route update drops, 2151 revisions of existing leaves
  0 CEF route update drops due to version mis-match
  Resolution Timer: 15s
  0 prefixes modified in place
  0 deleted stale prefixes
  0 prefixes with label imposition, 0 prefixes with label information

 159 next hops
  0 incomplete next hops
          
 0 PD backwalks on LDIs with backup path

RP/0/RP0/CPU0:router# show cef ipv6 summary

Router ID is 10.2.2.2

IP CEF with switching (Table Version 0) for node0_RP0_CPU0

  Load balancing: L4
  Tableid 0xe0800000 (0x9cdee368),  Flags 0x21
   Refcount 39
  17 routes, 0 protected, 0 reresolve, 0 unresolved (0 old, 0 new), 1360 bytes
  17 load sharing elements, 4876 bytes, 4 references
  4 shared load sharing elements, 1072 bytes
  13 exclusive load sharing elements, 3804 bytes
  0 route delete cache elements
  199321 local route bufs received, 49838 remote route bufs received,  0 mix bud
  9 local routes, 0 remote routes
  1046420 total local route updates processed
  0 total remote route updates processed 
  0 pkts pre-routed to cust card

  0 pkts received from core card
  0 CEF route update drops, 1 revisions of existing leaves
  0 CEF route update drops due to version mis-match
  Resolution Timer: 15s
  0 prefixes modified in place
  0 deleted stale prefixes
  0 prefixes with label imposition, 0 prefixes with label information

 3 next hops
  0 incomplete next hops
          
 0 PD backwalks on LDIs with backup path

                Use the show cef {ipv4 | ipv6} exact-route command in XR EXEC mode to verify that the interface selected for load balancing matches with the output from this command. The following examples show the exact route for the Layer 4 information:


                Note

                Use 16MSBist of TEID in source port and 16LSBits of TEID in destination port in place of L4 protocol source and destination port number.

                For example:

                If TEID=241210E1 (in hexadecimal), then source-port=9234 (Decimal equivalent of 16MSBits of TEID 2412) and destination-port=4321 (Decimal equivalent of 16LSBits of TEID 10E1)

                If TEID=0069012F (in hexadecimal), then source-port= 105 (Decimal equivalent of 16MSBits of TEID 0069) and destination-port= 303 (Decimal equivalent of 16LSBits of TEID 012F) 

                RP/0/RP0/CPU0:router# show cef ipv4 exact-route 20.0.0.2 60.0.0.2 protocol udp source-port 9234 destination-port 4321 ingress-interface HundredGigE 0/6/5/0

0.0.0.0/0, version 12, proxy default, internal 0x4000021 (ptr 0x9d760060) [1], )
 Updated Jul 17 03:12:35.566 
 local adjacency 172.29.52.1
 Prefix Len 0, traffic index 0, precedence routine (0), priority 3
   via MgmtEth0/RP0/CPU0/0
   via 172.29.52.1, 5 dependencies, recursive [flags 0x0]
    path-idx 0 [0x9d760648 0x0]
    next hop 172.29.52.1 via 172.29.52.1/32

RP/0/RP0/CPU0:router# show cef ipv6 exact-route 20:6:1::9 22:6:1::9 protocol udp source-port 105 destination-port 303 ingress-interface HundredGigE 0/6/5/4

::/0, version 8, proxy default, internal 0x4000021 (ptr 0x9d6ac06c) [1], 0x0 (0)
 Updated Jul 17 03:14:49.695 
 remote adjacency to HundredGigE0/6/5/0.22
 Prefix Len 0, traffic index 0, precedence routine (0), priority 3
   via HundredGigE0/6/5/0.22
   via 5001:db8::1, HundredGigE0/6/5/0.22, 4 dependencies, weight 0, class ]
    path-idx 0 [0x9dd7e0c4 0x0]
    next hop 5001:db8::1
    remote adjacency

                Additional References

                The following sections provide references related to implementing CEF.

                Related Documents

                Related Topic

                Document Title

                CEF commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples

                Cisco Express Forwarding Commands module in IP Addresses and Services Command Reference for Cisco NCS 6000 Series Routers

                BGP commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples

                BGP Commands module in the Routing Command Reference for Cisco NCS 6000 Series Routers

                Link Bundling Commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples

                Link Bundling Commands module in the Interface and Hardware Component Command Reference for Cisco NCS 6000 Series RoutersInterface and Hardware Component Command Reference for Cisco NCS 5000 Series Routers

                Standards

                Standards

                Title

                No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

                		 —

                MIBs

                MIBs

                MIBs Link
                —

                To locate and download MIBs, use the Cisco MIB Locator found at the following URL and choose a platform under the Cisco Access Products menu: http:/​/​cisco.com/​public/​sw-center/​netmgmt/​cmtk/​mibs.shtml

                RFCs

                RFCs

                Title

                No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.

                		 —

                Technical Assistance

                Description

                Link

                The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

                http:/​/​www.cisco.com/​techsupport

                Was this Document Helpful?

                FeedbackFeedback

                Contact Cisco