This feature is
introduced to support creation and communication of duplicate Rf records to
secondary AAA group servers configured for the Rf interface.
To achieve this
functionality, the following configurations must be enabled –
aaa group CLI command under APN to configure a
maximum of 2 AAA groups - primary and secondary AAA groups, or two different
endpoints for Rf Diameter accounting servers
diameter accounting duplicate-record under AAA
group to allow Rf duplicate record creation
duplicate-record is a new CLI command introduced in this release
for duplicating the Rf START, INTERIM and STOP accounting records.
This is a
license-controlled CLI command. For more information, contact your Cisco
In releases prior
to 21, gateway allows only one AAA group configuration per APN for Rf
accounting. The AAA group is configured to load balance across multiple servers
to pass the Rf traffic and also expect an accounting answer. Note that the
secondary AAA group configuration is allowed currently but is restricted to
only RADIUS accounting.
In release 21 and
beyond, the gateway is provided with the ability to configure a secondary AAA
group per APN for the Rf interface, and send the duplicate Diameter Rf
accounting records to the secondary AAA group servers. The secondary AAA group
is used for non-billing purposes only.
duplicate records will neither be written to HDD nor added to the archival
There is no change
in the current behavior with the primary AAA group messages. The primary AAA
group is independent of the secondary AAA group, and it has multiple Rf servers
configured. When the Rf servers do not respond even after multiple retries as
per the applicable configuration, the Rf records are archived and stored in
HDD. This behavior continues as is irrespective of the configuration of
group has a very similar configuration as the primary aaa group except that the
new CLI command
diameter accounting duplicate-record is
additionally included to configure the secondary aaa-group. It is also
important to note that different Diameter endpoints and a separate set of Rf
servers should be provisioned for both primary and secondary AAA groups.
If all the
configured servers are down, the request message will be discarded without
writing it in HDD or archiving at aaamgr.
The original and
duplicate Rf messages use two different aaa-groups and two different Diameter
endpoints. Hence, the values for Session-ID AVP will be different. Based on the
configuration of primary and secondary endpoints the values for Origin-Host,
Origin-Realm, Destination-Realm, and Destination-Host AVPs may be different.
Also based on the configuration under policy accounting for inclusion of
virtual/gn apn name for secondary group Called-Station-ID AVP might change. All
other AVPs will have the same values as with the primary aaa group Rf message.
Also, note that
the values such as Acct-Interim-Interval (AII) interval received in ACA from
secondary group of AAA servers will be ignored.