commissioning guide(v600r001c00 03)

HUAWEI NetEngine80E/40E RouterV600R001C00

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 writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

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

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 03 (2010-03-31) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

OverviewThis document describes the basic procedure for and the method of commissioning devices indeployment in terms of hardware, software, connections, services, and maintenance andmanagement. This document serves as a guide to the stable and reliable running of devices ona network.

This document provides the procedure for and the method of commissioning an NE80E/40Edevice.

Product VersionThe following table lists the product version involved in this document.

Product Name Product Version

HUAWEI NetEngine80E/40E V600R001C00

Intended AudienceThis document is intended for:

l Installation and commissioning engineers

OrganizationThis document is organized as follows.

Chapter Description

1 Commissioning Flow Describes the definition of and procedures forcommissioning.

2 Preparations forCommissioning

Describes preparations for commissioning.

HUAWEI NetEngine80E/40E RouterCommissioning Guide About This Document


iii

Chapter Description

3 Basic Commissioning Describes the stand-alone commissioning.

A Appendix Describes the used commands.

Conventions

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

Symbol Description

DANGERIndicates a hazard with a high level of risk, which, if not avoided,will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk which, ifnot avoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation that, if not avoided,could cause device damage, data loss, and performancedegradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or save yourtime.

NOTE Provides additional information to emphasize or supplementimportant points of the main text.

General ConventionsFormat 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.

About This DocumentHUAWEI NetEngine80E/40E Router

Commissioning Guide

iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

Command ConventionsFormat 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 verticalbars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets andseparated by vertical bars. One or none is selected.

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

[ x | y | ... ] * Optional alternative items are grouped in square brackets andseparated 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 ConventionsFormat Description

boldface Buttons, menus, parameters, tabs, windows, and dialog titles arein boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">" signs.For example, choose File > Create > Folder.

Keyboard OperationFormat Description

Key Press the key. For example, press Enter, Tab, Backspace, anda.

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.

HUAWEI NetEngine80E/40E RouterCommissioning Guide About This Document


v

Mouse OperationsFormat Description

Click Select and release the primary mouse button without moving thepointer.

Double-click Press the primary mouse button twice continuously and quicklywithout moving the pointer.

Drag Press and hold the primary mouse button and move the pointerto a certain position.

Update HistoryUpdates between document versions are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

Updates in Issue 03 (2010-03-31)This is the third release.

Updates in Issue 02 (2009-12-10)This is the second release.

Updates in Issue 01 (2009-10-20)This is the first release.

About This DocumentHUAWEI NetEngine80E/40E Router

Commissioning Guide

vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

Contents

About This Document...................................................................................................................iii

1 Commissioning Flow.................................................................................................................1-1

2 Preparations for Commissioning............................................................................................2-12.1 Hardware Preparation......................................................................................................................................2-22.2 Software Preparation.......................................................................................................................................2-22.3 Tool Preparation..............................................................................................................................................2-32.4 Data Preparation..............................................................................................................................................2-4

3 Basic Commissioning................................................................................................................3-13.1 Logging in to a Device Through the Console Interface..................................................................................3-23.2 Checking a Device..........................................................................................................................................3-4

3.2.1 Checking Software Versions..................................................................................................................3-53.2.2 Checking the Health Status of a Device.................................................................................................3-63.2.3 Checking License Files..........................................................................................................................3-63.2.4 Checking the Status of Boards...............................................................................................................3-73.2.5 Checking the Status of the FAN.............................................................................................................3-83.2.6 Checking the Status of the Power..........................................................................................................3-9

3.3 (Optional) Specifying a Device Name............................................................................................................3-93.4 Setting System Time.....................................................................................................................................3-103.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-123.5.2 (Operational) Configuring ACLs to Filter Login Users.......................................................................3-143.5.3 (Optional) Configuring a User to Log in to a Device Through FTP....................................................3-163.5.4 (Optional) Configuring a User to Log in to a Device Through SSH...................................................3-18

3.6 Commissioning the Link Layer.....................................................................................................................3-213.6.1 Commissioning the Link Layer of an Ethernet Interface.....................................................................3-223.6.1.1 Commissioning the Link Layer of an Ethernet Interface on an LPU................................................3-223.6.1.2 Commissioning the Link Layer of an Ethernet Interface on an MPU...............................................3-263.6.1.3 Configuring Layer 2 Parameters for an Ethernet Interface...............................................................3-273.6.2 Commissioning the Link Layer of a POS Interface.............................................................................3-273.6.3 Commissioning the Link Layer of a CPOS Interface..........................................................................3-313.6.3.1 Configuring an STM-1 CPOS Interface............................................................................................3-313.6.3.2 Configuring the E1 Channel of a CPOS Interface............................................................................3-33

HUAWEI NetEngine80E/40E RouterCommissioning Guide Contents


vii

3.6.3.3 Configuring the T1 Channel of a CPOS Interface............................................................................3-353.6.3.4 Configuring the E3 Channel of an STM-1 CPOS Interface..............................................................3-373.6.3.5 Configuring the T3 Channel of an STM-1 CPOS Interface..............................................................3-393.6.4 Commissioning the Link Layer of the E1/T1 Interface.......................................................................3-413.6.5 Commissioning the Link Layer of an ATM Interface..........................................................................3-423.6.6 Commissioning the Link Layer of a User Interface on an FR Network..............................................3-443.6.7 Commissioning the Power of an Optical Interface..............................................................................3-46

3.7 Commissioning the Network Layer..............................................................................................................3-473.7.1 Introduction to Commissioning the Network Layer............................................................................3-483.7.2 Assigning an IP Address to an Interface..............................................................................................3-503.7.3 Configuring a Static Route...................................................................................................................3-543.7.4 Configuring OSPF................................................................................................................................3-563.7.5 Configuring IS-IS.................................................................................................................................3-583.7.6 Configuring BGP..................................................................................................................................3-603.7.7 Connecting a Device to the NMS.........................................................................................................3-62

3.8 Saving Configurations...................................................................................................................................3-64

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

ContentsHUAWEI NetEngine80E/40E Router

Commissioning Guide

viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

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

HUAWEI NetEngine80E/40E RouterCommissioning Guide Contents


ix

Figures

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

HUAWEI NetEngine80E/40E RouterCommissioning Guide Figures


xi

Tables

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

HUAWEI NetEngine80E/40E RouterCommissioning Guide Tables


xiii

1 Commissioning Flow

This chapter describes the basic flow of commissioning the NE80E/40E. Users can thus knowthe entire process of device commissioning in site deployment.

You can follow the procedure to complete the commissioning. This document only describesthe preparations for commissioning and the basic commissioning of NE80E/40E.

HUAWEI NetEngine80E/40E RouterCommissioning Guide 1 Commissioning Flow


1-1

Figure 1-1 Commissioning flow

Hardwarepreparation

Software preparation

Tool preparation

Data preparation

Log in to a devicethrough a console

interface

Configure a user tolog in to a device

remotely

Save configurations

Preparations for thecommissioning Basic commissioning Typical service

commissioning

Commissioning theLink Layer

Commissioning theNetwork Layer

Connect a device tothe NMS

Specify a devicename

Configure systemtime

Check the device

Table 1-1 Introduction to the procedures involved in the commissioning flow

Commissioning Procedure Description

Preparations for Commissioning To ensure that the subsequent commissioningworks well, preparations must be made interms of the hardware, software, tools, anddata.

Basic Commissioning It describes how to commission a singleNE80E/40E after hardware installation iscompleted so that the NE80E/40E can worknormally and users can remotely log in to theNE80E/40E.

1 Commissioning FlowHUAWEI NetEngine80E/40E Router

Commissioning Guide

1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

Commissioning Procedure Description

Typical service commissioning Before typical service commissioning,configuration scripts must be finished. Theconfiguration scripts are written based on theactual networking plan and typicalconfiguration examples.

HUAWEI NetEngine80E/40E RouterCommissioning Guide 1 Commissioning Flow


1-3

2 Preparations for Commissioning

About This Chapter

2.1 Hardware PreparationBefore commissioning, you need to check the power supply and grounding, cables andconnectors, and downstream devices to make sure that all the hardware is ready forcommissioning.

2.2 Software PreparationThis chapter describes the software to be prepared before commissioning.

2.3 Tool PreparationThis chapter describes the tools to be prepared before commissioning.

2.4 Data PreparationInformation about hardware configurations, network topologies, and data planning needs to becollected to prepare for data configurations.

HUAWEI NetEngine80E/40E RouterCommissioning Guide 2 Preparations for Commissioning


2-1

2.1 Hardware PreparationBefore commissioning, you need to check the power supply and grounding, cables andconnectors, and downstream devices to make sure that all the hardware is ready forcommissioning.

Table 2-1 shows the hardware checklist before commissioning.

Table 2-1 Hardware checklist

Item Description

Power supply and grounding l Power cables and grounding cables are connectedproperly and are in good contact.

l Power cables, grounding cables, and power distributionswitches are labeled correctly, clearly, and orderly.

l The external grounding cable of the cabinet andprotection grounding cables are connected properly,without any damage or break.

l Power supply for the device is normal.

Cables and connectors Check the console cables, network cables, optical fibers,and subscriber lines to ensure the following:l Cable connectors are tight and firm.

l Cable jackets are intact.

Downstream devices l Confirm the physical position of the connected interfaceon the peer device.

l The peer device works normally and can be used forcommissioning.

NOTEThe hardware installation engineers have already checked Item 1 and Item 2 listed in Table 2-1. To ensurethe proper and reliable connection of the hardware, you can recheck the preceding items.

2.2 Software PreparationThis 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 Preparations for CommissioningHUAWEI NetEngine80E/40E Router

Commissioning Guide


Issue 03 (2010-03-31)

Table 2-2 Software checklist

Item Description

System softwarepackage

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 purchasea GTL license to obtain authorization of related service modules.

Softwarecommissioning tools

All the software commissioning tools are available. Thecommissioning 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 WindowsOperating System (OS).

l Trivial File Transfer Protocol (TFTP) and File Transfer Protocol(FTP): used for loading software to the NE80E/40E. The tools canbe downloaded from http://support.huawei.com.

2.3 Tool PreparationThis chapter describes the tools to be prepared before commissioning.

Commissioning is performed with the help of tools. Therefore, you need to prepare related toolsin advance to facilitate the subsequent commissioning.

Table 2-3 shows the tool checklist.

Table 2-3 Tool checklist

Item Description

Cables and interfaces Check that cables connecting devices are complete and correct, andinterface types are consistent with cable types according to networkdeployment.l One RS232 serial interface cable: used for logging in to the

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

Ethernet (MEth) interfaces or other services.l Several optical fibers: used for connecting the peer device.

Maintenance terminal A maintenance terminal, generally a laptop, with a HyperTerminalapplication. It is used for logging in to the NE80E/40E tocommission the NE80E/40E.

Auxiliary device andmeter

l Optical power meter: used for checking the actual input power,receiver sensibility, and overload optical power of opticalinterfaces.

l Multimeter: used for measuring the voltage, resistance, andcurrent amperage during power commissioning.

HUAWEI NetEngine80E/40E RouterCommissioning Guide 2 Preparations for Commissioning


2-3

2.4 Data PreparationInformation about hardware configurations, network topologies, and data planning needs to becollected to prepare for data configurations.

Table 2-4 lists the data that needs to be collected.

Table 2-4 Data checklist

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

l IP address allocation

l VLAN division

l Service type and data planning

2 Preparations for CommissioningHUAWEI NetEngine80E/40E Router

Commissioning Guide


Issue 03 (2010-03-31)

3 Basic Commissioning

About This Chapter

3.1 Logging in to a Device Through the Console InterfaceWhen setting up a local configuration environment through the console interface, you can login to the NE80E/40E through the HyperTerminal in Windows on the PC.

3.2 Checking a DeviceYou can check a device to make sure that the current status meets the deployment requirement.

3.3 (Optional) Specifying a Device NameSpecifying a device name according to the networking plan helps to identify and maintain adevice.

3.4 Setting System TimeSetting system time accurately ensures that the NE80E/40E works with other devicescoordinately.

3.5 Configuring a Management User to Remotely Log in to a DeviceThis 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 thecentral equipment room.

3.6 Commissioning the Link LayerThis section describes how to commission the link layer of the Router that connects to otherrouters or transmission devices.

3.7 Commissioning the Network LayerYou can adopt the out-band management mode or in-band management mode according to thenetwork planning.

3.8 Saving Configurations

HUAWEI NetEngine80E/40E RouterCommissioning Guide 3 Basic Commissioning


3-1

3.1 Logging in to a Device Through the Console InterfaceWhen setting up a local configuration environment through the console interface, you can login 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 theNE80E/40E.

For details on the console interface, see HUAWEI NetEngine80E/40E Router - HardwareDescription.

Step 2 Start the HyperTerminal on the PC.

Choose Start > Programs > Accessories > Communications > HyperTerminal to start theHyperTerminal 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 thenselect an icon. Click OK.

3 Basic CommissioningHUAWEI NetEngine80E/40E Router

Commissioning Guide


Issue 03 (2010-03-31)

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 boxof 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 COM1properties according to the description in Figure 3-4 or by clicking Restore Defaults.



3-3

Figure 3-4 Setting communication parameters

----End

Operation ResultAfter the preceding configurations are complete, press Enter. If the prompt <HUAWEI> isdisplayed on the screen, it indicates that logging in to the NE80E/40E through the consoleinterface 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 checkwhether the parameters or physical connections are correct. If they are correct, log in to thedevice again.

3.2 Checking a DeviceYou can check a device to make sure that the current status meets the deployment requirement.

3.2.1 Checking Software VersionsYou need to check whether the software version in use meets the deployment requirement.

3.2.2 Checking the Health Status of a DeviceYou need to check whether the current status of a device meets the deployment requirement.

3.2.3 Checking License FilesYou need to check whether GTL license files are correctly loaded.

3.2.4 Checking the Status of Boards


Commissioning Guide


Issue 03 (2010-03-31)

You need to check whether all boards are in position and work normally.

3.2.5 Checking the Status of the FANYou need to check whether the fan works normally.

3.2.6 Checking the Status of the PowerYou need to check whether the power works normally.

3.2.1 Checking Software VersionsYou need to check whether the software version in use meets the deployment requirement.

Prerequisite3.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 canenter [ | slot slot-id ] to view the command output that is filtered through regular expressions orthe version information of the board in a specified slot.<HUAWEI> display versionHuawei Versatile Routing Platform SoftwareVRP (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 thecurrent and next startup.<HUAWEI> display startupMainBoard: Configured startup system software: cfcard:/V600R001C00.cc Startup system software: cfcard:/V600R001C00.cc Next startup system software: cfcard:/V600R001C00.cc Startup saved-configuration file: cfcard:/vrpcfg.cfg Next startup saved-configuration file: cfcard:/vrpcfg.cfg Startup paf file: cfcard:/paf-V600R001C00.txt Next startup paf file: cfcard:/paf-V600R001C00.txt Startup license file: cfcard:/license-V600R001C00.txt Next startup license file: cfcard:/license-V600R001C00.txt Startup patch package: cfcard:/patch.bat Next startup patch package: cfcard:/patch.bat

----End

Operation Resultl 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 consistentwith the version for deployment, you can go on with the subsequent stand-alonecommissioning.

l 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 usedduring the upgrade, including the Version Upgrade Guide, Release Notes, Patch Operation Guide,Paf&License Selection Guide, and Version Configuration Table.



3-5

3.2.2 Checking the Health Status of a DeviceYou need to check whether the current status of a device meets the deployment requirement.


ContextYou can check the following items to see whether a device is normal.

l CPU usage

l Memory usage

ProcedureStep 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 ResultIn 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, contactHuawei technical support personnel.

3.2.3 Checking License FilesYou need to check whether GTL license files are correctly loaded.

PrerequisiteBefore checking license files, complete the following tasks: is complete.l 3.1 Logging in to a Device Through the Console Interfacel Applying for a GTL license file

l Installing and loading the GTL license file

Context

WARNINGThe extension of the GTL license is .dat, which is different from that of the system license file.


Commissioning Guide


Issue 03 (2010-03-31)

A user that purchases a new device needs to apply for and purchase a GTL license to obtainauthorization of related service modules. After activating the license, the user can apply relatedservice modules.

When the activated GTL license file expires on a device, the user needs to reapply, upgrade andactivatea new GTL license file. Otherwise, the GTL license file becomes invalid on expiryandfunction modules are closed and services are interrupted.

ProcedureStep 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 licenseActive 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 Resultl 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 actuallyapplied for, you can go on with the subsequent stand-alone commissioning.

l If a license file is incorrectly loaded, you need to run the license active filename commandto 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 MPUand slave MPU.# Activate the license file GTL.dat on the master and slave MPUs.<HUAWEI> license active GTL.datInfo: Please wait for a while...Info: Succeeded in activating the License file on the master board.

3.2.4 Checking the Status of BoardsYou need to check whether all boards are in position and work normally.




3-7

Procedure

Step 1 Run the display device [ pic-status | slot-id ] command to view information about the devicesin position. You can enter [ pic-status | slot-id ] to view information about the Physical InterfaceCards (PICs) on all LPUs and information about a specified slot, including the LPU, MPU, SFU,clock board, power module, or fan module.<HUAWEI> display deviceNE40E's Device status:Slot # Type Online Register Status Primary- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -2 LPU Present Registered Normal NA3 LPU Present Registered Normal NA6 LPU Present Registered Normal NA9 MPU Present NA Normal Master11 SFU Present Registered Normal NA12 SFU Present Registered Normal NA13 SFU Present Registered Normal NA15 CLK Present Registered Normal Master17 PWR Present Registered Normal NA18 PWR Present Registered Abnormal NA19 FAN Present Registered Normal NA20 FAN Present Registered Normal NA21 LCD Present Registered Normal NA

----End

Operation Resultl 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 thesubsequent stand-alone commissioning.

l If boards are working abnormally, do as follows:

1. Run the display alarm all or display trapbuffer command to check whether alarmsof 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 viewthe alarm information.

Refer to the Alarm Reference according to preceding alarm information to locate the fault andseek solutions.

3.2.5 Checking the Status of the FANYou need to check whether the fan works normally.

Prerequisite

3.1 Logging in to a Device Through the Console Interface is complete.


Commissioning Guide


Issue 03 (2010-03-31)

Procedure

Step 1 Using the display fan command, you can view the status of FAN.<HUAWEI> display fanSlotid : 19Present : YESRegistered: YESStatus : AUTOFanSpeed : [No.]Speed [1]30% [2]30%Slotid : 20Present : YESRegistered: YESStatus : AUTOFanSpeed : [No.]Speed [1]30% [2]30%

----End

Commissioning ResultsThe status of the fan may be different. For details, please refer to display fan.

3.2.6 Checking the Status of the PowerYou need to check whether the power works normally.


Procedure

Step 1 Using the command display power, you can view the status of the power<HUAWEI> display powerNo Present mode State Num-------------------------------------------------------------------------------17 Yes * Abnormal(failure) 118 Yes AC Normal 1Power monitor cable state: Plug

----End

Commissioning ResultsThe status of the power may be different. For details, please refer to display power.

3.3 (Optional) Specifying a Device NameSpecifying a device name according to the networking plan helps to identify and maintain adevice.

Prerequisite3.2 Checking a Device is complete and the device is running normally.



3-9

Data Planning

Table 3-1 Data planning

Item Data Remarks

Device name NE40E-1 By default, the device nameis 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 ResultAfter the configuration is complete, the system name is displayed as [NE40E-1].

3.4 Setting System TimeSetting system time accurately ensures that the NE80E/40E works with other devicescoordinately.


Data Planning

Table 3-2 Data planning

Item Data Remarks

Universal Time Coordinated(UTC)

00:00:00 2009-01-01 The NE80E/40E calculatesits own time based on theUTC and the time zone.


Commissioning Guide


Issue 03 (2010-03-31)

Item Data Remarks

Time zone gmt add 05:00:00 The time zone can be setthrough the clock timezonetime-zone-name { add |minus } offset command.The NE80E/40E obtains thecurrent system time bysubtracting (add) an offsetfrom or adding (minus) anoffset to the UTC.

Start time of the daylightsaving time

01:00 (HH:MM) on the lastSunday in March annually

At this time, the NE80E/40Eadds an offset to the currentsystem time.

End time of the daylightsaving time

02:00 (HH:MM) on the lastSunday in October annually

At this time, the NE80E/40Esubtracts an offset from thecurrent system time.

Offset of the daylight savingtime

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, endtime, 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) anoffset 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 ResultRun the display clock command to view the configuration.

<HUAWEI> dispaly clock2008-12-31 19:16:14WednesdayTime Zone : z5 add 05:00:00



3-11

Daylight saving time : Name : gmt Repeat mode : repeat Start year : 2000 End year : 2099 Start time : last Sunday March 01:00:00 End time : last Sunday October 02:00:00 Saving time : 01:00:00

3.5 Configuring a Management User to Remotely Log in toa 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 thecentral equipment room.

3.5.1 Configuring a User to Log in to a Device Through TelnetThis section describes how to configure Telnet. Through Telnet, a user can remotely log in to adevice.

3.5.2 (Operational) Configuring ACLs to Filter Login UsersThis section describes how to filter users through Access Control Lists (ACLs). By configuringACLs, you can configure a device to filter login users.

3.5.3 (Optional) Configuring a User to Log in to a Device Through FTPThis 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 SSHThis section describes how to configure Secure Shell (SSH). SSH is a secure remote loginprotocol, developed based on the traditional Telnet. Compared with Telnet, SSH is greatelyimproved in terms of the authentication mode and data transmission security.

3.5.1 Configuring a User to Log in to a Device Through TelnetThis section describes how to configure Telnet. Through Telnet, a user can remotely log in to adevice.

PrerequisiteThe configuration 3.2 Checking a Device is complete and the device is running normally.

Data Preparation

Table 3-3 Data preparation

Item Data Remarks

Maximum number of usersthat can log in to the device atthe same time

5 -

Default user level 1 For details on user levels, see"Command Level."


Commissioning Guide


Issue 03 (2010-03-31)

Item Data Remarks

User name huawei -

Password huawei -

Specified user level 3 If no user level is specified,the default user level isadopted as the level of a loginuser.

(Optional) user type telnet User types include ftp, ppp,ssh, telnet, and terminal. Bydefault, a local user can useany access type.

Idle-cut traffic 10 It is used to determinewhether a user is idle. It isexpressed in bytes. In thiscase, when the user traffic isless than 10 bytes, the user isin the idle state.

Idle-cut time 30 It indicates the duration whena user remains idle. It isexpressed in minutes. In thiscase, when a user remainsidle for 30 minutes, theconnection between the userand the device is torn down.

Command LevelSystem commands are hierarchical. By default, the following commands ranging from level 0to level 3 are registered.

l Commands of level 0, the visit level: includes diagnostic tools (such as the ping andtracert commands) and the commands that are used to access a remote device (such asTelnet and SSH). The commands of level 0 cannot be used to save configuration files.

l Commands of level 1, the monitoring level: are used for system maintenance, includingdisplay commands. The commands of level 1 cannot be used to save configuration files.

l Commands of level 2, the configuration level: are used for service configuration, includingrouting commands and commands at each network layer to provide network services tousers.

l Commands of level 3, the management level: are used for system basic operation to supportservices, including file system, FTP, Trivial File Transfer Protocol (TFTP), andconfiguration file switching commands, slave board control commands, user managementcommands, command level configuration commands, system parameter configurationcommands, and debugging commands.



3-13

Procedure

Step 1 Set the maximum number of users that can log in to the device at the same time.<HUAWEI> system-view[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] local-user huawei password cipher huawei[HUAWEI-aaa] local-user huawei level 3[HUAWEI-aaa] local-user huawei service-type telnet[HUAWEI-aaa] 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

Commissioning ResultsAfter the preceding configurations are complete, run the following command to check the result.

<HUAWEI> telnet 127.0.0.1Trying 127.0.0.1 ...Press CTRL+K to abortConnected 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:huaweiPassword: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 UsersThis section describes how to filter users through Access Control Lists (ACLs). By configuringACLs, you can configure a device to filter login users.

PrerequisiteThe following configurations are complete and the device is running normally:


Commissioning Guide


Issue 03 (2010-03-31)

l 3.2 Checking a Device

l 3.5.1 Configuring a User to Log in to a Device Through Telnet

Background InformationYou 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 howto 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 loginusers rather than attack packets.

Data Preparation


Item Data Remarks

ACL number 3001 For details on differentlevels, see "ACLClassification." Generally,advanced ACLs areconfigured to filter loginusers.

IP address that can access thedevice

100.100.1.1100.100.1.2

It can be the source IP addressof the NMS device or the loghost.

ACL Classification

Table 3-5 ACL classification

ACL Type ACL Number Range Remarks

Interface-based ACL 1000 to 1999 An interface-based ACL candefine rules based on theinterface that receivespackets.

Basic ACL 2000 to 2999 A basic ACL can define rulesbased on only sourceaddresses.



3-15

ACL Type ACL Number Range Remarks

Advanced ACL 3000 to 3999 An advanced ACL can definerules based on the sourceaddress, destination address,type of the protocol over IP,and protocol features (such asthe source port anddestination port of TCP andthe type and code of ICMP).

Ethernet frame header-basedACL

4000 to 4099 An Ethernet frame header-based ACL, which is aspecial ACL, can define rulesbased on the Ethernet frameheader of the receivedpackets.

Procedure

Step 1 Create an ACL.<HUAWEI> system-view[HUAWEI] acl 3001[HUAWEI-acl-adv-3001] rule permit ip source 100.100.1.1 0[HUAWEI-acl-adv-3001] rule permit ip source 100.100.1.2 0[HUAWEI-acl-adv-3001] rule deny ip source any[HUAWEI-acl-adv-3001] 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] user-interface vty 0 4[HUAWEI-ui-vty0-4] acl 3001 inbound[HUAWEI-ui-vty0-4] quit

----End

Commissioning ResultsA 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 ThroughFTP

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.

PrerequisiteThe configuration 3.2 Checking a Device is complete and the device is running normally.


Commissioning Guide


Issue 03 (2010-03-31)

Data Preparation


Item Data Remarks

User name ftp -

Password huawei -

User path cfcard:/ It is the path that a user canaccess after logging in to adevice through FTP.

(Optional) user type telnet User types include FTP users,PPP users, SSH users, Telnetusers, and terminal users. Bydefault, a local user can useany access type.

ACL number 2001 It indicates that only basicACLs can be used to filterlogin users.

IP address that can access thedevice

100.100.1.3 -

Procedure

Step 1 Enable FTP on the NE80E/40E.<HUAWEI> system-view[HUAWEI] ftp server enableInfo: 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] local-user ftp password cipher huawei[HUAWEI-aaa] local-user ftp ftp-directory cfcard:/[HUAWEI-aaa] local-user ftp service-type ftp[HUAWEI-aaa] 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



3-17

Commissioning Results

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.200Trying 100.1.1.200 ...Press CTRL+K to abortConnected to 100.1.1.200.220 FTP service ready.User(100.1.1.200:(none)):ftp331 Password required for ftp.Enter password:230 User logged in.

2. View the files in the specified path.ftp> dir200 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.txt226 Transfer complete.FTP: 351 byte(s) received in 0.053 second(s) 6.62Kbyte(s)/sec.

3. Upload a file.ftp> put d:\test.txt200 Port command okay.150 Opening ASCII mode data connection for test.txt.226 Transfer complete.

ftp> dir200 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-rwxrwxrwx 1 noone nogroup 0 May 22 14:30 test.txt226 Transfer complete.FTP: 416 byte(s) received in 0.042 second(s) 9.90Kbyte(s)/sec.

4. Delete a file.ftp> delete test.txt250 DELE command successful.

5. Close an FTP connection.ftp> quit221 Server closing.

3.5.4 (Optional) Configuring a User to Log in to a Device ThroughSSH

This section describes how to configure Secure Shell (SSH). SSH is a secure remote loginprotocol, developed based on the traditional Telnet. Compared with Telnet, SSH is greatelyimproved in terms of the authentication mode and data transmission security.

Prerequisite

The configuration 3.2 Checking a Device is complete and the device is running normally.


Commissioning Guide


Issue 03 (2010-03-31)

Data Preparation


Item Data Remarks

SSH user name client001 -

SSH user password huawei -

SSH user level 3 If no level is specified for anSSH user, the default userlevel configured in the userinterface view is adopted asthe level of a login user.

SSH user authenticationmode

password SSH authentication modescan be classified into twotypes: Revest-Shamir-Adleman (RSA)authentication and passwordauthentication. This sectiondescribes only the passwordauthentication.

Procedure

Step 1 Generate a local key pair.<HUAWEI> system-view[HUAWEI] rsa local-key-pair createThe key name will be: HUAWEI_HostThe 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]:512Generating keys.......++++++++++++..........++++++++++++....++++++++......................................++++++++

Step 2 Configure a VTY user interface.[HUAWEI] user-interface vty 0 4[HUAWEI-ui-vty0-4] authentication-mode aaa[HUAWEI-ui-vty0-4] protocol inbound ssh[HUAWEI-ui-vty0-4] quit

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



3-19

[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

Commissioning ResultsLog in to a device through SSH. This section only describes how to log in to a device throughthe software putty.

1. As shown in the following figure, the IP address of the device is 192.168.1.1 and the loginprotocol is SSH.

2. Enter the user name client001 and the password huawei.


Commissioning Guide


Issue 03 (2010-03-31)

3.6 Commissioning the Link LayerThis section describes how to commission the link layer of the Router that connects to otherrouters or transmission devices.

3.6.1 Commissioning the Link Layer of an Ethernet InterfaceThis section describes how to commission the link layer of an Ethernet interface.

3.6.2 Commissioning the Link Layer of a POS InterfaceThis section describes how to commission the link layer of a POS interface. When using theSONET/SDH optical interface to transmit packets, you need to configure parameters for thePOS interface.

3.6.3 Commissioning the Link Layer of a CPOS InterfaceThis section describes how to commission the link layer of a CPOS interface.

3.6.4 Commissioning the Link Layer of the E1/T1 InterfaceThis section describes how to commission the link layer of the E1/T1 interface.

3.6.5 Commissioning the Link Layer of an ATM InterfaceThis 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 NetworkThis 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



3-21

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 InterfaceThis 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 LPUThis 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 MPUThis 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 InterfaceThis 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 LPUThis section describes how to commission the link layer of an Ethernet interface on an LPU.


Data PreparationNo. Data

1 Number of the Ethernet interface

2 MTU of the Ethernet interface

Procedurel 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 dependson the device. By default, the MTU is 1500.


Commissioning Guide


Issue 03 (2010-03-31)

CAUTIONIf IPv6 runs on an Ethernet interface and the MTU set through the mtu mtu commandon the interface is smaller than 1280, IPv6 works abnormally on this interface. Toavoid this problem, when IPv6 runs on an Ethernet interface, set the value of the MTUof the interface to greater than or equal to 1280.

Configure the MTU for IPv6 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 enterthe view of a specified Ethernet interface.

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 theEthernet interface.

The MTU is in bytes. The value range of the MTU of an Ethernet interface dependson the device. By default, the MTU is 1500.

l Configuring the working mode for the Ethernet interface



3. Run the following command as required:

– Run the duplex { full | half | auto } command to set the working mode for theEthernet interface.

– Run the negotiation auto command to configure the Ethernet interface to work inauto-negotiation mode.

NOTE

l Ethernet optical interfaces can work only in full-duplex mode.

l When connecting to a hub, the Ethernet electrical interface on the router should work inhalf-duplex because hubs can work only in half-duplex mode. When connecting to a LANswitch, the Ethernet electrical interface on the router can work in either full-duplex modeor half-duplex mode. Note that the working mode of the Ethernet interface and that of thepeer must be the same.

l For a GE electrical interface, the working rate 1000 Mbit/s and half-duplex working modeare mutually exclusive; therefore, they cannot be configured simultaneously.

l For a GE electrical interface enabled with auto-negotiation and working at 1000 Mbit/s, itcannot be configured with simplex mode or duplex mode. In addition, the auto-negotiationmode cannot be canceled.

l For a GE electrical interface working at 10 Mbit/s or 100 Mbit/s, you can configure it towork in simplex mode, duplex mode, or auto-negotiation mode.

l For a GE optical interface enabled with auto-negotiation, you must configure both ends ofthe link to work in auto-negotiation mode.

l Configuring the rate for the Ethernet electrical interface




3-23


3. Run the speed { 10 | 100 | auto } command to configure the rate for the Ethernetelectrical interface.

NOTE

By default, a GE electrical interface works at 1000 Mbit/s in auto-negotiation mode. You canforcibly change the rate, ensuring that the rates of both ends are the same. When you set therate to 10 Mbit/s or 100 Mbit/s, the auto-negotiation mode is canceled.

l Configuring the mode of the GE/FE optical/electrical 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.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 whichthe system automatically sets the working mode for the interface, no configuration isrequired.

If the router cannot recognize the type of the SFP module that works normally, youneed to forcibly set the working mode for the interface.

NOTE

Before configuring the working mode for the GE/FE optical/electrical interface, you need todelete all the configurations on the interface.

l Configuring LAN/WAN transmission mode for a 10GE interface1. Run the system-view command to enter the system view.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

l Before configuring the transmission mode of an interface to WAN, you need to clear allLAN configurations on the interface and shut down the interface.

l Before configuring the transmission mode of an interface to LAN, you need to clear allWAN configurations on the interface and shut down the interface.

----End

Commissioning Results# Run the display interface { ethernet | gigabitethernet } command. If information about theEthernet interface, such as the MTU, IP address, mask, working rate, and working mode, isdisplayed, it means that the configuration succeeds. For example:

<HUAWEI> display interface gigabitethernet 2/0/0GigabitEthernet2/0/0 current state : UPLine protocol current state : UPLast line protocol up time : 2009-12-17 14:38:21


Commissioning Guide


Issue 03 (2010-03-31)

Description:HUAWEI, GigabitEthernet2/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 1500Internet Address is 192.168.10.20/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc7d-a497The Vendor PN is SCP6F86-GL-CWHThe Vendor Name is SumitomoElectricPort BW: 1G, Transceiver max BW: 1G, Transceiver Mode: MultiModeWaveLength: 850nm, Transmission Distance: 300mRx Power: -18.76dBm, Tx Power: -5.05dBmLoopback:none, full-duplex mode, negotiation: disable, Pause Flowcontrol:Receive Enable and Send EnableLast physical up time : 2009-12-17 14:33:29Last physical down time : 2009-12-17 14:33:27Statistics 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-negotiationmethod, duplex mode, interface rate, and latest average inbound and outbound bandwidthutilization are displayed, it means that the configuration succeeds. For example:

<HUAWEI> display interface ethernet briefPHY: Physical*down: administratively down ^down: standby (l): loopback (b): BFD down InUti/OutUti: input utility/output utilityInterface PHY Auto-Neg Duplex Bandwidth InUti OutUti TrunkGigabitEthernet0/0/0 up enable half 100M 0% 0% --GigabitEthernet2/0/0 up disable full 1000M 0% 0% --GigabitEthernet2/0/1 *down disable full 1000M 0% 0% --GigabitEthernet2/0/2 *down disable full 1000M 0% 0% --GigabitEthernet2/0/3 *down disable full 1000M 0% 0% --GigabitEthernet2/0/4 *down disable full 1000M 0% 0% --GigabitEthernet2/0/5 *down disable full 1000M 0% 0% --GigabitEthernet2/0/6 *down disable full 1000M 0% 0% --GigabitEthernet2/0/7 up disable full 1000M 0% 0% --GigabitEthernet2/0/8 down disable full 1000M 0% 0% --GigabitEthernet2/0/9 *down disable full 1000M 0% 0% --GigabitEthernet4/1/0 down disable full 1000M 0% 0% --GigabitEthernet4/1/1 down disable full 1000M 0% 0% --GigabitEthernet4/1/1.7 down disable full 1000M 0% 0% --GigabitEthernet4/1/2 down disable full 1000M 0% 0% --GigabitEthernet4/1/3 down disable full 1000M 0% 0% --GigabitEthernet4/1/4 down disable full 1000M 0% 0% --GigabitEthernet4/1/5 down disable full 1000M 0% 0% --GigabitEthernet4/1/6 down disable full 1000M 0% 0% --GigabitEthernet4/1/7 down disable full 1000M 0% 0% --GigabitEthernet4/1/7.7 down disable full 1000M 0% 0% --



3-25

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

3.2 Checking a Device is complete and the device is running normally.

Data Preparation

No. Data


Procedurel Configuring the working type for 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.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 peerto work out the optimal duplex mode.

NOTE

l When connecting to a hub, the Ethernet interface on the router should be work in half-duplex because hubs can work only in half-duplex mode. When connecting to a LANswitch, the Ethernet 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 peermust be the same.

l Configuring the rate for the Ethernet electrical interface1. 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.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 andworks out the optimal working rate.

You can forcibly set the rate, ensuring that the rate of the interface is the same as the rate ofthe interface on the peer.

l Configuring the hybrid mode for the Ethernet electrical interface1. Run the system-view command to enter the system view.


Commissioning Guide


Issue 03 (2010-03-31)


3. Run the promode { on | off } command to configure the hybrid mode for the Ethernetinterface.

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 1 Run the system-view command to enter the system view.

Step 2 Run the interface { ethernet | gigabitethernet } interface-number command to enter the viewof 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 interfacetype.

By default, the interface type is hybrid.

----End

3.6.2 Commissioning the Link Layer of a POS InterfaceThis section describes how to commission the link layer of a POS interface. When using theSONET/SDH optical interface to transmit packets, you need to configure parameters for thePOS interface.

Prerequisite




3-27

Data Preparation

No. Data

1 Number of the CPOS interface

2 Value of the overhead byte, which can be J0, J1, or C2

3 Link layer protocol running on the POS interface

4 Frame format of the POS interface

5 Length of the CRC field of the POS interface

6 Clock mode of the POS interface

Procedurel 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 specifiedPOS interface.

3. Run the A.13 flag (pos interface view) command to configure the overhead byte forthe POS interface.

l Configuring the same scrambling mode for the POS interfaces that are connected to eachother (That is, both POS interfaces are enabled with or disabled from the scramblingfunction.)



3. Run the A.24 scramble (POS interface view) command to enable the scramblingfunction.

l Configuring the same link layer protocol for the POS interfaces that are connected to eachother (HDLC or PPP is preferred)



3. Run the A.20 link-protocol (POS interface view) command to configure the linklayer protocol for the POS interface.

NOTE

POS interfaces support only the basic functions of FR P2P sub-interfaces and do not supportother FR functions.

If PPP is adopted, it is recommended that CHAP and PAP authentication modes be configuredon the interface at the same time. The CHAP authentication mode is preferentially used. Fordetails, see A.21 ppp authentication-mode.

l Configuring the same physical layer protocol for the POS interfaces that are connected toeach other (SONET or SDH is preferred)


Commissioning Guide


Issue 03 (2010-03-31)

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.18 frame-format (POS interface view) command to configure the frame

format for the POS interface.l Configuring the same CRC field for the POS interfaces that are connected to each other

(CRC32 or CRC16 is preferred)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.4 crc (POS interface view) command to configure the CRC field for the

POS interface.l 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 ineither master clock mode or slave clock mode.

– When the POS interfaces on two routers are connected directly or through WavelengthDivision Multiplexing (WDM), set one POS interface to the master clock mode and theother 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 DCEusing 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. Run the system-view command 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.3 clock (POS interface view) command to configure the clock mode for

the POS interface.l Configuring the next hop of a static route as the outgoing interface if route iteration is not

expected on the POS link

----End

Commissioning Results# After the configuration is complete, run the display interface pos command. If informationabout the POS interface, such as the physical status, link protocol status, and clock mode, isdisplayed, it means that the configuration succeeds. For example:<HUAWEI> display interface pos 1/0/0Pos1/0/0 current state : UPLine protocol current state : UPLast line protocol up time : 2009-12-17 11:51:12Description : Pos1/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 4470 bytes, Hold timer is 10(sec)



3-29

Internet Address is 1.1.1.1/24Link layer protocol is PPPLCP opened, IPCP openedThe Vendor Name is FINISAR CORP. The Vendor PN is FTLF1321P1BTL-HWPort BW: 2.5G, Transceiver Mode: Single ModeWaveLength: 1310nm, Transmission Distance: 2kmRx Optical Power: -40.00dBm, Tx Optical Power: -40.00dBmPhysical layer is Packet Over SDH,Scramble enabled, clock master, CRC-32, loopback: noneFlag 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 0Statistics 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 configurationsucceeds. For example:<HUAWEI> display interface brief | include PosPHY: Physical*down: administratively down^down: standby(l): loopback(s): spoofing(b): BFD down(e): EFM down(d): Dampening SuppressedInUti/OutUti: input utility/output utilityInterface PHY Protocol InUti OutUti inErrors outErrorsPos1/0/0 up up 0.01% 0.01% 3795064053 0 Pos1/0/1 down down 0% 0% 343911292 0 Pos1/0/2 down down 0% 0% 343913408 0 Pos1/0/3 down down 0% 0% 343915353 0

# Run the display pos interface command. If information about the physical layer of the POSinterface is displayed, it means that the configuration succeeds. For example:<HUAWEI> display pos interface pos 6/0/0Pos6/0/0 current state:UPLine protocol current state:UPPhysical layer is Packet Over SDHScramble enabled, clock master, CRC-32, loopback: none SDH alarm: section layer: OOF LOF LOS line layer: none path layer: PAIS PRDI SDH error: section layer: B1 306207965


Commissioning Guide


Issue 03 (2010-03-31)

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 Input: 0 packets, 75870759 bytes Input error: 0 shortpacket, 3 longpacket, 48 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets SFP Transp Infomation:The Vendor PN is FTRJ1321P1BTLThe Vendor name is FINISAR CORP.address : 3 4 5 6 7 8 9 10 12 14 15 16 17 18 60 61value(hex): 0 1 22 2 12 10 1 5 19 5 32 0 0 0 5 1ePort BW: 2.5G, Transceiver max BW: 2.5G, Transceiver Mode: SingleModeWaveLength: 1310nm, Transmission Distance: 5km PIC Packet Statics Per Sencond:Rxd: 0x0 Packets 0x0 FCS 0x0 Receiv Abort Packets 0x0 Long Packets 0x0 Short PacketsTxd: 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 J1 Flag: Unknown Tx J0 ASCII : f8 4e 65 74 45 6e 67 69 6e 65 20 20 20 20 20 20 Tx J0 String :NetEngine Tx J1 ASCII : f8 4e 65 74 45 6e 67 69 6e 65 20 20 20 20 20 20 Tx J1 String :NetEngine

3.6.3 Commissioning the Link Layer of a CPOS InterfaceThis section describes how to commission the link layer of a CPOS interface.

3.6.3.1 Configuring an STM-1 CPOS InterfaceThis section describes how to configure an STM-1 CPOS interface.

3.6.3.2 Configuring the E1 Channel of a CPOS InterfaceThis section describes how to configure the E1 channel of a CPOS interface.

3.6.3.3 Configuring the T1 Channel of a CPOS InterfaceThis 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 InterfaceThis 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 InterfaceThis section describes how to configure the T3 channel of an STM-1 CPOS interface.

3.6.3.1 Configuring an STM-1 CPOS InterfaceThis section describes how to configure an STM-1 CPOS interface.



3-31

Prerequisite


Data Preparation

No. Data


2 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 otherespecially when the router and a non-Huawei device interconnect.


2. Run the controller cpos interface-number command to enter the view of a specified CPOSinterface.

3. Run the flag { j0 { sdh | sonet } j0 | j1 j1 | c2 c2 } command to configure the overheadbyte 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 eachother (SONET or SDH is preferred)



3. Run the frame-format { sdh | sonet } command to configure the frame format for theCPOS 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.

l Slave: uses the line clock signal.

When connecting to an SDH/SONET device, the CPOS interface should be configured with theslave mode because the clock accuracy on an SONET/SDH network is higher than the accuracyof the internal clock source on a CPOS interface.

When CPOS interfaces are connected through optical fibers or Wavelength DivisionMultiplexing (WDM), you should set one CPOS interface to the master mode and the other tothe slave mode.





Commissioning Guide


Issue 03 (2010-03-31)

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 thechannels of the CPOS interface is displayed, it means that the configuration succeeds. Forexample:

<HUAWEI> display controller cpos 1/0/0Cpos1/0/0 current state : UPDescription : Cpos1/0/0 InterfaceThe Vendor Name is AGILENTThe Vendor PN is QFCT-5736TPPort BW: 155M, Transceiver max BW: 155M, Transceiver Mode: SingleModeWaveLengh: 1310nm, Transmission Distance: 15km

Physical layer is Packet Over SDHclock master, Multiplex AU-4, loopback noneTX:Flag J0: "NetEngine ", Flag J1: "NetEngine ", Flag C2: 2(0x2)RX:Flag J0: "NetEngine ", Flag J1: "NetEngine ", Flag C2: 2(0x2)section layer: alarm: none error: B1 0line layer: alarm: none error: B2 0 REI 0path layer: alarm: none error: B3 0 REI 0

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


2 Number of the E1 channel

3 Number of the channels or timeslots that are bound to form a channel-set on the CE1interface

Procedure

Step 1 Configuring a synchronous serial interface of the E1 channel1. Run the system-view command on the router to enter the system view.



3-33


3. Run the following commands to create synchronous serial interfaces working in differentmodes:

l Run the e1 e1-number unframed command to create an E1 channel in clear channelmode. For details, see A.9 e1 unframed (CPOS interface view).

l 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 serialinterface; timeslots 0 to 31 can also be randomly bound to form one or multiple serialinterfaces. In this case, timeslot 0 needs to be separately listed in the command as theparameter ts0.

Timeslot 0 is used to transmit management and alarm information. After timeslot 0 isbound to form a serial interface, management and alarm information can betransparently 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 serialinterface and can be configured like a serial interface. A serial interface formed bybinding 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



3. Run the e1 e1-number set frame-format { crc4 | no-crc4 } command t set the frame formatfor the CPOS interface. For details, see A.8 e1 set frame-format (CPOS interfaceview).

Step 3 Configuring the clock mode for the E1 channel

Different E1 channels can be separately configured with the clock mode. Whether to use themaster 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 theslave mode.

l If two routers are connected through optical fibers, you should configure one end to the mastermode and the other end to the slave mode.

By default, an E1 channel works in master mode.




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

----End


Commissioning Guide


Issue 03 (2010-03-31)


# Run the display interface serial command. If information about the serial interface on the E1channel of the CPOS interface, such as the interface status, link layer protocol, and trafficstatistics, is displayed, it means that the configuration succeeds. For example:

<HUAWEI> display interface serial 1/0/0/1:1Serial1/0/0/1:1 current state : UPLine protocol current state : UPLast line protocol up time : 2009-01-20 15:55:16Description : Serial1/0/0/1:1 InterfaceRoute 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 bpsInternet protocol processing : disabledLink layer protocol is PPPLCP openedclock master, loopback noneCRC: CRC-32Scramble disabledAlarm: NoneStatistics last cleared:2009-01-20 15:55:04 Traffic statistics: Last 300 seconds input rate 16 bits/sec, 0 packets/sec Last 300 seconds output rate 16 bits/sec, 0 packets/sec Input: 33 packets, 426 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 30 packets, 372 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

# Run the display controller cpos command. If information about the CPOS interface, such theinterface status and clock mode, is displayed, it means that the configuration succeeds. Forexample:<HUAWEI> display controller cpos 1/0/0Cpos1/0/0 current state : UPDescription : Cpos1/0/0 InterfaceThe Vendor Name is SumitomoElectricThe Vendor PN is SCP6828-H1-BNEPort BW: 155M, Transceiver max BW: 2.5G, Transceiver Mode: SingleModeWaveLengh: 1310nm, Transmission Distance: 2kmPhysical layer is Packet Over SDHclock master, Multiplex AU-3, loopback noneTX:Flag J0: "NetEngine ", Flag J1: "NetEngine ", Flag C2: 2(0x2)

RX:Flag J0: "", Flag J1: "NetEngine ", Flag C2: 2(0x2)

section layer: alarm: none error: B1 0line layer: alarm: none error: B2 0 REI 27path layer: alarm: none error: B3 0 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




3-35



2 Number of the T1 channel

3 Number of the channels or timeslots that are bound to form a channel-set on theCT1 interface

Procedure

Step 1 Configuring a synchronous serial interface of the T1 channel1. Run the system-view command to enter the system view.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 thesynchronous serial interface.

l 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 serialinterface 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 toaccess the synchronous serial interface.

NOTE

The default rate of the synchronous serial interface formed by binding the timeslots of a T1channel is calculated as N x 56 kbit/s, N indicating the number of timeslots.

Step 2 Configuring the frame format for the T1 channel1. Run the system-view command to enter the system view.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 themaster mode or the slave mode is determined by the peer. For example, when connecting to anSONET/SDH device, the T1 channel should be configured with the slave mode.

If two routers are connected through optical fibers, you should configure one end to the mastermode and the other end to the slave mode.

By default, a T1 channel works in master mode.



Commissioning Guide


Issue 03 (2010-03-31)

1. Run the system-view command to enter the system view.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

Commissioning Results# Run the display interface serial command. If information about the serial interface on the T1channel of the CPOS interface, such as the interface status, link layer protocol, and trafficstatistics, is displayed, it means that the configuration succeeds.

<HUAWEI> display interface serial 1/0/0/1:0Serial1/0/0/1:0 current state : UPLine protocol current state : UPLast line protocol up time : 2009-01-20 15:55:16Description: Serial1/0/0/1:0 InterfaceRoute 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 bpsInternet protocol processing : disabledLink layer protocol is PPPLCP openedPhysical layer is Packet Over ESFclock master, loopback noneCRC: CRC-32Scramble disabledAlarm: noneStatistics last cleared:2009-01-13 19:03:08 Traffic statistics: Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

3.6.3.4 Configuring the E3 Channel of an STM-1 CPOS InterfaceThis section describes how to configure the E3 channel of an STM-1 CPOS interface.




2 Number of the E3 channel

Procedure

Step 1 Configuring a synchronous serial interface of the E3 channel



3-37

1. Run the system-view command to enter the system view.2. Run the controller cpos cpos-number command to enter the view of a specified CPOS

interface.3. Run the following command as required:

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

l Run the e3 e3-number unframed command to create a synchronous serial interface ofthe 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 themaster mode or the slave mode is determined by the peer. For example, when connecting to anSONET/SDH device, the E3 channel should be configured with the slave mode.


By default, an E3 channel works in master mode.



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

Commissioning Results# Run the display controller cpos command. If information about the CPOS interface, such asthe clock mode, frame format, and multiplexing path, is displayed, it means that the configurationsucceeds.

<HUAWEI> display controller cpos 1/0/0Cpos1/0/0 current state : Administratively DOWN Description : Cpos1/0/0 Interface The Vendor Name is AGILENT The Vendor PN is HFBR-5710LP-H3C Port BW: 155M, Transceiver max BW: 1G, Transceiver Mode: MultiMode WaveLengh: 850nm, Transmission Distance: 550m Physical layer is Packet Over SDHclock master, Multiplex AU-3, loopback none TX:Flag J0: "NetEngine ", Flag J1: "NetEngine ", 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


Commissioning Guide


Issue 03 (2010-03-31)

# Run the display interface serial command. If information about the synchronous serialinterface formed by binding timeslots of the E3 channel, such as the interface status and clockmode, is displayed, it means that the configuration succeeds.

<HUAWEI> display interface serial 2/0/0/1:0Serial2/0/0/1:0 current state : UPLine protocol current state : UPLast line protocol up time : 2009-01-20 15:55:16Description: Serial2/0/0/1:0 InterfaceRoute Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec)Derived from Cpos2/0/0 e3 1, Unframed mode, baudrate is 34368000 bpsInternet protocol processing : disabledLink layer protocol is PPPLCP openedclock master, loopback noneCRC: CRC-32Scramble disabledAlarm: NoneStatistics last cleared:2009-01-23 10:56:33 Traffic statistics: Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

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




2 Number of the T3 channel

Procedure

Step 1 Configuring a synchronous serial interface of the T3 channel1. Run the system-view command to enter the system view.2. Run the controller cpos cpos-number command to enter the view of a specified CPOS

interface.3. Run the following command as required:

l Run the t3 t3-number framed command to create a synchronous serial interface of theT3 channel in unchannelized mode.

l Run the t3 t3-number unframed command to create a synchronous serial interface ofthe T3 channel in clear channel mode.



3-39

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 themaster mode or the slave mode is determined by the peer. For example, when connecting to anSONET/SDH device, the E3 channel should be configured with the slave mode.


By default, a T3 channel works in master mode.



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

Commissioning Results# Run the display controller cpos command. If information about the CPOS interface, such asthe clock mode, frame format, and multiplexing path, is displayed, it means that the configurationsucceeds.

<HUAWEI> display controller cpos 1/0/0Cpos1/0/0 current state : Administratively DOWN Description : Cpos1/0/0 Interface The Vendor Name is AGILENT The Vendor PN is HFBR-5710LP-H3C Port BW: 155M, Transceiver max BW: 1G, Transceiver Mode: MultiMode WaveLengh: 850nm, Transmission Distance: 550m Physical layer is Packet Over SDHclock master, Multiplex AU-3, loopback none TX:Flag J0: "NetEngine ", Flag J1: "NetEngine ", 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 serialinterface formed by binding timeslots of the T3 channel, such as the interface status and clockmode, is displayed, it means that the configuration succeeds.

<HUAWEI> display interface serial 2/0/0/1:0Serial2/0/0/1:0 current state : UPLine protocol current state :UPLast line protocol up time : 2009-01-20 15:55:16Description: Serial2/0/0/1:0 InterfaceRoute Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec)Derived from Cpos2/0/0 t3 1, Unframed mode, baudrate is 44736000 bpsInternet protocol processing : disabled


Commissioning Guide


Issue 03 (2010-03-31)

Link layer protocol is PPPLCP openedclock master, loopback noneCRC: CRC-32Scramble disabledAlarm: NoneStatistics last cleared:2009-01-23 11:04:14 Traffic statistics: Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

3.6.4 Commissioning the Link Layer of the E1/T1 InterfaceThis section describes how to commission the link layer of the E1/T1 interface.

Prerequisite


Data Preparation

Item Data

Configue CE1Interfaces

l Number of the CE1 interface

l Number of the channel formed by binding timeslots on the CE1 interface

l Number of the timeslots that are bound to form a channel-set on the CE1interface

Configue CT1Interfaces

l Number of the CT1 interface

l Number of the channel formed by binding timeslots on the CT1 interface

l Number of the timeslots that are bound to form a channel-set on the CT1interface

Configue E3Interfaces

Number of the E3 interface

Configue CT3Interfaces

l Number of the CT3 interface

l T1 channel number on the CT1 interface

l Timeslot number, timeslot range, or number of the channel of the T1interface

Context

For detailed procedure for commissioning the link layer of the E1/T1 interface, see "Configuringan 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:



3-41

l Different E1/T1 channels are separately configured with the clock mode. Which clock modeis used depends on the peer.

– When the commissioned device is connected to a transmission device, it is configuredwith the slave mode.

– When the commissioned device is directly connected to a router through optical fibersor is connected to a router on a dense wavelength division multiplexing (DWDM)network, both the commissioned device and the router are configured with the mastermode.

l When the CT1 interface functions as a DCE, it is configured with the master mode; whenthe CT1 interface functions as a DTE, it is configured with the slave mode.

l When the CT1 interfaces of two routers are directly connected, one interface is configuredwith the master mode and the other interface is configured with the slave mode.

3.6.5 Commissioning the Link Layer of an ATM InterfaceThis section describes how to commission the link layer of an ATM interface.

Prerequisite


Data Preparation

No. Data

1 Number of the ATM interface

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


2. Run the interface atm interface-number command to enter the view of a specifiedATM interface.

3. Run the A.11 flag (atm interface view) command to configure the overhead byte forthe ATM interface.

l Configuring the same scrambling mode for the ATM interfaces that are connected to eachother (Both ATM interfaces are enabled with or disabled from the scrambling function.)



3. Run the A.23 scramble (ATM interface view) command to enable the scramblingfunction.

l Configuring the same physical layer protocol for both ATM interfaces that are connectedto each other (SONET or SDH is preferred)



Commissioning Guide


Issue 03 (2010-03-31)


3. Run the A.16 frame-format (ATM OC/STM) command to configure the frameformat for the ATM interface.

l Configuring the clock mode for the ATM interface

According to the function on the network, ATM devices and their interfaces can beclassified 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 deviceand is called a DCE, and the type of the corresponding interface is DCE.


1. Run the system-view command to enter the system view.2. Run the interface atm interface-number command to enter the view of a specified

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; anATM interface serving as a DCE should be configured with the master mode.

In the scenario where two routers are directly connected through ATM interfaces orthrough Wavelength Division Multiplexing (WDM), you need to configure the mastermode for one end and the slave mode for the other end.

When connecting to an SDH/SONET device, the router should be configured with theslave mode.

----End

Commissioning Results# Run the display interface atm command. If the configuration of the ATM interface, such asthe scrambling function ,frame format, clock mode, and statistical period, is displayed, it meansthat the configuration succeeds. For example:

<HUAWEI> display interface atm 1/0/0Atm1/0/0 current state : UPLine protocol current state : UPLast line protocol up time: 2008-11-03, 17:24:24 Description : Atm1/0/0 InterfaceRoute Port, The Maximum Transmit Unit is 1500Internet protocol processing : disabledAAL enabled: AAL5, Maximum VCs: 2048VCs 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 FTRJ1321P1BTLTransceiver BW: 2.5G, Transceiver Mode: Single ModeWaveLength: 1310nm, Transmission Distance: 5kmRx Optical Power: -24.95dBm, Tx Optical Power: -1.99dBmPhysical layer is Packet Over SDH



3-43

UBR: 1, CBR: 0, VBR: 0, USED BandWidth: 0KbpsVPI Max: 255, VCI Max: 2047Scramble enabled, clock master, CRC-32, loopback: noneFlag: 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: 0Statistics last cleared:never 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/0Last 30 seconds input rate: 0 bits/sec, 0 Packets/secLast 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 configurationsucceeds. For example:

<HUAWEI> display interface brief | include 1/0/PHY: Physical*down: administratively down^down: standby(l): loopback(s): spoofing(b): BFD down(e): EFM down(d): Dampening SuppressedInUti/OutUti: input utility/output utilityInterface PHY Protocol InUti OutUti inErrors outErrorsAtm1/0/1 up up 0.08% 0.08% 0 0 Atm1/0/1.1 up up 0.03% 0.03% 0 0 Atm1/0/1.2 up up 0.03% 0.03% 0 0

3.6.6 Commissioning the Link Layer of a User Interface on an FRNetwork

This section describes how to commission the link layer of a user interface on an FR network.



Commissioning Guide


Issue 03 (2010-03-31)

Data Preparation

No. Data

1 Number of the FR interface

2 Number of the Multilink Frame Relay (MFR) interface that is formed by bundlingphysical links

3 VC ID assigned to the interface

4 Number of the FR sub-interface

Procedure

Step 1 Run the system-view command to enter the system view.

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 layerprotocol 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

l After the FR encapsulation format on an interface is changed, the system automatically deletes all theFR configurations on the interface. At this time, you need to delete all the sub-interfaces and re-configure FR on the interface.

l After the configuration of the link layer of the interface is changed, you need to run the shutdowncommand to shut down the interface, and then run the undo shutdown command to start the interfaceto validate the new configuration.

Step 4 (Optional) Run the fr interface-type { dte |dce } command to set the type of the FR interfaceto 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 interfacetype 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 sub-interface.

NOTE

l The NE80E/40E supports only P2P FR sub-interfaces.

l The type of FR sub-interfaces must be the same as the type of the FR main interface.

l When an interface is configured with a sub-interface, the interval for consecutively running theshutdown 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.



3-45

Before configuring the Data Link Connection Identifier (DLCI) on a sub-interface, you need toshut down the sub-interface.

Step 8 Run the fr dlci dlci command to configure the DLCI for an FR sub-interface. For details, seeA.14 fr dlci.

FR sub-interfaces must be configured with DLCIs, and the DLCIs of the sub-interfaces at bothends 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 thesub-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 theFR protocol is displayed, it means that the configuration succeeds. For example:<HUAWEI> display fr interfacePos1/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 addressmapping table is displayed, it means that the configuration succeeds. Address mappinginformation is not displayed for P2P sub-interfaces. For example:<HUAWEI> display fr map-infoMap 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 InterfacePerform 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, packetsmay be lost or the communication may be interrupted at the network layer. Therefore, it isrecommended that you measure the optical power of interfaces before using the NE80E/40E.

When measuring the optical power, pay attention to the following points:

l Clean the fiber splice and the optical connector on the panel of the optical interface LPUand connect them properly.

l Do not look strictly into the laser transmitter on the LPU or the fiber splice.

l Measure the attenuation of the fiber jumper in advance to ensure accurate location of thefaulty point.

l Use different fiber jumpers for single mode and multi-mode optical modules.

l Use a calibrated tester (optical power meter).


Commissioning Guide


Issue 03 (2010-03-31)

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 themaximum transmission distance and the central wavelength of the optical modules at both ends areconsistent. 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 otherend 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 interfaceis 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 receiversensitivity; otherwise, the peer cannot receive the optical signal.

l The maximum output optical power of the optical module must be smaller than the overload opticalpower; otherwise, the optical module is probably burnt.

----End

3.7 Commissioning the Network LayerYou can adopt the out-band management mode or in-band management mode according to thenetwork planning.

3.7.1 Introduction to Commissioning the Network LayerYou can adopt the out-band management mode or in-band management mode according to thenetwork planning.

3.7.2 Assigning an IP Address to an InterfaceThis section describes how to assign an IP address to an interface. To implement Layer 3interworking between a device and other devices, you need to configure IP addresses for theinterfaces connecting the device to other devices.

3.7.3 Configuring a Static RouteThis section describes how to configure a static route. The management network interface doesnot participate in dynamic route calculation. Thus, in the scenario where the device to becommissioned is connected to the NMS through the management network interface, and the IPaddress of the management network interface and the IP address of the NMS are not on the samenetwork segment, you can configure static routes to enable the Layer 3 communication betweenthe device and the NMS.

3.7.4 Configuring OSPFYou can configure a routing protocol according to the network planning. This section describeshow to configure OSPF.



3-47

3.7.5 Configuring IS-ISYou can configure a routing protocol according to the network planning. This section describeshow to configure IS-IS.

3.7.6 Configuring BGPYou can configure a routing protocol according to the network planning. This section describeshow to configure BGP.

3.7.7 Connecting a Device to the NMSThis section describes how to connect a device to the NMS. You can connect a device to theNMS through SNMPv1, SNMPv2c, or SNMPv3. This section describes the three methods toconnect a device to the NMS.

3.7.1 Introduction to Commissioning the Network LayerYou can adopt the out-band management mode or in-band management mode according to thenetwork planning.

Background Information

Figure 3-5 Networking diagram in out-band management mode

GE0/0/0Console

NE

Switch

NMSNetwork

PC

192.167.1.10 / 24

NMS

192.168.1.3 / 24GE0/0/0

192.168.1.2 / 24GE1/0/0

Router A

Router B

192.168.1.1 / 24

Figure 3-5 shows the networking in out-band management mode. The commissioned deviceaccesses the Layer 3 network through the management network interface GE 0/0/0. As themanagement network interface cannot participate in dynamic routing calculation, if the IPaddresses of the management network interface and the NMS server are not in the same networksegment, 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.


Commissioning Guide


Issue 03 (2010-03-31)

Figure 3-6 Networking diagram in in-band management mode (a Layer 3 interface accessingthe NMS)

POS1/0/0Console

NE

NMSNetwork

PC

192.167.1.10 / 24NMS

192.168.1.2 / 24POS2/0/0

192.167.2.2 / 24GE1/0/1

Router B

Router A

192.168.1.1 / 24 192.167.2.1 / 24GE1/0/1

Figure 3-6 shows the networking in in-band management mode. The commissioned deviceaccesses the network through a Layer 3 interface POS 1/0/0. You can implement the commissionby configuring dynamic routes to make the management channel between the device and theNMS server routable.

You can configure dynamic routes through the methods provided in 3.7.4 Configuring OSPFand 3.7.5 Configuring IS-IS according to the network service planning. In addition, 3.7.3Configuring a Static Route is acceptable.


Figure 3-7 Networking diagram in in-band management mode (a Layer 2 interface accessingthe NMS)

VLANIF100192.168.1.1 / 24

Console

NE

NMSNetwork

PC

192.167.1.10 / 24NMS

VLANIF100192.168.1.2 / 24

192.167.2.2 / 24GE1/0/1

Router B

Router A

192.167.2.1 / 24GE1/0/1

VLAN 100

GE2/0/0

GE2/0/0



3-49

Figure 3-7 shows the networking in in-band management mode. The commissioned deviceaccesses the network through a Layer 2 interface. You can switch a Layer 3 Ethernet interfaceto a Layer 2 Ethernet interface, and then add the Layer 2 Ethernet interface to a VLAN and createa VLANIF interface.

You can configure dynamic routes through the methods provided in 3.7.4 Configuring OSPFand 3.7.5 Configuring IS-IS according to the network service planning. In addition, 3.7.3Configuring a Static Route is acceptable.


3.7.2 Assigning an IP Address to an InterfaceThis section describes how to assign an IP address to an interface. To implement Layer 3interworking between a device and other devices, you need to configure IP addresses for theinterfaces connecting the device to other devices.



Commissioning Guide


Issue 03 (2010-03-31)

Data Preparation

Table 3-8 Data Preparation

Item Data Remarks

Interface name l In the scenario in out-bandmanagement mode asshown in Figure 3-5, youneed to assign an IPaddress to themanagement networkinterface GE 0/0/0.

l In the scenario in in-bandmanagement mode (aLayer 3 interfaceaccessing the NMS) asshown in Figure 3-6, youneed to assign an IPaddress to the serviceinterface POS 1/0/0.

l In the scenario in in-bandmanagement mode (aLayer 2 interfaceaccessing the NMS) asshown in Figure 3-7, youneed to assign an IPaddress to the serviceinterface GE 2/0/0.

NOTEThis section describes how toassign IP addresses to POSinterfaces and VLANIFinterfaces. Assigning IPaddresses to managementnetwork interfaces and Layer 3Ethernet interfaces is the sameas assigning IP addresses toPOS interfaces.

Before assigning an IPaddress to an interface, youneed to confirm the interfacetype and the protocol type.This section describes onlythe IP address configurationof POS interfaces. For the IPaddress configuration ofEthernet interfaces and ATMinterfaces, see the HUAWEINetEngine80E/40E RouterConfiguration Guide WANAccess.

ID of the VLAN to which theinterfaces belong

100 This field is applicable onlyto the scenario where therouter is connected to theNMS through a Layer 2interface.

IP address/mask 192.168.1.1 / 24 The IP address of theinterface is in the samenetwork segment as the IPaddress of the connecteddevice.



3-51

Procedurel 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> system-view[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

l If a device is connected to another device through a Layer 2 interface, you can assign anIP address to the interface according to the following procedure.

# Assign an IP address to VLANIF 100. Switch the Layer 3 Ethernet interface to a Layer2 Ethernet interface.

<HUAWEI> system-view[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

Commissioning Results# After the configuration is complete, you can run the display interface interface-type interface-number 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/0POS1/0/0 current state : UPLine protocol current state : UPLast line protocol up time : 2009-10-09 15:03:02Description:HUAWEI, Pos6/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec)Internet Address is 192.168.1.1/24Link layer protocol is PPPLCP opened, IPCP openedThe Vendor PN is FTRJ8519P1BNL-HWPort BW: 2.5G, Transceiver max BW: 1G, Transceiver Mode: MultiModeWaveLength: 850nm, Transmission Distance: 550mRx Power: -6.05dBm, Tx Power: -5.76dBmPhysical layer is Packet Over SDHScramble enabled, clock master, CRC-32, loopback: noneFlag J0 "NetEngine "Flag J1 "NetEngine "Flag C2 22(0x16) SDH alarm: section layer: none line layer: none path layer: none


Commissioning Guide


Issue 03 (2010-03-31)

SDH error: section layer: B1 0 line layer: B2 0 REI 1318004 path layer: B3 0 REI 54250Statistics last cleared:never Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 24 bits/sec, 0 packets/sec Input: 1631 packets, 26118 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 1631 packets, 26112 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpacketsl 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.l 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 toview whether the interfaces are shut down.If so, go to Step 2.If not, go to Step 3.

2. Run the undo shutdown command and then the display this interface command inthe interface view to check whether the interface is in the Up state.If so, go to Step 11.If not, go to Step 3.

3. For a non-Ethernet interface, perform 5.Check whether the rate and duplex mode are configured on the peer device.If so, go to Step 4.If not, go to Step 5.

4. Configure the rate and duplex mode on the interface of the NE80E/40E according tothe rate and duplex mode configured on the peer device. Then, run the display thisinterface 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.If so, go to Step 11.If not, go to Step 5.

5. For an electrical interface, perform 7.Check whether the optical modules on the interfaces of the local and peer devices arematched, for example, whether the wavelengths or optical powers are matched.If so, go to Step 7.If not, go to Step 6.

NOTE

For details on how to check the optical power of an optical interface, see 3.6.7 Commissioningthe Power of an Optical Interface.

6. Replace the optical module with a matched one, and then run the display thisinterface command to check whether the interface is in the Up state.If so, go to Step 11.



3-53

If not, go to Step 7.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.If so, go to Step 11.If not, go to Step 8.

8. Run the display trapbuffer command to check whether alarms of interfaces aregenerated.If so, go to Step 9.If not, go to Step 10.

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 Reply from 192.168.1.2: bytes=56 Sequence=2 ttl=255 time=1 ms Reply from 192.168.1.2: bytes=56 Sequence=3 ttl=255 time=1 ms Reply from 192.168.1.2: bytes=56 Sequence=4 ttl=255 time=1 ms Reply from 192.168.1.2: bytes=56 Sequence=5 ttl=255 time=113 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 RouteThis section describes how to configure a static route. The management network interface doesnot participate in dynamic route calculation. Thus, in the scenario where the device to becommissioned is connected to the NMS through the management network interface, and the IPaddress of the management network interface and the IP address of the NMS are not on the samenetwork segment, you can configure static routes to enable the Layer 3 communication betweenthe device and the NMS.



l 3.7.2 Assigning an IP Address to an Interface


Commissioning Guide


Issue 03 (2010-03-31)

Background Information

Figure 3-8 Networking for applying out-band NMS

GE0/0/0Console

NE

Switch

NMSNetwork

PC

192.167.1.10 / 24

NMS

192.168.1.3 / 24GE0/0/0

192.168.1.2 / 24GE1/0/0

Router A

Router B

192.168.1.1 / 24

As shown in Figure 3-8, the NE80E/40E to be commissioned is connected to the NMS throughthe management network interface GE 0/0/0. The IP address of the management networkinterface 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, youneed to configure static routes to enable the Layer 3 communication between the NE80E/40Eand the NMS.

Procedure

Step 1 Configure a static route on the NE80E/40E to be commissioned.<HUAWEI> system-view[HUAWEI] ip route-static 192.167.1.10 24 gigabitethernet 0/0/0 192.168.1.2

----End

Commissioning Results# 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-tableRoute Flags: R - relay, D - download to fib------------------------------------------------------------------------------Routing Tables: Public Destinations : 9 Routes : 9

Destination/Mask Proto Pre Cost Flags NextHop Interface

1.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 192.168.1.0/24 Direct 0 0 D 192.168.1.1 GigabitEthernet0/0/0 100.1.1.200/32 Direct 0 0 D 127.0.0.1 InLoopBack0 100.1.1.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0



3-55

127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0 127.0.0.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0127.255.255.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0 192.167.1.0/24 Static 60 0 D 192.168.1.2 GigabitEthernet0/0/0255.255.255.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0

# Run the ping command on NE80E/40E to verify the connectivity.

<HUAWEI> ping 192.167.1.10PING 192.167.1.10: 56 data bytes, press CTRL_C to break Reply from 192.167.1.10: bytes=56 Sequence=1 ttl=254 time=60 ms Reply from 192.167.1.10: bytes=56 Sequence=2 ttl=254 time=65 ms Reply from 192.167.1.10: bytes=56 Sequence=3 ttl=254 time=36 ms Reply from 192.167.1.10: bytes=56 Sequence=4 ttl=254 time=93 ms Reply from 192.167.1.10: bytes=56 Sequence=5 ttl=254 time=23 ms


3.7.4 Configuring OSPFYou can configure a routing protocol according to the network planning. This section describeshow to configure OSPF.

Prerequisite

The following configurations are complete and the device is running normally:


l 3.7.2 Assigning an IP Address to an Interface

Data Preparation

Figure 3-9 Networking diagram of configuring OSPF

POS1/0/0Console

NE

NMSNetwork

PC

192.167.1.10 / 24NMS

192.168.1.2 / 24POS2/0/0

192.167.2.2 / 24GE1/0/1

Router B

Router A

192.168.1.1 / 24 192.167.2.1 / 24GE1/0/1


Commissioning Guide


Issue 03 (2010-03-31)

Item Data Remarks

Router ID of NE80E/40E 1.1.1.1 Router IDs need to beconfigured according to thenetworking plan.

Router ID of RouterA 2.2.2.2 Router IDs need to beconfigured according to thenetworking plan.

OSPF process ID 1 By default, the OSPF processID is 1.

Area to which an interfacebelongs

0 A network segment canbelong to only one OSPFarea.

Procedure

Step 1 Enable OSPF and enter the OSPF view.

# Configure NE80E/40E.

<HUAWEI> system-view[HUAWEI] router id 1.1.1.1[HUAWEI] ospf

# Configure RouterA.

<HUAWEI> system-view[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 thearea.

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 thenetwork command.

l The primary IP address of the interface must be within the network segment specified by thenetwork 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



3-57

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 GR State: Normal 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 ]

# Ping the remote device on NE80E/40E to check whether the ping succeeds.<HUAWEI> ping 192.167.1.10PING 192.167.1.10: 56 data bytes, press CTRL_C to break Reply from 192.167.1.10: bytes=56 Sequence=1 ttl=254 time=60 ms Reply from 192.167.1.10: bytes=56 Sequence=2 ttl=254 time=65 ms Reply from 192.167.1.10: bytes=56 Sequence=3 ttl=254 time=36 ms Reply from 192.167.1.10: bytes=56 Sequence=4 ttl=254 time=93 ms Reply from 192.167.1.10: bytes=56 Sequence=5 ttl=254 time=23 ms


3.7.5 Configuring IS-ISYou can configure a routing protocol according to the network planning. This section describeshow to configure IS-IS.


l 3.2 Checking a Devicel 3.7.2 Assigning an IP Address to an Interface

Data Preparation

Figure 3-10 Networking diagram of configuring IS-IS

POS1/0/0Console

NE

NMSNetwork

PC

192.167.1.10 / 24NMS

192.168.1.2 / 24POS2/0/0

192.167.2.2 / 24GE1/0/1

Router B

Router A

192.168.1.1 / 24 192.167.2.1 / 24GE1/0/1


Commissioning Guide


Issue 03 (2010-03-31)

Item Data Remarks

Network entity name of theNE80E/40E

10.0000.0000.0001.00 The network entity name is inthe format of X…X.XXXX.XXXX.XXXX.00.Here, X…X indicates the areaaddress; the 12 X in the middleindicates the system ID of therouter; and 00 in the endindicates the SEL.

Network entity name ofRouterA

20.0000.0000.0002.00 The network entity name is inthe format of X…X.XXXX.XXXX.XXXX.00.Here, X…X indicates an areaaddress; the twelve X in themiddle indicates the system IDof the RouterA; and 00 in theend indicates the selector(SEL).

IS-IS process IDs of twoconnected devices

1 By default, the IS-IS processID is 1.

Number of the interface onthe router that is connected toRouterA

POS 1/0/0 None.

Level of RouterA and therouter

l Level of NE80E/40E isLevel-2

l Level of RouterA isLevel-1-2

There are three levels, namely,level-1, level-1-2, and level-2.It is recommended that thelevel be set to level-2 for laterexpansion.

Procedure

Step 1 On RouterA and the NE80E/40E, start the IS-IS process and enter the IS-IS view.<HUAWEI> system-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



3-59

Step 4 Enable IS-IS on the specified interface.


[HUAWEI] interface pos 2/0/0[HUAWEI-Pos2/0/0] isis enable 1[HUAWEI-Pos2/0/0] quit

# Configure the NE80E/40E.

[HUAWEI] interface pos 1/0/0[HUAWEI-Pos1/0/0] isis enable 1[HUAWEI-Pos1/0/0] quit

----End

Postrequisite# After the configuration is complete, run the display isis peer command on NE80E/40E, andyou 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) 640000.0000.0001 GigabitEthernet1/0/0 0000.0000.0001.01 Up 24s L2(L1L2) 64

Total Peer(s): 2

# Ping the remote device on NE80E/40E to check whether the ping succeeds.



3.7.6 Configuring BGPYou can configure a routing protocol according to the network planning. This section describeshow to configure BGP.


l 3.2 Checking a Devicel 3.7.2 Assigning an IP Address to an Interface

ContextAs shown in Figure 3-11, BGP is configured to enable the Layer 3 communication between thedevice to be commissioned and the NMS. This section only describes how to configure BGP.


Commissioning Guide


Issue 03 (2010-03-31)

Figure 3-11 Networking for applying in-band NMS

POS1/0/0Console

NE

NMSNetwork

PC

192.167.1.10 / 24

NMS

192.168.1.2 / 24POS2/0/0

192.167.2.2 / 24GE1/0/1

Router B

Router A

192.168.1.1 / 24 192.167.2.1 / 24GE1/0/1

AS 65008AS 65009

ProcedureStep 1 Configure EBGP.

# Configure NE80E/40E.

<HUAWEI> system-view[HUAWEI] bgp 65008[HUAWEI-bgp] router-id 1.1.1.1[HUAWEI-bgp] peer 192.168.1.2 as-number 65009


<HUAWEI> system-view[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 unicastHUAWEI-bgp-af-ipv4] import-route direct

----End

Postrequisite# After the configuration is complete, run the display bgp peer command on NE80E/40E, andyou can view information about the BGP neighbors on the device.

BGP local router ID : 1.1.1.1 Local AS number : 65008



3-61

Total number of peers : 1 Peers in established state : 1

Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv

192.168.1.2 4 65009 274 207 0 03:07:01 Established 5

# Ping the remote device on NE80E/40E to check whether the ping succeeds.



3.7.7 Connecting a Device to the NMSThis section describes how to connect a device to the NMS. You can connect a device to theNMS through SNMPv1, SNMPv2c, or SNMPv3. This section describes the three methods toconnect a device to the NMS.

PrerequisiteThe route between the NE80E/40E and the NMS is reachable.

Data preparationItem 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 andwrite community names andthe ACL number.

l read community name: comaccess

l write community name: mgr

l ACL number: 2000

None.

Parameters of SNMPv2c,including SNMP read andwrite community names andthe ACL number.

l read community name: comaccess

l write community name: mgr

l ACL number: 2001

None.

Parameters of SNMPv3,including SNMP group anduser names and the ACLnumber.

l SNMP group name: NMS

l SNMP user name: John

l ACL number: 2002

None.


Commissioning Guide


Issue 03 (2010-03-31)

Procedurel Configure SNMPv1.

1. Configure basic functions of SNMPv1 on the NE80E/40E.

# Configure SNMP version.

<HUAWEI> system-view[HUAWEI] snmp-agent[HUAWEI] snmp-agent sys-info version v1

# Set the SNMP community name: the read community name of NE80E/40E iscomaccess and the write community name is mgr. For details, please refer to A.25snmp-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 (ACLview).[HUAWEI] acl 2000[HUAWEI-acl-basic-2000] rule permit source 192.167.1.10 0[HUAWEI-acl-basic-2000] quit

3. Configure trap functions and set the IP address of the trap server to be the IP addressof 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

l Configure SNMPv2c.1. Configure basic functions of SNMPv2c on the NE80E/40E.


<HUAWEI> system-view[HUAWEI] snmp-agent[HUAWEI] snmp-agent sys-info version v2c

# Set the SNMP community name: the read community name of NE80E/40E iscomaccess and the write community name is mgr. For details, please refer to A.25snmp-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, pleaserefer to A.22 rule (ACL view).[HUAWEI] acl 2001[HUAWEI-acl-basic-2001] rule permit source 192.167.1.10 0[HUAWEI-acl-basic-2001] quit

3. Configure trap functions and set the IP address of the trap server to be the IP addressof the NMS, 192.167.1.10. For details, please refer to A.26 snmp-agent target-hosttrap.[HUAWEI] snmp-agent trap enable[HUAWEI] snmp-agent target-host trap address udp-domain 192.167.1.10 params securityname comaccess v1 private-netmanager

l Configure SNMPv3.1. Configure basic functions of SNMPv3 on the NE80E/40E




3-63

<HUAWEI> system-view[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 SNMPgroup named Johngroup, with the security level being authentication, theauthentication protocol being HMAC-MD5-96 and the password being hello. Fordetails, 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 (ACLview).

[HUAWEI] acl 2002[HUAWEI-acl-basic-2002] rule permit source 192.167.1.10 0[HUAWEI-acl-basic-2002] quit

# Apply the ACL based on the user. For details, please refer to the command A.28snmp-agent usm-user.

[HUAWEI] snmp-agent usm-user v3 John NMS acl 2002

3. Configure trap functions and set the IP address of the trap server to be the IP addressof the NMS, 192.167.1.10. For details, please refer to the command A.26 snmp-agenttarget-host trap.[HUAWEI] snmp-agent trap enable[HUAWEI] snmp-agent target-host trap address udp-domain 192.167.1.10 params securityname comaccess v3 private-netmanager

----End


After the configurations of the NE80E/40E and the NMS are complete, you can access theNE80E/40E through the NMS.

Install the Huawei iManager N2000 DMS Compound Package on the NM station and configureSNMP in the network management software.

For configuring and using the iManager N2000 DMS, refer to HUAWEI iManager N2000DMS - Compound Package User Manual Volume II.

3.8 Saving Configurations

Prerequisite

The software commissioning of a device is complete.


Commissioning Guide


Issue 03 (2010-03-31)

Data PreparationItem Data Remarks

Configuration file name to besaved

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

PostrequisiteNone.



3-65

A 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)

HUAWEI NetEngine80E/40E RouterCommissioning Guide A Appendix


A-1

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 AppendixHUAWEI NetEngine80E/40E Router

Commissioning Guide

A-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

A.1 clock (ATM interface view)

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

Formatclock { master | slave }

undo clock

Parametersmaster: sets an ATM interface work in master clock mode.

slave: sets an ATM interface work in slave clock mode.

ViewsATM interface view

Default Level2: Configuration level

Usage GuidelinesNOTE

Although this command can be applied to ATM main interfaces and sub-interfaces, you can use thiscommand only in the ATM main interface view. This command cannot be run in the ATM sub-interfaceview.

l As a DCE device, an ATM interface should work in master clock mode.

l As a DTE device, an ATM interface should work in slave clock mode.

l When the ATM interfaces of two routers are directly connected through the optical fiberor Wavelength Division Multiplexing (WDM), one end should work in master clock modeand the other in slave clock mode.

l When an ATM interface is connected to an SDH/SONET device, the ATM interface shouldwork in slave clock mode.

Example# Set ATM 4/0/0 to work in master clock mode.

<HUAWEI> system-view[HUAWEI] interface atm 4/0/0[HUAWEI-Atm4/0/0] clock master



A-3

A.2 clock (CPOS interface view)

FunctionUsing the clock command, you can set the clock mode of a CPOS interface.


By default, a CPOS interface works in master clock mode.


undo clock

Parametersmaster: sets a CPOS interface to work in master clock mode.

slave: sets a CPOS interface to work in slave clock mode.

ViewsCPOS interface view


Usage GuidelinesWhen the CPOS interfaces of two routers are directly connected, one end should work in masterclock mode and use internal clock signals, and the other work in slave clock mode and use lineclock signals.

Example# Set CPOS 1/0/0 to work in master clock mode.

<HUAWEI> system-view[HUAWEI] controller cpos 1/0/0[HUAWEI-Cpos1/0/0] clock master

A.3 clock (POS interface view)

FunctionUsing the clock command, you can set the clock mode of a POS interface.


By default, a POS interface works in the master clock mode.


Commissioning Guide


Issue 03 (2010-03-31)


undo clock

Parametersmaster: sets a POS interface to work in master clock mode.

slave: sets a POS interface to work in slave clock mode.

ViewsPOS interface view


Usage GuidelinesWhen the POS interfaces of two routers are directly connected, one end should work in masterclock mode and use internal clock signals, and the other works in slave clock mode and use lineclock signals.

Example# Set POS 1/0/0 on the router to work in slave clock mode.

<HUAWEI> system-view[HUAWEI] interface pos 1/0/0[HUAWEI-Pos1/0/0] clock slave

A.4 crc (POS interface view)

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

Formatcrc { 16 | 32 }

undo crc

Parameters16: indicates that the CRC field is 16 bits.

32: indicates that the CRC field is 32 bits.



A-5



Usage GuidelinesA 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> system-view[HUAWEI] interface pos 1/0/0[HUAWEI-Pos1/0/0] crc 16

A.5 display power

FunctionUsing thedisplay power command, you can view the status of the power.

Formatdisplay power [{environment-info |manufacture-info}slot slot-id |slot[slot-id]]

Parametersenvironment-info: displays the environment information of the specified power that is inposition.

manufacture-info: displays the manufacturing information of the specified power that is inposition.

slot [ slot-id]: displays the power status of the specified LPU that is in position.

ViewsAll views

Default Level1: Monitoring level

Usage GuidelinesNone


Commissioning Guide


Issue 03 (2010-03-31)

Example# Display the status of the power.

<HUAWEI>display powerNo Present mode State Num---------------------------------------------------------------25 No * * 126 Yes * Normal 1Power 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 alternatingcurrent.

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 17Info: 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 17Info: 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 4Slot: 4- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -BOARD POWER: 280W- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

A.6 e1 channel-set (CPOS interface view)

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

Formate1 e1-number channel-set set-number timeslot-list { ts0 | slot-list [ ts0 ] }

undo e1 e1-number channel-set set-number



A-7

Parameterse1-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 isrun, timeslot 0 alone is bound to form a synchronous serial interface. After the channel-set set-number timeslot-list slot-list ts0 command is run, timeslot 0 and the timeslots specified by slot-list 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. Itcan be separate timeslot or time ranges. Time slots are separated by ","; while the range isexpressed by "-".



Usage GuidelinesIn channelized mode, timeslot 0 alone can be bound to form a serial interface; timeslots 0 to 31can also be randomly bound to form one or multiple serial interfaces. In this case, timeslot 0needs to be specified in the command as the parameter ts0.

Example# Bind timeslots of the E1 channel 63.

<HUAWEI> system-view[HUAWEI] controller cpos 1/0/0[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.

<HUAWEI> display interface serial 1/0/0/63:1Serial1/0/0/63:1 current state : DOWNLine protocol current state : DOWNDescription:HUAWEI, HUAWEI Series, Serial1/0/0/63:1 InterfaceRoute Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec)Derived from Cpos1/0/0 e1 63, Timeslot(s) Used: 1-31, baudrate is 1984000 bpsInternet protocol processing : disabledLink layer protocol is PPPLCP initialPhysical layer is Packet Over NO-CRC4,clock master, loopback noneCRC: CRC-32Scramble disabledAlarm: OOF PAISStatistics last cleared:2009-03-18 15:30:13 Traffic statistics: Last 300 seconds input rate 0 bits/sec, 0 packets/sec


Commissioning Guide


Issue 03 (2010-03-31)

Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

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

Item Description

Serial1/0/0/63:1 currentstate

Indicates the current physical status of the serial interfacel UP: indicates the normal enabled state.

l DOWN: indicates the abnormal state.

l Administratively Down: If the administrator uses theshutdown command on the interface, the state isAdministratively Down.

Line protocol currentstate

Indicates the status of the link protocol of the interface:l UP: indicates the normal enabled state.

l DOWN: indicates the abnormal state.

Description Indicates the description about the interface. Up to 242 characterscan be entered. It is case sensitive and can be blank spaces. Thedescription can help the user to get familiar with the interfacefunction.

The Maximum TransmitUnit is

As for the serial interface, the default value is 1500 bytes. Thepacket larger than the MTU is fragmented before being sent. Ifthe non-fragmentation is configured, the packet is discarded.

Hold timer is Indicates the interval for sending the hold packets. If the packetis not sent out during the life cycle, it is discarded. By default, itis 10 seconds.

Derived from Indicates the number of the T3 interface that forms the serialinterface.

Timeslot(s) Used: Indicates the number of the time slot that forms the serialinterface.

Baudrate is Indicates the baudrate of the serial interface.

Internet protocolprocessing : 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

Item Description

Scramble Indicates that the scrambling is disabled or enabled.

Last 300 seconds inputrate:Last 300 seconds outputrate:

Indicates the rate of the byte and the packet that pass through theinterface in the last 300 seconds.

Input Indicates the total number of the packets and bytes received onthe interface.

Output Indicates the total number of the packets and bytes sent on theinterface.

shortpacket Indicates the number of received packets smaller than thespecified minimum packet.

longpacket Indicates the number of received packets whose size is greaterthan 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 beprocessed because the packet-receiving speed is higher than theforwarding speed.

underrunpackets Indicates the number of packets that cannot be sent because thereading-memory speed is lower than the forwarding speed on theinterface.


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

Formate1 e1-number set clock { master | slave }

undo e1 e1-number set clock

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


Commissioning Guide


Issue 03 (2010-03-31)



Usage GuidelinesThe 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> system-view[HUAWEI] controller cpos 1/0/0[HUAWEI-Cpos1/0/0] e1 1 set clock slave

A.8 e1 set frame-format (CPOS interface view)

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

Formate1 e1-number set frame-format { crc4 | no-crc4 }

undo e1 e1-number set frame-format

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





A-11

Usage GuidelinesThe 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> system-view[HUAWEI] controller cpos 1/0/0[HUAWEI-Cpos1/0/0] e1 1 set frame-format crc4

A.9 e1 unframed (CPOS interface view)

FunctionUsing the e1 unframed command, you can configure the E1 channel of CPOS to operate inunframed 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.

Formate1 e1-number unframed

undo e1 e1-number unframed

Parameterse1-number: specifies the E1 channel number of CPOS. The value is an integer that ranges from1 to 63.



Usage GuidelinesWhen the E1 channel is set to work in unframed mode, the E1 channel does not include framecontrol 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.

<HUAWEI> system-view


Commissioning Guide


Issue 03 (2010-03-31)

[HUAWEI] controller cpos 1/0/0[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 CPOSinterface.

Using the undo e3 set clock command, you can cancel the clock mode set for the E3 channelof 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 rangesfrom 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

2: Configuration 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 clocksignal.

<HUAWEI> system-view[HUAWEI] controller cpos 1/0/0[HUAWEI-Cpos1/0/0] e3 3 set clock slave



A-13

A.11 flag (atm interface view)

FunctionUsing the flag command, you can set the overhead byte of SDH frame.

Using the undo flag command, you can restore the default setting.

Formatflag c2 c2-value

flag j0 { 64byte-or-null-mode j0-value | 16byte-mode j0-value | 1byte-mode j0-value |peer }


undo flag

Parametersc2 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. Thevalue 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 pathoverhead. 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.

l 16byte-mode: it is a string ranging from 1 to 15 characters.

l 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".

ViewsATM interface view


Usage GuidelinesC2 and J1 on the sending end must be the same as that on the receiving end.


Commissioning Guide


Issue 03 (2010-03-31)

J0 can any character in the same carrier network. However, on the border between differentcarriers, J0 on the sending end must be the same as that on the receiving end. J0 helps the carrierto discover the fault early.

Example# Set the path trace byte j1 of ATM 1/0/0 as the character string HUAWEI.

<HUAWEI> system-view[HUAWEI] interface atm 1/0/0[HUAWEI-Atm1/0/0] flag j1 16byte-mode HUAWEI

A.12 flag (cpos interface view)

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

Formatflag { j0 { sdh | sonet } j0 | j1 j1 | c2 c2 }

undo flag

Parametersj0: specifies the regeneration section trace byte. It is used to test the continuous connection ofthe 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. Thedefault 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 valueof J0 is 1

l In the 16-byte mode (sdh), j0 is a string ranging from 1 to 15. By default, the value of J0is "NetEngine"





A-15

Usage GuidelinesSONET or SDH frame has a variety of overhead bytes and can implement Operation andMaintenance (OAM) such as management of layers on the transmission network. j1, j0 and c2are mainly used to provide interworking to devices from different countries, areas ormanufacturers.

Example# Set the path trace byte j1 of CPOS 1/0/0 as the character string HUAWEI.

<HUAWEI> system-view[HUAWEI] controller cpos 1/0/0[HUAWEI-Cpos1/0/0] flag j1 HUAWEI

A.13 flag (pos interface view)

FunctionUsing 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".

Formatflag j0 { 64byte-or-null-mode j0-value | 16byte-mode j0-value | 1byte-mode j0-value |peer }


flag c2 c2-value

undo flag

Parametersj0 j0-value: specifies the regeneration section trace message, which belongs to the sectionoverhead. It tests the continuity of the connection between two ports on the section level.j1 j1-value: indicates the higher-order VC-N path trace byte, which belongs to higher-order pathoverhead. 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.

l 16byte-mode: It is a string ranging from 1 to 15.

l 1byte-mode: It is a integer ranging from 0 to 255.

peer: specifies the match with the Flag on the peer end.


Commissioning Guide


Issue 03 (2010-03-31)

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.Thevalue 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 thereceiving end. J0 helps the carrier to discover the fault early.

Example

# Configure the overhead byte J1

<HUAWEI> system-view[HUAWEI] interface pos 1/0/0[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 16to 1007. If dlci-number is not specified in the undo fr dlci command, all the local DLCIs aredeleted.

Views

FR interface view, FR sub-interface view, MFR interface view



A-17

Default Level


Usage Guidelines

When the FR interface type is DCE or NNI, it is necessary to manually configure the VC forboth 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 accordingto the peer device.

l If the interface is a sub-interface, the VC should be manually specified for the interface atboth DCE and DTE sides.

Example

# Allocate a VC with DLCI 100 for the FR sub-interface Serial 1/0/0:0.1.

<HUAWEI> system-view[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



Commissioning Guide


Issue 03 (2010-03-31)

Usage Guidelines

In FR, there are two communicating parties:

l User side: The user side is called DTE.

l 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 theDCE mode.

Example

# Set the type of the FR interface Serial 1/0/0:0 as DCE.

<HUAWEI> system-view[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 interfaceuses 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.



A-19

Example

# Set the frame format of an ATM interface as SONET.

<HUAWEI> system-view[HUAWEI] interface atm 4/0/0[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.l 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> system-view[HUAWEI] controller cpos 1/0/0[HUAWEI-Cpos1/0/0] frame-format sonet


Commissioning Guide


Issue 03 (2010-03-31)

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> system-view[HUAWEI] interface pos 1/0/0[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 frameformat is IETF.



A-21

Formatlink-protocol fr [ ietf | nonstandard ]

Parametersietf: 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.

ViewsFR interface view, MFR interface view


Usage GuidelinesTo configure the FR network, you must configure the encapsulation protocol of the interfacesto FR.

NOTE

After the FR encapsulation format of the interface is changed, the system automatically deletes all the FRconfigurations 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> system-view[HUAWEI] interface serial 1/0/0:0[HUAWEI-Serial1/0/0:0] link-protocol fr nonstandard

A.20 link-protocol (POS interface view)

FunctionUsing the link-protocol command, you can specify the link layer protocol on a POS interface.

By default, PPP is used.

Formatlink-protocol { fr [ ietf | nonstandard ] | hdlc | ppp }

Parametersfr: indicates the link layer protocol is FR.

ietf: indicates the Internet Engineering Task Force (IETF) standard encapsulation. It isperformed according to the format specified in RFC1490. It is the default encapsulation format.


Commissioning Guide


Issue 03 (2010-03-31)

nonstandard: indicates the non-standard compatible encapsulation format.

hdlc: indicates the link layer protocol is HDLC.

ppp: indicates the link layer protocol is PPP.



Usage GuidelinesInterface parameters must be configured in the interface view. The protocol related parameterscan 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 FRfunctions.

Example# Specify HDLC as the link layer protocol for POS 1/0/0.

<HUAWEI> system-view[HUAWEI] interface pos 1/0/0[HUAWEI-Pos1/0/0] link-protocol hdlc

A.21 ppp authentication-mode

FunctionUsing the ppp authentication-mode command, you can set the local PPP authentication modefor the peer router.

Using the undo ppp authentication-mode command, you can remove the authentication. Thatis, no authentication is performed.

By default, no authentication is performed.

Formatppp authentication-mode { chap [ pap ] | pap } [ call-in ]

undo ppp authentication-mode

Parameterschap: indicates the CHAP authentication.

pap: indicates the PAP authentication.

call-in: authenticates the peer only when the remote user calls in.



A-23

ViewsInterface view


Usage GuidelinesUsing the ppp authentication-mode chap pap command, you can perform the CHAPauthentication 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.

l 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 isdecided by AAA, which can perform authentication on the basis of the local authenticationdatabase or an AAA server.

Example# Authenticate the peer router by PAP on POS 1/0/0.

<HUAWEI> system-view[HUAWEI] interface pos 1/0/0[HUAWEI-Pos1/0/0] ppp authentication-mode pap

A.22 rule (ACL view)

FunctionUsing 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 aclcommand 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-ip-address 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.


Commissioning Guide


Issue 03 (2010-03-31)

l 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 destination-wildcard | any } | destination-port operator port | fragment-type fragment-type-name |source { source-ip-address source-wildcard | any } | source-port operator port | syn-flag syn-flag | time-range time-name | vpn-instance vpn-instance-name | dscp dscp ] *

rule [ rule-id ] { deny | permit } protocol [ destination { destination-ip-address destination-wildcard | any } | destination-port operator port | fragment-type fragment-type-name |source { source-ip-address source-wildcard | any } | source-port operator port | syn-flag syn-flag | time-range time-name | vpn-instance vpn-instance-name | precedence precedence |tostos ] *

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 destination-wildcard | any } | fragment-type fragment-type-name | icmp-type { icmp-name | icmp-typeicmp-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 destination-wildcard | any } | fragment-type fragment-type-name | icmp-type { icmp-name |icmp-typeicmp-code } |source { source-ip-address source-wildcard | any } | time-range time-name | vpn-instance 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 destination-wildcard | any } | fragment-type fragment-type-name | 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 destination-wildcard | any } | fragment-type fragment-type-name | source { source-ip-address source-wildcard | any } | time-range time-name | vpn-instance vpn-instance-name | precedenceprecedence | tos tos ] *

l Deleting rules in the advanced ACL

undo rule rule-id [ destination | destination-port | dscp | fragment-type fragment-type-name | 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 sourcemac-mask | dest-mac dest-mac destmac-mask ]

undo rule rule-id

# Create or delete a rule of UCL.



A-25

l When protocol is specified as TCP or UDPrule [ 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 | source-port operator port | syn-flag syn-flag | time-range time-name | dscp dscp ] *

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 | source-port operator port | syn-flag syn-flag | time-range time-name | precedence precedence| tos tos ] *

syn-flag syn-flag applies to TCP only.l When protocol is specified as ICMP

rule [ rule-id ] { deny | permit } protocol source user-group source-group-name[ destination { any | ip-address { destination-ip-address destination-wildcard | any } } |fragment-type fragment-type-name | icmp-type { icmp-name | icmp-type icmp-code } |logging | time-range time-name | dscp dscp ] *

rule [ rule-id ] { deny | permit } protocol source user-group source-group-name[ destination { any | ip-address { destination-ip-address destination-wildcard | any } } |fragment-type fragment-type-name | icmp-type { icmp-name | icmp-type icmp-code } |logging | time-range time-name | precedence precedence | tos tos ] *

l When protocol is specified as other protocol except TCP, UDP or ICMPrule [ rule-id ] { deny | permit } protocol source user-group source-group-name[ destination { any | ip-address { destination-ip-address destination-wildcard | any } } |fragment-type fragment-type-name } | logging | time-range time-name | dscp dscp ] *

rule [ rule-id ] { deny | permit } protocol source user-group source-group-name[ destination { any | ip-address { destination-ip-address destination-wildcard | any } } |fragment-type fragment-type-name } | logging | time-range time-name | precedenceprecedence | tos tos ] *

l # 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 ] *

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

l If the rule corresponding to the ACL number does not exist, create new rule for the ACLnumber and order the rules based on the ACL number.

l If the ACL number is not specified, the system automatically assigns one when you createa new rule. The number is in an order from a bigger value to a smaller value. The systemautomatically reserves a certain range between two ACL rules. The step command is usedto define the range.

NOTE

The rule ID automatically generated by the system begins with the step value so that a new rule can beinserted in front of the first rule. For instance, if the step value is 5, the rule ID begins with 5 and if the stepvalue is 2, the rule ID begins with 2.


Commissioning Guide


Issue 03 (2010-03-31)

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, youneed 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 acharacter 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 andUDP use the parameter [ source-port operator port ] [ destination-port operator port ], butthe other protocols do not.

destination: indicates the destination address information of an ACL rule. It is optional. If it isnot 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. Thedestination address wildcard can be 0.0.0.0, indicating that the destination address is a hostaddress.

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 andmeanings 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 numberranges 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 to63.

fragment-type fragment-type-name: indicates that this rule is only valid for the non-firstfragment packets.fragment-type-name includes:l fragment: checks the fragment packets

l fragment-spe-first: checks the first fragment packet

l fragment-subseq: checks the following fragment packets

l non-fragment: checks non-fragment packets

l non-subseq: checks the first fragment packet or non-fragment packets

interface-type interface-number: specifies the interface. If "any" is specified, it indicates allinterfaces.

logging: indicates whether to log the matched packets, optional. The log contents includesequence 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 valueis a number ranges from 0 to 7 or a name.



A-27

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. Theparameter 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 sourceaddress 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, andvalid in UDP or TCP. If it is not specified, it indicates any source port information of TCP/UDPpackets 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 to15 or a name such as normal, min-monetary-cost, max-reliability, max-throughput, and min-delay.

vpn-instance vpn-instance-name: This parameter is optional. It indicates that packets are filteredbased on the names of VPN instances. If the inbound interface is bound to a VPN, vpn-instance-name 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 inICMP. 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 0to 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

icmp-name icmp-type icmp-code

Echo 8 0

Echo-reply 0 0

Parameter-problem 12 0

Port-unreachable 3 3

Protocol-unreachable 3 2

Reassembly-timeout 11 1

Source-quench 4 0

Source-route-failed 3 5

Timestamp-reply 14 0

Timestamp-request 13 0

Ttl-exceeded 11 0


Commissioning Guide


Issue 03 (2010-03-31)

icmp-name icmp-type icmp-code

Fragmentneed-DFset 3 4

Host-redirect 5 1

Host-tos-redirect 5 3

Host-unreachable 3 1

Information-reply 16 0

Information-request 15 0

Net-redirect 5 0

Net-tos-redirect 5 2

Net-unreachable 3 0

# 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 theparameter after rule-id is not specified, this ACL rule is deleted completely; otherwise, only thepartial information of this rule is deleted.

source: This parameter is optional, indicating that only the information about the source IP ofspecified ACL rule is deleted.

destination: This parameter is optional, indicating that only the information about thedestination IP of specified ACL rule is deleted.

source-port: This parameter is optional, indicating that only the information about the sourceport of specified ACL rule is deleted. This parameter is valid only when the protocol type of therule is TCP or UDP.

destination-port: This parameter is optional, indicating that only the information about thedestination port of specified ACL rule is deleted. This parameter is valid only when the protocoltype of the rule is TCP or UDP.

precedence: This parameter is optional, indicating that the information about precedence of thespecified 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 isoptional.

icmp-type: This parameter is optional. The ACL rule that contains the settings of the specifiedtype of ICMP messages and message codes is deleted.

ViewsThe first group of commands is used in the basic ACL view.



A-29

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

The fifth group of commands is used in the view of the UCL.


Usage GuidelinesDifferent applications require differentiated configurations about the ACL rules. ACL rules mayvary with types of routing protocols.

Example# Create an ACL 3101 and add a rule to prohibit receiving or sending of RIP packets.

<HUAWEI> system-view[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 theIP 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 fromthe 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)

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

Formatscramble

undo scramble


Commissioning Guide


Issue 03 (2010-03-31)

Parameters

None

Views

ATM interface view

Default Level


Usage Guidelines

The scramble command scrambles and descrambles only the payload, and exerts no influenceon 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> system-view[HUAWEI] interface atm 4/0/0[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



A-31

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> system-view[HUAWEI] interface pos 1/0/0[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 ofSNMPv1 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 } [ mib-view 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 rangeof 1 to 32 characters.

cipher community-name: indicates the community name in cipher text. The value is in the rangeof 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 rangeof 2000 to 2999.

Views

System view


Commissioning Guide


Issue 03 (2010-03-31)


Usage GuidelinesUsing the snmp-agent community command, you can set the read and write authority of thecommunity 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

FunctionUsing the snmp-agent target-host trap command, you can set the destination host that receivesthe SNMP notification.

Using the undo snmp-agent target-host command, you can remove the host that receives theSNMP messages.

Formatsnmp-agent target-host trap [ ipv6 ] address udp-domain ip-address [ udp-port port-number ] [ 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 vpn-instance-name ]

Parametersaddress: 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 valueis 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 1to31 characters.



A-33

params: indicates the information of the login host that generates SNMP messages.

securityname security-string: specifies the community name of SNMPv1, SNMPv2C or theuser 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 NMSis used, the alarm message sent to the Huawei NMS can contain more detailed information, suchas the alarm type, alarm ID, and send time of the alarm message.

ViewsSystem view


Usage GuidelinesUse 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 alarmmessages. To enable a host to send notifications, you need to run the snmp-agent target-host command and the A.27 snmp-agent trap enable command on the host.

l In the situation that SNMP alarm is enabled, to enable SNMPv3 to send alarm messagesnormally, you need to ensure that the user name in the securityname command is addedto 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> system-view[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

FunctionUsing the snmp-agent trap enable command, you can enable the device to send trap packetsand 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.

Formatsnmp-agent trap enable [ trap-type [ trap-list ] ]


Commissioning Guide


Issue 03 (2010-03-31)

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 allthe modules to send any type of SNMP trap packets.

The snmp-agent trap enable command should be used together with the snmp-agent target-host 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 andstandard 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 trappackets are in the form of v2c with the security name as public.

<HUAWEI> system-view[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 }



A-35

Parametersv3: 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 64characters.

local: indicates the local entity user.

ViewsSystem view


Usage GuidelinesAfter a remote user is configured for the agent, when the agent communicates with the remoteuser, engineID is used for verification. If the engine ID changes after the user is configured, theuser corresponding to the original engine ID becomes ineffective.

Example# Add a user named John to the SNMP group named Johngroup, with the security level beingauthentication, the authentication protocol being HMAC-MD5-96 and the password being hello.

<HUAWEI> system-view[HUAWEI] snmp-agent usm-user v3 John Johngroup authentication-mode md5 hello


FunctionUsing the t1 set clock command, you can set the clock mode of a T1 channel.


Commissioning Guide


Issue 03 (2010-03-31)

Using the undo t1 set clock command, you can restore the default setting.

By default, the clock mode of the T1 channel is master.

Formatt1 t1-number set clock { master | slave }

undo t1 t1-number set clock

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



Usage GuidelinesThe clock modes of the different T1 channels of the same CPOS interface are independent fromeach other.

NOTE


Example# Configure T1 channel 1 to use the slave clock mode.

<HUAWEI> system-view[HUAWEI] controller cpos 1/0/0[HUAWEI-Cpos1/0/0] t1 1 set clock slave

A.30 t1 set frame-format (CPOS interface view)

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

Formatt1 t1-number set frame-format { esf | sf }



A-37

undo t1 t1-number set frame-format

Parameterst1-number: specifies the T1 channel number. The value ranges from 1 to 84.

esf: indicates the ESF format.

sf: indicates the SF format.



Usage GuidelinesThe 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> system-view[HUAWEI] controller cpos 1/0/0[HUAWEI-Cpos1/0/0] t1 1 set frame-format sf


FunctionUsing the t3 set clock command, you can configure the clock mode of the T3 channel on theCPOS 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.

Formatt3 t3-number set clock { master | slave }

undo t3 t3-number set clock

Parameterst3-number: specifies the sequence number of the T3 channel. The value is an integer that rangesfrom 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.


Commissioning Guide


Issue 03 (2010-03-31)



Usage GuidelinesIt 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 internalclock signal.

<HUAWEI> system-view[HUAWEI] controller cpos 1/0/0[HUAWEI-Cpos1/0/0] t3 3 set clock master



A-39

commissioning guide(v600r001c00 03)

Documents

primary mouse

prior written

startup patch

central equipment

maximum transmit

dampening

internal clock

h3c port bw