Cisco Cisco Packet Data Interworking Function (PDIF) Guía Para Resolver Problemas
CoA, RADIUS DM, and Session Redirection (Hotlining)
RADIUS Change of Authorization and Disconnect Message ▀
Cisco ASR 5000 Series Enhanced Feature Configuration Guide ▄
OL-22983-01
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).
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:
server:
Notes:
must be the name of the AAA context where you want to enable CoA and DM. The AAA
context must have been configured as described in the Configuring Context-Level AAA Functionality section of
the AAA Interface Administration Guide.
the AAA Interface Administration Guide.
A number of optional keywords and variables are available for the
command. For more information regarding this command please refer to the Command Line Interface
Reference.
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. Use one of the following attributes to identify the system:
identified correctly. Use one of the following attributes to identify the system:
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.
3GPP-NSAPI: Network Service Access Point Identifier (NSAPI) should match to the NSAPI specified
for specific PDP context.