Cisco Cisco Packet Data Gateway (PDG)
AAA Changes in Release 16
▀ AAA Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
64
CSCue51208, CSCue68211, CSCue68228, CSCue68231, CSCui08926 - support
for SN-Transparent-Data on Gx, Gy and CDRs - IPSG
Applicable Products: GGSN, IPSG
Feature Changes
Support for SN-Transparent-Data AVP on Gy
With this enhancement, the AVPs “SN-Transparent-Data” and “Vlan-Id” will be sent over Gy Interface in the Credit-
Control-Request message. Any change in SN-Transparent-Data AVP will not be triggering an update, and the updated
values will be reported during the next CCR-Request.
Control-Request message. Any change in SN-Transparent-Data AVP will not be triggering an update, and the updated
values will be reported during the next CCR-Request.
The SN-Transparent-Data and VLAN-Id AVPs will be populated by ECS, and DCCA simply reads these values. These
AVPs will be sent in CCR requests, only if these are present in the dictionary used. Since there is no custom dictionary,
Dynamic-Dictionary feature is used. So, a Dynamic-Dictionary based on dcca-custom8 is constructed with theses AVPs
and added to the CCR message.
AVPs will be sent in CCR requests, only if these are present in the dictionary used. Since there is no custom dictionary,
Dynamic-Dictionary feature is used. So, a Dynamic-Dictionary based on dcca-custom8 is constructed with theses AVPs
and added to the CCR message.
CSCue68677 - include Framed-IPv6-Prefix AVP in custom43 Radius dictionary
Applicable Products: GGSN, P-GW
Feature Changes
Support for Framed-IPv6-Prefix AVP in custom43 RADIUS Dictionary
With this release, Framed-IPv6-Prefix AVP will be included in Accounting-Start messages in custom43 RADIUS
dictionary for P-GW IPv6 calls.
dictionary for P-GW IPv6 calls.
CSCuf56984 - Gx-Support for Flow-Direction AVP - Bidirectional(3) required
Applicable Products: GGSN, P-GW
Feature Changes
Support for BIDIRECTIONAL Flow-Direction
In this release, Flow-Direction AVP with the value set to BIDIRECTIONAL (3) is supported on Gx.
This feature should be enabled only after upgrading the active and standby chassis to the build having this feature. That
is, PCRF should install dynamic rule with Flow-Direction “BIDIRECTIONAL (3)" only after active and standby chassis
is upgraded to the same build which supports Flow-Direction AVP with the value BIDIRECTIONAL (3).
is, PCRF should install dynamic rule with Flow-Direction “BIDIRECTIONAL (3)" only after active and standby chassis
is upgraded to the same build which supports Flow-Direction AVP with the value BIDIRECTIONAL (3).