3com 8807 참조 가이드
RADIUS Protocol Configuration Commands
335
request packets saved during a specified time range. The displayed packet
information can help with diagnosis and troubleshooting.
information can help with diagnosis and troubleshooting.
After transmitting the stopping accounting requests, if there is no response from
the RADIUS scheme, the switch will save the packet in the buffer and retransmit it
for several times, which is set through the retry stop-accounting command.
the RADIUS scheme, the switch will save the packet in the buffer and retransmit it
for several times, which is set through the retry stop-accounting command.
Related command: reset stop-accounting-buffer, stop-accounting-buffer
enable, retry stop-accounting.
enable, retry stop-accounting.
Example
# Display the stopping accounting requests saved in the system buffer since 0:0:0
to 23:59:59 on August 31, 2002.
to 23:59:59 on August 31, 2002.
<SW8800> display stop-accounting-buffer time-range 0:0:0-2002/08/31
23:59:59-2002/08/31
Total find 0 record
key
Syntax
key { accounting | authentication } string
undo key { accounting | authentication }
View
RADIUS scheme view
Parameter
accounting: Configures to set the encryption key for RADIUS accounting packet.
authentication: Configures to set the encryption key for RADIUS
authentication/authorization packet.
authentication/authorization packet.
string: Specifies the key with a character string not exceeding 16 characters. By
default, the key is 3com.
default, the key is 3com.
Description
Use the key command to configure encryption key for RADIUS
authentication/authorization or accounting packet.
authentication/authorization or accounting packet.
Use the undo key command, you can restore the default key.
RADIUS client (switch system) and RADIUS scheme use MD5 algorithm to encrypt
the exchanged packets. The two ends verify the packet through setting the
encryption key. Only when the keys are identical can both ends accept the packets
from each other and give responses. So it is necessary to ensure that the keys set
on the switch and the RADIUS scheme are identical. If the
authentication/authorization and accounting are performed on two different
servers with different encryption keys, you are supposed to set two encryption
keys respectively.
the exchanged packets. The two ends verify the packet through setting the
encryption key. Only when the keys are identical can both ends accept the packets
from each other and give responses. So it is necessary to ensure that the keys set
on the switch and the RADIUS scheme are identical. If the
authentication/authorization and accounting are performed on two different
servers with different encryption keys, you are supposed to set two encryption
keys respectively.
Related command: primary accounting, primary authentication, radius
scheme.
scheme.