Cisco Cisco Packet Data Interworking Function (PDIF)
AAA Changes in Release 17
AAA Enhancements for 17.0 ▀
Release Change Reference, StarOS Release 17 ▄
65
The AAA proxy allocates a lot of memory on a per GTPP group basis statically regardless of the usage. So if the
number of GTPP groups is reduced to around 6 then the issue with the AAA proxy going to warn memory state will not
be observed.
number of GTPP groups is reduced to around 6 then the issue with the AAA proxy going to warn memory state will not
be observed.
Previous Behavior: Up to a maximum of 32 GTPP groups were allowed to be configured.
New Behavior: Now there is a limit of configuring only up to six GTPP groups. In case customers are using more than
six GTPP groups, the AAAProxy will use more memory than is supported and will be in “warn” state of memory.
six GTPP groups, the AAAProxy will use more memory than is supported and will be in “warn” state of memory.
Customer Impact: On an analysis, it is determined that customers have not yet exceeded a maximum of six GTPP
groups in the configuration. With the reduction in the number of GTPP groups configured, there will no CDR loss as
CDRs are archived in AAA manager when AAA proxy goes to warn state.
groups in the configuration. With the reduction in the number of GTPP groups configured, there will no CDR loss as
CDRs are archived in AAA manager when AAA proxy goes to warn state.
Command Changes
gtpp group
This CLI command allows the user to configure only up to six GTPP groups.
configure
context context_name
apn apn_name
gtpp group group_name [ accounting-context ac_context_name ]
default gtpp group
no gtpp group group_name
end
CSCul98917, CSCum70480, CSCum36649, CSCum36659, CSCuo59964 -
Support for Gx Sync after Session or Message Loss
Applicable Products: GGSN, HA, HSGW, IPSG, PDSN, P-GW, S-GW
Feature Changes
Support for Session Recovery and Session Sync
Currently PCRF and ASR5K gateway node are in sync during normal scenarios and when Gx assume positive is not
applied. However, there are potential scenarios where the PCRF might have been locally deleted or lost the Gx session
information and it is also possible that due to the loss of message, gateway node and PCRF can be out of sync on the
session state.
applied. However, there are potential scenarios where the PCRF might have been locally deleted or lost the Gx session
information and it is also possible that due to the loss of message, gateway node and PCRF can be out of sync on the
session state.
While these are rare conditions in the network, the desired behavior is to have PCRF recover the Gx session when it is
lost and also to have PCRF and gateway sync the rule and session information. This feature provides functionality to
ensure PCRF and gateway can sync on session information and recover any lost Gx sessions. Configuration support has
been provided to enable session recovery and session sync features. Dynamic dictionaries also support the Gx session
sync feature.
lost and also to have PCRF and gateway sync the rule and session information. This feature provides functionality to
ensure PCRF and gateway can sync on session information and recover any lost Gx sessions. Configuration support has
been provided to enable session recovery and session sync features. Dynamic dictionaries also support the Gx session
sync feature.