Table Of Contents
Cisco IOS Broadband High Availability Stateful Switchover
Finding Feature Information
Contents
Prerequisites for Cisco IOS Broadband High Availability Stateful Switchover
Restrictions for Cisco IOS Broadband High Availability Stateful Switchover
Information About Cisco IOS Broadband High Availability Stateful Switchover
Feature Design of Cisco IOS Broadband High Availability Stateful Switchover
Performing an ISSU
Supported Broadband Aggregation Protocols
ISSU L2TP
ISSU PPPoE
ISSU RA-MLPS VPN
Benefits of Cisco IOS Broadband High Availability Stateful Switchover
How to Configure Cisco IOS Broadband High Availability Stateful Switchover
Configuring Subscriber Redundancy Policy for Cisco IOS Broadband High Availability Stateful Switchover
Prerequisites
Verifying and Troubleshooting Subscriber Redundancy Policy for Broadband HA ISSU
Configuration Examples for Cisco IOS Broadband High Availability Stateful Switchover
PPPoX Terminated into an RA-MPLS Network with ISSU: Example
Additional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Feature Information for Cisco IOS Broadband High Availability Stateful Switchover
Cisco IOS Broadband High Availability Stateful Switchover
First Published: December 4, 2006
Last Updated: November 25, 2009
The Broadband High Availability (HA) In Service Software Upgrade feature uses the ISSU—PPPoE feature to ensure continuous operations of broadband access protocols during software upgrades, downgrades, and service enhancements.
Finding Feature Information
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 Cisco IOS Broadband High Availability Stateful Switchover" section.
Use Cisco Feature Navigator to find information about platform support 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 Cisco IOS Broadband High Availability Stateful Switchover
•
Restrictions for Cisco IOS Broadband High Availability Stateful Switchover
•
Information About Cisco IOS Broadband High Availability Stateful Switchover
•
How to Configure Cisco IOS Broadband High Availability Stateful Switchover
•
Configuration Examples for Cisco IOS Broadband High Availability Stateful Switchover
•
Additional References
•
Feature Information for Cisco IOS Broadband High Availability Stateful Switchover
Prerequisites for Cisco IOS Broadband High Availability Stateful Switchover
The stateful switchover (SSO) and nonstop forwarding (NSF) features must be enabled. For more information on SSO, see Stateful Switchover. For more information on NSF, see Cisco Nonstop Forwarding.
Restrictions for Cisco IOS Broadband High Availability Stateful Switchover
•
You can perform an ISSU across a major Cisco IOS XE release.
•
You can perform an ISSU from a Cisco IOS XE release that supports ISSU capability.
Information About Cisco IOS Broadband High Availability Stateful Switchover
To configure the Cisco IOS Broadband High Availability Stateful Switchover feature, you should understand the following concepts:
•
Feature Design of Cisco IOS Broadband High Availability Stateful Switchover
•
Benefits of Cisco IOS Broadband High Availability Stateful Switchover
Feature Design of Cisco IOS Broadband High Availability Stateful Switchover
Prior to the implementation of the Cisco IOS Broadband High Availability Stateful Switchover feature, software upgrades typically required planned outages that took the router or network out of service. The Cisco IOS Broadband High Availability Stateful Switchover feature enables the service provider to maximize network availability and eliminate planned outages by allowing the Cisco IOS XE release to be upgraded without taking the router or network out of service. ISSU is a procedure, based on Cisco high availability (HA) architecture, whereby the Cisco IOS XE infrastructure accomplishes an upgrade while packet forwarding continues and broadband sessions are maintained. Cisco HA architecture is based on redundant Route Processors and the NSF and SSO features, such that ports stay active and calls do not drop, eliminating network disruption during upgrades.
The ISSU feature allows deployment of new features, hardware, services, and maintenance fixes in a procedure that is seamless to end users. A critical component of ISSU and Cisco HA technology is the cluster control manager (CCM) that manages session recreation and synchronization on the standby processor. The Cisco IOS Broadband High Availability Stateful Switchover feature allows the configuration of subscriber redundancy policies that tune the synchronization process. For more information see the "Configuring Subscriber Redundancy Policy for Cisco IOS Broadband High Availability Stateful Switchover" section.
The Cisco IOS Broadband High Availability Stateful Switchover feature handles upgrades and downgrades, and supports the following:
•
Upgrades from one software feature release to another, as long as both versions support the ISSU feature, for example, from Cisco IOS XE Release 2.2 to Cisco IOS XE Release 2.3.
•
Upgrades from one software maintenance release to another, for example from Cisco IOS XE Release 2.2.1 to Cisco IOS XE Release 2.2.2.
The Cisco IOS Broadband High Availability Stateful Switchover feature works with other Cisco IOS XE HA features, NSF and SSO, to maintain broadband sessions.
Performing an ISSU
For detailed information about High Availability and about performing an ISSU, see the following chapters in the Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide:
•
"High Availability Overview"
•
"Cisco IOS XE Software Package Compatibility for ISSU"
•
"In Service Software Upgrade (ISSU)"
Supported Broadband Aggregation Protocols
The Cisco IOS Broadband High Availability Stateful Switchover feature supports the following broadband aggregation protocols:
•
ISSU L2TP
•
ISSU PPPoE
•
ISSU RA-MLPS VPN
ISSU L2TP
The L2TP HA Session SSO/ISSU on a LAC/LNS feature provides a generic stateful switchover/In Service Software Upgrade (SSO/ISSU) mechanism for Layer 2 Tunneling Protocol (L2TP) on a Layer 2 Access Concentrator (LAC) and a Layer 2 Network Server (LNS). This feature preserves all fully established PPP and L2TP sessions during an SSO switchover or an ISSU upgrade or downgrade.
ISSU PPPoE
The Cisco IOS Broadband High Availability Stateful Switchover feature delivers ISSU capability for PPP over Ethernet (PPPoE) subscriber access sessions, including PPPoE, PPPoEoVLAN, and PPPoEoQinQ sessions, during supported software upgrades, downgrades, and enhancements.
ISSU RA-MLPS VPN
The Cisco IOS Broadband High Availability Stateful Switchover feature delivers ISSU capability for PPPoA and PPPoE (PPPoX) sessions terminated into remote access (RA)-Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPN) or PPPoX into MPLS VPN during supported software upgrades, downgrades, and enhancements.
Figure 1 shows a typical broadband aggregation HA deployment with ISSU functionality.
Figure 1 Broadband Aggregation High Availability Deployment
Benefits of Cisco IOS Broadband High Availability Stateful Switchover
•
Eliminates network downtime for Cisco IOS XE software upgrades.
•
Eliminates resource scheduling challenges associated with planned outages and late night maintenance windows.
•
Accelerates deployment of new services and applications and allows faster implementation of new features, hardware, and fixes.
•
Reduces operating costs due to outages while delivering higher service levels.
•
Provides additional options for adjusting maintenance windows.
•
Minimizes the impact of upgrades to service and allows for faster upgrades, resulting in higher availability.
How to Configure Cisco IOS Broadband High Availability Stateful Switchover
This section contains the following procedures:
•
Configuring Subscriber Redundancy Policy for Cisco IOS Broadband High Availability Stateful Switchover
•
Verifying and Troubleshooting Subscriber Redundancy Policy for Broadband HA ISSU
Configuring Subscriber Redundancy Policy for Cisco IOS Broadband High Availability Stateful Switchover
The Cisco IOS Broadband High Availability Stateful Switchover feature is enabled by default. This task configures subscriber redundancy policy for HA ISSU capability, allowing you to manage synchronization between HA active and standby processors.
Prerequisites
For information about High Availability and about performing an ISSU, see the following chapters in the Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide:
•
"High Availability Overview"
•
"Cisco IOS XE Software Package Compatibility for ISSU"
•
"In Service Software Upgrade (ISSU)"
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
subscriber redundancy [bulk limit cpu percentage delay seconds allow value] [dynamic limit cpu percentage delay seconds allow value] [delay time] [rate sessions time]
4.
exit
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
subscriber redundancy [bulk limit cpu
percentage delay seconds allow value][dynamic
limit cpu percentage delay seconds allow
value][delay time][rate sessions time]
Example:
Router(config)# subscriber redundancy bulk
limit cpu 75 delay 20 allow 30
|
(Optional) Configures subscriber redundancy policy.
• bulk—Configures bulk synchronization redundancy policy.
• limit cpu percentage—Specifies CPU busy threshold value as a percentage. Range is 0 to 100; default is 90.
• delay seconds—Specifies delay in seconds before the CCM component synchronizes sessions after the CPU busy threshold is exceeded.
• allow value—Specifies the minimum number of sessions to synchronize once the CPU busy threshold is exceeded and the specified delay is met. Range is 1 to 2147483637; default is 25.
• dynamic—Configures a dynamic synchronization redundancy policy.
• delay time—Specifies a minimum amount of time in seconds that a session must be ready before dynamic synchronization occurs. Range is 1 to 33550.
• rate sessions time—Specifies number of sessions per time period for bulk and dynamic synchronization.
– sessions—Range is 1 to 32000; default is 250.
– time—Range in seconds is 1 to 33550; default is 1.
|
Step 4
|
exit
Example:
Router(config)# exit
|
Exits the current configuration mode.
|
Verifying and Troubleshooting Subscriber Redundancy Policy for Broadband HA ISSU
To verify the subscriber redundancy policy configuration, use the show running-config command. Sample output is available in the "Configuration Examples for Cisco IOS Broadband High Availability Stateful Switchover" section.
Step 1 and Step 2 are useful for troubleshooting the CCM synchronization component. Step 3 and Step 4, are useful for reviewing PPPoX session statistics. Step 5 and Step 6, are useful for verifying the failure of any L2TP tunnels or VPDN groups. Step 7 is typically used by Cisco engineers for internal debugging purposes.
SUMMARY STEPS
1.
show ccm clients
2.
show ccm sessions
3.
show ppp subscriber statistics
4.
show pppoe statistics
5.
show vpdn redundancy
6.
show vpdn history failure
7.
debug pppoe redundancy
DETAILED STEPS
Step 1
show ccm clients
This command shows information on the CCM, the HA component that manages the capability to
synchronize session launch on the standby processor of a redundant processor HA system. Use the
show ccm clients command to display information on CCM clients.
Active Route Processor
CCM bundles sent since peer up:
Sent Queued for flow control
Client events sent since peer up:
Standby Route Processor
CCM bundles rcvd since last boot:
Client events extracted since last boot:
Step 2
show ccm sessions
This command shows information on sessions managed by CCM.
Active Route Processor
Router# show ccm sessions
Global CCM state: CCM HA Active - Dynamic Sync
Global ISSU state: Compatible, Clients Cap 0x9EFFE
Current Bulk Sent Bulk Rcvd
----------- ----------- -----------
Number of sessions in state Down: 0 0 0
Number of sessions in state Not Ready: 0 0 9279
Number of sessions in state Ready: 0 0 6721
Number of sessions in state Dyn Sync: 16000 16000 0
Timeout: Timer Type Delay Remaining Starts CPU Limit CPU Last
------------ -------- --------- ----------- --------- --------
Dynamic CPU 00:00:10 - 0 90 0
Bulk Time Li 00:08:00 - 1 - -
RF Notif Ext 00:00:01 - 475 - -
Standby Route Processor
Router# show ccm sessions
Global CCM state: CCM HA Standby - Collecting
Global ISSU state: Compatible, Clients Cap 0x9EFFE
Current Bulk Sent Bulk Rcvd
----------- ----------- -----------
Number of sessions in state Down: 0 0 0
Number of sessions in state Not Ready: 0 0 8384
Number of sessions in state Ready: 16000 0 7616
Number of sessions in state Dyn Sync: 0 0 0
Timeout: Timer Type Delay Remaining Starts CPU Limit CPU Last
------------ -------- --------- ----------- --------- --------
Dynamic CPU 00:00:10 - 0 90 0
Bulk Time Li 00:08:00 - 1 - -
RF Notif Ext 00:00:01 - 0 - -
Step 3
show ppp subscriber statistics
This command is useful for displaying events and statistics for PPP subscribers. Use the
show ppp subscriber statistics command to display a cumulative count of PPP subscriber events and statistics, and to display an incremental count since the clear ppp subscriber statistics command was last issued.
The following is sample output from the show ppp subscriber statistics command:
Router# show ppp subscriber statistics
PPP Subscriber Events TOTAL SINCE CLEARED
PPP Subscriber Statistics TOTAL SINCE CLEARED
Step 4
show pppoe statistics
This command is useful for obtaining statistics and events for PPPoE sessions. Use the
show pppoe statistics command to display a cumulative count of PPPoE events and statistics, and to display an incremental count since the last time the clear pppoe statistics command was issued.
The following is sample output from the show pppoe statistics command:
Router# show pppoe statistics
PPPoE Events TOTAL SINCE CLEARED
------------------------------ ------------- -------------
PPPoE Statistics TOTAL SINCE CLEARED
------------------------------ ------------- -------------
PPPoE Handles Allocated 0 0
Step 5
show vpdn redundancy
Use this command to verify the failure of any L2TP tunnels.
Router# show vpdn redundancy
L2TP HA support: Silent Failover
Checkpoint Messaging on: FALSE
L2TP Tunnels: 2/2/2/0 (total/HA-enabled/HA-est/resync)
L2TP Sessions: 10/10/10 (total/HA-enabled/HA-est)
L2TP Resynced Tunnels: 0/0 (success/fail)
Step 6
show vpdn history failure
Use this command to verify the failure of any VPDN groups.
Router# show vpdn history failure
% VPDN user failure table is empty
Step 7
debug pppoe redundancy
Use the debug pppoe redundancy command to display CCM events and messages for PPPoE sessions on HA systems. This command is generally used only by Cisco engineers for internal debugging of CCM processes.
Router# debug pppoe redundancy
Nov 22 17:21:11.327: PPPoE HA[0xBE000008] 9: Session ready to sync data
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: code = PADR, length = 58
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: code = SESSION ID, length = 2
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: code = SWITCH HDL, length = 4
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: code = SEGMENT HDL, length = 4
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: code = PHY SWIDB DESC, length = 20
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: code = VACCESS DESC, length = 28
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: Sync collection for ready events
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: code = PADR, length = 58
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: code = SESSION ID, length = 2
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: code = SWITCH HDL, length = 4
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: code = SEGMENT HDL, length = 4
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: code = PHY SWIDB DESC, length = 20
Nov 22 17:21:11.351: PPPoE HA[0xBE000008] 9: code = VACCESS DESC, length = 28
Configuration Examples for Cisco IOS Broadband High Availability Stateful Switchover
This section provides the following configuration example:
•
PPPoX Terminated into an RA-MPLS Network with ISSU: Example
PPPoX Terminated into an RA-MPLS Network with ISSU: Example
The following example shows how to configure PPPoX session subscriber redundancy policy for the Cisco IOS Broadband High Availability Stateful Switchover feature in an RA-MPLS network:
Router# show running-config
boot system bootflash:packages.conf !
aaa authentication ppp default local
no ip dhcp use vrf connected
no subscriber policy recording rules
The following lines show subscriber redundancy policy configuration:
subscriber redundancy dynamic limit cpu 90 delay 10
subscriber redundancy bulk limit cpu 90 delay 10
subscriber redundancy rate 4000 1
subscriber redundancy delay 10
mpls ldp graceful-restart
mpls ldp router-id Loopback100
no issu config-sync policy bulk prc
no issu config-sync policy bulk bem
username cisco password 0 cisco
buffers small permanent 15000
buffers middle permanent 12000
buffers large permanent 1000
ip address 172.16.1.1 255.255.255.255
ip address 172.31.0.1 255.255.255.255
interface FastEthernet0/0/0
ip address 192.168.2.26 255.255.255.0
interface GigabitEthernet1/0/0
interface GigabitEthernet1/0/0.1
interface GigabitEthernet1/0/0.2
interface GigabitEthernet1/0/1
interface GigabitEthernet1/0/1.1
interface GigabitEthernet1/0/1.2
interface GigabitEthernet1/0/2
interface GigabitEthernet1/0/2.1
interface GigabitEthernet1/0/2.2
interface GigabitEthernet1/0/3
interface GigabitEthernet1/0/3.1
interface GigabitEthernet1/0/3.2
interface GigabitEthernet7/0/3
interface GigabitEthernet8/0/0
mac-address 0011.0022.0033
ip address 10.1.1.2 255.255.255.0
interface GigabitEthernet8/1/0
ip address 10.1.1.1 255.255.255.0
interface Virtual-Template1
no logging event link-status
peer default ip address pool pool1
interface Virtual-Template2
no logging event link-status
peer default ip address pool pool2
interface Virtual-Template3
no logging event link-status
peer default ip address pool pool3
interface Virtual-Template4
no logging event link-status
peer default ip address pool pool4
interface Virtual-Template5
no logging event link-status
peer default ip address pool pool5
interface Virtual-Template6
no logging event link-status
peer default ip address pool pool6
interface Virtual-Template7
no logging event link-status
peer default ip address pool pool7
interface Virtual-Template8
no logging event link-status
peer default ip address pool pool8
network 10.1.1.0 0.0.0.255 area 0
network 10.0.0.0 0.0.0.255 area 0
bgp graceful-restart restart-time 120
bgp graceful-restart stalepath-time 360
neighbor 10.0.0.3 remote-as 1
neighbor 10.0.0.3 update-source Loopback100
neighbor 10.0.0.3 activate
neighbor 10.0.0.3 send-community extended
address-family ipv4 vrf vrf1
ip local pool pool2 10.1.1.1 10.1.16.160
ip local pool pool3 10.1.1.1 10.1.16.160
ip local pool pool4 10.1.1.1 10.1.16.160
ip local pool pool5 10.1.1.1 10.1.16.160
ip local pool pool6 10.1.1.1 10.1.16.160
ip local pool pool7 10.1.1.1 10.1.16.160
ip local pool pool8 10.1.1.1 10.1.16.160
arp 10.1.1.1 0020.0001.0001 ARPA
arp vrf vrf1 10.1.1.1 0020.0001.0001 ARPA !
exception crashinfo file bootflash:crash.log !
Additional References
The following sections provide references related to the Cisco IOS Broadband High Availability Stateful Switchover feature.
Related Documents
Standards
Standard
|
Title
|
No new or modified standards are supported by this feature, and support for existing RFCs has not been modified by this feature.
|
—
|
MIBs
MIB
|
MIBs Link
|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.
|
To locate and download MIBs for selected platforms, Cisco IOS XE releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://www.cisco.com/go/mibs
|
RFCs
RFC
|
Title
|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
|
—
|
Technical Assistance
Description
|
Link
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.
To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.
|
http://www.cisco.com/cisco/web/support/index.html
|
Feature Information for Cisco IOS Broadband High Availability Stateful Switchover
Table 1 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which 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
Table 1 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.
Table 1 Feature Information for Cisco IOS Broadband High Availability Stateful Switchover
Feature Name
|
Releases
|
Feature Information
|
ISSU—PPPoE; Cisco IOS Broadband High Availability In Service Software Upgrade for PPPoE
|
Cisco IOS XE Release 2.1,
Cisco IOS XE Release 2.5
|
This feature was introduced to Cisco ASR 1000 Series Routers.
This feature uses the ISSU—PPPoE feature to ensure continuous operations of broadband access protocols during software upgrades, downgrades, and service enhancements.
The following commands were introduced or modified: clear ppp subscriber statistics, clear pppoe statistics, debug pppoe redundancy, show ccm clients, show ccm sessions, show ppp subscriber statistics, show pppoe statistic, subscriber redundancy
|
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.
© 2006-2009 Cisco Systems, Inc. All rights reserved