huawei configuration guide - wan access(v600r001c00_03)

HUAWEI NetEngine80E/40E RouterV600R001C00

Configuration Guide - WAN Access

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

PurposeThis document systematically describes WAN access protocols and configurations supportedby the NE80E/40E . The main contents cover common WAN interfaces, the basic knowledgeof WAN access protocols, configurations of common WAN access protocols and variousconfiguration examples. This manual provides common glossary, acronyms and abbreviationsin WAN access protocols.

Reading this manual helps users systematically master interface types, protocols of commonWAN access, and configurations.

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

HUAWEI NetEngine80E/40ERouter

V600R001C00

Intended AudienceThe intended audience of this document is:

l Commissioning Engineer

l Data Configuration Engineer

l Network Monitoring Engineer

l System Maintenance Engineer

OrganizationThis document consists of eight chapters and is organized as follows.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access About This Document


iii

Chapter Description

1 Serial InterfaceConfiguration

This chapter describes synchronous serial interfaces. It alsodescribes the configuration steps of serial interface, alongwith typical examples.

2 E-Carrier and T-CarrierInterface Configuration

This chapter describes E-Carrier and T-Carrier interfacerelated concepts, the configuration steps of various interfacesincluding CE1, CT1, E3, T3, along with typical examples.

3 POS and CPOS InterfaceConfiguration

This chapter describes Synchronous Digital Hierarchy(SDH), Synchronous Optical Network (SONET), Packetover SONET/SDH (POS), and Channelized POS interface(CPOS interface) related concepts. It also describes theconfiguration steps of various interfaces including POS,STM-1 CPOS, E1/T1 channels of the CPOS interface,STM-16 CPOS, Channelized POS interface, along withtypical examples.

4 PPP and MPConfiguration

This chapter describes Point-to-Point Protocol (PPP) andMultiLink PPP (MP) related concepts includingauthentication and link operation.

5 Frame RelayConfiguration

This chapter describes frame relay related concepts andconfiguration steps for frame function, LMI type and MFR,along with typical examples.

6 HDLC and IP-TrunkConfiguration

This chapter describes how to encapsulate an interface withHDLC protocol, IP-Trunk interface and how to set the HDLCparameters and IP-Trunk interface.

7 ATM Configuration This chapter describes Asynchronous Transfer Mode (ATM)broadband networking technologies and configuration stepsfor ATM interface, IPoA application, PVC service mapping,and service type of a PVC, along with typical examples.

8 1483B Configuration This chapter describes 1483B technologies and configurationsteps for IPoEoA application, along with typical examples.

A Glossary This appendix collates frequently used glossaries in thisdocument.

B Acronyms andAbbreviations

This appendix collates frequently used acronyms andabbreviations in this document.

Conventions

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

About This DocumentHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access

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

Issue 03 (2010-03-31)

Symbol Description

Indicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or savetime.

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

General ConventionsThe general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are inCourier New.

Command ConventionsThe command conventions that may be found in this document are defined as follows.


boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

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

{ x | y | ... } Alternative items are grouped in braces and separated byvertical bars. One is selected.



v


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

{ x | y | ... }* Alternative items are grouped in braces and separated byvertical bars. A minimum of one or a maximum of all canbe selected.

[ x | y | ... ]* Optional alternative items are grouped in square bracketsand separated by vertical bars. Many or none can beselected.

&<1-n> This parameter before the & sign can be repeated 1 to ntimes.

# A line starting with the # sign is comments.

GUI ConventionsThe GUI conventions that may be found in this document are defined as follows.


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface. For example, click OK.

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

Keyboard OperationThe keyboard operations that may be found in this document are defined as follows.

Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A meansthe two keys should be pressed in turn.

Mouse OperationThe mouse operations that may be found in this document are defined as follows.

About This DocumentHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access

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

Issue 03 (2010-03-31)

Action Description

Click Select and release the primary mouse button without movingthe pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move thepointer to 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)The third commercial release.

Updates in Issue 02 (2009-12-10)The second commercial release.

Updates in Issue 01 (2009-09-05)Initial commercial release.



vii

Contents

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

1 Serial Interface Configuration.................................................................................................1-11.1 Introduction to the Serial Interface..................................................................................................................1-2

1.1.1 Overview of the Synchronous Serial Interface.......................................................................................1-21.1.2 Features of the Synchronous Serial Interface on the NE80E/40E..........................................................1-2

1.2 Configuring the Link Layer Attributes for a Serial Interface..........................................................................1-21.2.1 Establishing the Configuration Task......................................................................................................1-31.2.2 Configuring Link Layer Protocol Type..................................................................................................1-31.2.3 Configuring Hold-Interval of the Link Layer Protocol of the Synchronous Serial Interface................ 1-41.2.4 Configuring the MTU.............................................................................................................................1-51.2.5 Configuring the Parity Bit......................................................................................................................1-51.2.6 Checking the Configuration...................................................................................................................1-6

1.3 Maintaining Serial Interface Configuration.................................................................................................... 1-71.3.1 Clearing the Interface Statistics..............................................................................................................1-7

2 E-Carrier and T-Carrier Interface Configuration.................................................................2-12.1 Introduction to the E-Carrier and T-Carrier Interface.....................................................................................2-2

2.1.1 E-Carrier and T-Carrier Overview.........................................................................................................2-22.1.2 Features of E-Carrier and T-Carrier Interfaces in the NE80E/40E........................................................2-4

2.2 Configuring CE1 Interfaces............................................................................................................................ 2-42.2.1 Establishing the Configuration Task......................................................................................................2-52.2.2 Creating Synchronous Serial Interface for CE1 Interface......................................................................2-52.2.3 Configuring Coding or Decoding Format of CE1 Interface...................................................................2-72.2.4 Configuring Clock Mode of CE1 Interface............................................................................................2-72.2.5 Configuring Frame Format of the CE1 Interface...................................................................................2-82.2.6 Checking the Configuration...................................................................................................................2-9

2.3 Configuring CT1 Interfaces..........................................................................................................................2-102.3.1 Establishing the Configuration Task....................................................................................................2-102.3.2 Creating Synchronous Serial Interface for CT1 Interface....................................................................2-112.3.3 Configuring Coding or Decoding Format of the CT1 Interface...........................................................2-122.3.4 Configuring Clock Mode of the CT1 Interface....................................................................................2-122.3.5 Configuring Frame Format of the CT1 Interface.................................................................................2-132.3.6 Checking the Configuration.................................................................................................................2-14

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access Contents


ix

2.4 Configuring E3 Interfaces.............................................................................................................................2-142.4.1 Establishing the Configuration Task....................................................................................................2-152.4.2 Creating Synchronous Serial Interface for E3 Interface......................................................................2-152.4.3 Checking the Configuration.................................................................................................................2-16

2.5 Configuring CT3 Interfaces..........................................................................................................................2-172.5.1 Establishing the Configuration Task....................................................................................................2-172.5.2 Creating Synchronous Serial Interface for CT3 Interface....................................................................2-182.5.3 Configuring Frame Format of the CT3 Interface.................................................................................2-192.5.4 Checking the Configuration.................................................................................................................2-20

2.6 Configuring a T1 Channel of CT3 Interfaces................................................................................................2-212.6.1 Establishing the Configuration Task....................................................................................................2-212.6.2 Configuring Clock Mode of a T1 Channel...........................................................................................2-222.6.3 Configuring Frame Format of a T1 Channel........................................................................................2-222.6.4 Checking the Configuration.................................................................................................................2-23

2.7 Maintaining E-Carrier and T-Carrier Interface Configuration......................................................................2-242.7.1 Setting Loopback to Detect Whether the Interface Is Normal.............................................................2-242.7.2 Clearing the Interface Statistics............................................................................................................2-25

2.8 Configuration Examples................................................................................................................................2-252.8.1 Example for Configuring Communication over CE1 Interfaces Bundle.............................................2-25

3 POS and CPOS Interface Configuration...............................................................................3-13.1 Introduction to the POS and CPOS Interfaces................................................................................................3-2

3.1.1 Overview of POS and CPOS Interfaces.................................................................................................3-23.1.2 Features of POS and CPOS Interfaces on the NE80E/40E....................................................................3-7

3.2 Configuring POS Interfaces............................................................................................................................3-93.2.1 Establishing the Configuration Task......................................................................................................3-93.2.2 Configuring the Link Layer Protocol...................................................................................................3-103.2.3 Configuring Clock Mode.....................................................................................................................3-113.2.4 Configuring the Overhead Byte...........................................................................................................3-113.2.5 Configuring Frame Format...................................................................................................................3-123.2.6 Configuring the Scramble Function.....................................................................................................3-133.2.7 Configuring the Length of the CRC Check Character.........................................................................3-133.2.8 Configuring MTU................................................................................................................................3-143.2.9 Checking the Configuration.................................................................................................................3-15

3.3 Configuring STM-1 CPOS Interfaces...........................................................................................................3-173.3.1 Establishing the Configuration Task....................................................................................................3-173.3.2 Configuring Clock Mode.....................................................................................................................3-183.3.3 Configuring Frame Format...................................................................................................................3-183.3.4 Configuring the Overhead Byte...........................................................................................................3-193.3.5 Configuring AUG Multiplexing Route................................................................................................3-203.3.6 Checking the Configuration.................................................................................................................3-21

3.4 Configuring E1 Channels of the CPOS Interface..........................................................................................3-213.4.1 Establishing the Configuration Task....................................................................................................3-21

ContentsHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access

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

Issue 03 (2010-03-31)

3.4.2 Creating Synchronous Serial Interface of E1 Channel.........................................................................3-223.4.3 Configuring Frame Format...................................................................................................................3-233.4.4 Configuring Clock Mode.....................................................................................................................3-233.4.5 Checking the Configuration.................................................................................................................3-24

3.5 Configuring T1 Channels of the CPOS Interface..........................................................................................3-253.5.1 Establishing the Configuration Task....................................................................................................3-253.5.2 Creating Synchronous Serial Interface of T1 Channel.........................................................................3-263.5.3 Configuring Frame Format...................................................................................................................3-263.5.4 Configuring Clock Mode.....................................................................................................................3-273.5.5 Checking the Configuration.................................................................................................................3-27

3.6 Configuring E3 Channels of an STM-1 CPOS Interface..............................................................................3-283.6.1 Establishing the Configuration Task....................................................................................................3-283.6.2 Creating Synchronous Serial Interface of E3 Channels.......................................................................3-293.6.3 Configuring Clock Mode.....................................................................................................................3-303.6.4 Checking the Configuration.................................................................................................................3-30

3.7 Configuring T3 Channels of an STM-1 CPOS Interface..............................................................................3-313.7.1 Establishing the Configuration Task....................................................................................................3-313.7.2 Creating T3 Channels...........................................................................................................................3-323.7.3 Configuring Frame Format...................................................................................................................3-333.7.4 Configuring Clock Mode.....................................................................................................................3-333.7.5 Checking the Configuration.................................................................................................................3-34

3.8 Maintaining POS and CPOS Interface Configuration...................................................................................3-353.8.1 Configuring the Self-loop to Detect Whether the Interface Is Normal................................................3-353.8.2 Clearing the Interface Statistics............................................................................................................3-36

3.9 Configuration Examples ...............................................................................................................................3-373.9.1 Example for Directly Connecting Devices Through POS Interfaces...................................................3-373.9.2 Example for Connecting Devices with POS Interfaces Through FR Network....................................3-393.9.3 Example for Configuring an STM-1 CPOS Interface..........................................................................3-42

4 PPP and MP Configuration......................................................................................................4-14.1 Introduction to PPP and MP............................................................................................................................4-2

4.1.1 PPP and MP Overview...........................................................................................................................4-24.1.2 Features of PPP and MP on the NE80E/40E..........................................................................................4-2

4.2 Encapsulating an Interface with PPP and MRU Negotiation..........................................................................4-34.2.1 Establishing the Configuration Task......................................................................................................4-34.2.2 Encapsulating the Interface with PPP.................................................................................................... 4-34.2.3 Enabling PPP MRU Negotiation............................................................................................................4-44.2.4 Checking the Configuration...................................................................................................................4-5

4.3 Configuring Unidirectional PAP.....................................................................................................................4-54.3.1 Establishing the Configuration Task......................................................................................................4-64.3.2 Configuring a Local Router to Authenticate Its Peer in PAP Mode......................................................4-64.3.3 Configuring the Peer to Be Authenticated by the Local Router in PAP Mode......................................4-74.3.4 Checking the Configuration...................................................................................................................4-8



xi

4.4 Configuring Unidirectional CHAP..................................................................................................................4-94.4.1 Establishing the Configuration Task......................................................................................................4-94.4.2 Configuring a Local Device with a User Name to Authenticate Its Peer in CHAP Mode..................4-104.4.3 Configuring a Local Device Without a User Name to Authenticate Its Peer in CHAP Mode............4-114.4.4 Checking the Configuration.................................................................................................................4-13

4.5 Configuring PPP Optional Parameters..........................................................................................................4-144.5.1 Establishing the Configuration Task....................................................................................................4-144.5.2 Configuring the Callback Function......................................................................................................4-154.5.3 Configuring Packet or Packet Header Compression............................................................................4-164.5.4 Configuring the Timeout Period of Negotiation..................................................................................4-174.5.5 Configuring the Polling Interval..........................................................................................................4-174.5.6 Configuring DNS Server Address Negotiation....................................................................................4-174.5.7 Configuring the PPP Link Quality Detection.......................................................................................4-184.5.8 Preventing the Peer Host Route from Being Added to the Local Routing Table of Direct Routes.....4-194.5.9 Checking the Configuration.................................................................................................................4-19

4.6 Configuring MP Binding Using an MP-Group.............................................................................................4-214.6.1 Establishing the Configuration Task....................................................................................................4-214.6.2 Adding an Interface to an MP-Group...................................................................................................4-224.6.3 Disabling the Endpoint Discriminator Negotiation..............................................................................4-234.6.4 Checking the Configuration.................................................................................................................4-24

4.7 Configuring MP Limiting Parameters...........................................................................................................4-254.7.1 Establishing the Configuration Task....................................................................................................4-264.7.2 Configuring the MRRU of an MP Group.............................................................................................4-264.7.3 Configuring the Damping Function for MP Subchannels....................................................................4-274.7.4 Configuring the Minimum Number of Subchannels in the Up State in an MP Link...........................4-284.7.5 Checking the Configuration.................................................................................................................4-28

4.8 Configuring MP Fragmentation....................................................................................................................4-294.8.1 Establishing the Configuration Task....................................................................................................4-294.8.2 Configuring the MP Fragment Function..............................................................................................4-294.8.3 Checking the Configuration.................................................................................................................4-30

4.9 Maintaining PPP and MP Configuration.......................................................................................................4-304.10 Configuration Examples..............................................................................................................................4-31

4.10.1 Example for Configuring PAP Authentication..................................................................................4-324.10.2 Example for Configuring Unidirectional CHAP Authentication.......................................................4-344.10.3 Example for Configuring Bidirectional CHAP Authentication.........................................................4-374.10.4 Example for Binding MPs into an MP-group....................................................................................4-39

5 Frame Relay Configuration......................................................................................................5-15.1 Introduction to Frame Relay...........................................................................................................................5-2

5.1.1 FR Protocol Overview............................................................................................................................5-25.1.2 Features of FR on the NE80E/40E.........................................................................................................5-2

5.2 Configuring FR...............................................................................................................................................5-25.2.1 Establishing the Configuration Task......................................................................................................5-2


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

Issue 03 (2010-03-31)

5.2.2 Configuring Basic FR Functions............................................................................................................5-35.2.3 Checking the Configuration...................................................................................................................5-5

5.3 Configuring FR LMI Type and Related Parameters.......................................................................................5-55.3.1 Establishing the Configuration Task......................................................................................................5-55.3.2 Configuring FR LMI and Related Parameters of DTE..........................................................................5-65.3.3 Configuring FR LMI and Related Parameters of DCE..........................................................................5-75.3.4 Checking the Configuration...................................................................................................................5-7

5.4 Maintaining Frame Relay Configuration........................................................................................................5-85.4.1 Clearing the Statistics of FR and Dynamic Address Mapping Entries..................................................5-85.4.2 Debugging FR........................................................................................................................................5-8

5.5 Configuration Examples..................................................................................................................................5-95.5.1 Example for Connecting Devices with POS Interfaces Through FR Network......................................5-9

6 HDLC and IP-Trunk Configuration.......................................................................................6-16.1 Introduction to HDLC and IP-Trunk...............................................................................................................6-2

6.1.1 HDLC and IP-Trunk Interface Overview...............................................................................................6-26.1.2 Features of HDLC and IP-Trunk interfaces on the router......................................................................6-2

6.2 Configuring HDLC.........................................................................................................................................6-36.2.1 Establishing the Configuration Task......................................................................................................6-36.2.2 Encapsulating an Interface with HDLC.................................................................................................6-36.2.3 Configuring the IP Address of the Interface..........................................................................................6-46.2.4 Setting the Polling Interval.....................................................................................................................6-46.2.5 Checking the Configuration...................................................................................................................6-5

6.3 Configuring an IP-Trunk Interface..................................................................................................................6-66.3.1 Establishing the Configuration Task......................................................................................................6-66.3.2 Creating an IP-Trunk and adding POS Interfaces into the IP-Trunk.....................................................6-76.3.3 Configuring an IP Address for the IP-Trunk Interface...........................................................................6-86.3.4 (Optional) Configuring the Lower Threshold of Up Links....................................................................6-96.3.5 (Optional) Configuring Load-balancing Mode for the IP-Trunk Interface............................................6-96.3.6 (Optional) Configuring Weights for Member Links............................................................................6-106.3.7 (Optional) Configuring the Method of Sending Trap Messages from an IP-Trunk Member Interface.......................................................................................................................................................................6-106.3.8 Checking the Configuration.................................................................................................................6-11

6.4 Maintaining HDLC and IP-Trunk Configuration..........................................................................................6-126.4.1 Clearing the statistics of the HDLC or IP-Trunk interfaces.................................................................6-136.4.2 Debugging HDLC................................................................................................................................6-13

6.5 Configuration Examples................................................................................................................................6-146.5.1 Example for Configuring HDLC..........................................................................................................6-146.5.2 Example for Configuring IP Address Unnumbered for HDLC...........................................................6-166.5.3 Example for Configuring an IP-Trunk.................................................................................................6-18

7 ATM Configuration...................................................................................................................7-17.1 Introduction to ATM.......................................................................................................................................7-2

7.1.1 ATM Overview......................................................................................................................................7-2



xiii

7.1.2 Features of ATM Supported by the NE80E/40E...................................................................................7-27.2 Configuring Parameters for an ATM OC-3/STM-1 Interface or an ATM OC-12/STM-4 Interface..............7-3

7.2.1 Establishing the Configuration Task......................................................................................................7-37.2.2 Configuring the Clock Mode..................................................................................................................7-47.2.3 Configuring the Frame Format...............................................................................................................7-57.2.4 Configuring the Overhead Byte.............................................................................................................7-57.2.5 Configuring the MTU.............................................................................................................................7-67.2.6 Configuring the Scrambling...................................................................................................................7-77.2.7 Configuring the Interval of Flow Statistics............................................................................................7-87.2.8 Checking the Configuration...................................................................................................................7-9

7.3 Configuring ATM Services on a Serial Interface..........................................................................................7-107.3.1 Establishing the Configuration Task....................................................................................................7-107.3.2 Configuring the ATM Protocol on a Serial Interface...........................................................................7-117.3.3 (Optional) Configuring the ATM Interface Type for a Serial Interface...............................................7-127.3.4 Creating a PVC on a Serial Interface................................................................................................... 7-127.3.5 Creating a PVP on a Serial Interface....................................................................................................7-137.3.6 Checking the Configuration.................................................................................................................7-14

7.4 Configuring IMA Groups..............................................................................................................................7-147.4.1 Establishing the Configuration Task....................................................................................................7-157.4.2 Creating an IMA Group....................................................................................................................... 7-157.4.3 Setting the Number of the Cells Contained in an IMA Frame.............................................................7-167.4.4 Configuring Bandwidth for an IMA Group......................................................................................... 7-167.4.5 Setting the Maximum Link Differential Delay for the IMA Group.....................................................7-177.4.6 Adding an Interface to an IMA Group.................................................................................................7-177.4.7 (Optional) Configuring the ATM Interface Type for an IMA Group..................................................7-187.4.8 Creating a PVC for an IMA Group......................................................................................................7-197.4.9 Creating a PVP for an IMA Group.......................................................................................................7-207.4.10 Checking the Configuration...............................................................................................................7-20

7.5 Configuring the IPoA Application................................................................................................................7-217.5.1 Establishing the Configuration Task....................................................................................................7-217.5.2 Configuring IPoA Mapping on a PVC.................................................................................................7-227.5.3 Checking the Configuration.................................................................................................................7-23

7.6 Configuring the Service Type and Optional Parameters of a PVC...............................................................7-257.6.1 Establishing the Configuration Task....................................................................................................7-257.6.2 Configuring the Service Type of a PVC.............................................................................................. 7-267.6.3 Configuring the Service Type of a PVP...............................................................................................7-277.6.4 (Optional) Configure the Overload Bandwidth Value of an ATM Interface.......................................7-287.6.5 Checking the Configuration.................................................................................................................7-28

7.7 Configuring ATM OAM...............................................................................................................................7-307.7.1 Establishing the Configuration Task....................................................................................................7-307.7.2 (Optional) Activating the CC Function................................................................................................7-317.7.3 (Optional) Configuring OAM End-to-End Loopback..........................................................................7-32


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

Issue 03 (2010-03-31)

7.7.4 (Optional) Configuring the Cell Loopback..........................................................................................7-337.7.5 Checking the Configuration.................................................................................................................7-34

7.8 Maintaining ATM Configuration..................................................................................................................7-357.8.1 Setting Loopback to Detect Whether an Interface Is Normal..............................................................7-357.8.2 Clearing the ATM Interface Statistics..................................................................................................7-367.8.3 Debugging ATM..................................................................................................................................7-36

7.9 Configuration Examples................................................................................................................................7-377.9.1 Example for Configuring IPoA............................................................................................................7-377.9.2 Example for Configuring ATM OAM.................................................................................................7-407.9.3 Example for Configuring IMAoPSN...................................................................................................7-44

8 1483B Configuration..................................................................................................................8-18.1 Introduction of 1483B.....................................................................................................................................8-2

8.1.1 1483B Overview....................................................................................................................................8-28.2 Configuring IPoEoA Services.........................................................................................................................8-3

8.2.1 Establishing the Configuration Task......................................................................................................8-38.2.2 Creating a VE Interface..........................................................................................................................8-38.2.3 Configuring IPoEoA Application Mapping on a PVC...........................................................................8-48.2.4 Configuring Services on the VE Interface.............................................................................................8-58.2.5 Checking the Configuration...................................................................................................................8-5

8.3 Configuration Examples..................................................................................................................................8-68.3.1 Example for Configuring a Routing VE Interface to Work as an IPoEoA Gateway.............................8-78.3.2 Example for Configuring ATM Bridged Ethernet.................................................................................8-98.3.3 Example for Configuring a VLANIF Interface to Work as an IPoEoA Gateway...............................8-11

A Glossary.....................................................................................................................................A-1

B Acronyms and Abbreviations.................................................................................................B-1



xv

Figures

Figure 2-1 Schematic diagram of CE1 interface configuration..........................................................................2-25Figure 3-1 STM-N frame structure......................................................................................................................3-4Figure 3-2 Process of multiplexing E1 to STM-1................................................................................................3-5Figure 3-3 Process of multiplexing T1 to STM-1................................................................................................3-5Figure 3-4 Sequence of arrangement of TUG-3, TUG-2 and TU-12 in VC-4.....................................................3-6Figure 3-5 Networking diagram of connecting devices directly through POS interfaces..................................3-37Figure 3-6 Networking diagram of connecting routers using the POS interface through FR network..............3-40Figure 3-7 Networking diagram of an STM-1 CPOS interface.........................................................................3-42Figure 4-1 Networking diagram of PAP authentication.....................................................................................4-32Figure 4-2 Networking diagram of unidirectional CHAP authentication..........................................................4-34Figure 4-3 Networking diagram of bidirectional CHAP authentication............................................................4-37Figure 4-4 Networking diagram of the MP-group binding................................................................................4-39Figure 5-1 Networking diagram of connecting routers using the POS interface through FR network................5-9Figure 6-1 Networking diagram of the HDLC functions...................................................................................6-14Figure 6-2 Networking diagram of the HDLC basic function...........................................................................6-16Figure 6-3 Configuring an IP-Trunk..................................................................................................................6-18Figure 7-1 Networking diagram for IPoA configuration...................................................................................7-38Figure 7-2 Networking diagram for ATM OAM configuration.........................................................................7-41Figure 7-3 Networking diagram of IMAoPSN configurations..........................................................................7-45Figure 8-1 Stack protocol of 1483B.....................................................................................................................8-2Figure 8-2 Networking diagram of IPoEoA configuration..................................................................................8-7Figure 8-3 Networking diagram of ATM bridged Ethernet.................................................................................8-9Figure 8-4 Networking diagram of IPoEoA configuration................................................................................8-12

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access Figures


xvii

Tables

Table 1-1 Index modes of the synchronous serial interface.................................................................................1-2Table 3-1 Relationship between common transmission rates of SONET and SDH............................................3-2Table 3-2 Link layer conditions of the E1/T1/E3/T3 supported by the NE80E/40E...........................................3-8Table 3-3 Working modes of the E1/T1/E3/T3 channels supported by the NE80E/40E.....................................3-9

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access Tables


xix

1 Serial Interface Configuration

About This Chapter

This chapter describes the physical attributes and configuration procedures of synchronous serialinterfaces.

1.1 Introduction to the Serial InterfaceDescribes the basic concepts and features of serial interfaces supported by the NE80E/40E.

1.2 Configuring the Link Layer Attributes for a Serial InterfaceDescribes how to configure link layer attributes for a serial interface.

1.3 Maintaining Serial Interface ConfigurationDescribes how to maintain serial interfaces.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access 1 Serial Interface Configuration


1-1

1.1 Introduction to the Serial InterfaceDescribes the basic concepts and features of serial interfaces supported by the NE80E/40E.

1.1.1 Overview of the Synchronous Serial Interface

1.1.2 Features of the Synchronous Serial Interface on the NE80E/40E

1.1.1 Overview of the Synchronous Serial InterfaceA serial interface is one of the most commonly used WAN interfaces. It can be classified intosynchronous serial interfaces and asynchronous serial interfaces. At present, synchronous serialinterfaces are widely used. Serial interfaces in this chapter refer to synchronous serial interfacesunless otherwise specified.

The serial interfaces, which are channelized by E-carrier, T-carrier, and CPOS interfaces andfunction as common serial interfaces, have the same logical features as synchronous serialinterfaces.

1.1.2 Features of the Synchronous Serial Interface on the NE80E/40E

On the NE80E/40E, various synchronous serial interfaces formed by channelizing physicalinterfaces support the configuration of the MTU and link layer protocols. Table 1-1 shows theindex modes of synchronous serial interfaces.

Table 1-1 Index modes of the synchronous serial interface

Physical Interface Index Mode

E1/T1 channelized by CPOS slot/card/port/channel:0 or slot/card/port/channel:channel-set

E3/T3 channelized by CPOS slot/card/port/channel:0

CE1 and CT1 slot/card/port:channel-set or slot/card/port:0

E3 and CT3 slot/card/port/0:0 or slot/card/port/channel:0 or slot/card/port/channel:channel-set

1.2 Configuring the Link Layer Attributes for a SerialInterface

Describes how to configure link layer attributes for a serial interface.

1.2.1 Establishing the Configuration Task

1.2.2 Configuring Link Layer Protocol Type

1.2.3 Configuring Hold-Interval of the Link Layer Protocol of the Synchronous Serial Interface

1.2.4 Configuring the MTU

1 Serial Interface ConfigurationHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access

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

Issue 03 (2010-03-31)

The MTU of a serial interface affects the assembling and disassembling of IP packets on theinterface.

1.2.5 Configuring the Parity Bit

1.2.6 Checking the Configuration


Applicable Environment

To configure link layer attributes for a serial interface, ensure that the link layer protocol of theserial interface is Up when it is used to bear upper layer services.

Pre-configuration Tasks

Before configuring link layer attributes for a serial interface, complete the following tasks:

l Powering on and starting the router normally

l Connecting the serial interface, configuring physical parameters for the interface, andensuring that the physical layer of the interface is Up

Data Preparation

To configure link layer attributes for a serial interface, you need the following data.

No. Data

1 Number of the synchronous serial interface on the router

2 Link layer protocol type of the interface

3 Hold-interval of the link layer protocol

4 MTU of the interface

5 Check bit of CRC of the interface

1.2.2 Configuring Link Layer Protocol Type

Context

The type of link layer protocols affects the format of link layer frames of the data that passesfrom the synchronous serial interface.

For detailed configurations of each link layer protocol, refer to the chapters PPP and MPConfiguration, ATM Configuration, FR Configuration, and HDLC and IP-TrunkConfiguration.

Do as follows on the routers:



1-3

Procedure

Step 1 Run:system-view

The system view is displayed.

Step 2 Run:interface serial interface-number

The serial interface view is displayed.

Step 3 Run:link-protocol { atm | fr | hdlc | ppp | tdm }

The type of link layer protocols is configured on the interface.

By default, PPP is adopted as the link layer protocol.

NOTE

The link layer protocol can be configured as ATM or TDM only on CE1 interfaces and synchronizationserial interfaces channelized from CPOS interfaces.

You can create a PW tunnel on an interface with the link layer protocol being TDM. For specificconfigurations, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.

NOTE

The link layer protocol can be configured as ATM or TDM only on CE1 interfaces and synchronizationserial interfaces channelized from CPOS interfaces.

You can create a PW tunnel on an interface with the link layer protocol being TDM. For specificconfigurations, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.

A synchronous serial interface formed by E3 and CT3 interfaces supports only PPP and HDLC as linklayer protocols.

----End

1.2.3 Configuring Hold-Interval of the Link Layer Protocol of theSynchronous Serial Interface

ContextDo as follows on the routers:

Procedure




The synchronous serial interface view is displayed.

Step 3 Run:timer hold hold-interval



Issue 03 (2010-03-31)

The hold-interval of the link layer protocol is configured.

Both ends of a link send detection packets to each other to detect and maintain the connectivityof the link.

By default, the hold-interval of the link layer protocol is 10 seconds. If the hold-interval isconfigured as 0, it means that the detection packets are no longer sent or detected.

----End

1.2.4 Configuring the MTUThe MTU of a serial interface affects the assembling and disassembling of IP packets on theinterface.

Procedure





Step 3 Run:mtu mtu

The MTU is configured for a serial interface.

----End

1.2.5 Configuring the Parity Bit


Procedure




The synchronous serial interface view is displayed.

Step 3 Run:crc { 16 | 32 }

The CRC check word length of the synchronous serial interface is configured.



1-5

When configuring the check word length of CRC on a synchronous serial interface, ensure thatthe configurations on the devices at both ends are consistent.

By default, the length of a CRC check word is 32 bits.

----End


Procedurel Run the display interface serial [ interface-number ] [ | { begin | exclude | include }

regular-expression ] command to check the status and statistics of a serial interface.l Run the display interface brief [ | { begin | include | exclude } regular-expression ]

command to check the brief information about a serial interface.l Run the display ip interface brief serial interface-number command to check Check the

network layer configuration of a serial interface.

----End

ExampleRun the following commands to check the previous configuration.

Action Command

Check the status and statistics ofa serial interface.

display interface serial [ interface-number ] [ | { begin| exclude | include } regular-expression ]

Check the brief information abouta serial interface.

display interface brief [ | { begin | include | exclude }regular-expression ]

Check the network layerconfiguration of a serial interface.

display ip interface brief serial interface-number

Run the display interface serial command. You can view the status and statistics of the serialinterface. For example:

<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 Address is 10.1.1.1/24Link layer protocol is PPPLCP opened, IPCP openedPhysical layer is Packet Over ESFclock 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



Issue 03 (2010-03-31)

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 interface brief [ | { begin | include | exclude } regular-expression ] command.You can view the brief information, including the physical status of the serial interface, statusof the link protocol, bandwidth utilization, and the number of errored packets. For example:<HUAWEI> display interface brief | include SerialPHY: 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 outErrors

Serial1/0/0:0 up down 0.01% 0% 599493799 0

Run the display ip interface brief command. You can view the IP configuration of the interface.For example:<HUAWEI> display ip interface brief serial 1/0/0:0*down: administratively down!down: FIB overload down(l): loopback(s): spoofingThe number of interface that is UP in Physical is 2The number of interface that is DOWN in Physical is 1The number of interface that is UP in Protocol is 2The number of interface that is DOWN in Protocol is 1

Interface IP Address/Mask Physical ProtocolAux0/0/1 unassigned *down downGigabitEthernet0/0/0 1.1.1.2/24 up upSerial1/0/0:0 10.1.1.1/24 up up

1.3 Maintaining Serial Interface ConfigurationDescribes how to maintain serial interfaces.

1.3.1 Clearing the Interface Statistics


Context

CAUTIONThe statistics cannot be restored after you clear it. So, confirm the action before you use thecommand.

To clear the interface statistics in the Network Management System (NMS) or those displayedby running the display interface command, run the following commands in the user view.



1-7

NOTE

For the display of interface statistics in the NMS, refer to related NMS manuals.

Procedurel Run the reset counters interface [ serial [ interface-number ] ] command to clear the

interface statistics displayed by running the display interface command.l Run the reset counters if-mib interface [ serial [ interface-number ] ] command to clear

the interface statistics in the NMS.

----End



Issue 03 (2010-03-31)

2 E-Carrier and T-Carrier InterfaceConfiguration

About This Chapter

Describes the basic concepts, configuration procedures, and configuration examples of E-Carrierand T-Carrier interfaces.

2.1 Introduction to the E-Carrier and T-Carrier InterfaceDescribes the fundamentals and concepts of E-Carrier and T-Carrier interfaces.

2.2 Configuring CE1 InterfacesDescribes how to configure CE1 interfaces.

2.3 Configuring CT1 InterfacesDescribes how to configure CT1 interfaces.

2.4 Configuring E3 InterfacesDescribes how to configure E3 interfaces.


2.6 Configuring a T1 Channel of CT3 InterfacesDescribes how to configure a T1 channel of a CT3 interface.

2.7 Maintaining E-Carrier and T-Carrier Interface ConfigurationDescribes how to maintain E-Carrier and T-Carrier interfaces.

2.8 Configuration ExamplesProvides a configuration example of the E3 interface.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access 2 E-Carrier and T-Carrier Interface Configuration


2-1

2.1 Introduction to the E-Carrier and T-Carrier InterfaceDescribes the fundamentals and concepts of E-Carrier and T-Carrier interfaces.

2.1.1 E-Carrier and T-Carrier Overview

2.1.2 Features of E-Carrier and T-Carrier Interfaces in the NE80E/40E

2.1.1 E-Carrier and T-Carrier Overview

Basic Concepts of E-Carrier and T-Carrier

The present digital transmission system adopts Pulse Code Modulation (PCM). PCM wasinitially designed to enable a trunk line among telephone exchanges to transfer multipletelephones. PCM has the following mutually incompatible international standards:

l European 30-channel PCM is called E1. 30 channels indicate that E1 has 32 timeslots, inwhich 30 timeslots are used to transmit data. Timeslot 0 is used to transmit framesynchronization and warning signals. Timeslot 15 is used to transmit control signaling. Therate of E1 is 2.048 Mbit/s. E1 supported by the NE80E/40E is 31-channel PCM. Timeslot15 also transmits data.

l The 24-channel PCM of North America is called T1. 24 channels indicate that T1 has 24timeslots that can be used to transmit data. The rate of T1 is 1.544 Mbit/s.

E-carrier is a digital communication system recommended by International TelecommunicationUnion-Telecommunication Standardization Sector (ITU-T). It starts from E1 and has beenapplied in regions except North America.

The American National Standards Institute (ANSI) set up the T-carrier system standard in theT1.107 Specification. The standard starts from T1 and has been widely applied in NorthAmerican region. Similar to T1, Japan's J1 also belongs to the T-carrier system standard.

The primary features of T-carrier and E-carrier are mostly the same although they differ in detailsof the protocols used by them.

Digital Carrier System

With the carrier system, a single physical communication channel can contain multiple logicalchannels. Therefore, it supports multi-channel communication.

In the digital carrier system, a single digital circuit with a large capacity supports multiple logicalchannels, each of which supports one independent channel.

Channelized, Unchannelized, and Clear Channel Modes

The operation mode of E-carrier and T-carrier interfaces involves the following concepts:

l Channelized: In framed mode, all timeslots except the frame header in data stream can beallocated to different channels.

l Unchannelized: In framed mode, all timeslots except the frame header in data stream areallocated to only one channel and are bound only once.

2 E-Carrier and T-Carrier Interface ConfigurationHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access


Issue 03 (2010-03-31)

l Clear Channel: It is also called the unframed mode. That is, there is no frame flag in thedata stream, and all bits are data bits and belong to the same channel.

Introduction to CE1 Interface

When a physical interface formed by E1 works in clear channel mode or channelized mode only,this interface is called a CE1 interface.

A CE1 interface has the following characteristics:

l In clear channelized mode, also called the unframed mode, the CE1 interface functions likean interface with no divided timeslot and the data bandwidth of 2.048 Mbit/s. It has thesame logical features as a synchronous serial interface, supporting network protocols suchas IP, link layer protocols such as PPP, HDLC and MP binding.

l In channelized mode, also called the framed mode, the CE1 interface is physically dividedinto 32 timeslots numbered from 0 to 31, which can be freely bound into a logical channelof N x 64 kbit/s.Each bound channel-set of timeslots is used as an interface with the same logical featuresas a synchronous serial interface, supporting network protocols such as IP, link layerprotocols such as PPP, HDLC, ATM, TDM and MP binding.

Introduction to CT1 Interfaces

When a physical interface formed by T1 works in clear channel mode or channelized mode only,this interface is called a CT1 interface.

A CT1 interface has the following characteristics:

l In clear channelized mode, also called the unframed mode, the CT1 interface functions likean interface with no divided timeslot and the data bandwidth of 1.544 Mbit/s. The interfacehas the same logical features as a synchronous serial interface, supporting networkprotocols such as IP, link layer protocols such as PPP, HDLC and MP binding.

l In channelized mode, also called the framed mode, the CT1 interface is physically dividedinto 24 timeslots numbered from 0 to 23, which can be freely bound into a logical channelof N x 64 kbit/s.When being used as CT1 mode, all timeslots can be freely divided into several channel-sets. Each bound channel-set of timeslots is used as an interface with the same logicalfeatures as a synchronous serial interface, supporting network protocols such as IP, linklayer protocols such as PPP, HDLC and MP binding.

Introduction to E3 Interfaces

An E3 interface has two working modes:

l In clear channelized mode, also called the unframed mode, the E3 interface functions likean interface with no divided timeslot and the data bandwidth of 34.368 Mbit/s.

l When the E3 interface works in unchannelized mode, a type of the framed mode, data istransmitted in the channel in the form of frames. All timeslots are bound to form a channelthat functions as an interface with the data bandwidth of 33.831 M without timeslot division.The logical feature of the channel is the same as that of a synchronous serial interface.

An E3 interface supports network protocols such as IP and link layer protocols such as PPP andHDLC.



2-3

Introduction to CT3 Interfaces

A CT3 interface has three working modes:

l In clear channelized mode, also called the unframed mode, the CT3 interface functions likean interface with no divided timeslot and the data bandwidth of 44.736 Mbit/s.

l When the CT3 interface works in unchannelized mode, one type of the framed mode, datais transmitted in the channel in the form of frames. All timeslots are bound to form a channelthat functions as an interface with the data bandwidth of 44.210 M without timeslot division.The logical feature of the channel is the same as that of a synchronous serial interface.

l When working in channelized mode, the other type of the framed mode, a CT3 interfacecan multiplex or demultiplex 28 T1 signals. Each T1 can be configured separately. Eachserial interface can function as an interface whose logical feature is the same as that of asynchronous serial interface.

A CT3 interface supports network protocols such as IP and link layer protocols such as PPP andHDLC.

2.1.2 Features of E-Carrier and T-Carrier Interfaces in the NE80E/40E

Types of E-Carrier and T-Carrier Interfaces

The E-carrier interface types supported by the NE80E/40E are as follows:

l CE1 interfaces

l E3 interfaces

The T-carrier interface types supported by the NE80E/40E are as follows:

l CT1 interfaces

l CT3 interfaces

Introduction to the Channelized Serial InterfaceThe serial interface formed by the E-carrier or T-carrier interface is called the channelized serialinterface. A channelized serial interface has the same logical features as a synchronous serialinterface.

The method of configuring link layer attributes of a channelized serial interface is the same asthat of a synchronous serial interface. For details, refer to the HUAWEI NetEngine80E/40ERouter Configuration Guide - Serial Interface Configuration.

2.2 Configuring CE1 InterfacesDescribes how to configure CE1 interfaces.


2.2.2 Creating Synchronous Serial Interface for CE1 Interface

2.2.3 Configuring Coding or Decoding Format of CE1 Interface



Issue 03 (2010-03-31)

2.2.4 Configuring Clock Mode of CE1 Interface

2.2.5 Configuring Frame Format of the CE1 Interface




An CE1 interface should be configured when it bears upper layer services.

CAUTIONl When a physical interface is not installed with any cable, run the shutdown command to

disable this interface to avoid interference.l After configuring the interface service, run the shutdown and undo shutdown commands

in the current interface view to ensure that the configured service is loaded to the interfacesuccessfully.

l Disabling the CE1 interface may affect the normal operation of its channel-set.


Before configuring CE1 interfaces, complete the following task:

l Powering on the router and starting it normally

Data Preparation

To configure CE1 interfaces, you need the following data.

No. Data

1 CE1 interface number of the router

2 Number of the channel into which the timeslots of the CE1 interface are bound

3 Number or range of the timeslot bound into a channel set

2.2.2 Creating Synchronous Serial Interface for CE1 Interface

Context

Create the synchronous serial interface with the specific rate on a CE1 interface:l When the CE1 interface works in clear channel mode, a synchronous serial interface can

be configured for the CE1 interface. The synchronous serial interface transmits data in thespeed of 2.048 Mbit/s, without timeslot division.



2-5

l When the CE1 interface works in channelized mode, timeslots 1 to 31 of the CE1 interfacecan be randomly bound together to function as one or multiple logical channels, that is,synchronous serial interfaces, with the rate of each interface calculated as N x 64 kbit/s. Nstands for the number of timeslots.

NOTE

By default, a CE1 interface works in channelized mode.


Procedurel Create the synchronous serial interface in clear channel mode.

1. Run:system-view

The system view is displayed.2. Run:

controller e1 controller-number

The CE1 interface view is displayed.3. Run:

using e1The CE1 interface is configured to the clear channel mode, and then a synchronousserial interface is configured for the CE1 interface. The synchronous serial interfacetransmits data in the speed of 2.048 Mbit/s, without timeslot division.

You can run the interface serial controller-number: 0 command to access thesynchronous serial interface.

l Create the synchronous serial interface in channelized mode.1. Run:

system-view



The CE1 interface view is displayed.3. Run:

using ce1The CE1 interface is configured to the channelized mode.

4. Run:channel-set set-number timeslot-list { ts0 | slot-list [ ts0 ] }The timeslots of the CE1 interface are bound together to function as a synchronousserial interface with the rate as N x 64 kbit/s. N stands for the number of boundtimeslots.

You can run the interface serial controller-number: set-number command to accessthe synchronous serial interface.

– To change an interface from the CE1 mode to the E1 mode, you need delete allconfigurations in CE1 mode and all synchronous serial interfaces, and then run theusing e1 command.



Issue 03 (2010-03-31)

– To change an interface from the E1 mode to the CE1 mode, you need delete all theconfigurations in E1 mode and all the configurations of synchronous serialinterfaces, but need not delete these interfaces. Then you can run the using ce1orundo using command.

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

Timeslot 0 is used to transmit frame synchronization and alarm information. Aftertimeslot 0 is bound to form a serial interface, frame synchronization and alarminformation can be transparently transmitted between the client and the server throughthe serial interface.

----End

2.2.3 Configuring Coding or Decoding Format of CE1 Interface

ContextAn CE1 interface supports the following coding or decoding formats:

l AMI format: Alternate Mark Inversion

l HDB3 format: High Density Bipolar of Order 3


Procedure



Step 2 Run:controller e1 controller-number

The CE1 interface view is displayed.

Step 3 Run:code { ami | hdb3 }

The coding or decoding format of the CE1 interface is configured.

By default,a CE1 interface works in HDB3 coding or decoding format.

----End

2.2.4 Configuring Clock Mode of CE1 Interface

ContextA CE1 interface supports the following clock modes:

l Master clock mode: uses internal clock signals.

l Slave clock mode: uses line clock signals.



2-7

When CE1 interfaces of two routers are connected directly, configure one interface to work inmaster clock mode and the other interface in slave clock mode. When the CE1 interface of arouter is connected with a transmission device, configure this interface to work in slave clockmode and use the clock signals provided by the transmission device.


Procedure



Step 2 Run:controller e1 controller-number


Step 3 Run:clock { master | slave }

Clock mode of the CE1 interface is configured.

NOTE

When being used as a synchronous serial interface, the CE1 interface also has two working modes: DTEand DCE. In this case, you need to choose the clock mode.

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

----End

2.2.5 Configuring Frame Format of the CE1 Interface

Context

The interface can be configured with the frame format only when it works in channelized mode.


Procedure



Step 2 Run:controller e1controller-number


Step 3 Run:frame-format { crc4 | no-crc4 }

The frame format of the CE1 interface is configured.



Issue 03 (2010-03-31)

NOTE

By default, the frame format of the CE1 interface is no-CRC4.

----End


Procedurel Run the display interface serial [ interface-number ] [ | { begin | exclude | include }

regular-expression ] command to check the configuration and status of the channel-set.

l Run the display controller e1 [ controller-number ] command to check the configurationand status of the CE1 interface.

----End

Example

Run the display interface serial command. You can view the configuration of the channel-setand status of the CE1 interface.

<HUAWEI> display interface serial 1/0/0:2Serial1/0/0:2 current state : UPLine protocol current state : UPLast line protocol up time : 2009-01-20 15:55:16Description : Serial1/0/0:2 InterfaceRoute Port, The Maximum Transmit Unit is 1500, Hold timer is 10(sec)Derived from E1 1/0/0, Timeslot(s) Used: 31, baudrate is 64000 bpsInternet protocol processing : disabledLink layer protocol is PPPLCP openedCRC: 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 e1 command. You can view the configuration and status informationof the CE1 interface.

<HUAWEI> display controller e1 1/0/0E1 1/0/0 current state : DOWNDescription : E1 1/0/0 Interface

Physical layer is Packet Over NO-CRC4clock master, linecode hdb3 , loopback nonesection layer: alarm: LOSline layer: alarm: nonepath layer: alarm: none



2-9



2.3.2 Creating Synchronous Serial Interface for CT1 Interface

2.3.3 Configuring Coding or Decoding Format of the CT1 Interface

2.3.4 Configuring Clock Mode of the CT1 Interface

2.3.5 Configuring Frame Format of the CT1 Interface



Applicable EnvironmentA CT1 interface needs to be configured when it bears upper layer services.


disable this interface to avoid interference.l After configuring the interface service, run the shutdown and the undo shutdowncommands


l Disabling the CT1 interface may affect the normal operation of its channel-set.

Pre-configuration TasksBefore configuring CT1 interfaces, complete the following task:


Data PreparationTo configure a CT1 interface, you need the following data.

No. Data

1 CT1 interface number of the router

2 Number of the channel into which the timeslots of the CT1 interface timeslot arebound

3 Number or range of the timeslot bound into a channel-set



Issue 03 (2010-03-31)


ContextCreate the synchronous serial interface with the specific rate on a CT1 interface:l When the CT1 interface works in clear channel mode, a synchronous serial interface can

be configured on the CT1 interface. The synchronous serial interface transmits data in thespeed of 1.544 Mbit/s, without timeslot division.

l When the CT1 interface works in channelized mode, timeslots 0 to 23 of the CT1 interfacecan be randomly bound together to function as one or several logical channels, that is,synchronous serial interfaces, with the rate of each interface calculated as N x 64 kbit/s. Nstands for the number of timeslots.


Procedurel Create the synchronous serial interface in clear channel mode.

1. Run:system-view


controller t1 controller-number

The CT1 interface view is displayed.3. Run:

using t1The CT1 interface is configured to the clear channel mode, and then a synchronousserial interface is configured for the CT1 interface. The synchronous serial interfacetransmits data in the speed of 1.544Mbit/s, without timeslot division.

You can run the interface serial controller-number:0 command to access thesynchronous serial interface.

l Create the synchronous serial interface in channelized mode.1. Run:

system-view




using ct1The CT1 interface is configured to the channelized mode.

4. Run:channel-set set-number timeslot-list slot-listThe timeslots of the CT1 interface are bound together to function as a synchronousserial interface with the rate as N x 64 kbit/s. N stands for the number of boundtimeslots.



2-11

You can run the interface serial controller-number:set-number command to accessthe synchronous serial interface.

– To change an interface from the CT1 mode to the T1 mode, you need delete allconfigurations in CT1 mode and all synchronous serial interfaces, and then run theusing t1 command.

– To change an interface from the T1 mode to the CT1 mode, you need delete all theconfigurations in T1 mode and all the configurations of synchronous serialinterfaces, but need not delete these interfaces. Then you can run the using t1command.

----End

2.3.3 Configuring Coding or Decoding Format of the CT1 Interface

ContextA CT1 supports the following coding or decoding formats:

l AMI: Alternate Mark Inversion

l B8ZS: Bipolar with 8-Zero Substitution


Procedure



Step 2 Run:controller t1 controller-number

The CT1 interface view is displayed.

Step 3 Run:code { ami | b8zs }

The coding or decoding format of the CT1 interface is configured.

By default, b8zs is used on CT1 interface.

----End

2.3.4 Configuring Clock Mode of the CT1 Interface

ContextA CT1 interface supports the following clock modes:



When a CT1 interface is used as the DCE device, configure the CT1 interface to work in masterclock mode. Configure the CT1 interface to work in slave clock mode when it is used as the



Issue 03 (2010-03-31)

DTE device. When CT1 interfaces of two routers are connected directly, configure one interfaceto work in master clock mode and the other interface in slave clock mode.


Procedure






The clock mode of the CT1 interface is configured.

----End

2.3.5 Configuring Frame Format of the CT1 Interface

Context

A CT1 interface supports the following frame formats:

l ESF: Extended Super Frame

l SF: Super Frame


Procedure





Step 3 Run:frame-format { esf | sf }

Frame format of the CT1 interface is configured.

By default, the frame format of the CT1 interface is ESF.

----End



2-13


Procedurel Run the display interface serial [interface-number ] [ | { begin | exclude | include }

regular-expression ] command to check the status and statistics of the serial interface boundby timeslots.

l Run the display controller t1 [ controller-number ] command to check configuration andstatus of the CT1 interface.

----End

ExampleRun the display interface serial command. You can view the information about the channel-set configuration and interface status.

<HUAWEI> display interface serial 1/0/0:2Serial1/0/0:2 current state : UPLine protocol current state : UPLast line protocol up time : 2009-01-20 15:55:16Description : Serial1/0/0:2 InterfaceRoute Port,The Maximum Transmit Unit is 1500 bytes, Hold timer is 10(sec)Derived from T1 1/0/0, Timeslot(s) Used: 3-10, baudrate is 512000 bpsInternet protocol processing : disabledLink layer protocol is PPPLCP openedPhysical layer is Channelized T1clock master, loopback noneCRC: CRC-32Scramble disabledAlarm: NoneStatistics last cleared:2009-01-20 15:55:04 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: 30 packets, 372 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

Run the display controller t1 command. You can view the information about the coding format,frame format and clock mode of the CT1 interface.

<HUAWEI> display controller t1 1/0/0T1 1/0/0 current state : Administratively DOWNDescription : T1 1/0/0 Interface clock master, no loopback linecode b8zs, frame-format ESF alarm:None,workmode:CT1

2.4 Configuring E3 InterfacesDescribes how to configure E3 interfaces.


2.4.2 Creating Synchronous Serial Interface for E3 Interface




Issue 03 (2010-03-31)


Applicable EnvironmentA E3 interface needs to be configured when it bears upper layer services.


disable this interface to avoid interference.l After configuring the interface service, run the shutdown and the undo shutdown commands

in current interface view to ensure that the configured service is loaded to the interfacesuccessfully.

l Disabling or enabling a E3 interface is valid on the CE3 channel and the serial interfaceformed by the E3 interface.

Pre-configuration TasksBefore configuring E3 interfaces, complete the following task:


Data PreparationTo configure E3 interfaces, you need the following data.

No. Data

1 E3 interface number of the router

2.4.2 Creating Synchronous Serial Interface for E3 Interface

ContextE3 interfaces work in either of the following modes:

l Clear channel mode (also known as E3 mode)When a E3 interface is configured to work in clear channel mode, a synchronous serialinterface that operates at 34.368 Mbit/s is generated and named serial slot/card/port/0:0.

l Unchannelized mode (also known as CE3 mode)When a E3 interface is configured to work in unchannelized mode, a framed E3 channelmust be manually created to form a synchronous serial interface named serial slot/card/port/0:0.

By default, a E3 interface works in unchannelized mode.

Do as follows on routers:



2-15

Procedurel Configure a E3 interface to work in clear channel mode.

1. Run:system-view



The E3 interface view is displayed.3. Run:

using e3

The E3 interface is configured to work in clear channel mode.l Configure a E3 interface to work in unchannelized mode.

1. Run:system-view



The E3 interface is displayed.3. Run:

using ce3

The E3 interface is configured to work in unchannelized mode.4. Run:

e3 framed

A framed E3 channel is created.

Then a synchronous serial interface is generated and named serial slot/card/port/0:0.

----End


Procedure

Step 1 Run the display controller e3 [ controller-number ] command to check the status of the E3interface.

----End

ExampleRun the display controller e3 command. You can view the clock mode and frame format of theE3 interface.

<HUAWEI> display controller e3 6/0/0E3 6/0/0 current state : UP Description : E3 6/0/0 Interface Physical layer is Packet Over G.751, clock master, loopback localsection layer:



Issue 03 (2010-03-31)

alarm: none line layer: alarm: nonepath layer: alarm: none




2.5.3 Configuring Frame Format of the CT3 InterfaceT1 corresponds to the digital signal level DS-1. With bit multiplexing, 28 T1s form T3. Twoframe formats are used: C-bit and M23.



Applicable EnvironmentA CT3 interface needs to be configured when it bears upper layer services.


disable this interface to avoid interference.l After configuring the interface service, run the shutdown and undo shutdown commands


l Disabling or enabling a CT3 interface is valid on the serial interface formed by the CT3channel, the T1 channel demultiplexed by the CT3 channel, and the serial interface formedby binding the CT3 channel.

Pre-configuration TasksBefore configuring CT3 interfaces, complete the following task:


Data PreparationTo configure a CT3 interface, you need the following data.

No. Data




2-17


ContextCT3 interfaces work in either of the following modes:

l Unframed mode (also known as clear channel mode or T3 mode)When a CT3 interface is configured to work in clear channel mode, a synchronous serialinterface that operates at 44.736 Mbit/s is generated and named serial slot/card/port/0:0.

l Framed mode (also known as CT3 mode) including unchannelized mode and channelizedmode– When a CT3 interface works in unchannelized mode, a framed T3 channel must be

manually created to form a synchronous serial interface for data transmission.– When working in channelized mode, a CT3 interface is demultiplexed into 28 T1

channels that operate at 1.544 Mbit/s. These T1 channels can be configured separately.– When a T1 channel works in clear channel mode, the T1 channel without timeslot

division forms a 1.544 Mbit/s serial interface.– When a T1 channel works in channelized mode, timeslots 0 to 23 of a T1 channel

can be randomly bound to form a serial interface. The default rate of the channel-set that is formed by binding T1 timeslots is N x 64 kbit/s (N represents the numberof timeslots that are bound).

By default, a CT3 interface works in channelized mode.


Procedurel Configure a CT3 interface to work in clear channel mode.

1. Run:system-view




using t3

The CT3 interface is configured to work in clear channel mode. Then a synchronousserial interface can be configured for the CT3 interface. The synchronous serialinterface transmits data in the speed of 44.736 Mbit/s, without timeslot division.


l Configure a CT3 interface to work in unchannelized mode.1. Run:

system-view




Issue 03 (2010-03-31)

2. Run:controller t3 controller-number


using ct3

The CT3 interface is configured to work in framed mode.4. Run:

t3 framed

A framed T3 channel is created. Then a synchronous serial interface can be configuredfor the CT3 interface.


l Configure a CT3 interface to work in channelized mode.1. Run:

system-view




using ct3

The CT3 interface is configured to work in framed mode.4. Run either of the following commands to create the synchronous serial interface of

the T1 channel.– Run the t1 t1-number unframed command to create the synchronous serial

interface with the rate as 1.544 Mbit/s.You can run the interface serial controller-number/t1-number:0 command toaccess the synchronous serial interface.

– Run the t1 t1-number channel-set set-number timeslot-list slot-list command tobind N timeslots of the T1 channel of the CT3 interface together to create asynchronous serial interface with the rate as N x 64kbit/s.You can run the interface serial controller-number/t1-number:set-numbercommand to access the synchronous serial interface.

----End

2.5.3 Configuring Frame Format of the CT3 InterfaceT1 corresponds to the digital signal level DS-1. With bit multiplexing, 28 T1s form T3. Twoframe formats are used: C-bit and M23.

Contextl C-bit is also called the C-bit parity check. When C-bit is set, the stuffing indication bit can

be used for maintenance.



2-19

l M23 is the multiplexing process from DS-2 to DS-3. Four T1s (DS-1) are multiplexed asa DS-2 line through M12. Seven DS-2 lines are multiplexed as T3 (DS-3) through M23.


Procedure





Step 3 Run:frame-format { c-bit | m23 }

Frame format of the CT3 interface is configured.

----End


Procedurel Run the display controller t3 [ controller-number ] command to check the status of the

CT3 interface.l Run the display interface serial interface-number command to check the status of the

serial interface.

----End

ExampleRun the display controller t3 command. You can view the clock mode and frame format of theCT3 interface.

<HUAWEI> display controller t3 1/0/0T3 1/0/0 current state : Administratively DOWNDescription : T3 1/0/0 InterfacePhysical layer is Packet Over C-Bit, clock master, loopback none section layer: alarm: OOF LOF line layer: alarm: none path layer: alarm: none

Run the display interface serial command. You can view the status of the serial interface.<HUAWEI> display interface serial 1/0/0/0:0Serial1/0/0/0:0 current state : UPLine protocol current state : UPLast line protocol up time : 2009-01-20 15:55:16Description:Serial1/0/0/0:0 InterfaceRoute Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec)Derived from T3 1/0/0, Unchannelized mode, baudrate is 44210000 bpsInternet protocol processing : disabledLink layer protocol is PPP



Issue 03 (2010-03-31)

LCP openedclock slave, loopback none CRC: CRC-16 Scramble disabled Statistics last cleared:2008-08-27 16:42:19 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

2.6 Configuring a T1 Channel of CT3 InterfacesDescribes how to configure a T1 channel of a CT3 interface.


2.6.2 Configuring Clock Mode of a T1 Channel

2.6.3 Configuring Frame Format of a T1 Channel




Before using a CT3 interface to bear upper layer services, you need to configure parameters forthe CT3 interface. When a CT3 interface works in channelized mode, the T1 channels on theCT3 interface need to be configured.


Before configuring a T1 channel on the CT3 interface, complete the following tasks:


l Connecting the CT3 interface and configuring physical attributes for the CT3 interface

l Connecting the CT3 interface to work in the channelized mode

Data Preparation

To configure a T1 channel of the CT3 interface, you need the following data.

No. Data


2 T1 channel number

3 Timeslot number, timeslot range, or number of the channel of the T1 interface



2-21

2.6.2 Configuring Clock Mode of a T1 Channel

ContextA T1 interface supports the following clock modes:



The selection of the clock mode depends on the connected peer device. When a T1 interface isconnected to a transmission device, configure the T1 interface to work in slave clock mode. Ifthe CT3 interfaces of two routers are directly connected, configure one interface to work inmaster clock mode and the other interface in slave clock mode.

By default, the CT3 interface works in master clock mode.


Procedure





Step 3 Run:t1 t1-number set clock { master | slave }

Clock mode of the T1 channel is configured.

----End

2.6.3 Configuring Frame Format of a T1 Channel

ContextA T1 channel supports the following frame formats:

l ESF: Extended Super Frame

l SF: Super Frame

By default, a T1 channel uses ESF.


Procedure





Issue 03 (2010-03-31)



Step 3 Run:t1 t1-number set frame-format { esf | sf }

Frame format of the T1 channel is configured.

----End


Procedurel Run the display controller t3 [ controller-number ] command to check the status of the

CT3 interface.l Run the display interface serial interface-number command to check the status of the

serial interface.

----End

ExampleRun the display controller t3 command. You can view the clock mode and frame format of theCT3 interface.

<HUAWEI> display controller t3 1/0/0T3 1/0/0 current state : DOWN Description : T3 1/0/0 InterfacePhysical layer is Packet Over C-Bit, clock slave, loopback nonesection layer: alarm: none line layer: alarm: nonepath layer: alarm: none

Run the display interface serial command. You can view the status of the serial interface.<HUAWEI> display interface serial 1/0/0/1:0Serial1/0/0/1:0 current state : DOWN Line protocol current state : UPLast line protocol up time : 2009-01-20 15:55:16 Description:Serial1/0/0/1:0 Interface Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec) Derived from T3 1/1/0 t1 1, Timeslot(s) Used: 0-23, baudrate is 1536000 bps Internet protocol processing : disabledLink layer protocol is PPP LCP opened Physical layer is Packet Over ESFclock master, loopback none CRC: CRC-16 Scramble disabled Alarm: None Statistics last cleared:2008-08-27 16:50:02 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



2-23

Output: 0 packets, 0 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

2.7 Maintaining E-Carrier and T-Carrier InterfaceConfiguration

Describes how to maintain E-Carrier and T-Carrier interfaces.

2.7.1 Setting Loopback to Detect Whether the Interface Is Normal


2.7.1 Setting Loopback to Detect Whether the Interface Is Normal

Context

CAUTIONAfter you configure the self-loop (run the loopback command), the interface on a router or thelink cannot run normally. Thus, you must check whether to set the self-loop. After the detection,run the undo loopback command to disable the self-loop.

Do as follows on the routers to be detected:

Procedure



Step 2 Run:controller controller-type controller-number

The view of the interface to be detected is displayed.

Step 3 According to the interface type, choose one of the following commands to enable the self-loop.l In the case of an CE1, CT1, E3 or CT3 interface, run the loopback { local | remote }

command.When configuring the loopback of an interface, note the following:– To enable the local loopback of the interface, the interface must be in the master clock

mode.– To enable the remote loopback of the interface, the interface must be in the slave clock

mode.l In the case of the T1 channel of the CT3 interface, run the t1 t1-number set loopback

{ local | remote }

By default, the self-loop is disabled on the interface.

----End



Issue 03 (2010-03-31)


Context

CAUTIONThe interface statistics cannot be restored after you run the reset command to clear it. So, confirmthe action before you use the command.

To reset the interface statistics of the Network Management System (NMS) or those displayedby running the display interface command, run the following commands in the user view. Clearthe interface statistics before collecting the traffic.

NOTE

For the interface statistics in the NMS, refer to related NMS manuals.

Procedurel Run the reset counters interface [ interface-type [ interface-number ] ] command to clear

the interface statistics displayed by running the display interface command.l Run the reset counters if-mib interface [ interface-type [ interface-number ] ] command

to clear the interface statistics in the NMS.

----End

2.8 Configuration ExamplesProvides a configuration example of the E3 interface.

2.8.1 Example for Configuring Communication over CE1 Interfaces Bundle

2.8.1 Example for Configuring Communication over CE1 InterfacesBundle

Networking RequirementsTwo routers connect with each other through two CE1 links and communicate with each otherby bundling these CE1 links.

Figure 2-1 Schematic diagram of CE1 interface configuration

RouterA RouterBCE1 4/0/0

CE1 4/0/1 CE1 4/0/1

CE1 4/0/0Link bundling



2-25

Configuration RoadmapThe configuration roadmap is as follows:

1. Configure a CE1 interface channel.2. Create an interface to be bound.3. Add the interface channel to the bound interface.4. Configure the IP address of the bound interface and re-enabling it.

Data PreparationTo configure a CE1 interface, you need the following data:

l Name of the bound interface

l IP address of the bound interface

l Index number of the interface when the timeslots of the CE1 interface are bound

l Number and range of the timeslots to be bound

NOTE

l On the NE80E/40E, the slot ID and the card ID of the interfaces added to the MP-group must beconsistent with the slot ID and card ID of the MP-group interface. That is, the trans-card binding is notsupported.

l The interfaces added to the MP-group can only be the serial interfaces instead of other interfaces.

Procedure

Step 1 Configure Router A.

# Configure the working mode and channel group of CE1.

<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] controller e1 4/0/0[RouterA-E1 4/0/0] shutdown[RouterA-E1 4/0/0] channel-set 0 timeslot-list 1-31[RouterA-E1 4/0/0] undo shutdown[RouterA-E1 4/0/0] quit[RouterA] controller e1 4/0/1[RouterA-E1 4/0/1] shutdown[RouterA-E1 4/0/1] channel-set 0 timeslot-list 1-31[RouterA-E1 4/0/1] undo shutdown[RouterA-E1 4/0/1] quit

# Create a bound interface.

[RouterA] interface mp-group 4/0/1[RouterA-Mp-group4/0/1] shutdown[RouterA-Mp-group4/0/1] quit

# Add the CE1 channel to the binding group.

[RouterA] interface serial 4/0/0:0[RouterA-Serial4/0/0:0] shutdown[RouterA-Serial4/0/0:0] ppp mp mp-group 4/0/1[RouterA-Serial4/0/0:0] quit[RouterA] interface serial 4/0/1:0[RouterA-Serial4/0/1:0] shutdown[RouterA-Serial4/0/1:0] ppp mp mp-group 4/0/1[RouterA-Serial4/0/1:0] quit



Issue 03 (2010-03-31)

# Restart the sub-channel on Router A.

[RouterA] interface serial4/0/0:0[RouterA-Serial4/0/0:0] undo shutdown[RouterA-Serial4/0/0:0] quit[RouterA] interface serial4/0/1:0[RouterA-Serial4/0/1:0] undo shutdown[RouterA-Serial4/0/1:0] quit

# Configure the IP address for the bound interface and restart the interface.

[RouterA] interface mp-group 4/0/1[RouterA-Mp-group4/0/1] ip address 5.0.0.1 255.255.255.0[RouterA-Mp-group4/0/1] undo shutdown

Step 2 Configure Router B.

# Configure the working mode and channel group of CE1.

<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] controller e1 4/0/0[RouterB-E1 4/0/0] shutdown[RouterB-E1 4/0/0] channel-set 0 timeslot-list 1-31[RouterB-E1 4/0/0] undo shutdown[RouterB-E1 4/0/0] quit[RouterB] controller e1 4/0/1[RouterB-E1 4/0/1] shutdown[RouterB-E1 4/0/1] channel-set 0 timeslot-list 1-31[RouterB-E1 4/0/1] undo shutdown[RouterB-E1 4/0/1] quit

# Create a bound interface.

[RouterB] interface mp-group 4/0/1[RouterB-Mp-group4/0/1] shutdown[RouterB-Mp-group4/0/1] quit

# Add tge CE1 channel to the binding group.

[RouterB] interface serial 4/0/0:0[RouterB-Serial4/0/0:0] shutdown[RouterB-Serial4/0/0:0] ppp mp mp-group 4/0/1[RouterB-Serial4/0/0:0] quit[RouterB] interface serial 4/0/1:0[RouterB-Serial4/0/1:0] shutdown[RouterB-Serial4/0/1:0] ppp mp mp-group 4/0/1[RouterB-Serial4/0/1:0] quit

# Restart the sub-channel on Router B.

[RouterB] interface serial4/0/0:0[RouterB-Serial4/0/0:0] undo shutdown[RouterB-Serial4/0/0:0] quit[RouterB] interface serial4/0/1:0[RouterB-Serial4/0/1:0] undo shutdown[RouterB-Serial4/0/1:0] quit

# Configure the IP address for the binding interface and restart the interface.

[RouterB] interface mp-group 4/0/1[RouterB-Mp-group4/0/1] ip address 5.0.0.2 255.255.255.0[RouterB-Mp-group4/0/1] undo shutdown

Step 3 Vefify the configuration.

Run the display interface command to view the binding status. The link negotiation succeeds.

Take Router A as an example:



2-27

<RouterA> display interface mp-group 4/0/1Mp-group4/0/1 current state : UPLine protocol current state : UPDescription: Mp-group4/0/1 InterfaceRoute Port,The Maximum Transmit Unit is 1500Internet Address is 5.0.0.1/24Link layer protocol is PPPLCP opened, MP opened, IPCP openedPhysical is MP, baudrate is 3968000 bps Traffic statistics: Last 300 seconds input rate 1352 bits/sec, 0 packets/sec Last 300 seconds output rate 824 bits/sec, 0 packets/sec Input: 21395674 packets, 2048796674 bytes 0 errors, 0 drops Output: 96504 packets, 3084968 bytes 0 errors, 0 drops

----End

Configuration Filesl Configuration file of Router A

#sysname RouterA#controller e1 4/0/0 channel-set 0 timeslot-list 1-31#controller e1 4/0/1 channel-set 0 timeslot-list 1-31#interface Serial4/0/0:0link-protocol pppppp mp Mp-group 4/0/1#interface Serial4/0/1:0 link-protocol pppppp mp Mp-group 4/0/1#interface Mp-group4/0/1ip address 5.0.0.1 255.255.255.0#return

l Configuration file of Router B#sysname RouterB#controller e1 4/0/0 channel-set 0 timeslot-list 1-31#controller e1 4/0/1 channel-set 0 timeslot-list 1-31#interface Serial4/0/0:0 link-protocol pppppp mp Mp-group 4/0/1#interface Serial4/0/1:0 link-protocol pppppp mp Mp-group 4/0/1#interface Mp-group4/0/1ip address 5.0.0.2 255.255.255.0#return



Issue 03 (2010-03-31)

3 POS and CPOS Interface Configuration

About This Chapter

Describes the basic concepts, configuration procedures, and configuration examples of Packetover SONET/SDH (POS) interfaces and Channelized POS (CPOS) interfaces.

3.1 Introduction to the POS and CPOS InterfacesDescribes the basic concepts of POS interfaces and CPOS interfaces.

3.2 Configuring POS InterfacesDescribes how to configure a POS interface.

3.3 Configuring STM-1 CPOS InterfacesThis section describes how to configure a STM-1 CPOS interface.

3.4 Configuring E1 Channels of the CPOS InterfaceDescribes how to configure E1 channels of CPOS interfaces.

3.5 Configuring T1 Channels of the CPOS InterfaceThis section describes how to configure T1 channels of CPOS interfaces.

3.6 Configuring E3 Channels of an STM-1 CPOS InterfaceThis section describes how to configure the E3 channels of the STM-1 CPOS interfaces.

3.7 Configuring T3 Channels of an STM-1 CPOS InterfaceThis section describes how to configure T3 channels of an STM-1 CPOS interfaces.

3.8 Maintaining POS and CPOS Interface ConfigurationThis section describes how to maintain POS interfaces and CPOS interfaces.

3.9 Configuration ExamplesThis section provides several configuration examples of POS and CPOS interfaces.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access 3 POS and CPOS Interface Configuration


3-1

3.1 Introduction to the POS and CPOS InterfacesDescribes the basic concepts of POS interfaces and CPOS interfaces.

3.1.1 Overview of POS and CPOS Interfaces

3.1.2 Features of POS and CPOS Interfaces on the NE80E/40E

3.1.1 Overview of POS and CPOS Interfaces

Introduction to SONET and SDH

Synchronous Optical Network (SONET) is the synchronous digital transmission standarddefined by the American National Standards Institute (ANSI) and mainly used in North Americaand Japan. Clocks at each level in an entire network are provided by a very precise master clock.

SONET defines the line rate hierarchical structure of synchronous transmission for the opticaltransmission system. The basic transmission rate of the SONET is 51.84 Mbit/s andapproximately equals the transmission rate of E3/T3.

l For an electrical signal, the transmission rate is called Level 1 Synchronous TransportSignal, namely, STS-1.

l For an optical signal, the transmission rate is called Level 1 Optical Carrier, namely, OC-1.

Adopting synchronous signals, SONET can easily multiplex multiple signals.

Based on SONET, Synchronous Digital Hierarchy (SDH) is an international standard definedby the ITU-T and mainly used in Europe. The corresponding standard of SDH is the proposalsfrom G.707 to G.709 passed in 1988 and the proposals added in 1992.

SDH is similar to SONET to a great extent. The basic rate of SDH is 155.52 Mbit/s, which iscalled Level 1 Synchronous Transfer Module, STM-1. This rate equals the OC-3 rate in SONET.

Adopting synchronous multiplexing and flexible mapping, SDH can multiplex or demultiplexlow-speed tributary signals from SDH signals without using multiplexing or demultiplexingdevices. This reduces signal consumption and equipment investment.

Table 3-1 lists the common transmission rates of SONET and SDH. The hierarchical relationshipbetween common transmission rates is four times. For convenience, the approximations in theparentheses are often used to express transmission rates.

Table 3-1 Relationship between common transmission rates of SONET and SDH

SONET SDH Transmission Rate(Mbit/s)

ElectricalSignal

Optical Signal Optical Signal

STS-1 OC-1 - 51.840

STS-3 OC-3 STM-1 155.520 (155)

STS-9 OC-9 STM-3 466.560

3 POS and CPOS Interface ConfigurationHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access


Issue 03 (2010-03-31)

SONET SDH Transmission Rate(Mbit/s)

ElectricalSignal

Optical Signal Optical Signal

STS-12 OC-12 STM-4 622.080 (622)

STS-18 OC-18 STM-6 933.120

STS-24 OC-24 STM-8 1244.160

STS-36 OC-36 STM-12 1866.240

STS-48 OC-48 STM-16 2488.320 (2.5 Gbit/s)

STS-96 OC-96 STM-32 4876.640

STS-192 OC-192 STM-64 9953.280 (10 Gbit/s)

STS-768 OC-768 STM-256 39813.120(40Gbit/s)

Channelization and Unchannelization

When SDH signals are formed by multiplexing low-speed tributary signals, these signals arecalled channels.

Channelization indicates that multiple independent channels of data are transmitted over anoptical fiber by using low-speed tributary STM-N signals. During the transmission, each channelhas its own bandwidth and start and end points, and follows its own monitoring policy.

Unchannelization indicates that all data is transmitted in a single channel over an optical fiberby using all STM-N signals. During the transmission, all the data has the same ID and start andend points, and follows the same monitoring policy.

Channelization can utilize bandwidth in transmitting multiple channels of low-speed signals.Unchannelization is adopted to transmit a single channel of high-speed signals.

POS and CPOS

The Packet over SONET/SDH (POS) technology is applied to MAN and WAN, supportingpacket data such as IP packets.

Making full use of the SDH system, Channelized POS (CPOS) interfaces have the followingfunctions:

l Perform refined division of bandwidth.

l Reduce the demand for the quantity of low-speed physical ports on a router in networking.

l Enhance the convergence capability of low-speed ports of a router.

l Improve the dedicated line access capability of a router.

Frame Structure of SDH



3-3

To facilitate understanding, the following section describes the frame structure of the SDHsignal, that is, the structure of the STM-N frame.

To add or drop low-speed tributary signals to or from high-speed signals, try to distributetributary signals in the frame equably and regularly. The ITU-T regulates that STM-N framesare rectangular and expressed in bytes, as shown in Figure 3-1.

Figure 3-1 STM-N frame structure

RegeneratorSection

OverheadAUPTR

MultiplexSection

Overhead

Payload

9*N 261*N

123456789

9*270*N(bytes)

STM-N is the frame with the dimension of 9 rows x 270 x N columns. Here, N is consistent withthat in STM-N, indicating how many STM-1 signals are multiplexed to this STM-N signal.

An STM-N frame consists of the following parts:

l Section Overhead (SOH): includes Regenerator Section Overhead (RSOH) and MultiplexSection Overhead (MSOH).

l Administration Unit Pointer (AU-PTR): is the pointer that specifies the first byte of thepayload. The receiving end can correctly extract the payload according to the location ofthe pointer.

l Payload

Termsl Multiplexing units: SDH contains basic multiplexing units, including container (C-n),

virtual container (VC-n), tributary unit (TU-n), tributary unit group (TUG-n),administrative unit (AU-n), and administrative unit group (AUG-n). Here, n stands for thenumber of the unit level.

l Container: It is used to carry service signals that are transmitted at different rates. G.709defines specifications for five types of standard containers: C-11, C-12, C-2, C-3, and C-4.



Issue 03 (2010-03-31)

l VC: It is used to support connections between channel layers of the SDH and is aninformation terminal of SDH channels. VCs are classified into lower-order VCs and higher-order VCs. VC-3 in AU-3 and VC-4 are higher-order VCs.

l TU and TUG: TU provides adaptation between lower-order and higher-order path layers.One TU or a set of multiple TUs, occupying a fixed position in the payload of the higher-order VC, is called a TUG.

l AU and AUG: AU provides adaptation between higher-order channel layer and multiplexsection layer. One AU and a set of multiple AUs, occupying a fixed position in the payloadof STM-N, is called an AUG.

Multiplexing E1/T1 to STM-1

In the process of SDH multiplexing recommended in G.709, there is more than one multiplexingpath from a valid payload to STM-N.

Figure 3-2 shows the multiplexing from E1/T1 to STM-1.

Figure 3-2 Process of multiplexing E1 to STM-1

MappingMultiplexingMapping

STM-1 AUG-1 AU-4 VC-4

VC-3AU-3

TUG-2 TU-12 VC-12

TUG-3

C-12

×1 ×1

×3

×3

×7

×7

×3

C-12:2.048Mb/s

Figure 3-3 Process of multiplexing T1 to STM-1

MappingMultiplexingMapping

STM-1 AUG-1 AU-4 VC-4

VC-3AU-3

TUG-2 TU-11 VC-11

TUG-3

C-11

×1 ×1

×3

×3

×7

×7

×4

C-11:1.544Mb/s



3-5

In application, different countries and regions may adopt different multiplexing paths. To ensuremutual communication, the NE80E/40E provides the multiplex mode command on the CPOSinterface so that you can select the AU-3 or AU-4 multiplexing path.

Calculation of E1/T1 Path Sequence Number

CPOS interfaces adopt the multiplexing mode of byte interleave, so the lower-order VCs in ahigher-order VC are not arranged in sequence. To facilitate user configuration, the followingtakes E1 in CPOS adopting AU-4 multiplexing path as an example to introduce the method ofcalculating the TU number.

The multiplexing process in Figure 3-2 shows that the 2 Mbit/s multiplexing structure is 3-7-3when the AU-4 multiplexing path is adopted. The following formula shows how to calculate thenumbers of TU-12s that are located in different positions in a VC-4:

VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12 number - 1) x 21

In a VC-4, all TUG-3s are numbered the same; all TUG-2s are numbered the same; the differencebetween two TU-12 numbers is 1. These two TU-12s are adjacent.

NOTE

l The numbers listed in the preceding formula stand for the positions in a VC-4 frame.

l The TUG-3 number ranges from 1 to 3; the TUG-2 number ranges from 1 to 7; the TU-12 numberranges from 1 to 3.

l The TU-12 number indicates which one of the 63 TU-12s is in the VC-4 frame according to the sequenceand also indicates the E1 channel number.

Figure 3-4 Sequence of arrangement of TUG-3, TUG-2 and TU-12 in VC-4

VC-4 TUG-3 TUG-2 TU-12

TU-12

TU-12

TU-12

TU-12

TU-12

TU-12

TU-12

TU-12

TUG-2

TUG-2

TUG-3

TUG-3

1

2

3

1

2

3

1

2

3

1

2

7

1

2

3



Issue 03 (2010-03-31)

When the AU-3 multiplexing path is adopted, the calculation of the TU-12 number can bededuced in a similar manner.

When 63 E1 channels or 84 T1 channels are configured on a CPOS interface, these channelscan be directly numbered from 1 to 63 or 1 to 84. If a router of Huawei is connected to achannelized STM-1 interface of a router from another vendor, note differences in channelnumbers.

Overhead Bytes

SDH provides monitoring and management in layers. Monitoring is classified into sectionmonitoring and path monitoring. Section monitoring is classified into regenerator sectionmonitoring and multiplex section monitoring. Path monitoring is classified into higher-orderpath monitoring and lower-order path monitoring. Different overhead bytes help to implementthe monitoring functions.

NOTE

This section describes only some SDH overhead bytes used in configuration. For details, refer to a bookabout the particular topic.

l SOH

SOH consists of RSOH and MSOH.

The payload of an STM-N frame contains the path overhead (POH) that monitors low-speed tributary signals.J0, the regeneration section trace byte is contained in RSOH. This byte is used to transmitthe Section Access Point Identifiers (SAPIs) repeatedly to check the connection betweenthe receiver and the transmitter. The byte can be any character in the networks of a carrier,whereas the J0 byte of the receiver and the transmitter must match each other at the borderof networks between two carriers. With the JO byte, a carrier can locate and rectify faultsin advance to speed up the network recovery.

l Path overhead

SOH monitors section layers, whereas POH monitors path layers. POH is classified intolower-order path overhead and higher-order path overhead.The higher-order path overhead monitors the paths at VC-4 and VC-3 levels.J1, the higher-order VC-N path trace byte, is contained in the higher-order path overhead.Similar to j0, J1 is used to transmit SAPIs repeatedly to check the connection between thereceiver and the transmitter. J1 bytes of the receiver and transmitter must match each other.C2, the path signal label byte, is contained in higher-order path overhead. C2 is used tospecify the multiplexing structure and the attributes of the information payload in a VCframe, including whether the path is loaded with services, service types, and the mappingmode. C2 bytes of the receiver and transmitter must match each other.

3.1.2 Features of POS and CPOS Interfaces on the NE80E/40E



3-7

POS

The POS can map packets of variable length directly into the payload of SONET. The POS usesthe physical layer transmission standard of SONET. This offers a high speed, reliable, and P2Pdata connection.

The NE80E/40E provides various rates of POS interfaces, which can be divided into three kindsbased on the rate: STM-1 (155Mbit/s), STM-4c (622Mbit/s), STM-16c (2.5Gbit/s), andSTM-64c (10Gbit/s).

The NE80E/40E provides various rates of POS interfaces, which can be divided into three kindsbased on the rate: STM-1 (155Mbit/s), STM-4c (622Mbit/s), STM-16c (2.5Gbit/s), STM-64c(10Gbit/s), and STM-256c(40Gbit/s).

CPOS

CPOS is mainly used to improve aggregation capacity of the router on low speed access. TheSTM-1 CPOS is suitable for aggregating multiple E1/T1s.

The physical port of the STM-1 CPOS interface is not used as a service port, it is called acontroller. E1/T1/E3/T3 channels are used as synchronous serial interfaces and configured inserial interface view. The indexing method of the interface number is four-dimension index,namely, slot number/card number/port number/channel number:channel number.

The STM-1 CPOS service board can provide the following channels:l 63 E1 channels (2.048M, DS-1)

l 84 T1 channels (1.544M, DS-1)

l 3 E3 channels (34.368M, DS-3)

l 3 T3 channels (44.736M, DS-3)

NOTE

The channelization type of STM-1 CPOS should take the specifications of the service board as thestandards.

The NE80E/40E only supports the channels on the same service board to be bound to be thebinding group, and the binding group is numbered from 1.

The link layer protocols of the channelized E1/T1/E3/T3 are as follows:

Table 3-2 Link layer conditions of the E1/T1/E3/T3 supported by the NE80E/40E

Channel Link Layer Protocol MP Binding

E1 PPP, HDLC Support.

T1 PPP, HDLC Support.

E3 PPP, HDLC Not support

T3 PPP, HDLC Not support

The working modes of the E1/T1/E3/T3 channels supported by the NE80E/40E are as follows:



Issue 03 (2010-03-31)

Table 3-3 Working modes of the E1/T1/E3/T3 channels supported by the NE80E/40E

Channel Unframed Framed

Unchannelized Channelized

E1 The serial interfacewith rate 2.048Mbit/s.

Not support The 31 timeslots except timeslot 0can be bound as the serial interfacesof Nx64Kbit/s

T1 The serial interfacewith rate 1.544Mbit/s

Not support The 24 timeslots can be bound asthe serial interfaces of Nx64Kbit/s

E3 The serial interfacewith rate 34.368Mbit/s

The rate is33.831Mbit/s

Not support

T3 The serial interfacewith rate 44.736Mbit/s

The rate is44.210Mbit/s

Not support

3.2 Configuring POS InterfacesDescribes how to configure a POS interface.


3.2.2 Configuring the Link Layer Protocol

3.2.3 Configuring Clock Mode

3.2.4 Configuring the Overhead Byte

3.2.5 Configuring Frame Format

3.2.6 Configuring the Scramble FunctionA POS interface supports the scrambling function for the payload data to avoid excessiveconsecutive 1s or 0s and facilitate line clock signal extraction for the receiver.

3.2.7 Configuring the Length of the CRC Check CharacterA POS interface supports two types of CRC check characters: 16 bits and 32 bits.

3.2.8 Configuring MTUThe Maximum Transmission Unit (MTU) of a POS interface is used for the assembly anddisassembly of the IP packets received and sent from the interface.




Before using a SONET/SDH optical interface to bear packet data, you need to configureparameters for the POS interface.



3-9

Pre-configuration TasksBefore configuring a POS interface, complete the following task:


Data PreparationTo configure a POS interface, you need the following data.

No. Data

1 Number of the POS interface on the router

2 Link layer protocol of the POS interface

3 Clock mode of the POS interface

4 Values of overload bytes C2, J0, and J1

5 Frame format of the POS interface

6 Length of the CRC check character

7 MTU of the POS interface

8 Alarm threshold of the POS interface

3.2.2 Configuring the Link Layer Protocol


Procedure



Step 2 Run:interface pos interface-number

The POS interface view is displayed.

Step 3 Run:link-protocol { ppp | hdlc | fr [ ietf | nonstandard ] }

The link layer protocol of the POS interface is configured.

NOTE

The POS interface supports only the basic functions of FR P2P sub-interfaces, excluding other FRfunctions.

----End



Issue 03 (2010-03-31)


ContextA POS interface supports the following clock modes:

l Master clock mode: uses internal clock signal.

l Slave clock mode: uses line clock signal.

Similar to a synchronous serial interface working in DTE and DCE modes, a POS also worksin different clock modes.

l When the POS interfaces of two routers are connected directly or through the WavelengthDivision Multiplexing (WDM) device, configure one interface to work in master clockmode and the other interface in slave clock mode to avoid link flapping.

l When the POS interface of a router, which functions as a DTE, is connected to a switchingdevice that functions as a DCE and uses internal clock signals, configure the POS interfaceto work in slave clock mode.


Procedure






Clock mode of the POS interface is configured.

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

----End


ContextThe SONET/SDH provides a variety of overhead bytes, which perform the monitoring functionof different levels.

The C2 (Path signal label byte) is included in higher order path overhead. C2 indicates themultiplex structure of VC frame and the property of information payload.

The J0 (Regeneration section Trace Message) is included in section overhead. It is used to testthe continuous connection of the two ports on the section level.

The J1 (Higher-Order VC-N path trace byte) is used to test the connectivity of two interfaces.



3-11


Procedure





Step 3 To configure the overhead bytes of the POS interface, perform the following as required:l To configure the regeneration section trace message J0, run:

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

l To configure the path trace byte J1, run:flag j1 { 64byte-or-null-mode j1-value | 16byte-mode j1-value | 1byte-mode j1-value | peer }

l To configure path signal label byte C2, run:flag j2 c2-value

The configuration of C2, J0 and J1 should be consistent. Otherwise an alarm is generated.

For the POS interface, the default value of C2 is 22 (0x16), the default value of J0 and J1 is"NetEngine".

----End


ContextA POS interface supports the following types of frame formats:

l SDH

l SONET

By default, the frame format of a POS interface is SDH.


Procedure







Issue 03 (2010-03-31)

Step 3 Run:frame-format { sdh | sonet }

Frame format of the POS interface is configured.

----End

3.2.6 Configuring the Scramble FunctionA POS interface supports the scrambling function for the payload data to avoid excessiveconsecutive 1s or 0s and facilitate line clock signal extraction for the receiver.

ContextThe scrambling function of the directly connected interfaces must be configured the same.

By default, the scrambling function is enabled on the payload.


Procedure





Step 3 Run:scramble

The scrambling function of the payload is configured for the POS interface.

----End

3.2.7 Configuring the Length of the CRC Check CharacterA POS interface supports two types of CRC check characters: 16 bits and 32 bits.

ContextBy default, 32-bit CRC is adopted.

Procedure






3-13


Step 3 Run:crc { 16 | 32}

The length of the CRC check character is configured for the POS interface.

NOTEThe 10G POS interfaces do not support this configuration.

----End

3.2.8 Configuring MTUThe Maximum Transmission Unit (MTU) of a POS interface is used for the assembly anddisassembly of the IP packets received and sent from the interface.

ContextA router reassembles and fragments the sent and received packets according to the MTU.

CAUTIONAfter changing the MTU of the interface by running the mtu command, restart the interface tovalidate the configuration by running the shutdown and undo shutdown commandsconsecutively.


Procedurel Configuring IPv4 MTU

1. Run:system-view


interface pos interface-number

The POS interface view is displayed.3. Run:

mtu mtu

The IPv4 MTU of the POS interface is configured.

The MTU is expressed in bytes, and its value ranges from 46 to 9600. By default, theMTU is 4470 bytes.

l Configuring IPv6 MTU1. Run:

system-view




Issue 03 (2010-03-31)

2. Run:interface pos interface-number

The POS interface view is displayed.3. Run:

ipv6 mtu mtu

The IPv6 MTU of the POS interface is configured.

The MTU is expressed in bytes, and its value range from 1280 to 9660. By default,the MTU is 4470 bytes.

CAUTIONAfter configuring the IPv6 MTU, run the ppp mru-negotiate ipv6 command to startnegotiation of the IPv6 MTU.

----End


Procedurel Run the display interface pos [ interface-number ] [ | { begin | exclude | include } regular-

expression ] command to check the configuration and status of the POS interface.l Run the display interface brief [ | { begin | include | exclude } regular-expression ]

command to check the brief information about the POS interface.l Run the display pos interface [ pos interface-number ] command to check the information

about the physical layer of the POS interface.

----End

ExampleRun the display interface pos command, you can view the information about the physical status,link protocol status and clock mode. For example:<HUAWEI> display interface pos 1/0/0Pos1/0/0 current state : UPLine protocol current state : UPDescription : Pos1/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 4470 bytes, Hold timer is 10(sec)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-HWTransceiver 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



3-15

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 you can view the brief information about the physical status, link protocol status, bandwidthutilization, and number of the error packets, it means that the configuration succeeds. Forexample:<HUAWEI> display interface brief | include Pos*down: administratively down^down: standby(l): loopback(s): spoofing(b): BFD down(d): DampeningSuppressedInUti/OutUti: input utility/output utilityInterface Physical Protocol InUti OutUti inErrors/ outErrorsPos4/0/0 down down 0% 0% 831745956 0 Pos5/0/0 up up 0.01% 0.01% 3795064053 0 Pos5/0/1 down down 0% 0% 343911292 0 Pos5/0/2 down down 0% 0% 343913408 0 Pos5/0/3 down down 0% 0% 343915353 0

Run the display pos interface command, you can view the detailed information about thephysical layer. For example:<HUAWEI> display pos interface pos 6/0/0Pos6/0/0 current state:DOWNLine protocol current state:DOWNPhysical 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 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 lostpacketsSFP 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: 5kmPIC Packet Statics Per Sencond:Rxd: 0x0 Packets 0x0 FCS 0x0 Receiv Abort Packets 0x0 Long Packets 0x0 Short Packets



Issue 03 (2010-03-31)

Txd: 0x0 Packets 0x0 Send Abort PacketsSDH 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.3 Configuring STM-1 CPOS InterfacesThis section describes how to configure a STM-1 CPOS interface.





3.3.5 Configuring AUG Multiplexing RouteIn the SDH, the payload has the following mapping and multiplexing solutions.




Before using a SONET/SDH optical interface to bear packet data and using low-speed ports foraccess, you need to configure parameters for the CPOS interface.


Before configuring a CPOS interface, complete the following task:


Data Preparation

To configure a CPOS interface, you need the following data.

No. Data

1 Number of the CPOS interface on the router

2 Overhead bytes C2, J0, and J1 of the CPOS interface



3-17


ContextA CPOS interface supports the following clock modes:

l Master clock mode: uses internal clock signal.

l Slave clock mode: uses line clock signal.

When a CPOS interface is connected to a SONET/SDH device, configure the CPOS interfaceto work in slave clock mode because the precision of the clock in the SONET/SDH network ishigher than the precision of the internal clock source of the CPOS interface.

When CPOS interfaces are connected directly through the optical fiber or a Wavelength DivisionMultiplexing (WDM) device, configure one interface to work in master clock mode and theother interface in slave clock mode.


Procedure



Step 2 Run:controller cpos cpos-number

The CPOS interface view is displayed.


Clock mode of the CPOS interface is configured.

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

----End



Procedure






Issue 03 (2010-03-31)



Frame format of the CPOS interface is configured.

The frame format determines whether a CPOS interface works in SONET mode or SDH mode.

By default, the frame type of a CPOS interface varies with the hardware:l For the CPOS interface that can be channelized into E1 or E3, the default frame type is SDH.

l For the CPOS interface that can be channelized into T1 or T3, the default frame type isSONET.

----End


ContextThe SONET/SDH provides a variety of overhead bytes, which perform the monitoring functionof different levels.

The C2 is used to indicate the multiplex structure of VC frame and the property of informationpayload.

The J0 is a section overhead byte which is used to detect the connectivity of two ports on thesection layer.

The J1 is higher order path overhead bytes and is used to detect the connectivity of two ports onthe path layer.


Procedure





Step 3 Perform the following as required.l To configure the regeneration section trace message J0, run:

flag j0 { sdh | sonet } j0For the regenerator section trace byte J0:– In the 1-byte mode (sonet), the default value of J0 is 1.

– In the 16-byte mode (sdh), the default value of J0 is "NetEngine".

l To configure the path trace byte J1, run:flag j1 j1



3-19

By default, the value of J1 is "NetEngine".l To configure path signal label byte C2, run:

flag c2 c2The C2 is mainly used for international interconnection and 0x02 is used in China. By default,c2 is 02 (in hexadecimal system).

The C2, J0, J1, on the receiving end and the sending end must be consistent; otherwise, an alarmis generated.

----End

3.3.5 Configuring AUG Multiplexing RouteIn the SDH, the payload has the following mapping and multiplexing solutions.

Contextl In the ANSI multiplexing, the lower-order payload is aggregated into the VC-3 higher-

order path. An AU-3 consists of a VC-3 and an AU pointer. Three AU-3s are multiplexedinto an AUG.

l In the ETSI multiplexing, the lower-order payload is aggregated into the VC-4 higher-orderpath. An AU-4 consists of a VC-4 and an AU pointer. An AU-4 is multiplexed into anAUG.

By default, an AU-4 is multiplexed into an AUG.


Procedure





Step 3 Run:frame-format sdh

Frame format of the CPOS interface is configured as SDH.

You can configure AUG to multiplex to AU-4 or AU-3 using the multiplex mode commandonly when the CPOS interface is applied in SDH mode.

Step 4 Run:multiplex mode { au-4 | au-3 }

The AUG multiplexing path of the CPOS interface is configured.

This command is supported on 1-port STM-1 CPOS flexible cards only and not supported onother types of STM-1 CPOS interface boards.

----End



Issue 03 (2010-03-31)


ProcedureStep 1 Run the display controller cpos [ cpos-number ] command to check information about all

channels of the CPOS interface.

----End

ExampleYou can view information about the clock, frame format, and multiplexing path by checkinginformation about the STM-1 CPOS interface.<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.4 Configuring E1 Channels of the CPOS InterfaceDescribes how to configure E1 channels of CPOS interfaces.


3.4.2 Creating Synchronous Serial Interface of E1 Channel





Applicable EnvironmentBefore using the low-speed interface channelized from the CPOS interface for access, you needto configure parameters for the E1 channel.

Pre-configuration TasksBefore configuring the E1 channel on a CPOS interface, complete the following tasks:



3-21


l Connecting the CPOS interface and configuring physical attributes for the CPOS interface

Data PreparationTo configure the E1 channel of a CPOS interface, you need the following data.

No. Data


2 Number of the E1 channel

3 Number of the CE1 channel whose timeslots are bound into the channel-set, andnumber and range of timeslots

3.4.2 Creating Synchronous Serial Interface of E1 Channel

ContextNOTE

One channel cannot work in both the clear channel mode and the channelized mode simultaneously. Toswitch the working mode between these two modes, cancel the current serial interface and re-create a newone.


Procedure





Step 3 To create the synchronous serial interface of the E1 channel, do as follows:l To create the E1 channel in clear channel mode, run:

e1 e1-number unframed

l To create the E1 channel in channelized mode, run:e1 e1-number channel-set set-number timeslot-list { ts0 | slot-list [ ts0 ] }

In channelized mode, timeslot 0 alone can be bound to form a serial interface; timeslots 0 to31 can also be randomly bound to form one or multiple serial interfaces. In this case, timeslot0 needs to be specified in the command as the parameter ts0.Timeslot 0 is used to transmit frame synchronization and alarm information. After timeslot0 is bound to form a serial interface, frame synchronization and alarm information can betransparently transmitted between the client and the server through the serial interface.



Issue 03 (2010-03-31)

The channel-set after the timeslot binding of the E1 channel forms a serial interface. You canconfigure this serial interface. The bound serial interface is numbered: slot/card/interface/channel number: channel-set number.

----End


ContextAn E1 channel supports the frame format with 4-bit CRC.

By default, the frame format of an E1 channel is no-CRC4.


Procedure





Step 3 Run:e1 e1-number set frame-format { crc4 | no-crc4 }

The frame format of the E1 channel is configured.

----End


ContextYou can configure the clock mode for each E1 channel separately. The clock mode of an E1channel depends on the device connecting the E1 channel. For example:

l If the E1 interface is connected to a SONET or SDH device, configure the E1 interface towork in slave clock mode.

l If two routers are connected directly through the optical fiber, configure one end to workin master clock mode and the other end in slave clock mode.

By default, an E1 interface works in master clock mode.


Procedure




3-23




Step 3 Run:e1 e1-number set clock { master | slave }

The clock mode of the E1 channel is configured.

----End


Procedurel Run the display interface serial slot/card/port/channel-number:set-number command to

check the information about the serial interface bound by E1 channels.l Run the display controller cpos [ cpos-number ]command to check the information about

the status and statistics of the CPOS interface.

----End

ExampleYou can view the status, link layer protocol and statistics of the serial interface channelized bythe E1 channel of a CPOS interface.

<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, you can view the information about the status andclock mode of CPOS interface. For example:<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: 2km



Issue 03 (2010-03-31)

Physical 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.5 Configuring T1 Channels of the CPOS InterfaceThis section describes how to configure T1 channels of CPOS interfaces.


3.5.2 Creating Synchronous Serial Interface of T1 Channel





Applicable EnvironmentBefore using the low-speed port channelized from the CPOS interface for access, you need toconfigure parameters the T1 channel.

Pre-configuration TasksBefore configuring the T1 channel of the CPOS interface, complete the following tasks:


l Connecting the CPOS interface and configuring physical attributes for the CPOS interface

Data PreparationTo configure T1 channels of the CPOS interface, you need the following data.

No. Data


2 Number of the T1 channel

3 Number of the CT1 channel whose timeslots are bound as the channel-set, timeslotnumber, or timeslot range



3-25

3.5.2 Creating Synchronous Serial Interface of T1 Channel

ContextNOTE

One channel cannot work in both the clear channel mode and the channelized mode simultaneously. Toswitch the working mode between these two modes, cancel the current serial interface and re-create a newone.


Procedure





Step 3 To create the synchronous serial interface of the T1 channel, do as follows:l To create the T1 channel in clear channel mode, run:

t1 t1-number unframed

l To create the T1 channel in channelized mode, run:t1 t1-number channel-set set-number timeslot-list slot-list

In the channelized mode, one or more timeslots from 0 to 23 can be bound as one or moreserial ports to be used.The channel-set after the timeslot binding of the T1 channel forms a serial interface. You canconfigure this serial interface. The bound serial interface is numbered: slot/card/interface/channel number: channel-set number.For the T1 channels, the default rate of the channel-set is N x 64kbit/s (N is the number ofthe bound timeslots).

----End


ContextA T1 channel supports two types of frame formats: super frame (SF) and extended super frame(ESF).


Procedure




Issue 03 (2010-03-31)




Step 3 Run:t1 t1-number set frame-format { esf | sf }

The frame format of the T1 channel is configured.

By default, the frame format of a T1 channel is ESF.

----End


Context

You can configure the clock mode for each T1 channel separately. The clock mode of a T1channel depends on the device connecting the T1 channel. For example, if an interface isconnected to a SONET or SDH device, you should configure the interface to work in slave clockmode. If two routers are connected directly through the optical fiber, configure one end to workin master clock mode and the other end in slave clock mode.

By default, a T1 channel works in master clock mode.


Procedure






The clock mode of the T1 channel is configured.

----End


Procedurel Run the display interface serial slot/card/port/channel-number:set-number command to

check the information about the serial interface bound by T1 channels.



3-27

l Run the display controller cpos [ cpos-number ] command to check the information aboutthe status and statistics of the CPOS interface.

----End

ExampleYou can view the status, link layer protocol and statistics of the serial interface channelized bythe T1 channel of a CPOS interface.

<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 Configuring E3 Channels of an STM-1 CPOS InterfaceThis section describes how to configure the E3 channels of the STM-1 CPOS interfaces.


3.6.2 Creating Synchronous Serial Interface of E3 Channels




Applicable EnvironmentWhen the accessing is performed through the low speed port channelized by the CPOS interface,you need to configure the E3 channels.

Pre-configuration TasksBefore configuring E3 channels on a CPOS interface, complete the following tasks:




Issue 03 (2010-03-31)

l Connecting the CPOS interface and configuring the physical attributes of the CPOSinterface

Data PreparationTo configure E3 channels of a CPOS interface, you need the following data.

No. Data

1 Number of CPOS interface of the router

2 Number of the E3 channel

3.6.2 Creating Synchronous Serial Interface of E3 Channels

ContextE3 channels work in either of the following modes:l Clear channel mode (also known as unframed mode)

When an E3 channel works in clear channel mode, data is transmitted in the form of bitflows in the E3 channel. The E3 channel without timeslot division functions as asynchronous serial interface named serial slot/card/port/0:0.

l Unchannelized modeWhen an E3 channel works in unchannelized mode, data is transmitted in the form of framesin the E3 channel. All timeslots of the E3 channel are bound to function as a synchronousserial interface named serial slot/card/port/0:0.


Procedure





Step 3 To create the synchronous serial interface, perform the following as required:l To create the serial interface of the unchannelized mode, run the e3 e3-number framed

command.l To create the serial interface of the clear channel mode, run the e3 e3-number unframed

command.

After the creation is successful, the number of the formed synchronous serial interface is: slot/card/port/0:0.

----End



3-29


ContextYou can configure the clock mode for each E3 channel separately. The clock mode of an E3channel depends on the device connecting the E3 channel. For example, if the E3 channel isconnected to a SONET or SDH device, configure the E3 channel to work in slave clock mode.

If two routers are connected directly through the optical fiber, configure one end to work inmaster clock mode and the other end in slave clock mode.

By default, an E3 channel works in master clock mode.

NOTE

This configuration is supported only by the 2 x 155 M CPOS FPIC.


Procedure





Step 3 Run:e3 e3-number set clock { master | slave }

The clock mode of the E3 channel is configured.

----End


Procedurel Run the display controller cpos cpos-number command to check the configuration and

status of the CPOS interface.l Run the display interface serial slot/card/port/channel-number:set-number command to

checks the information about the serial interface bound by E3 channels.

----End

ExampleYou can view information about the clock, frame format, and multiplexing path by checkinginformation about the STM-1 CPOS interface.<HUAWEI> display controller cpos 1/0/0Cpos1/0/0 current state : Administratively DOWN Description : Cpos1/0/0 Interface The Vendor Name is AGILENT



Issue 03 (2010-03-31)

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

You can view information about the status and clock information by checking information aboutthe serial interface.<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.7 Configuring T3 Channels of an STM-1 CPOS InterfaceThis section describes how to configure T3 channels of an STM-1 CPOS interfaces.


3.7.2 Creating T3 Channels





Applicable EnvironmentWhen the accessing is performed through the low speed port channelized by the CPOS interface,you need to configure the T3 channels.



3-31


Before configuring T3 channels on a CPOS interface, complete the following tasks:


l Connecting the CPOS interface and configuring the physical attributes of the CPOSinterface

Data Preparation

To configure T3 channels of a CPOS interface, you need the following data.

No. Data

1 Number of CPOS interface of the router

2 Number of the T3 channel

3.7.2 Creating T3 Channels

Context

T3 channels work in either of the following modes:

l Clear channel mode (also known as unframed mode)When a T3 channel works in clear channel mode, data is transmitted in the form of bit flowsin the T3 channel. The T3 channel without timeslot division functions as a synchronousserial interface named serial slot/card/port/channel-number:0.

l Unchannelized modeWhen a T3 channel works in unchannelized mode, data is transmitted in the form of framesin the T3 channel. All timeslots of the T3 channel are bound to function as a synchronousserial interface named serial slot/card/port/channel-number:0.


Procedure





Step 3 To create the synchronous serial interface, perform the following as required:l To create the serial interface of the unchannelized mode, run the t3 t3-number framed

command.



Issue 03 (2010-03-31)

l To create the serial interface of the clear channel mode, run the t3 t3-number unframedcommand.

After the creation is successful, the number of the formed synchronous serial interface is: slot/card/port/channel-number:0.

----End


ContextT1 corresponds to the digital signal level DS-1. 28 T1s form a T3 through the bit multiplexing.There are two kinds of frame format:

l C-bit: is also called C-bit parity check. In this frame format, the padding field can be usedin maintenance.

l M23: it is a multiplexing process from DS-2 to DS-3. Four T1s (DS-1) multiplex to a DS-2line through M12; seven DS-2 lines multiplex to a T3 (DS-3).

By default, C-bit is used.

NOTE



Procedure





Step 3 Run:t3 t3-number set frame-format { c-bit | m23 }

The frame format of the T3 channel is configured.

It is recommended that the frame formats of the T3 channel and the CPOS interface be the same.

----End


ContextYou can configure the clock mode for each T3 channel separately. The clock mode of an T3channel depends on the device connecting the T3 channel. For example, if the T3 channel isconnected to a SONET or SDH device, configure the T3 channel to work in slave clock mode.



3-33

If two routers are connected directly through the optical fiber, configure one end to work inmaster clock mode and the other end in slave clock mode.

By default, an T3 channel works in master clock mode.

NOTE



Procedure






The clock mode of the T3 channel is configured.

----End


Procedurel Run the display controller cpos [ cpos-number ] command to check the status and statistics

of the CPOS interface.l Run the display interface serial slot/card/port/channel-number:set-number command to

checks the information about the serial interface bound by T3 channels.

----End

ExampleYou can view information about the clock, frame format, and multiplexing path by checkinginformation about the STM-1 CPOS interface.<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



Issue 03 (2010-03-31)

error: B2 511275881 REI 1175934524 path layer: alarm: PPLM error: B3 2711 REI 1451

You can view information about the status and clock information by checking information aboutthe serial interface.<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 : disabledLink 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.8 Maintaining POS and CPOS Interface ConfigurationThis section describes how to maintain POS interfaces and CPOS interfaces.

3.8.1 Configuring the Self-loop to Detect Whether the Interface Is Normal


3.8.1 Configuring the Self-loop to Detect Whether the Interface IsNormal

Context

CAUTIONAfter you configure the self-loop or run the loopback command, the interface on a router or thelink may not run normally. Thus, you must check whether to set the self-loop. After the detectionis complete, run the undo loopback command to disable the self-loop.

Procedure




3-35


Step 2 Choose one of the following commands according to the interface type to enter the interfaceview.l In the case of a POS interface, run:

interface pos interface-numberl In the case of a STM-1 CPOS interface or E1/T1/E3/T3 channel of STM-1 CPOS interface,

run:controller cpos interface-number

Step 3 Choose one of the following commands according to the interface type to enable the self-loop.l In the case of a POS interface, STM-1 CPOS interface or STM-16 CPOS interface, run:

loopback { local | remote }l In the case of an E1 channel of STM-1 CPOS interface, run:

e1 e1-number set loopback { local | remote }l In the case of an T1 channel of STM-1 CPOS interface, run:

t1 t1-number set loopback { local | remote }l In the case of an E3 channel of STM-1 CPOS interface, run:

e3 e3-number set loopback { local | remote }l In the case of an T3 channel of STM-1 CPOS interface, run:

t3 t3-number set loopback { local | remote }

By default, the self-loop is disabled.

When configuring the loopback of the interface, note the following points:l For the POS interface, the configurations of the loopback differ with different service boards.

The following cases may occur in the actual configurations:– To enable the local loopback of the interface, the interface must be in the master clock


mode.Take the prompt information as the standards.

l For the STM-1 CPOS interface or E1/T1/E3/T3 channel of STM-1 CPOS interface– To enable the local loopback of the interface, the interface must be in the master clock


mode.

----End


Context

CAUTIONThe interface statistics cannot be restored after you run the reset command to clear it. So, confirmthe action before you use the command.



Issue 03 (2010-03-31)

To reset the interface statistics of the Network Management System (NMS) or those displayedby running the display interface command, run the following commands in the user view. Clearthe interface statistics before collecting the traffic.

NOTE

For the interface statistics in the NMS, refer to related NMS manuals.


the interface statistics displayed by running the display interface command.l Run the reset counters if-mib interface [ interface-type [ interface-number ] ] command

to clear the interface statistics in the NMS.

----End

3.9 Configuration ExamplesThis section provides several configuration examples of POS and CPOS interfaces.

3.9.1 Example for Directly Connecting Devices Through POS Interfaces

3.9.2 Example for Connecting Devices with POS Interfaces Through FR Network

3.9.3 Example for Configuring an STM-1 CPOS Interface

3.9.1 Example for Directly Connecting Devices Through POSInterfaces

Networking RequirementsAs shown in Figure 3-5, POS interfaces on Router A and Router B are directly connected witha pair of single-mode fibers for receiving and sending packets; PPP is the link layer protocol. Itis required that Router A and Router B can communicate.

Figure 3-5 Networking diagram of connecting devices directly through POS interfaces

POS1/0/010.1.1.1/30

POS1/0/010.1.1.2/30

RouterA RouterB


1. Configure PPP as the link layer protocol.



3-37

2. Configure IP addresses.

Data PreparationTo complete the configuration, you need the following data:

l IP address of POS 1/0/0 on Router A

l IP address of POS 1/0/0 on Router B

Procedure


# Configure POS 1/0/0, and set default values for all physical parameters.

<HUAWEI> system-view[HUAWEI] sysname A[RouterA] interface pos 1/0/0[RouterA-Pos1/0/0] ip address 10.1.1.1 30[RouterA-Pos1/0/0] undo shutdown[RouterA-Pos1/0/0] quit


# Configure POS 1/0/0, set the clock mode to slave, and set default values for other physicalparameters.

<HUAWEI> system-view[HUAWEI] sysname B[RouterB] interface pos 1/0/0[RouterB-Pos1/0/0] clock slave[RouterB-Pos1/0/0] ip address 10.1.1.2 30[RouterB-pos1/0/0] undo shutdown[RouterB-Pos1/0/0] quit

Step 3 Verify the configuration.

Run the display interface pos command to check the connectivity of the POS interface on RouterA.<RouterA> display interface pos 1/0/0Pos1/0/0 current state : UPLine protocol current state : UPLast line protocol up time : 2009-01-20 11:35:15Description: Pos1/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec)Internet Address is 10.1.1.1/30Link layer protocol is PPPLCP opened, IPCP openedThe Vendor Name is FINISAR CORP. , The Vendor PN is FTLF1321P1BTL-HWTransceiver BW: 2.5G, Transceiver Mode: Single ModeWaveLength: 1310nm, Transmission Distance: 2kmRx Optical Power: -40.00dBm, Tx Optical Power: -40.00dBmPhysical 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 SDH error: section layer: B1 0 line layer: B2 0 REI 0 path layer: B3 0 REI 0



Issue 03 (2010-03-31)

Statistics last cleared:2009-01-20 15:55:04 Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 24 bits/sec, 0 packets/sec Input: 604 packets, 9640 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 604 packets, 9688 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

Run the ping command to check the network connectivity.

[RouterA] ping 10.1.1.2 PING 10.1.1.2: 56 data bytes, press CTRL_C to break Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=255 time=3 ms Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=255 time=2 ms Reply from 10.1.1.2: bytes=56 Sequence=3 ttl=255 time=2 ms Reply from 10.1.1.2: bytes=56 Sequence=4 ttl=255 time=2 ms Reply from 10.1.1.2: bytes=56 Sequence=5 ttl=255 time=2 ms --- 10.1.1.2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet lossround-trip min/avg/max = 2/2/3 ms

----End


# sysname RouterA#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 10.1.1.1 255.255.255.252#return

l Configuration file of Router B# sysname RouterB#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 10.1.1.2 255.255.255.252 clock slave#return

3.9.2 Example for Connecting Devices with POS Interfaces ThroughFR Network

Networking Requirements

As shown in Figure 3-6, routers are interconnected through POS interfaces on the FRnetwork,and routers work in DTE mode as user devices.

Router A connects Router B and Router C, which reside on different network segments fromRouter A, through sub-interfaces.



3-39

Figure 3-6 Networking diagram of connecting routers using the POS interface through FRnetwork

FrameRelay

networkRouter A

Router B

Router C

POS1/0/0.1DLCI=21

10.1.1.1/30

POS1/0/0.2DLCI=22

10.2.1.1/30

POS1/0/0.1DLCI=21

10.1.1.2/30

POS1/0/0.2DLCI=22

10.2.1.2/30


1. Configure FR as the link protocol.2. Configure the working mode for interfaces.3. Configure IP addresses for interfaces.4. Configure the address mapping.


l IP address and DLCI of POS 1/0/0.1 on Router A


l IP address and DLCI of POS 1/0/0.1 on Router B

l IP address and DLCI of POS 1/0/0.2 on Router C

Procedure

Step 1 Configure Router A.<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] interface pos 1/0/0

# Encapsulate the FR protocol.

[RouterA-Pos1/0/0] link-protocol fr[RouterA-Pos1/0/0] fr interface-type dte[RouterA-Pos1/0/0] undo shutdown[RouterA-Pos1/0/0] quit

# Configure POS 1/0/0.1.

[RouterA] interface pos 1/0/0.1[RouterA-Pos1/0/0.1] shutdown



Issue 03 (2010-03-31)

[RouterA-Pos1/0/0.1] fr dlci 21[RouterA-fr-dlci-Pos1/0/0.1-21] quit[RouterA-Pos1/0/0.1] ip address 10.1.1.1 30[RouterA-Pos1/0/0.1] undo shutdown[RouterA-Pos1/0/0.1] quit


[RouterA] interface pos 1/0/0.2[RouterA-Pos1/0/0.2] shutdown[RouterA-Pos1/0/0.2] fr dlci 22[RouterA-fr-dlci-Pos1/0/0.2-22] quit[RouterA-Pos1/0/0.2] ip address 10.2.1.1 30[RouterA-Pos1/0/0.2] undo shutdown[RouterA-Pos1/0/0.2] quit

Step 2 Configure Router B and Router C.

The method of configuring Router B and Router C is the same as the method of configuringRouter A. The configuration details are not mentioned here.


Run the display interface pos command on each router. You can find that the connectivity ofPOS interfaces is Up.

Run the ping command on each router. Each router can ping through the network.

----End


# sysname RouterA#interface Pos1/0/0 link-protocol fr undo shutdown#interface Pos1/0/0.1 fr dlci 21 ip address 10.1.1.1 255.255.255.252#interface Pos1/0/0.2 fr dlci 22 ip address 10.2.1.1 255.255.255.252#return

l Configuration file of Router B#sysname RouterB#interface Pos1/0/0 link-protocol fr undo shutdown#interface Pos1/0/0.1 fr dlci 21 ip address 10.1.1.2 255.255.255.252#return

l Configuration file of Router C#sysname RouterC



3-41

#interface Pos1/0/0 link-protocol fr undo shutdown#interface Pos1/0/0.2 fr dlci 22 ip address 10.2.1.2 255.255.255.252#return

3.9.3 Example for Configuring an STM-1 CPOS Interface


As shown in Figure 3-7, certain mid-range-and-low-end devices access the transmissionnetwork through E1/T1 leased cable. All the bandwidths converge to the CPOS interface 3/0/1on Router A through transmission network. Each mid-range-and-low-end device is defined byits unique timeslot.

There cannot be only one transmission network between the channelized POS interface and themid-range-and-low-end deivce. Other transmission methods can also be adopted.

NOTE

The configurations of the T1 channel and the E1 channel are consistent. Take the E1 channel as an example.

Figure 3-7 Networking diagram of an STM-1 CPOS interface

STM-4/16ADM

ADM

ADM

ADM

Router ACPOS 3/0/1

OC-3/STM-1

E1/T1

E1/T1

nx E1/T1

Internet

..

..

Configuration Roadmap

The configuration roadmap is as follows:

1. Create the channel.

2. Create the bound group.

3. Configure the channel to join the bound group.



Issue 03 (2010-03-31)


l Channel number and slot number of each E1 channel

l Number of the bound group on each interface

NOTE

l The slot number and card number of the added Mp-group interface and the Mp-group interface mustbe consistent. That is, trans-board binding is not supported.


Procedure

Step 1 Configure RouterA

# Create a channel on the CPOS interface.

<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] controller cpos 3/0/1[RouterA-Cpos3/0/1] e1 1 channel-set 1 timeslot-list 1-10[RouterA-Cpos3/0/1] e1 2 channel-set 2 timeslot-list 11-15[RouterA-Cpos3/0/1] e1 3 channel-set 3 timeslot-list 16-20[RouterA-Cpos3/0/1] e1 4 channel-set 4 timeslot-list 21-30[RouterA-Cpos3/0/1] undo shutdown[RouterA-Cpos3/0/1] quit

# Configure a bundle group and the terminal authenticator.

[RouterA] interface Mp-group 3/0/1[RouterA-Mp-group3/0/1] discriminator[RouterA-Mp-group3/0/1] shutdown[RouterA-Mp-group3/0/1] quit

# Bind the channel to the bundle group.

[RouterA] interface Serial 3/0/1/1:1[RouterA-Serial3/0/1/1:1] shutdown[RouterA-Serial3/0/1/1:1] ppp mp Mp-group 3/0/1[RouterA-Serial3/0/1/1:1] quit[RouterA] interface Serial 3/0/1/2:2[RouterA-Serial3/0/1/2:2] shutdown[RouterA-Serial3/0/1/2:2] ppp mp Mp-group 3/0/1[RouterA-Serial3/0/1/2:2] quit[RouterA] interface Serial 3/0/1/3:3[RouterA-Serial3/0/1/3:3] shutdown[RouterA-Serial3/0/1/3:3] ppp mp Mp-group 3/0/1[RouterA-Serial3/0/1/3:3] quit[RouterA] interface Serial 3/0/1/4:4[RouterA-Serial3/0/1/4:4] shutdown[RouterA-Serial3/0/1/4:4] ppp mp Mp-group 3/0/1[RouterA-Serial3/0/1/4:4] quit

# Restart the channel and MP-group.

[RouterA] interface Mp-group 3/0/1[RouterA-Mp-group3/0/1] undo shutdown[RouterA-Mp-group3/0/1] quit[RouterA] interface Serial 3/0/1/1:1[RouterA-Serial3/0/1/1:1] undo shutdown[RouterA-Serial3/0/1/1:1] quit[RouterA] interface Serial 3/0/1/2:2[RouterA-Serial3/0/1/2:2] undo shutdown[RouterA-Serial3/0/1/2:2] quit



3-43

[RouterA] interface Serial 3/0/1/3:3[RouterA-Serial3/0/1/3:3] undo shutdown[RouterA-Serial3/0/1/3:3] quit[RouterA] interface Serial 3/0/1/4:4[RouterA-Serial3/0/1/4:4] undo shutdown[RouterA-Serial3/0/1/4:4] quit

----End

Configuration FilesConfiguration file of Router A

# sysname RouterA#controller Cpos3/0/1 undo shutdown e1 1 channel-set 1 timeslot-list 1-10 e1 2 channel-set 2 timeslot-list 11-15 e1 3 channel-set 3 timeslot-list 16-20 e1 4 channel-set 4 timeslot-list 21-30#interface Serial3/0/1/1:1 undo shutdown link-protocol ppp ppp mp Mp-group 3/0/1#interface Serial3/0/1/2:2 undo shutdown link-protocol ppp ppp mp Mp-group 3/0/1#interface Serial3/0/1/3:3 undo shutdown link-protocol ppp ppp mp Mp-group 3/0/1#interface Serial3/0/1/4:4 undo shutdown link-protocol ppp ppp mp Mp-group 3/0/1#interface Mp-group3/0/1 undo shutdown#return



Issue 03 (2010-03-31)

4 PPP and MP Configuration

About This Chapter

This chapter describes the basic concepts, configuration procedures, configuration examples,and troubleshooting of Point-to-Point Protocol (PPP) and MultiLink PPP (MP).

4.1 Introduction to PPP and MPThis section describes the basic concepts and principle of PPP and MP.

4.2 Encapsulating an Interface with PPP and MRU NegotiationThis section describes how to encapsulate an interface with PPP and configure the PPP MRUnegotiation.

4.3 Configuring Unidirectional PAPThis section describes how to configure PAP authentication.

4.4 Configuring Unidirectional CHAPThis section describes how to configure CHAP authentication.

4.5 Configuring PPP Optional ParametersThis section describes how to configure optional parameters of PPP.

4.6 Configuring MP Binding Using an MP-GroupThis section describes how to configure MP binding by using an MP-group.

4.7 Configuring MP Limiting ParametersThis section describes how to configure MP parameters.

4.8 Configuring MP FragmentationDescribes how to configure the length of the MP fragment on the MP-Group interface.

4.9 Maintaining PPP and MP ConfigurationDescribes how to maintain PPP and MP.

4.10 Configuration ExamplesProvides several configuration examples of PPP and MP.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access 4 PPP and MP Configuration


4-1

4.1 Introduction to PPP and MPThis section describes the basic concepts and principle of PPP and MP.

4.1.1 PPP and MP Overview

4.1.2 Features of PPP and MP on the NE80E/40E

4.1.1 PPP and MP OverviewA point-to-point (P2P) connection is a simple WAN connection. Link layer protocols of a PPPlink are as follows:

l Point-to-Point Protocol (PPP): supports synchronous and asynchronous transmission.

l High-level Data Link Control protocol (HDLC): supports only synchronous transmission.

Located at the data link layer of the Open Systems Interconnection (OSI), PPP supportssynchronous or asynchronous full-duplex links to transmit data from point to point. PPP is widelyused because:l It provides user authentication.

l It supports synchronous and asynchronous communications.

l It can be easily expanded.

PPP defines a set of protocols, including:

l Link Control Protocol (LCP): is used to establish, monitor, and terminate data links.

l Network Control Protocol (NCP): is used to establish and configure different network-layerprotocols, and negotiate the format and type of packets transmitted over data links.

l Authentication protocols: include Password Authentication Protocol (PAP) and Challenge-Handshake Authentication Protocol (CHAP), which are used for network securityauthentication.

The Multilink PPP (MP) technology binds multiple PPP links into a logical channel to increasebandwidth. MP can be applied to the low-speed interfaces supporting PPP, such as serialinterfaces.

4.1.2 Features of PPP and MP on the NE80E/40E

The NE80E/40E supports the configuration of PPP on the serial interface or POS interface toimplement the following functions:

l Supporting the Maximum Receive Unit (MRU) negotiation

l Performing the PAP or CHAP authentication

l Compressing the IP, UDP or RTP packet header

The MP is supported to be configured in the MP-group type on the NE80E/40E.

On the NE80E/40E, the interfaces supporting the MP binding are as follows:l Synchronous serial interface formed by E1/T1 channelized by the STM-1 CPOS.

l Synchronous serial interface formed by T1 channelized by the T3.

4 PPP and MP ConfigurationHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access


Issue 03 (2010-03-31)

l Synchronous serial interface formed by CE1 and CT1.

The NE80E/40E does not support the trans-board or trans-card MP binding.

When you configure MP in the MP-group mode, you can directly add the serial interface to theMP-group.

4.2 Encapsulating an Interface with PPP and MRUNegotiation

This section describes how to encapsulate an interface with PPP and configure the PPP MRUnegotiation.


4.2.2 Encapsulating the Interface with PPP

4.2.3 Enabling PPP MRU Negotiation




As a link layer protocol that bears network-layer packets over P2P links, PPP supports the MRUnegotiation. If a link is configured with the MTU value, apply the MRU negotiation to make theMTU values on both ends of the PPP link consistent so that data can be transmitted.


Before configuring PPP, complete the following task:

Connecting the interface and configuring physical parameters for the interface to ensure that thephysical layer status of the interface is Up.

Data Preparation

To configure PPP or PPP MRU negotiation, you need the following data.

No. Data

1 Number of the interface

4.2.2 Encapsulating the Interface with PPP

Context




4-3

Procedure



Step 2 Run:interface interface-type interface-number

The interface view is displayed.

Step 3 Run:link-protocol ppp

The link layer protocol is configured as PPP.

By default, the link layer protocol of serial interfaces and POS interfaces is PPP.

----End

4.2.3 Enabling PPP MRU Negotiation

ContextIf an interface is configured with the IPv6 MTU, enable the PPP IPv6 MRU negotiation so thatthe link control layer can perform the IPv6 MRU negotiation.

MRU refers to the capability of an interface to receive packets.

The initial negotiation value of MRU is the MTU set by users or the default MTU on an interface.

After the negotiation, the MTU on an interface is the smaller value between the MTUs on bothends, whereas the MRUs on both ends remain unchanged. Thus, the MTU on an interface is notgreater than the MRU on the interface. This ensures that communicating devices can receivepackets from each other.


Procedure





Step 3 Run:ppp mru-negotiate { ipv4 | ipv6 }

The MRU negotiation is enabled on the link control layer.

By default, the link control layer performs the IPv4 MRU negotiation.

----End



Issue 03 (2010-03-31)


PrerequisiteThe configurations of the encapsulating an interface with PPP and MRU negotiation arecomplete.

Procedurel Run the display interface [ interface-type [ interface-number ] ] [ | { begin | exclude |

include } regular-expression ] command to check the PPP configuration and the negotiatedMTU value of the interface.

----End

ExampleRun the display interface command. If the PPP configuration of the interface is displayed, itmeans 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-01-20 11:35:15Description: Pos1/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec)Internet Address is 10.1.1.1/30Link layer protocol is PPPLCP opened, IPCP openedThe Vendor Name is FINISAR CORP. , The Vendor PN is FTLF1321P1BTL-HWTransceiver BW: 2.5G, Transceiver Mode: Single ModeWaveLength: 1310nm, Transmission Distance: 2kmRx Optical Power: -40.00dBm, Tx Optical Power: -40.00dBmPhysical 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 SDH error: section layer: B1 0 line layer: B2 0 REI 0 path layer: B3 0 REI 0Statistics last cleared:2009-01-20 15:55:04 Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 24 bits/sec, 0 packets/sec Input: 604 packets, 9640 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 604 packets, 9688 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

4.3 Configuring Unidirectional PAPThis section describes how to configure PAP authentication.


4.3.2 Configuring a Local Router to Authenticate Its Peer in PAP Mode



4-5

4.3.3 Configuring the Peer to Be Authenticated by the Local Router in PAP Mode



Applicable EnvironmentIn PAP authentication, passwords are sent over the link in plain text. The username and passwordof the authenticated can be added to the user list of the authenticator in Authentication,Authorization, and Accounting (AAA) mode or through the Remote Authentication Dial in UserService (RADIUS) server.

PAP authentication is classified into the following types:

l Unidirectional authentication: One of two communication parties functions as theauthenticator, while the other as the authenticated.

l Bidirectional authentication: Two communication parties function as both the authenticatorand the authenticated.

This section describes how to configure unidirectional PAP authentication.

Pre-configuration TasksBefore configuring PAP authentication, complete the following tasks:

l Connecting interfaces and configuring physical attributes for these interfaces to ensure thatthe physical layer of the interfaces is Up

l Configuring PPP as the link layer protocol of interfaces

Data PreparationTo configure PAP authentication, you need the following data.

No. Data


2 Username and password of the authenticated

4.3.2 Configuring a Local Router to Authenticate Its Peer in PAPMode


Procedure




Issue 03 (2010-03-31)


Step 2 Run:aaa

The AAA view is displayed.

Step 3 Run:local-user user-name password { simple | cipher } password

The username and password of the authenticated are added to the local user list.

Step 4 Run:quit

Return to the system view.



Step 6 Run:ppp authentication-mode pap [ call-in ]

The local end authenticates the peer end using PAP.

Step 7 Run:restart

The interface is restarted.

NOTE

After changing the username and password, run the restart command, or the shutdown and undoshutdownv commands in the interface view to validate the configuration.

----End

4.3.3 Configuring the Peer to Be Authenticated by the Local Routerin PAP Mode


Procedure





Step 3 Run:ppp pap local-user user-name password { cipher | simple } password



4-7

The username and password of the local end are configured when the local end is configured tobe authenticated using PAP.

Step 4 Run:restart


NOTE

After changing the username and password, use the restart command, or the shutdown and undoshutdown commands in the interface view to validate the configuration.

----End


PrerequisiteThe configurations of the unidirectional PAP function are complete.

Procedurel Run the display interface [ interface-type [ interface-number ] ] command to check the

link status of the interface and the running status of the LCP.

----End

Example

Run the display interface command. If the LCP status is Opened, it means that the PAPauthentication succeeds. For example:<HUAWEI> display interface pos 6/0/0Pos6/0/0 current state : UPLine protocol current state : UPLast up time: 2007-11-03, 12:36:19Description : Pos6/0/0 InterfaceRoute Port, The Maximum Transmit Unit is 4470, Hold timer is 10(sec)Internet Address is 10.1.1.1/30Link layer protocol is PPPLCP opened, IPCP openedTransponder Information: Not in positionPhysical 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: OOF LOF LOS line layer: none path layer: PAIS PRDI SDH error: section layer: B1 31470839 line layer: B2 6140811495 REI 1021746943 path layer: B3 251087875Statistics 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 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets



Issue 03 (2010-03-31)

4.4 Configuring Unidirectional CHAPThis section describes how to configure CHAP authentication.


4.4.2 Configuring a Local Device with a User Name to Authenticate Its Peer in CHAP Mode

4.4.3 Configuring a Local Device Without a User Name to Authenticate Its Peer in CHAP Mode




In CHAP authentication, passwords are sent over the link in encrypted text. The username andpassword of the authenticated can be authenticated in AAA mode or through the RADIUS serverand then added into the user list of the authenticator.

CHAP authentication is classified into the following types:

l Unidirectional: One of two communication parties functions as the authenticator, while theother as the authenticated.

l Bidirectional: Two communication parties function as both the authenticator and theauthenticated.

This section describes how to configure unidirectional CHAP authentication.


Before configuring CHAP authentication, complete the following tasks:

l Connecting interfaces and configuring physical attributes for these interfaces to ensure thatthe physical layer of the interfaces is Up

l Configuring PPP as the link layer protocol of interfaces

Data Preparation

To configure CHAP authentication, you need the following data.

No. Data


2 (Optional) Username of the authenticator

3 Username and password of the authenticated



4-9

4.4.2 Configuring a Local Device with a User Name to AuthenticateIts Peer in CHAP Mode

ContextNOTE

In CHAP authentication, when configuring the username for the authenticator, ensure that the samepassword is configured for the authenticator and the authenticated.

Procedurel Configuring the authenticator


1. Run:system-view


aaa

The AAA view is displayed.3. Run:

local-user user-name password { simple | cipher } password

The username and password of the authenticated are added to the local user list.4. Run:

quit

Return to the system view.5. Run:

interface interface-type interface-number

The interface view is displayed.6. Run:

ppp authentication-mode chap [ pap ] [ call-in ]

The local end authenticates the peer end by using CHAP.

You can run the ppp authentication-mode chap pap command to perform CHAPnegotiation preferentially in LCP negotiation. If the peer end does not support CHAPauthentication, PAP negotiation is performed. If the peer end does not support CHAPor PAP, the LCP negotiation fails. Either CHAP or PAP is involved in a PPPnegotiation.

7. Run:ppp chap user user-name

The local username is configured.8. Run:

restart




Issue 03 (2010-03-31)

NOTE

After changing the username and password, run the restart command, or the shutdown andundo shutdown commands in the interface view to validate the configuration.

l Configuring the authenticated


1. Run:system-view


aaa




quit




ppp chap user user-name


restart


NOTE


----End

4.4.3 Configuring a Local Device Without a User Name toAuthenticate Its Peer in CHAP Mode

Procedurel Configuring the authenticator


1. Run:system-view




4-11

2. Run:aaa




quit




ppp authentication-mode chap [ pap ] [ call-in ]

The local end authenticates the peer end using CHAP.

You can run the ppp authentication-mode chap pap command to perform CHAPnegotiation preferentially in LCP negotiation. If the peer end does not support CHAPauthentication, PAP negotiation is performed. If the peer end does not support CHAPor PAP, the LCP negotiation fails. Either CHAP or PAP is involved in a PPPnegotiation.

7. Run:restart


In authentication, if the username and password of the interface on the peer end areconsistent with the username and password in the local AAA user list, theauthentication succeeds.

l Configuring the authenticated


1. Run:system-view




ppp chap user user-name


ppp chap password { cipher | simple } password

The password of the local end is configured, which is used when the local end isauthenticated by the peer end using CHAP.



Issue 03 (2010-03-31)

5. Run:restart


NOTE


----End


PrerequisiteThe configurations of uidirectional CHAP are complete.

Procedurel Run the display interface [ interface-type [ interface-number ] ] command to check the

PPP configuration and the status of the interface.

----End

Example

Run the display interface command. You can view the status of PPP, LCP, and IPCP. If thestatus of the LCP and IPCP is opened, it means that CHAP authentication succeeds. For example:<HUAWEI> display interface pos 6/0/0Pos6/0/0 current state : UPLine protocol current state : UPLast up time: 2007-11-03, 12:36:19Description : Pos6/0/0 InterfaceRoute Port, The Maximum Transmit Unit is 4470, Hold timer is 10(sec)Internet Address is 10.1.1.1/30Link layer protocol is PPPLCP opened, IPCP openedTransponder Information: Not in positionPhysical 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: OOF LOF LOS line layer: none path layer: PAIS PRDI SDH error: section layer: B1 31470839 line layer: B2 6140811495 REI 1021746943 path layer: B3 251087875Statistics last cleared:never 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, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets



4-13

4.5 Configuring PPP Optional ParametersThis section describes how to configure optional parameters of PPP.


4.5.2 Configuring the Callback Function

4.5.3 Configuring Packet or Packet Header Compression

4.5.4 Configuring the Timeout Period of Negotiation

4.5.5 Configuring the Polling Interval

4.5.6 Configuring DNS Server Address Negotiation

4.5.7 Configuring the PPP Link Quality Detection

4.5.8 Preventing the Peer Host Route from Being Added to the Local Routing Table of DirectRoutes



Applicable Environmentl Callback

When a router works as the callback client and the server allows calling back the numberspecified by the user, you can configure the dial string required to call back the router. Inthis manner, reverse charging is realized.

l Header compression

IP Header Compression (IPHC) is a host-to-host protocol. IPHC is used on the IP networkto compress real-time multimedia services such as voice and video. To improve bandwidthutilization, you can apply IPHC to the link to compress the IP header, UDP header, andRTP header.

l Interval for the negotiation timeout

In PPP negotiation, if no response is received from the peer end within the interval, PPPresends a request for negotiation.

l Polling interval

Link layer protocols such as PPP, FR, and HDLC use a polling timer to check whether alink works normally.

In the case of long network delay or severe congestion, you can prolong the polling intervalto reduce network flapping.

When configuring the polling interval, ensure that both ends are configured with the samepolling interval.

l DNS server address negotiation

When other devices are connected to a router through PPP, for example, a PC is connectedto a router through dialup, the peer device directly accesses the network through the domainname. In this case, the router needs to assign DNS server addresses for the peer device.



Issue 03 (2010-03-31)

If you access a router through a PC, you can run the winipcfg (windows 98) or the ipconfig/all (windows 2000/XP) command to view the DNS server addresses that are provided bythe router.

The NE80E/40E can provide the peer device with two server addresses, a primary DNSserver address and a secondary DNS server address.

l Link quality parameter

PPP link quality detection is to detect the quality of a PPP link in real time, including thePPP link bound in MP.

When the quality of a link is lower than the quality percentage of the forbidden link, thelink is disabled. When the link quality restores to the quality percentage of the recoveredlink, the link is enabled automatically.

To avoid a link from frequently switching between prohibition and restoration, the delayfor restarting a link is required.


Before configuring optional parameters of PPP, complete the following tasks:

l Connecting interfaces and configuring physical attributes for the interfaces to ensure thatthe physical layer of the interfaces is Up

l Configuring PPP as the link layer protocol of the interfaces

l Configuring interfaces to adopt PAP or CHAP authentication, which is required only duringthe configuration of the negotiation timeout interval

Data Preparation

To configure optional parameters of PPP, you need the following data.

No. Data

1 Dial string used for calling back the router

2 Maximum number of RTP connections and maximum number of TCP connectionsin the IPHC function

3 Timeout interval of PPP negotiation

4 Polling interval

5 Primary DNS server address and secondary DNS server address

6 Quality percentage of the forbidden link and quality percentage of the recovered link

4.5.2 Configuring the Callback Function




4-15

Procedure





Step 3 Choose one of the following commands to configure the interface as the callback server or thecallback client:l Run the ppp callback server command to set the interface as the callback server.

l Run the ppp callback client command to set the interface as the callback client.

NOTE

l Only the low-speed serial interface and the AUX interface support the callback function.

l One interface cannot be set as the server and client at the same time.

Step 4 Run:ppp callback ntstring dial-string

The dial string used to call back the router is configured.

NOTE

The ppp callback ntstring command can be used only when the router is configured as the callback client.

----End

4.5.3 Configuring Packet or Packet Header Compression

Procedurel Enabling IPHC on the interface

1. Run:system-view




In NE80E/40E, only synchronous serial interfaces and MP-Group interfaces supportIPHC.

3. Run:ppp compression iphc

IPHC is enabled on the interface.

For the details about IPHC, refer to the HUAWEI NetEngine80E/40E RouterConfiguration Guide - QoS.

----End



Issue 03 (2010-03-31)

4.5.4 Configuring the Timeout Period of Negotiation

Procedure





Step 3 Run:ppp timer negotiate seconds

The timeout period of negotiation is configured on the interface.

NOTE

The MP-Group interface does not support this configuration.

----End

4.5.5 Configuring the Polling Interval

Procedure





Step 3 Run:timer hold seconds

The polling interval is configured on the interface.

NOTE

The GE interfaces and MP-Group interfaces do not support this configuration.

----End

4.5.6 Configuring DNS Server Address Negotiation

Procedurel Admitting any DNS server address proposed by the peer


1. Run:



4-17

system-view




ppp ipcp dns admit-any

Any DNS server address proposed by the peer is admitted.l Configuring the DNS server address of the local negotiation


1. Run:system-view




ppp ipcp dns primary-dns-address [ secondary-dns-address ]

The DNS server address of the local negotiation is configured.

By default, a router does not provide DNS server address for its peer.

----End

4.5.7 Configuring the PPP Link Quality Detection

Procedure





Step 3 Run:ppp lqc close-percentage [ resume-percentage ]

The PPP link quality detection is enabled.

Using the ppp lqc command, you can detect the quality of the low-speed line. The ppp lqccommand can be used only on the serial interface and AUX interface.

Step 4 Choose one of the following methods to restart the interface.l Run the shutdown and undo shutdown commands.



Issue 03 (2010-03-31)

l Run the restart command.

After enabling or disabling the PPP link quality detection, restart the interface to validate theconfiguration.

----End

4.5.8 Preventing the Peer Host Route from Being Added to the LocalRouting Table of Direct Routes

ContextThe PPP link does not strictly require that the peer route and local route exist at the same networksegment. Two ends of the PPP link at different network segments can communicate. In addition,the peer host route at a different network segment is automatically added to local routing tableof direct routes.

However, when one end is configured with an incorrect IP address, the other end automaticallyadds the incorrect peer host route to the local routing table of direct routes. As a result, theincorrect routing information is advertised across the network.

With this command, you can decide whether the peer host route is added to the local routingtable of direct routes.

ProcedureStep 1 Run:

system-view




Step 3 Run:ppp peer hostroute-suppress

The peer host route is prevented from being added to the local routing table of direct routes.

NOTE

After enabling or disabling the function of preventing the peer host route from being added to the localrouting table of direct routes, restart the interface to validate the configuration.



----End


PrerequisiteThe configurations of the PPP otional prameters are complete.



4-19


include } regular-expression ] command to check the PPP configuration and the status ofthe interface.

l Run the display ppp compression iphc rtp [ interface-type interface-number ] commandto check the statistics on the IP header compression on the PPP link.

----End

ExampleRun the display interface command to check the PPP configuration and the status of theinterface. For example:<HUAWEI> display interface pos 6/0/1Pos6/0/1 current state : UPLine protocol current state : UPLast line protocol up time : 2009-08-17 00:19:56Description: Pos6/0/1 InterfaceRoute Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec)Internet Address is 192.168.20.2/24Link layer protocol is PPPLCP opened, IPCP openedThe Vendor Name is FINISAR CORP. , The Vendor PN is FTRJ8519P1BNL-HWTransceiver BW: 1G, Transceiver Mode: Multi ModeWaveLength: 850nm, Transmission Distance: 550mRx Optical Power: -4.95dBm, Tx Optical Power: -3.30dBmPhysical 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 SDH error: section layer: B1 0 line layer: B2 0 REI 16777215 path layer: B3 0 REI 0Statistics 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: 14861 packets, 237808 bytes Input error: 0 shortpacket, 0 longpacket, 1 CRC, 0 lostpacket Output: 14859 packets, 237762 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

Run the display ppp compression iphc rtp command to check the statistics on the IP headercompression on the PPP link. For example:<HUAWEI> display ppp compression iphc rtpIPHC: RTP/UDP/IP header compression Interface: Serial1/0/0:0 Received: Compress/Error/Discard/Total: 0/0/0/0 (Packets) Sent: Compress/Total: 0/0 (Packets) Send/Save/Total: 0/0/0 (Bytes) Connect: Rx/Tx: 300/300



Issue 03 (2010-03-31)

4.6 Configuring MP Binding Using an MP-GroupThis section describes how to configure MP binding by using an MP-group.


4.6.2 Adding an Interface to an MP-Group

4.6.3 Disabling the Endpoint Discriminator Negotiation




When configuring MP binding using MP-Group, the slot number and card number of MP-Groupinterface must be consistent with the slot number and card number of the interface added to theMP-Group.

The interfaces added to the MP-Group can only be the channelized synchronous serial interfaces.

In MP negotiation, different carriers complements differently.

By default, the endpoint discriminator needs to be negotiated in NE80E/40E MP negotiation. Ifno endpoint discriminator is sent, MP negotiation fails. Then the endpoint discriminatornegotiation can not be configured on the local side.

NOTE

You need to configure the local and the peer ends separately. The methods of configuration are the same.


Before configuring MP binding using MP-Group, complete the following tasks:

l Configuring physical attributes of the router interface.

l Configuring the link layer protocol of the interface as PPP.

Data Preparation

To configure MP binding using MP-Group, you need the following data.

No. Data

1 Interface number of the router

2 Interface number of MP-Group

3 IP addresses and subnet masks of the MP-Group interface

4 Username and password of the peer device



4-21

4.6.2 Adding an Interface to an MP-Group

ContextWhen using an MP-group to bind an interface, consider the following items:

l Physical interfaces must be bound into one MP-group in the same mode.

l All physical interfaces in one MP-group must be at the same interface card as the routerdoes not support trans-board and trans-card MP binding.

l Number of the physical interfaces bound in one MP-group that are used to interwork at twoends must be the same.

l Multiple physical interfaces are bound in one local MP-group. The peer interfaces directlyconnected to those physical interfaces must be bound into one MP-group.


Procedure



Step 2 Run:interface mp-group number

The MP-group interface is created.

Step 3 Run:ip address ip-address { mask | mask-length } [ sub ]

The IP address is assigned for the MP-group interface.

Step 4 Run:shutdown

The MP-group interface is shutdown.

Step 5 Run:quit




Step 7 Run:shutdown

The interface is shutdown.

Step 8 Run:ppp mp mp-group number

The interface is added to the MP-group.



Issue 03 (2010-03-31)

Step 9 Run:undo shutdown


Step 10 Run:quit



The MP-group interface view is displayed.


The MP-group is restarted.

----End

4.6.3 Disabling the Endpoint Discriminator Negotiation

Procedure




The MP-Group interface is created.

Step 3 Run:undo discriminator

The terminal discriminator negotiation is disabled.

By default, the endpoint discriminator negotiation is enabled. The LCP status is Up only whenthe endpoint discriminators of the MP-Group ports are the same.

The configuration of the endpoint discriminator negotiation on both ends must be the same. Ifone end is configured with the undo discriminator command whereas the other end isconfigured with the discriminator command, the parameters sent by the end configured withthe undo discriminator command do not contain the endpoint discriminator, and this endaccepts the endpoint discriminator of the other end. As a result, MP cannot be established.

If you want to use the undo discriminator command on the MP-Group interface, you must usethe shutdown and undo shutdown commands to enable the configuration.

Step 4 Run:quit





4-23




When binding an interface to the MP-Group, consider the following items:

l If the LCP status of the interface is Opened, the interface must be restarted. This ensures thatPPP can be renegotiated and the interface can be successfully bound to the MP.

l If the LCP status is not Opened, the interface need not be restarted because PPP canautomatically perform negotiation.

NOTE

To ensure the success of MP binding after PPP is renegotiated, it is recommended to restart all the boundinterfaces after the configuration.

After the undo ppp mp command is successfully run in the interface view, the interface isunbound from the MP. At this time, the interface need not be restarted because PPP canautomatically perform negotiation until the link layer protocol status of the interface changes toUp. The whole process lasts about 40 seconds.

----End


Procedurel Run the display ppp mp [ interface interface-type interface-number ] command to check

the MP binding information.l Run the display interface mp-group [ number ] [ | { begin | exclude | include } regular-

expression ] command to check the status of the MP-group interface.l Run the display interface brief [ | { begin | include | exclude } regular-expression ]

command to check brief information about the MP-Group interface and its memberinterfaces.

----End

ExampleAfter running the display ppp mp command, you can check MP binding information, includingthe status and number of the bound member interfaces.

<HUAWEI> display ppp mpMp-group is Mp-group1/0/1 ===========Sublinks status begin====== Serial1/0/1:1 physical UP,protocol UP Serial1/0/1:2 physical UP,protocol UP Serial1/0/1:3 physical UP,protocol DOWN Serial1/0/1:4 physical UP,protocol DOWN ===========Sublinks status end======== Bundle Multilink, 2 member, slot 1, Master link is Mp-group1/0/1 0 lost fragments, 0 reordered, 0 unassigned, 0 interleaved, sequence 0/0 rcvd/sent The bundled son channels are: Serial1/0/1:1 Serial1/0/1:2



Issue 03 (2010-03-31)

After running the display interface mp-group command, you can check the status of the MP-Group interface. The following is the display of the command:<HUAWEI> display interface mp-groupMp-group1/0/1 current state : UPLine protocol current state : UPLast line protocol up time : 2009-01-20 11:01:43Description:Mp-group1/0/1 InterfaceRoute Port,The Maximum Transmit Unit is 1500Internet Address is 1.2.2.1/24Link layer protocol is PPPLCP opened, MP opened, IPCP reqsentPhysical is MP, baudrate is 1984000 bps 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: 117 packets, 1440 bytes 0 errors, 0 drops Output: 118 packets, 1475 bytes 0 errors, 0 drops

After running the display interface brief [ | { begin | include | exclude } regular-expression ]command, you can check brief information about the physical status, link layer protocol status,bandwidth utilization, and number of incorrect packets of the MP-Group interface and itsmember interfaces. The following is the display of the command:

<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 outErrorsMp-group1/0/1 up up 0% 0% 0 0Serial1/0/0:0 up up 1% 1% 5 0Serial1/0/1:0 up up 1% 1% 2 0Serial1/0/2:0 *down down 0% 0% 0 0Serial1/0/5:0 up down 0% 0.01% 21 0

4.7 Configuring MP Limiting ParametersThis section describes how to configure MP parameters.


4.7.2 Configuring the MRRU of an MP Group

4.7.3 Configuring the Damping Function for MP SubchannelsThe damping function can suppress the frequent flappings of an MP subchannel, and thesubchannel can be released from the damping state only after it keeps Up for a specified timeof period.

4.7.4 Configuring the Minimum Number of Subchannels in the Up State in an MP LinkAfter the LCP negotiation succeeds, a PPP link can be added to an MP link only when the numberof subchannels in the Up state in the MP link reaches the configured minimum value, and then



4-25

the MP can perform the NCP negotiation. That is, you can set the minimum bandwidth for anMP link as required.




After configuring MP binding, you can configure MP limiting parameters to optimize the linkchannels.

The limiting parameters include:

l Maximum receiving re-group unit


Before configuring MP limiting parameters, complete the following tasks:

l Connecting the interface and configuring the physical parameters of the interface to makethe physical layer status of the interface change to Up

l Configuring MP binding

Data Preparation

To configure MP limiting parameters, you need the following data.

No. Data

1 The MRRU of MP

2 Time period during which the MP subchannel status is detected

3 Maximum number of times of the flappings occuring on the MP subchannel withinthe detection time

4 Minimum time during which the MP subchannel keeps Up to be released fromdamping

5 Minimum number of subchannels in the Up state in an MP

NOTE

l After changing the parameters configured in the MP-group view, you need to use the shutdowncommand in all the bound sub-channels to disable the MP binding.

l Then use the undo shutdown command in all the bound sub-channels to bind MP again.

l Finally, all the configured commands will be effective.

4.7.2 Configuring the MRRU of an MP Group



Issue 03 (2010-03-31)

ContextMax-Receive-Reconstructed Unit (MRRU) refers to the maximum size of the packet re-assembled with the received fragment packets, and MP must negotiate MRRU with the remotebefore performing IP packet fragmentation.


Procedure




The MP group interface is displayed.

Step 3 Run:mrru mrru

The MRRU of the MP group is configured.

By default, MRRU is 1500 bytes.

----End

4.7.3 Configuring the Damping Function for MP SubchannelsThe damping function can suppress the frequent flappings of an MP subchannel, and thesubchannel can be released from the damping state only after it keeps Up for a specified timeof period.

ContextDo as follows on the routers configured with MP-Group interfaces:

Procedure




The MP-Group interface view is displayed.

Step 3 Run:ppp mp damping detect-time detect-time flapping-count flapping-count damp-time damp-time

The damping function is configured for the MP subchannels.

----End



4-27

4.7.4 Configuring the Minimum Number of Subchannels in the UpState in an MP Link

After the LCP negotiation succeeds, a PPP link can be added to an MP link only when the numberof subchannels in the Up state in the MP link reaches the configured minimum value, and thenthe MP can perform the NCP negotiation. That is, you can set the minimum bandwidth for anMP link as required.

ContextDo as follows on the routers configured with MP-Group interfaces:

Procedure




The MP-Group interface view is displayed.

Step 3 Run:ppp mp threshold-least number

The minimum number of subchannels in the Up state in the MP link is set.

Step 4 Run:shutdown

The MP-Group interface is shut down.


The MP-Group interface is restarted.

----End


Procedure

Step 1 Run the display current-configuration interface [ interface-type [ interface-number ] ]command to check the configuration of MP-Group interface.

----End

ExampleAfter running the display current-configuration interface command, you can checkconfigurations on the MP-Group interface.

<HUAWEI> display current-configuration interface mp-group 1/0/1#



Issue 03 (2010-03-31)

interface Mp-group1/0/1 mrru 1200 ppp mp threshiold 2 ppp mp damping detect-time 32 flapping-count 32 damping-time 62##return

4.8 Configuring MP FragmentationDescribes how to configure the length of the MP fragment on the MP-Group interface.


4.8.2 Configuring the MP Fragment Function




After binding the interface to the MP, configure MP fragmentation as required to optimize thelink channel.


Before configuring MP fragmentation, complete the following tasks:

l Connecting the interface and configuring the physical parameters of the interface to makethe physical layer status of the interface change to Up.

l Configuring MP binding

Data Preparation

To configure MP fragmentation, you need the following data.

No. Data

1 Length of the MP packet to be fragmented

4.8.2 Configuring the MP Fragment Function

Context

Using the MP fragment function, you can adjust the value of the MP fragment packets.

By default, no fragment value is configured.




4-29

Procedure




The MP group interface is displayed.

Step 3 Run:fragment-threshold threshold

The fragment value of MP data packet is configured.

----End


Procedure

Step 1 Run the display ppp mp [ interface interface-type interface-number ] command to check theMP binding information.

----End

ExampleRun the display ppp mp command, you can view the binding information about the MP-Group.For example:

<HUAWEI> display ppp mp interface mp-group 1/0/1Mp-group is Mp-group1/0/1 ===========Sublinks status begin======Serial1/0/1:1 physical UP,protocol UP Serial1/0/1:2 physical UP,protocol UP Serial1/0/1:3 physical UP,protocol DOWN(damping) Serial1/0/1:4 physical UP,protocol DOWN ===========Sublinks status end======== Bundle Multilink, 2 member, slot 1, Master link is Mp-group1/0/1 0 lost fragments, 0 reordered, 0 unassigned, 0 interleaved, sequence 0/0 rcvd/sent The bundled son channels are: Serial1/0/1:1 Serial1/0/1:2

4.9 Maintaining PPP and MP ConfigurationDescribes how to maintain PPP and MP.



Issue 03 (2010-03-31)

Context

CAUTIONDebugging affects on the performance of the system. So, after the debugging, run the undodebugging all command to disable it immediately.

When the operation faults of PPP and MP occur, use the debugging command in the user viewto debug the PPP and MP link protocol and locate the fault.

For the operation of the debugging, refer to the chapter "Information Center Configuration" inthe HUAWEI NetEngine80E/40E Router Configuration Guide - System Management.

For the debugging commands, refer to the HUAWEI NetEngine80E/40E Router DebuggingReference.

Procedurel Run the debugging ppp all [ verbose ] [ interface interface-type interface-number ]

command to enable the debugging of PPP.l Run the debugging ppp { ccp | chap | ipcp | lcp | mplscp | osicp | pap } { all | error |

event | packet [ verbose ] | state } [ interface interface-type interface-number ] commandto enable the debugging of the PPP control protocols.

l Run the debugging ppp mp { all | error | event | packet [ verbose ] } [ interface interface-type interface-number ] command to enable the debugging of MP.

l Run the debugging ppp ipv6cp { all | error | event | packet | state } [ interface interface-type interface-number ] command to enable the debugging of the IPv6 control protocol.

l Run the debugging ppp { cbcp | ip | mpls-multicast | mpls-unicast | osi-npdu | scp |vjcomp } packet [ verbose ] [ interface interface-type interface-number ] command toenable the debugging of the PPP packets.

l Run the debugging ppp ipv6 packet [ interface interface-type interface-number ]command to enable the debugging of the IPv6 packets.

l Run the debugging ppp core event [ interface interface-type interface-number ] commandto enable the debugging of the PPP core events.

l Run the debugging ppp compression iphc { rtp | tcp } command to enable the debuggingof the IPHC compression of PPP.

----End

4.10 Configuration ExamplesProvides several configuration examples of PPP and MP.

4.10.1 Example for Configuring PAP Authentication

4.10.2 Example for Configuring Unidirectional CHAP Authentication

4.10.3 Example for Configuring Bidirectional CHAP Authentication

4.10.4 Example for Binding MPs into an MP-group



4-31

4.10.1 Example for Configuring PAP Authentication

Networking RequirementsAs shown in Figure 4-1, Router A and Router B are connected through the POS interface. RouterA (the authenticator) is required to authenticate Router B (the authenticated) in PAP mode.

Figure 4-1 Networking diagram of PAP authentication

RouterA RouterB

POS1/0/010.110.0.1/24

POS1/0/010.110.0.2/24


1. Add the user name and password of Router B to the local user list of Router A.2. Configure Router A to authenticate Router B in PAP mode.3. Configure the local user name and password on Router B.


l The user name and password of Router B

l The IP address of the interface on Router A

l The IP address of the interface on Router B

Procedure

Step 1 Configure Router A

# Add the username and password of Router B to the local user list of Router A.

<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] aaa[RouterA-aaa] local-user rtb password simple quidway[RouterA-aaa] quit

# Configure an IP address for POS 1/0/0 and configure the link-layer encapsulation protocol asPPP.

[RouterA] interface pos 1/0/0[RouterA-Pos1/0/0] ip address 10.110.0.1 255.255.255.0[RouterA-Pos1/0/0] link-protocol ppp

# Authenticate Router B in the PAP mode.



Issue 03 (2010-03-31)

[RouterA-Pos1/0/0] ppp authentication-mode pap[RouterA-Pos1/0/0] undo shutdown



<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] interface pos 1/0/0[RouterB-Pos1/0/0] ip address 10.110.0.2 255.255.255.0[RouterB-Pos1/0/0] link-protocol PPP

# Configure the username and password sent to the authentication object in the PAP mode.

[RouterB-Pos1/0/0] ppp pap local-user rtb password simple quidway[RouterB-Pos1/0/0] undo shutdown


After the configuration is completed, executing the display interface command on everyrouter, you can see the LCP status is Opened.

Take Router A as an example.<RouterA-Pos1/0/0] display interface pos 1/0/0 Pos1/0/0 current state : UPLine protocol current state : UPLast up time: 2007-11-03, 12:36:19Description: Pos1/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec)Internet Address is 10.110.0.1/24Link layer protocol is PPPLCP opened, IPCP openedThe Vendor PN is FTRJ1321P1BTLPort BW: 2.5G, Transceiver max BW: 2.5G, Transceiver Mode: SingleModeWaveLength: 1310nm, Transmission Distance: 5kmRx Power: -3.91dBm, Tx Power: -1.87dBm Physical 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 SDH error: section layer: B1 21424008 line layer: B2 1093838510 REI 705143440 path layer: B3 45521365Statistics last cleared:never Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 152 bits/sec, 0 packets/sec Input: 18791 packets, 490767 bytes Input error: 10 shortpacket, 0 longpacket, 143 CRC, 0 lostpacket Output: 30960 packets, 1408202 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

----End


#sysname RouterA



4-33

#interface Pos 1/0/0 link-protocol ppp ppp authentication-mode pap undo shutdown ip address 10.110.0.1 255.255.255.0#aaalocal-user rtb password simple quidway#return

l Configuration file of Router B#sysname RouterB#interface Pos1/0/0 link-protocol ppp ppp pap local-user rtb password simple quidway undo shutdown ip address 10.110.0.2 255.255.255.0#return

4.10.2 Example for Configuring Unidirectional CHAPAuthentication

Networking RequirementsAs shown in Figure 4-2, Router A is required to authenticate Router B in CHAP mode andshould be configured with a user name.

Figure 4-2 Networking diagram of unidirectional CHAP authentication

RouterA RouterB

POS1/0/010.110.0.1/24

POS1/0/010.110.0.2/24


1. Add the user name and password of Router B to the local user list of Router A.2. Configure the local user name for Router A.3. Configure Router A to authenticate the peer in CHAP mode.4. Configure the local user list on Router B.5. Configure the local user name for Router B.




Issue 03 (2010-03-31)

l Local user name of Router A

l Local user name and password of Router B

l IP address of the interface on Router A

l IP address of the interface on Router B

Procedure



<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] aaa[RouterA-aaa] local-user rtb password simple hello[RouterA-aaa] quit



# Configure the local to authenticate the peer in CHAP mode.

[RouterA-Pos1/0/0] ppp authentication-mode chap

# Configure the local username of RouterA

[RouterA-Pos1/0/0] ppp chap user rta

# Enable the interface.

[RouterA-Pos1/0/0] undo shutdown

Step 2 Configure Router B

# Add the user name of Router A and the local password to the local user list of Router B.

<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] aaa[RouterB-aaa] local-user rta password simple hello[RouterB-aaa] quit

# Configure the IP address for POS 1/0/0 and configure the link-layer encapsulation protocol asPPP.

[RouterB] interface pos 1/0/0[RouterB-Pos1/0/0] ip address 10.110.0.2 255.255.255.0[RouterB-Pos1/0/0] link-protocol ppp

# Configure the peer to authenticate the local in CHAP mode.

[RouterB-Pos1/0/0] ppp chap user rtb[RouterB-Pos1/0/0] undo shutdown


After the configuration is complete, running the display interface command on every router,you can find the LCP state is LCP opened. Take the Router A as the example.[RouterA] display interface pos 1/0/0Pos1/0/0 current state : UP



4-35

Line protocol current state : UPLast up time: 2007-11-03, 12:36:19Description: Pos1/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec)Internet Address is 10.110.0.1/24Link layer protocol is PPPLCP opened, IPCP openedThe Vendor PN is FTRJ1321P1BTLPort BW: 2.5G, Transceiver max BW: 2.5G, Transceiver Mode: SingleModeWaveLength: 1310nm, Transmission Distance: 5kmRx Power: -3.91dBm, Tx Power: -1.87dBm Physical 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 SDH error: section layer: B1 21424008 line layer: B2 1093838510 REI 705143440 path layer: B3 45521365Statistics last cleared:never Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 152 bits/sec, 0 packets/sec Input: 18791 packets, 490767 bytes Input error: 10 shortpacket, 0 longpacket, 143 CRC, 0 lostpacket Output: 30960 packets, 1408202 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

----End


#sysname RouterA#interface Pos1/0/0 link-protocol ppp ppp authentication-mode chap ppp chap user rta undo shutdown ip address 10.110.0.1 255.255.255.0#aaa local-user rtb password simple hello#return

l Configuration file of Router B#sysname RouterB#interface Pos1/0/0 link-protocol ppp ppp chap user rtb undo shutdown ip address 10.110.0.2 255.255.255.0#aaa local-user rta password simple hello#return



Issue 03 (2010-03-31)

4.10.3 Example for Configuring Bidirectional CHAPAuthentication


As shown in Figure 4-3, Router A and Router B need to perform bidirectional CHAPauthentication.

Figure 4-3 Networking diagram of bidirectional CHAP authentication

RouterA RouterB

POS1/0/010.110.0.1/24

POS1/0/010.110.0.2/24



1. Configure the local user lists on Router A and Route B.2. Configure local user names for Router A and Router B.3. Enable CHAP authentication on the interfaces of Router A and Route B.

Data Preparation

To complete the configuration, you need the following data:

l The user names of Router A and Router B

l The passwords of Router A and Router B

l The IP address of the interface on Router A

l The IP address of the interface onRouter B

NOTE

Router A and Router B must be configured with the same password, or the authentication fails.

Procedure



<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] aaa[RouterA-aaa] local-user rtb password simple hello[RouterA-aaa] quit



4-37



# Configure the username of Router A used in its authentication by Router B in the CHAP mode.

[RouterA-Pos1/0/0] ppp chap user rta

# Configure the authentication in CHAP mode.

[RouterA-Pos1/0/0] ppp authentication-mode chap[RouterA-Pos1/0/0] undo shutdown


# Add the username of Router A and the local password to the local user list of Router B.

<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] aaa[RouterB-aaa] local-user rta password simple hello[RouterB-aaa] quit


[RouterB] interface pos 1/0/0[RouterB-Pos1/0/0] ip address 10.110.0.2 255.255.255.0[RouterB-Pos1/0/0] link-protocol ppp

# Configure the user name of Router B used in its authentication by Router A in the CHAP mode.

[RouterB-Pos1/0/0] ppp chap user rtb

# Configure the authentication in CHAP mode.

[RouterB-Pos1/0/0] ppp authentication-mode chap[RouterB-Pos1/0/0] undo shutdown


After the configuration is completed, running the display interface command on every router,you can see the LCP status is Opened.[RouterA] display interface pos 1/0/0Pos1/0/0 current state : UPLine protocol current state : UPLast up time: 2007-11-03, 12:36:19Description: Pos1/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec)Internet Address is 10.110.0.1/24Link layer protocol is PPPLCP opened, IPCP openedThe Vendor PN is FTRJ1321P1BTLPort BW: 2.5G, Transceiver max BW: 2.5G, Transceiver Mode: SingleModeWaveLength: 1310nm, Transmission Distance: 5kmRx Power: -3.91dBm, Tx Power: -1.87dBm Physical 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 SDH error:



Issue 03 (2010-03-31)

section layer: B1 21424008 line layer: B2 1093838510 REI 705143440 path layer: B3 45521365Statistics last cleared:never Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 152 bits/sec, 0 packets/sec Input: 18791 packets, 490767 bytes Input error: 10 shortpacket, 0 longpacket, 143 CRC, 0 lostpacket Output: 30960 packets, 1408202 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

----End


#sysname RouterA#interface Pos1/0/0 link-protocol ppp ppp authentication-mode chap ppp chap user rta undo shutdown ip address 10.110.0.1 255.255.255.0#aaa local-user rtb password simple hello #return

l Configuration file of Router B#sysname RouterB#interface Pos1/0/0 link-protocol ppp ppp authentication-mode chap ppp chap user rtb undo shutdown ip address 10.110.0.2 255.255.255.0#aaa local-user rta password simple hello #return

4.10.4 Example for Binding MPs into an MP-group

Networking RequirementsFor the two serial interfaces of Router A and Router B are connected respectively with eachother, you can bind MP group to configure MP binding.

Figure 4-4 Networking diagram of the MP-group binding

Router A Router BSerial1/0/1:0 Serial2/0/1:0

Serial1/0/0:0 Serial2/0/0:0

Mp-group1/0/1111.1.1.1/24

Mp-group2/0/1111.1.1.2/24



4-39


1. Configure the local user lists on Router A and Router B.2. Enable PAP authentication on Router A and Router B.3. Create MP-group interface and add related interfaces to MP-group.4. Restart interfaces to validate the configuration.


l The IP addresses of the Mp-groups on Router A

l The IP addresses of the Mp-groups on Router B

l The bound sub-tunnel is authenticated by the PAP

NOTE

l The slot number and card number of MP-Group interface must be consistent with the slot number andcard number of the interface added to the MP-Group.


l PAP or CHAP authentication is unnecessarily configured when you configure MP binding by usingMP-group.

ProcedureStep 1 Configure Router A.


<RouterA> system-view[RouterA] aaa[RouterA-aaa] local-user rtb password simple rtb[RouterA-aaa] quit

# Create an Mp-group interface and configure the corresponding interface.

[RouterA] interface mp-group1/0/1[RouterA-Mp-group1/0/1] ip address 111.1.1.1 255.255.255.0[RouterA-Mp-group1/0/1] shutdown[RouterA-Mp-group1/0/1] quit

# Configure Serial 1/0/0:0 to perform the PAP authentication.

[RouterA] interface serial1/0/0:0[RouterA-Serial1/0/0:0] link-protocol ppp[RouterA-Serial1/0/0:0] ppp authentication-mode pap[RouterA-Serial1/0/0:0] ppp pap local-user rta password simple rta[RouterA-Serial1/0/0:0] shutdown

# Add Serial 1/0/0:0 to the Mp-group interface.

[RouterA-Serial1/0/0:0] ppp mp mp-group1/0/1[RouterA-Serial1/0/0:0] quit

# Configure Serial 1/0/1:0 to perform the PAP authentication.

[RouterA] interface Serial1/0/1:0



Issue 03 (2010-03-31)

[RouterA-Serial1/0/1:0] link-protocol ppp[RouterA-Serial1/0/1:0] ppp authentication-mode pap[RouterA-Serial1/0/1:0] ppp pap local-user rta password simple rta[RouterA-Serial1/0/1:0] shutdown


[RouterA-Serial1/0/1:0] ppp mp mp-group1/0/1[RouterA-Serial1/0/1:0] quit


# Add the username and password of Router A to the local user list of Router B.

<RouterB> system-view[RouterB] aaa[RouterB-aaa] local-user rta password simple rta[RouterB-aaa] quit

# Create an Mp-group interface and configure the corresponding IP address.

[RouterB] interface mp-group2/0/1[RouterB-Mp-group2/0/1] ip address 111.1.1.2 255.255.255.0[RouterB-Mp-group2/0/1] shutdown[RouterB-Mp-group2/0/1] quit

# Configure Serial 2/0/0:0 and perform the PAP authentication.

[RouterB] interface serial2/0/0:0[RouterB-Serial2/0/0:0] link-protocol ppp[RouterB-Serial2/0/0:0] ppp authentication-mode pap[RouterB-Serial2/0/0:0] ppp pap local-user rtb password simple rtb[RouterB-Serial2/0/0:0] shutdown


[RouterB-Serial2/0/0:0] ppp mp mp-group2/0/1[RouterB-Serial2/0/0:0] quit

# Configure Serial 2/0/1:0 and perform the PAP authentication.

[RouterB] interface serial2/0/1:0[RouterB-Serial2/0/1:0] link-protocol ppp[RouterB-Serial2/0/1:0] ppp authentication-mode pap[RouterB-Serial2/0/1:0] ppp pap local-user rtb password simple rtb[RouterB-Serial2/0/1:0] shutdown


[RouterB-Serial2/0/1:0] ppp mp mp-group2/0/1[RouterB-Serial2/0/1:0] quit

Step 3 Bind the sub-tunnel.

# Restart the sub-tunnel on Router A.

[RouterA] interface serial1/0/0:0[RouterA-Serial1/0/0:0] undo shutdown[RouterA-Serial1/0/0:0] quit[RouterA] interface serial1/0/1:0:0[RouterA-Serial1/0/1:0:0] undo shutdown[RouterA-Serial1/0/1:0:0] quit[RouterA] interface mp-group1/0/1[RouterA-Mp-group1/0/1] undo shutdown[RouterA-Mp-group1/0/1] quit

# Restart the sub-tunnel on Router B.

[RouterB] interface serial2/0/0:0[RouterB-Serial2/0/0:0] undo shutdown



4-41

[RouterB-Serial2/0/0:0] quit[RouterB] interface serial2/0/1:0[RouterB-Serial2/0/1:0] undo shutdown[RouterB-Serial2/0/1:0] quit[RouterB] interface mp-group2/0/1[RouterB-Mp-group2/0/1] undo shutdown[RouterB-Mp-group2/0/1] quit


# Check the configuration on Router A.

[RouterA] display ppp mp interface Mp-group1/0/1Mp-group is Mp-group1/0/1 ===========Sublinks status begin====== Serial1/0/0:0 physical UP,protocol UP Serial1/0/1:0 physical UP,protocol UP ===========Sublinks status end======== Bundle Multilink, 2 member, slot 0, Master link is Mp-group1/0/1 0 lost fragments, 0 reordered, 0 unassigned, 0 interleaved, sequence 0/0 rcvd/sent The bundled son channels are: Serial1/0/0:0 Serial1/0/1:0

# Check the Mp-group 2/0/1 status on Router B.

[RouterB] display ppp mp interface Mp-group2/0/1Mp-group is Mp-group2/0/1===========Sublinks status begin====== Serial2/0/0:0 physical UP,protocol UPSerial2/0/1:0 physical UP,protocol UP===========Sublinks status end======== Bundle Multilink, 2 member, slot 2, Master link is Mp-group2/0/ 0 lost fragments, 0 reordered, 0 unassigned, 0 interleaved, sequence 0/0 rcvd/sent The bundled son channels are: Serial2/0/0:0 Serial2/0/1:0

You can ping through the IP address of the MP-group 2/0/1 on Router A.


----End


# sysname RouterA#interface Serial1/0/0:0 undo shutdown link-protocol ppp ppp authentication-mode pap ppp pap local-user rta password simple rta



Issue 03 (2010-03-31)

ppp mp Mp-group 1/0/1#interface Serial1/0/1:0 undo shutdown link-protocol ppp ppp authentication-mode pap ppp pap local-user rta password simple rta ppp mp Mp-group 1/0/1 #interface Mp-group1/0/1 undo shutdown ip address 111.1.1.1 255.255.255.0#aaa local-user rtb password simple rtb #return

l Configuration file of Router B# sysname RouterB#interface Serial2/0/0:0 undo shutdown link-protocol ppp ppp authentication-mode pap ppp pap local-user rtb password simple rtb ppp mp Mp-group 2/0/1#interface Serial2/0/1:0 undo shutdown link-protocol ppp ppp authentication-mode pap ppp pap local-user rtb password simple rtb ppp mp Mp-group 2/0/1#interface Mp-group2/0/1 undo shutdown ip address 111.1.1.2 255.255.255.0#aaa local-user rta password simple rta #return



4-43

5 Frame Relay Configuration

About This Chapter

Describes frame relay related concepts and configuration steps for frame relay compression,LMI type, frame relay switching, and PVC standby groups, along with typical examples.

5.1 Introduction to Frame RelayDescribes concepts and fundamentals of FR.

5.2 Configuring FRDescribes how to configure FR.

5.3 Configuring FR LMI Type and Related ParametersDescribes how to configure FR LMI.

5.4 Maintaining Frame Relay ConfigurationDescribes how to maintain FR .

5.5 Configuration ExamplesProvides several configuration examples of FR.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access 5 Frame Relay Configuration


5-1

5.1 Introduction to Frame RelayDescribes concepts and fundamentals of FR.

5.1.1 FR Protocol Overview

5.1.2 Features of FR on the NE80E/40E

5.1.1 FR Protocol OverviewA Frame Relay (FR) network provides data communication between user devices (such asrouters and hosts).

According to different functions, FR devices and interfaces can be divided into Data TerminalEquipment (DTE) , Data Circuit-terminating Equipment (DCE) , and Network-to-NetworkInterfaces (NNIs) .

In practice, the DTE interface can be connected only with the DCE interface; the NNI interfacecan be connected only with the NNI interface. For the equipment used for FR switching, its FRinterface type should be NNI or DCE.

A FR network can be a public network, a private network, or a network formed by directconnection between data devices.

As a statistics multiplexing protocol, the FR protocol can provide multiple Virtual Circuits (VCs)over a single physical transmission line. VCs are differentiated by Data Link ConnectionIdentifiers (DLCIs). Each VC detects and maintains the VC status through the LocalManagement Interface (LMI).

5.1.2 Features of FR on the NE80E/40E

On the NE80E/40E, the POS interfaces support the frame relay.

5.2 Configuring FRDescribes how to configure FR.


5.2.2 Configuring Basic FR Functions



Applicable EnvironmentFR is a fast packet switching technology developed on the basis of X.25 technology. Itimplements bandwidth multiplexing and dynamic allocation, provides a reasonable bandwidthmanagement and congestion avoidance mechanism, and is widely used.

FR has two kinds of protocols: Internet Engineering Task Force (IETF) and nonstandard.

5 Frame Relay ConfigurationHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access


Issue 03 (2010-03-31)

IETF is used to encapsulate the packets according to RFC 1490 specifications and nonstandardis used to interconnect with routers of other vendors.

In FR, both parties in communication are distinguished as DTE and DCE and they configure theinterface with DTE or DCE format according to their respective location in a network.

The FR module has two types of interfaces: main interface and sub-interface. The NE80E/40Ecan communicate with other devices only through P2P sub-itnerfaces if the link layer protocolis FR.

For the network layer, the sub-interface can be used to configure the PVC. This PVC is used toconnect with the remote equipment.

Data Link Connection Identifier is locally valid. You can specify the same DLCI number fortwo ends of a link, or specify the same DLCI number for multiple interfaces. Different physicalinterfaces, however, must be configured with different DLCI numbers.

Pre-configuration TasksBefore configuring the basic FR functions, configure the physical attributes of the FR interfaceon a router.

Data PreparationTo configure basic FR functions, you need the following data.

No. Data

1 FR interface number of a router and IP addresses to be allocated

2 Interface number of multilink FR bundle

3 DLCI to be allocated to the interface

4 Interface number of the FR sub-interfaces

5.2.2 Configuring Basic FR Functions


Procedure




The FR interface view is displayed.



5-3

Step 3 Run:link-protocol fr [ ietf | nonstandard ]

The link layer protocol of the interface is configured as FR.

By default, the encapsulation format is IETF.

A FR sub-interface can be created only after the FR main interface is configured.

NOTE

l After the FR encapsulation format of the interface is changed, the system automatically deletes all theFR configurations on the interface. Then, you need to delete all the sub-interfaces to re-configure theFR.

l After modifying the link layer protocol, you need to first run the shutdown command to shut downthe interface and then run the undo shutdown command to restart the interface to validate theconfiguration.

Step 4 ( Optional )Run:fr interface-type { dte |dce }

The type of the FR interface is configured.

By default, the FR interface type is DTE.

Step 5 Run:quit


Step 6 Run:interface interface-type interface-number.subnumber

An FR sub-interface is created.

NOTE

l NE80E/40E supports the FR sub-itnerfaces only in P2P mode.

l An FR sub-interface must be of the same type as that of its main interface.

l When sub-interfaces exist, if you execute the shutdown command and the undo shutdown commandon the main interface in succession, the two commands should be used at an interval of at least 15seconds.

Step 7 Run:fr dlci dlci

The DLCI of the interface is configured.

For an FR sub-interface, the DLCI must be configured. In addition, DLCIs on both ends mustbe consistent.

Step 8 Run:quit

Return to the interface view.

Step 9 Run:ip address ip-address { mask | mask-length }

The IP address of the sub-interface is configured.

----End



Issue 03 (2010-03-31)


PrerequisiteThe configurations of FR are complete.

Procedurel Run the display fr interface [ interface-type interface-number[.subnumber ] ] command

to check the status of the FR protocol and information about the interface.

l Run the display fr map-info [ interface interface-type interface-number[.subnumber ] ]command to check the mapping between the protocol address and the FR address.

----End

Example

Run the display fr interface command. If the status of the FR protocol and information aboutthe interface are displayed, it means the configuration succeeds.<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 the mapping between the protocol address and theFR address is displayed, it means the configuration succeeds. Detailed address mappinginformation is not displayed for P2P sub-interfaces.<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

5.3 Configuring FR LMI Type and Related ParametersDescribes how to configure FR LMI.


5.3.2 Configuring FR LMI and Related Parameters of DTE

5.3.3 Configuring FR LMI and Related Parameters of DCE




When the LMI protocol is needed to maintain link status and PVC status of FR as well as optimizethe running of the device, you need to configure the LMI type and related parameters.


Before configuring FR LMI type and related parameters, complete the following tasks:



5-5

l Configuring physical parameters for Frame Relay interfaces

l Configuring Frame Relay interfaces

Data PreparationTo configure the FR LMI type and related parameters, you need the following data:

No. Data

1 FR interface number of a router and IP addresses to be allocated

2 Required n391, n392 and n393 parameters as well as polling interval on DTE

3 Required n392, n393 and t392 parameters on DCE

5.3.2 Configuring FR LMI and Related Parameters of DTE

Procedure





NOTE

The FR LMI and related parameters can be configured only on the main interface.

Step 3 Run:fr lmi type { ansi | nonstandard | q933a }

The FR LMI type is configured.

By default, the LMI protocol type of is q933a.


The polling interval (determined by T391) on the DCE device is configured.

Step 5 Run:fr lmi n391dte n391-value

The LMI N391 parameters on the DTE device are configured.


The DTE N392 parameter is configured.




Issue 03 (2010-03-31)

The DTE N393 parameter is configured.

----End

5.3.3 Configuring FR LMI and Related Parameters of DCE

Procedure





NOTE

The FR LMI and related parameters can be configured only on the main interface.

Step 3 Run:fr lmi type { ansi | nonstandard | q933a }

The FR LMI type is configured.

By default, the LMI protocol type of is q933a.

Step 4 Run:fr lmi t392dce t392-value

The timeout period (determined by T392) for the DCE device to wait for a status request packetis configured. LMI N391 parameters on the DTE device are configured.

Step 5 Run:fr lmi n392dce n392-value

The DCE N392 parameter is configured.

Step 6 Run:fr lmi n393dce n393-value

The DCE N393 parameter is configured.

----End


PrerequisiteThe configurations of FR LMI type and related parameters are complete.

Procedurel Run the display fr lmi-info [ interface interface-type interface-number ] command to

check statistics about FR LMI packets.

----End



5-7

ExampleRun the display fr lmi-info command. If statistics about FR LMI packets are displayed, it meansthe configuration succeeds. For example:<HUAWEI> display fr lmi-infoFrame relay LMI statistics for interface Pos2/1/0 (DCE, ANSI) T392DCE = 15, N392DCE = 5, N393DCE = 4 in status enquiry = 0, out status = 0 status enquiry timeout = 0, discarded messages = 0

5.4 Maintaining Frame Relay ConfigurationDescribes how to maintain FR .

5.4.1 Clearing the Statistics of FR and Dynamic Address Mapping Entries

5.4.2 Debugging FR

5.4.1 Clearing the Statistics of FR and Dynamic Address MappingEntries

Procedurel Run the reset counters interface [ interface-type [ interface-number ] ] command to check

the interface statistics displayed by running the display interface command.

----End

5.4.2 Debugging FR

Context

CAUTIONDebugging affects the performance of the system. So, after the debugging, run the undodebugging all command to disable it immediately.

When a fault of FR occurs, execute the following debugging commands in user view to debugFR and to locate the fault. For detailed steps, refer to the "Information Center Configuration" inthe HUAWEI NetEngine80E/40E Router Configuration Guide - System Management. For thedescription of debugging commands, refer to the HUAWEI NetEngine80E/40E RouterDebugging Reference.

NOTE

l If the debugging is enabled globally, running the same debugging command on the interface does nottake effect.

l If the debugging is disabled globally, running the same undo debugging command on the interfacedoes not take effect.

l If the verbose option has been selected, to disable it, use the undo debugging command. For example,after the debugging fr packet ip verbose command is executed, the debugging fr packet ip commanddoes not take effect, and the previous output of the debugging fr packet ip verbose command remains.



Issue 03 (2010-03-31)

Procedurel Run the debugging fr { all | compress | congestion | de | lmi | transmit-rate }

[ interface interface-type interface-number ] debugging fr { event | ipc } command in theuser view to enable the FR debugging.

l Run the debugging fr fragment interface interface-type interface-number dlci-numbercommand in the user view to enable the packet fragment debugging.

l Run the debugging fr inarp [ verbose ] [interface interface-type inertface-number[ dlci dlci-number] ] command in the user view to enable the FR inverse ASP. (The 64-byte packets can be output if the verbose is chosen.)

l Run the debugging fr packet [ ip | mpls | isis | switch | error ] [ verbose ] [ interfaceinterface-type inertface-number [ dlci dlci-number ] ] command in the user view to enablethe FR packets debugging and output the debugging information according to differentpackets.

----End

5.5 Configuration ExamplesProvides several configuration examples of FR.

5.5.1 Example for Connecting Devices with POS Interfaces Through FR Network

5.5.1 Example for Connecting Devices with POS Interfaces ThroughFR Network


As shown in Figure 5-1, routers are interconnected through POS interfaces on the FRnetwork,and routers work in DTE mode as user devices.

Router A connects Router B and Router C, which reside on different network segments fromRouter A, through sub-interfaces.

Figure 5-1 Networking diagram of connecting routers using the POS interface through FRnetwork

FrameRelay

networkRouter A

Router B

Router C

POS1/0/0.1DLCI=21

10.1.1.1/30

POS1/0/0.2DLCI=22

10.2.1.1/30

POS1/0/0.1DLCI=21

10.1.1.2/30

POS1/0/0.2DLCI=22

10.2.1.2/30



5-9



1. Configure FR as the link protocol.2. Configure the working mode for interfaces.3. Configure IP addresses for interfaces.4. Configure the address mapping.

Data Preparation




l IP address and DLCI of POS 1/0/0.1 on Router B

l IP address and DLCI of POS 1/0/0.2 on Router C

Procedure

Step 1 Configure Router A.<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] interface pos 1/0/0

# Encapsulate the FR protocol.

[RouterA-Pos1/0/0] link-protocol fr[RouterA-Pos1/0/0] fr interface-type dte[RouterA-Pos1/0/0] undo shutdown[RouterA-Pos1/0/0] quit





Step 2 Configure Router B and Router C.

The method of configuring Router B and Router C is the same as the method of configuringRouter A. The configuration details are not mentioned here.



Issue 03 (2010-03-31)


Run the display interface pos command on each router. You can find that the connectivity ofPOS interfaces is Up.

Run the ping command on each router. Each router can ping through the network.

----End


# sysname RouterA#interface Pos1/0/0 link-protocol fr undo shutdown#interface Pos1/0/0.1 fr dlci 21 ip address 10.1.1.1 255.255.255.252#interface Pos1/0/0.2 fr dlci 22 ip address 10.2.1.1 255.255.255.252#return

l Configuration file of Router B#sysname RouterB#interface Pos1/0/0 link-protocol fr undo shutdown#interface Pos1/0/0.1 fr dlci 21 ip address 10.1.1.2 255.255.255.252#return

l Configuration file of Router C#sysname RouterC#interface Pos1/0/0 link-protocol fr undo shutdown#interface Pos1/0/0.2 fr dlci 22 ip address 10.2.1.2 255.255.255.252#return



5-11

6 HDLC and IP-Trunk Configuration

About This Chapter

Describes how to encapsulate an interface with HDLC protocol, how to configuration IP-Trunkinterface and how to set the polling interval.

6.1 Introduction to HDLC and IP-TrunkDescribes the concepts of HDLC and IP-Trunk interfaces.

6.2 Configuring HDLCDescribes how to configure HDLC.

6.3 Configuring an IP-Trunk InterfaceDescribes how to configure an IP-Trunk interface and the basic parameters of the interface.

6.4 Maintaining HDLC and IP-Trunk ConfigurationDescribes how to maintain HDLC and IP-Trunk interfaces.

6.5 Configuration ExamplesProvides several configuration examples of HDLC.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access 6 HDLC and IP-Trunk Configuration


6-1

6.1 Introduction to HDLC and IP-TrunkDescribes the concepts of HDLC and IP-Trunk interfaces.

6.1.1 HDLC and IP-Trunk Interface Overview

6.1.2 Features of HDLC and IP-Trunk interfaces on the router

6.1.1 HDLC and IP-Trunk Interface OverviewThe High-level Data Link Control (HDLC) is a bit-oriented link layer protocol. HDLC is featuredby its transparent transmission of any kind of bit flow. The data is not required to be a characterset.

A trunk is aggregated by multiple ports among which load balancing is carried out. A trunk canenhance the connection reliability.

Trunk interfaces are divided into Eth-Trunk interface and IP-Trunk interface.

The IP-Trunk consists of POS links only. The Eth-Trunk consists of Ethernet links only. Forconfiguration of the Eth-Trunk interface, refer to the HUAWEI NetEngine80E/40E RouterConfiguration Guide - LAN Access & MAN Access.

The IP-Trunk technology has the following advantages:

l Increasing bandwidth: Bandwidth of an IP-Trunk interface is the sum of all the bandwidthof member ports.

l Enhancing reliability: If a member link failed, traffic is automatically switched to otheravailable links.

6.1.2 Features of HDLC and IP-Trunk interfaces on the routerThe protocols in standard HDLC suite operate on the synchronous serial lines.

The IP-Trunk consists of POS links only. The link layer protocol of the member interface joiningthe IP-Trunk interface must be HDLC.

Up to 64 trunk interfaces can be created on a router, and each trunk interface can contain up to16 physical member links.

An IP-Trunk interface has the following characteristics:

l Supports configured IP addresses. When forwarding packets, each member interface usesthe IP address of the IP-Trunk interface.

l Supports MPLS forwarding, and Layer 3 forwarding (including unicast and multicast). TheHash algorithm can be used in load balancing by flow.

l Supports QoS based on physical ports rather than logical ports.

l Supports MPLS and binding VPN instances.

l Supports hot backup and hot swap.

6 HDLC and IP-Trunk ConfigurationHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access


Issue 03 (2010-03-31)

NOTE

If member ports of the Trunk are not on the same LPU, you need to configure the BFD session to detectthe links between member ports and configure the association between process pst and interfaces in theBFD session. Otherwise, in some scenarios (for example, restarting the LPU where member ports of theTrunk locate), traffic loss can be caused. For detailed configurations of BFD, refer to the HUAWEINetEngine80E/40E Router Configuration Guide - Reliability.

6.2 Configuring HDLCDescribes how to configure HDLC.


6.2.2 Encapsulating an Interface with HDLC

6.2.3 Configuring the IP Address of the Interface

6.2.4 Setting the Polling Interval



Applicable EnvironmentWhen you need to enable the bits synchronous transmission using the link layer protocol, youcan adopt the HDLC protocol.

Pre-configuration TasksBefore configuring the basic HDLC functions, configure the physical attributes of the interfaceto make the physical status of the interface become Up.

Data PreparationTo configure HDLC, you need the following data.

No. Data

1 Numbers of the interfaces on the router

6.2.2 Encapsulating an Interface with HDLC

Procedure






6-3


Step 3 Run:link-protocol hdlc

The interface is configured with HDLC.

----End

6.2.3 Configuring the IP Address of the Interface

Procedure





Step 3 Choose one of the following steps to configure the IP address or IP unnumbered address of theinterface as required.l Run the ip address ip-address { mask | mask-length } [ sub ] command to configure the IP

address of the interface.l Run the ip address unnumbered interface interface-type interface-number command to

configure the IP unnumbered address.

NOTE

If you configure IP address unnumbered on an interface encapsulated with HDLC, the borrower must havethe ability to learn the route to the remote end. Otherwise, it cannot reach the remote end.

When you use IP address unnumbered, you can configure static route or dynamic routingprotocol to make the borrower learn the route to the remote end.

Note the following principles:

l If you use dynamic routing protocol, ensure the length of the learned route mask is longerthan that of the lender's IP address mask, because the NE80E/40E adopts the principle oflongest match in routing lookup.

l If you use static route and the IP address of the lender adopts 32-bit mask, the length of thestatic route mask should be shorter than 32 bits.

l If you use static route and the IP address of the lender adopts a mask less than 32 bits, thelength of the static route mask should be longer than that of the lender's IP address mask.

----End

6.2.4 Setting the Polling Interval

Procedure




Issue 03 (2010-03-31)





The polling interval is configured.

By default, the pooling interval is 10 seconds. If it is set to 0, then link detection is prohibited.

The link layer protocols such as PPP, FR, and HDLC adopt a polling timer to check the statusof a link. Configure identical polling interval on the both ends.

You can adopt the default polling interval or adjust the polling interval as required. In the caseof long network delay or high congestion, you can prolong the polling interval to reduce thepossibility of network flapping.

NOTE

The GE interfaces, MP-Group interfaces do not support this configuration.

----End


PrerequisiteThe configurations of HDLC are complete.


include } regular-expression ] command to check the status, link layer protocol andconfiguration of the interface.

----End

ExampleRun the display interface command, you can view the status, link layer protocol andconfiguration of the interface.

<HUAWEI> display interface pos 1/0/0Pos1/0/0 current state : UPLine protocol current state : UPLast line protocol up time : 2003-01-28 11:19:00Description: Pos1/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec)Internet Address is 192.168.19.2/24Link layer protocol is nonstandard HDLCThe Vendor PN is FTRJ8519P1BNL-HWPort BW: 2.5G, Transceiver max BW: 1G, Transceiver Mode: MultiModeWaveLength: 850nm, Transmission Distance: 300mRx Power: -5.84dBm, Tx Power: -5.97dBmPhysical layer is Packet Over SDHScramble enabled, clock master, CRC-32, loopback: noneFlag J0 "NetEngine "Flag J1 "NetEngine "



6-5

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 16802934 path layer: B3 0 REI 66775Statistics last cleared:never Last 300 seconds input rate 72 bits/sec, 0 packets/sec Last 300 seconds output rate 24 bits/sec, 0 packets/sec Input: 1642 packets, 35940 bytes Input error: 0 shortpacket, 0 longpacket, 3 CRC, 0 lostpacket Output: 1475 packets, 24008 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets

6.3 Configuring an IP-Trunk InterfaceDescribes how to configure an IP-Trunk interface and the basic parameters of the interface.


6.3.2 Creating an IP-Trunk and adding POS Interfaces into the IP-Trunk

6.3.3 Configuring an IP Address for the IP-Trunk Interface

6.3.4 (Optional) Configuring the Lower Threshold of Up Links

6.3.5 (Optional) Configuring Load-balancing Mode for the IP-Trunk Interface

6.3.6 (Optional) Configuring Weights for Member Links

6.3.7 (Optional) Configuring the Method of Sending Trap Messages from an IP-Trunk MemberInterface



Applicable EnvironmentTo improve the communication ability of links, sometimes, multiple POS ports are bound to anIP-Trunk interface. The bandwidth of an IP-Trunk interface is the sum of bandwidth of all themember interfaces.

IP-Trunk interfaces can realize load balancing. Traffic to the same destination is transported ondifferent member links to avoid congestion.

In addition, IP-Trunk interfaces can improve link reliability. If a member port is Down, trafficis switched to other available ports.

Pre-configuration TasksNone

Data PreparationTo create an IP-Trunk interface, you need the following data.



Issue 03 (2010-03-31)

No. Data

1 IP-Trunk ID

2 IP address of the IP-Trunk interface

3 Lower threshold of Up links

4 Load balancing mode

5 Type and number of the backup port

6 Weight of the member port

6.3.2 Creating an IP-Trunk and adding POS Interfaces into the IP-Trunk


Procedure



Step 2 Run:interface ip-trunk trunk-id

The IP-Trunk interface is created.


The view of the POS interface to be added to the IP-Trunk is displayed.

Step 4 Run:shutdown

The interface is shut down.

Step 5 Run:link-protocol hdlc

The link-layer protocol of the interface is configured as High-level Data Link Control (HDLC).

Step 6 Run:ip-trunk trunk-id

The interface is added to the IP-Trunk.

When configuring an IP-Trunk interface, note the following points:



6-7

l The link layer protocol of the interfaces that are added into an IP-Trunk interface must beHDLC.

l By default, the link layer protocol of a POS interface is PPP. You need to run the link-protocol hdlc command in the POS interface view to change the link layer protocol to HDLC.

l Before adding an interface to an IP-Trunk, ensure the interface is not configured with anyLayer 3 feature or service.

l A POS interface can join only one IP-Trunk interface. To add the POS interface to anotherIP-Trunk interface, you must remove it from the original IP-Trunk first.

l Member interfaces of an IP-Trunk cannot be IP-Trunks.

l The POS interfaces of different interface boards can be added into the same IP-Trunk.

l Do not bind interfaces with different forwarding capabilities to an IP-Trunk.

l After interfaces with different forwarding capabilities are bound to an IP-Trunk, eachinterface assumes the least capability among all the interfaces. For example, after a 10 Gbit/s POS interface and a 2.5 Gbit/s POS interface are added into an IP-Trunk, the transmissioncapability of the 10 Gbit/s POS interface can only reach 2.5 Gbit/s. The transmissioncapability of the IP-Trunk is 5 Gbit/s rather than 12.5 Gbit/s.

l If an IP-Trunk is created on a local device, the peer device interfaces that are directlyconnected with the member interfaces must be bound to an IP-Trunk interface. Otherwise,the two ends cannot communicate.


The interface is enabled.

----End

6.3.3 Configuring an IP Address for the IP-Trunk Interface

Context

Do as follows on the routers that are configured with IP-Trunk interfaces.

Procedure




The IP-Trunk interface view is displayed.

Step 3 Run:ip address ip-address { mask | mask-length } [ sub ]

The IP address is configured for the IP-Trunk interface.

----End



Issue 03 (2010-03-31)

6.3.4 (Optional) Configuring the Lower Threshold of Up Links

ContextDo as follows on the routers configured with IP-Trunk interfaces.


system-view



The view of the IP-Trunk interface is displayed.

Step 3 Run:least active-linknumber link-number

The lower threshold of the member links in the Up state is configured.

By default, the lower threshold is 1. That is, an IP-Trunk remains Up as long as one memberinterface is Up.

NOTE

To ensure normal forwarding, it is recommended to configure the same lower threshold on the Trunkinterfaces at both ends of the same Trunk link.

----End

6.3.5 (Optional) Configuring Load-balancing Mode for the IP-Trunk Interface

ContextDo as follows on the routers configured with IP-Trunk interfaces.


system-view



The view of the IP-Trunk interface is displayed.

Step 3 Run:load-balance { ip | packet-all }

The load-balancing mode of the IP-Trunk interface is configured.

By default, load balancing is carried out among IP-Trunk member interfaces based on ip.



6-9

l Load balancing based on IP addresses can guarantee the packet order, but cannot improvethe bandwidth usage.

l Packet-by-packet load balancing can improve the bandwidth usage, but cannot guarantee thepacket order.

----End

6.3.6 (Optional) Configuring Weights for Member Links

Context

For an IP-Trunk interface, sum of weights of all its member interfaces cannot be greater than16. The IP-Trunk interface implements load balancing based on the weight of each memberinterface.

In an IP-Trunk interface, the larger the weight of a member interface is, the heavier the trafficon the member link is.

Do as follows on the routers configured with IP-Trunk interfaces.

Procedure




The view of the IP-Trunk member interface is displayed.

Step 3 Run:distribute-weight weight-value

The weight of the interface is configured.

By default, the weight of a member interface is 1.

NOTE

When an IP-Trunk bears multicast traffic, if you run the distribute-weight command to change the loadbalancing weight of a member interface, you need to run the shutdown and undo shutdown commandsto restart the member interface so that the configuration can take effect.

----End

6.3.7 (Optional) Configuring the Method of Sending Trap Messagesfrom an IP-Trunk Member Interface

Context

Do as follows on the device where IP-Trunk interfaces are created:



Issue 03 (2010-03-31)

Procedure



Step 2 Run:trunk-member trap in private-mib enable

An IP-Trunk member interface in the Up or Down state sends trap messages through the privateMIB.

By default, an IP-Trunk member interface in the Up or Down state sends trap messages throughthe public MIB.

The trap message sent through the public MIB does not carry information about the IP-Trunkinterface. If you want the trap message sent by an IP-Trunk member interface to carryinformation about the IP-Trunk interface, run the trunk-member trap in private-mib enablecommand.

----End


PrerequisiteThe configurations of an IP-Trunk Interface are complete.

Procedurel Run the display interface ip-trunk [ trunk-id ] [ | { begin | exclude | include } regular-

expression ] command to check the status of the IP-Trunk interface.l Run the display trunkmembership ip-trunk trunk-id [ slot slot-id ] command to check

information about the IP-Trunk member interface.l Run the display trunkfwdtbl ip-trunk trunk-id [ slot slot-id ] command to check the

forwarding table of the IP-Trunk interface.

----End

ExampleRun the display interface ip-trunk command. If the physical status, link protocol status, IPaddress, and load-balancing mode of the IP-Trunk interface are displayed, it means theconfiguration succeeds. For example:

<HUAWEI> display interface ip-trunk 1Ip-Trunk1 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-03, 17:45:06Description : HUAWEI, Quidway Series, Ip-Trunk1 InterfaceRoute Port,Hash arithmetic : According to IP,The Maximum Transmit Unit is 4470Internet Address is 10.2.1.1/19Link layer protocol is nonstandard HDLCPhysical is IP_TRUNKStatistics last cleared: 2008-08-02 15:32:27 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,



6-11

0 unicast,0 broadcast,0 multicast 0 errors,0 drops,0 unknownprotocol Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicast 0 errors,0 drops-----------------------------------------------------PortName Status Weight-----------------------------------------------------Pos1/0/0 UP 1-----------------------------------------------------The Number of Ports in Trunk : 1The Number of UP Ports in Trunk : 1

Run the display trunkmembership ip-trunk command. If the member interfaces, number ofmembers, and number of Up members are displayed, it means the configuration succeeds. Forexample:<HUAWEI> display trunkmembership ip-trunk 1Trunk ID: 1TYPE: posNumber Of Ports in Trunk = 2Number Of UP Ports in Trunk = 0operate status: downInterface Pos6/0/0, valid,selected,operate down,weight=1standby interface NULLInterface Pos6/0/1, valid,selected,operate down,weight=1standby interface NULL

Run the display trunkfwdtbl ip-trunk command. You can view the forwarding table of an IP-Trunk interface.<HUAWEI> display trunkfwdtbl ip-trunk 1 Show the Trunk Forwarding Table Ip-Trunk1's forwarding table is: MASTER SLAVEPos3/1/1 Pos3/1/0Pos3/1/0 Pos3/1/1Pos3/1/1 Pos3/1/0Pos3/1/1 Pos3/1/0Pos3/1/0 Pos3/1/1Pos3/1/1 Pos3/1/0Pos3/1/1 Pos3/1/0Pos3/1/0 Pos3/1/1Pos3/1/1 Pos3/1/0Pos3/1/1 Pos3/1/0Pos3/1/0 Pos3/1/1Pos3/1/1 Pos3/1/0Pos3/1/1 Pos3/1/0Pos3/1/0 Pos3/1/1Pos3/1/0 Pos3/1/1Pos3/1/1 Pos3/1/0

6.4 Maintaining HDLC and IP-Trunk ConfigurationDescribes how to maintain HDLC and IP-Trunk interfaces.

6.4.1 Clearing the statistics of the HDLC or IP-Trunk interfaces

6.4.2 Debugging HDLC



Issue 03 (2010-03-31)

6.4.1 Clearing the statistics of the HDLC or IP-Trunk interfaces

Context

CAUTIONThe previous statistics cannot be restored after you clear them. So, confirm the action beforeyou use the command.

To reset the interface statistics of the Network Management System (NMS) or that displayed byrunning the display interface command, run the following commands in the user view.

NOTE



the interface statistics displayed by running the display interface command.

l Run the reset counters if-mib interface [ interface-type [ interface-number ] ] commandto clear the interface statistics in the NMS.

----End

6.4.2 Debugging HDLC

Context

CAUTIONDebugging affects the performance of the system. So, after debugging, run the undo debuggingall command to disable it immediately.

When an HDLC fault occurs, run the following debugging commands in the user view to debugHDLC, view the debugging information, and locate and analyze the fault. For the procedure ofdisplaying the debugging information, refer to the "Information Center Configuration" in theHUAWEI NetEngine80E/40E Router Configuration Guide - System Management. For thedescription of debugging commands, refer to the HUAWEI NetEngine80E/40E RouterDebugging Reference.

NOTE

l If a debugging is enabled globally, running the same debugging command on the interface does nottake effect.

l If a debugging is disabled globally, running the same undo debugging command on the interface doesnot take effect.



6-13

Procedurel Run the debugging hdlc all command in the user view to enable all HDLC debugging.l Run the debugging hdlc event [ interface interface-type interface-number ] command in

the user view to enable HDLC event debugging.l Run the debugging hdlc { ip | ipv6 | isis | keepalive } { in | in-out | out } [ interface

interface-type interface-number ] command in the user view to enable HDLC packetdebugging.

----End

6.5 Configuration ExamplesProvides several configuration examples of HDLC.

6.5.1 Example for Configuring HDLC

6.5.2 Example for Configuring IP Address Unnumbered for HDLC

6.5.3 Example for Configuring an IP-Trunk

6.5.1 Example for Configuring HDLC


Router A and Router B are connected by POS interfaces, and the interfaces are required to runHDLC.

Figure 6-1 Networking diagram of the HDLC functions

RouterA RouterB

POS1/0/0100.1.1.1/24

POS1/0/0100.1.1.2/24



1. Configure the link protocol of each interface to HDLC.2. Configure the IP address of each interface.

Data Preparation

To configure DHCP, you need the following data:

l IP address of the interface on Router A

l IP address of the interface on Router B



Issue 03 (2010-03-31)

NOTE

The IP addresses of Router A and Router B must be in the same network segment, or the link layer cannotbe Up.

Procedure

Step 1 Configure Router A.<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] interface pos 1/0/0[RouterA-Pos1/0/0] link-protocol hdlc[RouterA-Pos1/0/0] ip address 100.1.1.1 24[RouterA-Pos1/0/0] undo shutdown[RouterA-Pos1/0/0] quit

Step 2 Configure Router B.<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] interface pos 1/0/0[RouterB-Pos1/0/0] link-protocol hdlc[RouterB-Pos1/0/0] ip address 100.1.1.2 24[RouterB-Pos1/0/0] undo shutdown[RouterB-Pos1/0/0] quit


After the configuration is completed, Router A and Router B can ping through each other.

Take Router A as an example.


Run the display ip routing-table command to check the correctness of the routing table.

[RouterA] display ip routing-tableRoute Flags: R - relied, D - download to fib------------------------------------------------------------------------------Routing Tables: Public Destinations : 4 Routes : 4Destination/Mask Proto Pre Cost Flags NextHop Interface 100.1.1.0/24 Direct 0 0 D 100.1.1.1 Pos1/0/0 100.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 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 InLoopBack0

----End


# sysname RouterA#interface Pos1/0/0



6-15

link-protocol hdlc undo shutdown ip address 100.1.1.1 255.255.255.0#return

l Configuration file of Router B# sysname RouterB#interface Pos1/0/0 link-protocol hdlc undo shutdown ip address 100.1.1.2 255.255.255.0#return

6.5.2 Example for Configuring IP Address Unnumbered for HDLC


Router A and Router B are connected through POS interfaces, and the interfaces are required torun HDLC.

POS 1/0/0 of Router A borrows the IP address of Loopback interface. The mask of Loopbackinterface is 32 bits.

Figure 6-2 Networking diagram of the HDLC basic function

Loopback1100.1.1.1/24

POS1/0/0POS1/0/0

100.1.1.2/24

RouterA RouterB



1. Configure the link protocol of each interface to HDLC.2. On Router A, configure the IP address of the loopback interface whose IP address is

unnumbered.3. Configure the POS interface on Router A to adopt the IP address unnumbered.4. Configure Router A to learn the opposite routing information through the static route.5. Configure the IP address of Router B.

Data Preparation

To configure the IP address unnumbered, you need the following data:



Issue 03 (2010-03-31)

l IP address of the loopback interface on Router A

l IP address of the POS interface on Router B

NOTE

These two IP addresses must be in the same network segment, or the link layer cannot be Up.

Procedure

Step 1 Configure Router A.<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] interface loopback1[RouterA-LoopBack1] ip address 100.1.1.1 32[RouterA-LoopBack1] quit[RouterA] interface pos 1/0/0[RouterA-Pos1/0/0] link-protocol hdlc[RouterA-Pos1/0/0] ip address unnumbered interface loopback1[RouterA-Pos1/0/0] undo shutdown[RouterA-Pos1/0/0] quit

Step 2 Configure Router B.<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] interface pos 1/0/0[RouterB-Pos1/0/0] link-protocol hdlc[RouterB-Pos1/0/0] ip address 100.1.1.2 24[RouterB-Pos1/0/0] undo shutdown[RouterB-Pos1/0/0] quit

Step 3 Configure the static routing on Router A.[RouterA] ip route-static 100.1.1.0 24 pos 1/0/0


After the configuration is completed, Router A and Router B can ping through each other.


[RouterA] ping 100.1.1.2 PING 100.1.1.2: 56 data bytes, press CTRL_C to break Reply from 100.1.1.2: bytes=56 Sequence=1 ttl=255 time=31 ms Reply from 100.1.1.2: bytes=56 Sequence=2 ttl=255 time=63 ms Reply from 100.1.1.2: bytes=56 Sequence=3 ttl=255 time=63 ms Reply from 100.1.1.2: bytes=56 Sequence=4 ttl=255 time=63 ms Reply from 100.1.1.2: bytes=56 Sequence=5 ttl=255 time=63 ms --- 100.1.1.2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 31/56/63 ms

Run the display ip routing-table command to check the correctness of the routing table.

[RouterA] display ip routing-tableRoute Flags: R - relied, D - download to fib------------------------------------------------------------------------------Routing Tables: Public Destinations : 4 Routes : 4Destination/Mask Proto Pre Cost Flags NextHop Interface 100.1.1.0/24 Static 60 0 D 100.1.1.1 Pos1/0/0 100.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 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 InLoopBack0

----End



6-17


# sysname RouterA#interface Pos1/0/0 link-protocol hdlc undo shutdown ip address unnumbered interface LoopBack1#interface LoopBack1 ip address 100.1.1.1 255.255.255.255# ip route-static 100.1.1.0 255.255.255.0 Pos1/0/0#return

l Configuration file of Router B# sysname RouterB#interface Pos1/0/0 link-protocol hdlc undo shutdown ip address 100.1.1.2 255.255.255.0#return

6.5.3 Example for Configuring an IP-Trunk

Networking RequirementsCreate an IP-Trunk between Router A and Router B.

Figure 6-3 Configuring an IP-Trunk

RouterA RouterB

POS1/0/0

POS2/0/0

POS1/0/0

POS2/0/0

IP-Trunk1100.1.1.1/24

IP-Trunk1100.1.1.2/24


1. Create an IP-Trunk interface.2. Add the POS interfaces to the IP-Trunk interface.


l Router A and Router B are connected through the POS interfaces.



Issue 03 (2010-03-31)

l IP address of the IP-Trunk interface at Router A

l IP address of the IP-Trunk interface at Router B

Procedure

Step 1 Configure Router A.<HUAWEI> system-view[HUAWEI] sysname RouterA

# Create IP-Trunk 1 and configure an IP address for it.

[RouterA] interface ip-trunk 1[RouterA-Ip-Trunk1] ip address 100.1.1.1 255.255.255.0[RouterA-Ip-Trunk1] undo shutdown[RouterA-Ip-Trunk1] quit

# Add POS 1/0/0 and POS 2/0/0 to IP-Trunk 1.

[RouterA] interface pos 1/0/0[RouterA-Pos1/0/0] link-protocol hdlc[RouterA-Pos1/0/0] ip-trunk 1[RouterA-Pos1/0/0] undo shutdown[RouterA-Pos1/0/0] quit[RouterA] interface pos 2/0/0[RouterA-Pos2/0/0] link-protocol hdlc[RouterA-Pos2/0/0] ip-trunk 1[RouterA-Pos2/0/0] undo shutdown[RouterA-Pos2/0/0] quit

Step 2 Configure Router B.<HUAWEI> system-view[HUAWEI] sysname RouterB

# Create IP-Trunk 1 and configure an IP address for it.

[RouterB] interface Ip-Trunk 1[RouterB-Ip-Trunk1] ip address 100.1.1.2 255.255.255.0[RouterB-Ip-Trunk1] undo shutdown[RouterB-Ip-Trunk1] quit

# Add POS 1/0/0 and POS 2/0/0 to IP-Trunk 1.

[RouterB] interface pos 1/0/0[RouterB-Pos1/0/0] link-protocol hdlc[RouterB-Pos1/0/0] ip-trunk 1[RouterB-Pos1/0/0] undo shutdown[RouterB-Pos1/0/0] quit[RouterB] interface pos 2/0/0[RouterB-Pos2/0/0] link-protocol hdlc[RouterB-Pos2/0/0] ip-trunk 1[RouterB-Pos2/0/0] undo shutdown[RouterB-Pos2/0/0] quit

Step 3 Check the configuration.

Run the display interface ip-trunk command on Router A or Router B, and you can find thatthe interface is Up.


[RouterA] display interface ip-trunk 1Ip-Trunk1 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-03, 17:45:06Description: Ip-Trunk1 InterfaceRoute Port,Hash arithmetic : According to flow,The Maximum Transmit Unit is 4470



6-19

Internet Address is 100.1.1.1/24Link layer protocol is nonstandard HDLCPhysical is IP_TRUNKStatistics last cleared: 2008-08-02 15:32:27 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, 0 unicast,0 broadcast,0 multicast 0 errors,0 drops,0 unknownprotocol Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicast 0 errors,0 drops-----------------------------------------------------PortName Status Weight-----------------------------------------------------Pos1/0/0 UP 1Pos2/0/0 UP 5-----------------------------------------------------The Number of Ports in Trunk : 2The Number of UP Ports in Trunk : 2

View information about the member port of the IP-Trunk interface on Router A.

[RouterA] display trunkmembership ip-trunk 1Trunk ID: 1TYPE: posNumber Of Ports in Trunk = 2Number Of UP Ports in Trunk = 2operate status: upInterface Pos1/0/0, valid, selected, operate up, weight=1,standby interface NULLInterface Pos2/0/0, valid, selected, operate up, weight=1,standby interface NULL

The IP-Trunk interface of Router A and that of Router B can ping each other successfully.

[RouterA] ping -a 100.1.1.1 100.1.1.2 PING 100.1.1.2: 56 data bytes, press CTRL_C to break Reply from 100.1.1.2: bytes=56 Sequence=1 ttl=255 time=62 ms Reply from 100.1.1.2: bytes=56 Sequence=2 ttl=255 time=62 ms Reply from 100.1.1.2: bytes=56 Sequence=3 ttl=255 time=62 ms Reply from 100.1.1.2: bytes=56 Sequence=4 ttl=255 time=62 ms Reply from 100.1.1.2: bytes=56 Sequence=5 ttl=255 time=62 ms --- 100.1.1.2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet lossround-trip min/avg/max = 62/62/62 ms

----End


# sysname RouterA#interface Ip-Trunk1 undo shutdown ip address 100.1.1.1 255.255.255.0#interface Pos1/0/0 link-protocol hdlc undo shutdown ip-trunk 1#interface Pos2/0/0 link-protocol hdlc



Issue 03 (2010-03-31)

undo shutdown ip-trunk 1#return

l Configuration file of Router B# sysname RouterB#interface Ip-Trunk1 undo shutdown ip address 100.1.1.2 255.255.255.0#interface Pos1/0/0 link-protocol hdlc undo shutdown ip-trunk 1#interface Pos2/0/0 link-protocol hdlc undo shutdown ip-trunk 1#return



6-21

7 ATM Configuration

About This Chapter

Describes Asynchronous Transfer Mode (ATM) broadband networking technologies andconfiguration steps for ATM interface, IMA groups, IPoA application, IPoEoA application,PPPoA application, PPPoEoA application, PVC service mapping, and service type of a PVC,OAM and VP, along with typical examples.

7.1 Introduction to ATMDescribes concepts and applications of ATM.

7.2 Configuring Parameters for an ATM OC-3/STM-1 Interface or an ATM OC-12/STM-4InterfaceThis section describes how to configure parameters for an ATM OC-3/STM-1 interface or anATM OC-12/STM-4 interface.

7.3 Configuring ATM Services on a Serial InterfaceThis section describes how to configure the ATM protocol on a serial interface, set the ATMinterface type, and create a PVC.

7.4 Configuring IMA GroupsDescribes how to configure an IMA group.

7.5 Configuring the IPoA ApplicationDescribes how to configure IPoA.

7.6 Configuring the Service Type and Optional Parameters of a PVCThis section describes how to configure service type and optional parameters of a PVC or PVP.

7.7 Configuring ATM OAMThis section describes how to configure the ATM OAM.

7.8 Maintaining ATM ConfigurationDescribes how to maintain ATM.

7.9 Configuration ExamplesProvides several configuration examples of ATM.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access 7 ATM Configuration


7-1

7.1 Introduction to ATMDescribes concepts and applications of ATM.

7.1.1 ATM Overview

7.1.2 Features of ATM Supported by the NE80E/40E

7.1.1 ATM OverviewAsynchronous Transfer Mode (ATM) is designated as the transmission and switching mode forbroadband ISDN services by the ITU-T in June, 1992. Due to its high flexibility and support tothe multi-media service, ATM is considered as the key to realizing broadband communications.

Defined by ITU-T, ATM implements transmission and switching of data based on cells. AnATM cell has a fixed length of 53 bytes. The first 5 bytes make up the cell header that containsthe cell routing and priority information. The remaining 48 bytes are used for payloads.

ATM is connection-oriented. Each virtual circuit (VC) is identified by a Virtual Path Identifier(VPI) and a Virtual Channel Identifier (VCI) together. One VPI/VCI value has local significanceon a segment of the link between ATM nodes. When a connection is released, the relevant VPI/VCI values are also released.

Broadband-Integrated Services Digital Network (ITU-T B-ISDN) I.610 defines the OAMfunction on the ATM network and classifies the OAM function into five layers.

The two types of operation flows are defined in the ATM layer: F4 and F5.l F4 flow is the OAM cell flow in the Virtual Path Connect (VPC) and provides the operation

management and maintenance of the VP layer.l F5 flow is the Virtual Channel Connect (VCC) and provides the operation management

and maintenance of the VC layer.

After the OAM is activated in the F4 and F5 flows, the specified OAM cells are inserted intothe user cells to occupy certain bandwidth and to be transmitted in the same physical channelwith the cells of the other users.

The F4 and F5 flows support four types of OAM cells: FM OAM cell, PM OAM cell, active/deactive OAM cell, and SM OAM cell.

On the ATM network, the three types of the OAM functional nodes are: end point, segment pointand middle point.The nodes having the different OAM attributes process the AIS/RDI cellsdifferently and indicate the information about the faults occurring in the ATM layer or thephysical layer to implement the fault management.

7.1.2 Features of ATM Supported by the NE80E/40E

NE80E/40E supports the ATM interface that carries ATM service over SONET/SDH.

These ATM interfaces supported by the NE80E/40E have the following features:

l Supports Permanent Virtual Circuit (PVC).

l Supports traffic shaping based on VP/VC.

l Supports User-to-Network Interface (UNI) signaling.

7 ATM ConfigurationHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access


Issue 03 (2010-03-31)

l Supports RFC1483: Multiprotocol Encapsulation over ATM Adaptation Layer 5.

l Supports RFC1577: Classical IP and ARP over ATM.

l Supports F5 End to End Loopback OAM.

l Supports AAL5 (ATM Adaptation Layer 5).

l Supports Non-real Time Variable Bit Rate (nrt_VBR).

l Supports Unspecified Bit Rate (UBR).

l Supports Real Time Variable Bit Rate (rt_VBR).

l Supports Constant Bit Rate(CBR)

The ATM interface supports PVCs and two applications namely, IPoA and IPoEoA.

The NE80E/40E supports the transparent transmission of ATM cells. For details, refer to thechapter "PWE3 Configuration" in the HUAWEI NetEngine80E/40E Router ConfigurationGuide - VPN. ATM has its QoS mechanism. For details, refer to the chapter "ATM QoSConfiguration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - QoS.

NE80E/40E supports the fault management function of OAM.

7.2 Configuring Parameters for an ATM OC-3/STM-1Interface or an ATM OC-12/STM-4 Interface

This section describes how to configure parameters for an ATM OC-3/STM-1 interface or anATM OC-12/STM-4 interface.


7.2.2 Configuring the Clock Mode

7.2.3 Configuring the Frame Format



7.2.6 Configuring the Scrambling

7.2.7 Configuring the Interval of Flow Statistics




In order to make the parameters of the ATM interface consistent well with physical network,you can configure the parameters according to the actual ATM network.

The parameters of the ATM interface mainly include the clock mode, frame format, scramblefunction, loopback mode, and interval of flow statistics. All these parameters have defaultconfigurations.



7-3

ATM sub-interface parameters such as the clock mode, frame format, scramble function,loopback mode, and interval of flow statistics cannot be configured. If those parameters areconfigured on the ATM main interface, the sub-interface inherits the parameters automatically.

The configured interval of flow statistics on the ATM main interface cannot be inherited to thesub interface, it needs to be configured independently on the sub interface.

When using an ATM interface to encapsulate the upper layer protocol, you need to configureits attributes.


Before configuring an ATM interface, complete the following task:


Data Preparation

To configure an ATM interface, you need the following data.

No. Data

1 Number of the ATM interface on the router

7.2.2 Configuring the Clock Mode

ContextNOTE

According to different functions, ATM devices and interfaces can be divided into Data Terminal Equipment(DTE) and Data Circuit-terminating Equipment (DCE).


Procedure



Step 2 Run:interface atm interface-number

The ATM interface view is displayed.


The clock mode is configured.

By default, the clock modes of ATM OC-3/STM-1 are master.



Issue 03 (2010-03-31)

l Master mode: indicates that the interface uses the internal clock signals.

l Slave mode: indicates that the interface uses the line clock signals.

When the ATM interface is used as a DTE device, use the slave clock mode. When the ATMinterface is used as a DCE device, use the master clock mode.

When the ATM interfaces of two routers are directly connected by optical fiber or WavelengthDivision Multiplexing (WDM) devices, do the following. One port should be configured to usethe master clock mode, and the other port should use the slave clock mode.

When the router is connected to the SDH/SONET device, use the slave clock mode.

----End

7.2.3 Configuring the Frame Format



system-view





The frame format is configured.

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 or . By default, SDH frame format isused.

----End


ContextThe SONET/SDH provides various overhead bytes to provide different levels of monitoringfunctions.

The signal label byte C2 belongs to the Higher-Order Path Overhead byte and is used to indicatethe multiplexing structure of the Virtual Container (VC) and the feature of the informationpayload.

The regenerator trace byte J0 belongs to the Section Overhead and is used to test the continuityof the connection between the two interfaces on the section layer.



7-5

The path trace byte J1 belongs to the Higher-Order VC-N path trace byte and is used to detectwhether the two interfaces are in the continuous connection status.


Procedure





Step 3 Perform the following as required:

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

The regenerator section trace byte J0 is configured.

l Run:flag j1 { 64byte-or-null-mode j1-value | 16byte-mode j1-value | 1byte-mode j1-value | peer }

The regenerator section trace byte J1 is configured.

NOTE

On the NE80E/40E, only the LPUF-10 ATM FPIC supports the 64byte-or-null-mode and peerparameters in the flag j0 and flag j1 commands.

l Run:flag c2 c2-value

The signal label byte C2 is configured.

The C2, J0, and J1 on the receiving and sending ends should be consistent. Otherwise, an alarmis generated.

For the ATM interface, by default, the value of C2 is 19 (13 in hex). The default value of J0 andJ1 is "NetEngine".

----End


Context

The MTU of the ATM interface is used for the assembly and fragmentation of IP packet inreceiving and sending packets on the interface.



Issue 03 (2010-03-31)

CAUTIONAfter changing the MTU of the interface by running the mtu command, restart the interface tovalidate the configuration by running the shutdown and undo shutdown commandsconsecutively.


Procedure





Step 3 Run:mtu mtu

The MTU of the interface is configured.

The default value is 1500 bytes.

Step 4 Run:shutdown

The ATM interface is disabled.


The ATM interface is enabled.

After changing the MTU of the interface by using the mtu command, you need to restart theinterface to validate the MTU.

----End

7.2.6 Configuring the Scrambling

ContextThe scrambling can effectively avoid continuous "0"s or "1"s in ATM cells.

When configuring the scrambling, ensure that the configurations at both ends are the same.


Procedure

Step 1 Run:



7-7

system-view




Step 3 Run:scramble

The scrambling is enabled.

By default, the scrambling is enabled. It is valid only for payloads and does not influence thecell header.

----End

7.2.7 Configuring the Interval of Flow Statistics

ContextNOTE

The NE80E/40E supports the flow and rate statistics based on the ATM interface and the ATM sub-interface. Before configuring the interval of rate statistics, you need to configure the PVC for the interfaceand the sub-interface, so that the configured statistics interval can be applied to the PVC


Procedure



Step 2 Perform the following as required:

l To enter the ATM interface view, run:interface atm interface-number

l To enter the ATM sub-interface view, run:interface atm interface-number.subinterface-number

Step 3 Run:set flow-stat interval interval-value

The period of the rate statistics is configured for the interface.

By default, the period of the rate statistics is 300 seconds.

The interval-value must be integral multiple times of 10.

----End



Issue 03 (2010-03-31)


Procedurel Run the display interface atm [ interface-number [.subinterface-number] ] [ | { begin |

exclude | include } regular-expression ] command to check the configuration and statusof the ATM interface.

l Run the display interface brief [ | { begin | include | exclude } regular-expression ]command to check the brief information about the ATM interface.

----End

ExampleRun the display interface atm command. If you can view the configuration information aboutthe ATM interface, including the enabled scramble, frame format, clock mode and the statisticsperiod, it means that the configuration succeeds.<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 SDHUBR: 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 you can view the physical status of the ATM interface, link protocol status, bandwidthutilization, and the number of the error packets, it means that the configuration succeeds. Forexample:



7-9

<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

7.3 Configuring ATM Services on a Serial InterfaceThis section describes how to configure the ATM protocol on a serial interface, set the ATMinterface type, and create a PVC.


7.3.2 Configuring the ATM Protocol on a Serial Interface

7.3.3 (Optional) Configuring the ATM Interface Type for a Serial Interface

7.3.4 Creating a PVC on a Serial Interface

7.3.5 Creating a PVP on a Serial Interface



Applicable EnvironmentTraditional ATM services can run only on ATM interfaces, which leads to high cost of ATMtransmission and very limited applications of ATM services.

By using the Time Division Multiplexing (TDM) technology, a CE1/CPOS interface enablesyou to choose different transmission channels according to bandwidth requirements to fullyutilize bandwidth resources. A CE1/CPOS interface can be channelized to multiplesynchronization serial interfaces. The CE1/CPOS interface, thus, can be configured withdifferent types of protocols, which decreases communication cost, increases configurationflexibility, and enables the CE1/CPOS interface to support various services.

Currently, the synchronization serial interfaces on the NE80E/40E can be configured wih theATM protocol and PVCs, and can be added to an IMA group.

NOTE

For how to add a serial interface to an IMA group, see Configuring an IMA Group in this chapter.

Pre-configuration TaskBefore configuring ATM services on a serial interface, complete the following tasks:



Issue 03 (2010-03-31)

l Configuring physical parameters for the CE1/CPOS interface to ensure that the physicallayer status of the interfaces is Up

l Channelizing the CE1/CPOS interface on the router to synchronization serial interfaces

NOTE

For configurations of a CE1/CPOS interface, refer to E-Carrier and T-Carrier InterfaceConfiguration and POS and CPOS Interface Configuration.

Data Preparation

To configure ATM services on a serial interface, you need the following data.

No. Data

1 Number of the synchronization serial interface

2 PVC name (optional) and VPI/VCI

7.3.2 Configuring the ATM Protocol on a Serial Interface

Context

After the link layer protocol of a serial interface is configured to ATM, the ATM status is Uponly when the physical status of the interface is Up.

A serial interface can be added to an IMA group only after the link layer protocol of this interfaceis configured to ATM.

By default, the link layer protocol of a serial interface is PPP.

Do as follows on the router:

Procedure





Step 3 Run:link-protocol atm

The ATM protocol is configured to be the link layer protocol on the serial interface.

----End



7-11

7.3.3 (Optional) Configuring the ATM Interface Type for a SerialInterface

ContextAfter the link layer protocol of a serial interface is configured to ATM, you can configure theATM interface type to User-to-Network Interface (UNI) or Network-to-Network Interface(NNI).

l If a device needs to work as a user side device, you need to set the ATM interface type ofthe interface connecting the peer device to UNI.

l If a device needs to work as a network side device, you need to set the ATM interface typeof the interface connecting the peer device to NNI.

By default, the ATM interface type on a serial interface is UNI.

NOTE

The ATM interface type on a serial interface can be configured only after the link layer protocol of theserial interface is set to ATM.

The VPI value range of the PVC/PVP on the serial sub-interface varies with the ATM interface type on aserial interface. For detailed information, refer to the PVC/PVP commands in the HUAWEI NetEngine80E/40E Router Command Reference.


Procedure





Step 3 Run:atm interface-type { uni | nni }

The type of the ATM interface is configured on the serial interface.

----End

7.3.4 Creating a PVC on a Serial Interface

ContextATM transmission can be implemented only after a PVC is created. PVCs support Point-to-Multipoint (P2MP) ATM transmission.

As for creating a PVC, note the following:

l A PVC can be created on a serial interface only after the link layer protocol of the interfaceis configured to ATM.



Issue 03 (2010-03-31)

l Currently, in the NE80E/40E, a PVC can be created on a serial sub-interface rather than aserial main interface.



system-view


Step 2 Run:interface serial interface-number.subinterface-number

The serial sub-interface is created and the sub-interface view is displayed. If the sub-interfacealready exists, the sub-interface view is displayed.

Step 3 Run:pvc vpi/vci

The PVC is created and the PVC view is displayed.

----End

7.3.5 Creating a PVP on a Serial Interface

ContextThe ATM VP monitoring function can be implemented only after a PVP is created.

As for creating a PVP, note the following:

l A PVP can be created on a serial interface only after the link layer protocol of the interfaceis configured to ATM.

l Currently, in the NE80E/40E, a PVP can be created only on a serial sub-interface ratherthan a serial main interface.



system-view


Step 2 Run:interface serial interface-number.subinterface-number

The serial sub-interface is created and the sub-interface view is displayed. If the sub-interfacealready exists, the sub-interface view is displayed.

Step 3 Run:pvp vpi

The PVP is created and the PVP view is displayed.

----End



7-13


PrerequisiteThe configurations of all ATM services on a serial interface are complete.

Procedurel Run the display interface serial interface-number [ | { begin | exclude | include } regular-

expression ] command to check the configurations on the serial interface.

l Run the display atm pvc-info [ interface serial interface-number [ pvc vpi/vci ] ] commandto check information about the PVC on the serial interface.

l Run the display atm pvp-info [ interface serial interface-number [ pvp vpi ] commandto check information about the PVP on the serial interface.

----End

Example

Run the display atm pvc-info command, and you can view information such as PVC status andinterface status.

<HUAWEI> display atm pvc-infoVPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE--------|-----|----------------|--------|-----|-----|-----------------------100/1 |DOWN | |0 |SNAP |None |Atm1/1/0.1 (DOWN) 1/1 |DOWN | |1 |SNAP |None |Atm1/1/1.1 (DOWN)VPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE--------|-----|----------------|--------|-----|-----|----------------------- 1/100 |DOWN | |65536 |None |None |Ima-group13/0/2.1 (DOWN) 0/1 |DOWN | |65537 |None |None |Serial13/0/3:4.1 (DOWN)

7.4 Configuring IMA GroupsDescribes how to configure an IMA group.


7.4.2 Creating an IMA Group

7.4.3 Setting the Number of the Cells Contained in an IMA Frame

7.4.4 Configuring Bandwidth for an IMA Group

7.4.5 Setting the Maximum Link Differential Delay for the IMA Group

7.4.6 Adding an Interface to an IMA Group

7.4.7 (Optional) Configuring the ATM Interface Type for an IMA Group

7.4.8 Creating a PVC for an IMA Group

7.4.9 Creating a PVP for an IMA Group




Issue 03 (2010-03-31)


Applicable EnvironmentWhen users want to access the ATM network at a rate between T1/E1 and T3/E3, using T3/E3is not cost-effective. Using multiple T1/E1 lines is a better solution that can be realized by IMA.

An IMA group is a logical link having one or more links. Its bandwidth is approximately equalto the sum of all the member links' bandwidth.

NOTE

IMA group interfaces do not support Layer 3 protocols.

Pre-configuration TasksBefore configuring an IMA group, complete the following task:

l Creating a synchronization serial interface channelized from CE1 or CPOS interfaces andconfiguring the ATM protocol on the serial interface if an IMA group needs to be configuredon the serial interface of the router

Data PreparationTo configure an IMA group, you need the following data.

No. Data

1 Number of the IMA group

2 Interface number of the IMA group

3 Bandwidth of the IMA group

7.4.2 Creating an IMA Group

ContextCreating an IMA group is the prerequisite to performing group-related configurations and addinginterfaces to the IMA group.


Procedure



Step 2 Run:interface ima-group interface-number



7-15

An IMA group is created and the IMA group interface view is displayed.

----End

7.4.3 Setting the Number of the Cells Contained in an IMA Frame

ContextBy default, the number of the cells contained in an IMA frame is 128.


Procedure




The IMA group interface view is displayed.

Step 3 Run:frame-length { 32 | 64 | 128 | 256 }

The number of the cells contained in an IMA frame is set.

----End

7.4.4 Configuring Bandwidth for an IMA Group

ContextThe bandwidth for an IMA group is determined by the minimum number of available memberlinks in the group. An IMA group can work only if the number of available member links islarger than or equal to the minimum number of available member links. The minimum numberof available member links cannot be larger than the total number of member links in an IMAgroup.

By default, the minimum number of available member links in an IMA group is 1. That is, anIMA group can work as long as one member link is available.


Procedure






Issue 03 (2010-03-31)


Step 3 Run:min-active-links number

The minimum number of available member links in the IMA group is set.

----End

7.4.5 Setting the Maximum Link Differential Delay for the IMAGroup

ContextBy default, the maximum differential delay of member links in an IMA group is 25 ms.


Procedure





Step 3 Run:differential-delay milliseconds

The maximum differential delay of member links in an IMA group is set, in milliseconds.

----End

7.4.6 Adding an Interface to an IMA Group

ContextSynchronization serial interfaces channelized from a CE1/CPOS interface can be added to anIMA group. As for adding an interface to an IMA group, note the following:

l An interface can be added to only one IMA group at one time.

l After an interface is added to an IMA group, the network layer configurations on theinterface do not take effect any more.

l The interface that joins an IMA group firstly can quit the group lastly.

As for adding a synchronization serial interface to an IMA group, besides the precedinginformation, note the following:

l A synchronization serial interface can be added to an IMA group only after the link layerprotocol of the interface is configured to ATM.



7-17

l After a synchronization serial interface is added to an IMA group, the link layer protocolof the interface can be changed only after the interface is removed from the group.

l After a synchronization serial interface is added to an IMA group, no sub-interfaces can becreated on the interface and the ATM interface type does not take effect any more. Youcan re-configure sub-interfaces and ATM interface type on the IMA group interface.

By default, no links are added to IMA groups, and each link can independently run variousservices.

NOTE

An interface can be added to an IMA group only after the group is created.


Procedure



Step 2 Run the following command as required:

l To enter the synchronization serial interface view, run the interface serialinterface-number command.

Step 3 Run:ima ima-group interface-number

The interface is added to the IMA group.

NOTE

The interface can be added only to one IMA group with the slot number and card number being the sameas those of the interface.

----End

7.4.7 (Optional) Configuring the ATM Interface Type for an IMAGroup

Context

After a serial interface is added to an IMA group, the ATM interface type of the serial interfacedoes not take effect any more. You can re-configure the ATM interface type on the IMA groupinterface.

l If a device needs to work as a user side device, you need to set the ATM interface type ofthe interface connecting the peer device to UNI.

l If a device needs to work as a network side device, you need to set the ATM interface typeof the interface connecting the peer device to NNI.

By default, the ATM interface type of an IMA group is UNI.



Issue 03 (2010-03-31)

NOTE

The VPI value range of the PVC/PVP on the IMA sub-interface varies with the ATM interface type of anIMA group. For detailed information, refer to pvc and pvp in the HUAWEI NetEngine80E/40E RouterCommand Reference.


Procedure





Step 3 Run:atm interface-type { uni | nni }

The ATM interface type is configured on the IMA group interface.

----End

7.4.8 Creating a PVC for an IMA Group

Context

ATM transmission can be implemented only after a PVC is created. PVCs support Point-to-Multipoint (P2MP) ATM transmission.

Currently, in the NE80E/40E, a PVC can be created on an IMA group sub-interface rather thanan IMA group interface.


Procedure



Step 2 Run:interface ima-group interface-number.subinterface-number

The IMA group sub-interface is created and the sub-interface view is displayed.

Step 3 Run:pvc vpi/vci


----End



7-19

7.4.9 Creating a PVP for an IMA Group

ContextThe ATM VP monitoring function can be implemented only after a PVP is created.

Currently, in the NE80E/40E, a PVP can be created on an IMA group sub-interface rather thanan IMA group interface.


Procedure



Step 2 Run:interface ima-group interface-number.subinterface-number

The IMA group sub-interface is created and the sub-interface view is displayed.

Step 3 Run:pvp vpi


----End


PrerequisiteThe configurations of the IMA groups are complete.

Procedurel Run the display interface [ atm | serial ] [ interface-number ] [ | { begin | exclude |

include } regular-expression ] [interface-type ] command to check the configuration andstatus of the ATM interface.

l Run the display interface brief [ | { begin | include | exclude } regular-expression ]command to check brief information about the IMA-Group interface and its memberinterfaces.

l Run the display interface ima-group [ group-number ] command to check configurationand status of the IMA group.

----End

ExampleAfter running the display interface brief [ | { begin | include | exclude } regular-expression ]command, you can view brief information about the physical status, link layer protocol status,bandwidth utilization, and number of incorrect packets of the IMA-Group interface and itsmember interfaces. The following is the display of the command:



Issue 03 (2010-03-31)

<HUAWEI> display interface brief | include Ima-group*down: administratively down^down: standby(l): loopback(s): spoofing(b): BFD down(d): DampeningSuppressedInUti/OutUti: input utility/output utilityInterface Physical Protocol InUti OutUti inErrors outErrorsIma-group1/0/0 UP UP 0.04% 0.04% 0 0

After running the display interface ima-group command, you can view the status of the IMA-Group interface and the number of VCs.

<HUAWEI> display interface ima-group 1/0/1Ima-group1/0/1 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-03, 17:24:24 Description: Ima-group1/0/1 InterfaceRoute Port,The Maximum Transmit Unit is 1500Internet Address is 21.161.163.2/24AAL enabled: AAL5, Maximum VCs: 128Current VCs: 1 (1 on main interface)Physical layer is ATM over IMAIMA-clock: CTC, differential-delay-maximum: 25, active-links-minimum: 1Frame-length: 128, symmetry: symmetrical configuration and operation IMA_GRP_NE_STATE OPERATIONAL IMA_GRP_FE_STATE OPERATIONAL IMA links: 1 ,First Link: 0 Link 0: Alarm: none Error: 0 FERR, 0 LCV, 0 CERR, 0 FEBE Defect: none F5 end-end loopback oam sends 0, F5 end-end loopback oam receives 0 my oam back 0, oam forward 0 oam send drops 0, oam forward drops 0Statistics last cleared: 2007-09-17 11:21:50 Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 1902 packets, 55496 bytes 0 errors, 0 CRC, 0 giants, 0 pads, 0 aborts, 0 overflows Output:1903 packets, 49760 bytes 0 errors, 0 underflows, 0 overflows

7.5 Configuring the IPoA ApplicationDescribes how to configure IPoA.


7.5.2 Configuring IPoA Mapping on a PVC




To make ATM bear IP packets, you need to create PVC first.

You can configure the IPoA application mapping on the PVC to make AAL5 bear IP packets.



7-21

Pre-configured Tasks

Before configuring IPoA applications, complete the following tasks:

l Configuring physical attributes for the ATM interface

l Configuring an IP address and mask for the ATM interface (or sub-interface)

Data Preparation

To configure the IPoA applications, you need the following data.

No. Data

1 Number of the ATM interface (or sub-interface)

2 IP address and mask of the ATM interface (or sub-interface)

3 PVC name, ATM network VPI and VCI

4 AAL5 encapsulation type

5 IP address and mask of the peer mapped to PVC

6 Interval of sending InARP packets

7.5.2 Configuring IPoA Mapping on a PVC

Procedure



Step 2 Run:interface atm interface-number[.subinterface ]

The ATM interface or the sub-interface view is displayed.

Step 3 Run:pvc { pvc-name [ vpi/vci ] | vpi/vci }

A PVC is created and the PVC view is displayed.

NOTE

l In normal cases, the VCI values 3 and 4 are reserved for special usage. You are recommended not touse these two values.

l The values of VPI and VCI cannot be 0 at the same time.

Step 4 Run:encapsulation aal5-encap

The encapsulation type of the PVC is configured as AAL5.



Issue 03 (2010-03-31)

The AAL5 encapsulation type for PVC can be aal5snap, aal5mux or aal5nlpid. By default, itis aal5snap.

NOTE

On the NE80E/40E, only the LPUF-10 FPIC supports the aal5nlpid encapsulation type.

InARP is not supported when aal5mux and aal5nlpid encapsulations are adopted.

To change the encapsulation type for PVC to aal5mux or aal5nlpid, delete InARP first.

Step 5 Run:map ip { ip-address | inarp [ minutes ] } [ broadcast ]

The IPoA mapping on the PVC is configured.

NOTE

IP addresses assigned to different ATM interfaces or ATM sub-interfaces on the local router cannot beidentical. Otherwise, packets cannot be forwarded.

When configuring the ip-address, if the specified address is the network segment address or themulticast address, the key word broadcast must be chosen.

When broadcast packets need to be processed on a PVC, the key word broadcast need to bespecified.

On one ATM interface, configure one PVC with InARP.

CAUTIONThe IP address specified by running the map ip command must be the IP address of the interfaceon the peer. Otherwise, data cannot be forwarded normally.

----End


PrerequisiteThe configurations of the IPoA application are complete.

Procedurel Run the display interface atm [ interface-number[.subinterface ] ] [ | { begin | exclude |

include } regular-expression ] command to check the configuration and status of the ATMinterface or sub-interface.

l Run the display atm pvc-info [ interface interface-type interface-number[.subinterface ][ pvc { pvc-name [ vpi/vci ] | vpi/vci } ] ] command to check information about the PVC.

l Run the display atm map-info [ interface interface-type interface-number[.subinterface ] [ pvc { pvc-name [ vpi/vci ] | vpi/vci } ] ] command to check informationabout the PVC mapping.

l Run the display atm { pvc | pvp } statistics interface atm interface-number [ pvc vpi/vci | pvp vpi ] command to check statistics about the PVC or PVP.



7-23

NOTERunning the display interface atm command displays the statistics of all the packets discarded onan interface. Running the display atm pvc statistics command displays only the statistics of thepackets discarded on the PVC or PVP due to congestion. Therefore, run the commands as required.

----End

ExampleRun the display interface atm command. If you can view information about the configurationand state of the ATM interface, it means that the configuration succeeds.<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 is 1500Internet protocol processing : disabledAAL enabled: AAL5, Maximum VCs: 2048VCs on main-interface: 1 (Total VCs: 1)VPs on main-interface: 0 (Total VPs: 0)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 SDHUBR: 1, CBR: 0, VBR: 0, USED BandWidth: 0KbpsVPI Max: 4095, VCI Max: 65535Scramble enabled, clock master, CRC-32, loopback: noneFlag: J0 "NetEngine "Flag: J1 "NetEngine "Flag: C2 19(0x13) SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1: 0 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 correct cell: 0 cells Receive idle cell: 0 cells Receive corrected cell: 0 cells Receive uncorrected cell: 0 cells Dropped receive cell: 0 cells Last dropped receive cell connection: 0/0 Last 30 seconds input rate: 0 bits/sec, 0 packets/sec Last 30 seconds output rate: 0 bits/sec, 0 packets/sec Input: 0 bytes, 0 packets Output: 0 bytes, 0 packets

Run the display atm pvc-info command. If you can view the status of the PVC and thecorresponding interface, it means that the configuration succeeds.<HUAWEI> display atm pvc-infoVPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE--------|-----|------------------|--------|-----|-----|----------------------- 0/40 |UP | |1 |SNAP |IP |Atm1/0/0 (UP)

Run the display atm map-info command. If you can view information about the PVC mapping,it means that the configuration succeeds.<HUAWEI> display atm map-infoAtm1/0/0, PVC 0/40, IP, State UP 10.0.0.1, vlink 65537



Issue 03 (2010-03-31)

Run the display atm pvc statistics command, you can view the statistics of the packets discardedon the PVC due to congestion.<HUAWEI> dispaly atm pvc statistics interface atm 1/0/0pvc 10/10: input drop pkts : 0, input drop rate 0 packets/secoutput drop pkts : 0, output drop rate 0 packets/secpvc 10/20: input drop pkts : 0, input drop rate 0 packets/secoutput drop pkts : 0, output drop rate 0 packets/sec

7.6 Configuring the Service Type and Optional Parametersof a PVC

This section describes how to configure service type and optional parameters of a PVC or PVP.


7.6.2 Configuring the Service Type of a PVC

7.6.3 Configuring the Service Type of a PVP

7.6.4 (Optional) Configure the Overload Bandwidth Value of an ATM Interface



Applicable EnvironmentIn the practical networking, to manage the traffic of PVC, you need to configure the service typeand the related parameters of a PVC.

Pre-configuration TasksBefore configuring the service types and optional parameters of a PVC, complete the followingtasks:


l Configuring an IP address and mask for the ATM interface or sub-interface

l Creating a PVC and configuring application modes

Data PreparationTo configure the service type and optional parameters of a PVC, you need the following data.

No. Data

1 Number of the ATM interface or sub-interface

2 IP address and mask of the ATM interface or sub-interface

3 PVC name, the network VPI and VCI

4 cbr: Peak rate of outputting ATM cells, variation range of cell delays



7-25

No. Data

5 nrt-vbr: Peak rate of outputting ATM cells, maintainable rate, variation range of celldelays and the maximum burst size

6 rt-vbr: Peak rate of outputting ATM cells, maintainable rate, variation range of celldelays and the maximum burst size

7 (Optional)overload bandwidth value of the ATM interface

7.6.2 Configuring the Service Type of a PVC

ContextWhen configuring the service type of PVC, you need to first create service type template in thesystem view and apply the service type to the concrete PVC.


Procedure



Step 2 Run:

atm service service-name {cbr output-pcr cdvt-value |nrt-vbr output-pcr output-scr output-mbs cdvt-value |rt-vbr output-pcr output-scr output-mbs cdvt-value | ubr output-pcr cdvt-value | ubr-plus output-mcr output-pcr output-mbs cdvt-value}

The service type template and rate parameters are created.

By default, the service type of PVP is UBR.

The service type can be configured as CBR, NRT-VBR, UBR, UBR-plus or RT-VBR.



Step 4 Run:pvc [ pvc-name ] vpi/vci


Step 5 Run:shutdown

The PVC is disabled.

Step 6 Run:service { output | input } service-name



Issue 03 (2010-03-31)

The service type of PVP is set.


The PVC is enabled.

----End

7.6.3 Configuring the Service Type of a PVP

ContextWhen configuring the service type of PVP, you need to first create the service type template inthe system view and apply the service type to the concrete PVP.


Procedure



Step 2 Run:

atm service service-name {cbr output-pcr cdvt-value |nrt-vbr output-pcr output-scr output-mbs cdvt-value |rt-vbr output-pcr output-scr output-mbs cdvt-value | ubr output-pcr cdvt-value | ubr-plus output-mcr output-pcr output-mbs cdvt-value}

The service type template and rate parameters are created.

By default, the service type of PVP is UBR.

The service type can be configured as CBR, NRT-VBR, UBR, UBR-plus or RT-VBR.

Step 3 Run:interface atm interface-number.subinterface


Step 4 Run:pvp vpi


The PVP is only supported to be configured in the ATM sub interface view.

Step 5 Run:shutdown

The PVP is shut down.

Step 6 Run:service { output | input } service-name

The service type of PVP is set.



7-27


The PVP is enabled.

----End

7.6.4 (Optional) Configure the Overload Bandwidth Value of anATM Interface

ContextNOTE

On the NE80E/40E, the LPUF-10 ATM FPIC does not support the configuration.


Procedure



Step 2 Run:interface atm interface-number [.subinterface ]

The ATM interface or the sub-interface view is displayed.

Step 3 Run:service bandwidth-overload peek-rate

The overload bandwidth value of the ATM interface is set.

Using the service bandwidth-overload command, you can set the overload bandwidth of thePVCs and PVPs of all services on the ATM interface.

----End


Procedurel Run the display interface atm [ interface-number [.subinterface ] ] [ | { begin | exclude |

include } regular-expression ] command to check the configuration and status of the ATM(sub) interface

l Run the display atm service [ service-name ] command to check the configuration of theservice type template.

l Run the display atm { pvc | pvp } statistics interface atm interface-number [ pvc vpi/vci | pvp vpi ] command to check the statistics of the PVC or PVP.



Issue 03 (2010-03-31)

NOTE

Running the display interface atm command displays the statistics of all the packets discarded onan interface. Running the display atm pvc statistics command displays only the statistics of thepackets discarded on the PVC or PVP due to congestion. Therefore, run the commands as required.

----End

ExampleRun the display interface atm command. If you can view information about the configurationand state of the ATM interface, it means that the configuration succeeds.

<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 is 1500Internet protocol processing : disabledAAL enabled: AAL5, Maximum VCs: 2048VCs on main-interface: 1 (Total VCs: 1)VPs on main-interface: 0 (Total VPs: 0)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 SDHUBR: 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: none line layer: none path layer: none SDH error: section layer: B1: 0 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/0 Last 30 seconds input rate: 0 bits/sec, 0 packets/sec Last 30 seconds output rate: 0 bits/sec, 0 packets/sec Input: 0 bytes, 0 packets Output: 0 bytes, 0 packets

Run the display atm service command. If you can view the configuration of the service typetemplate, it means that the configuration succeeds.

<HUAWEI> display atm serviceAtm Service Config: Service Name: aa State: VALID Index: 0 ServiceType: CBR PCR: 120 SCR: 0 MBS: 0 CDVT: 3



7-29

Traffic Type: Shaper

Run the display atm pvc statistics command. If you can view the statistics of the packetsdiscarded on the PVC due to congestion, it means that the configuration succeeds.<HUAWEI> dispaly atm pvc statistics interface atm 1/0/0pvc 10/0: input drop pkts : 0, input drop bytes : 0, input drop rate 0 bits/sec, 0 packets/secouput drop pkts : 0, ouput drop bytes : 0, output drop rate 0 bits/sec, 0 packets/secpvc 10/20: input drop pkts : 0, input drop bytes : 0, input drop rate 0 bits/sec, 0 packets/secouput drop pkts : 0, ouput drop bytes : 0, output drop rate 0 bits/sec, 0 packets/secTotal items : 2

7.7 Configuring ATM OAMThis section describes how to configure the ATM OAM.


7.7.2 (Optional) Activating the CC Function

7.7.3 (Optional) Configuring OAM End-to-End Loopback

7.7.4 (Optional) Configuring the Cell Loopback




OAM provides various methods of detecting and locating the faults of an ATM link. The OAMconfigurations are optional. Choose the configuration as required.

l To detect the link status and report faults in real time without interrupting services, activatethe CC function or configure the function of end-to-end loopback detection:

– The CC function detects the link status in real time by sending CC cells periodicallyand does not restrict the connection point attribute.

– The end-to-end loopback detection function detects the link status in real time bysending loopback cells periodically and is available on only the PVP/PVC of which theconnection point attribute is end-point.

Check whether the device supports CC cells or loopback cells and then chooseconfigurations according to the connection point attribute of the OAM.

The CC function and the loopback function cannot be configured on the same PVP/PVC.

l To locate and remove the faults of a link, configure the cell loopback.

l To debug and detect whether the ATM OAM mechanism works normally, inserting OAMcells manually.

l To response the OAM F5 loopback cells on the peer, configure the response of the OAMF5 loopback cells.



Issue 03 (2010-03-31)

Pre-configuration TasksBefore configuring ATM OAM, complete the following tasks:


l Configuring an IP address and mask for the ATM interface

l Configuring ATM PVC

Data PreparationTo configure ATM OAM, you need the following data.

No. Data

1 Number of the ATM interface or sub-interface

2 PVC name, the network VPI and VCI

3 Interval for sending loopback cells

4 Interval for sending OAM end-to-end Loopback cells

5 Number of delayed intervals for responding after the status of the PVP/PVC changes

7.7.2 (Optional) Activating the CC Function

ContextNOTE

On the NE80E/40E, only the LPUF-10 ATM FPIC supports the activation of the CC function.


Procedure



Step 2 Run:interface interface-type interface-number [.subinterface ]


Step 3 Run:oam

The OAM view is displayed.

Step 4 Run:attribute {start-vpi [ end-vpi ] | vpi/start-vci [ vpi/end-vci ] } { end-point | seg-point }



7-31

The OAM attributes of the connection point are configured.

When the following services are configured on a PVC, the PVC attribute can be configured onlyas end-point.

l IPoA or IPoEoA

l Transparent transmission of frames

l IWF

When the OAM attribute of the PVC is end-point, the PVC can respond to the OAM F5 loopbackcells.

Step 5 Run:cc { start-vpi [ end-vpi ] | vpi/start-vci [ vpi/end-vci ] } { end-to-end | segment } { both | sink | source }

The CC function is activated.

When activating the CC function of PVC, note the following points:

l Before activating the CC function, you need to complete the configurations of OAMattributes on the both ends.

l The type of the CC function and the OAM attributes must be consistent.

l During the recovery stage, you cannot cancel the CC function.

l Before deleting the OAM connection, if the board is not faulty, you must cancel the CCfunction first.

----End

7.7.3 (Optional) Configuring OAM End-to-End Loopback

ContextWhen configuring the function of OAM end-to-end loopback detection, note the following:l Set the attribute of the OAM connection point of the PVP/PVC to end-point.

l The CC function and the loopback function cannot be configured on the same PVP/PVC.

l During fault recovery, the undo oam-loopback command cannot be run.

l Before deleting OAM connections, run the undo oam-loopback command to disable thefunction of OAM end-to-end loopback detection if no faults occur on the board.


Procedure







Issue 03 (2010-03-31)

Step 3 Run:oam

The OAM interface view is displayed.

Step 4 Run:attribute {start-vpi [ end-vpi ] | vpi/start-vci [ vpi/end-vci ] } end-point

The attribute of the OAM connection point is set to end-point.

Step 5 Run:oam-loopback { start-vpi [ end-vpi ] | vpi/start-vci [ vpi/end-vci }end-to-end

The function of OAM end-to-end loopback detection of the PVP/PVC is enabled.

Step 6 (Optional) Run:oam-loopback { start-vpi [ end-vpi ] | vpi/start-vci [ vpi/end-vci }up-cycle cycle-number down-cycle cycle-number

The number of delayed intervals for responding after the change of the PVP/PVC status isconfigured.

By default, the number of delayed intervals for responding to the change of the PVP/PVC statusis 5.

After the function of OAM end-to-end loopback detection is enabled, when the PVP/PVC statuschanges, the system does not immediately respond to avoid PVP/PVC flapping. When the PVP/PVC keeps being Down or Up in consecutive delayed intervals of the specified number, thesystem responds to the change.

----End

7.7.4 (Optional) Configuring the Cell Loopback

ContextNOTE

On the NE80E/40E, only the LPUF-10 ATM FPIC supports the cell loopback function.


Procedure





Step 3 Run:oam

An OAM view is displayed.



7-33

Step 4 Run:attribute {start-vpi [ end-vpi ] | vpi/start-vci [ vpi/end-vci ] } { end-point | seg-point }

The OAM attributes of the connection point is configured.

When the following services are configured on a PVC, the PVC attribute can be configured onlyas end-point.

l IPoA or IPoEoA

l Transparent transmission of frames

l IWF

When the OAM attribute of the PVC is end-point, the PVC can respond to the OAM F5 loopbackcells.

Step 5 Run:loopback { vpi | vpi/vci } { end-loopback | seg-loopback } times

The cell loopback function is configured.

The OAM provides the loopback test function for the convenient fault location and test. Theloopback test refers to that the loopback cells is inserted in the VC/VP link of a certain connectionpoint and is looped back in another connection point. The system detects and locates the faultsof the link through the received loopback cells.

The loopback includes the following two types: segment loopback and end loopback.

l Before configuring the loopback of the segment point, you need to configure the end loopbackpoint as the segment point.

l Before configuring the loopback of the end point, you need to configure the end loopbackpoint as the end point.

l The loopback in one board fails.

----End


Procedurel Run the display atm oam statistics atm interface-number { vpi | vpi/vci } command to

check the statistics of the ATM OAM.l Run the display atm oam alarm-status atm interface-number [ vpi | vpi/vci ] command

to check the alarm status of the ATM OAM.l Run the display atm oam configuration atminterface-number [ vpi | vpi/vci ] command

to check the configuration of the ATM OAM.

----End

ExampleRun the display atm oam statistics,display atm oam alarm-status and display atm oamconfiguration commands. If you can view information about the alarm state, configuration, andstatistics of ATM OAM, it means that the configuration succeeds.

<HUAWEI> display atm oam statistics atm 3/0/1 10/10



Issue 03 (2010-03-31)

Total number of received OAM Cells : 0Number of received AIS Cells : 0Number of received RDI Cells : 0Number of received CC cells : 0Total number of sent OAM Cells : 44Number of sent AIS Cells : 0Number of sent RDI Cells : 44Number of sent CC cells : 0<HUAWEI> system-view[HUAWEI] interface atm 3/0/1[HUAWEI-Atm3/0/1] oam[HUAWEI-Atm3/0/1-fatm-oam] display atm oam alarm-status atm 3/0/1Interface PVC/PVP AIS state AIS type AIS reason RDI state RDI type--------- ----- --------- -------- ---------- --------- --------Atm3/0/1 10/10 RELEASE - - RELEASE -Current displayed item(s) is : 1[HUAWEI-Atm3/0/1-fatm-oam] display atm oam configuration atm 3/0/1Interface PVC/PVP Attribute CC func CC dir CC attr--------- ----- --------- ------- ------ -------Atm3/0/1 10/10 end-point disable - -Current displayed item(s) is : 1

7.8 Maintaining ATM ConfigurationDescribes how to maintain ATM.

7.8.1 Setting Loopback to Detect Whether an Interface Is Normal

7.8.2 Clearing the ATM Interface Statistics

7.8.3 Debugging ATM

7.8.1 Setting Loopback to Detect Whether an Interface Is Normal

Context

CAUTIONAfter you configure the self-loop (run the loopback command), the interface on a router or thelink cannot run normally. Thus, you must check whether to set the self-loop. After the detectionis complete, run the undo loopback command to disable the self-loop.

Do as follows on the device to be detected:

Procedure




The view of the interface to be detected is displayed.



7-35

Step 3 Run:loopback { local | remote }

The self-loop of the interface is enabled.

By default, the self-loop is disabled on the interface.

----End

7.8.2 Clearing the ATM Interface Statistics

Context

CAUTIONAll the statistics data cannot be restored after you clear it. Thus, confirm the action before youuse the command.

To reset the interface statistics of the Network Management System (NMS) or that displayed byrunning the display interface command, run the following commands in the user view.

NOTE


Procedure

Step 1 Run the reset counters interface [ atm [ interface-number ] ] command to clear the interfacestatistics displayed by running the display interface command.

Step 2 Run the reset counters if-mib interface [ atm [ interface-number ] ] command to clear theinterface statistics in the NMS.

Step 3 Run the reset atm interface [ atm interface-number ] command to clear the ATM interfacestatistics.

----End

7.8.3 Debugging ATM

Context

CAUTIONDebugging affects the system performance. So, after the debugging, run the undo debuggingall command to disable it immediately.

When ATM runs abnormally, run the debugging command in user view to debug the ATMinterface and locate the fault.



Issue 03 (2010-03-31)

For the procedure of outputting the debugging information, refer to the chapter "InformationCenter Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide -System Management. For the detailed debugging commands, refer to the HUAWEINetEngine80E/40E Router Debugging Reference.

Procedure

Step 1 Run the debugging atm error [ interface atm interface-number[.subinterface ] [ pvc { pvc-name [ vpi/vci ] | vpi/vci } ] ] command to enable ATM error debugging.

Step 2 Run the debugging atm event [ interface atm interface-number[.subinterface ] [ pvc { pvc-name [ vpi/vci ] | vpi/vci } ] ] command to enable ATM event debugging.

Step 3 Run the debugging atm packet [ interface atm interface-number[.subinterface ] [ pvc { pvc-name [ vpi/vci ] | vpi/vci } ] ] command to enable ATM packet debugging.

Step 4 Run the debugging atm all command to enable all ATM debugging.

----End

7.9 Configuration ExamplesProvides several configuration examples of ATM.

7.9.1 Example for Configuring IPoA

7.9.2 Example for Configuring ATM OAM

7.9.3 Example for Configuring IMAoPSNATM IMAoPSN enables the transmission of ATM cells of a 3G wireless bearer network in apacket-switched network (PSN) without the need of deploying an extra ATM network for 3Gservices.

7.9.1 Example for Configuring IPoA

Networking RequirementsIn Figure 7-1, Router A, Router B and Router C are connected to the ATM network. All thePVCs on ATM interfaces of the three routers employ IPoA application mode.



7-37

Figure 7-1 Networking diagram for IPoA configuration

ATMnetwork

RouterA

RouterB

RouterCIP:202.38.160.1/24

To B:0/40To C:0/41

Interface:ATM1/0/0

IP:202.38.160.3/24To A:0/41To B:0/42

Interface:ATM1/0/0

IP:202.38.160.2/24To A:0/40To C:0/42

Interface:ATM1/0/0


1. Create the PVC of ATM interfaces on each router.2. Specify the protocol to bear the IP protocol.

Data PreparationTo configure IPoA, you need the following data:

l IP addresses of their ATM interfaces of the three routers

l VPI/VCI of Router A connecting with Router B and Router C

l VPI/VCI of Router B connecting with Router A and Router C

l VPI/VCI of Router C connecting with Router A and Router B

ProcedureStep 1 Configure Router A.

# Enter the ATM interface view, and configure an IP address for it.<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] interface atm 1/0/0[RouterA-Atm1/0/0] ip address 202.38.160.1 255.255.255.0

# Establish PVC to bear IP.



Issue 03 (2010-03-31)

[RouterA-Atm1/0/0] pvc to_b 0/40[RouterA-atm-pvc-Atm1/0/0-0/40-to_b] map ip 202.38.160.2[RouterA-atm-pvc-Atm1/0/0-0/40-to_b] quit[RouterA-Atm1/0/0] pvc to_c 0/41[RouterA-atm-pvc-Atm1/0/0-0/41-to_c] map ip 202.38.160.3[RouterA-atm-pvc-Atm1/0/0-0/41-to_c] quit[RouterA-Atm1/0/0] undo shutdown


# Enter the ATM interface, and configure an IP address for it.

<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] interface atm 1/0/0[RouterB-Atm1/0/0] ip address 202.38.160.2 255.255.255.0


[RouterB-Atm1/0/0] pvc to_a 0/40[RouterB-atm-pvc-Atm1/0/0-0/40-to_a] map ip 202.38.160.1[RouterB-atm-pvc-Atm1/0/0-0/40-to_a] quit[RouterB-Atm1/0/0] pvc to_c 0/42[RouterB-atm-pvc-Atm1/0/0-0/42-to_c] map ip 202.38.160.3[RouterB-atm-pvc-Atm1/0/0-0/42-to_c] quit[RouterB-Atm1/0/0] undo shutdown

Step 3 Configure Router C.

# Enter the ATM interface view, and configure an IP address for it.

<HUAWEI> system-view[HUAWEI] sysname RouterC[RouterC] interface atm 1/0/0[RouterC-Atm1/0/0] ip address 202.38.160.3 255.255.255.0


[RouterC-Atm1/0/0] pvc to_a 0/41[RouterC-atm-pvc-Atm1/0/0-0/41-to_a] map ip 202.38.160.1[RouterC-atm-pvc-Atm1/0/0-0/41-to_a] quit[RouterC-Atm1/0/0] pvc to_b 0/42[RouterC-atm-pvc-Atm1/0/0-0/42-to_b] map ip 202.38.160.2[RouterC-atm-pvc-Atm1/0/0-0/42-to_b] quit[RouterC-Atm1/0/0] undo shutdown


# Check the PVC status information on Router A.

[RouterA] display atm pvc-infoVPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE--------|-----|--------------|--------|-----|-----|--------------------- 0/40 |UP |to_b |1 |SNAP |IP |Atm1/0/0 (UP) 0/41 |UP |to_c |2 |SNAP |IP |Atm1/0/0 (UP)

# Check the PVC mapping information on Router A.

[RouterA] display atm map-infoAtm1/0/0, PVC 0/40, IP, State UP 202.38.160.2, vlink 393217Atm1/0/0, PVC 0/41, IP, State UP 202.38.160.3, vlink 393218

Similarly, check the PVC status information and the PVC mapping information on Router B andRouter C.

# Router A can ping through Router B.

[RouterA] ping 202.38.160.2



7-39

PING 202.38.160.2: 56 data bytes, press CTRL_C to break Reply from 202.38.160.2: bytes=56 Sequence=1 ttl=255 time=62 ms Reply from 202.38.160.2: bytes=56 Sequence=2 ttl=255 time=31 ms Reply from 202.38.160.2: bytes=56 Sequence=3 ttl=255 time=31 ms Reply from 202.38.160.2: bytes=56 Sequence=4 ttl=255 time=31 ms Reply from 202.38.160.2: bytes=56 Sequence=5 ttl=255 time=31 ms --- 202.38.160.2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 31/37/62 ms

After performing similar operation, you observe the following:

l Router A can ping through Router C.l Router B can ping through Router A and Router C.l Router C can ping through Router A and Router B.

----End


# sysname RouterA#interface Atm1/0/0 undo shutdown ip address 202.38.160.1 255.255.255.0 pvc to_b 0/40 map ip 202.38.160.2 pvc to_c 0/41 map ip 202.38.160.3#return

l Configuration file of Router B# sysname RouterB#interface Atm1/0/0 undo shutdown ip address 202.38.160.2 255.255.255.0 pvc to_a 0/40 map ip 202.38.160.1 pvc to_c 0/42 map ip 202.38.160.3#return

l Configuration file of Router C# sysname RouterC#interface Atm1/0/0 undo shutdown ip address 202.38.160.3 255.255.255.0 pvc to_a 0/41 map ip 202.38.160.1 pvc to_b 0/42 map ip 202.38.160.2#return

7.9.2 Example for Configuring ATM OAM



Issue 03 (2010-03-31)


In Figure 7-2, Router A, Router B and Router C are connected to the ATM network. IPoAservices are configured in all the PVCs on ATM interfaces of the three routers.

To implement the real-time and continuous detection without interrupting services, you need toconfigure the OAM CC function.

Figure 7-2 Networking diagram for ATM OAM configuration

Router ARouter C

Router B

IP:202.38.160.1/24To B: 0/40To C:0/41

Interface:ATM 1/0/0IP:202.38.160.3/24

To A: 0/41To B:0/42

Interface:ATM 1/0/0

IP:202.38.160.2/24To A: 0/40To C:0/42

Interface:ATM 1/0/0ATM

Network



1. Configure IPoA services.

2. Configure the OAM attributes of the connection point.

3. Activate the CC function.

Data Preparation

To configure IPoA, you need the following data:

l The IP addresses of the ATM interfaces of the three routers

l In ATM network, the VPI/VCI of Router A connecting with Router B and Router Crespectively

l The VPI/VCI of Router B connecting with Router A and Router C respectively

l The VPI/VCI of Router C connecting with Router A and Router B respectively



7-41

Procedure

Step 1 Configure IPoA.

# Configure Router A.

<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] interface atm 1/0/0[RouterA-Atm1/0/0] ip address 202.38.160.1 255.255.255.0[RouterA-Atm1/0/0] pvc to_b 0/40[RouterA-atm-pvc-Atm1/0/0-0/40-to_b] map ip 202.38.160.2[RouterA-atm-pvc-Atm1/0/0-0/40-to_b] quit[RouterA-Atm1/0/0] pvc to_c 0/41[RouterA-atm-pvc-Atm1/0/0-0/41-to_c] map ip 202.38.160.3[RouterA-atm-pvc-Atm1/0/0-0/41-to_c] quit

# Configure Router B.

<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] interface atm 1/0/0[RouterB-Atm1/0/0] ip address 202.38.160.2 255.255.255.0[RouterB-Atm1/0/0] pvc to_a 0/40[RouterB-atm-pvc-Atm1/0/0-0/40-to_a] map ip 202.38.160.1[RouterB-atm-pvc-Atm1/0/0-0/40-to_a] quit[RouterB-Atm1/0/0] pvc to_c 0/42[RouterB-atm-pvc-Atm1/0/0-0/42-to_c] map ip 202.38.160.3[RouterB-atm-pvc-Atm1/0/0-0/42-to_c] quit

# Configure Router C.

<HUAWEI> system-view[HUAWEI] sysname RouterC[RouterC] interface atm 1/0/0[RouterC-Atm1/0/0] ip address 202.38.160.3 255.255.255.0[RouterC-Atm1/0/0] pvc to_a 0/41[RouterC-atm-pvc-Atm1/0/0-0/41-to_a] map ip 202.38.160.1[RouterC-atm-pvc-Atm1/0/0-0/41-to_a] quit[RouterC-Atm1/0/0] pvc to_b 0/42[RouterC-atm-pvc-Atm1/0/0-0/42-to_b] map ip 202.38.160.2[RouterC-atm-pvc-Atm1/0/0-0/42-to_b] quit

Step 2 Configure the OAM attributes of the connection point.


[RouterA] interface atm 1/0/0[RouterA-Atm1/0/0] oam[RouterA-Atm1/0/0-fatm-oam] attribute 0/40 0/41 end-point


[RouterB] interface atm 1/0/0[RouterB-Atm1/0/0] oam[RouterB-Atm1/0/0-fatm-oam] attribute 0/40 end-point[RouterB-Atm1/0/0-fatm-oam] attribute 0/42 end-point


[RouterC] interface atm 1/0/0[RouterC-Atm1/0/0] oam[RouterC-Atm1/0/0-fatm-oam] attribute 0/41 0/42 end-point

Step 3 Activate the CC function.


[RouterA] interface atm 1/0/0



Issue 03 (2010-03-31)

[RouterA-Atm1/0/0] oam[RouterA-Atm1/0/0-fatm-oam] cc 0/40 0/41 end-to-end both


[RouterB] interface atm 1/0/0[RouterB-Atm1/0/0] oam[RouterB-Atm1/0/0-fatm-oam] cc 0/40 end-to-end both[RouterB-Atm1/0/0-fatm-oam] cc 0/42 end-to-end both


[RouterC] interface atm 1/0/0[RouterC-Atm1/0/0] oam[RouterC-Atm1/0/0-fatm-oam] cc 0/41 0/42 end-to-end both


# Check information about the OAM configuration on the router.

Take the display on Router A as an example:

<RouterA> system-view[RouterA] interface atm 1/0/0[RouterA-Atm1/0/0] oam[RouterA-Atm3/0/1-fatm-oam] display atm oam configuration atm 1/0/0Interface PVC Attribute CC func CC dir CC attr--------- ----- --------- ------- ------ -------Atm1/0/0 0/40 end-point enable both end-to-endAtm1/0/0 0/41 end-point enable both end-to-endCurrent displayed item(s) is : 2

# Check the OAM statistics on the PVC.

Take the display on Router A as an example:

<RouterA> display atm oam statistics atm 1/0/0 0/40Total number of received OAM Cells : 0Number of received AIS Cells : 0Number of received RDI Cells : 0Number of received loopback cells : 0Number of received CC cells : 0Number of received crc error cells : 0Number of received other cells : 0Total number of sent OAM Cells : 88Number of sent AIS Cells : 0Number of sent RDI Cells : 44Number of sent loopback cells : 0Number of sent CC cells : 44

----End


# sysname RouterA#interface Atm1/0/0 ip address 202.38.160.1 255.255.255.0 pvc to_b 0/40 map ip 202.38.160.2 pvc to_c 0/41 map ip 202.38.160.3 oam attribute 0/40 0/41 end-point cc 0/40 0/41 end-to-end both#



7-43

returnl Configuration file of Router B

# sysname RouterB#interface Atm1/0/0 ip address 202.38.160.2 255.255.255.0 pvc to_a 0/40 map ip 202.38.160.1 pvc to_c 0/42 map ip 202.38.160.3oam attribute 0/40 end-point attribute 0/42 end-point cc 0/40 end-to-end both cc 0/42 end-to-end both#return

l Configuration file of Router C# sysname RouterC#interface Atm1/0/0 ip address 202.38.160.3 255.255.255.0 pvc to_a 0/41 map ip 202.38.160.1 pvc to_b 0/42 map ip 202.38.160.2oam attribute 0/41 0/42 end-point cc 0/41 0/42 end-to-end both#return

7.9.3 Example for Configuring IMAoPSNATM IMAoPSN enables the transmission of ATM cells of a 3G wireless bearer network in apacket-switched network (PSN) without the need of deploying an extra ATM network for 3Gservices.

Networking RequirementsThe bearer protocol for services between a NodeB and an RNC defined by UMTS R99/R4 isATM. But the actual situation of an operator is that between the majority of its NodeBs andRNCs, no ready ATM network is available. By deploying the ATM IMAoPSN service, anoperator can achieve transparent transmission of ATM cells through PWE3 tunnels in the PSN.

The traditional solution is transparently transmitting some E1s of a NodeB to the RNC directlythrough a pure TDM SDH network. This method cannot achieve multiplexing of bandwidthresources, and requires a large number of E1 interfaces on the RNC. The traditional solutionrequires enormous construction and maintenance cost. With ATM IMAoPSN, the PE router atthe side of NodeB uses the E1 IMA interface to dynamically allocate bandwidth resources andtransparently transports PWE3 ATM cells after the E1 IMA termination. In this way, bandwidthresources can be multiplexed. After ATM STM-1s (or other high-speed links) are deployed onrouters at the RNC side, RNCs and routers at the RNC side no longer need a larger number ofE1 interfaces. In this way, construction and maintenance cost is reduced.

As shown in Figure 7-3, it is required that NodeB and PE1 should be connected through multipleE1 links On PE1, add the multiple E1 links to an IMA group. Configure a VC on an interfaceof the IMA group. The RNC and PE2 are connected through the ATM interface. Configure a



Issue 03 (2010-03-31)

VC on the ATM interface. Then, a PW is set up between PE1 and PE2 to transparently transmitATM cells.

Figure 7-3 Networking diagram of IMAoPSN configurations

PE1 PE2P

NodeB

RNC2×IMA E1 ATM3/0/1

GE2/0/0GE1/0/0 GE2/0/0

GE2/0/0

STM-1

E12/0/1

E12/0/2

PWE3 ATM TransparentCell Transport

Router Interface IP Address

PE1 GE2/0/0

Loopback0

10.1.1.1/24

192.2.2.2/32

P GE1/0/0

GE2/0/0

Loopback0

10.1.1.2/24

10.2.1.1/24

192.4.4.4/32

PE2 GE2/0/0

Loopback0

10.2.1.2/24

192.3.3.3/32


1. Run the IGP protocol on the backbone network so that devices can communicate with eachother.

2. Configure basic MPLS functions on the backbone network, and configure MPLS L2VPNfunctions on PE devices. Establish the remote MPLS LDP peer relationship between PEsat both ends of the PW.

3. Set parameters for the serial interface.4. Configure the PW template.5. Establish MPLS L2VC connections on PEs.


l Identical L2VC IDs at both ends of the PW



7-45

l MPLS LSR IDs of the PEs and P router

l IP address of the remote peer of the PE

l Coding mode and frame format of the E1/CE1 interface

l IMA group number and IMA interface number

Procedure

Step 1 Run the IGP protocol on the backbone network so that devices can communicate with each other.For detailed configurations, see the following configuration.

Step 2 Configure basic MPLS functions on the backbone network, and configure MPLS L2VPNfunctions on PE devices. Then, establish the remote MPLS LDP peer relationship between PEsat both ends of the PW. For detailed configurations, see the following configuration:

The remote MPLS LDP peer relationship is required only for the dynamic PW.

Step 3 Set parameters for the serial interface on PE1 and then add the serial interface to the IMA group.Set parameters for the ATM interface on PE2.

1. Configure PE1.# Configure the channelized mode, AMI code, and no-CRC4 frames for CE1 2/0/1 andCE1 2/0/2 on PE1.[PE1] controller e1 2/0/1[PE1-E1 2/0/1] using ce1[PE1-E1 2/0/1] code ami[PE1-E1 2/0/1] channel-set 1 timeslot-list 1-15[PE1] controller e1 2/0/2[PE1-E1 2/0/2] using ce1[PE1-E1 2/0/2] code ami[PE1-E1 2/0/2] channel-set 1 timeslot-list 16-30[PE1-E1 2/0/2] quit

# Create an IMA interface and configure the interface with transparent transmission.[PE1] interface ima-group 2/0/1[PE1-Ima-group2/0/1] atm cell transfer[PE1-Ima-group2/0/1] quit

# Add the channelized serial interface to the IMA group.[PE1] interface serial2/0/1:1[PE1-Serial2/0/1:1] link-protocol atm[PE1-Serial2/0/1:1] ima ima-group 2/0/1[PE1-Serial2/0/1:1] quit[PE1] interface serial2/0/2:1[PE1-Serial2/0/2:1] link-protocol atm[PE1-Serial2/0/2:1] ima ima-group 2/0/1[PE1-Serial2/0/2:1] quit

2. Configure PE2.[PE2] interface atm 3/0/1[PE2-Atm3/0/1] atm cell transfer[PE2-Atm3/0/1] quit

Step 4 Configuring the PW.

1. Configure PE1.[PE1] pw-template 1to3[PE1-pw-template-1to3] peer-address 192.3.3.3[PE1-pw-template-1to3] atm-pack-overtime 1000[PE1-pw-template-1to3] quit[PE1] interface ima-group 2/0/1[PE1-Ima-group2/0/1] mpls l2vc pw-template 1to3 100



Issue 03 (2010-03-31)

[PE1-Ima-group2/0/1] undo shutdown[PE1-Ima-group2/0/1] quit

2. Configure PE2.[PE2] pw-template 3to1[PE2-pw-template-3to1] peer-address 192.2.2.2[PE2-pw-template-3to1] quit[PE2] interface atm 3/0/1[PE2-Atm3/0/1] mpls l2vc pw-template 3to1 100[PE2-Atm3/0/1] undo shutdown[PE2-Atm3/0/1] quit


Run the display mpls l2vc command on PEs. You can view that the status of the PW is Up.

# The display on PE1 is as follows:<PE1> display mpls l2vc interface ima-group 2/0/1*Client Interface : Ima-group 2/0/1 is up Session State : up AC State : up VC State : up VC ID : 7 VC Type : ATM transparent cell destination : 192.3.3.3 local group ID : 0 remote group ID : 0 local VC label : 146433 remote VC label : 21504 max ATM cells : 28 ATM pack overtime : 1000 seq-number : disable local AC OAM State : up local PSN State : up local forwarding state : forwarding local status code : 0x0 remote AC OAM state : up remote PSN state : up remote forwarding state: forwarding remote statuscode : 0x0 BFD for PW : unavailable manual fault : not set active state : active forwarding entry : not exist link state : up local ATM cells : 28 remote ATM cells : 28 local VCCV : cw alert lsp-ping bfd remote VCCV : none local control word : enable remote control word : enable tunnel policy name : -- traffic behavior name : -- PW template name : -- primary or secondary : primary VC tunnel/token info : 0 tunnels/tokens create time : 0 days, 0 hours, 0 minutes, 21 seconds up time : 0 days, 0 hours, 0 minutes, 0 seconds last change time : 0 days, 0 hours, 0 minutes, 21 seconds VC last up time : 0000/00/00 00:00:00 VC total up time : 0 days, 0 hours, 0 minutes, 0 seconds CKey : 11 NKey : 10

# The display on PE2 is as follows:<PE2> display mpls l2vc interface atm 3/0/1*client interface : Atm3/0/1 is upsession state : upAC state : upVC state : up



7-47

VC ID : 101 VC type : ATM transparent cell destination : 192.2.2.2 local group ID : 0 remote group ID : 0 local VC label : 140289 remote VC label : 140289 local AC OAM State : up local PSN State : up local forwarding state : forwarding local status code : 0x0 remote AC OAM state : up remote PSN state : up remote forwarding state: forwarding remote statuscode : 0x0 BFD for PW : unavailable manual fault : not set active state : active forwarding entry : exist link state : up local ATM cells : 1 remote ATM cells : 1 local VCCV : cw alert lsp-ping bfd remote VCCV : cw alert lsp-ping bfd local control word : enable remote control word : enable tunnel policy : -- traffic behavior : -- PW template name : -- primary or secondary : primary VC tunnel/token info : 1 tunnels/tokens NO.0 TNL type : lsp , TNL ID : 0x208000 create time : 0 days, 0 hours, 16 minutes, 54 seconds up time : 0 days, 0 hours, 16 minutes, 54 seconds last change time : 0 days, 0 hours, 16 minutes, 54 seconds VC last up time : 2008/07/24 12:31:31 VC total up time : 0 days, 2 hours, 12 minutes, 51 seconds CKey : 11 NKey : 10

----End

Configuration Filesl Configuration file of PE1:

# sysname PE1# mpls lsr-id 192.2.2.2 mpls# mpls l2vpn#pw-template 1to3 peer-address 192.3.3.3 atm-pack-overtime 1000#mpls ldp# mpls ldp remote-peer 192.3.3.3 remote-ip 192.3.3.3 #controller e1 2/0/1using ce1code amichannel-set 1 timeslot-list 1-15undo shutdown#controller e1 2/0/2using ce1code ami



Issue 03 (2010-03-31)

channel-set 1 timeslot-list 16-30undo shutdown#interface serial2/0/1:1link-protocol atmima ima-group 2/0/1undo shutdown#interface serial2/0/2:1link-protocol atmima ima-group 2/0/1undo shutdown#interface ima-group 2/0/1 atm cell transfer mpls l2vc pw-template 1to3 100#interface GigabitEthernet2/0/0 undo shutdown ip address 10.1.1.1 255.255.255.0 mpls mpls ldp#interface LoopBack0 ip address 192.2.2.2 255.255.255.255#ospf 1area 0.0.0.0 network 192.2.2.2 0.0.0.0 network 10.1.1.0 0.0.0.255#return

l Configuration file of PE2:# sysname PE2# mpls lsr-id 192.3.3.3 mpls# mpls l2vpn#pw-template 3to1 peer-address 192.2.2.2 atm-pack-overtime 1000#mpls ldp# mpls ldp remote-peer 192.2.2.2 remote-ip 192.2.2.2#interface GigabitEthernet2/0/0 undo shutdown ip address 10.2.2.2 255.255.255.0 mpls mpls ldp#interface Atm3/0/1undo shutdownatm cell transfermpls l2vc pw-template 3to1 100#interface LoopBack0 ip address 192.3.3.3 255.255.255.255#ospf 1 area 0.0.0.0 network 192.3.3.3 0.0.0.0network 10.2.2.0 0.0.0.255



7-49

#return

l Configuration file of the P router:# sysname P# mpls lsr-id 192.4.4.4 mpls#mpls ldp#interface GigabitEthernet1/0/0 undo shutdown ip address 10.1.1.2 255.255.255.0 mpls mpls ldp#interface GigabitEthernet2/0/0 undo shutdown ip address 10.2.2.1 255.255.255.0 mpls mpls ldp#interface LoopBack0 ip address 192.4.4.4 255.255.255.255#ospf 1 area 0.0.0.0 network 192.4.4.4 0.0.0.0 network 10.1.1.0 0.0.0.255 network 10.2.2.0 0.0.0.255#return



Issue 03 (2010-03-31)

8 1483B Configuration

About This Chapter

This chapter describes 1483B technologies and configuration steps for IPoEoA application,along with typical examples.

8.1 Introduction of 1483BIntroduction of 1483B

8.2 Configuring IPoEoA ServicesThis section describes how to configure IPoEoA services by using an ATM network.

8.3 Configuration ExamplesThis section provides several configuration examples of IPoEoA.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access 8 1483B Configuration


8-1

8.1 Introduction of 1483BIntroduction of 1483B

8.1.1 1483B Overview

8.1.1 1483B Overview

RFC 1483 defines the standards of transmitting multi-protocol data unit on an ATM network inthe following manners:

l The 1483 Bridged: It is applied to the bridged protocol data unit.

l The 1483 Routing: It is applied to the routing protocol data unit.

RFC 1483 Bridged encapsulates the data packet of the network layer in the data link layer. Itimitates the bridge function of the Ethernet network, so that the terminal devices at the user sideand the bridge devices at the network side are connected.

Figure 8-1 shows the stack protocol of 1483B.

Figure 8-1 Stack protocol of 1483B

ATM Network

Router AAccess Router

TCP/UDP

IP

Ethernet

TCP/UDP

IP

Ethernet

1438B

AAL5

ATM

The IPoE Ethernet stack protocol is used to connect the device at the users' side. After 1483Bis configured on the entry Router A on the ATM network, Router A can implement the bridgeof Ethernet packets to the ATM cells. This enables Router A to transparently transmit thereceived IPoE packets on the ATM network.

IPoEoA is the main application of 1483B supported by the NE80E/40E. IPoEoA indicates thatAAL5 carries Ethernet packets, and the Ethernet carries IP packets to implement the layer 2

8 1483B ConfigurationHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access


Issue 03 (2010-03-31)

forwarding of IPoEoA packets between the Ethernet and PVC. IPoEoA converges the ATMbackbone network and the IP network. It also supports Ethernet protocols and IP protocols.

8.2 Configuring IPoEoA ServicesThis section describes how to configure IPoEoA services by using an ATM network.


8.2.2 Creating a VE Interface

8.2.3 Configuring IPoEoA Application Mapping on a PVC

8.2.4 Configuring Services on the VE Interface



Applicable EnvironmentsThe NE80E/40E support the VE interface as the gateway of IPoEoA.

The core task of configuring IPoEoA on the NE80E/40E is to configure the mapping betweenPVC and the VE interface on the incoming interface of the ATM network. This is done to ensurethat the IPoEoA packets can be transmitted transparently on the ATM network.

Pre-configured TasksBefore configuring IPoEoA services, complete the following task:

l Configuring parameters of the ATM interface connecting the router and ATM switch orthat connecting the router and the peer device

Data PreparationTo configure IPoEoA services, you need the following data.

No. Data

1 Number of the VE interface

2 Number of the ATM interface

3 VPI/VCI value of PVC

8.2.2 Creating a VE Interface




8-3

Procedure



Step 2 Run:interface virtual-ethernet interface-number

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

----End

8.2.3 Configuring IPoEoA Application Mapping on a PVC


Procedure





Step 3 Run:pvc { pvc [ vpi/vci ] | vpi/vci }

A PVC is created and the PVC interface view is displayed.

Step 4 Run:encapsulation aal5-encap

The AAL5 encapsulation protocol type of PVC is configured.

The AAL5 encapsulation type for PVC can be aal5snap, aal5mux or aal5nlpid. By default, theencapsulation type is aal5snap.

NOTE

On the NE80E/40E, only the LPUF-10 ATM FPIC supports the aal5nlpid encapsulation type.

NOTE

Only aal5snap encapsulation supports InARP. InARP cannot be configured when aal5mux oraal5nlpid is adopted.To change the AAL5 encapsulation type of PVC to aal5mux or aal5nlpid, InARP must be deleted first ifit has been configured.

Step 5 Run:map bridge virtual-ethernet interface-number

The application mapping from PVC to VE interface is configured.



Issue 03 (2010-03-31)

PVC and the VE interface which it is mapped to must on the same interface board, that is,numbers of the interface boards must be the same.

When configuring the IPoEoA application mapping, ensure that there is no other mapping onthe PVC. When configuring other mappings, ensure that there is no IPoEoA configuration onthe PVC.

----End

8.2.4 Configuring Services on the VE Interface

The method for configuring VE interfaces is the same as that for configuring common Ethernetinterfaces.

VE interfaces support the routing mode and switching mode and support the switchover betweenrouting and switching modes.

You can configure IP address and routing protocols for routing VE interfaces and add a switchingVE interface to the default VLAN. For the VE interface added to the VLAN, all PVCs mappedto the VE are in the same VLAN.


Procedurel Run the display interface atm interface-number command to check the statistic

information and status of the ATM interface.l Run the display atm pvc-info [ interface atm interface-number pvc [ vpi/vci ] ] command

to check the related information about PVC.l Run the display atm map-info command to check the mapping between PVC and the peer

address.l Run the display interface virtual-ethernet [ interface-number ] [ | { begin | exclude |

include } regular-expression ] command to check the statistic information and status ofthe VE interface.

----End

ExampleRun the display interface atm command. If you can view the information of the ATM interface,it means that the configuration succeeds.

<HUAWEI> display atm 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 1500 bytesInternet Address is 21.1.1.1/24AAL 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



8-5

UBR: 4, 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: none line layer: none path layer: none SDH error: section layer: B1: 356 line layer: B2: 0 M1: 0 path layer: B3: 143 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/0 Last 30 seconds input rate: 2872 bits/sec, 0 Packets/sec Last 30 seconds output rate: 3024 bits/sec, 0 Packets/sec Input: 91929764 Bytes, 96982 Packets Output: 110681532 Bytes, 250553 Packets

Run the display atm pvc-info command. If you can view the PVC status and the interface status,it means that the configuration succeeds.

<HUAWEI> display atm pvc-infoVPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE--------|-----|----------------|--------|-----|-----|----------------------- 0/40 |UP |1 |1 |SNAP |None |Atm8/0/0.1 (UP)

Run the display atm map-info command. If you can view the mapping between the PVC andthe peer address, it means that the configuration succeeds.

<HUAWEI> display atm map-infoAtm1/0/0, PVC 1/33, IP, State UP100.11.1.1, vlink 1Atm1/0/0, PVC 2/101, ETH, Virtual-Ethernet1/1/1, UP

Run the display interface virtual-ethernet command. If you can view the statistic informationand status of the virtual ethernet interface, it means that the configuration succeeds.

<HUAWEI> display interface virtual-ethernet 1/0/0Virtual-Ethernet1/0/0 current state : UPLine protocol current state : DOWNDescription : Virtual-Ethernet1/0/0 InterfaceRoute Port, The Maximum Transmit Unit is 1500Internet protocol processing : disabledIP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc7a-9e15Carrier Layer: 1 PVC total, 1 map up, 0 map down 5 minutes input rate 0 bytes/sec, 0 packets/sec 5 minutes output rate 0 bytes/sec, 0 packets/sec 0 packets input, 0 bytes, 0 drops 0 packets output, 0 bytes, 0 drops

8.3 Configuration ExamplesThis section provides several configuration examples of IPoEoA.

8.3.1 Example for Configuring a Routing VE Interface to Work as an IPoEoA Gateway

8.3.2 Example for Configuring ATM Bridged Ethernet



Issue 03 (2010-03-31)

8.3.3 Example for Configuring a VLANIF Interface to Work as an IPoEoA Gateway

8.3.1 Example for Configuring a Routing VE Interface to Work asan IPoEoA Gateway

Networking Requirments

As shown in Figure 8-2, each host in two Ethernets accesses the ATM network through anADSL router and communicates with the router through DSLAM. The hosts in the Ethernet arerequired to access the Internet network directly through the ADSL method.

The detailed networking conditions are as follows:

l IP address of VE of the Router C is 202.38.160.1.

l VPI/VCI values of two PVCs connecting Router C and DSLAM are 0/60 and 0/61, whichbelong to ADSL Router A and ADSL Router B respectively.

Figure 8-2 Networking diagram of IPoEoA configuration

Workstation

Workstation

Workstation

Server

Server

ADSLRouter A

ADSLRouter B

DSLAM

Router C

Eth

erne

tE

ther

net TO ADSL Router A:0/60

TO ADSL Router B:0/61Interface:Virtual-ethernet1/0/0

IP:202.38.160.1



1. Create a VE interface.

2. Configure an IP address for the VE interface.

3. Create a PVC and enter the PVC view.

4. Create the IPoEoA mapping on PVC.



8-7

Data Preparation


l IP address of the VE interface

l VPI/VCI value of PVC

Procedure


# Create a VE interface and configure an IP address for it.

<RouterC> system-view[RouterC] interface virtual-ethernet 1/0/0[RouterC-Virtual-Ethernet1/0/0] ip address 202.38.160.1 255.255.255.0[RouterC-Virtual-Ethernet1/0/0] quit

# Create a PVC and specify it to carry the IPoEoA protocol.

[RouterC] interface atm 1/0/0[RouterC-Atm1/0/0] pvc to_adsl_a 0/60[RouterC-atm-pvc-Atm1/0/0-0/60-to_adsl_a] map bridge virtual-ethernet 1/0/0[RouterC-atm-pvc-Atm1/0/0-0/60-to_adsl_a] quit[RouterC-Atm1/0/0] pvc to_adsl_b 0/61[RouterC-atm-pvc-Atm1/0/0-0/61-to_adsl_b] map bridge virtual-ethernet 1/0/0[RouterC-atm-pvc-Atm1/0/0-0/61-to_adsl_b] quit[RouterC-Atm1/0/0] undo shutdown


# Check the PVC status information on Router C.

[RouterC] display atm pvc-infoVPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE--------|-----|----------------|--------|-----|-----|--------------------- 0/60 |UP |to_adsl_a |60 |SNAP |ETH |Atm1/0/0 (UP) 0/61 |UP |to_adsl_b |61 |SNAP |ETH |Atm1/0/0 (UP)

The PCs connected Router A and the PCs connected Router B can ping through the VE interfaceson Router C.

----End

Configuration Files

Configuration file of RouterC

#Sysname RouterC#interface Atm1/0/0 pvc to_adsl_a 0/60 map bridge Virtual-Ethernet1/0/0 # pvc to_adsl_b 0/61 map bridge Virtual-Ethernet1/0/0 ##interface Virtual-Ethernet1/0/0 ip address 202.38.160.1 255.255.255.0#return



Issue 03 (2010-03-31)

8.3.2 Example for Configuring ATM Bridged Ethernet


As shown in Figure 8-3, Router A and Router B are in the ATM network. The Ethernets of anenterprise are located in two places and transparently transmit Ethernet packets through the ATMinterface of the router connecting them.

The organization has two departments, with the VLAN IDs being 10 and 20 respectively. TheATM bridge function is configured on the routers so that users using the same VLAN ID indifferent locations feel that they are in the same LAN.

Figure 8-3 Networking diagram of ATM bridged Ethernet

VLAN 10 VLAN 10

VLAN 20VLAN 20

Ethernet3/0/1

Ethernet3/0/2

Router AEthernet3/0/1

Ethernet3/0/2

Router B

ATM1/0/0 ATM1/0/0

PVC 100/1

ATM

PVC 100/2



1. Create a VLAN.

2. Add Ethernet interfaces to the VLAN.

3. Create a VE interface.

4. Add the VE to the VLAN.

5. Create a PVC and enter the PVC view.

6. Create the IPoEoA mapping on PVC.

Data Preparation


l Number of the interface added to the VLAN

l VLAN ID to be accessed to the ATM network

l VPI/VCI value of PVC that transparently transmit layer 2 packets



8-9

ProcedureStep 1 Configurations of Router A and Router B are the same, as follows:

# Create a VLAN.

[HUAWEI] vlan 10[HUAWEI-vlan10] quit[HUAWEI] vlan 20[HUAWEI-vlan20] quit

# Switch the interface to the layer 2 mode and configure the default VLAN.

[HUAWEI] interface Ethernet3/0/1[HUAWEI-Ethernet3/0/1] portswitch[HUAWEI-Ethernet3/0/1] port default vlan 10[HUAWEI-Ethernet3/0/1] quit[HUAWEI] interface Ethernet3/0/2[HUAWEI-Ethernet3/0/2] portswitch[HUAWEI-Ethernet3/0/2] port default vlan 20[HUAWEI-Ethernet3/0/2] quit

# Create a VE interface and configure the default VLAN.

[HUAWEI] interface Virtual-Ethernet1/0/0[HUAWEI-Virtual-Ethernet1/0/0] portswitch[HUAWEI-Virtual-Ethernet1/0/0] port default vlan 10[HUAWEI-Virtual-Ethernet1/0/0] quit[HUAWEI] interface Virtual-Ethernet1/0/1[HUAWEI-Virtual-Ethernet1/0/1] portswitch[HUAWEI-Virtual-Ethernet1/0/1] port default vlan 20[HUAWEI-Virtual-Ethernet1/0/0] quit

# Create a PVC and configure the IPoEoA service mapping.

[HUAWEI] interface Atm1/0/0[HUAWEI-Atm1/0/0] undo shutdown[HUAWEI-Atm1/0/0] pvc 100/1[HUAWEI-atm-pvc-Atm1/0/0-100/1-1] encapsulation aal5snap[HUAWEI-atm-pvc-Atm1/0/0-100/1-1] map bridge Virtual-Ethernet1/0/0[HUAWEI-atm-pvc-Atm1/0/0-100/1-1] quit[HUAWEI-Atm1/0/0] pvc 100/2[HUAWEI-atm-pvc-Atm1/0/0-100/2-2] encapsulation aal5snap[HUAWEI-atm-pvc-Atm1/0/0-100/2-2] map bridge Virtual-Ethernet1/0/1[HUAWEI-atm-pvc-Atm1/0/0-100/2-2] quit[HUAWEI-Atm1/0/0] quit


# View the pvc status information on Router A and Router B.

[HUAWEI] display atm pvc-infoVPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE--------|-----|----------------|--------|-----|-----|-----------------------100/1 |UP | |0 |SNAP |ETH |Atm1/0/0 (UP) 100/2 |UP | |0 |SNAP |ETH |Atm1/0/0 (UP)

The PCs connected Router A and PC s connected Router B can ping through each other.

----End

Configuration FilesConfiguration files of Router A and Router B

#Sysname HUAWEI#



Issue 03 (2010-03-31)

interface Ethernet3/0/1portswitch port default vlan 10#interface Ethernet3/0/2portswitch port default vlan 20#interface Atm1/0/0 pvc 100/1 map bridge Virtual-Ethernet1/0/0 # pvc 100/2 map bridge Virtual-Ethernet1/0/1 ##interface Virtual-Ethernet1/0/0 portswitch port default vlan 10#interface Virtual-Ethernet1/0/1 portswitch port default vlan 20#return

8.3.3 Example for Configuring a VLANIF Interface to Work as anIPoEoA Gateway

Networking RequirementsAs shown in Figure 8-4, each host in two Ethernets accesses the ATM network through anADSL router and communicates with the router through DSLAM. The hosts in the Ethernet arerequired to access the Internet directly through the ADSL to manage the users in the Ethernetson Router C.

The detailed networking conditions are as follows:

l The VE interface of Router C is added to VLAN 100.

l IP address of VLANIF 100 is 202.38.160.1.

l VPI/VCI values of two PVCs connecting the router and DSLAM are 0/60 and 0/61, whichbelong to ADSL Router A and ADSL Router B respectively.



8-11

Figure 8-4 Networking diagram of IPoEoA configuration

Workstation

Workstation

Workstation

Server

Server

ADSLRouter A

ADSLRouter B

DSLAM

Router C

Eth

erne

tE

ther

net TO ADSL Router A:0/60

TO ADSL Router B:0/61Interface:Virtual-ethernet1/0/0

IP:202.38.160.1


1. Create VLAN 100.2. Create a VLANIF interface.3. Configure an IP address for the interface.4. Create a VE interface.5. Add the VE to the VLAN.6. Create a PVC and enter PVC view.7. Create the IPoEoA mapping on PVC.


l IP address of the VLANIF interface

l VPI/VCI value of PVC

Procedure


# Create VLAN 100 and VLANIF 100.

<RouterC> system-view[RouterC] vlan 100[RouterC-vlan100] quit[RouterC] interface vlanif 100[RouterC-vlanif100] ip address 202.38.160.1 24[RouterC-vlanif100] quit



Issue 03 (2010-03-31)

# Create a VE interface and add it to VLAN 100.

[RouterC] interface virtual-ethernet 1/0/0[RouterC-Virtual-Ethernet1/0/0] portswitch[RouterC-Virtual-Ethernet1/0/0] port default vlan 100[RouterC-Virtual-Ethernet1/0/0] quit

# Create a PVC and specify it to carry the IPoEoA protocol.

[RouterC] interface atm 1/0/0[RouterC-atm1/0/0] pvc to_adsl_a 0/60[RouterC-atm-pvc-atm1/0/0-0/60-to_adsl_a] map bridge virtual-ethernet1/0/0[RouterC-atm-pvc-atm1/0/0-0/60-to_adsl_a] quit[RouterC-atm1/0/0] pvc to_adsl_b 0/61[RouterC-atm-pvc-atm1/0/0-0/61-to_adsl_b] map bridge virtual-ethernet1/0/0[RouterC-atm-pvc-atm1/0/0-0/61-to_adsl_b] quit[RouterC-atm1/0/0] quit


# View the pvc status information on Router C.

[HUAWEI] display atm pvc-infoVPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE--------|-----|----------------|--------|-----|-----|------------- 0/60 |UP |to_adsl_a |60 |SNAP |ETH |Atm1/0/0 (UP) 0/61 |UP |to_adsl_b |61 |SNAP |ETH |Atm1/0/0 (UP)

The PCs connected Router A and the PCs connected Router B can ping through the VE interfaceson Router C.

----End

Configuraion FilesConfiguration file of Router C

#Sysname RouterC# vlan batch 100#interface Vlanif100 ip address 202.38.160.1 255.255.255.0#interface Atm1/0/0 pvc to_adsl_a 0/60 map bridge Virtual-Ethernet1/0/0 # pvc to_adsl_b 0/61 map bridge Virtual-Ethernet1/0/0 ##interface Virtual-Ethernet1/0/0 portswitch port default vlan 100#return



8-13

A Glossary

Collates frequently used glossaries in this document.

A

ATM Asynchronous Transfer Mode (ATM). A data transmissiontechnology in which data is transferred at high data rates in fixedlength, 53 bytes.

Authentication An act that decides whether a user can be awarded with access rightor what kinds of users can access a network.

Authorization An act that accredits a user with access to certain services.

AUX Auxiliary interface that provides an EIA/TIA-232 DTE interface.By using the AUX interface and the Modem, a user can access anetwork through dialup.

C

Callback A call mode in which both ends of the communication participatein the call. One end is called the Client, while the other end is callerthe Server. The Client initiates a call, and the Server decideswhether to callback or not. If a callback is needed, the Server tearsdown the connection and then initiates a call to the Client.

Called Number Number of the called party.

Calling Number Number of the calling party.

P

POS A MAN and LAN technology that provides a point to pointconnection. The POS interface is based on SONET.

S

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access A Glossary


A-1

SONET Synchronous Optical Network (SONET). A standard forsynchronous data transfer over optical networks. The standardcontains a series of transmission speed, including SDH TransportModule (STM) -1 (155Mbit/s), STM-4c (622 Mbit/s) andSTM-16c/STM-16 (2.5 Gbit/s).

W

WAN Wide Area Network. A network that covers a large geographicarea.

A GlossaryHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access

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

Issue 03 (2010-03-31)

B Acronyms and Abbreviations

Collates frequently used acronyms and abbreviations in this document.

A

AA Anonymous Access

AAA Authentication, Authorization and Accounting

AAL ATM Adaptation Layer

AAL1 ATM Adaptation Layer Type 1




ACL Access Control List

ADSL Asymmetric Digital Subscriber Line

AMI Alternate Mark Inversion

ANSI American National Standard Institute

ARP Address Resolution Protocol

ATM Asynchronous Transfer Mode

AU Administrative Unit

AUG Administrative Unit Group

AUX Auxiliary (port)

B

BAS Broadband Access Server

BRI Basic Rate Interface

HUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access B Acronyms and Abbreviations


B-1

C

CAR Committed Access Rate

CBR Constant Bit Rate

CCITT International Telegraph and Telephone Consultative Committee

CD Carrier Detect

CDV Cell Delay Variation

CHAP Challenge Handshake Authentication Protocol

CPE Customer Premises Equipment

CPOS Channelized-POS

CSMA Carrier Sense Multiple Access

CUG Closed User Group

D

DCC Data Communication Channel

DCD Data Carrier Detected

DCE Data Circuit-terminating Equipment

DDN Digital Data Network

DHCP Dynamic Host Configuration Protocol

DLCI Data Link Control Identifier

DLSw Data Link Switching

DNS Domain Name System

DSL Digital Subscriber Line

DSLAM DSL Access Multiplexer

DTE Data Terminal Equipment

E

EIA Electronics Industry Association

ESF Extended Service Frame

ETSI European Telecommunications Standards Institute

F

FCS Frame Check Sequence

B Acronyms and AbbreviationsHUAWEI NetEngine80E/40E RouterConfiguration Guide - WAN Access

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

Issue 03 (2010-03-31)

FDDI Fiber Distributed Digital Interface

FE Fast Ethernet

FIFO First In First Out

FR Frame Relay

FRF Frame Relay Forum

FRMR Frame Rejection

FS Forced Switch

FTP File Transfer Protocol

G

GE Gigabit Ethernet

GPRS General Packet Radio Service

GRE Generic Routing Encapsulation

H

HDB3 High Density Bipolar of Order 3

HDLC High level Data Link Control

HDSL High-bit-rate Digital Subscriber Link

HFC Hybrid Fiber-Coaxial

HIC Highest Incoming-only Channel

HOC Highest Outgoing-only Channel

HTTP Hyper Text Transport Protocol

I

IAD Integrated Access Device

IBGP Internal BGP

ID IDentification

IEEE Institute of Electrical and Electronics Engineers

IETF Internet Engineering Task Force

IF Information Frame

IGMP Internet Group Management Protocol

IP Internet Protocol



B-3

IPC Inter-Process Communication

IPCP IP Control Protocol

IPHC IP Header compression

IPoA Internet Protocols over ATM

IPoE IP over Ethernet

IPoEoA IP over Ethernet over AAL5

ISDN Integrated Services Digital Network

ISO International Organization for Standardization

ISP Internet Service Provider

ITU-T International Telecommunication Union - TelecommunicationStandardization Sector

L

L2TP Layer 2 Tunneling Protocol

LAN Local Area Network

LAPB Link Access Procedure, Balanced

LCP Link Control Protocol

LFI Link Fragmentation and Interleaving

LIC Lowest Incoming-only Channel

LOC Loss of continuity

LQR Link Quality Reports

LTC Lowest Two-way Channel

M

MAP Mobile Application Part

MD5 Message Digest 5

MFR Multiple Frame Relay

MIB Management Information Base

MP Multilink PPP

MTU Maximum Transmission Unit

N

NAT Network Address Translation



Issue 03 (2010-03-31)

NBMA Non Broadcast Multiple Access

NCP Network Control Protocol

NE NetEngine

NNI Network Node Interface

NT Network Terminal

O

OAM Operation, Administration and Maintenance

OC-3 OC-3

OSI Open System Interconnection

OSPF Open Shortest Path First

P

PAP Password Authentication Protocol

PC Personal Computer

PCI Protocol Control Information

PCM Pulse-Code Modulation

POH Path Overhead

POS Packet Over SDH/SONET

PPP Point-to-Point Protocol

PRI Primary Rate Interface

PSE Packet Switching Exchange

PSTN Public Switched Telephone Network

PVC Permanent Virtual Circuit

Q

QoS Quality of Service

R

RADIUS Remote Authentication Dial in User Service

RAS Remote Access Server

RFC Request for Comments



B-5

RIP Routing Information Protocol

RSOH Regenerator Section Overhead

RSU Routing Switch Unit

RTP Real-time Transport Protocol

RTU Remote Test Unit

S

SDH Synchronous Digital Hierarchy

SDLC Synchronous Data Link Control

SDSL Symmetrical Digital Subscriber Line

SF Signal Failure

SGSN Serving GPRS Support Node

SLIP Serial Line Internet Protocol

SNA Systems Network Architecture

SNMP Simple Network Management Protocol

SNP Sequence Number PDUs

SOH Section Overhead

SONET Synchronous Optical Network

SP Service Provider

STM-1 SDH Transport Module -1

SVC Switched Virtual Channel

T

TACACS Terminal Access Controller Access Control System

TCP Transmission Control Protocol

TFTP Trivial File Transfer Protocol

TU Tributary Unit

TUG Tributary Unit Group

U

UBR Unspecified Bit Rate

UDP User Datagram Protocol



Issue 03 (2010-03-31)

UNI User Network Interface

UP User Plane

V

VBR Variable Bit Rate

VC Virtual Circuit

VCI Virtual Channel Identifier

VLAN Virtual Local Area Network

VP Virtual Path

VPI Virtual Path Identifier

VPLS Virtual Private LAN Service

VPN Virtual Private Network

VRP Versatile Routing Platform

W

WWW World Wide Web



B-7

huawei configuration guide - wan access(v600r001c00_03)

Documents