Cisco IOS XE Broadband Access Aggregation and DSL Configuration Guide, Release 2 - Broadband High Availability Stateful Switchover [Cisco IOS XE Software]

Table Of Contents

Broadband High Availability Stateful Switchover

Finding Feature Information

Contents

Prerequisites for Broadband High Availability Stateful Switchover

Restrictions for Broadband High Availability Stateful Switchover

Information About Broadband High Availability Stateful Switchover

Feature Design of Broadband High Availability Stateful Switchover

Supported Broadband Aggregation Protocols

SSO L2TP

SSO PPPoE

SSO RA-MLPS VPN

Benefits of Broadband High Availability Stateful Switchover

How to Configure Broadband High Availability Stateful Switchover

Configuring Subscriber Redundancy Policy for Broadband HA Stateful Switchover

Verifying and Troubleshooting Subscriber Redundancy Policy for Broadband HA Stateful Switchover

Configuration Examples for Broadband High Availability Stateful Switchover

PPPoX Terminated into an RA-MPLS Network with SSO: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Feature Information for Broadband High Availability Stateful Switchover

Broadband High Availability Stateful Switchover

First Published: December 4, 2006

Last Updated: November 25, 2009

The Broadband High Availability Stateful Switchover feature uses the SSO—PPPoE feature to provide the capability for dual Route Processor systems to support stateful switchover of Point-to-Point Protocol over various media (PPPoX) sessions and allow applications and features to maintain state while system control and routing protocol execution is transferred between an active and a standby processor.

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 Broadband High Availability Stateful Switchover.

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 Broadband High Availability Stateful Switchover

•Restrictions for Broadband High Availability Stateful Switchover

•Information About Broadband High Availability Stateful Switchover

•How to Configure Broadband High Availability Stateful Switchover

•Configuration Examples for Broadband High Availability Stateful Switchover

•Additional References

•Feature Information for Broadband High Availability Stateful Switchover

Prerequisites for 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 Broadband High Availability Stateful Switchover

SSO is supported only on High Availability (HA) network devices.

Information About Broadband High Availability Stateful Switchover

To configure the Broadband High Availability Stateful Switchover feature, you should understand the following concepts:

•Feature Design of Broadband High Availability Stateful Switchover

•Benefits of Broadband High Availability Stateful Switchover

Feature Design of Broadband High Availability Stateful Switchover

Prior to the implementation of the Broadband High Availability Stateful Switchover feature, unplanned control plane and dataplane failures resulted in service outages and network downtime for PPPoX sessions. Cisco High Availability features, including SSO, enable network protection by providing fast recovery from such failures. The Broadband High Availability Stateful Switchover feature eliminates a source of outages by providing for stateful switchover to a standby processor while continuing to forward traffic. SSO protects from hardware or software faults on an active Route Processor by synchronizing protocol and state information for supported features with a standby Route Processor, helping to ensure no interruption of sessions or connections if a switchover occurs.

The SSO feature takes advantage of route-processor redundancy by establishing one of the Route Processors as the active processor, designating the other Route Processor as the standby processor, and then synchronizing critical state information between them. Following an initial (bulk) synchronization between the two processors, SSO dynamically maintains Route Processor state information between them. A switchover from the active to the standby processor occurs when the active Route Processor fails, when it is removed from the networking device, or when it is manually taken down for maintenance. The standby Route Processor then takes control and becomes the active Route Processor, preserving the sessions and connections for the supported features. At this time, packet forwarding continues while route convergence is completed on the newly active Route Processor. A critical component of SSO and Cisco HA technology is the cluster control manager (CCM) that manages session recreation on the standby processor. The Broadband High Availability Stateful Switchover feature allows you to configure subscriber redundancy policies that tune the synchronization process. For more information see "Configuring Subscriber Redundancy Policy for Broadband HA Stateful Switchover" section.

The Broadband High Availability Stateful Switchover feature works with the Cisco NSF and SSO HA features, to maintain PPPoX sessions. NSF continues forwarding network traffic and application state information so that user session information is maintained after a switchover.

For information about High Availability and stateful switchover, see the "High Availability Overview" chapter in the Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide.

Supported Broadband Aggregation Protocols

The Broadband High Availability Stateful Switchover feature set supports the broadband aggregation protocols described in the following:

•SSO L2TP

•SSO PPPoE

•SSO RA-MLPS VPN

SSO 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.

SSO PPPoE

The Broadband High Availability Stateful Switchover feature delivers stateful switchover capability for PPP over Ethernet (PPPoE) subscriber access sessions, including PPPoE, PPPoEoVLAN, and PPPoEoQinQ.

SSO RA-MLPS VPN

The Broadband High Availability Stateful Switchover feature delivers stateful switchover capability for PPPoX terminated into remote access (RA)-MPLS VPN or PPPoX into MPLS VPN sessions during processor switchover.

Figure 1 shows a typical broadband aggregation HA deployment with SSO functionality.

Figure 1 Broadband Aggregation High Availability Deployment

Benefits of Broadband High Availability Stateful Switchover

•Reduces operating costs associated with outages.

•Delivers higher service levels to subscribers.

•Improves network availability.

•Promotes continuous connectivity, lower packet loss, and consistent path flow through nodes providing specific network services.

•Mitigates service disruptions, reduces downtime costs, and increases operational efficiency.

How to Configure Broadband High Availability Stateful Switchover

This section contains the following tasks:

•Configuring Subscriber Redundancy Policy for Broadband HA Stateful Switchover

•Verifying and Troubleshooting Subscriber Redundancy Policy for Broadband HA Stateful Switchover

Configuring Subscriber Redundancy Policy for Broadband HA Stateful Switchover

Perform this task to configure subscriber redundancy policy for HA SSO capability for broadband subscriber sessions.

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 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 Stateful Switchover

To view the configuration, use the show running-config command. Sample output is available at"Configuration Examples for 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
Router# show ccm clients
CCM bundles sent since peer up:
Sent Queued for flow control 
Sync Session 16000 0 
Update Session 0 0 
Active Bulk Sync End 1 0 
Session Down 0 0 
ISSU client msgs 346 0 
Dynamic Session Sync 0 0 
Unknown msgs 0 0 
Client events sent since peer up: 
PPP 144000 
PPPoE 96002 
VPDN FSP 0 
AAA 64000 
PPP SIP 0 
LTERM 16000 
AC 0 
L2TP CC 0 
SSS FM 16000 
VPDN LNS 0 
Standby Route Processor
Router# show ccm clients 
CCM bundles rcvd since last boot: 
Sync Session 16000 
Update Session 0 
Active Bulk Sync End 1 
Session Down 0 
ISSU client msgs 173 
Dynamic Session Sync 0 
Unknown msgs 0 
Client events extracted since last boot: 
PPP 144000 
PPPoE 96002 
VPDN FSP 0 
AAA 64000 
PPP SIP 0 
LTERM 16000 
AC 0 
L2TP CC 0 
SSS FM 16000 
VPDN LNS 0 
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 
------------ -------- --------- ----------- --------- -------- 
Rate 00:00:01 - 64 - - 
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 
------------ -------- --------- ----------- --------- --------
Rate 00:00:01 - 0 - - 
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
Encap                          5             5
DeEncap                        0             0
CstateUp                       7             7
CstateDown                     4             4
FastStart                      0             0
LocalTerm                      7             7
LocalTermVP                    0             0
MoreKeys                       7             7
Forwarding                     0             0
Forwarded                      0             0
SSSDisc                        0             0
SSMDisc                        0             0
PPPDisc                        0             0
PPPBindResp                    7             7
PPPReneg                       3             3
RestartTimeout                 5             5
PPP Subscriber Statistics      TOTAL         SINCE CLEARED
IDB CSTATE UP                  4             4
IDB CSTATE DOWN                8             8
APS UP                         0             0
APS UP IGNORE                  0             0
APS DOWN                       0             0
READY FOR SYNC                 8             8
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
------------------------------ ------------- -------------
INVALID                        0             0
PRE-SERVICE FOUND              0             0
PRE-SERVICE NONE               0             0
SSS CONNECT LOCAL              0             0
SSS FORWARDING                 0             0
SSS FORWARDED                  0             0
SSS MORE KEYS                  0             0
SSS DISCONNECT                 0             0
CONFIG UPDATE                  0             0
STATIC BIND RESPONSE           0             0
PPP FORWARDING                 0             0
PPP FORWARDED                  0             0
PPP DISCONNECT                 0             0
PPP RENEGOTIATION              0             0
SSM PROVISIONED                0             0
SSM UPDATED                    0             0
SSM DISCONNECT                 0             0
PPPoE Statistics               TOTAL         SINCE CLEARED
------------------------------ ------------- -------------
SSS Request                    0             0
SSS Response Stale             0             0
SSS Disconnect                 0             0
PPPoE Handles Allocated        0             0
PPPoE Handles Freed            0             0
Dynamic Bind Request           0             0
Static Bind Request            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 
L2TP HA Status: 
Checkpoint Messaging on: FALSE 
Standby RP is up: TRUE 
Recv'd Message Count: 0 
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 Broadband High Availability Stateful Switchover

This section provides the following configuration example:

•PPPoX Terminated into an RA-MPLS Network with SSO: Example

PPPoX Terminated into an RA-MPLS Network with SSO: Example

The following example shows how to configure the Broadband High Availability Stateful Switchover feature in an RA-MPLS network:
Router# show running-config
hostname Router
!
boot-start-marker
boot system bootflash:packages.conf !
enable password cisco
!
aaa new-model
!
!
aaa authentication ppp default local
!
!
!
aaa session-id common
ppp hold-queue 80000
ip subnet-zero
no ip gratuitous-arps
no ip domain lookup
ip vrf vrf1
  rd 1:1
  route-target export 1:1
  route-target import 1:1
!
no ip dhcp use vrf connected
!
!
!
!
no subscriber policy recording rules
The following lines show the 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 
no mpls traffic-eng 
mpls ldp graceful-restart 
mpls ldp router-id Loopback100 
no virtual-template snmp 
no issu config-sync policy bulk prc 
no issu config-sync policy bulk bem 
!
redundancy mode sso
username cisco password 0 cisco
!
bba-group pppoe grp1
  virtual-template 1
!
bba-group pppoe grp2
  virtual-template 2
!
bba-group pppoe grp3
  virtual-template 3
!
bba-group pppoe grp4
  virtual-template 4
!
bba-group pppoe grp5
  virtual-template 5
!
bba-group pppoe grp7
  virtual-template 7
!
bba-group pppoe grp8
  virtual-template 8
!
bba-group pppoe grp6
  virtual-template 6
!
!
interface Loopback0
  ip vrf forwarding vrf1
  ip address 10.1.1.1 255.255.255.255
!
interface Loopback100
  ip address 192.168.0.1 255.255.255.255
!
interface FastEthernet0/0/0
  ip address 192.168.2.26 255.255.255.0
  speed 100
  full-duplex
!
interface GigabitEthernet1/0/0 
no ip address 
load-interval 30 
! 
interface GigabitEthernet1/0/0.1 
encapsulation dot1Q 2 
pppoe enable group grp1 
! 
! 
interface GigabitEthernet1/0/0.2 
encapsulation dot1Q 2 
pppoe enable group grp2 
! 
! 
interface GigabitEthernet1/0/1 
no ip address 
! 
interface GigabitEthernet1/0/1.1 
encapsulation dot1Q 2 
pppoe enable group grp3
! 
! 
interface GigabitEthernet1/0/1.2 
encapsulation dot1Q 2 
pppoe enable group grp4 
! 
! 
interface GigabitEthernet1/0/2 
no ip address 
! 
interface GigabitEthernet1/0/2.1 
encapsulation dot1Q 2 
pppoe enable group grp5 
! 
! 
interface GigabitEthernet1/0/2.2 
encapsulation dot1Q 2 
pppoe enable group grp6 
! 
! 
interface GigabitEthernet1/0/3 
no ip address 
! 
interface GigabitEthernet1/0/3.1 
encapsulation dot1Q 2 
pppoe enable group grp7
! 
! 
interface GigabitEthernet1/0/3.2 
encapsulation dot1Q 2 
pppoe enable group grp8 
! 
interface GigabitEthernet7/0/3 
no ip address 
!
interface GigabitEthernet8/0/0
  mac-address 0011.0022.0033
  ip vrf forwarding vrf1
  ip address 10.1.1.2 255.255.255.0
  negotiation auto
!
interface GigabitEthernet8/1/0
  ip address 10.1.1.1 255.255.255.0
  negotiation auto
  mpls ip
!
interface Virtual-Template1
  ip vrf forwarding vrf1
  ip unnumbered Loopback0
  no logging event link-status
  peer default ip address pool pool1
  no snmp trap link-status
  keepalive 30
  ppp authentication pap
!
interface Virtual-Template2
  ip vrf forwarding vrf1
  ip unnumbered Loopback0
  no logging event link-status
  peer default ip address pool pool2
  no snmp trap link-status
  keepalive 30
  ppp authentication pap
!
interface Virtual-Template3
  ip vrf forwarding vrf1
  ip unnumbered Loopback0
  no logging event link-status
  peer default ip address pool pool3
  no snmp trap link-status
  keepalive 30
  ppp authentication pap
!
interface Virtual-Template4
  ip vrf forwarding vrf1
  ip unnumbered Loopback0
  no logging event link-status
  peer default ip address pool pool4
  no snmp trap link-status
  keepalive 30
  ppp authentication pap
!
interface Virtual-Template5
  ip vrf forwarding vrf1
  ip unnumbered Loopback0
  no logging event link-status
  peer default ip address pool pool5
  no snmp trap link-status
  keepalive 30
  ppp authentication pap
!
interface Virtual-Template6
  ip vrf forwarding vrf1
  ip unnumbered Loopback0
  no logging event link-status
  peer default ip address pool pool6
  no snmp trap link-status
  keepalive 30
  ppp authentication pap
!
interface Virtual-Template7
  ip vrf forwarding vrf1
  ip unnumbered Loopback0
  no logging event link-status
  peer default ip address pool pool7
  no snmp trap link-status
  keepalive 30
  ppp authentication pap
!
interface Virtual-Template8
  ip vrf forwarding vrf1
  ip unnumbered Loopback0
  no logging event link-status
  peer default ip address pool pool8
  no snmp trap link-status
  keepalive 30
  ppp authentication pap
!
router ospf 1
  log-adjacency-changes
  nsf
  network 10.1.1.0 0.0.0.255 area 0
  network 224.0.0.0 0.0.0.255 area 0
!
router bgp 1
  no synchronization
  bgp log-neighbor-changes
  bgp graceful-restart restart-time 120
  bgp graceful-restart stalepath-time 360
  bgp graceful-restart
  neighbor 224.0.0.3 remote-as 1
  neighbor 224.0.0.3 update-source Loopback100
  no auto-summary
  !
  address-family vpnv4
  neighbor 224.0.0.3 activate
  neighbor 224.0.0.3 send-community extended
  exit-address-family
  !
  address-family ipv4 vrf vrf1
  redistribute connected
  redistribute static
  no auto-summary
  no synchronization
  exit-address-family
!
ip local pool pool2 10.1.1.1 10.1.16.160 
ip local pool pool3 10.13.1.1 10.13.16.160 
ip local pool pool4 10.14.1.1 10.14.16.160 
ip local pool pool5 10.15.1.1 10.15.16.160 
ip local pool pool6 10.16.1.1 10.16.16.160 
ip local pool pool7 10.17.1.1 10.17.16.160 
ip local pool pool8 10.18.1.1 10.18.16.160 
ip classless !
!
no ip http server
!
!
arp 10.20.1.1 0020.0001.0001 ARPA
arp vrf vrf1 10.20.1.1 0020.0001.0001 ARPA !
!
!
line con 0
line aux 0
line vty 0 4
  password cisco
!
exception crashinfo file bootflash:crash.log !
end
Additional References

The following sections provide references related to the Broadband High Availability Stateful Switchover feature.

Related Documents

Related Topic

Document Title

High Availability

"High Availability Overview" chapter in the Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

Performing an ISSU

The following chapters in the Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide:

•"Cisco IOS XE Software Package Compatibility for ISSU"

•"In Service Software Upgrade (ISSU)"

Broadband ISSU

Broadband High Availability In Service Software Upgrade

Stateful switchover

Stateful Switchover

Cisco nonstop forwarding

Cisco Nonstop Forwarding

Layer 2 Tunnel Protocol

Layer 2 Tunnel Protocol Technology Brief

Additional information about commands used in this document

•Cisco IOS Broadband Access Aggregation and DSL Command Reference

•Cisco IOS Master Command List, All Releases

Standards

Standard

Title

No new or modified standards are supported by this feature, and support for existing standards 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 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 the Broadband High Availability Stateful Switchover Feature

Feature Name

Releases

Feature Information

SSO—PPPoE

Cisco IOS XE Release 2.1;

Cisco IOS XE Release 2.5

In Cisco IOS XE Release 2.1, this feature was implemented on ASR 1000 routers.

This feature uses the SSO—PPPoE feature to provide the capability for dual Route Processor systems to support stateful switchover of PPPoX sessions and allow applications and features to maintain state while system control and routing protocol execution is transferred between an active and a standby processor.

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