Table Of Contents
Configuring Cisco Express Forwarding Consistency Checkers for Route Processors and Line Cards
Finding Feature Information
Contents
Prerequisites for Configuring Basic Cisco Express Forwarding
Restrictions for Configuring Basic Cisco Express Forwarding
Information About Configuring Basic Cisco Express Forwarding
Cisco Platform Support for Cisco Express Forwarding and Distributed Cisco Express Forwarding
Cisco Express Forwarding Consistency Checker Types for Cisco Express Forwarding and Distributed Cisco Express Forwarding
How to Configure Cisco Express Forwarding Consistency Checkers
Enabling Cisco Express Forwarding Consistency Checkers
Displaying and Clearing Cisco Express Forwarding Table Inconsistencies
Configuration Examples for Configuring Basic Cisco Express Forwarding
Enabling Cisco Express Forwarding Consistency Checkers: Example
Additional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Feature Information for Configuring Basic Cisco Express Forwarding Consistency Checkers for Route Processors and Line Cards
Glossary
Configuring Cisco Express Forwarding Consistency Checkers for Route Processors and Line Cards
First Published: May 2, 2005
Last Updated: February 11, 2008
This module contains information about and instructions for configuring Cisco Express Forwarding consistency checkers for route processors and line cards. Cisco Express Forwarding consistency checkers help you find any database inconsistencies, such as an IP prefix missing from a line card or a Route Processor (RP). You can investigate and resolve the inconsistency by examining the associated Cisco Express Forwarding system error messages that occur and by issuing Cisco Express Forwarding debug and show commands.
Cisco Express Forwarding is an advanced Layer 3 IP switching technology. It optimizes network performance and scalability for all kinds of networks: those that carry small amounts of traffic and those that carry large amounts of traffic in complex patterns, such as the Internet and networks characterized by intensive web-based applications or interactive sessions.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Configuring Basic Cisco Express Forwarding Consistency Checkers for Route Processors and Line Cards" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Configuring Basic Cisco Express Forwarding
•
Restrictions for Configuring Basic Cisco Express Forwarding
•
Information About Configuring Basic Cisco Express Forwarding
•
How to Configure Cisco Express Forwarding Consistency Checkers
•
Configuration Examples for Configuring Basic Cisco Express Forwarding
•
Additional References
•
Feature Information for Configuring Basic Cisco Express Forwarding Consistency Checkers for Route Processors and Line Cards
•
Glossary
Prerequisites for Configuring Basic Cisco Express Forwarding
Cisco Express Forwarding must be up and running on the networking device before you can configure Cisco Express Forwarding consistency checkers.
Restrictions for Configuring Basic Cisco Express Forwarding
The Cisco Express Forwarding consistency checkers lc-detect and scan-lc apply only to devices that have distributed Cisco Express Forwarding enabled.
Information About Configuring Basic Cisco Express Forwarding
Before configuring Cisco Express Forwarding consistency checkers, you should understand the following:
•
Cisco Platform Support for Cisco Express Forwarding and Distributed Cisco Express Forwarding
•
Cisco Express Forwarding Consistency Checker Types for Cisco Express Forwarding and Distributed Cisco Express Forwarding
For links to information about other Cisco Express Forwarding and distributed Cisco Express Forwarding features that you can configure, refer to the following section:
•
How to Configure Cisco Express Forwarding Consistency Checkers
Cisco Platform Support for Cisco Express Forwarding and Distributed Cisco Express Forwarding
Cisco Express Forwarding is enabled by default on most Cisco platforms running Cisco IOS software Release12.0 or later. When Cisco Express Forwarding is enabled on a router, the RP performs the express forwarding.
To find out if Cisco Express Forwarding is enabled on your platform, enter the show ip cef command. If Cisco Express Forwarding is enabled, you receive output that looks like this:
Prefix Next Hop Interface
10.2.61.8/24 192.168.100.1 FastEthernet1/0/0
192.168.101.1 FastEthernet6/1
If Cisco Express Forwarding is not enabled on your platform, the output for the show ip cef command looks like this:
Distributed Cisco Express Forwarding is enabled by default on the Catalyst 6500 series switch, the Cisco 7500 series router, and the Cisco 12000 Series Internet Router. When distributed Cisco Express Forwarding is enabled on your platform, the line cards perform the express forwarding.
If Cisco Express Forwarding is not enabled on your platform, use the ip cef command to enable Cisco Express Forwarding or the ip cef distributed command to enable distributed Cisco Express Forwarding.
Cisco Express Forwarding Consistency Checker Types for Cisco Express Forwarding and Distributed Cisco Express Forwarding
Cisco Express Forwarding uses routing information that is retrieved from the Routing Information Base (RIB), the RP, and the line card databases to perform express forwarding. As these databases are updated, inconsistencies might result, due to the asynchronous nature of the distribution mechanism for these databases. Inconsistencies caused by asynchronous database distribution are of the following types:
•
Missing information, such as a particular prefix, on a line card
•
Different information, such as different next hop IP addresses, on the line card
Cisco Express Forwarding supports passive and active consistency checkers that run independently to uncover these forwarding inconsistencies. Table 1 describes the consistency checkers and indicates whether the checker operates on the RP or the line card.
Table 1 Types of Cisco Express Forwarding Consistency Checkers
Checker Type
|
Operates On
|
Description
|
Lc-detect
|
Line card
|
(Distributed Cisco Express Forwarding only) Retrieves IP prefixes found missing from the line card FIB table. If IP prefixes are missing, the line card cannot forward packets for the corresponding addresses. Lc-detect then sends IP prefixes to the RP for confirmation. If the RP finds that it has the relevant entry, an inconsistency is detected, and an error message is displayed. Also, the RP sends a signal back to the line card confirming that the IP prefix contributes to the creation of an inconsistency.
|
Scan-lc
|
Line card
|
(Distributed Cisco Express Forwarding only) Looks through the FIB table for a configurable time period and sends the next n prefixes to the RP. The RP does an exact lookup in its FIB table. If the RP finds that the prefix is missing, the RP reports an inconsistency. The RP sends a signal back to the line card for confirmation.
The time period and number of prefixes sent are configured with the ip cef table consistency-check command.
|
Scan-rp
|
Route Processor
|
Looks through the RP FIB table for a configurable time period and sends the next n prefixes to the line card. (This action is opposite to the one that the scan-lc checker performs.) The line card does an exact lookup in the FIB table. If the line card finds the prefix missing, the line card reports an inconsistency and signals the RP for confirmation.
The time period and number of prefixes sent are configured with the ip cef table consistency-check command.
|
Scan-rib
|
Route Processor
|
Operates on all (even nondistributed) RPs, and scans the RIB to ensure that prefix entries are present in the RP FIB table.
|
Cisco Express Forwarding consistency checkers are enabled by default for Cisco IOS Releases 12.0(20)S and later. Console errors are disabled by default.
If you find a database inconsistency, such as an IP prefix missing from a line card or an RP, you can investigate and resolve it by examining the Cisco Express Forwarding system error messages and by issuing Cisco Express Forwarding debug and show commands.
For Cisco Express Forwarding consistency checker system error messages, see the System Message Guide for your Cisco IOS Release.
How to Configure Cisco Express Forwarding Consistency Checkers
Perform the following tasks to configure Cisco Express Forwarding consistency checkers:
•
Enabling Cisco Express Forwarding Consistency Checkers (optional)
•
Displaying and Clearing Cisco Express Forwarding Table Inconsistencies (optional)
Enabling Cisco Express Forwarding Consistency Checkers
Perform the following task to enable Cisco Express Forwarding consistency checkers.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip cef table consistency-check [type {lc-detect | scan-lc | scan-rib | scan-rp}]
[count count-number] [period seconds]
4.
ip cef table consistency-check [settle-time seconds]
5.
end
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
ip cef table consistency-check [type {lc-detect
| scan-lc | scan-rib | scan-rp}] [count
count-number] [period seconds]
Example:
Router(config)# ip cef table consistency-check
scan-rib count 100 period 60
|
Enables Cisco Express Forwarding table consistency checker types and parameters.
• The type keyword indicates the type of consistency check to enable.
• The lc-detect keyword enables the line card to detect a missing prefix, which is confirmed by the RP.
• The scan-lc keyword enables a passive scan check of tables on the line card.
• The scan-rib keyword enables a passive scan check of tables on the RP and a comparison with the RIB.
• The scan-rp keyword enables a passive scan check of tables on the RP.
• The count-number keyword-argument pair is the maximum number of prefixes to check per scan. The range is from 1 to 225.
• The period seconds keyword-argument pair is the time during which updates for a candidate prefix are ignored as inconsistencies. The range is from 1 to 3600 seconds.
|
Step 4
|
ip cef table consistency-check [settle-time
seconds]
Example:
Router(config)# ip cef table consistency-check
settle-time 65
|
Suppresses inconsistency errors during route updates.
• The settle-time seconds keyword-argument pair is the time elapsed during which updates for a candidate prefix are ignored as inconsistencies. The range is from 1 to 3600 seconds.
|
Step 5
|
end
Example:
Router(config)# end
|
Exits to privileged EXEC mode.
|
Displaying and Clearing Cisco Express Forwarding Table Inconsistencies
Perform the following task to display and clear Cisco Express Forwarding table inconsistency records found by the lc-detect, scan-rp, scan-rib, and scan-lc detection mechanisms.
SUMMARY STEPS
1.
enable
2.
show ip cef inconsistency
3.
clear ip cef inconsistency
4.
clear cef linecard [slot-number] [adjacency | interface | prefix]
5.
show ip cef inconsistency
6.
exit
DETAILED STEPS
Step 1
enable
Use this command to enable privileged EXEC mode. For example:
Enter your password if prompted.
Step 2
show ip cef inconsistency
Use this command to display Cisco Express Forwarding IP inconsistencies. For example:
Router# show ip cef inconsistency
Table consistency checkers (settle time 65s)
0/0/0 queries sent/ignored/received
scan-lc:running [100 prefixes checked every 60s]
0/0/0 queries sent/ignored/received
scan-rp:running [100 prefixes checked every 60s]
0/0/0 queries sent/ignored/received
scan-rib:running [100 prefixes checked every 60s]
0/0/0 queries sent/ignored/received
Inconsistencies:0 confirmed, 0/16 recorded
For each checker type, the output shows the number of prefixes that Cisco Express Forwarding must check and the number of seconds (the settle time) during which an inconsistency between RP and line card tables is ignored. The preceding output shows that 0 inconsistencies existed between these tables at the time the command was entered on the router.
Step 3
clear ip cef inconsistency
Use this command to clear the Cisco Express Forwarding inconsistency statistics and records found by the Cisco Express Forwarding consistency checkers. For example:
Router# clear ip cef inconsistency
Step 4
clear cef linecard [slot-number] [adjacency | interface | prefix]
Use this command to clear Cisco Express Forwarding information from line cards. For example:
Router# clear cef linecard
Step 5
show ip cef inconsistency
Use this command to verify that Cisco Express Forwarding statistics on inconsistencies are removed from the RP and the line cards. For example:
Router# show ip cef inconsistency
Table consistency checkers (settle time 65s)
0/0/0 queries sent/ignored/received
scan-lc:running [100 prefixes checked every 60s]
0/0/0 queries sent/ignored/received
scan-rp:running [100 prefixes checked every 60s]
0/0/0 queries sent/ignored/received
scan-rib:running [1000 prefixes checked every 60s]
0/0/0 queries sent/ignored/received
Inconsistencies:0 confirmed, 0/16 recorded
This sample output shows that four consistency checkers are enabled, that each checker sends 100 prefixes to be checked every 60 seconds, and that the time during which inconsistencies are ignored is 65 seconds. In this example, no inconsistencies were found.
Step 6
exit
Use this command to exit to user EXEC mode. For example:
Configuration Examples for Configuring Basic Cisco Express Forwarding
This section contains the following Cisco Express Forwarding consistency checker configuration example:
•
Enabling Cisco Express Forwarding Consistency Checkers: Example
Enabling Cisco Express Forwarding Consistency Checkers: Example
The following example shows how to enable the scan-rp Cisco Express Forwarding consistency checker.
ip cef table consistency-check scan-rp count 225 period 3600
ip cef table consistency-check settle-time 2500
The RP is configured to send 3600 prefixes to the line cards every 225 seconds. After the prefixes are sent, the line cards is to wait 2500 seconds before signaling the PR to report an inconsistency (if there is one).
Additional References
The following sections provide references related to configuring Cisco Express Forwarding consistency checkers.
Related Documents
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
|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.
|
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://www.cisco.com/go/mibs
|
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 Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.
To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.
|
http://www.cisco.com/cisco/web/support/index.html
|
Feature Information for Configuring Basic Cisco Express Forwarding Consistency Checkers for Route Processors and Line Cards
Table 2 lists the release history for this feature.
For information on a feature in this technology that is not documented here, see the Cisco Express Forwarding Features Roadmap.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 2 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Table 2 Feature Information for Configuring Basic Cisco Express Forwarding Consistency Checkers for Route Processors and Line Cards
Feature Name
|
Releases
|
Feature Configuration Information
|
This table is intentionally left blank because no features were introduced or modified in Cisco IOS Release 12.2(1) or later. This table will be updated when feature information is added to this module.
|
—
|
—
|
Glossary
adjacency—A relationship formed between selected neighboring routers and end nodes for the purpose of exchanging routing information. Adjacency is based upon the use of a common media segment by the routers and nodes involved.
Cisco Express Forwarding—A Layer 3 switching technology. Cisco Express Forwarding can also refer to central Cisco Express Forwarding mode, one of two modes of Cisco Express Forwarding operation. Cisco Express Forwarding enables a Route Processor to perform express forwarding. Distributed Cisco Express Forwarding is the other mode of Cisco Express Forwarding operation.
distributed Cisco Express Forwarding—A mode of Cisco Express Forwarding switching in which line cards (such as Versatile Interface Processor (VIP) line cards) maintain identical copies of the forwarding information base (FIB) and adjacency tables. The line cards perform the express forwarding between port adapters; this relieves the Route Switch Processor of involvement in the switching operation.
FIB—forwarding information base. A component of Cisco Express Forwarding that is conceptually similar to a routing table or information base. The router uses the FIB lookup table to make destination-based switching decisions during Cisco Express Forwarding operation. The router maintains a mirror image of the forwarding information in an IP routing table.
IPC—interprocess communication. The mechanism that enables the distribution of Cisco Express Forwarding tables from the Route Switch Processor (RSP) to the line card when the router is operating in distributed Cisco Express Forwarding mode.
LIB—label information base. A database used by a label switch router (LSR) to store labels learned from other LSRs, as well as labels assigned by the local LSR.
line card—A general term for an interface processor that can be used in various Cisco products. For example, a Versatile Interface Processor (VIP) is a line card for the Cisco 7500 series router.
MPLS—Multiprotocol Label Switching. An emerging industry standard for the forwarding of packets along the normal routing paths (sometimes called MPLS hop-by-hop forwarding).
prefix—The network address portion of an IP address. A prefix is specified by a network and mask and is generally represented in the format network/mask. The mask indicates which bits are the network bits. For example, 1.0.0.0/16 means that the first 16 bits of the IP address are masked, making them the network bits. The remaining bits are the host bits. In this example, the network number is 10.0.
RIB—Routing Information Base. A central repository of routes that contains Layer 3 reachability information and destination IP addresses or prefixes. The RIB is also known as the routing table.
RP—Route Processor. The processor module in the Cisco 7000 series routers that contains the CPU, system software, and most of the memory components that are used in the router. It is sometimes called a supervisory processor.
VPN—Virtual Private Network. The result of a router configuration that enables IP traffic to use tunneling to travel securely over a public TCP/IP network.
VRF—A Virtual Private Network (VPN) routing/forwarding instance. A VRF consists of an IP routing table, a derived forwarding table, a set of interfaces that use the forwarding table, and a set of rules and routing protocols that determine what goes into the forwarding table. In general, a VRF includes the routing information that defines a customer VPN site that is attached to a PE router.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
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.
© 2005—2008 Cisco Systems, Inc. All rights reserved.