Cisco Cisco Packet Data Gateway (PDG)
Changing ACL and rulebase together in a single CoA is not supported. For this, two separate CoA requests
can be sent through AAA server requesting for one attribute change per request.
can be sent through AAA server requesting for one attribute change per request.
Important
DM Overview
The DM message is used to disconnect subscriber sessions in the system from a RADIUS server. The DM
request message should contain necessary attributes to identify the subscriber session. If the system successfully
disconnects the subscriber session, a DM-ACK message is sent back to the RADIUS server, otherwise, a
DM-NAK message is sent with proper error reasons.
request message should contain necessary attributes to identify the subscriber session. If the system successfully
disconnects the subscriber session, a DM-ACK message is sent back to the RADIUS server, otherwise, a
DM-NAK message is sent with proper error reasons.
License Requirements
The RADIUS Change of Authorization (CoA) and Disconnect Message (DM) are licensed Cisco features. A
separate feature license may be required. Contact your Cisco account representative for detailed information
on specific licensing requirements. For information on installing and verifying licenses, refer to the Managing
License Keys section of the Software Management Operations chapter in the System Administration Guide.
separate feature license may be required. Contact your Cisco account representative for detailed information
on specific licensing requirements. For information on installing and verifying licenses, refer to the Managing
License Keys section of the Software Management Operations chapter in the System Administration Guide.
Enabling CoA and DM
To enable RADIUS Change of Authorization and Disconnect Message:
Step 1
Enable the system to listen for and respond to CoA and DM messages from the RADIUS server as described in
CoA and DM, on page 136
.
Step 2
Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode
command save configuration. For additional information on how to verify and save configuration files, refer to the
System Administration Guide and the Command Line Interface Reference.
command save configuration. For additional information on how to verify and save configuration files, refer to the
System Administration Guide and the Command Line Interface Reference.
Step 3
View CoA and DM message statistics as described in
Viewing CoA and DM Statistics, on page 139
.
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).
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).
Important
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:
RADIUS server:
configure
context <context_name>
HNB-GW Administration Guide, StarOS Release 19
136
CoA, RADIUS DM, and Session Redirection (Hotlining)
DM Overview