для Cisco Cisco Packet Data Gateway (PDG)
AAA Changes in Release 16
AAA Enhancements for 16.0 ▀
Release Change Reference, StarOS Release 16 ▄
69
Important:
This behavior change is currently applicable only to Gy interface, and not on Gx.
Previous Behavior: Currently, the maximum length of a FUI-Redirect-URL on the Gy interface is 256 characters.
New Behavior: The maximum length of Redirect URL is now increased to support up to 512 bytes.
Important:
For a better memory management, a total of 512 bytes is allowed for the Redirect-URL, in which the
last character will be used for the '\0' char at the end of the string. So, a maximum of 511 characters can be possible in
Redirect-URL.
Redirect-URL.
Customer Impact: This helps the operator to have a large URL with additional parameters to be sent to AoC server.
CSCug70326, CSCun27457 - Gy Backpressure Enhancements
Applicable Products: GGSN, HA, IPSG, PDSN, P-GW
Feature Changes
Gy Backpressure Enhancement
This feature is extended to maintain a list of DCCA sessions that hit backpressure while creating a message i.e.,
backpressured list, eliminating the current polling procedure. This will maintain a single queue for all types of messages
(CCR-I, CCR-U, CCR-T, CCR-E) that are backpressured. The messages will be sent in FIFO order (i.e., session which
got first backpressured hit will be served first) from the queue.
backpressured list, eliminating the current polling procedure. This will maintain a single queue for all types of messages
(CCR-I, CCR-U, CCR-T, CCR-E) that are backpressured. The messages will be sent in FIFO order (i.e., session which
got first backpressured hit will be served first) from the queue.
After processing a session from the backpressure queue DCCA will check for the congestion status of the peer and
continue only if the peer has empty slots in the outstanding message queue to accommodate further CCRs.
continue only if the peer has empty slots in the outstanding message queue to accommodate further CCRs.
Previous Behavior: Currently, the gateway has a max-outstanding configuration at Diameter endpoint level to manage
a number of messages that were waiting for response from OCS. When the max-outstanding was configured to a low
value, then the frequency to be in congested state was very high. With polling procedure in DCCA application, CPU
utilization was reaching very high.
a number of messages that were waiting for response from OCS. When the max-outstanding was configured to a low
value, then the frequency to be in congested state was very high. With polling procedure in DCCA application, CPU
utilization was reaching very high.
New Behavior: All DCCA sessions associated with the CCR messages that are triggered BACKPRESSURE (when
max-outstanding has been reached) will be queued in backpressure list which is maintained per ACS manager instance
(credit-control) level.
max-outstanding has been reached) will be queued in backpressure list which is maintained per ACS manager instance
(credit-control) level.
This list will not have any specific configurable limits on the number of sessions that will be queued in it. This is
because there is an inherent limit that is already present which is dependent on the number of subscriber/DCCA
sessions.
because there is an inherent limit that is already present which is dependent on the number of subscriber/DCCA
sessions.
With this new separate backpressured list, CPU utilization will come down under high backpressure case.
Performance Indicator Changes
DCCA Group Schema
The following new bulkstats variables have been added to track the total number of times backpressure got hit while
creating CCR messages.
creating CCR messages.
ccri-bp-stats