37
•
Server response timeout timer
(
response-timeout
)—Defines the HWTACACS server response
timeout timer. The device starts this timer immediately after an HWTACACS authentication,
authorization, or accounting request is sent. If the device does not receive a response from the
server within the timer, it sets the server to blocked. Then, the device sends the request to another
HWTACACS server.
•
Real-time accounting timer
(
realtime-accounting
)—Defines the interval at which the device sends
real-time accounting packets to the HWTACACS accounting server for online users.
•
Server quiet timer
(
quiet
)—Defines the duration to keep an unreachable server in blocked state. If
a server is not reachable, the device changes the server 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.
The server quiet timer setting affects the status of HWTACACS servers. If the scheme includes one
primary HWTACACS server and multiple secondary HWTACACS servers, the device communicates
with the HWTACACS servers based on the following rules:
•
When the primary server is in active state, the device communicates with the primary server.
•
If the primary server fails, the device performs the following tasks:
{
Changes the server status to blocked.
{
Starts a quiet timer for the server.
{
Tries to communicate with a secondary server in active state that has the highest priority.
•
If the secondary server is unreachable, the device performs the following tasks:
{
Changes the server status to blocked.
{
Starts a quiet timer for the server.
{
Tries to communicate with the next secondary server in active state that has the highest priority.
•
The search process continues until the device finds an available secondary server or has checked
all secondary servers in active state. If no server is available, the device considers the authentication,
authorization, or accounting attempt a failure.
•
When the quiet timer of a server expires, the status of the server changes back to active. The device
does not check the server again during the authentication, authorization, or accounting process.
•
When you remove a server in use, communication with the server times out. The device looks for a
server in active state by first checking the primary server, and then checking secondary servers in
the order they are configured.
•
When the primary server and secondary servers are all in blocked state, the device tries to
communicate with the primary server.
•
When one or more servers are in active state, the device tries to communicate with these active
servers only, even if they are unavailable.
•
When an HWTACACS server's status changes automatically, the device changes this server's
status accordingly in all HWTACACS schemes in which this server is specified.
To set HWTACACS timers:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter HWTACACS scheme
view.
hwtacacs scheme
hwtacacs-scheme-name
N/A
