112
A timer that is too short might result in frequent authentication or accounting failures. This is 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.
This is because the server will remain in blocked state until the timer expires.
Examples
# In RADIUS scheme
radius1
, set the quiet timer to 10 minutes for the servers.
<Sysname> system-view
[Sysname] radius scheme radius1
[Sysname-radius-radius1] timer quiet 10
Related commands
display radius scheme
timer realtime-accounting (RADIUS scheme view)
Use
timer realtime-accounting
to set the real-time accounting interval.
Use
undo timer realtime-accounting
to restore the default.
Syntax
timer realtime-accounting
interval
[
second
]
undo timer realtime-accounting
Default
The real-time accounting interval is 12 minutes.
Views
RADIUS scheme view
Predefined user roles
network-admin
mdc-admin
Parameters
interval
: Specifies the real-time accounting interval in the range of 0 to 71582.
second
: Specifies the measurement unit as second. If you do not specify this keyword, the real-time
accounting interval is measured in minutes.
Usage guidelines
When the real-time accounting interval on the device is not zero, the device sends online user
accounting information to the RADIUS accounting server at the configured interval.
When the real-time accounting interval on the device is zero, the device sends online user
accounting information to the RADIUS accounting server at the real-time accounting interval
configured on the server. If the real-time accounting interval is not configured on the server, the
device does not send online user accounting information.
A short interval helps improve accounting precision but requires many system resources.
Table 9 Recommended real-time accounting intervals
Number of users
Real-time accounting interval
1 to 99
3 minutes
100 to 499
6 minutes
