Release Note для Cisco Cisco Packet Data Gateway (PDG)
SGSN Changes in Release 15.0
SGSN Enhancements for September 30, 2013 ▀
Cisco ASR 5x00 Release Change Reference ▄
513
New Behavior: Using the
no peer-server id instance
command now removes both the peer server and all
routes associated with this peer server from the configuration and operation. A warning message will be displayed prior
to removing the peer server and routes.
to removing the peer server and routes.
‘Prohibit payload compression’ Bit Removed From SGSN Initiated UPCQ
Previous Behavior: It is observed that in some scenarios the SGSN was sending “Prohibit payload compression” bit
present in Common flags of UPCQ towards the GGSN.
present in Common flags of UPCQ towards the GGSN.
New Behavior: The “Prohibit payload compression” bit is defined only for GGSN initiated messages like CPCR,
UPCR from GGSN and UPCQ from GGSN. The SGSN need not send the “Prohibit payload compression” bit. The
“Prohibit payload compression” bit will no longer be present in SGSN initiated UPCQ.
UPCR from GGSN and UPCQ from GGSN. The SGSN need not send the “Prohibit payload compression” bit. The
“Prohibit payload compression” bit will no longer be present in SGSN initiated UPCQ.
Removal of Access Restriction Data Modified
Previous Behavior: Removal of
access-restriction-data
from a call-control-profile provides the option to
remove either
eutran-not-allowed
or
failure-code
. Removal of
failure-code
from
access-restriction-
data
pops up the following warning:
Warning: failure-code keyword is deprecated while removing ard configuration. Entire ard
configuration is removed
configuration is removed
Prior to introduction of this enhancement, removal of
failure-code
was the only option. So entire ARD configuration
was warned to be removed.
New Behavior: Removal of
access-restriction-data
from call-control-profile now provides option to remove
both
eutran-not-allowed
and
failure code
. To remove both
eutran-not-allowed
and
failure code
execute the following command:
remove access-restriction-data eutran-not-allowed failure-code <cr>
When the user wants to remove
failure-code
alone, the warning which was displayed in the earlier implementation
is no longer displayed.
Removal Of Record-Module
Previous Behavior: The “record-module” can be deleted even when shared configuration policy is configured. This
internally affects the policy for all other active modules.
internally affects the policy for all other active modules.
New Behavior: The “record-module” cannot be deleted if shared policies like use-hard disk, remove-file-after-transfer,
file-transfer and so on are configured for the module. The shared policies have to be manually removed before deleting
the module. The module can be deleted anytime if no shared policies are configured.
file-transfer and so on are configured for the module. The shared policies have to be manually removed before deleting
the module. The module can be deleted anytime if no shared policies are configured.
Report Subscriber Summary per GTPU Address
Previous Behavior: It was not possible to report subscriber GTPU sessions or statistics per local-address.
New Behavior: With changes to the
show gtpu
command, it is now possible to display active subscriber sessions on
each local GTPU address categorized by GTPU service and to display GTPU statistics per local IP address
Routing Context in M3ua Data Messages
Previous Behavior: Routing context was not inserted in m3ua-data messages.
New Behavior: A new keyword has been introduced in the
routing-context
command. This keyword controls the
insertion of routing context in m3ua-data messages.