If a server performs both RADIUS authentication and accounting functions, it uses a separate interface for each function.
To configure RADIUS authentication and accounting servers, you need the following data:
IP addresses of RADIUS authentication and accounting servers
Names of the VPN instances to which RADIUS authentication and accounting servers belong
Port numbers of RADIUS authentication and accounting servers (The default port numbers are 1812 and 1813, respectively.)
Weights of RADIUS authentication and accounting servers (The weights apply only to load balancing scenarios, and the default value is 0.)
RADIUS authentication and accounting servers can use the same IP address, indicating that one server can perform both RADIUS authentication and accounting functions.
The system view is displayed.
The RADIUS server group view is displayed.
A shared key is configured for the communication with the RADIUS server.
A RADIUS authentication server is configured.
To specify a different authentication port for PPP users, run the radius-server authentication ip-address [ vpn-instance instance-name ] ppp-user-port port command to configure a RADIUS authentication server.
The function to poll RADIUS servers after receiving a RADIUS Access-Reject packet is enabled.
The maximum number of times the packets can be retransmitted to the RADIUS server and the interval for retransmitting such packets are configured.
When you run this command, pay attention to the following:
A RADIUS accounting server is configured.
To specify a different accounting port for PPP users, run the radius-server accounting ip-address [ vpn-instance instance-name ] ppp-user-port port command to configure a RADIUS accounting server.
The maximum number of times a buffered Accounting-Start packet can be retransmitted to the RADIUS accounting server is configured.
The maximum number of times an Accounting-Stop packet can be retransmitted to the RADIUS accounting server is configured.
The function to forcibly send an Accounting-Stop packet is enabled.
In normal cases, a RADIUS server generates user entries only after accounting succeeds. However, some user entries may be generated in the database after authentication succeeds but before accounting is started. For example, if users have requested IP addresses and authentication succeeds but accounting fails due to an exception, the requested IP addresses cannot be released and users fail to go online using these IP addresses. In this case, you need to run this command on the NetEngine 8000 F to forcibly send an Accounting-Stop packet to the RADIUS server to release the requested IP addresses.
This command applies only to scenarios where user authentication succeeds but accounting fails and residual user entries generated by the RADIUS server exist in the database.
The function to buffer RADIUS Accounting-Interim packets is enabled, and the maximum number of times a buffered RADIUS Accounting-Interim packet can be retransmitted is configured.
The device is configured not to generate a RADIUS server down alarm when the communication between the device and RADIUS server is interrupted.
The maximum number of accounting packets that can be buffered is configured.
If the value specified by max-packet-number is not 8192, the maximum number of accounting packets that can be buffered equals the specified value and the number of users whose accounting packets can be buffered is not limited.
The interval for retransmitting buffered RADIUS accounting packets and the number of users whose accounting packets are triggered to be retransmitted each time are configured.
A memory usage threshold is configured for the main control board.
The function to generate an accounting packet buffer alarm is enabled, and the upper and lower limits are configured for buffering accounting packets.
Buffer usage of accounting packets = Number of buffered accounting packets/Maximum number of accounting packets that can be buffered
The device is configured not to delete buffered packets when the number of times these packets are retransmitted reaches the specified threshold.
By default, buffered packets are deleted when the number of times these packets are retransmitted reaches the specified threshold.
The function to retransmit buffered packets is manually triggered.
The configuration is committed.