HP VPN Firewall Appliances Access Control Configuration Guide

212
To specify a source IP address for a specific RADIUS scheme:
Ste
p
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 { ip-address |
ipv6 ipv6-address }
By default, the IP address of the outbound interface
is used as the source IP address.
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 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 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 cannot
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, consider the number of secondary servers. If the
retransmission process takes too long, the client connection in the access module might time out
when the device is trying to find an available server. For more information about the maximum
number of RADIUS packet transmission attempts, see "
Setting the maximum number of RADIUS
r
eques
t transmission attempts."
• 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. In this case, the next authentication or accounting attempt can
succeed because the device has set the status of the unreachable servers to blocked so time for
finding a reachable server is shortened.
• Set a correct server quiet timer. Too short a quiet timer can result in frequent authentication or
accounting failures because the device has to repeatedly attempt to communicate with an
unreachable server that is in active state.