Downloads |
Table Of Contents
1:1 Supervisor Card Redundancy
Prerequisites for 1:1 Supervisor Card Redundancy
Restrictions for 1:1 Supervisor Card Redundancy
Information About 1:1 Supervisor Card Redundancy
Need for Supervisor Redundancy
Causes for Supervisor Switchover
Accessing the Standby Supervisor Card
Supervisor Redundancy SSO Support on Cisco RFGW-10
Supervisor Uplink Configuration
Forcing a Switchover Between Active and Standby Supervisor
Reloading the Supervisor Cards
How to Configure 1:1 Supervisor Card Redundancy
Configuring Route Processor Redundancy
Configuring Stateful Switchover
How to Verify 1:1 Supervisor Card Redundancy
Verifying Route Processor Redundancy
Feature Information for 1:1 Supervisor Card Redundancy
1:1 Supervisor Card Redundancy
First Published: January 8, 2009Last Updated: November 16, 2009This document describes high availability and redundancy features of the Supervisor card on the Cisco RF Gateway 10 (RFGW-10) Universal Edge Quadrature Amplitude Modulation (UEQAM).
High availability is a critical requirement in networks to provide continuous access to applications and data. It is required to minimize downtime and ensure maximum productivity in a network.
Supervisor high availability is achieved through:
•
Route Processor Redundancy (RPR)
•
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module and to see a list of the releases in which each feature is supported, see the "Feature Information for 1:1 Supervisor Card Redundancy" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS, Catalyst OS, and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
•
•
•
•
•
Prerequisites for 1:1 Supervisor Card Redundancy
•
•
Restrictions for 1:1 Supervisor Card Redundancy
•
Information About 1:1 Supervisor Card Redundancy
This section describes the types of high availability, supervisor redundancy, and the need and cause for a Supervisor switchover on the Cisco RFGW-10:
•
•
•
•
Supervisor Redundancy
The Cisco RFGW-10 supports two redundant Supervisor cards—one active card and one standby card. In a switchover, the standby Supervisor card takes over the active Supervisor card. Running the Supervisor card in RPR or SSO operating mode enables Supervisor redundancy.
Need for Supervisor Redundancy
In a switchover scenario, if the active Supervisor card fails and the standby card takes over or a manual switchover is performed, the standby Supervisor card becomes the active Supervisor. The standby Supervisor card is automatically initialized with the startup configuration of the active Supervisor card, thus shortening the switchover time.
The switchover time for a Supervisor card in RPR mode could vary from 30 seconds or longer depending on the configuration. The switchover time for a Supervisor card in SSO mode is less than 1 second.
In addition to the minimal switchover time, Supervisor redundancy supports:
•
•
Tip
Causes for Supervisor Switchover
Some of the possible causes that can trigger a switchover from the active Supervisor card to the standby Supervisor card are:
•
•
•
•
•
•
Route Processor Redundancy
In Route Processor Redundancy (RPR) mode, the standby Supervisor card completes its initialization but suspends just before parsing the startup-config. The standby Supervisor card monitors the active Supervisor card, and switches over when it detects a failure on the active Supervisor card. When the standby Supervisor card becomes active, the TCC cards and all the line cards in the chassis are reset, and the startup-config is parsed. There is a traffic outage in this mode because the line cards are reset.
The switchover time of the active Supervisor card can be 30 seconds or more depending on the configuration.
The following are synchronized between the active and the standby Supervisor cards:
•
•
•
•
•
The following are not synchronized between the active and standby Supervisor cards:
•
•
•
•
•
Switchover
The standby Supervisor card loads a Cisco IOS software image at startup and initializes itself in standby mode. In the event of a switchover, the standby Supervisor card reinitializes itself as the active Supervisor card, reloads all the line cards, and restarts the system. Because all line cards are reloaded, adjacent routers detect the physical link failure for most types of point-to-point connections. The standby Supervisor card parses the complete configuration, completes the booting sequence, resets the modules to perform self diagnostics, waits for the modules to come online and builds routing tables, MAC address tables, and dynamic protocols.
Stateful Switchover
In Stateful Switchover (SSO) mode, the standby Supervisor card is fully initialized and configured. This allows SSO to shorten the switchover time if the active Supervisor card fails, or if a manual switchover is performed. Both the startup and running configurations are continually synchronized from the active to the standby Supervisor cards, and the line cards are not reset during a switchover. The interfaces remain up during this transfer, so neighboring routers do not detect a physical link flap (the link does not go down and come back up).
The line cards, Layer 2 protocols, and application state information are synchronized and the standby Supervisor card is in a "hot" standby ready state to take over immediately. As the standby Supervisor card recognizes the hardware link status of every link, ports that were previously active remain active after a switchover has taken place.
The following are synchronized between the active and the standby Supervisor cards:
•
•
•
•
The following are not synchronized between the active and the standby Supervisor cards:
•
•
•
•
Switchover
In the event of a switchover, the standby Supervisor card becomes the active Supervisor card. As the standby Supervisor card is continuously synchronized with the startup and running configuration, switchover downtime is minimal. The state information synchronization (often called "checkpointing") from the active Supervisor card to the standby Supervisor card occurs at normal run time. At the switchover, the newly active Supervisor card immediately uses the state information previously synchronized (checkpointed).
The line cards are not reset as part of the switchover. The Supervisor card reconciles the line card state information with its own state information on switchover. SSO-aware features or protocols such as DHCP protocols are check pointed during switchover. Non-SSO aware features or protocols such as OSPF, BGP, Multicast PIM and IGMP, and L2VPNv3 protocols are quickly available on the standby as the standby Supervisor card is completely initialized.
Benefits of SSO
SSO provides a faster switchover compared to Route Processor Redundancy (RPR) by fully initializing and configuring the standby Supervisor card. By using check pointed state information, the time required for routing protocols to converge is minimized. As protocol information, application information, and user session information are maintained during the switchover, improved network availability is provided and line cards continuously forward network traffic with no loss of sessions.
Accessing the Standby Supervisor Card
The following activities can be performed on the standby Supervisor card.
Supervisor Redundancy SSO Support on Cisco RFGW-10
The following features are supported for Supervisor Redundancy in SSO mode.
Platform
Configuration Synchronization
The running configuration and the startup configuration are synchronized from the active Supervisor card to the standby Supervisor card. The running configuration is synchronized line by line. The commands are executed on the active Supervisor card and then on the standby Supervisor card. Parser Return Code (PRC) is used to verify the active and standby Supervisor card have the same path of execution for the command.
All interfaces and ports are synchronized as part of the configuration.
Alarm management
Syslog alarms are synchronized to the standby Supervisor card at run time. Active alarms reside on each line card. On a Supervisor switchover, the newly active Supervisor card receives the alarms from the line cards.
Line card management
The state of line cards progresses through events such as line card insertion, line card removal, line card partial reset, and line card full reset. These events and the corresponding line card states are check pointed from the active Supervisor card to the standby Supervisor card. At the Supervisor switchover, the newly active Supervisor card continues to manage the line cards with the check pointed state information.
RF Switch
The RF switch management maintains state information on all the RF switch cards, whether or not the card is present in the system. The state information is synchronized from the active Supervisor to the standby Supervisor card whenever the RF switch is inserted or removed.
DEPI
In the Cisco IOS Release12.2(50)SQ, DEPI is configured in one of the two modes—manual mode via static DEPI path configuration or protocol mode via dynamic DEPI protocol. In DEPI manual mode, the Supervisor switchover does not affect the statically configured DEPI connections. Hence, the switchover interruption to DEPI data traffic is in subseconds.
In DEPI protocol mode, the DEPI control plane is SSO-unaware as the underlying IOS L2TPv3 protocol is SSO-unaware. Neither the L2TPv3 protocol state nor the DEPI state is checkpointed from the active Supervisor card to the standby Supervisor card. During Supervisor switchover, the DEPI control plane and data plane are recovered as follows with minimal service outage time:
•
•
Video
The video SSO feature is not available in Cisco IOS Release 12.2(50)SQ. The video feature needs to run with the 1:1 Supervisor Redundancy in RPR mode.
Supervisor Uplink Configuration
To configure Supervisor uplink, use the following command in configuration mode:
Router(config)# hw-module uplink select [all | gigabitethernet | tengigabitethernet]When Supervisor uplink is configured, only specific uplink ports are active and available for uplink connectivity. If you try to configure other uplink ports, an error message similar to the following is displayed:
% WARNING: Interface GigabitEthernet1/5 is usable/operational only in 'all' or % 'gigabit' uplink configuration when only one supervisor is present in the % chassis in slot 1.Table 1, Table 2, and Table 3 show the valid port configurations for uplink.
Table 1 Only 10-Gigabit Ethernet Ports for Uplink
Table 2 Only Gigabit Ethernet Ports for Uplink
Table 3 Both 10-Gigabit Ethernet and Gigabit Ethernet Ports for Uplink
Forcing a Switchover Between Active and Standby Supervisor
This section describes how to do a manual switchover between the active and standby Supervisor cards on the Cisco RFGW-10:
•
Forcing RPR Switchover
To force the active Supervisor card to standby mode and the standby to active, use the redundancy force-switchover command in privileged EXEC mode:
Before the redundancy command is used, ensure that the active and standby Supervisor cards have a high availability Cisco IOS image installed and configured for Route Processor Redundancy (RPR) mode. Before the system switches over, it verifies that the standby Supervisor card is ready to take over. If the current running configuration is different from the startup configuration, the system prompts to save the running configuration before the switchover is performed.
A manual switchover is performed for one of the following reasons:
•
•
•
The following example shows a switchover being initiated manually:
Router# redundancy force-switchoverProceed with switchover to standby Supervisor? [confirm] y
Note
The following example shows a switchover failure because the standby Supervisor card is either not ready, not available, or not installed:
Router# redundancy force-switchoverThere is no STANDBY present. Failed to force switchoverReloading the Supervisor Cards
To reset the standby Supervisor card or to reset both the active and standby Supervisor cards, use the redundancy reload command in privileged EXEC mode:
Router# redundancy reload {peer | shelf}Use peer to reload only the standby Supervisor card and use shelf to reload both the active and standby Supervisor cards.
The following example shows how to reset the standby Supervisor card:
Router# redundancy reload peerReload peer? [confirm] yPreparing to reload peer
Note
The following example shows the system response when a standby Supervisor card is not installed in the router:
Router# redundancy reload peerSystem is running in SIMPLEX mode, reload anyway? [confirm] nPeer reload not performed.The following example shows how to reload both Supervisor cards:
Router# redundancy reload shelfReload the entire shelf [confirm] yPreparing to reload entire shelf
Note
Forcing Stateful Switchover
The following commands are used to perform a manual switchover from the active Supervisor card to the standby Supervisor card:
•
•
Note
How to Configure 1:1 Supervisor Card Redundancy
This section describes how to configure 1:1 Supervisor card redundancy in Cisco RFGW-10:
•
•
Configuring Route Processor Redundancy
This section describes how to configure Route Processor Redundancy (RPR).
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Example:
The following example shows how to enter RPR and main-CPU redundancy mode:
Router# configure terminalRouter(config)# redundancyRouter(config-red)# mode rprRouter(config-red)# main-cpuRouter(config-red-mc)# auto-sync standardRouter(config-red-mc)# exitRouter# write memoryConfiguring Stateful Switchover
This section describes how to configure Stateful Switchover (SSO).
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Example:
The following example shows how to enter SSO redundancy mode:
Router# configure terminalRouter(config)# redundancyRouter(config-red)# mode ssoRouter(config-red)# exitRouter# write memoryHow to Verify 1:1 Supervisor Card Redundancy
This section describes how to verify 1:1 Supervisor Card Redundancy in Cisco RFGW-10:
•
•
Verifying Route Processor Redundancy
The following is a sample output of the show redundancy command showing Supervisor Redundancy RPR mode configured the on the Cisco RFGW-10:
Router# show redundancyLoad for five secs: 8%/0%; one minute: 9%; five minutes: 10%Time source is hardware calendar, *15:26:51.687 PDT Wed Sep 16 2009Redundant System Information :------------------------------Available system uptime = 2 days, 4 hours, 5 minutesSwitchovers system experienced = 0Standby failures = 1Last switchover reason = noneHardware Mode = SimplexConfigured Redundancy Mode = RPROperating Redundancy Mode = RPRMaintenance Mode = DisabledCommunications = Down Reason: Simplex modeCurrent Processor Information :-------------------------------Active Location = slot 1Current Software state = ACTIVEUptime in current state = 2 days, 4 hours, 5 minutesImage Version = Cisco IOS Software, Catalyst 4500 L3 Switch Software (rfgw-ENTSERVICESK9-M), Version 12.2(122SQ_20090905)SQ EARLY DEPLOYMENT DATECODE BUILD, synced to 122_50_SG_THROTTLE_BASE_LABELCopyright (c) 1986-2009 by Cisco Systems, Inc.Compiled Sat 05-Sep-09 04:24 by jdkerrBOOT = bootflash:rfgw-entservicesk9-mz.122SQ_20090905,12;Configuration register = 0x2Peer (slot: 2) information is not available because it is in 'DISABLED' stateRouterTo verify the current Supervisor redundancy status, use the following command in user EXEC or privileged EXEC mode:
Router# show redundancy [clients | counters | history | states]The following is sample output of the show redundancy clients command:
Router# show redundancy clientsclientID = 0 clientSeq = 0 RF_INTERNAL_MSGclientID = 25 clientSeq = 130 CHKPT RFclientID = 5 clientSeq = 170 RFS clientclientID = 50 clientSeq = 530 Slot RFclientID = 65000 clientSeq = 65000 RF_LAST_CLIENTThe following is sample output of the show redundancy counters command:
Router# show redundancy countersRedundancy Facility OMscomm link up = 1comm link down down = 0invalid client tx = 0null tx by client = 0tx failures = 0tx msg length invalid = 0client not rxing msgs = 0rx peer msg routing errors = 0null peer msg rx = 0errored peer msg rx = 0buffers tx = 1009tx buffers unavailable = 0buffers rx = 1006buffer release errors = 0duplicate client registers = 0failed to register client = 0Invalid client syncs = 0The following is sample output of the show redundancy history command:
Router# show redundancy history00:00:00 client added: RF_INTERNAL_MSG(0) seq=000:00:00 client added: RF_LAST_CLIENT(65000) seq=6500000:00:00 client added: CHKPT RF(25) seq=13000:00:01 client added: Slot RF(50) seq=53000:00:15 client added: RFS client(5) seq=17000:00:16 *my state = INITIALIZATION(2) *peer state = DISABLED(1)00:00:16 RF_PROG_INITIALIZATION(100) RF_INTERNAL_MSG(0) op=0 rc=1100:00:16 RF_PROG_INITIALIZATION(100) CHKPT RF(25) op=0 rc=1100:00:16 RF_PROG_INITIALIZATION(100) RFS client(5) op=0 rc=1100:00:16 RF_PROG_INITIALIZATION(100) Slot RF(50) op=0 rc=1100:00:16 RF_PROG_INITIALIZATION(100) RF_LAST_CLIENT(65000) op=0 rc=1100:00:16 *my state = NEGOTIATION(3) peer state = DISABLED(1)00:00:16 RF_EVENT_GO_ACTIVE(512) op=0 rc=000: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=000:00:16 RF_STATUS_MAINTENANCE_ENABLE(403) RFS client(5) op=0 rc=000:00:16 RF_STATUS_MAINTENANCE_ENABLE(403) Slot RF(50) op=0 rc=000:00:16 RF_PROG_ACTIVE_FAST(200) RF_INTERNAL_MSG(0) op=0 rc=1100:00:16 RF_PROG_ACTIVE_FAST(200) CHKPT RF(25) op=0 rc=1100:00:16 RF_PROG_ACTIVE_FAST(200) RFS client(5) op=0 rc=1100:00:16 RF_PROG_ACTIVE_FAST(200) Slot RF(50) op=0 rc=1100:00:16 RF_PROG_ACTIVE_FAST(200) RF_LAST_CLIENT(65000) op=0 rc=1100: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=1100:00:16 RF_PROG_ACTIVE_DRAIN(201) CHKPT RF(25) op=0 rc=1100:00:16 RF_PROG_ACTIVE_DRAIN(201) RFS client(5) op=0 rc=1100:00:16 RF_PROG_ACTIVE_DRAIN(201) Slot RF(50) op=0 rc=11The following is sample output of the show redundancy states command:
Router# show redundancy statesmy state = 13 -ACTIVEpeer state = 8 -STANDBY HOTMode = DuplexUnit = PrimaryUnit ID = 0Redundancy Mode = Hot Standby RedundancyMaintenance Mode = DisabledManual Swact = EnabledCommunications = Upclient count = 5client_notification_TMR = 30000 millisecondsRF debug mask = 0x0Verifying Stateful Switchover
The following is a sample output of the show redundancy command showing Supervisor redundancy SSO mode configured using the on the Cisco RFGW-10:
Router# show redundancyLoad for five secs: 8%/0%; one minute: 10%; five minutes: 10%Time source is hardware calendar, *15:18:51.999 PDT Wed Sep 16 2009Redundant System Information :------------------------------Available system uptime = 2 days, 3 hours, 57 minutesSwitchovers system experienced = 0Standby failures = 0Last switchover reason = noneHardware Mode = DuplexConfigured Redundancy Mode = Stateful SwitchoverOperating Redundancy Mode = Stateful SwitchoverMaintenance Mode = DisabledCommunications = UpCurrent Processor Information :-------------------------------Active Location = slot 1Current Software state = ACTIVEUptime in current state = 2 days, 3 hours, 57 minutesImage Version = Cisco IOS Software, Catalyst 4500 L3 Switch Software (rfgw-ENTSERVICESK9-M), Version 12.2(122SQ_20090905)SQ EARLY DEPLOYMENT DATECODE BUILD, synced to 122_50_SG_THROTTLE_BASE_LABELCopyright (c) 1986-2009 by Cisco Systems, Inc.Compiled Sat 05-Sep-09 04:24 by jdkerrBOOT = bootflash:rfgw-entservicesk9-mz.122SQ_20090905,12;Configuration register = 0x2Peer Processor Information :----------------------------Standby Location = slot 2Current Software state = STANDBY HOTUptime in current state = 2 days, 3 hours, 56 minutesImage Version = Cisco IOS Software, Catalyst 4500 L3 Switch Software (rfgw-ENTSERVICESK9-M), Version 12.2(122SQ_20090905)SQ EARLY DEPLOYMENT DATECODE BUILD, synced to 122_50_SG_THROTTLE_BASE_LABELCopyright (c) 1986-2009 by Cisco Systems, Inc.Compiled Sat 05-Sep-09 04:2BOOT = bootflash:rfgw-entservicesk9-mz.122SQ_20090905,12;Configuration register = 0x2RouterTo verify the current Supervisor redundancy status, use the following command in user EXEC or privileged EXEC mode:
Router# show redundancy [clients | counters | history | states]The following is sample output of the show redundancy clients command:
Router# show redundancy clientsLoad for five secs: 11%/0%; one minute: 10%; five minutes: 11%Time source is hardware calendar, *15:20:08.899 PDT Wed Sep 16 2009clientID = 0 clientSeq = 0 RF_INTERNAL_MSGclientID = 29 clientSeq = 60 Redundancy Mode RFclientID = 139 clientSeq = 61 IfIndexclientID = 3300 clientSeq = 62 Persistent VariableclientID = 25 clientSeq = 68 CHKPT RFclientID = 77 clientSeq = 75 Event ManagerclientID = 22 clientSeq = 98 Network RF ClientclientID = 88 clientSeq = 99 HSRPclientID = 71 clientSeq = 114 XDR RRP RF ClientclientID = 24 clientSeq = 115 CEF RRP RF ClientclientID = 75 clientSeq = 132 Tableid HAclientID = 520 clientSeq = 135 RFS RFclientID = 210 clientSeq = 136 Auth MgrclientID = 5 clientSeq = 137 Config Sync RF clienclientID = 501 clientSeq = 145 LAN-Switch VTP VLANclientID = 502 clientSeq = 147 LAN-Switch Port ManaclientID = 200 clientSeq = 165 ETHERNET OAM RFclientID = 201 clientSeq = 166 ETHERNET CFM RFclientID = 20 clientSeq = 177 IPROUTING NSF RF cliclientID = 55 clientSeq = 187 GALIOS_CONFIG_SYNCclientID = 34 clientSeq = 192 SNMP RF ClientclientID = 35 clientSeq = 202 History RF ClientclientID = 91 clientSeq = 223 REDSSOCclientID = 250 clientSeq = 226 EEM Server RF CLIENTclientID = 252 clientSeq = 228 EEM POLICY-DIR RF CLclientID = 54 clientSeq = 230 SNMP HA RF ClientclientID = 57 clientSeq = 233 ARPclientID = 50 clientSeq = 240 FH_RF_Event_DetectorclientID = 2001 clientSeq = 241 CAT4K CHASSISclientID = 2002 clientSeq = 242 Link StateclientID = 2003 clientSeq = 244 K2ManclientID = 2005 clientSeq = 248 RkiosThe following is sample output of the show redundancy counters command:
Router# show redundancy countersLoad for five secs: 12%/0%; one minute: 11%; five minutes: 11%Time source is hardware calendar, *15:18:05.943 PDT Wed Sep 16 2009Redundancy Facility OMscomm link up = 1comm link down = 0invalid client tx = 0null tx by client = 0tx failures = 0tx msg length invalid = 0client not rxing msgs = 0rx peer msg routing errors = 0null peer msg rx = 0errored peer msg rx = 0buffers tx = 23994tx buffers unavailable = 0buffers rx = 20810buffer release errors = 0duplicate client registers = 0failed to register client = 0Invalid client syncs = 0The following is sample output of the show redundancy history command:
Router# show redundancy historyLoad for five secs: 8%/0%; one minute: 10%; five minutes: 10%Time source is hardware calendar, *15:16:40.079 PDT Wed Sep 16 200900:00:00 client added: RF_INTERNAL_MSG(0) seq=000:00:00 client added: RF_LAST_CLIENT(65000) seq=36100:00:00 RF_STATUS_SEND_RF_STATE(408) RF_LAST_CLIENT(65000) op=1 rc=000:00:01 client added: IfIndex(139) seq=6100:00:01 RF_STATUS_SEND_RF_STATE(408) IfIndex(139) op=1 rc=000:00:01 client added: ISSU Test Client(4005) seq=31900:00:01 RF_STATUS_SEND_RF_STATE(408) ISSU Test Client(4005) op=1 rc=000:00:01 client added: RFS RF(520) seq=13500:00:01 client added: DATA DESCRIPTOR RF CLIENT(141) seq=32300:00:01 client added: ISSU process(3099) seq=31600:00:01 RF_STATUS_SEND_RF_STATE(408) ISSU process(3099) op=1 rc=000:00:01 client added: Persistent Variable(3300) seq=6200:00:01 RF_STATUS_SEND_RF_STATE(408) Persistent Variable(3300) op=1 rc=000:00:01 client added: REP Protocol(212) seq=27800:00:01 RF_STATUS_SEND_RF_STATE(408) REP Protocol(212) op=1 rc=000:00:01 client added: History RF Client(35) seq=20200:00:01 RF_STATUS_SEND_RF_STATE(408) History RF Client(35) op=1 rc=000:00:01 client added: CHKPT RF(25) seq=6800:00:01 RF_STATUS_SEND_RF_STATE(408) CHKPT RF(25) op=1 rc=000:00:01 client added: XDR RRP RF Client(71) seq=11400:00:01 RF_STATUS_SEND_RF_STATE(408) XDR RRP RF Client(71) op=1 rc=000:00:01 client added: Config Sync RF client(5) seq=13700:00:01 RF_STATUS_SEND_RF_STATE(408) Config Sync RF client(5) op=1 rc=000:00:01 client added: Config Verify RF client(94) seq=29200:00:01 RF_STATUS_SEND_RF_STATE(408) Config Verify RF client(94) op=1 rc=000:00:01 client added: Inline Power rf client(505) seq=29400:00:01 RF_STATUS_SEND_RF_STATE(408) Inline Power rf client(505) op=1 rc=000:00:01 client added: Port Security(508) seq=29700:00:01 RF_STATUS_SEND_RF_STATE(408) Port Security(508) op=1 rc=000:00:01 client added: LAN-Switch Port Manager(502) seq=14700:00:01 RF_STATUS_SEND_RF_STATE(408) LAN-Switch Port Manager(502) op=1 rc=000:00:01 client added: LAN-Switch PAgP/LACP(510) seq=32600:00:01 RF_STATUS_SEND_RF_STATE(408) LAN-Switch PAgP/LACP(510) op=1 rc=000:00:01 client added: LAN-Switch IP Host Table(509) seq=29800:00:01 RF_STATUS_SEND_RF_STATE(408) LAN-Switch IP Host Table(509) op=1 rc=000:00:01 client added: CEF RRP RF Client(24) seq=11500:00:01 RF_STATUS_SEND_RF_STATE(408) CEF RRP RF Client(24) op=1 rc=0The following is sample output of the show redundancy states command:
Router# show redundancy statesLoad for five secs: 8%/0%; one minute: 10%; five minutes: 11%Time source is hardware calendar, *15:14:31.131 PDT Wed Sep 16 2009my state = 13 -ACTIVEpeer state = 8 -STANDBY HOTMode = DuplexUnit = PrimaryUnit ID = 1Redundancy Mode (Operational) = Stateful SwitchoverRedundancy Mode (Configured) = Stateful SwitchoverRedundancy State = Stateful SwitchoverMaintenance Mode = DisabledManual Swact = enabledCommunications = Upclient count = 59client_notification_TMR = 240000 millisecondskeep_alive TMR = 9000 millisecondskeep_alive count = 0keep_alive threshold = 18RF debug mask = 0x0Additional References
The following sections provide references related to 1:1 Supervisor Card Redundancy feature.
Related Documents
Cisco RFGW-10 commands
Cisco RF Gateway 10 Command Reference
http://www.cisco.com/en/US/docs/cable/rf_gateway/command/reference/RFGW-10_Book.html
New Software Features in Cisco IOS Release 12.2(44)SQ
Cisco RF Gateway 10 New Features List
http://www.cisco.com/en/US/docs/cable/rf_gateway/feature/list/rfgw10_featlist.html
New Software Features in Cisco IOS Release 12.2(50)SQ
Cisco RF Gateway 10 New Features List
http://www.cisco.com/en/US/docs/cable/rf_gateway/feature/list/rfgw10_featlist_12_2_50_SQ.html
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for 1:1 Supervisor Card Redundancy
Table 4 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS, Catalyst OS, and Cisco IOS XE 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
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.
