R3166-R3206-HP High-End Firewalls Access Control Command Reference-6PW101

116
Use the undo stop-accounting-buffer enable command to disable the buffering function.
By default, the device buffers stop-accounting requests to which no responses are received.
Stop-accounting requests affect the charge to users. A NAS must make its best effort to send every
stop-accounting request to the RADIUS accounting servers. For each stop-accounting request getting no
response in the specified period of time, the NAS buffers and resends the packet until it receives a
response or the number of transmission attempts reaches the configured limit. In the latter case, the NAS
discards the packet. However, if you have removed the accounting server, stop-accounting messages are
not buffered.
Related commands: reset stop-accounting-buffer and display stop-accounting-buffer.
Examples
# Enable the device to buffer the stop-accounting requests to which no responses are received.
<Sysname> system-view
[Sysname] radius scheme radius1
[Sysname-radius-radius1] stop-accounting-buffer enable
timer quiet (RADIUS scheme view)
Syntax
timer quiet minutes
undo timer quiet
View
RADIUS scheme view
Default level
2: System level
Parameters
minutes: Server quiet period in minutes, in the ranges from 0 to 255. If you set this argument to 0, when
the device needs to send an authentication or accounting request but the current server is unreachable,
the device sends the request to the next server in the active state, without changing the current server’s
status. As a result, when the device needs to send a request of the same type for another user, it still tries
to send the request to the current server because the current server is in the active state.
Description
Use the timer quiet command to set the quiet timer for the servers, that is, the duration during which the
servers stay blocked before resuming the active state.
Use the undo timer quiet command to restore the default.
By default, the server quiet period is 5 minutes.
You can use the command to adjust the duration during which a server must stay quiet, and control
whether the device changes the status of an unreachable server. For example, if you determine that the
primary server is unreachable because the device’s port connected to the server is out of service
temporarily or the server is busy, you can set the server quiet period to 0 so that the device uses the
primary server whenever possible.
Be sure to set the server quiet timer properly. Too short a quiet timer may result in frequent authentication
or accounting failures because the device has to repeatedly try to communicate with an unreachable
server that is in the active state.