 Feedback
|
Table Of Contents
Route-Switch-Controller Handover Redundancy on the Cisco AS5850
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Configuring Classic-Split Mode
Configuring Handover-Split Mode
Monitoring and Maintaining Handover Redundancy
Route-Switch-Controller Handover Redundancy on the Cisco AS5850
Feature History
This document describes the Route-Switch-Controller Handover Redundancy feature on the Cisco AS5850. It includes the following sections:
•
Supported Standards, MIBs, and RFCs
•
Feature Overview
Route-Switch-Controller Handover Redundancy on the Cisco AS5850, with its provision of handover-split mode, provides the first phase of high availability to the Cisco AS5850 platform.
If your gateway contains two route-switch-controller (RSC) cards, you can configure your Cisco AS5850 into either of two split modes: classic split or handover split.
Classic-Split Mode
Classic-split (the default) mode maximizes system throughput by splitting slots between two RSCs. Each RSC controls a certain set of slots (slots 0-5 are owned by the RSC in slot 6 and slots 8-13 are owned by the RSC in slot 7), and operates as though slots other than those that it controls contain no cards because those cards are controlled by the other RSC. Configuration on each RSC affects only the slots owned by that RSC. Calls on a failed RSC are lost, but calls on the functioning RSC continue normally. Operating a Cisco AS5850 in classic-split mode is the same as having two Cisco AS5850s, each with a separate set of cards.
Handover-Split Mode
Handover-split mode maximizes system availability by allowing an RSC to automatically take control of the slots, cards, and calls of the other RSC should that other RSC fail. Each RSC is configured identically as appropriate for the full set of cards. During normal operation, both RSCs are active, handling their own slots, cards, and calls just as in classic-split mode. Should an RSC fail, the other RSC takes over control of the failed RSC's slots, goes into extraload state, restarts the failed RSC's cards, and handles newly arrived calls on those cards—although calls on the failed RSC are lost at the moment of failure. The failed RSC, should it recover or be restarted, remains in standby state until you instruct the active RSC to hand back its newly acquired slots to the standby RSC. This is, in effect, split dial shelf with handover capability.
Alternately, to use system resources most efficiently, you can operate with one of the two RSCs initially and intentionally in extraload state. In this configuration, RSCA initially controls all slots in the chassis and RSCB is in standby mode, ready to take over should RSCA fail. This allows you to overcome the limits of normal classic-split mode in which, because only six slots are available per RSC, an optimal combination of trunk and DSP cards is difficult to achieve. For more information on performance loads, see the "Restrictions" section.
Benefits
High Availability
RSC Handover Redundancy for the Cisco AS5850, enabled in handover-split mode, eliminates any single point of failure, subsequent downtime, and required user intervention to resolve unrecoverable hardware faults. This improves service availability and reduces both service-affecting time and service interruption.
Restrictions
RSC Card Requirements
You must have two RSC cards installed in your Cisco AS5850 system chassis.
Performance Load and Possible Trunk-Card and Port-Density Limitations
The number of CT3, T1, or E1 trunk cards that your system can support depends on the split mode in which it is configured to operate. In classic-split mode, an RSC card needs to handle the trunk cards in its own half only. In handover-split mode, an RSC card needs to be able to handle the full load of trunk cards across the entire chassis. In either case, the number of trunk cards allowed should not exceed the performance load of the handling RSC card.
For further information about performance loads, refer to the tables on Cisco AS5850 universal port capacities in the overview chapter of Cisco AS5850 Universal Gateway Operations, Administration, Maintenance, and Provisioning Guide.
Throughput Versus Availability
You must choose between maximal throughput and maximal availability:
•
•
Dropped Calls
Calls on a failed RSC, regardless of mode, are lost at the moment of failure.
Fixed Slot Assignments
Slot assignments are fixed and cannot be changed except by a system in handover-split mode during handover. Slots 0-5 are owned by the RSC in slot 6, and slots 8-13 are owned by the RSC in slot 7.
Related Features and Technologies
Router-Shelf Redundancy
The Router-Shelf Redundancy feature that is available on the Cisco AS5800 is similar to RSC Handover Redundancy on the Cisco AS5850.
Related Documents
•
Supported Platforms
•
Table 1 Cisco IOS Release and Platform Support for this Feature
Cisco AS5850
X
X
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/fn. An account on Cisco.com is not required.
Availability of Cisco IOS Software Images
Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.
Supported Standards, MIBs, and RFCs
Standards
None
MIBs
•
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtmlRFCs
None
Prerequisites
RSC Cards
Be sure that you have two RSC cards installed in your Cisco AS5850, one in slot 6 and one in slot 7.
Trunk Cards
If you have CT3, T1, or E1 trunk cards in your Cisco AS5850, be sure that you have a supportable number. For more information on performance loads, see the "Restrictions" section.
Cisco IOS Image
•
•
You must replicate the startup configuration for all line cards in the system in both RSCs' saved configurations to ensure correct operation after a handover.
•
Configuration Tasks
See the following sections for configuration tasks for this feature. Each task in the list is identified as either required or optional. Note that you must configure and verify either classic-split mode (the default) or handover-split mode.
•
•
or
•
•
Configuring Classic-Split Mode
Connect to each RSC in turn and enter these commands.
Note
Note
A classic-split system appears to SNMP management applications as two separate Cisco AS5850s. You must conduct a console session for each RSC (two console sessions) to configure your splits. The system controller manages a classic-split configuration as two separate Cisco AS5850 universal gateways.
Network management systems (NMSs) such as the Cisco Universal Gateway Manager (Cisco UGM) are available that provide a single system view of multiple points of presence (POPs) as they monitor performance and log accounting data. An NMS has a graphical user interface (GUI); runs on a UNIX SPARC station; and includes a database-management system, polling engine, trap management, and map integration.The NMS can be installed at a remote facility so that you can access multiple systems through a console port or Web interface.
In classic-split mode, it is desirable—and, with an NMS, essential—to use four unique IDs, one for each RSC and one for each set of slots. In some cases, however, it is sufficient to use the same ID for the two RSCs.
Verifying Classic-Split Mode
In classic-split mode, most show commands (with exceptions noted below) display information for only those slots owned by the RSC; they look and behave as they would if there were no cards in the slots that the RSC does not own. To see show command information for a slot, you must connect to the RSC that owns that slot.
Enter any of the following commands, in any order.
•
•
•
RouterA# show chassisSystem is in classic-split mode, RSC in slot 6.Slots owned: 0 1 2 3 4 5Slots configured: 0 1 2 3 4 5Slots owned by other: 8 9 10 11 12 13Slot Board CPU DRAM I/O Memory State ElapsedType Util Total (free) Total (free) Time1 UP324 0%/0% 60159040( 51%) 67108864( 73%) Up 6d01h2 UP324 0%/0% 60159040( 56%) 67108864( 73%) Up 6d01h3 UP324 0%/0% 60159040( 56%) 67108864( 73%) Up 6d01h4 CT3_UP216 0%/0% 60159040( 50%) 67108864( 72%) Up 6d01hSystem set for auto bootRouterB# show chassisSystem is in classic-split mode, RSC in slot 7.Slots owned: 8 9 10 11 12 13Slots configured: 8 9 10 11 12 13Slots owned by other: 0 1 2 3 4 5Slot Board CPU DRAM I/O Memory State ElapsedType Util Total (free) Total (free) Time9 CT3_UP216 0%/0% 60159040( 65%) 67108864( 72%) Up 00:21:4610 UP324 0%/0% 60159040( 62%) 67108864( 73%) Up 00:21:4811 UP324 0%/0% 60159040( 62%) 67108864( 73%) Up 00:21:49System set for auto boot•
RouterA# show chassis clocksPrimary Clock:--------------Slot 6:System primary is Slot: 4 Port: 1 of priority 10TDM Bus Master Clock Generator State = NORMALBackup clocks:Source Slot Port DS3-Port Priority Status State-------------------------------------------------------------Trunk 9 1 0 8 Good ConfiguredTrunk 4 21 0 498 Good DefaultTrunk 9 21 0 503 Good DefaultStatus of trunk clocks:-----------------------Ds3 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1Slot Port Type 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 14 0 T3 B B B B B B B G G G G G G G G G G G G G G G G G G G G G9 0 T3 B B B B B B B G G G G G G G G G G G G G G G G G G G G GConfiguring Handover-Split Mode
Perform the following steps on both RSCs so that all cards are configured on both RSCs.
Connect to each RSC in turn, change the running configuration so that all cards are configured on this RSC, and perform the following steps.
The net result, when you are done, is that all cards are configured on each RSC.
Note
Note
Verifying Handover-Split Mode
Enter any of the following commands, in any order.
•
RouterA# show redundancy statesmy state = 13 -ACTIVEpeer state = 13 -ACTIVEMode = DuplexUnit = Preferred PrimaryUnit ID = 6Redundancy Mode = Handover-split: If one RSC fails, the peer RSC will take over the feature boardsMaintenance Mode = DisabledManual Swact = EnabledCommunications = Upclient count = 3client_notification_TMR = 30000 millisecondskeep_alive TMR = 4000 millisecondskeep_alive count = 0keep_alive threshold = 7RF debug mask = 0x0•
RouterA# show redundancy historyRedundancy Facility Event Log:00:00:00 client added: RF_INTERNAL_MSG(0) seq=000:00:00 client added: RF_LAST_CLIENT(65000) seq=6500000:00:09 client added: Rsc split dshelf client(19) seq=80000:00:09 *my state = INITIALIZATION(2) *peer state = DISABLED(1)00:00:09 RF_PROG_INITIALIZATION(100) RF_INTERNAL_MSG(0) op=0 rc=1100:00:09 RF_PROG_INITIALIZATION(100) Rsc split dshelf client(19) op=0 rc=1100:00:09 RF_PROG_INITIALIZATION(100) RF_LAST_CLIENT(65000) op=0 rc=1100:00:09 *my state = NEGOTIATION(3) peer state = DISABLED(1)00:00:11 RF_STATUS_PEER_PRESENCE(400) op=100:00:11 RF_STATUS_PEER_PRESENCE(400) Rsc split dshelf client(19) op=100:00:11 RF_STATUS_PEER_COMM(401) op=100:00:11 RF_STATUS_PEER_COMM(401) Rsc split dshelf client(19) op=100:00:11 my state = NEGOTIATION(3) *peer state = UNKNOWN(0)00:00:15 RF_EVENT_CLIENT_PROGRESSION(503) RF_LAST_CLIENT(65000) op=100:00:15 RF_PROG_PLATFORM_SYNC(300) RF_LAST_CLIENT(65000) op=1 rc=000:00:15 RF_EVENT_CLIENT_PROGRESSION(503) RF_LAST_CLIENT(65000) op=1 rc=000:00:17 RF_STATUS_REDUNDANCY_MODE_CHANGE(405) Rsc split dshelf client(19) op=300:00:17 RF_EVENT_GO_STANDBY(512) op=000:00:17 *my state = STANDBY COLD(4) peer state = UNKNOWN(0)00:00:17 RF_PROG_STANDBY_COLD(101) RF_INTERNAL_MSG(0) op=0 rc=1100:00:17 RF_PROG_STANDBY_COLD(101) Rsc split dshelf client(19) op=0 rc=1100:00:17 RF_PROG_STANDBY_COLD(101) RF_LAST_CLIENT(65000) op=0 rc=1100:00:19 my state = STANDBY COLD(4) *peer state = ACTIVE_EXTRALOAD(14)00:00:51 Configuration parsing complete00:00:53 System initialization complete00:01:11 RF_STATUS_PEER_PRESENCE(400) op=000:01:11 RF_STATUS_PEER_PRESENCE(400) Rsc split dshelf client(19) op=000:01:11 my state = STANDBY COLD(4) *peer state = DISABLED(1)00:01:11 Reloading peer (peer presence lost)00:01:11 *my state = ACTIVE-FAST(9) peer state = DISABLED(1)00:01:11 RF_STATUS_MAINTENANCE_ENABLE(403) Rsc split dshelf client(19) op=000:01:11 RF_PROG_ACTIVE_FAST(200) RF_INTERNAL_MSG(0) op=0 rc=1100:01:11 RF_PROG_ACTIVE_FAST(200) Rsc split dshelf client(19) op=0 rc=1100:01:11 RF_PROG_ACTIVE_FAST(200) RF_LAST_CLIENT(65000) op=0 rc=1100:01:11 *my state = ACTIVE-DRAIN(10) peer state = DISABLED(1)00:01:11 RF_PROG_ACTIVE_DRAIN(201) RF_INTERNAL_MSG(0) op=0 rc=1100:01:11 RF_PROG_ACTIVE_DRAIN(201) Rsc split dshelf client(19) op=0 rc=1100:01:11 RF_PROG_ACTIVE_DRAIN(201) RF_LAST_CLIENT(65000) op=0 rc=1100:01:11 *my state = ACTIVE_PRECONFIG(11) peer state = DISABLED(1)00:01:11 RF_PROG_ACTIVE_PRECONFIG(202) RF_INTERNAL_MSG(0) op=0 rc=1100:01:11 RF_PROG_ACTIVE_PRECONFIG(202) Rsc split dshelf client(19) op=0 rc=1100:01:11 RF_PROG_ACTIVE_PRECONFIG(202) RF_LAST_CLIENT(65000) op=0 rc=1100:01:11 *my state = ACTIVE_POSTCONFIG(12) peer state = DISABLED(1)00:01:11 RF_PROG_ACTIVE_POSTCONFIG(203) RF_INTERNAL_MSG(0) op=0 rc=1100:01:11 RF_PROG_ACTIVE_POSTCONFIG(203) Rsc split dshelf client(19) op=0 rc=1100:01:11 RF_PROG_ACTIVE_POSTCONFIG(203) RF_LAST_CLIENT(65000) op=0 rc=1100:01:11 *my state = ACTIVE(13) peer state = DISABLED(1)00:01:11 RF_PROG_ACTIVE(204) RF_INTERNAL_MSG(0) op=0 rc=1100:01:11 RF_PROG_ACTIVE(204) Rsc split dshelf client(19) op=0 rc=1100:01:11 RF_PROG_ACTIVE(204) RF_LAST_CLIENT(65000) op=0 rc=1100:01:11 RF_STATUS_PEER_COMM(401) op=000:01:11 RF_STATUS_PEER_COMM(401) Rsc split dshelf client(19) op=000:01:11 Reloading peer (communication down)00:01:11 RF_EVENT_GO_ACTIVE_EXTRALOAD(513) RF_INTERNAL_MSG(0) op=000:01:11 RF_PROG_EXTRALOAD(301) RF_INTERNAL_MSG(0) op=0 rc=1100:01:11 RF_PROG_EXTRALOAD(301) Rsc split dshelf client(19) op=0 rc=1100:01:11 RF_PROG_EXTRALOAD(301) RF_LAST_CLIENT(65000) op=0 rc=1100:01:11 RF_EVENT_GO_ACTIVE_EXTRALOAD(513) RF_INTERNAL_MSG(0) op=000:03:02 RF_STATUS_PEER_PRESENCE(400) op=100:03:02 RF_STATUS_PEER_PRESENCE(400) Rsc split dshelf client(19) op=100:03:02 RF_STATUS_PEER_COMM(401) op=100:03:02 RF_STATUS_PEER_COMM(401) Rsc split dshelf client(19) op=100:03:02 *my state = ACTIVE_EXTRALOAD(14) *peer state = UNKNOWN(0)00:03:02 RF_PROG_PLATFORM_SYNC(300) RF_INTERNAL_MSG(0) op=0 rc=1100:03:02 RF_PROG_PLATFORM_SYNC(300) Rsc split dshelf client(19) op=0 rc=1100:03:02 RF_PROG_PLATFORM_SYNC(300) RF_LAST_CLIENT(65000) op=0 rc=000:03:02 RF_EVENT_CLIENT_PROGRESSION(503) RF_LAST_CLIENT(65000) op=1 rc=000:03:02 my state = ACTIVE_EXTRALOAD(14) *peer state = NEGOTIATION(3)00:03:02 RF_EVENT_PEER_PROG_DONE(506) RF_LAST_CLIENT(65000) op=30000:03:06 my state = ACTIVE_EXTRALOAD(14) *peer state = STANDBY COLD(4)6d01h RF_EVENT_GO_ACTIVE_HANDBACK(514) RF_INTERNAL_MSG(0) op=06d01h RF_PROG_HANDBACK(302) RF_INTERNAL_MSG(0) op=0 rc=116d01h RF_PROG_HANDBACK(302) Rsc split dshelf client(19) op=0 rc=06d01h RF_EVENT_CLIENT_PROGRESSION(503) Rsc split dshelf client(19) op=1 rc=06d01h RF_EVENT_GO_ACTIVE(511) op=06d01h Reloading peer (this unit becoming active)6d01h *my state = ACTIVE-FAST(9) peer state = STANDBY COLD(4)6d01h RF_STATUS_MAINTENANCE_ENABLE(403) Rsc split dshelf client(19) op=06d01h RF_PROG_ACTIVE_FAST(200) RF_INTERNAL_MSG(0) op=0 rc=116d01h RF_PROG_ACTIVE_FAST(200) Rsc split dshelf client(19) op=0 rc=116d01h RF_PROG_ACTIVE_FAST(200) RF_LAST_CLIENT(65000) op=0 rc=116d01h *my state = ACTIVE-DRAIN(10) peer state = STANDBY COLD(4)6d01h RF_PROG_ACTIVE_DRAIN(201) RF_INTERNAL_MSG(0) op=0 rc=116d01h RF_PROG_ACTIVE_DRAIN(201) Rsc split dshelf client(19) op=0 rc=116d01h RF_PROG_ACTIVE_DRAIN(201) RF_LAST_CLIENT(65000) op=0 rc=116d01h *my state = ACTIVE_PRECONFIG(11) peer state = STANDBY COLD(4)6d01h RF_PROG_ACTIVE_PRECONFIG(202) RF_INTERNAL_MSG(0) op=0 rc=116d01h RF_PROG_ACTIVE_PRECONFIG(202) Rsc split dshelf client(19) op=0 rc=116d01h RF_PROG_ACTIVE_PRECONFIG(202) RF_LAST_CLIENT(65000) op=0 rc=116d01h *my state = ACTIVE_POSTCONFIG(12) peer state = STANDBY COLD(4)6d01h RF_PROG_ACTIVE_POSTCONFIG(203) RF_INTERNAL_MSG(0) op=0 rc=116d01h RF_PROG_ACTIVE_POSTCONFIG(203) Rsc split dshelf client(19) op=0 rc=116d01h RF_PROG_ACTIVE_POSTCONFIG(203) RF_LAST_CLIENT(65000) op=0 rc=116d01h *my state = ACTIVE(13) peer state = STANDBY COLD(4)6d01h RF_PROG_ACTIVE(204) RF_INTERNAL_MSG(0) op=0 rc=116d01h RF_PROG_ACTIVE(204) Rsc split dshelf client(19) op=0 rc=06d01h RF_EVENT_CLIENT_PROGRESSION(503) Rsc split dshelf client(19) op=1 rc=06d01h my state = ACTIVE(13) *peer state = ACTIVE(13)6d01h my state = ACTIVE(13) *peer state = UNKNOWN(0)6d01h Reloading peer (notification timeout)6d01h my state = ACTIVE(13) *peer state = ACTIVE(13)6d01h RF_STATUS_REDUNDANCY_MODE_CHANGE(405) Rsc split dshelf client(19) op=16d01h RF_EVENT_GO_ACTIVE(511) op=06d01h RF_STATUS_REDUNDANCY_MODE_CHANGE(405) Rsc split dshelf client(19) op=36d01h RF_EVENT_GO_ACTIVE(511) op=0•
RouterA# show redundancy handoverNo handover pending•
•
The following example shows output for two RSCs in normal-load state.
RouterA# show chassisSystem is in handover-split mode, RSC in slot 6.Slots owned: 0 1 2 3 4 5Slots configured: 0 1 2 3 4 5 8 9 10 11 12 13Slots owned by other: 8 9 10 11 12 13Slot Board CPU DRAM I/O Memory State ElapsedType Util Total (free) Total (free) Time1 UP324 17%/17% 60159040( 50%) 67108864( 73%) Up 6d01h2 UP324 1%/0% 60159040( 56%) 67108864( 73%) Up 6d01h3 UP324 0%/0% 60159040( 56%) 67108864( 73%) Up 6d01h4 CT3_UP216 1%/0% 60159040( 49%) 67108864( 72%) Up 6d01h9 CT3_UP216 60159040( 0%) 67108864( 0%) Ignore 00:00:2010 UP324 60159040( 0%) 67108864( 0%) Ignore 00:00:1911 UP324 60159040( 0%) 67108864( 0%) Ignore 00:00:18System set for auto bootRouterB# show chassisSystem is in handover-split mode, RSC in slot 7.Slots owned: 8 9 10 11 12 13Slots configured: 0 1 2 3 4 5 8 9 10 11 12 13Slots owned by other: 0 1 2 3 4 5Slot Board CPU DRAM I/O Memory State ElapsedType Util Total (free) Total (free) Time1 UP324 0( 0%) 0( 0%) Ignore 00:00:382 UP324 0( 0%) 0( 0%) Ignore 00:00:373 UP324 0( 0%) 0( 0%) Ignore 00:00:364 CT3_UP216 0( 0%) 0( 0%) Ignore 00:00:359 CT3_UP216 0%/0% 60159040( 65%) 67108864( 72%) Up 00:23:1410 UP324 0%/0% 60159040( 62%) 67108864( 73%) Up 00:23:1611 UP324 0%/0% 60159040( 62%) 67108864( 73%) Up 00:23:17System set for auto bootThe following example shows output for one RSC in extraload state.
RouterA# show chassisSystem is in handover-split mode, RSC in slot 6.Slots owned: 0 1 2 3 4 5 8 9 10 11 12 13Slots configured: 0 1 2 3 4 5 8 9 10 11 12 13Slots owned by other: noneSlot Board CPU DRAM I/O Memory State ElapsedType Util Total (free) Total (free) Time1 UP324 0%/0% 60159040( 50%) 67108864( 73%) Up 6d02h2 UP324 1%/0% 60159040( 56%) 67108864( 73%) Up 6d02h3 UP324 0%/0% 60159040( 56%) 67108864( 73%) Up 6d02h4 CT3_UP216 6%/5% 60159040( 49%) 67108864( 72%) Up 6d02h9 CT3_UP216 5%/4% 60159040( 56%) 67108864( 72%) Up 00:10:2910 UP324 20%/20% 60159040( 56%) 67108864( 73%) Up 00:10:3011 UP324 0%/0% 60159040( 56%) 67108864( 73%) Up 00:10:30System set for auto bootTroubleshooting Tips
Monitoring and Maintaining Handover Redundancy
Note
The following example shows two instances of handover scheduling, verification, cancellation, and verification of cancellation:
RouterA# redundancy handover shelf-resources busyout-period 10 at 16:15 5 Sept 2001Newly entered handover schedule:Busyout period at 16:15:00 PST Wed Sep 5 2001 for a duration of 10 minute(s)Handover pending at 16:25:00 PST Wed Sep 5 2001Clear calls, handover and reload as specified above?[confirm]RouterA# show redundancy handoverBusyout period at 16:15:00 PST Wed Sep 5 2001 for a duration of 10 minute(s)Handover pending at 16:25:00 PST Wed Sep 5 2001RouterA# redundancy handover cancelScheduled handover is cancelledRSC-Slot6# show redundancy handoverNo handover pendingRouterA# redundancy handover peer-resources busyout-period 10 at 16:37 5 Sep 2001Newly entered handover schedule:Busyout period at 16:37:00 PST Wed Sep 5 2001 for a duration of 10 minute(s)Handover pending at 16:47:00 PST Wed Sep 5 2001Clear calls and handover as specified above?[confirm]RouterA# show redundancy handoverBusyout period at 16:37:00 PST Wed Sep 5 2001 for a duration of 10 minute(s)Handover pending at 16:47:00 PST Wed Sep 5 2001RouterA# redundancy handover cancelScheduled handover is cancelledRouterA# show redundancy handoverNo handover pendingConfiguration Examples
The following example shows a startup configuration that supports redundancy. Note, in the sections on resource-pool range and controller numbers, that every card in the chassis is configured.
RouterA# show startup-configversion 12.2no service padservice timestamps debug datetime msecservice timestamps log datetime msecno service password-encryptionservice compress-config!hostname RouterA!redundancymode handover-splitaaa new-model!!aaa group server tacacs+ redline2!aaa group server radius RADIUS-GROUPserver 172.22.51.9 auth-port 1645 acct-port 1646!aaa authentication login CONSOLE noneaaa authentication login VTY noneaaa authentication ppp default group RADIUS-GROUPaaa authentication ppp RADIUS-LIST group RADIUS-GROUPaaa authorization exec CONSOLE noneaaa authorization exec RADIUS-LIST group RADIUS-GROUPaaa authorization network default group RADIUS-GROUP if-authenticatedaaa authorization network RADIUS-LIST group RADIUS-GROUP if-authenticatedaaa accounting network default start-stop group RADIUS-GROUPaaa nas port extendedaaa session-id commonenable password xxx!username RouterB password 0 xxxusername 54006username 54006_1 password 0 xxxusername RouterA password 0 xxxusername 54006_d_119 password 0 xxx!resource-pool enable!resource-pool group resource group1range port 1/0 1/323range port 4/20 4/30!resource-pool group resource group2range port 9/0 9/215range port 10/0 10/120!resource-pool group resource digital_group_6range limit 207!resource-pool group resource digital_grouprange limit 116!resource-pool group resource vpdn_digrange limit 92!resource-pool profile customer 54006_customerlimit base-size alllimit overflow-size 0resource group1 speechdnis group 54006_dnis!resource-pool profile customer 54007_customerlimit base-size alllimit overflow-size 0resource group2 speechdnis group 54007_dnis!resource-pool profile customer 54006_customer_synclimit base-size alllimit overflow-size 0resource digital_group_6 digitaldnis group 54006_sync_dnis!resource-pool profile customer 54007_synclimit base-size alllimit overflow-size 0resource digital_group digitaldnis group 54007_sync_dnis!resource-pool profile customer 54007_sync_vpdnlimit base-size alllimit overflow-size 0resource vpdn_dig digitaldnis group 54007_sync_vpdn_dnisclock timezone PST -7dial-tdm-clock priority 8 trunk-slot 9 ds3-port 0 port 1dial-tdm-clock priority 10 trunk-slot 4 ds3-port 0 port 1spe country t1-default!spe link-info poll voice 5!ip subnet-zeroip cef distributedip ftp source-interface FastEthernet6/0ip ftp username rootip ftp password xxxxxno ip domain-lookup!vpdn enable!vpdn-group 1request-dialinprotocol l2fsource-ip 30.0.0.1!chat-script dial "" "ATZ" OK "ATDT\T" TIMEOUT 60 CONNECTisdn switch-type primary-5ess!controller T3 4/0framing c-bitcablelength 224t1 1-28 controller!controller T1 4/0:1framing esfpri-group timeslots 1-24!controller T1 4/0:2framing esfpri-group timeslots 1-24!controller T1 4/0:3framing esfpri-group timeslots 1-24!...controller T1 4/0:28shutdownframing esfpri-group timeslots 1-24!controller T3 9/0framing c-bitcablelength 224t1 1-28 controller!controller T1 9/0:1framing esfds0-group 0 timeslots 1-24 type e&m-fgb dtmf dnis!controller T1 9/0:2framing esfds0-group 0 timeslots 1-24 type e&m-fgb dtmf dnis!controller T1 9/0:3framing esfds0-group 0 timeslots 1-24 type e&m-fgb dtmf dnis!...controller T1 9/0:12framing esfds0-group 0 timeslots 1-24 type e&m-fgb dtmf dnis!controller T1 9/0:13framing esfpri-group timeslots 1-24!...controller T1 9/0:21framing esfpri-group timeslots 1-24!controller T1 9/0:22shutdownframing esfds0-group 0 timeslots 1-24 type e&m-fgb dtmf dnis!...controller T1 9/0:28shutdownframing esfds0-group 0 timeslots 1-24 type e&m-fgb dtmf dnis!!!interface Loopback0ip address 111.111.111.11 255.255.255.0no ip mroute-cache!interface Serial4/0:1:23no ip addressencapsulation pppip mroute-cacheisdn switch-type primary-5essisdn incoming-voice modem!interface Serial4/0:2:23no ip addressencapsulation pppip mroute-cacheisdn switch-type primary-5essisdn incoming-voice modem!interface Serial4/0:3:23no ip addressencapsulation pppip mroute-cacheisdn switch-type primary-5essisdn incoming-voice modem!...interface Serial4/0:10:23no ip addressencapsulation pppip mroute-cacheisdn switch-type primary-5essisdn incoming-voice modem!interface Serial4/0:11:23no ip addressencapsulation pppip mroute-cacheisdn switch-type primary-5essisdn incoming-voice modem!interface Serial9/0:21:23ip unnumbered Loopback0encapsulation pppip mroute-cachedialer rotary-group 1dialer-group 1isdn switch-type primary-5ess!interface Group-Async0ip unnumbered Loopback0encapsulation pppdialer in-banddialer idle-timeout 36000 eitherdialer string 6003dialer-group 1async default routingasync mode dedicatedpeer default ip address pool KRAMERppp max-bad-auth 3ppp authentication chap pap callin RADIUS_LISTppp chap hostname RouterBppp chap password 7 xxxxxgroup-range 9/00 11/323!interface Group-Async1ip unnumbered Loopback0encapsulation pppdialer in-banddialer idle-timeout 36000 eitherdialer string 6003dialer-group 1async default routingasync mode dedicatedpeer default ip address pool KRAMER1ppp max-bad-auth 3ppp authentication chap pap callin RADIUS_LISTppp chap hostname RouterAppp chap password 7 xxxxxgroup-range 1/00 4/215!interface Dialer0ip unnumbered Loopback0encapsulation pppdialer in-banddialer idle-timeout 36000 eitherdialer string 6003dialer-group 1peer default ip address pool KRAMER1_d_mno fair-queueno cdp enableppp authentication chap pap callin RADIUS_LISTppp chap hostname RouterAppp chap password 7 xxxxxppp multilink!interface Dialer1ip unnumbered Loopback0encapsulation pppdialer in-banddialer idle-timeout 36000 eitherdialer string 6003dialer-group 1peer default ip address pool KRAMER_dno cdp enableppp max-bad-auth 3ppp authentication chap pap callin RADIUS_LISTppp chap hostname RouterBppp chap password 7 xxxxx!interface Dialer2ip unnumbered Loopback0encapsulation pppdialer in-banddialer idle-timeout 36000 eitherdialer string 6003dialer-group 1peer default ip address pool KRAMER1_dno fair-queueno cdp enableppp authentication chap pap callin RADIUS_LISTppp chap hostname RouterAppp chap password 7 xxxxx!interface Dialer5no ip addressno cdp enable!interface Dialer6no ip addressno cdp enable!interface Dialer7no ip addressno cdp enable!...interface Dialer26no ip addressno cdp enable!ip local pool KRAMER1 10.6.1.1 10.6.1.108ip local pool KRAMER1 10.6.2.1 10.6.2.108ip local pool KRAMER1 10.6.3.1 10.6.3.60ip local pool KRAMER 10.7.1.1 10.7.1.108ip local pool KRAMER 10.7.2.1 10.7.2.108ip local pool KRAMER 10.7.3.1 10.7.3.60ip local pool KRAMER1_d 10.6.4.1 10.6.4.115ip local pool KRAMER_d 10.7.4.1 10.7.4.115ip local pool KRAMER1_d_m 10.6.4.116 10.6.4.163ip classlessno ip http server!ip radius source-interface FastEthernet6/0!dialer dnis group 54006_dnisnumber 1002number 1002100212!dialer dnis group 54007_dnisnumber 38327!dialer dnis group 54006_sync_dnisnumber 6666number 6600number 6666666666!dialer dnis group 54007_sync_dnisnumber 7700number 7700000000!dialer dnis group 54007_sync_vpdn_dnisnumber 7777number 7777777777!dialer dnis group 54007_vpdn_dnisnumber 38777dialer-list 1 protocol ip permitno cdp run!tacacs-server host 152.22.51.64tacacs-server timeout 30tacacs-server key ciscosnmp-server community public RWsnmp-server enable traps rf!radius-server configure-nasradius-server host 172.22.51.9 auth-port 1645 acct-port 1646 non-standardradius-server retransmit 3radius-server attribute nas-port format cradius-server key labcall rsvp-sync!voice-port 4/0:1:D!voice-port 4/0:2:D!...voice-port 4/0:28:D!voice-port 9/0:1:0!voice-port 9/0:2:0!...voice-port 9/0:28:0!!line con 0password xxxxxxlogging synchronousline aux 0logging synchronousmodem InOuttransport input allline vty 0 4password xxxtransport preferred telnettransport input telnetline 1/00 4/215modem InOutno modem status-pollno modem log rs232transport preferred nonetransport input allautoselect during-loginautoselect pppline 9/00 9/215modem InOutno modem status-pollno modem log rs232transport preferred nonetransport input allautoselect during-loginautoselect pppline 10/00 11/323modem InOutno modem status-pollno modem log rs232transport preferred nonetransport input allautoselect during-loginautoselect ppp!endCommand Reference
The following commands are introduced or modified in the feature or features documented in this module. For information about these commands, see the Cisco IOS Interface and Hardware Component Command Reference at http://www.cisco.com/en/US/docs/ios/interface/command/reference/ir_book.html. For information about all Cisco IOS commands, go to the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or to the Cisco IOS Master Commands List.
•
•
•
•
•
Glossary
classic-split mode—Mode in which system throughput is maximized because slots are split between two RSCs.
handover—The ability of one part of a system to take over resources that were managed by another part of the system when the latter part fails.
handover-split mode—Mode in which system availability is maximized because an RSC can automatically take control over the slots, cards, and calls of the other RSC, should that other RSC fail.
RSC—route switch controller. The card that provides switch functions, routing, management control, clock control, and egress ports.
service-affecting time—Amount of time during which the system is unable to take new calls or carry the full number of calls.
service interruption—Event during which an in-progress call is dropped, requiring the user to call back.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Pulse, 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, and Flip Gift Card 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 Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Fast Step, Follow Me Browsing, FormShare, GainMaker, GigaDrive, HomeLink, iLYNX, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, 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. (0908R)
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.
© 2007-2009 Cisco Systems, Inc. All rights reserved.
