Configuring RADIUS
Configure Remote Authentication Dial-In User Service (RADIUS) parameters if a remote RADIUS server implements authentication and accounting.
- Configuring RADIUS Authentication and Accounting Servers
- If a server performs both RADIUS authentication and accounting functions, it uses a separate interface for each function.
- (Optional) Configuring RADIUS Proxy Authentication
- RADIUS proxy authentication is configured on a BRAS to forward RADIUS packets between a RADIUS client and a RADIUS server to authenticate user information
- (Optional) Configuring a RADIUS Server Selection Algorithm
- If there is more than one authentication or accounting server in a RADIUS server group, you can configure a RADIUS server selection algorithm to implement load balancing or master/backup for these servers.
- (Optional) Configuring Flexible Interoperation of RADIUS Attributes
- The RADIUS attributes supported by a Huawei device and a RADIUS server may be different. Python scripts can be loaded to implement flexible interoperation of RADIUS attributes.
- (Optional) Configuring Negotiated Parameters of the RADIUS Server
- A RADIUS server and the NetEngine 8000 F must use the same RADIUS parameters and message format to communicate.
- (Optional) Configuring RADIUS Attribute Translation
- The NetEngine 8000 F can communicate with RADIUS servers from different vendors through the RADIUS attribute translation function.
- (Optional) Disabling RADIUS Attributes
- You must enable RADIUS attribute translation before disabling RADIUS attributes.
- (Optional) Configuring a Tunnel Password Delivery Mode
- The RADIUS server supports a tunnel password in cipher text or simple text.
- (Optional) Configuring the Class Attribute to Carry the CAR Value
- You can configure the Class attribute to carry or not to carry the committed access rate (CAR) value to ensure the communication between the NetEngine 8000 F and RADIUS servers from different vendors.
- (Optional) Configuring the NAS-Port Attribute Format
- You can configure different formats of the NAS-Port attribute so that the NetEngine 8000 F can communicate with RADIUS servers from different vendors.
- (Optional) Configuring the Source Interface of a RADIUS Server on a Client
- When the NetEngine 8000 F connects to multiple RADIUS servers, you can configure the source interface of each RADIUS server on the NetEngine 8000 F to identify the route between the NetEngine 8000 F and each RADIUS server.
- (Optional) Configuring a RADIUS Authorization Server
- You can configure multiple RADIUS authorization servers to authorize users who access dynamic services.
- (Optional) Setting RADIUS Server Status Parameters
- You can configure RADIUS server status parameters on the NetEngine 8000 F to monitor the RADIUS server status.
- (Optional) Configuring Extended Source Interfaces of a RADIUS Server
- If you do not want to use the default extended source interface to send and receive RADIUS packets, you can change the default extended source interface of a RADIUS server.
- (Optional) Configuring Formats for the Calling-Station-Id Attribute
- This section describes how to configure formats for the RADIUS attribute Calling-Station-Id (31) to adapt to different vendors' devices and different RADIUS servers.
- (Optional) Configuring Negotiation Parameters for RADIUS Attributes
- When a RADIUS server communicates with the NetEngine 8000 F, the RADIUS attributes configured on them must be consistent.
- (Optional) Setting DSCP Values for RADIUS Packets
- To prevent RADIUS packets sent by the NetEngine 8000 F from being discarded in the case of network congestion, you can set DSCP values for the RADIUS packets.
- (Optional) Configuring a Mode of Encapsulating User IP Addresses
- A RADIUS server and the NetEngine 8000 F must use the same RADIUS attributes, including user IP address-related attributes, to communicate.
- (Optional) Configuring RADIUS Attributes
- The attributes delivered by the RADIUS server take effect only when there are corresponding configurations on the NetEngine 8000 F.
- (Optional) Using the Framed-Ipv6-Pool Attribute to Replace IPv6 Address Pools
- A BRAS can be configured to use an IPv6 address pool delivered by a RADIUS server using the Framed-Ipv6-Pool attribute and IPv6 address pools configured in the domain to assign IPv6 addresses to users.
- (Optional) Configuring the User-Defined Encapsulation for RADIUS Attributes
- You can also specify a DHCP/DHCPv6 option to encapsulate a RADIUS attribute.
- (Optional) Configuring the RADIUS Client to Support ACLs Dynamically Delivered by a RADIUS Server
- The RADIUS server can dynamically deliver the HW-Data-Filter attribute that contains traffic classifier-behavior pair information to a RADIUS client.
- (Optional) Configuring a Device to Parse the Option 17 Field Based on the Format Defined by the DSL Forum
- Configure a device to parse the Option 17 field based on the format defined by the DSL Forum and send the obtained sub-attributes to a RADIUS server.
- (Optional) Configuring CAR for Whitelisted RADIUS Sessions
- You can configure CAR for whitelisted RADIUS sessions to limit the rate at which packets of the whitelisted RADIUS sessions are sent to the RADIUS server. This configuration prevents non-whitelisted RADIUS sessions from preempting bandwidth if the RADIUS server encounters a traffic burst.
- Verifying the RADIUS Configuration
- You can verify the server configurations, RADIUS attributes supported by the system, and statistics on RADIUS packets.