Cisco Cisco Packet Data Gateway (PDG)
SAEGW Changes in Release 17
SAEGW Enhancements for 17.1 ▀
Release Change Reference, StarOS Release 17 ▄
425
To address the issues caused when the sesstrc task allocates memory over the allotted limit, under a random subscriber
session trace load tests on P-GW/S-GW, support for B-type XML files is introduced in addition to the A-type files
already supported.
session trace load tests on P-GW/S-GW, support for B-type XML files is introduced in addition to the A-type files
already supported.
Previous Behavior: The file type was A-type XML file and the type could not be changed.
New Behavior: The CLI has been modified (see Command Changes section) to allow the operator to select the file
type generated by session trace. It should be noted that different trace recording sessions may be associated with
different TCEs, according to the TCE IP address specified during activation. Each Type-B XML file will contain
traceRecSession elements that pertain only to the same target TCE. There will be different XML Type-B files created
for different TCEs and they will be placed in different tce_x directories for transmission to the target TCEs.
type generated by session trace. It should be noted that different trace recording sessions may be associated with
different TCEs, according to the TCE IP address specified during activation. Each Type-B XML file will contain
traceRecSession elements that pertain only to the same target TCE. There will be different XML Type-B files created
for different TCEs and they will be placed in different tce_x directories for transmission to the target TCEs.
Command Changes
session trace network-element
The new
file-type
keyword enables the operator to determine which type of XML file is generated by the session
trace:
configure
session trace network-element { all | enb | ggsn | hnbgw | mme | pgw | sgw } [ file-
type { a-type | b-type } ] [ collection-timer | tce-mode ]
type { a-type | b-type } ] [ collection-timer | tce-mode ]
no session trace network-element { all | enb | ggsn | hnbgw | mme | pgw | sgw }
end
Notes:
Default file-type is a-type.
To keep the syntax simple, we recommend that you enter the
file-type
keyword prior to adding either of the
other optional keywords to the command.
To modify the session trace network-element configuration, you must first enter the
no session trace
network-element
form of the command to remove the session trace configuration.
CSCur43509 - 17.1: MLF-3298: PCEF is not triggering 29 as APN-AMBR mod
failure in CCR
Feature Changes
APN AMBR Modification Failure Event Trigger Support for all Usage Report Trigger Values
The fix implemented for CSCur43509 has resulted in a behavior change.
Previous Behavior: When diameter map usage-report is 26 then APN AMBR modification failure event trigger was
not supported.
not supported.
New Behavior: APN AMBR modification failure event trigger is supported for all usage report trigger values
(26,33,29).
(26,33,29).
Customer Impact: This affects all Gx/Gxx products.