CoA, RADIUS DM, and Session Redirection (Hotlining)
RADIUS Change of Authorization and Disconnect Message ▀
Cisco ASR 5x00 Packet Data Network Gateway Administration Guide ▄
233
Step 3
View CoA and DM message statistics as described in the
Viewing CoA and DM Statistics
section.
Important:
Commands used in the configuration examples in this section provide base functionality to
the extent that the most common or likely commands and/or keyword options are presented. In many cases,
other optional commands and/or keyword options are available. Refer to the
Command Line Interface
Reference
for complete information regarding all commands. Not all commands and keywords/variables are
available or supported. This depends on the platform type and the installed license(s).
Enabling CoA and DM
Use the following example to enable the system to listen for and respond to CoA and DM messages from the RADIUS
server:
configure
context
<context_name>
radius change-authorize-nas-ip
<ipv4/ipv6_address>
end
Notes:
<context_name>
must be the name of the AAA context where you want to enable CoA and DM.
For more information on configuring the AAA context, if you are using StarOS 12.3 or an earlier release, refer
to the
Configuring Context-Level AAA Functionality
section of the
AAA and GTPP Interface Administration
and Reference
. If you are using StarOS 14.0 or a later release, refer to the
AAA Interface Administration and
Reference
.
A number of optional keywords and variables are available for the
radius change-authorize-nas-ip
command. For more information regarding this command please refer to the
Command Line Interface
Reference
.
CoA and DM Attributes
For CoA and DM messages to be accepted and acted upon, the system and subscriber session to be affected must be
identified correctly.
To identify the system, use any one of the following attributes:
NAS-IP-Address: NAS IP address if present in the CoA/DM request should match with the NAS IP address.
NAS-Identifier: If this attribute is present, its value should match to the nas-identifier generated for the
subscriber session
To identify the subscriber session, use any one of the following attributes.
If 3GPP2 service is configured the following attribute is used for correlation identifier:
3GPP2-Correlation-ID: The values should exactly match the 3GPP2-correlation-id of the subscriber
session. This is one of the preferred methods of subscriber session identification.
If 3GPP service is configured the following attributes are used for different identifiers:
3GPP-IMSI: International Mobile Subscriber Identification (IMSI) number should be validated and
matched with the specified IMSI for specific PDP context.
