HUAWEI NetEngine9000

V800R022C00SPC600

Configuration Guide

Issue 01
Date 2022-10-31

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2022. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: https://www.huawei.com
Email: [email protected]

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. i

HUAWEI NetEngine9000
Configuration Guide Contents

Contents

1 Configuration............................................................................................................................1
1.1 Interface and Data Link........................................................................................................................................................ 1
1.1.1 About This Document........................................................................................................................................................ 1
1.1.2 Interface Management Configuration.......................................................................................................................... 5
1.1.2.1 Overview of Interface Management..........................................................................................................................5
1.1.2.2 Configuration Precautions for Interface_Management.................................................................................... 12
1.1.2.3 Interface Basics Configuration................................................................................................................................... 12
1.1.2.3.1 Entering the Interface View.................................................................................................................................... 13
1.1.2.3.2 (Optional) Setting Interface Parameters............................................................................................................ 13
1.1.2.3.3 Enabling an Interface................................................................................................................................................ 17
1.1.2.3.4 (Optional) Configuring a Device to Send a Trap Message to an NMS When an Interface Physical
Status Changes............................................................................................................................................................................. 17
1.1.2.3.5 (Optional) Configuring IPv4 and IPv6 Traffic Statistics Collection on a Main Interface................... 18
1.1.2.3.6 (Optional) Configuring Power Locking and Gain Locking for an Optical Amplifier Module...........18
1.1.2.3.7 (Optional) Configuring an Interface Splitting Mode......................................................................................19
1.1.2.3.8 Verifying the Configuration.....................................................................................................................................19
1.1.2.4 Configuring the Physical Link Detection Function............................................................................................. 20
1.1.2.4.1 Configuring the Alarm Function for CRC Errors, SDH Errors, Input Errors, Output Errors, or
Optical Module Power Exceptions......................................................................................................................................... 20
1.1.2.4.2 Configuring the Alarm Function for Pause-Frame Errors Received on an Interface........................... 23
1.1.2.4.3 Configuring the Alarm Function in Case the Number of SDH B1 or SDH B2 Error Packets That an
Interface Receives Exceeds an Alarm Threshold............................................................................................................... 24
1.1.2.4.4 Configuring the Alarm Function in Case the Number of Bytes of Error Packets That an Interface
Receives Exceeds an Alarm Threshold.................................................................................................................................. 24
1.1.2.4.5 Verifying the Configuration.....................................................................................................................................25
1.1.2.5 Configuring MAC Accounting.................................................................................................................................... 26
1.1.2.6 Configuring Strict Filter for EVC Sub-Interfaces.................................................................................................. 27
1.1.2.7 Enabling the Signal Sending Delay Function....................................................................................................... 28
1.1.2.8 Enabling or Disabling the Optical Module Laser................................................................................................ 29
1.1.2.8.1 Disabling the Optical Module Laser.................................................................................................................... 30
1.1.2.8.2 (Optional) Enabling the Optical Module Laser................................................................................................30
1.1.2.8.3 Verifying the Configuration of Enabling or Disabling the Optical Module Laser................................ 31
1.1.2.9 Enabling the Optical Module Alarm Threshold Standardization Function................................................ 32
1.1.2.10 Disabling the Optical Module Alarm Function................................................................................................. 32

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. ii

HUAWEI NetEngine9000
Configuration Guide Contents

1.1.2.11 Managing Non-Huawei-Certified Optical Modules.........................................................................................33

1.1.2.12 Configuring the Control-Flap Function................................................................................................................ 34
1.1.2.13 Logical Interface Configuration.............................................................................................................................. 36
1.1.2.13.1 Creating a Global-VE interface............................................................................................................................ 37
1.1.2.13.2 Configuring a Channelized Sub-interface........................................................................................................ 37
1.1.2.13.3 Creating a Loopback Interface and Configuring an IP Address for It.................................................... 38
1.1.2.13.4 Entering the NULL Interface View......................................................................................................................39
1.1.2.13.5 Verifying the Configuration.................................................................................................................................. 39
1.1.2.14 FlexE Interface Configuration.................................................................................................................................. 40
1.1.2.14.1 Activating the FlexE Interface License on a Board....................................................................................... 40
1.1.2.14.2 Configuring a Standard Ethernet Interface to Work in FlexE Mode...................................................... 41
1.1.2.14.3 Configuring a PHY Number for a FlexE Physical Interface........................................................................ 42
1.1.2.14.4 Creating a FlexE Group and Binding a FlexE Physical Interface to It.....................................................42
1.1.2.14.5 Configuring a Number for a FlexE Group........................................................................................................43
1.1.2.14.6 (Optional) Configuring a Sub-timeslot Granularity for a FlexE Card.................................................... 44
1.1.2.14.7 (Optional) Configuring a Mode for a FlexE Card......................................................................................... 44
1.1.2.14.8 Creating a FlexE Client and Configuring an ID and Bandwidth for It....................................................45
1.1.2.14.9 Adding a FlexE NE in an Ethernet Service Scenario..................................................................................... 48
1.1.2.14.10 Adding a FlexE or Ethernet NE in a FlexE Service Scenario.................................................................... 50
1.1.2.14.11 (Optional) Configuring a Time Synchronization Mode for a FlexE Physical Interface..................53
1.1.2.14.12 Verifying the Configuration................................................................................................................................ 54
1.1.2.15 Interface Group Configuration................................................................................................................................ 55
1.1.2.16 Configuring an Interface Monitoring Group...................................................................................................... 56
1.1.2.17 Maintaining Interfaces............................................................................................................................................... 59
1.1.2.17.1 Clearing Interface Statistics.................................................................................................................................. 59
1.1.2.17.2 Monitoring Interface Information...................................................................................................................... 59
1.1.2.18 Configuration Examples for Interface Management.......................................................................................60
1.1.2.18.1 Example for Managing Interfaces...................................................................................................................... 60
1.1.2.18.2 Example for Configuring FlexE Interfaces........................................................................................................61
1.1.3 Port Extension Configuration........................................................................................................................................ 67
1.1.3.1 Configuration Precautions for Port Extension...................................................................................................... 68
1.1.3.2 Establishing a Port Extension System..................................................................................................................... 73
1.1.3.2.1 Configuring Basic Master Functions.................................................................................................................... 73
1.1.3.2.2 Configuring Basic AP Functions on a Master....................................................................................................75
1.1.3.2.3 Configuring an Authentication Scheme for a Port Extension System...................................................... 76
1.1.3.2.4 Configuring Internal Communication Interfaces............................................................................................. 78
1.1.3.2.5 Configuring a Port Extension Interface............................................................................................................... 81
1.1.3.2.6 (Optional) Configuring Route Import Between the Port Extension System and External Network
............................................................................................................................................................................................................ 82
1.1.3.2.7 Verifying the Configuration of Establishing a Port Extension System..................................................... 83
1.1.3.3 Upgrading and Managing an AP.............................................................................................................................. 84
1.1.3.3.1 Using a Software Package to Upgrade an AP.................................................................................................. 85
1.1.3.3.2 Installing a Patch........................................................................................................................................................ 86

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. iii

HUAWEI NetEngine9000
Configuration Guide Contents

1.1.3.3.3 Restarting an AP......................................................................................................................................................... 87

1.1.3.3.4 Configuring APs to Communicate with an NMS over SNMP...................................................................... 88
1.1.3.3.5 Configuring APs to Send Information to a Syslog Server............................................................................. 91
1.1.3.3.6 Configuring a Time Format for AP Information.............................................................................................. 92
1.1.3.3.7 Configuring an AP Information Output Mode................................................................................................. 93
1.1.3.3.8 Setting an Interval for Collecting Traffic Statistics on an AP Interface................................................... 94
1.1.3.3.9 Configuring Alarm Thresholds for Bandwidth Usage on an AP Interface.............................................. 95
1.1.3.4 Maintaining the Port Extension System................................................................................................................. 96
1.1.3.4.1 Clearing Statistics About a Port Extension Interface......................................................................................96
1.1.3.5 Configuration Examples for Port Extension.......................................................................................................... 97
1.1.3.5.1 Example for Configuring a Port Extension System......................................................................................... 97
1.1.4 Transmission Alarm Customization and Suppression Configuration ........................................................... 107
1.1.4.1 Overview of Transmission Alarm Customization and Suppression............................................................ 107
1.1.4.2 Configuration Precautions for Transmission Alarm Customization and Suppression.......................... 108
1.1.4.3 Configuring Transmission Alarm Customization...............................................................................................108
1.1.4.3.1 Configuring the Types of Alarms that Affect the Physical Status of Interfaces................................. 109
1.1.4.3.2 Verifying the Transmission Alarm Customization Configuration.............................................................110
1.1.4.4 Configuring Transmission Alarm Filtering Intervals........................................................................................ 111
1.1.4.5 Configuring Transmission Alarm Suppression................................................................................................... 113
1.1.4.6 Maintaining Transmission Alarm Customization and Suppression ........................................................... 114
1.1.4.6.1 Checking Bit Error Rates........................................................................................................................................ 114
1.1.4.6.2 Clearing the Information About Transmission Alarms ...............................................................................114

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. iv

HUAWEI NetEngine9000
Configuration Guide Figures

Figures

Figure 1-1 MAC accounting usage scenario......................................................................................................... 26

Figure 1-2 Adding a FlexE NE to a live network running Ethernet services..............................................48
Figure 1-3 Adding a FlexE NE to a live network running FlexE services.................................................... 50
Figure 1-4 Adding an Ethernet NE to a live network running FlexE services........................................... 51
Figure 1-5 Typical application of an interface monitoring group................................................................. 57
Figure 1-6 Networking diagram for configuring FlexE interfaces.................................................................62
Figure 1-7 Typical networking for port extension.............................................................................................. 68
Figure 1-8 Typical networking of a port extension system............................................................................. 97

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. v

HUAWEI NetEngine9000
Configuration Guide Tables

Tables

Table 1-1 Commands, views, and prompts of physical interfaces supported by the NE9000............... 6
Table 1-2 Commands, views, and prompts of logical interfaces..................................................................... 8
Table 1-3 Flapping control modes............................................................................................................................11
Table 1-4 Feature requirements................................................................................................................................ 12
Table 1-5 Configurable parameters of an interface...........................................................................................14
Table 1-6 Setting interface parameters.................................................................................................................. 15
Table 1-7 Logical interface list.................................................................................................................................. 36
Table 1-8 Numbers of physical ports that can be added to the same group and port-id value
ranges for different subcard models........................................................................................................................ 45
Table 1-9 Feature requirements................................................................................................................................ 68
Table 1-10 Elements of the date format................................................................................................................93

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. vi

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

1 Configuration

1.1 Interface and Data Link

1.1.1 About This Document

Purpose
This document provides the basic concepts, configuration procedures, and
configuration examples in different application scenarios of the Interface
Management feature.

Licensing Requirements
For details about the License, see the License Guide.
● Carrier user: License Usage Guide
● Enterprise users: License Usage Guide

Related Version
The following table lists the product version related to this document.

Product Name Version

HUAWEI NetEngine9000 V800R022C00SPC600

iMaster NCE-IP V100R022C00SPC100

Intended Audience
This document is intended for:
● Data configuration engineers

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 1

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● Commissioning engineers
● Network monitoring engineers
● System maintenance engineers

Security Declaration
● Notice on Limited Command Permission
The documentation describes commands when you use Huawei devices and
make network deployment and maintenance. The interfaces and commands
for production, manufacturing, repair for returned products are not described
here.
If some advanced commands and compatible commands for engineering or
fault location are incorrectly used, exceptions may occur or services may be
interrupted. It is recommended that the advanced commands be used by
engineers with high rights. If necessary, you can apply to Huawei for the
permissions to use advanced commands.
● Encryption algorithm declaration
The encryption algorithms DES/3DES/RSA (with a key length of less than
2048 bits)/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 (with a key length of at least 2048 bits)/SHA2/HMAC-SHA2
is recommended.
For security purposes, insecure protocols Telnet, FTP, and TFTP as well as
weak security algorithms in BGP, LDP, PECP, MSDP, DCN, TCP-AO, MSTP, VRRP,
E-Trunk, AAA, IPsec, BFD, QX, port extension, SSH, SNMP, IS-IS, RIP, SSL, NTP,
OSPF, and keychain features are not recommended. To use such weak security
algorithms, run the undo crypto weak-algorithm disable command to enable
the weak security algorithm function. For details, see the Configuration Guide.
● Password configuration declaration
– When the password encryption mode is cipher, avoid setting both the
start and end characters of a password to "%^%#". This causes the
password to be displayed directly in the configuration file.
– To further improve device security, periodically change the password.
● Personal data declaration
– Your purchased products, services, or features may use users' some
personal data during service operation or fault locating. You must define
user privacy policies in compliance with local laws and take proper
measures to fully protect personal data.
– When discarding, recycling, or reusing a device, back up or delete data on
the device as required to prevent data leakage. If you need support,
contact after-sales technical support personnel.
● Feature declaration
– The NetStream feature may be used to analyze the communication
information of terminal customers for network traffic statistics and
management purposes. Before enabling the NetStream feature, ensure
that it is performed within the boundaries permitted by applicable laws
and regulations. Effective measures must be taken to ensure that
information is securely protected.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 2

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

– The mirroring feature may be used to analyze the communication

information of terminal customers for a maintenance purpose. Before
enabling the mirroring function, ensure that it is performed within the
boundaries permitted by applicable laws and regulations. Effective
measures must be taken to ensure that information is securely protected.
– The packet header obtaining feature may be used to collect or store
some communication information about specific customers for
transmission fault and error detection purposes. Huawei cannot offer
services to collect or store this information unilaterally. Before enabling
the function, ensure that it is performed within the boundaries permitted
by applicable laws and regulations. Effective measures must be taken to
ensure that information is securely protected.
● 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.

Special Declaration
● This document serves only as a guide. The content is written based on device
information gathered under lab conditions. The content provided by this
document is intended to be taken as general guidance, and does not cover all
scenarios. The content provided by this document may be different from the
information on user device interfaces due to factors such as version upgrades
and differences in device models, board restrictions, and configuration files.
The actual user device information takes precedence over the content
provided by this document. The preceding differences are beyond the scope of
this document.
● The maximum values provided in this document are obtained in specific lab
environments (for example, only a certain type of board or protocol is
configured on a tested device). The actually obtained maximum values may
be different from the maximum values provided in this document due to
factors such as differences in hardware configurations and carried services.
● Interface numbers used in this document are examples. Use the existing
interface numbers on devices for configuration.
● The pictures of hardware in this document are for reference only.
● The supported boards are described in the document. Whether a
customization requirement can be met is subject to the information provided
at the pre-sales interface.
● In this document, public IP addresses may be used in feature introduction and
configuration examples and are for reference only unless otherwise specified.
● The configuration precautions described in this document may not accurately
reflect all scenarios.
● Log Reference and Alarm Reference respectively describe the logs and alarms
for which a trigger mechanism is available. The actual logs and alarms that
the product can generate depend on the types of services it supports.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 3

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

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.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 4

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Convention Description

{ 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.

Change History
Changes between document issues are cumulative. The latest document issue
contains all the changes made in earlier issues.
● Changes in Issue 01 (2022-10-31)
This issue is the first official release. The software version of this issue is
V800R022C00SPC600.

1.1.2 Interface Management Configuration

Interface management helps to provide quick and accurate communication
between devices.

1.1.2.1 Overview of Interface Management

This section provides the physical and logical interfaces supported by the NE9000
and describes the interface views and prompts and common link protocols and
access technologies.

Interface Types
Devices exchange data and interact with other devices on a network through
interfaces. Interfaces are classified into physical and logical interfaces.
● Physical Interfaces
Physical interfaces physically exist on boards. They are divided into the
following types:
– LAN interfaces: interfaces through which the router can exchange data
with other devices on a LAN.
– WAN interfaces: interfaces through which the router can exchange data
with remote devices on external networks.
● Logical Interfaces
Logical interfaces are manually configured interfaces that do not exist
physically. Logical interfaces can be used to exchange data.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 5

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

NOTICE

The management network port of the main control board does not forward
services.

Interface Views and Prompts

Table 1-1 lists the commands, views, and prompts of physical interfaces supported
by the NE9000. Table 1-2 lists the commands, views, and prompts of logical
interfaces supported by the NE9000.

Table 1-1 Commands, views, and prompts of physical interfaces supported by the
NE9000
Interface Command Operation Prompt
Name View

GE interface GE interface Run the [~HUAWEI-

view interface GigabitEthernet2/0/0]
gigabitetherne
t 2/0/0
command in
the system
view.

10GE interface 10GE interface Run the [~HUAWEI-

view interface GigabitEthernet1/0/0]
gigabitetherne
t 1/0/0
command in
the system
view.
NOTE
The interfaces
marked with
10G displayed
in the display
interface brief
command
output indicate
GE interfaces
whose
bandwidth is 10
Gbit/s.

25GE interface 25GE interface Run the [~HUAWEI-25GE2/0/0]

view interface 25GE
2/0/0
command in
the system
view.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 6

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Interface Command Operation Prompt

Name View

40GE interface 40GE interface Run the [~HUAWEI-40GE2/0/0]

view interface 40GE
1/0/0
command in
the system
view.

100GE interface 100GE interface Run the [~HUAWEI-100GE1/0/0]

view interface
100GE 1/0/0
command in
the system
view.

200GE interface 200GE interface Run the [~HUAWEI-200GE1/0/0]

view interface
200GE 1/0/0
command in
the system
view.

400GE interface 400GE interface Run the [~HUAWEI-400GE1/0/0]

view interface
400GE 1/0/0
command in
the system
view.

XGE interface XGE interface Run the [~HUAWEI-

view interface XGigabitEthernet1/0/0]
XGigabitEther
net 1/0/0
command in
the system
view.

POS interface POS interface Run the [~HUAWEI-Pos3/0/0]

view interface pos
3/0/0
command in
the system
view.

50GE interface 50GE interface Run the [~HUAWEI-50GE1/0/0]

view interface 50GE
1/0/0
command in
the system
view.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 7

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Interface Command Operation Prompt

Name View

FlexE-50G FlexE-50G Run the [~HUAWEI-

interface interface view interface FlexE-50G1/0/0]
FlexE-50G
1/0/0
command in
the system
view.

FlexE-100G FlexE-100G Run the [~HUAWEI-

interface interface view interface FlexE-100G1/0/0]
FlexE-100G
1/0/0
command in
the system
view.

FlexE-400G FlexE-400G Run the [~HUAWEI-

interface interface view interface FlexE-400G1/0/0]
FlexE-400G
1/0/0
command in
the system
view.

Table 1-2 Commands, views, and prompts of logical interfaces

Interface Command Operation Prompt
Name View

Sub-interface Sub- Run the interface [~HUAWEI-

interface gigabitethernet GigabitEthernet1/0/0.1]
view 1/0/0.1 command in
the system view.

Eth-Trunk Eth-Trunk Run the interface [~HUAWEI-Eth-Trunk2]

interface interface eth-trunk 2
view command in the
system view.

VE interface VE interface Run the interface [~HUAWEI-Virtual-

view virtual-ethernet Ethernet1/0/0]
1/0/0 command in
the system view.

Global VE Global VE Run the interface [~HUAWEI-Global-VE0]

interface interface global-ve 0
view command in the
system view.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 8

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Interface Command Operation Prompt

Name View

VLANIF VLANIF Run the interface [~HUAWEI-Vlanif2]

interface interface vlanif 2 command
view in the system view.

Loopback Loopback Run the interface [~HUAWEI-LoopBack2]

interface interface loopback 2
view command in the
system view.

Null interface Null Run the interface [~HUAWEI-NULL0]

interface null 0 command in
view the system view.

IP-Trunk IP-Trunk Run the interface [~HUAWEI-Ip-Trunk2]

interface interface ip-trunk 2
view command in the
system view.

Tunnel Tunnel Run the interface [~HUAWEI-Tunnel 2]

interface interface tunnel 2 command
view in the system view.

NVE interface NVE Run the interface [~HUAWEI-Nve1]

interface nve 1 command in
view the system view.

FlexE FlexE Run the interface [~HUAWEI-FlexE2/0/5]

interface interface FlexE 2/0/5
view command in the
system view.

PW-VE PW-VE Run the interface [~HUAWEI-pw-ve1]

interface interface pw-ve 1 command
view in the system view.

Commonly-used Link Protocols and Access Technologies

The link layer is responsible for accurately sending data from a node to a
neighboring node. It receives packets from the network layer, encapsulates the
packets in frames, and then sends the frames to the physical layer.
Major link layer protocols supported by the NE9000 are listed as follows:
● Ethernet
Currently, the LAN mostly refers to the Ethernet. The Ethernet is a broadcast
network, which is flexible and simple in configuration as well as easy to
expand. For these reasons, the Ethernet is widely used.
● Trunk
Trunks can be classified into Eth-Trunks and IP-Trunks. An Eth-Trunk must be
composed of Ethernet links, and an IP-Trunk must be composed of POS links.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 9

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

The trunk technology has the following advantages:

– Bandwidth increase: The bandwidth of a trunk is the total bandwidth of
all member interfaces.
– Reliability enhancement: When a link fails, other links in the same trunk
automatically take over the services on the faulty link to prevent traffic
interruption.
● PPP
The Point-to-Point Protocol (PPP) is used to encapsulate IP packets on serial
links. It supports both the asynchronous transmission of 8-bit data without
the parity check and the bit-oriented synchronous connection.
PPP consists of the Link Control Protocol (LCP) and the Network Control
Protocol (NCP). LCP is used to create, configure, and test links; NCP is used to
control different network layer protocols.
● HDLC
The High-Level Data Link Control (HDLC) is a suite of protocols that are used
to transmit data between network nodes. HDLC is widely used at the data link
layer.
In HDLC, the receiver responds with an acknowledgment when it receives
frames transmitted over the network. In addition, HDLC manages data flows
and the interval at which data packets are transmitted.

Interface Flapping Control

The status of an interface on a device may alternate between up and down for
various reasons, including physical signal interference and incorrect link layer
configurations. The changing status causes Multiprotocol Label Switching (MPLS)
and routing protocols to flap. As a result, the device may break down, causing
network interruption. Control-flap controls the frequency of interface status
alternations between up and down to minimize the impact on device and network
stability.
The following two control modes are available.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 10

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Table 1-3 Flapping control modes

Control Mode Function Usage Scenario

control-flap Controls the frequent ● This control mode is

flappings of interfaces at interface-specific.
the network layer to ● This control mode
minimize the impact on suppresses interface
device and network flappings from the
stability. network layer and
reports the flappings
to the routing
management module,
thereby improving
network-layer
stability.
● This control mode
allows you to
precisely configure
parameters based on
service requirements.
● This control mode
involves complex
algorithms and is
highly demanding to
use.

damp-interface Controls the frequent ● This function is

flappings of interfaces at supported globally or
the physical layer to on a specified
minimize the impact on interface.
device and network ● This control mode
stability. suppresses the
flappings from the
physical layer, thereby
improving link-layer
and network-layer
stability.
● This control mode
prevents the upper-
layer protocols from
frequently alternating
between enabled and
disabled, thereby
reducing the
consumption of CPU
and memory
resources.
● This control mode
does not involve any
complex algorithms
and is easy to use.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 11

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

1.1.2.2 Configuration Precautions for Interface_Management

Feature Requirements

Table 1-4 Feature requirements

Feature Requirements Series Models

The commands used to query information NE9000 NE9000

about interfaces do not support offline
interfaces.

The interface fixed index function is dependent NE9000 NE9000

on device.sys files. When the data in device.sys
files is deleted, the interface index may change
after the device restart.

The display counters rate command displays NE9000 NE9000

only the traffic rate of packets that are sent or
received by Up interfaces. The display counters
rate command does not display information
about Down interfaces.

After IP address conflict detection is disabled NE9000 NE9000

and the preemption function for conflicting IP
addresses is enabled:
1. If the preemption function for conflicting IP
addresses is disabled, the same IP address may
take effect on a different interface after a
device restart.
2. The preemption function for conflicting IP
addresses does not take effect for VRRP virtual
addresses.
3. If the IP address of the source interface
specified for a service takes effect on another
interface with a higher priority, the protocol
status of the source interface is Down, which
may cause service interruption.
4. After a conflicting IP address takes effect on
an interface with a higher priority, traffic may
be temporarily interrupted due to interface
switchover.

1.1.2.3 Interface Basics Configuration

Learning about interface basics, including common interface types and
configurable interface parameters, helps with interface management.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 12

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Usage Scenario
To ensure better communication between devices on the network, physical and
logical interfaces must be used together. In addition, you need to set parameters
for each interface as required, such as the description, MTU, alarm thresholds for
the inbound and outbound bandwidth usage of each interface, interval for
collecting traffic statistics, trap reporting to the NMS when the protocol status of
an interface changes, and control-flap.

Pre-configuration Tasks
Before performing interface basics configurations, verify that the device has been
powered on and started properly.

1.1.2.3.1 Entering the Interface View

The command for entering the view of an interface varies with the physical
attribute of the interface.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
In this command, interface-type specifies the type of the interface, and interface-
number specifies the number of the interface.
Step 3 (Optional) Run commit
The configuration is committed.
If the interface of the specified type and number exists in the preceding step, you
do not need to run the commit command.

----End

1.1.2.3.2 (Optional) Setting Interface Parameters

This section describes how to set parameters for an interface based on the actual
service requirements. The parameters include the description and maximum
transmission unit (MTU).

Context
Table 1-5 describes the configurable parameters of an interface.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 13

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Table 1-5 Configurable parameters of an interface

Parameter Description

Interface description When you maintain a large number of interfaces, an

interface description helps identify an interface easily.

Interface MTU After the MTU is configured for an interface, the device
fragments a packet transmitted on the interface if the
size of the packet exceeds the MTU.
NOTE
Loopback and NULL interfaces do not support the MTU.

Interface bandwidth You can calculate the bandwidth usage by setting the
that can be obtained interface bandwidth that can be obtained by the NMS
by the NMS through through the MIB.
the MIB

Whether the device You can enable the device to send a trap message to the
sends a trap NMS when the interface status changes. After this
message to the NMS function is enabled, the NMS monitors the interface
when the interface status in real time.
status changes However, if an interface alternates between up and
down, the device will frequently send trap messages to
the NMS, which increases the processing load on the
NMS. In this situation, you can disable the device from
sending trap messages to the NMS to avoid adverse
impact on the NMS.

Interval at which After setting the interval at which traffic statistics are
traffic statistics are collected for an interface, you can view the traffic
collected volumes and rates of the interface in different time
ranges.

Whether the Control-flap controls the frequency of interface status

control-flap function alternations between up and down, which minimizes the
is enabled impact on device and network stability.
NOTE
Loopback and NULL interfaces do not support the control-flap
function.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface interface-type interface-number

The interface view is displayed.

In this command, interface-type specifies the type of the interface, and interface-
number specifies the number of the interface.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 14

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Step 3 Perform one or more operations in Table 1-6 to set the desired interface
parameters.

Table 1-6 Setting interface parameters

Operation Description

Configure a Run the description regular-expression command to

description for an configure a description for an interface.
interface.

Set an MTU for an Run the mtu mtu or ipv6 mtu mtu command to set an
interface. MTU for an interface.
Run the mtu mtu spread or ipv6 mtu mtu spread
command to set an MTU for an interface and apply the
MTU to all the sub-interfaces on the interface.
NOTE
● After changing the MTU on a POS interface using the mtu
or mtu spread command, run the shutdown and undo
shutdown commands in the interface view for the change to
take effect. Alternatively, you can run the restart command
in the interface view to restart the interface for the change
to take effect.
● If IPv4 attributes are configured on an interface, run the mtu
or mtu spread command to set an MTU for the IPv4 packets
to be sent by the interface.
● If IPv6 attributes are configured on an interface, run the ipv6
mtu or ipv6 mtu spread command to set an MTU for the
IPv6 packets to be sent by the interface.

Set configuration Run the bandwidth command to set configuration

bandwidth for an bandwidth for an interface.
interface. NOTE
To view the command configurations, you can check the ifSpeed
and ifHighSpeed objects in the IF-MIB on the NMS.
By default, services typically use only the physical bandwidth for
protocol route selection calculation. You can run the
bandwidth-config effect service enable command to use the
configuration bandwidth for protocol route selection calculation.

Configure whether Run the enable snmp trap updown command to enable
the device sends a the device to send a trap message to the NMS when the
trap message to the interface status changes.
NMS when the NOTE
interface status If an interface alternates between up and down, the device will
changes. frequently send trap messages to the NMS, which increases the
processing load on the NMS. In this situation, you can run the
undo enable snmp trap updown command to disable the
device from sending trap messages to the NMS to avoid adverse
impact on the NMS.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 15

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Operation Description

Set the interval at Run the set flow-stat interval interval command to set
which traffic the interval at which traffic statistics are collected.
statistics are NOTE
collected. ● To set a global interval at which traffic statistics are
collected, run the set flow-stat interval interval command
in the system view, and you do not need to run the interface
interface-type interface-number command. You can
configure a global traffic statistic collection interval, which
takes effect on all interfaces, including the interfaces on
which no traffic statistic collection interval has been set.
● The new interval takes effect after the original interval
expires. If the interface is logical, traffic statistics about the
interface are updated when the new interval takes effect for
the second time. If the interface is physical, traffic statistics
about the interface are updated immediately after the new
interval takes effect.

Enable the control- Run the control-flap [ suppress reuse ceiling decay-ok
flap function. decay-ng ] command to enable the control-flap function
on an interface.
The value of suppress is 1000 times the interface
suppression threshold. It ranges from 1 to 20000. The
default value is 2000. The value of suppress must be
greater than the value of reuse and less than the value
of ceiling.
The value of reuse is 1000 times the interface reuse
threshold. It ranges from 1 to 20000. The default value is
750. The value of reuse must be less than the value of
suppress.
The value of ceiling is 1000 times the maximum
interface suppression penalty value. It ranges from 1001
to 20000. The default value is 6000. The value of ceiling
must be greater than the value of suppress.
decay-ok specifies the half life for the penalty value
when an interface is up. It ranges from 1 to 900, in
seconds. The default value is 54.
decay-ng specifies the half life for the penalty value
when an interface is down. It ranges from 1 to 900, in
seconds. The default value is 54.

Configure whether Run the signal-coding { dqpsk | qpsk } command to

to adjust the configure a modulation mode for an interface.
modulation mode of
an interface.

Step 4 Run commit

The configuration is committed.

----End

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 16

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

1.1.2.3.3 Enabling an Interface

Physical interfaces on a device are initialized and started when the device is
powered on.

Context
NOTE

This configuration process is supported only by the admin VS.

Procedure
● By default, interfaces are started.
● If an interface is shut down, perform the following steps to start the interface:
a. Run system-view
The system view is displayed.
b. Run interface interface-type interface-number
The interface view is displayed.
c. Run undo shutdown
The interface is started.
d. Run commit
The configuration is committed.
----End

1.1.2.3.4 (Optional) Configuring a Device to Send a Trap Message to an NMS When

an Interface Physical Status Changes
You can enable a device to send a trap message to an NMS when the interface
physical status changes. After this function is enabled, the NMS monitors the
interface status in real time.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
Step 3 Run enable snmp trap physical-updown
The device is enabled to send a trap message to the NMS when the interface
physical status changes.

Step 4 Run commit

The configuration is committed.

----End

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 17

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

1.1.2.3.5 (Optional) Configuring IPv4 and IPv6 Traffic Statistics Collection on a

Main Interface
You can configure IPv4 and IPv6 traffic statistics collection for all main interfaces.

Context
Do as follows on the router that needs to be configured with IPv4 and IPv6 traffic
statistics collection.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface interface-type interface-number

The interface view is displayed.

Step 3 Run statistic mode forward

IPv4 and IPv6 traffic statistics collection is enabled on the main interface.

Step 4 Run commit

The configuration is committed.

----End

1.1.2.3.6 (Optional) Configuring Power Locking and Gain Locking for an Optical
Amplifier Module
You can configure power locking and gain locking for an optical amplifier module
to amplify the optical power.

Context
Perform the following steps on the router where power locking and gain locking
need to be configured for an optical amplifier module.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Perform either of the following configurations as required.

● Run the interface interface-type interface-number command to enter the
view of a specified interface.

Step 3 Run work-mode { agc agc-value | apc apc-value }

Power locking and gain locking are configured for the optical amplifier module.

Step 4 Run commit

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 18

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

The configuration is committed.

----End

1.1.2.3.7 (Optional) Configuring an Interface Splitting Mode

By configuring an interface splitting mode, you can switch the bandwidth mode of
the split interface.

Context
To switch an interface bandwidth mode, configure an interface splitting mode,
which increases the networking flexibility and saves interface costs.

NOTE

In VS mode, this configuration process is supported only by the admin VS.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run port split dimension interface { { interface-name1 | interface-type interface-
number1 } [ to { interface-name2 | interface-type interface-number2 } ] } &<1–
32> split-type split-type
Interface splitting is configured.
Step 3 Run commit
The configuration is committed.

----End

1.1.2.3.8 Verifying the Configuration

After the configurations are complete, check the status of the interface, statistics
on the interface, and the control-flap operation.

Procedure
● Run the display interface [ interface-type interface-number ] command to
check the status of the interface and statistics on the interface.
● Run the display control-flap interface interface-type interface-number
command to check the configuration and running status of the control-flap
function on interfaces.
● Run the display counters [ bit ] [ inbound | outbound ] [ interface
interface-type [ interface-number ] ] [ slot slot-id ] command to check the
interface traffic statistics.
● Run the display counters [ bit ] rate [ inbound | outbound ] [ interface
interface-type [ interface-number | slot slot-id ] | slot slot-id ] command to
check the interface traffic rates.
● Run the display port split or display port split slot command to check the
splitting status of the interface.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 19

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● Run the display interface neighbor [ interface-type interface-number | slot

slot-id [ card card-number ] ] command to check information about the
neighboring devices and interfaces of a physical interface on the device.
● Run the display interface description [ interface-type [ interface-number ] |
slot slot-id [ card card-number ] ][ full-name ] command to check the
interface description.

----End

1.1.2.4 Configuring the Physical Link Detection Function

The physical link detection function helps reduce the number of alarms generated
on links and avoid system performance degradation caused by plenty of alarms
that would be otherwise generated.

Usage Scenario
When plenty of alarms are generated on links, system performance deteriorates
because the system has to process the huge number of alarms. You can set
thresholds for different types of alarms, so that alarms are generated only when
the alarm thresholds are reached. In addition, measures can be taken when
necessary to remove faults and guarantee the transmission of normal traffic.

Pre-configuration Tasks
Before configuring physical link detection, complete the following tasks:

● Powering on the router, ensuring that the router works properly and
completes self-check successfully.
● Configure physical attributes for interfaces on the router.

1.1.2.4.1 Configuring the Alarm Function for CRC Errors, SDH Errors, Input Errors,
Output Errors, or Optical Module Power Exceptions
This section describes how to configure the alarm function for CRC errors, SDH
errors, input errors, output errors, or optical module power exceptions.

Context
If the alarm function for CRC errors, SDH errors, input errors, output errors, or
optical module power exceptions is enabled on an interface, the system generates
an alarm when the number of errors or exceptions exceeds or falls below the
threshold set on the interface. If a large number of alarms are generated on links,
the system will be busy processing them, which causes performance deterioration.
To prevent this problem, properly configure the type of interface alarm, alarm
thresholds, and detection interval.

Procedure
Step 1 Run system-view

The system view is displayed.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 20

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Step 2 Run snmp-agent trap enable port { crcexc-error | input-error | output-error |

sdh-error-rising | optical-module-abnormal }

The alarm function is enabled on interfaces.

The configuration takes effect on all physical interfaces supporting the alarm
function.

You can set a type of alarm as required.

● crcexc-error: Enables the alarm function for CRC errors.

● sdh-error-rising: Enables the alarm function for SDH errors.
● optical-module-abnormal: Enables the alarm function for optical module
power exceptions.

In VS mode, this command is supported only by the admin VS.

Step 3 Run interface interface-type interface-number

The interface view is displayed.

Step 4 Configure alarm thresholds and a detection interval.

● Configure alarm thresholds for inbound and outbound bandwidth usage:
– Run trap-threshold { input-rate | output-rate } bandwidth-in-use
[ resume-rate resume-threshold ]
The inbound and outbound bandwidth usage threshold is set.
To prevent alarms from being generated frequently, keep a large
difference between bandwidth-in-use and resume-threshold.
– Run set flow-stat interval interval
The traffic statistic collection interval is set for the interface, in seconds.
The new interval takes effect after the original interval expires. If the
interface is logical, traffic statistics about the interface are updated when
the new interval takes effect for the second time. If the interface is
physical, traffic statistics about the interface are updated immediately
after the new interval takes effect.
The traffic statistic collection interval set on an interface is effective only
on the interface.
NOTE

You can configure a global traffic statistic collection interval, which takes effect
on all interfaces, including the interfaces on which no traffic statistic collection
interval has been set. To configure a global traffic statistic collection interval, run
the set flow-stat interval interval command in the system view. The traffic
statistic collection interval of an interface takes preference over a global traffic
statistic collection interval.
● Configure CRC alarm thresholds and a detection interval (for Ethernet
interfaces and POS interfaces using either of the following methods):
– Run trap-threshold crc-error threshold interval-second interval
An alarm threshold and a detection interval are set for CRC errors.
– Run trap-threshold crc-error high-threshold high-threshold low-
threshold low-threshold interval-second interval [ shutdown ]

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 21

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

The upper and lower alarm thresholds for CRC errors as well as the
detection interval are set.

NOTE

You can run the trap-threshold slot slot-id card card-id crc-error high-
threshold high-threshold low-threshold low-threshold interval-second interval
command in the system view to configure global values for all interfaces on the
specified subcard.
● Configure SDH alarm thresholds and a detection interval (for 10GE WAN
interfaces and POS interfaces using either of the following methods):
– Run trap-threshold sdh-error threshold interval-second interval
An alarm threshold and a detection interval are set for SDH errors.
– Run trap-threshold sdh-error high-threshold high-threshold low-
threshold low-threshold interval-second interval
The upper and lower alarm thresholds for SDH errors as well as the
detection interval are set.
● Configure SDH alarm thresholds and a detection interval (for POS interfaces
using either of the following methods):
– Run trap-threshold sdh-error threshold interval-second interval
An alarm threshold and a detection interval are set for SDH errors.
– Run trap-threshold sdh-error high-threshold high-threshold low-
threshold low-threshold interval-second interval
The upper and lower alarm thresholds for SDH errors as well as the
detection interval are set.
● Configure symbol alarm thresholds and a detection interval (for Ethernet
interfaces only).
– Run trap-threshold symbol-error high-threshold high-threshold low-
threshold low-threshold interval-second interval
The upper and lower alarm thresholds for symbol errors as well as the
detection interval are set.
NOTE

You can run the trap-threshold slot slot-id card card-id symbol-error high-
threshold high-threshold low-threshold low-threshold interval-second interval
command in the system view to configure global values for all interfaces on the
specified subcard.
● Configure input/output alarm thresholds and a detection interval (for
Ethernet interfaces and POS interfaces).
– Run trap-threshold { input-error | output-error } high-threshold high-
threshold low-threshold low-threshold interval-second interval
The upper and lower alarm thresholds for interface input or output errors
are set.
NOTE

You can run the trap-threshold slot slot-id card card-id { input-error | output-
error } high-threshold high-threshold low-threshold low-threshold interval-
second interval command in the system view to configure global values for all
interfaces on the specified subcard.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 22

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● Configure BIP8 SD alarm thresholds and a detection interval (for 40GE/100GE

interfaces only).
– Run trap-threshold bip8-sd bip8-sd
The alarm threshold for BIP8 SD errors is set on a 40GE or 100GE
interface.

Step 5 (Optional) Run port-alarm down { crc-error | sdh-error | symbol-error | input-

error | output-error | bip8-sd }

An interface is configured to go Down upon receiving the alarms.

NOTE

● You can run the port-alarm down slot slot-id card card-id { crc-error | sdh-error |
symbol-error | input-error | output-error | bip8-sd } command in the system view to
apply the configurations to all interfaces on the subcard.
● After the association function is enabled, you can run the port-alarm clear { crc-error |
sdh-error | symbol-error | input-error | output-error | bip8-sd } command to clear the
alarms on the interface.

Step 6 Run commit

The configuration is committed.

----End

1.1.2.4.2 Configuring the Alarm Function for Pause-Frame Errors Received on an

Interface
This section describes how to configure the alarm function for pause-frame errors
received on an interface.

Context
A device generates an alarm and sends it to an NMS only when the number of
pause-frame error packets sent or received by the device reaches the upper
threshold for three consecutive detection intervals. The device sends a clear alarm
to the NMS only when the number of pause-frame error packets sent or received
by the device falls below the lower threshold for three consecutive detection
intervals.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface interface-type interface-number

The view of an interface is displayed.

Step 3 Run trap-threshold pause-frame high-threshold high-threshold low-threshold

low-threshold interval-second interval
The upper threshold, lower threshold, and detection interval for the pause-frame
error alarm are set.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 23

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Step 4 Run commit

The configuration is committed.

----End

1.1.2.4.3 Configuring the Alarm Function in Case the Number of SDH B1 or SDH B2
Error Packets That an Interface Receives Exceeds an Alarm Threshold
You can configure the alarm function in case the number of SDH B1 or SDH B2
error packets exceeds an alarm threshold. If such an alarm is generated, the link is
in a poor condition.

Context
If an interface receives a large number of SDH B1 or SDH B2 error packets, the
link is in a poor condition, affecting service transmission. In this situation, you can
configure the alarm function, alarm threshold, and detection interval on an
interface. The system then detects the number of SDH B1 or SDH B2 error packets
that the interface receives at the configured interval. If the number of SDH B1 or
SDH B2 error packets exceeds the configured alarm threshold, the system
generates an alarm and sends it to the NMS, prompting the administrator to
perform maintenance on the interface and troubleshoot the fault. When the
number of SDH B1 or SDH B2 error packets falls below the alarm threshold, the
system generates a clear alarm and sends it to the NMS, notifying the
administrator that the alarm has been cleared.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface interface-type interface-number

The interface view is displayed.

Step 3 Run trap-threshold { sdh-b1-error | sdh-b2-error } threshold interval-second

interval

A threshold and detection interval for the SDH B1 or SDH B2 error alarm on an
interface are set.

Step 4 Run commit

The configuration is committed.

----End

1.1.2.4.4 Configuring the Alarm Function in Case the Number of Bytes of Error
Packets That an Interface Receives Exceeds an Alarm Threshold
You can configure the alarm function in case the number of bytes of error packets
exceeds a threshold. If such an alarm is generated, the link is in a poor condition.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 24

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Context
If an interface receives a large number of bytes of error packets, the link is in a
poor condition, affecting service transmission. In this situation, you can configure
the alarm function, alarm threshold, and detection interval on an interface. The
system then detects the number of bytes of error packets that the interface
receives at the configured interval. If the number of bytes of error packets exceeds
the configured alarm threshold, the system generates an alarm and sends it to the
NMS, prompting the administrator to perform maintenance on the interface and
troubleshoot the fault. When the number of bytes of error packets falls below the
alarm threshold, the system generates a clear alarm and sends it to the NMS,
notifying the administrator that the alarm has been cleared.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run snmp-agent trap enable port bad-bytes
The alarm function is configured in case the number of bytes of error packets
exceeds an alarm threshold.

Step 3 Run interface interface-type interface-number

The interface view is displayed.
Step 4 Run trap-threshold bad-bytes trap-threshold interval-second interval
An alarm threshold is configured for the number of bytes of error packets that the
interface receives, and an interval is configured for the system to detect the
number of bytes of error packets.

Step 5 Run commit

The configuration is committed.

----End

1.1.2.4.5 Verifying the Configuration

You can check the interface configuration and state information after configuring
the physical link detection function.

Context
The physical link detection function has been configured.

Procedure
● Run the display trap-info command in the interface view or run the display
trap-info { interface-type interface-number | interface-name | slot slot-id
card card-id } command in the system view to check alarm configurations on
the specified interface, including the alarm function status, alarm thresholds,
detection interval, alarm blocking status, current alarm state, and the number
of current alarms.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 25

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● Run the display port-error-info interface { interface-type interface-number |

interface-name } command in the interface view to check the trap
information about error codes/error packets of an interface.

----End

1.1.2.5 Configuring MAC Accounting

If the MAC accounting function is enabled on an interface of a device, the device
collects IPv4 or IPv6 traffic statistics corresponding to MAC addresses learned by
the interface.

Usage Scenario

Figure 1-1 MAC accounting usage scenario

MAC accounting can be used in either of the following scenarios:

● When a Huawei device on an ISP network functions as an Internet exchange
point (IXP), the networks connected to the IXP are provided by other carriers.
When the ISP leases the other carriers' networks, for example, Network1 and
Network2, they charge the ISP by traffic volume. To check traffic of MAC
addresses, run the mac accounting enable command to enable the MAC
accounting function on the IXP's interface, so that traffic of the peer routers
can be obtained. This facilitates the ISP to verify or analyze traffic.
● If the IXP is under DDoS attacks, the MAC accounting function helps the ISP
to check the traffic of peer routers with specified MAC addresses. If traffic of a
specified MAC address is huge, the attack traffic may be from this device with
the specified MAC address.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 26

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface interface-type interface-number

The user interface view is displayed.

Step 3 Run mac accounting enable

MAC accounting is enabled.

Step 4 Run commit

The configuration is committed.

----End

Verifying the Configuration

After MAC accounting is enabled, run the display mac accounting command to
check MAC accounting statistics on the interface or its sub-interfaces.

If you need to re-check MAC accounting statistics after a period, run the reset
mac accounting command to delete the existing statistics and then run the
display mac accounting command. This ensures statistics accuracy.

1.1.2.6 Configuring Strict Filter for EVC Sub-Interfaces

This section describes how to configure strict filter for EVC sub-interfaces.

Usage Scenario
On a BD scenario, the router has two sub-interfaces configured in a main
interface, one with the Dot1q encapsulation type and the other with the default
encapsulation type. Once the sub-interface encapsulated Dot1q receives traffic,
the sub-interface with the default encapsulation type also sends out the traffic.
This may cause the illusion of return current. Besides, the router has two
interfaces configured on a BD scenario. The first interface has a sub-interface that
is configured with the Dot1q encapsulation type. The second interface has two
sub-interfaces that are configured with the Dot1q and default encapsulation types
respectively. Once traffic passes through the sub-interface on the first interface,
the second interface also sends two copied traffic from each of its sub-interfaces.
This causes traffic to be replicated, wasting resources and reducing the board's
forwarding efficiency. To allow traffic to be sent through specific interfaces, enable
strict filter.

Pre-configuration Tasks
Before configuring strict filter on an interface, configure physical attributes for
interfaces on the router.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 27

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Procedure
● Enable strict filter globally.
a. Run system-view

The system view is displayed.

b. Run ethernet egress-strict-filter enable

Strict filter is enabled globally.

c. Run commit

The configuration is committed.

● Enable strict filter on an EVC sub-interface.
a. Run system-view

The system view is displayed.

b. Run interface interface-type interface-number.sub-interface-number
mode l2

The EVC sub-interface view is displayed.

c. Run ethernet egress-strict-filter enable

Strict filter is enabled for the EVC sub-interface.

d. Run commit

The configuration is committed.

NOTE

The strict filter configuration on an EVC sub-interface takes precedence over that
configured in the system view. The strict filter configuration on an EVC sub-
interface takes effect, regardless of whether strict filter is configured globally.

----End

1.1.2.7 Enabling the Signal Sending Delay Function

This section describes how to configure the signal sending delay function.

Usage Scenario
After a device is restarted or a board is replaced, if an interface sends signals
immediately after initialization before the link completes a switchover or
configuration restoration, data loss may occur. To prevent data loss, configure the
signal sending delay function.

NOTE

● Only physical interfaces can be configured with signal sending delays. Logical interfaces
do not support this function.
● Configuring a signal sending delay does not affect an interface that has sent signals to
the peer, and the configuration takes effect after the interface is initialized.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 28

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Perform either of the following configurations as required.

1. Run interface interface-type interface-number

The GE, POS, 10GE WAN or 10GE LAN interface view is displayed.
2. Run controller wdm interface-number

The WDM interface view is displayed.

Step 3 Run port-tx-enabling-delay port-tx-delay-time

The signal sending delay function is enabled, and the signal sending delay is
configured.

Step 4 Run commit

The configuration is committed.

----End

Verifying the Configuration

Run the display port-tx-enabling-delay interface { ethernet | gigabitethernet |
pos } interface-number command to check information about the signal sending
delay configured on the interface.

1.1.2.8 Enabling or Disabling the Optical Module Laser

This section describes how to enable or disable the optical module laser.

Usage Scenario
Before locating or troubleshooting a link failure, maintenance engineers should
ensure that the optical module laser is disabled so that it cannot cause injury. The
optical module can be configured to disable the laser automatically if it detects a
link failure. The laser can also be disabled manually. If the optical module is
configured to disable the laser automatically, the laser is not immediately re-
enabled when the link failure is cleared. However, maintenance engineers can
enable the optical module laser manually to check whether services have
recovered.

Pre-configuration Tasks
Before enabling or disabling the optical module laser, complete the following
tasks:

● Power on the router.

● Ensure that the optical module has been installed and that the interface is Up.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 29

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

1.1.2.8.1 Disabling the Optical Module Laser

Disabling the optical module laser before troubleshooting a link failure protects
maintenance engineers from the laser.

Context
Before locating or troubleshooting a link failure, maintenance engineers should
ensure that the optical module laser is disabled so that it cannot cause injury. The
optical module can be configured to disable the laser automatically if it detects a
link failure. The laser can also be disabled manually.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
Step 3 Perform either of the following operations:
● Configure the optical module to disable the laser automatically.
a. To configure the optical module to disable the laser automatically, run
the laser autoshutdown enable command.
b. (Optional) To configure intervals at which the optical module laser is
disabled or enabled and the system checks for link failures, run the laser
auto-shutdown-interval { open opentime-interval | close closetime-
interval } command.
● Disable the optical module laser manually.
To disable the optical module laser manually, run the laser turn-off
command.

NOTICE

Running the laser turn-off command interrupts services on the interface.

Therefore, do not run the command when the interface is working properly.

Step 4 Run commit

The configuration is committed.
----End

1.1.2.8.2 (Optional) Enabling the Optical Module Laser

After enabling the optical module laser, you can check whether the link failure is
cleared.

Context
If the optical module is configured to disable the laser automatically, the laser is
not immediately re-enabled when the link failure is cleared. However,

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 30

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

maintenance engineers can enable the optical module laser manually to check
whether services have recovered.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface interface-type interface-number

The interface view is displayed.

The interface can be a GE optical, POS interface.

Step 3 Run laser turn-on [ duration duration ]

The optical module laser is enabled, and the duration for which the optical
module laser will be temporarily enabled is configured.

The duration takes effect only after the laser autoshutdown enable command is
run.

Step 4 Run commit

The configuration is committed.

----End

1.1.2.8.3 Verifying the Configuration of Enabling or Disabling the Optical Module

Laser
After enabling or disabling the optical module laser, check its status.

Prerequisites
The optical module laser has been enabled or disabled as required.

Context
The following operations affect the status of the optical module laser:
● Run the laser turn-on command to enable the optical module laser.
● Run the laser turn-off command to disable the optical module laser.
● Run the laser autoshutdown enable command to configure the optical
module to disable the laser automatically if it detects a link failure.
● Run the shutdown command to deactivate the interface.

Procedure
● Run the display laser status { interface interface-type interface-number }
command in any view to check the status of the optical module laser.

----End

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 31

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

1.1.2.9 Enabling the Optical Module Alarm Threshold Standardization

Function
You can enable the alarm standardization function for an optical module to
prevent the optical module from reporting alarms when its optical power exceeds
the threshold.

Context
The system automatically obtains the vendor-defined power threshold of an
optical module and compares it with the actual power. If the actual power exceeds
the vendor-defined threshold, an alarm will be generated. However, the vendor-
defined power threshold of an optical module may not meet user requirements. If
the alarm standardization function is enabled, a unified power threshold is used,
and the threshold is calculated based on the optical module transmission distance
and bandwidth.

NOTE

The device has two types of optical module power alarms: warning and alarm. A warning is
reported when the difference between the actual power and vendor-defined threshold is
not great. It can also be considered as a precaution. Some optical modules can continue
working properly when the actual optical power is at the warning level. You can disable
warning detection as required.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run optical-module alarm-threshold standardization enable

The alarm threshold standardization function is enabled for the optical module.

Step 3 Run commit

The configuration is committed.

----End

1.1.2.10 Disabling the Optical Module Alarm Function

You can disable the alarm function for an optical module to prevent the optical
module from reporting alarms when its optical power exceeds the threshold.

Context
The system automatically obtains the vendor-defined power threshold of an
optical module and compares it with the actual power. If the actual power exceeds
the vendor-defined threshold, an alarm will be generated. Generally, the actual
power is greater than the vendor-defined threshold, which means frequent alarm
reporting. It is unfeasible to install an attenuator on each optical module to
prevent frequent reporting of such power alarms. You can disable the alarm
function for the optical module by executing the following command.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 32

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

NOTE

The device has two types of optical module power alarms: warning and alarm. A warning is
reported when the difference between the actual power and vendor-defined threshold is
not great. It can also be considered as a precaution. Some optical modules can continue
working properly when the actual optical power is at the warning level. You can disable the
alarm function for these optical modules to prevent these optical modules from frequently
reporting warnings by executing the following command.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface interface-type interface-number

The interface view is displayed.

Step 3 Run port-alarm disable optical-module { rx-power-high-warning | rx-power-

low-warning | tx-power-high-warning | tx-power-low-warning | voltage-high-
warning | voltage-low-warning } *

The alarm function is disabled for the optical module.

Step 4 Run commit

The configuration is committed.

----End

1.1.2.11 Managing Non-Huawei-Certified Optical Modules

To manage non-Huawei-certified optical modules, you can suppress the alarms for
non-Huawei-certified optical modules and enable the function of setting
interfaces with the optical modules inserted to Down.

Context
When an interface is inserted with a non-Huawei-certified optical module, the
system automatically reports an alarm. If you want to suppress the alarm, you can
disable the function of reporting the alarm for the non-Huawei-certified optical
module. If you do not want to use the interface with the optical module inserted,
you can enable the function of setting the interface to Down.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run transceiver non-certified-alarm disable

The function of reporting an alarm for a non-Huawei-certified optical module is

disabled.

Step 3 Run transceiver non-certified-alarm port-down enable

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 33

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

The function of setting an interface with a non-Huawei-certified optical module

inserted to Down is enabled.

Step 4 Run commit

The configuration is committed.

----End

1.1.2.12 Configuring the Control-Flap Function

This section describes how to configure the control-flap function.

Usage Scenario
The flapping of routing protocols, MPLS, and other protocols caused by the
frequent change of the interface status may influence the stability of the whole
network. To resolve this problem, you can configure the control-flap function.

The function controls the frequency of interface status alternations between up

and down, which minimizes the impact on device and network stability.

For related concepts and fundamentals, see Interface Flapping Control.

Pre-configuration Tasks
Before configuring the control-flap function, configure the physical attributes for
the router interfaces.

Procedure
● Configure the control-flap function.
a. Run system-view

The system view is displayed.

b. Run interface interface-type interface-number

The interface view is displayed.

NOTE

The null interface and loopback interface do not support the control-flap
function.
c. Run control-flap [ suppress reuse ceiling decay-ok decay-ng ]

The control-flap function is enabled on the interface.

The value of suppress is 1000 times the suppress threshold of the

interface. It ranges from 1 to 20000. The default value is 2000. The value
of suppress must be greater than the value of reuse and smaller than the
value of ceiling.

The value of reuse is 1000 times the reuse threshold of the interface. It
ranges from 1 to 20000. The default value is 750. The value of reuse must
be smaller than the value of suppress.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 34

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

The value of ceiling is 1000 times the suppress penalty value of the
interface. It ranges from 1001 to 20000. The default value is 6000. The
value of ceiling must be greater than the value of suppress.

The value of decay-ok is the time taken to decay the penalty value to
half when the interface is Up. It ranges from 1 to 900 seconds. The
default value is 54 seconds.

The value of decay-ng is the time taken to decay the penalty value to
half when the interface is Down. It ranges from 1 to 900 seconds. The
default value is 54 seconds.
d. Run commit

The configuration is committed.

● Configure status flapping suppression on a physical interface.
a. Run system-view

The system view is displayed.

b. (Optional) Run interface interface-type interface-number

The view of an interface is displayed.

c. Run damp-interface enable

Status flapping suppression is enabled on the interface.

d. (Optional) Run damp-interface level { light | middle | heavy | manual
{ half-life-period suppress reuse max-suppress-time } }

A suppression level is configured for status flapping suppression.

▪ light: If light suppression is configured, the system triggers

suppression only when an interface's status flaps frequently and
rapidly. The light suppression level is the default setting and applies
to flappings that have the maximum impact on the system.

▪ heavy: If heavy suppression is configured, the system triggers

suppression when detecting an interface's status begins to flap, even
if the flapping is not severe. At the heavy suppression level, an
interface is prone to be suppressed. This level applies to services that
are sensitive to flappings. Enabling heavy suppression prevents
service interruptions or resource waste caused by interface flappings.

▪ middle: Intensity of middle suppression is between the light and

heavy levels.

▪ manual: If light, middle, or heavy suppression cannot meet your

requirement, you can specify manual.
e. (Optional) Run damp-interface mode tx-off

The interface is disabled from sending signals if it is under status flapping

suppression.

If an interface is under status flapping suppression, the interface can be

disabled from sending signals, so that the remote interface can detect
that the local interface is unavailable.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 35

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

If the local interface is disabled from sending signals, the remote

interface considers it Down.

If status flapping suppression on the local interface is canceled, this

interface automatically begins to send signals to the remote interface.
The remote interface then considers this interface Up.
f. Run commit

The configuration is committed.

----End

Checking the Configuration

Run the display control-flap interface interface-type interface-number command
to check the previous configuration.

Run the display damp-interface [ interface interface-type interface-number ]

command to check the status and statistics about status flapping suppression on
the interface.

1.1.2.13 Logical Interface Configuration

This section describes how to configure logical interfaces. Logical interfaces are
manually configured interfaces, which are used to exchange data. Logical
interfaces do not exist physically.

Usage Scenario
For usage scenarios of logical interfaces, see "Logical Interface" in NE9000-Feature
Description-Interface Management.

Table 1-7 Logical interface list

Feature Interface Name Configuration Guide

System DCN serial This interface is automatically created by

management interface the system.

Interface Virtual Ethernet Creating an L2VE Interface

management (VE) interface Creating an L3VE Interface

Interface Global VE interface Creating a Global-VE interface

management

Interface Loopback interface Creating a Loopback Interface and

management Configuring Its IP Address

Interface Null0 interface Entering the NULL Interface View

management

LAN access Ethernet sub- Configuring Ethernet Sub-interfaces to

and MAN interface Support Communication Between VLANs
access

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 36

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Feature Interface Name Configuration Guide

LAN access Eth-Trunk interface Eth-Trunk Interface Configuration

and MAN
access

LAN access VLANIF interface Configuring Layer 3 Communication

and MAN Between VLANIF Interfaces
access

WAN access IP-Trunk interface Configuring an IP-Trunk Interface

MPLS Tunnel interface MPLS TE Configuration

Pre-configuration Tasks
Before configuring logical interfaces, connect interfaces and set their physical
parameters to ensure that these interfaces are physically up.

1.1.2.13.1 Creating a Global-VE interface

Global-VE interfaces are independent of boards. You can create Global-VE
interfaces only if the router is powered on.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface global-ve ve-number

A Global-VE interface is created and the Global-VE interface view is displayed.

Step 3 Run commit

The configuration is committed.

----End

1.1.2.13.2 Configuring a Channelized Sub-interface

This section describes how to configure a channelized sub-interface.

Context
To prevent services from affecting each other, a mechanism to isolate different
types of services is needed. Different service flows are forwarded through different
VLAN channelized sub-interfaces with dot1q encapsulation, and each channelized
sub-interface implements independent HQoS scheduling to isolate services of
different types.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 37

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface interface-type interface-number.subinterface-number

The view of a physical sub-interface is displayed.

Step 3 Configure the sub-interface as required.

● If the sub-interface is an Ethernet one, run the vlan-type dot1q vlanid
command to set its encapsulation mode to dot1q.
Run the encapsulation qinq-termination and qinq termination pe-vid pe-
vlanid ce-vid ce-vlanid commands to set the encapsulation mode of the sub-
interface to QinQ termination.

Step 4 Run quit

Return to the system view.

Step 5 Run license

The license view is displayed.

NOTE

The channelized sub-interface license does not need to be activated on GE interfaces.

The channelized sub-interface license does not need to be activated on POS interfaces.

Step 6 Run active port-mode-channel

The license for channelized sub-interfaces is activated.

Step 7 Run quit

Return to the system view.

Step 8 Run interface interface-type interface-number.subinterface-number

The view of a physical sub-interface is displayed.

Step 9 Run mode channel enable

Channelization is enabled for the sub-interface.

Step 10 (Optional) Run mode channel bandwidth bwvalue

The bandwidth is configured for the channelized sub-interface.

Step 11 Run commit

The configuration is committed.

----End

1.1.2.13.3 Creating a Loopback Interface and Configuring an IP Address for It

IP addresses need to be configured for loopback interfaces that are always up so
that these interfaces can be used to communicate with other devices.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 38

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface loopback loopback-number

A loopback interface is created.

You can create or delete loopback interfaces as required. Once a loopback

interface is created, it remains up all the time unless it monitors an interface
monitoring group and may go down.

Step 3 Run ip address ip-address { mask | mask-length }

The IP address of the loopback interface is configured.

Step 4 Run commit

The configuration is committed.

----End

1.1.2.13.4 Entering the NULL Interface View

The system automatically creates a NULL0 interface. The NULL interface is used
for preventing routing loops and filtering traffic.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface null 0

The NULL interface view is displayed.

The NULL interface is always in the Up state but does not forward any data
packets. In addition, IP addresses cannot be configured on the NULL interface, and
data link layer protocol cannot be encapsulated on the NULL interface.

----End

Follow-up Procedure
The NULL interface is used to prevent routing loops and filtering traffic. If the ip
route-static 192.168.0.0 255.255.0.0 NULL 0 command is run, the device will
discard all packets destined for the network segments 192.168.0.1 to
192.168.255.255.

1.1.2.13.5 Verifying the Configuration

After the configuration is completed on the Global-VE interface, FlexE interface
license, FlexE interface, loopback interface, and Null interface, check the
configurations.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 39

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Prerequisites
The Global-VE interface, FlexE interface license, FlexE interface, loopback interface,
and NULL interface have been configured.

Procedure
● Run the display interface loopback [ loopback-number ] command to check
the status of the Loopback interface.
● Run the display interface null [ 0 ] command to check the status of the Null
interface.
● Run the display flexe group information slot slot-id card card-id command
to check information about groups, FlexE physical interfaces added to the
groups, and timeslot allocation in the groups on a FlexE subcard.

----End

1.1.2.14 FlexE Interface Configuration

FlexE interfaces refer to FlexE clients, which correspond to various externally
observed user interfaces on networks. Each FlexE client can be flexibly allocated
bandwidth from a group resource pool, and the bandwidth can be adjusted. In VS
mode, this feature is supported only by the admin VS.

Usage Scenario
The need for higher mobile bearer bandwidth is increasing as 5G networks
continue to evolve. In addition, customers want a unified network to transmit
various services, such as home broadband, leased line access, and mobile bearer
services. These factors place increasingly higher requirements on
telecommunication network interfaces. FlexE isolates services by isolating the
bandwidth resources of interfaces. FlexE interfaces are isolated from each other so
that traffic is isolated at the physical layer and network slicing is performed for
services on the same physical network.

FlexE applies to the access, aggregation, and core layers. As 5G services transition
through the initial, development, and maturity phases, the service volume
increases gradually. FlexE allows the bearer network to be smoothly upgraded.

Pre-configuration Tasks
Before configuring FlexE interfaces, complete the following tasks:

● Power on the device and ensure that it passes the self-check.

● Install a FlexE-capable board on the device.
● Activate the FlexE interface license on the board.

1.1.2.14.1 Activating the FlexE Interface License on a Board

To configure FlexE services on a board, you must activate the FlexE interface
license on the board first.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 40

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Pre-configuration Tasks
Before activating the FlexE interface license on a board, complete the following
tasks:
1. Run the license active file-name command to activate a specified license file
on the main control board.
2. Run the system-view command to enter the system view.
3. Run the license command to enter the license view.
4. Run the active port-basic slot slotid card cardid port port-list command to
activate the interface-specific basic hardware license.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run license
The license view is displayed.
Step 3 Run active port-flexe slot slotid card cardid port port-list
The FlexE interface license is activated on a specified board.
Step 4 Run commit
The configuration is committed.

----End

1.1.2.14.2 Configuring a Standard Ethernet Interface to Work in FlexE Mode

The bandwidth of a standard Ethernet interface is fixed. To flexibly specify the
bandwidth of an interface, you need to switch its working mode from standard
Ethernet to FlexE.

Context
After a standard Ethernet interface is switched to the FlexE mode, the system
automatically creates a FlexE physical interface and deletes the services
configured on the original interface. If the Ethernet interface is an Eth-Trunk
interface's member interface, it is also deleted from the Eth-Trunk interface.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run flexe enable port port-position
The working mode of the Ethernet interface is switched from standard Ethernet to
FlexE.
Step 3 Run commit

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 41

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

The configuration is committed.

----End

1.1.2.14.3 Configuring a PHY Number for a FlexE Physical Interface

To ensure normal communication between interconnected devices, you need to
configure the same PHY number for the FlexE physical interfaces on both of them.

Context
Different FlexE physical interfaces can be configured with the same PHY number.
However, the FlexE physical interfaces with the same PHY number cannot be
added to the same FlexE group, and a FlexE physical interface can be added to
only one FlexE group.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The view of a specified FlexE physical interface (for example, FlexE-50G 1/1/1) is
displayed.
Step 3 Run phy-number phy-number
A PHY number is configured for the FlexE physical interface.
Step 4 (Optional) Run management-channel mode { union | section | shim-to-shim |
shim-to-shim-op2 }
A management channel mode is configured for the FlexE physical interface.

Step 5 (Optional) Run down-filter disable

Down interrupt suppression is disabled on the FlexE physical interface.
Step 6 Run commit
The configuration is committed.

----End

1.1.2.14.4 Creating a FlexE Group and Binding a FlexE Physical Interface to It

After a FlexE group is created, you can bind a group of FlexE physical interfaces to
it, flexibly allocating bandwidth to FlexE clients based on the sub-timeslot
granularity.

Procedure
Step 1 Run system-view
The system view is displayed.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 42

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Step 2 Run flexe group group-index

A FlexE group is created and its view is displayed, or the view of a specified
existing FlexE group is displayed.
Step 3 Run binding interface interface-type interface-number
A specified FlexE physical interface is bound to the FlexE group.
Step 4 (Optional) Run padding enable
Padding is enabled.
Step 5 (Optional) Run timeslot-negotiation mode disable
Timeslot negotiation is disabled.

NOTE

If the timeslot mode has been configured on the FlexE card where the PHYs bound to a
FlexE group reside, ensure that the FlexE clients in the group are not bound to any sub-
timeslots before disabling timeslot negotiation.
● If the peer device does not support timeslot negotiation, you need to disable it in the
FlexE group view of the local device.
● The same timeslot negotiation mode must be configured for the FlexE groups on both
ends. Otherwise, the FlexE interfaces may fail to go up or fail to forward traffic after a
reliability operation (such as an active/standby switchover, subcard reset, or interface
shutdown/startup) is performed.
● After timeslot negotiation is disabled for the FlexE groups on both ends, the same
timeslot number must be configured for the corresponding FlexE clients. Otherwise, the
FlexE interfaces may fail to go up or fail to forward traffic.

Step 6 Run commit

The configuration is committed.

----End

1.1.2.14.5 Configuring a Number for a FlexE Group

To ensure normal communication between interconnected devices, you need to
configure the same group number for the FlexE groups to which the FlexE physical
interfaces on both devices are added.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run flexe group group-index
A FlexE group is created and its view is displayed, or the view of a specified
existing FlexE group is displayed.
Step 3 Run flexe-groupnum group-number
A group number is configured for the FlexE group.
Step 4 Run commit

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 43

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

The configuration is committed.

----End

1.1.2.14.6 (Optional) Configuring a Sub-timeslot Granularity for a FlexE Card

The sub-timeslot granularity of a FlexE card restricts the bandwidth configuration
of a FlexE client. By default, the sub-timeslot granularity of a FlexE card is 5
Gbit/s.

Context
To configure a bandwidth lower than 5 Gbit/s for a FlexE client, set the sub-
timeslot granularity of the FlexE client to 1 Gbit/s first.
Bandwidth configuration rules for FlexE clients based on different sub-timeslot
granularities are as follows:
● If the sub-timeslot granularity is 5 Gbit/s (default value), the bandwidth of a
FlexE client can be set to an integer multiple of 5 Gbit/s, such as 5 Gbit/s, 10
Gbit/s, or 15 Gbit/s.
● If the sub-timeslot granularity is 1 Gbit/s, the bandwidth of a FlexE client can
be set to 1 Gbit/s, 2 Gbit/s, 3 Gbit/s, 4 Gbit/s, or an integer multiple of 5
Gbit/s.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run set flexe sub-time-slot granula slot slotid card cardid { 1g | 5g }
A sub-timeslot granularity is configured for a specified FlexE card.
Step 3 Run commit
The configuration is committed.

----End

1.1.2.14.7 (Optional) Configuring a Mode for a FlexE Card

FlexE cards support timeslot and bandwidth modes. The bandwidth mode is
recommended.

Context
● Timeslot mode: A timeslot number to be allocated to a FlexE client is
statically specified when the client is configured.
● Bandwidth mode: Only the needed bandwidth is specified when a FlexE client
is configured, and the device automatically allocates the corresponding
timeslot.
NOTE

By default, the bandwidth mode is used for a FlexE card.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 44

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run slot slot-id

The slot view is displayed.

Step 3 Run flexe config-mode card cardid { bandwidth | timeslot }

The bandwidth or timeslot mode is configured for a specified FlexE card.

Step 4 Run commit

The configuration is committed.

----End

1.1.2.14.8 Creating a FlexE Client and Configuring an ID and Bandwidth for It

FlexE clients correspond to externally observed user interfaces. Each FlexE client
can be flexibly allocated bandwidth from a group resource pool, and the
bandwidth can be adjusted.

Context
To ensure that the FlexE clients on both ends can communicate with each other,
you need to configure the same ID and bandwidth for them.

Table 1-8 Numbers of physical ports that can be added to the same group and
port-id value ranges for different subcard models

Model Numbers of Physical port-id Value Range

Ports that Can Be Added
to the Same Group

CR9P9KHAL 0, 1 20-39, 1000-3000

M8B
2, 3 40-59, 1000-3000

4 60-69, 1000-3000

5 70-79, 1000-3000

6, 7 80-99, 1000-3000

8, 9 100-119, 1000-3000

10, 11 120-139, 1000-3000

12, 13 140-159, 1000-3000

14 160-169, 1000-3000

15 170-179, 1000-3000

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 45

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Model Numbers of Physical port-id Value Range

Ports that Can Be Added
to the Same Group

16, 17 180-199, 1000-3000

18, 19 200-219, 1000-3000

CR9D00EEN 0, 1 20-39, 1000-3000

B83
2, 3 40-59, 1000-3000

4 60-69, 1000-3000

5 70-79, 1000-3000

6, 7 80-99, 1000-3000

8, 9 100-119, 1000-3000

10, 11 120-139, 1000-3000

12, 13 140-159, 1000-3000

14 160-169, 1000-3000

15 170-179, 1000-3000

16, 17 180-199, 1000-3000

18, 19 200-219, 1000-3000

CR9D00EEN 0, 1 20-39, 1000-3000

B84
2, 3 40-59, 1000-3000

4 60-69, 1000-3000

5 70-79, 1000-3000

6, 7 80-99, 1000-3000

8, 9 100-119, 1000-3000

10, 11 120-139, 1000-3000

12, 13 140-159, 1000-3000

14 160-169, 1000-3000

15 170-179, 1000-3000

16, 17 180-199, 1000-3000

18, 19 200-219, 1000-3000

CR9D00EKN 0, 2, 4, 6 40-69, 1000-3000

B8R
1, 3, 5, 7 70-99, 1000-3000

10, 12, 14, 16 100-129, 1000-3000

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 46

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Model Numbers of Physical port-id Value Range

Ports that Can Be Added
to the Same Group

11, 13, 15, 17 130-159, 1000-3000

20, 22, 24, 26 160-189, 1000-3000

21, 23, 25, 27 190-219, 1000-3000

30, 32, 34, 36 220-249, 1000-3000

31, 33, 35, 37 250-279, 1000-3000

CR9D00EKN 0, 2, 4, 6 40-69, 1000-3000

B8Q
1, 3, 5, 7 70-99, 1000-3000

10, 12, 14, 16 100-129, 1000-3000

11, 13, 15, 17 130-159, 1000-3000

20, 22, 24, 26 160-189, 1000-3000

21, 23, 25, 27 190-219, 1000-3000

30, 32, 34, 36 220-249, 1000-3000

31, 33, 35, 37 250-279, 1000-3000

CR58EENBH 0, 2, 4, 6 20-49, 1000-3000

S0
1, 3, 5, 7 50-79, 1000-3000

10, 12, 14, 16 80-109, 1000-3000

11, 13, 15, 17 110-139, 1000-3000

CR58E8KE8N 0 1000-3000
CS0
1 1000-3000

4 1000-3000

5 1000-3000

8 1000-3000

9 1000-3000

12 1000-3000

13 1000-3000

Procedure
Step 1 Run system-view
The system view is displayed.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 47

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Step 2 Run flexe client-instance clientindex [ flexe-group groupIndex flexe-type { cross

| full-function } [ port-id portid ] ]
A FlexE client is created and its view is displayed.
Step 3 Run flexe-clientid clientid
An ID is configured for the FlexE client.
Step 4 Configure bandwidth for the FlexE client.
● If the bandwidth mode is configured for the FlexE card, run the flexe-
bandwidth { 1 | 2 | 3 | 4 | bandwidth-value } command to configure
bandwidth for the FlexE client.
● If the timeslot mode is configured for the FlexE card, run the binding
interface interface-type interface-number time-slot timeslot-list [ sub-time-
slot subtime-slot ] command to bind one or more sub-timeslots to the FlexE
client. The bound sub-timeslots constitute the bandwidth of the FlexE client.
Step 5 (Optional) Run minimal available bandwidth percent
The minimum available bandwidth percentage is configured for the FlexE client.
Step 6 Run commit
The configuration is committed.
----End

1.1.2.14.9 Adding a FlexE NE in an Ethernet Service Scenario

Adding a FlexE NE to a live network running Ethernet services involves the
connection between a FlexE physical interface and standard Ethernet interface. If
DCN auto-negotiation is enabled on the FlexE physical interface, the two
interfaces can automatically communicate with each other, and the NMS can
manage the FlexE NE.

Usage Scenario
As shown in Figure 1-2, DeviceA and DeviceB on the live network work in
standard Ethernet mode and do not support DCN auto-negotiation on FlexE
physical interfaces. The new NE DeviceC works in FlexE mode and supports DCN
auto-negotiation on FlexE physical interfaces.

Figure 1-2 Adding a FlexE NE to a live network running Ethernet services

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 48

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

After DeviceC is added, the underlying working mode of the FlexE physical
interfaces automatically switches from FlexE to standard Ethernet within about
10s because DCN auto-negotiation is enabled on them by default. The NMS can
then manage DeviceC.
● If you run the following commands on DeviceC within 20 minutes of being
added, the configuration takes effect immediately to ensure DCN continuity.
a. Run the force-physical-mode ethernet command to forcibly switch the
underlying working mode of the FlexE physical interface to standard
Ethernet.
NOTE

By default, the underlying working mode of a FlexE physical interface

automatically switches from standard Ethernet back to FlexE after 20 minutes.
b. To change the time for switching the underlying working mode of a FlexE
physical interface from standard Ethernet back to FlexE, or to disable a
FlexE physical interface from switching from the standard Ethernet mode
back to the FlexE mode, perform the following operations:

▪ Run the phyautoclear forcephysicalmode enable cleartime

command to set the time for switching the underlying working mode
of the FlexE physical interface from standard Ethernet back to FlexE.

▪ Run the phyautoclear forcephysicalmode disable command to

disable the underlying working mode of the FlexE physical interface
from switching from standard Ethernet back to FlexE.
● If the preceding commands are not run on DeviceC within 20 minutes of
being added, the underlying working mode of the FlexE physical interfaces on
DeviceC is switched from the standard Ethernet mode to the FlexE mode at
the 20-minute mark. DCN auto-negotiation is then performed 10 seconds
later to implement DCN connectivity. As a result, the NMS cannot manage
DeviceC for about 10 seconds, and the process repeats.
If you want to change the services on the live network to the FlexE mode, perform
the following steps:

Procedure
Step 1 Run the flexe enable port port-position command on DeviceA to switch the
working mode of the Ethernet interface from standard Ethernet to FlexE. Because
the underlying working mode of the FlexE physical interface on DeviceC has been
switched to standard Ethernet, the DCN channel between DeviceA and DeviceC is
interrupted, and DeviceC is disconnected from the NMS.
Step 2 Change the status of the FlexE physical interface on DeviceA manually, triggering
the underlying working mode of DeviceC's FlexE physical interface connected to
the FlexE physical interface on DeviceA to quickly switch back to the FlexE mode.
You can perform the following operations:
● Run the laser turn-off command on DeviceA to disable the optical module
laser, and then run the laser turn-on command to enable the optical module
laser.
● Run the shutdown command on DeviceA to disable the interface, and then
run the undo shutdown command to enable the interface.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 49

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

After the preceding operations are complete, the FlexE physical interface
connecting DeviceC to DeviceA is switched back to the FlexE mode. The two
devices are now successfully connected using FlexE, and the NMS can continue to
manage DeviceC.

NOTE

In the preceding scenarios, the operations on DeviceB are the same as those on DeviceA.

----End

1.1.2.14.10 Adding a FlexE or Ethernet NE in a FlexE Service Scenario

Adding an Ethernet NE to a live network running FlexE services involves the
connection between a FlexE physical interface and standard Ethernet interface. If
DCN auto-negotiation is enabled on the FlexE physical interface, the two
interfaces can automatically communicate with each other, and the NMS can
manage the FlexE NE.

Usage Scenario
● Adding a FlexE NE to a live network running FlexE services
As shown in Figure 1-3, DeviceA and DeviceB work in FlexE mode on the live
network, and the new NE DeviceC also works in FlexE mode.

Figure 1-3 Adding a FlexE NE to a live network running FlexE services

After DeviceC is added, it successfully connects to DeviceA and DeviceB

because they all work in FlexE mode. In this case, the NMS can directly
manage DeviceC.
● Adding an Ethernet NE to a live network running FlexE services
As shown in Figure 1-4, DeviceA and DeviceB work in FlexE mode on the live
network, and the new NE DeviceC works in Ethernet mode.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 50

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Figure 1-4 Adding an Ethernet NE to a live network running FlexE services

For different scenarios, you can perform the corresponding operations to

ensure that the new Ethernet NE can be successfully connected and managed
by the NMS.
NOTE

In the following scenarios, the operations on DeviceB are the same as those on
DeviceA.

Procedure
● If DeviceA supports DCN auto-negotiation on FlexE physical interfaces, but
DeviceC does not:
After DeviceC is added, the underlying working mode of the FlexE physical
interface on DeviceA automatically switches from FlexE to standard Ethernet
within about 10s because DCN auto-negotiation is enabled on the FlexE
physical interface by default. The NMS can then manage DeviceC.
– If you run the following commands on DeviceA within 20 minutes of
being added, the configuration takes effect immediately to ensure DCN
continuity.
i. Run the system-view command to enter the system view.
ii. Run the interface interface-type interface-number command to
enter the view of a specified FlexE physical interface (for example,
FlexE-50G 1/0/0).
iii. Run the force-physical-mode ethernet command to forcibly switch
the underlying working mode of the FlexE physical interface to
standard Ethernet.
NOTE

By default, the underlying working mode of a FlexE physical interface

automatically switches from standard Ethernet back to FlexE after 20
minutes.
iv. To change the time for switching the underlying working mode of a
FlexE physical interface from standard Ethernet back to FlexE, or to
disable a FlexE physical interface from switching from the standard
Ethernet mode back to the FlexE mode, perform the following
operations:

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 51

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

○ Run the phyautoclear forcephysicalmode enable cleartime

command to set the time for switching the underlying working
mode of the FlexE physical interface from standard Ethernet
back to FlexE.
○ Run the phyautoclear forcephysicalmode disable command to
disable the underlying working mode of the FlexE physical
interface from switching from standard Ethernet back to FlexE.
– If the preceding commands are not run on DeviceA within 20 minutes of
being added, the underlying working mode of the FlexE physical interface
on DeviceA is switched from the standard Ethernet mode to the FlexE
mode at the 20-minute mark. DCN auto-negotiation is then performed
10 seconds later to implement DCN connectivity. As a result, the NMS
cannot manage DeviceC for about 10 seconds, and the process repeats.
If you want to continue to run FlexE services on the live network, perform the
following operations:
a. Run the flexe enable port port-position command on DeviceC to switch
the working mode of the Ethernet interface from standard Ethernet to
FlexE. Because the underlying working mode of the FlexE physical
interface on DeviceA has been switched to standard Ethernet, the DCN
channel between DeviceC and DeviceA is interrupted, and DeviceC is
disconnected from the NMS.
b. Change the status of the FlexE physical interface on DeviceC manually,
triggering the underlying working mode of DeviceA's FlexE physical
interface connected to the FlexE physical interface on DeviceC to quickly
switch back to the FlexE mode. You can perform the following operations:

▪ Run the laser turn-off command on DeviceC to disable the optical

module laser, and then run the laser turn-on command to enable
the optical module laser.

▪ Run the shutdown command on DeviceC to disable the interface,

and then run the undo shutdown command to enable the interface.
After the preceding operations are complete, the FlexE physical interface
connecting DeviceA to DeviceC is switched back to the FlexE mode. The two
devices are now successfully connected using FlexE, and the NMS can
continue to manage DeviceC.
● If both DeviceA and DeviceC support DCN auto-negotiation on FlexE physical
interfaces:
After DeviceC is added, the underlying working mode of the FlexE physical
interface on DeviceA automatically switches from FlexE to standard Ethernet
within about 10s because DCN auto-negotiation is enabled on the FlexE
physical interface by default. The NMS can then manage DeviceC.
DeviceC supports DCN auto-negotiation on FlexE physical interfaces, and this
function is enabled by default. To continue to run FlexE services on the live
network, run the flexe enable port port-position command on DeviceC to
switch the working mode of the Ethernet interface from standard Ethernet to
FlexE.
● If DeviceA does not support DCN auto-negotiation on FlexE physical
interfaces, but DeviceC does:

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 52

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

After DeviceC is added, run the force-physical-mode ethernet command on

DeviceA to forcibly switch the underlying working mode of the FlexE physical
interface to standard Ethernet. In this case DeviceC can communicate with
DeviceA and can be managed by the NMS.
If you want to continue to run FlexE services on the live network, perform the
following operations:
a. Run the flexe enable port port-position command on DeviceC to switch
the working mode of the Ethernet interface from standard Ethernet to
FlexE. DeviceC supports DCN auto-negotiation on FlexE physical
interfaces, and this function is enabled by default. Therefore, the
underlying working mode of the FlexE physical interfaces automatically
switches from FlexE to standard Ethernet within about 10s.
b. Run the undo force-physical-mode command on DeviceA to restore the
underlying working mode of the FlexE physical interface to FlexE.
c. Change the status of the FlexE physical interface on DeviceA manually,
triggering the underlying working mode of DeviceC's FlexE physical
interface connected to the FlexE physical interface on DeviceA to quickly
switch back to the FlexE mode. You can perform the following operations:

▪ Run the laser turn-off command on DeviceA to disable the optical

module laser, and then run the laser turn-on command to enable
the optical module laser.

▪ Run the shutdown command on DeviceA to disable the interface,

and then run the undo shutdown command to enable the interface.
After the preceding operations are complete, the FlexE physical interface
connecting DeviceC to DeviceA is switched back to the FlexE mode. The two
devices are now successfully connected using FlexE, and the NMS can
continue to manage DeviceC.
----End

1.1.2.14.11 (Optional) Configuring a Time Synchronization Mode for a FlexE

Physical Interface
The FlexE standards define two 1588v2 message transmission modes: Overhead
(OH) and Client. By default, 1588v2 messages are transmitted in OH mode.

Context
● OH mode: Clock messages are transmitted using FlexE overhead timeslots.
The configuration related to clock synchronization is the same as that on a
standard Ethernet interface.
● Client mode: Clock messages are transmitted using FlexE clients. In this mode,
the FlexE interface that carries clock services must be bound to a FlexE
physical interface that has clock services deployed.

Pre-configuration Tasks
1588v2 has been configured, no matter which mode is used to transmit 1588v2
messages. For details, see HUAWEI NetEngine9000 Core Router Configuration
Guide > System Management.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 53

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

After 1588v2 is configured on a FlexE physical interface, 1588v2 messages are

transmitted in OH mode by default. To change the transmission mode of 1588v2
messages to Client, perform the following steps.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface interface-type interface-number

The view of a specified FlexE physical interface (for example, FlexE-50G 1/0/0) is
displayed.

Step 3 Run clock binding flexe interface iftype ifnum

A specified FlexE interface carrying clock services is bound to the FlexE physical
interface.

Step 4 Run commit

The configuration is committed.

----End

1.1.2.14.12 Verifying the Configuration

After configuring a FlexE interface, verify the configuration.

Prerequisites
A FlexE interface has been configured.

Procedure
● Run the display license resource usage port-flexe { all | slot slotid } [ active
| deactive ] command to check information about FlexE interface licenses on
boards.
● Run the display flexe group information slot slot-id card card-id command
to check the group information of a FlexE card.
● Run any of the following commands to check information about FlexE service
interfaces, FlexE physical interfaces, and physical interfaces bound to a FlexE
group:
– display flexe client information [ interface { interface-type interface-
number | interface-name } ]
– display flexe client information [ index clientindex ]
– display flexe physical-interface information [ interface { interface-type
interface-number | interface-name } } ]
● Run the display interface ethernet brief command to check brief
information about FlexE interfaces.
● Run the display interface flexe interface-number command to check the
running status and statistics of a FlexE interface.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 54

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● Run the display lldp neighbor brief command to check brief information
about LLDP neighbors of FlexE interfaces.

----End

1.1.2.15 Interface Group Configuration

An interface group can be used to perform interface configuration in batches,
simplifying interface configurations and reducing management costs.

Context
Interface groups are classified into permanent and temporary interface groups.
Multiple interfaces can be added to the same permanent or temporary interface
group to enable batch command configurations for the interfaces. The differences
between permanent and temporary interface groups are described as follows:
● After a user exits the view of a temporary interface group, the system
automatically deletes the temporary interface group. A permanent interface
group, however, can be deleted only by using the undo port-group command.
● Information about a permanent interface group can be viewed using the
display port-group command, whereas information about a temporary
interface group cannot.
● After a permanent interface group is configured, a configuration file is
generated. However, no configuration file is generated after a temporary
interface group is configured.

Procedure
● Configure a permanent interface group.
a. Run system-view

The system view is displayed.

b. Run port-group port-group-name

A permanent interface group is created and the view of the permanent

interface group is displayed.
c. Run group-member { interface-type interface-number1 [ to interface-
type interface-number2 ] } &<1-10>
Specified interfaces are added to the permanent interface group.
d. Run commit

The configuration is committed.

● Configure a temporary interface group.
a. Run system-view

The system view is displayed.

b. Run port-group group-member { interface-type-start interface-number-
start [ to interface-type-end interface-number-end ] } &<1-10>
A temporary interface group is created, and specified interfaces are added
to the group.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 55

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

NOTE

● If the shutdown or undo shutdown command is run for a permanent interface

group and the configuration is committed, the configuration is not recorded in the
configuration file.
c. Run commit
The configuration is committed.
----End

Verifying the Configuration

After the configuration is complete, run the display port-group [ all | port-group-
name ] command to view information about a specified permanent interface
group or all permanent interface groups.

1.1.2.16 Configuring an Interface Monitoring Group

You can configure an interface monitoring group in a dual-device backup scenario
to allow the user-side interface status to change with the network-side interface
status so that traffic can be switched between the master and backup links.

Usage Scenario
When a network-side interface goes Down in a dual-device backup scenario, user-
side devices cannot detect the Down event and therefore do not switch traffic to
the backup link. As a result, traffic overloads or interruptions occur. To prevent
these problems, you can configure an interface monitoring group to monitor the
network-side interface status and instruct the user-side interface to change its
status accordingly. An interface monitoring group allows traffic to be switched
between the master and backup links and prevents traffic overloads or
interruptions.
On the network shown in Figure 1-5, PE2 backs up PE1. NPE1 through NPEM on
the user side is dual-homed to the two PEs to load-balance traffic, and the two
PEs are connected to DeviceA through DeviceN on the network side. When only
the link between PE1 and DeviceN is available and all the links between PE1 and
all the other routers fail, the NPEs do not detect the failure and continue sending
packets to DeviceN through PE1. As a result, the link between PE1 and DeviceN
becomes overloaded.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 56

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Figure 1-5 Typical application of an interface monitoring group

To resolve this problem, you can configure an interface monitoring group and add
multiple network-side interfaces on the PEs to the interface monitoring group.
When a link failure occurs on the network side and the interface monitoring group
detects that the status of a certain proportion of network-side interfaces changes,
the system instructs the user-side interfaces associated with the interface
monitoring group to change their status accordingly and allows traffic to be
switched between the master and backup links. Therefore, the interface
monitoring group can be used to prevent traffic overloads or interruptions.

Pre-configuration Tasks
Before configuring an interface monitoring group, configure physical attributes for
interfaces on the router.

Procedure
Step 1 Run system-view

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 57

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

The system view is displayed.

Step 2 Run monitor-group monitor-group-name
An interface monitoring group is created, and the interface monitoring group view
is displayed.
Step 3 Run binding interface interface-type interface-number [ down-weight down-
weight-value ]
An interface is added to the interface monitoring group.
The interface added to an interface monitoring group is called a binding interface.
A binding interface is located on the network side and a track interface on the
user side. An interface monitoring group monitors the binding interface status and
allows the track interfaces to change their status accordingly.
You can repeat this step to add multiple binding interfaces to an interface
monitoring group.
Step 4 Run quit
Exit from the interface monitoring group view.
Step 5 Run interface interface-type interface-number
The view of the specified interface on the user side is displayed.
Step 6 Run track monitor-group monitor-group-name [ trigger-down-weight trigger-
down-weight-value ]
The interface is associated with an interface monitoring group.
The user-side interface associated with an interface monitoring group is called a
track interface.
You can repeat steps 5 and 6 to associate multiple track interfaces to an interface
monitoring group.
If the down weight sum of all the binding interfaces in the monitoring group is
greater than or equal to the value specified using trigger-down-weight-value on
the track interface, the track interface goes down, and service traffic is switched to
the backup link. Otherwise, the track interface goes up, and service traffic is
switched back to the primary link.
Step 7 Run quit
Exit from the interface view.
Step 8 Run monitor-group monitor-group-name
The view of the created interface monitoring group is displayed.
Step 9 (Optional) Run trigger-up-delay trigger-up-delay-value
The delay after which a track interface goes Up is set.
Step 10 Run monitor enable
The monitoring function is enabled.
Step 11 Run commit

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 58

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

The configuration is committed.

----End

Verifying the Configuration

Run the display monitor-group [ monitor-group-name ] command to view
information about an interface monitoring group.

1.1.2.17 Maintaining Interfaces

The reset commands help locate faults on interfaces.

1.1.2.17.1 Clearing Interface Statistics

Before collecting traffic statistics within a specified period of time on an interface,
you must clear existing statistics on the interface.

Context

NOTICE

Statistics cannot be restored after being cleared. Exercise caution when running
the following commands.

Procedure
● To clear the traffic statistics on an interface, run the reset counters interface
command in the user view.

----End

1.1.2.17.2 Monitoring Interface Information

Monitoring interface statistics helps you analyze network information based on
traffic statistics and rates.

Procedure
● Run the monitor interface-statistics interface-type interface-number &<1-5>
[ interval interval-value | times { times-value | infinity } ] * command in any
view to check traffic statistics on a specified interface.
● Run the monitor interface-statistics batch [ interface-type [ interface-
number-begin [ to interface-number-end ] ] ] [ interval interval-value | times
{ times-value | infinity } ] * [ main ] command in any view to check traffic
statistics on interfaces in a batch.
● Run the monitor interface-information interface interface-type interface-
number [ interval interval-value | times { times-value | infinity } ] *
command in any view to check detailed information, including the running
status and traffic statistics, on a specified interface.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 59

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● Run the monitor counters bit [ rate ] interface interface-type interface-

number [ interval interval-value | times { times-value | infinity } ] *
command in any view to monitor traffic statistics on an interface. The traffic
statistics include the number of unicast, multicast, and broadcast packets sent
or received by the interface and the packet transmission rate.
----End

1.1.2.18 Configuration Examples for Interface Management

This section provides interface management examples.

1.1.2.18.1 Example for Managing Interfaces

This section uses an example to describe how to configure interface parameters,
such as the interface description, maximum transmission unit (MTU), and interval
at which traffic statistics are collected.

Networking Requirements
To ensure smooth communication between devices on a network, you need to
configure both physical and logical interfaces properly and set the following
parameters:
● Interface description
● MTU
● Trap threshold for the outbound and inbound bandwidth usage on a specified
interface
● Interval at which traffic statistics are collected
● Whether the device sends a trap message to the network management
system (NMS) when the interface status changes
● Whether the control-flap function is enabled

Configuration Roadmap
The configuration roadmap is as follows:
1. Configure a description for an interface.
2. Set an MTU for the interface to ensure successful packet transmission over
the interface.
3. Set the interval at which traffic statistics (including the traffic volumes and
rates) are collected globally.
4. Create a sub-interface and set an MTU for the sub-interface so that packets
can reach the receiver.

Data Preparation
To complete the configuration, you need the following data:
● Interface name
● Interface description

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 60

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● Interface MTU
● Interval at which traffic statistics are collected globally
● Sub-interface MTU

Procedure
Step 1 Configure a description for an interface.
<HUAWEI> system-view
[~HUAWEI] interface gigabitethernet 2/0/0
[~HUAWEI-GigabitEthernet2/0/0] description for IFM
[*HUAWEI-GigabitEthernet2/0/0] commit

Step 2 Set an MTU for the interface.

[~HUAWEI-GigabitEthernet2/0/0] mtu 1000
[*HUAWEI-GigabitEthernet2/0/0] commit
[~HUAWEI-GigabitEthernet2/0/0] quit

Step 3 Set the interval at which traffic statistics are collected globally.
[~HUAWEI] set flow-stat interval 100
[*HUAWEI] commit

Step 4 Create a sub-interface and set the MTU of the sub-interface.

[~HUAWEI] interface gigabitethernet 2/0/0.1
[*HUAWEI-GigabitEthernet2/0/0.1] mtu 800
[*HUAWEI-GigabitEthernet2/0/0.1] commit

----End

Configuration Files
#
sysname HUAWEI
#
set flow-stat interval 100
#
interface gigabitethernet2/0/0
description for IFM
mtu 1000
#
interface gigabitethernet2/0/0.1
mtu 800
#
return

1.1.2.18.2 Example for Configuring FlexE Interfaces

This section provides an example for configuring interfaces on two devices that
are connected using FlexE.

Networking Requirements
On the network shown in Figure 1-6, FlexE clients need to be created on DeviceA
and DeviceB for communication. Different bandwidths are configured for the FlexE
clients to meet requirements for diversified services and applications. The
bandwidths of FlexE Client1, FlexE Client2, FlexE Client3, and FlexE Client4 need to
be set to 4 Gbit/s, 5 Gbit/s, 15 Gbit/s, and 20 Gbit/s, respectively.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 61

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Figure 1-6 Networking diagram for configuring FlexE interfaces

NOTE

In this example, interface 0, interface 1, interface 2, interface 3, and interface 4 represent

FlexE-50G 1/1/1, FlexE 1/1/129, FlexE 1/1/130, FlexE 1/1/131, and FlexE 1/1/132,
respectively.

Precautions
When you configure FlexE interfaces, note the following:
● To ensure normal communication between interconnected devices, you need
to configure the same PHY number for the FlexE physical interfaces on both
of them.
● To ensure normal communication between interconnected devices, you need
to configure the same group number for the FlexE groups to which the FlexE
physical interfaces on both devices are added.
● To ensure that the FlexE clients on both ends can communicate with each
other, you need to configure the same ID and bandwidth for them.

Configuration Roadmap
The configuration roadmap is as follows:
1. Activate the FlexE interface license on a board.
2. Configure a standard Ethernet interface to work in FlexE mode.
3. Configure a PHY number for a FlexE physical interface.
4. Create a FlexE group and bind the FlexE physical interface to it.
5. Configure a number for the FlexE group.
6. Configure a sub-timeslot granularity for a FlexE card.
7. Create a FlexE client and configure an ID and bandwidth for it.
8. Configure an IP address for each interface.

Data Preparation
To complete the configuration, you need the following data:

● PHY number of a FlexE physical interface: 5

● Index of a FlexE group: 1
● Number of a FlexE group: 2345
● Sub-timeslot granularity of a FlexE card: 1 Gbit/s

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 62

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● IDs of four FlexE interfaces: port numbers of interface 1, interface 2, interface

3, and interface 4
● IDs of four FlexE clients: 1, 2, 3, and 4 (corresponding to 4 Gbit/s, 5 Gbit/s, 15
Gbit/s, and 20 Gbit/s bandwidths, respectively)

Procedure
Step 1 Activate the FlexE interface license on a board.
<DeviceA> license active XXXXX.dat
<DeviceA> system-view
[~DeviceA] license
[~DeviceA-license] active port-basic slot 1 card 1 port 1
[*DeviceA-license] active port-flexe slot 1 card 1 port 1
[*DeviceA-license] commit
[~DeviceA-license] quit

Step 2 Configure a standard Ethernet interface to work in FlexE mode.

[~DeviceA] flexe enable port 1/1/1
Warning: This operation will delete interface 50GE1/1/1 and related services. Continue? [Y/N]:y
[*DeviceA] commit

Step 3 Configure a PHY number for a FlexE physical interface.

[~DeviceA] interface FlexE-50G 1/1/1
[~DeviceA-FlexE-50G1/1/1] phy-number 5
Warning: The traffic on this interface may be interrupted if the operation is performed. Continue? [Y/N]:y
[*DeviceA-FlexE-50G1/1/1] commit
[~DeviceA-FlexE-50G1/1/1] quit

Step 4 Create a FlexE group and bind the FlexE physical interface to it.
[~DeviceA] flexe group 1
[*DeviceA-flexe-group-1] binding interface FlexE-50G1/1/1

Step 5 Configure a number for the FlexE group.

[*DeviceA-flexe-group-1] flexe-groupnum 2345
Warning: The traffic on related clients may be interrupted if the operation is performed. Continue? [Y/N]:y
[*DeviceA-flexe-group-1] commit
[~DeviceA-flexe-group-1] quit

Step 6 Configure a sub-timeslot granularity for a FlexE card.

[~DeviceA] set flexe sub-time-slot granula slot 1 card 1 1g
[*DeviceA] commit

Step 7 Create a FlexE client and configure an ID and bandwidth for it.
[~DeviceA] flexe client-instance 1 flexe-group 1 flexe-type full-function port-id 129
[*DeviceA-flexe-client-1] flexe-clientid 1
Warning: The traffic on this interface may be interrupted if the operation is performed. Continue? [Y/N]:y
[*DeviceA-flexe-client-1] flexe-bandwidth 4
[*DeviceA-flexe-client-1] commit
[~DeviceA-flexe-client-1] quit
[~DeviceA] flexe client-instance 2 flexe-group 1 flexe-type full-function port-id 130
[*DeviceA-flexe-client-2] flexe-clientid 2
Warning: The traffic on this interface may be interrupted if the operation is performed. Continue? [Y/N]:y
[*DeviceA-flexe-client-2] flexe-bandwidth 5
[*DeviceA-flexe-client-2] commit
[~DeviceA-flexe-client-2] quit
[~DeviceA] flexe client-instance 3 flexe-group 1 flexe-type full-function port-id 131
[*DeviceA-flexe-client-3] flexe-clientid 3
Warning: The traffic on this interface may be interrupted if the operation is performed. Continue? [Y/N]:y
[*DeviceA-flexe-client-3] flexe-bandwidth 15
[*DeviceA-flexe-client-3] commit
[~DeviceA-flexe-client-3] quit
[~DeviceA] flexe client-instance 4 flexe-group 1 flexe-type full-function port-id 132
[*DeviceA-flexe-client-4] flexe-clientid 4
Warning: The traffic on this interface may be interrupted if the operation is performed. Continue? [Y/N]:y

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 63

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

[*DeviceA-flexe-client-4] flexe-bandwidth 20
[*DeviceA-flexe-client-4] commi
[~DeviceA-flexe-client-4] quit

Step 8 Configure an IP address for each interface. For configuration details, see
Configuration Files in this section.

Step 9 Repeat the preceding steps on DeviceB. For configuration details, see
Configuration Files in this section.

Step 10 Verify the configuration.

After completing the preceding configuration, run the display flexe group
information command on DeviceA and DeviceB to check group information of
FlexE cards. The command output on DeviceA is used as an example.
[~DeviceA] display flexe group information slot 9 card 1
FlexE Card Info:
=============================================================
FlexE Config Mode : Bandwidth
=============================================================

FlexE Group Info:

=============================================================
GroupID Total Bandwidth(M) Valid Bandwidth(M)
------------------------------------------------------
1 50000 50000
=============================================================

FlexE Group Binding Interfaces Capability:

=============================================================
-------------------------------------------------------------
GroupID Interfaces already bound Interfaces can be bound
-------------------------------------------------------------
1 FlexE-50G1/1/1
-------------------------------------------------------------
=============================================================

FlexE Phy Info:

=============================================================
Port No : FlexE-50G1/1/1
Active Status :1
Cfg Group ID :1
Cfg Group No : 2345
Real TX Group No : 2345
Real RX Group No : 2345
Remote Group No : 2345
Cfg Phy No :5
Real TX Phy No :5
Real RX Phy No :5
Remote Phy No :5
=============================================================

FlexE Time Slot Info:

=============================================================

------------------------------------------------------
port-no : FlexE-50G1/1/1
ts-num : 20
sub-ts-num :5
-------------------------------------------------------
time-slot-id ts-port-map
-------------------------------------------------------
0: [129][129][129][129][130]
1: [130][130][130][130][131]
2: [131][131][131][131][131]
3: [131][131][131][131][131]
4: [131][131][131][131][132]

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 64

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

5: [132][132][132][132][132]
6: [132][132][132][132][132]
7: [132][132][132][132][132]
8: [132][132][132][132][-]
9: [-][-][-][-][-]
10: [-][-][-][-][-]
11: [-][-][-][-][-]
12: [-][-][-][-][-]
13: [-][-][-][-][-]
14: [-][-][-][-][-]
15: [-][-][-][-][-]
16: [-][-][-][-][-]
17: [-][-][-][-][-]
18: [-][-][-][-][-]
19: [-][-][-][-][-]
=============================================================

FlexE Client Info:

=============================================================
---------------------------------------------------
Instance Index Port Name
---------------------------------------------------
129 FlexE1/1/129
130 FlexE1/1/130
131 FlexE1/1/131
132 FlexE1/1/132
---------------------------------------------------
=============================================================

Run the display interface ethernet brief command on DeviceA and DeviceB to
check brief information about FlexE interfaces. The command output on DeviceA
is used as an example.
[~DeviceA] display interface ethernet brief
PHY: Physical
*down: administratively down
^down: standby
(l): loopback
(b): BFD down
(d): Dampening Suppressed
(p): port alarm down
InUti/OutUti: input utility/output utility
Interface PHY Auto-Neg Duplex Bandwidth InUti OutUti Trunk
FlexE1/1/129 up - full 4G 0.01% 0.01% --
FlexE1/1/130 up - full 5G 0.01% 0.01% --
FlexE1/1/131 up - full 15G 0.01% 0.01% --
FlexE1/1/132 up - full 20G 0.01% 0.01% --
FlexE-50G1/1/1 up - full 50G -- -- --

Run the display lldp neighbor brief command on DeviceA and DeviceB to check
brief information about LLDP neighbors of FlexE interfaces. The command output
on DeviceA is used as an example.
[~DeviceA] display lldp neighbor brief
Local Intf Neighbor Dev Neighbor Intf Exptime (sec)
--------------------------------------------------------------------------------------
FlexE1/1/129 DeviceB FlexE1/1/129 114
FlexE1/1/130 DeviceB FlexE1/1/130 114
FlexE1/1/131 DeviceB FlexE1/1/131 114
FlexE1/1/132 DeviceB FlexE1/1/132 114
FlexE-50G1/1/1 DeviceB FlexE-50G1/1/1 95

Run the display interface flexe interface-number command on DeviceA and

DeviceB to check the running status and statistics of a FlexE interface. The
following example uses the command output on FlexE 1/1/129 of DeviceA.
[~DeviceA] display interface flexe 1/1/129
FlexE1/1/129 current state : UP (ifindex: 285)
Line protocol current state : UP
Last line protocol up time : 2021-03-11 09:11:24
Link quality grade : GOOD

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 65

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Description:
Route Port,The Maximum Transmit Unit is 1500
Internet Address is 10.1.1.1/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc12-3456
Port BW: 4G
Pause Flowcontrol: Receive Enable and Send Enable
Client-id Match State: Match
Last physical up time : 2021-03-10 15:11:46
Last physical down time : 2021-03-10 15:11:29
Current system time: 2021-03-11 11:36:52
Statistics last cleared:never
Last 300 seconds input rate: 10031 bits/sec, 1 packets/sec
Last 300 seconds output rate: 10041 bits/sec, 1 packets/sec
Input peak rate 125150137 bits/sec, Record time: 2021-03-10 09:25:57
Output peak rate 125757954 bits/sec, Record time: 2021-03-10 09:25:57
Input: 7006191780 bytes, 52343200 packets
Output: 7024402448 bytes, 52482810 packets
Input:
Unicast: 52334185 packets, Multicast: 9010 packets
Broadcast: 5 packets, JumboOctets: 0 packets
CRC: 0 packets, Symbol: 0 packets
Overrun: 0 packets, InRangeLength: 0 packets
LongPacket: 0 packets, Jabber: 0 packets, Alignment: 0 packets
Fragment: 0 packets, Undersized Frame: 0 packets
RxPause: 0 packets
Output:
Unicast: 52473465 packets, Multicast: 9334 packets
Broadcast: 11 packets, JumboOctets: 0 packets
Lost: 0 packets, Overflow: 0 packets, Underrun: 0 packets
System: 0 packets, Overruns: 0 packets
TxPause: 0 packets
Last 300 seconds input utility rate: 0.01%
Last 300 seconds output utility rate: 0.01%

----End

Configuration Files
● DeviceA configuration file
#
sysname DeviceA
#
set flexe sub-time-slot granula slot 1 card 1 1g
flexe enable port 1/1/1
#
flexe group 1
flexe-groupnum 2345
binding interface FlexE-50G1/1/1
#
flexe client-instance 1 flexe-group 1 flexe-type full-function port-id 129
flexe-clientid 1
flexe-bandwidth 4
#
flexe client-instance 2 flexe-group 1 flexe-type full-function port-id 130
flexe-clientid 2
flexe-bandwidth 5
#
flexe client-instance 3 flexe-group 1 flexe-type full-function port-id 131
flexe-clientid 3
flexe-bandwidth 15
#
flexe client-instance 4 flexe-group 1 flexe-type full-function port-id 132
flexe-clientid 4
flexe-bandwidth 20
#
license
active port-basic slot 1 card 1 port 1
active port-flexe slot 1 card 1 port 1
#

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 66

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

interface FlexE-50G1/1/1
undo shutdown
undo dcn
phy-number 5
#
return
● DeviceB configuration file
#
sysname DeviceB
#
set flexe sub-time-slot granula slot 1 card 1 1g
flexe enable port 1/1/1
#
flexe group 1
flexe-groupnum 2345
binding interface FlexE-50G1/1/1
#
flexe client-instance 1 flexe-group 1 flexe-type full-function port-id 129
flexe-clientid 1
flexe-bandwidth 4
#
flexe client-instance 2 flexe-group 1 flexe-type full-function port-id 130
flexe-clientid 2
flexe-bandwidth 5
#
flexe client-instance 3 flexe-group 1 flexe-type full-function port-id 131
flexe-clientid 3
flexe-bandwidth 15
#
flexe client-instance 4 flexe-group 1 flexe-type full-function port-id 132
flexe-clientid 4
flexe-bandwidth 20
#
license
active port-basic slot 1 card 1 port 1
active port-flexe slot 1 card 1 port 1
#
interface FlexE-50G1/1/1
undo shutdown
undo dcn
phy-number 5
#
return

1.1.3 Port Extension Configuration

You can configure port extension so that a device uses fewer slots to provide high-
density Ethernet interfaces.

Usage Scenario
NOTE

This feature is supported only on the Admin-VS.

On an IP core network, to meet more and more service deployment requirements

on the access and network sides, PE or P devices need to provide high-density
Ethernet interfaces. To meet this need, deploy a port extension system. In this
system, configure a device with higher performance as a master and a large
number of low-end devices that support Ethernet interfaces as APs, and map the
APs' Ethernet interfaces to the master's port extension interfaces, so that the
master provides high-density Ethernet interfaces. Services only need to be
configured on the master's port extension interfaces. This ensures that the existing
devices that support Ethernet interfaces are fully used and prevents a large

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 67

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

number of devices that support Ethernet interfaces from being purchased,

significantly reducing network construction costs. The port extension system can
implement AP plug-and-play (PnP). You can configure and manage all APs on a
master, which simplifies network and service deployment and reduces O&M
difficulties. Figure 1-7 shows the typical networking for port extension.

Figure 1-7 Typical networking for port extension

NOTE

After a port extension system is deployed, the scope of service features supported by the
master's port extension interfaces is the same as that supported by local common Ethernet
interfaces.

Deployment Guidance
To completely deploy a port extension system and maintain and manage the
system on demand, perform the following configurations on a master:

1.1.3.1 Configuration Precautions for Port Extension

Feature Requirements

Table 1-9 Feature requirements

Feature Requirements Series Models

A master's internal communication interface NE9000 NE9000

supports only eTM subcards. If the board on
which the internal communication interface
resides is replaced with a non-eTM subcard,
the extended interface bound to the internal
communication interface on the eTM subcard
is deleted, and services on the extended
interface are also deleted.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 68

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Feature Requirements Series Models

Load balancing among different trunk sub- NE9000 NE9000

interfaces in the same multicast group
implemented by TM is not supported.
The aggregation mode does not support trunk
load balancing in a tunnel.

After a board is removed from a master and an NE9000 NE9000

extended interface is added to a trunk
interface, traffic statistics on the trunk
interface and its sub-interfaces are lost.

Port extension does not support IPv6 sampling. NE9000 NE9000

Port extension does not support IPv6 multicast. NE9000 NE9000

Port extension does not support MoFRR. NE9000 NE9000

Port extension does not support PW OAM. NE9000 NE9000

Port extension does not support TP OAM. NE9000 NE9000

Port extension does not support tunnel OAM. NE9000 NE9000

Port extension does not support VLL VPN QoS. NE9000 NE9000

Port extension does not support VPLS VPN NE9000 NE9000

QoS.

Port extension interfaces do not support BFD NE9000 NE9000

bit-error-triggered protection switching.

Port extension interfaces cannot function as NE9000 NE9000

network-side interfaces of EVPN.

Port extension interfaces cannot function as NE9000 NE9000

network-side interfaces of L2TPv3.

Port extension interfaces cannot function as NE9000 NE9000

network-side interfaces of PWE3.

Port extension interfaces cannot function as NE9000 NE9000

network-side interfaces of VLL.

Port extension interfaces cannot function as NE9000 NE9000

network-side interfaces of VPLS.

When any of the connectivity check NE9000 NE9000

mechanisms (such as BFD, Ethernet OAM CFM,
MPLS OAM, and MPLS-TP OAM) monitors a
path traversing an extended interface, if an
internal communication interface goes faulty
and internal communication interface
switching takes longer than the detection time,
the detection may fail.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 69

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Feature Requirements Series Models

In trunk scenarios with internal communication NE9000 NE9000

interfaces, traffic is hashed on internal
communication interfaces based on external
communication interfaces. Traffic cannot be
evenly distributed on internal communication
member interfaces. As a result, the traffic
carried on the internal communication
interfaces may exceed the bandwidth, causing
packet loss. Plan services properly and ensure
that bandwidth on each member internal
communication interface is sufficient.

In internal trunk interface scenarios, after all NE9000 NE9000

interfaces on a subcard are removed from the
internal trunk interface, HQoS statistics about
the external communication interface
corresponding to the internal trunk interface
are lost on the subcard.
Statistics commands: "display port-queue
statistics" and "display QoS-profile statistics"

The port-queue, port-queue-alarm and QoS NE9000 NE9000

default user-queue commands configured on
an internal communication interface take
effect for the default queue of the interface.
Traffic of the external communication interface
is not scheduled using the default queue of the
internal communication interface. As a result,
the port-queue, port-queue-alarm, and qos
default user-queue commands do not take
effect for traffic transmitted by the external
communication interface.
Port rate limiting and port scheduling services
need to be configured on external
communication interfaces. You can run the
port shaping command to plan the port
bandwidth for internal communication
interfaces.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 70

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Feature Requirements Series Models

When member interfaces of an external Eth- NE9000 NE9000

Trunk interface reside on different APs and the
AP fails, the Eth-Trunk interface in non-static
LACP mode does not support fast switchback
after the fault is rectified.
Eth-Trunk interfaces in non-LACP mode include
common manual Eth-Trunk interfaces and
manual 1:1 master/backup Eth-Trunk
interfaces.
It is recommended that an Eth-Trunk interface
in static LACP mode be used in an AP fault
scenario.

In the scenario where an Eth-Trunk interface is NE9000 NE9000

used as an external communication interface,
software-based route selection is performed
for multicast traffic based on the multicast
group ID. The route selection for multicast
traffic is the same as that for TM trunk traffic.
In a multicast external communication
interface Eth-Trunk scenario, if the selected
external communication interface fails and the
internal communication interface
corresponding to the newly selected external
communication interface is different from the
previous internal communication interface, fast
protection switching cannot be implemented.
Impact:
The aggregation mode does not support trunk
load balancing in a tunnel.
Workarounds:
1. It is recommended that the internal
communication interfaces bound to the
external communication interfaces on the AP
be the same.
2. If the internal communication interface is a
trunk interface, it is recommended that
member interfaces of the trunk interface be on
the same board to increase the switching
speed.

In BFD scenarios, port extension interfaces NE9000 NE9000

cannot function as IPv6 or public network
outbound interfaces.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 71

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Feature Requirements Series Models

The display interface command does not NE9000 NE9000

display unicast and multicast traffic statistics,
error packets, or discarded packets on a port
extension interface. To check remote statistics
on the external communication interface of an
AP, run the "display interface <ifname>
remote" command. When the AP displays the
statistics, it may stall.

Ensure that the interface binding relationship NE9000 NE9000

configured using the inner-connect command
is consistent with the physical connection
between the master and AP. Otherwise,
services are unavailable and the AP may fail to
go online.

Before adding a member interface to or NE9000 NE9000

deleting a member interface from a trunk
internal communication interface, shut down
the member interface and then add or delete
the member interface. Ensure that the
corresponding trunk member interface on the
AP has been correctly added or deleted, and
then run the undo shutdown command on the
member interface. Otherwise, service traffic
may be lost.

APs cannot be brought online manually. Avoid NE9000 NE9000

manually configuring APs to go online.
Otherwise, APs may fail to go online or
services may be abnormal.

Network-side interfaces do not support MPLS NE9000 NE9000

in the virtual access port extension view.

When a port-extended interface is configured NE9000 NE9000

on a master device, a binding relationship
must be established between the port-
extended interface and an internal
communication interface or trunk internal
communication interface. The binding
relationship cannot be modified. Instead, you
can delete the port-extended interface first
(configurations on the port-extended interface
will be cleared). Then you can reconfigure a
port-extended interface and establish a new
binding relationship.

A trunk internal communication interface NE9000 NE9000

supports only manual load balancing.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 72

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Feature Requirements Series Models

Member interfaces of the same trunk internal NE9000 NE9000

communication interface can be bound only to
internal communication interfaces on the same
AP.

A Master device cannot install the dynamic NE9000 NE9000

module to an AP using the install-module
command.

An extended interface and a common interface NE9000 NE9000

cannot be added to the same Eth-Trunk
interface.

The software versions of the master and AP NE9000 NE9000

must be the same. Otherwise, services may be
unavailable after the AP goes online.

A Master device and an AP are managed as NE9000 NE9000

separate NEs by the NMS.
The Master device and AP are displayed as
separate NEs on the NMS.

1.1.3.2 Establishing a Port Extension System

This section describes how to establish a port extension system.

Background
A port extension system consists of masters and APs. To simplify service
deployment and facilitate O&M and management, the control plane of the port
extension system is on a master. You can establish a port extension system on a
master. APs support plug-and-play (PnP). A master uses ESNs to automatically
identify APs and manage them, and delivers basic configurations to APs through
NETCONF channels. You do not need to perform configurations on APs.

Pre-configuration Tasks
Before establishing a port extension system, complete the following tasks:

● Retain the default configurations of the AP and load the pre-configuration

file.
● Obtain AP ESNs.
● Run the ssh client first-time enable command to enable SSH client first-time
authentication on a master.

1.1.3.2.1 Configuring Basic Master Functions

A master is a main device in a port extension system. You must configure a master
before establishing a port extension system.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 73

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run virtual-access port-extend

Port extension is enabled, and the port extension view is displayed.

Step 3 Run role master

The node is configured as a master. After this step is performed:

● All local physical interfaces become four-dimensional interfaces. For example,

dimension 1 in GigabitEthernet 1/1/0/1 indicates that the interface is a local
interface.
● The node automatically enables global BFD capabilities and establishes an IS-
IS process inside the port extension system based on local feature
configurations. The following table describes IS-IS process establishment rules.

Scenario Sub-scenario IS-IS Process

Establishment Rules

No IS-IS process By default, no IS-IS An AP and a master

exists. process exists. automatically establish
an IS-IS process with the
ID of 65534.

One or more IS-IS The ID of 65534 has An AP and a master

processes exist. been used for an IS-IS search for an unused IS-
process. IS process ID in
descending order from
65534 and use the ID to
establish a port
extension IS-IS process.

The ID of 65534 has not An AP and a master

been used for an IS-IS automatically establish
process. an IS-IS process with the
ID of 65534.

Step 4 Run admin ip-address

A management IP address is configured for the master.

The management IP address of the master is advertised to an AP over IS-IS for

establishing internal control and management channels to the AP. After this step
is performed, the master automatically generates a loopback interface with the
management IP address specified by ip-address.

Step 5 Run the following commands as required to configure a username, password, and
slave password for the master to establish an STelnet connection with an AP.
● ap default login-user user-name { login-password password | slave slave-
password-value } *

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 74

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● ap default login-user user-name login-password

● ap default login-user user-name slave-password
NOTE

The username and password must be set to the default username and password of an AP.

Step 6 (Optional) Run isis authentication-mode hmac-sha256 key-id key-id cipher

cipher-text [ send-only ]
IS-IS authentication is configured.

To improve the security of a port extension system, run the isis authentication-
mode command to authenticate received Hello, LSP, and SNP packets and to
encapsulate authentication information into sent Hello, LSP, and SNP packets.
Only authenticated or encrypted packets can be forwarded on a network,
preventing invalid packets from interfering with the network.

Step 7 (Optional) Run control-tunnel authentication keychain keychain-name

Keychain authentication is configured for a control channel.

An AP and master establish a control channel to exchange control information. To

improve control channel security, perform this step on a master to configure
keychain authentication for the control channel.

Before performing this step, you must have created a keychain.

Step 8 Run commit

The configuration is committed.

----End

1.1.3.2.2 Configuring Basic AP Functions on a Master

An AP can be considered as a master's remote card. You can configure basic AP
functions on a master.

Context
In a port extension system, a master can manage multiple APs at the same time.
You can repeat the following steps on a master to configure basic functions for
multiple APs.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run ap-id ap-id

An AP is configured on the master, and the AP view is displayed.

Step 3 Run esn esn-number

An ESN is configured for the AP.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 75

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

The port extension system supports plug-and-play (PnP) for an AP. After an AP
starts, it automatically enables the data communication network (DCN) function
and uses OSPF to advertise its ESN and initial PnP status. After a master discovers
the AP and identifies the initial PnP status, the master checks whether the AP's
ESN has been locally configured. If the AP's ESN has been locally configured, the
master starts the PnP process. A master uses an ESN to uniquely identify an AP,
and therefore different APs' ESNs cannot be the same.
Step 4 (Optional) Run sysname host-name
A host name is specified for the AP.
Step 5 Run commit
The configuration is committed.
Step 6 Run admin ip-address
A management IP address is configured for the AP.
The management IP address of the AP is used to establish internal control and
management channels to the master. This configuration is delivered by the master
to the AP in the AP plug-and-play process. Then, the AP automatically generates a
loopback interface with the IP address specified by ip-address.
The command takes effect immediately after being run.

----End

1.1.3.2.3 Configuring an Authentication Scheme for a Port Extension System

To ensure the security of a port extension system, you must configure an
authentication scheme.

Context
To establish a port extension system, you must establish channels (such as
STelnet, SFTP, and NETCONF channels) between a master and AP. To ensure
system security, you must configure an authentication scheme for AP login. The
current authentication scheme supports the following authentication modes:
● Local authentication: If no HWTACACS server is deployed on the current
network, you can use the local authentication mode. Local authentication
features fast processing and low operation costs, but the amount of
information that can be stored is limited by a device's hardware capacity.
● HWTACACS authentication: HWTACACS authentication can be used to prevent
unauthorized users from attacking a port extension system. Compared with
local authentication, HWTACACS authentication features more reliable
transmission and encryption.
Perform the following steps on a master.

Procedure
Step 1 Run system-view
The system view is displayed.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 76

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Step 2 Run ap-id ap-id

The AP view is displayed.

Step 3 Run login-user user-name login-password password

A username and password required for the master to log in to the AP are
configured.

Step 4 Run commit

The configuration is committed.

Step 5 Run login-user user-name sftp-directory sftp-directory

A user name and SFTP directory required for the master to log in to the AP are
configured.

Step 6 Run authentication-mode { hwtacacs | local } *

An authentication mode is configured for the authentication scheme. To configure

local authentication, specify the local parameter. To configure HWTACACS
authentication, specify the hwtacacs parameter. By default, local authentication is
used.

You can configure both local and hwtacacs authentication modes in an

authentication scheme. The system performs authentication based on the
configuration sequence.

● When the authentication mode is configured as local authentication and then

HWTACACS authentication: If the user name in Step 3 is not created on the
AP, the system performs HWTACACS authentication. If the user name in Step
3 has been created on both the AP and HWTACACS server and a password
error causes local authentication to fail, the system does not perform
HWTACACS authentication.
● When the authentication mode is configured as HWTACACS authentication
and then local authentication:
If the user name in Step 3 is not created on the HWTACACS server but exists
on the AP, the system considers HWTACACS authentication failed and does
not perform local authentication. The system performs local authentication
only when the HWTACACS authentication server goes Down.

The authentication mode of HWTACACS authentication and then local

authentication is recommended.

Step 7 Perform operations based on the configured authentication mode.

● If HWTACACS authentication is configured, perform the following operations:
a. Run the hwtacacs command to enter the port extension HWTACACS
view.
b. Run the hwtacacs-server shared-key { cipher cipher-string | key-string }
command to configure a global shared key for the AP's HWTACACS
server for communicating with the master.
To improve the security of communication between the master and the
AP's HWTACACS server, configure a shared key.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 77

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

c. Run the hwtacacs-server ip-address [ port ] [ shared-key { key-string |

cipher cipher-string } ] [ secondary ] command to configure primary and
secondary HWTACACS servers for the AP.
Where:

▪ If you do not specify shared-key { key-string | cipher cipher-string },

the global shared key is used.

▪ The IP addresses of the primary and secondary HWTACACS servers

must be different; otherwise, the configuration fails.

NOTE

If HWTACACS authentication is used, you must ensure that the user name and
password configured using the login-user command in Step 3 are the same as those
on the HWTACACS server. Otherwise, the AP cannot work normally.
● If local authentication is configured, perform the following operations:
a. Run the ap-user command to enter the virtual access AP-user view.
b. Run the local-user user-name password cipher password command to
create a local user name on the AP and configure a login password.

NOTE

If local authentication is used, you must ensure that the user name and password
configured using the login-user command in Step 3 are the same as those configured
using the local-user command. Otherwise, the AP cannot work normally.

Step 8 Run commit

The configuration is committed.

----End

1.1.3.2.4 Configuring Internal Communication Interfaces

To establish a port extension system, you must configure internal communication
interfaces between a master and AP.

Context
In a port extension system, data traffic is transmitted through the internal
forwarding channel between internal communication interfaces on an AP and
master. To set up the channel, you must configure the directly connected physical
interfaces between the master and AP as physical internal communication
interfaces. To increase the bandwidth or improve reliability, you can also configure
the Eth-Trunk interfaces between the master and AP as internal trunk interfaces.

NOTE

Physical internal communication interfaces and internal trunk interfaces do not support
service configuration or sub-interface creation.
To view a physical internal communication interface on the AP connected to a physical
internal communication interface on a master, run the link detect interface interface-type
interface-number command in the user view to enable the master to send LAD packets.
Then, run the display link neighbor interface interface-type interface-number command
to view the neighbor information about the internal communication interfaces between the
master and AP.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 78

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Procedure
● Configure a physical internal communication interface.
a. Run system-view

The system view is displayed.

b. Run interface interface-type interface-number

The directly connected physical interface view is displayed.

c. Run virtual-access enable

Port extension is enabled on the interface, and the interface is configured

as a physical internal communication interface.

After this step is performed, an IS-IS process inside the port extension
system is automatically enabled on the interface and the isis circuit-type
p2p command is automatically run to simulate the interface as a P2P
interface.

NOTE

● If you manually run the isis enable process-id command and then run the
virtual-access enable command on the interface, the port extension IS-IS
process is not automatically enabled and the isis circuit-type p2p command
is not automatically run on the interface. In this situation, you need to ensure
that port extension has been enabled for the IS-IS process specified by
process-id and manually run the isis circuit-type p2p command on the
interface. This brings heavy configuration workloads. In this case, the
automatic configuration solution is recommended. Do not run the isis enable
process-id command before running the virtual-access enable command.
● After an AP automatically goes online, port extension is automatically
enabled on the AP's all Ethernet interfaces. In addition, the AP automatically
saves the virtual-access enable configuration on corresponding interfaces.
d. Run commit

The configuration is committed.

e. Run quit

Return to the system view.

f. Run ap-id ap-id

The AP view is displayed.

g. Run inner-connect ap-interface-type ap-interface-number binding
master-interface-type master-interface-number
The internal communication interfaces on the AP and master are bound.

Where:

▪ ap-interface-type ap-interface-number specifies the AP's physical

internal communication interface, and master-interface-type master-
interface-number specifies the master's physical internal
communication interface.

▪ The binding configured in this step must match the actual physical
connection.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 79

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

h. Run commit
The configuration is committed.
● Configure an internal trunk interface.
a. Configure an Eth-Trunk interface to work in manual load balancing
mode.
Configuration details are as follows:

▪ Configure a Layer 3 Eth-Trunk interface.

▪ Add a physical interface through which the master is directly

connected to the AP to the Eth-Trunk interface.
b. Run interface eth-trunk trunk-id
The Eth-Trunk interface view is displayed.
c. Run virtual-access enable
Port extension is enabled on the Eth-Trunk interface, and the interface is
configured as an internal trunk interface.
After this step is performed, a port extension IS-IS process is
automatically enabled on the Eth-Trunk interface and the isis circuit-type
p2p command is automatically run to simulate the Eth-Trunk interface as
a P2P interface. The Eth-Trunk interface's member interfaces
automatically inherit the attributes of the internal trunk interface.

NOTE

If you manually run the isis enable process-id command and then run the
virtual-access enable command on the Eth-Trunk interface, the port extension
IS-IS process is not automatically enabled and the isis circuit-type p2p
command is not automatically run on the Eth-Trunk interface. In this situation,
you need to ensure that port extension has been enabled for the IS-IS process
specified by process-id and manually run the isis circuit-type p2p command on
the Eth-Trunk interface. This brings heavy configuration workloads. Therefore, do
not manually run the isis enable process-id command before running the
virtual-access enable command.
d. Run commit
The configuration is committed.
e. Run quit
Return to the system view.
f. Run ap-id ap-id
The AP view is displayed.
g. Run inner-connect ap-interface-type ap-interface-number binding
master-interface-type master-interface-number
The internal communication interfaces on the AP and master are bound.
Where:

▪ ap-interface-type ap-interface-number specifies the AP's physical

internal communication interface, and master-interface-type master-

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 80

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

interface-number specifies an internal trunk interface's member

interface on the master.

▪ The same internal trunk interface's member interface can only be

bound to the same AP's internal communication interface.

▪ The binding configured in this step must match the actual physical
connection.
After this step is performed, the AP automatically configures the
corresponding internal trunk interface.
h. Run commit
The configuration is committed.
----End

1.1.3.2.5 Configuring a Port Extension Interface

You can configure a port extension interface to map an AP's external
communication interface to a master's virtual interface, increasing the master's
interface density.

Context
In a port extension system, an AP can be considered as a card for extending
master interfaces. An AP receives configurations and forwarding entries from a
master and provides an external communication interface. To improve interface
density on a master, bind an AP's external communication interface to the
master's internal communication interface and create a port extension interface.
To configure Eth-Trunk for an AP's external communication interface, add the port
extension interface for the external communication interface to a common Eth-
Trunk interface as a port extension trunk interface on a master.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run ap-id ap-id
The AP view is displayed.
Step 3 Run remote-interface ap-interface-type ap-interface-number [ to max-port-
number ] binding master-interface-type master-interface-number
The AP's external communication interface is bound to the master's internal
communication interface, and a port extension interface is created.
Where:
● ap-interface-type ap-interface-number specifies an AP's external
communication interface, and master-interface-type master-interface-number
specifies a master's physical internal communication interface or internal
trunk interface.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 81

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● max-port-number specifies a maximum number for an external

communication interface on the AP. If this parameter is specified, the
command binds a group of external communication interfaces on an AP to a
master's internal communication interface, and creates a group of port
extension interfaces. The number range of external communication interfaces
bound is the last dimension of ap-interface-number to max-port-number.
A port extension interface is a four-dimensional interface, which is an extended
interface of an AP's external communication interface mapped on a master. For
example, GigabitEthernet 1025/1/0/1 indicates that the port extension interface
corresponds to AP 1025's external communication interface GigabitEthernet 1/0/1.
After creating a port extension interface, you can treat the AP's external
communication interface as the master's local interface for service configurations.

NOTE

After an AP goes online, port extension is automatically enabled on the AP's all Ethernet
interfaces. That is, the interfaces are internal communication interfaces by default. After
this step is performed on the master, port extension is automatically disabled on the AP's
external communication interface, because an interface cannot function as both an internal
communication interface and an external communication interface.

Step 4 Run commit

The configuration is committed.
Step 5 (Optional) Run quit
Return to the system view.
Step 6 (Optional) Configure a port extension trunk interface. Perform any of the
following tasks based on service requirements:
● Configure an Eth-Trunk interface to work in manual load balancing
mode.
● Configure an Eth-Trunk interface to work in static LACP mode.
● Configure an Eth-Trunk interface to work in manual 1:1 master/backup
mode.
When you perform any task, you must add the created port extension interface to
the Eth-Trunk interface.

NOTE

Currently, port extension interfaces and local common interfaces cannot be added to the
same Eth-Trunk interface.

----End

1.1.3.2.6 (Optional) Configuring Route Import Between the Port Extension System
and External Network
To enable an NMS to directly manage masters and APs, configure route import
between the port extension system and external network.

Context
A port extension system uses the DCN function to implement AP PnP, but a DCN is
characterized by route isolation. Therefore, if an NMS is used to manage a master

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 82

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

and AP, you must configure route import between the port extension system and
external network on a master.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run virtual-access port-extend

The port extension view is displayed.

Step 3 Run import admin-ip to { bgp [ vpn-instance vpn-instance-name ] | isis process-

id [ level-1 | level-1-2 | level-2 ] | ospf process-id | public }
The routes to the management IP addresses of the master and AP are imported
into a specified routing protocol. After this step is performed, routes in the port
extension system are imported into the DCN's external network. Before this step is
performed, configure routing protocols into which routes are to be imported on
the master.

NOTE

If a route to a management IP address is imported into IS-IS or OSPF, ensure that the
process specified by process-id does not import other routes. Otherwise, the configuration
fails.

Step 4 Run import { bgp [ vpn-instance vpn-instance-name ] | static [ vpn-instance

vpn-instance-name ] | isis process-id | ospf process-id } to dcn-ospf [ route-policy
route-policy-name ]
A specified protocol's routes are imported into DCN. After this step is performed,
the route between the master and NMS is imported into DCN in the port
extension system. Before this step is performed, configure routing protocols whose
routes are to be imported into DCN and routing policies on the master.

Step 5 Run commit

The configuration is committed.

----End

1.1.3.2.7 Verifying the Configuration of Establishing a Port Extension System

After establishing a port extension system, check the configurations on the master,
including basic AP information, AP statistics, AP interface information, port
extension interface information, and NVTAG allocation information.

Prerequisites
A port extension system has been established.

Procedure
● Run the display virtual-access ap [ ap-id ] command to check basic AP
information.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 83

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● Run the display virtual-access ap statistics command to check AP statistics.

● Run the display virtual-access ap-interface [ ap-id ap-id ] command to
check AP interface information.
● Run the display interface { interface-name | interface-type interface-
number } remote command to check information about a specified port
extension interface on the master corresponding to the external
communication interface.
● Run the display remote interface interface-type interface-number command
to check information about a specified port extension interface on the master.
● Run the display virtual-access bindinfo [ ap ap-id | interface interface-type
interface-number ] command to check the bindings between external
communication interfaces and port extension interfaces on the master.
----End

1.1.3.3 Upgrading and Managing an AP

This section describes how to upgrade and manage an AP.

Background
In the port extension solution, the control and management planes are centralized
on a master. You can upgrade and manage an AP on a master, including:
● Upgrade using a software package
● Patch installation
● AP restart
● Configuring APs to communicate with an NMS over SNMP
● Configuring APs to send information to a syslog server
● Setting an interval for collecting traffic statistics on an AP interface
● Configuring alarm thresholds for bandwidth usage on an AP interface
● Configuring a time format for AP information
● Configuring an AP information output mode
After you complete configurations, the master uses the NETCONF channel to
deliver the configurations to the AP and the AP automatically performs the
configurations.

NOTE

● During a software upgrade of the port extension system, upgrade APs and then masters.
The process for upgrading a master is the same as that for upgrading a common device.
● Ensure that the software versions running on the master and APs are the same. If the
software versions are inconsistent, services may be unavailable after the APs go online.
● You can also log in to an AP to upgrade and manage it.

Pre-configuration Tasks
Before upgrading and managing an AP on a master, complete the following tasks:
● Establish a port extension system.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 84

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● Upload a software package or patch file for an upgrade to a master or

specified server.

1.1.3.3.1 Using a Software Package to Upgrade an AP

A software package optimizes an AP's original functions, adds functions, and
resolves the issue that the running version cannot be promptly updated.

Procedure
Step 1 Upload a software package for an upgrade to an AP. The following table describes
upload methods.

Softw AP Command
are Range
Packa
ge
Sourc
e

Maste APs in a upgrade download-package packagename ap-id

r specified { startapid [ to endapid ] } &<1-10>
range

All APs upgrade download-package packagename all-ap

Specifi APs in a upgrade download-package packagename server-ip ip-

ed specified address server-port port-number ap-id { startapid [ to
server range endapid ] } &<1-10>
All APs upgrade download-package packagename server-ip ip-
address server-port port-number all-ap

NOTE

● After upgrade download-package is run, a user must enter an SFTP user name and
password as prompted for SFTP authentication between an AP and master or between
an AP and specified server.
● If the software package source is a specified server, configure the port extension system
and server to import each other's network segment route to implement connectivity
between the APs and server.
● To free up the system storage space, run the upgrade delete-package type command
on the master to delete unnecessary AP software packages.

Step 2 Run the display patch-information ap-id ap-id command to check whether any
running patch exists on the AP.
Step 3 (Optional) Run the patch delete all { all-ap | ap-id { startapid [ to endapid ] }
&<1-10> } command to delete the running patches on the AP.
Before using a software package to upgrade an AP, ensure that no patches are
running on the AP. If any patch is running on the AP, system software cannot be
upgraded. Perform this step if any patch is running on the AP. Otherwise, skip this
step.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 85

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Step 4 Run the startup system-software system-file { all-ap | ap-id { startapid [ to

endapid ] } &<1-10> } command to configure system software for the AP's next
startup.
Parameters are described as follows:
● all-ap: configures system software for the next startup of all APs managed by
the master.
● ap-id { startapid [ to endapid ] } &<1-10>: configures system software for the
next startup of the APs in the specified range.
Step 5 After a period of time, run the display startup ap-id ap-id command to check the
configuration result.

----End

Follow-up Procedure
Restart the AP for the software package to take effect immediately.

1.1.3.3.2 Installing a Patch

You can install a patch for an AP to optimize the AP's system functions or add
small requirements.

Procedure
Step 1 Upload a patch file to an AP. The following table describes upload methods.
Patch AP Command
File Range
Sourc
e

Maste APs in a upgrade download-package packagename ap-id

r specified { startapid [ to endapid ] } &<1-10>
range

All APs upgrade download-package packagename all-ap

Specifi APs in a upgrade download-package packagename server-ip ip-

ed specified address server-port port-number ap-id { startapid [ to
server range endapid ] } &<1-10>
All APs upgrade download-package packagename server-ip ip-
address server-port port-number all-ap

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 86

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

NOTE

● After upgrade download-package is run, a user must enter an SFTP user name and
password as prompted for SFTP authentication between an AP and master or between
an AP and specified server.
● If the software package source is a specified server, configure the port extension system
and server to import each other's network segment route to implement connectivity
between the APs and server.
● To free up the system storage space, run the upgrade delete-package type command
on the master to delete unnecessary AP patch packages.

Step 2 Install the patch for the AP.

● Install the patch without interrupting services.
a. Run the patch load file-name all run { all-ap | ap-id { startapid [ to
endapid ] } &<1-10> } command to install the patch for the AP.
Parameter Description

run The patch is in the running state after being

installed.

all-ap The patch is installed for all APs managed by the

master.

ap-id { startapid The patch is installed for the APs in a specified

[ to endapid ] } range.
&<1-10>

● Install the patch for the next startup.

a. Run the startup patch packagename all { all-ap | ap-id { startapid [ to
endapid ] } &<1-10> } command to configure the patch for the AP's next
startup.
After the AP restarts, the patch takes effect permanently.

----End

Follow-up Procedure
● When the patch is installed without interrupting services:
– To delete the installed patch that results in an exception, run the patch
delete all { all-ap | ap-id { startapid [ to endapid ] } &<1-10> }
command.
● When the patch is installed for the next startup:
– To clear the patch configuration for the next startup, run the reset patch-
configure next-startup { all-ap | ap-id { startapid [ to endapid ] }
&<1-10>} command.
– Restart the AP for the patch to take effect immediately.

1.1.3.3.3 Restarting an AP
After configuring a software package for an AP's upgrade or a patch for an AP's
next startup, restart the AP to immediately validate the software package or patch
and check whether the configuration is successful.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 87

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run ap-id ap-id
The AP view is displayed.
Step 3 Run reboot
The AP is restarted.

----End

1.1.3.3.4 Configuring APs to Communicate with an NMS over SNMP

To use a network management system (NMS) to manage APs, configure the APs
to communicate with the NMS over SNMP on a master.

Context
In a port extension scenario, to use an NMS to manage APs, you need to configure
SNMP in the port extension view of a master. After the configuration, when the IP
route between the NMS and an AP is reachable:
● The AP uses a trap message to report a fault alarm to the NMS.
● The AP records active alarms, and the NMS can use the MIB to query or
synchronize the active alarms on the AP.
NOTE

● In a port extension system, all services are configured on a master. Therefore, the
master is responsible for service alarm reporting. If an AP fails, it independently reports
a fault alarm.
● A master communicates with an NMS over SNMP. The configuration procedure is the
same as that in a common scenario.

Perform the following steps on a master.

Pre-configuration Tasks
Before configuring APs to communicate with an NMS over SNMP:
● Establish a port extension system.
When establishing a port extension system, you can configure route import
between the port extension system and external network so that the
routes between the NMS and APs are reachable.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run virtual-access port-extend

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 88

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

The port extension view is displayed.

Step 3 Run snmp-agent

The SNMP agent service is started.

Step 4 Run snmp-agent sys-info version { v1 | v2c | v3 | all } *

An SNMP version is configured.

Step 5 Perform either of the following configurations based on the SNMP version. You
are advised to use SNMPv3 with higher security.
● For SNMPv1 or SNMPv2:
Run snmp-agent community { read | write } cipher community-name
[ mib-view view-name ]
A read/write community name and MIB view are configured for APs.
A community is a set of an NMS and SNMP agents and is identified using a
community name. The community name acts like a password to regulate
access to a managed device. An NMS can access a managed device only if the
community name carried in an SNMP request sent by the NMS is the same as
the community name configured on the managed device. Perform this step to
configure an SNMP community name for APs so that the NMS communicates
with the APs. You can also run the snmp-agent community command to set
a MIB view that is accessible using a community name.
● For SNMPv3:
a. Run snmp-agent group v3 group-name { authentication | privacy |
noauthentication } [ read-view read-view | write-view write-view |
notify-view notify-view ]
An SNMP user group is configured.
If an NMS and a device reside in an insecure network environment, for
example, they are prone to network attacks, you are advised to set
authentication or privacy to enable data authentication and encryption.
The available authentication and encryption modes are as follows:

▪ If neither authentication nor privacy is configured or

noauthentication is configured, authentication and encryption are
not performed. This mode is applicable to secure networks managed
by a specified administrator.

▪ If only authentication is configured, only authentication is

performed. This mode is applicable to secure networks managed by
many administrators who may frequently perform operations on the
same device. In this mode, only the authenticated administrators can
access the managed device.

▪ If both authentication and privacy are configured, both

authentication and encryption are performed. This mode is
applicable to insecure networks managed by many administrators
who may frequently perform operations on the same device. In this
mode, only the authenticated administrators can access the
managed device, and transmitted data is encrypted to guard against
tampering and data leaking.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 89

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

If the NMS administrator needs the read permission in a specified view,

configure read-view in this command. For example, a low-level
administrator needs to read certain data.
If the NMS administrator needs the read and write permissions in a
specified view, configure write-view in this command. For example, a
high-level administrator needs to read and write certain data.
If the NMS administrator needs to filter out irrelevant alarms and
configure the managed device to send only the alarms of specified MIB
objects to the NMS, configure notify-view. If the parameter is
configured, only the alarms of the MIB objects specified by notify-view is
sent to the NMS.
b. Run snmp-agent usm-userv3 user-name [ group group-name ]
A USM user is added to an SNMP group.
c. Run snmp-agent usm-user
An authentication mode, encryption mode, and password are configured
for the SNMP USM user.
NOTE

The md5, sha, sha2-224, DES56, and 3DES168 algorithms in the snmp-agent
usm-user command are weak security algorithms. You are advised to use other
security algorithms. To prevent security risks, run the crypto weak-algorithm
disable command to disable the weak security algorithm function.

Step 6 Run snmp-agent target-host host-name host-name trap address udp-domain

ip-address params securityname cipher cipher-name [ [ v1 | v2c ] | private-
netmanager | ext-vb ] *

A destination is set for trap messages sent by APs.

Perform this step to set a destination NMS address for trap messages sent by APs.
If a target host that receives trap messages is a Huawei NMS, specify private-
netmanager. To enable trap messages to carry extended bound variables, specify
ext-vb.

Step 7 (Optional) Run snmp-agent extend error-code enable

The extended error code function is enabled for APs.

The extended error code function can be configured to extend standard error
codes only when an NMS is a Huawei NMS and managed APs are Huawei devices.
Extended error codes facilitate fault locating.

Step 8 (Optional) Run snmp-agent mib-view view-name view-name oid-tree

A MIB view is created, and MIB objects monitored and managed by an NMS are
specified.

● If there are only a few MIB objects that do not need to be managed by an
NMS when you create a MIB view or you want to remove some MIB objects
from an existing MIB view, specify excluded in the command.
● If there are only a few MIB objects that need to be managed by an NMS
when you create a MIB view or you want to add some MIB objects to an
existing MIB view, specify included in the command.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 90

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Step 9 (Optional) Run snmp-agent trap enable

An AP is enabled to send trap messages.
Enabling an AP to send trap messages to the NMS facilitates problem locating.
You can perform this step to enable all modules of an AP to send trap messages.
Step 10 Run commit
The configuration is committed.

----End

1.1.3.3.5 Configuring APs to Send Information to a Syslog Server

To view AP running information on a syslog server, configure the APs managed by
the master to send information to the syslog server on a master.

Context
When an AP is running, the system records the AP's running status in real time
and generates related information. After the information management function is
enabled, configure the APs managed by the master to send information to a
syslog server for storage and query on a master. A network administrator can use
the information to monitor the running status of the APs and diagnose network
faults.
Perform the following steps on a master.

Pre-configuration Tasks
Before configuring APs to send information to a syslog server:
● Establish a port extension system.
When establishing a port extension system, you can configure route import
between the port extension system and external network so that the
routes between the NMS and APs are reachable.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run virtual-access port-extend
The port extension view is displayed.
Step 3 Run info-center loghost source interface-type interface-number
The source interface through which APs send information to a specified syslog
server is configured.
The syslog server can obtain the source interface address of received information
and determine which AP sends the information based on the source interface
address. This helps the syslog server properly retrieve the received information.
Step 4 Run info-center loghostipv4-address [ { local-time | utc } | facilitylocal-number |
port port-number | levellog-level | transport { udp | tcp } ] *

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 91

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

All the APs managed by the master are configured to send information to the
specified syslog server. Repeat this step to configure APs to send information to
multiple syslog servers, implementing information backup between the syslog
servers.
Step 5 (Optional) Run info-center source { module-name | default } channel { channel-
number | channel-name } [ log { state { off | on } | levelseverity } * | trap { state
{ off | on } | levelseverity } * | debug { state { off | on } | levelseverity } * ] *
A rule is configured for each AP to output information to an information channel.
Step 6 Run commit
The configuration is committed.

----End

1.1.3.3.6 Configuring a Time Format for AP Information

This section describes how to configure a time format for AP information.

Usage Scenario
On a master, you can configure a time format for AP information to meet the time
requirements in different places. After the configuration is complete, new
information on APs is generated using the configured time format.

NOTE

In this section, AP information refers to log, trap, and debugging information.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run virtual-access port-extend
The port extension view is displayed.
Step 3 Run one or more of the following commands to configure time formats for desired
information:
● Run the info-center timestamp log { boot | { date | short-date | format-
date | rfc-3339 } [ precision-time { tenth-second | millisecond | second } ] }
[ without-timezone ] command to configure the time format of log
information.
● Run the info-center timestamp trap { boot | { date | short-date | format-
date | rfc-3339 } [ precision-time { tenth-second | millisecond | second } ] }
[ without-timezone ] command to configure the time format of trap
information.
● Run the info-center timestamp debugging { boot | { date | short-date |
format-date | rfc-3339 } [ precision-time { tenth-second | second |
millisecond } ] } [ without-timezone ] command to configure the time
format of debugging information.
The following table describes the elements of the date format.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 92

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Table 1-10 Elements of the date format

Field Meaning Value

yyyy Year The value contains four digits.

mm Month Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct,
Nov, or Dec.

dd Date If the date value (such as 7) is smaller than 10,

a blank is added before the date.

hh:mm:ss Local time in The value of hh ranges from 00 to 23 in 24-

hh:mm:ss format hour format, whereas the values of mm and ss
both range from 00 to 59.

Step 4 Run commit

The configuration is committed.

----End

1.1.3.3.7 Configuring an AP Information Output Mode

This section describes how to configure an AP information output mode. This
configuration enables you to export AP information to a local file or display area,
and set attributes for the file and display area.

Context
APs log their operation information in real time. You can configure an AP
information output mode and log in to the desired AP to know its operation
information.
Perform the following steps on a master.

Procedure
● Output information to the display area.
a. Run system-view
The system view is displayed.
b. Run virtual-access port-extend
The port extension view is displayed.
c. (Optional) Run info-center logbuffer size buffersize
The maximum number of AP logs to be displayed is configured.
d. Run info-center source { module-name | default } channel { channel-
number | channel-name } log { state { off | on } | level severity } *
A rule is configured for each AP to output log information to an
information channel.
e. Run commit
The configuration is committed.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 93

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

● Output information to a file.

a. Run system-view
The system view is displayed.
b. Run virtual-access port-extend
The port extension view is displayed.
c. (Optional) Run info-center debugfile-name file-name
A name is configured for an AP debugging log file.
The default debugging log file name is debug.log on an AP. To configure
a name for a specified debugging log file, perform this step. You can
obtain the debugging log file based on the name.
d. (Optional) Run info-center max-debugfile-number max-debugfile-
number
The maximum number of AP debugging log files that can be saved to the
log directory is configured.
The debug.log file that is generated on an AP by default is compressed
into a debug_*.log.zip file if its size exceeds 8 MB.
You can perform this step to configure the maximum number of AP
debugging log files that can be saved to the log directory.
When the number of compressed log files exceeds the maximum number
configured, the system deletes earliest log files.
e. Run info-center source { module-name | default } channel { channel-
number | channel-name } [ log { state { off | on } | level severity } * |
trap { state { off | on } | level severity } * | debug { state { off | on } |
level severity } * ] *
A rule is configured for each AP to output information to an information
channel.
f. Run commit
The configuration is committed.
----End

1.1.3.3.8 Setting an Interval for Collecting Traffic Statistics on an AP Interface

This section describes how to set an interval on a master for collecting traffic
statistics on one or more external communication interfaces of an AP.

Context
By default, traffic statistics collection is enabled on external communication
interfaces of an AP to monitor the running status of interfaces and services. To
adjust the interval for collecting traffic statistics on external communication
interfaces of an AP, perform either of the following operations on the master:
● Configure a global interval for collecting traffic statistics on an AP:
Run the set flow-stat interval command in the AP view. The configuration is
delivered to the corresponding AP and takes effect on the AP's external

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 94

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

communication interfaces mapped to the port extension interfaces with no

traffic statistics collection interval configured.
● Configure an interval for collecting traffic statistics on one or more specified
external communication interfaces of an AP:
Run the set flow-stat interval command in the view of a port extension
interface or port extension trunk interface. The configuration is delivered to
the corresponding AP and takes effect on the AP's external communication
interface mapped to the port extension interface or the AP's external
communication interfaces mapped to the port extension trunk member
interfaces. This configuration takes precedence over the global configuration.

Procedure
● Configure a global interval for collecting traffic statistics on an AP.
a. Run system-view
The system view is displayed.
b. Run ap-id ap-id
The AP view is displayed.
c. Run set flow-stat interval interval
A global interval for collecting traffic statistics on the AP is set.
d. Run commit
The configuration is committed.
● Configure an interval for collecting traffic statistics on one or more specified
external communication interfaces of an AP.
a. Run system-view
The system view is displayed.
b. Run interface interface-type interface-number
The port extension interface view or port extension trunk interface view is
displayed.
c. Run set flow-stat interval interval
An interval for collecting traffic statistics on one or more specified
external communication interfaces of the AP is set.
d. Run commit
The configuration is committed.
----End

1.1.3.3.9 Configuring Alarm Thresholds for Bandwidth Usage on an AP Interface

This section describes how to configure alarm thresholds for bandwidth usage on
a master to take effect on an external communication interface of an AP.

Context
Monitoring bandwidth usage helps you keep track of the load on an AP. If
bandwidth usage exceeds a specified threshold, bandwidth resources are

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 95

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

insufficient on an AP. In this case, you need to expand the capacity of the AP or
migrate services to another AP. The default alarm threshold for bandwidth usage
on an external communication interface of an AP is 90%. If the bandwidth usage
exceeds 90%, an alarm is generated, indicating that bandwidth resources are
almost exhausted. As a result, packet loss may occur before the capacity is
expanded or services are migrated. To resolve the preceding problem, adjust the
alarm threshold for bandwidth usage on an external communication interface of
an AP. For example, you can set the alarm threshold for inbound bandwidth usage
to 80% so that an alarm is generated when the inbound bandwidth usage exceeds
80%.

Procedure
Step 1 Run system-view

The system view is displayed.

Step 2 Run interface interface-type interface-number [ .sub-interface-number ]

The port extension interface or port extension sub-interface view is displayed.

Step 3 Run trap-threshold { input-rate | output-rate } bandwidth-in-use [ resume-rate

resume-threshold ]

An alarm threshold and a clear alarm threshold for inbound or outbound

bandwidth usage are set for the corresponding external communication interface
on the AP. When performing this step, note the following:

● The value of resume-threshold must be less than or equal to that of

bandwidth-in-use.
● If resume-rate resume-threshold is not specified, the system automatically
sets the clear alarm threshold for bandwidth usage to be the same as the
alarm threshold for bandwidth usage.
● To prevent alarms from being frequently generated or cleared, set a large
difference between the bandwidth-in-use and resume-threshold values.

Step 4 Run commit

The configuration is committed.

----End

1.1.3.4 Maintaining the Port Extension System

This section describes how to maintain the port extension system.

1.1.3.4.1 Clearing Statistics About a Port Extension Interface

Before collecting traffic statistics about a port extension interface within a
specified period, you must clear the existing statistics on the port extension
interface.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 96

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Context

NOTICE

Statistics cannot be restored after being cleared. Therefore, exercise caution when
clearing statistics.

Procedure
● Run the reset counters [ if-mib ] interface { interface-name | interface-type
interface-number } remote command in the user view to clear remote
statistics or remote MIB statistics about a specified port extension interface or
port extension trunk interface.
----End

1.1.3.5 Configuration Examples for Port Extension

This section provides port extension system deployment examples.

1.1.3.5.1 Example for Configuring a Port Extension System

This section provides an example for configuring a port extension system.

Networking Requirements
Figure 1-8 shows the typical networking of a port extension system, which is used
to provide devices with high-density Ethernet interfaces on the IP core network.
Port extension enables a device with higher performance to be configured as a
master and a large number of low-end devices that support Ethernet interfaces to
be configured as APs. The APs' Ethernet interfaces are then mapped to the
master's port extension interfaces, so that the master provides high-density
Ethernet interfaces. Services only need to be configured on the master's port
extension interfaces.

Figure 1-8 Typical networking of a port extension system

NOTE

Interfaces 1 through 3 in this example are GE 1/0/1, GE 1/0/2, and GE 1/0/3, respectively.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 97

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Configuration Roadmap
The configuration roadmap is as follows:

1. Configure basic master functions.

2. Configure basic AP functions on the master.
3. Configure an authentication scheme for the port extension system.
4. Configure internal communication interfaces.
5. Configure port extension interfaces.

Data Preparation
To complete the configuration, you need the following data:

● Management IP address of the master: 1.1.1.1; management IP address of

AP1: 2.2.2.2; management IP address of AP2: 3.3.3.3
● IS-IS authentication key ID: 1; authentication password: YsHsjx_202206
● Default username and password for the master to establish an STelnet
connection with an AP: root; password: Changeme_123
● Internal communication interfaces between the master and AP1: GE 1/0/1;
internal communication interfaces between the master and AP2: GE 1/0/2
and GE 1/0/1
● AP1 ID: 2000; AP1 ESN: 391092333866236; AP1's external communication
interfaces: GE 1/0/2 and GE 1/0/3
● AP2 ID: 2001; AP2 ESN: 391092333000298; AP2's external communication
interfaces: GE 1/0/2 and GE 1/0/3
● Authentication mode between the master and AP1 and between the master
and AP2: local authentication; username required for the master to log in to
AP1 and AP2: sys-admin; password: YsHsjx_202207; SFTP directory: cfcard:/;
name of a user created for AP1 and AP2 on the master: sys-admin; password:
YsHsjx_202207

Procedure
Step 1 Retain the default configurations for APs.

When an AP goes online for the first time, the master delivers a root user
configuration to the AP to establish a connection with the AP.

● Before an AP goes online, if the AP is logged in to in STelnet mode for the

first time, or the AP is logged in to through the console port and then the
console port password is modified, the AP cannot go online. In this case, you
need to manually clear the configuration and load the pre-configuration file.
<AP> reset saved-configuration
Warning: The action will delete the saved configuration on the device.
The configuration will be erased to reconfigure.Continue? [Y/N]:y
Warning: Now clearing the configuration on the device.
Info: Succeeded in clearing the configuration on the device.
<AP> startup default-configuration default-custom_XXX_V***R***C**SPC***.defcfg
Warning: The action will override and update the default configuration file on the device. Continue?
[Y/N]:y
...
Info: Succeeded in setting the configuration for booting system.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 98

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

NOTE

Obtain the pre-configuration file default-custom_XXX_V***R***C**SPC***.defcfg of

the corresponding product version from Huawei.
● After an AP goes online, if the password of the root user on the AP is
modified, the AP cannot establish a connection with the master for
reconciliation.
Step 2 Configure basic master functions.
<Master> system-view
[~Master] ssh client first-time enable
[~Master] dcn
Warning: This operation will enable DCN function. Continue? [Y/N]:y
Info: The operation may take a few seconds. Please wait for a moment....done.
[*Master] commit
[~Master] virtual-access port-extend
[*Master-virtual-access-portextend] role master
[*Master-virtual-access-portextend] admin 1.1.1.1
[*Master-virtual-access-portextend] ap default login-user root login-password Changeme_123
[*Master-virtual-access-portextend] isis authentication-mode hmac-sha256 key-id 1 cipher
YsHsjx_202206
[*Master-virtual-access-portextend] commit
[~Master-virtual-access-portextend] quit

Step 3 Configure basic AP functions on the master.

[~Master] ap-id 2000
[*Master-ap2000] esn 391092333866236
[*Master-ap2000] commit
[~Master-ap2000] admin 2.2.2.2
[~Master-ap2000] quit
[~Master] ap-id 2001
[*Master-ap2001] esn 391092333000298
[*Master-ap2001] commit
[~Master-ap2001] admin 3.3.3.3
[~Master-ap2001] quit

Step 4 Configure an authentication scheme for the port extension system.

[~Master] ap-id 2000
[~Master-ap2000] login-user sys-admin login-password YsHsjx_202207
[*Master-ap2000] commit
[~Master-ap2000] login-user sys-admin sftp-directory cfcard:/
[~Master-ap2000] ap-user
[~Master-ap2000-ap-user] local-user sys-admin password cipher YsHsjx_202207
[~Master-ap2000-ap-user] quit
[~Master-ap2000] authentication-mode local
[~Master-ap2000] quit
[~Master] ap-id 2001
[~Master-ap2001] login-user sys-admin login-password YsHsjx_202207
[*Master-ap2001] commit
[~Master-ap2001] login-user sys-admin sftp-directory cfcard:/
[~Master-ap2001] ap-user
[~Master-ap2001-ap-user] local-user sys-admin password cipher YsHsjx_202207
[~Master-ap2001-ap-user] quit
[~Master-ap2001] authentication-mode local
[~Master-ap2001] quit

Step 5 Configure internal communication interfaces.

[~Master] interface GigabitEthernet1/1/0/1
[~Master-GigabitEthernet1/1/0/1] virtual-access enable
[~Master-GigabitEthernet1/1/0/1] dcn
[*Master-GigabitEthernet1/1/0/1] quit
[*Master] interface GigabitEthernet1/1/0/2
[*Master-GigabitEthernet1/1/0/2] virtual-access enable
[*Master-GigabitEthernet1/1/0/2] dcn
[*Master-GigabitEthernet1/1/0/2] quit
[~Master] ap-id 2000

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 99

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

[~Master-ap2000] inner-connect GigabitEthernet1/0/1 binding GigabitEthernet1/1/0/1

[*Master-ap2000] quit
[*Master] ap-id 2001
[*Master-ap2001] inner-connect GigabitEthernet1/0/1 binding GigabitEthernet1/1/0/2
[*Master-ap2001] commit
[~Master-ap2001] quit

Step 6 Configure port extension interfaces.

[~Master] ap-id 2000
[~Master-ap2000] remote-interface GigabitEthernet1/0/2 binding GigabitEthernet1/1/0/1
[*Master-ap2000] remote-interface GigabitEthernet1/0/3 binding GigabitEthernet1/1/0/1
[*Master-ap2000] quit
[*Master] ap-id 2001
[*Master-ap2001] remote-interface GigabitEthernet1/0/2 binding GigabitEthernet1/1/0/2
[*Master-ap2001] remote-interface GigabitEthernet1/0/3 binding GigabitEthernet1/1/0/2
[*Master-ap2001] commit
[~Master-ap2001] quit

Step 7 Verify the configuration.

Run the display virtual-access ap command on the master to view basic

information about APs.
[~Master] display virtual-access ap
AP Information
-----------------------------------------------------------------------------------------------
AP Esn : 391092333866236
AP ID : 2000 Admin IP : 2.2.2.2
Master : 1.1.1.1
State : Online
Online Time : 2017-09-30 01:03:56

AP Esn : 391092333000298
AP ID : 2001 Admin IP : 3.3.3.3
Master : 1.1.1.1
State : Online
Online Time : 2017-09-30 01:31:26

-----------------------------------------------------------------------------------------------

Run the display virtual-access ap-interface command on the master to view

basic information about AP interfaces.
[~Master] display virtual-access ap-interface
Ap Interface Information
Total 20 record(s) found:
-----------------------------------------------------------------------------------------
APID APAdminIP Interface IfIndex State Type
-----------------------------------------------------------------------------------------
2000 2.2.2.2 GigabitEthernet1/0/1 8 Up inner
2000 2.2.2.2 GigabitEthernet1/0/2 9 Up outer
2000 2.2.2.2 GigabitEthernet1/0/3 10 Up outer
2001 3.3.3.3 GigabitEthernet1/0/1 8 Up inner
2001 3.3.3.3 GigabitEthernet1/0/2 9 Up outer
2001 3.3.3.3 GigabitEthernet1/0/3 10 Up outer
-----------------------------------------------------------------------------------------

Run the display virtual-access bindinfo command on the master to view the
bindings between internal communication interfaces and port extension interfaces
on the master.
[~Master] display virtual-access bindinfo
--------------------------------------------------------------------------------------
AP-ID Inner-interface Out-interface
--------------------------------------------------------------------------------------
2000 GigabitEthernet1/1/0/1 GigabitEthernet2000/1/0/2
2000 GigabitEthernet1/1/0/1 GigabitEthernet2000/1/0/3

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 100

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

2001 GigabitEthernet1/1/0/2 GigabitEthernet2001/1/0/2

2001 GigabitEthernet1/1/0/2 GigabitEthernet2001/1/0/3

----End

Configuration Files
● AP1 configuration file
#
sysname AP1
#
virtual-access
role ap
admin 2.2.2.2
master admin-ip primary 1.1.1.1
isis authentication-mode hmac-sha256 key-id 1 cipher %^%#OqaV.B&wk-eu\lD0(u:5ZWFN)r'k:2uIW.-/
9:NU%^%#
#
undo user-security-policy enable
#
ip dcn vpn-instance __dcn_vpn__
ipv4-family
#
bfd
#
aaa
local-user sys-admin password irreversible-cipher $1c$VW58EBdUe"$uXfj.2l)I#za`:6tJ,w$U|
([5}MsD#|):rU(cV/+$
local-user sys-admin service-type ssh
local-user sys-admin state block fail-times 3 interval 5
local-user sys-admin user-group manage-ug
#
authentication-scheme default0
#
authentication-scheme default1
#
authentication-scheme default
authentication-mode local
#
authorization-scheme default
#
accounting-scheme default0
#
accounting-scheme default1
#
domain default0
#
domain default1
#
domain default_admin
authorization-scheme default
#
isis 65534
description auto-generated for virtual-access
is-level level-2
cost-style wide
virtual-access enable
network-entity 00.38ba.33bc.a402.00
binding interface GigabitEthernet1/0/1 down-weight 10
#
interface GigabitEthernet1/0/1
undo shutdown
isis enable 65534
isis circuit-type p2p
dcn
virtual-access enable
#
interface GigabitEthernet1/0/2

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 101

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

undo shutdown
#
interface GigabitEthernet1/0/3
undo shutdown
#
interface LoopBack2147483646
description virtual-access loopback interface
ip binding vpn-instance __dcn_vpn__
ip address 2.2.2.2 255.255.255.255
#
interface LoopBack2147483647
description DCN loopback interface
ip binding vpn-instance __dcn_vpn__
ip address 172.16.1.1 255.255.0.0
#
ospf 65534 vpn-instance __dcn_vpn__
description DCN ospf create by default
opaque-capability enable
hostname
vpn-instance-capability simple
area 0.0.0.0
network 0.0.0.0 255.255.255.255
#
!The DCN function implements the capability of plug-and-play for this device.
!A NE IP address based on the unique NE ID is automatically generated in VPN
!of DCN. It is recommended that the NE IP address be changed to the planned
!one by running the ne-ip X.X.X.X <mask> command after the device being online.
dcn
bandwidth ethernet 1024
bandwidth pos 1024
#
stelnet ipv4 server enable
sftp ipv4 server enable
snetconf ipv4 server enable
stelnet ipv6 server enable
sftp ipv6 server enable
snetconf ipv6 server enable
ssh user sys-admin
ssh user sys-admin authentication-type password
ssh user sys-admin service-type all
ssh user sys-admin sftp-directory cfcard:/
ssh authorization-type default aaa
#
ssh server cipher aes256_gcm aes128_gcm aes256_ctr aes192_ctr aes128_ctr
ssh server hmac sha2_512 sha2_256
ssh server key-exchange dh_group_exchange_sha256
#
ssh server publickey rsa_sha2_256 rsa_sha2_512
#
ssh server dh-exchange min-len 3072
#
ssh client first-time enable
sftp client-source -a 2.2.2.2 -vpn-instance __dcn_vpn__
#
user-interface con 0
#
user-interface vty 0 4
authentication-mode aaa
protocol inbound ssh
#
netconf
idle-timeout 0 0
#
local-aaa-server
#
return
● AP2 configuration file
#
sysname AP2

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 102

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

#
virtual-access
role ap
admin 3.3.3.3
master admin-ip primary 1.1.1.1
isis authentication-mode hmac-sha256 key-id 1 cipher %^%#gb0N3W.{o6QZelLT!#yIPjdj/
~Dk8$F&p73~P/x.%^%#
#
undo user-security-policy enable
#
ip dcn vpn-instance __dcn_vpn__
ipv4-family
#
bfd
#
aaa
local-user sys-admin password irreversible-cipher $1c$2"iN;T!PrW$4H+g1J;+D>"[]=$i,Z/4(5"MWJ-Ld
%)']CO`l>Z9$
local-user sys-admin service-type ssh
local-user sys-admin state block fail-times 3 interval 5
local-user sys-admin user-group manage-ug
#
authentication-scheme default0
#
authentication-scheme default1
#
authentication-scheme default
authentication-mode local
#
authorization-scheme default
#
accounting-scheme default0
#
accounting-scheme default1
#
domain default0
#
domain default1
#
domain default_admin
authorization-scheme default
#
isis 65534
description auto-generated for virtual-access
is-level level-2
cost-style wide
virtual-access enable
network-entity 00.38ba.33bc.a402.00
binding interface GigabitEthernet1/0/1 down-weight 10
#
interface GigabitEthernet1/0/1
undo shutdown
isis enable 65534
isis circuit-type p2p
dcn
virtual-access enable
#
interface GigabitEthernet1/0/2
undo shutdown
#
interface GigabitEthernet1/0/3
undo shutdown
#
interface LoopBack2147483646
description virtual-access loopback interface
ip binding vpn-instance __dcn_vpn__
ip address 3.3.3.3 255.255.255.255
#
interface LoopBack2147483647

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 103

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

description DCN loopback interface

ip binding vpn-instance __dcn_vpn__
ip address 172.16.1.2 255.255.0.0
#
ospf 65534 vpn-instance __dcn_vpn__
description DCN ospf create by default
opaque-capability enable
hostname
vpn-instance-capability simple
area 0.0.0.0
network 0.0.0.0 255.255.255.255
#
!The DCN function implements the capability of plug-and-play for this device.
!A NE IP address based on the unique NE ID is automatically generated in VPN
!of DCN. It is recommended that the NE IP address be changed to the planned
!one by running the ne-ip X.X.X.X <mask> command after the device being online.
dcn
#
stelnet ipv4 server enable
sftp ipv4 server enable
snetconf ipv4 server enable
stelnet ipv6 server enable
sftp ipv6 server enable
snetconf ipv6 server enable
ssh user sys-admin
ssh user sys-admin authentication-type password
ssh user sys-admin service-type all
ssh user sys-admin sftp-directory cfcard:/
ssh authorization-type default aaa
#
ssh server cipher aes256_gcm aes128_gcm aes256_ctr aes192_ctr aes128_ctr
ssh server hmac sha2_512 sha2_256
ssh server key-exchange dh_group_exchange_sha256
#
ssh server publickey rsa_sha2_256 rsa_sha2_512
#
ssh server dh-exchange min-len 3072
#
ssh client first-time enable
sftp client-source -a 3.3.3.3 -vpn-instance __dcn_vpn__
#
user-interface con 0
#
user-interface vty 0 4
authentication-mode aaa
protocol inbound ssh
#
netconf
idle-timeout 0 0
#
local-aaa-server
#
return
● Master configuration file
#
sysname Master
#
virtual-access port-extend
role master
admin 1.1.1.1
ap default login-user root login-password %^%#gOTF'nZ=j7+odk7U&I%>xVl0+h.l8AuNHt2_Y*n~%^
%#
isis authentication-mode hmac-sha256 key-id 1 cipher %^%#RmQD<'UJ)/Nl3L6*
+L8=*&(P"e4H[B~JbRW!W>3A%^%#
#
rsa peer-public-key 2.2.2.2
public-key-code begin
3082010A
02820101

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 104

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

009FD60F 4245F341 C86A4717 BB17C282 CE090BB7 12E1A73F FFBF0D44 D51EF073

49A6CA0D 90077E7C BE173037 2851FDB5 A3390BB9 96EAE330 3F999B47 0A765780
C21BEA42 9A132975 D3A1D64B DEF6E5C2 4CD6A7F3 909F7574 9B84B0A8 BF744446
67B00D1D 440DD081 8ABDA172 F995C80C C2953A13 F8D6EECA E835A442 C650A464
BA4B96A2 15D21EBE DD71D5FC 06F559D9 7DC11AD7 3D538CFC FDD408C8 03AA4B3B
D93E4764 BBDE5FB8 9A2ACBCF 3E7188EE 81995DC4 5A2C8F63 8994F7DA 0094E410
96C3F70E 9AFBA22A 273F53A3 D152B245 636419BA 71B03A9A E488BA20 1FC18BFB
396A66A4 0F325E9C A2F1C0CD 9759E1AA ED9A27E6 68605CE2 D284F541 AAD00ED0
9F
0203
010001
public-key-code end
peer-public-key end
#
rsa peer-public-key 3.3.3.3
public-key-code begin
3082010A
02820101
00CFEC57 3531F1E0 97D6D719 5A4B3D2D 707EE3DD E3FDF9FA C4B73D47 E6D439B5
3ED2E12F C63D83B7 E76C9B25 125490F5 30AB7277 3BCCB159 F3C90881 32CCDEDC
E703EB64 5A46DDD2 969A2368 16CFF8FB DA1628D3 F8989A6B 135B66E5 CDC00157
68246295 C4670F50 BFD4F1C0 48A2C195 E4243F3A BD6BA3E3 32651930 F8A8E4B5
3020F373 2A58F15E DFE003B4 1B1ACF80 9E0490C1 BE5A2997 97D8B146 3FB16FF5
9F26DFF6 F83040AF 012D59EA 943F8AB8 71E21A07 5785537F F6523D9E C3050217
FD03E7B3 BA72AEEA FD108F6D 644EFABB 7C9F2971 065EE65F DDB61426 6ED5084B
CC7C99E3 C0B6A4BF 95181DBC E2DF89DD 29A24AD8 51E55CCA 8DB1F130 7CE0798F
83
0203
010001
public-key-code end
peer-public-key end
#
rsa peer-public-key 172.16.1.1
public-key-code begin
3082010A
02820101
009FD60F 4245F341 C86A4717 BB17C282 CE090BB7 12E1A73F FFBF0D44 D51EF073
49A6CA0D 90077E7C BE173037 2851FDB5 A3390BB9 96EAE330 3F999B47 0A765780
C21BEA42 9A132975 D3A1D64B DEF6E5C2 4CD6A7F3 909F7574 9B84B0A8 BF744446
67B00D1D 440DD081 8ABDA172 F995C80C C2953A13 F8D6EECA E835A442 C650A464
BA4B96A2 15D21EBE DD71D5FC 06F559D9 7DC11AD7 3D538CFC FDD408C8 03AA4B3B
D93E4764 BBDE5FB8 9A2ACBCF 3E7188EE 81995DC4 5A2C8F63 8994F7DA 0094E410
96C3F70E 9AFBA22A 273F53A3 D152B245 636419BA 71B03A9A E488BA20 1FC18BFB
396A66A4 0F325E9C A2F1C0CD 9759E1AA ED9A27E6 68605CE2 D284F541 AAD00ED0
9F
0203
010001
public-key-code end
peer-public-key end
#
rsa peer-public-key 172.16.1.2
public-key-code begin
3082010A
02820101
00CFEC57 3531F1E0 97D6D719 5A4B3D2D 707EE3DD E3FDF9FA C4B73D47 E6D439B5
3ED2E12F C63D83B7 E76C9B25 125490F5 30AB7277 3BCCB159 F3C90881 32CCDEDC
E703EB64 5A46DDD2 969A2368 16CFF8FB DA1628D3 F8989A6B 135B66E5 CDC00157
68246295 C4670F50 BFD4F1C0 48A2C195 E4243F3A BD6BA3E3 32651930 F8A8E4B5
3020F373 2A58F15E DFE003B4 1B1ACF80 9E0490C1 BE5A2997 97D8B146 3FB16FF5
9F26DFF6 F83040AF 012D59EA 943F8AB8 71E21A07 5785537F F6523D9E C3050217
FD03E7B3 BA72AEEA FD108F6D 644EFABB 7C9F2971 065EE65F DDB61426 6ED5084B
CC7C99E3 C0B6A4BF 95181DBC E2DF89DD 29A24AD8 51E55CCA 8DB1F130 7CE0798F
83
0203
010001
public-key-code end
peer-public-key end
#
ip dcn vpn-instance __dcn_vpn__

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 105

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

ipv4-family
#
bfd
#
dcn
#
isis 65534
description auto-generated for virtual-access
is-level level-2
cost-style wide
virtual-access enable
network-entity 00.38ba.1a42.1f01.00
binding interface GigabitEthernet1/1/0/1 down-weight 10
binding interface GigabitEthernet1/1/0/2 down-weight 10
#
interface GigabitEthernet1/1/0/1
undo shutdown
isis enable 65534
isis circuit-type p2p
dcn
virtual-access enable
#
interface GigabitEthernet1/1/0/2
undo shutdown
isis enable 65534
isis circuit-type p2p
dcn
virtual-access enable
#
interface LoopBack2147483646
description virtual-access loopback interface
ip binding vpn-instance __dcn_vpn__
ip address 1.1.1.1 255.255.255.255
#
interface LoopBack2147483647
description DCN loopback interface
ip binding vpn-instance __dcn_vpn__
ip address 10.1.1.1 255.255.0.0
#
ap-id 2000
sysname ap2000
esn 391092333866236
admin 2.2.2.2
login-user sys-admin login-password %^%#(p@y@~'n3/4m<"=;YyWDZIyvCQuK5D1JbuYk^ODQ%^%#
login-user sys-admin sftp-directory cfcard:/
authentication-mode local
#
ap-user
local-user sys-admin password cipher %^%#otll=pnt1#I_[1TE|k'F9-RT!@>rGAa%<&J@q9H&%^%#
inner-connect GigabitEthernet1/0/1 binding GigabitEthernet1/1/0/1
remote-interface GigabitEthernet1/0/2 binding GigabitEthernet1/1/0/1
remote-interface GigabitEthernet1/0/3 binding GigabitEthernet1/1/0/1
#
ap-id 2001
sysname ap2001
esn 391092333000298
admin 3.3.3.3
login-user sys-admin login-password %^%#/md1*$flA+)0\t.0B"43,q{>+2*)f-k&PWLDzjcL%^%#
login-user sys-admin sftp-directory cfcard:/
authentication-mode local
#
ap-user
local-user sys-admin password cipher %^%#(1F!FQJ[FP&+-H@%pe)G5h9r:g$)DF&19m@N\T(9%^%#
inner-connect GigabitEthernet1/0/1 binding GigabitEthernet1/1/0/2
remote-interface GigabitEthernet1/0/2 binding GigabitEthernet1/1/0/2
remote-interface GigabitEthernet1/0/3 binding GigabitEthernet1/1/0/2
#
interface NULL0
#

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 106

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

ospf 65534 vpn-instance __dcn_vpn__

description DCN ospf create by default
opaque-capability enable
hostname
vpn-instance-capability simple
area 0.0.0.0
network 0.0.0.0 255.255.255.255
#
!The DCN function implements the capability of plug-and-play for this device.
!A NE IP address based on the unique NE ID is automatically generated in VPN
!of DCN. It is recommended that the NE IP address be changed to the planned
!one by running the ne-ip X.X.X.X <MASK> command after the device being online.
dcn
bandwidth ethernet 1024
bandwidth pos 1024
#
ssh authorization-type default aaa
#
ssh client publickey dsa ecc rsa rsa_sha2_256 rsa_sha2_512
#
ssh client cipher aes256_gcm aes128_gcm aes256_ctr aes192_ctr aes128_ctr
ssh client hmac sha2_512 sha2_256
ssh client key-exchange dh_group_exchange_sha256
#
ssh client first-time enable
ssh client 172.16.1.1 assign rsa-key 172.16.1.1
ssh client 172.16.1.2 assign rsa-key 172.16.1.2
ssh client 2.2.2.2 assign rsa-key 2.2.2.2
ssh client 3.3.3.3 assign rsa-key 3.3.3.3
#
user-interface con 0
#
local-aaa-server
#
return

1.1.4 Transmission Alarm Customization and Suppression

Configuration
Transmission alarm customization and suppression can reduce the impact of
transmission alarms on network stability.

1.1.4.1 Overview of Transmission Alarm Customization and Suppression

Transmission alarm customization can control the impact of alarms on interface
status. Transmission alarm suppression can efficiently suppress alarms, which
prevents interfaces from frequently flapping.

Definition
Currently, carrier-class networks require high reliability for IP devices. As such,
devices on the networks are required to rapidly detect faults. After fast detection is
enabled on an interface, the alarm reporting speed is accelerated. As a result, the
physical status of the interface frequently alternates between up and down,
causing frequent network flapping. Therefore, alarms must be filtered and
suppressed to prevent frequent network flapping.

Transmission alarm suppression can efficiently filter and suppress alarm signals to
prevent interfaces from frequently flapping. In addition, transmission alarm
customization can control the impact of alarms on the interface status.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 107

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Transmission alarm customization and suppression provide the following

functions:
● Transmission alarm customization allows you to specify alarms that can cause
the physical status of an interface to change. This function helps filter out
unwanted alarms.
● Transmission alarm suppression allows you to suppress frequent network
flapping by setting thresholds and using a series of algorithms.

Purpose
Transmission alarm customization allows you to filter unwanted alarms, and
transmission alarm suppression enables you to set thresholds on customized
alarms, allowing devices to ignore burrs generated during transmission link
protection and preventing frequent network flapping.
On a backbone or metro network, IP devices are connected to transmission
devices, such as Synchronous Digital Hierarchy (SDH), Wavelength Division
Multiplexing (WDM), or Synchronous Optical Network (SONET) devices. If a
transmission device becomes faulty, the interconnected IP device receives an
alarm. The transmission devices then perform a link switchover. After the link of
the transmission device recovers, the transmission device sends a clear alarm to
the IP device. After an alarm is generated, a link switchover lasts 50 ms to 200 ms.
In the log information on IP devices, the transmission alarms are displayed as
burrs that last 50 ms to 200 ms. These burrs will cause the interface status of IP
devices to switch frequently. IP devices will perform route calculation frequently.
As a result, routes flap frequently, affecting the performance of IP devices.
From the perspective of the entire network, IP devices are expected to ignore such
burrs. That is, IP devices must customize and suppress the alarms that are
generated during transmission device maintenance or link switchovers. This can
prevent route flapping. Transmission alarm customization can control the impact
of transmission alarms on the physical status of interfaces. Transmission alarm
suppression can efficiently filter and suppress specific alarm signals to avoid
frequent interface flapping.
During the active/standby switchover, various transmission alarm signals can be
processed properly, and the transmission alarm configuration still takes effect.

1.1.4.2 Configuration Precautions for Transmission Alarm Customization and

Suppression

Feature Requirements
None

1.1.4.3 Configuring Transmission Alarm Customization

This section describes the usage scenario, pre-configuration tasks, and data
preparation for transmission alarm customization.

Usage Scenario
In the scenario where transmission devices are connected to IP devices, if the
network is unstable, a large number of burr alarms will be generated. As a result,

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 108

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

the physical status of interfaces on the transmission devices will switch between
Up and Down. To enable IP devices to ignore these burrs, configure transmission
alarm customization on the IP devices.

Pre-configuration Tasks
Before configuring the transmission alarm customization function, power on the
router and ensure that it is working properly.

1.1.4.3.1 Configuring the Types of Alarms that Affect the Physical Status of
Interfaces
In the scenario where a router is connected to a transmission device, if the
network is unstable, a large number of burr alarms may be generated. As a result,
the physical status of interfaces will frequently change between up and down. To
specify the alarms that can trigger the physical status of an interface to go down,
you can configure transmission alarm customization.

Context
Transmission alarm customization can be used to control the impact of
transmission alarms on the physical interface status. Perform the following steps
globally or on the interface connected to a transmission device:

Transmission alarm filtering intervals can be configured globally or on an

interface. The global configuration takes effect on interfaces supporting the
function. The relationship is as follows:
● If the alarm customization is configured globally and a non-default alarm
customization configuration exists on an interface, the configuration on the
interface preferentially takes effect.
● If the alarm customization is configured globally but is not configured on an
interface, the global configuration takes effect on the interface.

NOTE

In VS mode, global transmission alarm customization is supported only by the admin VS.

Procedure
● Configure transmission alarm customization globally.
a. Run system-view

The system view is displayed.

b. Run transmission-alarm down { wan | pos } { auais | b1tca | b2tca |
b3tca | lais | lcd | lof | lom | lop | los | lrdi | lrei | oof | pais | pplm | prdi |
prei | puneq | rdool | rrool | sdbere | sfbere | trool } *

The types of transmission alarms whose generation causes 10GE WAN

and POS interfaces to go down physically are customized globally.
c. Run commit

The configuration is committed.

● Configure transmission alarm customization on an interface.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 109

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

a. Run system-view

The system view is displayed.

b. Run the following commands as required:

▪ To enter the POS or 10GE WAN interface view, run the interface
interface-type interface-number command.

▪ To enter the WDM interface view, run the controller wdm controller-
number command.
c. Run the following commands as required:

▪ To customize the types of transmission alarms whose generation

causes the POS or 10GE WAN interface to go down physically, run
the transmission-alarm down { auais | b1tca | b2tca | b3tca | lais |
lcd | lof | lom | lop | los | lrdi | lrei | oof | pais | pplm | prdi | prei |
puneq | rdool | rrool | sdbere | sfbere | trool } * command.

▪ To customize the types of transmission alarms whose generation

causes the WDM interface to go down physically, run the
transmission-alarm down { odu-ais | odu-lck | odu-oci | otu-ais |
otu-lom | otu-sd-ber | otu-sf-ber | pm-bdi | pm-tim | r-lof | r-los |
r-oof | sm-bdi | sm-iae | sm-tim | prefec-tca | local-fault | remote-
fault } * command.
NOTE

● Not all interfaces support the preceding alarms because the alarm types
supported may vary with subcards. If you attempt to customize an alarm type
that is not supported by an interface for the interface, the customization fails,
and a message is displayed, telling you which alarm types are not supported
by this interface.
● WLNK alarms can be viewed only and cannot be customized. The WLNK
alarms are always enabled, and their generation causes interfaces to go down
physically. To view the status and statistics on WLNK alarms, run the display
transmission-alarm command.

NOTICE

By default, the LAIS, LOF, and LOS alarms can change interface status. If
these alarms are disabled, forwarding of service data may be adversely
affected. Therefore, you are advised to keep these alarms enabled.

d. Run commit

The configuration is committed.

----End

1.1.4.3.2 Verifying the Transmission Alarm Customization Configuration

After configuring transmission alarm customization, verify the configuration and
check the alarm status and statistics on an interface.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 110

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Prerequisites
Transmission alarm customization has been configured. The transmission alarm
suppression function has been enabled using the transmission-alarm damping
command.

Procedure
● To check the alarm configuration on a POS or 10GE WAN interface, run the
display transmission-alarm { pos | wan } interface-number [ auais | b1tca |
b2tca | b3tca | lais | lcd | lof | lom | lop | los | lrdi | lrei | oof | pais | prdi |
prei | pplm | puneq | rdool | rrool | sdbere | sfbere | trool | wlnk ] *
command.
● To check the alarm configuration on a WDM interface, run the display
transmission-alarm wdm interface-number [ odu-ais | odu-lck | odu-oci |
otu-ais | otu-lom | otu-sd-ber | otu-sf-ber | pm-bdi | pm-tim | r-lof | r-los |
r-oof | sm-bdi | sm-iae | sm-tim | prefec-tca | odu-sd-ber ] * command.

----End

1.1.4.4 Configuring Transmission Alarm Filtering Intervals

This section describes the usage scenario of transmission alarm filtering intervals,
and the pre-configuration tasks and operation procedure for configuring the
transmission alarm filtering intervals. If the lifetime (interval between alarm
generation and alarm clearance) of an alarm is less than the generation alarm
filtering interval, the alarm is filtered out as a burr. Otherwise, the alarm is
considered as a normal alarm.

Usage Scenario
In the scenario where a router is connected to a transmission device, if the
network is unstable, a large number of burr alarms may be generated. As a result,
the physical status of interfaces will frequently change between up and down. If a
transmission alarm filtering interval is configured, the alarms whose lifetime is
shorter than the interval will be ignored.

Transmission alarm filtering intervals can be configured globally or on an

interface. The global configuration takes effect on interfaces supporting the
function. The relationship is as follows:

● If a transmission alarm filtering interval is configured globally and a non-

default transmission alarm filtering interval is configured on an interface, the
configuration on the interface preferentially takes effect.
● If no transmission alarm filtering interval is configured in the interface view,
the global configuration takes effect.
NOTE

In VS mode, global transmission alarm filtering intervals are supported only by the admin
VS.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 111

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Pre-configuration Tasks
Before configuring transmission alarm filtering intervals, complete the following
tasks:

● Power on the router and ensure that the router passes the self-check.
● Configure transmission alarm customization on the router's interface
connected to the transmission device by referring to 1.1.4.3 Configuring
Transmission Alarm Customization.
NOTE

The alarm filtering function on an interface takes effect only after transmission alarm
customization is configured on the interface.

Procedure
● Enable the global alarm filtering function and set global generation and
clearance alarm filtering intervals.
a. Run system-view

The system view is displayed.

b. Run transmission-alarm holdoff-timer holdoff-time

Generation alarm filtering is enabled globally, and an interval for filtering

generation alarms is configured globally.
c. Run transmission-alarm holdup-timer holdup-time

Clearance alarm filtering is enabled globally, and an interval for filtering

clearance alarms is configured globally.
d. Run commit

The configuration is committed.

● Configure the alarm filtering function on an interface and set generation and
clearance alarm filtering intervals for the interface.
a. Run system-view

The system view is displayed.

b. Run the following commands as required:

▪ To enter the POS or 10GE WAN interface view, run the interface
interface-type interface-number command.

▪ To enter the WDM interface view, run the controller wdm controller-
number command.
c. Run transmission-alarm holdoff-timer [ holdoff-time ]

The generation alarm filtering function is configured on the interface,

and a generation alarm filtering interval is set for the interface.

If the lifetime (interval between alarm generation and alarm clearance)

of an alarm is less than the generation alarm filtering interval, the alarm
is filtered out as a burr. Otherwise, the alarm is considered as a normal
alarm.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 112

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

d. Run transmission-alarm holdup-timer [ holdup-time ]

The clearance alarm filtering function is configured on the interface, and
a clearance alarm filtering interval is set for the interface.
e. Run commit
The configuration is committed.
----End

Verifying the Configuration

After the configuration is complete, run the display transmission-alarm
command to check the interface configuration.

1.1.4.5 Configuring Transmission Alarm Suppression

This section describes the usage scenario, pre-configuration tasks, and
configuration procedure for transmission alarm suppression. If a transmission
alarm suppression threshold is configured, an alarm is reported only when the
threshold is reached.

Usage Scenario
In the scenario where a router is connected to a transmission device, if the
network is unstable, a large number of burr alarms may be generated. As a result,
the physical status of interfaces will frequently change between up and down. To
prevent these alarms from frequently flapping or configure the device to ignore
these burr alarms, you need to enable transmission alarm suppression.

Pre-configuration Tasks
Before configuring transmission alarm suppression, complete the following tasks:
● Power on the router and ensure that the router passes the self-check.
● Configure transmission alarm customization on the router's interface
connected to the transmission device by referring to 1.1.4.3 Configuring
Transmission Alarm Customization.
NOTE

Transmission alarm suppression takes effect on an interface only after transmission alarm
customization is configured on the interface.

Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run the following commands as required:
1. To enter the POS or 10GE WAN interface view, run the interface interface-
type interface-number command.
2. To enter the WDM interface view, run the controller wdm interface-number
command.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 113

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Step 3 Run transmission-alarm damping [ ceiling ceiling | reuse reuse | suppress

suppress | decay-ok decay-ok | decay-ng decay-ng ] *

Transmission alarm suppression is enabled, and suppression parameters are set.

Step 4 Run commit

The configuration is committed.

----End

Verifying the Configuration

After configuring transmission alarm suppression, verify the configuration.

Run the display transmission-alarm configuration command to check the

transmission alarm configuration on an interface.

1.1.4.6 Maintaining Transmission Alarm Customization and Suppression

This section describes how to check bit error rates and how to clear information
about transmission alarms.

1.1.4.6.1 Checking Bit Error Rates

When a bit error rate alarm is generated and the device sets the interface to
down, you can query the current bit error rates.

Procedure
● To query the current bit error rates of an interface, run the display
transmission-alarm bit-error-rate command in any view.

----End

1.1.4.6.2 Clearing the Information About Transmission Alarms

Before re-collecting information about transmission alarms on an interface, clear
the existing information about transmission alarms on the interface.

Context

NOTICE

After information about transmission alarms has been cleared, all statistics on
alarms will be reset. Exercise caution when running the reset transmission-alarm
statistics command.

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 114

HUAWEI NetEngine9000
Configuration Guide 1 Configuration

Procedure
● To clear the information about transmission alarms on an interface, run the
reset transmission-alarm statistics command in the interface view.
----End

Issue 01 (2022-10-31) Copyright © Huawei Technologies Co., Ltd. 115