Table of Contents

Console Port Usage After a PRE1 Module Switchover
Encrypted Multicast
External Management Stations
Flap Detection on WAN Interfaces During Switchover
Link States Reinitialized After Switchover
MIB Variables Reinitialized After Switchover
SNMP Not Supported During Switchover
Telnet Sessions Disconnected During Switchover

Benefits
Terminology Changes with Cisco IOS Release 12.2(11)BC3
Synchronization

Synchronization During Initialization
Synchronization of Startup Configuration
Incremental Synchronization of the Running Configuration

The RPR+ Switchover Process

Configuring RPR+ on the Cisco uBR10012 Universal Broadband Router

Prerequisites

Verifying RPR+ Configuration

Examples

Upgrading Cisco IOS Software Images

Prerequisites
Creating Additional Disk Space (Optional)
Copying the Cisco IOS Image
Resetting a PRE1 Module or Line Card After Upgrade
Reloading Cisco IOS (Restarting the System)

Troubleshooting Route Processor Redundancy Plus

CHKPT
LCINFO

Supported Standards, MIBs, and RFCs
Technical Assistance

Route Processor Redundancy Plus on the Cisco uBR10012 Universal Broadband Router

April 8, 2003
OL-125118-01 Rev. AC

This document describes the Route Processor Redundancy Plus (RPR+) feature on the Cisco uBR10012 universal broadband router. It includes information on the benefits of RPR+, supported platforms, prerequisites, configuration procedures, examples, and command reference.

Feature Specifications for Route Processor Redundancy Plus on the Cisco uBR10012 Universal Broadband Router

Finding Support Information for Platforms and Cisco IOS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn . You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

Using the Cisco Broadband Cable Command Reference Guide

For the most current information about the Cisco IOS commands described in this document, and additional commands for use with the Cisco uBR10012 router, refer to the Cisco Broadband Cable Command Reference Guide, available on Cisco.com and on the Documentation CD-ROM.

Contents

This document includes the following sections:

Prerequisites for Route Processor Redundancy Plus on the Cisco uBR10012 Universal Broadband Router

To support the Route Processor Redundancy feature, the Cisco uBR10012 universal broadband router must fulfill the following prerequisites:

---

Note    The PRE module is no longer shipping with the Cisco uBR10012 chassis.

Restrictions for Route Processor Redundancy Plus on the Cisco uBR10012 Universal Broadband Router

Console Port Usage After a PRE1 Module Switchover

When an active RP fails, and the standby RP becomes the active RP, you must use the console port on the new active RP to give CLI commands and display statistics for the system. If you have connected your PC or terminal to the console port on an active RP and a switchover occurs, you will no longer be able to access the console, and the display will display "Standby console disabled."

To access the console, move the PC or terminal's serial cable to the console port on the other PRE1 module, which is now acting as the active RP.

Encrypted Multicast

Encrypted multicast is not supported during a line card switchover nor during a PRE1 switchover.

External Management Stations

External management stations lose connectivity with the CMTS during PRE1 switchover. Stations must reestablish connectivity after the switchover between PRE1 modules is complete.

Flap Detection on WAN Interfaces During Switchover

Neighboring routers will detect flapping on WAN interfaces during a switchover. The neighboring routers will reconverge after the switchover is complete.

Note   Cable interfaces do not flap during a switchover. Service may be temporarily suspended for approximately 30 seconds during a switchover and reinitialization, but service to cable interfaces does not stop.

Link States Reinitialized After Switchover

The synchronization of link states is not maintained between the active and standby RP. Link states are re-initialized after switchover

MIB Variables Reinitialized After Switchover

All MIB variables will be re-initialized following a switchover.

SNMP Not Supported During Switchover

SNMP persistence is not supported through a PRE1 switch over.

Telnet Sessions Disconnected During Switchover

A switchover automatically disconnects any Telnet sessions on the active (failed) RP.

Information about Route Processor Redundancy Plus on the Cisco uBR10012 Universal Broadband Router

When two route processors (RPs) are installed in a Cisco uBR10012 router chassis, one RP acts as the active RP, and the other acts as a backup, or standby, RP. If the active RP fails, or is removed from the system, the standby RP detects the failure and initiates a switchover. During a switchover, the standby RP assumes control of the router, connects with the network interfaces, and activates the local network management interface and system console.

Using the RPR+ feature, the standby RP is fully initialized and configured. This allows RPR+ to dramatically shorten the switchover time if the active RP fails, or if a manual switchover is performed. Because both the startup config and running config are continually synchronized from the active to the standby RP, line cards are not reset during a switchover. The interfaces remain up during this transfer, so neighboring routers do not detect a link flap (that is, the link does not go down and back up).

Each RP contains all the resources required to operate the router, such as bootflash memory, Flash disks, Ethernet ports, and console port. In the default operation, the secondary RP also synchronizes the major systems files, such as the Cisco IOS startup configuration file, so that during a switchover, the secondary RP can duplicate the active RP's configuration. This process also resets the cable and network uplink interfaces.

This section describes the switchover process with RPR+, including synchronization between the active and standby RPs, and includes the following topics:

Benefits

RPR+ is part of an ongoing effort to improve high availability in Cisco uBR10012 router.

DOCSIS Stateful Switchover (DSSO)

DOCSIS stateful switchover (DSSO) increases service uptime by instantaneously switching over between dual route processors should one processor fail. Switchover takes place without resetting or reloading line cards or affecting related subsystems or processes. The advantage of DSSO (with RPR+) is that a switchover between the primary and standby RP will not require the cable interfaces to be reset, nor will the modems reregister or go offline. Furthermore, the cable modems retain their service IDs (SIDs) through the switchover.

Standard RPR

In standard RPR, the system implemented Extended High System Availability (EHSA) redundancy, wherein the standby RP suspended its initialization midway through the startup process. To complete the initialization during a switchover, all line cards were reset and the switch fabric was reinitialized. Since initialization of the standby RP was suspended before configuration was parsed, chassis discovery and startup config parsing were conducted during the switchover.

Improved Switchover Time with RPR+

RPR+ provides a faster switchover by fully initializing and fully configuring the standby RP. The configuration data on the standby RP is fully synchronized with the active RP. With RPR+, the communication with line cards is reinitialized, but the line cards are not reset.

Supported Cable Interface Line Cards and Interface Modules

Commencing with Cisco IOS Release 12.2(11)BC3, the Cisco uBR10012 router supports the following cable interface line cards and interface modules with RPR+ and PRE1 modules:

Terminology Changes with Cisco IOS Release 12.2(11)BC3

In Cisco IOS Release 12.2(11)BC3 and later, the following High Availability terms for the Cisco uBR10012 universal broadband router have been changed

:

Synchronization

To achieve the benefits of RPR+, the chassis and slot configuration information is synchronized from the active RP to the standby RP at startup and whenever changes to the active RP configuration occur. This synchronization occurs in two separate phases:

1. When a standby RP first comes online, the configuration information is synced in bulk from the active RP to the standby RP.

2. When configuration changes occur, an incremental sync from the active RP to the standby RP is conducted. Incremental syncs contain either the modifications to the shelf configuration or the trigger that caused the modification.

Synchronization During Initialization

When a system with RPR+ is initialized, the active RP performs a chassis discovery (discovery of the number and type of line cards and fabric cards in the system) and parses the startup configuration file.

The active RP then synchronizes this data to the standby RP and instructs the standby RP to complete its initialization. This method ensures that both RPs contain the same configuration information.

Note   Even though the standby RP is fully initialized, it interacts only with the active RP to receive incremental changes to the configuration files as they occur. CLI commands on the standby RP are not supported.

Synchronization of Startup Configuration

The startup config is a text file stored in the RP's NVRAM. During system startup, the startup config file is copied from the active RP to the standby RP. Any existing startup config file on the standby RP is overwritten.

The startup config file is also synced whenever you perform the following operations:

Incremental Synchronization of the Running Configuration

When both RPs are fully initialized, any further changes to the running config are synced to the standby RP as they occur.

CLI commands

CLI changes to the running config are synced from the active RP to the standby RP. In effect, the CLI command is run on both the active and the standby RP.

SNMP SET Commands

Configuration changes caused by an SNMP SET are also synced on a case-by-case basis. Currently only two SNMP configuration SETs are supported on the Cisco uBR10012 router:

Changes to Chassis State

The RPR+ Switchover Process

A switchover occurs when the standby RP takes over responsibilities from the active RP. The switchover can occur automatically if the standby RP has determined that the active RP has failed, or an operator can initiate a manual switchover whenever desired.

A switchover triggers the following events:

1. If this is a manual switchover, the active RP verifies that the standby RP is present and is running Cisco IOS software that supports the RPR feature. If so, it instructs the standby RP to begin switchover procedures, and the active RP either attempts to reload its configured Cisco IOS software image or enters ROM monitor mode, depending on the setting of its configuration register.

2. The standby RP completes its initialization procedures, which includes completely loading the Cisco IOS software, verifying the physical components of the Cisco uBR10012 chassis, and parsing the startup configuration file. The standby RP is configured identically to the previous active RP, including the IP address for its onboard FastEthernet management interface.

3. The standby RP assumes responsibility as the active RP and brings the Cisco uBR10012 chassis into a known state, which includes resetting all installed and enabled line cards and respective interfaces.

---

Note    Resetting the Gigabit Ethernet and OC-12 POS line cards will interrupt traffic for approximately 30 seconds. The cable interface will not be reset, and in support of DOCSIS requirements, the cable modems will not go offline.

---

---

Note    Depending on the network configuration and on the configuration of the Ethernet/FastEthernet interfaces, the network could take between 3 to 25 seconds after an RPR+ switchover before all end-to-end connections are fully restored. During that time it is possible that some packets might be dropped.

---

4. The new active RP begins normal systems operations, including passing traffic.

Note   Depending on the setting of the PRE1 module's config register, it either reloads the Cisco IOS software or is left in the ROM monitor state. If the PRE1 module is in the ROM monitor state, it does not begin functioning as a standby RP until it is reloaded with the hw-module sec-cpu reset command.

Note   The backup PRE1 module starts forwarding traffic immediately to cable modems, presuming that the interfaces are up, and that all the FIB, adjacency, service flow, classifiers, and Virtual Traffic Management System (VTMS) queue information are correctly configured.

How to Configure, Verify, and Troubleshoot Route Processor Redundancy Plus on the Cisco uBR10012 Universal Broadband Router

This section provides the following procedures to configure and verify RPR+ and high availability on the Cisco uBR10012 route.

Configuring RPR+ on the Cisco uBR10012 Universal Broadband Router

The default redundancy mode in the Cisco uBR10012 router is standard Route Processor Redundancy (RPR). Perform the steps below to enable RPR+ on the Cisco uBR10012 router.

Prerequisites

To enable RPR+, both route processors must be running the same version of Cisco IOS software.

Note   If necessary, refer to the "Upgrading Cisco IOS Software Images" section on page 14 to change the image on the Cisco uBR10012 router. Reload is required.

SUMMARY STEPS

1. enable

2. configure terminal

3. main-cpu

4. auto-sync option

5. no auto-sync option (optional)

6. CTRL/Z

7. copy running-config startup-config

DETAILED STEPS

Verifying RPR+ Configuration

Perform the steps below to verify that RPR+ is configured on the Cisco uBR10012 router:

SUMMARY STEPS

1. enable

2. show startup-config

3. show redundancy

DETAILED STEPS

Examples

If a switchover has occurred, the show redundancy command displays information similar to the following, showing that the active RP has changed slots (in this case, moving from slot A to slot B):

If the standby RP is not installed or is not operational, the show redundancy command displays information similar to the following:

Note   The show redundancy command shows whether the PRE1 A slot or PRE1 B slot contains the active (Primary) PRE1 module. The other PRE1 slot will always be marked as Secondary, even if a second PRE1 module is not installed.

Both the active and standby RPs have active file systems that can be accessed to store and transfer files. Table 1 lists the available file systems, the filenames that you can use with CLI commands to access the file systems, and a short description of each.

You can use the Privileged EXEC commands dir, del, and copy to manage the contents of the file systems. You can also use the commands mkdir and rmdir to create and remove directories on Flash disks. You cannot use the commands squeeze and undelete on Flash disks.

Note   For more information about using these file systems, see the "File Management" manual in the Cisco IOS Release 12.2 Configuration Fundamentals Configuration Guide.

Upgrading Cisco IOS Software Images

RPR+ is enabled by default with the Cisco IOS Release 12.2(11)BC3 and later releases. Use this set of procedures when you need to upgrade your Cisco IOS to a release that supports RPR+ on the Cisco uBR10012 router.

Cisco IOS software upgrade involves these three procedures:

Prerequisites

Note   You are required to have the same image on both the active and standby RPs in order to support RPR+. If one or more RPs does not have an RPR+ image, the router reverts to RPR mode on both RPs.

Creating Additional Disk Space (Optional)

(Optional) To create additional disk space in preparation for the RPR+ image, issue the following commands from global configuration mode on the active and/or standby RPs (where slot is the RP slot number and filename is the RPR+ image file name).

SUMMARY STEPS

1. delete slot slot:filename or delete sec-slot slot:filename

2. squeeze flash:

DETAILED STEPS

Copying the Cisco IOS Image

To copy the Cisco IOS image from a TFTP server, and to set the boot variable on the active RP, issue the following commands from global configuration mode (where filkename is the RPR+ image file name).

SUMMARY STEPS

1. copy tftp://tftp-server/filename bootflash:filename
or
copy tftp://tftp-server/filename sec-bootflash:filename

2. boot system bootflash:filename

3. write memory

4. show bootvar

DETAILED STEPS.

Resetting a PRE1 Module or Line Card After Upgrade

To reset a particularRoute Processor (RP) or a particular line card, use the hw-module reset command in privileged EXEC mode.

hw-module {main-cpu | pre {A|B} | sec-cpu | slot slot-number | subslot slot/card} reset [hold | release]

Syntax Description

SUMMARY STEPS

1. hw-module reset

DETAILED STEPS.

Reloading Cisco IOS (Restarting the System)

To reload the operating system, use the reload command in privileged EXEC mode.

Note   This reload is required if you are reloading an RPR+ image, but optional otherwise. The reload command restarts the entire system, including both the active and standby RPs.

1. reload

DETAILED STEPS.

Note   If you are upgrading from a Cisco IOS image previously configured with RPR+ to a newer image with RPR+, the procedure is now complete. When the new active RP comes up, it will automatically configure RPR+ from the configuration information in the startup config (synced from old active RP).

For testing or maintenance purposes, you may need to perform a manual switchover where your standby RP becomes your active RP. Perform the following steps to force a manual switchover between RPs.

SUMMARY STEPS

1. show cable modem

2. redundancy force-failover main-cpu

3. show cable modem

DETAILED STEPS

Troubleshooting Route Processor Redundancy Plus

If RPR+ is not enabled after mode rpr-plus is run, verify that both the active and standby RPs are running the Cisco IOS Release 12.2(11)BC3 or higher. If the active RP detects a different version of the image on the standby RP, the system automatically reverts to standard RPR behavior.

Configuration Examples for Route Processor Redundancy Plus on the Cisco uBR10012 Universal Broadband Router

The following output from the show redundancy, show running, and show version commands display a Cisco uBR10012 router supporting RPR+ with active and standby RPs. For additional debugging information, refer to the "Command Reference" section.

Command Reference

This section describes the following commands that configure and monitor RPR+ on the Cisco uBR10012 router:

Note   For additional information about the Cisco IOS commands supported by the Cisco uBR10012 router, refer to the Cisco Broadband Cable Command Reference Guide on Cisco.com.

debug checkpoint

The Checkpointing Facility is a software subsystem by which information is transferred from the active RP to the standby RP. To enable debugging of the Checkpointing Facility (CF) subsystem on the Cisco uBR10012 router, use the debug checkpoint command in privileged EXEC mode. To disable debugging output, use the no form of the command.

debug checkpoint [all | errors | messages | temporary | timers]

no debug checkpoint [all | errors | messages | temporary | timers]

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug checkpoint command enables debugging of the Checkpoint Facility (CF) subsystem, which manages the passing of messages from the Active to Standby cards. It also handles sequencing and throttling, as needed, during redundancy operations.

Examples

The following example shows how to enable debugging messages for the CF subsystem:

Related Commands

debug cr10k-rp

To enable debugging of the subsystems on the active Performance Routing Engine (PRE1) module on the Cisco uBR10012 router, use the debug cr10k-rp pkt command in privileged EXEC mode. To disable debugging output, use the no form of the command.

debug cr10k-rp [cli | drv | ha-all | ha-msg | ha-timing | ipc | oir | pkt [conditional [peek byte] ] | sid | spec]

no debug cr10k-rp [cli | drv | ha-all | ha-msg | ha-timing | ipc | oir | pkt [conditional
[peek byte] ] | sid | spec]

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug cr10k-rp pkt command enables debugging of the different subsystems that are active on the PRE1 modules in the Cisco uBR10012 router. You can perform general debugging by giving the command without any options, or you can limit the debugging output to a specific subsystem by specifying one of the optional keywords.

In Cisco IOS Release 12.2(11)BC2 and later releases, you can use the conditional option, together with the debug cable mac-address and debug cable interface commands, to display information about selected packets. The command will display only those packets that match the specified cable interface or MAC address options.

Together with the conditional option, you can also optionally specify the peek keyword to create specifically match only those packets that contain a matching MAC address at the specified location in the datagram. This can be useful for examining certain types of packets, such as DHCP or ARP packets.

Examples

The following example shows typical output for CLI debugging messages:

The following example shows typical output for IPC debugging messages:

The following example shows typical output for IPC debugging messages when you are shutting down and reenabling a cable interface:

The following example shows a typical display for the debug cr10k-rp pkt conditional command, which displays packets for SID 2 on cable interface 6/1/0:

The following example shows how to enable conditional debugging of packets, displaying only those packets that contain the desired mac address at byte 92 in the datagram:

Both types of packet debugging generate output similar to the following example:

Table 2 explains the information contained in the display for each packet:

The following example shows typical output for SID debugging messages:

The following example shows typical output for spectrum management debugging messages for a particular interface:

The following example shows the typical messages for the ha-timing option. These messages show the total time it takes to synchronize all of the cable modems on a cable interface after a switchover, as well as the total time it takes for all cable modems to recover and come online. These messages also show the total time it took the HCCP and DOCSIS protocol subsystems to synchronize after a switchover.

The following example shows the typical messages for the ha-msg option. These messages show the total time it takes to synchronize all of the cable modems on a cable interface after a switchover, as well as the total time it takes for all cable modems to recover and come online. These messages also show the total time it took the HCCP and DOCSIS protocol subsystems to synchronize after a switchover.

Related Commands

debug redundancy

To enable debugging of the Route Processor Redundancy (RPR) feature and its background procedures, use the debug redundancy command in Privileged EXEC mode.

debug redundancy {alarms | all | configsync | fsm | keepalive | peer-monitor | services | timesync}

Syntax Description

Command Modes

Privileged EXEC

Command History

Examples

The following example shows all redundancy debugging messages being enabled:

The following example shows typical messages that the debug redundancy alarms command displays:

The following example shows the typical state changes that the debug redundancy fsm command displays when the standby RP is reset:

The following example shows the messages that are displayed by the debug redundancy keepalive command:

Related Commands

hw-module reset

To reset a particular Performance Routing Engine (PRE1) module or a particular line card, use the hw-module reset command in privileged EXEC mode.

hw-module {main-cpu | pre {A|B} | sec-cpu | slot slot-number | subslot slot/card} reset [hold | release]

Syntax Description

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The hw-module reset command typically is used to reset a standby PRE1 module so that it can load a new version of Cisco IOS software. However, this command can also be used to reset the active PRE1 module, as well as any other line card in the Cisco uBR10012 chassis.

Caution   If the standby PRE1 module is installed and configured, resetting the active PRE1 module triggers a failover, so that the standby PRE1 module becomes the active PRE1 module.

Note   The hold and release options are not needed for normal operations but are typically used for debugging and lab tests.

The following example shows the standby PRE1 module being reset:

The following example shows the active PRE1 module being reset and kept in the reset state (which will trigger a failover to the standby PRE1 module):

The following example shows the PRE1 module in PRE slot B being reset:

Note   The hw-module pre B reset command resets the PRE1 module that is physically present in slot B, regardless of whether the module is the active or standby PRE1 module.

Related Commands

main-cpu

To enter main-CPU redundancy configuration mode, so that you can configure the synchronization of the active and secondary Performance Routing Engine (PRE1) modules, use the main-cpu command in redundancy configuration mode.

main-cpu

Syntax Description

This command has no keywords or arguments.

Defaults

No default behavior or values

Command Modes

Redundancy configuration

Command History

Usage Guidelines

When you enter main-CPU redundancy configuration mode, the prompt changes to the following:

After you enter main-CPU redundancy configuration mode, you can use the auto-sync command to specify which files are synchronized between the active and standby RPs. In Cisco IOS Release 12.2(11)BC3 and later releases, you can also use the switchover timeout command to specify the amount of time that the standby RP should wait when it first detects that the active RP is not active and when it initiates a switchover and becomes the active RP.

To leave main-CPU redundancy configuration mode and to return to redundancy configuration mode, use the exit command.

Examples

The following example shows how to enter main-CPU redundancy mode and the commands that are available there:

Related Commands

redundancy force-failover main-cpu

To force a failover, so that the standby Performance Routing Engine (PRE1) module becomes the active PRE1 module, use the redundancy force-failover main-cpu command in privileged EXEC mode.

redundancy force-failover main-cpu

Syntax Description

This command has no keywords or arguments.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The redundancy force-failover main-cpu command initiates a manual failover, so that the standby PRE1 module becomes the active PRE1 module and assumes full responsibilities for router operations. This command requires that both PRE1 modules are running a Cisco IOS software image that supports the Route Processor Redundancy (RPR) feature.

A manual failover is typically done for one of the following reasons:

A failover can also be manually initiated by removing the active PRE1 module from the chassis, but using the redundancy force-failover main-cpu command provides a more graceful failover, without generating hardware alarms.

Tip Wait two to three minutes after a failover before switching the system back to the original PRE1 module, so as to allow the system to stabilize and so that both PRE1 modules are ready for the switch.

Examples

The following example shows a failover being manually initiated:

Note   Pressing Enter or y confirms the action and begins the failover. Pressing any other key aborts the failover and returns control to the current active PRE1 module.

The following example shows a failover being attempted but failing because the standby PRE1 module is either not ready, not available, or not installed:

Note   In some versions of Cisco IOS software, a failed software switchover will show the following message: Unable to communicate with standby PRE, switchover aborted.

The following example shows the complete information for a forced switchover using the redundancy force-failover main-cpu command.

Note   The output of your system may vary depending on the number of line cards and interfaces configured.

secondary aux

To enable the auxiliary port on the standby PRE1 module, use the secondary aux command in redundancy configuration (main-cpu) mode mode. To disable the auxiliary port, use the no form of this command.

secondary aux

no secondary aux

Syntax Description

This command has no keywords or arguments.

Defaults

The auxiliary port on the standby RP is disabled.

Command Modes

Redundancy configuration, main-cpu mode

Command History

Examples

The following example shows how to enable the auxiliary port on the standby PRE1 module.

Related Commands

show cable modem

After a switchover occurs, you can use the show cable modem command to display the status of all recognized cable modems. This status should be similar, if not identical, to the status before the switchover. The CMTS will be able to communicate with all cable modems at the DOCSIS MAC layer (using the modem's MAC address). However, the CMTS will not be able to communicate with a cable modem or CPE device at the IP layer (using the IP address) until the cable modem (or one of its CPE devices) transmits an IP packet.

This allows the CMTS to rebuild its IP address table using the IP addresses of devices that are actually active on the network, instead of using the previous information, which could have become stale since the switchover.

To display information for the registered and unregistered CMs, use the show cable modem command in privileged EXEC mode.

show cable modem [ip-address | interface | mac-address] [options]

Note   Several options in the show cable modem command do not pause the screen to display the information page by page, even if the terminal length command has been used to set the page size of your terminal. Paging and pausing the display could result in outdated or stale information for CMs, and thus produce an incorrect snapshot of the system's current CM state. To capture or review this information, use your terminal program's capture buffer to save the information to a file, and then review it offline.

Syntax Description

Examples

The following show cable modem command output shows the registered and unregistered CMs supported by the active RP prior to the manual switchover. The information from the show cable modem command can be used before and after manual switchover to verify success (refer also to redundancy force-failover main-cpu).

show chassis eeprom

The show version command identifies the PRE-1 modules by name. Use the show chassis EEPROM command to verify the Top Level Assembly Part Number of a PRE1 module. This information is displayed as the last item in the RP EEPROM contents as shown below.

show chassis

Syntax Description

This command has no keywords or arguments.

Command Modes

Privileged EXEC

Command History

Examples

Router# show chassis eeprom

Backplane EEPROM contents:

Number of Slots : 14

Hardware Revision : 1.1

Top Assy. Part Number : 800-09026-01

Board Revision : A0

Product Number : UBR10012

CLEI Code : IPM1400CRA

Deviation Number : 0-0

Fab Version : 01

PCB Serial Number : TBC06062909

Chassis Serial Number : TBA06060427

Chassis MAC Address : 0005.00e4.5c96

MAC Address block size : 598

RMA Test History : 00

RMA Number : 0-0-0-0

RMA History : 00

RP EEPROM contents:

Hardware Revision : 1.0

Part Number : 73-7041-02

Board Revision : A0

Deviation Number : 0-0

Fab Version : 02

PCB Serial Number : CAB0609MSCA

RMA Test History : 00

RMA Number : 0-0-0-0

RMA History : 00

Top Assy. Part Number : 800-17437-03

FP EEPROM contents:

Hardware Revision : 1.0

Part Number : 73-7042-03

Board Revision : A0

Deviation Number : 0-0

Fab Version : 03

PCB Serial Number : CAB0610MU22

RMA Test History : 00

RMA Number : 0-0-0-0

RMA History : 00

show checkpoint

The Checkpointing Facility is a software subsystem by which information is transferred from the active RP to the standby RP. To display information about the Checkpoint Facility (CF) subsystem on a Cisco CMTS, use the show checkpoint command in privileged EXEC mode.

show checkpoint {clients | statistics}

Syntax Description

clients	Displays a list of current checkpoint clients.
statistics	Displays the current status for checkpoint operations.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(11)BC3	This command was introduced to support High Availability (HA) redundancy operations.

Usage Guidelines

The Checkpoint Facility (CF) subsystem manages the passing of messages from the active to standby interfaces. It also handles sequencing and throttling, as needed during redundancy operations. The show checkpoint command displays information about the clients (other processes on the CMTS that are sending checkpoint messages) and run-time status for checkpoint operations.

Examples

The following shows typical output for the show checkpoint clients command:

Router# show checkpoint clients

Check Point List of Clients

CHKPT on ACTIVE server.

Client Name Client ID Msg Send Msg len Bundling

(number of) (Total)

-----------------------------------------------------------

CHKPT DevTest 3 0 0 On

CHKPT EXAMPLE 2 0 0 On

CR10K RP CHKPT 20 0 0 On

Router#

The following shows typical output for the show checkpoint statistics command:

Router# show checkpoint statistics

Check Point Status

CHKPT on ACTIVE server.

Number of chkpt messages currently in hold queue 0

CHKPT MAX MTU size = 1422

IPC MAX MTU size = 4096

CHKPT Pending msg timer = 100 ms

Related Commands

Command	Description
hccp authentication	Changes the minimum time between frequency hops.
hccp check version	Exits bypass version mode, and returns to normal HCCP operation.
hccp ds-switch	Specifies the downstream upconverter module for a Working CMTS or Protect CMTS (deprecated command).
hccp protect	Allows you to configure a Cisco CMTS to be a Protect CMTS for a specified Working CMTS in a 1+1 redundancy environment.
hccp working	Allows you to designate a Cisco CMTS to be a Working CMTS in a 1+1 redundancy environment.
show cable ha	Displays information about High Availability operations and configuration.
show hccp	Displays information for all cable interfaces on which one or more HCCP groups and authentication modes have been configured.
show hccp interface	Displays group information for a specific cable interface on which one or more groups and authentication modes have been configured.

show redundancy

To display the current redundancy status, use the show redundancy command in privileged EXEC mode.

show redundancy {clients | counters | history| states}

Syntax Description

This command has the following options that provide additional RPR+ information.

clients	Provides a Redundancy Facility (RF) client list.
counters	Lists Redundancy Facility (RF) operational counters.
history	Summarizes Redundancy Facility (RF) history.
states	Lists Redundancy Facility (RF) states.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(4)XF1	This command was introduced for the Cisco uBR10012 router.
12.2(11)BC3	The command was enhanced to show the version of Cisco IOS software that is running on the secondary PRE module.

Usage Guidelines

The show redundancy command shows whether the PRE A slot or PRE B slot contains the active (Primary) Performance Routing Engine (PRE1) module, the status of the standby RP, and the values for the standby RP's boot variables and configuration register. In Cisco IOS Release 12.2(13)BC1 and later releases, it also shows the version of Cisco IOS software that is running on the secondary PRE module.

---

Note   The show redundancy command always shows the correct location of the active RP. The other PRE slot will always be marked as Secondary, even if a standby RP is not installed.

---

Examples

The following example shows a typical display from the show redundancy command. The active RP is in PRE slot A, and the standby RP is in PRE slot B:

Router# show redundancy

PRE A (This PRE) : Primary

PRE B : Secondary

Redundancy state is REDUNDANCY_PEERSECONDARY_INITED

Secondary PRE information....

Secondary is up.

Secondary has 524288K bytes of memory.

Secondary BOOT variable = bootflash:ubr10k-k8p6-mz.999-99.122BC_UB_030303,1;

Secondary CONFIG_FILE variable =

Secondary BOOTLDR variable =

Secondary Configuration register is 0x0

Secondary version:

Cisco Internetwork Operating System Software

IOS (tm) 10000 Software (UBR10K-K8P6-M), Version 12.2(122BC.030303.)

Copyright (c) 1986-2003 by cisco Systems, Inc.

Compiled Mon 03-Mar-03 21:23 by

The following example shows the same display but after a switchover has occurred. The show redundancy command now shows that the active (primary) RP has changed slots (in this case, moving from slot A to slot B):

Router# show redundancy

PRE A : Secondary

PRE B (This PRE) : Primary

Redundancy state is REDUNDANCY_PEERSECONDARY_INITED

Secondary PRE information....

Secondary is up.

Secondary BOOT variable = bootflash:ubr10k-k8p6-mz

Secondary CONFIG_FILE variable =

Secondary BOOTLDR variable = bootflash:c10k-eboot-mz

Secondary Configuration register is 0x2

Secondary version:

Cisco Internetwork Operating System Software

IOS (tm) 10000 Software (UBR10K-K8P6-M), Released Version 12.2(13)BC2

Copyright (c) 1986-2003 by cisco Systems, Inc.

Compiled 26 08-Feb-03 11:28 by texbnt

Router#

The following example shows a typical display when the standby RP is not installed or is not operational. The standby RP is shown as not up, and its boot variables and configuration register are not shown.

Router# show redundancy

PRE A (This PRE) : Primary

PRE B : Secondary

Redundancy state is REDUNDANCY_PEERSECONDARY_NONOPERATIONAL

Secondary PRE information....

Secondary PRE is not up

Router#

The following example shows a typical display for show redundancy clients:

Router# show redundancy clients

clientID = 0 clientSeq = 0 RF_INTERNAL_MSG

clientID = 25 clientSeq = 130 CHKPT RF

clientID = 5 clientSeq = 170 RFS client

clientID = 50 clientSeq = 530 Slot RF

clientID = 65000 clientSeq = 65000 RF_LAST_CLIENT

The following example shows a typical display for show redundancy counters:

Router# show redundancy counters

Redundancy Facility OMs

comm link up = 1

comm link down down = 0

invalid client tx = 0

null tx by client = 0

tx failures = 0

tx msg length invalid = 0

client not rxing msgs = 0

rx peer msg routing errors = 0

null peer msg rx = 0

errored peer msg rx = 0

buffers tx = 1009

tx buffers unavailable = 0

buffers rx = 1006

buffer release errors = 0

duplicate client registers = 0

failed to register client = 0

Invalid client syncs = 0

The following example shows a typical display for show redundancy history:

Router# show redundancy history

00:00:00 client added: RF_INTERNAL_MSG(0) seq=0

00:00:00 client added: RF_LAST_CLIENT(65000) seq=65000

00:00:00 client added: CHKPT RF(25) seq=130

00:00:01 client added: Slot RF(50) seq=530

00:00:15 client added: RFS client(5) seq=170

00:00:16 *my state = INITIALIZATION(2) *peer state = DISABLED(1)

00:00:16 RF_PROG_INITIALIZATION(100) RF_INTERNAL_MSG(0) op=0 rc=11

00:00:16 RF_PROG_INITIALIZATION(100) CHKPT RF(25) op=0 rc=11

00:00:16 RF_PROG_INITIALIZATION(100) RFS client(5) op=0 rc=11

00:00:16 RF_PROG_INITIALIZATION(100) Slot RF(50) op=0 rc=11

00:00:16 RF_PROG_INITIALIZATION(100) RF_LAST_CLIENT(65000) op=0 rc=11

00:00:16 *my state = NEGOTIATION(3) peer state = DISABLED(1)

00:00:16 RF_EVENT_GO_ACTIVE(512) op=0 rc=0

00:00:16 *my state = ACTIVE-FAST(9) peer state = DISABLED(1)

00:00:16 RF_STATUS_MAINTENANCE_ENABLE(403) CHKPT RF(25) op=0 rc=0

00:00:16 RF_STATUS_MAINTENANCE_ENABLE(403) RFS client(5) op=0 rc=0

00:00:16 RF_STATUS_MAINTENANCE_ENABLE(403) Slot RF(50) op=0 rc=0

00:00:16 RF_PROG_ACTIVE_FAST(200) RF_INTERNAL_MSG(0) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_FAST(200) CHKPT RF(25) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_FAST(200) RFS client(5) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_FAST(200) Slot RF(50) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_FAST(200) RF_LAST_CLIENT(65000) op=0 rc=11

00:00:16 *my state = ACTIVE-DRAIN(10) peer state = DISABLED(1)

00:00:16 RF_PROG_ACTIVE_DRAIN(201) RF_INTERNAL_MSG(0) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_DRAIN(201) CHKPT RF(25) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_DRAIN(201) RFS client(5) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_DRAIN(201) Slot RF(50) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_DRAIN(201) RF_LAST_CLIENT(65000) op=0 rc=11

00:00:16 *my state = ACTIVE_PRECONFIG(11) peer state = DISABLED(1)

00:00:16 RF_PROG_ACTIVE_PRECONFIG(202) RF_INTERNAL_MSG(0) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_PRECONFIG(202) CHKPT RF(25) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_PRECONFIG(202) RFS client(5) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_PRECONFIG(202) Slot RF(50) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_PRECONFIG(202) RF_LAST_CLIENT(65000) op=0 rc=11

00:00:16 *my state = ACTIVE_POSTCONFIG(12) peer state = DISABLED(1)

00:00:16 RF_PROG_ACTIVE_POSTCONFIG(203) RF_INTERNAL_MSG(0) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_POSTCONFIG(203) CHKPT RF(25) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_POSTCONFIG(203) RFS client(5) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_POSTCONFIG(203) Slot RF(50) op=0 rc=11

00:00:16 RF_PROG_ACTIVE_POSTCONFIG(203) RF_LAST_CLIENT(65000) op=0 rc=11

00:00:16 *my state = ACTIVE(13) peer state = DISABLED(1)

00:00:16 RF_PROG_ACTIVE(204) RF_INTERNAL_MSG(0) op=0 rc=11

00:00:16 RF_PROG_ACTIVE(204) CHKPT RF(25) op=0 rc=11

00:00:16 RF_PROG_ACTIVE(204) RFS client(5) op=0 rc=11

00:00:16 RF_PROG_ACTIVE(204) Slot RF(50) op=0 rc=11

00:00:16 RF_PROG_ACTIVE(204) RF_LAST_CLIENT(65000) op=0 rc=11

00:00:25 Configuration parsing complete

00:00:30 System initialization complete

00:03:27 *my state = ACTIVE(13) *peer state = UNKNOWN(0)

00:03:29 RF_STATUS_PEER_PRESENCE(400) op=1 rc=0

00:03:29 RF_STATUS_PEER_PRESENCE(400) CHKPT RF(25) op=1 rc=0

00:03:29 RF_STATUS_PEER_PRESENCE(400) RFS client(5) op=1 rc=0

00:03:29 RF_STATUS_PEER_PRESENCE(400) Slot RF(50) op=1 rc=0

00:03:34 RF_STATUS_PEER_COMM(401) op=1 rc=0

00:03:34 RF_STATUS_PEER_COMM(401) CHKPT RF(25) op=1 rc=0

00:03:34 RF_STATUS_PEER_COMM(401) RFS client(5) op=1 rc=0

00:03:34 RF_STATUS_PEER_COMM(401) Slot RF(50) op=1 rc=0

00:03:34 RF_PROG_PLATFORM_SYNC(300) RF_INTERNAL_MSG(0) op=0 rc=11

00:03:34 RF_PROG_PLATFORM_SYNC(300) CHKPT RF(25) op=0 rc=11

00:03:34 RF_PROG_PLATFORM_SYNC(300) RFS client(5) op=0 rc=11

00:03:34 RF_PROG_PLATFORM_SYNC(300) Slot RF(50) op=0 rc=11

00:03:34 RF_PROG_PLATFORM_SYNC(300) RF_LAST_CLIENT(65000) op=0 rc=0

00:03:34 RF_EVENT_CLIENT_PROGRESSION(503) RF_LAST_CLIENT(65000) op=1 rc=0

00:03:34 RF_EVENT_PEER_PROG_DONE(506) RF_LAST_CLIENT(65000) op=300 rc=0

00:03:38 *my state = ACTIVE(13) *peer state = STANDBY COLD(4)

00:03:42 RF_EVENT_START_PROGRESSION(501) op=0 rc=0

00:03:42 RF_EVENT_STANDBY_PROGRESSION(502) RF_INTERNAL_MSG(0) op=5 rc=0

00:03:42 RF_PROG_STANDBY_CONFIG(102) RF_INTERNAL_MSG(0) op=0 rc=11

00:03:42 RF_PROG_STANDBY_CONFIG(102) CHKPT RF(25) op=0 rc=11

00:03:42 RF_PROG_STANDBY_CONFIG(102) RFS client(5) op=0 rc=0

00:03:42 RF_EVENT_CLIENT_PROGRESSION(503) RFS client(5) op=5 rc=0

00:03:47 *my state = ACTIVE(13) *peer state = STANDBY COLD-CONFIG(5)

00:03:48 RF_EVENT_PEER_PROG_DONE(506) RFS client(5) op=102 rc=11

00:03:48 RF_PROG_STANDBY_CONFIG(102) Slot RF(50) op=0 rc=11

00:03:48 RF_PROG_STANDBY_CONFIG(102) RF_LAST_CLIENT(65000) op=0 rc=11

00:03:48 RF_EVENT_CONTINUE_PROGRESSION(504) op=0 rc=0

00:03:48 RF_EVENT_STANDBY_PROGRESSION(502) RF_INTERNAL_MSG(0) op=6 rc=0

00:03:48 RF_PROG_STANDBY_FILESYS(103) RF_INTERNAL_MSG(0) op=0 rc=11

00:03:48 RF_PROG_STANDBY_FILESYS(103) CHKPT RF(25) op=0 rc=11

00:03:48 RF_PROG_STANDBY_FILESYS(103) RFS client(5) op=0 rc=11

00:03:48 RF_PROG_STANDBY_FILESYS(103) Slot RF(50) op=0 rc=11

00:03:48 RF_PROG_STANDBY_FILESYS(103) RF_LAST_CLIENT(65000) op=0 rc=11

00:03:48 RF_EVENT_CONTINUE_PROGRESSION(504) op=0 rc=0

00:03:48 RF_EVENT_STANDBY_PROGRESSION(502) RF_INTERNAL_MSG(0) op=7 rc=0

00:03:48 RF_PROG_STANDBY_BULK(104) RF_INTERNAL_MSG(0) op=0 rc=11

00:03:48 RF_PROG_STANDBY_BULK(104) CHKPT RF(25) op=0 rc=11

00:03:48 RF_PROG_STANDBY_BULK(104) RFS client(5) op=0 rc=11

00:03:48 RF_PROG_STANDBY_BULK(104) Slot RF(50) op=0 rc=0

00:03:48 RF_EVENT_CLIENT_PROGRESSION(503) Slot RF(50) op=7 rc=0

00:03:48 RF_EVENT_PEER_PROG_DONE(506) Slot RF(50) op=104 rc=11

00:03:48 RF_PROG_STANDBY_BULK(104) RF_LAST_CLIENT(65000) op=0 rc=11

00:03:48 RF_EVENT_CONTINUE_PROGRESSION(504) op=0 rc=0

00:03:48 RF_EVENT_STANDBY_PROGRESSION(502) RF_INTERNAL_MSG(0) op=8 rc=0

00:03:48 RF_PROG_STANDBY_HOT(105) RF_INTERNAL_MSG(0) op=0 rc=11

00:03:48 RF_PROG_STANDBY_HOT(105) CHKPT RF(25) op=0 rc=11

00:03:48 RF_PROG_STANDBY_HOT(105) RFS client(5) op=0 rc=11

00:03:48 RF_PROG_STANDBY_HOT(105) Slot RF(50) op=0 rc=11

00:03:48 RF_PROG_STANDBY_HOT(105) RF_LAST_CLIENT(65000) op=0 rc=0

00:03:48 RF_EVENT_CLIENT_PROGRESSION(503) RF_LAST_CLIENT(65000) op=8 rc=0

00:03:48 RF_EVENT_PEER_PROG_DONE(506) RF_LAST_CLIENT(65000) op=105 rc=0

00:03:51 *my state = ACTIVE(13) *peer state = STANDBY HOT(8)

The following example shows a typical display for show redundancy states:

Router# show redundancy states

my state = 13 -ACTIVE

peer state = 8 -STANDBY HOT

Mode = Duplex

Unit = Primary

Unit ID = 0

Redundancy Mode = Hot Standby Redundancy

Maintenance Mode = Disabled

Manual Swact = Enabled

Communications = Up

client count = 5

client_notification_TMR = 30000 milliseconds

RF debug mask = 0x0

Related Commands

Command	Description
associate	Associates two line cards for Automatic Protection Switching (APS) redundancy protection.
redundancy	Configures the synchronization of system files between the active and standby RPs.
redundancy force-failover main-cpu	Forces a manual switchover between the active and standby RPs.

switchover timeout

To configure the switchover timeout period of the PRE1 module, use the switchover timeout command in redundancy configuration (main-cpu) mode mode. To reset the timeout period to its default value, use the no form of this command.

switchover timeout timeout-period

no switchover timeout

Syntax Description

timeout-period

Specifies the timeout, in milliseconds. The valid range is 0 to 25000 milliseconds (25 seconds), where 0 specifies no timeout period.

Defaults

0

Command Modes

Redundancy configuration, main-cpu mode

Command History

Release	Modification
12.2(11)BC3	This command was introduced for the Cisco uBR10012 router.

Usage Guidelines

The switchover timeout command specifies how long the secondary PRE module should wait when it does not detect a heartbeat from the active RP before initiating a switchover and assuming responsibility as the active RP. If set to 0, the secondaryRP initiates a switchover immediately when the active RP misses a scheduled heartbeat.

Examples

The following example shows how to set the timeout period to 60 milliseconds:

Router# config t

Router(config)# redundancy

Router(config-r)# main-cpu

Router(config-r-mc)# switchover timeout 60

Router(config-r-mc)# exit

Router(config-f)# exit

Router(config)#

Related Commands

Command	Description
main-cpu	Enters main-CPU redundancy configuration mode, so that you can configure the synchronization of the active and standby RPs.
redundancy	Configures the synchronization of system files between the active and standby RPs.
redundancy force-failover main-cpu	Forces a manual switchover between the active and standby RPs.

Error Messages for Route Processor Redundancy Plus on the Cisco uBR10012 Universal Broadband Router

CHKPT

This section describes system error messages that are related to the Checkpoint Facility (CF) subsystem, which manages the passing of messages from the active to standby interfaces, and which also handles sequencing and throttling, as needed during redundancy operations.

%CHKPT-3-IPCPORT: Unable to create IPC port on ([chars]).

Explanation   A severe checkpoint error occurred because the system was unable to allocate the resources needed to create a communications port for the Interprocess Communications (IPC) channel needed to transmit messages.

Recommended Action   Verify that the CMTS is running released software. If the problem persists, copy the error message exactly as it appears, and use the show tech-support command to collect information about the problem. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%CHKPT-3-IPCSESSION: Unable to open an IPC session for communicating with ([chars]). rc= [dec]

Explanation   A severe checkpoint error occurred because the system was unable to establish an Interprocess Communications (IPC) session between interfaces, which is needed to transmit messages.

Recommended Action   Verify that the CMTS is runVning released software. If the problem persists, copy the error message exactly as it appears, and use the show tech-support command to collect information about the problem. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%CHKPT-3-RFREG: Unable to register checkpoint as client of RF.

Explanation   A severe checkpoint error occurred because the system was unable to register with the redundancy facility (RF) so that it could begin the transmission of IPC messages between interfaces.

Recommended Action   Verify that the CMTS is running released software. If the problem persists, copy the error message exactly as it appears, and use the show tech-support command to collect information about the problem. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%CHKPT-4-INVALID: Invalid checkpoint client ID ([dec]).

Explanation   A checkpoint client is using an old or stale client ID. This could be due to a synchronization delay, which typically will resolve itself.

Recommended Action   No action is required.

%CHKPT-4-DUPID: Duplicate checkpoint client ID ([dec]).

Explanation   A checkpoint client is using a client ID that is already assigned to another client. This could be due to a synchronization delay, which typically will resolve itself.

Recommended Action   No action is required.

%CHKPT-3-NOMEM: Unable allocate resource for CF on ([chars]).

Explanation   A severe checkpoint error occurred because the system was unable to allocate the resources (typically memory) on the indicated interface, as needed to create an Interprocess Communications (IPC) channel needed to transmit messages.

Recommended Action   Verify that the CMTS is running released software. If the problem persists, copy the error message exactly as it appears, and use the show tech-support command to collect information about the problem. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%CHKPT-3-ILLEGAL: ILLEGAL call to CF API on ([chars]) by ([chars]).

Explanation   A severe software error occured with the Checkpoint Facility subsystem.

Recommended Action   Verify that the CMTS is running released software. If the problem persists, copy the error message exactly as it appears, and use the show tech-support command to collect information about the problem. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%CHKPT-3-UNKNOWNMSG: Unknown message recieved from peer on standby for client ([dec]).

Explanation   A severe software error occured with the Checkpoint Facility subsystem. This might indicate a Cisco IOS software mismatch between the active and standby interfaces, or between a line card and the PRE module.

Recommended Action   Verify that the CMTS is running released software. Reload the microcode on the affected line cards. If the problem persists, copy the error message exactly as it appears, and use the show tech-support command to collect information about the problem. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%CHKPT-4-DISABLED: Check Pointing is disabled. Client [chars] should not be calling any CF API

Explanation   A checkpoint client has attempted to send an IPC message after redundancy operations have been disabled. This can be due to lost IPC messages or delays in synchronization, which will eventually resolve themselves.

Recommended Action   No action is required.

%CHKPT-4-SENDFAILED: Checkpointing send failed client ([dec])

Explanation   A checkpoint client failed in an attempt to send an IPC message after redundancy operations have been disabled. This can be due to lost IPC messages or delays in synchronization, which will eventually resolve themselves.

Recommended Action   No action is required.

LCINFO

This section describes error messages concerning the operation of line cards that are in the system.

%LCINFO-6-LCRESET: PRE switchover. Reset empty slot [dec/dec]

Explanation   This message can occur during a switchover of PRE modules. The secondary PRE module that initiated the switchover examines each line card slot and issues a hw-module reset command for each slot that does not have a line card that is already running a Cisco IOS image. This ensures that any line cards that were in the process of download a Cisco IOS image at the time of the switchover are properly reset and reloaded.

Recommended Action   No action is required.

Additional References

To access documentation for the Cisco uBR10012 universal broadband router and router components, use the following procedure:

---

Step 1   Go to the Cisco web site at http://www.cisco.com/ .

Step 2   Select Products and Services from the Welcome to Cisco Systems list.

Step 3   Select Cable Products from the Products list.

Step 4   Select Cisco uBR10012 Universal Broadband Router from the Cisco Cable Products list.

Step 5   Select Technical Documentation from the Cisco uBR10012 universal broadband router menu.

To go directly to this web site, enter the following URL in your web browser.

http://www.cisco.com/en/US/products/hw/cable/ps2209/prod_instructions_guides.html

---

The following documents provide additional information about the Cisco uBR10012 universal broadband router, supporting line cards and interface modules, and feature configuration.

Document	Description
Release Notes for Cisco uBR10012 Universal Broadband Router for Cisco IOS Release 12.2 BC	Describes the enhancements and caveats provided in Cisco IOS Release 12.2(11)BC3.
Cisco Broadband Cable Command Reference Guide	Contains the cable-specific commands for the Cisco uBR7100 series, Cisco uBR7200 series, and Cisco uBR10012 universal broadband routers.
Cisco Cable Modem Termination System Feature Guide	Document describes software features contained in the Cisco Cable Modem Termination System (CMTS). Each chapter describes a feature; the supported releases; benefits; restrictions; any supported standards, MIBs, or RFCs; any prerequisites; and the configuration tasks and examples used to set up and implement the feature. The CMTS features are used by the Cisco uBR7100 series, the Cisco uBR7200 series, and the Cisco uBR10012 universal broadband routers.
Cisco High Availability Initiatives	Article provides an overview of high availability networks and Cisco's related initiatives and hardware.
Documentation for the Cisco uBR10000 Series Universal Broadband Routers	Web page provides an index of primary documentation for the Cisco uBR10012 router, including release notes, Field Replaceable Units, installation and configuration documents.
Technical Support for the Cisco uBR10012 Universal Broadband Router	Web page provides an index of technical support information.

Supported Standards, MIBs, and RFCs

MIBs	MIBs Link
No new or modified MIBs are supported 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

Technical Assistance

Description	Link
Technical Assistance Center (TAC) home page, containing 30,000 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/public/support/tac/home.shtml

Posted: Wed Apr 9 10:26:26 PDT 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.