Session recovery is not supported for the following functions:Important: Session Recovery can only be enabled through a feature use license key. If you have not previously purchased this enhanced feature, contact your sales representative for more information.
Session Recovery is also useful for Software Patch Upgrade activities. If session recovery feature is enabled during the software patch upgrading, it helps to permit preservation of existing sessions on the active PAC/PSC/PSC2 during the upgrade process. For more details refer to Software Patch Upgrade in the System Administration Guide.Important: Any partially connected calls (e.g., a session where HA authentication was pending but has not yet been acknowledged by the AAA server) are not recovered when a failure occurs.
• Task recovery mode: Wherein one or more session manager failures occur and are recovered without the need to use resources on a standby PAC/PSC/PSC2. In this mode, recovery is performed by using the mirrored “standby-mode” session manager task(s) running on active PACs/PSCs/PSC2s. The “standby-mode” task is renamed, made active, and is then populated using information from other tasks such as AAA manager. In case of Task failure, limited subscribers will be affected and will suffer outage only until the task starts back up.
• Full PAC/PSC/PSC2 recovery mode: Used when a PAC/PSC/PSC2 hardware failure occurs, or when a planned PAC/PSC/PSC2 migration fails. In this mode, the standby PAC/PSC/PSC2 is made active and the “standby-mode” session manager and AAA manager tasks on the newly activated PAC/PSC/PSC2 perform session recovery.Important: After a session recovery operation, some statistics, such as those collected and maintained on a per manager basis (AAA Manager, Session Manager, etc.) are in general not recovered, only accounting/billing related information is checkpointed/recovered.
Important: A minimum of four PACs/PSCs/PSC2s (three active and one standby) per individual chassis is required to use this feature.
Important: Session recovery can only be enabled through a feature use license key. If you have not previously purchased this enhanced feature, contact your sales representative for more information.
Important: If the Session Recovery feature appears as Disabled, then you cannot enable this feature until a new license key is installed in the system.
Step 3 Save your configuration as described in the Saving Your Configuration section in the System Administration Guide.
Step 4Important: If the Session Recovery feature for HA appears as Disabled, then you cannot enable this feature until a new license key is installed in the system.
Step 3 Save your configuration as described in Saving Your Configuration.
Step 5 After the system has been restarted, you should verify the preparedness of the system to support this feature as described in the Viewing Session Recovery Status section.Important: More advanced users may opt to simply insert the require session recovery command syntax into an existing configuration file using a text editor or other means, and then applying the configuration file manually. Caution should be taken when doing this to ensure that this command is placed among the first few lines of any existing configuration file to ensure that it appears before the creation of any non-local context.
Important: If this command is issued on an in-service system, then the system must be restarted by issuing the reload command.
show session recovery status [verbose][local]host_name# show session recovery status[local]host_name# show session recovery status[local]host_name# show session recovery status verbose
• Original - indicating that this is the original session information, containing all event states and time information.
• Recreated Session - indicating that this session was reconstructed during a session recovery operation.
callid id Displays subscriber information for the call specified by id. The call ID must be specified as an 8-byte hexadecimal number. msid id Displays information for the mobile user identified by id. id must be from 7 to 16 digits specified as an IMSI, MIN, or RMI. Wildcard characters $ and * are allowed. The * wildcard matches multiple characters and the $ wildcard matches a single character. If you do not want the wildcard characters interpreted as a wildcard enclose them in single quotes ( ‘ ). For example; ‘$’. username name Displays information for connections for the subscriber identified by name. The user must have ben previously configured. name must be a sequence of characters and/or wildcard characters ('$' and '*') from 1 to 127 characters in length. The * wildcard matches multiple characters and the $ wildcard matches a single character. If you do not want the wildcard characters interpreted as wildcard enclose them in single quotes ( ‘). For example; ‘$’.
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |