HP 10500 Series Configuration Manual page 38

Step
2. Enter RADIUS scheme view.
3. Specify a source IP address
for outgoing RADIUS packets.
Setting RADIUS timers
The device uses the following types of timers to control the communication with a RADIUS server:
• Server response timeout timer (response-timeout)—Defines the RADIUS request retransmission
interval. After sending a RADIUS request (authentication/authorization or accounting request), the
device starts the server response timeout timer. If the device receives no response from the RADIUS
server before this 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 the server quiet
timer, and tries to communicate with another server in active state. After the timer expires, the device
changes the status of the server back to active.
• Real-time accounting timer (realtime-accounting)—Defines the interval at which the device sends
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 to the
accounting server for online users.
Follow these guidelines when you set RADIUS timers:
• For the same type of users, the maximum number of transmission attempts multiplied by the RADIUS
server response timeout period must be less than the client connection timeout time and must not
exceed 75 seconds. Otherwise, stop-accounting messages cannot be buffered, and the
primary/secondary server switchover cannot take place. For example, the product of the two
parameters must be less than 10 seconds for voice users and less than 30 seconds for Telnet users,
because the client connection timeout period for voice users is 10 seconds and that for Telnet users
is 30 seconds.
When you configure the maximum number of RADIUS packet transmission attempts and the
•
RADIUS server response timeout timer, take the number of secondary servers into account. If the
retransmission process takes too much time, the client connection in the access module may be
timed 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 may 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. In this case, the next authentication or accounting attempt may
succeed because the device has set the status of the unreachable servers to blocked and the time for
finding a reachable server is shortened.
• Set the server quiet timer properly. Too short a quiet timer may result in frequent authentication or
accounting failures because the device keeps trying to communicate with an unreachable server
that is in active state.
For more information about the maximum number of RADIUS packet transmission attempts, see
the maximum number of RADIUS request transmission
Command
radius scheme
radius-scheme-name
nas-ip { ip-address | ipv6
ipv6-address }
attempts."
28
Remarks
N/A
By default, the IP address of the
outbound interface is used as the
source IP address.
"Setting