Cisco Cisco Packet Data Gateway (PDG)
[ no ] diameter authentication strip-leading-digit { user-name }
end
end
Notes:
• strip-leading-digit: Strips off leading digit from User-Name AVP of non-authentication procedures.
By default, this feature is disabled.
• This CLI command will not take effect for aaa-custom17 and aaa-custom19 dictionaries.
• This CLI is not applicable for response messages (RAA/ASA) sent by chassis.
Performance Indicator Changes
show aaa group name
The following field is added to the output of this show command to indicate the configuration status of this
feature.
feature.
• Strip-leading-digit user-name
Default Setting for Failure Handling Action for aaa-custom2 Dictionary
CSCuv74175 - Restore default CCFH behavior of 5xxx result codes in SWm interface
Applicable Products: ePDG, HSGW
Feature Changes
Previous Behavior: Diameter messages in SWm interface were retried when 5xxx result code is received
and no Credit Contol Failure Handling (CCFH) action is configured. That is, the default FH action was
"retry-and-terminate" for 5xxx result codes in aaa-custom2 dictionary.
and no Credit Contol Failure Handling (CCFH) action is configured. That is, the default FH action was
"retry-and-terminate" for 5xxx result codes in aaa-custom2 dictionary.
New Behavior: In the case of aaa-custom2 dictionary, the default CCFH action is configured as "terminate"
for 5xxx result codes.
for 5xxx result codes.
Diameter Overload Control on P-GW and ePDG
CSCut42292 - Support for vendor specific cause code to handle Network Overload
Applicable Products: ePDG, P-GW
Related CDETS ID: CSCut88698
Feature Changes
This feature is implemented to support Overload Control on Diameter interfaces such as Gx, S6b and SWm
and also to prevent network overload and outages. Whenever there is an overload condition at the Diameter
Servers or DRA and request times out, the clients (ePDG/P-GW) are typically unaware of the overload
condition and attempt to send the message on an alternate connection with the Diameter server causing some
more traffic in the network. In order to handle this overload condition effectively, a new vendor-specific
and also to prevent network overload and outages. Whenever there is an overload condition at the Diameter
Servers or DRA and request times out, the clients (ePDG/P-GW) are typically unaware of the overload
condition and attempt to send the message on an alternate connection with the Diameter server causing some
more traffic in the network. In order to handle this overload condition effectively, a new vendor-specific
Release Change Reference, StarOS Release 19
30
AAA Changes in Release 19
Default Setting for Failure Handling Action for aaa-custom2 Dictionary