Table of Contents
Advertisement
RADIUS Authentication and Accounting
Configuring RADIUS Accounting
5-32
3.
(Optional) Configure session blocking and interim updating options
•
Updating: Periodically update the accounting data for sessions-in-
progress
•
Suppress accounting: Block the accounting session for any
unknown user with no username access to the switch
1. Configure the Switch To Access a RADIUS Server
Before you configure the actual accounting parameters, you should first
configure the switch to use a RADIUS server. This is the same as the process
described on page 5-13. You need to repeat this step here only if you have not
yet configured the switch to use a RADIUS server, your server data has
changed, or you need to specify a non-default UDP destination port for
accounting requests. Note that switch operation expects a RADIUS server to
accommodate both authentication and accounting.
Syntax: [no] radius-server host < ip-address >
Adds a server to the RADIUS configuration or (with no)
deletes a server from the configuration.
[acct-port < port-number >]
Optional. Changes the UDP destination port for
accounting requests to the specified RADIUS server. If
you do not use this option, the switch automatically
assigns the default accounting port number. (Default:
1813)
[key < key-string >]
Optional. Specifies an encryption key for use during
accounting or authentication sessions with the speci-
fied server. This key must match the encryption key
used on the RADIUS server. Use this command only if
the specified server requires a different encryption key
than configured for the global encryption key.
Note: When you save the config file using Xmodem
or TFTP, the key information is not saved in the
file. This causes Radius authentication to fail
when the config file is loaded back onto the switch.
(For a more complete description of the radius-server command and its
options, turn to page 5-13.)
Advertisement
Table of Contents
