NE40E-M2

V800R021C10

Commissioning Guide

Issue Date 2022-07-01

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 statments, 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]
Commissioning Guide

Contents

1 About This Document 1

2 Commissioning Flow 5

3 Logging In to the NE40E 6

3.1 Logging In to the NE40E by Using the Console Interface 6

3.2 Logging In to the NE40E by Using Telnet 10

3.3 Logging In to the NE40E by Using SSH 13

3.4 Logging In to the NE40E by Using DCN 16

4 Checking the Hardware 21

4.1 Checking the Software Version 21

4.2 Checking the Health Status of the NE40E 21

4.3 Checking the Master/Slave State of Components on a Device 22

4.4 Checking the Board Registration Status 22

4.5 Checking the Power Status 24

4.6 Checking System Time 24

4.7 Checking the Fan Status 25

4.8 Checking the Interface Status 25

4.9 Checking Alarm Information 26

4.10 Checking the Voltage of Each Board 27

4.11 Checking the Temperature of Each Board 28

5 Commissioning the Link Layer 30

5.1 Checking Ethernet Interfaces 30

5.2 Checking WDM Interfaces 31

5.3 Checking E-Carrier Interfaces 32

5.4 Commissioning TDM Interfaces 33

5.5 Checking the Optical Power of Interfaces 36

2022-07-08 I
Commissioning Guide

1 About This Document

Purpose
This document is a guide to HUAWEI NE40E-M2 series commissioning and verification. It describes how to
commission hardware, links, services, and maintenance and management during deployment, ensuring
stable and reliable operation of HUAWEI NE40E-M2 seriess on networks.
The intended audience of this document includes installation and commissioning engineers.

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

Product Name Version

HUAWEI NE40E-M2 series V800R021C10SPC600

iMaster NCE-IP V100R021C10SPC201

Intended Audience
This document is intended for:

• Commissioning engineers

Security Declaration
• Notice on Limited Command Permission
This document describes the commands used for network deployment and maintenance, but does not
cover confidential commands such as those used for production, assembly, and return-to-factory
inspection. For details about confidential commands, please submit an application.

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

• 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

2022-07-08 1
Commissioning Guide

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

■ 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

2022-07-08 2
Commissioning Guide

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.

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.

2022-07-08 3
Commissioning Guide

Convention Description

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

{ x | y | ... } Optional items are grouped in braces and separated by vertical bars.
One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated by vertical

bars. One item is selected or no item is selected.

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

[ x | y | ... ]* Optional items are grouped in brackets and separated by vertical

bars. Several items or no item can be selected.

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

# A line starting with the # sign is comments.

Change History
Changes between document issues are cumulative. The latest document issue contains all the changes made
in earlier issues.

• Changes in Issue 03 (2022-05-31)

This issue is the third official release. The software version of this issue is V800R021C10SPC600.

• Changes in Issue 02 (2022-03-31)

This issue is the second official release. The software version of this issue is V800R021C10SPC500.

• Changes in Issue 01 (2021-12-31)

This issue is the first official release. The software version of this issue is V800R021C10SPC300.

2022-07-08 4
Commissioning Guide

2 Commissioning Flow
This section describes the NE40E commissioning flow. Users can know the entire process of NE40E
commissioning in site deployment after reading this section.

Figure 1 Commissioning flow

Table 1 Commissioning procedures

Commissioning Procedure Description

Logging In to the NE40E Describes how to log in to the NE40E for later
commissioning.

Checking the Hardware Describes how to check power supply, fans, boards,
and interfaces to prepare for NE40E commissioning.

Commissioning the Link Layer Describes how to commission the link layer when
the NE40E is connected to other routers or transport
devices.

Commissioning Services and Protocols Describes how to commission services and protocols,
especially routing protocols, tunnel services, VPN
services, and BFD functions, when the NE40E is
connected to other routers or transport devices.

2022-07-08 5
Commissioning Guide

3 Logging In to the NE40E

This section describes how to log in to a device through a console interface, Telnet, or SSH for
commissioning. You can also batch deploy devices through the DCN function.

Prerequisites
Command levels are associated with user privilege levels. A user can run only the commands at the same or
lower level than the user privilege level. This mechanism ensures device security.

• If you log in to a device through SSH (STelnet) for the first time, the first-login process is used to create
a new username and password. To log in to the device using a customized account, load the default-
custom.defcfg file. For details about accounts and passwords, see List of Customized and Default
Accounts and Passwords.

• When you log in through a console interface for the first time, no default user name or password is
available. Therefore, configure a user name and password after the login. Keep your password safe. If
your password is lost, you can restore the default settings and use the preset password to log in.
However, this method causes the system to clear all your manual configurations and the configurations
cannot be restored.

• The console interface login method is still available if you log in not through a console interface.
Therefore, to prevent unauthorized users from logging in through the console interface, configure a
user name and password for the console interface login method immediately after you log in using
another method and configure services. This configuration prevents unauthorized users from querying
or modifying service configurations.

• After the device is powered on, it will automatically bind the management network interface to the VPN
for exclusive use (__LOCAL_OAM_VPN__) and configure the IP address 192.168.0.1/24 for the
management network interface. Use the IP address 192.168.0.1 to stelnet to the that is powered on for
the first time. The user can configure any other IP address for the network segment 192.168.0.1/24 on
the PC, and directly log in to the device using the user name and password for on-site equipment
maintenance. The IP address of the management network interface can be changed or deleted. The
management interface can be disabled as required.

3.1 Logging In to the NE40E by Using the Console Interface

When setting up a local configuration environment with the console interface being used, you can log in to
the NE40E by using the terminal emulation program on the PC.

Prerequisites

2022-07-08 6
Commissioning Guide

Figure 1 Networking diagram of logging in to the NE40E by using the console interface

• The NE40E is powered on and works properly.

• The PC is connected to the NE40E through asynchronous interfaces.

• Installing terminal emulation program on the PC (such as PuTTY.exe)

Perform the following configurations on the terminal emulation program on the PC.

Procedure
1. Use a serial cable to connect the serial interface on the PC and the console interface on the NE40E.
For details about the console interface, see the NE40E Hardware Description.

If a third-party USB-to-RJ45 serial cable is used, it is recommended that the cable length be less than or equal to
2 m to ensure signal integrity.

2. Start the terminal emulation program such as PuTTY.exe on the PC.

3. On the PuTTY configuration page (shown in Figure 2), set the connection type to Serial.

2022-07-08 7
Commissioning Guide

Figure 2 PuTTY configuration page

4. Select Serial under Connection from the left navigation tree on the PuTTY configuration page. On the
page shown in Figure 3, set communication parameters of the port to be consistent with those on the
device. (The following figure is for reference only. Use the default settings during configuration.)

2022-07-08 8
Commissioning Guide

Figure 3 PuTTY configuration page

5. Click Open. Then the system prompts you to set an authentication password, as shown in Figure 4.
After the confirm the password, the system automatically saves it.

Figure 4 Login page

Commissioning Result
After the password is set, the command prompt (for example, <HUAWEI>) of the user view is displayed,
which indicates that you have entered the user view and can perform configurations.
You can enter commands to configure the router or view its running status. Enter a question mark (?) when
you need help.
2022-07-08 9
Commissioning Guide

• A password is entered in man-machine interaction mode. The system does not display the entered password.

• A password is a string of 8 to 16 case-sensitive characters and must contain at least two types of the following
characters: uppercase letters, lowercase letters, digits, and special characters.
Special characters do not include question marks (?) or spaces. However, when double quotation marks are used
around a password, spaces are allowed in the password.
■ Double quotation marks cannot contain double quotation marks if spaces are used in a password.
■ Double quotation marks can contain double quotation marks if no space is used in a password.

For example, the password "Aa123"45"" is valid, but the password "Aa 123"45"" is invalid.

The configured password is displayed in ciphertext in the configuration file.

If the login fails, click Disconnect and then Call. If the login still fails, repeat Step 1 to check whether the
parameters or physical connections are correct. If they are correct, log in to the NE40E again.

3.2 Logging In to the NE40E by Using Telnet

This section describes how to log in to the NE40E by using Telnet. A Telnet operation allows you to log in to
a remote device for device management.

Prerequisites
Figure 1 Networking diagram of logging in to the NE40E by using Telnet

Before logging in to the NE40E by using Telnet, complete the following tasks:

• Ensure that the NE40E is working properly.

• Log in to the NE40E by using the console interface and configure an IP address for each interface on the
NE40E.

• Ensure that there is a direct or reachable route between the Telnet client and the NE40E.

Perform the following configurations through the console interface on the NE40E that serves as the Telnet server:

Procedure
1. Enable the Telnet function.

a. Run the system-view command to enter the system view.

b. Run the telnet server enable command to enable the telnet function.

2022-07-08 10
Commissioning Guide

c. Configure the source interface or source address for the Telnet server.

• Run telnet server-source -i { interface-type interface-number | interface-name }

The source interface is specified for the Telnet server.

If you specify a logical interface as the source interface of the Telnet server, this interface must have
been created. Otherwise, the command cannot be executed successfully.

• Run telnet server-source all-interface

Any interface on the Telnet server can be used as its source interface.
After the command is run, users can log in to the Telnet server through any physical
interface configured with an IPv4 address or any created logical interface configured with
an IPv4 address.

If the telnet server-source all-interface command is run, users can log in to the Telnet server
through any interface with a valid IPv4 address, which increases system security risks. Therefore,
running the command is not recommended.

• Run telnet ipv6 server-source -a ipv6-address [ -vpn-instance vpn-instance-name ]

A source IPv6 address is specified for the Telnet server.
If a source IPv6 address is specified, the Telnet server allows users to log in using this
source IPv6 address only and denies access of the users who attempt to log in using other
IPv6 addresses.

• Run telnet ipv6 server-source all-interface

The IPv6 address of any interface on the Telnet server can be used as the source IPv6
address of the Telnet server.
After the command is run, users can log in to the Telnet server through any physical
interface configured with an IPv6 address or any created logical interface configured with
an IPv6 address.

If the telnet ipv6 server-source all-interface command is run, users can log in to the Telnet server
through any valid interface IPv6 address, which increases system security risks. Therefore, running
the command is not recommended.

• Run telnet server-source physic-isolate -i { interface-type interface-number | interface-

name } -a ip-address
A source interface is specified for the Telnet server, and the interface isolation attribute is
set for the Telnet server.

• Run telnet ipv6 server-source physic-isolate -i { interface-type interface-number |

interface-name } -a ipv6-address

A source IPv6 interface is specified for the Telnet server, and the interface isolation

2022-07-08 11
Commissioning Guide

attribute is set for the Telnet server.

After the interface isolation attribute is set successfully, packets can be sent to the server only
through the specified physical interface, and those sent through other interfaces are discarded.

d. Run the commit command to commit the configuration.

2. Set the maximum number of users that are allowed to log in to the NE40E at the same time.

a. Run the system-view command to enter the system view.

b. Run the user-interface maximum-vty number command to set the maximum number of login
users that can use VTY user interfaces on the Router.

c. Run the commit command to commit the configuration.

3. Configure a user authentication mode.

Two authentication modes are available: password authentication and AAA authentication. One of
them can be selected as needed.

• If users with passwords need to be created and managed on the Router, AAA authentication is
recommended.
• Using STelnet is recommended for a network that has high security requirements.

• Configure password authentication.

a. Run the system-view command to enter the system view.

b. Run the user-interface { ui-type ui-number1 | ui-number } command to enter the user interface
view.

c. Run the authentication-mode password command to configure password authentication.

d. Run the set authentication password cipher password command to change the password used
in authentication.

e. Run the commit command to commit the configuration.

• Configure AAA authentication.

a. Run the system-view command to enter the system view.

b. Run the user-interface { ui-type ui-number1 | ui-number } command to enter the user interface
view.

c. Run the authentication-mode aaa command to configure AAA authentication.

d. Run the protocol inbound { telnet | all } command to configure VTY user interfaces to support
Telnet.

2022-07-08 12
Commissioning Guide

e. Run the aaa command to enter the AAA view.

f. Run the local-user user-name password cipher password command to configure the local user
name and password.

g. Run the local-user user-name service-type telnet command to set the access type of the local
user to Telnet.

h. Run the quit command to exit from the AAA view.

4. Run the user privilege level level command in the user interface view to control the user rights.

5. Run the commit command to commit the configuration.

3.3 Logging In to the NE40E by Using SSH

This section describes how to log in to the NE40E by using SSH. SSH is a secure remote login protocol, which
is developed based on the traditional Telnet protocol. Compared with Telnet, SSH is greatly improved in
terms of the authentication mode and data transmission security.

Prerequisites
Figure 1 Networking diagram of logging in to the NE40E by using SSH

Before logging in to the NE40E by using SSH, complete the following tasks:

• Ensure that the NE40E is working properly.

• Log in to the NE40E by using the console interface and configure an IP address for each interface on the
NE40E.

• Ensure that there is a direct or reachable route between the SSH client and the NE40E.

By default, you can log in to a device directly using STelnet through the management network port.
After the device is powered on, the system will automatically bind the management network port to the VPN for
exclusive use (__LOCAL_OAM_VPN__) and assign the IP address 192.168.0.1/24 for the management network port.
You can configure other IP address in the network segment 192.168.0.0/24 for the terminal. Then, log in to the device
using SSH (STelnet) to maintain the device on site. See the default user name and password in List of Customized and
Default Accounts and Passwords.
After configuring services, change the user name and password immediately to ensure service security. The IP address of
the management network port can be changed or deleted. You can shut down the management network port as
required.
Perform the following configurations on the NE40E that serves as the SSH server:

2022-07-08 13
Commissioning Guide

Procedure
1. Configure the NE40E to generate a local key pair.

a. Run the system-view command to enter the system view.

b. Run the rsa local-key-pair create command to configure the NE40E to generate a local RSA key
pair.

2. Configure a VTY user interface to support SSH.

a. Run the system-view command to enter the system view.

b. Run the user-interface { vty first-ui-number | last-ui-number } command to enter the VTY user
interface view.

c. Run the authentication-mode aaa command to specify AAA authentication as the

authentication mode.

d. Run the protocol inbound ssh command to configure SSH as the access protocol in the VTY user
interface view.

AAA authentication must be configured in the VTY user interface view; otherwise, the protocol inbound
ssh command does not take effect.

3. Run the ssh user user-name command in the system view to create an SSH user.

4. Run the ssh user user-name authentication-type { password | rsa | dsa | ecc | password-dsa |
password-rsa | password-ecc | sm2 | password-sm2 | all } command in the system view to configure
an authentication mode for SSH users.
Perform one of the following operations as needed:

• Configure password authentication.

■ Run the ssh user user-name authentication-type password command to configure

password authentication.

■ Run the ssh authentication-type default password command to configure preset password
authentication.

In local authentication or HWTACACS authentication mode, password authentication is

recommended if the number of SSH users is small, and preset password authentication is
recommended if the number of SSH users is large.

• Configure RSA authentication.

By default, you can log in to a device directly using STelnet through the management network port.

2022-07-08 14
Commissioning Guide

After the device is powered on, the system will automatically bind the management network port to the VPN for
exclusive use (__LOCAL_OAM_VPN__) and assign the IP address 192.168.0.1/24 for the management network
port.
You can configure any other IP address in the network segment 192.168.0.0/24 for the terminal. Then, log in to
the device using SSH (STelnet) to maintain the device on site. For more details about the default accounts and
passwords, see the List of Customized and Default Accounts and Passwords.
After configuring services, change the user name and password immediately to ensure service security. The IP
address of the management network port can be changed or deleted. You can shut down the management
network port as required.
To ensure high security, do not use the RSA algorithm whose length is less than 2048 digits. You are advised to
use ECC authentication algorithm which ensures higher security.

a. Run the ssh user user-name authentication-type rsa command to configure RSA
authentication.

b. Run the rsa peer-public-key key-name command to enter the public key view.

c. Run the public-key-code begin command to enter the public key edit view.

d. Enter illegal hexadecimal hex-data to edit the public key.

e. Run the public-key-code end command to exit from the public key edit view.
If illegal hexadecimal data is entered, no key will be generated after the peer-public-key end
command is run. If key-name specified in Step b has been deleted in another window, the
system will display a message indicating that the key does not exist and return to the system
view directly after you run the peer-public-key end command.

f. Run the peer-public-key end command to return to the system view.

g. Run the ssh user user-name assign rsa-key key-name command to assign the SSH user a public
key.

5. In password or RSA authentication mode, create a local user with the SSH user name in the AAA view.

a. Run the aaa command in the system view to enter the AAA view.

b. Run the local-user user-name password cipher password command to configure the local user
name and password.

The new password is at least eight characters long and contains at least two of the following types:
upper-case letters, lower-case letters, digits, and special characters, except the question mark (?) and
space.

c. Run the local-user user-name level level command to configure the priority of the local user.

d. Run the local-user user-name service-type ssh command to configure the local user access
type.

e. Run the quit command to exit from the AAA view.

6. Run the ssh user username service-type { sftp | stelnet | snetconf | all } command in the system view
to configure a service type for the SSH user.

7. Run the stelnet server enable command in the system view to enable STelnet.

2022-07-08 15
Commissioning Guide

8. Specify the source interface or source address for the SSH server.

• Run the ssh server-source -i { interface-type interface-number | interface-name } command to

specify the source interface of the SSH server.

• Run the ssh server-source all-interface command to specifies all interfaces on the device as the
source interface of the SSH server.

• Run the ssh ipv6 server-source -a ipv6-address [ -vpn-instance vpn-instance-name ] command to

specify the source IPv6 address of the SSH server.

• Run the ssh ipv6 server-source all-interface command to specifies all IPv6 interfaces on the
device as the source interface of the SSH server.

• Run the ssh server-source physic-isolate -i { interface-type interface-number | interface-name } -

a ip-address command to specify the source interface of the SSH server and set the interface
isolation attribute of the SSH server.

• Run the ssh ipv6 server-source physic-isolate -i { interface-type interface-number | interface-

name } -a ipv6-address command to specify the source IPv6 interface of the SSH server and set
the interface isolation attribute of the SSH server.

If the all-interface parameter is configured, users can log in to the SSH server through all valid interfaces, which
increases system security risks. Therefore, running the command is not recommended.
After the interface isolation attribute is set successfully, packets can be sent to the server only through the
specified physical interface, and those sent through other interfaces are discarded.

9. Run the commit command in the system view to commit the configuration.

3.4 Logging In to the NE40E by Using DCN

This chapter describes how to enable DCN globally, enable DCN on an interface, enable the automatic NE
report function on a GNE, and configure NE IDs and NE IP addresses.

Usage Scenario
The construction of a large network requires significant human and material resources if software
commissioning engineers have to configure devices on site, causing high operational expenditure (OPEX).
DCN can reduce the OPEX by allowing GNEs to manage NEs. DCN enables NMSs to rapidly detect new NEs
and remotely manage the NEs.
The DCN technique offers a mechanism to implement plug-and-play. After each NE is initialized, it generates
an NE IP address based on its NE ID, creates a mapping entry for the NE ID and NE IP address, adds the
mapping entry to its DCN core routing table, and uses OSPF to advertise the mapping entry to all other NEs
on the DCN. Therefore, all the NEs on the DCN can communicate with each other.
The DCN feature allows NMSs to use GNEs to manage NEs. A GNE supports the automatic NE report
function, enabling the GNE to automatically report a new NE's information to NMSs immediately after the

2022-07-08 16
Commissioning Guide

GNE detects the new NE. Then the NMSs can manage the new NE in time. In addition, a GNE can send a
trap to its interworking NMSs when the number of NEs connected to the GNE reaches the alarm threshold.
Then the NMSs will generate alarms to inform users of this information.

Pre-configuration Tasks
Before configuring basic DCN functions, complete the following tasks:

• Configure reachable routes between the GNE and NMSs.

• Configure reachable routes between the GNE and NEs.

When the GNE is connected to an NE for the first time, the SSH default user account is used for login.

Procedure
1. Enable DCN Globally.

a. Run system-view
The system view is displayed.

b. Run dcn
The DCN function is enabled globally.

c. Run commit
The configuration is committed.

2. Enable DCN on an interface and specify a DCN VLAN.

By default, DCN is enabled on some interfaces. For details, see .

After an interface is switched to a FLEX interface, the DCN status does not change.
The default DCN enabling rule of a subcard with adjustable interface bandwidth is the same as that of a subcard
with only one type of interface bandwidth and is not affected by the adjustable bandwidth.

Table 1 Rules for enabling DCN on interfaces by default

Interfaces on Fixed Ethernet Interfaces on POS Interface on E1 and CPOS

Boards Flexible Cards Flexible Cards Interfaces on Subcards
That Support the DCN
Function

DCN is enabled on all In transport mode: For a subcard with For channelized
interfaces by default. For a subcard with eight or more interfaces, DCN is

multiple types of interfaces, DCN is enabled on interfaces 2,

2022-07-08 17
Commissioning Guide

Interfaces on Fixed Ethernet Interfaces on POS Interface on E1 and CPOS

Boards Flexible Cards Flexible Cards Interfaces on Subcards
That Support the DCN
Function

interface bandwidths, enabled on the first 18, 34, and 50 by

DCN is enabled on the four interfaces by default.
first four interfaces by default. For non-channelized
default. For a subcard with four interfaces, DCN is
For a subcard with only to seven interfaces, enabled on interfaces 2
one type of interface DCN is enabled on the and 18 by default in
bandwidth: first two interfaces by transport mode.DCN is
For a subcard with default. enabled on interfaces 1
eight or more For a subcard with less and 17 by default in
interfaces, DCN is than four interfaces, non-transport mode.
enabled on the first DCN is enabled on the
four interfaces by first interface.
default.
For a subcard with five
to seven interfaces,
DCN is enabled on the
first two interfaces by
default.
For a subcard with four
or less interfaces, DCN
is enabled on the first
interface by default.
In non-transport mode:
DCN is enabled on all
interfaces by default.

In router mode:

a. Run the system-view command to enter the system view.

b. Run the interface interface-type interface-number command to enter the interface view.

c. Run the dcn (interface view) command to enable DCN on the interface.

d. Run the dcn vlan vlan-id or or dcn vlan { beginvlan-id [ to endvlan-id ] } &<1–4094>command
to specify a DCN VLAN.

e. Run the commit command to commit the configuration.

2022-07-08 18
Commissioning Guide

In router mode, a DCN VLAN can be a service VLAN.

In transport mode:

a. Run the system-view command to enter the system view.

b. Run the interface interface-type interface-number command to enter the interface view.

c. Run the dcn command to enable DCN on the interface.

d. Run the dcn vlan vlan-id command to specify a DCN VLAN.

e. Run the commit command to commit the configuration.

In transport mode, only one DCN VLAN can be configured. And it is conflicted with service VLAN.

3. Configure the automatic NE report function on a GNE.

a. Run system-view
The system view is displayed.

b. Run dcn
The DCN view is displayed.

c. Run auto-report
The automatic NE report function is enabled.

d. Run commit
The configuration is committed.

4. Configure an NE ID and NE IP address.

a. Run system-view
The system view is displayed.

b. Run set neid ne-id

An NE ID is set.

c. Run dcn
The DCN view is displayed.

d. Run ne-ip ip-address { ip-mask | mask-length }

An NE IP address is set.

e. Run commit
The configuration is committed.

5. (Optional) Configure the bandwidth for DCN interfaces to send packets.

a. Run system-view

2022-07-08 19
Commissioning Guide

The system view is displayed.

b. Run dcn
The DCN view is displayed.

c. Run bandwidth { ethernet bandwidth | pos bandwidth | serial bandwidth }

d. Run commit
The configuration is committed.

Checking the Configurations

Perform the following operations to check the configurations:

• Run the display neid command to check the NE ID.

• Run the display dcn brief command to check configurations of the GNE.

• Run the display dcn ne-info command to check information about the DCN core routing table.

• Run the display dcn global command to check whether DCN is enabled globally.

• Run the display dcn default-port command to check the interface on which DCN is enabled by default.

• Run the display dcn interface [ interface-type interface-number ] command to check DCN
configurations and traffic statistics of an interface.

• Run the display dcn warning command to check DCN trap information.

Follow-up Procedure
An NMS's IP address is a public IP address, and a GNE's NE IP address is a Layer 3 VPN address. To
implement address conversion, specify the interface that connects a GNE to an NMS, bind the interface to a
DCN VPN instance, and set an IP address for the interface. After DCN is enabled globally on the GNE, it
automatically generates a DCN VPN instance named __dcn_vpn__. Detailed operations are as follows:

• Run the interface interface-type interface-number command to display the interface view.

• Run the ip binding vpn-instance vpn-instance-name command to bind a DCN VPN instance.

• Run the ip address { mask | mask-length } command to set an interface IP address.

2022-07-08 20
Commissioning Guide

4 Checking the Hardware

This section describes how to check power supply, fans, boards, and interfaces to prepare for NE40E
commissioning.

4.1 Checking the Software Version

You need to check whether the used software version meets deployment requirements.

Prerequisites
Logging In to the NE40E is complete.

Procedure
1. Run the display version [ slot slot-id ] command to view the version information.
If the version displayed in the preceding information on the NE40E is consistent with the version
required for deployment, go on with the subsequent commissioning.

2. Run the display startup command to view the system software and configuration files for the current
and next startup.
If the names of system software and configuration files, displayed in the preceding information, for
the next startup are consistent with that required for deployment, go on with the subsequent
commissioning.

Troubleshooting
If the software version does not meet the deployment requirement, it needs to be upgraded.

Before upgrade, use either of the following methods to view or download the reference product document or system
software:

• Contact Huawei technical support engineers.

• For carrier network users, log in to https://support.huawei.com to browse or search for product names.
• For enterprise network users, log in to https://support.huawei.com/enterprise/ to browse or search for product
names.

4.2 Checking the Health Status of the NE40E

You need to check whether the current status of the NE40E meets the deployment requirement.

Prerequisites
Logging In to the NE40E is complete.

2022-07-08 21
Commissioning Guide

Procedure
1. Run the display health command to view the health status of the NE40E.
If the CPU usage and memory usage of the boards on the NE40E remain under 80%, as shown by the
percentages in boldface in the displayed information, go on with the subsequent commissioning.

Troubleshooting
In normal situations, CPU or memory usage should be lower than 80%.
If CPU or memory usage remains high before services are deployed in a large scale, contact Huawei
technical support personnel.

4.3 Checking the Master/Slave State of Components on a

Device
The following section describes how to check the master/slave state of components on a device.

Prerequisites
Logging In to the NE40E is complete.

Procedure
1. Run the display device [ pic-status | slot-id ] command to view the master/slave state of installed
components on a device.
Focus on the Primary field to check whether the current component has a backup. Master indicates
that the component is a master component, Slave indicates that the component is a slave component,
and NA indicates that there is no master or slave role.

4.4 Checking the Board Registration Status

You need to check whether all boards are properly installed and work normally.

Prerequisites
Logging In to the NE40E is complete.

Procedure
1. Run the display device [ pic-status | slot-id ] command to view information about the components
installed on the NE40E. If [ pic-status | slot-id ] is specified, the command will display information
about the broads.

2022-07-08 22
Commissioning Guide

Pay attention to the Register and Status fields in the displayed information.

• Register field: indicates whether a component is successfully registered. The field value can be
Registered or Unregistered. Registered indicates that a component is successfully registered.
Unregistered indicates that a component is not registered.

• Status field: indicates the component status. The field value can be Normal or Abnormal.

If the Register field values are Registered and the Status field values are Normal, as shown by the
characters in boldface in the preceding displayed information, go on with the subsequent
commissioning.

Troubleshooting
If the interface board is not registered, perform the following operations:

1. Check that the start-up time of the board has expired.

The time required for a board to complete registration after it is powered on is called the start-up
time.
Wait until the start-up time expires. If the board is still unregistered when the start-up time expires, go
to Step 2.

2. Check that the board type is supported by the system software.

Supported board types vary with system software versions. For the types of boards that are supported
by this software version, see the chapter titled "Boards" in the NE40EHardware Description.
If the board type is supported by this system software version but the board cannot be registered, go
to Step 3.

3. Check that the board has been powered on.

Run the power on slot ? command in the user view. If "<null>" is displayed, all boards have been
powered on.
If the slot number of the board is displayed, the board is not powered on. Check whether the power
supply of the slot where the board resides is normal. If the indicator on the board is on, the power
supply of this slot is normal.

• If the power supply of the slot is abnormal, contact Huawei technical support personnel.

• If the power supply of the slot is normal but the system still informs that the board is not
powered on, the power module on the board is faulty. In this case, you need to replace the board.

If the device has a standby main control board and the power supply is normal but the board still
cannot be registered, go to Step 4.

4. If a new board cannot be registered, remove the board and then insert it back. If the board still cannot
be registered, go to Step 5.

5. Collect the following information and contact Huawei technical support personnel:

• Results of the preceding operation procedure.

2022-07-08 23
Commissioning Guide

• Configuration files, log files, and alarm files of the NE40E.

4.5 Checking the Power Status

You need to check whether power modules work properly.

Prerequisites
Logging In to the NE40E is complete.

Procedure
1. Run the display power command to check the power status.
If the power modules are properly installed and work normally, go on with the subsequent
commissioning.

Commissioning Result
The displayed information may be different in real-world situations. For details, see display power.

4.6 Checking System Time

You need to check system time to ensure that the NE40E works with other devices coordinately.

Prerequisites
Logging In to the NE40E is complete.

Procedure
1. Run the display clock command to view system time.
If the system time and time zone are consistent with the local time and time zone, go on with the
subsequent commissioning.

Troubleshooting
If the system time and time zone displayed in the display clock command output are inconsistent with the
local time and time zone, follow the procedure below to reconfigure the system time:

1. Run the clock datetime HH:MM:SS YYYY-MM-DD command in the user view to set the current date
and Universal Time Coordinated (UTC).

2. Run the clock timezone time-zone-name { add | minus } offset command in the system view or user
view to set the local time zone based on an offset. (The NE40E obtains the current system time by

2022-07-08 24
Commissioning Guide

subtracting an offset from or adding an offset to the UTC.)

3. (Optional) Run the clock daylight-saving-time time-zone-name repeating start-time { { first | second
| third | fourth | last } weekday month | start-date } end-time { { first | second | third | fourth | last }
weekday month | end-date } offset [ start-year [ end-year ] ] command in the system view to set the
daylight saving time.

4.7 Checking the Fan Status

This section describes how to check whether fans function properly. By default, fans work in auto adjusting
mode. When the ambient temperature rises sharply, you can manually set it to full speed mode to protect
the device.

Prerequisites
The NE40E has been logged in to. For more information, see Logging In to the NE40E.

Procedure
1. Run the display fan command to check the fan status.
If fan modules are properly installed and successfully registered, as shown in the displayed
information, go on with the subsequent commissioning.

Commissioning Result
The displayed information may be different in real-world situations. For more information, see display fan.

4.8 Checking the Interface Status

You need to check whether interfaces are in the normal state.

Prerequisites
Logging In to the NE40E is complete.

Procedure
1. Run the display interface brief [ main ] command to view brief information about all interfaces on
the NE40E. The information includes the physical status, protocol status, latest bandwidth usage in the
inbound or outbound direction, and number of received or transmitted incorrect packets.
Ensure that the physical status and protocol status are Up.

Troubleshooting
If the physical status is Down, perform the following operations:
2022-07-08 25
Commissioning Guide

1. Run the display this command on both the local and remote interfaces to check whether they have
been shut down. If either one of them or both of them have been shut down, run the undo shutdown
command in the interface view. After that, run the display this interface command to check whether
the interfaces have gone Up.

2. At this step, Ethernet interfaces and non-Ethernet interfaces are handled differently.

• If Ethernet interfaces are used for connection, check that the rate and duplex mode have been
configured on the peer device. Then, set the same rate and duplex mode on the local interface as
that on the peer device. After that, run the display this interface command to check whether the
interface status is Up.
The available commands are as follows:

■ Run the duplex { full | half | auto } command to configure the half-duplex mode on an
Ethernet interface.

■ Run the speed { 100 | 1000 | auto } command to configure the rate on an Ethernet interface.

• If non-Ethernet interfaces are used for connection, skip this step.

3. At this step, optical interfaces and electrical interfaces are handled differently.

• If optical interfaces are used for connection, check whether the optical modules on the interfaces
of the local and peer ends are matched in terms of wavelengths, optical power, and other
elements. If they are not matched, replace optical modules. Then, run the display this interface
command to check whether the interface status is Up.

For details on how to check optical power of optical interfaces, see Checking the Optical Power of
Interfaces.

• If electrical interfaces are used for connection, skip this step.

4. Replace the network cable or fiber, and then run the display this interface command to check whether
the interface status is Up.

5. Contact Huawei technical support personnel.

4.9 Checking Alarm Information

You need to check whether faults have occurred and important alarm information have been generated on
the NE40E.

Prerequisites
Logging In to the NE40E is complete.

2022-07-08 26
Commissioning Guide

Procedure
1. Run the display alarm all command to view all active hardware alarms on the NE40E to determine if
faults have occurred on the NE40E.
<HUAWEI> display alarm all
Info: NO alarm!

If the preceding information is displayed, the hardware is not faulty. Otherwise, locate and rectify any
found fault based on the contents of the Info field in the command output.

2. Run the display trapbuffer [ size buffersize ] command to view information about trap messages in
the trap buffer on the NE40E.
<HUAWEI> display trapbuffer
Trapping buffer configuration and contents : enabled
Allowed max buffer size : 1024
Actual buffer size : 512
Dropped messages : 0
Overwritten messages :
Current messages : 187
May 1 2011 19:20:32 HUAWEI %%01STANDARD/6/linkup:CID=0x807a271c-OID=1.3.6.
1.6.3.1.1.5.4;The interface status changes. (ifName=Ethernet 1/0/1, AdminStatus=U
P, OperStatus=UP, Reason=Interface physical link is Up.)

The part displayed in boldface in the preceding information indicates the alarm severity. Note down
the alarms and immediately handle the alarms whose alarm severities are 3 or higher.

3. Run the display alarm statistics [ name alarm-name ] command to check alarm statistics.
<HUAWEI> display alarm statistics

Alarm Statistic
----------------------------------------------------------------------------
AlarmName : IsisAdjacencyChange
Active : 0
All :1

AlarmName : linkDown
Active : 0
All : 142

If an alarm name is specified in the command, the command will display statistics about the specified
alarm only. Displayed alarm statistics will inform you of the number of alarm generations and help
you evaluate the NE40E operating status and service quality.

4.10 Checking the Voltage of Each Board

You need to check the voltage of each board.

Prerequisites
Logging In to the NE40E is complete.

2022-07-08 27
Commissioning Guide

Procedure
1. Run the display voltagecommand to view the status of the voltage sensor on each board.
The Require field indicates the ideal voltage. The Vlt field indicates the current voltage. The MajorL
field indicates the threshold of a low voltage for a minor alarm. If the voltage is below this threshold,
a minor alarm will be generated. The FatalL field indicates the threshold of a low voltage for a critical
alarm. If the voltage is below this threshold, the NE40E may work abnormally or be damaged. The
MajorH field indicates the threshold of a high voltage for a minor alarm. If the voltage is higher than
this threshold, a minor alarm will be generated. The FatalH field indicates the threshold of a high
voltage for a critical alarm. If the voltage is higher than this threshold, the NE40E may work
abnormally or be damaged.
If the value of the Vlt field is between the value of the MajorL field and the value of the MajorH field,
the board voltage is normal. Then, go on with the subsequent commissioning.

Troubleshooting
If the board voltage is below the lower voltage threshold, perform the following operations:

1. Check that the voltage of power supply is sufficient.

2. Replace the board and check that the board voltage increases above the lower voltage threshold.

3. If the fault persists after the preceding operations are complete, contact Huawei technical support
personnel.

If the board voltage is higher than the upper voltage threshold, perform the following operations:

1. Replace the board and check that the board voltage drops below the upper voltage threshold.

2. If the fault persists after the preceding operations are complete, contact Huawei technical support
personnel.

4.11 Checking the Temperature of Each Board

You need to check the temperature of each board.

Prerequisites
Logging In to the NE40E is complete.

Procedure
1. Run the display temperature command to view the temperature status on each board.

2022-07-08 28
Commissioning Guide

To check the temperature of boards on CCCs and CLCs in a cluster system, run the display temperature [ chassis
chassis-id | mpu | lpu | sfu | icu | slot slot-id ] command.

The Temp(C) field indicates the current temperature. The Minor field indicates the threshold of a high
temperature for a minor alarm. The Major field indicates the threshold of a high temperature for a
major alarm. The Fatal field indicates the threshold of a high temperature for a critical alarm. If the
board temperature reaches or exceeds the value of the Fatal field, the NE40E may work abnormally or
be damaged.
If the value of the Temp(C) field is lower than that of the Minor field, the board temperature is
normal. Then, go on with the subsequent commissioning.

Troubleshooting
If the board temperature exceeds the threshold, perform the following operations:

1. Check whether fans are faulty and replace any faulty fans.

2. Check whether the ambient temperature is too high. If the ambient temperature is too high, lower the
temperature in the equipment room.

3. If the board temperature is still high after the preceding operations, it is due to the high component
temperature. In this case, contact Huawei technical support personnel.

2022-07-08 29
Commissioning Guide

5 Commissioning the Link Layer

This section describes how to commission the link layer when the NE40E is connected to other routers or
transport devices.

5.1 Checking Ethernet Interfaces

This section describes how to check the link layer on Ethernet interfaces.

Prerequisites
Checking the Hardware is complete and the NE40E works properly.

Procedure
1. Run the display interface brief command to view brief information about Ethernet interfaces, including
the physical status, link layer protocol status, bandwidth usage in the inbound and outbound
directions, and statistics about incorrect packets.
This command can quickly display the physical status and link layer protocol status of all Ethernet
interfaces on the NE40E.

2. Run the display interface command to view the physical status, auto-negotiation mode, MTU, IP
address, mask, rate, and operation mode of an Ethernet interface. For example:
In normal situations, the physical status and protocol status of an interface are up, and the link status
on the local end are the same as that on the peer end.

3. Run the ping command to test Ethernet link connectivity. For example:
In normal situations, the ping operation should succeed.

Troubleshooting
• If the physical status of an Ethernet interface is Down after the interface is configured, perform the
following operations:

1. Check that the peer device is started. If the peer device is not started, start it.

2. Run the display interface interface-type interface-number command to view optical module
information and interface configurations on the local and peer ends.

• Check that the optical modules on the local and peer interfaces are matched and the fiber
connected the optical modules and the power of connected optical modules meet the
requirement. If the fiber or either of the optical modules does not meet the requirement,
replace it.

• Check that the auto-negotiation modes on the local and peer interfaces are consistent. If
they are inconsistent, run the duplex command or negotiation auto command to make the
two interfaces use the same duplex mode.

2022-07-08 30
Commissioning Guide

• Check that the interface configurations such as the MTU, TTL of packets, format of
transmitted Ethernet frames, and maximum QoS bandwidth on the local and peer ends are
consistent. If they are inconsistent, adjust them to ensure consistency.

• Check that the traffic is normal.

3. Check that the fiber is properly and correctly installed. This means that the fiber is connected to
the correct transmit optical module and receive optical module.

4. Run the loopback command to check that the fiber between the local and peer ends is not
damaged.
If the physical layer on the local interface is Up after the loopback local command is run, the
local interface is normal. If the peer interface is also configured with loopback local and the
physical layer on the peer interface is Up, the peer interface is normal but the fiber does not work
properly. In this case, replace the fiber.

5. If the fault persists after the preceding operations are complete, contact Huawei technical support
personnel.

• If an Ethernet interface cannot be pinged, perform the following operations:

1. Check that the local end is correctly connected to the peer end. Observe the Link indicator on the
interface board where the local Ethernet interface resides. If the indicator is on, the link works
properly. If the indicator is off, check the optical module, interface, fiber, and the device.

2. Check that the auto-negotiation modes on the local and peer Ethernet interfaces are consistent.

3. Check that the IP address of the local Ethernet interface belongs to the same subnet as that of
the peer Ethernet interface. This means that the two IP addresses must have the same network
address and different host addresses. If the two IP addresses do not belong to the same subnet,
reconfiguration the IP addresses.

4. Check that the link layer protocols on the local and peer ends are consistent. Reliable
communication between two Ethernet devices is available only when they use the same link layer
protocol.

5. If the fault persists after the preceding operations are complete, contact Huawei technical support
personnel.

5.2 Checking WDM Interfaces

This section describes how to check the link layer on WDM interfaces.

Prerequisites
The Checking the Hardware is complete, and the NE40E works properly.

2022-07-08 31
Commissioning Guide

Procedure
1. Run the display this interface command to view information about the optical module, alarm, error
counters, and TTIs on the WDM interface.
Under normal conditions, parameters (such as FEC, TTI) of WDM interfaces on the two ends of the
NE40E are the same; there are no link alarms or errors.

2. Run the ping command to test the connectivity of WDM link.

In normal conditions, the ping operation should succeed.

Common Troubleshooting
The WDM interface is composed of a controller WDM interface and an Ethernet interface. If the physical
layer of the Ethernet interface cannot go Up, perform the following steps:

1. Check whether parameters (such as FEC, TTI) of WDM interfaces on two ends of the NE40E are the
same. If not, adjust configurations of WDM interfaces on two ends of the NE40E.

2. Check the Ethernet interface according to "Common Troubleshooting" in Checking Ethernet Interfaces.

3. If the fault persists, contact Huawei technical support personnel.

5.3 Checking E-Carrier Interfaces

This section describes how to check the link layer on E-Carrier and T-Carrier interfaces. In this section, a CE1
interface is used as an example.

Prerequisites
• Hardware installation is complete. For more information, see Checking the Hardware.

• The NE40E is running properly.

Procedure
1. Run the display controller e1 command to check the status of a CE1 interface. For example:
The CE1 interface status is UP when the CE1 interface is correctly configured, and no alarms or errors
are displayed.

Troubleshooting
If E-carrier interfaces on both ends of a link cannot communicate with each other after the interfaces are
configured, perform the following operations:

1. Check that the physical layer is Up.

2022-07-08 32
Commissioning Guide

a. Run the display controller e1 command to view interface information on each end.
If the physical status is displayed as Administratively Down, the shutdown command has been
run on the interface. Run the undo shutdown command to enable the interface.

If the physical status is displayed as Down, check the following items:

• Fiber is properly connected to the local interface and the indicator for the interface is in a
normal state.

• Fiber is properly connected to the peer interface. Run the display this interface command in
the interface view to check if the physical status of the peer interface is Administratively
Down and if loopback is configured on the peer interface.

• Interface configurations, such as the operation mode and line coding/decoding format, on
the two ends are consistent, and the clock modes configured on the two ends are correct.

b. If the fault persists, run the loopback command in the CE1 interface view.
If the physical status of the interface is Up, the hardware on the local end works properly. The
problem lies in the cable, and you need to replace the cable. If the physical status of the
interface is Down, the board where the interface resides is faulty. The board needs to be
repaired.

2. If the interfaces on the two ends of the link still cannot communicate with each other even if all
configurations are correct, view statistics on the interfaces and contact Huawei technical support
personnel.

5.4 Commissioning TDM Interfaces

This section describes how to commission TDM interfaces.

Prerequisites
Checking the Hardware has been completed, the Router device to be commissioned is running properly, the
E1 cables on the AC sides for carrying TDM services are correctly connected, and network-side cables are
connected correctly.

Context
As shown in Figure 1, a static routing protocol has to be deployed in the network to ensure normal
communication between the DeviceA device and the network segment 172.16.1.0 where the DeviceB is
located.

2022-07-08 33
Commissioning Guide

Figure 1 Typical networking diagram for TDM interface commissioning

Procedure
1. Configure a TDM serial interface and specify the protocol of the interface as TDM. The following uses
serial interface 0/2/0:1 as an example to describe how to configure a TDM serial interface.

2. Configure a TDM PWE3 service for the serial interface.

For the detailed procedure, see the guides to configure TDM services for Router devices. Then run the
display this command on the Router device to view the configurations of the serial interface.
[HUAWEI-Serial0/2/0:1] display this
#
interface Serial0/2/0:1
link-protocol tdm
mpls l2vc 2.2.2.2 pw-template 1 101
#
return

On the device, use the same way to configure a TDM PWE3 service for the serial interface. Ensure that
the PW profile parameters of the device are same.

3. On the Router device, run the display mpls l2vc command to check the status of the TDM PW.
As shown in the command output, the interface configurations and cable connections are correct, no
alarms are reported for the interface, and the PW is up. In addition, after a test instrument feeds a
service to the Router device, the service is transmitted properly.

Handling Common Faults

The PW profile parameters of the Router device are inconsistent.

1. Handling procedure:

a. Run the display pw-template command on the Router device to check whether the PW profile
parameters are consistent. If they are inconsistent, make changes properly to make them
consistent.

2022-07-08 34
Commissioning Guide

The AC-side interfaces that carry TDM services are not up. These interfaces include the E1 and serial
interfaces.

1. Handling procedure 1:

a. In the E1 interface view, run the display this interface command to check whether the physical
state of the interface is up. If the state is not up, handle the fault of the E1 interface being
down.

b. In the serial interface view, run the display this interface command to check whether the serial
interface has been shut down. If the serial interface has been shut down, run the undoshut
serial command to turn on the interface.

c. In the serial interface view, run the display this command separately on the Router device to
check whether the TDM protocol is used on the two devices. If it is not, correct the setting to
ensure that the two devices use the TDM protocol.
[HUAWEI-Serial0/2/0:1] display this
#
interface Serial0/2/0:1
link-protocol tdm
mpls l2vc 2.2.2.2 pw-template 1 101
#
return

For the E1 interfaces on the Router device, the channelized mode or the number of bound timeslots
differs.

1. Handling procedure:

a. In the E1 interface view, run the display this command on the Router device to view the
channelized mode and number of bound timeslots configured for the E1 interfaces. If the
configurations are inconsistent, correct them.
[HUAWEI-E1 0/2/0] display this
#
controller E1 0/2/0
channel-set 1 timeslot-list 1-31
undo shutdown
#
return
An example is as follows:
[PPP_980B-E1 0/2/1]display this
#
controller E1 0/2/1
using e1
undo shutdown
#
return

The PW or tunnel that carries the TDM service is down.

1. Handling procedure: On the Router device, run the display mpls l2vc command to check the PW
status of the port where the service is interrupted.

2022-07-08 35
Commissioning Guide

a. If the AC status is displayed as down in the command output, see the fault handling procedure
for cause 3. If the session state is displayed as down, handle the fault by referring to the MPLS
fault handling procedure.

b. If the AC status and the session state are displayed as up but the VC is down, check whether the
VC ID, VC type, and control word of the Router device are same.

c. If they are inconsistent, make changes properly to make them consistent. If they are consistent
but the VC is down, handle the fault by referring to the tunnel fault handling procedure.

2. Handling procedure 2:

a. Check whether the QoS is configured for the network interface. If QoS is configured, handle the
fault by referring to the QoS fault handling procedure.

b. If the physical state of the TDM link is displayed as *down, then the serial interface has been
shut down manually. Enter the serial interface view and run the undo shutdown command.

c. If the physical state of the TDM link is displayed as down, then the E1 line is faulty. Handle the
fault by referring to the E1 fault handling procedure.

The bandwidth allocated to the TDM service on the NNI side is insufficient, or the service packets of a
higher priority occupied the bandwidth allocated to the TDM service.

1. Handling procedure:

a. Check whether the QoS is configured for the network interface. If QoS is configured, handle the
fault by referring to the QoS fault handling procedure.

b. Check whether the bandwidth on the NNI side is sufficient for transmitting the TDM service. For
example, if n timeslots have been configured for the TDM service, calculate the bandwidth
required by one TDM service using the following formula: TDM service bandwidth = n x 8 x
8000/8 + Length of the Ethernet packet header.

5.5 Checking the Optical Power of Interfaces

You need to check whether the optical power of SFP optical modules meets requirements. If the output
optical power of SFP optical modules on the boards of the NE40E does not meet requirements, packets will
be lost and communication will be interrupted on the network layer.

Prerequisites
Checking the Hardware is complete and the NE40E works properly.

Procedure
1. Run the display interface interface-type interface-number command to view the operating status of
and statistics on each of two connected interfaces. Go on with the subsequent commissioning if the

2022-07-08 36
Commissioning Guide

maximum transmission distance and central wavelength of the optical modules on the two connected
interfaces are consistent and the input optical power and output optical power of the optical modules
are within the allowed range. In the following example, the display on a GE interface is used.

The display this interface command can also be run in the interface view to display interface information. The
output of the display interface command and that of the display this interface command are the same.

Check the information and ensure that the interface bandwidth, fiber mode, maximum transmission
distance, and central wavelength of the optical module on the GE interface are the same as that of its
connected optical module on the peer end. Check the output optical power of optical modules on the
two ends against the "Hardware Description-Optical Module" to determine if the output optical power
is within the allowed range.

During engineering commissioning, a common optical power meter can measure only the total average optical
power. To measure the optical power of a single channel, a professional instrument is required. The following
formula provides a method for inexact conversion between the total average optical power Pt and the single-
channel average optical power Ps, which helps simplify commissioning.
Ps = Pt – 10lgn, where n indicates the number of channels, Pt indicates the total average optical power, and Ps
indicates the average optical power of a single channel, in dBm.
For example, if the total average optical power of four channels is 10 dBm, the average optical power of a single
channel is calculated as follows: Ps = 10 – 10lg4 ≈ 4 dBm.

The output optical power of the local optical module must meet the following requirements:
• The minimum output optical power must be higher than the receiver sensitivity of the optical module.
Otherwise, the peer end cannot receive signals.
• The maximum output optical power must be lower than the overload power of the optical module.
Otherwise, the optical module may be damaged.

Troubleshooting
If the optical power of an optical module is beyond the allowed range, use the optical power meter to check
whether the receiving and sending optical signals at both ends are normal. If it is not convenient to use the
optical power meter, you can use the optical power detecting function in the optical module: run display this
interface in the error interface and compare the parameters in the display information with the optical
module parameters, and check whether the power of the send or receive optical signals are in normal range.
If optical interfaces only send or receive optical signals, the optical module is possibly faulty or the optical
fiber does not match the optical module. Then, you can try to replace the optical module or the optical fiber.

2022-07-08 37