Chapter 2 Configuring User Profiles and CSS Parameters
Configuring the CSS as a Client of a RADIUS Server
To specify a secondary RADIUS server, enter:
(config)# radius-server secondary 172.27.56.79 secret Hello auth-port 30658
To remove a secondary RADIUS server, enter:
(config)# no radius-server secondary
Configuring the RADIUS Server Timeouts
Use the radius-server timeout command to specify the time interval that the CSS is to wait for the RADIUS server (primary or secondary) to reply to an authentication request before retransmitting requests to the RADIUS server. You configure the number of retransmitted requests to the server through the radius-server retransmit command. Valid entries are 1 to 255 seconds. The default is 10 seconds.
To configure the configure the RADIUS server timeout interval to 1 minute
(60 seconds), enter:
(config)# radius-server timeout 60
To set the RADIUS server retransmit request back to the default of 10 seconds, enter:
(config)# no radius-server timeout
Configuring the RADIUS Server Retransmits
Use the radius-server retransmit command to specify the number of times the CSS is to retransmit an authentication request to a timed-out RADIUS server before considering the server dead and stop transmitting. If a secondary RADIUS server has been identified, that server is selected as the active server. Valid entries are 1 to 30 retries. The default is 3.
If the RADIUS server does not respond to the CSS retransmitted requests, the CSS considers the server as dead, stops transmitting to the server, and starts the dead timer as defined through the radius-serverdead-timecommand. If a secondary server is configured, the CSS transmits the requests to the secondary server. If the secondary server does not respond to the request, the CSS considers it dead and starts the dead timer. If there is no active server, the CSS stops transmitting requests until the primary RADIUS server becomes alive.
| | Cisco Content Services Switch Basic Configuration Guide | | |
| | |
| 78-11424-03 | | | 2-31 |
| | |
