Cisco Cisco Packet Data Gateway (PDG) Nota Di Rilascio
SGSN Changes in Release 15.0
▀ SGSN Enhancements for September 30, 2013
▄ Cisco ASR 5x00 Release Change Reference
506
suspended PDPs or the UE directly sends a Routing Area Update Request (RAU) in 2G which will be treated as an
implicit resume.
implicit resume.
The ability for a GPRS user to access circuit-switched services depends on the subscription held, the network
capabilities, and the MS capabilities.
capabilities, and the MS capabilities.
For more information on this feature, refer to the S4-SGSN Suspend-Resume Feature chapter in the ASR 5000 SGSN
Administration Guide.
Administration Guide.
Support for Supplementary Services
As part of the Location Services (LCS) enhancements, support has been implement for Supplementary Service
procedures as provided in 3GPP TS 24.030, including:
procedures as provided in 3GPP TS 24.030, including:
LCS Location Notification Invoke
LCS Location Notification Return Result
LCS Area Event Invoke
LCS Area Event Invoke Ack
LCS Area Event Report
LCS Area Event Cancel
LCS Area Event Cancel Ack
LCS Periodic Location Invoke
LCS Periodic Location Invoke Ack
LCS Location Update
LCS Location Update Ack
LCS Periodic Location Cancel
LCS Periodic Location Cancel Ack
LCS MO-LR Invoke
LCS MO-LR Return Result
Synchronization of Crash Events and Minicores Between Management Cards
The crashlog is unique to each of the management cards, so if a crash occurs when card the “8” is active it will be
logged on card “8”. A subsequent switchover would no longer display the crash in the log. To retrieve this crash, a
switch back over to card “8” has to be done. The crash event log and dumps are unique to active and standby
management cards, so if a crash occurs on an active card then the crash event log and related dumps will be stored on an
active card only. This crash information is not available on the standby card. Whenever the cards switchover due to a
crash in the active card, and crash information is no longer displayed on the card which takes over. Crash information
can be retrieved only from the current active card. To retrieve the crash list of the other card a switchover is required
again. To avoid this switchover and to obtain the crash information from the standby card, synchronization between two
management cards and maintaining latest crash information is required.
logged on card “8”. A subsequent switchover would no longer display the crash in the log. To retrieve this crash, a
switch back over to card “8” has to be done. The crash event log and dumps are unique to active and standby
management cards, so if a crash occurs on an active card then the crash event log and related dumps will be stored on an
active card only. This crash information is not available on the standby card. Whenever the cards switchover due to a
crash in the active card, and crash information is no longer displayed on the card which takes over. Crash information
can be retrieved only from the current active card. To retrieve the crash list of the other card a switchover is required
again. To avoid this switchover and to obtain the crash information from the standby card, synchronization between two
management cards and maintaining latest crash information is required.
The arriving crash event will be sent over to the standby SMC/MMIO and saved in the standby’s crashlog file in the
similar manner. Minicore, NPU or kernel dumps on flash of active SMC/MMIO needs to be synchronized to standby
SMC/MMIO using the ‘rsync’ command. When a crashlog entry or the whole list is deleted through the CLI command,
it should be erased on both active and standby SMCs/MMIOs. There is no impact on memory. All the crash related
similar manner. Minicore, NPU or kernel dumps on flash of active SMC/MMIO needs to be synchronized to standby
SMC/MMIO using the ‘rsync’ command. When a crashlog entry or the whole list is deleted through the CLI command,
it should be erased on both active and standby SMCs/MMIOs. There is no impact on memory. All the crash related