No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

WLAN Product Interoperation Configuration Guide

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).
About This Document

About This Document

Purpose

This document describes how to configure interoperation between Huawei WLAN products and other authentication servers in different scenarios.

Intended Audience

This document is intended for network engineers responsible for WLAN configuration and management. You should be familiar with basic Ethernet knowledge and have extensive experience in network deployment and management.

Symbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol

Description

Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.

Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury.

Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury.

Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results.

NOTICE is used to address practices not related to personal injury.

Calls attention to important information, best practices and tips.

NOTE is used to address information not related to personal injury, equipment damage, and environment deterioration.

Command Conventions

The command conventions that may be found in this document are defined as follows.

Convention

Description

Boldface

The keywords of a command line are in boldface.

Italic

Command arguments are in italics.

[ ]

Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... }

Optional items are grouped in braces and separated by vertical bars. One item is selected.

[ x | y | ... ]

Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.

{ x | y | ... }*

Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected.

[ x | y | ... ]*

Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.

&<1-n>

The parameter before the & sign can be repeated 1 to n times.

#

A line starting with the # sign is comments.

NOTE:

The interface types, command outputs, and device models provided in this manual vary according to device configurations and may differ from the actual information.

To obtain better user experience, you are advised to set the number of columns displayed on the command line editor to 132 or higher.

Interface Numbering Conventions

Interface numbers used in this manual are examples. In device configuration, use the existing interface numbers on devices.

Security Conventions

  • Password setting

    When configuring a password, the cipher text is recommended. To ensure device security, do not disable password complexity check, and change the password periodically.

    When configuring a plaintext password, do not start and end it with %$%$, %^%#, %#%#, %@%@, or @%@%, which are considered valid ciphertext characters. The device can decrypt such as password and display the same plaintext password as that configured by the user in the configuration file. Ciphertext passwords starting and ending with %$%$, %^%#, %#%#, %@%@, or @%@% are valid. However, ciphertext passwords for different features are not interchangeable. For example, the ciphertext password generated for Authentication, Authorization, Accounting (AAA) cannot be configured for other features.

  • Encryption algorithm

    Currently, the device uses the following encryption algorithms: DES, 3DES, AES, RSA, SHA1, SHA-2, MD5 and SMS4. The encryption algorithm depends on the applicable scenario. Use the recommended encryption algorithm; otherwise, security defense requirements may be not met.

    • For the symmetrical encryption algorithm, use AES with the key of 128 bits or more.
    • For the asymmetrical encryption algorithm, use RSA with the key of 2048 bits or more.
    • For the hash algorithm, use SHA2 with the key of 256 bits or more.
    • For the HMAC algorithm, use HMAC-SHA2.
    • The encryption algorithms DES/3DES/RSA (RSA-1024 or lower)/MD5 (in digital signature scenarios and password encryption)/SHA1 (in digital signature scenarios) have a low security, which may bring security risks. If protocols allowed, using more secure encryption algorithms, such as AES/RSA (RSA-2048 or higher)/SHA2/HMAC-SHA2, is recommended.
    • SHA2 is irreversible encryption algorithm. The irreversible encryption algorithm must be used for the administrator password.
  • Personal data

    Some personal data (such as the MAC or IP addresses of users) may be obtained or used during operation or fault location of your purchased products, services, features, so you have an obligation to make privacy policies and take measures according to the applicable law of the country to protect personal data.

Configuration Conventions

Large-scale or batch service configuration using scripts may cause high CPU usage, preventing the system from processing regular services.

Translation
简体中文
Download
Updated: 2018-07-26

Document ID: EDOC1000113779

Views: 6238

Downloads: 1263

Average rating:
This Document Applies to these Products
Related Documents
Share
Previous Next