Commissioning Guide (V600R001C00 - 03) PDF

HUAWEI NetEngine80E/40E Router
V600R001C00
Commissioning Guide
Issue
03
Date
2010-03-31
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2010. 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 the 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:
http://www.huawei.com
Email:
support@huawei.com
Issue 03 (2010-03-31)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

Commissioning Guide
About This Document
About This Document

Overview
This document describes the basic procedure for and the method of commissioning devices in
deployment in terms of hardware, software, connections, services, and maintenance and
management. This document serves as a guide to the stable and reliable running of devices on
a network.
This document provides the procedure for and the method of commissioning an NE80E/40E
device.
Product Version
The following table lists the product version involved in this document.
Product Name
Product Version
HUAWEI NetEngine80E/40E
V600R001C00
Intended Audience
This document is intended for:
l
Installation and commissioning engineers
Organization
This document is organized as follows.
Issue 03 (2010-03-31)
Chapter
Description
1 Commissioning Flow
Describes the definition of and procedures for

commissioning.
2 Preparations for
Commissioning
Describes preparations for commissioning.

iii

Commissioning Guide
About This Document
Chapter
Description
3 Basic Commissioning
Describes the stand-alone commissioning.
A Appendix
Describes the used commands.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
DANGER
WARNING
CAUTION
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 or low level of risk which, if
not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not avoided,
could cause device damage, data loss, and performance
degradation, or unexpected results.
TIP
Indicates a tip that may help you solve a problem or save your
time.
NOTE
Provides additional information to emphasize or supplement

important points of the main text.
General Conventions
iv
Format
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in Boldface.
Italic
Book titles are in italics.
Courier New
Terminal display is in Courier New.

Issue 03 (2010-03-31)

Commissioning Guide
About This Document
Command Conventions
Format
Description
Boldface
The keywords of a command line are in boldface.
Italic
The arguments of a command line are in italic.
[]
Items (keywords or arguments) in square brackets [ ] are optional.
{ x | y | ... }
Alternative items are grouped in braces and separated by vertical

bars. One is selected.
[ x | y | ... ]
Optional alternative items are grouped in square brackets and

separated by vertical bars. One or none is selected.
{ x | y | ... } *
Alternative items are grouped in braces and separated by vertical

bars. A minimum of one or a maximum of all can be selected.
[ x | y | ... ] *
Optional alternative items are grouped in square brackets and

separated by vertical bars. Many or none can be selected.
&<1-n>
This parameter before the & sign can be repeated 1 to n times.
A line starting with the # sign is comments.
GUI Conventions
Format
Description
boldface
Buttons, menus, parameters, tabs, windows, and dialog titles are

in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">" signs.

For example, choose File > Create > Folder.
Keyboard Operation
Issue 03 (2010-03-31)
Format
Description
Key
Press the key. For example, press Enter, Tab, Backspace, and
a.
Key 1+Key 2
Press the keys concurrently. For example, press Ctrl+Alt+A.
Key 1, Key 2
Press the keys in turn. For example, press Alt and F in turn.


Commissioning Guide
About This Document
Mouse Operations
Format
Description
Click
Select and release the primary mouse button without moving the
pointer.
Double-click
Press the primary mouse button twice continuously and quickly

without moving the pointer.
Drag
Press and hold the primary mouse button and move the pointer
to a certain position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 03 (2010-03-31)

This is the third release.

This is the second release.

This is the first release.
vi

Issue 03 (2010-03-31)

Commissioning Guide
Contents
Contents
About This Document...................................................................................................................iii
1 Commissioning Flow.................................................................................................................1-1
2 Preparations for Commissioning............................................................................................2-1
2.1 Hardware Preparation......................................................................................................................................2-2
2.2 Software Preparation.......................................................................................................................................2-2
2.3 Tool Preparation..............................................................................................................................................2-3
2.4 Data Preparation..............................................................................................................................................2-4
3 Basic Commissioning................................................................................................................3-1
3.1 Logging in to a Device Through the Console Interface..................................................................................3-2
3.2 Checking a Device..........................................................................................................................................3-4
3.2.1 Checking Software Versions..................................................................................................................3-5
3.2.2 Checking the Health Status of a Device.................................................................................................3-6
3.2.3 Checking License Files..........................................................................................................................3-6
3.2.4 Checking the Status of Boards...............................................................................................................3-7
3.2.5 Checking the Status of the FAN.............................................................................................................3-8
3.2.6 Checking the Status of the Power..........................................................................................................3-9
3.3 (Optional) Specifying a Device Name............................................................................................................3-9
3.4 Setting System Time.....................................................................................................................................3-10
3.5 Configuring a Management User to Remotely Log in to a Device...............................................................3-12
3.5.1 Configuring a User to Log in to a Device Through Telnet..................................................................3-12
3.5.2 (Operational) Configuring ACLs to Filter Login Users.......................................................................3-14
3.5.3 (Optional) Configuring a User to Log in to a Device Through FTP....................................................3-16
3.5.4 (Optional) Configuring a User to Log in to a Device Through SSH...................................................3-18
3.6 Commissioning the Link Layer.....................................................................................................................3-21
3.6.1 Commissioning the Link Layer of an Ethernet Interface.....................................................................3-22
3.6.1.1 Commissioning the Link Layer of an Ethernet Interface on an LPU................................................3-22
3.6.1.2 Commissioning the Link Layer of an Ethernet Interface on an MPU...............................................3-26
3.6.1.3 Configuring Layer 2 Parameters for an Ethernet Interface...............................................................3-27
3.6.2 Commissioning the Link Layer of a POS Interface.............................................................................3-27
3.6.3 Commissioning the Link Layer of a CPOS Interface..........................................................................3-31
3.6.3.1 Configuring an STM-1 CPOS Interface............................................................................................3-31
3.6.3.2 Configuring the E1 Channel of a CPOS Interface............................................................................3-33
Issue 03 (2010-03-31)

vii

Commissioning Guide
Contents
3.6.3.3 Configuring the T1 Channel of a CPOS Interface............................................................................3-35

3.6.3.4 Configuring the E3 Channel of an STM-1 CPOS Interface..............................................................3-37
3.6.3.5 Configuring the T3 Channel of an STM-1 CPOS Interface..............................................................3-39
3.6.4 Commissioning the Link Layer of the E1/T1 Interface.......................................................................3-41
3.6.5 Commissioning the Link Layer of an ATM Interface..........................................................................3-42
3.6.6 Commissioning the Link Layer of a User Interface on an FR Network..............................................3-44
3.6.7 Commissioning the Power of an Optical Interface..............................................................................3-46
3.7 Commissioning the Network Layer..............................................................................................................3-47
3.7.1 Introduction to Commissioning the Network Layer............................................................................3-48
3.7.2 Assigning an IP Address to an Interface..............................................................................................3-50
3.7.3 Configuring a Static Route...................................................................................................................3-54
3.7.4 Configuring OSPF................................................................................................................................3-56
3.7.5 Configuring IS-IS.................................................................................................................................3-58
3.7.6 Configuring BGP..................................................................................................................................3-60
3.7.7 Connecting a Device to the NMS.........................................................................................................3-62
3.8 Saving Configurations...................................................................................................................................3-64
A Appendix...................................................................................................................................A-1
A.1 clock (ATM interface view)..........................................................................................................................A-3
A.2 clock (CPOS interface view).........................................................................................................................A-4
A.3 clock (POS interface view)............................................................................................................................A-4
A.4 crc (POS interface view)...............................................................................................................................A-5
A.5 display power.................................................................................................................................................A-6
A.6 e1 channel-set (CPOS interface view)...........................................................................................................A-7
A.7 e1 set clock (CPOS interface view).............................................................................................................A-10
A.8 e1 set frame-format (CPOS interface view)................................................................................................A-11
A.9 e1 unframed (CPOS interface view)............................................................................................................A-12
A.10 e3 set clock (CPOS interface view)...........................................................................................................A-13
A.11 flag (atm interface view)............................................................................................................................A-14
A.12 flag (cpos interface view)..........................................................................................................................A-15
A.13 flag (pos interface view)............................................................................................................................A-16
A.14 fr dlci.........................................................................................................................................................A-17
A.15 fr interface-type.........................................................................................................................................A-18
A.16 frame-format (ATM OC/STM).................................................................................................................A-19
A.17 frame-format (CPOS interface view)........................................................................................................A-20
A.18 frame-format (POS interface view)...........................................................................................................A-21
A.19 link-protocol fr...........................................................................................................................................A-21
A.20 link-protocol (POS interface view)...........................................................................................................A-22
A.21 ppp authentication-mode...........................................................................................................................A-23
A.22 rule (ACL view)........................................................................................................................................A-24
A.23 scramble (ATM interface view)................................................................................................................A-30
A.24 scramble (POS interface view)..................................................................................................................A-31
A.25 snmp-agent community.............................................................................................................................A-32
viii

Issue 03 (2010-03-31)

Commissioning Guide
Contents
A.26 snmp-agent target-host trap.......................................................................................................................A-33

A.27 snmp-agent trap enable..............................................................................................................................A-34
A.28 snmp-agent usm-user.................................................................................................................................A-35
A.29 t1 set clock (CPOS interface view)...........................................................................................................A-36
A.30 t1 set frame-format (CPOS interface view)...............................................................................................A-37
A.31 t3 set clock (CPOS interface view)...........................................................................................................A-38
Issue 03 (2010-03-31)

ix

Commissioning Guide
Figures
Figures
Figure 1-1 Commissioning flow...........................................................................................................................1-2
Figure 3-1 Networking diagram of logging in to the NE80E/40E through the console interface........................3-2
Figure 3-2 Setting up a connection.......................................................................................................................3-3
Figure 3-3 Setting a connection port....................................................................................................................3-3
Figure 3-4 Setting communication parameters.....................................................................................................3-4
Figure 3-5 Networking diagram in out-band management mode......................................................................3-48
Figure 3-6 Networking diagram in in-band management mode (a Layer 3 interface accessing the NMS).......3-49
Figure 3-7 Networking diagram in in-band management mode (a Layer 2 interface accessing the NMS).......3-49
Figure 3-8 Networking for applying out-band NMS..........................................................................................3-55
Figure 3-9 Networking diagram of configuring OSPF......................................................................................3-56
Figure 3-10 Networking diagram of configuring IS-IS......................................................................................3-58
Figure 3-11 Networking for applying in-band NMS..........................................................................................3-61
Issue 03 (2010-03-31)

xi

Commissioning Guide
Tables
Tables
Table 1-1 Introduction to the procedures involved in the commissioning flow...................................................1-2
Table 2-1 Hardware checklist...............................................................................................................................2-2
Table 2-2 Software checklist................................................................................................................................2-3
Table 2-3 Tool checklist.......................................................................................................................................2-3
Table 2-4 Data checklist.......................................................................................................................................2-4
Table 3-1 Data planning.....................................................................................................................................3-10
Table 3-2 Data planning.....................................................................................................................................3-10
Table 3-3 Data preparation.................................................................................................................................3-12
Table 3-5 ACL classification..............................................................................................................................3-15
Table 3-8 Data Preparation.................................................................................................................................3-51
Table A-1 Description of the display power command output..........................................................................A-7
Table A-2 Description of the display interface serial command output...........................................................A-9
Table A-3 Relationship between icmp-name, icmp-type and icmp-code..........................................................A-28
Issue 03 (2010-03-31)

xiii

Commissioning Guide
Commissioning Flow
This chapter describes the basic flow of commissioning the NE80E/40E. Users can thus know
the entire process of device commissioning in site deployment.
You can follow the procedure to complete the commissioning. This document only describes
the preparations for commissioning and the basic commissioning of NE80E/40E.
Issue 03 (2010-03-31)

1-1

Commissioning Guide
Figure 1-1 Commissioning flow

Preparations for the
commissioning
Hardware
preparation
Software preparation
Typical service
commissioning
Basic commissioning
Log in to a device
through a console
interface
Check the device
Tool preparation
Specify a device
name
Data preparation
Configure system
time
Configure a user to
log in to a device
remotely
Commissioning the
Link Layer
Commissioning the
Network Layer
Connect a device to
the NMS
Save configurations
Table 1-1 Introduction to the procedures involved in the commissioning flow
1-2
Commissioning Procedure
Description
Preparations for Commissioning
To ensure that the subsequent commissioning

works well, preparations must be made in
terms of the hardware, software, tools, and
data.
Basic Commissioning
It describes how to commission a single

NE80E/40E after hardware installation is
completed so that the NE80E/40E can work
normally and users can remotely log in to the
NE80E/40E.

Issue 03 (2010-03-31)

Commissioning Guide
Issue 03 (2010-03-31)
Commissioning Procedure
Description
Typical service commissioning
Before typical service commissioning,

configuration scripts must be finished. The
configuration scripts are written based on the
actual networking plan and typical
configuration examples.

1-3

Commissioning Guide
2 Preparations for Commissioning
Preparations for Commissioning
About This Chapter

2.1 Hardware Preparation
Before commissioning, you need to check the power supply and grounding, cables and
connectors, and downstream devices to make sure that all the hardware is ready for
commissioning.
2.2 Software Preparation
This chapter describes the software to be prepared before commissioning.
2.3 Tool Preparation
This chapter describes the tools to be prepared before commissioning.
2.4 Data Preparation
Information about hardware configurations, network topologies, and data planning needs to be
collected to prepare for data configurations.
Issue 03 (2010-03-31)

2-1

Commissioning Guide
2.1 Hardware Preparation

Before commissioning, you need to check the power supply and grounding, cables and
connectors, and downstream devices to make sure that all the hardware is ready for
commissioning.
Table 2-1 shows the hardware checklist before commissioning.
Table 2-1 Hardware checklist
Item
Description
Power supply and grounding
Power cables and grounding cables are connected

properly and are in good contact.
Power cables, grounding cables, and power distribution

switches are labeled correctly, clearly, and orderly.
The external grounding cable of the cabinet and

protection grounding cables are connected properly,
without any damage or break.
Power supply for the device is normal.
Cables and connectors
Downstream devices
Check the console cables, network cables, optical fibers,

and subscriber lines to ensure the following:
l
Cable connectors are tight and firm.
Cable jackets are intact.
Confirm the physical position of the connected interface

on the peer device.
The peer device works normally and can be used for

commissioning.
NOTE
The hardware installation engineers have already checked Item 1 and Item 2 listed in Table 2-1. To ensure
the proper and reliable connection of the hardware, you can recheck the preceding items.
2.2 Software Preparation

This chapter describes the software to be prepared before commissioning.
You should prepare related software in advance to facilitate the subsequent commissioning.
Table 2-2 shows the software checklist.
2-2

Issue 03 (2010-03-31)

Commissioning Guide
Table 2-2 Software checklist

Item
Description
System software
package
The system software package contains correct system software,

license files and paf files.
GTL License
A user that purchases a new device needs to apply for and purchase
a GTL license to obtain authorization of related service modules.
Software
commissioning tools
All the software commissioning tools are available. The

commissioning tools are listed as follows:
l
HyperTerminal: used for logging in to the NE80E/40E through

the console interface. This tool is embedded in the Windows
Operating System (OS).
Trivial File Transfer Protocol (TFTP) and File Transfer Protocol

(FTP): used for loading software to the NE80E/40E. The tools can
be downloaded from http://support.huawei.com.
2.3 Tool Preparation

This chapter describes the tools to be prepared before commissioning.
Commissioning is performed with the help of tools. Therefore, you need to prepare related tools
in advance to facilitate the subsequent commissioning.
Table 2-3 shows the tool checklist.
Table 2-3 Tool checklist
Issue 03 (2010-03-31)
Item
Description
Cables and interfaces
Check that cables connecting devices are complete and correct, and
interface types are consistent with cable types according to network
deployment.
l
One RS232 serial interface cable: used for logging in to the

NE80E/40E through the console interface.
One network cable: used for commissioning the Management

Ethernet (MEth) interfaces or other services.
Several optical fibers: used for connecting the peer device.
Maintenance terminal
A maintenance terminal, generally a laptop, with a HyperTerminal

application. It is used for logging in to the NE80E/40E to
commission the NE80E/40E.
Auxiliary device and

meter
Optical power meter: used for checking the actual input power,
receiver sensibility, and overload optical power of optical
interfaces.
Multimeter: used for measuring the voltage, resistance, and

current amperage during power commissioning.

2-3

Commissioning Guide
2.4 Data Preparation

Information about hardware configurations, network topologies, and data planning needs to be
collected to prepare for data configurations.
Table 2-4 lists the data that needs to be collected.
Table 2-4 Data checklist
2-4
Item
Description
Hardware configuration
It indicates all the required boards and their slot numbers.
Networking and data planning
It includes but is not limited to the following items:

l
Networking mode
IP address allocation
VLAN division
Service type and data planning

Issue 03 (2010-03-31)

Commissioning Guide
Basic Commissioning
About This Chapter

3.1 Logging in to a Device Through the Console Interface
When setting up a local configuration environment through the console interface, you can log
in to the NE80E/40E through the HyperTerminal in Windows on the PC.
3.2 Checking a Device
You can check a device to make sure that the current status meets the deployment requirement.
3.3 (Optional) Specifying a Device Name
Specifying a device name according to the networking plan helps to identify and maintain a
device.
3.4 Setting System Time
Setting system time accurately ensures that the NE80E/40E works with other devices
coordinately.
3.5 Configuring a Management User to Remotely Log in to a Device
This section describes how to configure a management user to remotely log in to a device.
Through remote login, the management user can log in to a device to deploy services from the
central equipment room.
3.6 Commissioning the Link Layer
This section describes how to commission the link layer of the Router that connects to other
routers or transmission devices.
3.7 Commissioning the Network Layer
You can adopt the out-band management mode or in-band management mode according to the
network planning.
3.8 Saving Configurations
Issue 03 (2010-03-31)

3-1

Commissioning Guide

When setting up a local configuration environment through the console interface, you can log
in to the NE80E/40E through the HyperTerminal in Windows on the PC.
Prerequisite
Figure 3-1 Networking diagram of logging in to the NE80E/40E through the console interface
PC
Router
Before logging in to the NE80E/40E through the console interface, make sure that the NE80E/
40E is properly powered on.
Procedure
Step 1 Use a serial cable to connect the serial interface on the PC and the console interface on the
NE80E/40E.
For details on the console interface, see HUAWEI NetEngine80E/40E Router - Hardware
Description.
Step 2 Start the HyperTerminal on the PC.
Choose Start > Programs > Accessories > Communications > HyperTerminal to start the
HyperTerminal in Windows.
Step 3 Set up a connection.
As shown in Figure 3-2, enter the name of the new connection in the Name text box, and then
select an icon. Click OK.
3-2

Issue 03 (2010-03-31)

Commissioning Guide
Figure 3-2 Setting up a connection
Step 4 Set a connection port.

In the Connect To dialog box as shown in Figure 3-3, select a port from the drop-down list box
of Connect using according to the port actually used on the PC or terminal. Then, click OK.
Figure 3-3 Setting a connection port
Step 5 Set communication parameters.

When the COM1 Properties dialog box is displayed as shown in Figure 3-4, set the COM1
properties according to the description in Figure 3-4 or by clicking Restore Defaults.
Issue 03 (2010-03-31)

3-3

Commissioning Guide
Figure 3-4 Setting communication parameters
----End
Operation Result
After the preceding configurations are complete, press Enter. If the prompt <HUAWEI> is
displayed on the screen, it indicates that logging in to the NE80E/40E through the console
interface is successful. Then, you can run commands to configure or manage the NE80E/40E.
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
device again.

You can check a device to make sure that the current status meets the deployment requirement.
3.2.1 Checking Software Versions
You need to check whether the software version in use meets the deployment requirement.
3.2.2 Checking the Health Status of a Device
You need to check whether the current status of a device meets the deployment requirement.
3.2.3 Checking License Files
You need to check whether GTL license files are correctly loaded.
3.2.4 Checking the Status of Boards
3-4

Issue 03 (2010-03-31)

Commissioning Guide
You need to check whether all boards are in position and work normally.
3.2.5 Checking the Status of the FAN
You need to check whether the fan works normally.
3.2.6 Checking the Status of the Power
You need to check whether the power works normally.
3.2.1 Checking Software Versions

You need to check whether the software version in use meets the deployment requirement.
Prerequisite
3.1 Logging in to a Device Through the Console Interface is complete.
Procedure
Step 1 Run the display version [ | slot slot-id ] command to view the version information. You can
enter [ | slot slot-id ] to view the command output that is filtered through regular expressions or
the version information of the board in a specified slot.
<HUAWEI> display version
Huawei Versatile Routing Platform Software
VRP (R) software, Version 5.70 (NE40E&80E V600R001C00)
Copyright (C) 2000-2009 Huawei Technologies Co., Ltd.
HUAWEI NetEngine 40E uptime is 0 day, 0 hours, 15 minute
---- More ---Step 2 Run the display startup command to view the system software and configuration files for the
current and next startup.
<HUAWEI> display startup
MainBoard:
Configured startup system software:
Startup system software:
Next startup system software:
Startup saved-configuration file:
Next startup saved-configuration file:
Startup paf file:
Next startup paf file:
Startup license file:
Next startup license file:
Startup patch package:
Next startup patch package:
cfcard:/V600R001C00.cc
cfcard:/vrpcfg.cfg
cfcard:/vrpcfg.cfg
cfcard:/paf-V600R001C00.txt
cfcard:/paf-V600R001C00.txt
cfcard:/license-V600R001C00.txt
cfcard:/license-V600R001C00.txt
cfcard:/patch.bat
cfcard:/patch.bat
----End
Operation Result
l
If the software version meets the deployment requirement, that is, the current version that
is displayed in bold characters in the preceding information on the NE80E/40E is consistent
with the version for deployment, you can go on with the subsequent stand-alone
commissioning.
If the software version does not meet the deployment requirement, it needs to be upgraded.
NOTE
Before upgrading the software version, contact Huawei technical support personnel or visit http://
support.huawei.com to download the reference documents and system software that may be used
during the upgrade, including the Version Upgrade Guide, Release Notes, Patch Operation Guide,
Paf&License Selection Guide, and Version Configuration Table.
Issue 03 (2010-03-31)

3-5

Commissioning Guide
3.2.2 Checking the Health Status of a Device

You need to check whether the current status of a device meets the deployment requirement.
Prerequisite
Context
You can check the following items to see whether a device is normal.
l
CPU usage
Memory usage
Procedure
Step 1 Run the display health command to view the health status of the NE80E/40E.
<HUAWEI> display health
Slot
CPU Usage Memory Usage(Used/Total)
--------------------------------------------------------9 MPU(System Master)
9%
72% 627MB/863MB
2 LPU
8%
32% 130MB/405MB
3 LPU
9%
42% 386MB/917MB
6 LPU
15%
31% 128MB/405MB
----End
Operation Result
In normal situations, CPU or memory usage should be lower than 80%.
If CPU or memory usage remains high before services are deployed on a large scale, contact
Huawei technical support personnel.
3.2.3 Checking License Files

You need to check whether GTL license files are correctly loaded.
Prerequisite
Before checking license files, complete the following tasks: is complete.
l
Applying for a GTL license file
Installing and loading the GTL license file
Context
WARNING
The extension of the GTL license is .dat, which is different from that of the system license file.
3-6

Issue 03 (2010-03-31)

Commissioning Guide
A user that purchases a new device needs to apply for and purchase a GTL license to obtain
authorization of related service modules. After activating the license, the user can apply related
service modules.
When the activated GTL license file expires on a device, the user needs to reapply, upgrade and
activatea new GTL license file. Otherwise, the GTL license file becomes invalid on expiryand
function modules are closed and services are interrupted.
Procedure
Step 1 Run the display license { all | { resource | service } item-name } command to view the license
files of the master and slave Main Processing Units (MPUs).
<HUAWEI> display license
Active License on master board: cfcard:/or6219.dat
Huawei Technologies Co., Ltd.
All rights reserved.
Product name
: NetEngine 80E
Product version
: V600R001C00
License Serial No : LIC20070205001010
Creator
: Huawei Technologies Co., Ltd.
Created Time
: 2007-02-05 02:55:48
Feature name
: CRFEA1
Authorize type : COMM
Expired date
: 2007-04-30
Trial days
: 60
Expired date of software maintenance : 0000-00-00
Expired date of hardware maintenance : 0000-00-00
Expired date of free software update : 0000-00-00
Configure items :
Item name : RPR
value : 1
Item name : IPV6
value : 1
Item name : L3VPN
value : 1
Item name : NETSTREAM
value : 1
Item name : LAYER2
value : 1
----End
Operation Result
l
If GTL license files are all correctly loaded, that is, Authorize type, Expired date, Item
name, and value displayed in the preceding information are consistent with those actually
applied for, you can go on with the subsequent stand-alone commissioning.
If a license file is incorrectly loaded, you need to run the license active filename command
to activate the GTL license file to obtain the corresponding authority.
NOTE
When you activate or upgrade a license file, the new license file must exist on both the master MPU
and slave MPU.
# Activate the license file GTL.dat on the master and slave MPUs.
<HUAWEI> license active GTL.dat
Info: Please wait for a while...
Info: Succeeded in activating the License file on the master board.
3.2.4 Checking the Status of Boards

You need to check whether all boards are in position and work normally.
Prerequisite
Issue 03 (2010-03-31)

3-7

Commissioning Guide
Procedure
Step 1 Run the display device [ pic-status | slot-id ] command to view information about the devices
in position. You can enter [ pic-status | slot-id ] to view information about the Physical Interface
Cards (PICs) on all LPUs and information about a specified slot, including the LPU, MPU, SFU,
clock board, power module, or fan module.
<HUAWEI> display device
NE40E's Device status:
Slot #
Type
Online
Register
Status
Primary
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2
LPU
Present
Registered
Normal
NA
3
LPU
Present
Registered
Normal
NA
6
LPU
Present
Registered
Normal
NA
9
MPU
Present
NA
Normal
Master
11
SFU
Present
Registered
Normal
NA
12
SFU
Present
Registered
Normal
NA
13
SFU
Present
Registered
Normal
NA
15
CLK
Present
Registered
Normal
Master
17
PWR
Present
Registered
Normal
NA
18
PWR
Present
Registered
Abnormal
NA
19
FAN
Present
Registered
Normal
NA
20
FAN
Present
Registered
Normal
NA
21
LCD
Present
Registered
Normal
NA
----End
Operation Result
l
If the status of all boards is displayed as Normal in the preceding information,which

indicates that boards are in position and working normally, you can go on with the
subsequent stand-alone commissioning.
If boards are working abnormally, do as follows:

1.
Run the display alarm all or display trapbuffer command to check whether alarms
of faulty boards are generated.
If so, go to Step 2.
If not, go to Step 3.
2.
Deal with the alarms according to the Alarm Reference.
3.
Contact Huawei technical support personnel.
For example, if you run the display device command and find that the Hub Power Supply Unit
(PWR) in slot 18 is in the Abnormal state, you can run the display trapbuffer command to view
the alarm information.
Refer to the Alarm Reference according to preceding alarm information to locate the fault and
seek solutions.
3.2.5 Checking the Status of the FAN

You need to check whether the fan works normally.
Prerequisite
3-8

Issue 03 (2010-03-31)

Commissioning Guide
Procedure
Step 1 Using the display fan command, you can view the status of FAN.
<HUAWEI> display fan
Slotid
: 19
Present : YES
Registered: YES
Status
: AUTO
FanSpeed : [No.]Speed
[1]30% [2]30%
Slotid
: 20
Present
: YES
Registered: YES
Status
: AUTO
FanSpeed : [No.]Speed
[1]30% [2]30%
----End
Commissioning Results
The status of the fan may be different. For details, please refer to display fan.
3.2.6 Checking the Status of the Power

You need to check whether the power works normally.
Prerequisite
Procedure
Step 1 Using the command display power, you can view the status of the power
<HUAWEI> display power
No Present mode State
Num
------------------------------------------------------------------------------17 Yes
*
Abnormal(failure)
1
18 Yes
AC
Normal
1
Power monitor cable state:
Plug
----End
The status of the power may be different. For details, please refer to display power.
3.3 (Optional) Specifying a Device Name

Specifying a device name according to the networking plan helps to identify and maintain a
device.
Prerequisite
3.2 Checking a Device is complete and the device is running normally.
Issue 03 (2010-03-31)

3-9

Commissioning Guide
Data Planning
Table 3-1 Data planning
Item
Data
Remarks
Device name
NE40E-1
By default, the device name

is HUAWEI.
Procedure
Step 1 Run the system-view command to enter the system view.
<HUAWEI> system-view
Step 2 Run the sysname NE40E-1 command to specify a device name.

[HUAWEI] sysname NE40E-1
[NE40E-1]
----End
Operation Result
After the configuration is complete, the system name is displayed as [NE40E-1].
3.4 Setting System Time

Setting system time accurately ensures that the NE80E/40E works with other devices
coordinately.
Prerequisite
Data Planning
Table 3-2 Data planning
3-10
Item
Data
Remarks
Universal Time Coordinated

(UTC)
00:00:00 2009-01-01
The NE80E/40E calculates

its own time based on the
UTC and the time zone.

Issue 03 (2010-03-31)

Commissioning Guide
Item
Data
Remarks
Time zone
gmt add 05:00:00
The time zone can be set

through the clock timezone
time-zone-name { add |
minus } offset command.
The NE80E/40E obtains the
current system time by
subtracting (add) an offset
from or adding (minus) an
offset to the UTC.
Start time of the daylight

saving time
01:00 (HH:MM) on the last

Sunday in March annually
At this time, the NE80E/40E

adds an offset to the current
system time.
End time of the daylight

saving time
02:00 (HH:MM) on the last

Sunday in October annually
At this time, the NE80E/40E

subtracts an offset from the
current system time.
Offset of the daylight saving

time
01:00 (HH:MM)
NOTE
The preceding takes the data of the daylight saving time at a certain site as an example. The start time, end
time, and offset of the daylight saving time are regulated by the country where the site is located.
Procedure
Step 1 Set the UTC.
<HUAWEI> clock datetime 00:00:00 2009-01-01
Step 2 Set the time zone based on an offset.

<HUAWEI> clock timezone gmt add 05:00:00
NOTE
The NE80E/40E obtains the current system time by subtracting (add) an offset from or adding (minus) an
offset to the UTC.
The obtained system time is 19:00:00 2008-12-31.
Step 3 (Optional) Set the daylight time.

<HUAWEI> clock daylight-saving-time gmt repeating 01:00 last Sun Mar 02:00 last Sun
Oct 01:00
----End
Operation Result
Run the display clock command to view the configuration.
<HUAWEI> dispaly clock
2008-12-31 19:16:14
Wednesday
Time Zone : z5 add 05:00:00
Issue 03 (2010-03-31)

3-11

Commissioning Guide
Daylight saving time
Name
Repeat mode
Start year
End year
Start time
End time
Saving time
:
:
:
:
:
:
:
:
gmt
repeat
2000
2099
last Sunday March 01:00:00
last Sunday October 02:00:00
01:00:00
3.5 Configuring a Management User to Remotely Log in to

a Device
This section describes how to configure a management user to remotely log in to a device.
Through remote login, the management user can log in to a device to deploy services from the
central equipment room.
3.5.1 Configuring a User to Log in to a Device Through Telnet
This section describes how to configure Telnet. Through Telnet, a user can remotely log in to a
device.
3.5.2 (Operational) Configuring ACLs to Filter Login Users
This section describes how to filter users through Access Control Lists (ACLs). By configuring
ACLs, you can configure a device to filter login users.
3.5.3 (Optional) Configuring a User to Log in to a Device Through FTP
This section describes how to configure the NE80E/40E as a File Transfer Protocol (FTP) server.
The NE80E/40E is configured to be an FTP server to upload system software.
3.5.4 (Optional) Configuring a User to Log in to a Device Through SSH
This section describes how to configure Secure Shell (SSH). SSH is a secure remote login
protocol, developed based on the traditional Telnet. Compared with Telnet, SSH is greately
improved in terms of the authentication mode and data transmission security.

This section describes how to configure Telnet. Through Telnet, a user can remotely log in to a
device.
Prerequisite
The configuration 3.2 Checking a Device is complete and the device is running normally.
Data Preparation
Table 3-3 Data preparation
3-12
Item
Data
Remarks
Maximum number of users

that can log in to the device at
the same time
Default user level
For details on user levels, see

"Command Level."

Issue 03 (2010-03-31)

Commissioning Guide
Item
Data
Remarks
User name
huawei
Password
huawei
Specified user level
If no user level is specified,

the default user level is
adopted as the level of a login
user.
(Optional) user type
telnet
User types include ftp, ppp,

ssh, telnet, and terminal. By
default, a local user can use
any access type.
Idle-cut traffic
10
It is used to determine
whether a user is idle. It is
expressed in bytes. In this
case, when the user traffic is
less than 10 bytes, the user is
in the idle state.
Idle-cut time
30
It indicates the duration when

a user remains idle. It is
expressed in minutes. In this
case, when a user remains
idle for 30 minutes, the
connection between the user
and the device is torn down.
Command Level
System commands are hierarchical. By default, the following commands ranging from level 0
to level 3 are registered.
l
Commands of level 0, the visit level: includes diagnostic tools (such as the ping and
tracert commands) and the commands that are used to access a remote device (such as
Telnet and SSH). The commands of level 0 cannot be used to save configuration files.
Commands of level 1, the monitoring level: are used for system maintenance, including
display commands. The commands of level 1 cannot be used to save configuration files.
Commands of level 2, the configuration level: are used for service configuration, including
routing commands and commands at each network layer to provide network services to
users.
Commands of level 3, the management level: are used for system basic operation to support
services, including file system, FTP, Trivial File Transfer Protocol (TFTP), and
configuration file switching commands, slave board control commands, user management
commands, command level configuration commands, system parameter configuration
commands, and debugging commands.
Issue 03 (2010-03-31)

3-13

Commissioning Guide
Procedure
Step 1 Set the maximum number of users that can log in to the device at the same time.
[HUAWEI] user-interface maximum-vty 5
Step 2 Create a user, configure the user name and user password, and specify the user level.
[HUAWEI] aaa
[HUAWEI-aaa]
[HUAWEI-aaa]
[HUAWEI-aaa]
[HUAWEI-aaa]
local-user huawei password cipher huawei

local-user huawei level 3
local-user huawei service-type telnet
quit
NOTE
If there are multiple users, repeat Step 2.
Step 3 Configure the authentication mode, default user level, and idle-cut time.
[HUAWEI] user-interface vty 0 4
[HUAWEI-ui-vty0-4] user privilege level 1
[HUAWEI-ui-vty0-4] authentication-mode aaa
[HUAWEI-ui-vty0-4] idle-timeout 30 10
[HUAWEI-ui-vty0-4] quit
----End
After the preceding configurations are complete, run the following command to check the result.
<HUAWEI> telnet 127.0.0.1
Trying 127.0.0.1 ...
Press CTRL+K to abort
Connected to 127.0.0.1 ...
***********************************************************
*
Copyright (C) 2000-2009 Huawei Technologies Co., Ltd. *
*
Without the owner's prior written consent,
*
* no decompiling or reverse-engineering shall be allowed. *
* Notice:
*
*
This is a private communication system.
*
*
Unauthorized access or use may lead to prosecution.
*
***********************************************************
Login authentication
Username:huawei
Password:
Info: huawei logs in through VTY4 from 127.0.0.1.
Info: The max number of VTY users is 20, and the number
of current VTY users on line is 1.
<HUAWEI>
3.5.2 (Operational) Configuring ACLs to Filter Login Users

This section describes how to filter users through Access Control Lists (ACLs). By configuring
ACLs, you can configure a device to filter login users.
Prerequisite
The following configurations are complete and the device is running normally:
3-14

Issue 03 (2010-03-31)

Commissioning Guide
Background Information
You can use different methods to filter the users that log in to the NE80E/40E. For example,
you can configure Quality of Service (QoS) or attack defense. This section describes only how
to filter login users by configuring ACLs in the user interface view.
If you configure ACLs in the user interface view, the device can filter only the packets of login
users rather than attack packets.
Data Preparation
Item
Data
Remarks
ACL number
3001
For details on different

levels, see "ACL
Classification." Generally,
advanced ACLs are
configured to filter login
users.
IP address that can access the

device
100.100.1.1
100.100.1.2
It can be the source IP address

of the NMS device or the log
host.
ACL Type
ACL Number Range
Remarks
Interface-based ACL
1000 to 1999
An interface-based ACL can

define rules based on the
interface that receives
packets.
Basic ACL
2000 to 2999
A basic ACL can define rules

based on only source
addresses.
ACL Classification
Table 3-5 ACL classification
Issue 03 (2010-03-31)

3-15

Commissioning Guide
ACL Type
ACL Number Range
Remarks
Advanced ACL
3000 to 3999
An advanced ACL can define

rules based on the source
address, destination address,
type of the protocol over IP,
and protocol features (such as
the source port and
destination port of TCP and
the type and code of ICMP).
Ethernet frame header-based

ACL
4000 to 4099
An Ethernet frame headerbased ACL, which is a

special ACL, can define rules
based on the Ethernet frame
header of the received
packets.
Procedure
Step 1 Create an ACL.
[HUAWEI] acl 3001
[HUAWEI-acl-adv-3001]
rule permit ip source 100.100.1.1 0

rule permit ip source 100.100.1.2 0
rule deny ip source any
quit
NOTE
You can specify other parameters to further match login users. For details on other parameters, see rule
(ACL view).
Step 2 Apply the ACL in the user interface view.

[HUAWEI-ui-vty0-4] acl 3001 inbound
----End
A terminal can access the NE80E/40E only when the terminal is assigned a specified IP address.
Otherwise, the terminal cannot access the NE80E/40E.
3.5.3 (Optional) Configuring a User to Log in to a Device Through

FTP
This section describes how to configure the NE80E/40E as a File Transfer Protocol (FTP) server.
The NE80E/40E is configured to be an FTP server to upload system software.
Prerequisite
3-16

Issue 03 (2010-03-31)

Commissioning Guide
Data Preparation
Item
Data
Remarks
User name
ftp
Password
huawei
User path
cfcard:/
It is the path that a user can

access after logging in to a
device through FTP.
(Optional) user type
telnet
User types include FTP users,

PPP users, SSH users, Telnet
users, and terminal users. By
default, a local user can use
any access type.
ACL number
2001
It indicates that only basic

ACLs can be used to filter
login users.
IP address that can access the

device
100.100.1.3
Procedure
Step 1 Enable FTP on the NE80E/40E.
[HUAWEI] ftp server enable
Info: Succeeded in starting the FTP server
Step 2 Create a user, configure the user name and user password, and specify the user path.
[HUAWEI] aaa
[HUAWEI-aaa]
[HUAWEI-aaa]
[HUAWEI-aaa]
[HUAWEI-aaa]
local-user ftp password cipher huawei

local-user ftp ftp-directory cfcard:/
local-user ftp service-type ftp
quit
NOTE
If there are multiple users, repeat Step 2.
Step 3 Create a basic ACL.

[HUAWEI] acl 2001
[HUAWEI-acl-basic-2001] rule permit source 100.100.1.3 0
[HUAWEI-acl-basic-2001] rule deny source any
[HUAWEI-acl-basic-2001] quit
Step 4 Apply the ACL to filter FTP users.

[HUAWEI] ftp acl 2001
----End
Issue 03 (2010-03-31)

3-17

Commissioning Guide
The following takes an example of logging in to the NE80E/40E through FTP from a PC.
1.
Log in to the NE80E/40E through FTP.

C:\> ftp 100.1.1.200
Trying 100.1.1.200 ...
Press CTRL+K to abort
Connected to 100.1.1.200.
220 FTP service ready.
User(100.1.1.200:(none)):ftp
331 Password required for ftp.
Enter password:
230 User logged in.
2.
View the files in the specified path.

ftp> dir
200 Port command okay.
150 Opening ASCII mode data connection for *.
drwxrwxrwx
1 noone
nogroup
0 May 22 11:04 log
-rwxrwxrwx
1 noone
nogroup
4 May 22 09:48 snmpnotilog.txt
-rwxrwxrwx
1 noone
nogroup
12579 Oct 31 2008 license-b201.txt
-rwxrwxrwx
1 noone
nogroup 163730936 Jan 16 08:38 v300r003c02b670smk1.cc
-rwxrwxrwx
1 noone
nogroup
66846 Jan 16 08:45 670paf.txt
226 Transfer complete.
FTP: 351 byte(s) received in 0.053 second(s) 6.62Kbyte(s)/sec.
3.
Upload a file.
ftp> put d:\test.txt
150 Opening ASCII mode data connection for test.txt.
ftp> dir
150 Opening ASCII mode data connection for *.
drwxrwxrwx
1 noone
nogroup
0 May 22 11:04 log
-rwxrwxrwx
1 noone
nogroup
4 May 22 09:48 snmpnotilog.txt
-rwxrwxrwx
1 noone
nogroup
12579 Oct 31 2008 license-b201.txt
-rwxrwxrwx
1 noone
nogroup 163730936 Jan 16 08:38 v300r003c02b670smk1.cc
-rwxrwxrwx
1 noone
nogroup
66846 Jan 16 08:45 670paf.txt
-rwxrwxrwx
1 noone
nogroup
0 May 22 14:30 test.txt
FTP: 416 byte(s) received in 0.042 second(s) 9.90Kbyte(s)/sec.
4.
Delete a file.
ftp> delete test.txt
250 DELE command successful.
5.
Close an FTP connection.

ftp> quit
221 Server closing.
3.5.4 (Optional) Configuring a User to Log in to a Device Through

SSH
This section describes how to configure Secure Shell (SSH). SSH is a secure remote login
protocol, developed based on the traditional Telnet. Compared with Telnet, SSH is greately
improved in terms of the authentication mode and data transmission security.
Prerequisite
3-18

Issue 03 (2010-03-31)

Commissioning Guide
Data Preparation
Item
Data
Remarks
SSH user name
client001
SSH user password
huawei
SSH user level
If no level is specified for an

SSH user, the default user
level configured in the user
interface view is adopted as
the level of a login user.
SSH user authentication

mode
password
SSH authentication modes

can be classified into two
types: Revest-ShamirAdleman (RSA)
authentication and password
authentication. This section
describes only the password
authentication.
Procedure
Step 1 Generate a local key pair.
[HUAWEI] rsa local-key-pair create
The key name will be: HUAWEI_Host
The range of public key size is (512 ~ 2048).
NOTES: If the key modulus is greater than 512,
It will take a few minutes.
Input the bits in the modulus[default = 512]:512
Generating keys...
....++++++++++++
..........++++++++++++
....++++++++
......................................++++++++
Step 2 Configure a VTY user interface.

[HUAWEI-ui-vty0-4] authentication-mode aaa
[HUAWEI-ui-vty0-4] protocol inbound ssh
NOTE
If SSH is configured as the login protocol, the NE80E/40E automatically disables Telnet.
Step 3 Create an SSH user and configure the user authentication mode as the password authentication.
[HUAWEI] ssh user client001 authentication-type password
Step 4 Configure the SSH user name and password.

[HUAWEI] aaa
[HUAWEI-aaa] local-user client001 password cipher huawei
Issue 03 (2010-03-31)

3-19

Commissioning Guide
[HUAWEI-aaa] local-user client001 level 3
[HUAWEI-aaa] local-user client001 service-type ssh
Step 5 Enable STelnet and configure the service type of the user as STelnet.
[HUAWEI] stelnet server enable
[HUAWEI] ssh user client001 service-type stelnet
----End
Log in to a device through SSH. This section only describes how to log in to a device through
the software putty.
3-20
1.
As shown in the following figure, the IP address of the device is 192.168.1.1 and the login
protocol is SSH.
2.
Enter the user name client001 and the password huawei.

Issue 03 (2010-03-31)

Commissioning Guide
3.6 Commissioning the Link Layer

This section describes how to commission the link layer of the Router that connects to other
routers or transmission devices.
3.6.1 Commissioning the Link Layer of an Ethernet Interface
This section describes how to commission the link layer of an Ethernet interface.
3.6.2 Commissioning the Link Layer of a POS Interface
This section describes how to commission the link layer of a POS interface. When using the
SONET/SDH optical interface to transmit packets, you need to configure parameters for the
POS interface.
3.6.3 Commissioning the Link Layer of a CPOS Interface
This section describes how to commission the link layer of a CPOS interface.
3.6.4 Commissioning the Link Layer of the E1/T1 Interface
This section describes how to commission the link layer of the E1/T1 interface.
3.6.5 Commissioning the Link Layer of an ATM Interface
This section describes how to commission the link layer of an ATM interface.
3.6.6 Commissioning the Link Layer of a User Interface on an FR Network
This section describes how to commission the link layer of a user interface on an FR network.
3.6.7 Commissioning the Power of an Optical Interface
Issue 03 (2010-03-31)

3-21

Commissioning Guide
Perform this task to commission the power of an optical interface of the NE80E/40E.
3.6.1 Commissioning the Link Layer of an Ethernet Interface

This section describes how to commission the link layer of an Ethernet interface.
3.6.1.1 Commissioning the Link Layer of an Ethernet Interface on an LPU
This section describes how to commission the link layer of an Ethernet interface on an LPU.
3.6.1.2 Commissioning the Link Layer of an Ethernet Interface on an MPU
This section describes how to commission the link layer of an Ethernet interface on an MPU.
3.6.1.3 Configuring Layer 2 Parameters for an Ethernet Interface
This section describes how to configure Layer 2 parameters for an Ethernet interface.
3.6.1.1 Commissioning the Link Layer of an Ethernet Interface on an LPU

This section describes how to commission the link layer of an Ethernet interface on an LPU.
Prerequisite
Data Preparation
No.
Data
Number of the Ethernet interface
MTU of the Ethernet interface
Procedure
l
Configuring the MTU for the Ethernet interface

Configure the MTU for IPv4 packets on the Ethernet interface.
1.
Run the system-view command to enter the system view.
2.
Run the interface { ethernet | gigabitethernet } interface-number command to enter

the view of a specified Ethernet interface.
By default, an Ethernet interface is in Layer 3 mode.
3.
Run the mtu mtu command to configure the MTU for IPv4 packets on the Ethernet
interface.
The MTU is in bytes. The value range of the MTU of an Ethernet interface depends
on the device. By default, the MTU is 1500.
3-22

Issue 03 (2010-03-31)

Commissioning Guide
CAUTION
If IPv6 runs on an Ethernet interface and the MTU set through the mtu mtu command
on the interface is smaller than 1280, IPv6 works abnormally on this interface. To
avoid this problem, when IPv6 runs on an Ethernet interface, set the value of the MTU
of the interface to greater than or equal to 1280.
Configure the MTU for IPv6 packets on the Ethernet interface.
1.
2.

By default, an Ethernet interface is in Layer 3 mode.
3.
Run the ipv6 enable command to enable IPv6 on the Ethernet interface.
4.
Run the ipv6 mtu mtu command to configure the MTU for IPv6 packets on the
Ethernet interface.
The MTU is in bytes. The value range of the MTU of an Ethernet interface depends
on the device. By default, the MTU is 1500.
Configuring the working mode for the Ethernet interface

1.
2.

3.
Run the following command as required:
Run the duplex { full | half | auto } command to set the working mode for the
Ethernet interface.
Run the negotiation auto command to configure the Ethernet interface to work in
auto-negotiation mode.
NOTE
Ethernet optical interfaces can work only in full-duplex mode.
When connecting to a hub, the Ethernet electrical interface on the router should work in
half-duplex because hubs can work only in half-duplex mode. When connecting to a LAN
switch, the Ethernet electrical interface on the router can work in either full-duplex mode
or half-duplex mode. Note that the working mode of the Ethernet interface and that of the
peer must be the same.
For a GE electrical interface, the working rate 1000 Mbit/s and half-duplex working mode
are mutually exclusive; therefore, they cannot be configured simultaneously.
For a GE electrical interface enabled with auto-negotiation and working at 1000 Mbit/s, it
cannot be configured with simplex mode or duplex mode. In addition, the auto-negotiation
mode cannot be canceled.
For a GE electrical interface working at 10 Mbit/s or 100 Mbit/s, you can configure it to
work in simplex mode, duplex mode, or auto-negotiation mode.
For a GE optical interface enabled with auto-negotiation, you must configure both ends of
the link to work in auto-negotiation mode.
Configuring the rate for the Ethernet electrical interface

1.
Issue 03 (2010-03-31)

3-23

Commissioning Guide
2.

3.
Run the speed { 10 | 100 | auto } command to configure the rate for the Ethernet
electrical interface.
NOTE
By default, a GE electrical interface works at 1000 Mbit/s in auto-negotiation mode. You can
forcibly change the rate, ensuring that the rates of both ends are the same. When you set the
rate to 10 Mbit/s or 100 Mbit/s, the auto-negotiation mode is canceled.
Configuring the mode of the GE/FE optical/electrical interface.

1.
2.

3.
Run the port-type { copper | fiber-100 | fiber-1000 } command to set the interface
mode.
As long as the router can recognize the type of the SFP module, according to which
the system automatically sets the working mode for the interface, no configuration is
required.
If the router cannot recognize the type of the SFP module that works normally, you
need to forcibly set the working mode for the interface.
NOTE
Before configuring the working mode for the GE/FE optical/electrical interface, you need to
delete all the configurations on the interface.
Configuring LAN/WAN transmission mode for a 10GE interface

1.
2.
Run the interface gigabitethernet interface-number command to enter the 10GE

interface view.
3.
Run the shutdown command to shut down the interface.
4.
Run the set transfer-mode { lan | wan } command to configure the LAN/WAN
transmission mode for the 10GE interface.
5.
Run the undo shutdown command to restart the interface.

NOTE
Before configuring the transmission mode of an interface to WAN, you need to clear all
LAN configurations on the interface and shut down the interface.
Before configuring the transmission mode of an interface to LAN, you need to clear all
WAN configurations on the interface and shut down the interface.
----End
# Run the display interface { ethernet | gigabitethernet } command. If information about the
Ethernet interface, such as the MTU, IP address, mask, working rate, and working mode, is
displayed, it means that the configuration succeeds. For example:
<HUAWEI> display interface gigabitethernet 2/0/0
GigabitEthernet2/0/0 current state : UP
Line protocol current state : UP
Last line protocol up time : 2009-12-17 14:38:21
3-24

Issue 03 (2010-03-31)

Commissioning Guide
Description:HUAWEI, GigabitEthernet2/0/0 Interface

Route Port,The Maximum Transmit Unit is 1500
Internet Address is 192.168.10.20/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc7d-a497
The Vendor PN is SCP6F86-GL-CWH
The Vendor Name is SumitomoElectric
Port BW: 1G, Transceiver max BW: 1G, Transceiver Mode: MultiMode
WaveLength: 850nm, Transmission Distance: 300m
Rx Power: -18.76dBm, Tx Power: -5.05dBm
Loopback:none, full-duplex mode, negotiation: disable, Pause Flowcontrol:Receive
Enable and Send Enable
Last physical up time
: 2009-12-17 14:33:29
Last physical down time : 2009-12-17 14:33:27
Statistics last cleared:never
Last 300 seconds input rate: 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bits/sec, 0 packets/sec
Input: 0 bytes, 0 packets
Output: 0 bytes, 0 packets
Input:
Unicast: 0 packets, Multicast: 0 packets
Broadcast: 0 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: 0 packets, Multicast: 0 packets
Broadcast: 0 packets, JumboOctets: 0 packets
Lost: 0 packets, Overflow: 0 packets, Underrun: 0 packets
System: 0 packets, Overruns: 0 packets
TxPause: 0 packets
# Run the display interface ethernet brief command. If the physical status, auto-negotiation
method, duplex mode, interface rate, and latest average inbound and outbound bandwidth
utilization are displayed, it means that the configuration succeeds. For example:
<HUAWEI> display interface ethernet brief
PHY: Physical
*down: administratively down
^down: standby
(l): loopback
(b): BFD down
InUti/OutUti: input utility/output utility
Interface
PHY
Auto-Neg
GigabitEthernet0/0/0
up
enable
up
disable
*down disable
*down disable
*down disable
*down disable
*down disable
*down disable
up
disable
down disable
*down disable
down disable
down disable
GigabitEthernet4/1/1.7
down disable
down disable
down disable
down disable
down disable
down disable
down disable
GigabitEthernet4/1/7.7
down disable
Issue 03 (2010-03-31)
Duplex Bandwidth InUti OutUti Trunk

half
100M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
-full
1000M
0%
0%
--

3-25

Commissioning Guide
3.6.1.2 Commissioning the Link Layer of an Ethernet Interface on an MPU

This section describes how to commission the link layer of an Ethernet interface on an MPU.
Prerequisite
Data Preparation
No.
Data
Procedure
l
Configuring the working type for the Ethernet interface

1.
2.

3.
Run the duplex { full | half | auto } command to set the working mode for the Ethernet
interface.
Ethernet electrical interfaces can work in either full-duplex mode or half-duplex mode.
By default, auto is adopted. That is, the system automatically negotiates with the peer
to work out the optimal duplex mode.
NOTE
When connecting to a hub, the Ethernet interface on the router should be work in halfduplex because hubs can work only in half-duplex mode. When connecting to a LAN
switch, the Ethernet interface on the router can work in either full-duplex mode or halfduplex mode. Note that the working mode of the Ethernet interface and that of the peer
must be the same.
Configuring the rate for the Ethernet electrical interface

1.
2.

3.
Run the speed { 10 | 100 | auto } command to set the rate of the Ethernet electrical
interface.
NOTE
Ethernet electrical interfaces on a router can work at 10 Mbit/s, 100 Mbit/s, or 1000 Mbit/s.
By default, auto is adopted. That is, the system automatically negotiates with the peer and
works out the optimal working rate.
You can forcibly set the rate, ensuring that the rate of the interface is the same as the rate of
the interface on the peer.
Configuring the hybrid mode for the Ethernet electrical interface

1.
3-26

Issue 03 (2010-03-31)

Commissioning Guide
2.

3.
Run the promode { on | off } command to configure the hybrid mode for the Ethernet
interface.
By default, the hybrid mode of an Ethernet interface on the MPU is off.
----End
3.6.1.3 Configuring Layer 2 Parameters for an Ethernet Interface

This section describes how to configure Layer 2 parameters for an Ethernet interface.
Prerequisite
Data Preparation
No.
Data
Procedure
Step 2 Run the interface { ethernet | gigabitethernet } interface-number command to enter the view
of a specified Ethernet interface.
Step 3 Run the portswitch command to switch the Ethernet interface to a Layer 2 interface.
Step 4 Run the port link-type { access | hybrid | trunk | dot1q-tunnel } command to set the interface
type.
By default, the interface type is hybrid.
----End
3.6.2 Commissioning the Link Layer of a POS Interface

This section describes how to commission the link layer of a POS interface. When using the
SONET/SDH optical interface to transmit packets, you need to configure parameters for the
POS interface.
Prerequisite
Issue 03 (2010-03-31)

3-27

Commissioning Guide
Data Preparation
No.
Data
Number of the CPOS interface
Value of the overhead byte, which can be J0, J1, or C2
Link layer protocol running on the POS interface
Frame format of the POS interface
Length of the CRC field of the POS interface
Clock mode of the POS interface
Procedure
l
Configuring the same C2/J0/J1 for the POS interfaces that are connected to each other
especially when the router and a non-Huawei device interconnect
1.
Run the system-view command on the router to enter the system view.
2.
Run the interface pos interface-number command to enter the view of a specified
POS interface.
3.
Run the A.13 flag (pos interface view) command to configure the overhead byte for
the POS interface.
Configuring the same scrambling mode for the POS interfaces that are connected to each
other (That is, both POS interfaces are enabled with or disabled from the scrambling
function.)
1.
2.
POS interface.
3.
Run the A.24 scramble (POS interface view) command to enable the scrambling
function.
Configuring the same link layer protocol for the POS interfaces that are connected to each
other (HDLC or PPP is preferred)
1.
2.
POS interface.
3.
Run the A.20 link-protocol (POS interface view) command to configure the link
layer protocol for the POS interface.
NOTE
POS interfaces support only the basic functions of FR P2P sub-interfaces and do not support
other FR functions.
If PPP is adopted, it is recommended that CHAP and PAP authentication modes be configured
on the interface at the same time. The CHAP authentication mode is preferentially used. For
details, see A.21 ppp authentication-mode.
3-28
Configuring the same physical layer protocol for the POS interfaces that are connected to
each other (SONET or SDH is preferred)
Issue 03 (2010-03-31)

Commissioning Guide
1.
2.
POS interface.
3.
Run the A.18 frame-format (POS interface view) command to configure the frame
format for the POS interface.
Configuring the same CRC field for the POS interfaces that are connected to each other
(CRC32 or CRC16 is preferred)
1.
2.
POS interface.
3.
Run the A.4 crc (POS interface view) command to configure the CRC field for the
POS interface.
Configuring the clock modes for the POS interfaces that are connected to each other
A POS interface supports two clock modes:
Master: uses the internal clock signal.
Slave: uses the line clock signal.
Similar to the synchronous serial interface that works in either data terminal equipment
(DTE) mode or data circuit-terminating equipment (DCE) mode, a POS interface works in
either master clock mode or slave clock mode.
When the POS interfaces on two routers are connected directly or through Wavelength
Division Multiplexing (WDM), set one POS interface to the master clock mode and the
other to the slave clock mode. Otherwise, link flapping may occur.
When a POS interface on the router is connected to a switch, which functions as DCE
using the internal clock signal, and the POS interface on the router functions as DTE,
you should set the POS interface to work in slave clock mode.
Do as follows on the router:
1.
2.
POS interface.
3.
Run the A.3 clock (POS interface view) command to configure the clock mode for
the POS interface.
Configuring the next hop of a static route as the outgoing interface if route iteration is not
expected on the POS link
----End
# After the configuration is complete, run the display interface pos command. If information
about the POS interface, such as the physical status, link protocol status, and clock mode, is
displayed, it means that the configuration succeeds. For example:
<HUAWEI> display interface pos 1/0/0
Pos1/0/0 current state : UP
Description : Pos1/0/0 Interface
Route Port,The Maximum Transmit Unit is 4470 bytes, Hold timer is 10(sec)
Issue 03 (2010-03-31)

3-29

Commissioning Guide

Link layer protocol is PPP
LCP opened, IPCP opened
The Vendor Name is FINISAR CORP.
The Vendor PN is FTLF1321P1BTL-HW
Port BW: 2.5G, Transceiver Mode: Single Mode
WaveLength: 1310nm, Transmission Distance: 2km
Rx Optical Power: -40.00dBm, Tx Optical Power: -40.00dBm
Physical layer is Packet Over SDH,
Scramble enabled, clock master, CRC-32, loopback: none
Flag J0 "NetEngine
"
Flag J1 "NetEngine
"
Flag C2 22(0x16)
SDH alarm:
section layer: none
line
layer: none
path
layer: none
SDH error:
section layer: B1 0
line
layer: B2 0 REI 0
path
layer: B3 0 REI 0
Statistics last cleared:2006-12-20 09:20:21
Last 300 seconds input rate 0 bits/sec, 0 packets/sec
Last 300 seconds output rate 0 bits/sec, 0 packets/sec
Input: 24 packets, 12593 bytes
Input error: 4 shortpacket, 0 longpacket, 80 CRC, 0 lostpacket
Output: 604 packets, 9688 bytes
Output error: 0 lostpackets
Output error: 0 overrunpackets, 0 underrunpackets
# Run the display interface brief [ | { begin |include |exclude } regular-expression ] command.
If the brief information about the POS interface, such as the physical status, link protocol status,
bandwidth utilization, and number of error packets, is displayed, it means that the configuration
succeeds. For example:
<HUAWEI> display interface brief | include Pos
PHY: Physical
^down: standby
(l): loopback
(s): spoofing
(b): BFD down
(e): EFM down
(d): Dampening Suppressed
Interface
PHY
Protocol
outErrors
Pos1/0/0
up
up
0
Pos1/0/1
down
down
0
Pos1/0/2
down
down
0
Pos1/0/3
down
down
0
InUti OutUti
inErrors
0.01%
0.01%
3795064053
0%
0%
343911292
0%
0%
343913408
0%
0%
343915353
# Run the display pos interface command. If information about the physical layer of the POS
interface is displayed, it means that the configuration succeeds. For example:
<HUAWEI> display pos interface pos 6/0/0
Pos6/0/0 current state:UP
Line protocol current state:UP
Physical layer is Packet Over SDH
SDH alarm:
section layer: OOF LOF LOS
line
layer: none
path
layer: PAIS PRDI
SDH error:
section layer: B1 306207965
3-30

Issue 03 (2010-03-31)

Commissioning Guide
line
layer: B2 39944626237 REI 9861843785
path
layer: B3 1641810669
Last 30 seconds input rate 0 Bits/sec, 0 packets/sec
Last 30 seconds output rate 0 Bits/sec, 0 packets/sec
SFP Transp Infomation:
The Vendor PN is FTRJ1321P1BTL
The Vendor name is FINISAR CORP.
address
: 3 4 5 6 7 8 9 10 12 14 15 16 17 18 60 61
value(hex): 0 1 22 2 12 10 1 5 19 5 32 0 0 0 5 1e
Port BW: 2.5G, Transceiver max BW: 2.5G, Transceiver Mode: SingleMode
PIC Packet Statics Per Sencond:
Rxd:
0x0
Packets
0x0
FCS
0x0
Receiv Abort Packets
0x0
Long Packets
0x0
Short Packets
Txd:
0x0 Packets
0x0 Send Abort Packets
SDH OverHead:
Rx C2 Flag : Unknown, Tx C2 Flag : 0x16.
Rx J0 ASCII :
Rx J0 Flag: Unknown
Rx J1 ASCII :
Rx
Tx
f8
Tx
Tx
f8
Tx
J1 Flag: Unknown
J0 ASCII :
4e 65 74 45 6e 67
J0 String :NetEngine
J1 ASCII :
4e 65 74 45 6e 67
J1 String :NetEngine
69
6e
65
20
20
20
20
20
20
69
6e
65
20
20
20
20
20
20
3.6.3 Commissioning the Link Layer of a CPOS Interface

This section describes how to commission the link layer of a CPOS interface.
3.6.3.1 Configuring an STM-1 CPOS Interface
This section describes how to configure an STM-1 CPOS interface.
3.6.3.2 Configuring the E1 Channel of a CPOS Interface
This section describes how to configure the E1 channel of a CPOS interface.
3.6.3.3 Configuring the T1 Channel of a CPOS Interface
This section describes how to configure the T1 channel of a CPOS interface.
3.6.3.4 Configuring the E3 Channel of an STM-1 CPOS Interface
This section describes how to configure the E3 channel of an STM-1 CPOS interface.
3.6.3.5 Configuring the T3 Channel of an STM-1 CPOS Interface
This section describes how to configure the T3 channel of an STM-1 CPOS interface.
3.6.3.1 Configuring an STM-1 CPOS Interface

This section describes how to configure an STM-1 CPOS interface.
Issue 03 (2010-03-31)

3-31

Commissioning Guide
Prerequisite
Data Preparation
No.
Data
Value of the overhead byte, which can be J0, J1, or C2
Procedure
Step 1 Configuring the same C2/J0/J1 for the CPOS interfaces that are connected to each other
especially when the router and a non-Huawei device interconnect.
1.
2.
Run the controller cpos interface-number command to enter the view of a specified CPOS
interface.
3.
Run the flag { j0 { sdh | sonet } j0 | j1 j1 | c2 c2 } command to configure the overhead

byte for the CPOS interface. For details, see A.12 flag (cpos interface view).
Step 2 Configuring the same physical layer protocol for the CPOS interfaces that are connected to each
other (SONET or SDH is preferred)
1.
2.
interface.
3.
Run the frame-format { sdh | sonet } command to configure the frame format for the
CPOS interface. For details, see A.17 frame-format (CPOS interface view).
Step 3 Configuring the clock mode for the CPOS interfaces that are connected to each other
A CPOS interface supports two clock modes:
l
Master: uses the internal clock signal.
Slave: uses the line clock signal.
When connecting to an SDH/SONET device, the CPOS interface should be configured with the
slave mode because the clock accuracy on an SONET/SDH network is higher than the accuracy
of the internal clock source on a CPOS interface.
When CPOS interfaces are connected through optical fibers or Wavelength Division
Multiplexing (WDM), you should set one CPOS interface to the master mode and the other to
the slave mode.
3-32
1.
2.
interface.
Issue 03 (2010-03-31)

Commissioning Guide
3.
Run the clock { master | slave } command to set the clock mode for the CPOS interface.
For details, see A.2 clock (CPOS interface view).
----End
# Run the display controller cpos [ cpos-number ] command. If information about all the
channels of the CPOS interface is displayed, it means that the configuration succeeds. For
example:
<HUAWEI> display controller cpos 1/0/0
Cpos1/0/0 current state : UP
Description : Cpos1/0/0 Interface
The Vendor Name is AGILENT
The Vendor PN is QFCT-5736TP
Port BW: 155M, Transceiver max BW: 155M, Transceiver Mode: SingleMode
WaveLengh: 1310nm, Transmission Distance: 15km
clock master, Multiplex AU-4, loopback none
TX:Flag J0: "NetEngine
", Flag J1: "NetEngine
RX:Flag J0: "NetEngine
section layer:
alarm: none
error: B1 0
line layer:
alarm: none
error: B2 0 REI 0
path layer:
alarm: none
error: B3 0 REI 0
", Flag C2: 2(0x2)

", Flag C2: 2(0x2)
3.6.3.2 Configuring the E1 Channel of a CPOS Interface

This section describes how to configure the E1 channel of a CPOS interface.
Prerequisite
Data Preparation
No.
Data
Number of the E1 channel
Number of the channels or timeslots that are bound to form a channel-set on the CE1
interface
Procedure
Step 1 Configuring a synchronous serial interface of the E1 channel
1.
Issue 03 (2010-03-31)
3-33

Commissioning Guide
2.
interface.
3.
Run the following commands to create synchronous serial interfaces working in different
modes:
l
Run the e1 e1-number unframed command to create an E1 channel in clear channel

mode. For details, see A.9 e1 unframed (CPOS interface view).
Run the e1 e1-number channel-set set-number timeslot-list { ts0 | slot-list [ ts0 ] }

command to create an E1 channel in channelized mode and bind timeslots.
In channelized mode, timeslot 0 of the E1 channel alone can be bound to form a serial
interface; timeslots 0 to 31 can also be randomly bound to form one or multiple serial
interfaces. In this case, timeslot 0 needs to be separately listed in the command as the
parameter ts0.
Timeslot 0 is used to transmit management and alarm information. After timeslot 0 is
bound to form a serial interface, management and alarm information can be
transparently transmitted between the client and the server through the serial interface.
The channel-set formed by binding the timeslots of the E1 channel functions as a serial
interface and can be configured like a serial interface. A serial interface formed by
binding timeslots is named in the format of slot number/card number/interface number/
channel number:channel-set number.
Step 2 Configuring the frame format for the E1 channel

1.
2.
interface.
3.
Run the e1 e1-number set frame-format { crc4 | no-crc4 } command t set the frame format
for the CPOS interface. For details, see A.8 e1 set frame-format (CPOS interface
view).
Step 3 Configuring the clock mode for the E1 channel

Different E1 channels can be separately configured with the clock mode. Whether to use the
master mode or the slave mode is determined by the peer. For example:
l
When connecting to an SONET/SDH device, the E1 channel should be configured with the
slave mode.
If two routers are connected through optical fibers, you should configure one end to the master
mode and the other end to the slave mode.
By default, an E1 channel works in master mode.

1.
2.
interface.
3.
Run the e1 e1-number set clock { master | slave } command to configure the clock mode
for the E1 channel. For details, see A.7 e1 set clock (CPOS interface view).
----End
3-34

Issue 03 (2010-03-31)

Commissioning Guide
# Run the display interface serial command. If information about the serial interface on the E1
channel of the CPOS interface, such as the interface status, link layer protocol, and traffic
statistics, is displayed, it means that the configuration succeeds. For example:
<HUAWEI> display interface serial 1/0/0/1:1
Serial1/0/0/1:1 current state : UP
Description : Serial1/0/0/1:1 Interface
Route Port, The Maximum Transmit Unit is 1500, Hold timer is 10(sec)
Derived from Cpos1/0/0 e1 1, Timeslot(s) Used: 1-24, baudrate is 1536000 bps
Internet protocol processing : disabled
LCP opened
clock master, loopback none
CRC: CRC-32
Scramble disabled
Alarm: None
Traffic statistics:
# Run the display controller cpos command. If information about the CPOS interface, such the
interface status and clock mode, is displayed, it means that the configuration succeeds. For
example:
Cpos1/0/0 current state : UP
The Vendor Name is SumitomoElectric
The Vendor PN is SCP6828-H1-BNE
Port BW: 155M, Transceiver max BW: 2.5G, Transceiver Mode: SingleMode
WaveLengh: 1310nm, Transmission Distance: 2km
", Flag C2: 2(0x2)
RX:Flag J0: "", Flag J1: "NetEngine
section layer:
alarm: none
error: B1 0
line layer:
alarm: none
error: B2 0
path layer:
alarm: none
error: B3 0
", Flag C2: 2(0x2)
REI 27
REI 24
3.6.3.3 Configuring the T1 Channel of a CPOS Interface

This section describes how to configure the T1 channel of a CPOS interface.
Prerequisite
Issue 03 (2010-03-31)

3-35

Commissioning Guide
Data Preparation
No.
Data
Number of the T1 channel
Number of the channels or timeslots that are bound to form a channel-set on the
CT1 interface
Procedure
Step 1 Configuring a synchronous serial interface of the T1 channel
1.
2.
Run the controller cpos cpos-number command to enter the view of a specified CPOS
interface.
3.
Run the following commands to create synchronous serial interfaces working at different
rates.
l
Run the t1 t1-number unframed command to create a synchronous serial interface

working at 1.544 Mbit/s.
You can run the interface serial cpos-number/t1-number:0 command to access the
synchronous serial interface.
Run the t1 t1-number channel-set set-number timeslot-list slot-list [ speed { 56k |

64k } ] command to bind N timeslots of the T1 channel to form a synchronous serial
interface working at N x 56 kbit/s or N x 64 kbit/s.
You can run the interface serial cpos-number/t1-number:set-number command to
access the synchronous serial interface.
NOTE
The default rate of the synchronous serial interface formed by binding the timeslots of a T1
channel is calculated as N x 56 kbit/s, N indicating the number of timeslots.
Step 2 Configuring the frame format for the T1 channel

1.
2.
Run the controller cpos cpos-number command to enter the specified CPOS interface view.
3.
Run the t1 t1-number set frame-format { esf | sf } command to configure the frame format
for the T1 channel. For details, see A.30 t1 set frame-format (CPOS interface view).
Step 3 Configuring the clock mode for the T1 channel

Different T1 channels can be separately configured with the clock mode. Whether to use the
master mode or the slave mode is determined by the peer. For example, when connecting to an
SONET/SDH device, the T1 channel should be configured with the slave mode.
By default, a T1 channel works in master mode.
3-36

Issue 03 (2010-03-31)

Commissioning Guide
1.
2.
Run the controller cpos cpos-number command to enter the specified CPOS interface view.
3.
Run the t1 t1-number set clock { master | slave } command to configure the clock mode
for the T1 channel. For details, see A.29 t1 set clock (CPOS interface view).
----End
# Run the display interface serial command. If information about the serial interface on the T1
channel of the CPOS interface, such as the interface status, link layer protocol, and traffic
statistics, is displayed, it means that the configuration succeeds.
Description: Serial1/0/0/1:0 Interface
Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec)
Derived from Cpos1/0/0 t1 1, Timeslot(s) Used: 0-23, baudrate is 1536000 bps
LCP opened
Physical layer is Packet Over ESF
CRC: CRC-32
Scramble disabled
Alarm: none
Traffic statistics:
3.6.3.4 Configuring the E3 Channel of an STM-1 CPOS Interface

This section describes how to configure the E3 channel of an STM-1 CPOS interface.
Prerequisite
Data Preparation
No.
Data
Number of the E3 channel
Procedure
Step 1 Configuring a synchronous serial interface of the E3 channel
Issue 03 (2010-03-31)

3-37

Commissioning Guide
1.
2.
interface.
3.

l
Run the e3 e3-number framed command to create a synchronous serial interface of the
E3 channel in unchannelized mode.
Run the e3 e3-number unframed command to create a synchronous serial interface of

the E3 channel in clear channel mode.
The created synchronous serial interface is named in the format of slot number/card number/
interface number/0:0.
Different E3 channels can be separately configured with the clock mode. Whether to use the
SONET/SDH device, the E3 channel should be configured with the slave mode.
By default, an E3 channel works in master mode.
1.
2.
interface.
3.
Run the e3 e3-number set clock { master | slave } command to configure the clock mode
for the E3 channel. For details, see A.10 e3 set clock (CPOS interface view).
----End
# Run the display controller cpos command. If information about the CPOS interface, such as
the clock mode, frame format, and multiplexing path, is displayed, it means that the configuration
succeeds.
Cpos1/0/0 current state : Administratively DOWN
The Vendor PN is HFBR-5710LP-H3C
Port BW: 155M, Transceiver max BW: 1G, Transceiver Mode: MultiMode
WaveLengh: 850nm, Transmission Distance: 550m
", Flag C2: 2(0x2)
RX:Flag J0: unknown, Flag J1: unknown, Flag C2: 255(0xff)
section layer:
alarm: LOS
error: B1 306431763
line layer:
alarm: LAIS LREI SF
error: B2 511275881 REI 1175934524
path layer:
alarm: PPLM
error: B3 2711 REI 1451
3-38

Issue 03 (2010-03-31)

Commissioning Guide
# Run the display interface serial command. If information about the synchronous serial
interface formed by binding timeslots of the E3 channel, such as the interface status and clock
mode, is displayed, it means that the configuration succeeds.
Derived from Cpos2/0/0 e3 1, Unframed mode, baudrate is 34368000 bps
LCP opened
CRC: CRC-32
Scramble disabled
Alarm: None
Traffic statistics:
3.6.3.5 Configuring the T3 Channel of an STM-1 CPOS Interface

This section describes how to configure the T3 channel of an STM-1 CPOS interface.
Prerequisite
Data Preparation
No.
Data
Number of the T3 channel
Procedure
Step 1 Configuring a synchronous serial interface of the T3 channel
1.
2.
interface.
3.
Issue 03 (2010-03-31)
Run the t3 t3-number framed command to create a synchronous serial interface of the
T3 channel in unchannelized mode.
Run the t3 t3-number unframed command to create a synchronous serial interface of

the T3 channel in clear channel mode.
3-39

Commissioning Guide
The created synchronous serial interface is named in the format of slot number/card number/
interface number/0:0.
Different T3 channels can be separately configured with the clock mode. Whether to use the
SONET/SDH device, the E3 channel should be configured with the slave mode.
By default, a T3 channel works in master mode.
1.
2.
interface.
3.
Run the t3 t3-number set clock { master | slave } command to configure the clock mode
for the T3 channel. For details, see A.31 t3 set clock (CPOS interface view).
----End
# Run the display controller cpos command. If information about the CPOS interface, such as
the clock mode, frame format, and multiplexing path, is displayed, it means that the configuration
succeeds.
Cpos1/0/0 current state : Administratively DOWN
The Vendor PN is HFBR-5710LP-H3C
Port BW: 155M, Transceiver max BW: 1G, Transceiver Mode: MultiMode
WaveLengh: 850nm, Transmission Distance: 550m
", Flag C2: 2(0x2)
RX:Flag J0: unknown, Flag J1: unknown, Flag C2: 255(0xff)
section layer:
alarm: LOS
error: B1 306431763
line layer:
alarm: LAIS LREI SF
error: B2 511275881 REI 1175934524
path layer:
alarm: PPLM
error: B3 2711 REI 1451
# Run the display interface serial command. If information about the synchronous serial
interface formed by binding timeslots of the T3 channel, such as the interface status and clock
mode, is displayed, it means that the configuration succeeds.
Line protocol current state :UP
Derived from Cpos2/0/0 t3 1, Unframed mode, baudrate is 44736000 bps
3-40

Issue 03 (2010-03-31)

Commissioning Guide

LCP opened
CRC: CRC-32
Scramble disabled
Alarm: None
Traffic statistics:
3.6.4 Commissioning the Link Layer of the E1/T1 Interface

This section describes how to commission the link layer of the E1/T1 interface.
Prerequisite
Data Preparation
Item
Data
Configue CE1
Interfaces
Number of the CE1 interface
Number of the channel formed by binding timeslots on the CE1 interface
Number of the timeslots that are bound to form a channel-set on the CE1
interface
Number of the CT1 interface
Number of the channel formed by binding timeslots on the CT1 interface
Number of the timeslots that are bound to form a channel-set on the CT1
interface
Configue CT1
Interfaces
Configue E3
Interfaces
Number of the E3 interface
Configue CT3
Interfaces
Number of the CT3 interface
T1 channel number on the CT1 interface
Timeslot number, timeslot range, or number of the channel of the T1

interface
Context
For detailed procedure for commissioning the link layer of the E1/T1 interface, see "Configuring
an E-Carrier Interface and a T-Carrier Interface" in the HUAWEI HUAWEI NetEngine80E/
40E Router Configuration Guide - WAN Access.
When configuring the clock mode for the E1/T1 interface, note the following:
Issue 03 (2010-03-31)

3-41

Commissioning Guide
l
Different E1/T1 channels are separately configured with the clock mode. Which clock mode
is used depends on the peer.
When the commissioned device is connected to a transmission device, it is configured

with the slave mode.
When the commissioned device is directly connected to a router through optical fibers
or is connected to a router on a dense wavelength division multiplexing (DWDM)
network, both the commissioned device and the router are configured with the master
mode.
When the CT1 interface functions as a DCE, it is configured with the master mode; when
the CT1 interface functions as a DTE, it is configured with the slave mode.
When the CT1 interfaces of two routers are directly connected, one interface is configured
with the master mode and the other interface is configured with the slave mode.
3.6.5 Commissioning the Link Layer of an ATM Interface

This section describes how to commission the link layer of an ATM interface.
Prerequisite
Data Preparation
No.
Data
Number of the ATM interface
Procedure
l
Configuring the same C2/J0/J1 for the ATM interfaces that are connected to each other
especially when the router and a non-Huawei device interconnect.
1.
2.
Run the interface atm interface-number command to enter the view of a specified
ATM interface.
3.
Run the A.11 flag (atm interface view) command to configure the overhead byte for
the ATM interface.
Configuring the same scrambling mode for the ATM interfaces that are connected to each
other (Both ATM interfaces are enabled with or disabled from the scrambling function.)
1.
2.
ATM interface.
3.
Run the A.23 scramble (ATM interface view) command to enable the scrambling
function.
Configuring the same physical layer protocol for both ATM interfaces that are connected
to each other (SONET or SDH is preferred)
1.
3-42

Issue 03 (2010-03-31)

Commissioning Guide
2.
ATM interface.
3.
Run the A.16 frame-format (ATM OC/STM) command to configure the frame
format for the ATM interface.
Configuring the clock mode for the ATM interface

According to the function on the network, ATM devices and their interfaces can be
classified into two types:
A user's device is called a DTE, and the type of the corresponding interface is DTE.
The device that provides access services for users' devices belongs to the network device
and is called a DCE, and the type of the corresponding interface is DCE.

1.
2.
ATM interface.
3.
Run the A.1 clock (ATM interface view) command to configure the clock mode for
the ATM interface.
By default, an ATM interface works in master mode.
Master mode: uses the internal clock signal.
Slave mode: uses the line clock signal.
An ATM interface serving as a DTE should be configured with the slave mode; an
ATM interface serving as a DCE should be configured with the master mode.
In the scenario where two routers are directly connected through ATM interfaces or
through Wavelength Division Multiplexing (WDM), you need to configure the master
mode for one end and the slave mode for the other end.
When connecting to an SDH/SONET device, the router should be configured with the
slave mode.
----End
# Run the display interface atm command. If the configuration of the ATM interface, such as
the scrambling function ,frame format, clock mode, and statistical period, is displayed, it means
that the configuration succeeds. For example:
<HUAWEI> display interface atm 1/0/0
Atm1/0/0 current state : UP
Last line protocol up time: 2008-11-03, 17:24:24
Description : Atm1/0/0 Interface
Route Port, The Maximum Transmit Unit is 1500
AAL enabled: AAL5, Maximum VCs: 2048
VCs on main-interface: 1 (Total VCs: 1)
VPs on main-interface: 0 (Total VPs: 1 )
The Vendor Name is FINISAR CORP.
, The Vendor PN is FTRJ1321P1BTL
Transceiver BW: 2.5G, Transceiver Mode: Single Mode
Rx Optical Power: -24.95dBm, Tx Optical Power: -1.99dBm
Issue 03 (2010-03-31)

3-43

Commissioning Guide
UBR: 1, CBR: 0, VBR: 0, USED BandWidth: 0Kbps

VPI Max: 255, VCI Max: 2047
Flag: J0 "NetEngine
"
Flag: J1 "NetEngine
"
Flag: C2 19(0x13)
SDH alarm:
section layer: OOF LOF LOS
line layer: AIS
path layer: AIS RDI
SDH error:
section layer: B1: 24
line layer: B2: 0
M1: 0
path layer: B3: 0
G1: 0
Send good cell: 0 cells
Send idle cell: 25099462530 cells
Receive idle cell: 0 cells
Receive corrected cell: 0
Receive uncorrected cell: 97
Dropped receive cell: 0 cells
Last dropped receive cell connection: 0/0
Last 30 seconds input rate: 0 bits/sec, 0 Packets/sec
Last 30 seconds output rate: 0 bits/sec, 0 Packets/sec
Input: 0 Bytes, 0 Packets
Output: 0 Bytes, 0 Packets
# Run the display interface brief [ | { begin | include | exclude } regular-expression ] command.
If the brief information about the ATM interface, such as the physical status, link protocol status,
bandwidth utilization, and number of error packets, is displayed, it means that the configuration
succeeds. For example:
<HUAWEI> display interface brief | include 1/0/
PHY: Physical
^down: standby
(l): loopback
(s): spoofing
(b): BFD down
(e): EFM down
(d): Dampening Suppressed
Interface
PHY
Protocol
InUti
OutUti
outErrors
Atm1/0/1
up
up
0.08%
0.08%
0
Atm1/0/1.1
up
up
0.03%
0.03%
0
Atm1/0/1.2
up
up
0.03%
0.03%
0
inErrors
0
0
0
3.6.6 Commissioning the Link Layer of a User Interface on an FR

Network
This section describes how to commission the link layer of a user interface on an FR network.
Prerequisite
3-44

Issue 03 (2010-03-31)

Commissioning Guide
Data Preparation
No.
Data
Number of the FR interface
Number of the Multilink Frame Relay (MFR) interface that is formed by bundling
physical links
VC ID assigned to the interface
Number of the FR sub-interface
Procedure
Step 2 Run the interface interface-type interface-number command to enter the interface view.
Step 3 Run the link-protocol fr [ ietf | nonstandard ] command to configure FR as the link layer
protocol of the interface. For details, see A.19 link-protocol fr.
An FR sub-interface can be created only after an FR interface is created.
By default, frames are encapsulated in the IETF format.
NOTE
After the FR encapsulation format on an interface is changed, the system automatically deletes all the
FR configurations on the interface. At this time, you need to delete all the sub-interfaces and reconfigure FR on the interface.
After the configuration of the link layer of the interface is changed, you need to run the shutdown
command to shut down the interface, and then run the undo shutdown command to start the interface
to validate the new configuration.
Step 4 (Optional) Run the fr interface-type { dte |dce } command to set the type of the FR interface
to DTE or DCE. For details, see A.15 fr interface-type.
An FR main interface can be configured with sub-interfaces regardless of whether the interface
type is DTE or DCE.
By default, the type of an FR interface is DTE.
Step 5 Run the quit command to return to the system view.
Step 6 Run the interface interface-type interface-number.subnumber command to create an FR subinterface.
NOTE
The NE80E/40E supports only P2P FR sub-interfaces.
The type of FR sub-interfaces must be the same as the type of the FR main interface.
When an interface is configured with a sub-interface, the interval for consecutively running the
shutdown and undo shutdown commands on the main interface must be 15 seconds or longer.
Step 7 Run the shutdown command to shut down sub-interfaces.

Issue 03 (2010-03-31)

3-45

Commissioning Guide
Before configuring the Data Link Connection Identifier (DLCI) on a sub-interface, you need to
shut down the sub-interface.
Step 8 Run the fr dlci dlci command to configure the DLCI for an FR sub-interface. For details, see
A.14 fr dlci.
FR sub-interfaces must be configured with DLCIs, and the DLCIs of the sub-interfaces at both
ends of a transmission device must be the same.
Step 9 Run the quit command to return to the view of the FR sub-interface.
Step 10 Run the ip address ip-address { mask | mask-length } command to assign an IP address to the
sub-interface.
Step 11 Run the undo shutdown command to start the sub-interface.
----End
# Run the display fr interface command. If information about the interface and the status of the
FR protocol is displayed, it means that the configuration succeeds. For example:
<HUAWEI> display fr interface
Pos1/0/0, DTE, physical up, protocol up
Pos1/0/0.1, point-to-point, protocol up
Pos1/0/0.2, point-to-point, protocol up
# Run the display fr map-info command. If information about the protocol address and address
mapping table is displayed, it means that the configuration succeeds. Address mapping
information is not displayed for P2P sub-interfaces. For example:
<HUAWEI> display fr map-info
Map Statistics for interface Pos2/1/0 (DCE)
DLCI 20, Point-to-Point DLCI, Pos2/1/0.1
created at: 2009/02/12 11:17:37, status: ACTIVE
3.6.7 Commissioning the Power of an Optical Interface

Perform this task to commission the power of an optical interface of the NE80E/40E.
Context
If the output optical power of the SFP optical module on the NE80E/40E is insufficient, packets
may be lost or the communication may be interrupted at the network layer. Therefore, it is
recommended that you measure the optical power of interfaces before using the NE80E/40E.
When measuring the optical power, pay attention to the following points:
3-46
Clean the fiber splice and the optical connector on the panel of the optical interface LPU
and connect them properly.
Do not look strictly into the laser transmitter on the LPU or the fiber splice.
Measure the attenuation of the fiber jumper in advance to ensure accurate location of the
faulty point.
Use different fiber jumpers for single mode and multi-mode optical modules.
Use a calibrated tester (optical power meter).

Issue 03 (2010-03-31)

Commissioning Guide
Procedure
Step 1 Check whether the optical modules at both ends are matched.
NOTE
You can run the display interface interface-type interface-number command to check whether the
maximum transmission distance and the central wavelength of the optical modules at both ends are
consistent. If so, the optical modules are matched.
Step 2 Set the working wavelength of the optical power meter to the wavelength of the tested fiber.
Step 3 Pull out the fiber jumper from the sending interface on the NE80E/40E.
Step 4 Connect one end of the fiber jumper to the sending interface on the NE80E/40E and the other
end to the optical power meter.
Step 5 Record the optical power when the optical power becomes stable.
Step 6 Look up the List of Interface Attributes to check whether the output optical power of the interface
is in the normal range.
NOTE
For the List of Interface Attributes, see the HUAWEI NetEngine80E/40E Hardware Description.
The optical module at the local end is available only when the following conditions are met:
l
The minimum output optical power of the optical module must be greater than the value of the receiver
sensitivity; otherwise, the peer cannot receive the optical signal.
The maximum output optical power of the optical module must be smaller than the overload optical
power; otherwise, the optical module is probably burnt.
----End
3.7 Commissioning the Network Layer

network planning.
3.7.1 Introduction to Commissioning the Network Layer
network planning.
3.7.2 Assigning an IP Address to an Interface
This section describes how to assign an IP address to an interface. To implement Layer 3
interworking between a device and other devices, you need to configure IP addresses for the
interfaces connecting the device to other devices.
3.7.3 Configuring a Static Route
This section describes how to configure a static route. The management network interface does
not participate in dynamic route calculation. Thus, in the scenario where the device to be
commissioned is connected to the NMS through the management network interface, and the IP
address of the management network interface and the IP address of the NMS are not on the same
network segment, you can configure static routes to enable the Layer 3 communication between
the device and the NMS.
3.7.4 Configuring OSPF
You can configure a routing protocol according to the network planning. This section describes
how to configure OSPF.
Issue 03 (2010-03-31)

3-47

Commissioning Guide
3.7.5 Configuring IS-IS

how to configure IS-IS.
3.7.6 Configuring BGP
how to configure BGP.
3.7.7 Connecting a Device to the NMS
This section describes how to connect a device to the NMS. You can connect a device to the
NMS through SNMPv1, SNMPv2c, or SNMPv3. This section describes the three methods to
connect a device to the NMS.
3.7.1 Introduction to Commissioning the Network Layer

network planning.
Figure 3-5 Networking diagram in out-band management mode
NMS
Network
NMS
192.167.1.10 / 24
Router A
192.168.1.1 / 24
Console
GE0/0/0
PC
NE
GE1/0/0
192.168.1.2 / 24
Switch
GE0/0/0
192.168.1.3 / 24
Router B
Figure 3-5 shows the networking in out-band management mode. The commissioned device
accesses the Layer 3 network through the management network interface GE 0/0/0. As the
management network interface cannot participate in dynamic routing calculation, if the IP
addresses of the management network interface and the NMS server are not in the same network
segment, you can configure static routes. For details, see 3.7.3 Configuring a Static Route.
The IP addresses of all interfaces are shown in Figure 3-5.
3-48

Issue 03 (2010-03-31)

Commissioning Guide
Figure 3-6 Networking diagram in in-band management mode (a Layer 3 interface accessing
the NMS)
NMS
Network
NMS
192.167.1.10 / 24
Router B
GE1/0/1
192.167.2.2 / 24
GE1/0/1
192.167.2.1 / 24
192.168.1.1 / 24
Console
POS1/0/0
PC
NE
POS2/0/0
192.168.1.2 / 24
Router A
Figure 3-6 shows the networking in in-band management mode. The commissioned device
accesses the network through a Layer 3 interface POS 1/0/0. You can implement the commission
by configuring dynamic routes to make the management channel between the device and the
NMS server routable.
You can configure dynamic routes through the methods provided in 3.7.4 Configuring OSPF
and 3.7.5 Configuring IS-IS according to the network service planning. In addition, 3.7.3
Configuring a Static Route is acceptable.
Figure 3-7 Networking diagram in in-band management mode (a Layer 2 interface accessing
the NMS)
NMS
Network
NMS
192.167.1.10 / 24
Router B
GE2/0/0
VLANIF100
192.168.1.1 / 24
Console
VLAN 100
PC
Issue 03 (2010-03-31)
NE
GE1/0/1
192.167.2.2 / 24
GE1/0/1
192.167.2.1 / 24
Router A
GE2/0/0
VLANIF100
192.168.1.2 / 24

3-49

Commissioning Guide
Figure 3-7 shows the networking in in-band management mode. The commissioned device
accesses the network through a Layer 2 interface. You can switch a Layer 3 Ethernet interface
to a Layer 2 Ethernet interface, and then add the Layer 2 Ethernet interface to a VLAN and create
a VLANIF interface.
You can configure dynamic routes through the methods provided in 3.7.4 Configuring OSPF
and 3.7.5 Configuring IS-IS according to the network service planning. In addition, 3.7.3
Configuring a Static Route is acceptable.

This section describes how to assign an IP address to an interface. To implement Layer 3
interworking between a device and other devices, you need to configure IP addresses for the
interfaces connecting the device to other devices.
Prerequisite
3-50

Issue 03 (2010-03-31)

Commissioning Guide
Data Preparation
Table 3-8 Data Preparation
Item
Data
Interface name
In the scenario in out-band

management mode as
shown in Figure 3-5, you
need to assign an IP
address to the
management network
interface GE 0/0/0.
In the scenario in in-band

management mode (a
Layer 3 interface
accessing the NMS) as
address to the service
interface POS 1/0/0.
In the scenario in in-band

management mode (a
Layer 2 interface
accessing the NMS) as
address to the service
interface GE 2/0/0.
Remarks
Before assigning an IP
address to an interface, you
need to confirm the interface
type and the protocol type.
This section describes only
the IP address configuration
of POS interfaces. For the IP
address configuration of
Ethernet interfaces and ATM
interfaces, see the HUAWEI
NetEngine80E/40E Router
Configuration Guide WAN
Access.
NOTE
This section describes how to
assign IP addresses to POS
interfaces and VLANIF
interfaces. Assigning IP
addresses to management
network interfaces and Layer 3
Ethernet interfaces is the same
as assigning IP addresses to
POS interfaces.
Issue 03 (2010-03-31)
ID of the VLAN to which the

interfaces belong
100
This field is applicable only

to the scenario where the
router is connected to the
NMS through a Layer 2
interface.
IP address/mask
192.168.1.1 / 24
The IP address of the

interface is in the same
network segment as the IP
address of the connected
device.

3-51

Commissioning Guide
Procedure
l
If a device is connected to another device through a Layer 3 interface, you can assign an
IP address to the interface according to the following procedure.
# Configure POS 1/0/0 by using the default values of all physical parameters.
[HUAWEI] interface pos 1/0/0
[HUAWEI-Pos1/0/0] undo shutdown
[HUAWEI-Pos1/0/0] ip address 192.168.1.1 24
[HUAWEI-Pos1/0/0] quit
If a device is connected to another device through a Layer 2 interface, you can assign an
IP address to the interface according to the following procedure.
# Assign an IP address to VLANIF 100. Switch the Layer 3 Ethernet interface to a Layer
2 Ethernet interface.
[HUAWEI] interface gigabitethernet 2/0/0
[HUAWEI-GigabitEthernet2/0/0] portswitch
[HUAWEI-GigabitEthernet2/0/0] quit
# Add the interface to VLAN 100.

[HUAWEI] vlan batch 100
[HUAWEI] interface gigabitethernet 2/0/0
[HUAWEI-GigabitEthernet2/0/0] port trunk allow-pass vlan 100
[HUAWEI-GigabitEthernet2/0/0] quit
# Create VLANIF 100 and assign an IP address to VLANIF 100.

[HUAWEI] interface vlanif 100
[HUAWEI-Vlanif100] ip address 192.168.1.1 24
----End
# After the configuration is complete, you can run the display interface interface-type interfacenumber command on NE80E/40E to check whether the configuration is correct.
For example, check whether the status of the interface POS 1/0/0 is correct.
<HUAWEI> display interface pos 1/0/0
POS1/0/0 current state : UP
Description:HUAWEI, Pos6/0/0 Interface
LCP opened, IPCP opened
The Vendor PN is FTRJ8519P1BNL-HW
Port BW: 2.5G, Transceiver max BW: 1G, Transceiver Mode: MultiMode
WaveLength: 850nm, Transmission Distance: 550m
Rx Power: -6.05dBm, Tx Power: -5.76dBm
Flag J0 "NetEngine
"
Flag J1 "NetEngine
"
Flag C2 22(0x16)
SDH alarm:
section layer: none
line
layer: none
path
layer: none
3-52

Issue 03 (2010-03-31)

Commissioning Guide
SDH error:
section layer: B1 0
line
layer: B2 0 REI 1318004
path
layer: B3 0 REI 54250
l
If the physical status of the interface is Up, which indicates that the interface is in the normal
state, you can go on with the subsequent stand-alone commissioning.
If the physical status of the interface is Down, do as follows:

1.
Run the display this command in the interface view on the local and peer devices to
view whether the interfaces are shut down.
2.
Run the undo shutdown command and then the display this interface command in
the interface view to check whether the interface is in the Up state.
3.
For a non-Ethernet interface, perform 5.

Check whether the rate and duplex mode are configured on the peer device.
4.
Configure the rate and duplex mode on the interface of the NE80E/40E according to
the rate and duplex mode configured on the peer device. Then, run the display this
interface command to check whether the interface is in the Up state.
Reference commands:
Using the duplex { full | half | auto } command sets the half-duplex mode for an
Ethernet interface.
Using the speed { 10 | 100 | 1000 | auto } } command sets the operation rate of an
Ethernet interface.

5.
For an electrical interface, perform 7.

Check whether the optical modules on the interfaces of the local and peer devices are
matched, for example, whether the wavelengths or optical powers are matched.
NOTE
For details on how to check the optical power of an optical interface, see 3.6.7 Commissioning
the Power of an Optical Interface.
6.
Replace the optical module with a matched one, and then run the display this
interface command to check whether the interface is in the Up state.
Issue 03 (2010-03-31)

3-53

Commissioning Guide
7.
Replace network cables or optical fibers, and then run the display this interface
command to check whether the interface is in the Up state.
8.
Run the display trapbuffer command to check whether alarms of interfaces are
generated.
9.
Deal with the alarms according to the Alarm Reference.
10. Contact Huawei technical support personnel.

11. End
# Ping the peer on NE80E/40E to check whether the ping succeeds.
<HUAWEI> ping 192.168.1.2
PING 192.168.1.2: 56 data bytes, press CTRL_C to break
Reply from 192.168.1.2: bytes=56 Sequence=1 ttl=255 time=2 ms
--- 192.168.1.2 ping statistics --5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/23/113 ms
3.7.3 Configuring a Static Route

This section describes how to configure a static route. The management network interface does
not participate in dynamic route calculation. Thus, in the scenario where the device to be
commissioned is connected to the NMS through the management network interface, and the IP
address of the management network interface and the IP address of the NMS are not on the same
network segment, you can configure static routes to enable the Layer 3 communication between
the device and the NMS.
Prerequisite
3-54

Issue 03 (2010-03-31)

Commissioning Guide
Figure 3-8 Networking for applying out-band NMS
NMS
Network
NMS
192.167.1.10 / 24
Router A
192.168.1.1 / 24
Console
GE0/0/0
NE
PC
GE1/0/0
192.168.1.2 / 24
Switch
GE0/0/0
192.168.1.3 / 24
Router B
As shown in Figure 3-8, the NE80E/40E to be commissioned is connected to the NMS through
the management network interface GE 0/0/0. The IP address of the management network
interface and the IP address of the NMS are not on the same network segment.
The management network interface does not participate in dynamic route calculation. Thus, you
need to configure static routes to enable the Layer 3 communication between the NE80E/40E
and the NMS.
Procedure
Step 1 Configure a static route on the NE80E/40E to be commissioned.
[HUAWEI] ip route-static 192.167.1.10 24 gigabitethernet 0/0/0 192.168.1.2
----End
# After the configuration is complete, run the display ip routing-table command on NE80E/
40E to check whether there is a static route in the routing table.
<HUAWEI> display ip routing-table
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 9
Routes : 9
Destination/Mask
Proto
1.1.1.1/32 Direct
192.168.1.0/24 Direct
100.1.1.200/32 Direct
100.1.1.255/32 Direct
Issue 03 (2010-03-31)
Pre
Cost
Flags NextHop
0
0
0
0
D
D
127.0.0.1
192.168.1.1
InLoopBack0
0
0
0
0
D
D
127.0.0.1
127.0.0.1
InLoopBack0
InLoopBack0

Interface
3-55

Commissioning Guide
127.0.0.0/8
Direct 0
0
127.0.0.1/32 Direct 0
0
127.255.255.255/32 Direct 0
0
192.167.1.0/24 Static 60
0
255.255.255.255/32 Direct 0
0
D
D
D
D
127.0.0.1
127.0.0.1
127.0.0.1
D 192.168.1.2
127.0.0.1
InLoopBack0
InLoopBack0
InLoopBack0
InLoopBack0
# Run the ping command on NE80E/40E to verify the connectivity.

<HUAWEI> ping 192.167.1.10
Reply from 192.167.1.10: bytes=56 Sequence=1 ttl=254
time=60
time=65
time=36
time=93
time=23
ms
ms
ms
ms
ms

0.00% packet loss
3.7.4 Configuring OSPF

how to configure OSPF.
Prerequisite
l
Data Preparation
Figure 3-9 Networking diagram of configuring OSPF
NMS
Network
NMS
192.167.1.10 / 24
Router B
GE1/0/1
192.167.2.2 / 24
192.168.1.1 / 24
Console
POS1/0/0
PC
3-56
NE
GE1/0/1
192.167.2.1 / 24
POS2/0/0
192.168.1.2 / 24
Router A

Issue 03 (2010-03-31)

Commissioning Guide
Item
Data
Remarks
Router ID of NE80E/40E
1.1.1.1
Router IDs need to be

configured according to the
networking plan.
Router ID of RouterA
2.2.2.2
Router IDs need to be

configured according to the
networking plan.
OSPF process ID
By default, the OSPF process

ID is 1.
Area to which an interface

belongs
A network segment can

belong to only one OSPF
area.
Procedure
Step 1 Enable OSPF and enter the OSPF view.
# Configure NE80E/40E.
[HUAWEI] router id 1.1.1.1
[HUAWEI] ospf
# Configure RouterA.
[HUAWEI] router id 2.2.2.2
[HUAWEI] ospf
Step 2 Enter the OSPF area view of an interface and configure the network segments contained in the
area.
NOTE
OSPF can run on the interface only when the following conditions are met:
l
The IP address mask length of the interface is equal to or longer than the mask length specified in the
network command.
The primary IP address of the interface must be within the network segment specified by the
network command.
# Run the following command on RouterA and the NE80E/40E.

[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255
[HUAWEI-ospf-1-area-0.0.0.0] quit
----End
Postrequisite
# Use the display ospf peer command on NE80E/40E to view neighbors in each area of OSPF
<HUAWEI> display ospf peer
OSPF Process 1 with Router ID 1.1.1.1
Neighbors
Issue 03 (2010-03-31)

3-57

Commissioning Guide
Area 0.0.0.0
interface 192.168.1.1(POS1/0/0)'s neighbors
Router ID: 2.2.2.2
Address: 192.168.1.2
State: Full Mode:Nbr is Slave Priority: 1
DR: 2.2.2.2 BDR: None
MTU: 0
Dead timer due in 35 sec
Retrans timer interval: 5
Neighbor is up for 00:00:05
Authentication Sequence: [ 0 ]
GR State: Normal
# Ping the remote device on NE80E/40E to check whether the ping succeeds.
<HUAWEI> ping 192.167.1.10
time=60
time=65
time=36
time=93
time=23
ms
ms
ms
ms
ms

0.00% packet loss
3.7.5 Configuring IS-IS

how to configure IS-IS.
Prerequisite
l
Data Preparation
Figure 3-10 Networking diagram of configuring IS-IS
NMS
Network
NMS
192.167.1.10 / 24
Router B
GE1/0/1
192.167.2.2 / 24
192.168.1.1 / 24
Console
POS1/0/0
PC
3-58
NE
GE1/0/1
192.167.2.1 / 24
POS2/0/0
192.168.1.2 / 24
Router A

Issue 03 (2010-03-31)

Commissioning Guide
Item
Data
Remarks
Network entity name of the

NE80E/40E
10.0000.0000.0001.00
The network entity name is in

the format of X
X.XXXX.XXXX.XXXX.00.
Here, XX indicates the area
address; the 12 X in the middle
indicates the system ID of the
router; and 00 in the end
indicates the SEL.
Network entity name of

RouterA
20.0000.0000.0002.00
The network entity name is in

the format of X
X.XXXX.XXXX.XXXX.00.
Here, XX indicates an area
address; the twelve X in the
middle indicates the system ID
of the RouterA; and 00 in the
end indicates the selector
(SEL).
IS-IS process IDs of two

connected devices
By default, the IS-IS process

ID is 1.
Number of the interface on

the router that is connected to
RouterA
POS 1/0/0
None.
Level of RouterA and the

router
Level of NE80E/40E is
Level-2
Level of RouterA is
Level-1-2
There are three levels, namely,

level-1, level-1-2, and level-2.
It is recommended that the
level be set to level-2 for later
expansion.
Procedure
Step 1 On RouterA and the NE80E/40E, start the IS-IS process and enter the IS-IS view.
[HUAWEI] isis 1
Step 2 Specify a network entity name.

[HUAWEI-isis-1] network-entity 20.0000.0000.0002.00
# Configure the NE80E/40E.

[HUAWEI-isis-1] network-entity 10.0000.0000.0001.00
Step 3 Set the level of the NE80E/40E.

# The level of RouterA is the default value level-1-2. Set the level of the NE80E/40E to level-2.
[HUAWEI-isis-1] is-level level-2
[HUAWEI-isis-1] quit
Issue 03 (2010-03-31)

3-59

Commissioning Guide
Step 4 Enable IS-IS on the specified interface.

[HUAWEI-Pos2/0/0] isis enable 1
# Configure the NE80E/40E.

[HUAWEI-Pos1/0/0] isis enable 1
----End
Postrequisite
# After the configuration is complete, run the display isis peer command on NE80E/40E, and
you can view information about the IS-IS neighbors on the device.
<HUAWEI> display isis peer
Peer information for ISIS(1)
System Id
Interface
Circuit Id
State HoldTime Type
PRI
------------------------------------------------------------------------------0000.0000.0001 GigabitEthernet1/0/0 0000.0000.0001.01 Up
24s
L1(L1L2) 64
0000.0000.0001 GigabitEthernet1/0/0 0000.0000.0001.01 Up
24s
L2(L1L2) 64
Total Peer(s): 2
<HUAWEI> ping 192.167.1.10
time=70
time=65
time=64
time=90
time=25
ms
ms
ms
ms
ms

0.00% packet loss
3.7.6 Configuring BGP

how to configure BGP.
Prerequisite
l
Context
As shown in Figure 3-11, BGP is configured to enable the Layer 3 communication between the
device to be commissioned and the NMS. This section only describes how to configure BGP.
3-60

Issue 03 (2010-03-31)

Commissioning Guide
Figure 3-11 Networking for applying in-band NMS
NMS
Network
NMS
192.167.1.10 / 24
Router B
GE1/0/1
192.167.2.2 / 24
192.168.1.1 / 24
Console
POS1/0/0
NE
PC
GE1/0/1
192.167.2.1 / 24
POS2/0/0
192.168.1.2 / 24
Router A
AS 65008
AS 65009
Procedure
Step 1 Configure EBGP.
# Configure NE80E/40E.
[HUAWEI] bgp 65008
[HUAWEI-bgp] router-id 1.1.1.1
[HUAWEI-bgp] peer 192.168.1.2 as-number 65009
[HUAWEI] bgp 65009
[HUAWEI-bgp] router-id 2.2.2.2
[HUAWEI-bgp] peer 192.168.1.1 as-number 65008
Step 2 Configure RouterA to advertise 192.167.0.0/16.

[HUAWEI-bgp] ipv4-family unicast
[HUAWEI-bgp-af-ipv4] network 192.167.0.0 255.255.0.0
Step 3 Configure BGP to import direct routes on NE80E/40E.

[HUAWEI-bgp] ipv4-family unicast
HUAWEI-bgp-af-ipv4] import-route direct
----End
Postrequisite
# After the configuration is complete, run the display bgp peer command on NE80E/40E, and
you can view information about the BGP neighbors on the device.
BGP local router ID : 1.1.1.1
Local AS number : 65008
Issue 03 (2010-03-31)

3-61

Commissioning Guide
Total number of peers : 1
Peers in established state : 1
Peer
AS
MsgRcvd
MsgSent
192.168.1.2
4 65009
274
207
OutQ
Up/Down
State PrefRcv
0 03:07:01 Established
<HUAWEI> ping 192.167.1.10
time=70
time=65
time=64
time=90
time=25
ms
ms
ms
ms
ms

0.00% packet loss
3.7.7 Connecting a Device to the NMS

This section describes how to connect a device to the NMS. You can connect a device to the
NMS through SNMPv1, SNMPv2c, or SNMPv3. This section describes the three methods to
connect a device to the NMS.
Prerequisite
The route between the NE80E/40E and the NMS is reachable.
Data preparation
3-62
Item
Data
Remarks
SNMP version of the NE80E/

40E
V1/V2C/V3
The value can be v1,

v2c, or v3.
IP address of the NMS
192.167.1.10
None.
Parameters of SNMPv1,
including SNMP read and
write community names and
the ACL number.
read community name: comaccess
write community name: mgr
ACL number: 2000
Parameters of SNMPv2c,
including SNMP read and
write community names and
the ACL number.
read community name: comaccess
write community name: mgr
ACL number: 2001
Parameters of SNMPv3,
including SNMP group and
user names and the ACL
number.
SNMP group name: NMS
SNMP user name: John
ACL number: 2002

None.
None.
None.
Issue 03 (2010-03-31)

Commissioning Guide
Procedure
l
Configure SNMPv1.
1.
Configure basic functions of SNMPv1 on the NE80E/40E.

# Configure SNMP version.
[HUAWEI] snmp-agent
[HUAWEI] snmp-agent sys-info version v1
# Set the SNMP community name: the read community name of NE80E/40E is
comaccess and the write community name is mgr. For details, please refer to A.25
snmp-agent community.
[HUAWEI] snmp-agent community read comaccess acl 2000
[HUAWEI] snmp-agent community write mgr acl 2000
2.
Configure access control in SNMPv1. For details, please refer to A.22 rule (ACL
view).
[HUAWEI] acl 2000
3.
Configure trap functions and set the IP address of the trap server to be the IP address
of the NMS, 192.167.1.10.
[HUAWEI] snmp-agent trap enable
[HUAWEI] snmp-agent target-host trap address udp-domain 192.167.1.10
params securityname comaccess v1 private-netmanager
Configure SNMPv2c.
1.
Configure basic functions of SNMPv2c on the NE80E/40E.

[HUAWEI] snmp-agent
[HUAWEI] snmp-agent sys-info version v2c
# Set the SNMP community name: the read community name of NE80E/40E is
comaccess and the write community name is mgr. For details, please refer to A.25
snmp-agent community.
[HUAWEI] snmp-agent community read comaccess acl 2001
[HUAWEI] snmp-agent community write mgr acl 2001
2.
Configure Community-Name-based access control in SNMPv2c. For details, please

refer to A.22 rule (ACL view).
[HUAWEI] acl 2001
3.
of the NMS, 192.167.1.10. For details, please refer to A.26 snmp-agent target-host
trap.
Configure SNMPv3.
1.
Configure basic functions of SNMPv3 on the NE80E/40E

Issue 03 (2010-03-31)

3-63

Commissioning Guide
[HUAWEI] snmp-agent
[HUAWEI] snmp-agent sys-info version v3
2.
Configure User-based access control in SNMPv3.

# Configure an SNMP user group, and the user group name is NMS.
[HUAWEI] snmp-agent group v3 NMS
# Configure user information. For example, Add a user named John to the SNMP
group named Johngroup, with the security level being authentication, the
authentication protocol being HMAC-MD5-96 and the password being hello. For
details, please refer to the command A.28 snmp-agent usm-user.
[HUAWEI] snmp-agent usm-user v3 John Johngroup authentication-mode md5
hello
# Configure a basic ACL. For details, please refer to the command A.22 rule (ACL
view).
[HUAWEI] acl 2002
# Apply the ACL based on the user. For details, please refer to the command A.28
snmp-agent usm-user.
[HUAWEI] snmp-agent usm-user v3 John NMS acl 2002
3.
of the NMS, 192.167.1.10. For details, please refer to the command A.26 snmp-agent
target-host trap.
----End
After the configurations of the NE80E/40E and the NMS are complete, you can access the
NE80E/40E through the NMS.
Install the Huawei iManager N2000 DMS Compound Package on the NM station and configure
SNMP in the network management software.
For configuring and using the iManager N2000 DMS, refer to HUAWEI iManager N2000
DMS - Compound Package User Manual Volume II.
3.8 Saving Configurations

Prerequisite
The software commissioning of a device is complete.
3-64

Issue 03 (2010-03-31)

Commissioning Guide
Data Preparation
Item
Data
Remarks
Configuration file name to be

saved
comm.cfg
None.
Procedure
Step 1 Run the save [ configuration-file ] command in the user view to save the configuration file.
<HUAWEI> save comm.cfg
NOTE
The suffix of the saved configuration file can be .cfg or .zip.
Step 2 Specify the configuration file as the configuration file for the next startup of the device.
<HUAWEI> startup saved-configuration comm.cfg
----End
Postrequisite
None.
Issue 03 (2010-03-31)

3-65

Commissioning Guide
A Appendix
Appendix
A.1 clock (ATM interface view)

A.2 clock (CPOS interface view)
A.3 clock (POS interface view)
A.4 crc (POS interface view)
A.5 display power
A.6 e1 channel-set (CPOS interface view)
A.7 e1 set clock (CPOS interface view)
A.8 e1 set frame-format (CPOS interface view)
A.9 e1 unframed (CPOS interface view)
A.11 flag (atm interface view)
A.12 flag (cpos interface view)
A.13 flag (pos interface view)
A.14 fr dlci
A.15 fr interface-type
A.16 frame-format (ATM OC/STM)
A.17 frame-format (CPOS interface view)
A.18 frame-format (POS interface view)
A.19 link-protocol fr
A.20 link-protocol (POS interface view)
A.21 ppp authentication-mode
A.22 rule (ACL view)
A.23 scramble (ATM interface view)
Issue 03 (2010-03-31)

A-1

Commissioning Guide
A Appendix
A.24 scramble (POS interface view)

A.25 snmp-agent community
A.26 snmp-agent target-host trap
A.27 snmp-agent trap enable
A.28 snmp-agent usm-user
A.29 t1 set clock (CPOS interface view)
A.30 t1 set frame-format (CPOS interface view)
A-2

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
A.1 clock (ATM interface view)

Function
Using the clock command, you can set the clock mode of an ATM interface.
Using the undo clock command, you can restore the default setting.
By default, the clock mode of an ATM interface is master.
Format
clock { master | slave }
undo clock
Parameters
master: sets an ATM interface work in master clock mode.
slave: sets an ATM interface work in slave clock mode.
Views
ATM interface view
Default Level
2: Configuration level
Usage Guidelines
NOTE
Although this command can be applied to ATM main interfaces and sub-interfaces, you can use this
command only in the ATM main interface view. This command cannot be run in the ATM sub-interface
view.
l
As a DCE device, an ATM interface should work in master clock mode.
As a DTE device, an ATM interface should work in slave clock mode.
When the ATM interfaces of two routers are directly connected through the optical fiber
or Wavelength Division Multiplexing (WDM), one end should work in master clock mode
and the other in slave clock mode.
When an ATM interface is connected to an SDH/SONET device, the ATM interface should
work in slave clock mode.
Example
# Set ATM 4/0/0 to work in master clock mode.
[HUAWEI] interface atm 4/0/0
[HUAWEI-Atm4/0/0] clock master
Issue 03 (2010-03-31)

A-3

Commissioning Guide
A Appendix
A.2 clock (CPOS interface view)

Function
Using the clock command, you can set the clock mode of a CPOS interface.
By default, a CPOS interface works in master clock mode.
Format
undo clock
Parameters
master: sets a CPOS interface to work in master clock mode.
slave: sets a CPOS interface to work in slave clock mode.
Views
CPOS interface view
Default Level
Usage Guidelines
When the CPOS interfaces of two routers are directly connected, one end should work in master
clock mode and use internal clock signals, and the other work in slave clock mode and use line
clock signals.
Example
# Set CPOS 1/0/0 to work in master clock mode.
[HUAWEI] controller cpos 1/0/0
[HUAWEI-Cpos1/0/0] clock master
A.3 clock (POS interface view)

Function
Using the clock command, you can set the clock mode of a POS interface.
By default, a POS interface works in the master clock mode.
A-4

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
Format
undo clock
Parameters
master: sets a POS interface to work in master clock mode.
slave: sets a POS interface to work in slave clock mode.
Views
POS interface view
Default Level
Usage Guidelines
When the POS interfaces of two routers are directly connected, one end should work in master
clock mode and use internal clock signals, and the other works in slave clock mode and use line
clock signals.
Example
# Set POS 1/0/0 on the router to work in slave clock mode.
[HUAWEI-Pos1/0/0] clock slave
A.4 crc (POS interface view)

Function
Using the crc command, you can set the length of the CRC field for a POS interface.
Using the undo crc command, you can restore the default setting.
By default, the length of the CRC field is 32 bits.
Format
crc { 16 | 32 }
undo crc
Parameters
16: indicates that the CRC field is 16 bits.
32: indicates that the CRC field is 32 bits.
Issue 03 (2010-03-31)

A-5

Commissioning Guide
A Appendix
Views
POS interface view
Default Level
Usage Guidelines
A POS interface supports the 16-bit and 32-bit CRC.
The length of the CRC field of the local end and remote end must be the same.
Example
# Set the length of the CRC field on POS 1/0/0 to 16 bits.
[HUAWEI-Pos1/0/0] crc 16
A.5 display power

Function
Using thedisplay power command, you can view the status of the power.
Format
display power [{environment-info |manufacture-info}slot slot-id |slot[slot-id]]
Parameters
environment-info: displays the environment information of the specified power that is in
position.
manufacture-info: displays the manufacturing information of the specified power that is in
position.
slot [ slot-id]: displays the power status of the specified LPU that is in position.
Views
All views
Default Level
1: Monitoring level
Usage Guidelines
None
A-6

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
Example
# Display the status of the power.
<HUAWEI>display power
No
Present
mode
State
Num
--------------------------------------------------------------25
No
*
*
1
26
Yes
*
Normal
1
Power monitor cable state:
Plug
Table A-1 Description of the display power command output

Item
Description
No
Indicates the slot number of the power module.
Present
Indicates whether the power module is in the slot.
mode
Indicates the output power mode of the power module:

DC indicates direct current; AC indicates alternating
current.
State
Indicates the status of the power module.
# Display the environment information of the specified power that is in position.

<HUAWEI> display power environment-info slot 17
Info: This power doesn't support to query the own information
# Display the manufacturing information of the specified power that is in position.

<HUAWEI> display power manufacture-info slot 17
Info: This power doesn't support to query the own information
# Display the power status of the specified LPU that is in position.

<HUAWEI> display power slot 4
Slot: 4
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - BOARD POWER:
280W
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
A.6 e1 channel-set (CPOS interface view)

Function
Using the e1 channel-set command, you can bind the timeslots of the E1 channel.
Using the undo e1 channel-set command, you can remove the binding.
Format
e1 e1-number channel-set set-number timeslot-list { ts0 | slot-list [ ts0 ] }
undo e1 e1-number channel-set set-number
Issue 03 (2010-03-31)

A-7

Commissioning Guide
A Appendix
Parameters
e1-number: specifies the E1 channel number of CPOS. The value ranges from 1 to 63.
set-number: specifies the number of the channel-set. The value ranges from 0 to 30.
ts0: is used to bind timeslot 0. After the channel-set set-number timeslot-list ts0 command is
run, timeslot 0 alone is bound to form a synchronous serial interface. After the channel-set setnumber timeslot-list slot-list ts0 command is run, timeslot 0 and the timeslots specified by slotlist are bound together to form a synchronous serial interface.
slots-list: specifies the timeslot number or the timeslot range. The value rages from 1 to 31. It
can be separate timeslot or time ranges. Time slots are separated by ","; while the range is
expressed by "-".
Views
CPOS interface view
Default Level
Usage Guidelines
In channelized mode, timeslot 0 alone can be bound to form a serial interface; timeslots 0 to 31
can also be randomly bound to form one or multiple serial interfaces. In this case, timeslot 0
needs to be specified in the command as the parameter ts0.
Example
# Bind timeslots of the E1 channel 63.
[HUAWEI-Cpos1/0/0] e1 63 channel-set 1 timeslot-list 1-31 tso
# Enter the serial port (generated after the binding) view.

[HUAWEI-Cpos1/0/0] quit
[HUAWEI] interface serial 1/0/0/63:1
[HUAWEI-Serial1/0/0/63:1]
# View the information of the serial interface generated after the binding.
Serial1/0/0/63:1 current state : DOWN
Line protocol current state : DOWN
Description:HUAWEI, HUAWEI Series, Serial1/0/0/63:1 Interface
Derived from Cpos1/0/0 e1 63, Timeslot(s) Used: 1-31, baudrate is 1984000 bps
LCP initial
Physical layer is Packet Over NO-CRC4,clock master, loopback none
CRC: CRC-32
Scramble disabled
Alarm: OOF PAIS
Traffic statistics:
A-8

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix

Table A-2 Description of the display interface serial command output

Item
Description
Serial1/0/0/63:1 current
state
Indicates the current physical status of the serial interface
Line protocol current

state
Issue 03 (2010-03-31)
UP: indicates the normal enabled state.
DOWN: indicates the abnormal state.
Administratively Down: If the administrator uses the

shutdown command on the interface, the state is
Administratively Down.
Indicates the status of the link protocol of the interface:

l
UP: indicates the normal enabled state.
DOWN: indicates the abnormal state.
Description
Indicates the description about the interface. Up to 242 characters

can be entered. It is case sensitive and can be blank spaces. The
description can help the user to get familiar with the interface
function.
The Maximum Transmit

Unit is
As for the serial interface, the default value is 1500 bytes. The
packet larger than the MTU is fragmented before being sent. If
the non-fragmentation is configured, the packet is discarded.
Hold timer is
Indicates the interval for sending the hold packets. If the packet
is not sent out during the life cycle, it is discarded. By default, it
is 10 seconds.
Derived from
Indicates the number of the T3 interface that forms the serial

interface.
Timeslot(s) Used:
Indicates the number of the time slot that forms the serial
interface.
Baudrate is
Indicates the baudrate of the serial interface.
Internet protocol
processing : disabled
Indicates the IP address is not configured on the interface.
Link layer protocol is
Indicates the data link protocol of the interface.
LCP initial
Indicates the initialization of the LCP.
Physical layer is
Indicates the link information on the physical layer.
clock
Indicates the clock mode.
loopback
Indicates the loopback mode.
CRC
Indicates the length of the CRC check word.

A-9

Commissioning Guide
A Appendix
Item
Description
Scramble
Indicates that the scrambling is disabled or enabled.
Last 300 seconds input

rate:
Indicates the rate of the byte and the packet that pass through the
interface in the last 300 seconds.
Last 300 seconds output

rate:
Input
Indicates the total number of the packets and bytes received on

the interface.
Output
Indicates the total number of the packets and bytes sent on the
interface.
shortpacket
Indicates the number of received packets smaller than the

specified minimum packet.
longpacket
Indicates the number of received packets whose size is greater

than the specified maximum packet.
lostpacket
Indicates the number of packets that are dropped on the interface.
overrunpackets
Indicates the number of the received packets that cannot be

processed because the packet-receiving speed is higher than the
forwarding speed.
underrunpackets
Indicates the number of packets that cannot be sent because the

reading-memory speed is lower than the forwarding speed on the
interface.

Function
Using the e1 set clock command, you can set the clock mode of E1.
Using the undo e1 set clock command, you can restore the default setting.
By default, the clock mode of an E1 channel is master.
Format
e1 e1-number set clock { master | slave }
undo e1 e1-number set clock
Parameters
e1-number: specifies the E1 channel number of CPOS. The value ranges from 1 to 63 in integer.
master: indicates the master clock.
slave: indicates the slave clock.
A-10

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
Views
CPOS interface view
Default Level
Usage Guidelines
The clock modes of different E1 channels on the same CPOS port are independent of each other.
NOTE
This command is supported only by the 2 x 155 M CPOS FPIC.
Example
# Set the clock mode of the E1 channel 1 to slave.
[HUAWEI-Cpos1/0/0] e1 1 set clock slave
A.8 e1 set frame-format (CPOS interface view)

Function
Using the e1 set frame-format command, you can configure the frame format of an E1 channel.
Using the undo e1 set frame-format command, you can restore the default setting.
By default, no-CRC4 is used.
Format
e1 e1-number set frame-format { crc4 | no-crc4 }
undo e1 e1-number set frame-format
Parameters
e1-number: specifies the E1 channel number of CPOS. The value ranges from 1 to 63 in integer.
crc4: indicates the frame format is CRC4.
no-crc4: indicates the frame format is no-CRC4.
Views
CPOS interface view
Default Level
Issue 03 (2010-03-31)

A-11

Commissioning Guide
A Appendix
Usage Guidelines
The frame format on the local end must be the same as that on the remote end.
NOTE
Example
# Set the frame format of the E1 channel 1 to CRC4.
[HUAWEI-Cpos1/0/0] e1 1 set frame-format crc4
A.9 e1 unframed (CPOS interface view)

Function
Using the e1 unframed command, you can configure the E1 channel of CPOS to operate in
unframed mode to create a 2.048 Mbit/s synchronous serial interface.
Using the undo e1 unframed command, you can delete the synchronous serial interface.
By default, no synchronous serial interface is created on the CPOS interface.
Format
e1 e1-number unframed
undo e1 e1-number unframed
Parameters
e1-number: specifies the E1 channel number of CPOS. The value is an integer that ranges from
1 to 63.
Views
CPOS interface view
Default Level
Usage Guidelines
When the E1 channel is set to work in unframed mode, the E1 channel does not include frame
control information and cannot be divided into timeslots or perform timeslot binding.
Example
# Configure E1 channel 3 of CPOS 1/0/0 to operate in unframed mode.
A-12

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix

[HUAWEI-Cpos 1/0/0] e1 3 unframed

Function
Using the e3 set clock command, you can set the clock mode of an E3 channel on the CPOS
interface.
Using the undo e3 set clock command, you can cancel the clock mode set for the E3 channel
of the CPOS interface and restore the default settings.
By default, an E3 channel functions as the master clock.
Format
e3 e3-number set clock { master | slave }
undo e3 e3-number set clock
Parameters
e3-number: specifies the sequence number of the E3 channel. The value is an integer that ranges
from 1 to 3.
master: indicates that the E3 channel is set to the master clock.
slave: indicates that the E3 channel is set to the slave clock.
Views
CPOS interface view
Default Level
Usage Guidelines
It is recommended that the clock modes of the E3 channel and the CPOS interface be the same.
Example
# Set the Number 3 E3 channel on CPOS 1/0/0 to the slave clock, which uses the line clock
signal.
[HUAWEI-Cpos1/0/0] e3 3 set clock slave
Issue 03 (2010-03-31)

A-13

Commissioning Guide
A Appendix
A.11 flag (atm interface view)

Function
Using the flag command, you can set the overhead byte of SDH frame.
Using the undo flag command, you can restore the default setting.
Format
flag c2 c2-value
flag j0 { 64byte-or-null-mode j0-value | 16byte-mode j0-value | 1byte-mode j0-value |
peer }
peer }
undo flag
Parameters
c2 c2-value: specifies the path signal label byte, which belongs to the higher-order path overhead.
It indicates the multiplex structure of VC frame and the property of information payload. The
value ranges from 0 to 255.
j0: specifies the regeneration section trace message.
j1: indicates the higher-order VC-N path trace byte, which belongs to higher-order path
overhead. It tests the whether two ports are in the continuous connection.
The values of j0-value and j1-value are different in the following cases:
l
64byte-or-null-mode: It is either a string ranging from 1 to 64 or null.
16byte-mode: it is a string ranging from 1 to 15 characters.
1bbyte-mode: it is an integer ranging from 0 to 255.
peer: specifies the match with the Flag on the peer end.
By default, the value of c2 is 19 (0x13), and the values of j1 and j0 are "NetEngine".
Views
ATM interface view
Default Level
Usage Guidelines
C2 and J1 on the sending end must be the same as that on the receiving end.
A-14

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
J0 can any character in the same carrier network. However, on the border between different
carriers, J0 on the sending end must be the same as that on the receiving end. J0 helps the carrier
to discover the fault early.
Example
# Set the path trace byte j1 of ATM 1/0/0 as the character string HUAWEI.
[HUAWEI-Atm1/0/0] flag j1 16byte-mode HUAWEI
A.12 flag (cpos interface view)

Function
Using the flag command, you can set the overhead byte of SONET or SDH frame.
Using the undo flag command, you can restore the default setting.
Format
flag { j0 { sdh | sonet } j0 | j1 j1 | c2 c2 }
undo flag
Parameters
j0: specifies the regeneration section trace byte. It is used to test the continuous connection of
the two ports on the section level.
j1: specifies the path trace byte. It is a string ranges from 1 to 15 characters. The default is
"NetEngine".
c2: specifies the signal label byte. The value is an integer. The value ranges from 0 to 255. The
default value is 0x02.
sdh: specifies J0 as the 16 bytes.
sonet: specifies J0 as the 1 byte.
j0: specifies the regenerator section trace byte.
l
In the 1-byte mode (sonet), j0 is an integer ranging from 1 to 127. By default, the value
of J0 is 1
In the 16-byte mode (sdh), j0 is a string ranging from 1 to 15. By default, the value of J0
is "NetEngine"
Views
CPOS interface view
Default Level
Issue 03 (2010-03-31)

A-15

Commissioning Guide
A Appendix
Usage Guidelines
SONET or SDH frame has a variety of overhead bytes and can implement Operation and
Maintenance (OAM) such as management of layers on the transmission network. j1, j0 and c2
are mainly used to provide interworking to devices from different countries, areas or
manufacturers.
Example
# Set the path trace byte j1 of CPOS 1/0/0 as the character string HUAWEI.
[HUAWEI-Cpos1/0/0] flag j1 HUAWEI
A.13 flag (pos interface view)

Function
Using the flag command, you can configure the SDH overhead byte.
Using the undo flag command, you can restore the default.
By default, the value of c2 is 22 (0x16).
By default, the value of j0 is "NetEngine".
By default, the value of j1 is "NetEngine".
Format
peer }
peer }
flag c2 c2-value
undo flag
Parameters
j0 j0-value: specifies the regeneration section trace message, which belongs to the section
overhead. It tests the continuity of the connection between two ports on the section level.j1 j1value: indicates the higher-order VC-N path trace byte, which belongs to higher-order path
overhead. It tests the whether two ports are in the continuous connection.
For j0-value and j1-value:
l
64byte-or-null-mode: It is either a string ranging from 1 to 63 or null.
16byte-mode: It is a string ranging from 1 to 15.
1byte-mode: It is a integer ranging from 0 to 255.
peer: specifies the match with the Flag on the peer end.
A-16

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
c2 c2-value: specifies the path signal label byte, which belongs to the higher-order path overhead.
It indicates the multiplex structure of VC frame and the property of information payload.The
value ranges from 0 to 255 in integer.
Views
POS interface view
Default Level
Usage Guidelines
C2 and J1 on the sending end must be the same as that on the receiving end.
The values of J0s on the two ends can be inconsistent in the network of the same carrier. However,
on the border between different carriers, J0 on the sending end must be the same as that on the
receiving end. J0 helps the carrier to discover the fault early.
Example
# Configure the overhead byte J1
[HUAWEI-Pos1/0/0] flag j1 16byte-mode HUAWEI
A.14 fr dlci
Function
Using the fr dlci command, you can configure the VC for an FR interface.
Using the undo fr dlci command, you can remove the configuration.
Format
fr dlci dlci-number
undo fr dlci [ dlci-number ]
Parameters
dlci-number: specifies the VC number allocated for an FR interface. The value ranges from 16
to 1007. If dlci-number is not specified in the undo fr dlci command, all the local DLCIs are
deleted.
Views
FR interface view, FR sub-interface view, MFR interface view
Issue 03 (2010-03-31)

A-17

Commissioning Guide
A Appendix
Default Level
Usage Guidelines
When the FR interface type is DCE or NNI, it is necessary to manually configure the VC for
both a main interface and a sub-interface interface.
When the FR interface type is DTE:
l
If the interface is a main interface, the system automatically determines the VC according
to the peer device.
If the interface is a sub-interface, the VC should be manually specified for the interface at
both DCE and DTE sides.
Example
# Allocate a VC with DLCI 100 for the FR sub-interface Serial 1/0/0:0.1.
[HUAWEI] interface serial 1/0/0:0.1
[HUAWEI-Serial1/0/0:0.1] fr dlci 100
[HUAWEI-fr-dlci-Serial1/0/0:0.1-100]
A.15 fr interface-type
Function
Using the fr interface-type command, you can set the FR interface type.
Using the undo fr interface-type command, you can restore the default type.
By default, the FR interface type is DTE.
Format
fr interface-type { dce | dte | nni }
undo fr interface-type
Parameters
dte, dce and nni: indicates three types of FR interfaces.
Views
FR interface view, MFR interface view
Default Level
A-18

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
Usage Guidelines
In FR, there are two communicating parties:
l
User side: The user side is called DTE.
Network side: The network side is called DCE.
In an FR network, the interface between the FR switches is NNI and works in the NNI mode.
If the device is used for FR switching, the FR interface should operate in the NNI mode or the
DCE mode.
Example
# Set the type of the FR interface Serial 1/0/0:0 as DCE.
[HUAWEI] interface serial 1/0/0:0
[HUAWEI-Serial1/0/0:0] link-protocol fr
[HUAWEI-Serial1/0/0:0] fr interface-type dce
A.16 frame-format (ATM OC/STM)

Function
Using the frame-format command, you can set the frame format of an ATM interface.
By default, SDH is used.
Format
frame-format { sdh | sonet }
Parameters
sdh: indicates the frame format is SDH STM-1.
sonet: indicates the frame format is SONET OC-3.
Views
ATM interface view
Default Level
Usage Guidelines
ATM interface uses SDH frame format when the optical interface is STM-1 . The ATM interface
uses SONET frame format when the interface is OC-3.
The frame format on an ATM interface should be consistent with that on the transmitting device.
Issue 03 (2010-03-31)

A-19

Commissioning Guide
A Appendix
Example
# Set the frame format of an ATM interface as SONET.
[HUAWEI-Atm4/0/0] frame-format sonet
A.17 frame-format (CPOS interface view)

Function
Using the frame-format command, you can set the frame type used by CPOS.
Using the undo frame-format command, you can restore the default setting.
The default frame formats of the CPOS interfaces differ with the difference of hardware:
l
For the CPOS interface that can be channelized to E1 or E3, the default frame format is
SDH.
For the CPOS interface that can be channelized to T1 or T3, the default frame format is
SONET.
Format
undo frame-format
Parameters
sdh: indicates the frame type is SDH.
sonet: indicates the frame type is SONET.
Views
CPOS interface view
Default Level
Usage Guidelines
The frame format of the local end must be the same as that on the remote end.
Example
# Configure the specified CPOS physical port to operate in the SONET mode.
[HUAWEI-Cpos1/0/0] frame-format sonet
A-20

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
A.18 frame-format (POS interface view)

Function
Using the frame-format command, you can set the frame format of a POS interface.
Using the undo frame-format command, you can restore the default setting.
By default, SDH is used.
Format
undo frame-format
Parameters
sdh: indicates the frame format is Synchronous Digital Hierarchy (SDH).
sonet: indicates the frame format is Synchronous Optical Network (SONET).
Views
POS interface view
Default Level
Usage Guidelines
The frame format on the receiving end must be the same as that on the sending end.
Example
# Set the frame format of the POS interface to SDH.
[HUAWEI-Pos1/0/0] frame-format sdh
A.19 link-protocol fr
Function
Using the link-protocol fr command, you can configure the link layer protocol as FR.
By default, the link-layer protocol encapsulated on the interface is PPP. The default FR frame
format is IETF.
Issue 03 (2010-03-31)

A-21

Commissioning Guide
A Appendix
Format
link-protocol fr [ ietf | nonstandard ]
Parameters
ietf: specifies the IETF standard encapsulation according to the format defined in the RFC1490.
It is the default encapsulation format.
nonstandard: specifies the nonstandard compatible encapsulation format.
Views
FR interface view, MFR interface view
Default Level
Usage Guidelines
To configure the FR network, you must configure the encapsulation protocol of the interfaces
to FR.
NOTE
After the FR encapsulation format of the interface is changed, the system automatically deletes all the FR
configurations on the interface. Then, you need to re-configure the FR.
Example
# Configure the FR encapsulation on Serial 1/0/0:0 and select the nonstandard encapsulation.
[HUAWEI] interface serial 1/0/0:0
[HUAWEI-Serial1/0/0:0] link-protocol fr nonstandard
A.20 link-protocol (POS interface view)

Function
Using the link-protocol command, you can specify the link layer protocol on a POS interface.
By default, PPP is used.
Format
link-protocol { fr [ ietf | nonstandard ] | hdlc | ppp }
Parameters
fr: indicates the link layer protocol is FR.
ietf: indicates the Internet Engineering Task Force (IETF) standard encapsulation. It is
performed according to the format specified in RFC1490. It is the default encapsulation format.
A-22

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
nonstandard: indicates the non-standard compatible encapsulation format.

hdlc: indicates the link layer protocol is HDLC.
ppp: indicates the link layer protocol is PPP.
Views
POS interface view
Default Level
Usage Guidelines
Interface parameters must be configured in the interface view. The protocol related parameters
can be configured only after the correct link layer protocol is configured.
A POS interface supports only the basic functions of FR P2P sub-interfaces instead of other FR
functions.
Example
# Specify HDLC as the link layer protocol for POS 1/0/0.
[HUAWEI-Pos1/0/0] link-protocol hdlc
A.21 ppp authentication-mode

Function
Using the ppp authentication-mode command, you can set the local PPP authentication mode
for the peer router.
Using the undo ppp authentication-mode command, you can remove the authentication. That
is, no authentication is performed.
By default, no authentication is performed.
Format
ppp authentication-mode { chap [ pap ] | pap } [ call-in ]
undo ppp authentication-mode
Parameters
chap: indicates the CHAP authentication.
pap: indicates the PAP authentication.
call-in: authenticates the peer only when the remote user calls in.
Issue 03 (2010-03-31)

A-23

Commissioning Guide
A Appendix
Views
Interface view
Default Level
Usage Guidelines
Using the ppp authentication-mode chap pap command, you can perform the CHAP
authentication first in the LCP negotiation.
If the authenticated part does not support this mode, perform the PAP authentication.
If the authenticated part does not support the two modes, the negotiation fails.
There are two PPP authentication methods:
l
PAP is a 2-way handshake authentication, which sends the password in plain text.
CHAP is a 3-way handshake authentication, which sends the password in encrypted text.
In addition, the pre-defined AAA authentication mode can be used.

Either CHAP or PAP is just an authentication process. The success of the authentication is
decided by AAA, which can perform authentication on the basis of the local authentication
database or an AAA server.
Example
# Authenticate the peer router by PAP on POS 1/0/0.
[HUAWEI-Pos1/0/0] ppp authentication-mode pap
A.22 rule (ACL view)

Function
Using the rule command, you can add a rule in the specified ACL view.
Using the undo rule command, you can delete a rule.
The rule ID is needed when you delete a rule. If you do not know the ID, use the display acl
command to find it out.
Format
# Create or delete a rule in a basic ACL.
rule [ rule-id ] { deny | permit } [ fragment-type fragment-type-name | source { source-ipaddress source-wildcard | any } | time-range time-name | vpn-instance vpn-instance-name ] *
undo rule rule-id [ fragment-type |source | time-range | vpn-instance ] *
# Create or delete a rule in an advanced ACL.
A-24

Issue 03 (2010-03-31)

Commissioning Guide
l
A Appendix
When protocol is TCP or UDP, the command format of the advanced ACL is as follows:
rule [ rule-id ] { deny | permit } protocol [ destination { destination-ip-address destinationwildcard | any } | destination-port operator port | fragment-type fragment-type-name |
source { source-ip-address source-wildcard | any } | source-port operator port | syn-flag synflag | time-range time-name | vpn-instance vpn-instance-name | dscp dscp ] *
rule [ rule-id ] { deny | permit } protocol [ destination { destination-ip-address destinationwildcard | any } | destination-port operator port | fragment-type fragment-type-name |
source { source-ip-address source-wildcard | any } | source-port operator port | syn-flag synflag | time-range time-name | vpn-instance vpn-instance-name | precedence precedence |tos
tos ] *
syn-flag syn-flag is applied only when TCP is specified.
l
When protocol is ICMP, the command format of the advanced ACL is as follows:
rule [ rule-id ] { deny | permit } protocol [ destination { destination-ip-address destinationwildcard | any } | fragment-type fragment-type-name | icmp-type { icmp-name | icmp-type
icmp-code } | source { source-ip-address source-wildcard | any } | time-range time-name |
vpn-instance vpn-instance-name | dscp dscp ] *
rule [ rule-id ] { deny | permit } protocol [ destination { destination-ip-address destinationwildcard | any } | fragment-type fragment-type-name | icmp-type { icmp-name |icmp-type
icmp-code } |source { source-ip-address source-wildcard | any } | time-range time-name | vpninstance vpn-instance-name | precedence precedence | tos tos ] *
l
When protocol is other protocols, the command format of the advanced ACL is as follows:
rule [ rule-id ] { deny | permit } protocol [ destination { destination-ip-address destinationwildcard | any } | fragment-type fragment-type-name | source { source-ip-address sourcewildcard | any } | time-range time-name | vpn-instance vpn-instance-name | dscp dscp ] *
rule [ rule-id ] { deny | permit } protocol [ destination { destination-ip-address destinationwildcard | any } | fragment-type fragment-type-name | source { source-ip-address sourcewildcard | any } | time-range time-name | vpn-instance vpn-instance-name | precedence
precedence | tos tos ] *
l
Deleting rules in the advanced ACL
undo rule rule-id [ destination | destination-port | dscp | fragment-type fragment-typename | icmp-type | precedence | source | source-port | time-range | vpn-instance | tos ] *
# Create or delete a rule in an interface-based ACL.
rule [ rule-id ] { deny | permit } interface { interface-type interface-number | any }
[ logging | time-range time-name ] *
undo rule rule-id [ logging | time-range ] *
# Create or delete a rule of ACL based on the Ethernet frame header.
rule [ rule-id ] { deny | permit } [ type type type-mask | source-mac source-mac sourcemacmask | dest-mac dest-mac destmac-mask ]
undo rule rule-id
# Create or delete a rule of UCL.
Issue 03 (2010-03-31)

A-25

Commissioning Guide
A Appendix
l
When protocol is specified as TCP or UDP

rule [ rule-id ] { deny | permit } protocol source user-group source-group-name
[ destination { any | ip-address { destination-ip-address destination-wildcard | any } } |
destination-port operator port | fragment-type fragment-type-name | logging | sourceport operator port | syn-flag syn-flag | time-range time-name | dscp dscp ] *
destination-port operator port | fragment-type fragment-type-name | logging | sourceport operator port | syn-flag syn-flag | time-range time-name | precedence precedence
| tos tos ] *
syn-flag syn-flag applies to TCP only.
When protocol is specified as ICMP

fragment-type fragment-type-name | icmp-type { icmp-name | icmp-type icmp-code } |
logging | time-range time-name | dscp dscp ] *
fragment-type fragment-type-name | icmp-type { icmp-name | icmp-type icmp-code } |
logging | time-range time-name | precedence precedence | tos tos ] *
When protocol is specified as other protocol except TCP, UDP or ICMP

fragment-type fragment-type-name } | logging | time-range time-name | dscp dscp ] *
fragment-type fragment-type-name } | logging | time-range time-name | precedence
precedence | tos tos ] *
# Delete a rule of UCL.

undo rule rule-id [ destination | destination-port | dscp | fragment-type fragment-type
| icmp-type | logging | precedence | source | source-port | time-range | tos ] *
Parameters
Use the rule command to add a rule. Parameters are describes as follows
rule-id: specifies the number of an ACL rule. The value ranges from 0 to 4294967294.
l
If the rule corresponding to the ACL number exists, the new rule overwrites the old one.
If the rule corresponding to the ACL number does not exist, create new rule for the ACL
number and order the rules based on the ACL number.
If the ACL number is not specified, the system automatically assigns one when you create
a new rule. The number is in an order from a bigger value to a smaller value. The system
automatically reserves a certain range between two ACL rules. The step command is used
to define the range.
NOTE
The rule ID automatically generated by the system begins with the step value so that a new rule can be
inserted in front of the first rule. For instance, if the step value is 5, the rule ID begins with 5 and if the step
value is 2, the rule ID begins with 2.
A-26

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
deny: discards the packets that match the rule.

permit: permits the packets that match the rule.
NOTE
The default action defined in the ACL rule is deny. Therefore, to allow the subsequent flows to pass, you
need to specify the action in the ACL rule to permit.
protocol: specifies the protocol type over IP. It can be an integer ranging from 1 to 255 or a
character string, such as gre,icmp, igmp, ip, ipinip, ospf, tcp and udp.
The combination of parameters used varies with the protocol type. For example, both TCP and
UDP use the parameter [ source-port operator port ] [ destination-port operator port ], but
the other protocols do not.
destination: indicates the destination address information of an ACL rule. It is optional. If it is
not configured, it indicates that any destination address matches.
destination-ip-address: specifies the destination IP address of a packet in dotted decimal format.
The parameter any represents any destination address.
destination-wildcard: specifies the destination address wildcard in dotted decimal format. The
destination address wildcard can be 0.0.0.0, indicating that the destination address is a host
address.
destination-port: indicates the destination port information of UDP or TCP packets, optional,
valid in UDP or TCP. If it is not specified, it indicates any destination port information of TCP/
UDP packets matches.
operator: compares the port operators of source or destination address. Their names and
meanings are as follows: lt (lower than), gt (greater than), eq (equal to), and range (between).
If the operator is range, two port numbers should follow it. Others only need one port number.
port: specifies the port number of TCP or UDP. It is expressed by name or number. The number
ranges from 0 to 65535. For the usage of the mnemonic, refer to the chapter "ACL Configuration"
in the HUAWEI NetEngine80E/40E Router Configuration Guide - IP Services.
dscp dscp: specifies the value of Differentiated Services CodePoint. The value ranges from 0 to
63.
fragment-type fragment-type-name: indicates that this rule is only valid for the non-first
fragment packets.fragment-type-name includes:
l
fragment: checks the fragment packets
fragment-spe-first: checks the first fragment packet
fragment-subseq: checks the following fragment packets
non-fragment: checks non-fragment packets
non-subseq: checks the first fragment packet or non-fragment packets
interface-type interface-number: specifies the interface. If "any" is specified, it indicates all

interfaces.
logging: indicates whether to log the matched packets, optional. The log contents include
sequence number of ACL rules, packets passed or discarded, upper layer protocol type over IP,
source/destination addresses, source/destination port numbers, and number of packets.
precedence precedence: filters packets according to precedence field. It is optional. The value
is a number ranges from 0 to 7 or a name.
Issue 03 (2010-03-31)

A-27

Commissioning Guide
A Appendix
source: indicates the source address information of an ACL rule, optional. If it is not configured,
it indicates that any source address matches.
source-ip-address: specifies the source IP address of a data packet in dotted decimal format. The
parameter any represents the source address 0.0.0.0 with the wildcard 255.255.255.255.
source-wildcard: specifies the source address wildcard in dotted decimal format. The source
address wildcard can be 0.0.0.0, indicating that the source address is a host address.
time-range time-name: specify a time range of the rule of an ACL.
source-port: indicates the source port information of UDP or TCP packets. It is optional, and
valid in UDP or TCP. If it is not specified, it indicates any source port information of TCP/UDP
packets matches.
tos: filters packets based on the service type field. It is optional.
tos: filters packets according to type of service, optional. It can be an integer ranging from 0 to
15 or a name such as normal, min-monetary-cost, max-reliability, max-throughput, and mindelay.
vpn-instance vpn-instance-name: This parameter is optional. It indicates that packets are filtered
based on the names of VPN instances. If the inbound interface is bound to a VPN, vpn-instancename must be specified in the ACL rule so that users can log in to the device.
icmp-type: indicates the ICMP packet type and ICMP message code, optional, only valid in
ICMP. If it is not configured, it indicates any ICMP packet matches.
icmp-name: filters ICMP packets according to the ICMP message name.
icmp-type: filters ICMP packets according to the ICMP message type. The value ranges from 0
to 255.
icmp-code: filters ICMP packets according to the message code. The value ranges from 0 to 255.
Table A-3 Relationship between icmp-name, icmp-type and icmp-code
A-28
icmp-name
icmp-type
icmp-code
Echo
Echo-reply
Parameter-problem
12
Port-unreachable
Protocol-unreachable
Reassembly-timeout
11
Source-quench
Source-route-failed
Timestamp-reply
14
Timestamp-request
13
Ttl-exceeded
11

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
icmp-name
icmp-type
icmp-code
Fragmentneed-DFset
Host-redirect
Host-tos-redirect
Host-unreachable
Information-reply
16
Information-request
15
Net-redirect
Net-tos-redirect
Net-unreachable
# Use the undo rule command to delete a rule. Parameters are described as follows:
rule-id: specifies the ID of an ACL rule. It should be ACL number containing rules. If the
parameter after rule-id is not specified, this ACL rule is deleted completely; otherwise, only the
partial information of this rule is deleted.
source: This parameter is optional, indicating that only the information about the source IP of
specified ACL rule is deleted.
destination: This parameter is optional, indicating that only the information about the
destination IP of specified ACL rule is deleted.
source-port: This parameter is optional, indicating that only the information about the source
port of specified ACL rule is deleted. This parameter is valid only when the protocol type of the
rule is TCP or UDP.
destination-port: This parameter is optional, indicating that only the information about the
destination port of specified ACL rule is deleted. This parameter is valid only when the protocol
type of the rule is TCP or UDP.
precedence: This parameter is optional, indicating that the information about precedence of the
specified rule is deleted.
tos: deletes the tos configuration of the specified rule. This parameter is optional.
time-range: deletes the time range configuration of the specified rule. This parameter is optional.
logging: deletes the logging configuration of the specified rule. This parameter is optional.
fragment-type: deletes the fragment configuration of the specified rule. This parameter is
optional.
icmp-type: This parameter is optional. The ACL rule that contains the settings of the specified
type of ICMP messages and message codes is deleted.
Views
The first group of commands is used in the basic ACL view.
Issue 03 (2010-03-31)

A-29

Commissioning Guide
A Appendix
The second group of commands is used in the advanced ACL view.

The third group of commands is used in the interface-based ACL view.
The fourth group of commands is used in the view of the ACL based on the Ethernet frame
header.
The fifth group of commands is used in the view of the UCL.
Default Level
Usage Guidelines
Different applications require differentiated configurations about the ACL rules. ACL rules may
vary with types of routing protocols.
Example
# Create an ACL 3101 and add a rule to prohibit receiving or sending of RIP packets.
[HUAWEI] acl number 3101
[HUAWEI-acl-adv-3101] rule deny udp destination-port eq rip
# Add a rule to permit hosts at 129.9.0.0 to send WWW packets to hosts at 202.38.160.0.
[HUAWEI-acl-adv-3101] rule permit tcp source 129.9.0.0 0.0.255.255 destination
202.38.160.0 0.0.0.255 destination-port eq www
# Add a rule to prohibit all hosts from establishing Telnet (23) connection to the host with the
IP address 202.38.160.1.
[HUAWEI-acl-adv-3101] rule deny tcp destination 202.38.160.1 0 destination-port eq
telnet
# Add a rule to prohibit creating UDP connections with the port number greater than 128 from
the host in network segment 129.9.8.0 to the host in network segment 202.38.160.0.
[HUAWEI-acl-adv-3101] rule deny udp source 129.9.8.0 0.0.0.255 destination
202.38.160.0 0.0.0.255 destination-port gt 128
A.23 scramble (ATM interface view)

Function
Using the scramble command, you can enable the payload scrambling on an ATM interface.
Using the undo scramble command, you can disable the scrambling.
By default, the scrambling of an ATM interface is enabled.
Format
scramble
undo scramble
A-30

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
Parameters
None
Views
ATM interface view
Default Level
Usage Guidelines
The scramble command scrambles and descrambles only the payload, and exerts no influence
on the cell header.
The scrambling can effectively avoid continuous "0"s or "1"s.
Uniform configuration at two ends when configuring the scrambling.
Example
# Disable the scrambling of the ATM interface.
[HUAWEI-Atm4/0/0] undo scramble
A.24 scramble (POS interface view)

Function
Using the scramble command, you can enable the payload scrambling of a POS interface.
Using the undo scramble command, you can disable the function.
By default, the payload scrambling of a POS interface is enabled.
Format
scramble
undo scramble
Parameters
None
Views
POS interface view
Issue 03 (2010-03-31)

A-31

Commissioning Guide
A Appendix
Default Level
Usage Guidelines
The scrambling mode on the receiving end must be consistent with that on the sending end.
Example
# Disable the scrambling of the payload on the POS interface.
[HUAWEI-Pos1/0/0] undo scramble
A.25 snmp-agent community

Function
Using the snmp-agent community command, you can set the community access name of
SNMPv1 and SNMPv2C,
Using the undo snmp-agent community command, you can cancel the setting.
Format
snmp-agent community { read | write } { community-name | cipher community-name } [ mibview view-name | acl acl-number ] *
undo snmp-agent community community-name
Parameters
read: indicates that the community name has the read-only authority in the specified view.
write: indicates that the community name has the read and write authority in the specified view.
community-name: specifies the character string of community name. The value is in the range
of 1 to 32 characters.
cipher community-name: indicates the community name in cipher text. The value is in the range
of 1 to 32 characters.
mib-view view-name: sets the MIB view names that the community name can have access to.
The value is in the range of 1 to 32 characters.
acl acl-number: sets the ACL corresponding to the community name. The value is in the range
of 2000 to 2999.
Views
System view
A-32

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
Default Level
Usage Guidelines
Using the snmp-agent community command, you can set the read and write authority of the
community name in the MIB view as to control the user access to the MIB view.
An SNMP community name can be set to either a plain-text name or a cipher-text name.
Example
# Set the community name as comaccess and allow read-only access using this community name.
[HUAWEI] snmp-agent community read comaccess
# Set the community name to mgr and allow read and write access.
[HUAWEI] snmp-agent community write mgr
# Set the community name to be a cipher-text name that can be read only.
[HUAWEI] snmp-agent community read cipher public
A.26 snmp-agent target-host trap

Function
Using the snmp-agent target-host trap command, you can set the destination host that receives
the SNMP notification.
Using the undo snmp-agent target-host command, you can remove the host that receives the
SNMP messages.
Format
snmp-agent target-host trap [ ipv6 ] address udp-domain ip-address [ udp-port portnumber ] [ vpn-instance vpn-instance-name ] params securityname security-string [ v1 |
v2c | v3 [ authentication | privacy ] ]
undo snmp-agent target-host ip-address securityname security-string [ vpn-instance vpninstance-name ]
Parameters
address: specifies the address of the destination host that receives the SNMP message.
udp-domain: specifies that the transmission domain of the destination host is based on UDP.
ip-address: specifies the IP address of the host.
udp-port port-number: specifies the number of the port that receives the trap packet. The value
is in the range of 0 to 65535. By default, it is 162.
vpn-instance vpn-instance-name: indicates the name of a VPN instance. It is in the range of 1
to31 characters.
Issue 03 (2010-03-31)

A-33

Commissioning Guide
A Appendix
params: indicates the information of the login host that generates SNMP messages.
securityname security-string: specifies the community name of SNMPv1, SNMPv2C or the
user name of SNMPv3. The value is in the range of 1 to 32 bytes.
v1 | v2c | v3: specifies the version of alarm messages. By default, it is v1.
authentication: authenticates but not encrypts the packet.
privacy: authenticates and encrypts the packet.
private-netmanager: sets the Huawei NMS to receive alarm messages. After the Huawei NMS
is used, the alarm message sent to the Huawei NMS can contain more detailed information, such
as the alarm type, alarm ID, and send time of the alarm message.
Views
System view
Default Level
Usage Guidelines
Use this command to specify the destination host that receives the alarm messages.
l
Using the snmp-agent trap enable command, you can enable the device to send alarm
messages. To enable a host to send notifications, you need to run the snmp-agent targethost command and the A.27 snmp-agent trap enable command on the host.
In the situation that SNMP alarm is enabled, to enable SNMPv3 to send alarm messages
normally, you need to ensure that the user name in the securityname command is added
to the corresponding group and the notification view is configured in the group.
Example
# Configure the Huawei NMS as the destination host for alarm messages.
[HUAWEI] snmp-agent target-host trap address udp-domain 10.1.1.1 params
securityname comaccess v2c private-netmanager
A.27 snmp-agent trap enable

Function
Using the snmp-agent trap enable command, you can enable the device to send trap packets
and set the related trap parameters.
Using the undo snmp-agent trap enable command, you can cancel the current setting.
By default, sending trap packets is disabled.
Format
snmp-agent trap enable [ trap-type [ trap-list ] ]
A-34

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
undo snmp-agent trap enable [ trap-type [ trap-list ] ]
Parameters
trap-type: enables a specified type of trap packets.
trap-list: specifies the parameter list corresponding to the specified type of trap packets.
Views
System view
Default Level
Usage Guidelines
If no parameter is specified in the snmp-agent trap enable command, it indicates allowing all
the modules to send any type of SNMP trap packets.
The snmp-agent trap enable command should be used together with the snmp-agent targethost command.
The snmp-agent target-host command applies to specify the destination host of the trap packet.
In the NE80E/40E system, alarms generated by the interface-name-change, port and
standard are enabled through the snmp-agent trap enable command.
Example
# Allow sending the trap packets notifying failing SNMP authentication to 10.1.1.1. The trap
packets are in the form of v2c with the security name as public.
[HUAWEI] snmp-agent trap enable standard authentication
[HUAWEI] snmp-agent target-host trap address udp-domain 10.1.1.1 params
securityname public v2c
A.28 snmp-agent usm-user

Function
Using the snmp-agent usm-user command, you can add a new user to an SNMP group.
Using the undo snmp-agent usm-user command, you can delete an SNMP group user.
Format
snmp-agent usm-user v3 user-name group-name [ authentication-mode { md5 | sha }
password [ privacy-mode des56 password ] ] [ acl acl-number ]
undo snmp-agent usm-user v3 user-name group-name { engineid engineid-string | local }
Issue 03 (2010-03-31)

A-35

Commissioning Guide
A Appendix
Parameters
v3: specifies the V3 security mode the user uses.
user-name: specifies the user name. It is a string of 1 to 32 characters.
group-name: specifies the name of the group the user belongs to. It is a string of 1 to 32 characters.
authentication-mode: specifies the authentication mode.
md5: specifies the authentication protocol as HMAC-MD5-96.
sha: specifies the authentication protocol as HMAC-SHA-96.
privacy-mode: specifies the encryption mode.
des56: specifies the encryption protocol as DES.
password: specifies the authentication password. It is a string of 1 to 64 characters.
acl: sets the ACL for the access view.
acl-number: specifies the basic ACL. The value is in the range of 2000 to 2999.
engineid: specifies the engine ID associated with the user.
engineid-string: specifies the character string of the engine ID. It is in the range of 10 to 64
characters.
local: indicates the local entity user.
Views
System view
Default Level
Usage Guidelines
After a remote user is configured for the agent, when the agent communicates with the remote
user, engineID is used for verification. If the engine ID changes after the user is configured, the
user corresponding to the original engine ID becomes ineffective.
Example
# Add a user named John to the SNMP group named Johngroup, with the security level being
authentication, the authentication protocol being HMAC-MD5-96 and the password being hello.
[HUAWEI] snmp-agent usm-user v3 John Johngroup authentication-mode md5 hello

Function
Using the t1 set clock command, you can set the clock mode of a T1 channel.
A-36

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
Using the undo t1 set clock command, you can restore the default setting.
By default, the clock mode of the T1 channel is master.
Format
t1 t1-number set clock { master | slave }
undo t1 t1-number set clock
Parameters
t1-number: specifies the T1 channel number. The value ranges from 1 to 84 in integer.
master: indicates the master clock.
slave: indicates the slave clock.
Views
CPOS interface view
Default Level
Usage Guidelines
The clock modes of the different T1 channels of the same CPOS interface are independent from
each other.
NOTE
Example
# Configure T1 channel 1 to use the slave clock mode.
[HUAWEI-Cpos1/0/0] t1 1 set clock slave
A.30 t1 set frame-format (CPOS interface view)

Function
Using the t1 set frame-format command, you can configure the frame format of a T1 channel.
Using the undo t1 set frame-format command, you can restore the default setting.
By default, the frame format of a T1 channel is ESF.
Format
t1 t1-number set frame-format { esf | sf }
Issue 03 (2010-03-31)

A-37

Commissioning Guide
A Appendix
undo t1 t1-number set frame-format
Parameters
t1-number: specifies the T1 channel number. The value ranges from 1 to 84.
esf: indicates the ESF format.
sf: indicates the SF format.
Views
CPOS interface view
Default Level
Usage Guidelines
The frame format on the local end must be the same as that on the remote end.
Example
# Configure the frame format of T1 channel 1 as SF.
[HUAWEI-Cpos1/0/0] t1 1 set frame-format sf

Function
Using the t3 set clock command, you can configure the clock mode of the T3 channel on the
CPOS interface.
Using the undo t3 set clock command, you can restore the default configuration.
By default, the T3 channel is set as the master clock mode.
Format
t3 t3-number set clock { master | slave }
undo t3 t3-number set clock
Parameters
t3-number: specifies the sequence number of the T3 channel. The value is an integer that ranges
from 1 to 3.
master: indicates that the T3 channel is set as the master clock.
slave: indicates that the T3 channel is set as the slave clock.
A-38

Issue 03 (2010-03-31)

Commissioning Guide
A Appendix
Views
CPOS interface view
Default Level
Usage Guidelines
It is recommended that the clock modes of the T3 channel and the CPOS interface be the same.
Example
# Set the Number 3 T3 channel on the CPOS 1/0/0 as the master clock, which uses the internal
clock signal.
[HUAWEI-Cpos1/0/0] t3 3 set clock master
Issue 03 (2010-03-31)

A-39

Commissioning Guide (V600R001C00 - 03) PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Commissioning Guide (V600R001C00 - 03) PDF

Uploaded by

Copyright:

Available Formats

HUAWEI NetEngine80E/40E Router

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

HUAWEI NetEngine80E/40E Router

About This Document

About This Document

Installation and commissioning engineers

Describes the definition of and procedures for

Describes preparations for commissioning.

Huawei Proprietary and Confidential

HUAWEI NetEngine80E/40E Router

About This Document

Describes the stand-alone commissioning.

Describes the used commands.

Indicates a hazard with a high level of risk, which, if not avoided,

Provides additional information to emphasize or supplement

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in Boldface.

Book titles are in italics.

Terminal display is in Courier New.

Huawei Proprietary and Confidential

HUAWEI NetEngine80E/40E Router

About This Document

The keywords of a command line are in boldface.

The arguments of a command line are in italic.

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

Alternative items are grouped in braces and separated by vertical

Optional alternative items are grouped in square brackets and

Alternative items are grouped in braces and separated by vertical

Optional alternative items are grouped in square brackets and

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

A line starting with the # sign is comments.

Buttons, menus, parameters, tabs, windows, and dialog titles are

Multi-level menus are in boldface and separated by the ">" signs.

Press the keys concurrently. For example, press Ctrl+Alt+A.

Huawei Proprietary and Confidential

HUAWEI NetEngine80E/40E Router

About This Document

Press the primary mouse button twice continuously and quickly

Updates in Issue 03 (2010-03-31)

Updates in Issue 02 (2009-12-10)

Updates in Issue 01 (2009-10-20)

Huawei Proprietary and Confidential

HUAWEI NetEngine80E/40E Router

Huawei Proprietary and Confidential

HUAWEI NetEngine80E/40E Router

3.6.3.3 Configuring the T1 Channel of a CPOS Interface............................................................................3-35

Huawei Proprietary and Confidential

HUAWEI NetEngine80E/40E Router

A.26 snmp-agent target-host trap.......................................................................................................................A-33

Huawei Proprietary and Confidential

HUAWEI NetEngine80E/40E Router

Huawei Proprietary and Confidential

HUAWEI NetEngine80E/40E Router

Huawei Proprietary and Confidential

HUAWEI NetEngine80E/40E Router

Huawei Proprietary and Confidential

HUAWEI NetEngine80E/40E Router