14.1 AAA
14.1.1 AAA Schemes
Context
Authentication, Authorization, and Accounting (AAA) provides a management mechanism for network security.
- Authentication: determines the users who can access the network. Authentication modes are as follows:
Non-authentication: Users are trusted without the check on their validity. This mode is rarely used.
Local authentication: Information about users is configured on a network access server (NAS). Local authentication features fast processing and low operation cost, whereas the amount of information that can be stored is limited by the hardware capacity of the device.
Remote authentication: Information about users is configured on an authentication server. Remote authentication supports the Remote Authentication Dial In User Service (RADIUS) protocol and the Huawei Terminal Access Controller Access Control System (HWTACACS) protocol.
- Authorization: authorizes users to use particular services. Authorization modes are as follows:
Non-authorization: Users are not authorized.
Local authorization: Users are authorized based on related attributes of the local user accounts configured on the NAS.
HWTACACS authorization: A HWTACACS server authorizes users.
if-authenticated authorization: Users are authorized after the users pass the authentication in either local or remote authentication mode.
RADIUS authorization: Users pass the RADIUS authorization upon passing the RADIUS authentication. RADIUS integrates authentication and authorization. Therefore, RADIUS authorization cannot be performed separately.
- Accounting: records the use of network resources by users. Accounting modes are as following:
Non-accounting: Users are not charged.
Remote accounting: A RADIUS server or a HWTACACS server performs remote accounting.
Procedure
- Authentication scheme
- Creating an authentication scheme
- Modifying an authentication scheme
- Choose .
- Select an authentication scheme in the Authentication Scheme area, and click
. - In the Modify Authentication Scheme dialog box that is displayed, modify the parameters. The parameter Name cannot be modified.
- Click OK.
- Deleting an authentication scheme
- Choose .
- Select the check box of an authentication scheme in the Authentication Scheme area, and click Delete.
- In the dialog box that is displayed, click OK.
- Authorization scheme
- Creating an authorization scheme
- Modifying an authorization scheme
- Choose .
- Select an authorization scheme in the Authorization Scheme area, and click
. - In the Modify Authorization Scheme dialog box that is displayed, modify the parameters. The parameter Name cannot be modified.
- Click OK.
- Deleting an authorization scheme
- Choose .
- Select the check box of an authorization scheme in the Authorization Scheme area, and click Delete.
- In the dialog box that is displayed, click OK.
- Accounting scheme
- Creating an accounting scheme
- Modifying an accounting scheme
- Choose .
- Select an accounting scheme in the Accounting Scheme area, and click
. - In the Modify Accounting Scheme dialog box that is displayed, modify the parameters. The parameter Name cannot be modified.
- Click OK.
- Deleting an accounting scheme
- Choose .
- Select the check box of an accounting scheme in the Accounting Scheme area, and click Delete.
- In the dialog box that is displayed, click OK.
14.1.2 RADIUS Setting
Context
RADIUS protects a network from unauthorized access. It is often used on the networks that require high security and remote user access control.
Procedure
- RADIUS server template
- Creating a RADIUS server template
- Modifying a RADIUS server template
- Choose .
- In the RADIUS Server Template area, select a RADIUS server template, and click
. - In the Modify RADIUS Server Template dialog box that is displayed, modify the parameters. The parameter Template name cannot be modified.
- Click OK.
- Deleting a RADIUS server template
- Choose .
- In the RADIUS Server Template area, select the check box of a RADIUS server template, and click Delete.
- In the dialog box that is displayed, click OK.
- Authentication/Accounting server
- Creating an authentication or accounting server
- Modifying an authentication or accounting server
- Choose .
- In the Authentication/Accounting Server area, select an authentication or accounting server, and click
. - In the Modify Authentication/Accounting Server dialog box that is displayed, modify the parameters. The parameters Template name and Server type cannot be modified.
- Click OK.
- Deleting an authentication or accounting server
- Choose .
- In the Authentication/Accounting Server area, select the check box of an authentication or accounting server, and click Delete.
- In the dialog box that is displayed, click OK.
- Authorization server
- Creating an authorization server
- Modifying an authorization server
- Choose .
- In the Authorization Server area, select an authorization server, and click
. - In the Modify Authorization Server dialog box that is displayed, modify the parameters. The parameters Authorization server IP address cannot be modified.
- Click OK.
- Deleting an authorization server
- Choose .
- In the Authorization Server area, select the check box of an authorization server, and click Delete.
- In the dialog box that is displayed, click OK.
14.1.3 HWTACACS Setting
Context
HWTACACS prevents unauthorized users from attacking a network and supports command-line authorization. Compared with RADIUS, HWTACACS is more reliable in transmission and encryption, and is more suitable for security control.
Procedure
- HWTACACS global setting
- HWTACACS server template
- Creating a HWTACACS server template
- Modifying a HWTACACS server template
- Choose .
- In the HWTACACS Server Template area, select the HWTACACS server template, and click
. - In the Modify HWTACACS Server Template dialog box that is displayed, modify the parameters. The parameter Template name cannot be modified.
- Click OK.
- Deleting a HWTACACS server template
- Choose .
- In the HWTACACS Server Template area, select the check box of the HWTACACS server template, and click Delete.
- In the dialog box that is displayed, click OK.
- Authentication/Authorization/Accounting server
- Creating an authentication, authorization, or accounting server
- Modifying an authentication, authorization, or accounting server
- Choose .
- In the Authentication/Authorization/Accounting Server area, select an authentication, authorization, or accounting server, and click
. - In the Modify Authentication/Authorization/Accounting Server dialog box that is displayed, modify the parameters. The parameters Template name and Server typecannot be modified.
- Click OK.
- Deleting an authentication, authorization, or accounting server
- Choose .
- In the Authentication/Authorization/Accounting Server area, select the check box of an authentication, authorization, or accounting server, and click Delete.
- In the dialog box that is displayed, click OK.
14.1.4 Domain Management
Context
The created authentication, authorization, and accounting schemes take effect only after being applied to a domain.
Procedure
- Creating a domain
- Modify a domain
- Choose .
- Select a domain in the Domains area, and click
. - In the Modify Domain dialog box that is displayed, modify the parameters. The parameter Domain name cannot be modified.
- Click OK.
- Deleting a domain
- Choose .
- Select the check box of a domain in the Domains area, and click Delete.
- In the dialog box that is displayed, click OK.
14.1.5 User Management
Context
You need to create a local user account and configure attributes of the local user so that the administrator can authenticate and authorize users who log in based on the local user information.
Procedure
- Create a user.
- Modify a user
- Choose .
- Select a domain in the User Management area and click
. - In the Modify User dialog box that is displayed, modify the parameters.
- Click OK.
- Deleting a user
- Choose .
- Select the check box of a user in the User Management area, and click Delete.
- In the dialog box that is displayed, click OK.
14.2 ACL Settings
14.2.1 Basic ACL
14.2.2 Advanced ACL
14.2.3 User ACL
14.2.4 Time Range
Context
To start services or functions periodically or in a specified period of time, you can set a time range for ACL rules.
Procedure
- Creating a time range
- Modifying a time range
- Choose .
- Click
next to a time range. - In the Modify Time Range dialog box that is displayed, modify parameters listed in Table 14-15. The parameter Time range name cannot be modified. To delete a validity time range, click
in the Time Range Has Been Added area. - Click OK.
- Deleting a time range
- Choose .
- Select the check box of a validity period and click Delete.
- In the dialog box that is displayed, click OK.
14.3 User Group
Context
- A user group can be bound to one or more ACLs, so users' data packets are filtered based on the bound ACL.
- A user group can be bound to one QoS profile, so the bandwidth used by users in the user group is restricted based on the bound QoS profile. To configure a QoS profile, see 13.1 QoS Profile.
- Isolation flags can be set in user groups to isolate users in the same group or in different groups. The inter-group isolation flag isolates users in the same group, and the intra-group isolation flat isolates users in a group from users in other groups.
- User VLANs can be configured in a user group. Users can visit resources in the same VLAN.
The administrator configures a user group using the delivered user group name.
Procedure
- Creating a user group
- Modifying a user group
- Choose .
- In User Group List area, click
corresponding to a user group to be modified. - In the Modify User Group dialog box that is displayed, set parameters described in Table 14-16.
- Deleting a user group
- Choose .
- In the User Group List area, select a user group, and click Delete.
- In the dialog box that is displayed, click OK. If the user group is removed from the user group list, the user group is deleted.
14.4 WIDS Configuration
14.4.1 WIDS Configuration
Context
WIDS: detects rouge APs, bridges, STAs, ad-hoc networks, and APs using the same working channel.
WIPS: disconnects authorized users from bogus APs and disconnects unauthorized STAs and ad-hoc networks from APs.
Wireless Intrusion Detection System (WIDS) supports attack detection and can detect flood attacks, weak IV attacks, spoofing attacks, and brude force cracking of the WPA/WPA2/WAPI pre-shared key and the WEP shared key, and notify the network administrator of insecurity factors using logs, statistics, and alarms. When detecting a device that initiates flood attacks or brude force cracking, the AC adds the device to the blacklist and rejects packets from the device within the blacklist timeout period.
Procedure
- Querying the status of an AP configured with WIDS
- Configuring WIDS for an AP
- Modifying WIDS configurations of an AP
- Choose .
- In the WIDS Configuration List area, click
corresponding to an AP to be modified. - In the Modify WIDS Configuration dialog box that is displayed, set parameters described in Table 14-17.
- Click OK.
- Disabling WIDS from an AP
14.4.2 SSID Whitelist
Context
SSIDs in the whitelist can be used only by the AC. If the rouge AP uses the SSIDs, the monitor AP does not counter the AP although SSIDs are countered.
Procedure
- Querying an SSID whitelist
- Creating an SSID whitelist
- Choose .
- In the SSID Whitelist area, click Create. In the Create SSID Whitelist dialog box that is displayed, set SSID.
- Click OK. If the SSID is displayed in the SSID whitelist, the SSID whitelist is created.
- Modifying an SSID whitelist
- Choose .
- In the SSID Whitelist area, click
corresponding to an SSID to be modified. - In the Modify SSID Whitelist dialog box that is displayed, change the SSID.
- Click OK.
- Deleting an SSID whitelist
14.4.3 Rogue Device
Context
After device detection is enabled, you can view information about rogue devices and historical records. All rouge devices are recorded in the historical records.
Procedure
- Viewing information about a rouge device
- Deleting information about a rouge device
- Choose .
- In the Rogue Device List area, select a rogue device, and click Delete.
- Viewing historical records of a rouge device
- Choose .
- In the Historical Records of Rogue Devices area, set Search, enter a keyword, and click Go. Table 14-18 describes search items of a rouge device.
- Deleting historical records of a rouge device
- Choose .
- In the Historical Records of Rogue Devices area, select a rogue device, and click Delete.
14.4.5 Attack Records
Context
After attack detection is enabled, information about a detected attack device will be saved in the attack detection list. If the attack device starts no more attacks, the device is removed from the attack detection list. This attack is added to the attack record list. You can check or delete entries in the attack detection list and attack record list.
Procedure
- Querying attack detection list
- Deleting attack detection list
- Choose .
- In the Attack Detection List area, click Clear. In the dialog box that is displayed, click OK. All attack records are deleted.
- Querying attack records
- Choose .
- In the Attack Records area, set Search, enter a keyword, and click Go. Table 14-20describes search items.
- Deleting attack records
- Choose .
- In the Attack Records area, click Clear. In the dialog box that is displayed, click OK. All attack records are deleted.
14.4.6 Dynamic Blacklist
Context
After attack detection and dynamic blacklist are enabled, an AP adds devices that initiate attacks to the dynamic blacklist and rejects packets from these devices within the blacklist timeout period.
Devices that initiate flood attacks and brute force cracking of the WPA/WPA2/WAPI pre-shared key and the WEP shared key can be added to the dynamic blacklist.
14.5 Portal Authentication
14.5.1 Global Portal Authentication Configuration
Context
Portal authentication is also referred to as Web authentication. When a user opens a browser for the first time and enters any website address, the user is forcibly redirected to an authentication page of a Portal server and can access network resources only after being authenticated.
The Portal protocol is based on a client/server structure and uses the User Datagram Protocol (UDP) as the transmission protocol. The Portal protocol is used in information exchange between the Portal server and other devices. In Portal authentication, the Portal protocol is used in communication between the Portal server and a device that is used as a client.
The administrator can set the maximum number of Portal authentication users that can access a device and the offline detection period for the users. If a user does not respond within the detection period, the device considers that the user is offline and release the occupied resources.
14.5.2 External Portal Server
Context
The Portal server is classified as either the external Portal server or the built-in Portal server. The external Portal server has independent hardware, while the built-in Portal server is an entity embedded in the access device (that is, functions of the Portal server are implemented by the access device).
During external Portal authentication, you must configure parameters for the Portal server (for example, the IP address for the Portal server) to ensure smooth communication between the device and the Portal server.
Procedure
- Querying an authentication server
- Creating an authentication server
- Modifying an authentication server
- Choose .
- In the Portal Servers area, click
corresponding to an authentication server. - In the Modify Portal Server dialog box that is displayed, set parameters described in Table 14-22.
- Click OK.
- Deleting an authentication server
14.5.3 Built-in Portal Server
Context
The Portal server is classified as either the external Portal server or the built-in Portal server. The external Portal server has independent hardware, while the built-in Portal server is an entity embedded in the access device (that is, functions of the Portal server are implemented by the access device).
During the built-in Portal server configuration process, to ensure that the server can provide the web authentication service, set parameters such as SSL policy, Port, and Web page file.
Procedure
- Choose .
- On the Built-in Portal Server tab page, set parameters described in Table 14-24, and click Apply.Table 14-24 Built-in Portal server parameters
Parameter
Description
Portal server IP
IP address of the Portal server. Users are then redirected to the Portal server if they enter URLs that are not located in the free IP subnet.
NOTE:The IP address assigned to the built-in Portal server must have a reachable route to the user.
The built-in Portal server cannot use the gateway IP address of the device interface connected to clients.
It is recommended that a loopback interface address be assigned to the built-in Portal server because the loopback interface is stable. Additionally, packets destined for loopback interfaces are not sent to other interfaces on the network; therefore, system performance is not deteriorated even if many users request to go online.
SSL policy
SSL policy applied to HTTPS services provided by the Portal server.
Port
Port that provides the authentication service on the Portal server.
Authentication mode
Authentication mode including PAP and CHAP. You are advised to use the CHAP with high security.
Web page file
File in .zip format. The file contains web pages that users access during authentication.
Maximum number of users
Maximum number of users that can access the Portal server.
Acceptable Use Policy(in HTML format)
The administrator can edit the login page used for user authentication to customize a disclaimer page. The hyperlink Acceptable Use Policy will be displayed on the login page. You can click the link to visit the disclaimer page.
Portal usage guideline(in HTML format)
There is a blank area on the login page of the built-in Portal server. You can customize the display contents on the login page.
14.5.4 Portal Free Rule
Context
You can set portal free rules for portal authentication users so that the users can access specified network resources without being authenticated or when the users fail authentication.
Procedure
- Searching a portal free rule
- Creating a portal free rule
- Modifying a portal free rule
- Choose .
- In the Portal Free Rule List area, click
corresponding to a portal free rule. - In the Modify Portal Free Rule dialog box that is displayed, set parameters described in Table 14-25.
- Click OK.
- Deleting a portal free rule
14.6 802.1X Authentication
14.6.1 Global 802.1X Authentication Configuration
Context
The IEEE 802.1X standard (802.1X) is an interface-based network access control protocol. The 802.1X configuration takes effect on an interface only after 802.1X authentication is enabled globally and on the interface.
Procedure
- Choose .
- On the Global 802.1X Authentication Configuration tab page, set parameters described in Table 14-26, and click Apply.
To reset parameters, click Reset.
Table 14-26 Global 802.1X authentication configuration parametersParameter
Description
Global 802.1X authentication
Global 802.1X authentication enabled or disabled.
Silence function
Silence function enabled or disabled.
After the silence function is enabled, when the number of times that a user fails 802.1X authentication reaches the maximum number, the device makes the user to enter the silence state, and during the silence period, the device discards the 802.1X authentication requests from the user. This prevents the impact of frequent user authentications on the system.
Authentication failure count
After the silence function is enabled, a user enters the silence state when the number of failed authentication times exceeds the value of this parameter.
Retransmission count
If a user does not respond in a specified period after the device sends an authentication request to the user, the device sends the authentication request again. If the device fails to receive the response from the offline user when the number of sent authentication request packets reaches the limit, the device stops initiating authentication. The authentication fails. If the device still fails to receive the response from the online user when the number of sent handshake request packets reaches the limit, the device considers that the user is offline, and sets the user to offline state.
Repeated authentication requests occupy a lot of system resources. You can set the maximum number of times according to user requirements and device resources. The default value is recommended.
STA response timeout period (s)
If the device fails to receive the response from the offline user when the number of sent authentication request packets reaches the limit, the device stops initiating authentication. The authentication fails.
Reauthentication interval (s)
After reauthentication is enabled, the device sends user's authentication information to the authentication server at a specified interval. If the user's authentication information does not change on the authentication server, the user is online normally. If the authentication information has been changed, the user is forced to go offline. The user then must be re-authenticated according to the changed authentication information.
Authentication request interval (s)
- If a client does not respond in a specified period after the client initiates authentication, the device sends an authentication request packet to the client.
- To authenticate the clients that cannot initiate authentication, the device sends authentication packets through the interface enabled with 802.1X authentication to the clients at a specified interval.
Server response timeout period (s)
If the authentication server does not respond to an authentication request within the timeout interval, the device retransmits the authentication request to the authentication server.
Silence time (s)
Silence duration of a 802.1X user.
14.7 MAC Authentication
14.7.1 Global MAC Authentication Configuration
Context
MAC address authentication controls a user's network access right based on the user's access interface and MAC address. The user does not need to install any client software. The user device MAC address is used as the user name and password. When detecting the user's MAC address the first time, the network access device starts authenticating the user.
The MAC configuration takes effect on an interface only after MAC authentication is enabled globally and on the interface.
Procedure
- Choose .
- On the Global MAC Authentication Configuration tab page, set parameters described in Table 14-27, and click Apply.
To reset parameters, click Reset.
Table 14-27 Global MAC authentication parametersParameter
Description
Global MAC authentication
Global MAC authentication enabled or disabled.
Authentication domain
When the MAC address without a domain name is used as the user name in MAC address authentication, the user is authenticated in a default domain if the administrator does not configure an authentication domain.
Before configuring a domain for MAC address authentication, ensure that the domain has been configured.
User name format
- MAC address: The user's MAC address is used as the user name and password during authentication.
- Fixed: Regardless of users' MAC addresses, all users have a fixed name and password specified by the administrator as an identity for authentication. Many users may be authenticated on the same interface. In this case, all users requiring MAC address authentication on the interface use the same fixed user name, and the server must only configure one user account to authenticate all users. This is applicable to a network environment with reliable access clients.
NOTE:When local authentication is used, a fixed user name must be used for MAC address authentication.
If configured in the interface page and this page at the same time, the user name format configured in the interface page has higher priority.
MAC address type
In MAC address authentication, the device sends the user's MAC address as the user name and password to the authentication server. You can determine whether the MAC address contains a hyphen (-).- Hyphenated: Indicates that the MAC address with hyphens is used as the user name, for example, 0005-e01c-02e3.
- Unhyphenated: Indicates that the MAC address without hyphens is used as the user name, for example, 0005e01c02e3.
User name
Fixed user name used for MAC address authentication.
Password
Password used for MAC address authentication.
Confirm password
Confirm password used for MAC address authentication.
Silence time(s)
Specifies the value of the quiet timer. If a user fails authentication, the device does not process the user's authentication requests until the quiet timer expires. During the quiet period, the device does not process the user's authentication requests.
Server response timeout period(s)
If the authentication server does not respond to an authentication request within the timeout period, the device retransmits the authentication request to the authentication server.
Reauthentication interval(s)
After reauthentication is enabled, the device sends user's authentication information to the authentication server at a specified interval. If the user's authentication information does not change on the authentication server, the user is online normally. If the authentication information has been changed, the user is forced to go offline. The user then must be re-authenticated according to the changed authentication information.
14.8 SSL
Context
A device supports server Secure Sockets Layer (SSL) policies and client SSL policies.
To use a device as an SSL server, configure a server SSL policy on the device. During an SSL handshake, the device uses SSL parameters in the server SSL policy to negotiate session parameters with an SSL client. After the handshake is complete, the device establishes a session with the client.
To use a device as an SSL client, configure a client SSL policy on the device. During an SSL handshake, the device uses SSL parameters in the client SSL policy to negotiate session parameters with the SSL server. After the handshake is complete, the device establishes a session with the server.
Procedure
- Creating an SSL policy
- Creating a server SSL policy
Access the SSL tab page.
Click Create and set parameters in the Create SSL Policy dialog box that is displayed. Set SSL policy type to Server. Table 14-28 describes other parameters.

Click OK. A server SSL policy is added to the SSL policy list.
Table 14-28 Server SSL policy parametersParameter
Description
SSL policy name
Name of an SSL policy, which is case-sensitive.
PKI domain
Name of a PKI domain. For details about the PKI domain configuration, see 14.9 PKI.
Maximum session count
Maximum number of sessions that can be saved on the SSL server.
Session timeout interval(s)
Timeout period of a saved session.
Supported cipher suite
Cipher suite supported by the server SSL policy.
- Creating a client SSL policy
Access the SSL tab page.
Choose .
Click Create and set parameters in the Create SSL Policy dialog box that is displayed. Set SSL policy type to Client. Table 14-29 describes other parameters.

Click OK. A client SSL policy is added to the SSL policy list.
Table 14-29 Client SSL policy parametersParameter
Description
SSL policy name
Name of an SSL policy, which is case-sensitive.
SSL server identity authentication
Whether to enable SSL server identity authentication.
PKI domain
Name of a PKI domain. For details about the PKI domain configuration, see 14.9 PKI.
SSL version
SSL protocol version.
Preferred cipher suite
Cipher suite used by the client SSL policy.
- Creating a server SSL policy
- Modifying an SSL policy
- Choose .
- Click
of an SSL policy in the SSL Configuration List area. - In the Modify SSL Policy dialog box that is displayed, modify parameters listed in Table 14-28 or Table 14-29. The parameter SSL policy name and SSL policy type cannot be modified.
- Click OK.
- Deleting an SSL policy
- Choose .
- Select an SSL policy and click Delete. In the dialog box that is displayed, click OK.
14.9 PKI
14.9.1 PKI Entity
Context
A certificate binds a public key to a set of information that uniquely identifies a public key interface (PKI) entity. The parameters of an entity indicate the identity information of the entity. A Certificate Authority (CA) uniquely identifies a certificate applicant based on identity information provided by an entity.
14.9.2 PKI Domain
Context
Before an entity applies for a certificate, some enrollment information must be configured. The collection of the enrollment information is called the PKI domain of an entity.
Procedure
- Creating a PKI domain
- Modifying a PKI domain
- Choose .
- Select a PKI domain in the PKI Domain Information area, and click
. - In the Modify PKI Domain dialog box that is displayed, modify the parameters. The parameter PKI domain name cannot be modified.
- Click OK.
- Deleting a PKI domain
- Choose .
- Select the check box of a PKI domain and click Delete.
- In the dialog box that is displayed, click OK.
NOTE:A PKI domain is referenced by the SSL policy cannot be deleted. To delete the PKI domain, remove the PKI domain from the SSL policy first. For details on how to modify or delete an SSL policy, see 14.8 SSL.
14.10 Security Protection
14.10.1 ACL Filtering
Context
An ACL is a set of rules that can only differentiate packets.
After ACLs are configured, you can configure ACL filtering to apply the ACLs so that packets are filtered.
Procedure
- Creating an ACL filtering rule
- Modifying an ACL filtering rule
- Choose .
- Click
of an ACL filtering rule. - In the Modify ACL Filtering dialog box that is displayed, modify parameters described in Table 14-32.
- Click OK.
- Deleting an ACL filtering rule
- Choose .
- Select the check box of an ACL filtering rule and click Delete.
- In the dialog box that is displayed, click OK.




















. To delete a basic ACL rule, click
.









, you can create or delete a QoS profile. Select a QoS profile in the












. To delete an IP address, select an IP address and click













