Cisco Cisco Packet Data Gateway (PDG)
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
MME Changes in Release 17
▀ MME Enhancements for 17.1
▄ Release Change Reference, StarOS Release 17
288
recovered-emm-msgtx-tau-illegal-ue
recovered-emm-msgtx-tau-illegal-me
recovered-emm-msgtx-tau-eps-not-allowed
recovered-emm-msgtx-tau-decode-failure
recovered-emm-msgtx-tau-no-bearer-active
recovered-emm-msgtx-tau-ue-identity-unk
recovered-emm-msgtx-tau-imei-not-accept
recovered-emm-msgtx-tau-roaming-restrict-ta
recovered-emm-msgtx-tau-plmn-not-allow
recovered-emm-msgtx-tau-ta-not-allow
recovered-in-tau-ho-2g3gto4g-s3-success
recovered-emm-msgtx-attach-accept-retx
recovered-emm-msgtx-tau-accept
recovered-emm-msgtx-no-suitable-cell-ta
recovered-emm-msgtx-tau-reject
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. When B-type XML files are used, multiple trace recording session elements will be
encoded in a single XML file. It should be noted that different trace recording sessions may be associated with different
TCEs, according to the TCE IP address specified during activation. As expected, 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. When B-type XML files are used, multiple trace recording session elements will be
encoded in a single XML file. It should be noted that different trace recording sessions may be associated with different
TCEs, according to the TCE IP address specified during activation. As expected, 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 optional
file-type
keyword enables the operator to determine which type of XML file is generated by the
session trace:
configure