About This Document
Intended Audience
This document describes the concepts and configuration procedures of QoS features on the S2700 and S3700, and provides the configuration examples.
This document is intended for:
- Data configuration engineers
- Commissioning engineers
- Network monitoring engineers
- System maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol |
Description |
|---|---|
Indicates a hazard with a high level of risk which, if not avoided, will result in death or serious injury. |
|
Indicates a hazard with a medium level of risk which, if not avoided, could result in death or serious injury. |
|
Indicates a hazard with a low level of risk which, if not avoided, could 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. |
|
Supplements the important information in the main text. 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. |
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, change the password periodically.
- When you configure a password in cipher text that starts and ends with %$%$ (the password can be decrypted by the device), the password is displayed in the same manner as the configured one in the configuration file. Do not use this setting.
- Encryption algorithm
Currently, the device uses the following encryption algorithms: DES, AES, SHA-1, SHA-2, and MD5. DES and AES are reversible, and SHA-1, SHA-2, and MD5 are irreversible. The encryption algorithm depends on actual networking. If protocols are used for interconnection, the locally stored password must be reversible. It is recommended that the irreversible encryption algorithm be used for the administrator password.
- Personal data
Some personal data (such as MAC or IP addresses of terminals) 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.
- The terms mirrored port, port mirroring, traffic mirroring, and mirroing in this manual are mentioned only to describe the product's function of communication error or failure detection, and do not involve collection or processing of any personal information or communication data of users.
- Reliability design declaration
Network planning and site design must comply with reliability design principles and provide device- and solution-level protection. Device-level protection includes planning principles of dual-network and inter-board dual-link to avoid single point or single link of failure. Solution-level protection refers to a fast convergence mechanism, such as FRR and VRRP. If solution-level protection is used, ensure that the primary and backup paths do not share links or transmission devices. Otherwise, solution-level protection may fail to take effect.