Cisco Cisco ASR 5000
Backup and Recovery of Key KPI Statistics
How It Works ▀
SGSN Administration Guide, StarOS Release 18 ▄
How It Works
A key set of counters, used in KPI computation will be backed up for recovery if a SessMgr task restarts. The counters
that will be backed up are determined by the KPIs typically used in several operator networks.
that will be backed up are determined by the KPIs typically used in several operator networks.
The backup of counters is enabled or disabled via configuration. The configuration specifies the product (currently only
supported by the SGSN) for which counters will be backed up and also a time interval for the back up of the counters.
supported by the SGSN) for which counters will be backed up and also a time interval for the back up of the counters.
The backed up counters can be identified via CLI generated displays or via display of the four SGSN-specific backup
statistics schemas: iups-bk, gprs-bk, map-bk, and sgtp-bk. The operator can use these schemas to compute the KPI as
statistics will have the recovered counters. During the display and the backup processes, both the normal counters and
backed-up counters are cumulatively displayed or backed up.
statistics schemas: iups-bk, gprs-bk, map-bk, and sgtp-bk. The operator can use these schemas to compute the KPI as
statistics will have the recovered counters. During the display and the backup processes, both the normal counters and
backed-up counters are cumulatively displayed or backed up.
iups-bk schema - This schema is used for 3G GMM-SM counters which are backed up. The counters in this
schema are pegged per IuPS service. Each line of output is per IuPS service. Additionally, there will be one set
of consolidated counters for all IuPS services which is displayed with the SGSN service name.
of consolidated counters for all IuPS services which is displayed with the SGSN service name.
gprs-bk schema - This schema is used for 2G GMM-SM counters which are backed up. The counters in this
schema are pegged per GPRS service. Each line of output is per GPRS service. Additionally, there will be one
set of consolidated counters for all GPRS services which is displayed with the SGSN service name.
set of consolidated counters for all GPRS services which is displayed with the SGSN service name.
map-bk schema - This schema is used for MAP and SMS counters which are backed up. The counters in this
schema are pegged per MAP service. Each line of output is per MAP service.
sgtp-bk schema - This schema is used for GTPU counters which are backed up. The counters in this schema are
pegged per IuPS and SGTP service, one per line. Additionally, there will be one line of output which represents
the counters consolidated for all IuPS and SGTP services.
the counters consolidated for all IuPS and SGTP services.
Architecture
When this feature is enabled (see Configuring Backup Statistics Feature below), the SGSN only backs up the counters
maintained at the SessMgr. Counters maintained by other managers, such as the LinkMgr or SGTPMgr, are not backed
up. The recovery function does not need to be configured or ‘started’ as it occurs automatically as needed when the
feature is enabled.
maintained at the SessMgr. Counters maintained by other managers, such as the LinkMgr or SGTPMgr, are not backed
up. The recovery function does not need to be configured or ‘started’ as it occurs automatically as needed when the
feature is enabled.
The counters are backed up to the AAAMgr that is paired with the SessMgr. They are recovered from the AAAMgr
after a SessMgr task is killed. This feature makes use of the session recovery framework to backup and retrieve the
counters.
after a SessMgr task is killed. This feature makes use of the session recovery framework to backup and retrieve the
counters.
The following diagram depicts how backed-up statistics are maintained separately at the SessMgr and how the
cumulative values are backed up and recovered from the AAAMgr after SessMgr task recovery completes.
cumulative values are backed up and recovered from the AAAMgr after SessMgr task recovery completes.