Configuring a RADIUS Server Group

CloudEngine 12800 and 12800E V200R005C10 Configuration Guide - Security

This document describes the configurations of Security, including AAA, 802.1x Authentication, ACL, TCAM ACL Customization, local attack defense, Microsegmentation, MFF, attack defense, traffic suppression and storm control, ARP security, Port security, MACsec, DHCP snooping, IPSG, URPF, SSL, Keychain and FIPS.

About This Document
AAA Configuration
- Overview of AAA
- Understanding AAA
- Application Scenarios for AAA
- Licensing Requirements and Limitations for AAA
- Summary of AAA Configuration Tasks
- Configuring Local Authentication and Authorization
- Configuring RADIUS AAA
- Configuring HWTACACS AAA
- Clearing AAA Statistics
- Configuration Examples for AAA
  - Example for Configuring RADIUS Authentication and Accounting
  - Example for Configuring HWTACACS Authentication, Accounting, and Authorization
- Troubleshooting AAA
  - An AAA Local User Cannot Be Created Due to Incorrect Password Setting
802.1x Authentication Configuration
- Understanding 802.1x Authentication
- Application Scenarios for 802.1x Authentication
- Licensing Requirements and Limitations for 802.1x Authentication
- Default Settings for 802.1x Authentication
- Configuring 802.1x Authentication
- Maintaining 802.1x Authentication
  - Clearing Statistics on 802.1x Authentication Packets
  - Forcing Users Offline
- Configuration Examples for 802.1x Authentication
  - Example for Configuring 802.1x Authentication to Control Users' Internal Access
ACL Configuration
- Overview of ACLs
- Understanding ACLs
- Application Scenarios for ACLs
- Licensing Requirements and Limitations for ACLs
- Default Settings for ACLs
- Configuring a Basic ACL
- Configuring an Advanced ACL
- Configuring a Layer 2 ACL
- Configuring a User-defined ACL
- Configuring an ARP-based ACL
- Configuring a Basic ACL6
- Configuring an Advanced ACL6
- Maintaining an ACL
  - Clearing ACL Statistics
  - Checking ACL Resource Usages
- Configuration Examples for ACLs
- ACL FAQ
  - Which Packets Cannot Be Filtered by the ACL Used by a Traffic Policy?
TCAM ACL Customization Configuration
- Overview of TCAM ACL Customization
- Licensing Requirements and Limitations for TCAM ACL Customization
- Configuring TCAM ACL Customization
  - Enabling TCAM ACL Customization
  - Configuring the TCAM ACL Customization Function for Services
- Displaying Information about a TCAM ACL Customization Profile or Preset Profile
- Configuration Examples for TCAM ACL Customization
  - Example for Configuring TCAM ACL Customization
Microsegmentation Configuration
- Overview of Microsegmentation
- Understanding Microsegmentation
- Application Scenarios for Microsegmentation
- Licensing Requirements and Limitations for Microsegmentation
- Configuring Microsegmentation
- Maintaining Microsegmentation
  - Checking Microsegmentation Statistics
  - Clearing Microsegmentation Statistics
- Configuration Examples for Microsegmentation
  - Example for Configuring IP Address-based Microsegmentation
Local Attack Defense Configuration
- Overview of Local Attack Defense
- Licensing Requirements and Limitations for Local Attack Defense
- Default Settings for Local Attack Defense
- Configuring CPU Attack Defense
- Configuring Attack Source Tracing
- Maintaining Local Attack Defense
- Configuration Examples for Local Attack Defense
  - Example for Configuring Local Attack Defense
- Troubleshooting Local Attack Defense
MFF Configuration
- Overview of MFF
- Understanding MFF
- Application Scenarios for MFF
- Licensing Requirements and Limitations for MFF
- Configuring MFF
- Configuration Examples for MFF
  - Example for Configuring MFF to Implement Layer 2 Isolation and Layer 3 Connection
- Troubleshooting MFF
  - Users Fail to Access the Internet After MFF Is Configured
Attack Defense Configuration
- Overview of Attack Defense
- Understanding Attack Defense
- Application Scenarios for Attack Defense
- Licensing Requirements and Limitations for Attack Defense
- Default Settings for Attack Defense
- Configuring Defense Against Malformed Packet Attacks
- Configuring Defense Against Packet Fragment Attacks
- Configuring Defense Against Flood Attacks
- Clearing Attack Defense Statistics
- Configuration Examples for Attack Defense
  - Example for Configuring Attack Defense
Traffic Suppression and Storm Control Configuration
- Overview of Traffic Suppression and Storm Control
- Understanding Traffic Suppression and Storm Control
  - Traffic Suppression
  - Storm Control
- Application Scenarios for Traffic Suppression and Storm Control
  - Traffic Suppression
  - Storm Control
- Licensing Requirements and Limitations for Traffic Suppression and Storm Control
- Default Settings for Traffic Suppression and Storm Control
- Configuring Traffic Suppression
- Configuring Storm Control
- Configuration Examples for Traffic Suppression and Storm Control
  - Example for Configuring Traffic Suppression
  - Example for Configuring Storm Control
ARP Security Configuration
- Overview of ARP Security
- Understanding ARP Security
- Application Scenarios for ARP Security
  - Defense Against ARP Flood Attacks
  - Defense Against ARP Spoofing Attacks
- Licensing Requirements and Limitations for ARP Security
- Default Settings for ARP Security
- Configuring Defense Against ARP Flood Attacks
- Configuring Defense Against ARP Spoofing Attacks
- Maintaining ARP Security
- Configuration Examples for ARP Security
  - Example for Configuring ARP Security Functions
  - Example for Configuring Defense Against ARP MITM Attacks
Port Security Configuration
- Overview of Port Security
- Understanding Port Security
- Application Scenarios for Port Security
- Licensing Requirements and Limitations for Port Security
- Default Settings for Port Security
- Configuring Port Security
- Configuration Examples for Port Security
  - Example for Configuring Port Security
MACsec Configuration
- Overview of MACsec
- Understanding MACsec
- Application Scenarios for MACsec
- Default Configuration
- Licensing Requirements and Limitations for MACsec
- Configuring MACsec
- Maintaining MACsec
  - Displaying MACsec Statistics
  - Clearing MACsec Statistics
- Configuration Examples for MACsec
  - Example for Configuring Point-to-Point MACsec
DHCP Snooping Configuration
- Overview of DHCP Snooping
- Understanding DHCP Snooping
  - DHCP Snooping Fundamentals
  - Option 82 Supported by DHCP Snooping
- Application Scenarios for DHCP Snooping
- Licensing Requirements and Limitations for DHCP Snooping
- Default Settings for DHCP Snooping
- Configuring Basic Functions of DHCP Snooping
- Configuring DHCP Snooping Attack Defense
- Inserting the Option 82 Field in a DHCP Message
- Maintaining DHCP Snooping
- Configuration Examples for DHCP Snooping
  - Example for Configuring DHCP Snooping Attack Defense
- Troubleshooting DHCP Snooping
  - DHCP Clients Cannot Go Online Due to DHCP Snooping
IPSG Configuration
- Overview of IPSG
- Licensing Requirements and Limitations for IPSG
- Default Settings for IPSG
- Configuring IPSG
- Maintaining IPSG
  - Checking Statistics on Discarded IP Packets
  - Clearing Statistics on Discarded IP Packets
- Configuration Examples for IPSG
  - Example for Configuring IPSG to Check Interface + IP + MAC Binding Entries
URPF Configuration
- Overview of URPF
- Understanding URPF
- Application Scenarios for URPF
- Licensing Requirements and Limitations for URPF
- Default Settings for URPF
- Configuring URPF
- Configuration Examples for URPF
  - Example for Configuring URPF (CE12800)
  - Example for Configuring URPF (CE12800E)
SSL Configuration
- Overview of SSL
- Understanding SSL
- Application Scenarios for SSL
  - Application of SSL in Information Center
- Licensing Requirements and Limitations for SSL
- Configuring SSL
  - Configuring an SSL Policy
  - Applying an SSL Policy
- Configuration Examples for SSL
  - Example for Outputting SSL-Encrypted Logs to a Log Host
Keychain Configuration
- Overview of Keychains
- Understanding Keychains
- Application Scenarios for Keychains
- Licensing Requirements and Limitations for Keychain
- Configuring a Keychain
- Configuration Examples for Keychains
  - Example for Applying the Keychain to RIP
  - Example for Applying the Keychain to BGP
FIPS Configuration
- Overview of FIPS
- Configuring the FIPS Mode
Separating the Management Port from the Service Plane
Checking Security Risks
Setting the System Master Key

Rate and give feedback:

Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).

Configuring a RADIUS Server Group

Context

In a RADIUS server group, you must specify the IP address, port number, and shared key of a specified RADIUS server. Other settings, such as the RADIUS user name format and number of times RADIUS request packets are retransmitted, have default values and can be changed based on network requirements.

The RADIUS server group settings such as the RADIUS user name format and shared key must be the same as those on the RADIUS server.

Procedure

Run system-view
The system view is displayed.
Run radius enable
The RADIUS function is enabled.

By default, the RADIUS function is disabled.
(Optional) Run radius server { dead-count dead-count [ fail-rate fail-rate-value ] | dead-interval dead-interval | dead-time dead-time [ recover-count invalid ] } ^*
The interval at which a RADIUS server alternates between Up and Down is set.
The default parameters settings are as follows:
- dead-count: 10
- dead-interval: 5 seconds
- dead-time: 3 minutes
That is, if a RADIUS server does not respond to 10 consecutive packets from the device within 5 seconds, the device considers that the RADIUS server is abnormal, and the device will try to communicate with the RADIUS server again after 3 minutes.
Run radius server group group-name
A RADIUS server group is created and the RADIUS server group view is displayed.
Run radius server { shared-key key-string | shared-key-cipher cipher-string }
The shared key is set for RADIUS servers.

By default, no shared key is set for RADIUS servers.
Run any of the following commands to configure the primary RADIUS authentication server.
- radius server authentication ip-address port [ vpn-instance vpn-instance-name | source { interface-type interface-number | ip-address ip-address } | { shared-key key-string | shared-key-cipher cipher-string } ] ^*
- radius server authentication ipv6-address port [ shared-key key-string | shared-key-cipher cipher-string ]
- radius server authentication hostname hostname port [ vpn-instance vpn-instance-name | source { interface-type interface-number | ip-address ip-address } | { shared-key key-string | shared-key-cipher cipher-string } ] ^*
By default, no primary RADIUS authentication server is configured.
(Optional) Run any of the following commands to configure the secondary RADIUS authentication server.
- radius server authentication ip-address port [ vpn-instance vpn-instance-name | source { interface-type interface-number | ip-address ip-address } | { shared-key key-string | shared-key-cipher cipher-string } ] ^* secondary
- radius server authentication ipv6-address port [ shared-key key-string | shared-key-cipher cipher-string ] secondary
- radius server authentication hostname hostname port [ vpn-instance vpn-instance-name | source { interface-type interface-number | ip-address ip-address } | { shared-key key-string | shared-key-cipher cipher-string } ] ^* secondary
By default, no secondary RADIUS authentication server is configured.
Run any of the following commands to configure the primary RADIUS accounting server.
- radius server accounting ip-address port [ vpn-instance vpn-instance-name | source { interface-type interface-number | ip-address ip-address } | { shared-key key-string | shared-key-cipher cipher-string } ] ^*
- radius server accounting ipv6-address port [ shared-key key-string | shared-key-cipher cipher-string ]
- radius server accounting hostname hostname port [ vpn-instance vpn-instance-name | source { interface-type interface-number | ip-address ip-address } | { shared-key key-string | shared-key-cipher cipher-string } ] ^*
By default, no primary RADIUS accounting server is configured.
(Optional) Run any of the following commands to configure the secondary RADIUS accounting server.
- radius server accounting ip-address port [ vpn-instance vpn-instance-name | source { interface-type interface-number | ip-address ip-address } | { shared-key key-string | shared-key-cipher cipher-string } ] ^* secondary
- radius server accounting ipv6-address port [ shared-key key-string | shared-key-cipher cipher-string ] secondary
- radius server accounting hostname hostname port [ vpn-instance vpn-instance-name | source { interface-type interface-number | ip-address ip-address } | { shared-key key-string | shared-key-cipher cipher-string } ] ^* secondary
By default, no secondary RADIUS accounting server is configured.
(Optional) Run radius server accounting retransmit retransmit-number timeout timeout-value
The number of retransmission times and timeout period are set for RADIUS accounting request packets.
(Optional) Run radius server authentication retransmit retransmit-number timeout timeout-value
The number of retransmission times and timeout period are set for RADIUS authentication request packets.
(Optional) Run radius server user-name domain-excluded
Or run radius server user-name original

The RADIUS user name format is specified.

By default, the device encapsulates the domain name in the user name when sending RADIUS packets to a RADIUS server.

If the RADIUS server does not accept the user name with the domain name, you need to run the step.
(Optional) Run radius server { retransmit retry-times | timeout time-value } ^*
The number of times that RADIUS request packets are retransmitted and timeout period are set.

The default number of retransmission times is 3 and the timeout period is 5 seconds.
(Optional) Run radius server nas-ip-address ip-address
The NAS IP address is specified for the RADIUS server group.

By default, no NAS IP address is specified for a RADIUS server group. The IP address of the interface for sending packets is used as the NAS IP address.
(Optional) Run radius server source interface interface-type interface-number
The source interface used by the device to send RADIUS packets is specified.

By default, the source interface used by the device to send RADIUS packets is not specified.
(Optional) Run mode load-balance
The working mode of RADIUS servers is changed from active/standby to load balancing.

By default, the RADIUS servers in a RADIUS server group work in active/standby mode.
(Optional) Configure RADIUS attributes.
1. Run radius server attribute translate
  The RADIUS attribute translation is enabled.
  
  By default, the RADIUS attribute translation is disabled.
2. Disable RADIUS attributes.
  - Run the radius attribute disable attribute-name { receive | send } ^* command to disable basic RADIUS attributes in request or response packets.
  - Run the radius attribute disable attribute-name { access-accept | access-request | account [ start ] } ^* command to disable basic RADIUS attributes in Access-Accept, Access-Request, or accounting packets.
  - Run the radius attribute disable attribute-name { bin string | integer integer | ip ip-address | string string } receive command to disable RADIUS attributes with the specified data type in response packets.
  By default, all RADIUS attributes are enabled.
(Optional) Run radius attribute set attribute-name attribute-value
RADIUS attribute values are set.

By default, RADIUS attribute values remain unchanged.
Run quit
The system view is displayed.
(Optional) Run radius server authorization ip-address [ vpn-instance vpn-instance-name ] { shared-key key-string | shared-key-cipher cipher-string } [ ack-reserved-interval interval ]
Or run radius server authorization ipv6-address { shared-key key-string | shared-key-cipher cipher-string } [ ack-reserved-interval interval ]

A RADIUS authorization server is configured.

By default, no RADIUS authorization server is configured.
Run commit
The configuration is committed.

Translation

简体中文

Download

Updated: 2021-09-17

Document ID: EDOC1100075347

Downloads: 100

Average rating:

This Document Applies to these Products

Related Version

Digital Signature File

Digital Signature Authentication Mode

Enterprise

Huawei Cloud

Carrier

Consumer

Corporate

Context

Procedure

Related Version

Related Documents

Digital Signature File