H3C Technologies H3C S12500-X Series Switches - Manual (Page 41)

29
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter RADIUS scheme view.
radius scheme
radius-scheme-name
N/A
3. Specify a source IP address
for outgoing RADIUS packets. nas-ip { ipv4-address | ipv6
ipv6-address }
By default, the source IP address
specified by the radius nas-ip
command in system view is used. If
the source IP address is not
specified, the IP address of the
outbound interface is used.
365B
Setting RADIUS timers
The device uses the following types of timers to control communication with a RADIUS server:
• Server response timeout timer (response-timeout)—Defines the RADIUS request retransmission
interval. The timer starts immediately after a RADIUS request is sent. If the device does not receive
a response from the RADIUS server before the timer expires, it resends the request.
• Server quiet timer (quiet)—Defines the duration to keep an unreachable server in blocked state. If
one server is not reachable, the device changes the server's status to blocked, starts this timer for the
server, and tries to communicate with another server in active state. After the server quiet timer
expires, the device changes the status of the server back to active.
• Real-time accounting timer (realtime-accounting)—Defines the interval for the device to send
real-time accounting packets to the RADIUS accounting server for online users. To implement
real-time accounting, the device must periodically send real-time accounting packets for online
users to the accounting server.
When you set RADIUS timers, follow these guidelines:
• When you configure the maximum number of RADIUS packet transmission attempts and the
RADIUS server response timeout timer, consider the number of secondary servers. If the
retransmission process takes too much time, the client connection in the access module such as the
Telnet module might time out while the device is trying to find an available server.
• When a number of secondary servers are configured, the client connections of access modules that
have a short client connection timeout period might still be timed out during initial authentication or
accounting, even if the packet transmission attempt limit and server response timeout period are
configured with small values. The next authentication or accounting attempt can succeed because
the device has set the status of the unreachable servers to blocked and the amount of time for
finding a reachable server has been shortened.
• Make sure the server quiet timer is set correctly. A timer that is too short might result in frequent
authentication or accounting failures because the device will continue to attempt to communicate
with an unreachable server that is in active state. A timer that is too long might temporarily block a
reachable server that has recovered from a failure, because the server will remain in blocked state
until the timer expires.
• A short real-time accounting interval helps improve accounting precision but requires many system
resources. When there are 1000 or more users, set the interval to 15 minutes or longer.
To set RADIUS timers: