Configuring The Maximum Number Of Radius Request Transmission Attempts; Configuring The Type Of Radius Servers To Be Supported - 3Com 4210 9-Port Configuration Manual

Operation
Set a shared key for RADIUS
accounting messages
The authentication/authorization shared key and the accounting shared key you set on the switch must
be respectively consistent with the shared key on the authentication/authorization server and the
shared key on the accounting server.

Configuring the Maximum Number of RADIUS Request Transmission Attempts

The communication in RADIUS is unreliable because this protocol uses UDP packets to carry its data.
Therefore, it is necessary for the switch to retransmit a RADIUS request if it gets no response from the
RADIUS server after the response timeout timer expires. If the switch gets no answer after it has tried
the maximum number of times to transmit the request, the switch considers that the request fails.
Table 2-16 Configure the maximum transmission attempts of a RADIUS request
Operation
Enter system view
Create a RADIUS scheme and
enter its view
Set the maximum number of
RADIUS request transmission
attempts

Configuring the Type of RADIUS Servers to be Supported

Table 2-17 Configure the type of RADIUS servers to be supported
Operation
Enter system view
Create a RADIUS scheme and
enter its view
Configure the type of RADIUS
servers to be supported
Command
key accounting string
Command
system-view
radius scheme
radius-scheme-name
retry retry-times
Command
system-view
radius scheme
radius-scheme-name
server-type { extended |
standard }
2-17
Remarks
Required
By default, no shared key is
created.
Remarks
—
Required
By default, a RADIUS scheme
named "system" has already been
created in the system.
Optional
By default, the system can try three
times to transmit a RADIUS
request.
Remarks
—
Required
By default, a RADIUS scheme
named "system" has already
been created in the system.
Optional