Cisco cbr Converged Broadband Routers High Availability Configuration Guide for Cisco IOS XE Everest 16.5.1 First Published: 2017-04-07 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883
2017 Cisco Systems, Inc. All rights reserved.
CONTENTS CHAPTER 1 Cisco IOS-XE In-Service Software Upgrade Process 1 Hardware Compatibility Matrix for Cisco cbr Series Routers 1 Information about In-Service Software Upgrade 2 How to Configure In-Service Software Upgrade 3 Configuring Consolidated Package Upgrade 3 Consolidated Package Upgrade 3 Consolidated Package Upgrade Abort 4 Consolidated Package Upgrade Rollback 4 Configuring Subpackage Upgrade 5 Subpackages Upgrade 5 Single SUP Subpackages Upgrade 5 Dual SUPs Subpackages Upgrade 6 Subpackage Upgrade Rollback 7 Linecard Only In-Service Software Upgrade 7 Additional References 8 Feature Information for In-Service Software Upgrade 8 CHAPTER 2 Supervisor Redundancy 11 Hardware Compatibility Matrix for Cisco cbr Series Routers 12 Prerequisites for Supervisor Redundancy 12 Information About Supervisor Redundancy 13 Switchover Procedure 13 Using Redundant File Systems 14 Console Port Usage After Supervisor Switchover 16 Benefits 16 How to Configure Supervisor Redundancy 16 Forcing Switchover 16 Changing the System Boot Behavior 17 iii
Contents Saving a Configuration File to the Bootflash or Hard Disk 21 Verifying the Supervisor Redundancy Configuration 21 Verifying Supervisor Redundancy 22 Verifying Supervisor Switchover 24 Configuration Example for Supervisor Redundancy 25 Additional References 25 Feature Information for Supervisor Redundancy 26 CHAPTER 3 Line Card Redundancy 27 Hardware Compatibility Matrix for Cisco cbr Series Routers 28 Prerequisites for Line Card Redundancy 28 Restrictions for Line Card Redundancy 29 Information About Line Card Redundancy 29 How to Configure Line Card Redundancy 30 Configuring Line Card Manual Switchover 30 Configuring N+1 Line Card Redundancy 31 Verifying the Line Card Redundancy Configuration 32 Additional References 35 Feature Information for Line Card Redundancy 36 iv
CHAPTER 1 Cisco IOS-XE In-Service Software Upgrade Process Cisco cbr-8 Routers support the In-Service Software Upgrades (ISSU) for redundant platforms. 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 Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://tools.cisco.com/itdit/cfn/. An account on http:// www.cisco.com/ is not required. Contents Hardware Compatibility Matrix for Cisco cbr Series Routers, page 1 Information about In-Service Software Upgrade, page 2 How to Configure In-Service Software Upgrade, page 3 Additional References, page 8 Feature Information for In-Service Software Upgrade, page 8 Hardware Compatibility Matrix for Cisco cbr Series Routers Note The hardware components introduced in a given Cisco IOS-XE Release are supported in all subsequent releases unless otherwise specified. 1
Information about In-Service Software Upgrade Cisco IOS-XE In-Service Software Upgrade Process Table 1: Hardware Compatibility Matrix for the Cisco cbr Series Routers Cisco CMTS Platform Cisco cbr-8 Converged Broadband Router Processor Engine Cisco IOS-XE Release 16.5.1 and Later Releases Cisco cbr-8 Supervisor: PID CBR-CCAP-SUP-160G PID CBR-CCAP-SUP-60G PID CBR-SUP-8X10G-PIC Interface Cards Cisco IOS-XE Release 16.5.1 and Later Releases Cisco cbr-8 CCAP Line Cards: PID CBR-LC-8D30-16U30 PID CBR-LC-8D31-16U30 PID CBR-RF-PIC PID CBR-RF-PROT-PIC PID CBR-CCAP-LC-40G-R Cisco cbr-8 Downstream PHY Modules: PID CBR-D30-DS-MOD PID CBR-D31-DS-MOD Cisco cbr-8 Upstream PHY Modules: PID CBR-D30-US-MOD Information about In-Service Software Upgrade Cisco cbr-8 Routers support the In-Service Software Upgrades (ISSU) for redundant platforms. The ISSU process allows software to be updated or otherwise modified while packet forwarding continues with the benefit of LCHA. ISSU supports two different software upgrade modes: Consolidated package mode Subpackages mode For the Cisco cbr Series Routers, ISSU-compatibility depends on the software subpackage being upgraded and the hardware configuration. Consolidated packages are ISSU-compatible in dual SUP configurations only and have other limitations described later in this document. The specific procedures in this document represent supported and tested installation sequences. The Cisco IOS-XE system software allows other installation sequences for special purposes under the guidance of Cisco customer support representatives, but the steps in this document should be followed otherwise. These steps should be followed completely, as the Cisco cbr Series Routers are designed to run one version of Cisco IOS-XE for all consolidated packages and subpackages on an SUP, and running subpackages from different versions of Cisco IOS-XE can cause unexpected router behavior. 2
Cisco IOS-XE In-Service Software Upgrade Process How to Configure In-Service Software Upgrade How to Configure In-Service Software Upgrade This section describes the configuration of the ISSU feature: Configuring Consolidated Package Upgrade Consolidated Package Upgrade Consolidated packages can only be upgraded using ISSU in dual SUP configurations. ISSU is not supported for consolidated package upgrades in single SUP configurations. In service one-shot software upgrade procedure enables you to upgrade or downgrade software using a single command. One-shot ISSU needs minimal user intervention or monitoring. The one-shot upgrade procedure is divided into stages. When a failure occurs, the command execution is stalled and users have to perform the rollback tasks manually. Necessary switchovers are automatically taken care of in one of the upgrade stages. During a switchover, the console and its output are lost. Additional commands are used to connect back to the console. Note One-shot upgrade does not support multiple upgrades at the same time. Before You Begin Be sure to complete the following prerequisites before running the consolidated package upgrade process: The router has two SUPs setup. Standby SUP must be in hot standby mode. Auto-boot is enabled. Both SUPs are in the consolidated package mode, running the same image from the same path. At lease 700MB free space on bootflash of both SUPs. DETAILED STEPS Step 1 Command or Action enable Router> enable Purpose Enables privileged EXEC mode. Enter your password if prompted. 3
Configuring Consolidated Package Upgrade Cisco IOS-XE In-Service Software Upgrade Process Step 2 Command or Action request platform software package install node bootflash: Purpose Upgrades the cbr-8 router using one-shot ISSU procedure. Router# request platform software package install node bootflash:subpkg_3_16/cbrsup-universalk9.03.16.00.s.155-3.s-std.spa.bin Consolidated Package Upgrade Abort DETAILED STEPS Use request platform software package install node abort command to abort the ISSU procedure. When user abort the ISSU, the linecards will be in the different version with the SUP. If the customer believes the new version is not stable, and wants to stop the upgrade, he can use this command to abort the current upgrade process. After this command is entered, the customer needs to check both SUP and LC's states to decide what to do in the next step, eg: rollback. Step 1 Step 2 Command or Action enable Router> enable request platform software package install node abort Purpose Enables privileged EXEC mode. Enter your password if prompted. Abort the ISSU procedure. Router# request platform software package install node abort Consolidated Package Upgrade Rollback If the customer is not satisfied with the new package after the upgrade, the system can go back to previous working state using rollback operation. The linecards that do not in the redundancy group will be reloaded. Note Rollback operation can only go back one step in the history. If the customer wants to go back to an earlier image, downgrade operation should be used. The following steps can be used to perform the consolidated package upgrade rollback. 4
Cisco IOS-XE In-Service Software Upgrade Process Configuring Subpackage Upgrade SUMMARY STEPS 1. enable 2. request platform software package install node rollback DETAILED STEPS Step 1 Step 2 Command or Action enable Router> enable request platform software package install node rollback Purpose Enables privileged EXEC mode. Enter your password if prompted. Go back to previous working state. Router# request platform software package install node rollback Configuring Subpackage Upgrade Subpackages Upgrade Subpackage upgrade allows a subset of the running software to be upgraded. It is intended for patching small and targeted fix instead of full image upgrade. Subpackage upgrade supports both single and dual SUP setup. Single SUP Subpackages Upgrade Before You Begin Be sure to complete the following prerequisites before running the ISSU process: Config register autoboot enabled. Target patch copied to active SUP in the same directory of the packages.conf file system is booted up with. If needed copy patch info file to SUP. Enough bootflash disk space on SUP. 5
Configuring Subpackage Upgrade Cisco IOS-XE In-Service Software Upgrade Process DETAILED STEPS Step 1 Command or Action enable Purpose Enables privileged EXEC mode. Enter your password if prompted. Step 2 Router> enable request platform software package install rp rp-slot file bootflash: Upgrades the cbr-8 router with one SUP using subpackages ISSU procedure. Router# request platform software package install rp 1 file bootflash:cbrsup-universalk9.03.17.00.s.156-1.s-std.spa.bin Dual SUPs Subpackages Upgrade Before You Begin Be sure to complete the following prerequisites before running the ISSU process: Standby SUP must be in hot standby. Config register autoboot enabled. Both SUP in sub-package mode, running same base image and patches from same path. Target patch copied to active SUP in the same directory of the packages.conf file system is booted up with. If needed copy patch info file to both SUPs. Enough bootflash disk space on both SUPs. DETAILED STEPS Step 1 Step 2 Command or Action enable Router> enable request platform software package install node file bootflash: Router# request platform software package install node file bootflash:cbrsup-universalk9.03.17.00.s.156-1.s-std.spa.bin Purpose Enables privileged EXEC mode. Enter your password if prompted. Upgrades the cbr-8 router with dual SUPs using subpackages ISSU procedure. 6
Cisco IOS-XE In-Service Software Upgrade Process Linecard Only In-Service Software Upgrade Subpackage Upgrade Rollback If the customer is not satisfied with the new package after the upgrade, the system can go back to previous working state using rollback operation. The linecards that do not in the redundancy group will be reloaded. Note Rollback operation can only go back one step in the history. If the customer wants to go back to an earlier image, downgrade operation should be used. The following steps can be used to perform the subpackage upgrade rollback. SUMMARY STEPS 1. enable 2. request platform software package install rp 0 rollback DETAILED STEPS Step 1 Step 2 Command or Action enable Router> enable request platform software package install rp 0 rollback Purpose Enables privileged EXEC mode. Enter your password if prompted. Go back to previous working state. Router# request platform software package install rp 0 rollback Linecard Only In-Service Software Upgrade If the upgrade fails or is manually aborted at linecard upgrade stage, user can initiate linecard only upgrade. Use request platform software package install node linecard-only command to upgrade only the linecard to the same version as the one in the current active SUP, the customer can choose to upgrade one linecard or all the linecards in the chassis. This command can be used together with request platform software package install node file file-path noreload linecard command to upgrade SUP first, and then upgrade linecard. 7
Additional References Cisco IOS-XE In-Service Software Upgrade Process DETAILED STEPS Step 1 Step 2 Command or Action enable Router> enable request platform software package install node linecard-only Purpose Enables privileged EXEC mode. Enter your password if prompted. Upgrade all the linecards to the same version as the one in the current active SUP. Router# request platform software package install node linecard-only all Additional References The following sections provide references related to the ISSU feature. Technical Assistance Description The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. Link http://www.cisco.com/cisco/web/support/index.html Feature Information for In-Service Software Upgrade Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which 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. 8
Cisco IOS-XE In-Service Software Upgrade Process Feature Information for In-Service Software Upgrade Note The table below lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Table 2: Feature Information for ISSU Feature Name ISSU Releases Cisco IOS-XE Release 16.5.1 Feature Information This feature was integrated into Cisco IOS-XE Release 16.5.1 on the cisco cbr Series Converged Broadband Routers. 9
Feature Information for In-Service Software Upgrade Cisco IOS-XE In-Service Software Upgrade Process 10
CHAPTER 2 Supervisor Redundancy The Supervisor Redundancy feature reduces unplanned downtime. It enables a quicker switchover between active and standby Supervisors when a fatal error occurs on the active Supervisor. When you configure Supervisor Redundancy, the standby Supervisor is synchronized with the active Supervisor. If a fatal error occurs on the active Supervisor, the system immediately switches to the standby Supervisor. 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 Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://tools.cisco.com/itdit/cfn/. An account on http:// www.cisco.com/ is not required. Contents Hardware Compatibility Matrix for Cisco cbr Series Routers, page 12 Prerequisites for Supervisor Redundancy, page 12 Information About Supervisor Redundancy, page 13 How to Configure Supervisor Redundancy, page 16 Verifying the Supervisor Redundancy Configuration, page 21 Configuration Example for Supervisor Redundancy, page 25 Additional References, page 25 Feature Information for Supervisor Redundancy, page 26 11
Hardware Compatibility Matrix for Cisco cbr Series Routers Supervisor Redundancy Hardware Compatibility Matrix for Cisco cbr Series Routers Note The hardware components introduced in a given Cisco IOS-XE Release are supported in all subsequent releases unless otherwise specified. Table 3: Hardware Compatibility Matrix for the Cisco cbr Series Routers Cisco CMTS Platform Cisco cbr-8 Converged Broadband Router Processor Engine Cisco IOS-XE Release 16.5.1 and Later Releases Cisco cbr-8 Supervisor: PID CBR-CCAP-SUP-160G PID CBR-CCAP-SUP-60G PID CBR-SUP-8X10G-PIC Interface Cards Cisco IOS-XE Release 16.5.1 and Later Releases Cisco cbr-8 CCAP Line Cards: PID CBR-LC-8D30-16U30 PID CBR-LC-8D31-16U30 PID CBR-RF-PIC PID CBR-RF-PROT-PIC PID CBR-CCAP-LC-40G-R Cisco cbr-8 Downstream PHY Modules: PID CBR-D30-DS-MOD PID CBR-D31-DS-MOD Cisco cbr-8 Upstream PHY Modules: PID CBR-D30-US-MOD Prerequisites for Supervisor Redundancy Two Supervisors (that is, two Supervisor Cards and two Supervisor PICs) must be installed in the Cisco cbr chassis. Both Supervisors must be running identical software releases. 12
Supervisor Redundancy Information About Supervisor Redundancy Information About Supervisor Redundancy Switchover Procedure The Supervisor redundancy feature enables the Cisco cbr router to use two Supervisors in a redundant configuration, so that if the active Supervisor fails or becomes inactive, the system automatically performs a switchover, where the standby Supervisor takes over and assumes full responsibility for systems operations. The Supervisor redundancy feature does not require a full reboot of the system to perform a switchover. When the system boots up, the standby Supervisor performs full initialization, which includes self initialization, running configuration synchronization from the active Supervisor, and SSO feature data synchronization from the active Supervisor, then it enters into hot standby state and monitors the active Supervisor. If the standby Supervisor detects a failure in the active Supervisor, it can quickly assume the active responsibility for systems operations. Each Supervisor contains all the resources required to operate the router, such as bootflash memory, hard disks, Ethernet ports, and console port. In the default operation, the standby Supervisor also synchronizes the major systems files, such as the running configuration file, so that during a switchover, the standby Supervisor can duplicate the active Supervisor s configuration. You can use Cisco IOS CLI commands to access the standby Supervisor resources, such as the bootflash and hard disk. For example, you can use the dir command to list the contents of a device, or use the copy command to transfer files between the active and standby Supervisor. A switchover occurs when the standby Supervisor takes over responsibilities from the active Supervisor. The switchover can occur automatically if the standby Supervisor has determined that the active Supervisor 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 Supervisor verifies that the standby Supervisor is present and has entered into SSO. If so, it instructs the standby Supervisor to begin switchover procedures, and the active Supervisor 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 Supervisor assumes responsibility as the active Supervisor and brings the Cisco cbr chassis into active state, and continues the service as active Supervisor. 3 The new active Supervisor begins normal systems operations, including passing traffic. Note The Supervisor does not begin functioning as a standby Supervisor until it is booted up with a proper Cisco IOS software. Is Supervisor Switchover Failing? The usual phenomenon for a Supervisor switchover to be affected is when the active Supervisor has these issues: Supervisor hangs Login to Supervisor console or Telnet to chassis fails 13
Using Redundant File Systems Supervisor Redundancy Interface cards unable to connect to active Supervisor, hence crashing Cable modems drop offline Chassis reload required Reset of active Supervisor required to restore service Note In case there is hardware issue with the Supervisor, do not reinsert the faulty Supervisor in the chassis. Inserting a faulty Supervisor (although a standby Supervisor) may cause the interface card to switch to the faulty Supervisor causing the interface card to crash and cable modems to go offline. Using Redundant File Systems Both the active and standby Supervisors have active file systems that can be accessed to store and transfer files. The table below 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. File System Bootflash Flash Hard disk USB Standby bootflash Standby hard disk Standby USB File Name for CLI Commands bootflash: flash: harddisk: usb0: usb1: stby-bootflash: stby-harddisk: stby-usb0: stby-usb1: Description Stores image, crash file, core files, saved configuration files, and various user files. System Temporary system Null Tar Syslog CNS RCSF system: tmpsys: null: tar: syslog: cns: revrcsf: Stores the running configuration and other system files. 14
Supervisor Redundancy Using Redundant File Systems File System NVRAM Standby NVRAM Standby RCSF File Name for CLI Commands nvram: stby-nvram: stby-rcsf: Description Typically stores the system default configuration file and startup configuration file. TFTP RCP PRAM FTP HTTP SCP HTTPS tftp: rcp: pram: ftp: http: scp: https: Protocols used to transfer files to and from remote devices. 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 bootflash or hard disks. Following is a sample output of the show file systems command on the Cisco cbrrouter: Router# show file systems File Systems: Size(b) Free(b) Type Flags Prefixes - - opaque rw system: - - opaque rw tmpsys: * 7800705024 1574408192 disk rw bootflash: 7800705024 1574408192 disk rw flash: 98394218496 79534682112 disk rw harddisk: 8009056256 8009023488 disk rw usb1: 33554432 33507452 nvram rw stby-nvram: - - opaque rw null: - - opaque ro tar: - - network rw tftp: - - opaque wo syslog: 33554432 33508476 nvram rw nvram: - - network rw rcp: - - network rw pram: - - network rw ftp: - - network rw http: - - network rw scp: - - network rw https: - - opaque ro cns: - - nvram rw stby-rcsf: 7800705024 1635270656 disk rw stby-bootflash: 98394218496 89040576512 disk rw stby-harddisk: - - disk rw stby-usb0: 1000787968 301559808 disk rw stby-usb1: - - opaque rw revrcsf: 15
Console Port Usage After Supervisor Switchover Supervisor Redundancy Console Port Usage After Supervisor Switchover When an active Supervisor fails, and the standby Supervisor becomes the active Supervisor, you must use the console port on the new active Supervisor to give CLI commands and display statistics for the router. The standby Supervisor console is disabled by default and cannot be used to run any CLI commands. Following is an sample output of the standby Supervisor console: Router-stby> Standby console disabled Router-stby> To access the console, move the PC or terminal's serial cable to the console port on the other Supervisor, which is now acting as the active Supervisor. Benefits The Supervisor is not a single point of hardware failure. If a permanent hardware failure in the active Supervisor occurs, the standby Supervisor recovers the system, increasing the level of network service and reliability. The standby Supervisor can become the active Supervisor without the manual intervention of a system operator. This reduces the recovery time and the need for an instant response from the network administrators. The active Supervisor continues to dynamically synchronize the changed configuration and feature data with the standby Supervisor after the system reaches SSO. Therefore, the standby Supervisor always operates as a hot standby and ready to take over. How to Configure Supervisor Redundancy The Supervisor redundancy feature is automatically enabled when two Supervisor are installed in the Cisco cbr chassis. The active Supervisor automatically synchronizes the running configuration file with the standby Supervisor during the bootup of standby Supervisor. Note The Cisco cbr router supports only the SSO mode for Supervisor redundancy. The default redundancy mode is SSO and this mode does not need any new configurations. This section contains the following: Forcing Switchover To manually force a switchover, so that the standby Supervisor becomes active, use the redundancy force-switchover command in privileged EXEC mode on the active Supervisor. Manually forcing a switchover is useful in the following situations: You need to remove, replace, or upgrade the currently active Supervisor. 16
Supervisor Redundancy Changing the System Boot Behavior A previous switchover has activated the standby Supervisor and you now want to restore the previously active Supervisor. Tip Simply removing the active Supervisor also triggers a switchover, but using the redundancy force-switchover command does not generate a hardware alarm. Before You Begin Ensure that the standby Supervisor is in the SSO state using the show redundancy command. For more information, see Verifying Supervisor Redundancy, on page 22. Step 1 Set the configuration register as 0x02 and the load the appropriate image on both the Supervisors Router# configure terminal Router(config)# config-register 0x02 Router(config)# boot system bootflash:cbrsup-universalk9.2015-03-08_01.38_xxxxx.ssa.bin Step 2 Note Do not perform this step if you want to set the previous active Supervisor to stay in ROM monitor mode or manually boot it up after the switchover. Use the redundancy force-switchover command to force the switchover. Router# redundancy force-switchover Proceed with switchover to standby RP? [confirm] Manual Swact = enabled Jan 1 19:23:22.483 R0/0: %PMAN-5-EXITACTION: Process manager is exiting: process exit with reload fru code Initializing Hardware... System Bootstrap, Version 12.2(20141120:061458) [153], DEVELOPMENT SOFTWARE Copyright (c) 1994-2014 by cisco Systems, Inc. Compiled Thu 11/20/2014 18:04:24.91 by xxxxx The standby Supervisor becomes the active Supervisor. Step 3 (Optional) If you have not performed Step 1, on page 17, the previous active Supervisor is put into the ROM monitor mode after the switchover. To enable the previous active Supervisor to become the new standby Supervisor, manually boot up the new standby Supervisor to enter into SSO mode. Changing the System Boot Behavior This section describes how to change the Cisco IOS software configuration register for modifying the system behavior when powering up or rebooting the system. The software configuration register is a 16 bit register in NVRAM that controls the following boot functions: Specifies the source of the Cisco IOS software image to be loaded 17
Changing the System Boot Behavior Supervisor Redundancy Specifies whether the Cisco IOS software must ignore the contents of the saved configuration file in NVRAM memory Enables or disables the use of the Break function Use the following procedure to change the software configuration register settings: Step 1 Enter global configuration mode and use the config-register command to set the contents of the software configuration register to a new value. Specify the new value as a 16 bit hexadecimal bitmask by using the values provided in the following table. Table 4: Definition of Bits in the Software Configuration Register Bit No. 00 to 03 Hex Value 0x0000 to 0x000F Meaning/Function Defines the source of the default Cisco IOS software image required to run the router: 00 When powering up, the system remains at the ROM monitor prompt (rommon), awaiting a user command to boot the system manually by the rommon boot command. 01 When powering up, the system automatically boots the first system image found in the flash memory's single in-line memory module (SIMM) on the Supervisor. 02 to 0F When powering up, the system automatically boots from a default Cisco IOS software image stored on a TFTP server in the network. For this setting, configure and enable the Network Management Ethernet port on the Supervisor. The port must be operational. This setting also enables boot system commands which can override the default filename. 06 0x0040 Causes system software to ignore the contents of the NVRAM configuration file. 18
Supervisor Redundancy Changing the System Boot Behavior Bit No. 07 08 09 10 11 and 12 13 14 15 Hex Value 0x0080 0x0100 0x0200 0x0400 0x0800 to 0x1000 0x2000 0x4000 0x8000 Meaning/Function Enables the original equipment manufacturer (OEM) bit. Disables the Break function after 30 seconds. Not used. Specifies that broadcast packets are based on the 0.0.0.0 IP address. Defines the console baud rate (the default value is 9600 baud). Boots an image from the boot flash memory. Specifies that the broadcast packets must use the subnet broadcast address. Enables diagnostic messages and ignores the contents of the NVRAM configuration file. For example, to configure the router to boot to the ROM monitor prompt, set the configuration register to 0x2100 with the following commands: Step 2 Router# config t Router(config)# config-register 0x2100 Router(config)# Tip The typical bitmask for normal use is 0x2102. It specifies that the router must load the Cisco IOS software from the flash memory and boot to the Cisco IOS CLI prompt. The Break key is enabled only for 30 seconds. Hence, if required, you can break to the ROM monitor prompt. Exit the global configuration mode. Router(config)# exit Router# Step 3 View the new software configuration register setting using the show version command. The last line shows the settings of the configuration register: Router# show version Cisco IOS XE Software, Version 2015-03-04_00.38_xxxxx Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Experimental \ 19
Changing the System Boot Behavior Supervisor Redundancy Version 15.5(20150302:044048) [v155_2_s_xe315_throttle-xxxxx-xe315_0301 121] This software is an Engineering Special Copyright (c) 1986-2015 by Cisco Systems, Inc. Compiled Wed 04-Mar-15 00:21 by xxxxx Cisco IOS-XE software, Copyright (c) 2005-2015 by cisco Systems, Inc. All rights reserved. Certain components of Cisco IOS-XE software are licensed under the GNU General Public License ("GPL") Version 2.0. The software code licensed under GPL Version 2.0 is free software that comes with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such GPL code under the terms of GPL Version 2.0. For more details, see the documentation or "License Notice" file accompanying the IOS-XE software, or the applicable URL provided on the flyer accompanying the IOS-XE software. ROM: IOS-XE ROMMON Router uptime is 14 minutes Uptime for this control processor is 17 minutes System returned to ROM by SSO Switchover System image file is "bootflash:cbrsup-universalk9.2015-03-04_00.38_xxxxx.ssa.bin" Last reload reason: Reload Command This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately. A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html If you require further assistance please contact us by sending email to export@cisco.com. cisco cbr1013 (CBR) processor (revision CBR) with 3647635K/6147K bytes of memory. Processor board ID CSJ13152101 16 Gigabit Ethernet interfaces 32768K bytes of non-volatile configuration memory. 50331648K bytes of physical memory. 7739391K bytes of eusb flash at bootflash:. 97620247K bytes of SATA hard disk at harddisk:. 979258K bytes of USB flash at usb1:. Configuration register is 0x2 When you modify the configuration register, the show version command shows both the current value of the register and the value that will be used during the next reboot or reload. Step 4 Perform one of the following to save the new software configuration register settings in the configuration file: Use the copy running-config startup-config command. Use the write command. 20
Supervisor Redundancy Saving a Configuration File to the Bootflash or Hard Disk Router# copy running-config startup-config Step 5 Router# write Building configuration... [OK] The changes to the software configuration register will take effect the next time the router is rebooted or restarted. To manually reboot the router, use the reload command: Router# reload System configuration has been modified. Save? [yes/no]: yes Proceed with reload? [confirm] Saving a Configuration File to the Bootflash or Hard Disk This section describes how to copy a configuration file to a bootflash or hard disk and configure the Cisco cbr router. Step 1 Copy the configuration file to the bootflash or hard disks in both Supervisors. Router# copy running-config bootflash:cbr8-config Router# copy running-config stby-bootflash:cbr8-config Router# copy running-config harddisk:cbr8-config Router# copy running-config stby-harddisk:cbr8-config Step 2 (Optional) If the configuration file is currently on a TFTP server, copy the file from the TFTP server to the bootflash or hard disk in each Supervisor. Router# copy tftp://192.168.100.10/router-config bootflash:cbr8-config Router# copy tftp://192.168.100.10/router-config stby-bootflash:cbr8-config Router# copy tftp://192.168.100.10/router-config harddisk:cbr8-config Router# copy tftp://192.168.100.10/router-config stby-harddisk:cbr8-config Verifying the Supervisor Redundancy Configuration This section contains the following topics: 21
Verifying Supervisor Redundancy Supervisor Redundancy Verifying Supervisor Redundancy Step 1 View the startup configuration and verify whether the lines for configuring redundancy appear: Router# show startup-config... redundancy mode sso... Step 2 View the current Supervisor redundancy state by running the show redundancy command. The active Supervisor is typically shown in slot 4 (SUP0). Router# show redundancy Redundant System Information : ------------------------------ Available system uptime = 28 minutes Switchovers system experienced = 0 Standby failures = 0 Last switchover reason = none Hardware Mode = Duplex Configured Redundancy Mode = sso Operating Redundancy Mode = sso Maintenance Mode = Disabled Communications = Up Current Processor Information : ------------------------------- Active Location = slot 4 Current Software state = ACTIVE Uptime in current state = 28 minutes Image Version = Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Experimental Version 15.5(20150302:044048) [v155_2_s_xe315_throttle-xxxxx-xe315_0301 121] This software is an Engineering Special Copyright (c) 1986-2015 by Cisco Systems, Inc. Compiled Wed 04-Mar-15 00:21 by xxxxx BOOT = bootflash:cbrsup-universalk9.2015-03-04_00.38_xxxxx.ssa.bin,12; CONFIG_FILE = bootflash:startup_config1419513118 Configuration register = 0x2 Peer Processor Information : ---------------------------- Standby Location = slot 5 Current Software state = STANDBY HOT Uptime in current state = 24 minutes Image Version = Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Experimental Version 15.5(20150302:044048) [v155_2_s_xe315_throttle-xxxxx-xe315_0301 121] This software is an Engineering Special Copyright (c) 1986-2015 by Cisco Systems, Inc. 22
Supervisor Redundancy Verifying Supervisor Redundancy Compiled Wed 04-Mar-15 00:21 by xxxxx BOOT = bootflash:cbrsup-universalk9.2015-03-04_00.38_xxxxx.ssa.bin,12; CONFIG_FILE = bootflash:startup_config1419513118 Configuration register = 0x2 If a switchover occurs, the show redundancy command shows that the active Supervisor has changed slots, moving from slot 4 (SUP0) to slot 5 (SUP1). The output is similar to the one in the following example. Router# show redundancy Redundant System Information : ------------------------------ Available system uptime = 39 minutes Switchovers system experienced = 1 Standby failures = 0 Last switchover reason = user forced Hardware Mode = Duplex Configured Redundancy Mode = sso Operating Redundancy Mode = sso Maintenance Mode = Disabled Communications = Up Current Processor Information : ------------------------------- Active Location = slot 5 Current Software state = ACTIVE Uptime in current state = 10 minutes Image Version = Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Experimental Version 15.5(20150302:044048) [v155_2_s_xe315_throttle-xxxxx-xe315_0301 121] This software is an Engineering Special Copyright (c) 1986-2015 by Cisco Systems, Inc. Compiled Wed 04-Mar-15 00:21 by xxxxx BOOT = bootflash:cbrsup-universalk9.2015-03-04_00.38_xxxxx.ssa.bin,12; CONFIG_FILE = bootflash:startup_config1419513118 Configuration register = 0x2 Peer Processor Information : ---------------------------- Standby Location = slot 4 Current Software state = STANDBY HOT Uptime in current state = 4 minutes Image Version = Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Experimental Version 15.5(20150302:044048) [v155_2_s_xe315_throttle-xxxxx-xe315_0301 121] This software is an Engineering Special Copyright (c) 1986-2015 by Cisco Systems, Inc. Compiled Wed 04-Mar-15 00:21 by xxxxx BOOT = bootflash:cbrsup-universalk9.2015-03-04_00.38_xxxxx.ssa.bin,12; CONFIG_FILE = bootflash:startup_config1419513118 Configuration register = 0x2 23
Verifying Supervisor Switchover Supervisor Redundancy If the standby Supervisor is not installed or is not operational, the show redundancy command gives an output similar to the following example: Router# show redundancy Redundant System Information : ------------------------------ Available system uptime = 31 minutes Switchovers system experienced = 1 Standby failures = 0 Last switchover reason = user forced Hardware Mode = Simplex Configured Redundancy Mode = sso Operating Redundancy Mode = Non-redundant Maintenance Mode = Disabled Communications = Down Reason: Failure Current Processor Information : ------------------------------- Active Location = slot 5 Current Software state = ACTIVE Uptime in current state = 2 minutes Image Version = Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Experimental Version 15.5(20150302:044048) [v155_2_s_xe315_throttle-xxxxx-xe315_0301 121] This software is an Engineering Special Copyright (c) 1986-2015 by Cisco Systems, Inc. Compiled Wed 04-Mar-15 00:21 by xxxxx BOOT = bootflash:cbrsup-universalk9.2015-03-04_00.38_xxxxx.ssa.bin,12; CONFIG_FILE = bootflash:startup_config1419513118 Configuration register = 0x2 Peer (slot: 4) information is not available because it is in 'DISABLED' state The show redundancy command shows details of the redundancy state, software state, system uptime, image version, boot, configuration file, and configuration register information. Verifying Supervisor Switchover Step 1 Step 2 Verify the LEDs on the Supervisor Card. When a Supervisor becomes active, the RP ACT and FP ACT LEDs on the Supervisor Card illuminate green to indicate that they have initialized and acting as the active Supervisor. The RP ACT and FP ACT on standby Supervisor Card are off. For more information, see Monitoring the Supervisor in the Cisco cbr Chassis. Verify the Supervisor switchover by running the show redundancy switchover history command. If the original Supervisor is in slot 4 (SUP0) and the standby Supervisor is in slot 5 (SUP1), the output is similar to the following sample: 24
Supervisor Redundancy Configuration Example for Supervisor Redundancy Router# show redundancy switchover history Index Previous Current Switchover Switchover active active reason time ----- -------- ------- ---------- ---------- 1 48 49 user forced 19:23:11 CST Sun Jan 1 2012 The value 48 indicates SUP0 and 49 indicates SUP1. Configuration Example for Supervisor Redundancy The following example shows the relevant portion of the Cisco IOS configuration file for the default configuration of the Supervisor Redundancy feature. Use this configuration for most of the applications: Router# show running-config sec redundancy redundancy mode sso Router# Additional References Related Documents Related Topic CMTS commands Stateful Switchover Document Title Cisco IOS CMTS Cable Command Reference Stateful Switchover 25
Feature Information for Supervisor Redundancy Supervisor Redundancy Technical Assistance Description 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. Link http://www.cisco.com/support Feature Information for Supervisor Redundancy Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which 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 The table below lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Table 5: Feature Information for Supervisor Redundancy Feature Name Supervisor Redundancy Releases Cisco IOS-XE Release 16.5.1 Feature Information This feature was integrated into Cisco IOS-XE Release 16.5.1 on Cisco cbr Series Converged Broadband Routers. 26
CHAPTER 3 Line Card Redundancy The line cards support high availability with redundancy schemes. Line card redundancy can help limit customer premises equipment (CPE) downtime by enabling robust automatic switchover and recovery in the event that there is a localized system failure. 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 Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://tools.cisco.com/itdit/cfn/. An account on http:// www.cisco.com/ is not required. Contents Hardware Compatibility Matrix for Cisco cbr Series Routers, page 28 Prerequisites for Line Card Redundancy, page 28 Restrictions for Line Card Redundancy, page 29 Information About Line Card Redundancy, page 29 How to Configure Line Card Redundancy, page 30 Verifying the Line Card Redundancy Configuration, page 32 Additional References, page 35 Feature Information for Line Card Redundancy, page 36 27
Hardware Compatibility Matrix for Cisco cbr Series Routers Line Card Redundancy Hardware Compatibility Matrix for Cisco cbr Series Routers Note The hardware components introduced in a given Cisco IOS-XE Release are supported in all subsequent releases unless otherwise specified. Table 6: Hardware Compatibility Matrix for the Cisco cbr Series Routers Cisco CMTS Platform Cisco cbr-8 Converged Broadband Router Processor Engine Cisco IOS-XE Release 16.5.1 and Later Releases Cisco cbr-8 Supervisor: PID CBR-CCAP-SUP-160G PID CBR-CCAP-SUP-60G PID CBR-SUP-8X10G-PIC Interface Cards Cisco IOS-XE Release 16.5.1 and Later Releases Cisco cbr-8 CCAP Line Cards: PID CBR-LC-8D30-16U30 PID CBR-LC-8D31-16U30 PID CBR-RF-PIC PID CBR-RF-PROT-PIC PID CBR-CCAP-LC-40G-R Cisco cbr-8 Downstream PHY Modules: PID CBR-D30-DS-MOD PID CBR-D31-DS-MOD Cisco cbr-8 Upstream PHY Modules: PID CBR-D30-US-MOD Prerequisites for Line Card Redundancy At least one RF Through PIC and its corresponding interface line card must be installed in the chassis to be configured as the primary card. An RF Protect PIC and its corresponding interface line card must be installed in the chassis to be configured as the secondary card. 28
Line Card Redundancy Restrictions for Line Card Redundancy Restrictions for Line Card Redundancy The line cards installed in slot 3 and 6 of the Cisco cbr-8 router cannot be configured as the secondary card. The RF Protect PIC can send RF signals only to the lower slots (with larger slot number). So, the slot number of the secondary card must be the smallest in the redundancy group. Note We recommend that you install the RF Protect PIC in the uppermost slot (slot 0) of the chassis and configure it as the secondary card. The RF Through PIC can send RF signal only from upper slot to lower slot. So, do not install any RF blank PICs between the secondary card and primary cards. You cannot change any configuration on the primary or secondary card when the secondary card is active. You cannot remove the last primary card if there is a secondary card in the redundancy group. You must remove the secondary card and then remove the primary card. If the primary card is in the standby role, you must revert to the primary card before removing it from the redundancy group. Information About Line Card Redundancy Line card redundancy reduces the unplanned downtime. When you configure line card redundancy, a protect zone (redundancy group) is created on the router and the configurations on the primary cards are synchronized with the secondary card. The following events can trigger a switchover from an active card to a standby card: Manual switchover using the redundancy linecard-group switchover from slot slotcommand. Line card reload using the hw-module slot reload command. Line card crash. Line card Online Insertion and Removal (OIR). The secondary card reloads after the switchover. The router can be configured to automatically revert to the primary card when it becomes hot standby after an unplanned switchover triggered by the line card OIR or crash. Following are the line card redundancy states: Unavail The line card state is not available. Init The line card did not boot up. Active Cold The active card is downloading the configuration. Active The active card is fully configured and working. 29
How to Configure Line Card Redundancy Line Card Redundancy Stdby Cold The standby card configuration is synchronizing with the active card. Stdby Warm (Only for the secondary card) The standby card is fully synchronized and ready for switchover. It is the stable state of a secondary standby card. Stdby Hot The primary standby card is fully synchronized. It is the stable state of a primary standby card. The secondary standby card is chosen to switchover for a primary card, and will be active soon. It is a transient state when secondary card is becoming active. N+1 Line Card Redundancy The Cisco cbr-8 router supports N+1 redundancy scheme for line cards. A single RF Protect PIC can be configured as a secondary card for multiple RF Through PICs (primary cards). In this redundancy scheme, when the secondary card becomes the active card for a primary card, the redundancy scheme is changed to 1+1 redundancy. The Cisco cbr-8 router supports a single protect zone or redundancy group (group 0). How to Configure Line Card Redundancy This section contains the following: Configuring Line Card Manual Switchover Before You Begin The line card must be in active role, and warm standby or hot standby state. Use the show redundancy linecard all command to verify the role and state of the card. Restrictions You cannot perform a manual switchover when the standby Supervisor is booting up and not yet entered into SSO. You cannot auto revert the switchover triggered manually. DETAILED STEPS Step 1 Step 2 Command or Action enable Router> enable redundancy linecard-group switchover from slot slot Purpose Enables privileged EXEC mode. Enter your password if prompted. Manually switches over from the active line card. Router# redundancy linecard-group switchover from slot 9 30
Line Card Redundancy Configuring N+1 Line Card Redundancy Configuring N+1 Line Card Redundancy DETAILED STEPS Step 1 Step 2 Command or Action enable Router> enable configure terminal Purpose Enables privileged EXEC mode. Enter your password if prompted. Enters global configuration mode. Step 3 Step 4 Step 5 Router# configure terminal redundancy Router(config)# redundancy linecard-group group-id internal-switch Router(config-red)# linecard-group 0 internal-switch description group-description Enables redundancy and enters redundancy configuration mode. Configures the redundancy group and enters the line card redundancy configuration mode. (Optional) Configures the redundancy group description. Step 6 Step 7 Step 8 Router(config-red-lc)# description RedundancyGroup0 class 1:N Router(config-red-lc)# class 1:N revertive seconds Router(config-red-lc)# revertive 60 member slot slot primary Router(config-red-lc)# member slot 1 primary Configures the N+1 redundancy class for the redundancy group. (Optional) Configures the auto revert time for the primary card, in seconds. Adds the line card as a primary card in the redundancy group. Note Repeat this step for each primary card to be added in the redundancy group. 31
Verifying the Line Card Redundancy Configuration Line Card Redundancy Step 9 Command or Action member slot slot secondary Router(config-red-lc)# member slot 0 secondary Purpose Adds the line card as a primary card in the redundancy group. Step 10 end Returns to privileged EXEC mode. Router(config-red-lc)# end Verifying the Line Card Redundancy Configuration show redundancy linecard group all Displays the redundancy group information. The following is a sample output of this command: Router# show redundancy linecard group all Group Identifier: 0 Revertive, Revert Timer: OFF (60000 sec) Reserved Cardtype: 0xFFFFFFFF 4294967295 Group Redundancy Type: INTERNAL SWITCH Group Redundancy Class: 1:N Group Redundancy Configuration Type: LINECARD GROUP Primary: Slot 6 Primary: Slot 7 Secondary: Slot 0 show redundancy linecard all Displays the role and state information for all line cards. Following is a sample output of this command: Router# show redundancy linecard all LC My Peer Peer Peer Slot Subslot Group State State Slot Subslot Role Mode ------------------------------------------------------------------------------- 9-0 Active Stdby Cold 0 - Active Primary 8-0 Active Stdby Warm 0 - Active Primary 7-0 Active Stdby Warm 0 - Active Primary 6-0 Active Stdby Cold 0 - Active Primary 3-0 Active Stdby Cold 0 - Active Primary 2-0 Active Stdby Cold 0 - Active Primary 1-0 Active Stdby Cold 0 - Active Primary 0-0 - - Multiple None Standby Secondary Note The secondary card does not have a valid My State when it is in Standby role as it is the peer for N primary cards. The secondary card has N peer states. For example, it can be cold standby for some primary cards and warm standby for the other primary card. 32
Line Card Redundancy Verifying the Line Card Redundancy Configuration Following is a sample output of the command when secondary card becomes active for a primary card, and the N+1 redundancy is changed to 1+1 redundancy: Router# show redundancy linecard all LC My Peer Peer Peer Slot Subslot Group State State Slot Subslot Role Mode ------------------------------------------------------------------------------- 9-0 Stdby Hot Active 0 - Standby Primary 8-0 Active Unavail 0 - Active Primary 7-0 Active Unavail 0 - Active Primary 6-0 Active Unavail 0 - Active Primary 3-0 Active Unavail 0 - Active Primary 2-0 Active Unavail 0 - Active Primary 1-0 Active Unavail 0 - Active Primary 0-0 Active Stdby Hot 9 - Active Secondary show redundancy linecard slot Displays the redundancy information for the line card. Following is a sample output of the command: Router# show redundancy linecard slot 9 LC Redundancy Is Configured: LC Group Number: 0 LC Slot: 9 (idx=9) LC Peer Slot: 0 LC Card Type: 0x4076, 16502 LC Name: 9 LC Mode: Primary LC Role: Active LC My State: Active LC Peer State: Stdby Warm show redundancy linecard history Displays the state change history for all line cards. Following is a sample output of the command: Router# show redundancy linecard history Jan 05 2012 12:24:27 20559 - st_mem(9): MY State Change, (Active Wait) -> (Active) Jan 05 2012 12:24:27 20559 - st_mem(9): MY FSM execution, Active Wait:Init:State Ntfy Jan 05 2012 12:24:27 20559 - st_mem(9): MY State Change, (Active LC Cfg Dnld) -> (Active Wait) Jan 05 2012 12:24:27 20559 - st_mem(9): MY FSM execution, Active LC Cfg Dnld:Init:Cfg Dnld Done Jan 05 2012 12:24:27 20559 - st_mem(9): MY State Change, (Active Cold) -> (Active LC Cfg Dnld) Jan 05 2012 12:23:09 12763 - st_mem(9): MY FSM execution, Active Cold:Init:Cfg Dnld Jan 05 2012 12:23:09 12760 - st_mem(9): MY State Change, (Init) -> (Active Cold) Jan 05 2012 12:23:09 12760 - st_mem(9): MY FSM execution, Init:Init:Up Jan 05 2012 12:21:39 3746 - st_mem(9): PEER FSM Execution, Init:Init:Reset show lcha rfsw Displays the internal RF switch PIC state information. Following is a sample output of the command: Router# show lcha rfsw Slot 0 ==================================== Type : Secondary PIC State: normal Slot 1 ==================================== Type : Primary PIC State: normal show lcha logging level Displays the cable modem line card logs. 33
Verifying the Line Card Redundancy Configuration Line Card Redundancy Following is a sample output of the command: Router# show lcha logging level noise 11:02:03.313 CST Tue Nov 18 2014 [error] [slot=3] [txn=229] Peer-Up Message [tag=1011] to slot 3 complete [36144 ms]; status=nak response 11:02:03.313 CST Tue Nov 18 2014 [error] [slot=0] [txn=229] Slot 0 downloaded configuration for slot 3; result=peer-up notification failed 11:02:03.316 CST Tue Nov 18 2014 [noise] [slot=0] [txn=none] lcha_plfm_get_max_port_count_for_slot: slot 0 maximum port count is 1794 11:02:03.316 CST Tue Nov 18 2014 [noise] [slot=0] [txn=none] lcha_plfm_get_starting_port_index: slot 0 starting port count is 0 11:02:03.331 CST Tue Nov 18 2014 [note] [slot=0] [txn=none] Slot 0 is being reset 11:02:04.352 CST Tue Nov 18 2014 [note] [slot=0] [txn=none] slot 0 removed When the secondary card is active, you can use the slot number of either the primary or secondary card in the show commands. Following is a sample output of the show interfaces command after the primary card in slot 8 switches over to secondary card in slot 0: Router# show interfaces c0/0/0 Cable0/0/0 is up, line protocol is up Hardware is CMTS MD interface, address is 0000.0000.031e (bia 0000.0000.031e) MTU 1500 bytes, BW 26000 Kbit/sec, DLY 1000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation MCNS, loopback not set Keepalive set (10 sec) ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/0/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 19500 kilobits/sec 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 13000 bits/sec, 17 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts (0 multicasts) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 140520 packets output, 14052672 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 unknown protocol drops 0 output buffer failures, 0 output buffers swapped out Router# show interfaces c8/0/0 Cable0/0/0 is up, line protocol is up Hardware is CMTS MD interface, address is 0000.0000.031e (bia 0000.0000.031e) MTU 1500 bytes, BW 26000 Kbit/sec, DLY 1000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation MCNS, loopback not set Keepalive set (10 sec) ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/0/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 19500 kilobits/sec 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 14000 bits/sec, 18 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts (0 multicasts) 0 runts, 0 giants, 0 throttles 34
Line Card Redundancy Additional References 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 140616 packets output, 14062272 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 unknown protocol drops 0 output buffer failures, 0 output buffers swapped out When the secondary card is active, the show running-config command displays the output for the secondary card. Note The output of the show running-config command is empty for the primary card when the secondary card is active. Following is a sample output of the show running-config command after the primary card in slot 8 switches over to secondary card in slot 0: Router# show running-config begin controller Upstream-Cable 0 controller Upstream-Cable 0/0/0 us-channel 0 channel-width 1600000 1600000 us-channel 0 docsis-mode atdma us-channel 0 minislot-size 4 us-channel 0 modulation-profile 221 no us-channel 0 shutdown us-channel 1 channel-width 1600000 1600000 us-channel 1 docsis-mode atdma Router# show running-config begin controller Upstream-Cable 8 Router# Router# Additional References Related Documents Related Topic CMTS commands Document Title Cisco CMTS Cable Command Reference 35
Feature Information for Line Card Redundancy Line Card Redundancy Technical Assistance Description 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. Link http://www.cisco.com/support Feature Information for Line Card Redundancy Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which 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 The table below lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Table 7: Feature Information for Line Card Redundancy Feature Name Line Card Redundancy Releases Cisco IOS-XE Release 16.5.1 Feature Information This feature was integrated into Cisco IOS-XE Release 16.5.1 on the Cisco cbr Series Converged Broadband Routers. 36