Table Of Contents
DDR-Dependent Implementation Decisions
Monitoring and Maintaining Dialer Cisco Express Forwarding Interfaces
Dialer CEF
First Published: 12.2(4)TLast Updated: April 18, 2006History for the Dialer CEF Feature
Release Modification12.2(4)T
This feature was introduced.
12.2(28)SB
This feature was integrated into Cisco IOS Release 12.2(28)SB.
This document describes the Dialer CEF feature.
It includes the following sections:
•
Monitoring and Maintaining Dialer Cisco Express Forwarding Interfaces
Restrictions for Dialer CEF
The Dialer CEF feature is not supported when a static route is pointing to the Dialer without specifying a next hop IP address. When using the Cisco IOS Release 12.3(11)T and higher, the ppp ipcp default route command may be used in Dialer interface configuration mode to work around this restriction.
Information about Dialer CEF
The Dialer CEF feature introduces Cisco Express Forwarding support for dialer interfaces. The Dialer Cisco Express Forwarding feature allows packets to be Cisco Express Forwarding switched across dialer interfaces rather than being low-end switched (LES) or fast switched. Compared to fast switching, Cisco Express Forwarding switching support improves switching performance by decreasing CPU utilization and lowering the packet loss rate.
DDR-Dependent Implementation Decisions
You must decide whether to implement legacy dial-on-demand routing (DDR) or the newer dialer profiles.
Dialer Profiles
The dialer profiles implementation of DDR is based on a separation between logical and physical interface configuration. Dialer profiles also allow the logical and physical configurations to be bound together dynamically on a per-call basis.
Dialer profiles are advantageous in the following situations:
•
When you want to share an interface (ISDN, asynchronous, or synchronous serial) to place or receive calls.
•
When you want to change any configuration on a per-user basis.
•
When you want to maximize ISDN channel usage using the Dynamic Multiple Encapsulations feature to configure various encapsulation types and per-user configurations on the same ISDN B channel at different times according to the type of call.
•
When you want to bridge to many destinations and avoiding split horizon problems.
Most routed protocols are supported; however, International Organization for Standardization Connectionless Network Service (ISO CLNS) is not supported.
If you decide to configure dialer profiles, you must disable validation of source addresses for the routed protocols you support.
For detailed dialer profiles information, see the "Configuring Peer-to-Peer DDR with Dialer Profiles" chapter in the Cisco IOS Dial Technologies Configuration Guide, Release 12.2.
For more information about Dynamic Multiple Encapsulations, see the "Dialer Profiles Configuration Task List" section in the Cisco IOS Dial Technologies Configuration Guide, Release 12.2.
Legacy DDR
Legacy DDR is powerful and comprehensive, but its limitations affect scaling and extensibility. Legacy DDR is based on a static binding between the per-destination call specification and the physical interface configuration.
However, legacy DDR also has many strengths. It supports Frame Relay, ISO CLNS, LAPB, snapshot routing, and all routed protocols that are supported on Cisco routers. By default, legacy DDR supports fast switching.
For information about simple legacy DDR spoke configurations, see the "Configuring Legacy DDR Spokes" chapter in the Cisco IOS Dial Technologies Configuration Guide, Release 12.2. For information about simple legacy DDR hub configurations, see the "Configuring Legacy DDR Hubs" chapter in the Cisco IOS Dial Technologies Configuration Guide, Release 12.2.
Benefits
Improved Performance
Cisco Express Forwarding 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.
Resilience
Cisco Express Forwarding 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. Cisco Express Forwarding can switch traffic more efficiently than typical demand caching schemes.
Although you can use Cisco Express Forwarding in any part of a network, it is designed for high-performance, highly resilient Layer 3 IP backbone switching.
Configuration Tasks
None
Monitoring and Maintaining Dialer Cisco Express Forwarding Interfaces
To monitor and maintain Dialer Cisco Express Forwarding interfaces, use the following EXEC commands:
Configuration Examples
None
Additional References
The following sections provide references related to the Dialer Cisco Express Forwarding feature.
Related Documents
Related Topic Document TitleDial Technologies Configuration Tasks
Cisco IOS Dial Technologies Configuration Guide, Release 12.2
Dial Technologies Commands List
Cisco IOS Dial Technologies Command Reference, Release 12.2
Standards
MIBs
MIB MIBs LinkNone
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Command Reference
This section documents modified commands.
debug ip cef
To troubleshoot various Cisco Express Forwarding (CEF) events, use the debug ip cef command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip cef {drops [rpf [access-list]] [access-list] | receive [access-list] | events [access-list] | interface | dialer}
no debug ip cef {drops [rpf [access-list]] [access-list] | receive [access-list] | events [access-list] | interface | dialer}
Specific to IPC Records
debug ip cef {ipc | interface-ipc | prefix-ipc [access-list]}
no debug ip cef {ipc | interface-ipc | prefix-ipc [access-list]}
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command gathers additional information for the handling of CEF interface, IPC, or packet events.
Note
For packet events, we recommend that you use an access control list (ACL) to limit the messages recorded.
Examples
The following is sample output from the debug ip cef rpf command for a packet that is dropped when it fails the RPF check. IP address 172.17.249.252 is the source address, and Ethernet 2/0/0 is the input interface:
Router# debug ip cef drops rpfIP CEF drops for RPF debugging is on00:42:02:CEF-Drop:Packet from 172.17.249.252 via Ethernet2/0/0 -- unicast rpf checkThe following is sample output for CEF packets that are not switched using information from the FIB table but are received and sent to the next switching layer:
Router# debug ip cef receiveIP CEF received packets debugging is on00:47:52:CEF-receive:Receive packet for 10.1.104.13Table 1 describes the significant fields shown in the display.
The following is sample output from the debug ip cef dialer command for a legacy dialer:
Router# debug ip cef dialer00:19:50:CEF-Dialer (legacy):add link to 10.10.10.2 via Dialer1 through BRI0/0:100:19:50:CEF-Dialer:adjacency added:0x8116485000:19:50:CEF-Dialer:adjacency found:0x81164850; fib->count:100:19:50:CEF-Dialer:setup loadinfo with 1 pathsThe following is sample output from the debug ip cef dialer command for a dialer profile:
Router# debug ip cef dialer00:31:44:CEF-Dialer (profile dynamic encap (not MLP)):add link to 10.10.10.2 via Dialer1 through Dialer100:31:44:CEF-Dialer:adjacency added:0x8116485000:31:44:CEF-Dialer:adjacency found:0x81164850; fib->count:1Table 2 describes the significant fields shown in the display.
Related Commands
Command Descriptionip cef
Enables Cisco Express Forwarding on the RPC card.
show ip cef
Displays entries in the FIB or displays a summary of the FIB.
show adjacency
To display information about the Cisco Express Forwarding (CEF) adjacency table or the hardware Layer 3-switching adjacency table, use the show adjacency command in user EXEC or privileged EXEC mode.
show adjacency [summary [interface interface-number]] | [prefix] [interface interface-number] [connectionid id] [link {ipv4 | ipv6 | mpls}] [detail]
Note
On the Cisco 10000 series routers IPv6 is supported on 12.2(28)SBD or later releases.
Syntax Description
Defaults
This command has no default settings.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
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.
You can use any combination of the prefix, interface, connectionid id, and link {ipv4 | ipv6 | mpls} keywords and arguments (in any order) as a filter to enable the display of a specified subset of adjacencies.
Note
On the Cisco 10000 series routers IPv6 is supported on 12.2(28)SBD or later releases.
The information displayed by the show adjacency commands includes the following:
•
Protocol
•
Interface
•
Type of routed protocol traffic using this adjacency
•
Next hop address
•
Adjacency source (for example, address resolution protocol (ARP) or ATM Map)
•
Encapsulation prepended to packet switched through this adjacency
•
Chain of output chain elements applied to packets after an adjacency
•
Packet and byte counts
•
HA epoch and summary event epoch
Examples
The following example shows how to display adjacency information:
For a Cisco 7000 Series Router
Router# show adjacencyProtocol Interface AddressIP FastEthernet2/3 172.20.52.1(3045)IP FastEthernet2/3 172.20.52.22(11)Router#The following example shows how to display adjacency information for a specific interface:
Router# show adjacency fastethernet 0/0Protocol Interface AddressIP FastEthernet0/0 10.4.9.2(5)IP FastEthernet0/0 10.4.9.3(5)Router#For a Cisco 10000 Series Router
Router# show adjacencyProtocol Interface AddressIP FastEthernet2/0/0 172.20.52.1(3045)IP FastEthernet2/0/0 172.20.52.22(11)Router#The following example shows how to display adjacency information for a specific interface:
Router# show adjacency fastethernet 2/0/0Protocol Interface AddressIP FastEthernet2/0/0 10.4.9.2(5)IP FastEthernet2/0/0 10.4.9.3(5)The following example shows how to display detailed adjacency information for adjacent IPv6 routers:
Router# show adjacency detailProtocol Interface AddressIP Tunnel0 point2point(6)0 packets, 0 bytes00000000CEF expires: 00:02:57refresh: 00:00:57Epoch: 0IPV6 Tunnel0 point2point(6)0 packets, 0 bytes00000000IPv6 CEF neverEpoch: 0IPV6 Ethernet2/0 FE80::A8BB:CCFF:FE01:9002(3)0 packets, 0 bytesAABBCC019002AABBCC012C0286DDIPv6 ND neverEpoch: 0IPV6 Ethernet2/0 3FFE:2002::A8BB:CCFF:FE01:9002(5)0 packets, 0 bytesAABBCC019002AABBCC012C0286DDIPv6 ND neverEpoch: 0Table 3 describes the significant fields shown in the displays.
Table 3 show adjacency Field Descriptions
Field DescriptionProtocol
Type of Internet protocol.
Interface
Outgoing interface.
172.20.52.1(3045)
Next hop address.
The following example shows how to display a summary of adjacency information:
For a Cisco 7000 Series Router
Router# show adjacency summaryAdjacency table has 7 adjacencies:each adjacency consumes 368 bytes (4 bytes platform extension)6 complete adjacencies1 incomplete adjacency4 adjacencies of linktype IP4 complete adjacencies of linktype IP0 incomplete adjacencies of linktype IP0 adjacencies with fixups of linktype IP2 adjacencies with IP redirect of linktype IP3 adjacencies of linktype IPV62 complete adjacencies of linktype IPV61 incomplete adjacency of linktype IPV6Adjacency database high availability:Database epoch: 8 (7 entries at this epoch)Adjacency manager summary event processing:Summary events epoch is 52Summary events queue contains 0 events (high water mark 113 events)Summary events queue can contain 49151 eventsAdj last sourced field refreshed every 16384 summary eventsRP adjacency component enabledFor a Cisco 10000 Series Router
Router# show adjacency summaryAdjacency table has 7 adjacencies:each adjacency consumes 368 bytes (4 bytes platform extension)6 complete adjacencies1 incomplete adjacency4 adjacencies of linktype IP4 complete adjacencies of linktype IP0 incomplete adjacencies of linktype IP0 adjacencies with fixups of linktype IP2 adjacencies with IP redirect of linktype IPAdjacency database high availability:Database epoch: 8 (7 entries at this epoch)Adjacency manager summary event processing:Summary events epoch is 52Summary events queue contains 0 events (high water mark 113 events)Summary events queue can contain 49151 eventsAdj last sourced field refreshed every 16384 summary eventsRP adjacency component enabledThe following example shows how to display protocol detail and timer information:
For a Cisco 7000 Series Router
Router# show adjacency detailProtocol Interface AddressIP FastEthernet0/0 10.4.9.2(5)0 packets, 0 bytesepoch 0sourced in sev-epoch 2Encap length 1400307131ABFC000500509C080800ARPIP FastEthernet0/0 10.4.9.3(5)0 packets, 0 bytesepoch 0sourced in sev-epoch 2Encap length 14000500506C08000500509C080800ARPRouter#For a Cisco 10000 Series Router
Router# show adjacency detailProtocol Interface AddressIP FastEthernet2/0/0 10.4.9.2(5)0 packets, 0 bytesepoch 0sourced in sev-epoch 2Encap length 1400307131ABFC000500509C080800ARPIP FastEthernet2/0/0 10.4.9.3(5)0 packets, 0 bytesepoch 0sourced in sev-epoch 2Encap length 14000500506C08000500509C080800ARPRouter#The following example shows how to display protocol detail and timer adjacency information for IP links for a specific interface:
For a Cisco 7000 Series Router
Router# show adjacency tunnel 1 link ip detailProtocol Interface AddressIP Tunnel1 point2point(7)0 packets, 0 bytesepoch 1sourced in sev-epoch 4empty encap stringP2P-ADJNext chain element:label 16 TAG adj out of Ethernet1/0, addr 10.0.0.0Router#For a Cisco 10000 Series Router
Router# show adjacency tunnel 1 link ip detailProtocol Interface AddressIP Tunnel1 point2point(7)0 packets, 0 bytesepoch 1sourced in sev-epoch 4empty encap stringP2P-ADJNext chain element:label 16 TAG adj out of FastEthernet1/0/0, addr 10.0.0.0Router#Table 4 describes the significant fields shown in the displays.
Related Commands
show ip interface
To display the usability status of interfaces configured for IP, use the show ip interface command in privileged EXEC mode.
show ip interface [type number] [brief]
Syntax Description
type
(Optional) Interface type.
number
(Optional) Interface number.
brief
(Optional) Displays a summary of the usability status information for each interface.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The Cisco IOS software automatically enters a directly connected route in the routing table if the interface is usable. A usable interface can send and receive packets. If an interface is not usable, the directly connected routing entry is removed from the routing table. Removing the entry allows the software to use dynamic routing protocols to determine backup routes to the network, if any.
If the interface can provide two-way communication, the line protocol is marked "up." If the interface hardware is usable, the interface is marked "up."
If you specify an optional interface type, you see information for that specific interface.
If you specify no optional arguments, you see information on all the interfaces.
When an asynchronous interface is encapsulated with PPP or Serial Line Internet Protocol (SLIP), IP fast switching is enabled. A show ip interface command on an asynchronous interface encapsulated with PPP or SLIP displays a message indicating that IP fast switching is enabled.
Examples
The following examples from Cisco IOS Release 12.3(14)YM2 show: 1) configuration information on interface Gigabit Ethernet0/3 where the IP flow egress feature is configured on the output side (where packets go out of the interface) and the policy route-map named PBR_NAME is configured on the input side (where packets come into the interface); and 2) interface information on interface Gigabit Ethernet0/3 showing that MPF is enabled and that both features are not supported by MPF and ignored.
The highlighted arrows (for documentation purposes only) show the configured output and input features and the additional MPF interface information.
Router# show running-config interface g0/3interface GigabitEthernet0/3ip address 192.1.1.1 255.255.0.0ip flow egress <== outputip policy route-map PBR_NAME <== inputduplex autospeed automedia-type gbicnegotiation autoendRouter# show ip interface g0/3GigabitEthernet0/3 is up, line protocol is upInternet address is 192.1.1.1/16Broadcast address is 255.255.255.255Address determined by setup commandMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is disabledOutgoing access list is not setInbound access list is not setProxy ARP is enabledLocal Proxy ARP is disabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is disabledIP Flow switching is disabledIP CEF switching is enabledIP Feature Fast switching turbo vectorIP VPN Flow CEF switching turbo vectorIP multicast fast switching is enabledIP multicast distributed fast switching is disabledIP route-cache flags are Fast, CEFRouter Discovery is disabledIP output packet accounting is disabledIP access violation accounting is disabledTCP/IP header compression is disabledRTP/IP header compression is disabledPolicy routing is enabled, using route map PBRNetwork address translation is disabledBGP Policy Mapping is disabledIP Multi-Processor Forwarding is enabled <======== MPF informationIP Input features, "PBR",are not supported by MPF and are IGNOREDIP Output features, "NetFlow",are not supported by MPF and are IGNOREDThe following example identifies a downstream VRF. The highlighted line (for documentation purposes only) identifies the downstream VRF.
Router# show ip interface vi 3Virtual-Access3 is up, line protocol is upInterface is unnumbered. Using address of Loopback2 (10.0.0.8)Broadcast address is 255.255.255.255Peer address is 10.8.1.1MTU is 1492 bytesHelper address is not setDirected broadcast forwarding is disabledOutgoing access list is not setInbound access list is not setProxy ARP is enabledLocal Proxy ARP is disabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is enabledIP Flow switching is disabledIP CEF switching is enabledIP Feature Fast switching turbo vectorIP VPN CEF switching turbo vectorVPN Routing/Forwarding "U"Downstream VPN Routing/Forwarding "D"IP multicast fast switching is disabledIP multicast distributed fast switching is disabledIP route-cache flags are Fast, CEFRouter Discovery is disabledIP output packet accounting is disabledIP access violation accounting is disabledTCP/IP header compression is disabledRTP/IP header compression is disabledPolicy routing is disabledNetwork address translation is disabledWCCP Redirect outbound is disabledWCCP Redirect inbound is disabledWCCP Redirect exclude is disabledBGP Policy Mapping is disabledTable 5 describes the significant fields shown in the display.
The following is sample output from the show ip interface brief command:
Router# show ip interface briefInterface IP-Address OK? Method Status ProtocolEthernet0 151.108.0.5 YES NVRAM up upEthernet1 unassigned YES unset administratively down downLoopback0 152.108.20.5 YES NVRAM up upSerial0 162.108.10.5 YES NVRAM up upSerial1 162.108.4.5 YES NVRAM up upSerial2 152.108.10.5 YES manual up upSerial3 unassigned YES unset administratively down downThe method field has the following possible values:
•
RARP or SLARP—Reverse Address Resolution Protocol (RARP) or Serial Line Address Resolution Protocol (SLARP) request
•
BOOTP—Bootstrap protocol
•
TFTP—Configuration file obtained from Trivial File Transfer Protocol (TFTP) server
•
manual—Manually changed by CLI command
•
NVRAM—Configuration file in nonvolatile RAM (NVRAM)
•
IPCP—ip address negotiated command
•
DHCP—ip address dhcp command
•
unassigned—No IP address
•
unset—Unset
•
other—Unknown
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2001-2002, 2005-2006 Cisco Systems, Inc. All rights reserved.


