Cisco Cisco Packet Data Interworking Function (PDIF)
S-GW Changes in Release 17
S-GW Enhancements for 17.1 ▀
Release Change Reference, StarOS Release 17 ▄
573
sgw-paging-profile three-tupple
ipv4 address 1.1.1.1 port 30 protocol tcp paging-identifier 1
ipv4 address 1.1.1.2 port 30 protocol tcp paging-identifier 2
end
associate sgw-paging-profile three-tupple
The new
associate sgw-paging-profile three-tupple
command has been added in APN Profile
Configuration mode to allow the association of an SGW Paging Profile with an APN profile on the S-GW.
configure
apn-profile apn_profile_name
associate sgw-paging-profile three-tupple
remove associate sgw-paging-profile
end
Notes:
remove
disables the SGW Paging Profile association.
CSCup59406 - sesstrc task in over state during longevity/aggravator run
Feature Changes
Configuring Session Trace File Type
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: