NE40E&80E V600R008C10 Configuration Guide - WAN Access 01 PDF

HUAWEI NetEngine80E/40E Router
V600R008C10
Configuration Guide - WAN Access
Issue 02
Date 2014-09-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2014-09-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Configuration Guide - WAN Access About This Document
About This Document
Purpose
This document systematically describes WAN access protocols and configurations supported
by the NE80E/40E . The main contents cover common WAN interfaces, the basic knowledge
of WAN access protocols, configurations of common WAN access protocols and various
configuration examples. This manual also provides a common glossary, acronyms and
abbreviations in WAN access protocols.
Reading this manual helps users systematically master interface types, protocols of common
WAN access, and configurations.
NOTICE
Note the following precautions:
l The encryption algorithms DES/3DES/SKIPJACK/RC2/RSA (RSA-1024 or lower)/MD2/
MD4/MD5 (in digital signature scenarios and password encryption)/SHA1 (in digital
signature scenarios) have a low security, which may bring security risks. If protocols allowed,
using more secure encryption algorithms, such as AES/RSA (RSA-2048 or higher)/SHA2/
HMAC-SHA2, is recommended.
l If the plain parameter is specified, the password will be saved in plaintext in the configuration
file, which has a high security risk. Therefore, specifying the cipher parameter is
recommended. To further improve device security, periodically change the password.
l Do not set both the start and end characters of a password to "%$%$." This causes the
password to be displayed directly in the configuration file.
Related Versions
The following table lists the product versions related to this document.
Issue 02 (2014-09-30) Huawei Proprietary and Confidential ii

Product Name Version
HUAWEI NetEngine80E/40E V600R008C10

Router
Intended Audience
This document is intended for:
l Commissioning Engineer
l Data Configuration Engineer
l Network Monitoring Engineer
l System Maintenance Engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.

avoided, may result in minor or moderate injury.

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and

tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
Issue 02 (2014-09-30) Huawei Proprietary and Confidential iii

Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

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

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

vertical bars. Several items or no item can be selected.
&<1-n> The parameter before the & sign can be repeated 1 to n times.
# A line starting with the # sign is comments.
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Changes in Issue 02 (2014-09-30)

This issue is the second official release.
Changes in Issue 01 (2014-06-30)

This issue is the first official release.
Issue 02 (2014-09-30) Huawei Proprietary and Confidential iv

Configuration Guide - WAN Access Contents
Contents
About This Document.....................................................................................................................ii

1 Serial Interface Configuration....................................................................................................1
1.1 Introduction....................................................................................................................................................................2
1.1.1 Overview of the Synchronous Serial Interface............................................................................................................2
1.1.2 Features of the Synchronous Serial Interface on the NE80E/40E...............................................................................2
1.2 Configuring the Link Layer Attributes for a Serial Interface.........................................................................................3
1.2.1 Before You Start..........................................................................................................................................................3
1.2.2 Configuring Link Layer Protocol Type.......................................................................................................................4
1.2.3 Configuring Hold-Interval of the Link Layer Protocol of the Synchronous Serial Interface......................................5
1.2.4 Configuring the MTU..................................................................................................................................................5
1.2.5 Configuring the CRC Length......................................................................................................................................6
1.2.6 Checking the Configurations.......................................................................................................................................6
1.3 Maintaining Serial Interface Configuration....................................................................................................................8
1.3.1 Clearing the Interface Statistics...................................................................................................................................8
2 E-Carrier and T-Carrier Interface Configuration....................................................................9

2.1 Introduction..................................................................................................................................................................11
2.1.1 E-Carrier and T-Carrier Interface Overview.............................................................................................................11
2.1.2 Features of E-Carrier and T-Carrier Interfaces in the NE80E/40E...........................................................................13
2.2 Configuring CE1 Interfaces..........................................................................................................................................14
2.2.1 Before You Start........................................................................................................................................................14
2.2.2 Creating Synchronous Serial Interface for CE1 Interface.........................................................................................15
2.2.3 Configuring Encoding and Decoding Format of CE1 Interface................................................................................17
2.2.4 Configuring Clock Mode of CE1 Interface...............................................................................................................18
2.2.5 Configuring Frame Format of the CE1 Interface......................................................................................................19
2.2.6 Testing the Bit Error Rate of a CE1 Interface...........................................................................................................19
2.2.7 Configuring ES-TCA Alarm Thresholds on a CE1 Interface....................................................................................20
2.2.8 Checking the Configurations.....................................................................................................................................20
2.3 Configuring CT1 Interfaces..........................................................................................................................................22
2.3.1 Before You Start........................................................................................................................................................22
2.3.2 Creating Synchronous Serial Interface for CT1 Interface.........................................................................................23
2.3.3 Configuring Encoding and Decoding Format of the CT1 Interface..........................................................................24
2.3.4 Configuring Clock Mode of the CT1 Interface.........................................................................................................25
Issue 02 (2014-09-30) Huawei Proprietary and Confidential v

2.3.5 Configuring Frame Format of the CT1 Interface......................................................................................................25

2.4 Configuring E3 Interfaces............................................................................................................................................27
2.4.1 Before You Start........................................................................................................................................................27
2.4.2 Creating Synchronous Serial Interface for E3 Interface............................................................................................28
2.5 Configuring CT3 Interfaces..........................................................................................................................................29
2.5.1 Before You Start........................................................................................................................................................29
2.5.2 Creating Synchronous Serial Interface for CT3 Interface.........................................................................................30
2.5.3 Configuring Frame Format of the CT3 Interface......................................................................................................32
2.6 Configuring a T1 Channel of CT3 Interfaces...............................................................................................................33
2.6.1 Before You Start........................................................................................................................................................33
2.6.2 Configuring Clock Mode of a T1 Channel................................................................................................................34
2.6.3 Configuring Frame Format of a T1 Channel.............................................................................................................35
2.7 Maintaining E-Carrier and T-Carrier Interface Configuration.....................................................................................36
2.7.1 Configuring the Loopback Function to Detect the Link Status.................................................................................36
2.7.2 Clearing the Interface Statistics.................................................................................................................................37
2.8 Configuration Examples...............................................................................................................................................38
2.8.1 Example for Configuring Communication over CE1 Interfaces...............................................................................38
3 POS and CPOS Interface Configuration.................................................................................43

3.1 Introduction..................................................................................................................................................................45
3.1.1 Overview of POS and CPOS Interfaces....................................................................................................................45
3.1.2 Features of POS and CPOS Interfaces on the NE80E/40E.......................................................................................51
3.1.3 Description of SDH Alarms on POS Interfaces........................................................................................................54
3.2 Configuring POS Interfaces..........................................................................................................................................56
3.2.1 Establishing the Configuration Task.........................................................................................................................56
3.2.2 Configuring a Link Layer Protocol...........................................................................................................................57
3.2.3 Configuring a Clock Mode........................................................................................................................................58
3.2.4 Configuring the Overhead Byte.................................................................................................................................58
3.2.5 Configuring Frame Format........................................................................................................................................59
3.2.6 Configuring the Scramble Function..........................................................................................................................60
3.2.7 Configuring the Length of the CRC Check Character..............................................................................................60
3.2.8 Configuring MTU......................................................................................................................................................61
3.2.9 Configuring the Speed of a POS Interface................................................................................................................62
3.2.10 Checking the Configurations...................................................................................................................................63
3.3 Configuring STM-1 CPOS Interfaces..........................................................................................................................65
3.3.1 Before You Start........................................................................................................................................................65
3.3.2 Configuring Clock Mode...........................................................................................................................................65
Issue 02 (2014-09-30) Huawei Proprietary and Confidential vi


3.3.5 Configuring AUG Multiplexing Route......................................................................................................................68
3.4 Configuring an STM-4 CPOS Interface.......................................................................................................................69
3.4.1 Before You Start........................................................................................................................................................69
3.4.2 Configuring the Clock Mode.....................................................................................................................................70
3.4.4 Configuring an Overhead Byte for an AUG Interface Created on a CPOS Interface...............................................72
3.5 Configuring a CPOS-Trunk Interface...........................................................................................................................74
3.5.1 Before You Start........................................................................................................................................................74
3.5.2 Creating a CPOS-Trunk Interface and Adding CPOS Interfaces to the CPOS-Trunk..............................................74
3.5.3 Creating a Trunk-Serial Interface..............................................................................................................................75
3.6 Configuring WDM Interfaces.......................................................................................................................................78
3.6.1 Before You Start........................................................................................................................................................78
3.6.2 Configuring the FEC Mode of a WDM Interface......................................................................................................79
3.6.3 Configuring FEC Bit Error Detection on an OTN....................................................................................................79
3.6.4 Configuring the TTIs of the OTU and ODU.............................................................................................................80
3.7 Configuring E1 Channels of the CPOS Interface.........................................................................................................82
3.7.1 Before You Start........................................................................................................................................................82
3.7.2 Creating Synchronous Serial Interface of E1 Channel..............................................................................................82
3.7.5 Testing the Bit Error Rate of CPOS E1 link..............................................................................................................85
3.8 Configuring T1 Channels of the CPOS Interface.........................................................................................................87
3.8.1 Before You Start........................................................................................................................................................88
3.8.2 Creating Synchronous Serial Interface of T1 Channel..............................................................................................88
3.9 Configuring E3 Channels of an STM-1 CPOS Interface.............................................................................................91
3.9.1 Before You Start........................................................................................................................................................91
3.9.2 Creating Synchronous Serial Interface of E3 Channels............................................................................................92
3.10 Configuring T3 Channels of an STM-1 CPOS Interface...........................................................................................94
3.10.1 Before You Start......................................................................................................................................................94
3.10.2 Creating T3 Channels..............................................................................................................................................95
Issue 02 (2014-09-30) Huawei Proprietary and Confidential vii

3.10.3 Configuring Frame Format......................................................................................................................................96

3.10.4 Configuring Clock Mode.........................................................................................................................................96
3.11 Configuring an AUG Interface on an STM-4 CPOS Interface...................................................................................98
3.11.1 Before You Start......................................................................................................................................................98
3.11.2 Creating an AUG Interface......................................................................................................................................99
3.11.3 Configuring a serial interface on the AUG Interface...............................................................................................99
3.11.4 Checking the Configurations.................................................................................................................................100
3.12 Maintaining POS and CPOS Interface Configuration..............................................................................................100
3.12.1 Configuring the Self-loop to Detect Whether the Interface Is Normal.................................................................100
3.12.2 Clearing the Interface Statistics.............................................................................................................................102
3.12.3 Monitoring the Physical Status of E1/T1 Links....................................................................................................102
3.13 Configuration Examples ..........................................................................................................................................103
3.13.1 Example for Directly Connecting Devices Through POS Interfaces....................................................................103
3.13.2 Example for Connecting Devices with POS Interfaces Through FR Network.....................................................105
3.13.3 Example for Configuring an STM-1 CPOS Interface...........................................................................................108
3.13.4 Example for Configuring a BTB IP RAN - PWE3 (IP-Interworking) + (VSI + L3VPN) with Ethernet NodeBs
..........................................................................................................................................................................................110
3.13.5 Example for Configuring an Integrated IP RAN (IP-Interworking) with TDM BTSs..........................................133
4 PPP and MP Configuration.....................................................................................................155

4.1 Introduction................................................................................................................................................................157
4.1.1 PPP Overview..........................................................................................................................................................157
4.1.2 Features of PPP and MP on the NE80E/40E...........................................................................................................157
4.2 Encapsulating an Interface with PPP and MRU Negotiation.....................................................................................158
4.2.1 Before You Start......................................................................................................................................................158
4.2.2 Encapsulating the Interface with PPP......................................................................................................................158
4.2.3 Enabling PPP MRU Negotiation.............................................................................................................................159
4.2.4 Enabling Magic Number Check for the PPP Protocol............................................................................................160
4.3 Configuring Unidirectional PAP................................................................................................................................161
4.3.1 Before You Start......................................................................................................................................................162
4.3.2 Configuring a Local Device to Authenticate Its Peer in PAP Mode.......................................................................162
4.3.3 Configuring the Peer to Be Authenticated by the Local Device in PAP Mode.......................................................163
4.4 Configuring Unidirectional CHAP.............................................................................................................................165
4.4.1 Before You Start......................................................................................................................................................165
4.4.2 Configuring a Local Device with a User Name to Authenticate Its Peer in CHAP Mode......................................166
4.4.3 Configuring a Local Device Without a User Name to Authenticate Its Peer in CHAP Mode................................168
4.5 Configuring PPP Optional Parameters.......................................................................................................................170
4.5.1 Before You Start......................................................................................................................................................170
Issue 02 (2014-09-30) Huawei Proprietary and Confidential viii

4.5.2 Configuring the Callback Function.........................................................................................................................172

4.5.3 Configuring Packet or Packet Header Compression...............................................................................................173
4.5.4 Configuring the Timeout Period of Negotiation......................................................................................................173
4.5.5 Configuring the Polling Interval..............................................................................................................................174
4.5.6 Configuring the PPP LCP Link Dead Duration.......................................................................................................174
4.5.7 Configuring DNS Server Address Negotiation.......................................................................................................175
4.5.8 Configuring the PPP Link Quality Detection..........................................................................................................175
4.5.9 Preventing the Peer Host Route from Being Added to the Local Routing Table of Direct Routes........................176
4.5.10 Configuring PPP Timeslot Detection....................................................................................................................177
4.5.11 Enabling OSICP and MPLSCP to Go Up Without Device Negotiation...............................................................177
4.6 Configuring MP Binding Using an MP-Group..........................................................................................................179
4.6.1 Before You Start......................................................................................................................................................179
4.6.2 Adding an Interface to an MP-Group......................................................................................................................180
4.6.3 Adding an Interface to an Global-MP-Group..........................................................................................................181
4.6.4 Disabling the Endpoint Discriminator Negotiation.................................................................................................182
4.7 Configuring MP Limiting Parameters........................................................................................................................185
4.7.1 Before You Start......................................................................................................................................................185
4.7.2 Configuring the MRRU of an MP Group................................................................................................................186
4.7.3 Configuring the Damping Function for MP Subchannels.......................................................................................186
4.7.4 Configuring the Minimum Number of Subchannels in the Up State in an MP Link..............................................187
4.7.5 Enabling Delay Detection for MP-Group Member Links.......................................................................................188
4.8 Configuring MP Fragmentation..................................................................................................................................189
4.8.1 Before You Start......................................................................................................................................................189
4.8.2 Configuring the MP Fragment Function.................................................................................................................190
4.9 Configuring PPP Multiplexing...................................................................................................................................191
4.9.1 Before You Start......................................................................................................................................................191
4.9.2 Enabling PPP Multiplexing.....................................................................................................................................192
4.9.3 (Optional) Configuring the Default PID for PPP Multiplexing..............................................................................192
4.9.4 (Optional) Configuring the Delay for PPP Multiplexing........................................................................................193
4.9.5 (Optional) Configuring the Maximum Length of a PPP Multiplexed Frame..........................................................193
4.9.6 (Optional) Configuring the Maximum Number of Sub-frames That Can Be Concatenated into a PPP Multiplexed
Frame................................................................................................................................................................................194
4.9.7 (Optional) Configuring the Maximum Length of a PPP Sub-frame.......................................................................195
4.10 Configuring Global-MP-Group Interfaces ..............................................................................................................196
4.10.1 Before You Start....................................................................................................................................................196
4.10.2 Establishing a Global-MP-Group Interface and Adding Member Interfaces to It................................................197
Issue 02 (2014-09-30) Huawei Proprietary and Confidential ix

4.11 Configuration Examples...........................................................................................................................................199

4.11.1 Example for Configuring PAP Authentication......................................................................................................199
4.11.2 Example for Configuring Unidirectional CHAP Authentication..........................................................................202
4.11.3 Example for Configuring Bidirectional CHAP Authentication............................................................................205
4.11.4 Example for Configuring PPP Multiplexing.........................................................................................................208
4.11.5 Example for Binding MPs into an MP-group........................................................................................................211
5 Frame Relay Configuration.....................................................................................................216

5.1 Introduction................................................................................................................................................................217
5.1.1 FR Protocol Overview.............................................................................................................................................217
5.1.2 Features of FR on the NE80E/40E..........................................................................................................................217
5.2 Configuring FR...........................................................................................................................................................217
5.2.1 Before You Start......................................................................................................................................................217
5.2.2 Configuring Basic FR Functions.............................................................................................................................218
5.3 Configuring FR LMI Type and Related Parameters..................................................................................................220
5.3.1 Before You Start......................................................................................................................................................220
5.3.2 Configuring FR LMI and Related Parameters of DTE............................................................................................221
5.3.3 Configuring FR LMI and Related Parameters of DCE...........................................................................................222
5.4 Configuring FRF.8......................................................................................................................................................223
5.5 Maintaining Frame Relay Configuration....................................................................................................................225
5.5.1 Clearing the Statistics of FR and Dynamic Address Mapping Entries....................................................................225
5.6 Configuration Examples.............................................................................................................................................225
5.6.1 Example for Connecting Devices with POS Interfaces Through an FR Network..................................................225
6 HDLC and IP-Trunk Configuration......................................................................................229

6.1 Introduction................................................................................................................................................................230
6.1.1 HDLC and IP-Trunk Interface Overview................................................................................................................230
6.1.2 Features of HDLC and IP-Trunk interfaces on the router.......................................................................................230
6.2 Configuring HDLC.....................................................................................................................................................231
6.2.1 Before You Start......................................................................................................................................................231
6.2.2 Encapsulating an Interface with HDLC...................................................................................................................231
6.2.3 Configuring the IP Address of the Interface............................................................................................................232
6.2.4 Setting the Polling Interval......................................................................................................................................232
6.3 Configuring an IP-Trunk Interface.............................................................................................................................234
6.3.1 Before You Start......................................................................................................................................................234
6.3.2 Creating an IP-Trunk and adding POS Interfaces into the IP-Trunk.......................................................................235
6.3.3 Configuring an IP Address for the IP-Trunk Interface............................................................................................236
6.3.4 (Optional) Configuring the Lower Threshold of Up Links.....................................................................................237
6.3.5 (Optional) Configuring Load-balancing Mode for the IP-Trunk Interface.............................................................237
6.3.6 (Optional) Configuring Weights for Member Links...............................................................................................238
Issue 02 (2014-09-30) Huawei Proprietary and Confidential x

6.3.7 (Optional) Configuring the Method of Sending Trap Messages from an IP-Trunk Member Interface..................239
6.4 Maintaining HDLC and IP-Trunk Configuration.......................................................................................................241
6.4.1 Clearing the Statistics About HDLC or IP-Trunk Interfaces...................................................................................241
6.5.1 Example for Configuring HDLC.............................................................................................................................242
6.5.2 Example for Configuring IP Address Unnumbered for HDLC...............................................................................244
6.5.3 Example for Configuring an IP-Trunk....................................................................................................................246
7 Modem Configuration.............................................................................................................250
7.1 Introduction................................................................................................................................................................251
7.1.1 Modem Overview....................................................................................................................................................251
7.1.2 Features of the Modem in the NE80E/40E..............................................................................................................251
7.2 Configuring the Modem Management.......................................................................................................................252
7.2.1 Establishing the Configuration................................................................................................................................252
7.2.2 Configuring the Incoming and Outgoing Call Authority of Modem.......................................................................253
7.2.3 Configuring the Answer-Mode of Modem..............................................................................................................253
7.3 Configuring the Modem Script...................................................................................................................................254
7.3.1 Establishing the Configuration................................................................................................................................254
7.3.2 Defining Modem Script...........................................................................................................................................257
7.3.3 Executing the Modem Script Manually...................................................................................................................257
7.3.4 Specifying Events to Trigger the Modem................................................................................................................257
7.4.1 Example for Configuring the Remote Access to the Router Through the Modem.................................................258
7.4.2 Example for Configuring the Management of Modem by the Script......................................................................260
7.4.3 Example for Configuring the Initiation of the Power-on by the Initiated Script.....................................................261
7.4.4 Example for Dialing by the Script...........................................................................................................................262
8 ATM Configuration.................................................................................................................. 264

8.1 ATM Overview...........................................................................................................................................................266
8.1.1 Introduction.............................................................................................................................................................266
8.1.2 Features of ATM Supported by the NE80E/40E.....................................................................................................266
8.2 Configuring Parameters for an ATM OC-3/STM-1 Interface or an ATM OC-12/STM-4 Interface.........................267
8.2.1 Before You Start......................................................................................................................................................267
8.2.2 Configuring the Clock Mode...................................................................................................................................268
8.2.3 Configuring the Frame Format................................................................................................................................269
8.2.4 Configuring the Overhead Byte...............................................................................................................................269
8.2.5 Configuring the MTU..............................................................................................................................................270
8.2.6 Configuring the Scrambling....................................................................................................................................271
8.2.7 Configuring the Interval of Flow Statistics.............................................................................................................272
8.2.8 (Optional)Configuring the VPI Range on an NNI ATM Interface..........................................................................272
8.2.9 (Optional) Configuring an ATM-Trunk Interface...................................................................................................273
8.2.10 Configuring the ATM Module to Report Alarms to the NMS..............................................................................274
Issue 02 (2014-09-30) Huawei Proprietary and Confidential xi


8.3 Configuring an ATM PVC Group..............................................................................................................................276
8.3.1 Before You Start......................................................................................................................................................276
8.3.2 Creating a PVC Group.............................................................................................................................................277
8.3.3 Mapping IP Precedence Values to Separate ATM PVCs in an ATM PVC Group.................................................278
8.3.4 Configuring QoS Policies for ATM PVCs in an ATM PVC Group.......................................................................279
8.4 Configuring ATM Links to Transmit Different Protocol Packets..............................................................................281
8.4.1 Before You Start......................................................................................................................................................281
8.4.2 Configuring IPoA Mapping on PVCs.....................................................................................................................282
8.4.3 Configuring IPoEoA Mapping on PVCs.................................................................................................................284
8.4.4 Configuring PPPoA Mapping on PVCs..................................................................................................................285
8.4.5 Configuring PPPoEoA Mapping on PVCs..............................................................................................................286
8.5 Configuring the Service Type and Optional Parameters of a PVC............................................................................289
8.5.1 Before You Start......................................................................................................................................................289
8.5.2 Configuring the Service Type of a PVC..................................................................................................................290
8.5.3 Configuring the Service Type of a PVP..................................................................................................................291
8.5.4 (Optional) Configure the Overload Bandwidth Value of an ATM Interface..........................................................292
8.6 Configuring ATM OAM............................................................................................................................................294
8.6.1 Before You Start......................................................................................................................................................294
8.6.2 (Optional) Activating the CC Function...................................................................................................................295
8.6.3 (Optional) Configuring OAM End-to-End Loopback.............................................................................................296
8.6.4 (Optional) Configuring the Cell Loopback.............................................................................................................297
8.6.5 (Optional) Configuring an ATM Connectivity Test................................................................................................299
8.7 Maintaining ATM Configuration...............................................................................................................................300
8.7.1 Setting Loopback to Detect Whether an Interface Is Normal..................................................................................300
8.7.2 Clearing the ATM Interface Statistics.....................................................................................................................301
8.8.1 Example for Configuring IPoA...............................................................................................................................302
8.8.2 Example for Configuring the PPPoA Service.........................................................................................................305
8.8.3 Example for Configuring PPPoEoA........................................................................................................................307
8.8.4 Example for Configuring ATM OAM.....................................................................................................................310
9 1483B Configuration.................................................................................................................314
9.1 Introduction of 1483B................................................................................................................................................315
9.1.1 1483B Overview......................................................................................................................................................315
9.2 Configuring IPoEoA Services....................................................................................................................................316
9.2.1 Before You Start......................................................................................................................................................316
9.2.2 Creating a VE Interface...........................................................................................................................................316
Issue 02 (2014-09-30) Huawei Proprietary and Confidential xii

9.2.3 Configuring IPoEoA Application Mapping on a PVC............................................................................................317

9.2.4 Configuring Services on the VE Interface...............................................................................................................318
9.3.1 Example for Configuring a Routing VE Interface to Work as an IPoEoA Gateway..............................................320
9.3.2 Example for Configuring ATM Bridged Ethernet..................................................................................................322
9.3.3 Example for Configuring a VLANIF Interface to Work as an IPoEoA Gateway...................................................324
10 PRBS Testing Configuration.................................................................................................327

10.1 Overview..................................................................................................................................................................328
10.2 Configuring PRBS Testing.......................................................................................................................................329
10.2.1 Before You Start....................................................................................................................................................329
10.2.2 (Optional) Configuring User-Side PRBS Testing.................................................................................................330
10.2.3 (Optional) Configuring Network-Side PRBS Testing...........................................................................................331
A Glossary......................................................................................................................................334
B Acronyms and Abbreviations.................................................................................................336
Issue 02 (2014-09-30) Huawei Proprietary and Confidential xiii

Configuration Guide - WAN Access 1 Serial Interface Configuration
1 Serial Interface Configuration
About This Chapter
This chapter describes how to configure physical layer attributes and link layer attributes of
synchronous serial interfaces.
1.1 Introduction
Serial interfaces are classified into synchronous serial interfaces and asynchronous serial
interfaces. Synchronous serial interfaces are widely used on the WAN.
1.2 Configuring the Link Layer Attributes for a Serial Interface

By configuring link layer attributes for a serial interface, you can make the link layer protocol
of the serial interface become available and the protocol status of the serial interface become
Up.
1.3 Maintaining Serial Interface Configuration

You can maintain a serial interface by enabling the loopback function to detect its status or by
clearing its statistics.
Issue 02 (2014-09-30) Huawei Proprietary and Confidential 1

1.1 Introduction
Serial interfaces are classified into synchronous serial interfaces and asynchronous serial
interfaces. Synchronous serial interfaces are widely used on the WAN.
1.1.1 Overview of the Synchronous Serial Interface

As one of the most commonly used interfaces on the WAN, serial interfaces can be classified
into synchronous and asynchronous serial interfaces.
A serial interface is one of the most commonly used WAN interfaces. At present, synchronous
serial interfaces are more widely used than asynchronous serial interfaces. Serial interfaces in
this chapter refer to synchronous serial interfaces unless otherwise specified.
The serial interfaces that are channelized from the E-carrier, T-carrier, and channelized-POS
(CPOS) interfaces and function as common serial interfaces, have the same logical features as
synchronous serial interfaces.
1.1.2 Features of the Synchronous Serial Interface on the NE80E/40E

The NE80E/40E supports synchronous serial interfaces formed by CE1, CT1, E3, CT3, as well
as E1/T1 and E3/T3 channelized from CPOS interfaces. Each of these interfaces has a different
index mode.
Features of the Synchronous Serial Interface on the X1 and X2 models of the NE80E/40E
On the X1 and X2 models of the NE80E/40E, the synchronous serial interfaces that are
channelized from physical interfaces can be configured with the MTU and link layer protocols.
Table 1-1 shows the index modes of synchronous serial interfaces.
Table 1-1 Index modes of synchronous serial interfaces
Physical Interface Index Mode
E1 channelized from a slot/card/port/channel:0 or slot/card/port/channel:channel-set

CPOS interface
CE1 interface slot/card/port:channel-set or slot/card/port:0
Features of the Synchronous Serial Interface on the other models of the NE80E/40E
On the other models of the NE80E/40E, the synchronous serial interfaces that are channelized
from physical interfaces can be configured with the MTU and link layer protocols. Table 1-2
shows the index modes of synchronous serial interfaces.

Table 1-2 Index modes of synchronous serial interfaces
Physical Interface Index Mode
E1/T1 channelized from a slot/card/port/channel:0 or slot/card/port/channel:channel-set

CPOS interface
E3/T3 channelized from a slot/card/port/channel:0

CPOS interface
CE1 and CT1 interfaces slot/card/port:channel-set or slot/card/port:0
E3 and CT3 interfaces slot/card/port/0:0, slot/card/port/channel:0, or slot/card/port/

channel:channel-set
1.2 Configuring the Link Layer Attributes for a Serial

Interface
By configuring link layer attributes for a serial interface, you can make the link layer protocol
of the serial interface become available and the protocol status of the serial interface become
Up.
1.2.1 Before You Start

Before configuring link layer attributes for a serial interface, familiarize yourself with the usage
scenario, complete the pre-configuration tasks, and obtain the data required for the configuration.
Usage Scenario
To enable upper layer services over a serial interface, configure link layer attributes for the serial
interface to ensure that its link layer protocol is Up.
Pre-configuration Tasks
Before configuring link layer attributes for a serial interface, complete the following tasks:
l Power on the router and conduct a successful self-check.

l Connect the serial interfaces and configure their physical parameters to ensure that they
are physically 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

No. Data
3 Hold-interval of the link layer protocol
4 MTU of the interface
5 CRC length of the interface
1.2.2 Configuring Link Layer Protocol Type

The link layer protocol type of a serial interface determines the frame format of the data that
passes through it. Currently, protocols, such as ATM, FR, HDLC, PPP, and TDM, are supported.
Context
The link layer protocol type of a serial interface determines the frame format of the data that
passes through it.
For detailed configurations of each link layer protocol, see the chapters PPP and MP
Configuration, FR Configuration, and HDLC and IP-Trunk Configuration.
Perform the following steps on the routers:
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 link layer protocol type is configured on the interface.
By default, the link layer protocol is PPP.
NOTE
l The link layer protocol can be configured as ATM or TDM only on the synchronous serial interfaces
that are channelized from CE1 interfaces and E1 channel of the CPOS interfaces.
l You can create a PW tunnel on an interface with the link layer protocol TDM. For specific
configurations, see the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.
l A synchronous serial interface formed by E3 and CT3 interfaces supports only PPP and HDLC as link
layer protocols.
l A synchronous serial interface on the X1 and X2 models of the NE80E/40E does not support HDLC
as link layer protocols.
----End

1.2.3 Configuring Hold-Interval of the Link Layer Protocol of the

Synchronous Serial Interface
To detect and maintain the connectivity of a link, each end of the link sends detection packets
to the other at the hold-interval of the link layer protocol.
Context
Two ends of a link periodically send detection packets to each other to check and maintain
connectivity.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The synchronous serial interface view is displayed.
Step 3 Run:
timer hold hold-interval
The hold-interval of the link layer protocol is set.
By default, the hold-interval of a link layer protocol is 10 seconds. If the hold-interval is set to
0, it indicates that no detection packets will be sent.
----End
1.2.4 Configuring the MTU

The Maximum Transmission Unit (MTU) of a serial interface affects the assembly and
disassembly of IP packets on the interface.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
mtu mtu

The MTU is configured for the serial interface.
----End
1.2.5 Configuring the CRC Length

When configuring the CRC length, ensure that two directly-connected devices are configured
with the same CRC length.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
The synchronous serial interface view is displayed.
Step 3 Run:
crc { 16 | 32 }
The CRC length of the synchronous serial interface is configured.
When configuring the CRC length on a synchronous serial interface, ensure that devices on both
ends are configured with the same CRC length.
By default, the CRC length is 32 bits.
----End
1.2.6 Checking the Configurations

After link layer attributes are configured for a synchronous serial interface, you can check the
protocol type, the hold-interval of the link layer protocol, MTU, and the CRC length.
Procedure
l Run the display interface serial [ interface-number ] [ | { begin | exclude | include }
regular-expression ] command to check the status and statistics of a synchronous serial
interface.
l Run the display interface brief [ | { begin | include | exclude } regular-expression ]
command to check brief information about a synchronous serial interface.
l Run the display ip interface brief serial interface-number command to check the network
layer configuration of a synchronous serial interface.
----End

Example
Run the display interface serial command. You can view the status and statistics of the
synchronous serial interface. For example:
<HUAWEI> display interface serial 1/0/0:0
Serial1/0/0:0 current state : UP
Line protocol current state : UP
Last line protocol up time : 2009-01-20 15:55:16
Description: Serial1/0/0:0 Interface
Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec)
Derived from E1 1/0/0, Unframed mode, baudrate is 2048000 bps
Internet Address is 10.1.1.1/24
Link layer protocol is PPP
LCP opened, IPCP opened
Physical layer is Packet Over ESF
clock master, loopback none
CRC: CRC-32
Scramble disabled
Alarm: None
Statistics 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 interface brief [ | { begin | include | exclude } regular-expression ] command.
You can view brief information about the synchronous serial interface, such as the physical
status, link protocol status, bandwidth utilization, and number of error packets. For example:
<HUAWEI> display interface brief | include Serial
PHY: Physical
*down: administratively down
^down: standby
(l): loopback
(s): spoofing
(b): BFD down
(e): EFM down
(d): Dampening Suppressed
InUti/OutUti: input utility/output utility
Interface 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: FIB overload down
(l): loopback
(s): spoofing
The number of interface that is UP in Physical is 2
The number of interface that is DOWN in Physical is 1
The number of interface that is UP in Protocol is 2
The number of interface that is DOWN in Protocol is 1
Interface IP Address/Mask Physical Protocol

Aux0/0/1 unassigned *down down
GigabitEthernet0/0/0 1.1.1.1/24 up up
Serial1/0/0:0 10.1.1.1/24 up up

1.3 Maintaining Serial Interface Configuration

You can maintain a serial interface by enabling the loopback function to detect its status or by
clearing its statistics.
1.3.1 Clearing the Interface Statistics

Statistics on a serial interface are traffic statistics that can be reset traffic statistics before
recollecting them.
Context
NOTICE
Interface statistics cannot be restored after they are cleared. Exercise caution when running the
clear commands.
To clear interface statistics in the Network Management System (NMS) or those displayed using
the display interface command, run the following commands in the user view.
NOTE
For the display of interface statistics on the NMS, see related NMS manuals.
Procedure
l Run the reset counters interface [ serial [ interface-number ] ] command to clear the
interface statistics previously displayed using the display interface command.
l Run the reset counters if-mib interface [ serial [ interface-number ] ] command to clear
the interface statistics on the NMS.
----End

Configuration Guide - WAN Access 2 E-Carrier and T-Carrier Interface Configuration
2 E-Carrier and T-Carrier Interface

Configuration
About This Chapter
Both types of carrier systems adopt PCM but belong to two incompatible international standards
which are European 30-channel PCM (E1 for short) and North American 24-channel PCM (T1
for short).
NOTE
CT1 interfaces, E3 interfaces, and CT3 interfaces are not supported on the X1 and X2 models of the NE80E/
40E.
2.1 Introduction
E-carrier interfaces include CE1 and E3 interfaces. T-carrier interfaces include CT1 and CT3
interfaces.
2.2 Configuring CE1 Interfaces

You can configure synchronous serial interfaces on CE1 interfaces; you can also configure the
encoding and decoding format, clock mode, frame format, and cable mode for the CE1 interfaces.
2.3 Configuring CT1 Interfaces

You can create synchronous serial interfaces on CT1 interfaces; you can also configure the
encoding and decoding format, clock mode, and frame format for the CT1 interfaces.
2.4 Configuring E3 Interfaces

You can create synchronous serial interfaces on CE3 interfaces; and you can also configure the
clock mode and national bit for the CE3 interfaces.

You can create synchronous serial interfaces on CT3 interfaces; and you can also configure the
frame format for the CT3 interfaces.
2.6 Configuring a T1 Channel of CT3 Interfaces

You can configure the clock mode and frame format for T1 channels of CT3 interfaces and
disable or enable T1 channels of the CT3 interfaces.
2.7 Maintaining E-Carrier and T-Carrier Interface Configuration

You can maintain E-carrier and T-carrier interfaces by enabling the loopback function to detect
whether an interface runs properly or by clearing interface statistics.
2.8 Configuration Examples

This section provides an example for configuring E-carrier and T-carrier interfaces. This
configuration example explains the networking requirements, configuration roadmap, data
preparation, configuration procedure, and configuration files.

2.1 Introduction
E-carrier interfaces include CE1 and E3 interfaces. T-carrier interfaces include CT1 and CT3
interfaces.
2.1.1 E-Carrier and T-Carrier Interface Overview

E-carrier interfaces and T-carrier interfaces can work in any of the three modes, channelized
mode, unchannelized mode, and clear channel mode.
Basic Concepts of E-Carrier and T-Carrier
The present digital transmission system adopts Pulse Code Modulation (PCM). PCM was
initially designed to enable a trunk cable between telephone exchanges to transfer multiple
telephones. PCM has two incompatible international standards:
l European 30-channel PCM, which is called E1

30 channels indicate that E1 has 32 timeslots, among which 30 timeslots are used to transmit
data. Timeslot 0 is used to transmit frame synchronization and alarm signals. Timeslot 15
is used to transmit control signaling. The rate of E1 is 2.048 Mbit/s. At present, the NE80E/
40E supports 31-channel PCM. Timeslot 15 is also used to transmit data in addition to
transmitting control signaling.
l 24-channel PCM of North America, which is called T1
24 channels indicate that T1 has 24 timeslots, all of which can be used to transmit data.
The rate of T1 is 1.544 Mbit/s.
E-carrier is a digital communication system recommended by the International

Telecommunication Union-Telecommunication Standardization Sector (ITU-T). It starts from
E1 and has been applied in many regions except North America.
The American National Standards Institute (ANSI) defines the T-carrier system standard in the
T1.107 Specification. The standard starts from T1 and is widely used in North America. Similar
to T1, Japan's J1 also belongs to the T-carrier system standard.
The primary features of T-carrier and E-carrier are almost the same although the detail of their
protocols differs.
Digital Carrier System

The carrier system enables a single physical communication channel to contain multiple logical
channels. Therefore, the carrier system supports multi-channel communication.
In the digital carrier system, a single digital circuit with a large capacity supports multiple logical
channels, each of which supports one independent channel.
Channelized, Unchannelized, and Clear Channel Modes

E-carrier and T-carrier interfaces can work in any of the following modes:

l Channelized mode: In framed mode, all timeslots except the frame header in the data stream
can be allocated to different channels.
l Unchannelized mode: In framed mode, all timeslots except the frame header in the data
stream can be bound only once and allocated to only one channel.
l Clear Channel mode: It is also called the unframed mode. In unframed mode, there is no
frame flag in the data stream, and all bits in the data stream are data. The data in the data
stream belongs to only one channel.
Introduction to CE1 Interface
When a physical interface formed by E1 works only in clear channel mode or unchannelized
mode, this interface is called a CE1 interface.
A CE1 interface has the following characteristics:
l In clear channel mode, also called the unframed mode, a CE1 interface functions like an
interface with the transmission rate of 2.048 Mbit/s and without timeslot division. It has
the same logical features as a synchronous serial interface and supports network protocols,
such as IP, link layer protocols, such as PPP and HDLC, and MP bundling.
l In channelized mode, also called the framed mode, a CE1 interface is physically divided
into 32 timeslots numbered from 0 to 31. The 32 timeslots can be randomly bundled to
form a logical channel with the transmission rate of N x 64 kbit/s.
Each bundled channel-set of timeslots is used as an interface with the same logical features
as a synchronous serial interface and supports network protocols, such as IP, link layer
protocols, such as PPP, HDLC, ATM, TDM, and MP bundling.
Introduction to CT1 Interfaces
When a physical interface formed by T1 works only in clear channel mode or channelized mode,
this interface is called a CT1 interface.
A CT1 interface has the following characteristics:
l In clear channel mode, also called the unframed mode, a CT1 interface functions like an
the same logical features as a synchronous serial interface and supports network protocols,
such as IP, link layer protocols, such as PPP and HDLC, and MP bundling.
l In channelized mode, also called the framed mode, a CT1 interface is physically divided
into 24 timeslots numbered from 0 to 23. The 24 timeslots can be randomly bundled to
form a logical channel with the transmission rate of N x 64 kbit/s.
In CT1 mode, all timeslots can be grouped into multiple channel-sets. Each bundled
channel-set of timeslots is used as an interface with the same logical features as a
synchronous serial interface and supports network protocols, such as IP, link layer
protocols, such as PPP and HDLC, and MP bundling.
Introduction to E3 Interfaces
An E3 interface works in either of the following modes:

l In clear channel mode, also called the unframed mode, an E3 interface functions like an
interface with the transmission rate of 34.368 Mbit/s and without timeslot division.
l In unchannelized mode, also called the framed mode, data is transmitted in the channel in
the form of frames. All timeslots are bundled to form a channel that functions like an
interface with the transmission rate of 33.831 Mbit/s and without timeslot division. The
channel has the same logical features as a synchronous serial interface.
An E3 interface supports network protocols, such as IP and link layer protocols, such as PPP
and HDLC.
Introduction to CT3 Interfaces
A CT3 interface works in any of the following modes:
l In clear channel mode, also called the unframed mode, a CT3 interface functions like an
the same logical features as a synchronous serial interface.
l In unchannelized mode, also called the framed mode, data is transmitted in the channel in
the form of frames. All timeslots are bundled to form a channel that functions like an
interface with the transmission rate of 44.210 Mbit/s and without timeslot division. The
channel has the same logical features as a synchronous serial interface.
l In channelized mode, also called the framed mode, a CT3 interface can multiplex or
demultiplex 28-channel T1 signals. Each T1 can be configured separately. Each serial
interface functions like an interface whose logical features are the same as those of a
synchronous serial interface.
A CT3 interface supports network protocols, such as IP and link layer protocols, such as PPP
and HDLC.
2.1.2 Features of E-Carrier and T-Carrier Interfaces in the NE80E/

40E
Interfaces supported by the NE80E/40E vary according to the operation modes of E-carrier and
T-carrier interfaces. The E-carrier interfaces supported by the NE80E/40E include E1 interfaces
in clear channel mode, CE1 interfaces, E3 interface, and CE3 interfaces. The T-carrier interfaces
supported by the NE80E/40E include CT1 interfaces in channelized mode, T3 interfaces, and
CT3 interfaces.
Types of E-Carrier and T-Carrier Interfaces
Types of E-Carrier and T-Carrier Interfaces Supported by the X1 and X2 Models of the
NE80E/40E
The E-carrier interface type supported by the X1 and X2 models of the NE80E/40E is only the
CE1 interface.
The X1 and X2 models of the NE80E/40E do not support T-carrier interfaces.
Types of E-Carrier and T-Carrier Interfaces Supported by the Other Models of the
NE80E/40E
The E-carrier interfaces supported by the Other Models of the NE80E/40E include:

l CE1 interfaces
l E3 interfaces
The T-carrier interfaces supported by the Other Models of the NE80E/40E include:
l CT1 interfaces
l CT3 interfaces
Introduction
The serial interface formed by an E-carrier or T-carrier interface is called a channelized serial
interface which has the same logical features as a synchronous serial interface.
The number of a channelized serial interface has a four-dimensional structure, and the name and
number format of the interface is serial interface-number:set-number. The parameter interface-
number specifies the E-carrier or T-carrier interface number. The parameter set-number specifies
the index of the interface that timeslots of an E-carrier or T-carrier interface are bundled into.
The method for configuring the link layer attributes of a channelized serial interface is the same
as that for a synchronous serial interface. For details, see the HUAWEI NetEngine80E/40E
Router Configuration Guide - Serial Interface Configuration.
2.2 Configuring CE1 Interfaces

You can configure synchronous serial interfaces on CE1 interfaces; you can also configure the
encoding and decoding format, clock mode, frame format, and cable mode for the CE1 interfaces.

Before configuring CE1 interfaces, familiarize yourself with the usage scenario, complete the
pre-configuration tasks, and obtain the data required for the configuration.
Usage Scenario
Before using a CE1 interface to bear upper layer services, configure parameters for the CE1
interface.
NOTICE
l When a physical interface is not installed with any type of cable, run the shutdown command
to disable the interface and to avoid any interference.
l After configuring services on an interface, run the shutdown and undo shutdown commands
in the interface view to ensure that the configured services are loaded properly.
l Disabling a CE1 interface may affect the normal operation of its channel-set.
Before configuring CE1 interfaces, power on the router and conduct a successful self-check.

Data Preparation
To configure CE1 interfaces, you need the following data.
No. Data
1 Number of the CE1 interface on the router
2 Number of the channel into which timeslots of the CE1 interface are bundled
3 Number or range of the timeslot bundled into a channel-set
2.2.2 Creating Synchronous Serial Interface for CE1 Interface

CE1 interfaces working in either clear channel mode or channelized mode can form synchronous
serial interfaces with different rates.
Context
CE1 interfaces on the X1 and X2 models of the NE80E/40E can form synchronous serial
interfaces with different rates:
l When a CE1 interface works in clear channel mode, a synchronous serial interface is formed
with the transmission rate of 2.048 Mbit/s and without timeslot division.
l When a CE1 interface works in channelized mode, timeslots of the CE1 interface need to
be bundled into a logical channel to form a synchronous serial interface. X1 and X2 models
of the NE80E/40E support two types of timeslot bundling:
– Bundling of timeslots 1 to 31, with timeslot 0 used to transmit signaling information
– Bundling of timeslots 1 to 15 or timeslots 17 to 31, with timeslots 1 and 16 used to
transmit signaling information
NOTE
By default, a CE1 interface works in channelized mode.
CE1 interfaces on the other models of the NE80E/40E can form synchronous serial interfaces
with different rates:
l When a CE1 interface works in clear channel mode, a synchronous serial interface is formed
l When a CE1 interface works in channelized mode, timeslots 0 to 31 of the CE1 interface
can be randomly bundled into a logical channel to form a synchronous serial interface, with
the transmission rate of N x 64 kbit/s. N stands for the number of bundled timeslots.
NOTE
By default, a CE1 interface works in channelized mode.
Procedure
l Create a synchronous serial interface in clear channel mode.

1. Run:
system-view

2. Run:
controller e1 controller-number
The CE1 interface view is displayed.

3. Run:
using e1
The CE1 interface is configured to work in clear channel mode, and a synchronous
serial interface is configured with the transmission rate of 2.048 Mbit/s and without
timeslot division.
You can run the interface serial controller-number:0 command to access the
l Create a synchronous serial interface in channelized mode on the X1 and X2 models of the
NE80E/40E.
1. Run:
system-view

2. Run:

3. Run:
using ce1
The CE1 interface is configured to work in channelized mode.

4. Run:
channel-set set-number timeslot-list slot-list
Timeslots of the CE1 interface are bundled to form a synchronous serial interface.
You can run the interface serial controller-number:set-number command to access

the synchronous serial interface.
– To change an interface from the CE1 mode to the E1 mode, delete all configurations
in CE1 mode and all synchronous serial interfaces, and then run the using e1
command.
– To change an interface from the E1 mode to the CE1 mode, delete all configurations
in E1 mode and all configurations of synchronous serial interfaces, and then run
the using ce1 or undo using command. In this case, the synchronous serial
interfaces do not need to be deleted.
l Create a synchronous serial interface in channelized mode on the other models of the
NE80E/40E.
1. Run:
system-view

2. Run:

3. Run:
using ce1
The CE1 interface is configured to work in channelized mode.

4. Run:
channel-set set-number timeslot-list { ts0 | slot-list [ ts0 ] }
Timeslots of the CE1 interface are bundled to form a synchronous serial interface with
the transmission rate of N x 64 kbit/s. N stands for the number of bundled timeslots.

– To change an interface from the CE1 mode to the E1 mode, delete all configurations
in CE1 mode and all synchronous serial interfaces, and then run the using e1
command.
– To change an interface from the E1 mode to the CE1 mode, delete all configurations
in E1 mode and all configurations of synchronous serial interfaces, and then run
the using ce1 or undo using command. In this case, the synchronous serial
interfaces do not need to be deleted.
In channelized mode, timeslot 0 alone can be bundled to form a synchronous serial

interface; timeslots 0 to 31 can also be randomly bundled to form one or multiple
synchronous serial interfaces. In this case, timeslot 0 needs to be specified in the
command using the parameter ts0.
Timeslot 0 is used to transmit frame synchronization and alarm information. After

timeslot 0 is bundled to form a synchronous serial interface, frame synchronization
and alarm information can be transparently transmitted between the client and the
server.
----End
2.2.3 Configuring Encoding and Decoding Format of CE1 Interface

CE1 interfaces support two types of encoding and decoding formats, namely, AMI and HDB3.
Context
A CE1 interface supports the following encoding and decoding formats:
l Alternate Mark Inversion (AMI)

l High Density Bipolar of Order 3 (HDB3)
Procedure
Step 1 Run:
system-view

Step 2 Run:
Step 3 Run:
code { ami | hdb3 }
The encoding and decoding format of the CE1 interface is configured.
By default, the encoding and decoding format of a CE1 interface is HDB3.
----End
2.2.4 Configuring Clock Mode of CE1 Interface

A CE1 interface works in either master clock or slave clock mode. When two CE1 interfaces
are directly connected, configure one to work in master clock mode and the other in slave clock
mode. However, when a CE1 interface is connected to a transmission device, the CE1 interface
must work in slave clock mode.
Context
A CE1 interface works in either of the following clock modes:
l In master clock mode, a CE1 interface uses internal clock signals.

l In slave clock mode, a CE1 interface uses line clock signals.
When the CE1 interfaces belonging to two routers are directly connected, configure one interface
to work in master clock mode and the other in slave clock mode. When the CE1 interface on the
router is connected to a transmission device, it is recommended that you configure the interface
to work in slave clock mode and use the clock signals provided by the transmission device.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
clock { master | slave }
Clock mode of the CE1 interface is configured.
NOTE
When used as a synchronous serial interface, a CE1 interface also has two working modes: DTE and DCE.
In this case, specify the clock mode for the CE1 interface.

By default, a CE1 interface works in master clock mode.
----End
2.2.5 Configuring Frame Format of the CE1 Interface

You can use the 4-bit CRC code to check physical frames on CE1 interfaces.
Context
An interface can be configured with the frame format only when in channelized mode.
Procedure
Step 1 Run:
system-view
Step 2 Run:
controller e1controller-number
Step 3 Run:
frame-format { crc4 | no-crc4 }
The frame format of the CE1 interface is configured.
NOTE
By default, the frame format of a CE1 interface is no-CRC4.
----End
2.2.6 Testing the Bit Error Rate of a CE1 Interface

Test results can be used to locate link faults.
Context
When faults occur on a CE1 interface, you can run the test connectivity e1 command to
determine the cause.
Procedure
Step 1 Run:
system-view
Step 2 Run:
test connectivity controller e1 controller-number { unframed | channelized timeslot-
list slot-list } duration time

Testing the Bit Error Rate of a CE1 Interface is enabled.
----End
2.2.7 Configuring ES-TCA Alarm Thresholds on a CE1 Interface

If the threshold for triggering an ES-TCA alarm is set and the number of E1 code errors exceeds
the threshold, an alarm will be generated.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The view of a specific CE1 interface is displayed.
Step 3 Run:
trap-threshold es-tca trigger-threshold trigger-threshold resume-threshold resume-
threshold
The thresholds for triggering and clearing an ES-TCA alarm are set.
By default, the threshold for triggering an ES-TCA alarm is 65, and the threshold for clearing
an ES-TCA alarm is 30.
----End

After a CE1 interface is configured, you can check the encoding and decoding format, clock
mode, and frame format.
Procedure
l 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 configuration
and status of the CE1 interface.
l Run the display e1 controller e1 controller-number command to check the current
statistics on alarms and error packets of the CE1 interface.
l Run the display e1 controller e1 controller-number history command to check the
historical statistics on alarms and error packets of a CE1 interface.
----End
Example
Run the display interface serial command to view the configuration of the channel-set and the
status of the CE1 interface.


Description : Serial1/0/0:2 Interface
Route 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 bps
Internet protocol processing : disabled
LCP opened
CRC: CRC-32
Scramble disabled
Alarm: None
Traffic statistics:
Run the display controller e1 command to view the configuration and status of the CE1
interface.
<HUAWEI> display controller e1 1/0/0
E1 1/0/0 current state : DOWN
Description : HUAWEI, Quidway Series, E1 1/0/0 Interface
Physical layer is Packet Over NO-CRC4
clock master, linecode hdb3 , loopback none
Alarm: LOS
Run the display e1 controller e1 command to view the current statistics of the CE1 interface.
<HUAWEI> display e1 controller e1 1/0/0
clock master, linecode hdb3, loopback none
E1 alarm: LOS
Statistics last cleared:never
Statistics:
Line Code Violation:0
CRC Error:0
Framing Error:5
E-Bit:0
Run the display e1 controller e1 history command to view the historical statistics on alarms
and error packets of the CE1 interface.
<HUAWEI> display e1 controller e1 1/0/0 history
clock master, linecode hdb3, loopback none
E1 alarm: None
E1 alarm history:
1 2012-02-22 16:42:17 LOF
2 2012-02-22 16:42:16 PAIS
3 2012-02-22 16:42:16 None
4 2012-02-22 16:42:16 PRDI
5 2012-02-22 16:42:16 PAIS
6 2012-02-22 16:42:16 None
7 2012-02-22 16:42:16 PRDI
8 2012-02-22 16:42:16 LOF
9 2012-02-22 16:42:16 PAIS
10 2012-02-22 16:33:48 LOF
Statistics:
Line Code Violation:0

CRC Error:0
Framing Error:185673
E-Bit:0
Statistics History:
Line Code Violation
No records.
CRC Error
No records.
Framing Error
1 2012-02-22 16:42:14 185673
2 2012-02-22 16:42:03 181665
3 2012-02-22 16:41:52 177600
4 2012-02-22 16:41:40 173295
5 2012-02-22 16:41:29 169095
6 2012-02-22 16:41:18 165291
7 2012-02-22 16:41:08 161400
8 2012-02-22 16:40:57 157539
9 2012-02-22 16:40:47 153654
10 2012-02-22 16:33:51 975
E-Bit
No records.

You can create synchronous serial interfaces on CT1 interfaces; you can also configure the
encoding and decoding format, clock mode, and frame format for the CT1 interfaces.

Before configuring CT1 interfaces, familiarize yourself with the usage scenario, complete the
Usage Scenario
Before using a CT1 interface to bear upper layer services, configure parameters for the CT1
interface.
NOTICE
l Disabling a CT1 interface may affect the normal operation of its channel-set.
Before configuring CT1 interfaces, power on the router and conduct a successful self-check.
Data Preparation
To configure CT1 interfaces, you need the following data.

No. Data
1 Number of the CT1 interface on the router
2 Number of the channel into which timeslots of the CT1 interface are bundled
3 Number or range of the timeslot bundled into a channel-set
2.3.2 Creating Synchronous Serial Interface for CT1 Interface

On CT1 interfaces, you must create synchronous serial interfaces before data transmission.
Context
CT1 interfaces working in different modes can form synchronous serial interfaces with different
rates:
l When a CT1 interface works in clear channel mode, a synchronous serial interface is formed
l When a CT1 interface works in channelized mode, timeslots 0 to 23 of the CT1 interface
can be bundled randomly to form a logical channel with the transmission rate of N x 64
kbit/s. N stands for the number of bundled timeslots.
By default, a CT1 interface works in channelized mode.
Procedure
l Creating a synchronous serial interface in clear channel mode
1. Run:
system-view

2. Run:
controller t1 controller-number
The CT1 interface view is displayed.

3. Run:
using t1
The CT1 interface is configured to work in clear channel mode, and a synchronous
serial interface is created with the transmission rate of 1.544 Mbit/s and without
timeslot division.
l Creating a synchronous serial interface in channelized mode
1. Run:
system-view


2. Run:

3. Run:
using ct1
The CT1 interface is configured to work in channelized mode.

4. Run:
channel-set set-number timeslot-list slot-list
Timeslots of the CT1 interface are bundled together to form a synchronous serial
interface with the transmission rate of N x 64 kbit/s. N stands for the number of bundled
timeslots.

– To change an interface from the CT1 mode to the T1 mode, delete all configurations
in CT1 mode and delete all synchronous serial interfaces, and then run the using
t1 command.
– To change an interface from the T1 mode to the CT1 mode, delete all configurations
in T1 mode and all configurations of synchronous serial interfaces, without having
to delete the synchronous serial interfaces, and then run the using ct1 or undo
using command.
----End
2.3.3 Configuring Encoding and Decoding Format of the CT1

Interface
CT1 interfaces support two types of encoding and decoding formats, namely, AMI and B8ZS.
Context
A CT1 interface supports the following encoding and decoding formats:
l Alternate Mark Inversion (AMI)

l Bipolar with 8-Zero Substitution (B8ZS)
Procedure
Step 1 Run:
system-view
Step 2 Run:

Step 3 Run:
code { ami | b8zs }
The encoding and decoding format of the CT1 interface is configured.
By default, the encoding and decoding format of a CT1 interface is B8ZS.
----End
2.3.4 Configuring Clock Mode of the CT1 Interface

A CT1 interface works in either master clock or slave clock mode. You can specify the clock
mode for a CT1 interface according to its working mode (the DTE device or the DCE device).
Context
A CT1 interface works in either of the following clock modes:
l In master clock mode, a CT1 interface uses internal clock signals.

l In slave clock mode, a CT1 interface uses line clock signals.
When a CT1 interface is used as a DCE device, configure the CT1 interface to work in master
clock mode. When a CT1 interface is used as a DTE device, configure the CT1 interface to work
in slave clock mode. When the CT1 interfaces of two routers are directly connected, configure
one interface to work in master clock mode and the other in slave clock mode.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
The clock mode of the CT1 interface is configured.
----End
2.3.5 Configuring Frame Format of the CT1 Interface

CT1 interfaces support two types of frame formats, namely, SF and ESF.
Context
A CT1 interface supports the following frame formats:
l Extended Super Frame (ESF)

l Super Frame (SF)

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
frame-format { esf | sf }
Frame format of the CT1 interface is configured.

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

After a CT1 interface is configured, you can check the encoding and decoding format, clock
mode, and frame format.
Procedure
l Run the display interface serial [interface-number ] [ | { begin | exclude | include }
regular-expression ] command to check the status and statistics of the synchronous serial
interface formed by timeslot bundling.
l Run the display controller t1 [ controller-number ] command to check the configuration
and status of the CT1 interface.
----End
Example
Run the display interface serial command to view the channel-set configuration and interface
status.
Description : Serial1/0/0:2 Interface
Route 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 bps
LCP opened
Physical layer is Channelized T1
CRC: CRC-32
Scramble disabled
Alarm: None
Traffic statistics:


Run the display controller t1 command to view the encoding and decoding format, clock mode,
and frame format for the CT1 interface.
<HUAWEI> display controller t1 1/0/0
T1 1/0/0 current state : Administratively DOWN
Description : T1 1/0/0 Interface
clock master, no loopback
linecode b8zs, frame-format ESF
alarm:None
2.4 Configuring E3 Interfaces

You can create synchronous serial interfaces on CE3 interfaces; and you can also configure the
clock mode and national bit for the CE3 interfaces.

Before configuring CE3 interfaces, familiarize yourself with the usage scenario, complete the
Usage Scenario
Before using an E3 interface to carry upper layer services, configure parameters for the E3
interface.
NOTICE
l Disabling or enabling an E3 interface takes effect on the E3 channel and the serial interface
formed by the E3 interface.
Before configuring E3 interfaces, power on the router and conduct a successful self-check.
Data Preparation
To configure E3 interfaces, you need the following data.

No. Data
1 Number of the E3 interface on the router
2.4.2 Creating Synchronous Serial Interface for E3 Interface

On E3 interfaces, you must create synchronous serial interfaces before data transmission.
Context
E3 interfaces working in different modes can form synchronous serial interfaces with different
rates:
l When an E3 interface works in clear channel mode, an unframed synchronous serial

interface is formed with the transmission rate of 34.368 Mbit/s.
l When an E3 interface works in unchannelized mode, a framed E3 channel must be manually
created to form a synchronous serial interface.
By default, an E3 interface works in unchannelized mode.
Procedure
1. Run:
system-view

2. Run:
The E3 interface view is displayed.

3. Run:
using e3
The E3 interface is configured to work in clear channel mode, and a synchronous serial
interface in clear channel mode is created.
l Creating a synchronous serial interface in unchannelized mode
1. Run:
system-view

2. Run:
controller e3controller-number
The E3 interface view 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, and a synchronous serial interface in unchannelized

mode is created.
----End

After an E3 interface is configured, you can check the status and clock configuration of the
interface.
Procedure
Step 1 Run the display controller e3 [ controller-number ] command to check the status of the E3
interface.
----End
Example
Run the display controller e3 command to view the status and clock mode of the E3 interface.
<HUAWEI> display controller e3 1/0/0
E3 1/0/0 current state : DOWN
Description : HUAWEI, E3 1/0/0 Interface
Physical layer is Packet Over G.751
Alarm: LOS

You can create synchronous serial interfaces on CT3 interfaces; and you can also configure the
frame format for the CT3 interfaces.

Before configuring CT3 interfaces, familiarize yourself with the usage scenario, complete the
Usage Scenario
interface.

NOTICE
l Disabling or enabling a CT3 interface takes effect on the serial interface formed by the CT3
channel, T1 channel demultiplexed by the CT3 channel, and serial interface formed by
bundling the CT3 channel.
Before configuring CT3 interfaces, power on the router and conduct a successful self-check.
Data Preparation
To configure a CT3 interface, you need the following data.
No. Data
2.5.2 Creating Synchronous Serial Interface for CT3 Interface

On CT3 interfaces, you must create synchronous serial interfaces before data transmission.
Context
CT3 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 serial
interface 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 channelized
mode
– 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, a synchronous serial interface is
formed with the transmission rate of 1.544 Mbit/s and without timeslot division.
– When a T1 channel works in channelized mode, timeslots 0 to 23 of the T1 channel
can be randomly bundled together to form one or multiple synchronous serial
interfaces with the transmission rate of N x 64 kbit/s. N stands for the number of
bundled timeslots.

By default, a CT3 interface works in channelized mode.
Perform the following steps on the router:
Procedure
1. Run:
system-view

2. Run:

3. Run:
using t3
The CT3 interface is configured to work in clear channel mode. That is, a synchronous
serial interface is created with the transmission rate of 44.736 Mbit/s and without
timeslot division.
l Creating a synchronous serial interface in unchannelized mode
1. Run:
system-view

2. Run:

3. Run:
using ct3
The CT3 interface is configured to work in framed mode.

4. Run:
t3 framed
A framed T3 channel is created, and a synchronous serial interface in unchannelized

mode is created.
l Creating a synchronous serial interface in channelized mode
1. Run:
system-view

2. Run:


3. Run:
using ct3
The CT3 interface is configured to work in framed mode.

4. Run either of the following commands to create synchronous serial interfaces with
different rates.
– Run the t1 t1-number unframed command to create a synchronous serial interface
with the transmission rate of 1.544 Mbit/s.
You can run the interface serial controller-number/t1-number:0 command to
access the synchronous serial interface.
– Run the t1 t1-number channel-set set-number timeslot-list slot-list command to
bundle together N timeslots of the T1 channel of the CT3 interface to create a
synchronous serial interface with the transmission rate of N x 64 kbit/s.
You can run the interface serial controller-number/t1-number:set-number
command to access the synchronous serial interface.
----End
2.5.3 Configuring Frame Format of the CT3 Interface

The digital signal level of T1 channels is DS-1. 28 T1 channels form a T3 channel using bit
multiplexing. The frame format of a CT3 channel is either C-bit or M23.
Context
l C-bit is also called the C-bit parity check. When C-bit is set, the stuffing bit indicator in a
frame can be used for maintenance.
l M23 is the multiplexing process from DS-2 to DS-3. Four T1s (DS-1) are multiplexed as
a DS-2 line through M12. Seven DS-2 lines are multiplexed as T3 (DS-3) through M23.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
frame-format { c-bit | m23 }
The frame format of the CT3 interface is configured.
----End


After a CT3 interface is configured, you can check the frame format for the CT3 interface and
the status of the created synchronous serial interface.
Procedure
l 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
----End
Example
Run the display controller t3 command to view the status and clock mode of the CT3 interface.
T3 1/0/0 current state : DOWN
Description : HUAWEI, T3 1/0/0 Interface
Physical layer is Packet Over C-Bit
Alarm: LOS
Run the display interface serial command to view the status and configuration of the
<HUAWEI> display interface serial 1/0/0/0:0
Serial1/0/0/0:0 current state : UP
Description:Serial1/0/0/0:0 Interface
Derived from T3 1/0/0, Unchannelized mode, baudrate is 44210000 bps
LCP opened
clock slave, loopback none
CRC: CRC-16
Scramble disabled
Traffic statistics:
2.6 Configuring a T1 Channel of CT3 Interfaces

You can configure the clock mode and frame format for T1 channels of CT3 interfaces and
disable or enable T1 channels of the CT3 interfaces.

Before configuring T1 channels of CT3 interfaces, familiarize yourself with the usage scenario,
complete the pre-configuration tasks, and obtain the data required for the configuration.

Usage Scenario
interface. When a CT3 interface works in channelized mode, the T1 channel of the CT3 interface
needs to be configured.
Before configuring a T1 channel of the CT3 interface, complete the following tasks:
l Power on the router and conduct a successful self-check.

l Connect the CT3 interface and configure physical attributes for the CT3 interface.
l Connect the CT3 interface to work in 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.6.2 Configuring Clock Mode of a T1 Channel

A T1 channel works in either master clock mode or slave clock mode.
Context
A T1 channel works in either of the following clock modes:
l In master clock mode, a T1 channel uses internal clock signals.

l In slave clock mode, a T1 channel uses line clock signals.
The T1 clock mode can be selected according to the peer device that it connects to. If the peer
device is a transmission device, configuring the local device to work in slave clock mode is
recommended. If the T1 channels from two routers are directly connected, configure one channel
to work in master clock mode and the other in slave clock mode.
By default, a T1 channel works in master clock mode.
Procedure
Step 1 Run:
system-view

Step 2 Run:

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

You can change the frame format of a T1 channel.
Context
A T1 channel supports the following frame formats:
l Extended Super Frame (ESF)
l Super Frame (SF)
By default, the frame format of a T1 channel is ESF.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
t1 t1-number set frame-format { esf | sf }
Frame format of the T1 channel is configured.
----End

After T1 channels of CT3 interfaces are configured, you can check the T1 clock mode and frame
format.
Procedure
l 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

Example
Run the display controller t3 command. You can view the clock mode and frame format for
the CT3 interface.
T3 1/0/0 current state : DOWN
Description : HUAWEI, T3 1/0/0 Interface
Physical layer is Packet Over C-Bit
Alarm: LOS
Run the display interface serial command. You can view the status of the serial interface.
Serial1/0/0/1:0 current state : DOWN
Last line protocol up time : 2009-01-20
15:55:16
Derived from T3 1/1/0 t1 1, Timeslot(s) Used: 0-23, baudrate is 1536000 bps

LCP opened
CRC: CRC-16
Scramble disabled
Alarm: None
Traffic statistics:
2.7 Maintaining E-Carrier and T-Carrier Interface

Configuration
You can maintain E-carrier and T-carrier interfaces by enabling the loopback function to detect
whether an interface runs properly or by clearing interface statistics.
2.7.1 Configuring the Loopback Function to Detect the Link Status

You can configure the loopback function on an interface to detect whether the interface itself or
the link is working properly.

Context
NOTICE
After you configure the loopback function (by running the loopback command), the interface
on the router or the link will not run properly. Therefore, check whether to configure the loopback
function. After the link status detection is complete, run the undo loopback command to disable
the loopback function.
Perform the following steps on the routers to be detected:
Procedure
Step 1 Run:
system-view

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 loopback
function.
l To detect a CE1, CT1, E3 or CT3 interface, run the loopback { local | remote } command.
When configuring the loopback function on an interface, note the following:
– To enable local loopback on an interface, ensure that the interface works in master clock
mode.
– To enable remote loopback on an interface, ensure that the interface works in slave clock
mode.
l To detect the T1 channel of a CT3 interface, run the t1 t1-number set loopback { local |
remote } command.
By default, the loopback function is disabled on an interface.
----End

You can run the reset command to clear interface statistics.
Context
NOTICE
Interface statistics cannot be restored after you run the reset command to clear them. Exercise
caution when running the commands.

To clear interface statistics in the Network Management System (NMS), interface statistics
displayed using the display e1 controller e1 controller-number history command or interface
statistics displayed using the display interface command, run the following commands in the
user view. You need to clear traffic statistics on an interface before recollecting them on the
interface.
NOTE
See the relevant NMS manual to learn how to view interface traffic statistics on the NMS.
Procedure
l Run the reset counters interface [ interface-type [ interface-number ] ] command to clear
the interface statistics previously displayed using the display interface command.
l Run the reset counters if-mib interface [ interface-type [ interface-number ] ] command
to clear the interface statistics on the NMS.
l Run the reset count controller e1 controller-number command to clear the interface
statistics previously displayed using the display e1 controller e1 controller-number
history command.
l Run the reset counters controller [ controller-type [ controller-number ] | controller-
name ] command to clear the interface statistics.
----End

This section provides an example for configuring E-carrier and T-carrier interfaces. This
configuration example explains the networking requirements, configuration roadmap, data
preparation, configuration procedure, and configuration files.
2.8.1 Example for Configuring Communication over CE1 Interfaces

This example describes how to enable two routers to connect to and communicate with one
another via two CE1 interfaces with bundled timeslots.
Networking Requirements
NOTE
Examples in this document use interface numbers and link types of the NE40E-X8. In real world situations,
the interface numbers and link types may be different from those used in this document.
Two routers connect to each other through two CE1 links and communicate with each other by
using a bundled link.
Figure 2-1 Networking diagram for configuring communication over CE1 interfaces
Router A Router B
CE1 1/0/0 Link bundling CE1 1/0/0
CE1 1/0/1 CE1 1/0/1

Configuration Roadmap
The configuration roadmap is as follows:
1. Create a synchronous serial interface.

2. Create an MP-Group interface.
3. Add the synchronous serial interface to the MP-Group interface.
4. Configure an IP address for the MP-Group interface and restart the MP-Group interface.
Data Preparation
To configure a CE1 interface, you need the following data:
l Name of the MP-Group interface

l IP address of the MP-Group interface
l Index of the synchronous serial interface that is formed by bundling timeslots of a CE1
interface
l Number or range of the bundled timeslots
NOTE
l On the NE80E/40E, interfaces to be added to an MP-Group interface must have the same slot ID and
subcard number as those of the MP-Group interface. That is, interfaces on different subcards cannot
be bundled together.
l Only synchronous serial interfaces can be added to an MP-Group interface.
Procedure
Step 1 Configure Router A.
# Configure the working mode for a CE1 interface and create a synchronous serial interface.
<HUAWEI> system-view
[HUAWEI] sysname RouterA
[RouterA] controller e1 1/0/0
[RouterA-E1 1/0/0] shutdown
[RouterA-E1 1/0/0] channel-set 0 timeslot-list 1-31
[RouterA-E1 1/0/0] undo shutdown
[RouterA-E1 1/0/0] quit
[RouterA] controller e1 1/0/1
[RouterA-E1 1/0/1] shutdown
[RouterA-E1 1/0/1] channel-set 0 timeslot-list 1-31
[RouterA-E1 1/0/1] undo shutdown
[RouterA-E1 1/0/1] quit
# Create an MP-Group interface.

[RouterA] interface mp-group 1/0/1
[RouterA-Mp-group1/0/1] shutdown
[RouterA-Mp-group1/0/1] quit
# Add the synchronous serial interface to the MP-Group interface.

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

[RouterA-Serial1/0/1:0] ppp mp mp-group 1/0/1

# Restart the synchronous serial interface on Router A.

[RouterA] interface serial1/0/0:0
[RouterA-Serial1/0/0:0] undo shutdown
# Configure an IP address for the MP-Group interface and restart the MP-Group interface.
[RouterA] interface mp-group 1/0/1
[RouterA-Mp-group1/0/1] ip address 10.0.0.1 255.255.255.0
[RouterA-Mp-group1/0/1] undo shutdown
Step 2 Configure Router B.
# Configure the working mode for a CE1 interface and create a synchronous serial interface.
[HUAWEI] sysname RouterB
[RouterB] controller e1 1/0/0
[RouterB-E1 1/0/0] shutdown
[RouterB-E1 1/0/0] channel-set 0 timeslot-list 1-31
[RouterB-E1 1/0/0] undo shutdown
[RouterB-E1 1/0/0] quit
[RouterB] controller e1 1/0/1
[RouterB-E1 1/0/1] shutdown
[RouterB-E1 1/0/1] channel-set 0 timeslot-list 1-31
[RouterB-E1 1/0/1] undo shutdown
[RouterB-E1 1/0/1] quit
# Create an MP-Group interface.

[RouterB] interface mp-group 1/0/1
[RouterB-Mp-group1/0/1] shutdown
[RouterB-Mp-group1/0/1] quit
# Add the synchronous serial interface to the MP-Group interface.

[RouterB] interface serial 1/0/0:0
[RouterB-Serial1/0/0:0] shutdown
[RouterB-Serial1/0/0:0] ppp mp mp-group 1/0/1
[RouterB-Serial1/0/0:0] quit
[RouterB] interface serial 1/0/1:0
[RouterB-Serial1/0/1:0] ppp mp mp-group 1/0/1
# Restart the synchronous serial interface on Router B.

[RouterB] interface serial1/0/0:0
[RouterB-Serial1/0/0:0] undo shutdown
# Configure an IP address for the MP-Group interface and restart the MP-Group interface.
[RouterB] interface mp-group 1/0/1
[RouterB-Mp-group1/0/1] ip address 10.0.0.2 255.255.255.0
[RouterB-Mp-group1/0/1] undo shutdown

Step 3 Verify the configuration.
Run the display interface command to view the MP-Group interface status. The command
output shows that link negotiation is successful. That is, the two routers can communicate.
Use the display on Router A as an example:

<RouterA> display interface mp-group 1/0/1
Mp-group1/0/1 current state : UP
Description: Mp-group1/0/1 Interface
Route Port,The Maximum Transmit Unit is 1500
LCP opened, MP opened, IPCP opened
Physical is MP, baudrate is 3968000 bps
Traffic statistics:
0 errors, 0 drops
0 errors, 0 drops
----End
Configuration Files
l Configuration file of Router A
#
sysname RouterA
#
controller e1 1/0/0
channel-set 0 timeslot-list 1-31
#
controller e1 1/0/1
#
interface Serial1/0/0:0
link-protocol ppp
ppp mp Mp-group 1/0/1
#
link-protocol ppp
#
interface Mp-group1/0/1
ip address 10.0.0.1 255.255.255.0
#
return
l Configuration file of Router B

#
sysname RouterB
#
controller e1 1/0/0
#
controller e1 1/0/1
#
link-protocol ppp
#

link-protocol ppp
#
ip address 10.0.0.2 255.255.255.0
#
return

Configuration Guide - WAN Access 3 POS and CPOS Interface Configuration
3 POS and CPOS Interface Configuration
About This Chapter
The Packet over SONET/SDH (POS) technology is applied to MAN and WAN. CPOS interfaces
are channelized POS interfaces.
NOTE
POS interfaces and T1, E3, and T3 channels of the CPOS interfaces are not supported on the X1 and X2 models
of the NE80E/40E.
3.1 Introduction
POS supports packet transmission. CPOS makes full use of the SDH system.
3.2 Configuring POS Interfaces
You can configure the link layer protocol, clock mode, overhead byte, frame format, and CRC
for POS interfaces.
3.3 Configuring STM-1 CPOS Interfaces
Configuring a CPOS interface on a device effectively converges low-speed channels. An STM-1
CPOS is applicable where multiple E1 or T1 channels need to be converged.
3.4 Configuring an STM-4 CPOS Interface
Configuring an STM-4 CPOS interface on a device effectively converges low-speed channels.
STM-4 CPOS interfaces apply where multiple E1 or T1 channels need to be converged.
3.5 Configuring a CPOS-Trunk Interface
You can create a CPOS-Trunk interface, add CPOS interfaces to the CPOS-Trunk, and create
Trunk-Serial interfaces.
3.6 Configuring WDM Interfaces
This section describes how to configure WDM interfaces, including how to configure the FEC
modes of WDM interfaces, how to configure OTN FEC bit error rate detection, and how to
configure TTIs for OTNs and ODUs.
3.7 Configuring E1 Channels of the CPOS Interface
You can create synchronous serial interfaces for E1 channels, configure their frame format, clock
mode, and timeslot binding, and disable or enable the E1 channels.
3.8 Configuring T1 Channels of the CPOS Interface

You can create synchronous serial interfaces for T1 channels, configure their frame format and
clock mode, and disable or enable the T1 channels.
3.9 Configuring E3 Channels of an STM-1 CPOS Interface

You can create synchronous serial interfaces of E3 channels and configure the clock mode of
E3 channels.
3.10 Configuring T3 Channels of an STM-1 CPOS Interface

You can create synchronous serial interfaces of T3 channels and configure their frame format
and clock mode.
3.11 Configuring an AUG Interface on an STM-4 CPOS Interface

STM-4 CPOS interfaces are used to carry high-bandwidth services. Some services, however, do
not have high requirements on bandwidths. In this case, you can configure an AUG interface on
an STM-4 CPOS interface so that the AUG interface can be used to implement low-bandwidth
services.
3.12 Maintaining POS and CPOS Interface Configuration

To maintain POS and CPOS interfaces, you can enable the self-loop function to detect whether
an interface runs properly and to clear interface statistics.

This section describes the POS and CPOS interfaces in detail from the aspect of applicable
scenarios and configuration commands.

3.1 Introduction
POS supports packet transmission. CPOS makes full use of the SDH system.
3.1.1 Overview of POS and CPOS Interfaces

This section briefly describes POS and CPOS interfaces in terms of basic SONET and SDH
concepts, channelization and non-channelization, and the frame structure of SDH.
Introduction
Synchronous Optical Network (SONET) is the synchronous digital transmission standard

defined by the American National Standards Institute (ANSI). It is used in North America and
Japan.
SONET defines the line rate hierarchical structure of synchronous transmission for the optical
transmission system. The basic SONET transmission rate is 51.84 Mbit/s which approximately
equals the transmission rate of E3/T3. Clocks at each level in an entire network are provided by
a precise master clock.
l For an electrical signal, the transmission rate is called Level 1 Synchronous Transport
Signal, 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 numerous signals.
Based on SONET, Synchronous Digital Hierarchy (SDH) is an international standard defined

by the ITU-T and used in Europe. The corresponding standard for SDH (compared to SONET's)
is found in proposals G.707 to G.709 passed in 1988 and in additional proposals added in 1992.
SDH is similar to SONET to a great extent. The basic SDH rate is 155.52 Mbit/s, which is called
Level 1 Synchronous Transfer Module, or STM-1. This rate equals the OC-3 rate in SONET.
Utilizing synchronous multiplexing and flexible mapping, SDH can multiplex or demultiplex
low-speed tributary signals from SDH signals without using multiplexing or demultiplexing
devices. This reduces signal consumption and investment in additional equipment.
Table 3-1 lists the common transmission rates of SONET and SDH. The hierarchical relationship
between common transmission rates is four times. For convenience sake, the approximations,
shown here in parentheses, 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)
Electrical Optical Signal Optical Signal
Signal
STS-1 OC-1 - 51.840
STS-3 OC-3 STM-1 155.520 (155)

SONET SDH Transmission Rate

(Mbit/s)
Electrical Optical Signal Optical Signal
Signal
STS-9 OC-9 STM-3 466.560
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)
Channelization and Unchannelization

When SDH signals are formed by multiplexing low-speed tributary signals, they are called
channels.
Channelization indicates that multiple independent data channels are transmitted over an optical
fiber using low-speed tributary STM-N signals. During transmission, each channel has 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 fiber
using all STM-N signals. During transmission, all the data has the same ID and start and end
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, supporting
packet data, such as IP packets.
Making full use of the SDH system, Channelized POS (CPOS) interfaces have the following
functions:
l Perform refined division of bandwidth.

l Reduce the demand for the number 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

To facilitate understanding, the following section describes the frame structure of the SDH
signal, 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 distribute
tributary signals across the frame equably and regularly. The ITU-T standard regulates that STM-
N frames are rectangular and expressed in bytes, as shown in Figure 3-1.
Figure 3-1 STM-N frame structure
9*270*N(bytes)
1
Regenerator
2
Section
3
Overhead
4
5 AU-PTR Payload
6
Multiplex
7
Section
8
Overhead
9
9*N 261*N
STM-N is a frame with the dimension of 9 rows x 270 x N columns. Here, N is consistent with
that 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 Multiplex
Section Overhead (MSOH).
l Administration Unit Pointer (AU-PTR): functions as the pointer that specifies the first byte
of the payload. The receiving end extracts the payload according to the location of the
pointer.
l Payload
Related Concepts
l 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 the
number of the unit level.
l Container: It is used to carry service signals that are transmitted at different rates. G.709
defines specifications for five types of standard containers: C-11, C-12, C-2, C-3, and C-4.

l VC: supports connections between channel layers of the SDH and is an information
terminal for the SDH channels. VCs are classified into lower-order 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 multiplex
section layer. One AU and a set of multiple AUs, occupying a fixed position in the payload
of 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 multiplexing
path 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

Figure 3-3 Process of multiplexing T1 to STM-1
In application, different countries and regions may adopt different multiplexing paths. To ensure
mutual communication, the NE80E/40E provides the multiplex mode command on the CPOS
interface so that you can select the AU-3 or AU-4 multiplexing path.
Multiplexing AUG to STM-4

An STM-4 CPOS interface is used to carry services requiring a high interface bandwidth. Figure
3-2 and Figure 3-3 show only the multiplexing from E1 to STM-1 and T1 to STM-1,
respectively. To multiplex STM-1 to STM-4, you must create AUG interfaces on an ATM-4
CPOS interface. As shown in Figure 3-4, an STM-4 CPOS interface is channelized into AUG
interfaces (STM-1 level). Each AUG interface works independently and is channelized into a
serial interface for PPP services.
Figure 3-4 Process of multiplexing AUG to STM-4
Calculation of E1/T1 Path Sequence Number
CPOS interfaces adopt the multiplexing mode of byte interleave, so the lower-order VCs in a
higher-order VC are not arranged in sequence. To facilitate user configuration, the following
takes E1 in CPOS adopting AU-4 multiplexing path as an example to introduce the method for
calculating the TU number.

The multiplexing process in Figure 3-5 shows that the 2 Mbit/s multiplexing structure is 3-7-3
when the AU-4 multiplexing path is adopted. The following formula shows how to calculate the
numbers of TU-12s that are located in different positions in a VC-4:
TU-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; and the
difference between two TU-12 numbers is 1. These 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; and the TU-12 number
ranges 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 sequence
and also indicates the E1 channel number.
Figure 3-5 Sequence of arrangement of TUG-3, TUG-2 and TU-12 in VC-4
TU-12 1
1 1
VC-4 TUG-3 TUG-2 TU-12 2
TU-12 3
TU-12 1
2 2
TUG-3 TUG-2 TU-12 2
. 3
.. TU-12
..
.
TU-12 1
3 7
TUG-3 TUG-2 TU-12 2
TU-12 3
When the AU-3 multiplexing path is adopted, the calculation of the TU-12 number can be
deduced in a similar manner.
When 63 E1 channels or 84 T1 channels are configured on a CPOS interface, these channels

can be directly numbered from 1 to 63 or 1 to 84. If a router of Huawei is connected to a
channelized STM-1 interface of a router from another vendor, note differences in channel
numbers.

Overhead Bytes
SDH provides monitoring and management in layers. Monitoring is classified into section
monitoring and path monitoring. Section monitoring is classified into regenerator section
monitoring and multiplex section monitoring. Path monitoring is classified into higher-order
path monitoring and lower-order path monitoring. Different overhead bytes help to implement
the monitoring functions.
NOTE
This section describes only some SDH overhead bytes used in a configuration. For details, refer to any
book about 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 transmit
the Section Access Point Identifiers (SAPIs) repeatedly to check the connection between
the receiver and the transmitter. The byte can be any character in the carrier network, but
the J0 byte of the receiver and the transmitter must match each other at the network border.
Using the JO byte, a carrier can locate and rectify faults in advance to speed up network
recovery.
l Path overhead
SOH monitors section layers, whereas POH monitors path layers. POH is classified into
lower-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 the
receiver and the transmitter. The J1 bytes from the receiver and the transmitter must match
each other.
C2, the path signal label byte, is contained in the higher-order path overhead. C2 is used
to specify the multiplexing structure and the attributes of the information payload in a VC
frame, including whether the path is loaded with services, service types, and/or the mapping
mode. The C2 bytes from the receiver and the transmitter must match each other.
3.1.2 Features of POS and CPOS Interfaces on the NE80E/40E

Ordinary POS interfaces can work at any of three rates; CPOS interfaces can be channelized
into E1, T1, E3, and T3 channels.
POS
NOTE
POS interfaces are not supported on the X1 and X2 models of the NE80E/40E.
POS can map packets of variable length directly into the payload of SONET/SDH. POS uses
the physical layer transmission standard of SONET/SDH. This offers a high speed, reliable, and
P2P data connection.

The NE80E/40E provides various rates of POS interfaces, which can be divided into three kinds
based on the rate: OC-3/STM-1 (155 Mbit/s), OC-12/STM-4 (622 Mbit/s), OC-48/STM-16 (2.5
Gbit/s), and OC-192/STM-64 (10 Gbit/s).
The NE80E/40E provides various rates of POS interfaces, which can be divided into three kinds
based on the rate: STM-1 (155 Mbit/s), STM-4c (622 Mbit/s), STM-16c (2.5 Gbit/s), STM-64c
(10 Gbit/s), and STM-256c (40 Gbit/s).
CPOS Interfaces on the X1 and X2 models of the NE80E/40E

CPOS is used to improve aggregation capacity of the router during low speed access. STM-1
CPOS is suitable for aggregating multiple E1s.
The physical port of the STM-1 CPOS interface, which is called a controller, is not used as a
service port. E1 channels are used as synchronous serial interfaces and are configured in serial
interface view. The indexing method of the interface number is a 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)
NOTE
The channelization type STM-1 CPOS should assume the specifications of the service board as standard.
The NE80E/40E only allows the channels on the same service board to be bundled to be a
bundling group, and the bundling group is numbered from 1.
The link layer protocols of the channelized E1 on the X1 and X2 models of the NE80E/40E are
as follows:
Table 3-2 Link layer conditions of the E1 supported by the X1 and X2 models of the NE80E/
40E
Channel Link Layer Protocol MP Bundling
E1 PPP, ATM and TDM Supported
The working modes of the E1 channels supported by the X1 and X2 models of the NE80E/
40E are as follows:
Table 3-3 Working modes of the E1/T1/E3/T3 channels supported by the X1 and X2 models of
the NE80E/40E
Channel Unframed Framed
Unchannelized Channelized
E1 The serial interface Not supported Timeslots 1 to 31, timeslots 1 to

with rate 2.048 Mbit/ 15, and timeslots 17 to 31 can
s be bundled

CPOS Interfaces on the other models of the NE80E/40E

CPOS is used to improve aggregation capacity of the router during low speed access. STM-1
CPOS is suitable for aggregating multiple E1/T1s.
The physical port of the STM-1 CPOS interface, which is called a controller, is not used as a
service port. E1/T1/E3/T3 channels are used as synchronous serial interfaces and are configured
in serial interface view. The indexing method of the interface number is a 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 84 T1 channels (1.544M, DS-1)
l 3 T3 channels (44.736M, DS-3)
NOTE
The channelization type STM-1 CPOS should assume the specifications of the service board as standard.
The NE80E/40E only allows the channels on the same service board to be bundled to be a
bundling group, and the bundling group is numbered from 1.
The link layer protocols of the channelized E1/T1/E3/T3 are as follows:
Table 3-4 Link layer conditions of the E1/T1/E3/T3 supported by the NE80E/40E
Channel Link Layer Protocol MP Bundling
E1 PPP, HDLC ATM and Supported

TDM
T1 PPP, HDLC ATM and Supported

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

Table 3-5 Working modes of the E1/T1/E3/T3 channels supported by the NE80E/40E
Channel Unframed Framed
Unchannelized Channelized
E1 The serial interface Supported 32 timeslots can be bundled as the

with rate 2.048 Mbit/s 32 timeslots can serial interfaces of N x 64 Kbit/s,
be bundled as a N<32
serial interface of
N × 64 kbit/s
(N=32).
T1 The serial interface Supported 24 timeslots can be bundled as the

with rate 1.544 Mbit/s 24 timeslots can serial interfaces of N x 64 Kbit/s,
be bundled as a N<24
serial interface of
N × 64 kbit/s
(N=24).
E3 The serial interface The rate is 33.831 Not supported

with rate 34.368 Mbit/ Mbit/s
s
T3 The serial interface The rate is 44.210 Not supported

with rate 44.736 Mbit/ Mbit/s
s
3.1.3 Description of SDH Alarms on POS Interfaces

Table 3-6 Description of SDH alarms on POS interfaces
Alarm Explanation Description Layer
Signal loss in the Section

receiving direction. A
LOS alarm is generated in
the following scenarios:
l The optical module
LOS Loss of Signal transmitter on the
remote end becomes
faulty.
l The optical channel is
interrupted in the
receiving direction.

A POS interface enters Section

OOF status after the
OOF Out of Frame interface receives five
consecutive frames that
cannot be resolved.
A POS interface enters Section

LOF Loss of Frame LOF status after being in
OOF status for 3 ms.
If the STE detects a fault Line

on the section layer, a
LAIS alarm is generated
Line Alarm Indication by a Section Terminating
LAIS
Signal Equipment (STE) and
sent to the downstream
Line Terminating
Equipment (LTE).
If the remote device Line

detects a fault at the line
Line Remote Defect
LRDI layer, an LRDI alarm is
Indication
generated and sent to a
local device.
A local device detects a Line

B2 check error at the
Line Remote Error
LREI remote line layer, and the
Indication
number of remote B2
error codes increases.
If the LTE detects a fault Path

on the line layer, a PAIS
alarm is generated by an
Path Alarm Indication
PAIS LTE and sent to the
Signal
downstream Path
Terminating Equipment
(PTE).
If the remote device Path

detects a fault at the path
Path Remote Defect layer, a PRDI alarm is
PRDI
Indication generated by a remote
device and sent to a local
device.
A local device detects a Path

B3 check error at the
Path Remote Error
PREI remote path layer, and the
Indication
number of remote B3
error codes increases.

A LOP alarm is generated Line

if a POS interface
LOP Loss of Pointer receives eight
consecutive frames
carrying invalid pointers.
C2 bytes on the sending Path

Path Payload Label
PPLM and receiving ends are
Mismatch
inconsistent.
PUNE Path Unequipped Path

A C2 byte is 0.
Q Indication
An SD alarm is generated Line

if the B2 bit error rate
exceeds the alarm
SD Signal Degrade
threshold in the receiving
direction. By default, the
alarm threshold is 10–6.
An SF alarm is generated Line

if the B2 bit error rate
exceeds the alarm
SF Signal Fail
threshold in the receiving
direction. By default, the
alarm threshold is 10–3.
A B3TCA alarm is Path

generated if the B3 bit
error rate exceeds the
B3TC B3 Threshold Crossing
alarm threshold in the
A Alarm
receiving direction. By
default, the alarm
–6
threshold is 10 .
3.2 Configuring POS Interfaces

You can configure the link layer protocol, clock mode, overhead byte, frame format, and CRC
for POS interfaces.
3.2.1 Establishing the Configuration Task

Before configuring POS interfaces, familiarize yourself with the usage scenario, complete the
Usage Scenario
Before using a SONET/SDH optical interface to bear packet data, configure the parameters of
the POS interface.

Before configuring a POS interface, power on the router and start it normally.
Data Preparation
To configure a POS interface, you need the following data.
No. Data
1 Number of the POS interface on the router
2 Link layer protocol
3 Clock mode
4 Values of overload bytes C2, J0, and J1
5 Frame format
6 Length of the CRC check character
7 MTU
8 Alarm threshold
3.2.2 Configuring a Link Layer Protocol

The link layer protocol for POS interfaces can be PPP, HDLC, FR, IETF, or Nonstandard.
Procedure
Step 1 Run:
system-view
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 specified.
NOTE
The POS interface only supports the basic functions of FR P2P sub-interfaces.
----End

3.2.3 Configuring a Clock Mode

A POS interface works in either master or slave clock mode. Configure different clock modes
for POS interfaces that function as Data Terminal Equipment (DTE) device and Data Circuit-
terminating Equipment (DCE) devices.
Context
A POS interface supports the following clock modes:
l Master clock mode: uses internal clock signals.

l Slave clock mode: uses line clock signals.
Similar to a synchronous serial interface working in DTE or DCE mode, a POS also works in
DTE or DCE mode.
l Clocks modes on the POS interfaces of two directly connected routers must be both set to
master, or on one end set to master and the other end set to slave.
l If two routers are connected over a WDM transmission device, clocks modes on the POS
interfaces of the two interconnected devices must be both set to master.
l If an SDH or SONET device is deployed in the intermediate of two interconnected
routers, clock modes on the POS interfaces of the two devices must be both set to slave to
trace clock signals of the SDH or SONET device.
l When the POS interface of a router, which functions as a DTE, is connected to a switching
device that functions as a DCE and uses internal clock signals, configure the POS interface
to work in slave clock mode.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
A clock mode is specified for the POS interface.
By default, a POS interface works in master clock mode.
----End
3.2.4 Configuring the Overhead Byte

SONET/SDH provides a variety of overhead bytes. You can configure overhead bytes for POS
interfaces to implement monitoring at different levels.

Context
SONET/SDH provides a variety of overhead bytes, which perform the monitoring function at
different levels.
C2 (path signal label byte) is included in higher order path overhead. C2 designates the multiplex
structure of VC frame and the property of information payload.
J0 (Regeneration section Trace Message) is included in section overhead. It is used to test the
continuous connection of the two ports at the section level.
J1 (Higher-Order VC-N path trace byte) is used to test the connectivity of two interfaces.
Procedure
Step 1 Run:
system-view
Step 2 Run:
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 the 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), and the default value of J0 and J1
is "NetEngine".
----End
3.2.5 Configuring Frame Format

The frame format of an interface determines its application mode. POS interfaces support two
frame formats, namely, SDH and SONET.
Context
A POS interface supports the following types of frame formats:
l SDH

l SONET
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
frame-format { sdh | sonet }
The frame format of the POS interface is configured.
By default, the frame format of a POS interface is SDH.
----End
3.2.6 Configuring the Scramble Function

POS interfaces support the scrambling function for the payload data to prevent the excessive
number of consecutive 1s or 0s and help the receiver extract line clock signals.
Context
The directly connected interfaces must have the same scrambling function.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
scramble
The scrambling function of the payload is configured on the POS interface.
By default, the scrambling function is enabled on the payload.
----End
3.2.7 Configuring the Length of the CRC Check Character

POS interfaces support the CRC check character in either 16 or 32 bits.

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
crc { 16 | 32 }
The length of the CRC check character is set for the POS interface.
By default, the 32-bit CRC check character is used.
NOTE
The 10G POS interfaces do not support this configuration.
----End
3.2.8 Configuring MTU

The MTU is used to assemble and disassemble packets on a POS interface when packets are
sent and received on an interface using the IP network protocol.
Context
A router fragments and reassembles the sent and received packets based on the MTU.
NOTICE
After changing the interface MTU using the mtu command, run the shutdown and undo
shutdown commands to restart the interface to make the configuration take effect.
Procedure
l Configure the IPv4 MTU.
1. Run:
system-view

2. Run:

3. Run:
mtu mtu
The IPv4 MTU of the POS interface is set.

The MTU is expressed in bytes, and its value ranges from 46 to 9600. By default, the
MTU is 4470 bytes. If the MTU values of the interfaces at both ends of the link are
different, the smaller MTU value is used as the MTU of the link.
l Configure the IPv6 MTU.
1. Run:
system-view

2. Run:

3. Run:
ipv6 mtu mtu
The IPv6 MTU of the POS interface is set.
The MTU is expressed in bytes, and its value ranges from 1280 to 9660. By default,
the MTU is 4470 bytes. If the MTU values of the interfaces at both ends of the link
are different, the smaller MTU value is used as the MTU of the link.
NOTICE
After configuring the IPv6 MTU, run the ppp mru-negotiate ipv6 command to start
the negotiation of the IPv6 MTU.
----End
3.2.9 Configuring the Speed of a POS Interface

POS interfaces working at different speeds transmit different volumes of data during the same
period of time. Correctly configuring speeds of POS interfaces is a prerequisite to network
communication.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:

speed { 155 | 622 }
The speed on the POS interface is configured.

The NE80E/40E POS interface supports two kinds of operating speed: 155Mbit/s and 622Mbit/
s.
By default, the 622 mode is adopted.
You can specify the operating speed of an interface manually. Do keep the rate the same as that
of the peer device.
----End

After a POS interface is configured, you can check the link layer protocol, clock mode, and
overhead bytes of the interface.
Procedure
l Run the display interface pos [ interface-number ] [ | { begin | exclude | include } regular-
expression ] command to check the configuration and status of the POS interface.
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
Example
Run 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/0
Pos1/0/0 current state : UP
Description : Pos1/0/0 Interface
Route Port,The Maximum Transmit Unit is 4470 bytes, Hold timer is 10(sec)
The Vendor Name is FINISAR CORP. , The Vendor PN is FTLF1321P1BTL-HW
Transceiver BW: 2.5G, Transceiver Mode: Single Mode
WaveLength: 1310nm, Transmission Distance: 2km
Rx Optical Power: -40.00dBm, Tx Optical Power: -40.00dBm
Physical layer is Packet Over SDH,
Scramble enabled, clock master, CRC-32, loopback: none
Flag J0 "NetEngine "
Flag 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


Run the display interface brief [ | { begin |include |exclude } regular-expression ] command.
If the command output shows the brief information about the physical status, link protocol status,
bandwidth utilization, and the number of the error packets, it means that the configuration has
succeeded. For example:
<HUAWEI> display interface brief | include Pos
^down: standby
(l): loopback
(s): spoofing
(b): BFD down
(d): DampeningSuppressed
Interface Physical Protocol InUti OutUti inErrors/ outErrors
Pos1/0/0 down down 0% 0% 831745956 0
Pos2/0/0 up up 0.01% 0.01% 3795064053 0
Pos2/0/1 down down 0% 0% 343911292 0
Pos2/0/2 down down 0% 0% 343913408 0
Pos2/0/3 down down 0% 0% 343915353 0
Run the display pos interface command, you can view detailed information about the physical
layer. For example:
<HUAWEI> display pos interface pos 1/0/0
Pos1/0/0 current state:DOWN
Line protocol current state:DOWN
Physical layer is Packet Over SDH
SDH alarm:
section layer: OOF LOF LOS
line layer: none
path layer: PAIS PRDI
SDH error:
section layer: B1 306207965
line layer: B2 39944626237 REI 9861843785
path layer: B3 1641810669
Last 30 seconds input rate 0 Bits/sec, 0 packets/sec
Last 30 seconds output rate 0 Bits/sec, 0 packets/sec
SFP Transp information:
The Vendor PN is FTRJ1321P1BTL
The Vendor name is FINISAR CORP.
address : 3 4 5 6 7 8 9 10 12 14 15 16 17 18 60 61
value(hex): 0 1 22 2 12 10 1 5 19 5 32 0 0 0 5 1e
Port BW: 2.5G, Transceiver max BW: 2.5G, Transceiver Mode: SingleMode
PIC Packet Statics Per Sencond:
Rxd:
0x0 Packets
0x0 FCS
0x0 Receiv Abort Packets
0x0 Long Packets
0x0 Short Packets
Txd:
0x0 Packets
0x0 Send Abort Packets

SDH OverHead:
Rx C2 Flag : Unknown, Tx C2 Flag : 0x16.
Rx J0 ASCII :
Rx J0 Flag: Unknown
Rx J1 ASCII :
Rx 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 Interfaces

Configuring a CPOS interface on a device effectively converges low-speed channels. An STM-1
CPOS is applicable where multiple E1 or T1 channels need to be converged.

Before configuring CPOS interfaces, familiarize yourself with the usage scenario, complete the
Usage Scenario
Configure parameters for the CPOS interface before using an SONET/SDH optical interface to
bear packet data and before using low-speed ports for access.
Before configuring a CPOS interface, power on the router and start it normally.
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 for the CPOS interface
3.3.2 Configuring Clock Mode

A CPOS interface works in either master clock or slave clock mode. Configure the clock mode
for the CPOS interface according to the type of link device.
Context
A CPOS interface supports the following clock modes:

When a CPOS interface is connected to a SONET/SDH device, configure the CPOS interface
to work in slave clock mode because the precision of the clock in the SONET/SDH network is
higher than the precision of the internal clock source of the CPOS interface.
When CPOS interfaces are connected directly through optical fiber or a Wavelength Division
Multiplexing (WDM) device, configure one interface to work in master clock mode and the
other interface in slave clock mode.
Procedure
Step 1 Run:
system-view
Step 2 Run:
controller cpos cpos-number
The CPOS interface view is displayed.
Step 3 Run:
Clock mode of the CPOS interface is configured.
By default, a CPOS interface works in master clock mode.
NOTE
Before you configure a CPOS interface on the 8-port or 4-port channelized OC-3c/STM-1c flexible card
to work in slave clock mode, ensure that the local clock synchronizes with the remote clock. If the local
clock and remote clock are not synchronized, clock abnormalities may occur and therefore affect services.
----End

The frame format of an interface determines the interface application mode. A CPOS interface
supports two frame formats, namely, SDH and SONET.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:

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 is
SONET.
----End

SONET/SDH provides a variety of overhead bytes. You can configure overhead bytes for CPOS
Context
SONET/SDH provides a variety of overhead bytes, which perform the monitoring function at
different levels.
C2 is used to indicate the multiplex structure of VC frames and information payload properties.
J0 is a section overhead byte which is used to detect the connectivity of two ports on the section
layer.
J1 is a higher order path overhead byte which is used to detect the connectivity of two ports on
the path layer.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Perform the following as required.

l To configure the regeneration section trace message J0, run:
flag j0 { sdh | sonet } j0
For 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".
flag j1 j1
By default, the value of J1 is "NetEngine".

l To configure the path signal label byte C2, run:

flag c2 c2
C2 is used for international interconnections and 0x02 is used in China. By default, C2 is 02

(in the hexadecimal system).
flag j2 { 1byte-mode | 16byte-mode } j2 e1-list
NOTE
The C2, J0, J2, on both the receiving and the sending ends must be consistent; otherwise, an alarm is
generated.
----End
3.3.5 Configuring AUG Multiplexing Route

In SDH, the payload has two mapping/multiplexing schemes.
Context
l In 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 multiplexed into
an AUG.
l In ETSI multiplexing, the lower-order payload is aggregated into the VC-4 higher-order
path. An AU-4 consists of a VC-4 and an AU pointer. An AU-4 is multiplexed into an
AUG.
By default, an AU-4 is multiplexed into an AUG.
Procedure
Step 1 Run:
system-view
Step 2 Run:
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 command
only 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 on
other types of STM-1 CPOS interface boards.
----End

After a CPOS interface is configured, you can check the clock mode, frame format, overhead
byte, and AUG multiplexing path of the interface.
Procedure
Step 1 Run the display controller cpos [ cpos-number ] command to check information about all
channels of the CPOS interface.
Step 2 Run the display poh controller cpos cpos-number [ e1 e1-number ] command to check
information about POH of a specified CPOS interface.
----End
Example
You can view information about the clock, frame format, and multiplexing path by checking
information about the STM-1 CPOS interface.
<HUAWEI> display controller cpos 1/0/0
Cpos1/0/0 current state : UP
Description : Cpos1/0/0 Interface
The Vendor Name is AGILENT
The Vendor PN is QFCT-5736TP
Port BW: 155M, Transceiver max BW: 155M, Transceiver Mode: SingleMode
WaveLengh: 1310nm, Transmission Distance: 15km

clock master, Multiplex AU-4, loopback none
TX:Flag J0: "NetEngine ", Flag J1: "NetEngine ", Flag C2: 2(0x2)
RX:Flag J0: "NetEngine ", Flag J1: "NetEngine ", Flag C2: 2(0x2)
section layer:
alarm: none
error: B1 0
line layer:
alarm: none
error: B2 0 REI 0
path layer:
alarm: none
error: B3 0 REI 0
3.4 Configuring an STM-4 CPOS Interface

Configuring an STM-4 CPOS interface on a device effectively converges low-speed channels.
STM-4 CPOS interfaces apply where multiple E1 or T1 channels need to be converged.

Before configuring a CPOS interface, familiarize yourself with the usage scenario, complete the

Usage Scenario
Configure parameters for a CPOS interface before using the interface to carry packet data and
to provide access for low-speed interfaces.
Before configuring a CPOS interface, power on the router and ensure that it starts up normally.
Data Preparation
To configure a CPOS interface, you need the following data.
No. Data
2 Number of an AUG interface on the CPOS interface
3 Overhead bytes C2 and J1 for the CPOS interface
3.4.2 Configuring the Clock Mode

A CPOS interface works in either master clock or slave clock mode. Configure the clock mode
for the CPOS interface according to the type of link device.
Context
A CPOS interface supports the following clock modes:

When a CPOS interface is connected to a SONET/SDH device, configure the CPOS interface
to work in slave clock mode because the precision of the clock in the SONET/SDH network is
higher than the precision of the internal clock source of the CPOS interface.
When CPOS interfaces are connected directly through optical fiber or a Wavelength Division
Multiplexing (WDM) device, configure one interface to work in master clock mode and the
other interface in slave clock mode.
Procedure
Step 1 Run:
system-view
Step 2 Run:

Step 3 Run:
Clock mode of the CPOS interface is configured.
By default, a CPOS interface works in master clock mode.
NOTE
Before you configure a CPOS interface on the 8-port or 4-port channelized OC-3c/STM-1c flexible card
to work in slave clock mode, ensure that the local clock synchronizes with the remote clock. If the local
clock and remote clock are not synchronized, clock abnormalities may occur and therefore affect services.
----End

SDH provides a variety of overhead bytes. You can configure overhead bytes for CPOS
Context
SDH provides a variety of overhead bytes, which perform the monitoring function at different
levels.
J0 is a section overhead byte which is used to detect the connectivity of two ports on the section
layer.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
flag j0 sdh j0
The regeneration section trace message J0 isconfigured.
NOTE
The J0 on both the receiving and the sending ends must be consistent; otherwise, an alarm is generated.
----End

3.4.4 Configuring an Overhead Byte for an AUG Interface Created

on a CPOS Interface
SONET/SDH provides a variety of overhead bytes. The overhead bytes configured for an AUG
interface created on a CPOS interface can be used to perform the monitoring function at different
levels.
Context
SONET/SDH provides a variety of overhead bytes, which can be used to perform the monitoring
function at different levels.
C2 (path signal label byte) is included in higher order path overhead. C2 designates the multiplex
structure of VC frame and the property of information payload.
J1 (Higher-order VC-N path trace byte) is used to test the connectivity between two interfaces.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the specified CPOS interface is displayed.

Step 3 Run:
aug aug-number
An AUG interface is created on the STM-4 CPOS interface.

Step 4 Run:
controller aug controller-number
The view of the specified AUG interface is displayed.

Step 5 Run:
flag { j1 { 1byte-mode | 16byte-mode | 64byte-mode } j1 | j1 c2 }
An overhead byte is configured on the AUG interface created on the STM-4 CPOS interface.
NOTE
The C2, J0 on both the receiving and the sending ends must be consistent; otherwise, an alarm is generated.
----End

After configuring an STM-4 CPOS interface, verify the configuration result, including whether
the overhead byte is correctly configured and whether an AUG interface is correctly configured
on the CPOS interface.

Procedure
Step 1 Run the display controller aug [ controller-number ] command to check information about an
AUG interface.
Step 2 Run the display controller cpos [ cpos-number command to check CPOS interface information.
----End
Example
Run the display controller aug [ controller-number ] command. The command output shows
information about the AUG interface.
<HUAWEI> display controller aug 1/0/0:1
AUG1/0/0:1 current state :
UP
Description : HUAWEI, AUG1/0/0:1

Interface
Multiplex AU-4, loopback

none
TX:Flag J1: "0

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

",
Flag C2: 2
(0x2)
path
layer:
alarm:
none
error: B3 4547 REI 0
Run the display controller cpos [ cpos-number ] command. The command output shows
information about the CPOS interface.
Description : HUAWEI, Cpos1/0/0 Interface
The Vendor PN is FTRJ1319P1BTL
The Vendor Name is FINISAR CORP.
Port BW: 622M, Transceiver max BW: 1G, Transceiver Mode: SingleMode
Rx Power: -2.70dBm, Warning range: [-20.00, -1.00]dBm
Tx Power: -4.68dBm, Warning range: [-11.50, -1.00]dBm
clock slave, Multiplex AU-4, loopback none
TX:Flag J0: "NetEngine ",
RX:Flag J0: "NetEngine ",
section layer:
alarm: none
error: B1 0
line layer:
alarm: none
error: B2 35670 REI 0

3.5 Configuring a CPOS-Trunk Interface

You can create a CPOS-Trunk interface, add CPOS interfaces to the CPOS-Trunk, and create
Trunk-Serial interfaces.

Before configuring a CPOS-Trunk interface, familiarize yourself with the usage scenario,
Usage Scenario
After bundling CPOS interfaces to create a CPOS-Trunk interface, you can configure automatic
protection switching (APS) on the CPOS-Trunk interface.
Before creating a CPOS-Trunk interface, power on the router and ensure that the router detects
no error during self-check.
Data Preparation
To configure a CPOS-Trunk interface, you need the following data.
No. Data
1 Number of a CPOS-Trunk interface on the router
2 Channel number and timeslot number
3.5.2 Creating a CPOS-Trunk Interface and Adding CPOS

Interfaces to the CPOS-Trunk
A CPOS-Trunk interface is created and CPOS interfaces are added to the CPOS-Trunk.
Context
In a scenario where automatic protection switching (APS) is configured to protect services,
CPOS interfaces must be added to a CPOS-Trunk interface so that services can be carried on a
Trunk-Serial interface channelized from the CPOS-Trunk interface.
Procedure
Step 1 Create a CPOS-Trunk interface.
1. Run:
system-view


2. Run:
interface cpos-trunk trunk-id
A CPOS-Trunk interface is created. If the CPOS-Trunk interface exists, the view of the
existing CPOS-Trunk interface is displayed.
3. Run:
quit

Step 2 Add CPOS interfaces to the CPOS-Trunk interface.
1. Run:
system-view

2. Run:
The view of the specified CPOS interface is displayed.

3. Run:
cpos-trunk trunk-id
The CPOS interface is added to the CPOS-Trunk.
NOTE
l To guarantee that CPOS member interfaces of a CPOS-Trunk interface have sufficient bandwidth
to carry CEP services, run the using vc4 command on the CPOS member interface to enable it
to work in VC4 clear channel mode.
l After a CPOS interface is added to a CPOS-Trunk interface, the CPOS interface will undergo
status changes according to the command run on the CPOS-Trunk interface.
l If you run the shutdown command on the CPOS-Trunk interface, the physical status of both
the CPOS-Trunk interface and its member interface becomes Administratively DOWN, and
the configuration file of the member interface displays shutdown automatically.
l If you run the undo shutdown command on the CPOS-Trunk interface, the configuration
file of the member interface displays undo shutdown automatically.
----End
3.5.3 Creating a Trunk-Serial Interface

You can configure an E1 channel or a T1 channel to work in clear channel mode or bundle
timeslots of the channel to create a Trunk-Serial interface.
Context
In a scenario where automatic protection switching (APS) is configured to protect services, the
services must run on a Trunk-Serial interface channelized from a CPOS-Trunk interface. A
Trunk-Serial interface is created using either of the following methods which can be flexibly
chosen by users based on their needs.
NOTE
The member interface of the CPOS-Trunk must be added to an APS Group, or the Trunk-Serial interface
created by the CPOS-Trunk will not be Up.

Procedure
l Configure an E1 channel of a CPOS-Trunk interface.
– Configure an E1 channel to work in clear channel mode.

1. Run:
system-view

2. Run:
The CPOS-Trunk interface view is displayed.

3. Run:
e1 e1-number unframed
An E1 channel of a CPOS-Trunk interface is configured to work in clear channel

mode.
– Bundle timeslots.
1. Run:
system-view

2. Run:

3. Run:
e1 e1-number channel-set set-number timeslot-list [ slot-list | ts0 ]
Timeslots of an E1 channel of the CPOS-Trunk interface are bundled, and a Trunk-

Serial interface is created.
l Configure a T1 channel of a CPOS-Trunk interface.
– Configure a T1 channel to work in clear channel mode.
1. Run:
system-view

2. Run:

3. Run:
working-mode t1
The working mode of the CPOS-Trunk interface is set to T1.

4. Run:
t1 t1-number unframed
A T1 channel of the CPOS-Trunk interface is configured to work in clear channel

mode, and a Trunk-Serial interface is created.
– Bundle timeslots.
1. Run:

system-view

2. Run:

3. Run:
working-mode t1
The working mode of the CPOS-Trunk interface is set to T1.

4. Run:
t1 t1-number channel-set set-number timeslot-list slot-list
Timeslots of a T1 channel of the CPOS-Trunk interface are bundled, and a Trunk-

Serial interface is created.
l Configure a CPOS-Trunk interface (including E1 and T1 channels) to work in VC4 clear
channel mode.
1. Run:
system-view

2. Run:

3. Run:
using vc4
The CPOS-Trunk interface is configured to work in VC4 clear channel mode, and a
Trunk-Serial interface is created.
----End

After the configurations of a CPOS-Trunk interface are complete, you can view its
configurations and status.
Prerequisites
A CPOS-Trunk interface has been configured.
Procedure
l Run the display cpos-trunk trunk-id command to check detailed information of the CPOS-
Trunk interface.
l Run the display interface trunk-serial interface-number command to check detailed
information of the Trunk-serial interface.
----End

Example
Run the display cpos-trunk trunk-id command to view detailed information of the CPOS-Trunk
interface.
<HUAWEI> display cpos-trunk 1
Interface Cpos-Trunk1's state information is:,
Operate status: up Number Of Up Port In Trunk: 2
--------------------------------------------------------------------------------
PortName Status Active Status
Cpos3/0/0 Up Inactive
Cpos2/2/0 Up Active
Run the display interface trunk-serial command to view detailed information of the Trunk-
serial interface.
<HUAWEI> display interface trunk-serial 1/0:0
Trunk-Serial1/1:0 current state : Administratively DOWN
Line protocol current state : DOWN
Description:HUAWEI, Trunk-Serial1/1:0 Interface
Derived from Cpos-Trunk1 e1 1, Unframed mode, baudrate is 2048000 bps
Physical is TRUNK_SERIAL
Current system time: 2012-08-16 10:26:31
Framer LOS Alarm Status(0-NONE 1-ALARM): 1
Framer LOF Alarm Status(0-NONE 1-ALARM): 0
Framer PAIS Alarm Status(0-NONE 1-ALARM): 0
Framer PRDI Alarm Status(0-NONE 1-ALARM): 0
PSN2TDM PW Alarm status(0-NONE 1-RDI 2-AIS): 0
Traffic statistics:
Input: 0 packets
Output:0 packets
0 underrun count, 0 overrun count
0 misorder packets, 0 malformed packets
0 los packets
ES: 0, SES: 0, UAS: 0
Input bandwidth utilization : 0%
Output bandwidth utilization : 0%
3.6 Configuring WDM Interfaces

This section describes how to configure WDM interfaces, including how to configure the FEC
modes of WDM interfaces, how to configure OTN FEC bit error rate detection, and how to
configure TTIs for OTNs and ODUs.

Before configuring WDM interfaces, familiarize yourself with the usage scenario, complete the
pre-configuration tasks, and obtain the required data.
Usage Scenario
When using the SONET/SDH optical interface to transmit packets, you need to configure POS
interface parameters.

Before you configure WDM interfaces, ensure that the router has been powered on and passed
the self-check.
Data Preparation
To configuring WDM interfaces, you need the following data.
No. Data
1 routerWDM interface number
2 FEC mode of the WDM interface
3 FEC bit error rate threshold
4 FEC bit error detection interval
5 TTIs of the OTU and ODU
3.6.2 Configuring the FEC Mode of a WDM Interface

This section describes how to configure the FEC mode of a WDM interface.
Procedure
Step 1 Run:
system-view

Step 2 Run:
controller wdm interface-number
The WDM interface view is displayed.

Step 3 Run:
fec{ standard | enhanced-i-4 | enhanced-i-7 | none }
The FEC mode of the WDM interface is configured.

By default, a WDM interface uses the standard FEC mode.
----End
3.6.3 Configuring FEC Bit Error Detection on an OTN

This section describes how to configure FEC bit error detection on an OTN.
Procedure
Step 1 Run:
system-view

Step 2 Run:
Step 3 Run:
otn prefec-tca trigger-threshold coefficient-value power-value trigger-interval
trigger-time-interval [ recover-threshold coefficient-value power-value ]
[ recover-interval recover-time-interval ]
The FEC bit error rate threshold and FEC bit error detection interval are configured.
Step 4 (Optional) Run:

transmission-alarm down prefec-tca
The WDM interface is configured to change its physical-layer status to Down upon the
generation of a prefec-tca alarm.
----End
3.6.4 Configuring the TTIs of the OTU and ODU

This section describes how to configure the TTIs of the OTU and ODU.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
tti { odu | odu-pm | otu } { expected | sent } 64byte-mode value
or
ttiodu-tcm { all | spending-segment } { expected | sent } 64byte-modevalue
The TTIs of the OTU and ODU are configured.
----End

After configuring WDM interfaces, you can check the WDM interface status, alarms and error
messages about the regenerator section, multiplex section, or higher order path, WDM interface
alarm status, and WDM interface alarm statistics.

Procedure
l Run the display controller wdm [ wdm-number ] command to check the WDM interface
status as well as the alarms and error messages about the regenerator section, multiplex
section, or higher order path.
l Run the display transmission-alarm interface-type interface-number prefec-tca
command to check the prefec-tca alarm status and statistics about the specified WDM
interface. If no alarm type is specified, alarms of all types on the interface are displayed.
----End
Example
Run the display controller wdm command. The command output displays information about
the POS interface, such as its physical status, link protocol status, and clock mode.
<HUAWEI> display controller wdm1/0/0
Wdm1/0/0 current state : DOWN
Description : HUAWEI, Wdm1/0/0 Interface
Optical transceiver is offline!
FEC Mode: none
OTN alarm:
OTU layer: OTU_LOM
ODU layer: ODU-AIS ODU-LCK
OPU layer: none
WDM Error Counter:
SM_BEI :0
PM_BEI :0
SM_BIP after FEC :0
PM_BIP :0
FEC 0 error :0
FEC 1 error :0
FEC 0 and 1 type error:0
FEC symbol error :0
FEC uncorrected error :0
BER :
Received OTU TTI: ""

Received ODU TTI: ""
Received ODU TCM1 TTI: ""
Run the display transmission-alarm command. The command output displays WDM interface
alarm status and statistics.
<HUAWEI> display transmission-alarm wdm 1/1/0 prefec-tca
Interface:
Wdm1/1/0
Filter function:
disabled
Damping function:
disabled
Last reset time: 0000-00-00

00:00:00
Alarm prefec-
tca

Status:
Down
Flapping count: 0
3.7 Configuring E1 Channels of the CPOS Interface

You can create synchronous serial interfaces for E1 channels, configure their frame format, clock
mode, and timeslot binding, and disable or enable the E1 channels.

Before configuring E1 channels of CPOS interfaces, familiarize yourself with the usage scenario,
Usage Scenario
Before using the low-speed interface channelized from the CPOS interface for access, configure
parameters for the E1 channel.
Before configuring the E1 channel on a CPOS interface, complete the following tasks:
l Power on the router and start it normally.

l Connect the CPOS interface and configure physical attributes for the CPOS interface.
Data Preparation
To 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 to the channel-set, and the
number and range of timeslots
3.7.2 Creating Synchronous Serial Interface of E1 Channel

Before transmitting data over E1 channels of a CPOS interface, you need to create synchronous
serial interfaces.
Context
NOTE
One channel cannot work in both the clear channel mode and the channelized mode simultaneously. To
switch between these two working modes, cancel the current serial interface and re-create a new one.

Procedure
l Create the synchronous serial interface of the E1 channel on the X1 and X2 models of the
NE80E/40E.
1. Run:
system-view

2. Run:

3. To create the synchronous serial interface of the E1 channel, perform the following
steps:
– To create the E1 channel in clear channel mode, run:
– To create the E1 channel in channelized mode, run:

e1 e1-number channel-set set-number timeslot-list slot-list
NE80E/40E-X1 and -X2 support the following types of timeslot bundling:

– Bundling of timeslots 1 to 31
The channel-set after the E1 channel timeslot bundling forms a serial interface.
You can configure this serial interface. It is numbered: slot/card/interface/channel
number: channel-set number.
l Create the synchronous serial interface of the E1 channel on the other models of the NE80E/
40E.
1. Run:
system-view

2. Run:

3. To create the synchronous serial interface of the E1 channel, perform the following
steps:
– To create the E1 channel in clear channel mode, run:
– 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 bundled to form a serial interface;

timeslots 0 to 31 can also be randomly bundled to form one or multiple serial
interfaces. In this case, timeslot 0 needs to be specified in the command as the
parameter ts0.

Timeslot 0 is used to transmit frame synchronization and alarm information. After

timeslot 0 is bundled to form a serial interface, frame synchronization and alarm
information can be transparently transmitted between the client and the server.
The channel-set after the timeslot binding of the E1 channel forms a serial interface.
You can configure this serial interface. It is numbered: slot/card/interface/channel
number: channel-set number.
----End

E1 channels support the frame format with 4-bit CRC.
Context
An E1 channel supports the frame format with 4-bit CRC.
By default, the frame format of an E1 channel is no-CRC4.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
e1 e1-number set frame-format { crc4 | no-crc4 }
The frame format of the E1 channel is configured.
----End

You can set an E1 channel to work in master or slave clock mode according to the connected
device.
Context
You can configure the clock mode for each E1 channel separately. The clock mode of an E1
channel depends on the device connected to the E1 channel. For example:
l If the E1 interface is connected to a SONET or SDH device, configure the E1 interface to

work in slave clock mode.
l If two routers are connected directly through optical fiber, configure one end to work in
master clock mode and the other end in slave clock mode.
By default, an E1 interface works in master clock mode.

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
e1 e1-number set clock { master | slave }
The clock mode of the E1 channel is configured.
----End
3.7.5 Testing the Bit Error Rate of CPOS E1 link

Test results can be used to locate link faults.
Context
When faults occur on a CPOS interface, you can run the test connectivity cpos e1 command to
determine the cause.
Procedure
Step 1 Run:
system-view
Step 2 Run:
test connectivity controller cpos e1 controller-number { unframed | channelized
timeslot-list slot-list } duration time
Testing the Bit Error Rate of a CPOS E1 link is enabled.
----End

After E1 channels of CPOS interfaces are configured, you can check their clock mode and frame
format.
Procedure
l 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.

l Run the display e1 controller cpos controller-number e1–number e1–number history

command to check the current statistics on alarms and error packets of E1 channels of a
CPOS interface.
l Run the display e1 controller cpos controller-number e1–number e1–number history
command to check the historical statistics on alarms and error packets of E1 channels of a
CPOS interface.
----End
Example
You can view the status, link layer protocol and statistics for the serial interface channelized by
the E1 channel of a CPOS interface.
Description : Serial1/0/0/1:1 Interface
Route Port, The Maximum Transmit Unit is 1500, Hold timer is 10(sec)
Derived from Cpos1/0/0 e1 1, Timeslot(s) Used: 1-24, baudrate is 1536000 bps
LCP opened
CRC: CRC-32
Scramble disabled
Alarm: None
Traffic statistics:
Run the display controller cpos command, you can view the information about the status and
clock mode of a CPOS interface. For example:
The Vendor Name is SumitomoElectric
The Vendor PN is SCP6828-H1-BNE
Port BW: 155M, Transceiver max BW: 2.5G, Transceiver Mode: SingleMode
WaveLengh: 1310nm, Transmission Distance: 2km
RX:Flag J0: "", Flag J1: "NetEngine ", Flag C2: 2(0x2)
section layer:
alarm: none
error: B1 0
line layer:
alarm: none
error: B2 0 REI 27
path layer:
alarm: none
error: B3 0 REI 24

Run the display e1 controller cpos e1–number command to view the current statistics on alarms
and error packets of E1 channels of a CPOS interface.
<HUAWEI> display e1 controller cpos 1/0/0 e1-number 1
Father Physical layer is Packet Over SDH
TUG3-TUG2-TU12: 1-1-1
E1 Alarm: LOS
Statistics:
CRC Error 0
Framing Error 0
E-Bit 0
Run the display e1 controller cpos e1–number history command to view the historical
statistics on alarms and error packets of E1 channels of a CPOS interface.
<HUAWEI> display e1 controller cpos 1/0/0 e1-number 1 history
Father physical layer is Packet Over SDH
TUG3-TUG2-TU12:1-2-1
E1 alarm: OOF
E1 alarm history:
1 2012-02-22 16:59:15 OOF
2 2012-02-22 16:59:14 None
3 2012-02-22 16:50:40 OOF
4 2012-02-22 16:32:40 OOF PAIS
5 2012-02-22 16:22:39 OOF
6 2012-02-22 16:20:09 None
7 2012-02-22 16:06:35 OOF
8 2012-02-22 16:06:34 None
9 2012-02-22 16:06:33 PRDI
10 2012-02-22 15:27:55 OOF
Statistics:
CRC Error:0
Framing Error:48538
E-Bit:0
Statistics History:
CRC Error
No records.
Framing Error
1 2012-02-22 17:01:04 48538
2 2012-02-22 17:00:54 48411
3 2012-02-22 17:00:44 48284
4 2012-02-22 17:00:34 48157
5 2012-02-22 17:00:24 48030
6 2012-02-22 17:00:14 47903
7 2012-02-22 17:00:04 47776
8 2012-02-22 16:59:54 47649
9 2012-02-22 16:59:44 47522
10 2012-02-22 15:28:07 127
E-Bit
No records.
3.8 Configuring T1 Channels of the CPOS Interface

You can create synchronous serial interfaces for T1 channels, configure their frame format and
clock mode, and disable or enable the T1 channels.


Before configuring T1 channels of CPOS interfaces, familiarize yourself with the usage scenario,
Usage Scenario
Before using the low-speed port channelized from the CPOS interface for access, configure the
T1 channel parameters.
Before configuring the T1 channel of the CPOS interface, complete the following tasks:
l Power on the router and start it normally.

l Connect the CPOS interface and configure the physical attributes for the CPOS interface.
Data Preparation
To 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 channel-set, timeslot
number, or timeslot range
3.8.2 Creating Synchronous Serial Interface of T1 Channel

Before transmitting data over T1 channels of CPOS interfaces, you need to create synchronous
serial interfaces.
Context
NOTE
One channel cannot work in both the clear channel mode and the channelized mode simultaneously. To
switch between these two working modes, cancel the current serial interface and re-create a new one.
Procedure
Step 1 Run:
system-view
Step 2 Run:


Step 3 To create the synchronous serial interface of the T1 channel, perform the following steps:
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 more
serial ports.
The channel-set after the timeslot binding of the T1 channel forms a serial interface. You can
configure 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 of
the bound timeslots).
----End

T1 channels support two frame formats, namely, super frame (SF) and extended super frame
(ESF).
Context
A T1 channel supports two types of frame formats: super frame (SF) and extended super frame
(ESF).
Procedure
Step 1 Run:
system-view

Step 2 Run:

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

You can set an E1 channel to work in master or slave clock mode according to the connected
device.

Context
You can configure the clock mode for each T1 channel separately. The clock mode of a T1
channel depends on the device connected to the T1 channel. For example, if an interface is
connected to a SONET or SDH device, you should configure the interface to work in slave clock
mode. If two routers are connected directly through optical fiber, configure one end to work in
master clock mode and the other end in slave clock mode.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
The clock mode of the T1 channel is configured.
----End

After T1 channels of CPOS interfaces are configured, you can check their clock mode and frame
format.
Procedure
check the information about the serial interface bound by T1 channels.
l Run the display controller cpos [ cpos-number ] command to check the information about
the status and statistics of the CPOS interface.
----End
Example
You can view the status, link layer protocol and statistics of the serial interface channelized by
the T1 channel of a CPOS interface.
Derived from Cpos1/0/0 t1 1, Timeslot(s) Used: 0-23, baudrate is 1536000 bps

LCP opened
CRC: CRC-32
Scramble disabled
Alarm: none
Traffic statistics:
3.9 Configuring E3 Channels of an STM-1 CPOS Interface

You can create synchronous serial interfaces of E3 channels and configure the clock mode of
E3 channels.

Before configuring E3 channels of CPOS interfaces, familiarize yourself with the usage scenario,
complete the pre-configuration tasks, and obtain the required data.
Usage Scenario
When accessing through the low speed port channelized by the CPOS interface, configure the
E3 channels.
Before configuring E3 channels on a CPOS interface, complete the following tasks:
l Power on and start the router normally

.
l Connect the CPOS interface and configure the physical attributes of the CPOS interface
.
Data Preparation
To configure E3 channels of a CPOS interface, you need the following data.
No. Data
2 Number of the E3 channel

3.9.2 Creating Synchronous Serial Interface of E3 Channels

E3 channels of CPOS interfaces can work in either clear channel mode or unchannelized mode
and be configured with synchronous serial interfaces.
Context
E3 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 bit
flows. The E3 channel without timeslot division functions as a synchronous serial interface
named serial slot/card/port/0:0.
l Unchannelized mode
When an E3 channel works in unchannelized mode, data is transmitted in the form of
frames. All timeslots of the E3 channel are bound to function as a synchronous serial
interface named serial slot/card/port/0:0.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 To create the synchronous serial interface, perform the following as required:
l To create the serial interface in unchannelized mode, run the e3 e3-number framed
command.
l To create the serial interface in 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

The clock mode on different E3 channels can be configured separately. Whether to use the master
clock or the slave clock mode varies according to the peer interface.
Context
You can configure the clock mode for each E3 channel separately. The clock mode of an E3
channel depends on the connected device. For example, if the E3 channel is connected to a
SONET or SDH device, configure the E3 channel to work in slave clock mode.

If two routers are connected directly through optical fiber, configure one end to work in master
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 1 Run:
system-view

Step 2 Run:

Step 3 Run:
e3 e3-number set clock { master | slave }
The clock mode of the E3 channel is configured.
----End

After E3 channels of CPOS interfaces are configured, you can check the status and clock mode
of synchronous serial interfaces of the E3 channels.
Procedure
l Run the display controller cpos cpos-number command to check the configuration and
status of the CPOS interface.
check the information about the serial interface bound by E3 channels.
----End
Example
You can view information about the clock, frame format, and multiplexing path.
Cpos1/0/0 current state : Administratively DOWN
The Vendor PN is HFBR-5710LP-H3C
Port BW: 155M, Transceiver max BW: 1G, Transceiver Mode: MultiMode
WaveLengh: 850nm, Transmission Distance: 550m
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 serial interface's status and clock information.
Description: Serial2/0/0/1:0 Interface
Derived from Cpos2/0/0 e3 1, Unframed mode, baudrate is 34368000 bps
LCP opened
CRC: CRC-32
Scramble disabled
Alarm: None
Traffic statistics:
3.10 Configuring T3 Channels of an STM-1 CPOS Interface

You can create synchronous serial interfaces of T3 channels and configure their frame format
and clock mode.

Before configuring T3 channels of CPOS interfaces, familiarize yourself with the usage scenario,
Usage Scenario
When accessing through the low speed port channelized by the CPOS interface, configure the
T3 channels.
Before configuring T3 channels on a CPOS interface, complete the following tasks:
l Power on and start the router normally

.
l Connect the CPOS interface and configure the physical attributes of the CPOS interface
.

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.10.2 Creating T3 Channels

T3 channels of CPOS interfaces can work in either clear channel mode or unchannelized mode
and be configured with synchronous serial interfaces.
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
flows. The T3 channel without timeslot division functions as a synchronous serial interface
named serial slot/card/port/channel-number:0.
l Unchannelized mode
When a T3 channel works in unchannelized mode, data is transmitted in the form of frames.
All timeslots of the T3 channel are bound to function as a synchronous serial interface
named serial slot/card/port/channel-number:0.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 To create the synchronous serial interface, perform the following as required:
l To create the serial interface in unchannelized mode, run the t3 t3-number framed command.
l To create the serial interface in clear channel mode, run the t3 t3-number unframed
command.
After the creation is successful, the number of the formed synchronous serial interface is: slot/
card/port/channel-number:0.
----End


T3 channels of CPOS interfaces support two frame formats, namely, C-bit and M23.
Context
T1 corresponds to the digital signal level DS-1. Twenty-eight T1s form a T3 through bit
multiplexing. There are two kinds of frame formats:
l C-bit is also called C-bit parity check. In this frame format, the padding field can be used
during maintenance.
l M23 it is a multiplexing process from DS-2 to DS-3. Four T1s (DS-1) multiplex to a DS-2
line through M12; seven DS-2 lines multiplex to a T3 (DS-3).
By default, C-bit is used.
NOTE
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
t3 t3-number set frame-format { c-bit | m23 }
The frame format for the T3 channel is configured.
It is recommended that the frame formats for the T3 channel and the CPOS interface be the same.
----End

The clock mode on different T3 channels can be configured separately. Whether to use the master
clock or the slave clock mode varies according to the peer.
Context
You can configure the clock mode for each T3 channel separately. The clock mode of a T3
channel depends on the connected device. For example, if the T3 channel is connected to a
SONET or SDH device, configure the T3 channel to work in slave clock mode.
If two routers are connected directly through optical fiber, configure one end to work in master
clock mode and the other end in slave clock mode.

NOTE
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
The clock mode of the T3 channel is configured.
----End

After T3 channels of CPOS interfaces are configured, you can check the status, frame format,
and clock mode of the serial interfaces formed by bundling timeslots of T3 channels.
Procedure
l Run the display controller cpos [ cpos-number ] command to check the status and statistics
of the CPOS interface.
check the information about the serial interface bound by T3 channels.
----End
Example
You can view information about the clock, frame format, and multiplexing path.
Cpos1/0/0 current state : Administratively DOWN
The Vendor PN is HFBR-5710LP-H3C
Port BW: 155M, Transceiver max BW: 1G, Transceiver Mode: MultiMode
WaveLengh: 850nm, Transmission Distance: 550m
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 serial interface's status and clock information.
Line protocol current state :UP
Description: Serial2/0/0/1:0 Interface
Derived from Cpos2/0/0 t3 1, Unframed mode, baudrate is 44736000 bps
LCP opened
CRC: CRC-32
Scramble disabled
Alarm: None
Traffic statistics:
3.11 Configuring an AUG Interface on an STM-4 CPOS

Interface
STM-4 CPOS interfaces are used to carry high-bandwidth services. Some services, however, do
not have high requirements on bandwidths. In this case, you can configure an AUG interface on
an STM-4 CPOS interface so that the AUG interface can be used to implement low-bandwidth
services.

Before configuring an AUG interface on an STM-4 CPOS interface, familiarize yourself with
the usage scenario, complete the pre-configuration tasks, and obtain the data required for the
configuration.
Usage Scenario
An STM-4 CPOS interface is used to carry services that require a high interface bandwidth.
Some services, however, do not have high requirements on the interface bandwidth. In this case,
you can channelize an STM-4 CPOS interface into AUG interfaces (STM-1 level) with a smaller
interface bandwidth, and create a channelized serial interface on each AUG interface for PPP
services.
Before configuring an AUG interface, power on the router.

Data Preparation
To configure an AUG interface, you need the following data.
No. Data
1 router CPOS interface number
3.11.2 Creating an AUG Interface

To implement low-bandwidth services using an STM-4 CPOS interface, create an AUG interface
on the STM-4 CPOS interface.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of a specified CPOS interface is displayed.

Step 3 Run:
aug aug-number
An AUG interface is created, and the AUG interface view is displayed.
----End
3.11.3 Configuring a serial interface on the AUG Interface

To maximize the utilization of the bandwidth of an AUG interface, configure the AUG interface
to work in VC4 clear channelized mode.
Procedure
Step 1 Run:
system-view

Step 2 Run:
controller aug aug-number
The view of a specified AUG interface is displayed.

Step 3 Run:
using vc4
The VC4 clear channelized mode is specified, and a serial interface is automatically created.
----End


After configuring an AUG interface, check its configurations and status information.
Prerequisites
Configurations on an AUG interface have been complete.
Procedure
l Run the display controller aug [ controller-number ] command to check the status
information about an AUG interface.
----End
Example
Run the display controller aug [ controller-number ] command. The command output shows
the status information about the specified AUG interface.
<HUAWEI> display controller aug 1/0/0:1
AUG1/0/0:1 current state : UP
Description : HUAWEI,AUG1/0/0:1 Interface
Multiplex AU-4, loopback none
TX: Flag J1: "NetEngine ",
Flag C2: 100(0x64)
RX:Flag J1: "NetEngine ",
Flag C2: 2(0x2)
alarm: AUAIS
error: B3 1601997296
3.12 Maintaining POS and CPOS Interface Configuration

To maintain POS and CPOS interfaces, you can enable the self-loop function to detect whether
an interface runs properly and to clear interface statistics.
3.12.1 Configuring the Self-loop to Detect Whether the Interface Is

Normal
You can enable the self-loop function on an interface to detect whether the interface or the link
is working properly.
Context
NOTICE
After you configure the self-loop or run the loopback command, the interface on a router or link
may not run normally. Therefore, you must determine whether to set the self-loop. After the
detection is complete, run the undo loopback command to disable it.

Procedure
Step 1 Run:
system-view
Step 2 Choose one of the following commands according to the interface type to enter the interface
view.
l In the case of a POS interface, run:
l In the case of an 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 a 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 a T3 channel of STM-1 CPOS interface, run:

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

e1 e1-number set loopback { local | remote }
NOTE
The e1 set loopback command cannot be configured on the X1 and X2 models of the NE80E/40E.
By default, the self-loop is disabled.
When configuring the loopback on 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 actual configurations:
– To enable the local loopback on the interface, the interface must be in the master clock
mode.
– To enable the remote loopback on the interface, the interface must be in the slave clock
mode.
Take the prompt information as the standard.
l For the STM-1 CPOS interface or E1/T1/E3/T3 channel of STM-1 CPOS interface, the
following cases may occur in actual configurations:
– To enable the local loopback on the interface, the interface must be in the master clock
mode.
– To enable the remote loopback on the interface, the interface must be in the slave clock
mode.
----End


You can run the reset command to clear interface traffic statistics before collecting statistics on
the interface again.
Context
NOTICE
Interface statistics cannot be restored after you run the reset command to clear them. Exercise
caution when running the commands.
To reset the interface statistics on the Network Management System (NMS) , the interface
statistics displayed using the display e1 controller cpos controller-number e1–number e1–
number history command or those displayed using the display interface command, run the
following commands in the user view. Clear the interface statistics before collecting them.
NOTE
For interface statistics on the NMS, refer to related NMS manuals.
Procedure
l Run the reset count controller cpos controller-number e1 e1–number command to clear
the interface statistics previously displayed using the display e1 controller cpos controller-
number e1–number e1–number history command.
l Run the reset counters controller [ controller-type [ controller-number ] | controller-
name ] command to clear the interface statistics.
----End
3.12.3 Monitoring the Physical Status of E1/T1 Links

To ensure correct link connections, you must monitor the physical status of E1/T1 links.
Context
Monitoring the physical status of E1/T1 links can help you locate E1/T1 link faults, ensuring
correct link connections. You can configure the system to monitor the physical status of multiple
E1/T1 links simultaneously while not affecting existing services.
Perform the following steps on a device to be checked:

Procedure
Step 1 Run:
monitor { e1 | t1 } { interface-type interface-number | interface-name } &<1-16>
[ interval interval [ times times ] | times times [ interval interval ] ]
The physical status of E1/T1 links is monitored.
----End

This section describes the POS and CPOS interfaces in detail from the aspect of applicable
scenarios and configuration commands.
3.13.1 Example for Directly Connecting Devices Through POS

Interfaces
This example shows how to connect two devices through POS interfaces in typical networking.
As shown in Figure 3-6, POS interfaces on Router A and Router B are directly connected with
a pair of single-mode fibers for receiving and sending packets; PPP is the link layer protocol. It
is required that Router A and Router B can communicate.
Figure 3-6 Networking diagram of connecting devices directly through POS interfaces
RouterA
POS1/0/0 RouterB
10.1.1.2/30
POS1/0/0
10.1.1.1/30
1. Configure PPP as the link layer protocol.

2. Configure IP addresses.
Data Preparation
To 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.
[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 any other physical
parameters.
[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

Run the display interface pos command to check the connectivity of the POS interface on Router
A.
<RouterA> display interface pos 1/0/0
Description: Pos1/0/0 Interface
The Vendor Name is FINISAR CORP. , The Vendor PN is FTLF1321P1BTL-HW
Flag C2 22(0x16)
SDH alarm:
section layer: none
line layer: none
path layer: none
SDH error:
section layer: B1 0
Run the ping command to check 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
--- 10.1.1.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 2/2/3 ms
----End
Configuration Files
#
sysname RouterA
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.1 255.255.255.252
#
return

#
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.13.2 Example for Connecting Devices with POS Interfaces

Through FR Network
This example shows how to configure POS interfaces on three routers in different network
segments to communicate with each other over an FR network.
As shown in Figure 3-7, three routers are interconnected through POS interfaces on the FR
network. The routers work in DTE mode as user devices.
Router A connects Router B and Router C through sub-interfaces. Router B and Router C reside
on different network segments than Router A.

Figure 3-7 Networking for connecting routers using a POS interface through an FR network
POS1/0/0.1
POS1/0/0.1 DLCI=21
DLCI=21 10.1.1.2/30 Router B
10.1.1.1/30 Frame
Relay
network
Router A POS1/0/0.2
DLCI=22 POS1/0/0.2
10.2.1.1/30 DLCI=22
10.2.1.2/30
Router C
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 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
# Encapsulate the FR protocol.

[RouterA-Pos1/0/0] link-protocol fr
[RouterA-Pos1/0/0] fr interface-type dte
# Configure POS 1/0/0.1.

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

[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

Step 2 Configure Router B and Router C.

The method for configuring Router B and Router C is the same as the method for configuring
Router A. For configuration details, see "Configuration Files" in this section.
Run the display interface pos command on each router. The command output shows that the
connectivity of each POS interface is Up.
Run the ping command on each router. Each router can ping through the network.
----End
Configuration Files
#
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
#
fr dlci 22
ip address 10.2.1.1 255.255.255.252
#
return

#
sysname RouterB
#
interface Pos1/0/0
link-protocol fr
undo shutdown
#
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
#
fr dlci 22
ip address 10.2.1.2 255.255.255.252
#
return
3.13.3 Example for Configuring an STM-1 CPOS Interface

This example shows how to configure a CPOS interface on a router to converge services from
mid-range-and-low-end routers over E1/T1 links and identify each mid-range and low-end router
by bundling different timeslots on the CPOS interface.
NOTE
This document uses interface numbers and link types of the NE40E-X8 as examples. In working situations,
the actual interface numbers and link types may be different.
As shown in Figure 3-8, certain mid-range-and-low-end devices access the transmission

network through an E1/T1 leased cable. All bandwidths converge to the CPOS interface 3/0/1
on Router A through the transmission network. Each mid-range and low-end device is defined
by its unique timeslot.
There cannot be only one transmission network between the channelized POS interface and the
mid-range and low-end devices. Other transmission methods must also be adopted.
NOTE
The configurations of the T1 channel and the E1 channel should be consistent. Use the E1 channel as an
example.
Figure 3-8 Networking for an STM-1 CPOS interface
E1/T1 ..
ADM
Router A
E1/T1 STM-4/16 CPOS 3/0/1
ADM ADM Internet
OC-3/STM-1
ADM
nx E1/T1 ..

1. Create the channel.

2. Create the bound group.
3. Configure the channel to join the bound group.
Data Preparation
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 must
be consistent, respectively. That is, trans-board binding is not supported.
l The interfaces added to the MP-group can only be serial interfaces.
Procedure
Step 1 Configure RouterA
# Create a channel on the CPOS interface.

[RouterA] controller cpos 3/0/1
[RouterA-Cpos3/0/1] e1 1 channel-set 1 timeslot-list 1-10
[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
# 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

# Restart the channel and MP-group.

[RouterA] interface Mp-group 3/0/1
[RouterA-Serial3/0/1/1:1] undo shutdown
----End
Configuration Files
Configuration file of Router A
#
sysname RouterA
#
controller Cpos3/0/1
undo shutdown
e1 1 channel-set 1 timeslot-list 1-10
#
interface Serial3/0/1/1:1
undo shutdown
link-protocol ppp
#
undo shutdown
link-protocol ppp
#
undo shutdown
link-protocol ppp
#
undo shutdown
link-protocol ppp
#
undo shutdown
#
return
3.13.4 Example for Configuring a BTB IP RAN - PWE3 (IP-

Interworking) + (VSI + L3VPN) with Ethernet NodeBs
This example provides a scheme for configuring a BTB IP RAN with an IP-interworking-enabled
L2VPN to implement the communication between channelized TDM BTSs and BSCs.

If an IP-interworking TDM NodeB is connected to a CSG by using the ML-PPP link, IP-
interworking is required because the AC interface on the PE-AGG is an Ethernet interface. As
only PWE3 redundancy supports IP-interworking, the BTB IP RAN - PWE3 (IP-interworking)
+ (VSI +L3VPN) solution is provided for this scenario.
On the network shown in Figure 3-9, the CSG configured with PWE3 redundancy in master/
slave mode is dual-homed to PE-AGG1 and PE-AGG2, and PWE3 IP-interworking is
configured. On PE-AGGs, the IP addresses of the local and remote CEs must be specified. A
spoke PW needs to be created between UPE1 and UPE2 to allow the network on one side of the
UPEs not to be affected by faults on the other side. VPN FRR is required to protect the L3VPN.
Figure 3-9 Networking diagram for configuring a BTB IP RAN - PWE3 (IP-interworking) +
(VSI + L3VPN) with TDM BTSs
PE-AGG1 UPE1 BSC-SR1
ar y
CSG prim
PW
MLPPP
spoke
PW
se
NodeB co RNC
n
PW dary
PE-AGG2 UPE2 BSC-SR2
PW redundancy VSI accessing L3VPN
Device Interface Peer Device IP Address
CSG GE1/0/1 PEAGG1 172.16.1.1/24
GE1/0/2 PEAGG2 172.16.4.1/24
Serial2/3/1 NodeB -
PEAGG1 GE1/0/1 CSG 172.16.1.2/24
GE1/0/3 UPE1 -
PEAGG2 GE1/0/2 CSG 172.16.4.2/24
GE1/0/3 UPE2 -
UPE1 GE1/0/0 UPE2 172.16.2.2/24
GE1/0/1 PEAGG1 -
GE1/0/3 BSC-SR1 172.16.3.1/24
GE1/0/4 BSC-SR2 172.16.8.1/24
UPE2 GE1/0/0 UPE1 172.16.2.1/24

GE1/0/1 PEAGG2 -
GE1/0/3 BSC-SR2 172.16.6.1/24
GE1/0/4 BSC-SR1 172.16.7.1/24
BSC-SR2 GE1/0/0 BSC-SR1 -
GE1/0/1 UPE2 172.16.6.2/24
GE1/0/2 UPE1 172.16.8.2/24
GE1/0/3 RNC -
1. Configure IP addresses and routes.

2. Configure MPLS and public network tunnels.
l Set up TE tunnels between the CSG and PE-AGGs.
l Configure an LSP between UPE1 and UPE2.
3. Configure PW redundancy in master/slave mode.
4. Configure a spoke PW.
5. Configure BFD to detect faults in public network links.
6. Configure L3VPN FRR.
7. Configure VRRP.
l Configure an mVRRP backup group on UPEs to function as a gateway for the NodeB.
l Configure a VRRP backup group on BSC-SRs to function as a gateway for the RNC.
Data Preparation
l Interface number, interface IP address, and OSPF process ID

l LSR ID
l L2VC's destination address, VC ID, and VC type
l VSI name and VSI ID
l BFD session name, local discriminator, and remote discriminator
l VE group number
l VRRP backup group ID and priority
Procedure
Step 1 Assign an IP address to and configure a routing protocol on each interface.
1. An IP address is assigned to each interface.

2. Configure a routing protocol, and configure the CSG, PE-AGG1, and PE-AGG2 in a routing
domain and the UPE1, UPE2, BSC-SR1, and BSC-SR2 in another routing domain. This
example uses OSPF, and the devices are group into Area 0 and Area 1 respectively.
After the configuration, run the display ip routing-table command on the CSG, PE-AGGs,
UPEs, and BSC-SRs. You can view the routes learned from each other. Note that when
configuring OSPF, you need to advertise 32-bit loopback interface addresses (LSR IDs) of the
CSG, PE-AGGs, UPEs, and BSC-SRs.
The detailed configuration is not mentioned here.
Step 2 Configure basic MPLS functions and public network tunnels.

NOTE
l Configure TE tunnels between the CSG and PE-AGG1, and between the CSG and PE-AGG2.
l Configure LSPs between UPE1 and UPE2, and between UPEs and BSC-SRs.
l Enable RSVP GR, LDP GR, BGP GR and OSPF GR to enhance the switching performance.
1. Enable MPLS TE and RSVP-TE and configure CSPF and OSPF TE.
# Configure the CSG.

[CSG] mpls lsr-id 1.1.1.1
[CSG] mpls
[CSG-mpls] mpls te
[CSG-mpls] mpls rsvp-te
[CSG-mpls] mpls rsvp-te hello
[CSG-mpls] mpls rsvp-te hello full-gr
[CSG-mpls] mpls te cspf
[CSG-mpls] quit
[CSG] interface gigabitethernet 1/0/1
[CSG-GigabitEthernet1/0/1] mpls
[CSG-GigabitEthernet1/0/1] mpls te
[CSG-GigabitEthernet1/0/1] mpls rsvp-te
[CSG-GigabitEthernet1/0/1] mpls rsvp-te hello
[CSG-GigabitEthernet1/0/1] quit
[CSG] interface gigabitethernet 1/0/2
[CSG] ospf 100
[CSG-ospf-100] opaque-capability enable
[CSG-ospf-100] graceful-restart
[CSG-ospf-100] area 0
[CSG-ospf-100-area-0.0.0.0] mpls-te enable
[CSG-ospf-100-area-0.0.0.0] quit
[CSG-ospf-100] quit
# Configure PE-AGG1.
[PEAGG1] mpls lsr-id 2.2.2.2
[PEAGG1] mpls
[PEAGG1-mpls] mpls te
[PEAGG1-mpls] mpls rsvp-te
[PEAGG1-mpls] mpls rsvp-te hello
[PEAGG1-mpls] mpls rsvp-te hello full-gr
[PEAGG1-mpls] mpls te cspf
[PEAGG1-mpls] quit
[PEAGG1] mpls ldp
[PEAGG1-mpls-ldp] graceful-restart
[PEAGG1-mpls-ldp] quit
[PEAGG1] interface gigabitethernet 1/0/1

[PEAGG1-GigabitEthernet1/0/1] mpls
[PEAGG1-GigabitEthernet1/0/1] mpls te
[PEAGG1-GigabitEthernet1/0/1] mpls rsvp-te
[PEAGG1-GigabitEthernet1/0/1] mpls rsvp-te hello
[PEAGG1-GigabitEthernet1/0/1] quit
[PEAGG1-GigabitEthernet1/0/3] undo shutdown
[PEAGG1] interface gigabitethernet 1/0/3.10
[PEAGG1-GigabitEthernet1/0/3.10] vlan-type dot1q 10
[PEAGG1-GigabitEthernet1/0/3.10] quit
[PEAGG1] ospf 100
[PEAGG1-ospf-100] opaque-capability enable
[PEAGG1-ospf-100] graceful-restart
[PEAGG1-ospf-100] area 0
[PEAGG1-ospf-100-area-0.0.0.0] mpls-te enable
[PEAGG1-ospf-100-area-0.0.0.0] quit
[PEAGG1-ospf-100] quit
[PEAGG2] mpls lsr-id 3.3.3.3
[PEAGG2] mpls
[PEAGG2-mpls] mpls te
[PEAGG2-mpls] mpls rsvp-te
[PEAGG2-mpls] mpls rsvp-te hello
[PEAGG2-mpls] mpls rsvp-te hello full-gr
[PEAGG2-mpls] mpls te cspf
[PEAGG2-mpls] quit
[PEAGG2] mpls ldp
[PEAGG2-mpls-ldp] graceful-restart
[PEAGG2-GigabitEthernet1/0/2] mpls
[PEAGG2-GigabitEthernet1/0/2] mpls te
[PEAGG2-GigabitEthernet1/0/2] mpls rsvp-te
[PEAGG2-GigabitEthernet1/0/2] mpls rsvp-te hello
[PEAGG2] ospf 100
[PEAGG2-ospf-100] opaque-capability enable
[PEAGG2-ospf-100] graceful-restart
[PEAGG2-ospf-100] area 0
[PEAGG2-ospf-100-area-0.0.0.0] mpls-te enable
[PEAGG2-ospf-100-area-0.0.0.0] quit
[PEAGG2-ospf-100] quit
# Configure UPE1.
[UPE1] mpls lsr-id 4.4.4.4
[UPE1] mpls
[UPE1-mpls] quit
[UPE1] mpls ldp
[UPE1-mpls-ldp] graceful-restart
[UPE1-mpls-ldp] quit
[UPE1] interface gigabitethernet 1/0/1
[UPE1-GigabitEthernet1/0/1] undo shutdown
[UPE1-GigabitEthernet1/0/1] quit
[UPE1] interface gigabitethernet 1/0/1.10
[UPE1-GigabitEthernet1/0/1.10] vlan-type dot1q 10
[UPE1-GigabitEthernet1/0/1.10] quit
[UPE1-GigabitEthernet1/0/2] mpls

[UPE1-GigabitEthernet1/0/2] mpls ldp

[UPE1] ospf 100
[UPE1-ospf-100] opaque-capability enable
[UPE1-ospf-100] graceful-restart
[UPE1-ospf-100] quit
# Configure UPE2.
[UPE2] mpls lsr-id 5.5.5.5
[UPE2] mpls
[UPE2-mpls] quit
[UPE2] mpls ldp
[UPE2-mpls-ldp] graceful-restart
[UPE2-mpls-ldp] quit
[UPE2-GigabitEthernet1/0/1] undo shutdown
[UPE2] interface gigabitethernet 1/0/1.10
[UPE2-GigabitEthernet1/0/1.10] vlan-type dot1q 10
[UPE2-GigabitEthernet1/0/1.10] quit
[UPE2] ospf 100
[UPE2-ospf-100] opaque-capability enable
[UPE2-ospf-100] graceful-restart
[UPE2-ospf-100] quit
# Configure BSC-SR1.
[BSC-SR1] mpls lsr-id 6.6.6.6
[BSC-SR1] mpls
[BSC-SR1-mpls] quit
[BSC-SR1] mpls ldp
[BSC-SR1-mpls-ldp] graceful-restart
[BSC-SR1-mpls-ldp] quit
[BSC-SR1] interface gigabitethernet 1/0/1
[BSC-SR1-GigabitEthernet1/0/1] mpls
[BSC-SR1-GigabitEthernet1/0/1] mpls ldp
[BSC-SR1-GigabitEthernet1/0/1] quit
[BSC-SR1] ospf 100
[BSC-SR1-ospf-100] opaque-capability enable
[BSC-SR1-ospf-100] graceful-restart
[BSC-SR1-ospf-100] quit

[BSC-SR2] mpls lsr-id 7.7.7.7

[BSC-SR2] mpls
[BSC-SR2-mpls] quit
[BSC-SR2] mpls ldp
[BSC-SR2-mpls-ldp] graceful-restart
[BSC-SR2-mpls-ldp] quit
[BSC-SR2] ospf 100
[BSC-SR2-ospf-100] opaque-capability enable
[BSC-SR2-ospf-100] graceful-restart
[BSC-SR2-ospf-100] quit
2. Configure MPLS TE tunnel interfaces.

[CSG] interface tunnel 1/0/1
[CSG-Tunnel1/0/1] ip address unnumbered interface loopback 1
[CSG-Tunnel1/0/1] tunnel-protocol mpls te
[CSG-Tunnel1/0/1] destination 2.2.2.2
[CSG-Tunnel1/0/1] mpls te tunnel-id 100
[CSG-Tunnel1/0/1] mpls te signal-protocol rsvp-te
[CSG-Tunnel1/0/1] mpls te reserved-for-binding
[CSG-Tunnel1/0/1] mpls te commit
[CSG-Tunnel1/0/1] quit
[PEAGG1] interface tunnel 1/0/1
[PEAGG1-Tunnel1/0/1] ip address unnumbered interface loopback 1
[PEAGG1-Tunnel1/0/1] tunnel-protocol mpls te
[PEAGG1-Tunnel1/0/1] destination 1.1.1.1
[PEAGG1-Tunnel1/0/1] mpls te tunnel-id 100
[PEAGG1-Tunnel1/0/1] mpls te signal-protocol rsvp-te
[PEAGG1-Tunnel1/0/1] mpls te reserved-for-binding
[PEAGG1-Tunnel1/0/1] mpls te commit
[PEAGG1-Tunnel1/0/1] quit
[PEAGG2] interface tunnel 1/0/2
[PEAGG2-Tunnel1/0/2] ip address unnumbered interface loopback 0
[PEAGG2-Tunnel1/0/2] tunnel-protocol mpls te
[PEAGG2-Tunnel1/0/2] destination 1.1.1.1
[PEAGG2-Tunnel1/0/2] mpls te tunnel-id 200
[PEAGG2-Tunnel1/0/2] mpls te signal-protocol rsvp-te
[PEAGG2-Tunnel1/0/2] mpls te reserved-for-binding
[PEAGG2-Tunnel1/0/2] mpls te commit
[PEAGG2-Tunnel1/0/2] quit
3. Configure a tunnel policy.


[CSG] tunnel-policy policy1

[CSG-tunnel-policy-policy1] tunnel binding destination 2.2.2.2 te tunnel1/0/1
[CSG-tunnel-policy-policy1] tunnel binding destination 3.3.3.3 te tunnel1/0/2
[CSG-tunnel-policy-policy1] quit
[PEAGG1] tunnel-policy policy1
[PEAGG1-tunnel-policy-policy1] tunnel binding destination 1.1.1.1 te
tunnel1/0/1
[PEAGG1-tunnel-policy-policy1] quit
[PEAGG2] tunnel-policy policy1
[PEAGG2-tunnel-policy-policy1] tunnel binding destination 1.1.1.1 te
tunnel1/0/2
[PEAGG2-tunnel-policy-policy1] quit
Step 3 Configure PW redundancy in master/slave mode.

1. Configure remote MPLS LDP sessions between the CSG and PE-AGGs.
NOTE
In this configuration example, TE tunnels are configured between the CSG and PE-AGGs, and MPLS
LDP is not required. PWE3, however, uses extended LDP signaling to distribute VPN labels. Therefore,
remote MPLS LDP sessions have to be configured between the CSG and PE-AGGs. An LDP LSP is
configured to directly connect PE-AGGs, and therefore no remote LDP session needs to be configured
between the PE-AGGs.

[CSG] mpls ldp
[CSG-mpls-ldp] quit
[CSG] mpls ldp remote-peer 2.2.2.2
[CSG-mpls-ldp-remote-2.2.2.2] remote-ip 2.2.2.2
[CSG-mpls-ldp-remote-2.2.2.2] quit
[PEAGG1] mpls ldp
[PEAGG1] mpls ldp remote-peer 1.1.1.1
[PEAGG1-mpls-ldp-remote-1.1.1.1] remote-ip 1.1.1.1
[PEAGG1-mpls-ldp-remote-1.1.1.1] quit
[PEAGG2] mpls ldp
[PEAGG2] mpls ldp remote-peer 1.1.1.1
[PEAGG2-mpls-ldp-remote-1.1.1.1] remote-ip 1.1.1.1
[PEAGG2-mpls-ldp-remote-1.1.1.1] quit
2. Configure PW redundancy in master/slave mode.

[CSG] mpls l2vpn
[CSG-l2vpn] quit
[CSG] controller Cpos2/3/1
[CSG-Cpos2/3/1] undo shutdown
[CSG-Cpos2/3/1] e1 1 channel-set 0 timeslot-list 1-7


[CSG-Cpos2/3/1] quit
[CSG] interface Serial2/3/1/1:0
[CSG-Serial2/3/1/1:0] ppp mp Mp-group 2/3/1
[CSG-Serial2/3/1/1:0] quit
[CSG] interface Mp-group2/3/1
[CSG-Mp-group2/3/1] ip address ppp-negotiate
[CSG-Mp-group2/3/1] mpls l2vc 2.2.2.2 100 tunnel-policy policy1 ip-interworking
[CSG-Mp-group2/3/1] mpls l2vc 3.3.3.3 200 ip-interworking tunnel-policy
policy1 secondary
[CSG-Mp-group2/3/1] mpls l2vpn redundancy independent
[CSG-Mp-group2/3/1] quit
[PEAGG1] mpls l2vpn
[PEAGG1-l2vpn] quit
[PEAGG1] interface GigabitEthernet1/0/3
[PEAGG1-GigabitEthernet1/0/3.10] local-ce mac broadcast
[PEAGG1-GigabitEthernet1/0/3.10] remote-ce ip 120.0.0.1
[PEAGG1-GigabitEthernet1/0/3.10] mpls l2vc 1.1.1.1 100 tunnel-policy policy1
ignore-standby-state
[PEAGG2] mpls l2vpn
[PEAGG2-l2vpn] quit
[PEAGG2] interface GigabitEthernet1/0/3
[PEAGG2-GigabitEthernet1/0/3.10] local-ce mac broadcast
[PEAGG2-GigabitEthernet1/0/3.10] remote-ce ip 120.0.0.1
[PEAGG2-GigabitEthernet1/0/3.10] mpls l2vc 1.1.1.1 100 tunnel-policy policy1
ignore-standby-state
# Run the display mpls l2vc brief command on the CSG and PE-AGGs to check whether
the VC state is Up. Use the display on the CSG as an example.
[CSG] display mpls l2vc brief
Total ldp vc : 2 2 up 0 down
*Client Interface : GigabitEthernet1/0/3.10

Administrator PW : no
AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 100
VC Type : IP-interworking
session state : up
Destination : 2.2.2.2
link state : up
*Client Interface : GigabitEthernet1/0/3.10

AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 200

session state : up
link state : up
Step 4 Configure a spoke PW.

NOTE
Configure a spoke PW between UPE1 and UPE2 so that the NodeB can communicate with the RNC through
the spoke PW even if the primary or secondary PW between the CSG and PE-AGGs fails.
# Configure UPE1.
[UPE1] vsi 1 static
[UPE1-vsi-1] pwsignal ldp
[UPE1-vsi-1-ldp] vsi-id 100
[UPE1-vsi-1-ldp] peer 5.5.5.5 negotiation-vc-id 8000 upe
[UPE1-vsi-1-ldp] quit
[UPE1-vsi-1] quit
[UPE1] interface Virtual-Ethernet 1/0/0
[UPE1-Virtual-Ethernet1/0/0] ve-group 10 l2-terminate
[UPE1-Virtual-Ethernet1/0/0] quit
[UPE1] interface Virtual-Ethernet 1/0/0.1
[UPE1-Virtual-Ethernet1/0/0.1] vlan-type dot1q 10
[UPE1-Virtual-Ethernet1/0/0.1] l2 binding vsi 1
[UPE1-Virtual-Ethernet1/0/0.1] quit
# Configure UPE2.
[UPE2-vpn-instance-vpna] vsi 1 static
[UPE2-vsi-1] pwsignal ldp
[UPE2-vsi-1-ldp] vsi-id 200
[UPE2-vsi-1-ldp] peer 4.4.4.4 negotiation-vc-id 8000 upe
[UPE2-vsi-1-ldp] quit
[UPE2-vsi-1] quit
[UPE2] interface Virtual-Ethernet 1/0/0
[UPE2-Virtual-Ethernet1/0/0] ve-group 10 l2-terminate
[UPE2] interface Virtual-Ethernet 1/0/0.1
[UPE2-Virtual-Ethernet1/0/0.1] l2 binding vsi 1
Step 5 Configure BFD to detect faults in public network links.

NOTE
l Configure BFD to monitor the primary PW and the physical uplink so that traffic can be switched to
the backup link immediately after a fault occurs on the primary link between a PE-AGG and a UPE.
l Configure BFD to monitor the spoke PW.
1. Configure BFD to monitor the primary PW.

[CSG] bfd
[CSG-bfd] quit
[CSG] bfd master bind pw interface gigabitethernet 1/0/3.10 remote-peer
2.2.2.2 pw-ttl auto-calculate
[CSG-bfd-lsp-session-master] discriminator local 2
[CSG-bfd-lsp-session-master] discriminator remote 2
[CSG-bfd-lsp-session-master] commit
[CSG-bfd-lsp-session-master] quit
[PEAGG1] bfd

[PEAGG1-bfd] quit
[PEAGG1] bfd master bind pw vsi 1 peer 1.1.1.1 remote-peer 1.1.1.1 pw-tt auto-
calculate track-interface
[PEAGG1-bfd-lsp-session-master] discriminator local 2
[PEAGG1-bfd-lsp-session-master] discriminator remote 2
[PEAGG1-bfd-lsp-session-master] commit
[PEAGG1-bfd-lsp-session-master] quit
2. Configure BFD to monitor the spoke PW.
# Configure UPE1.
[UPE1] bfd spoke bind pw vsi 1 peer 5.5.5.5 vc-id 8000
[UPE1-bfd-lsp-session-spoke] discriminator local 5
[UPE1-bfd-lsp-session-spoke] discriminator remote 5
[UPE1-bfd-lsp-session-spoke] commit
[UPE1-bfd-lsp-session-spoke] quit
# Configure UPE2.
[UPE2] bfd
[UPE2-bfd] quit
[UPE2] bfd spoke bind pw vsi 1 peer 4.4.4.4 vc-id 8000
[UPE2-bfd-lsp-session-spoke] discriminator local 5
[UPE2-bfd-lsp-session-spoke] discriminator remote 5
[UPE2-bfd-lsp-session-spoke] commit
[UPE2-bfd-lsp-session-spoke] quit
Step 6 Configure L3VPN FRR.

1. Configure a VPN instance on UPEs and BSC-SRs, and then bind the VPN instance to
interfaces.
# The configuration on UPE1 is as follows, the same as the configuration on UPE2.

[UPE1] ip vpn-instance vpna
[UPE1-vpn-instance-vpna] ipv4-family
[UPE1-vpn-instance-vpna-af-ipv4] route-distinguisher 1:1
[UPE1-vpn-instance-vpna-af-ipv4] vpn-target 1:1
[UPE1-vpn-instance-vpna-af-ipv4] quit
[UPE1] interface virtual-ethernet 1/0/1
[UPE1-Virtual-Ethernet1/0/1] ve-group 10 l3-access
[UPE1] interface virtual-ethernet 1/0/1.1
[UPE1-Virtual-Ethernet1/0/1.1] ip binding vpn-instance vpna
[UPE1-Virtual-Ethernet1/0/1.1] ip address 120.0.0.2 24
# The configuration on BSC-SR1 is as follows, the same as the configuration on BSC-SR2.

[BSC-SR1] ip vpn-instance vpna
[BSC-vpn-instance-vpna] ipv4-family
[BSC-SR1-vpn-instance-vpna-af-ipv4] route-distinguisher 1:1
[BSC-SR1-vpn-instance-vpna-af-ipv4] vpn-target 1:1
[BSC-SR1-vpn-instance-vpna-af-ipv4] quit
[BSC-SR1-GigabitEthernet1/0/3] portswitch
[BSC-SR1-GigabitEthernet1/0/3] port link-type trunk
[BSC-SR1-GigabitEthernet1/0/3] port trunk allow-pass vlan 10
[BSC-SR1-GigabitEthernet1/0/0] portswitch
[BSC-SR1-GigabitEthernet1/0/0] port link-type trunk
[BSC-SR1-GigabitEthernet1/0/0] port trunk allow-pass vlan 10
[BSC-SR1] vlan 10
[BSC-SR1-vlan10] quit

[BSC-SR1] interface Vlanif 10

[BSC-SR1-Vlanif10] ip binding vpn-instance vpna
[BSC-SR1-Vlanif10] ip address 120.0.1.1 24
[BSC-SR1-Vlanif10] quit
2. Establish MP-IBGP peer relationships between UPEs and BSC-SRs.
# The configuration on UPE1 is as follows, the same as the configuration on UPE2.

[UPE1] bgp 100
[UPE1-bgp] peer 5.5.5.5 as-number 100
[UPE1-bgp] peer 5.5.5.5 connect-interface loopback 1
[UPE1-bgp] ipv4-family vpnv4
[UPE1-bgp-af-vpnv4] peer 5.5.5.5 enable
[UPE1-bgp-af-vpnv4] quit
# The configuration on BSC-SR1 is as follows, the same as the configuration on BSC-SR2.

[BSC-SR1] bgp 100
[BSC-SR1-bgp] peer 4.4.4.4 as-number 100
[BSC-SR1-bgp] peer 4.4.4.4 connect-interface loopback 0
[BSC-SR1-bgp] ipv4-family vpnv4
[BSC-SR1-bgp-af-vpnv4] peer 4.4.4.4 enable
[BSC-SR1-bgp-af-vpnv4] quit
3. Import direct VPN routes to UPEs and BSC-SRs.
# Configure UPE1. The configuration on UPE1 is as follows, the same as the configuration
on UPE2.
[UPE1-bgp] ipv4-family vpn-instance vpna
[UPE1-bgp-vpna] import-route direct
[UPE1-bgp-vpna] quit
[UPE1-bgp] quit
# Configure BSC-SR1. The configuration on BSC-SR1 is as follows, the same as the

configuration on BSC-SR2.
[BSC-SR1-bgp] ipv4-family vpn-instance vpna
[BSC-SR1-bgp-vpna] import-route direct
[BSC-SR1-bgp-vpna] quit
[BSC-SR1-bgp] quit
4. Configure VPN FRR.
# Configure UPE1. The configurations on UPEs are the same as those on BSC-SRs. Use
UPE1 as an example.
[UPE1] ip vpn-instance vpna
[UPE1-vpn-instance-vpna-af-ipv4] vpn frr route-policy vpna
[UPE1-vpn-instance-vpna-af-ipv4] quit
[UPE1-vpn-instance-vpna] route-policy vpna permit node 5
[UPE1-route-policy] apply backup-nexthop auto
[UPE1-route-policy] quit

Step 7 Configuring VRRP

1. Configure an mVRRP backup group on UPE1 and UPE2 to function as a gateway for the
Ethernet NodeB.
NOTE
Configure mVRRP on the interfaces interconnecting UPE1 and UPE2 to send VRRP Advertisement
packets. In addition, mVRRP needs to be configured to track the status of the physical downlink so
that the master/backup switchover can be performed in the VRRP backup group immediately after
the primary link between a UPE and a PE-AGG fails. Before the configuration, switch the
downstream physical interface to the Layer 2 mode.
# Configure UPE1.
[UPE1-GigabitEthernet1/0/1] portswitch
[UPE1-GigabitEthernet1/0/0] vrrp vrid 20 virtual-ip 172.16.2.3
[UPE1-GigabitEthernet1/0/0] admin-vrrp vrid 20 ignore-if-down
[UPE1-GigabitEthernet1/0/0] vrrp vrid 20 priority 150
[UPE1-GigabitEthernet1/0/0] vrrp vrid 20 track interface gigabitethernet 1/0/1
[UPE1-Virtual-Ethernet1/0/1.1] vrrp vrid 10 virtual-ip 120.0.0.3
[UPE1-Virtual-Ethernet1/0/1.1] vrrp vrid 10 track admin-vrrp interface
gigabitethernet 1/0/0 vrid 20
# Configure UPE2.
[UPE2-GigabitEthernet1/0/1] portswitch
[UPE2-GigabitEthernet1/0/0] vrrp vrid 20 virtual-ip 172.16.2.3
[UPE2-GigabitEthernet1/0/0] admin-vrrp vrid 20 ignore-if-down
[UPE2-GigabitEthernet1/0/0] vrrp vrid 20 track interface gigabitethernet 1/0/1
[UPE2-Virtual-Ethernet1/0/1.1] vrrp vrid 10 track admin-vrrp interface
gigabitethernet 1/0/0 vrid 20
2. Configure a VRRP backup group on BSC-SRs to function as a gateway for the RNC.
[RSG1] interface Vlanif 10
[RSG1-Vlanif10] vrrp vrid 1 virtual-ip 120.0.1.3
[RSG1-Vlanif10] vrrp vrid 1 priority 150
[RSG1-Vlanif10] quit

NOTE
Configure the RNC as follows:

l Switch the Ethernet interface from the Layer 3 mode to the Layer 2 mode; add the interface to a
VLAN; create a VLANIF interface.
l Configure a VLANIF interface and assign an IP address to the VLANIF interface. Ensure that
the IP address is in the same network segment with the virtual IP addresses configured on BSC-
SRs.
On the Ethernet NodeB, you need to create a sub-interface on an Ethernet interface, configure 802.1Q
as the encapsulation type for the sub-interface, and configure a VLAN ID for the sub-interface.
----End
Configuration Files
l Configuration file of the CSG
#
sysname CSG
#
bfd
#
mpls lsr-id 1.1.1.1
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls rsvp-te hello full-gr
mpls te cspf
#
mpls l2vpn
#
mpls ldp
graceful-restart
#
#
mpls ldp remote-peer 2.2.2.2
remote-ip 2.2.2.2
#
remote-ip 3.3.3.3
#
undo shutdown
#
ip address ppp-negotiate
mpls l2vc 2.2.2.2 100 tunnel-policy policy1 ip-interworking
mpls l2vc 3.3.3.3 200 tunnel-policy policy1 ip-interworking secondary
mpls l2vpn redundancy master
mpls l2vpn stream-dual-receiving
#
link-protocol ppp
#
interface GigabitEthernet1/0/1
undo shutdown
ip address 172.16.1.1 255.255.255.0
mpls
mpls te

mpls rsvp-te
mpls rsvp-te hello
#
undo shutdown
ip address 172.16.4.1 255.255.255.0
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
interface Tunnel1/0/1
ip address unnumbered interface LoopBack0
tunnel-protocol mpls te
destination 2.2.2.2
mpls te tunnel-id 100
mpls te reserved-for-binding
mpls te commit
#
destination 3.3.3.3
mpls te commit
#
ospf 100
opaque-capability enable
graceful-restart
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 172.16.1.0 0.0.0.255
network 172.16.4.0 0.0.0.255
mpls-te enable
#
tunnel-policy policy1
tunnel binding destination 2.2.2.2 te Tunnel1/0/1
#
bfd master bind pw interface GigabitEthernet1/0/3.10 remote-peer 2.2.2.2 pw-
ttl auto-calculate
discriminator local 2
discriminator remote 2
detect-multiplier 50
commit
#
return
l Configuration file of PE-AGG1

#
sysname PEAGG1
#
bfd
#
mpls lsr-id 2.2.2.2
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
#
mpls l2vpn

#
mpls ldp
graceful-restart
#
#
remote-ip 1.1.1.1
#
undo shutdown
ip address 172.16.1.2 255.255.255.0
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
undo shutdown
#
interface GigabitEthernet1/0/3.10
vlan-type dot1q 10
local-ce mac broadcast
remote-ce ip 120.0.0.1
mpls l2vc 1.1.1.1 100 tunnel-policy policy1 ignore-standby-state
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
destination 1.1.1.1
mpls te commit
#
ospf 100
graceful-restart
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 172.16.1.0 0.0.0.255
mpls-te enable
#
#
bfd master bind pw vsi 1 peer 1.1.1.1 remote-peer 1.1.1.1 pw-ttl auto-calculate
track-interface
commit
#
return
l Configuration file of PE-AGG2

#
sysname PEAGG2
#
bfd
#
mpls lsr-id 3.3.3.3
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello

mpls te cspf
#
mpls l2vpn
#
mpls ldp
graceful-restart
#
#
remote-ip 1.1.1.1
#
undo shutdown
ip address 172.16.4.2 255.255.255.0
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
undo shutdown
#
interface GigabitEthernet1/0/3.10
vlan-type dot1q 10
mpls l2vc 1.1.1.1 100 tunnel-policy policy1 ignore-standby-state
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
destination 1.1.1.1
mpls te commit
#
ospf 100
graceful-restart
area 0.0.0.0
network 3.3.3.3 0.0.0.0
network 172.16.4.0 0.0.0.255
mpls-te enable
#
#
bfd master bind pw vsi 1 peer 1.1.1.1 remote-peer 1.1.1.1 pw-ttl auto-calculate
track-interface
commit
#
return
l Configuration file of UPE1

#
sysname UPE1
#
ip vpn-instance vpna
ipv4-family
route-distinguisher 1:1
vpn frr route-policy vpna
vpn-target 1:1 export-extcommunity

vpn-target 1:1 import-extcommunity

#
bfd
#
mpls lsr-id 4.4.4.4
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
#
mpls l2vpn
#
vsi 1 static
pwsignal ldp
vsi-id 100
peer 5.5.5.5 negotiation-vc-id 8000 upe
#
mpls ldp
graceful-restart
#
#
undo shutdown
ip address 172.16.2.2 255.255.255.0
vrrp vrid 20 virtual-ip 172.16.2.3
admin-vrrp vrid 20 ignore-if-down
vrrp vrid 20 priority 150
vrrp vrid 20 track interface gigabitethernet 1/0/1
mpls
mpls ldp
#
portswitch
undo shutdown
#
undo shutdown
ip address 172.16.3.1 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 172.16.8.1 255.255.255.0
mpls
mpls ldp
#
interface Virtual-Ethernet1/0/0
ve-group 10 l2-terminate
#
interface Virtual-Ethernet1/0/0.1
vlan-type dot1q 10
l2 binding vsi 1
#
ve-group 10 l3-access
#
vlan-type dot1q 10
ip binding vpn-instance vpna
ip address 120.0.0.2 255.255.255.0
vrrp vrid 10 track admin-vrrp interface GigabitEthernet1/0/0 vrid 20
#
interface LoopBack1

ip address 4.4.4.4 255.255.255.255

#
bgp 100
peer 5.5.5.5 as-number 100
peer 5.5.5.5 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 5.5.5.5 enable
peer 6.6.6.6 enable
peer 7.7.7.7 enable
#
ipv4-family vpnv4
policy vpn-target
peer 5.5.5.5 enable
peer 6.6.6.6 enable
peer 7.7.7.7 enable
#
ipv4-family vpn-instance vpna
import-route direct
#
ospf 100
graceful-restart
area 0.0.0.1
network 4.4.4.4 0.0.0.0
network 172.16.3.0 0.0.0.255
network 172.16.2.0 0.0.0.255
network 172.16.8.0 0.0.0.255
mpls-te enable
#
route-policy vpna permit node 5
apply backup-nexthop auto
#
bfd spoke bind pw vsi 1 peer 5.5.5.5 vc-id 8000
commit
#
return
l Configuration file of UPE2

#
sysname UPE2
#
ipv4-family
#
bfd
#
mpls lsr-id 5.5.5.5
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
#
mpls l2vpn

#
vsi 1 static
pwsignal ldp
vsi-id 100
peer 4.4.4.4 negotiation-vc-id 8000 upe
#
mpls ldp
graceful-restart
#
#
undo shutdown
ip address 172.16.2.1 255.255.255.0
vrrp vrid 20 track interface gigabitethernet 1/0/1
mpls
mpls ldp
#
portswitch
undo shutdown
#
undo shutdown
ip address 172.16.6.1 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 172.16.7.1 255.255.255.0
mpls
mpls ldp
#
#
vlan-type dot1q 10
l2 binding vsi 1
#
#
vlan-type dot1q 10
ip address 120.0.0.2 255.255.255.0
#
interface LoopBack1
ip address 5.5.5.5 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 4.4.4.4 enable
peer 6.6.6.6 enable

peer 7.7.7.7 enable

#
ipv4-family vpnv4
policy vpn-target
peer 4.4.4.4 enable
peer 6.6.6.6 enable
peer 7.7.7.7 enable
#
import-route direct
#
ospf 100
graceful-restart
area 0.0.0.1
network 5.5.5.5 0.0.0.0
network 172.16.6.0 0.0.0.255
network 172.16.2.0 0.0.0.255
network 172.16.7.0 0.0.0.255
mpls-te enable
#
#
bfd spoke bind pw vsi 1 peer 4.4.4.4 vc-id 8000
commit
#
return
l Configuration file of BSC-SR1

#
sysname BSC-SR1
#
vlan batch 10
#
ipv4-family
#
mpls lsr-id 6.6.6.6
mpls
#
mpls ldp
graceful-restart
#
#
interface Vlanif10
ip address 120.0.1.1 255.255.255.0
#
portswitch
undo shutdown
port link-type trunk
port trunk allow-pass vlan 10
#
undo shutdown
ip address 172.16.3.2 255.255.255.0
mpls

mpls ldp
#
undo shutdown
ip address 172.16.7.2 255.255.255.0
mpls
mpls ldp
#
portswitch
undo shutdown
#
interface LoopBack1
ip address 6.6.6.6 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 4.4.4.4 enable
peer 5.5.5.5 enable
peer 7.7.7.7 enable
#
ipv4-family vpnv4
policy vpn-target
peer 4.4.4.4 enable
peer 5.5.5.5 enable
peer 7.7.7.7 enable
#
import-route direct
#
ospf 100
graceful-restart
area 0.0.0.1
network 6.6.6.6 0.0.0.0
network 172.16.3.0 0.0.0.255
network 172.16.7.0 0.0.0.255
mpls-te enable
#
#
return
l Configuration file of BSC-SR2

#
sysname BSC-SR2
#
vlan batch 10
#
ipv4-family
route-distinguisher 11
vpn-target 11 export-extcommunity
vpn-target 11 import-extcommunity
#

mpls lsr-id 7.7.7.7

mpls
#
mpls ldp
graceful-restart
#
interface Vlanif10
ip address 120.0.1.2 255.255.255.0
#
portswitch
undo shutdown
#
undo shutdown
ip address 172.16.6.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 172.16.8.2 255.255.255.0
mpls
mpls ldp
#
portswitch
undo shutdown
#
interface LoopBack1
ip address 7.7.7.7 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 4.4.4.4 enable
peer 5.5.5.5 enable
peer 6.6.6.6 enable
#
ipv4-family vpnv4
policy vpn-target
peer 4.4.4.4 enable
peer 5.5.5.5 enable
peer 6.6.6.6 enable
#
import-route direct
#
ospf 100
graceful-restart
area 0.0.0.1
network 7.7.7.7 0.0.0.0
network 172.16.8.0 0.0.0.255

network 172.16.6.0 0.0.0.255

mpls-te enable
#
#
return
3.13.5 Example for Configuring an Integrated IP RAN (IP-

Interworking) with TDM BTSs
After being channelized, TDM Base Transceiver Stations (BTSs) become IP BTSs, which access
CSGs by using Multi-Link Point-to-Point (ML-PPP). In this case, an IP-interworking-enabled
L2VPN is required.
After being channelized, TDM BTSs become IP BTSs, which access CSGs by using ML-PPP.
In this case, an IP-interworking-enabled L2VPN is required. This solution is similar to that for
Ethernet NodeBs.
Figure 3-10 Networking diagram for configuring an integrated IP RAN (IP-interworking) with
TDM BTSs
PWE3
SR1 RSG1
CSG
ML PPP
NodeB RNC
SR2 RSG2
L2VPN L3VPN
Device Interface Peer Device IP Address
CSG GE1/0/1 SR1 172.16.1.1/24
GE1/0/2 SR2 172.16.4.1/24
Serial2/3/1 NodeB -
LoopBack0 - 1.1.1.1/32
SR1 GE1/0/0 SR2 172.16.2.2/24
GE1/0/1 CSG 172.16.1.2/24

GE1/0/3 RSG1 172.16.3.1/24
GE1/0/4 RSG2 172.16.8.0/24
LoopBack0 - 2.2.2.2/32
SR2 GE1/0/0 SR1 172.16.2.1/24
GE1/0/2 CSG 172.16.4.2/24
GE1/0/3 RSG2 172.16.6.1/24
GE1/0/4 RSG1 172.16.7.1/24
LoopBack0 - 3.3.3.3/32
RSG1 GE1/0/0 RSG2 -
GE1/0/1 SR1 172.16.3.2/24
GE1/0/2 SR2 172.16.7.2/24
GE1/0/3 RNC -
LoopBack0 - 4.4.4.4/32
RSG2 GE1/0/0 RSG1 -
GE1/0/1 SR2 172.16.6.2/24
GE1/0/2 SR1 172.16.8.2/24
GE1/0/3 RNC -
LoopBack0 - 5.5.5.5/32
1. Configure IP addresses and routes.

2. Configure MPLS and public network tunnels:
l Configure a TE tunnel protection group on the CSG and SRs.
l Configure LSPs between SRs and RSGs.
3. Configure PW redundancy in independent mode:
l Configure MPLS LDP remote sessions between the CSG and SRs.
l Configure service PWs.
l Configure an mPW and a bypass PW, and then associate the bypass PW with the mPW.
l Configure BFD to monitor the mPW.
l Configure VRRP to determine the primary PW.
4. Configure an L3VPN.
l Configure the same VPN instance on SRs and RSGs.
l Configure a VE group on SRs and bind the VPN instance to the L3VE sub-interfaces.
l Establish MP-IBGP peer relationships between SRs and RSGs.

l Import direct VPN routes to SRs and RSGs.

l Configure VPN FRR.
5. Configure BFD to detect faults on public network links.
6. Configure VRRP on RSGs to determine their roles in the VRRP backup group.
Data Preparation
l Interface number, interface IP address, and OSPF process ID
l LSR ID
l L2VC destination address, VC ID, and VC type
l BFD session name, local discriminator, and remote discriminator
l VE group number
l VRRP backup group number and priority
Procedure
Step 1 Assign an IP address to and configure a routing protocol on each interface.
1. Assign an IP address to each interface.
2. Configure a routing protocol on the CSG, SR1, SR2, RSG1, and RSG2 to make them
routable. In this example, OSPF is used.
After the configuration is complete, run the display ip routing-table command on the CSG,
SRs, and RSGs. You can view the routes learned from each other. Note that when configuring
OSPF, you need to advertise 32-bit loopback interface addresses (LSR IDs) of the CSG, SRs,
and RSGs.
The detailed configuration is not mentioned here.
Step 2 Configure basic MPLS functions and public network tunnels.
NOTE
l Configure explicit paths between the CSG and SR1 and between the CSG and SR2.
l Configure LSPs between SRs and between SRs and RSGs.
l To improve performance, enable RSVP GR, LDP GR, and OSPF GR.
1. Enable MPLS TE and RSVP-TE and configure CSPF and OSPF TE.
[CSG] mpls lsr-id 1.1.1.1
[CSG] mpls
[CSG-mpls] mpls te
[CSG-mpls] mpls rsvp-te
[CSG-mpls] mpls rsvp-te hello
[CSG-mpls] mpls rsvp-te hello full-gr
[CSG-mpls] mpls te cspf
[CSG-mpls] quit
[CSG] interface GigabitEthernet1/0/1

[CSG] interface GigabitEthernet1/0/2

[CSG] ospf 100
[CSG-ospf-100] opaque-capability enable
[CSG-ospf-100] graceful-restart
[CSG-ospf-100] area 0
[CSG-ospf-100-area-0.0.0.0] mpls-te enable
[CSG-ospf-100-area-0.0.0.0] quit
[CSG-ospf-100] quit
# Configure SR1.
[SR1] mpls lsr-id 2.2.2.2
[SR1] mpls
[SR1-mpls] mpls te
[SR1-mpls] mpls rsvp-te
[SR1-mpls] mpls rsvp-te hello
[SR1-mpls] mpls rsvp-te hello full-gr
[SR1-mpls] mpls te cspf
[SR1-mpls] quit
[SR1] mpls ldp
[SR1] graceful-restart
[SR1-mpls-ldp] quit
[SR1] interface gigabitEthernet1/0/1
[SR1-GigabitEthernet1/0/1] mpls
[SR1-GigabitEthernet1/0/1] mpls te
[SR1-GigabitEthernet1/0/1] mpls rsvp-te
[SR1-GigabitEthernet1/0/1] mpls rsvp-te hello
[SR1-GigabitEthernet1/0/1] quit
[SR1-GigabitEthernet1/0/3] mpls ldp
[SR1] interface GigabitEthernet1/0/0
[SR1] ospf 100
[SR1-ospf-100] opaque-capability enable
[SR1-ospf-100] graceful-restart
[SR1-ospf-100] area 0
[SR1-ospf-100-area-0.0.0.0] mpls-te enable
[SR1-ospf-100-area-0.0.0.0] quit
[SR1-ospf-100] quit
# Configure SR2.
[SR2] mpls lsr-id 3.3.3.3
[SR2] mpls
[SR2-mpls] mpls te
[SR2-mpls] mpls rsvp-te
[SR2-mpls] mpls rsvp-te hello
[SR2-mpls] mpls rsvp-te hello full-gr
[SR2-mpls] mpls te cspf
[SR2-mpls] quit
[SR2] mpls ldp
[SR2] graceful-restart
[SR2-mpls-ldp] quit

[SR2-GigabitEthernet1/0/2] mpls te
[SR2-GigabitEthernet1/0/2] mpls rsvp-te
[SR2-GigabitEthernet1/0/2] mpls rsvp-te hello
[SR2] ospf 100
[SR2-ospf-100] opaque-capability enable
[SR2-ospf-100] graceful-restart
[SR2-ospf-100] area 0
[SR2-ospf-100-area-0.0.0.0] mpls-te enable
[SR2-ospf-100-area-0.0.0.0] quit
[SR2-ospf-100] quit
# Configure RSG1.
[RSG1] mpls lsr-id 4.4.4.4
[RSG1] mpls
[RSG1-mpls] quit
[RSG1] mpls ldp
[RSG1-mpls-ldp] graceful-restart
[RSG1-mpls-ldp] quit
[RSG1] interface GigabitEthernet1/0/1
[RSG1-GigabitEthernet1/0/1] mpls
[RSG1-GigabitEthernet1/0/1] mpls ldp
[RSG1-GigabitEthernet1/0/1] quit
[RSG1] ospf 100
[RSG1-ospf-100] opaque-capability enable
[RSG1-ospf-100] graceful-restart
[RSG1-ospf-100] quit
# Configure RSG2.
[RSG2] mpls lsr-id 5.5.5.5
[RSG2] mpls
[RSG2-mpls] quit
[RSG2] mpls ldp
[RSG2-mpls-ldp] graceful-restart
[RSG2-mpls-ldp] quit
[RSG2] ospf 100
[RSG2-ospf-100] opaque-capability enable
[RSG2-ospf-100] graceful-restart
[RSG2-ospf-100] quit
2. Configure explicit paths for the primary and backup MPLS TE tunnels.

[CSG] explicit-path to_sr1

[CSG-explicit-path-to_sr1] next hop 172.16.1.2
[CSG-explicit-path-to_sr1] quit
[CSG] explicit-path to_sr2
[CSG-explicit-path-to_sr2] quit
# Configure SR1.
[SR1] explicit-path to_csg
[SR1-explicit-path-to_csg] next hop 172.16.1.1
[SR1-explicit-path-to_csg] quit
# Configure SR2.
[SR2] explicit-path to_csg
[SR2-explicit-path-to_csg] quit
3. Configure MPLS TE tunnel interfaces and hot backup.

[CSG-Tunnel1/0/1] mpls te record-route
[CSG-Tunnel1/0/1] mpls te path explicit-path to_sr1
[CSG-Tunnel1/0/1] mpls te backup hot-standby wtr 15
[CSG-Tunnel1/0/2] mpls te record-route
[CSG-Tunnel1/0/2] mpls te path explicit-path to_sr2
[CSG-Tunnel1/0/2] mpls te backup hot-standby wtr 15
# Configure SR1.
[SR1] interface tunnel 1/0/1
[SR1-Tunnel1/0/1] ip address unnumbered interface loopback 0
[SR1-Tunnel1/0/1] tunnel-protocol mpls te
[SR1-Tunnel1/0/1] destination 1.1.1.1
[SR1-Tunnel1/0/1] mpls te tunnel-id 100
[SR1-Tunnel1/0/1] mpls te record-route
[SR1-Tunnel1/0/1] mpls te signal-protocol rsvp-te
[SR1-Tunnel1/0/1] mpls te path explicit-path to_csg
[SR1-Tunnel1/0/1] mpls te backup hot-standby wtr 15
[SR1-Tunnel1/0/1] mpls te reserved-for-binding
[SR1-Tunnel1/0/1] mpls te commit
[SR1-Tunnel1/0/1] quit
# Configure SR2.

[SR2] interface tunnel 1/0/2

[SR2-Tunnel1/0/2] ip address unnumbered interface loopback 0
[SR2-Tunnel1/0/2] tunnel-protocol mpls te
[SR2-Tunnel1/0/2] destination 1.1.1.1
[SR2-Tunnel1/0/2] mpls te tunnel-id 200
[SR2-Tunnel1/0/2] mpls te record-route
[SR2-Tunnel1/0/2] mpls te signal-protocol rsvp-te
[SR2-Tunnel1/0/2] mpls te path explicit-path to_csg
[SR2-Tunnel1/0/2] mpls te backup hot-standby wtr 15
[SR2-Tunnel1/0/2] mpls te reserved-for-binding
[SR2-Tunnel1/0/2] mpls te commit
[SR2-Tunnel1/0/2] quit
4. Configure a tunnel policy.

[CSG] tunnel-policy policy1
[CSG-tunnel-policy-policy1] tunnel binding destination 2.2.2.2 te Tunnel1/0/1
[CSG-tunnel-policy-policy1] tunnel binding destination 3.3.3.3 te Tunnel1/0/2
[CSG-tunnel-policy-policy1] quit
# Configure SR1.
[SR1] tunnel-policy policy1
[SR1-tunnel-policy-policy1] tunnel binding destination 1.1.1.1 te Tunnel1/0/1
[SR1-tunnel-policy-policy1] quit
# Configure SR2.
[SR2] tunnel-policy policy1
[SR2-tunnel-policy-policy1] tunnel binding destination 1.1.1.1 te Tunnel1/0/2
[SR2-tunnel-policy-policy1] quit
Step 3 Configure PW redundancy.

1. Configure MPLS LDP remote sessions between the CSG and SRs.
NOTE
In this configuration example, TE tunnels are configured between the CSG and SRs, and MPLS LDP is
not required. PWE3, however, uses extended LDP signaling to distribute VPN labels. Therefore, MPLS
LDP remote sessions have to be configured between the CSG and SRs. An LDP LSP is configured to
directly connect SRs, and no LDP remote session needs to be configured between SRs.

[CSG] mpls ldp
[CSG-mpls-ldp] quit
# Configure SR1.
[SR1] mpls ldp
[SR1-mpls-ldp] quit
[SR1] mpls ldp remote-peer 1.1.1.1
[SR1-mpls-ldp-remote-1.1.1.1] remote-ip 1.1.1.1
[SR1-mpls-ldp-remote-1.1.1.1] quit
# Configure SR2.
[SR2] mpls ldp
[SR2-mpls-ldp] quit
[SR2] mpls ldp remote-peer 1.1.1.1

[SR2-mpls-ldp-remote-1.1.1.1] remote-ip 1.1.1.1

[SR2-mpls-ldp-remote-1.1.1.1] quit
# Verify the configuration. Run the display mpls ldp session all command on the CSG
and SRs. You can view that the LDP session is in the Operational state. Use the CSG as an
example.
[CSG] display mpls ldp session all
LDP Session(s) in Public Network

Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
A '*' before a session means the session is being deleted.
------------------------------------------------------------------------------
PeerID Status LAM SsnRole SsnAge KASent/Rcv
------------------------------------------------------------------------------
2.2.2.2:0 Operational DU Passive 0000:00:47 190/190
3.3.3.3:0 Operational DU Passive 0000:00:47 190/190
------------------------------------------------------------------------------
TOTAL: 2 session(s) Found.
2. Configure service PWs.

[CSG] mpls l2vpn
[CSG-l2vpn] quit
[CSG] controller Cpos2/3/1
[CSG-Cpos2/3/1] undo shutdown
[CSG-Cpos2/3/1] quit
[CSG] interface Serial2/3/1/1:0
[CSG-Serial2/3/1/1:0] ppp mp Mp-group 2/3/1
[CSG-Serial2/3/1/1:0] quit
[CSG] interface Mp-group2/3/1
[CSG-Mp-group2/3/1] ip address ppp-negotiate
[CSG-Mp-group2/3/1] mpls l2vc 2.2.2.2 100 tunnel-policy policy1 ip-interworking
[CSG-Mp-group2/3/1] mpls l2vc 3.3.3.3 200 ip-interworking tunnel-policy
policy1 secondary
[CSG-Mp-group2/3/1] mpls l2vpn redundancy master
[CSG-Mp-group2/3/1] mpls l2vpn stream-dual-receiving
[CSG-Mp-group2/3/1] quit
# Configure SR1.
[SR1] mpls l2vpn
[SR1-l2vpn] quit
[SR1] interface virtual-ethernet 1/0/0
[SR1-Virtual-Ethernet1/0/0] ve-group 1 l2-terminate
[SR1-Virtual-Ethernet1/0/0] quit
[SR1] interface virtual-ethernet 1/0/0.1
[SR1-Virtual-Ethernet1/0/0.1] vlan-type dot1q 10
[SR1-Virtual-Ethernet1/0/0.1] local-ce mac broadcast
[SR1-Virtual-Ethernet1/0/0.1] remote-ce ip 120.0.0.1
[SR1-Virtual-Ethernet1/0/0.1] mpls l2vc 1.1.1.1 100 tunnel-policy policy1 ip-
interworking
[SR1-Virtual-Ethernet1/0/0.1] mpls l2vc 3.3.3.3 300 ip-interworking bypass
[SR1-Virtual-Ethernet1/0/0.1] quit
# Configure SR2.
[SR2] mpls l2vpn
[SR2-l2vpn] quit


[SR2-Virtual-Ethernet1/0/0] ve-group 1 l2-terminate
[SR2-Virtual-Ethernet1/0/0.1] local-ce mac broadcast
[SR2-Virtual-Ethernet1/0/0.1] remote-ce ip 120.0.0.1
[SR2-Virtual-Ethernet1/0/0.1] mpls l2vc 1.1.1.1 200 tunnel-policy policy1 ip-
interworking
[SR2-Virtual-Ethernet1/0/0.1] mpls l2vc 2.2.2.2 300 ip-interworking bypass
3. Configure an mPW and a bypass PW, and then associate the bypass PW with the mPW.
# Configure SR1.
[SR1] interface loopback 1
[SR1-LoopBack1] mpls l2vc 3.3.3.3 400 control-word admin
[SR1-LoopBack1] quit
[SR1-Virtual-Ethernet1/0/0.1] mpls l2vc bypass track admin-vc interface
LoopBack1
# Configure SR2.
[SR2] interface loopback 1
[SR2-LoopBack1] mpls l2vc 2.2.2.2 400 control-word admin
[SR2-LoopBack1] quit
[SR2-Virtual-Ethernet1/0/0.1] mpls l2vc bypass track admin-vc interface
LoopBack1
# Verify the configuration. Run the display mpls l2vc brief command on the CSG and
SRs. You can view that service PWs and the mPW are in the Up state. Use SR1 as an
example.
[SR1] display mpls l2vc brief
Total ldp vc : 3 3 up 0 down
*Client Interface : Virtual-Ethernet1/0/0.1

AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 100
VC Type : VLAN
session state : up
link state : up
*Client Interface : Virtual-Ethernet1/0/0.1

AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 300
VC Type : VLAN
session state : up
link state : up
*Client Interface : LoopBack1

Administrator PW : yes
AC status : up

VC State : up
Label state : 0
Token state : 0
VC ID : 400
session state : up
link state : up
4. Configure BFD to monitor the mPW.

# Configure SR1.
[SR1] bfd
[SR1-bfd] quit
[SR1] bfd bypass bind pw interface loopback 1
[SR1-bfd-lsp-session-SR1] discriminator local 2
[SR1-bfd-lsp-session-SR1] discriminator remote 2
[SR1-bfd-lsp-session-SR1] commit
[SR1-bfd-lsp-session-SR1] quit
# Configure SR2.
[SR2] bfd
[SR2-bfd] quit
[SR2] bfd bypass bind pw interface loopback 1
[SR2-bfd-lsp-session-SR2] discriminator local 2
[SR2-bfd-lsp-session-SR2] discriminator remote 2
[SR2-bfd-lsp-session-SR2] commit
[SR2-bfd-lsp-session-SR2] quit
# Verify the configuration. Run the display bfd session all command on SRs. You can
view that BFD sessions are in the Up state. Use SR1 as an example.
[SR1] display bfd session all
------------------------------------------------------------------------------
--
Local Remote PeerIpAddr State Type InterfaceName
------------------------------------------------------------------------------
--
2 2 --.--.--.-- Up S_PW(M) LoopBack1
------------------------------------------------------------------------------
--
Total UP/DOWN Session Number : 1/0
5. Configure VRRP to determine the primary PW.

NOTE
If PW redundancy in independent mode is configured, VRRP has to be configured on SRs to
determine which SR is the master device in the VRRP backup group. After PWs are associated with
mVRRP, the primary PW is determined.
# Configure SR1.
[SR1] interface gigabitethernet 1/0/0
[SR1-GigabitEthernet1/0/0] vrrp vrid 1 virtual-ip 172.16.2.254
[SR1-GigabitEthernet1/0/0] admin-vrrp vrid 1 ignore-if-down
[SR1-GigabitEthernet1/0/0] vrrp vrid 1 priority 150
[SR1-Virtual-Ethernet1/0/0.1] mpls l2vc track admin-vrrp interface
gigabitethernet 1/0/0 vrid 1 pw-redundancy
# Configure SR2.
[SR2] interface gigabitethernet 1/0/0
[SR2-GigabitEthernet1/0/0] vrrp vrid 1 virtual-ip 172.16.2.254

[SR2-GigabitEthernet1/0/0] admin-vrrp vrid 1 ignore-if-down

[SR2-Virtual-Ethernet1/0/0.1] mpls l2vc track admin-vrrp interface
gigabitethernet 1/0/0 vrid 1 pw-redundancy
# Verify the configuration. Run the display vrrp command on SRs. You can view the role
of each SR in the VRRP backup group. Use SR1 as an example. The default VRRP priority
value is 100, and SR1 whose VRRP priority value is set to 150 functions as the master in
the VRRP backup group.
[SR1] display vrrp
GigabitEthernet1/0/0 | Virtual Router 1
State : Master
Virtual IP : 172.16.2.254
Master IP : 172.16.2.2
PriorityRun : 150
PriorityConfig : 150
MasterPriority : 150
Preempt : YES Delay Time : 0
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Config type : admin-vrrp
Create time : 2010-09-05 15:25:47
Last change time : 2010-09-05 15:25:51
Step 4 Configure an L3VPN.

1. Configure a VPN instance on SR1 and RSG1, and then bind the VPN instance to interfaces.
# The configuration on SR1 is as follows, the same as the configuration on SR2.

[SR1] ip vpn-instance vpna
[SR1-vpn-instance-vpna] ipv4-family
[SR1-vpn-instance-vpna-af-ipv4] route-distinguisher 1:1
[SR1-vpn-instance-vpna-af-ipv4] vpn-target 1:1
[SR1-vpn-instance-vpna-af-ipv4] quit
[SR1-Virtual-Ethernet1/0/1] ve-group 1 l3-access
[SR1-Virtual-Ethernet1/0/1.1] ip binding vpn-instance vpna
[SR1-Virtual-Ethernet1/0/1.1] ip address 120.0.0.2 24
# The configuration on RSG1 is as follows, the same as the configuration on RSG2.

[RSG1] ip vpn-instance vpna
[RSG1-vpn-instance-vpna] ipv4-family
[RSG1-vpn-instance-vpna-af-ipv4] route-distinguisher 1:1
[RSG1-vpn-instance-vpna-af-ipv4] vpn-target 1:1
[RSG1-vpn-instance-vpna-af-ipv4] quit
[RSG1-GigabitEthernet1/0/3] portswitch
[RSG1-GigabitEthernet1/0/3] port link-type trunk
[RSG1-GigabitEthernet1/0/3] port trunk allow-pass vlan 10
[RSG1-GigabitEthernet1/0/0] portswitch
[RSG1-GigabitEthernet1/0/0] port link-type trunk
[RSG1-GigabitEthernet1/0/0] port trunk allow-pass vlan 10

[RSG1] vlan 10
[RSG1-vlan10] quit
[RSG1-Vlanif10] ip binding vpn-instance vpna
[RSG1-Vlanif10] ip address 120.0.1.1 24
2. Establish MP-IBGP peer relationships between SRs and RSGs.

[SR2] bgp 100
[SR2-bgp] graceful-restart
[SR2-bgp] peer 2.2.2.2 as-number 100
[SR2-bgp] peer 2.2.2.2 connect-interface LoopBack0
[SR2-bgp] ipv4-family vpnv4
[SR2-bgp-af-vpnv4] peer 2.2.2.2 enable
[SR2-bgp-af-vpnv4] quit

[RSG1] bgp 100
[RSG1-bgp] graceful-restart
[RSG1-bgp] peer 2.2.2.2 as-number 100
[RSG1-bgp] peer 2.2.2.2 connect-interface LoopBack0
[RSG1-bgp] ipv4-family vpnv4
[RSG1-bgp-af-vpnv4] peer 2.2.2.2 enable
[RSG1-bgp-af-vpnv4] quit
3. Import direct VPN routes to SRs and RSGs.

[SR2-bgp] ipv4-family vpn-instance vpna
[SR2-bgp-vpna] import-route direct
[SR2-bgp-vpna] quit
[SR2-bgp] quit

[RSG1-bgp] ipv4-family vpn-instance vpna
[RSG1-bgp-vpna] import-route direct
[RSG1-bgp-vpna] quit
[RSG1-bgp] quit
4. Configure VPN FRR.
# The configuration of RSG1 is as follows, the same as the configuration on SRs and RSG2.
[RSG1] ip vpn-instance vpna
[RSG1-vpn-instance-vpna-af-ipv4] vpn frr route-policy vpna
[RSG1-vpn-instance-vpna-af-ipv4] quit
[RSG1-vpn-instance-vpna] route-policy vpna permit node 5
[RSG1-route-policy] apply backup-nexthop auto
[RSG1-route-policy] quit

Step 5 Configure VRRP on SR1 and SR2 to determine a gateway for Ethernet NodeBs.
# Configure SR1.
[SR1-Virtual-Ethernet1/0/1.1] vrrp vrid 10 virtual-ip 120.0.0.3
[SR1-Virtual-Ethernet1/0/1.1] vrrp vrid 10 track admin-vrrp interface
gigabitethernet1/0/0 vrid 20
# Configure SR2.
[SR1-Virtual-Ethernet1/0/1.1] vrrp vrid 10 virtual-ip 120.0.0.3
[SR2-Virtual-Ethernet1/0/1.1] vrrp vrid 10 track admin-vrrp interface
gigabitethernet1/0/0 vrid 20
Step 6 Configure VRRP on RSGs to determine their roles in the VRRP backup group.
# Configure RSG1.
[RSG1-Vlanif10] vrrp vrid 1 priority 150
# Configure RSG2.
NOTE
Configure the RNC as follows:

l Configure an Eth-Trunk link to determine the active and standby links.
l Configure a VLANIF interface and assign an IP address to the VLANIF interface. Ensure that the IP address
is in the same network segment with the virtual IP addresses configured on RSGs.
On an IP BTS, you need to create a sub-interface on an Ethernet interface, encapsulate 802.1Q on the sub-
interface, and associate a VLAN ID with the sub-interface.
----End
Configuration Files
l Configuration file of the CSG
#
sysname CSG
#
mpls lsr-id 1.1.1.1
mpls
mpls te
mpls rsvp-te
mpls te cspf
#
mpls l2vpn
#
#
explicit-path to_sr1
next hop 172.16.1.2
next hop 2.2.2.2
#
explicit-path to_sr2
next hop 172.16.4.2

next hop 3.3.3.3

mpls ldp
#
#
remote-ip 2.2.2.2
#
remote-ip 3.3.3.3
#
undo shutdown
#
ip address ppp-negotiate
mpls l2vc 3.3.3.3 200 tunnel-policy policy1 ip-interworking secondary
mpls l2vpn redundancy master
mpls l2vpn stream-dual-receiving
#
link-protocol ppp
#
undo shutdown
ip address 172.16.1.1 255.255.255.0
mpls
mpls te
mpls rsvp-te
#
undo shutdown
ip address 172.16.4.1 255.255.255.0
mpls
mpls te
mpls rsvp-te
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.255
#
destination 2.2.2.2
mpls te record-route
mpls te path explicit-path to_sr1
mpls te backup hot-standby wtr 15
mpls te commit
#
destination 3.3.3.3
mpls te path explicit-path to_sr2
mpls te backup hot-standby
mpls te commit
#

ospf 100
graceful-restart
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 172.16.1.0 0.0.0.255
network 172.16.4.0 0.0.0.255
mpls-te enable
#
tunnel binding destination 2.2.2.2 te Tunnel1/0/1 te Tunnel1/0/1
tunnel binding destination 3.3.3.3 te Tunnel1/0/2 te Tunnel1/0/2
#
return
l Configuration file of SR1

#
sysname SR1
#
ipv4-family
#
bfd
#
mpls lsr-id 2.2.2.2
mpls
mpls te
mpls rsvp-te
mpls te cspf
#
mpls l2vpn
#
explicit-path to_csg
next hop 172.16.1.1
next hop 1.1.1.1
#
mpls ldp
graceful-restart
#
#
remote-ip 1.1.1.1
#
undo shutdown
ip address 172.16.2.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 172.16.1.2 255.255.255.0
mpls
mpls te
mpls rsvp-te
#
#
undo shutdown
ip address 172.16.3.1 255.255.255.0

mpls
mpls ldp
#
undo shutdown
ip address 172.16.8.1 255.255.255.0
mpls
mpls ldp
#
#
vlan-type dot1q 10
remote-ce ip 120.0.0.1 mpls l2vc 1.1.1.1 100 tunnel-policy policy1 ip-
interworking
mpls l2vc 3.3.3.3 300 ip-interworking bypass
mpls l2vc bypass track admin-vc interface LoopBack1
#
#
vlan-type dot1q 10
ip address 120.0.0.2 255.255.255.0
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.255
#
interface LoopBack1
mpls l2vc 3.3.3.3 400 control-word admin
#
destination 1.1.1.1
mpls te path explicit-path to_csg
mpls te commit
#
bgp 100
#
ipv4-family unicast
peer 3.3.3.3 enable
peer 4.4.4.4 enable
peer 5.5.5.5 enable
#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.3 enable
peer 4.4.4.4 enable
peer 5.5.5.5 enable
#


import-route direct
#
ospf 100
graceful-restart
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 172.16.1.0 0.0.0.255
network 172.16.3.0 0.0.0.255
network 172.16.2.0 0.0.0.255
network 172.16.8.0 0.0.0.255
mpls-te enable
#
#
#
bfd bypass bind pw interface LoopBack1
commit
#
return
l Configuration file of SR2

#
sysname SR2
#
ipv4-family
#
bfd
#
mpls lsr-id 3.3.3.3
mpls
mpls te
mpls rsvp-te
mpls te cspf
#
mpls l2vpn
#
explicit-path to_csg
next hop 172.16.4.1
next hop 1.1.1.1
#
mpls ldp
graceful-restart
#
#
remote-ip 1.1.1.1
#
undo shutdown
ip address 172.16.2.1 255.255.255.0
mpls
mpls ldp
#

undo shutdown
#
undo shutdown
ip address 172.16.4.2 255.255.255.0
mpls
mpls te
mpls rsvp-te
#
undo shutdown
ip address 172.16.6.1 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 172.16.7.1 255.255.255.0
mpls
mpls ldp
#
#
vlan-type dot1q 10
mpls l2vc 2.2.2.2 300 ip-interworking bypass
mpls l2vc bypass track admin-vc interface LoopBack1
#
#
vlan-type dot1q 10
ip address 120.0.0.4 255.255.255.0
#
interface LoopBack0
ip address 3.3.3.3 255.255.255.255
#
interface LoopBack1
mpls l2vc 2.2.2.2 400 control-word admin
#
destination 1.1.1.1
mpls te path explicit-path to_csg
mpls te commit
#
bgp 100

#
ipv4-family unicast
peer 2.2.2.2 enable
peer 4.4.4.4 enable
peer 5.5.5.5 enable
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.2 enable
peer 4.4.4.4 enable
peer 5.5.5.5 enable
#
import-route direct
#
ospf 100
graceful-restart
area 0.0.0.0
network 3.3.3.3 0.0.0.0
network 172.16.2.0 0.0.0.255
network 172.16.7.0 0.0.0.255
network 172.16.4.0 0.0.0.255
network 172.16.6.0 0.0.0.255
mpls-te enable
#
#
#
bfd bypass bind pw interface LoopBack1
commit
#
return
l Configuration file of RSG1

#
sysname RSG1
#
vlan batch 10
#
ipv4-family
#
mpls lsr-id 4.4.4.4
#
mpls l2vpn
#
mpls ldp
graceful-restart
#
interface Vlanif10
ip address 120.0.1.1 255.255.255.0
#

portswitch
undo shutdown
#
undo shutdown
ip address 172.16.3.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 172.16.7.2 255.255.255.0
mpls
mpls ldp
#
portswitch
undo shutdown
#
interface LoopBack0
ip address 4.4.4.4 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 2.2.2.2 enable
peer 3.3.3.3 enable
peer 5.5.5.5 enable
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.2 enable
peer 3.3.3.3 enable
peer 5.5.5.5 enable
#
import-route direct
#
ospf 100
graceful-restart
area 0.0.0.0
network 4.4.4.4 0.0.0.0
network 172.16.3.0 0.0.0.255
network 172.16.7.0 0.0.0.255
mpls-te enable
#
#
return
l Configuration file of RSG2

#
sysname RSG2
#

vlan batch 10
#
ipv4-family
route-distinguisher 11
vpn-target 11 export-extcommunity
vpn-target 11 import-extcommunity
#
bfd
#
mpls lsr-id 5.5.5.5
#
mpls l2vpn
#
mpls ldp
graceful-restart
#
interface Vlanif10
ip address 120.0.1.2 255.255.255.0
#
portswitch
undo shutdown
#
undo shutdown
ip address 172.16.6.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 172.16.8.2 255.255.255.0
mpls
mpls ldp
#
portswitch
undo shutdown
#
interface LoopBack0
ip address 5.5.5.5 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 2.2.2.2 enable
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.2 enable

peer 3.3.3.3 enable

peer 4.4.4.4 enable
#
import-route direct
#
ospf 100
graceful-restart
area 0.0.0.0
network 5.5.5.5 0.0.0.0
network 172.16.8.0 0.0.0.255
network 172.16.6.0 0.0.0.255
mpls-te enable
#
#
return

Configuration Guide - WAN Access 4 PPP and MP Configuration
4 PPP and MP Configuration
About This Chapter
Applied to the data link layer of the OSI model and the link layer of the TCP/IP protocol suite,
the Point-to-Point Protocol (PPP) is a link layer protocol that specifies how to transmit and
encapsulate network layer packets over P2P links. PPP is developed based on the Serial Line
Internet Protocol (SLIP). Multilink PPP (MP) is a technique that binds multiple PPP links to
increase bandwidth.
4.1 Introduction
This section describes PPP and MP features including the format, encapsulation, and
authentication modes of PPP packets.
4.2 Encapsulating an Interface with PPP and MRU Negotiation
This section describes how to configure PPP as the link layer protocol on an interface and how
to enable MRU negotiation.
4.3 Configuring Unidirectional PAP
This section describes how to configure unidirectional PAP authentication. Detailed operations
include configuring the local device to authenticate the peer device in PAP mode and configuring
the peer device to be authenticated by the local device in PAP mode.
4.4 Configuring Unidirectional CHAP
This section describes how to configure unidirectional CHAP authentication. Detailed
operations include configuring the authenticator with a user name to authenticate the peer device
in CHAP mode and configuring the authenticator without a user name to authenticate the peer
device in CHAP mode.
4.5 Configuring PPP Optional Parameters
This section describes how to configure optional PPP parameters. Detailed operations include
configuring the callback function, packet or packet header compression, negotiation timeout
period, polling interval,DNS server address negotiation, and PPP link quality detection, and also
include preventing the peer host route from being added to the local routing table of direct routes.
4.6 Configuring MP Binding Using an MP-Group
Multiple serial interfaces can be bundled into a logical interface. The NE80E/40E allows
interfaces to be bundled into an MP-group interface.
4.7 Configuring MP Limiting Parameters

This section describes how to configure MP limiting parameters.
4.8 Configuring MP Fragmentation

This section describes how to configure MP fragmentation. Detailed operations include setting
the minimum length of outgoing packets to be fragmented and disabling MP fragments from
being reassembled.
4.9 Configuring PPP Multiplexing

PPP multiplexing indicates that the transmitter multiplexes PPP encapsulated frames (sub-
frames) into a single PPP frame and then sends the multiplexed frame. As a result, the PPP
overhead per sub-frame is reduced.
4.10 Configuring Global-MP-Group Interfaces

Multiple Trunk-Serial interfaces can be bundled into a logical Global-MP-Group interface.

This section provides several examples for configuring PPP and MP. These configuration
examples explain networking requirements, configuration roadmap, data preparation,
configuration procedure, and configuration files.

4.1 Introduction
This section describes PPP and MP features including the format, encapsulation, and
authentication modes of PPP packets.
4.1.1 PPP Overview

The PPP protocol consists of the Link Control Protocol (LCP), Network Control Protocol (NCP),
and PPP extension protocols. PPP establishes links through a series of negotiations.
A point-to-point (P2P) connection is a simple WAN connection. Link layer protocols of a PPP
link 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 supports
synchronous or asynchronous full-duplex links to transmit data from point to point. PPP is widely
used 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-layer
protocols, and to 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), both of which are used for network security
authentication.
4.1.2 Features of PPP and MP on the NE80E/40E

On the NE80E/40E, PPP-enabled interfaces can be configured with MRU negotiation and PAP/
CHAP authentication. In addition, multiple serial interfaces can be bundled into an MP-group
interface.
The NE80E/40E supports the configuration of PPP on the serial or POS interface to implement
the following functions:
l Supporting the Maximum Receive Unit (MRU) negotiation
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.
l Synchronous serial interface formed by CE1 and CT1.

NOTE
The following are not supported on the X1 and X2 models of the NE80E/40E: synchronous serial interface
formed by T1 channelized by the STM-1 CPOS, synchronous serial interface formed by T1 channelized
by the T3, and synchronous serial interface formed by CT1.
The NE80E/40E does not support trans-board or trans-card MP binding.
When you configure MP in the MP-group mode, you can directly add the serial interface to the
MP-group.
4.2 Encapsulating an Interface with PPP and MRU

Negotiation
This section describes how to configure PPP as the link layer protocol on an interface and how
to enable MRU negotiation.

Before configuring PPP and enabling MRU negotiation, familiarize yourself with the usage
scenario, complete the pre-configuration tasks, and obtain the required data.
Usage Scenario
As a link layer protocol that bears network-layer packets over P2P links, PPP supports MRU
negotiation. If a link is configured with MTU values, apply MRU negotiation to make the values
on both ends consistent so that data can be transmitted.
Before configuring PPP, connect the interface and configure physical parameters for the
interface to ensure that the physical 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

This section describes how to configure PPP as the link layer protocol on an interface.
Context

Procedure
Step 1 Run:
system-view
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 both serial and POS interfaces is PPP.
NOTE
POS interfaces are not supported on the X1 and X2 models of the NE80E/40E.
----End
4.2.3 Enabling PPP MRU Negotiation

If MRU negotiation is enabled at the link control layer, both interfaces of a PPP link must be
configured with the same MRU negotiation mode.
Context
If an interface is configured with the IPv6 MTU, enable the PPP IPv6 MRU negotiation so that
the link control layer can perform the IPv6 MRU negotiation.
MRU refers to the capability of an interface to receive packets.
The initial MRU negotiation value is the MTU value set by users or the default MTU value on
an interface.
After the negotiation, the MTU on an interface is the smaller value of the MTUs on both ends,
whereas the MRUs on both ends remain unchanged. Therefore, the MTU on an interface is not
greater than the MRU on the interface. This ensures that communicating devices can receive
packets from each other.
Procedure
Step 1 Run:
system-view
Step 2 Run:

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
4.2.4 Enabling Magic Number Check for the PPP Protocol

After the magic number check function for the PPP protocol is enabled on a device, the device
compares the magic number of the LCP Echo Request and Reply packets it receives with the
remote device's magic number used for LCP negotiation. If the two magic numbers are different,
an LCP Down event is triggered, and the device re-initiates LCP negotiation.
Context
If a PPP link flaps or cross-connection occurs, enable the magic number check function for the
PPP protocol. After this function is enabled on the router, the router compares the magic number
of the LCP Echo Request and Reply packets it receives with the remote device's magic number
used for LCP negotiation. If the two magic numbers differ from each other for more than 5 times,
an LCP Down event is triggered, and the device re-initiates LCP negotiation. If the two magic
numbers are the same, the number of times the two magic numbers differ from each other is
reset.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
link-protocol ppp
PPP is configured as the link layer protocol of the interface.
Step 4 Run:
ppp magic-number check
The magic word check function is enabled for the PPP protocol.
----End

After PPP encapsulation and PPP MRU negotiation are configured on an interface, you can view
the PPP configuration and the negotiated MRU value.

Prerequisites
The configurations for the encapsulating an interface with PPP and MRU negotiation are
complete.
Procedure
l Run the display interface [ interface-type [ interface-number ] ] command to check the
PPP configuration and the negotiated MTU value of the interface.
----End
Example
Run the display interface command. If the PPP configuration is displayed, it means that the
configuration is successful. For example:
Description:Pos1/0/0 Interface
The Vendor PN is FTLF1321P1BTL-HW
Rx Power: -6.38dBm, normal range: [-18.01, -3.00]dBm
Tx Power: -5.72dBm, normal range: [-13.00, 1.00]dBm
Flag C2 22(0x16)
SDH alarm:
section layer: none
line layer: none
path layer: none
SDH error:
section layer: B1 0
4.3 Configuring Unidirectional PAP

This section describes how to configure unidirectional PAP authentication. Detailed operations
include configuring the local device to authenticate the peer device in PAP mode and configuring
the peer device to be authenticated by the local device in PAP mode.
NOTE
Unidirectional PAP Authentication is not supported on the X1 and X2 models of the NE80E/40E.


Before configuring unidirectional PAP authentication, familiarize yourself with the usage
Usage Scenario
In PAP authentication, simple passwords are sent over the link. The username and password of
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 User
Service (RADIUS) server.
PAP authentication is classified into the following types:
l Unidirectional authentication: One of the two communication parties functions as the

authenticator, while the other is the authenticated.
l Bidirectional authentication: The two communication parties function as both the
authenticator and the authenticated.
This section describes how to configure unidirectional PAP authentication.
Before configuring PAP authentication, complete the following tasks:
l Connect interfaces and configure physical attributes for these interfaces to ensure that the
physical layer of the interfaces is Up.
l Configure PPP as the link layer protocol of interfaces
.
Data Preparation
To configure PAP authentication, you need the following data.
No. Data
2 Username and password of the authenticated user
4.3.2 Configuring a Local Device to Authenticate Its Peer in PAP

Mode
This section describes how to configure PAP-related parameters for the authenticator. PAP
authentication is a two-way authentication mode and is implemented only at the beginning of
link establishment.
Context

Procedure
Step 1 Run:
system-view

Step 2 Run:
aaa
The AAA view is displayed.

Step 3 Run:
local-user user-name password { cipher cipher-password | irreversible-cipher
irreversible--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 5 Run:

Step 6 Run:
ppp authentication-mode pap
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 undo
shutdown commands in the interface view to validate the configuration.
----End
4.3.3 Configuring the Peer to Be Authenticated by the Local Device

in PAP Mode
This section describes how to configure PAP-related attributes for the authenticated user.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
Step 3 Run:
ppp pap local-user user-name password { cipher | simple } password
The username and password of the local end are configured when the local end is configured to
be authenticated using PAP.
Step 4 Run:
restart
NOTE
After changing the username and password, run the restart command, or the shutdown and undo
shutdown commands in the interface view to validate the configuration.
----End

After unidirectional PAP authentication is configured, you can view the link status and LCP
running status on the interface.
Prerequisites
Unidirectional PAP has been configured.
Procedure
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 PAP
authentication is successful. For example:


Flag C2 22(0x16)
SDH alarm:
section layer: none
line layer: none
path layer: none
SDH error:
section layer: B1 0
4.4 Configuring Unidirectional CHAP

This section describes how to configure unidirectional CHAP authentication. Detailed
operations include configuring the authenticator with a user name to authenticate the peer device
in CHAP mode and configuring the authenticator without a user name to authenticate the peer
device in CHAP mode.
NOTE
Unidirectional CHAP is not supported on the X1 and X2 models of the NE80E/40E.

Before configuring unidirectional CHAP authentication, familiarize yourself with the usage
Usage Scenario
In CHAP authentication, passwords are sent over the link in encrypted text. The authenticated
username and password can be authenticated in AAA mode or through the RADIUS server and
then added to 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 the
other is the authenticated.
l Bidirectional: Two communication parties function as both the authenticator and the
authenticated.
This section describes how to configure unidirectional CHAP authentication.
Before configuring CHAP authentication, complete the following tasks:

.
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.4.2 Configuring a Local Device with a User Name to Authenticate

Its Peer in CHAP Mode
This section describes how to configure the authenticator with a user name to authenticate the
peer in CHAP mode.
Context
NOTE
In CHAP authentication, when configuring the username for the authenticator, ensure that the same
password is configured for the authenticator and the authenticated.
Procedure
l Configuring the authenticator
1. Run:
system-view

2. Run:
aaa

3. Run:
local-user user-name password { cipher cipher-password | irreversible-
cipher irreversible--password }
4. Run:
quit


5. Run:

6. Run:
ppp authentication-mode chap
The local end authenticates the peer end using CHAP.

You can run the ppp authentication-mode command to perform CHAP negotiation
preferentially in LCP negotiation. If the peer end does not support CHAP
authentication, PAP negotiation is performed. If the peer end does not support CHAP
or PAP, the LCP negotiation fails. Either CHAP or PAP is involved in a PPP
negotiation.
7. Run:
ppp chap user user-name
The local username is configured.

8. Run:
restart
NOTE
After changing the username and password, run the restart command, or the shutdown and
undo shutdown commands in the interface view to validate the configuration.
l Configuring the authenticated
1. Run:
system-view

2. Run:
aaa

3. Run:
4. Run:
quit

5. Run:

6. Run:


7. Run:
restart
NOTE
----End
4.4.3 Configuring a Local Device Without a User Name to

Authenticate Its Peer in CHAP Mode
This section describes how to configure the authenticator without a user name to authenticate
the peer in CHAP mode.
Procedure
l Configuring the authenticator
1. Run:
system-view

2. Run:
aaa

3. Run:
4. Run:
quit

5. Run:

6. Run:
ppp authentication-mode { { chap | pap | mschapv1 | mschapv2 } * | auto }
The local end authenticates the peer end using CHAP.
You can run the ppp authentication-mode command to perform CHAP negotiation
preferentially in LCP negotiation. If the peer end does not support CHAP
authentication, PAP negotiation is performed. If the peer end does not support CHAP

or PAP, the LCP negotiation fails. Either CHAP or PAP is involved in a PPP
negotiation.
7. Run:
restart
In authentication, if the username and password of the interface on the peer end are
consistent with the username and password in the local AAA user list, the
authentication is successful.
l Configuring the authenticated
1. Run:
system-view

2. Run:

3. Run:

4. Run:
ppp chap password { cipher | simple } password
The password of the local end is configured, which is used when the local end is
authenticated by the peer end using CHAP.
5. Run:
restart
NOTE
----End

After unidirectional CHAP authentication is configured, you can view the PPP configuration
and PPP status on the interface.
Prerequisites
Unidirectional CHAP has been configured.

Procedure
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 the
status of LCP and IPCP is opened, it means that CHAP authentication is successful. For example:
Flag C2 22(0x16)
SDH alarm:
section layer: none
line layer: none
path layer: none
SDH error:
section layer: B1 0
4.5 Configuring PPP Optional Parameters

This section describes how to configure optional PPP parameters. Detailed operations include
configuring the callback function, packet or packet header compression, negotiation timeout
period, polling interval,DNS server address negotiation, and PPP link quality detection, and also
include preventing the peer host route from being added to the local routing table of direct routes.

Before configuring PPP optional parameters, familiarize yourself with the usage scenario,

Usage Scenario
l Callback
When a router works as the callback client and the server allows calling back the number
specified by the user, you can configure the dial string required to call back the router. In
this manner, reverse charging is realized.
l Header compression
IP Header Compression (IPHC) is a host-to-host protocol. IPHC is used on the IP network
to compress real-time multimedia services such as voice and video. To improve bandwidth
utilization, you can apply IPHC to the link to compress the IP, UDP, and RTP headers.
l Interval for the negotiation timeout
In PPP negotiation, if no response is received from the peer end within the interval, PPP
resends a negotiation request.
l Polling interval
Link layer protocols such as PPP, FR, and HDLC use a polling timer to check whether a
link is working normally.
In the case of a long network delay or severe congestion, you can prolong the polling interval
to reduce network flapping.
When configuring the polling interval, ensure that both ends are configured with the same
interval.
l DNS server address negotiation
When other devices are connected to a router through PPP, for example, a PC is connected
to a router through dialup, the peer device directly accesses the network through the domain
name. In this case, the router needs to assign DNS server addresses for the peer device.
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 by
the router.
The NE80E/40E can provide the peer device with two server addresses, a primary DNS
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 the
PPP link bound in MP.
When the quality of a link is lower than the quality percentage of the forbidden link, the
link is disabled. When the link quality is restored to the quality percentage of the recovered
link, the link is enabled automatically.
When the quality of a link is lower than the quality percentage of the forbidden link, the
link is disabled. When the link quality is restored to the quality percentage of the recovered
link, the link is enabled automatically.
To avoid a link from frequently switching between prohibition and restoration, the delay
for restarting a link is required.
Before configuring optional parameters of PPP, complete the following tasks:

.
l Configure interfaces to adopt PAP or CHAP authentication, which is required only during
the 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 connections

in the IPHC function
3 Timeout interval of the 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

You can set the callback function as required and specify the dial string used to call back a
router.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Choose one of the following commands to configure the interface as the callback server or the
callback 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

This section describes how PPP compresses packets or packet headers.
Procedure
l Enabling IPHC on the interface
1. Run:
system-view

2. Run:
In NE80E/40E, only synchronous serial interfaces and MP-Group interfaces support

IPHC.
3. Run:
ppp compression iphc
IPHC is enabled on the interface.
For the details about IPHC, refer to theHUAWEI NetEngine80E/40E Router

ConfigurationGuide-QoS.
----End
4.5.4 Configuring the Timeout Period of Negotiation

During PPP negotiation, if the peer does not reply with a response packet before the negotiation
times out, PPP resends the negotiation request packet.
Procedure
Step 1 Run:
system-view

Step 2 Run:

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

This section describes how to configure the interval for sending Keepalive packets to a peer.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
timer hold hold-time
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 the PPP LCP Link Dead Duration

Procedure
Step 1 On the router, run:
system-view

Step 2 Run:

Step 3 Run:
ppp timer link-dead timer

The PPP LCP link dead duration is configured.
The default PPP LCP link dead duration is 30s.
----End
4.5.7 Configuring DNS Server Address Negotiation

This section describes how to configure the local router to accept any DNS server address and
the locally negotiated DNS server address.
Procedure
l Admit any DNS server address proposed by the peer.
1. Run:
system-view

2. Run:

3. Run:
ppp ipcp dns admit-any
Any DNS server address proposed by the peer is admitted.

l Configure the DNS server address from the local negotiation.
1. Run:
system-view

2. Run:

3. Run:
ppp ipcp dns primary-dns-address [ secondary-dns-address ]
The DNS server address from the local negotiation is configured.
By default, a router does not provide a DNS server address for its peer.
----End
4.5.8 Configuring the PPP Link Quality Detection

This section describes how to configure quality detection for low-speed links. When the detected
link quality is lower than the close percentage, the link is disabled; when the detected link quality
once again becomes higher than the resume percentage, the link is automatically enabled.

Procedure
Step 1 Run:
system-view

Step 2 Run:

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 lqc
command 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.
l Run the restart command.
After enabling or disabling the PPP link quality detection, restart the interface to validate the
configuration.
----End
4.5.9 Preventing the Peer Host Route from Being Added to the Local
Routing Table of Direct Routes
This section describes how to prevent the peer host route from being added to the local routing
table of direct routes. This prevents the situation where one end is configured with an incorrect
IP address, and the other end automatically adds the incorrect peer host route to the local routing
table, which results in the discrimination of incorrect routing information on the network.
Context
The PPP link does not strictly require that the peer route and local route exist on the same network
segment. Two ends of the PPP link at different network segments can communicate. In addition,
the peer host route at a different network segment can also be automatically added to local routing
table of direct routes.
However, when one end is configured with an incorrect IP address, the other end automatically
adds the incorrect peer host route to the local routing table of direct routes. As a result, the
incorrect routing information is advertised across the network.
With the following command, you can decide whether the peer host route is added to the local
routing table of direct routes.
Procedure
Step 1 Run:
system-view

Step 2 Run:
Step 3 Run:
ppp peer hostroute-suppress
The peer host route is prevented from being added to the local routing table.
NOTE
After enabling or disabling this function, restart the interface to validate the configuration.

----End
4.5.10 Configuring PPP Timeslot Detection

Procedure
Step 1 Perform the following steps on the router:
system-view
Step 2 Run:
NOTE
PPP timeslot detection can be configured on serial interfaces formed by CE1 interfaces, CT1 interfaces,
E1 and T1 channels of CPOS interfaces, and T1 channels of CT3 interfaces as well as Trunk-Serial
interfaces formed by CPOS-Trunk interfaces.
Step 3 Run:
ppp time-slot detect enable
PPP timeslot detection is enabled.
----End
4.5.11 Enabling OSICP and MPLSCP to Go Up Without Device

Negotiation
Context
The interconnected interfaces of the NE80E/40E and a PTN3900 need to perform a PPP
negotiation. OSICP and MPLSCP are Up by default on PTN3900 interfaces, whereas the two

protocols are not Up by default on NE80E/40E interfaces. Perform the following steps to enable
OSICP and MPLSCP to go Up without negotiation on the NE80E/40E interface:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
ppp { osicp | mplscp } disable
OSICP and MPLSCP are enabled to go Up without device negotiation.
NOTE
This command can be used on an MP-group interface, Global-MP-group interface view, trunk-serial
interface view, POS interface view, POS-Trunk interface view, and an FR-capable serial interface.
Step 4 Run:
shutdown and undo shutdown
The interface is restarted to make the configuration take effect.
----End

After PPP optional parameters are configured, you can view the PPP configuration and running
status on the interface.
Prerequisites
PPP optional parameters have been configured.
Procedure
PPP configuration and the status of the interface.
----End
Example
Run the display interface command to check the PPP configuration and the status of the
interface. For example:
Description:HUAWEI, Pos1/0/0 Interface


LCP opened, IPCP opened, OSICP opened, MPLSCP opened
Flag C2 22(0x16)
SDH alarm:
section layer: none
line layer: none
path layer: none
SDH error:
section layer: B1 0
4.6 Configuring MP Binding Using an MP-Group

Multiple serial interfaces can be bundled into a logical interface. The NE80E/40E allows
interfaces to be bundled into an MP-group interface.

Before configuring MP binding through the MP-Group, familiarize yourself with the usage
Usage Scenario
When configuring MP binding using MP-Group, the slot number and the card number of MP-
Group interface must be consistent with the slot number and card number of the interface added
to the MP-Group.
Only channelized synchronous serial interfaces can be added to the MP-Group.
In MP negotiation, different carriers complements differently.
By default, the endpoint discriminator needs to be negotiated in NE80E/40E MP negotiation. If

no endpoint discriminator is sent, MP negotiation fails. As a result, the endpoint discriminator
negotiation cannot be configured on the local side.
NOTE
Configure the local and the peer ends separately. However, the configuration methods are the same.

Before configuring MP binding using MP-Group, complete the following tasks:
l Configure physical attributes for the router interface.

l Configure 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.6.2 Adding an Interface to an MP-Group

Bundling multiple interfaces into an MP-group interface increases bandwidth.
Context
When 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 on the same interface card because the
router does not support trans-board and trans-card MP binding.
l The number of physical interfaces bound in one MP-group used to interwork at two ends
must be the same.
l When multiple physical interfaces are bound in one local MP-group, the peer interfaces
directly connected to those physical interfaces must be bound into one MP-group.
Procedure
Step 1 Run:
system-view
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:
quit
Step 5 Run:
Step 6 Run:
ppp mp mp-group number
The interface is added to the MP-group.
Step 7 Run:
quit
Step 8 Run:
The MP-group interface view is displayed.
----End
4.6.3 Adding an Interface to an Global-MP-Group

Bundling multiple interfaces into an Global-MP-group interface increases bandwidth.
Context
When using an Global-MP-group to bind an interface, consider the following items:
l Physical interfaces must be bound into one Global-MP-group in the same mode.
l All physical interfaces in one Global-MP-group must be on the same interface card because
the router does not support trans-board and trans-card MP binding.
l The number of physical interfaces bound in one Global-MP-group used to interwork at two
ends must be the same.
l When multiple physical interfaces are bound in one local Global-MP-group, the peer
interfaces directly connected to those physical interfaces must be bound into one Global-
MP-group.
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface global-mp-group number
The Global-MP-group interface is created.

Step 3 Run:
The IP address is assigned for the Global-MP-group interface.

Step 4 Run:
quit

Step 5 Run:

Step 6 Run:
ppp mp-global global-mp-group number
The interface is added to the Global-MP-group.

Step 7 Run:
quit

Step 8 Run:
interface global-mp-group number
The Global-MP-group interface view is displayed.
----End
4.6.4 Disabling the Endpoint Discriminator Negotiation

The LCP status can be Up only when the terminal discriminators of the MP-Groups on both ends
are the same. If the terminal discriminators are different, disable the terminal discriminator
negotiation.
Procedure
Step 1 Run:
system-view

Step 2 Run:
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 when
the endpoint discriminators of the MP-Group ports are the same.
If one end is configured with the undo discriminator command and the other end is configured
with the discriminator command, the parameters sent by the former end do not contain the
endpoint discriminator. This end then accepts 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 use
the shutdown and undo shutdown commands on the MP-Group interface to enable the
configuration.
Step 4 Run:
quit
Step 5 Run:

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 that
PPP 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 can
automatically perform negotiation.
NOTE
To ensure the success of MP binding after PPP is renegotiated, it is recommended to restart all the bound
interfaces after the configuration.
----End

After an MP-group interface is configured, you can check information about the MP-group
interface and the status of member interfaces.
Procedure
l 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.
command to check brief information about the MP-Group interface and its member
interfaces.
----End

Example
After running the display ppp mp command, you can check MP binding information, including
the status and number of the bound member interfaces.
<HUAWEI> display ppp mp
Mp-group is Mp-group1/0/1
===========Sublinks status begin======
Serial1/0/1:1 physical UP,protocol UP
Serial1/0/1:3 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
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-group
Description:Mp-group1/0/1 Interface
LCP opened, MP opened, IPCP reqsent
Traffic statistics:
0 errors, 0 drops
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 its
member interfaces. The following is the display of the command:
<HUAWEI> display interface brief | include 1/0/
PHY: Physical
^down: standby
(l): loopback
(s): spoofing
(b): BFD down
(e): EFM down
outErrors
Mp-group1/0/1 up up 0% 0% 0
0
Serial1/0/0:0 up up 1% 1% 5
0
Serial1/0/1:0 up up 1% 1% 2
0
Serial1/0/2:0 *down down 0% 0% 0
0

Serial1/0/5:0 up down 0% 0.01% 21

0
4.7 Configuring MP Limiting Parameters

This section describes how to configure MP limiting parameters.

Before configuring MP limiting parameters, familiarize yourself with the usage scenario,
Usage Scenario
After configuring MP binding, you can configure MP limiting parameters to optimize the link
channels.
The limiting parameters include:
l Maximum receiving re-group unit
Before configuring MP limiting parameters, complete the following tasks:
l Connect the interface and configure its physical parameters to change the physical layer
status Up
.
l Configure 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 flappings occur on the MP subchannel within the

detection time
4 Minimum time during which the MP subchannel keeps Up to be released from

damping
5 Minimum number of subchannels in the Up state in an MP

NOTE
l After changing the parameters configured in the MP-group view, use the shutdown command in all
the bound sub-channels to disable 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

The Max-Receive-Reconstructed Unit (MRRU) is a mandatory parameter of MP negotiation.
By negotiating the MRRU with the peer, the local end confirms the maximum length of a packet
that the peer can reassemble from fragments and determines how to fragment IP packets.
Context
Max-Receive-Reconstructed Unit (MRRU) refers to the maximum size of the packet that can
be re-assembled with the received fragment packets. MP must negotiate MRRU with the remote
before performing IP packet fragmentation.
Procedure
Step 1 Run:
system-view
Step 2 Run:
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 Subchannels

The damping function can suppress the frequent flappings of an MP subchannel, and the
subchannel can be released from the damping state only after it keeps Up for a specified time
of period.
Context
Perform the following steps on the routers configured with MP-Group interfaces:
Procedure
Step 1 Run:

system-view
Step 2 Run:
The MP-Group interface view is displayed.
Step 3 Run:
ppp mp damping detect-time detect-time flapping-count flapping-count damping-time
damping-time
The damping function is configured for the MP subchannels.
----End
4.7.4 Configuring the Minimum Number of Subchannels in the Up

State in an MP Link
After the LCP negotiation is successful, a PPP link can be added to an MP link only when the
number of subchannels in the Up state in the MP link reaches the configured minimum value,
and then the MP can perform the NCP negotiation. That is, you can set the minimum bandwidth
for an MP link as required.
Context
Perform the following steps on the routers configured with MP-Group interfaces:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
ppp mp threshold-least number
The minimum number of subchannels in the Up state in the MP link is set.
NOTE
It is recommended that the lower thresholds of the MP groups at both ends of the link be set to the same value.
Step 4 Run:
shutdown
The MP-group interface is shut down.
Step 5 Run:
undo shutdown

The MP-Group interface is restarted.
----End
4.7.5 Enabling Delay Detection for MP-Group Member Links

Enabling delay detection for MP-group member links can reduce the impact of long link delay
on the service transmission quality.
Context
If devices are connected using low-speed links, these low-speed links can be bundled as an MP-
group to extend the link bandwidth and implement link protection and load balancing. The
transmission delay on each MP-group member link, however, is different. When the delay of
different MP-group member links is large, service transmission quality will be greatly affected.
The router can be enabled with delay detection for MP-group member links, allowing the system
to send a detection packet every second to detect the transmission delay on each MP-group
member link. If the transmission delay on a member link reaches the threshold, services to be
transmitted on the member link are switched to another. You can set the delay difference
threshold according to the requirements of each service.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface mp-group mp-group-number
The MP-group interface view is displayed.
Step 3 Run:
time-delay-detect enable
Delay detection for MP-group member links is enabled.
Step 4 Run:
time-delay-detect threshold time-delay-threshold
The delay difference threshold for MP-group member links is set.
NOTE
The value supported by the command ranges from 25 to 500, in 100 μs, which means the actual delay
difference threshold is time-delay-threshold*100 μs.
----End

After MP limiting parameters are configured, you can check the configurations of the parameters.

Procedure
Step 1 Run the display current-configuration interface [ interface-type [ interface-number ] ]
command to check the configuration of MP-Group interface.
----End
Example
After running the display current-configuration interface command, you can check
configurations on the MP-Group interface.
<HUAWEI> display current-configuration interface mp-group 1/0/1
#
mrru 1200
ppp mp threshold 2
ppp mp damping detect-time 32 flapping-count 32 damping-time 62
#
return
4.8 Configuring MP Fragmentation

This section describes how to configure MP fragmentation. Detailed operations include setting
the minimum length of outgoing packets to be fragmented and disabling MP fragments from
being reassembled.

Before configuring MP fragmentation, familiarize yourself with the usage scenario, complete
the pre-configuration tasks, and obtain the required data.
Usage Scenario
After binding the interface to the MP, configure MP fragmentation as required to optimize the
link channel.
Before configuring MP fragmentation, complete the following tasks:
l Connect the interface and configure its physical parameters to change the physical layer
status Up.
l Configure 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

Setting the proper size for an MP fragment improves bandwidth usage.
Context
Using the MP fragment function, you can adjust the value of the MP fragment packets.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The MP group interface is displayed.

Step 3 Run:
fragment-threshold threshold
The fragment value of MP data packet is configured.
NOTE
On an MP link, configuring MP fragmentation to improve link efficiency and setting the size of each
fragment to 256 bytes are recommended.
----End

After MP fragmentation is configured, you can check its configuration.
Procedure
Step 1 Run the display ppp mp [ interface interface-type interface-number ] command to check the
MP binding information.
----End
Example
Run the display ppp mp command to view the binding information about the MP-Group. For
example:
<HUAWEI> display ppp mp interface mp-group 1/0/1

Serial1/0/1:3 physical UP,protocol DOWN(damping)

Serial1/0/1:1
Serial1/0/1:2
4.9 Configuring PPP Multiplexing

PPP multiplexing indicates that the transmitter multiplexes PPP encapsulated frames (sub-
frames) into a single PPP frame and then sends the multiplexed frame. As a result, the PPP
overhead per sub-frame is reduced.
Prerequisites
NOTE
PPP Multiplexing cannot be configured on the X1 and X2 models of the NE80E/40E.

You can control the time spent on PPP multiplexing by configuring the delay, the maximum
length of a PPP multiplexed frame, the maximum number of sub-frames that can be concatenated
into a PPP multiplexed frame, and the maximum length of a sub-frame.
Usage Scenario
For links that forward a large number of voice packets, PPP multiplexing can greatly improve
bandwidth usage. The transmitter encapsulates a PPP multiplexing header and adds sub-frames.
The number of sub-frames to be added is configurable or controlled by timers. In this manner,
multiple PPP sub-frames are concatenated into one PPP multiplexed frame and then sent out.
Multiple sub-frames can share one protocol field. That is, if a sub-frame complies with the same
protocol as the previous sub-frame, the protocol field in the sub-frame is deleted. In this manner,
the PPP overhead per sub-frame is reduced. Then, the receiver demultiplexes the PPP
multiplexed frame to recreate the original PPP frames.
The compression function provided by the Real-Time Transport Protocol (CRTP) is applicable
to PPP multiplexing to improve bandwidth usage.
Before configuring PPP multiplexing, add an Interface to an MP-Group.
Data Preparation
To configure PPP multiplexing, you need the following data.
No. Data
1 (Optional) Default protocol ID (PID) of PPP multiplexed frames

No. Data
2 (Optional) Delay for PPP multiplexing
3 (Optional) Maximum length of a PPP multiplexed frame
4 (Optional) Maximum number of sub-frames that can be concatenated into a PPP

multiplexed frame
5 (Optional) Maximum length of a PPP sub-frame
4.9.2 Enabling PPP Multiplexing

After the relevant command is used, PPP multiplexing or demultiplexing takes effect.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
ppp multiplexed
PPP multiplexing is enabled.
NOTE
Both the transmitter and receiver need to be configured with the ppp multiplexed command for PPP Mux
Control Protocol (PPPMuxCP) negotiation. PPP frames can be multiplexed or demultiplexed only after
the negotiation is successful.
----End
4.9.3 (Optional) Configuring the Default PID for PPP Multiplexing

You need to configure the default PID for PPPMuxCP negotiation.
Procedure
Step 1 Run the following command on the router:
system-view

Step 2 Run:
Step 3 Run:
ppp multiplexed pid pid
The default PID is configured for PPP multiplexing.
By default, the PID for PPP multiplexed frames is 33 (0x21), indicating the IP protocol.
NOTE
You must enable PPP multiplexing before configuring the default PID.
----End
4.9.4 (Optional) Configuring the Delay for PPP Multiplexing

You can control the time spent on multiplexing PPP frames by configuring the delay.
Procedure
system-view
Step 2 Run:
Step 3 Run:
ppp multiplexed delay delay-time
The delay for PPP multiplexing is configured.
By default, the delay for PPP multiplexing is 0, indicating that multiplexed frames are sent when
the buffer is full.
To ensure normal running of the protocol, do not use the default value, but set the delay-time to
1 ms.
NOTE
You must enable PPP multiplexing before configuring the delay.
----End
4.9.5 (Optional) Configuring the Maximum Length of a PPP

Multiplexed Frame
You can control the time spent on multiplexing PPP frames by configuring the maximum length.

Procedure
system-view

Step 2 Run:

Step 3 Run:
ppp multiplexed frame length length
The maximum length of a PPP multiplexed frame is configured.

By default, the maximum length is 190 bytes.
NOTE
l You must enable PPP multiplexing before configuring its maximum length.
l The configured maximum length of a PPP multiplexed frame must be greater than the configured
maximum length of a PPP sub-frame by the length of a Layer 2 packet header.
----End
4.9.6 (Optional) Configuring the Maximum Number of Sub-frames

That Can Be Concatenated into a PPP Multiplexed Frame
You can control the time spent on multiplexing PPP frames by configuring the maximum number
of sub-frames that can be concatenated into a PPP multiplexed frame.
Procedure
system-view

Step 2 Run:

Step 3 Run:
ppp multiplexed subframe count count
The maximum number of sub-frames that can be concatenated into a PPP multiplexed frame is
configured.
By default, a maximum of 15 sub-frames can be concatenated into a PPP multiplexed frame.
NOTE
You must enable PPP multiplexing before configuring the maximum number of sub-frames that can be
concatenated into a PPP multiplexed frame.
----End

4.9.7 (Optional) Configuring the Maximum Length of a PPP Sub-

frame
You can control the time spent on multiplexing PPP frames by configuring the maximum length
of a PPP sub-frame.
Procedure
system-view
Step 2 Run:
Step 3 Run:
ppp multiplexed subframe length length
The maximum length of a PPP sub-frame is configured.
By default, the maximum length of a PPP sub-frame is 189 bytes.
NOTE
l You must enable PPP multiplexing before configuring the maximum length of a PPP sub-frame.
l The configured maximum length of a PPP sub-frame must be smaller than the configured maximum
length of a PPP multiplexed frame by the length of a Layer 2 packet header.
----End

Prerequisites
PPP multiplexing has been configured.
Procedure
l Run the display interface mp-group [ number ] [ | { begin | exclude | include } regular-
expression ] command to view the status of the MP-Group interface.
----End
Example
Run the display interface mp-group command to view that PPPMuxCP negotiation is
successful.
<HUAWEI> display interface mp-group1/0/0


LCP opened, MP opened, IPCP opened, PPPMuxCP opened
Traffic statistics:
Last 300 seconds input rate 0 bytes/sec, 0 packets/sec
Last 300 seconds output rate 0 bytes/sec, 0 packets/sec
0 errors, 0 drops
0 errors, 0 drops
<HUAWEI> display interface mp-group1/0/0
Interface: Mp-group1/0/0
Multiplex:
Total input packets: 2
Error input packets: 0
Valid input bytes: 290
Total output packets: 4
Multiplexed output packets: 4
Output bytes: 288
Efficiency improvement factor: 0%
Demultiplex:
Multiplexed input packets: 382
Output bytes: 67232
Interface: Mp-group2/2/5
Multiplex:
Multiplexed output packets: 764
Output bytes: 65704
Demultiplex:
Multiplexed input packets: 2
Output bytes: 296
4.10 Configuring Global-MP-Group Interfaces

Multiple Trunk-Serial interfaces can be bundled into a logical Global-MP-Group interface.

Before configuring a Global-MP-Group interface, familiarize yourself with the usage scenario,
Usage Scenario
To increase service bandwidth, you can bundle multiple Trunk-Serial interfaces of the E1
channel in a CPOS-Trunk into a Global-MP-Group interface.
After these Trunk-Serial interfaces are added to the Global-MP-Group interface, services can
be configured directly on the Global-MP-Group interface.

Before configuring the Global-MP-Group interface, configure PPP as the link layer protocol for
these Trunk-Serial interfaces.
Data Preparation
To configure the Global-MP-Group interface, you need the following data.
No. Data
1 Numbers of Trunk-Serial interfaces
2 Number of the Global-MP-Group interface
4.10.2 Establishing a Global-MP-Group Interface and Adding

Member Interfaces to It
This section describes how to bundle multiple Trunk-Serial interfaces into a Global-MP-Group
interface to increase the service bandwidth.
Context
When bundling multiple Trunk-Serial interfaces into a Global-MP-Group interface, note the
following points:
l The number of Trunk-Serial interfaces that are bundled into a Global-MP-Group interface
must be the same on each end.
l The Trunk-Serial interfaces that are directly connected to Trunk-Serial interfaces bundled
into the local Global-MP-Group interface on the peer end must be bundled into the same
Global-MP-Group interface.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface global-mp-group global-mp-group-number
A Global-MP-Group interface is created.
Step 3 Run:
quit
Step 4 Run:

interface trunk-serial interface-number
The Trunk-Serial interface view is displayed.
Step 5 Run:
shutdown
A Trunk-Serial interface is shut down.
Step 6 Run:
ppp mp-global global-mp-group global-mp-group-number
A member interface is added to the Global-MP-Group interface.
Step 7 Run:
undo shutdown
The Trunk-Serial interface is restarted.
Step 8 Run:
quit
Step 9 Run:
interface global-mp-group global-mp-group-number
The Global-MP-Group interface view is displayed.

mtu
An MTU is configured for the Global-MP-Group interface.
NOTE
After a new MTU is configured by using the mtu command on the Global-MP-Group interface, restart the
interface to validate the MTU value.

discriminator
Terminal discriminator negotiation is enabled on the Global-MP-Group interface.

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 this function, restart the interface to validate the configuration.
----End

This section describes how to check Global-Mp-Group interface configurations.

Procedure
Step 1 Run the display ppp mp-global [ interface global-mp-group interface-number ] command to
check information about the member interfaces of the Global-Mp-Group interface.
----End
Example
Run the display ppp mp-global command to view information about the member interfaces of
the Global-Mp-Group interface.
<HUAWEI> display ppp mp-global interface global-mp-group 1
Global-Mp-Group is Global-Mp-Group1
Trunk-Serial1/2:0 physical UP,protocol UP
Trunk-Serial1/3:0 physical UP,protocol UP

This section provides several examples for configuring PPP and MP. These configuration
examples explain networking requirements, configuration roadmap, data preparation,
configuration procedure, and configuration files.
4.11.1 Example for Configuring PAP Authentication

This example shows how to configure two devices so that one end (the authenticator) can
authenticate the other end (the authenticated) in PAP mode on a typical network.
NOTE
PAP Authentication is not supported on the X1 and X2 models of the NE80E/40E.
As shown in Figure 4-1, Router A and Router B are connected through the POS interface. Router
A (the authenticator) is required to authenticate Router B (the authenticated) in PAP mode.
Figure 4-1 Networking for PAP authentication
POS1/0/0
RouterA 10.110.0.2/24 RouterB
POS1/0/0
10.110.0.1/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.
Data Preparation
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
# Add the username and password of Router B to the local user list of Router A.
[RouterA] aaa
[RouterA-aaa] local-user hello@163.net password cipher !QAZ@WSX3edc
[RouterA-aaa] quit
# Configure an IP address for POS 1/0/0 and configure the link-layer encapsulation protocol as
PPP.
[RouterA-Pos1/0/0] ip address 10.110.0.1 255.255.255.0
NOTE
l When you configure an IP address for an interface on a PPP link, if you delete the IP address of the
interface on the PPP link that fulfills the IPCP negotiation and assign this IP address to an interface on
another PPP link, the IPCP negotiation of the later PPP link will definitely be unsuccessful. To solve
this problem, you can run the shutdown and undo shutdown commands on the former interface to
restore the IPCP negotiation or assign a new IP address to the later interface.
l When you configure an IP address for an interface on a PPP link, if the configuration is correct but the
negotiation is always unsuccessful, it is recommended that you assign a new IP address to the interface.
[RouterA-Pos1/0/0] link-protocol ppp
# Authenticate Router B in the PAP mode.

[RouterA-Pos1/0/0] ppp authentication-mode pap
PPP.
[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 hello@163.net password cipher !QAZ@WSX3edc

[RouterB-Pos1/0/0] undo shutdown
After the configuration is complete, by executing the display interface command on every
router, you can see the LCP status is Opened.
Use Router A as an example.

<RouterA-Pos1/0/0] display interface pos 1/0/0
Flag C2 22(0x16)
SDH alarm:
section layer: none
line layer: none
path layer: none
SDH error:
section layer: B1 0
----End
Configuration Files
#
sysname RouterA
#
interface Pos 1/0/0
link-protocol ppp
undo shutdown
ip address 10.110.0.1 255.255.255.0
#
aaa
local-user hello@163.net password cipher %$%$#{!{*"|uh/$|z(E0TW=G_Gj~%$%
$
local-user hello@163.net service-type
none
local-user hello@163.net state block fail-times 3 interval 5

#
return

#
sysname RouterB
#
interface Pos1/0/0
link-protocol ppp
ppp pap local-user hello@163.net password cipher %$%$#{!{*"|uh/$|z(E0TW=G_Gj~
%$%$
undo shutdown
ip address 10.110.0.2 255.255.255.0
#
return
4.11.2 Example for Configuring Unidirectional CHAP

Authentication
This example shows how to configure two devices so that one end (the authenticator) can
authenticate the other end (the authenticated) in CHAP mode on a typical network.
NOTE
Unidirectional CHAP Authentication is not supported on the X1 and X2 models of the NE80E/40E.
As shown in Figure 4-2, Router A is required to authenticate Router B in CHAP mode and
should be configured with a user name.
Figure 4-2 Networking for unidirectional CHAP authentication

POS1/0/0
POS1/0/0
10.110.0.1/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.
Data Preparation

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
[RouterA] aaa
[RouterA-aaa] quit
PPP.
NOTE
# 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.

Step 2 Configure Router B
# Add the user name of Router A and the local password to the local user list of Router B.
[RouterB] aaa
[RouterB-aaa] local-user hello1@163.net password cipher 6yhn&UJM
[RouterB-aaa] quit
# Configure the IP address for POS 1/0/0 and configure the link-layer encapsulation protocol as
PPP.
[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
After the configuration is complete, run the display interface command on every router, and
you can find the LCP state is LCP opened. Use Router A as the example.
[RouterA] display interface pos 1/0/0
Flag C2 22(0x16)
SDH alarm:
section layer: none
line layer: none
path layer: none
SDH error:
section layer: B1 0
----End
Configuration Files
#
sysname RouterA
#
interface Pos1/0/0
link-protocol ppp
ppp chap user rta
undo shutdown
ip address 10.110.0.1 255.255.255.0
#
aaa
$

none
#
return

#
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 hello1@163.net password cipher %$%$>ca'OE)3tA<_sj(c}[v(`,-=%$%
$
local-user hello1@163.net service-type
none
local-user hello1@163.net state block fail-times 3 interval 5
#
return
4.11.3 Example for Configuring Bidirectional CHAP

Authentication
This example shows how to configure bidirectional CHAP authentication between two devices
on a typical network.
NOTE
CHAP Authentication is not supported on the X1 and X2 models of the NE80E/40E.
As shown in Figure 4-3, Router A and Router B need to perform bidirectional CHAP
authentication.
Figure 4-3 Networking for bidirectional CHAP authentication
POS1/0/0
POS1/0/0
10.110.0.1/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
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 on Router B
NOTE
Router A and Router B must be configured with the same password, or the authentication fails.
Procedure
[RouterA] aaa
[RouterA-aaa] quit
PPP.
NOTE
# Configure the username of Router A used by Router B to authenticate it 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

# Add the username of Router A and the local password to the local user list of Router B.
[RouterB] aaa
[RouterB-aaa] quit

PPP.
[RouterB-Pos1/0/0] link-protocol ppp
# Configure the user name of Router B used by Router A to authenticate it 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
After the configuration is complete, run the display interface command on every router, and
you can see the LCP status is Opened.
[RouterA] display interface pos 1/0/0
Flag C2 22(0x16)
SDH alarm:
section layer: none
line layer: none
path layer: none
SDH error:
section layer: B1 0
----End
Configuration Files
#
sysname RouterA
#

interface Pos1/0/0
link-protocol ppp
ppp chap user rta
undo shutdown
ip address 10.110.0.1 255.255.255.0
#
aaa
$
none
#
return

#
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
$
none
#
return
4.11.4 Example for Configuring PPP Multiplexing
Router A and Router B are connected through CPOS interfaces, which are added to an MP-
Group. PPP multiplexing is enabled on both ends of the MP link so that all PPP frames
transmitted on the link are multiplexed.
Figure 4-4 Networking for PPP multiplexing configurations
MP-Group3/0/0 MP-Group3/0/0
10.1.1.1/24 10.1.1.2/24
Serial 3/0/1/1:1 Serial 3/0/1/1:1
Serial 3/0/1/2:2 Serial 3/0/1/2:2

RouterA RouterB

1. Create an MP-Group interface and add interfaces to it.

2. Enable PPP multiplexing.
Data Preparation
l IP addresses of the MP-Group interfaces on Router A and Router B
Procedure
Step 1 Create an MP-Group interface and add interfaces to it.
NOTE
The two slot IDs where the MP-Group interface and the added interface reside must be on the same board.
That is, inter-board binding is not supported.
# Configure Router A.
[RouterA] interface mp-group3/0/0
[RouterA] controller cpos 3/0/1
[RouterA-Cpos3/0/1] undo shutdown
[RouterA-Cpos3/0/1] quit
[RouterA] interface serial 3/0/1/1:1
[RouterA-Serial3/0/1/1:1] ppp mp mp-group3/0/0
[RouterA] interface serial 3/0/1/2:2
[RouterA-Serial3/0/1/2:2] ppp mp mp-group3/0/0
[RouterA-Mp-group3/0/0] ip address 10.1.1.1 24
# Configure Router B.
[RouterB] interface mp-group3/0/0
[RouterB] controller cpos 3/0/1
[RouterB-Cpos3/0/1] e1 1 channel-set 1 timeslot-list 1-10
[RouterB-Cpos3/0/1] e1 2 channel-set 2 timeslot-list 11-15
[RouterB-Cpos3/0/1] undo shutdown
[RouterB-Cpos3/0/1] quit
[RouterB] interface serial 3/0/1/1:1
[RouterB-Serial3/0/1/1:1] shutdown
[RouterB-Serial3/0/1/1:1] ppp mp mp-group3/0/0
[RouterB-Serial3/0/1/1:1] undo shutdown
[RouterB-Serial3/0/1/1:1] quit
[RouterB] interface serial 3/0/1/2:2
[RouterB-Serial3/0/1/2:2] shutdown
[RouterB-Serial3/0/1/2:2] ppp mp mp-group3/0/0
[RouterB-Serial3/0/1/2:2] undo shutdown
[RouterB-Serial3/0/1/2:2] quit


[RouterB-Mp-group3/0/0] ip address 10.1.1.2 24
Step 2 Configure PPP multiplexing.

NOTE
Default parameter values for PPP multiplexing
# Enable PPP multiplexing on Router A.

[RouterA-Mp-group3/0/0] ppp multiplexed
[RouterA-Mp-group3/0/0] ppp multiplexed delay 1
# Enable PPP multiplexing on Router B.

[RouterB-Mp-group3/0/0] ppp multiplexed
[RouterB-Mp-group3/0/0] ppp multiplexed delay 1

Check the negotiation results of PPP multiplexing on Router A.
[RouterA] display interface mp-group3/0/0
LCP opened, MP opened, IPCP opened, PPPMuxCP opened
Traffic statistics:
Last 300 seconds input rate 0 bytes/sec, 0 packets/sec
Last 300 seconds output rate 0 bytes/sec, 0 packets/sec
0 errors, 0 drops
0 errors, 0 drops
----End
Configuration Files
#
sysname RouterA
#
undo shutdown
#
link-protocol ppp
#
link-protocol ppp
#

ppp multiplexed
ppp multiplexed delay 1
ip address 10.1.1.1 255.255.255.0
#
return

#
sysname RouterB
#
undo shutdown
#
link-protocol ppp
#
link-protocol ppp
#
ppp multiplexed
ppp multiplexed delay 1
ip address 10.1.1.2 255.255.255.0
#
return
4.11.5 Example for Binding MPs into an MP-group

This example shows how to bundle serial interfaces into an MP-group interface so that routers
can communicate through the MP-group interface on the typical network where two routers are
connected through two pairs of serial interfaces.
NOTE
This document uses interface numbers and link types of the NE40E-X8 as examples. In working situations,
the actual interface numbers and link types may be different.
Two serial interfaces of Router A and Router B are connected, respectively, you can bundle the
serial interfaces into an MP group to configure MP binding.
Figure 4-5 Networking for the MP-group binding

Mp-group1/0/1 Mp-group2/0/1
10.1.1.1/24 10.1.1.2/24
Serial1/0/0:0 Serial2/0/0:0
Serial1/0/1:0 Serial2/0/1:0
Router A Router B

1. Configure the local user lists on Router A and Router B.

2. Enable PAP authentication on Router A and Router B.
3. Create the MP-group interface and add related interfaces to MP-group.
4. Restart interfaces to validate the configuration.
Data Preparation
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 and card numbers of MP-Group interface must be consistent with the slot and card numbers
of the interface added to the MP-Group.
l The interfaces added to the MP-group can only be serial interfaces.
l PAP or CHAP authentication is unnecessary when you configure MP binding by using MP-group.
Procedure
<RouterA> system-view
[RouterA] aaa
[RouterA-aaa] quit
# Create an Mp-group interface and configure the corresponding interface.

[RouterA-Mp-group1/0/1] ip address 10.1.1.1 255.255.255.0
# Configure Serial 1/0/0:0 to perform the PAP authentication.

[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
# Add Serial 1/0/0:0 to the Mp-group interface.

[RouterA-Serial1/0/0:0] ppp mp mp-group1/0/1
# Configure Serial 1/0/1:0 to perform the PAP authentication.

[RouterA] interface Serial1/0/1:0
[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] ppp mp mp-group1/0/1

# Add the username and password of Router A to the local user list of Router B.
<RouterB> system-view
[RouterB] aaa
[RouterB-aaa] quit
# Create an Mp-group interface and configure the corresponding IP address.

[RouterB-Mp-group2/0/1] ip address 10.1.1.2 255.255.255.0
[RouterB-Mp-group2/0/1] shutdown
# Configure Serial 2/0/0:0 and perform the PAP authentication.

[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] ppp mp mp-group2/0/1
# Configure Serial 2/0/1:0 and perform the PAP authentication.

[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] ppp mp mp-group2/0/1
Step 3 Restart the sub-tunnel and the MP-group interface.
# Restart the sub-tunnel and the MP-group interface on Router A.

# Restart the sub-tunnel and the MP-group interface on Router B.


[RouterB-Mp-group2/0/1] undo shutdown

# Check the configuration on Router A.

[RouterA] display ppp mp interface Mp-group1/0/1
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/1
Bundle Multilink, 2 member, slot 2, Master link is Mp-group2/0/
Serial2/0/0:0
Serial2/0/1:0
Ping through the IP address of the MP-group 2/0/1 on Router A.

0.00% packet loss
----End
Configuration Files
#
sysname RouterA
#
undo shutdown
link-protocol ppp
ppp pap local-user rta password simple rta
#

undo shutdown
link-protocol ppp
ppp pap local-user rta password simple rta
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
aaa
$
none
#
return

#
sysname RouterB
#
undo shutdown
link-protocol ppp
ppp pap local-user rtb password simple rtb
#
undo shutdown
link-protocol ppp
ppp pap local-user rtb password simple rtb
#
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
aaa
$
none
#
return

Configuration Guide - WAN Access 5 Frame Relay Configuration
5 Frame Relay Configuration
About This Chapter
Frame Relay (FR) uses virtual circuits (VCs) and works at the physical layer and data link layer
of the OSI model. FR features large throughput and short delays. It is most applicable to network
services with bursts of traffic.
NOTE
Frame Relay cannot be configured on the X1 and X2 models of the NE80E/40E.
5.1 Introduction
This section describes FR in terms of concepts, frame formats, and Multilink Frame Relay
(MFR).
5.2 Configuring FR
This section describes how to configure basic FR functions. Detailed operations include
configuring FR user-network interfaces (UNIs) and FR network-network interfaces (NNIs) to
communicate and configuring basic functions for FR sub-interfaces.
5.3 Configuring FR LMI Type and Related Parameters

This section describes how to configure the FR LMI protocol and DTE-related or DCE-related
parameters.
5.4 Configuring FRF.8

FRF.8 provides service interworking functionality that allows a Frame Relay end user to
communicate with an ATM end user.
5.5 Maintaining Frame Relay Configuration

This section describes how to maintain FR. Detailed operations include clearing the FR statistics.

This section provides several FR examples. These configuration examples explain the
networking requirements, configuration roadmap, data preparation, configuration procedure,
and configuration files.

5.1 Introduction
This section describes FR in terms of concepts, frame formats, and Multilink Frame Relay
(MFR).
5.1.1 FR Protocol Overview

FR uses Virtual Circuits (VCs) to connect FR devices on both ends of an FR network. Each VC
defines an FR channel using the Data Link Connection Identifier (DLCI).
A Frame Relay (FR) network provides data communication between user devices (such as
routers and hosts).
FR devices and interfaces can be divided into Data Terminal Equipment (DTE) , Data Circuit-
terminating Equipment (DCE) , and Network-to-Network Interfaces (NNIs) .
In practice, the DTE interface can be connected only with the DCE interface; the NNI interface
can be connected only with another NNI interface.
An FR network can be a public network, a private network, or a network formed by direct

connection 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 Connection
Identifiers (DLCIs). Each VC detects and maintains the VC status through the Local
Management Interface (LMI).
5.1.2 Features of FR on the NE80E/40E

The NE80E/40E allows P2P POS sub-interfaces and synchronous serial interfaces created by
CE1 interfaces or E1 channels of the CPOS interfaces to be enabled with FR for transmitting
FR services.
On the NE80E/40E, the P2P POS sub-interfaces and synchronous serial interfaces created by
CE1 interfaces or E1 channels of the CPOS interfaces support the frame relay.
5.2 Configuring FR
This section describes how to configure basic FR functions. Detailed operations include
configuring FR user-network interfaces (UNIs) and FR network-network interfaces (NNIs) to
communicate and configuring basic functions for FR sub-interfaces.

Before configuring basic FR functions, familiarize yourself with the usage scenario, complete
the pre-configuration tasks, and obtain the required data.

Usage Scenario
FR is a widely used fast packet switching technology developed on the basis of X.25 technology.
It implements bandwidth multiplexing and dynamic allocation and provides a reasonable
bandwidth management and congestion avoidance mechanism.
FR has two kinds of protocols: Internet Engineering Task Force (IETF) and nonstandard.
IETF is used to encapsulate packets according to RFC 1490 specifications and nonstandard is
used to interconnect to non-Huawei routers.
Both parties in communication are configured in either DTE or DCE format according to their
respective location on a network.
The FR module has two types of interfaces: main interface and sub-interface. The NE80E/40E
can communicate with other devices only through P2P POS sub-interfaces, through synchronous
serial interfaces, and/or through sub-interfaces created by CE1 interfaces or E1 channels of the
CPOS interfaces.
For the network layer, the sub-interface can be used to configure the PVC. This PVC is used to
connect to the remote equipment.
Data Link Connection Identifier is locally valid. You can specify the same DLCI number for
two ends of a link, or specify the same DLCI number for multiple interfaces. Different physical
interfaces, however, must be configured with different DLCI numbers.
Before configuring the basic FR functions, configure the physical attributes of the FR interface
on a router.
Data Preparation
To 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

To enable an interface to forward FR services, configure FR as a link layer protocol, the Data
Link Control Identifier (DLCI), and the IP address.
Context

Procedure
Step 1 Run:
system-view
Step 2 Run:
The FR interface view is displayed.
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.
An 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 FR
configurations on the interface. Then, delete all the sub-interfaces to re-configure the FR.
l After modifying the link layer protocol, first run the shutdown command to shut down the interface
and then run the undo shutdown command to restart the interface to validate the configuration.

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 configuring the FR function on P2P POS sub-interfaces , on synchronous serial
interfaces, and on sub-interfaces created by CE1 interfaces or E1 channels of the CPOS interfaces.
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 command
on the main interface in succession, the two commands should be used at an interval of at least 15
seconds.
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 must
be 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

After basic FR functions are configured, you can view the status of the FR protocol, interface
information, and the mapping between the protocol address and the FR address.
Prerequisites
The configurations of FR are complete.
Procedure
l Run the display fr interface [ interface-type interface-number[.subnumber ] ] command
to check the status of the FR protocol and information about the interface.
----End
Example
Run the display fr interface command. If the status of the FR protocol and information about
the interface are displayed, it means the configuration is successful.
<HUAWEI> display fr interface
Pos1/0/0, DTE, physical up, protocol up
Pos1/0/0.1, point-to-point, protocol up
Pos1/0/0.2, point-to-point, protocol up
5.3 Configuring FR LMI Type and Related Parameters

This section describes how to configure the FR LMI protocol and DTE-related or DCE-related
parameters.

Before configuring the FR LMI type and related parameters, familiarize yourself with the usage
scenario, complete the pre-configuration tasks, and obtain the data required for the configuration.
Usage Scenario
When the LMI protocol is needed to maintain FR link status and PVC status as well as to optimize
the device, configure the LMI type and other related parameters.

Before configuring the FR LMI type and related parameters, complete the following tasks:
l Configure physical parameters for Frame Relay interfaces.

l Configure Frame Relay interfaces.
Data Preparation
To 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

This section describes how to configure DTE-related parameters including the polling interval
and the n391, n392, and n393 values.
Procedure
Step 1 Run:
system-view
Step 2 Run:
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:
timer hold seconds
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.
Step 6 Run:
The DTE N392 parameter is configured.
Step 7 Run:
The DTE N393 parameter is configured.
----End
5.3.3 Configuring FR LMI and Related Parameters of DCE

This section describes how to configure DCE-related parameters including the n392, n393, and
t392 values.
Procedure
Step 1 Run:
system-view
Step 2 Run:
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 packet
is 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


After the FR LMI type and related parameters are configured, you can view the FR LMI packet
statistics.
Prerequisites
FR LMI type and related parameters have been configured.
Procedure
l Run the display fr lmi-info [ interface interface-type interface-number ] command to
check FR LMI packet statistics.
----End
Example
Run the display fr lmi-info command. If statistics about FR LMI packets are displayed, it means
the configuration succeeds. For example:
<HUAWEI> display fr lmi-info
Frame 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 Configuring FRF.8

FRF.8 provides service interworking functionality that allows a Frame Relay end user to
communicate with an ATM end user.
Usage Scenario
To communicate over WANs, end-user stations must use the same type of transmission protocol.
This limitation has prevented differing networks, such as Frame Relay and ATM, from being
linked. However, the Frame Relay-to-ATM Service Interworking (FRF.8) feature allows Frame
Relay and ATM networks to exchange data, despite differing network protocols.
Before configuring FRF.8, configure link layer protocol parameters for the interface and ensure
that the status of the link layer protocol on the interface is Up.
Data Preparation
To configure FRF.8, you need the following data.
No. Data
1 Serial interface number
2 FR sub-interface number

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
link-protocol fr
The link layer protocol is configured as FR encapsulation format.
By default, the link layer protocol of a serial interface is PPP.
The link layer protocol of a serial interface must be configured as FR encapsulation format in
order to configure FRF.8 on the interface.
Step 4 Run:
interface serial interface-number.subinterface-number p2p
The P2P FR sub-interface view is displayed.
Step 5 Run:
fr iwf service { transparent | translation }
The function of Frame Relay-to-ATM Service Interworking feature is enabled and the working-
mode of Frame Relay-to-ATM Service Interworking feature is set.

fr iwf clp-bit { 1 | 0 | map-de }
The ATM cell loss priority (CLP) field in the ATM cell header is set.

fr iwf efci-bit { 0 | map-fecn }
The ATM cell explicit forward congestion indication (EFCI) field in the ATM cell header is set.

fr iwf de-bit { 1 | 0 | map-clp }
The Frame Relay discard eligible (DE) field in the Frame Relay cell header is set.
----End
Checking the Configurations

Run the display this command to check the FRF.8 configuration information about FR sub-
interface.
[HUAWEI-Serial2/1/0.1] display this
#
interface Serial1/2/0/4:0.1 p2p
fr dlci 23
fr iwf service transparent

fr iwf clp-bit 1
fr iwf efci-bit 0
#
return
5.5 Maintaining Frame Relay Configuration

This section describes how to maintain FR. Detailed operations include clearing the FR statistics.
5.5.1 Clearing the Statistics of FR and Dynamic Address Mapping

Entries
You can use the reset commands to clear the statistics on FR interfaces or dynamic address
mapping entries.
Procedure
l Run the reset counters interface [ interface-type [ interface-number ] ] command to check
----End

This section provides several FR examples. These configuration examples explain the
and configuration files.
5.6.1 Example for Connecting Devices with POS Interfaces Through

an FR Network
This example shows how to configure POS interfaces on three routers in different network
segments to communicate with each other over an FR network.
As shown in Figure 5-1, three routers are interconnected through POS interfaces on the FR
network. The routers work in DTE mode as user devices.
Router A connects Router B and Router C through sub-interfaces. Router B and Router C reside
on different network segments than Router A.

Figure 5-1 Networking for connecting routers using a POS interface through an FR network
POS1/0/0.1
POS1/0/0.1 DLCI=21
DLCI=21 10.1.1.2/30 Router B
10.1.1.1/30 Frame
Relay
network
Router A POS1/0/0.2
DLCI=22 POS1/0/0.2
10.2.1.1/30 DLCI=22
10.2.1.2/30
Router C
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
# Encapsulate the FR protocol.

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



Step 2 Configure Router B and Router C.

The method for configuring Router B and Router C is the same as the method for configuring
Router A. For configuration details, see "Configuration Files" in this section.
Run the display interface pos command on each router. The command output shows that the
connectivity of each POS interface is Up.
Run the ping command on each router. Each router can ping through the network.
----End
Configuration Files
#
sysname RouterA
#
interface Pos1/0/0
link-protocol fr
undo shutdown
#
fr dlci 21
ip address 10.1.1.1 255.255.255.252
#
fr dlci 22
ip address 10.2.1.1 255.255.255.252
#
return

#
sysname RouterB
#
interface Pos1/0/0
link-protocol fr
undo shutdown
#
fr dlci 21
ip address 10.1.1.2 255.255.255.252
#
return

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

Configuration Guide - WAN Access 6 HDLC and IP-Trunk Configuration
6 HDLC and IP-Trunk Configuration
About This Chapter
The High-level Data Link Control (HDLC) is a bit-oriented link layer protocol. HDLC boasts
transparent transmission of any type of bit flow. A trunk can aggregate multiple interfaces into
an aggregation group to implement load balancing on member interfaces for received and sent
packets. At the same time, connectivity can be of higher reliability.
NOTE
HDLC and IP-Trunk cannot be configured on the X1 and X2 models of the NE80E/40E.
6.1 Introduction
This section describes HDLC in terms of frame formats, frame types, and applicable scenarios
together with IP-Trunk applications.
6.2 Configuring HDLC

This section describes how to configure basic HDLC functions, including configuring the data
link protocol of an interface as HDLC, an IP address for an interface, and the polling interval.
6.3 Configuring an IP-Trunk Interface

This section describes how to configure an IP-Trunk interface, add interfaces, configure an IP
address, configure the lower threshold of Up links, configure the load-balance mode, weights
for member links, a backup interface, and the method for sending trap messages.
6.4 Maintaining HDLC and IP-Trunk Configuration

This section describes how to maintain HDLC and IP-Trunk, including clearing the statistics
about the HDLC or on IP-Trunk interfaces.

This section provides several examples for HDLC and IP-Trunk. These configuration examples
explain the networking requirements, configuration roadmap, data preparation, configuration
procedure, and configuration files.

6.1 Introduction
This section describes HDLC in terms of frame formats, frame types, and applicable scenarios
together with IP-Trunk applications.
6.1.1 HDLC and IP-Trunk Interface Overview

The High-level Data Link Control (HDLC) is a typical bit-oriented synchronization data control
protocol. It uses the full-duplex mode and CRC check. Its transmission control function is
independent of the processing function. It features control capabilities and can be flexibly used.
HDLC allows any type of bit flow to be transparently transmitted. Data does not need to be a
character set.
A trunk is aggregated by multiple ports for load balancing. A trunk can enhance connection
reliability.
Trunk interfaces are divided into Eth-Trunk and IP-Trunk interfaces.
The IP-Trunk consists of POS links only. The Eth-Trunk consists of only Ethernet links. For
configuration of the Eth-Trunk interface, refer to the HUAWEI NetEngine80E/40E Router
Configuration Guide - LAN Access & MAN Access.
IP-Trunk technology has the following advantages:

l Increasing bandwidth: The bandwidth of an IP-Trunk interface is the sum of all the
bandwidth of member ports.
l Enhancing reliability: If a member link fails, traffic is automatically switched to other
available links.
6.1.2 Features of HDLC and IP-Trunk interfaces on the router

Standard HDLC suite protocols run on synchronous serial lines. An IP-Trunk consists of POS
links only. Any link layer protocol added to an IP-Trunk interface must be HDLC.
A maximum of 64 trunk interfaces can be created on a router, and each trunk interface can contain
up to 16 physical member links.
An IP-Trunk interface has the following characteristics. It supports:

l Configured IP addresses. When forwarding packets, each member interface uses the IP
address of the IP-Trunk interface.
l MPLS forwarding and Layer 3 forwarding (including unicast and multicast). The Hash
algorithm can be used in flow-based load balancing.
l QoS based on physical ports rather than logical ports.
l MPLS and binding VPN instances.
l Hot backup and hot swapping.

NOTE
If member ports of the Trunk reside on different LPUs, configure a BFD session to detect the links between
member ports and use the process-interface-status command to associate the status of an interface with
the BFD session. Otherwise, in some scenarios (for example, restarting the LPU where member ports of
the Trunk are located), traffic loss will occur. For detailed configurations of BFD, see the HUAWEI
NetEngine80E/40E Router Configuration Guide - Reliability.
6.2 Configuring HDLC

This section describes how to configure basic HDLC functions, including configuring the data
link protocol of an interface as HDLC, an IP address for an interface, and the polling interval.

Before configuring basic HDLC functions, familiarize yourself with the usage scenario,
Usage Scenario
When you need to enable the bits synchronous transmission, you can adopt the HDLC protocol.
Before configuring the basic HDLC functions, configure the physical attributes of the interface
to change the physical status to Up.
Data Preparation
To 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

The link layer protocol of the interfaces joining an IP-Trunk interface must be HDLC.
Procedure
Step 1 Run:
system-view
Step 2 Run:

Step 3 Run:
link-protocol hdlc
The interface is configured with HDLC.
----End
6.2.3 Configuring the IP Address of the Interface

You can assign an IP address to an interface or configure an unnumbered IP address on the
interface.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Choose one of the following steps to configure the IP address or IP unnumbered address of the
interface.
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 interface borrowing
an IP address from another interface must have the ability to learn about the route to the remote end.
Otherwise, the packets sent from the interface cannot reach the remote end.
When you use IP address unnumbered, configure a static route or dynamic routing protocol so
that the interface borrowing the interface can learn about the route to the remote end.
When an interface borrows an IP address from another interface, adhere to the following rules:
l If you use a dynamic routing protocol, ensure the length of the learned route mask is longer
than that of the lender's IP address mask, because the NE80E/40E uses the longest match
rule when searching for routes.
l If you use a static route and the IP address of the lender uses a 32-bit mask, the length of the
static route mask must be shorter than 32 bits.
l If you use a static route and the IP address of the lender uses a mask less than 32 bits, the
length of the static route mask must be longer than that of the lender's IP address mask.
----End
6.2.4 Setting the Polling Interval

You can configure the interval for the DTE to send status inquiry packets.

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
timer hold seconds
The polling interval is configured.
By default, the polling 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 status
of a link. Configure identical polling interval on the both ends.
You can use the default polling interval or adjust it as required. In the case of long network delay
or high congestion, prolong the polling interval to reduce the possibility of network flapping.
NOTE
The GE interfaces and MP-Group interfaces do not support this configuration.
----End

After basic HDLC functions are configured, you can view the status, link layer protocol and
configuration of the interface.
Prerequisites
HDLC has been configured.
Procedure
status, link layer protocol and configuration of the interface.
----End
Example
Run the display interface command to view the status, link layer protocol, and configuration
of the interface.
Description: Pos1/0/0 Interface

Link layer protocol is nonstandard HDLC

The Vendor PN is FTRJ8519P1BNL-HW
Port BW: 2.5G, Transceiver max BW: 1G, Transceiver Mode: MultiMode
WaveLength: 850nm, Transmission Distance: 300m
Rx Power: -5.84dBm, Tx Power: -5.97dBm
Flag C2 22(0x16)
SDH alarm:
section layer: none
line layer: none
path layer: none
SDH error:
section layer: B1 0
6.3 Configuring an IP-Trunk Interface

This section describes how to configure an IP-Trunk interface, add interfaces, configure an IP
address, configure the lower threshold of Up links, configure the load-balance mode, weights
for member links, a backup interface, and the method for sending trap messages.

Before configuring an IP-Trunk interface, familiarize yourself with the usage scenario, complete
the pre-configuration tasks, and obtain the data required for the configuration.
Usage Scenario
To improve the communication ability of links, sometimes, multiple POS ports are bound to an
IP-Trunk interface. The bandwidth of an IP-Trunk interface is the sum of all bandwidth on all
the member interfaces.
IP-Trunk interfaces can realize load balancing. To avoid congestion, traffic to the same
destination is transported on different member links.
In addition, IP-Trunk interfaces can improve link reliability. If a member port is Down, traffic
is switched to another available port.
None
Data Preparation
To create an IP-Trunk interface, you need the following data.

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
You first need to create an IP-Trunk interface and then to add POS interfaces whose link layer
protocol is HDLC to the IP-Trunk interface.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface ip-trunk trunk-id
The IP-Trunk interface is created.

Step 3 Run:
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:
l The link layer protocol of the interfaces that are added into an IP-Trunk interface must be
HDLC.
l By default, the link layer protocol of a POS interface is PPP. 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 any
Layer 3 feature or service.
l A POS interface can join only one IP-Trunk interface. To add the POS interface to another
IP-Trunk interface, you must first remove it from the original IP-Trunk.
l Member interfaces of an IP-Trunk cannot be IP-Trunks.
l The POS interfaces of different interface boards can be added to 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, each
interface 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 transmission
capability of the 10 Gbit/s POS interface can only reach 2.5 Gbit/s. The transmission
capability of the IP-Trunk drops to 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 directly
connected to the member interfaces must be bound to an IP-Trunk interface. Otherwise, the
two ends cannot communicate.
Step 7 Run:
undo shutdown
The interface is enabled.
----End
6.3.3 Configuring an IP Address for the IP-Trunk Interface

You can assign an IP address to an IP-Trunk interface and configure member interfaces to borrow
the IP address.
Context
Perform the following steps on the routers that are configured with IP-Trunk interfaces.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The IP-Trunk interface view is displayed.
Step 3 Run:

The IP address is configured for the IP-Trunk interface.
----End
6.3.4 (Optional) Configuring the Lower Threshold of Up Links

When the number of Up member interfaces of an IP-Trunk is less than the lower threshold, the
IP-Trunk goes Down.
Context
Perform the following steps on the routers configured with IP-Trunk interfaces.
Procedure
Step 1 Run:
system-view
Step 2 Run:
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 member
interface is Up.
NOTE
To ensure normal forwarding, it is recommended to configure the same lower threshold at both ends of a
Trunk link.
----End
6.3.5 (Optional) Configuring Load-balancing Mode for the IP-

Trunk Interface
The load-balancing mode of an IP-Trunk interface can be configured as required.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the IP-Trunk interface is displayed.
Step 3 Run:
load-balance { src-dst-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 src-dst-
ip.
l Load balancing based on IP addresses can guarantee packet order, but cannot improve
bandwidth usage.
l Packet-by-packet load balancing can improve bandwidth usage but cannot guarantee packet
order.
----End
6.3.6 (Optional) Configuring Weights for Member Links

The greater weight a member interface possesses, the heavier load the member link carries.
Context
For an IP-Trunk interface, the sum of the weights of all its member interfaces cannot be greater
than 16. The IP-Trunk interface implements load balancing based on the weight of each member
interface.
In an IP-Trunk interface, the larger the weight of a member interface, the heavier the traffic on
the member link.
Procedure
Step 1 Run:
system-view
Step 2 Run:
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 load
balancing weight of a member interface, run the shutdown and undo shutdown commands to restart the
member interface so the configuration can take effect.
----End
6.3.7 (Optional) Configuring the Method of Sending Trap Messages

from an IP-Trunk Member Interface
You can configure an IP-Trunk member interface to send trap messages through a private MIB.
Context
Perform the following steps on the devices where IP-Trunk interfaces are created:
Procedure
Step 1 Run:
system-view
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 private
MIB.
By default, an IP-Trunk member interface in the Up or Down state sends trap messages through
the public MIB.
The trap message sent through the public MIB does not carry information about the IP-Trunk
interface. If you want the trap message sent by an IP-Trunk member interface to carry
information about the IP-Trunk interface, run the trunk-member trap in private-mib enable
command.
----End

After an IP-Trunk interface is configured, you can view its status, information about the other
IP-Trunk member interfaces, and the forwarding table of the IP-Trunk interface.
Prerequisites
An IP-Trunk interface has been configured.
Procedure
l Run the display interface ip-trunk [ trunk-id ] command to check the status of the IP-
Trunk interface.

l Run the display trunkmembership ip-trunk trunk-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
Example
Run the display interface ip-trunk command. If the physical status, link protocol status, IP
address, and load-balancing mode of the IP-Trunk interface are displayed, it means the
configuration succeeds. For example:
<HUAWEI> display interface ip-trunk 1
Ip-Trunk1 current state : UP
Last line protocol up time: 2007-11-03, 17:45:06
Description : Ip-Trunk1 Interface
Route Port,Hash arithmetic : According to IP,The Maximum Transmit Unit is 4470
Physical is IP_TRUNK
Statistics last cleared: 2008-08-02 15:32:27
Input: 0 packets,0 bytes,
0 unicast,0 broadcast,0 multicast
0 errors,0 drops,0 unknownprotocol
Output:0 packets,0 bytes,
0 errors,0 drops
-----------------------------------------------------
PortName Status Weight
-----------------------------------------------------
Pos1/0/0 UP 1
-----------------------------------------------------
The Number of Ports in Trunk : 1
The Number of UP Ports in Trunk : 1
Run the display trunkmembership ip-trunk command. If the member interfaces, number of
members, and number of Up members are displayed, it means the configuration succeeds. For
example:
<HUAWEI> display trunkmembership ip-trunk 1
Trunk ID: 1
TYPE: pos
Number Of Ports in Trunk = 2
Number Of UP Ports in Trunk = 0
operate status: down
Interface Pos6/0/0, valid,selected,operate down,weight=1
standby interface NULL
Interface Pos6/0/1, valid,selected,operate down,weight=1
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 SLAVE
Pos3/1/1 Pos3/1/0
Pos3/1/0 Pos3/1/1
Pos3/1/1 Pos3/1/0
Pos3/1/1 Pos3/1/0

Pos3/1/0 Pos3/1/1
Pos3/1/1 Pos3/1/0
Pos3/1/1 Pos3/1/0
Pos3/1/0 Pos3/1/1
Pos3/1/1 Pos3/1/0
Pos3/1/1 Pos3/1/0
Pos3/1/0 Pos3/1/1
Pos3/1/1 Pos3/1/0
Pos3/1/1 Pos3/1/0
Pos3/1/0 Pos3/1/1
Pos3/1/0 Pos3/1/1
Pos3/1/1 Pos3/1/0
6.4 Maintaining HDLC and IP-Trunk Configuration

This section describes how to maintain HDLC and IP-Trunk, including clearing the statistics
about the HDLC or on IP-Trunk interfaces.
6.4.1 Clearing the Statistics About HDLC or IP-Trunk Interfaces

You can run the reset commands to clear interface statistics before recollecting traffic statistics
on the interface.
Context
NOTICE
The previous statistics cannot be restored after you clear them. Exercise caution when you use
the reset command.
To reset the interface statistics about the Network Management System (NMS) or the interface
statistics displayed using the display interface command, run the following commands in the
user view.
NOTE
For the display of interface statistics on the NMS, see the related NMS manuals.
Procedure
----End

This section provides several examples for HDLC and IP-Trunk. These configuration examples

6.5.1 Example for Configuring HDLC

This example shows how to configure HDLC to interconnect devices in typical networking.
Router A and Router B are connected by POS interfaces, and the interfaces are required to run
HDLC.
Figure 6-1 Networking diagram of the HDLC functions
POS1/0/0 POS1/0/0
10.1.1.1/24 10.1.1.2/24
RouterA RouterB
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
NOTE
The IP addresses of interfaces on Router A and Router B must be on the same network segment; otherwise,
the link layer status of the two interfaces cannot be Up.
Procedure
[RouterA-Pos1/0/0] link-protocol hdlc
[RouterA-Pos1/0/0] ip address 10.1.1.1 24

[RouterB-Pos1/0/0] link-protocol hdlc


After the configuration is complete, Router A and Router B can ping through each other.

0.00% packet loss
Run the display ip routing-table command to check the accuracy of the routing table.
[RouterA] display ip routing-table
Route Flags: R - relied, D - download to fib
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 4 Routes : 4
Destination/Mask Proto Pre Cost Flags NextHop Interface
10.1.1.0/24 Direct 0 0 D 10.1.1.1 Pos1/0/0
10.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0
----End
Configuration Files
#
sysname RouterA
#
interface Pos1/0/0
link-protocol hdlc
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
return

#
sysname RouterB
#
interface Pos1/0/0
link-protocol hdlc
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
return

6.5.2 Example for Configuring IP Address Unnumbered for HDLC

This example shows how to configure IP address unnumbered to interconnect devices running
HDLC in typical networking.
Router A and Router B are connected through POS interfaces, and the interfaces are required to
run HDLC.
POS 1/0/0 of Router A borrows the IP address of the loopback interface with a mask of 32 bits.
Figure 6-2 Networking diagram of the HDLC basic function
Loopback1
11.11.11.1/24
POS1/0/0
POS1/0/0 11.11.11.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:
l IP address of the loopback interface on Router A

l IP address of the POS interface on Router B
NOTE
The two IP addresses must be on the same network segment; otherwise, the link layer status of the two
interfaces cannot be Up.

Procedure
[RouterA] interface loopback1
[RouterA-LoopBack1] ip address 10.1.1.1 32
[RouterA-LoopBack1] quit
[RouterA-Pos1/0/0] ip address unnumbered interface loopback1

Step 3 Configure the static routing on Router A.

[RouterA] ip route-static 10.1.1.2 32 pos 1/0/0
After the configuration is complete, Router A and Router B can ping through each other.

0.00% packet loss
Run the display ip routing-table command to check the accuracy of the routing table.
[RouterA] display ip routing-table
Route Flags: R - relied, D - download to fib
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 4 Routes : 4
Destination/Mask Proto Pre Cost Flags NextHop Interface
10.1.1.0/24 Static 60 0 D 10.1.1.1 Pos1/0/0
----End
Configuration Files
#

sysname RouterA
#
interface Pos1/0/0
link-protocol hdlc
undo shutdown
#
interface LoopBack1
ip address 10.1.1.1 255.255.255.255
#
ip route-static 10.1.1.0 255.255.255.0 Pos1/0/0
#
return

#
sysname RouterB
#
interface Pos1/0/0
link-protocol hdlc
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
return
6.5.3 Example for Configuring an IP-Trunk

This example shows how to configure IP-Trunk logical links to interconnect devices in typical
networking.
Create an IP-Trunk between Router A and Router B.
Figure 6-3 Configuring an IP-Trunk
IP-Trunk1
POS1/0/0 11.11.11.1/24 POS1/0/0
POS2/0/0 IP-Trunk1 POS2/0/0

1. Create an IP-Trunk interface.

2. Add the POS interfaces to the IP-Trunk interface.
Data Preparation

l Router A and Router B are connected through the POS interfaces.

l IP address of the IP-Trunk interface at Router A
l IP address of the IP-Trunk interface at Router B
Procedure
# Create IP-Trunk 1 and configure an IP address for it.

[RouterA] interface ip-trunk 1
[RouterA-Ip-Trunk1] ip address 10.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-Pos1/0/0] ip-trunk 1
[RouterA-Pos2/0/0] ip-trunk 1

# Create IP-Trunk 1 and configure an IP address for it.

[RouterB] interface Ip-Trunk 1
[RouterB-Ip-Trunk1] ip address 10.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-Pos1/0/0] ip-trunk 1
[RouterB-Pos2/0/0] ip-trunk 1
Step 3 Check the configuration.
Run the display interface ip-trunk command on Router A or Router B, and you can find that
the interface is Up.

[RouterA] display interface ip-trunk 1
Ip-Trunk1 current state : UP


Description: Ip-Trunk1 Interface
Route Port,Hash arithmetic : According to flow,The Maximum Transmit Unit is 4470
Physical is IP_TRUNK
Statistics last cleared: 2008-08-02 15:32:27
Input: 0 packets,0 bytes,
0 errors,0 drops,0 unknownprotocol
Output:0 packets,0 bytes,
0 errors,0 drops
-----------------------------------------------------
PortName Status Weight
-----------------------------------------------------
Pos1/0/0 UP 1
Pos2/0/0 UP 5
-----------------------------------------------------
The Number of Ports in Trunk : 2
The 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 1
Trunk ID: 1
TYPE: pos
Number Of Ports in Trunk = 2
Number Of UP Ports in Trunk = 2
operate status: up
Interface Pos1/0/0, valid, selected, operate up, weight=1,
Interface Pos2/0/0, valid, selected, operate up, weight=1,
The IP-Trunk interfaces of Router A and Router B can ping each other successfully.
[RouterA] ping -a 10.1.1.1 10.1.1.2
0.00% packet loss
----End
Configuration Files
#
sysname RouterA
#
interface Ip-Trunk1
undo shutdown
ip address 10.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
undo shutdown
ip-trunk 1
#
return

#
sysname RouterB
#
interface Ip-Trunk1
undo shutdown
ip address 10.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

Configuration Guide - WAN Access 7 Modem Configuration
7 Modem Configuration
About This Chapter
The modem is a commonly-used network device. It is important for a router to properly manage
and control the use of modems.
7.1 Introduction
This section describes the principle and concepts of modems.
7.2 Configuring the Modem Management

This section describes how to configure modem management. Detailed operations include
configuring the incoming and outgoing call rights of the modem and the answer mode of the
modem.
7.3 Configuring the Modem Script

This section describes how to configure the modem script. Detailed operations include
configuring the modem script, manually executing the modem script, and specifying events to
trigger the modem script.

This section provides several examples for modems. These configuration examples explain the
and configuration files

7.1 Introduction
This section describes the principle and concepts of modems.
7.1.1 Modem Overview

You can configure a router to properly manage and control modems.
Modem is a widely-used network device. The NE80E/40E provides the Modem management
and the Modem script function.
It is important for a router to properly manage and control the use of modem in a network. There
are however, many modem manufacturers and various modem models. Even though all of them
support the AT command set and are compliant with the industry standard, each type of modem
differs somewhat on the implementations and command details.
7.1.2 Features of the Modem in the NE80E/40E

The NE80E/40E provides the scripts for modem management and can trigger the modem script
with particular events, and supports the remote configuration function of a router and
communication between Huawei products and non-Huawei products.
To offer the optimal flexibility, NE80E/40E provides the following modem management
functions:
l Provides the scripts (modem script) for modem management, hence enables the user to
control the modems connected to the router. Modem script can be executed by the following
two means:
– Execute a modem script directly through the script-string command to initialize the
modem or other configurations.
– Trigger the modem script with particular events, such as router startup, modem dial-in
connection, and the start-script command.
l Using the script along with the related commands can enhance the remote configuration
function of a router. If the asynchronous serial interface works in the flow mode, the user
can establish a remote connection to the interface through the dumb terminal or modem
dial-up, to configure and manage the router.
l Interconnects Huawei products and non-Huawei products. That is, the asynchronous serial
interfaces of the participating parties are working in the flow mode and interconnected
through modems.
Running the Scripts

You can manually run a modem script or specify an event to trigger a modem script.
Then, when specific events occur, the router automatically runs the corresponding modem
scripts. The router supports the following events that can trigger a modem script.
l Successful setup of outbound connections: A specific modem script runs when an outbound
modem connection is successfully set up.

l Successful setup of inbound connections: A specific modem script runs when an inbound
modem connection is successfully set up.
l Dial-up through DCC: A dial-up script runs when dial-up is implemented through DCC.
l Connection reset: A specific modem script runs when the connection tears down.
l System power-on and reboot: A specific modem script runs on asynchronous serial
interfaces when the system is powered on and initialized.
You can also use the script command to specify a script for the preceding events.
7.2 Configuring the Modem Management

This section describes how to configure modem management. Detailed operations include
configuring the incoming and outgoing call rights of the modem and the answer mode of the
modem.
7.2.1 Establishing the Configuration

Before configuring modem management, familiarize yourself with the usage scenario, complete
the pre-configuration tasks, and obtain the data required for the configuration.
Usage Scenario
The Modem management consists of configuring the incoming and outgoing call authority and
the answer-mode
The answer-mode of Modem depends on whether the status of the asynchronous external
interface is in auto-answer mode.
l If the Modem is the auto-answer mode, users need to execute the modem auto-answer
command before dialing.
l If the Modem is not the auto-answer mode, users need to execute the undo modem auto-
answer command.
The inconsistency of the configuration with the Modem causes failure to receive the call from
Modem normally.
Before configuring Modem management, complete the following tasks:
l Power on the Modem and start the Modem normally.

l Connect the Modem to the router correctly.
Data Preparation
To configure the Modem management, you need the following data.
No. Data
1 Number of the user interface connected with Modem

No. Data
2 Interval time of the automatic response from Modem
7.2.2 Configuring the Incoming and Outgoing Call Authority of

Modem
You can configure the incoming and outgoing call rights of the modem as required.
Procedure
Step 1 Run:
system-view
Step 2 Run:
user-interface [ aux | tty ] ui-number
The user interface view is displayed.
Step 3 Choose one of the following steps to configure the call authority as required.
l Run the modem call-in command to permit only the incoming call of Modem.
l Run the modem both command to permit the incoming and outgoing call of Modem.
By default, forbid the incoming and outgoing call of Modem.
----End
7.2.3 Configuring the Answer-Mode of Modem

You can configure the answer mode of the modem and the waiting time in auto-answer mode.
Procedure
Step 1 Run:
system-view
Step 2 Run:
user-interface aux 0
the synchronous serial interface view or AUX view is displayed.
Step 3 Choose one of the following steps to configure the answer mode of the Modem as required.
l Run the modem auto-answer command to enable the Modem auto-answer.
l Run the undo modem auto-answer command to disable Modem auto-answer.
Step 4 Run:
modem timer answer seconds

The interval of the automatic response is configured.
By default, Modem is in the mode of undo modem auto-answer.
If the Modem is configured in the mode of auto-answer, the default interval time of auto-answer
is 30 seconds.
----End
7.3 Configuring the Modem Script

This section describes how to configure the modem script. Detailed operations include
configuring the modem script, manually executing the modem script, and specifying events to
trigger the modem script.
7.3.1 Establishing the Configuration

Before configuring the modem script, familiarize yourself with the usage scenario, complete the
Usage Scenario
l Usage of Modem script
– Flexibly controlling the modems of different models. Using different initialization AT
command strings can make the modems of different manufacturers or models to
interoperate better with the HUAWEI series Routers.
– Implementing the interactive login to remote systems. Interactive negotiation of the
scripts can enable the system to enter different link states. After the asynchronous serial
interfaces on the two routers set up a connection through the modem, the routers can
negotiate the protocol to be encapsulated with the physical link and its operating
parameters.
l Syntax of modem script
The modem script format that is commonly used is as follows:
receive-string1 send-string1 receive-string2 send-string2......
Where:
– Receive-string indicates receiving the character string; send-string indicates sending the
character string.
– Normally, receive-string and send-string appear in pairs, and the script must begin with
a receive-string. For example, "receive-string1 send-string1" represents the execution
flow: Expect to receive receive-string1, and send send-string1 to the modem if the
received string matches receive-string1 before timeout. Otherwise, the execution of the
subsequent script will be terminated.
– If the last string is a send-string, it indicates that the execution of the script will be
terminated after the string is sent without waiting for any receive-string.
– If it is unnecessary to receive a string at the beginning of a script, and the system can
directly wait for the send-string, then the user can set the first receive string to "", which
will be explained later.

– Except for ending with "\c", the send-string will be automatically added with an
additional return character to its end when it is sent.
– A receive-string is matched with the location-independent matching method. That is,
the match is considered successful as long as the received contents contain the expected
string.
– The match operation on a receive-string will be considered successful if the receive-
string is matched with any expected receive-strings which are separated with "-".
– By default timer will timeout after 5 seconds while waiting for a receive-string.
TIMEOUT seconds can be inserted into the script anytime to adjust the timeout time
waiting for the receive-string, which is valid till a new TIMEOUT is set in the same
script.
– All the strings and keywords in a script are case sensitive.
– Both the strings and keywords are separated by spaces. If a space is contained in a string,
it should be put in the double quotation marks (" "). A pair of empty quotation marks
(that is, "") has two meanings. When put in the beginning of a script, "" means that no
string is expected from the modem and the system will directly send the strings to the
modem. If "" locates in any other locations, the string content will be regarded to be "".
– ABORT receive-string can be inserted at any point in a script to change the script
execution flow. Its presence in the script indicates that the script execution will be
terminated if a received string is fully matched the receive-string set by ABORT
receive-string. Multiple ABORT entries can be defined in a script, and they will take
effect concurrently. Once a received string matches any of them, the script execution
will be terminated. Regardless of where the ABORT receive-string is placed, it will
take effect in the whole script execution process.
– Escape characters can be inserted in a script to control the script better and to increase
its flexibility. In addition, all the escape characters are the delimiters in the string at the
same time.
Table 7-1 Script keywords
Keyword Description
ABORT receive-string The string following ABORT will be compared with the
strings sent from a modems or remote DTE device for a match.
The match mode is full match. Multiple ABORT entries can
be configured for a script, and all of them take effect in the
whole script execution period.
TIMEOUT seconds The digit following TIMEOUT is used to set the timeout
interval that the device waits for receiving strings. If no
expected strings are received within the interval, the execution
of the script will be failed. Once set, the setting will be valid
till a new TIMEOUT is set.
By default, seconds ranges from 0 to 180. The default is 180.

Table 7-2 Script escape characters
Escape character Description
\c It means that only the specified string can be sent and the character
"Enter" will not be sent. The character of "\c" must be at the end
of the sending strings. Otherwise, it is invalid at the other location.
\d Represents pausing 2 seconds.
\n Represents the character "new line".
\r Represents the character "Enter".
\s Represents the character "Space".
\t Represents the character "Tab".
\\ Represents the character "\".
\T Represents telephone number.
l Execution Script
You can execute the Modem script manually and can also specify the event triggered
Modem script.
To connect the Modem script with events means to execute the corresponding script
automatically when some events happen. The types of the script events supported by
NE80E/40E contain:
– Establishment of successful connection of the outgoing call: execute the specified script
when the Modem outgoing call is established successfully.
– Establishment of successful connection of the incoming call: execute the specified script
when the Modem incoming call is established successfully.
– DCC dialing: enables the dialing script when you perform the DCC dialing.
– Line reset: executes the specified script when the line is disconnected.
– System powered-on and rebooted: when the system is powered on and initialized,
execute the specified script in the asynchronous serial port.
Using the script command you can specify the corresponding scripts to all the events
provided above.
Before configuring the Modem scripts, complete the following tasks:
l Connect the Modem to the router correctly.

l Configure the Modem management.
Data Preparation
To configure the Modem script, you need the following data.

No. Data
1 Name of the Modem script
2 Contents of the Modem script
7.3.2 Defining Modem Script

You can configure modem scripts to control interactive login of remote systems through modems
in different models.
Procedure
Step 1 Run:
system-view

Step 2 Run:
script-string script-name script-content
The Modem script is defined.
----End
7.3.3 Executing the Modem Script Manually

You can manually execute the modem script to management the modem attached to an interface.
Procedure
Step 1 Run:
start-script script-name number
The Modem script is executed manually.

Using the start-script command, you can manage the Modem in the interface if necessary.
----End
7.3.4 Specifying Events to Trigger the Modem

You can specify the events that trigger the automatic execution of the modem script.
Procedure
Step 1 Run:
system-view

Step 2 Run:
user-interface tty first-ui-number [ last-ui-number ]

The TTY user interface is displayed.
Step 3 Run:
script trigger login script-name
The Modem script that you can execute automatically when the connection of the outgoing call
is established successfully is specified.
Step 4 Run:
script trigger connect script-name
The Modem script that you can execute automatically when the connection of the incoming call
is established successfully is specified.
Step 5 Run:
script trigger dial script-name
The Modem script that you can execute automatically before dialing DCC is specified.
Step 6 Run:
script trigger logout script-name
The Modem script that you can execute automatically when the line resets is specified.
Step 7 Run:
script trigger init script-name
The Modem script that you can execute automatically when the charge restarts is specified.
NOTE
You can choose the any step from 2 to 7 in the above table as required.
----End

This section provides several examples for modems. These configuration examples explain the
and configuration files
7.4.1 Example for Configuring the Remote Access to the Router

Through the Modem
This example shows how to configure a PC to remotely access a router through a modem to
implement remote management of the router in typical networking.
As shown in Figure 7-1, the host accesses the AUX interface of the router through the Modem
to implement the remote management of the router.

Figure 7-1 Networking diagram of configuring the remote access to the router through the
Modem
Telephone
network
PC Modem Modem Router
1. The PC, Modem, and router are correctly interconnected.
2. Power on the PC, Modem, and router and start them normally.
3. Configure the AUX interface of the router to implement the remote access to the router
through the Modem.
Data Preparation
To configure the remote access to the router through the Modem, you need the following data:
l Level of the remote access user
l User name and password of the remote access user
l Dialup number of the PC
Procedure
Step 1 Configure the authentication mode, user level, Modem dial-in, and response mode of the access
user.
[HUAWEI] sysname Router
[Router] user-interface aux 0
[Router-ui-aux0] authentication-mode aaa
[Router-ui-aux0] user privilege level 15
[Router-ui-aux0] modem call-in
[Router-ui-aux0] modem auto-answer
[Router-ui-aux0] quit
Step 2 Configure the user name and password of the access user.
# Configure the user name and password in the AAA view.
[Router] aaa
[Router-aaa] local-user huawei password cipher Huawei-123
Step 3 Use the PC dialup number to access the AUX interface of the router.
----End
Configuration Files
#

sysname Router
#
aaa
local-user huawei password cipher %$%$#{!{*"|uh/$|z(E0TW=G_Gj~%$%$
local-user huawei service-type none
local-user huawei state block fail-times 3 interval 5
authentication-scheme default
#
authorization-scheme default
#
accounting-scheme default
#
domain default
#
#
user-interface con 0
user-interface aux 0
authentication-mode aaa
user privilege level 15
modem call-in
modem auto-answer
user-interface vty 0 4
#
return
7.4.2 Example for Configuring the Management of Modem by the

Script
This example shows how to configure a router to manage the modem using the modem script
in typical networking.
As shown in Figure 7-2, the script management of modems is adopted.
Figure 7-2 Networking diagram of the management configuration of Modem
PSTN
PC Router Modem
1. Use the standard AT command to configure the baud rate of Modem. In the AT command
group, send "AT" to Modem, and then press "OK". The Modem can then match the baud
rate automatically and store the configuration into Modem. The storing command is the
AT&W command.
2. Remove the entire configuration on Modem to restore Modem to the original state.

Data Preparation
To configure the script management of Modem, you need the following data:
l The script names are baud and factory.

l The returning message is OK after the AT is sent successfully.
l The returning message is OK after the AT&W is sent successfully.
Procedure
Step 1 Configure the baud rate of Modem.
# Configure the Modem script.

[Router] script-string baud "" AT OK AT&W OK
[Router] quit
# Assume that the Modem is connected with the interface tty1, execute the corresponding script
in the user view. Check the displayed information about the number of the interface tty1.
<Router> start-script baud 1
Step 2 Restore the Modem Factory-Set.
# The command to restore the Modem factory-set is AT&F.

[Router] script-string factory "" AT OK AT&F OK
# Assume that the Modem is connected with the interface tty1, execute the corresponding script
<Router> start-script factory 1
----End
Configuration Files
#
sysname Router
#
script-string baud "" RT OK AT&W OK
script-string factory "" AT OK AT&F OK
#
return
7.4.3 Example for Configuring the Initiation of the Power-on by the

Initiated Script
This example shows how to configure the initiation of the modem connected to a router through
an asynchronous interface when the router is powered on or restarted in typical networking.
Enable the router to initialize the Modem connected with the asynchronous port when the
router is powered-on or restarts.

l Define the Modem script.

l Specify the Modem script that runs automatically when the system is powered on or restarts.
Data Preparation
To configure the application, you need the following data:
l The script name is init.

l The returning message is OK after the sending succeeds.
Procedure
Step 1 # Define the Modem script.
[HUAWEI] script-string init "" AT OK AT&B1&C1&D2&S0=1 OK AT&W OK
Step 2 # Run the Modem script.

[HUAWEI] user-interface tty 1
[HUAWEI-ui-tty1] modem
[HUAWEI-ui-tty1] script trigger init init
----End
Configuration Files
#
sysname Router
#
script-string init "" AT OK AT&B1&C1&D2&S0=1 OK AT&W OK
#
user-interface tty 1
modem
script trigger init init
#
return
7.4.4 Example for Dialing by the Script

This example shows how to configure the modem script so that you can direct dial up on the
router.
Configure the Modem script and dial directly.
After the script is defined, you can dial up directly.
Data Preparation
To configure this application, you need the following data:

l The called number is 8810058.

l The dialer ID is 1.
Procedure
Step 1 # Assume that the Modem is connected with the interface tty1, execute the corresponding script
[Router] script-string dial "" AT OK ATDT8810058 CONNEC
[Router] quit
<Router> start-script dial 1
----End
Configuration Files
#
sysname Router
#
script-string dial "" AT OK ATDT8810058 CONNECT
#
return

Configuration Guide - WAN Access 8 ATM Configuration
8 ATM Configuration
About This Chapter
The Asynchronous Transfer Mode (ATM) is a cell transmission standard defined by the
International Telecommunication Union - Telecommunication Standardization Sector (ITU-T).
ATM organizes digital data into 53-byte cells and then transmits, multiplexes, or switches the
cells. ATM transmits cells in fixed length (53 bytes), provides connection-oriented services, and
simplifies the transmission process.
8.1 ATM Overview

This section describes the ATM protocol, ATM cell encapsulation, and ATM applications in
detail.
8.2 Configuring Parameters for an ATM OC-3/STM-1 Interface or an ATM OC-12/STM-4
Interface
This section describes how to configure parameters for an ATM OC-3/STM-1 or an ATM
OC-12/STM-4 interface. Detailed operations include configuring the clock mode, frame format,
and the scramble function for an ATM OC-3/STM-1 or an ATM OC-12/STM-4 interface.
8.3 Configuring an ATM PVC Group
You can configure a PVC group to allow PVCs destined for the same IP address to forward data
at the same time. Configuring a PVC group fully utilizes bandwidth resources and improves
reliability of important services.
8.4 Configuring ATM Links to Transmit Different Protocol Packets
This section describes how to configure IPoA, IPoEoA, PPPoA, PPPoEoA and ATM transparent
bridging.
8.5 Configuring the Service Type and Optional Parameters of a PVC
If PVC/PVP traffic planning is required, you can configure the service type and overload
bandwidth for PVCs/PVPs.
8.6 Configuring ATM OAM
To detect and locate faults on ATM links, you can configure ATM OAM.
8.7 Maintaining ATM Configuration
This section describes how to maintain ATM. Detailed operations include enabling the self-loop
function to detect whether an interface runs normally and clearing statistics on an ATM interface.


This section provides several examples for configuring ATM. These configuration examples

8.1 ATM Overview

This section describes the ATM protocol, ATM cell encapsulation, and ATM applications in
detail.
8.1.1 Introduction
ATM was specified as the transmission and switching mode for the Broadband Integrated
Services Digital Network (B-ISDN) by the ITU-T in June 1992. Due to its high flexibility and
support for multi-media services, ATM is a key technique for broadband communications.
ATM organizes digital data into 53-byte cells and then transmits, multiplexes, or switches the
cells. An ATM cell consists of 53 bytes. The first 5 bytes is the cell header that contains routing
and priority information. The remaining 48 bytes are payloads.
ATM is connection-oriented. Each VC is identified by a Virtual Path Identifier (VPI) and a

Virtual Channel Identifier (VCI). One pair of VPI/VCI values is useful only on a link segment
between ATM nodes. If a connection is broken, the relevant VPI/VCI values are released.
ITU-T B-ISDN I.610 defines the Operation, Administration and Maintenance (OAM) functions
on ATM networks. The OAM functions are divided into five levels: F1 (regenerator section
level), F2 (digital section level), F3 (transmission path level), F4 (virtual path level), and F5
(virtual channel level). Two types of operating flows, F4 and F5, are defined for the ATM layer.
l F4 flows are OAM cell flows in Virtual Path Connect (VPC), providing VP-level operation
management and maintenance.
l F5 flows are OAM cell flows in Virtual Channel Connect (VCC), providing VC-level
operation management and maintenance.
After OAM is enabled for F4 and F5 flows, specific OAM cells are inserted into user cell flows.
OAM and user cells are transmitted along the same physical channels and share bandwidth.
F4 and F5 flows support four types of OAM cells, namely, fault management, performance
management, activation-deactivation, and system management.
8.1.2 Features of ATM Supported by the NE80E/40E

The NE80E/40E supports various ATM features, such as PVC, traffic shaping, and OAM, and
therefore is capable of transmitting ATM services.
NE80E/40E supports the ATM interface that carries ATM services over SONET/SDH.
These ATM interfaces supported by the NE80E/40E have the following features:
l Permanent Virtual Circuit (PVC)

l Traffic shaping based on VP/VC
l User-to-Network Interface (UNI) signaling
l RFC1483: Multiprotocol Encapsulation over ATM Adaptation Layer 5
l RFC1577: Classical IP and ARP over ATM
l F5 End to End Loopback OAM

l AAL5 (ATM Adaptation Layer 5)

l Non-real Time Variable Bit Rate (nrt_VBR)
l Unspecified Bit Rate (UBR)
l Real Time Variable Bit Rate (rt_VBR)
l Constant Bit Rate(CBR)
The ATM interface supports PVCs and two applications: IPoA and IPoEoA.
The NE80E/40E supports the transparent transmission of ATM cells. For details, refer to the
chapter "PWE3 Configuration" in the HUAWEI NetEngine80E/40E Router Configuration
Guide - VPN. ATM has its QoS mechanism. For details, refer to the chapter "ATM QoS
Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - QoS.
NE80E/40E supports the fault management function of OAM.
8.2 Configuring Parameters for an ATM OC-3/STM-1

Interface or an ATM OC-12/STM-4 Interface
This section describes how to configure parameters for an ATM OC-3/STM-1 or an ATM
OC-12/STM-4 interface. Detailed operations include configuring the clock mode, frame format,
and the scramble function for an ATM OC-3/STM-1 or an ATM OC-12/STM-4 interface.

Before configuring parameters for ATM interfaces, familiarize yourself with the usage scenario,
Usage Scenario
In order to make the parameters of the ATM interface consistent with a physical network,
configure the interface parameters to match the actual ATM network.
The parameters of the ATM interface include the clock mode, frame format, scramble function,
loopback mode, and interval of flow statistics. All these parameters have default configurations.
However, 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 are configured 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 by the
sub interface, it needs to be configured independently on the sub interface.
When using an ATM interface to encapsulate the upper layer protocol, configure its attributes.
Before configuring an ATM interface, power on and start the router normally.
Data Preparation
To configure an ATM interface, you need the following data.

No. Data
1 Number of the ATM interface
2 The VPI Range on an NNI ATM Interface
8.2.2 Configuring the Clock Mode

ATM interfaces playing different roles need to be configured with different clock modes.
Context
NOTE
According to different functions, ATM devices and interfaces can be divided into Data Terminal Equipment
(DTE) and Data Circuit-terminating Equipment (DCE).
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface atm interface-number
The ATM interface view is displayed.
Step 3 Run:
The clock mode is configured.
By default, the clock mode of ATM OC-3/STM-1 is master.
l Master mode: The interface uses the internal clock signals.

l Slave mode: The interface uses the line clock signals.
When the ATM interface is used as a DTE device, use the slave clock mode. When the ATM
interface 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 Wavelength
Division Multiplexing (WDM) devices, one port should be configured to use the master clock
mode and the other the slave clock mode.
When the router is connected to the SDH/SONET device, use the slave clock mode.
----End

8.2.3 Configuring the Frame Format

ATM interfaces complying with different standards need to be configured with different frame
formats.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
The frame format is configured.
An ATM interface uses the SDH frame format when the optical interface is STM-1. An ATM
interface uses the SONET frame format when the interface is OC-3. By default, the SDH frame
format is used.
----End

You can configure different overhead bytes for interfaces to implement monitoring at different
levels.
Context
The SONET/SDH provides various overhead bytes to provide different levels of monitoring
functions.
The signal label byte C2 belongs to the Higher-Order Path Overhead byte and is used to indicate
the multiplexing structure of the Virtual Container (VC) and the feature of the information
payload.
The regenerator trace byte J0 belongs to the Section Overhead and is used to test the continuity
of the connection between the two interfaces on the section layer.
The path trace byte J1 belongs to the Higher-Order VC-N path trace byte and is used to detect
whether the two interfaces are in the continuous connection status.

Procedure
Step 1 Run:
system-view
Step 2 Run:

l Run:
value | peer }
The regenerator section trace byte J0 is configured.

l Run:
value | peer }
The regenerator section trace byte J1 is configured.

l Run:
flag c2 c2-value
The signal label byte C2 is configured.
The C2, J0, and J1 bytes on the receiving and sending ends should be consistent. Otherwise, an
alarm is generated.
For the ATM interface, by default, the value of C2 is 19 (13 in hex). The default value of J0 and
J1 is "NetEngine".
----End
8.2.5 Configuring the MTU

Configuring a proper Maximum Transmission Unit (MTU) for an ATM interface improves the
disassembly and assembly efficiency of IP packets.
Context
The MTU of the ATM interface is used for the assembly and fragmentation of IP packet in
receiving and sending packets.
NOTICE
After changing the interface MTU using the mtu command, restart the interface to validate the
configuration by running the shutdown and undo shutdown commands consecutively.

Procedure
Step 1 Run:
system-view
Step 2 Run:
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.
Step 5 Run:
undo shutdown
The ATM interface is enabled.
After changing the interface MTU using the mtu command, restart the interface to validate the
change.
----End
8.2.6 Configuring the Scrambling

Configuring the scrambling function effectively prevents consecutive 0s or 1s in ATM cells.
Context
The 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:
system-view
Step 2 Run:

Step 3 Run:
scramble
The scrambling is enabled.
By default, the scrambling is enabled. It is valid only for payloads and does not influence the
cell header.
----End
8.2.7 Configuring the Interval of Flow Statistics

Configure an interval at which traffic statistics are collected on an ATM interface or on an ATM
sub-interface. Note that the interval must be a multiple of 10.
Context
NOTE
The NE80E/40E supports the flow and rate statistics based on the ATM interface and sub-interface. Before
configuring the interval of rate statistics, configure the PVC for the interface and the sub-interface, so that
the configured statistics interval can be applied to the PVC.
Procedure
Step 1 Run:
system-view

l To enter the ATM interface view, run:
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
8.2.8 (Optional)Configuring the VPI Range on an NNI ATM

Interface
The VPI range can be configured manually on an NNI ATM interface to ensure that a Huawei
device and a non-Huawei device that are connected through NNI ATM interfaces can
intercommunicate.

Context
By default, the VPI on an NNI ATM interface of the NE80E/40E can be configured to range
from 0 to 1023, which is different from the VPI range supported by a device of another vendor.
When a Huawei device is connected to a non-Huawei device through NNI ATM interfaces, you
must ensure that the VPIs on the two connected devices are the same. In this case, you can run
the atm vpi-config command to configure the VPI range on an NNI ATM interface.
Procedure
Step 1 Run:
system-view
Step 2 Run:
atm vpi-config slot slot-id card card-id { port0 vpi_min_value to vpi_max_value |
port1 vpi_min_value to vpi_max_value | port2 vpi_min_value to vpi_max_value |
port3 vpi_min_value to vpi_max_value }*
The VPI range is configured on an NNI ATM interface.
NOTICE
The VPI ranges configured on NNI ATM interfaces on an ATM board can be the same, but the
sum of the numbers of available VPIs cannot be greater than 4096.
The atm vpi-config command can be used to configure the VPI range for certain or all ATM
interfaces on an ATM board. When the VPI range is configured for certain ATM interfaces, the
other ATM interfaces become unavailable.
----End
8.2.9 (Optional) Configuring an ATM-Trunk Interface

An ATM-Trunk interface is created and its member interfaces are configured.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface atm-trunk { trunk-id | trunk-id.subnumber [ p2mp | p2p ] }
An ATM-Trunk sub-interface is created and the sub-interface view is displayed.
Step 3 Run:
pvc vpi/vci
A PVC or a range of PVCs are added to the ATM-Trunk sub-interface.

Step 4 Run:
encapsulation aal5-encap
The encapsulation type of the ATM-Trunk sub-interface is set to ATM AAL5.
Step 5 Run the following command as required:

l To configure PPPoEoA mapping on PVCs, run:
map bridge virtual-ethernet interface-number
l To configure PPPoA mapping on PVCs, run:

map ppp virtual-template vt-number
NOTE
Before you add an ATM interface to an ATM-Trunk interface, configure APS on the ATM interface. This
can ensure that the services configured on the CPOS-Trunk interface run normally.
A physical interface added to an ATM-Trunk interface is affected by the ATM-Trunk interface:
l If the shutdown command is run on the ATM-Trunk interface before or after the physical interface is
added, the physical status of the ATM-Trunk interface becomes Administratively DOWN.
Accordingly, the configuration file shows that the physical interface is shutdown and its physical status
is Administratively DOWN.
l If the undo shutdown command is run on the ATM-Trunk interface after the physical interface is
added, the configuration file shows that the physical interface is undo shutdown.
----End
8.2.10 Configuring the ATM Module to Report Alarms to the NMS

After configuring the ATM module to report alarms to the NMS, you can monitor the alarm
status of the ATM module on the NMS interface.
Context
After the ATM alarm function is enabled, if an alarm is generated, a trap message containing
the alarm information will be reported to the NMS. By viewing the alarm information, you can
learn the status of your device on the NMS interface.
Procedure
Step 1 Run:
system-view
Step 2 Run:
snmp-agent trap enable feature-name atm trap-name { hwatmpwlospktexcalarm |
hwatmpwlospktexcalarmresume | hwatmpwmisorderpktexcalarm |
hwatmpwmisorderpktexcalarmresume | hwatmpwunknowncellexcalarm |
hwatmpwunknowncellexcalarmresume | hwchcsalarm | hwchcsalarmresume | hwlcdalarm |
hwlcdalarmresume | hwocdalarm | hwocdalarmresume | hwuhcsalarm |
hwuhcsalarmresume }
The specified alarm functions are enabled on the ATM module.
By default, all alarm functions of the ATM module are enabled. When your device generates an
alarm, it automatically reports a trap message containing the alarm information to the NMS.

Step 3 Run:
Enter the ATM interface view.

Step 4 Run:
trap-threshold { atmpw-lospkt-exc | atmpw-misorderpkt-exc | atmpw-unknowncell-
exc } trigger-threshold trigger-threshold-value resume-threshold resume-threshold-
value
The thresholds for triggering and clearing the performance threshold-crossing alarm for ATM
transparent cell transport are configured.
By default, the threshold for triggering the alarm is 100 and the threshold for clearing the alarm
is 1.
----End

After parameters are configured on an ATM interface, you can check its clock mode, frame
format, and MTU.
Procedure
l Run the display interface atm [ interface-number [.subinterface-number] ] [ | { begin |
exclude | include } regular-expression ] command to check the configuration and status
of the ATM interface.
command to check the brief information about the ATM interface.
l Run the display atm vpi-config slot slot-id card card-id command to check the brief
information about the ATM interface.
----End
Example
Run the display interface atm command. If you can view the configuration information about
the ATM interface, including the enabled scramble, frame format, clock mode and the statistics
period, it means that the configuration is successful.
<HUAWEI> display interface atm 1/0/0
Atm1/0/0 current state : UP
Description : Atm1/0/0 Interface
Route Port, The Maximum Transmit Unit is 1500
AAL enabled: AAL5, Maximum VCs: 2048
VCs on main-interface: 1 (Total VCs: 1)
VPs on main-interface: 0 (Total VPs: 1 )
The Vendor Name is FINISAR CORP. , The Vendor PN is FTRJ1321P1BTL
UBR: 1, CBR: 0, VBR: 0, USED BandWidth: 0Kbps
VPI Max: 255, VCI Max: 2047

Flag: J0 "NetEngine "

Flag: C2 19(0x13)
SDH alarm:
section layer: OOF LOF LOS
line layer: AIS
path layer: AIS RDI
SDH error:
section layer: B1: 24
line layer: B2: 0 M1: 0
path layer: B3: 0 G1: 0
Send good cell: 0 cells
Send idle cell: 25099462530 cells
Receive idle cell: 0 cells
Receive corrected cell: 0
Receive uncorrected cell: 97
Dropped receive cell: 0 cells
Last dropped receive cell connection: 0/0
Last 30 seconds input rate: 0 bits/sec, 0 Packets/sec
Last 30 seconds output rate: 0 bits/sec, 0 Packets/sec
Input: 0 Bytes, 0 Packets
Output: 0 Bytes, 0 Packets
Run the display interface brief [ | { begin | include | exclude } regular-expression ] command.
If you can view the physical status of the ATM interface, link protocol status, bandwidth
utilization, and the number of the error packets, it means that the configuration is successful.
For example:
<HUAWEI> display interface brief | include 1/0/
PHY: Physical
^down: standby
(l): loopback
(s): spoofing
(b): BFD down
(e): EFM down
outErrors
Atm1/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
8.3 Configuring an ATM PVC Group

You can configure a PVC group to allow PVCs destined for the same IP address to forward data
at the same time. Configuring a PVC group fully utilizes bandwidth resources and improves
reliability of important services.

Before creating a PVC group and configuring PVC service mapping, familiarize yourself with
configuration.

Usage Scenario
In an IP over ATM (IPoA) environment, PVC service mapping allows different PVCs to transmit
IP packets with different priorities between two nodes.
You configure a PVC group so that, when IP packets are transmitted over an ATM network, IP
packets with different priorities are transmitted between two nodes along different PVCs.
Before creating a PVC group and configuring PVC service mapping, complete the following
tasks:
l Configure physical attributes for ATM interfaces on the router.

l Configure IP addresses and masks for ATM interfaces and sub-interfaces.
l Create PVCs and configuring their application mode as IPoA.
l (Optional) Create an ATM service type template.
Data Preparation
To create a PVC group and configure PVC service mapping, you need the following data.
No. Data
1 Number of an ATM interface or a sub-interface
2 IP address and mask of the ATM interface or sub-interface
3 PVC name (optional) and VPI/VCI values for the PVC group
4 Name (optional) and VPI/VCI values for each PVC in the PVC group
5 Lowest and highest priorities of IP packets transmitted along PVCs in the PVC group
6 (Optional) Name of a service type template, which is to be referenced by PVCs in

the PVC group
7 (Optional) Queue scheduling parameters for PVCs in the PVC group
8.3.2 Creating a PVC Group

This section describes how to create a PVC group.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface atm interface-number[.subinterface ]

The ATM interface or sub-interface view is displayed.
Step 3 Run:
pvc { { pvc-name [ vpi/vci ] | vpi/vci } | { start-vpi/start-vci end-vpi/end-vci } }
A PVC is created and the PVC view is displayed.
NOTE
The virtual path identifier (VPI)/virtual channel identifier (VCI) values configured for the primary and
secondary ATM PVCs in an ATM PVC group must be the same on the local and remote ends. The IP
precedence value configured for each ATM PVC must also be the same on the local and remote ends. If
ATM PVCs on the local and remote ends are configured with different IP precedence values, services
provided by the ATM PVC group will be interrupted.
Step 4 Run:
quit
Step 5 Run:
pvc-group { pvc-name [ vpi/vci ] | vpi/vci }
A PVC group is created and the PVC group view is displayed.
The PVC name or VPI/VCI values must be available for creating a PVC group or entering the
view of a PVC group.
----End
8.3.3 Mapping IP Precedence Values to Separate ATM PVCs in an

ATM PVC Group
PVCs in a group can be configured to transmit IP packets with different precedence values.
PVCs transmitting IP packets with high precedence values preferentially use bandwidth
resources.
Prerequisites
PVCs with specified precedence values have been configured.
Context
After IP precedence values are mapped to PVCs, IP packets with different precedence values
are transmitted along different PVCs. In this manner, IP packets with different precedence values
can be transmitted separately.
Procedure
Step 1 Run:
system-view
Step 2 Run:

Step 3 Run:
The PVC group view is displayed.
IP precedence values can only be mapped to PVCs transmitting IPoA packets.
Step 4 Run:
ip precedence { pvc-name [ vpi/vci ] | vpi/vci } { min [ max ] | default }
Precedence values are set for the IP packets transmitted between PVCs in the PVC group.
NOTE
PVC service mapping does not change the precedence values of IP packets transmitted along PVCs in a
PVC group. To change precedence values for IP packets, configure certain tags carried in IP packets. For
details, see the HUAWEI NetEngine80E/40E Router Configuration Guide - QoS.
----End
8.3.4 Configuring QoS Policies for ATM PVCs in an ATM PVC

Group
If you want services to have different bandwidths and scheduling priorities, configure different
quality of service (QoS) policies for asynchronous transfer mode (ATM) permanent virtual
circuits (PVCs) in an ATM PVC group.
Prerequisites
The mapping between IP precedence values and ATM PVCs has been configured.
Context
You can configure different QoS policies for the primary and secondary ATM PVCs in an ATM
PVC group separately. The configuration difference is in the views:
l To apply a QoS policy to the primary ATM PVC in an ATM PVC group, from the ATM
interface or sub-interface view enter the ATM PVC view of the primary ATM PVC; then
configure a service type template and queue scheduling parameters.
l To apply a QoS policy to a secondary ATM PVC in an ATM PVC group, from the PVC
group view enter the ATM PVC group PVC view of the secondary ATM PVC; then
configure a service type template and queue scheduling parameters.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface atm interface-number [.subinterface ]

Step 3 Run:
pvc { pvc-name [ vpi/vci ] | vpi/vci }
The ATM PVC view is displayed.
To apply a QoS policy to the primary ATM PVC in an ATM PVC group, configure the
service or pvc-queue command in the ATM PVC view of the primary ATM PVC.

The PVC group view is displayed.
NOTE
The pvc-group { pvc-name [ vpi/vci ] | vpi/vci } command cannot be configured on the flexible plug-in
cards (FPICs) 4port OC-3c/STM-1c ATM-SFP, the NE80E/40E-X1 and X2 models or the flexible plug–
in cards (FPICs) 8-port OC-3c/STM-1c ATM-SFP.

pvc { pvc-name [ vpi/vci ] | vpi/vci }
The ATM PVC group PVC view is displayed.
To apply a QoS policy to a secondary ATM PVC in an ATM PVC group, configure the
service or pvc-queue command in the ATM PVC group PVC view of the secondary ATM PVC.
Step 6 Run:
service { output | input } service-name
A service type template is configured for the specified ATM PVC.
Step 7 Run:
pvc-queue cos-value { pq | wfq weight weight } outbound
Queue scheduling parameters are set for the specified ATM PVC.
NOTE
The pvc-queue cos-value { pq | wfq weight weight } outbound command cannot be configured on the
flexible plug–in cards (FPICs) 8-port OC-3c/STM-1c ATM-SFP or the NE80E/40E-X1 and X2 models.
l Priority queuing (PQ) scheduling can be configured for only one of the eight queues on an ATM PVC.
l If PQ or weighted fair queuing (WFQ) scheduling is configured for a queue on an ATM PVC, the other
queues on the ATM PVC use WFQ scheduling by default, with the weight 20.
l Queue scheduling parameters can be set only for downstream queues on an ATM PVC.
----End

After a PVC group is created and PVC service mapping is configured, you can view information
about the PVC group and PVCs in the group.
Prerequisites
A PVC group and PVC service mapping have been configured.

Procedure
l Run the display atm pvc-info [ interface { atm | ima-group | serial } interface-number
[ pvc { pvc-name [ vpi/vci ] | vpi/vci } ] ] command to check information about PVCs.
l Run the display atm pvc-group [ interface { atm | serial } interface-number [ pvc { pvc-
name [ vpi/vci ] | vpi/vci } ] ] command to check information about a PVC group.
----End
Example
Run the display atm pvc-info command. The command output shows PVC status and ATM
interface status.
<HUAWEI> display atm pvc-info
VPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE
--------|-----|----------------|--------|-----|-----|-----------------------
0/40 |UP |1 |1 |SNAP |None |Atm8/0/0.1 (UP)
Run the display atm pvc-group command. The command output shows information about a
PVC group, including the VPI/VCI values, PVC name, and group status.
<HUAWEI> display atm pvc-group
PVC-GROUP-NAME VPI/VCI STATE ENCAP PROTOCOL INTERFACE
aaa 3/35 Down SNAP None Atm1/0/0(DOWN)
8.4 Configuring ATM Links to Transmit Different Protocol

Packets
This section describes how to configure IPoA, IPoEoA, PPPoA, PPPoEoA and ATM transparent
bridging.

Before configuring ATM links to transmit different protocol packets, familiarize yourself with
configuration.
Usage Scenario
Currently, ATM links can transmit packets of the following protocols:
l IPoA
By configuring IPoA mapping on PVCs, you can enable a device to encapsulate IP packets
into ATM cells and transmit them over ATM networks. This allows AAL5 to transmit IP
protocol packets.
l IPoEoA
By configuring IPoEoA mapping on PVCs, you can enable PVCs associated with the same
Virtual Ethernet (VE) interface to communicate at Layer 2. This allows AAL5 to transmit
IPoE protocol packets.
l PPPoA

By configuring PPPoA mapping on PVCs, you can enable a device to encapsulate PPP
packets into ATM cells and transmit them over ATM networks. This allows AAL5 to
transmit PPP protocol packets.
l PPPoEoA
By configuring PPPoEoA mapping on PVCs, you can enable a device to encapsulate PPPoE
packets into ATM cells and transmit them over ATM networks. This allows AAL5 to
transmit PPPoE protocol packets.
Before configuring ATM links to transmit different protocol packets, complete the following
tasks:
l Power on the router and ensure that the router detects no error during self-check.
l Create PVCs.
Data Preparation
To configure ATM links to transmit different protocol packets, you need the following data.
No. Data
1 Number of an ATM interface or a sub-interface
3 Name and VPI/VCI values of each PVC
4 AAL5 encapsulation type
5 Number of a VE interface
6 Virtual template number
7 IP address and mask of the virtual template
8.4.2 Configuring IPoA Mapping on PVCs

IPoA mapping on PVCs enables a device to encapsulate IP packets into ATM cells and transmit
them over ATM networks.
Prerequisites
Before creating PVCs and configuring IPoA mapping on PVCs, complete the following
configuration:
l Configuring physical attributes for ATM interfaces on the router
Context
Configure IPoA mapping on PVCs to allow AAL5 to transmit IP protocol packets.

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:

If start-vpi/start-vci end-vpi/end-vci is specified, PVCs are created in batches, and the views are
displayed.
NOTE
l The VCI values 3 and 4 are reserved.

l The VPI and VCI values cannot both be 0s.
Step 4 Run:
encapsulation aal5snap
The AAL5 encapsulation type is specified for the PVC.

The AAL5 encapsulation type can be aal5snap, aal5mux, or aal5nlpid. The default value is
aal5snap.
If aal5mux or aal5nlpid is configured as the AAL5 encapsulation type, InARP cannot be
enabled. If InARP has been enabled, disable InARP before setting the AAL5 encapsulation type
to aal5mux or aal5nlpid for PVCs.
Step 5 Run:
map ip { ip-address | inarp [ minutes ] } [ broadcast ]
IPoA mapping is configured.
NOTE
One IP address cannot be mapped to multiple ATM interfaces or sub-interfaces on the same device as this
interrupts traffic forwarding.
If the PVC needs to transmit broadcast IP packets, broadcast must be configured.

Only one PVC of an ATM interface or sub-interface can be enabled with InARP.
NOTICE
The IP address specified in this command must be the IP address of the peer interface. Otherwise,
data cannot be correctly forwarded.
----End

8.4.3 Configuring IPoEoA Mapping on PVCs

IPoEoA mapping on PVCs allows AAL5 to transmit IPoE protocol packets.
Prerequisites
Before creating PVCs and configuring IPoEoA mapping on PVCs, complete the following
configurations:
l Configure physical attributes for ATM interfaces on the router.

l Create a VE interface and configure an IP address and a mask for the interface.
Context
IPoEoA mapping on PVCs enables PVCs associated with the same VE interface to communicate
at Layer 2.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface virtual-ethernet interface-number
A VE interface is created and the VE interface view is displayed.
In a distributed system, the slot ID of the VE interface is the same as that of the ATM interface.
Step 3 Run:
quit
Step 4 Run:
Step 5 Run:
If start-vpi/start-vci end-vpi/end-vci is specified, PVCs are created in batches, and the views of
these PVCs are displayed.
Step 6 Run:
The AAL5 encapsulation type can be aal5snap, aal5muxunstandard, or aal5mux. The default
value is aal5snap.

Step 7 Run:
IPoEoA mapping is configured.
----End
8.4.4 Configuring PPPoA Mapping on PVCs

PPPoA mapping on PVCs enables a device to encapsulate PPP packets into ATM cells and
transmit them over ATM networks.
Context
Configuring PPPoA mapping on PVCs allows AAL5 to transmit PPP protocol packets.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface virtual-template vt-number
A VT interface is created and the VT interface view is displayed.
Step 3 Run:
quit
Step 4 Run:
Step 5 Run:
Step 6 Run:
The AAL5 encapsulation type can be aal5snap, aal5mux, aal5nlpidietf, aal5nlpid or

aal5muxunstandard. The default value is aal5snap.
Step 7 Run either of the following commands as required:

l To configure permanent-online PPPoA, run the map ppp virtual-template vt-number
command.

l To configure on-demand PPPoA, run the map ppp virtual-template vt-number server or
map ppp dialer dialer-number command.
Step 8 Run:
map ppp virtual-template vt-number
PPPoA mapping is configured.
----End
8.4.5 Configuring PPPoEoA Mapping on PVCs

PPPoEoA mapping on PVCs enables a device to encapsulate PPPoE packets into ATM cells
and transmit them over ATM networks.
Context
Configuring PPPoEoA mapping on PVCs allows AAL5 to transmit PPPoE protocol packets.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface virtual-template vt-number
A virtual template interface is created and the virtual template interface view is displayed.
Step 3 Run:
ip address ip-address { mask | mask-length }
An IP address is assigned to the virtual template interface.
Step 4 Run:
quit
Step 5 Run:
Step 6 Run:
pppoe-server bind virtual-template number
The PPPoE server is bound to the virtual template.
Step 7 Run:
quit
Step 8 Run:


Step 9 Run:

Step 10 Run:

The AAL5 encapsulation type can be aal5snap, aal5muxunstandard, or aal5mux. The default
value is aal5snap.
The slot ID of the VE interface must be the same as that of the ATM interface.
Step 11 Run:
PPPoEoA mapping is configured.
----End

After configuring ATM links to transmit different protocol packets, you can view configurations
and the status of ATM interfaces or sub-interfaces, information about PVCs and PVC mapping,
and the status and statistics of VE interfaces.
Prerequisites
ATM links have been configured to transmit different protocol packets.
Procedure
l Run the display interface atm [ interface-number ] command to check configurations and
status of ATM interfaces or sub-interfaces.
l Run the display atm pvc-info [ interface { atm | ima-group | serial } interface-number
[ pvc { pvc-name [ vpi/vci ] | vpi/vci } ] ] command to check information about PVCs.
l Run the display atm map-info [ interface { atm | serial } interface-type interface-number
[.subinterface ] [ pvc { pvc-name | vpi/vci }* ] ] command to check information about PVC
mapping.
l Run the display interface virtual-ethernet [ interface-number ] command to check status
and statistics of VE interfaces.
----End
Example

Description: Atm3/1/0 Interface

Physical layer is ATM over OC-3
Scramble enabled, frame-format SONET, clock master, loopback not set
SONET alarm:
section layer: none
line layer: none
path layer: none
C2(Rx): 0x13 C2(Tx): 0x13
SONET error:
section layer: B1 0
line layer: B2 0 M1 0
path layer: B3 0 G1 0
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 0
0 errors, 0 CRC, 0 giants,
0 pads, 0 aborts,0 overflows
Output:0 packets, 0 bytes
0 errors, 0 underflows, 0 overflows
Run the display atm pvc-info command. The command output shows PVC status and ATM
interface status.
VPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROTOCOL |INTERFACE
--------|-----|----------------|--------|-----|-----|-----------------------
100/1 |DOWN | |0 |SNAP |None |Atm1/1/0.1 (DOWN)
1/1 |DOWN | |1 |SNAP |None |Atm1/1/1.1 (DOWN)
--------|-----|----------------|--------|-----|-----|-----------------------
1/100 |DOWN | |65536 |None |None |Ima-group13/0/2.1 (DOWN)
0/1 |DOWN | |65537 |None |None |Serial13/0/3:4.1 (DOWN)
After PVC mapping is successfully configured, the VE interface goes Up.

<HUAWEI> display interface virtual-ethernet 1/0/0
Virtual-Ethernet1/0/0 current state : UP
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc7a-9e15
Carrier Layer: 1 PVC total, 1 map up, 0 map down
263 packets input, 22134 bytes, 0 drops
339 packets output, 29534 bytes, 0 drops
Input bandwidth utilization : 5.00%
Output bandwidth utilization : 6.00%

8.5 Configuring the Service Type and Optional Parameters

of a PVC
If PVC/PVP traffic planning is required, you can configure the service type and overload
bandwidth for PVCs/PVPs.

Before configuring the service type and optional parameters for a PVC, familiarize yourself with
the usage scenario, complete the pre-configuration tasks, and obtain the required data.
Usage Scenario
In practical networking, to manage the PVC traffic, you need to configure the service type and
the related parameters of a PVC.
Before configuring the service types and optional parameters of a PVC, complete the following
tasks:
l Configure physical attributes for the ATM interface.

l Configure an IP address and mask for the ATM interface or sub-interface
.
l Create a PVC and configuring application modes
.
Data Preparation
To 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
3 PVC name, the network VPI and VCI
4 cbr: Peak rate of outputting ATM cells, variation range of cell delays
5 nrt-vbr: Peak rate of outputting ATM cells, maintainable rate, variation range of cell
delays and the maximum burst size
6 rt-vbr: Peak rate of outputting ATM cells, maintainable rate, variation range of cell
delays and the maximum burst size
7 (Optional) Overload bandwidth value of the ATM interface

8.5.2 Configuring the Service Type of a PVC

PVC services are classified into the following types: CBR, VBR-rt, VBR-nrt, UBR, and UBR
plus.
Context
When configuring the PVC service type, you need to first create a service type template in the
system view and apply it to the concrete PVC.
Procedure
Step 1 Run:
system-view

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 [ ubr-cdvt-
value ] | ubr-plus output-pcr output-mcr cdvt-value }
The service type template and rate parameters are created.
By default, the service type of PVC 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 ]
The ATM main interface or ATM subinterface view is displayed.

Step 4 Run:
atm cell transfer
Configure the ATM cell transfer mode.
NOTE
Perform this step only on the flexible plug-in cards (FPICs) 4port OC-3c/STM-1c ATM-SFP, the NE80E/
40E-X1 and X2 models or the flexible plug–in cards (FPICs) 8-port OC-3c/STM-1c ATM-SFP. These
flexible cards do not support AAL5 services, so you need to run the atm cell transfer command before
you configure a PVC.
Step 5 Run:
pvc [ pvc-name ] vpi/vci
The PVC is created and the PVC view is displayed.

Step 6 Run:
service output service-name
The PVC service type is set.
----End

8.5.3 Configuring the Service Type of a PVP

PVP services are classified into the following types: CBR, VBR-rt, VBR-nrt, UBR, and UBR
plus.
Context
When configuring the PVP service type, you need to first create a service type template in the
system view and apply it to the concrete PVP.
Procedure
Step 1 Run:
system-view
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 [ ubr-cdvt-
value ] | ubr-plus output-pcr output-mcr 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:
atm cell transfer
Configure the ATM cell transfer mode.
NOTE
Perform this step only on the flexible plug-in cards (FPICs) 4port OC-3c/STM-1c ATM-SFP, the NE80E/
40E-X1 and X2 models or the flexible plug–in cards (FPICs) 8-port OC-3c/STM-1c ATM-SFP. These
flexible cards do not support AAL5 services, so you need to run the atm cell transfer command before
you configure a PVP.
Step 5 Run:
pvp vpi
The PVP is created and the PVP view is displayed.
The PVP can only be configured in the ATM sub interface view.
Step 6 Run:
service { output | input } service-name

The service type of PVP is set.
----End
8.5.4 (Optional) Configure the Overload Bandwidth Value of an

ATM Interface
The overhead bandwidth of an ATM interface refers to the sum of committed bandwidth of all
PVCs and PVPs on the interface.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
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 the
PVCs and PVPs of all services on the ATM interface.
By default, the overload bandwidth of the ATM interface is 0 kbps.
----End

After the service type and optional parameters of a PVC are configured, you can check the
configuration of the service type template and the statistics.
Procedure
l 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 the
service 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.

NOTE
Running the display interface atm command displays the statistics of all the packets discarded on
an interface. Running the display atm pvc statistics command displays only the statistics of the
packets discarded on the PVC or PVP due to congestion. Therefore, run the commands as required.
----End
Example
Run the display interface atm command. If you can view information about the configuration
and state of the ATM interface, it means that the configuration is successful.
Description:Atm1/0/0 Interface
Route Port, The Maximum Transmit Unit is is 1500
VPs on main-interface: 0 (Total VPs: 0)
Flag: C2 19(0x13)
SDH alarm:
section layer: none
line layer: none
path layer: none
SDH error:
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 type
template, it means that the configuration is successful.
<HUAWEI> display atm service
Atm Service Config:
Service Name: aa
State: VALID
Index: 0
ServiceType: CBR
PCR: 120
SCR: 0

MBS: 0
CDVT: 3
Traffic Type: Shaper
Run the display atm pvc statistics command. If you can view the statistics of the packets
discarded on the PVC due to congestion, it means that the configuration is successful.
<HUAWEI> dispaly atm pvc statistics interface atm 1/0/0
pvc 10/0:
input drop pkts : 0, input drop bytes : 0, input drop rate 0 bits/sec, 0 packets/
sec
ouput drop pkts : 0, ouput drop bytes : 0, output drop rate 0 bits/sec, 0 packets/
sec
pvc 10/20:
input drop pkts : 0, input drop bytes : 0, input drop rate 0 bits/sec, 0 packets/
sec
ouput drop pkts : 0, ouput drop bytes : 0, output drop rate 0 bits/sec, 0 packets/
sec
Total items : 2
8.6 Configuring ATM OAM

To detect and locate faults on ATM links, you can configure ATM OAM.

Before configuring ATM OAM, familiarize yourself with the usage scenario, complete the pre-
configuration tasks, and obtain the required data.
Usage Scenario
OAM provides various optional methods of detecting and locating the faults on an ATM link.
Choose the configuration as required.
l To detect the link status and report faults in real time without interrupting services, activate
the CC function or configure the end-to-end loopback detection function:
– The CC function detects the link status in real time by periodically transmitting CC cells
while not restricting the connection point attribute.
– The end-to-end loopback detection function detects the link status in real time by
sending loopback cells periodically and is available on only the PVP/PVC with the
connection point attribute of end-point.
Check whether the device supports CC cells or loopback cells and then choose
configurations according to the OAM connection point attribute.
The CC function and the loopback function cannot be configured on the same PVP/PVC.
l To locate and remove the link faults, configure the cell loopback.
l To debug and detect whether the ATM OAM mechanism works normally, insert OAM
cells manually.
l To response to the OAM F5 loopback cells on the peer, configure their response.
Before configuring ATM OAM, complete the following tasks:
l Configure physical attributes for the ATM interface.

l Configure an IP address and mask for the ATM interface

.
l Configure ATM PVC
.
Data Preparation
To 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
8.6.2 (Optional) Activating the CC Function

You can activate the CC function to enable a device to detect link status and report faults in real
time without service interruption.
Context
NOTE
On the NE80E/40E, only the LPUF-10 ATM FPIC supports the activation of the CC function.
Procedure
Step 1 Run:
system-view

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 }

The OAM attributes of the connection point are configured.
When the following services are configured on a PVC, the PVC attribute can be configured only
as 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 loopback
cells.
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 OAM attribute configurations
on 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 CC
function first.
l If the parameter sink or both is configured, a clear alarm will be generated when either of
the following conditions is met:
– The local end receives CC cells from the peer end.
– The local end receives data cells from the peer end.
----End
8.6.3 (Optional) Configuring OAM End-to-End Loopback

You can configure end-to-end loopback detection to enable a device to detect link status and
report faults in real time without service interruption.
Context
When configuring the function of end-to-end loopback detection in the ATM OAM view, 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 the
function of OAM end-to-end loopback detection if no faults occur on the board.

Procedure
l Implement end-to-end loopback detection in the ATM OAM view.
1. Run:
system-view

2. Run:

3. Run:
oam
The OAM interface view is displayed.

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.

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.
NOTICE
If you need to enable OAM end-to-end loopback detection on an interface that is
transmitting traffic, ensure that the OAM connection is end-point. Otherwise, traffic
on the local interface will be interrupted.
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 is configured.
By default, the number of delayed intervals for responding to the change of the PVP/
PVC status is 5.
After the function of OAM end-to-end loopback detection is enabled, when the PVP/
PVC status changes, the system does not immediately respond to avoid PVP/PVC
flapping. When the PVP/PVC remains Down or Up for consecutive specified delayed
intervals, the system responds to the change.
----End
8.6.4 (Optional) Configuring the Cell Loopback

After cell loopback is configured, the system checks loopback cells to detect and locate link
faults.

Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
oam
An OAM view is displayed.

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 are configured.

When the following services are configured on a PVC, the PVC attribute can be configured only
as 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 loopback
cells.
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 convenient fault locating and testing. The
loopback test inserts loopback cells in the VC/VP link of a certain connection point and the cells
loop back to another connection point. The system detects and locates any link faults through
the received loopback cells.
The loopback includes the following two types: segment loopback and end loopback.
l Before configuring the segment point loopback, you need to configure the end loopback point
as the segment point.
l Before configuring the end point loopback, you need to configure the end loopback point as
the end point.
l The loopback in one board fails.
----End

8.6.5 (Optional) Configuring an ATM Connectivity Test

After ATM cell relay has been configured on an ATM interface or a logical interface that runs
the ATM protocol, a connectivity test can be configured for ATM services.
Context
Before configuring a connectivity test for ATM services, you must complete the following tasks:
1. Check that the interface on which the connectivity test will be performed is Up. If the
interface is a synchronous serial interface, configure ATM on the interface.
2. Configure PVC or PVP on the interface.
3. Configure the end-point attribute for the connection point of the PVC or PVP on the end
that initiates a one-key test.
4. Run the llid command to configure a local LLID for both the local and peer ends.
Procedure
Step 1 Run:
system-view
Step 2 Run:
test connectivity interface interface-type interface-number { pvc vpi/vci | pvp
vpi } llid llid
A connectivity test is configured for ATM services.
----End
Result
Run the display connectivity-testinterface interface-type interface-number { pvc vpi/vci |
pvp vpi } command to check the results of the connectivity test on ATM services.

After ATM OAM is configured, you can check ATM OAM configurations and statistics.
Procedure
l 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

Example
Run the display atm oam statistics,display atm oam alarm-status and display atm oam
configuration commands. If you can view information about the alarm state, configuration, and
statistics of ATM OAM, it means that the configuration is successful.
<HUAWEI> display atm oam statistics atm 3/0/1 10/10
Total number of received OAM Cells : 0
Number of received AIS Cells : 0
Number of received RDI Cells : 0
Number of received CC cells : 0
Total number of sent OAM Cells : 44
Number of sent AIS Cells : 0
Number of sent RDI Cells : 44
Number of sent CC cells : 0
[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/1
Interface 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/1
Interface PVC/PVP Attribute CC func CC dir CC attr
--------- ----- --------- ------- ------ -------
Atm3/0/1 10/10 end-point disable - -
8.7 Maintaining ATM Configuration

This section describes how to maintain ATM. Detailed operations include enabling the self-loop
function to detect whether an interface runs normally and clearing statistics on an ATM interface.
8.7.1 Setting Loopback to Detect Whether an Interface Is Normal

The self-loop function is used to detect whether an interface or a link works properly.
Context
NOTICE
After you configure the self-loop (run the loopback command), the interface on a router or the
link cannot run normally. Therefore, you must check whether to set the self-loop. After the
detection is complete, run the undo loopback command to disable the self-loop.
Perform the following steps on the device to be detected:
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the interface to be detected is displayed.
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
8.7.2 Clearing the ATM Interface Statistics

You can run the reset commands to clear interface statistics before recollecting traffic statistics
on the interface.
Context
NOTICE
The statistics data cannot be restored after you clear it. Confirm the action before you use the
command.
To reset the interface statistics on the Network Management System (NMS) or that displayed
using the display interface command, run the following commands in the user view.
NOTE
For more information about the display of interface statistics on the NMS, see related NMS manuals.
Procedure
Step 1 Run the reset counters interface [ atm [ interface-number ] ] command to clear the interface
statistics displayed using the display interface command.
Step 2 Run the reset counters if-mib interface [ atm [ interface-number ] ] command to clear the
interface statistics on the NMS.
Step 3 Run the reset atm interface [ atm interface-number ] command to clear the ATM interface
statistics.
----End

This section provides several examples for configuring ATM. These configuration examples

8.8.1 Example for Configuring IPoA

This example shows how to interconnect three devices using the IPoA application in typical
ATM networking.
In Figure 8-1, Router A, Router B and Router C are connected to the ATM network. All the
PVCs on ATM interfaces of the routers employ IPoA application mode.
Figure 8-1 Networking diagram for IPoA configuration
RouterB
IP:202.38.160.2/24
RouterA
To A:0/40
ATM To C:0/42
network Interface:ATM1/0/0
IP:202.38.160.1/24 RouterC
To B:0/40
To C:0/41
Interface:ATM1/0/0
IP:202.38.160.3/24
To A:0/41
To B:0/42
Interface:ATM1/0/0
1. Create the ATM interface PVC on each router.

2. Specify the protocol to bear the IP protocol.
Data Preparation
To configure IPoA, you need the following data:
l IP addresses of the ATM interfaces on the 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

Procedure
# Enter the ATM interface view and configure an IP address for it.
[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.

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

[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] 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-info
--------|-----|--------------|--------|-----|-----|---------------------
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-info
Atm1/0/0, PVC 0/40, IP, State UP
202.38.160.2, vlink 393217
202.38.160.3, vlink 393218
Similarly, check the PVC status information and the PVC mapping information on Router B and
Router C.
# Router A can ping through Router B.

--- 202.38.160.2 ping statistics ---
0.00% packet loss
After performing the same operation on the other Router s, you should 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
Configuration Files
#
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

#
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

#
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
8.8.2 Example for Configuring the PPPoA Service

This example describes how to configure PPPoA to allow PPP packets to be transmitted along
ATM PVCs in typical networking.
As shown in Figure 8-2, two PCs use different ADSL Routers to connect to a DSLAM. The
DSLAM is connected to router C and this allows the PCs to communicate with router C on an
ATM network.
The ATM interface on router C and the DSL interfaces on ADSL Routers must be configured
with PPPoA. PAP is used to authenticate ADSL Routers.
A remote AAA server connected to router C assigns IP addresses to ADSL Routers.
Figure 8-2 Networking for PPPoA configuration
PC ADSL RouterA
VT10：10.38.160.1/24
VT11：10.38.161.1/24
DSLAM
RouterC
To ADSL RouterA:0/60
To ADSL RouterB:0/61
ATM1/0/0.1
PC ADSL RouterB

1. Create PPP users for PAP authentication.

2. Create VT interfaces for the users on router C.
3. Configure PAP authentication.
4. Create Permanent Virtual Circuits (PVCs) and configure the PVCs to carry PPP packets.
Data Preparation
l User names and passwords for PAP authentication

l Local address pool number and address range
l IP addresses of VT interfaces
l Virtual Path Identifier (VPI)/Virtual Channel Identifier (VCI) values of the PVCs
connecting router C to the DSLAM
Procedure
Step 1 Create PPP users for PAP authentication and a local IP address pool.
[RouterC] aaa
[RouterC-aaa] local-user userr1 password cipher Huawei-123
[RouterC-aaa] local-user userr2 password cipher Huawei-123
[RouterC-aaa] ip pool 1 10.38.162.1 10.38.162.100
[RouterC-aaa] quit
Step 2 Create VT interfaces. Configure PAP authentication on the interfaces. Configure IP address
allocation from an address pool to the peers.
[RouterC] interface virtual-template 10
[RouterC-Virtual-Template10] ip address 10.38.160.1 255.255.255.0
[RouterC-Virtual-Template10] ppp authentication-mode pap
[RouterC-Virtual-Template10] remote address pool 1
[RouterC-Virtual-Template10] quit
[RouterC-Virtual-Template11] remote address pool 1
Step 3 Create PVCs and configure PPPoA mapping on the PVCs.

[RouterC-Atm1/0/0] quit
[RouterC] interface atm 1/0/0.1
[RouterC-Atm1/0/0.1] pvc to_adsl_a 0/60
[RouterC-atm-pvc-Atm1/0/0.1-0/60-to_adsl_a] map ppp virtual-template 10
[RouterC-atm-pvc-Atm1/0/0.1-0/60-to_adsl_a] quit
[RouterC-Atm1/0/0.1] pvc to_adsl_b 0/61
[RouterC-atm-pvc-Atm1/0/0.1-0/61-to_adsl_b] map ppp virtual-template 11
[RouterC-atm-pvc-Atm1/0/0.1-0/61-to_adsl_b] quit
Step 4 Configure routes on Router A, Router B, and Router C to make them reachable.

# Check the PVC status on Router C.

[RouterC] display atm pvc-info
--------|-----|----------------|--------|-----|-----|---------------------
0/60 |UP |to_adsl_a |60 |SNAP |PPP |Atm1/0/0.1 (UP)
0/61 |UP |to_adsl_b |61 |SNAP |PPP |Atm1/0/0.1 (UP)
Establish a PPP connection from a PC to an ADSL router, and the PPP user is authenticated.
The PC can ping the ATM interface on Router C successfully.
----End
Configuration Files
Configuration file of Router C
#
sysname RouterC
#
interface Virtual-Template10
ip address 10.38.160.1 255.255.255.0
remote address pool 1
#
ip address 10.38.161.1 255.255.255.0
remote address pool 1
#
interface Atm1/0/0
undo shutdown
#
interface Atm1/0/0.1
pvc to_adsl_a 0/60
map ppp Virtual-Template10
pvc to_adsl_b 0/61
map ppp Virtual-Template11
#
aaa
local-user userr1 password cipher %$%$#{!{*"|uh/$|z(E0TW=G_Gj~%$%$
local-user userr1 service-type none
local-user userr1 state block fail-times 3 interval 5
local-user userr2 password cipher %$%$>ca'OE)3tA<_sj(c}[v(`,-=%$%$
local-user userr2 service-type none
local-user userr2 state block fail-times 3 interval 5
ip pool 1 10.38.162.1 10.38.162.100
#
return
Configuration files of Router A and Router B are similar to the configuration file of Router C,
and are not provided here.
8.8.3 Example for Configuring PPPoEoA

This example shows how to configure the PPPoEoA application in typical networking.
Each host inside the two Ethernets dials into the ATM network through an ADSL Router and
communicates with the Router through DSLAM.

Both the Router's WAN port and the ADSL Router's DSL interface adopt PPPoEoA. Each host
will use a pre-installed PPPoE Client program to complete PAP authentication with the
Routers and will obtain the IP address from the remote AAA server on the other side (not included
in the following figure).
Figure 8-3 PPPoEoA configuration networking diagram
ADSL RouterA
VT10:202.38.160.1/24
VT11:202.38.161.1/24
PC
ADSL RouterB
DSLAM RouterC
To ADSL Router A:0/60
To ADSL Router B:0/61
ATM1/0/0.1
PC
1. Create the virtual interface template and encapsulating PPP.
2. Create the virtual Ethernet interface and encapsulating PPP.
3. Create the PVC and specify the PVC to bear PPPoE.
Data Preparation
l IP addresses of VT interfaces on the Router
l VPI/VCI values of two PVCs connecting Routers with DSLAM
l IP address of RADIUS server
Procedure
# Connect to the RADIUS server for PPP negotiation.
[RouterC] aaa
[RouterC-aaa] authentication-scheme radius
[RouterC-aaa-authen-radius] authentication-mode radius
[RouterC-aaa-authen-radius] quit
[RouterC-aaa] quit
[RouterC] radius-server template shiva

[RouterC-radius-shiva] radius-server authentication 100.1.1.1 1645

[RouterC-radius-shiva] quit
# Create a VT interface to encapsulate PPP and configure PAP options.

# Create a VE interface to encapsulate PPP.

[RouterC] interface virtual-ethernet 1/1/0
[RouterC-Virtual-Ethernet1/1/0] pppoe-server bind virtual-template 10
[RouterC-Virtual-Ethernet1/1/0] quit
[RouterC-Virtual-Ethernet1/1/1] pppoe-server bind virtual-template 11
# Establish PVC to bear PPPoE.

[RouterC-Atm1/0/0] quit
[RouterC] interface atm 1/0/0.1
[RouterC-Atm1/0/0.1] pvc to_adsl_a 0/60
[RouterC-atm-pvc-Atm1/0/0.1-0/60-to_adsl_a] map bridge virtual-ethernet 1/1/0
[RouterC-atm-pvc-Atm1/0/0.1-0/60-to_adsl_a] quit
[RouterC-Atm1/0/0.1] pvc to_adsl_b 0/61
[RouterC-atm-pvc-Atm1/0/0.1-0/61-to_adsl_b] map bridge virtual-ethernet 1/1/1
[RouterC-atm-pvc-Atm1/0/0.1-0/61-to_adsl_b] quit
# Check the PVC status information on Router C.

--------|-----|----------------|--------|-----|-----|---------------------
0/60 |UP |to_adsl_a |60 |SNAP |ETH |Atm1/0/0.1 (UP)
0/61 |UP |to_adsl_b |61 |SNAP |ETH |Atm1/0/0.1 (UP)
----End
Configuration Files
#
sysname RouterC
#
radius-server template shiva
radius-server authentication 100.1.1.1 1645
#
ip address 202.38.160.1 255.255.255.0
#
ip address 202.38.161.1 255.255.255.0
#
interface Atm1/0/0
undo shutdown
#

interface Atm1/0/0.1
pvc to_adsl_a 0/60
map bridge Virtual-Ethernet1/1/0
pvc to_adsl_b 0/61
#
pppoe-server bind Virtual-Template 10
#
pppoe-server bind Virtual-Template 11
#
aaa
authentication-scheme default
authentication-scheme radius
authentication-mode radius
return
8.8.4 Example for Configuring ATM OAM

ATM OAM detects links in real time without interrupting services.
In Figure 8-4, Router A, Router B and Router C are connected to the ATM network. IPoA
services are configured on all the PVCs on ATM interfaces of the three routers.
To implement real-time and continuous detection without interrupting services, you need to
configure the OAM CC function.
Figure 8-4 Networking for ATM OAM configuration

Router B
IP:202.38.160.2/24
To A: 0/40
ATM To C:0/42
Network Interface:ATM 1/0/0
Router A
IP:202.38.160.1/24 Router C
To B: 0/40
To C:0/41
Interface:ATM 1/0/0
IP:202.38.160.3/24
To A: 0/41
To B:0/42
Interface:ATM 1/0/0

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 the ATM network, the VPI/VCI of Router A connecting to Router B and Router C,
respectively
l The VPI/VCI of Router B connecting to Router A and Router C, respectively
l The VPI/VCI of Router C connecting to Router A and Router B, respectively
Procedure
Step 1 Configure IPoA.
[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
[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.
[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-Atm1/0/0] oam
[RouterA-Atm1/0/0-fatm-oam] attribute 0/40 0/41 end-point
[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-Atm1/0/0] oam
[RouterC-Atm1/0/0-fatm-oam] attribute 0/41 0/42 end-point
Step 3 Activate the CC function.

[RouterA-Atm1/0/0-fatm-oam] cc 0/40 0/41 end-to-end both
[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-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.
<RouterA> system-view
[RouterA-Atm3/0/1-fatm-oam] display atm oam configuration atm 1/0/0
Interface PVC Attribute CC func CC dir CC attr
--------- ----- --------- ------- ------ -------
Atm1/0/0 0/40 end-point enable both end-to-end
Atm1/0/0 0/41 end-point enable both end-to-end
# Check the OAM statistics on the PVC.

<RouterA> display atm oam statistics atm 1/0/0 0/40
Total number of received OAM Cells : 0
Number of received AIS Cells : 0
Number of received RDI Cells : 0
Number of received loopback cells : 0
Number of received CC cells : 0
Number of received crc error cells : 0
Number of received other cells : 0
Total number of sent OAM Cells : 88
Number of sent AIS Cells : 0

Number of sent RDI Cells : 44

Number of sent loopback cells : 0
Number of sent CC cells : 44
----End
Configuration Files
#
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
#
return

#
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.3
oam
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

#
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.2
oam
attribute 0/41 0/42 end-point
cc 0/41 0/42 end-to-end both
#
return

Configuration Guide - WAN Access 9 1483B Configuration
9 1483B Configuration
About This Chapter
You can configure RFC 1483 Bridged (1483B) to connect user terminals to network-side bridge
devices.
9.1 Introduction of 1483B

1483B encapsulates data packets of the network layer at the data link layer, simulating the bridge
function of an Ethernet network. In this manner, user terminals and network-side bridge devices
are connected.
9.2 Configuring IPoEoA Services

IPoEoA indicates that AAL5 bears Ethernet packets and the Ethernet, in turn, bears IP packets.
In this manner, the layer 2 forwarding of IPoEoA packets is implemented between the Ethernet
and PVC. Configuring IPoEoA helps integrate both the ATM backbone and the IP networks to
transmit various Ethernet and IP services.

This section provides examples for configuring 1483B in terms of application scenarios,
configuration procedures, and verification.

9.1 Introduction of 1483B

function of an Ethernet network. In this manner, user terminals and network-side bridge devices
are connected.
9.1.1 1483B Overview

function of an Ethernet network.
RFC 1483 defines the standards of transmitting multi-protocol data unit on an ATM network in
the following manners:
l The 1483 Bridged: applied to the bridged protocol data unit.

l The 1483 Routing: applied to the routing protocol data unit.
RFC 1483 Bridged encapsulates the data packet of the network layer in the data link layer. It
imitates the bridge function of the Ethernet network, so that the terminal devices at the user side
and the bridge devices at the network side are connected.
Figure 9-1 shows the stack protocol of 1483B.
Figure 9-1 Stack protocol of 1483B
TCP/UDP
IP
Ethernet
1483B
TCP/UDP AAL5
ATM
IP
Ethernet
ATM Network
Access Router Router A
The IPoE Ethernet stack protocol is used to connect the device at the users' side. After the 1483B
is configured on the entry Router A on the ATM network, Router A can implement the bridge
of Ethernet packets to the ATM cells. This enables Router A to transparently transmit the
received IPoE packets on the ATM network.

IPoEoA is the main application of 1483B supported by the NE80E/40E. IPoEoA indicates that
AAL5 carries Ethernet packets, and the Ethernet carries IP packets to implement the layer 2
forwarding of IPoEoA packets between the Ethernet and PVC. IPoEoA converges the ATM
backbone and the IP networks. It also supports Ethernet and IP protocols.
9.2 Configuring IPoEoA Services

IPoEoA indicates that AAL5 bears Ethernet packets and the Ethernet, in turn, bears IP packets.
In this manner, the layer 2 forwarding of IPoEoA packets is implemented between the Ethernet
and PVC. Configuring IPoEoA helps integrate both the ATM backbone and the IP networks to
transmit various Ethernet and IP services.

Before configuring IPoEoA services, familiarize yourself with the usage scenario, complete the
pre-configuration tasks, and obtain the required data.
Usage Scenarios
The NE80E/40E supports the VE interface as the gateway of IPoEoA.
The core task of configuring IPoEoA on the NE80E/40E is to configure the mapping between
PVC and the VE interface on the incoming interface on the ATM network. This is done to ensure
that the IPoEoA packets can be transmitted transparently on the ATM network.
Pre-configured Tasks
Before configuring IPoEoA services, configure parameters of the ATM interface connecting the
router and ATM switch or that connecting the router and the peer device.
Data Preparation
To 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
9.2.2 Creating a VE Interface

VE interfaces are configured to implement IPoEoA service mapping on PVCs.
Context

Procedure
Step 1 Run:
system-view
Step 2 Run:
----End
9.2.3 Configuring IPoEoA Application Mapping on a PVC

Configuring IPoEoA mapping on PVCs implements transparent transmission of IPoE packets
over an ATM network.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
pvc { pvc [ vpi/vci ] | vpi/vci }
A PVC is created and the PVC interface view is displayed.
Step 4 Run:
The AAL5 encapsulation protocol type of PVC is configured.
The AAL5 encapsulation type for PVC can be aal5snap, aal5mux or aal5nlpid. By default, the
encapsulation type is aal5snap.
NOTE
Only aal5snap encapsulation supports InARP. InARP cannot be configured when aal5mux or
aal5nlpid is adopted.
To change the AAL5 encapsulation type of PVC to aal5mux or aal5nlpid, InARP must be deleted first if
it has been configured.
Step 5 Run:

The application mapping from PVC to VE interface is configured.
The PVC and the VE interface to which the PVC is mapped must on the same interface board.
When configuring the IPoEoA application mapping, ensure that there is no other mapping on
the PVC. When configuring other mappings, also ensure that there is no IPoEoA configuration
on the PVC.
----End
9.2.4 Configuring Services on the VE Interface

VE interfaces can be configured with all service functions of ordinary Ethernet interfaces.
Context
The method for configuring VE interfaces is the same as that for configuring common Ethernet
interfaces.
VE interfaces support routing and switching modes as well as the switchover between routing
and switching modes.
You can configure IP address and routing protocols for routing VE interfaces and add a switching
VE interface to the default VLAN. For the VE interface added to the VLAN, all PVCs mapped
to the VE are in the same VLAN.

After IPoEoA services, you can check the status of PVCs and VE interfaces and statistics.
Procedure
l 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 of
the VE interface.
----End
Example
Run the display interface atm command. If you can view the information about the ATM
interface, it means that the configuration is successful.
<HUAWEI> display atm interface atm 1/0/0
Description : Atm1/0/0 Interface
Route Port, The Maximum Transmit Unit is 1500 bytes


Flag: C2 19(0x13)
SDH alarm:
section layer: none
line layer: none
path layer: none
SDH error:
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 and the interface status, it
means that the configuration is successful.
--------|-----|----------------|--------|-----|-----|-----------------------
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 and
the peer address, it means that the configuration is successful.
<HUAWEI> display atm map-info
100.11.1.1, vlink 1
Atm1/0/0, PVC 2/101, ETH, Virtual-Ethernet1/1/1, UP
Run the display interface virtual-ethernet command. If you can view the statistics information
and status of the virtual ethernet interface, it means that the configuration is successful.
<HUAWEI> display interface virtual-ethernet 1/0/0
Virtual-Ethernet1/0/0 current state : UP
Line protocol current state : DOWN
Description : Virtual-Ethernet1/0/0 Interface
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc7a-9e15
Carrier 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


This section provides examples for configuring 1483B in terms of application scenarios,
configuration procedures, and verification.
9.3.1 Example for Configuring a Routing VE Interface to Work as

an IPoEoA Gateway
You can configure a routed VE interface as an IPoEoA gateway to connect hosts on the Ethernet
to an ATM network.
As shown in Figure 9-2, each Ethernet host accesses the ATM network through an ADSL router
and communicates with the router through DSLAM. The Ethernet hosts are required 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 the two PVCs connecting Router C and DSLAM are 0/60 and 0/61,
which belong to ADSL Router A and ADSL Router B, respectively.
Figure 9-2 Networking for IPoEoA configuration
ADSL
Workstation Router A
Ethernet
Workstation
DSLAM IP:202.38.160.1
Server
ADSL Router C
Router B TO ADSL Router A:0/60
Ethernet
Workstation TO ADSL Router B:0/61

Interface:Virtual-ethernet1/0/0
Server

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.
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-Virtual-Ethernet1/0/0] ip address 202.38.160.1 255.255.255.0
# Create a PVC and specify it to carry the IPoEoA protocol.

[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
# Check the PVC status information on Router C.

--------|-----|----------------|--------|-----|-----|---------------------
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 to Router A and the PCs connected to Router B can ping through the VE
interfaces on Router C.
----End
Configuration Files
Configuration file of RouterC
#
Sysname RouterC
#
interface Atm1/0/0
pvc to_adsl_a 0/60
#

pvc to_adsl_b 0/61

#
#
ip address 202.38.160.1 255.255.255.0
#
return
9.3.2 Example for Configuring ATM Bridged Ethernet

To enable users to communicate with each other over the ATM network, configure an ATM
bridge on the routers to recognize users that belong to the same VLAN and reside on both ends
of an ATM interface.
As shown in Figure 9-3, Router A and Router B are in the same ATM network. The enterprise
Ethernet networks are located in two places and transparently transmit Ethernet packets through
the ATM interface of the router connecting them.
The organization has two departments, with the VLAN IDs being 10 and 20, respectively. The
ATM bridge function is configured on the routers so that users using the same VLAN ID in
different locations feel that they are in the same LAN.
Figure 9-3 Networking for ATM bridged Ethernet
VLAN 10 VLAN 10
Ethernet3/0/1 PVC 100/1 Ethernet3/0/1

Router A ATM Router B
Ethernet3/0/2 PVC 100/2 Ethernet3/0/2
ATM1/0/0 ATM1/0/0
VLAN 20 VLAN 20
1. Create a VLAN.
2. Add Ethernet interfaces to the VLAN.
4. Add the VE to the VLAN.
5. Create a PVC and enter the PVC view.

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
Procedure
Step 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/1] 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-info

--------|-----|----------------|--------|-----|-----|-----------------------
100/1 |UP | |0 |SNAP |ETH |Atm1/0/0 (UP)
100/2 |UP | |0 |SNAP |ETH |Atm1/0/0 (UP)
The PCs connected to Router A and PCs connected to Router B can ping through each other.
----End
Configuration Files
Configuration files of Router A and Router B
#
Sysname HUAWEI
#
interface Ethernet3/0/1
portswitch
port default vlan 10
#
interface Ethernet3/0/2
portswitch
#
interface Atm1/0/0
pvc 100/1
#
pvc 100/2
#
#
portswitch
#
portswitch
#
return
9.3.3 Example for Configuring a VLANIF Interface to Work as an

IPoEoA Gateway
You can configure a VLANIF interface as an IPoEoA gateway to connect hosts on the Ethernet
to an ATM network.
As shown in Figure 9-4, each host on two Ethernet networks accesses the ATM network through
an ADSL router and communicates with the router through DSLAM. The hosts in the Ethernet
are required to access the Internet directly through the ADSL to manage the users in the Ethernet
networks on Router C.
The detailed networking conditions are as follows:
l 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 the two PVCs connecting the router and DSLAM are 0/60 and 0/61,
which belong to ADSL Router A and ADSL Router B, respectively.
Figure 9-4 Networking for IPoEoA configuration
ADSL
Workstation Router A
Ethernet
Workstation
DSLAM IP:202.38.160.1
Server
ADSL Router C
Router B TO ADSL Router A:0/60
Ethernet
Workstation TO ADSL Router B:0/61

Interface:Virtual-ethernet1/0/0
Server
1. Create VLAN 100.

2. Create a VLANIF interface.
3. Configure an IP address for the interface.
5. Add the VE to the VLAN.
6. Create a PVC and enter PVC view.
Data Preparation
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
# Create a VE interface and add it to VLAN 100.

[RouterC-Virtual-Ethernet1/0/0] portswitch
[RouterC-Virtual-Ethernet1/0/0] port default vlan 100
# Create a PVC and specify it to carry the IPoEoA protocol.

[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-info
--------|-----|----------------|--------|-----|-----|-------------
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 to Router A and the PCs connected to Router B can ping through the VE
interfaces on Router C.
----End
Configuration Files
Configuration 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
#
pvc to_adsl_b 0/61
#
#
portswitch
#
return

Configuration Guide - WAN Access 10 PRBS Testing Configuration
10 PRBS Testing Configuration
About This Chapter
The Pseudo Random Binary Sequence (PRBS) testing function supports one-click tests on user-
side and network-side service connectivity.
10.1 Overview
PRBS generates random data for service connectivity testing.
10.2 Configuring PRBS Testing

This section describes how to configure user-side and network-side PRBS testing.

10.1 Overview
PRBS generates random data for service connectivity testing.
During site deployment or device maintenance, PRBS testing can be performed when there is
no BER tester. The testing details are as follows:
l A PRBS testing-enabled local device sends a PRBS bit stream over a link to a loopback-
enabled remote device on a tested network.
l The bit stream is looped back to the local device.
l Upon receipt of the bit stream, the PRBS monitoring module on the local device checks
whether the bit stream is the same as the one previously sent and determines whether the
link or devices on the tested network are working properly.
PRBS testing includes user-side and network-side tests.
Figure 10-1 shows user-side RPBS testing.
Figure 10-1 User-side RPBS testing
Enables PRBS
testing and sends a
Enables remote PRBS bit stream.
loopback on the TX 1
base station and RX Receives the looped
loops back the back PRBS bit stream,
PRBS bit stream. 2 compares it with the
RX one previously sent,
TX 3 and calculates a bit
error rate.
MPLS/IP Core
CE PE1 PE2
After PRBS testing is enabled on PE1, PE1 sends a PRBS bit stream to the remote loopback-
enabled CE. The PRBS bit stream is then looped back to PE1. Upon receipt of the bit stream,
PE1 checks whether the bit stream is the same as the one previously sent and calculates a bit
error rate.
Figure 10-2 shows network-side RPBS testing.

Figure 10-2 Network-side RPBS testing
NMS
1
Sends a
PRBS bit
stream. Enables local 2
loopback.
PW
CE PE1 PE2 Local RNC

loopback
Calculates a bit
3 error rate.
After PRBS testing is enabled on PE1, PE1 sends a PRBS bit stream to PE2 that has local
loopback enabled. The PRBS bit stream is then looped back to PE1. Upon receipt of the bit
stream, PE1 checks whether the bit stream is the same as the one previously sent and calculates
a bit error rate.
10.2 Configuring PRBS Testing

This section describes how to configure user-side and network-side PRBS testing.

Before configuring PRBS testing, familiarize yourself with the usage scenario, complete the pre-
configuration tasks, and obtain the data required for the configuration.
Usage Scenario
PRBS testing is used to test service connectivity between two devices. A PRBS testing-enabled
NE80E/40E sends a PRBS bit stream to a remote device that has remote loopback enabled to
perform a user-side test or to a remote device that has local loopback enabled to perform a
network-side test. After the bit stream is looped back to NE80E/40E, NE80E/40E compares the
bit stream with the one it previously sent and calculates a bit error rate to determine the service
connectivity.
l Before configuring user-side PRBS, ensure that remote loopback has been enabled on the
remote device.
l Before configuring network-side PRBS, ensure that local loopback has been enabled on
the remote device.

Data Preparation
To configure PRBS testing, you need the following data.
No. Data
1 Number of an Ethernet interface on PE1
2 Number of an Ethernet interface on PE2
3 Number of an Ethernet interface on the CE
10.2.2 (Optional) Configuring User-Side PRBS Testing

After PRBS testing is enabled, you can perform a one-click test to check the service connectivity
on the UNI side, that is, whether services between CE and PE are running properly.
Context
As shown in Figure 10-3, remote loopback is enabled on a base station, and service connectivity
between PE1 and the base station is tested by enabling PE1 to send a PRBS bit stream to the
base station.
Figure 10-3 User-side RPBS testing
Enables PRBS
testing and sends a
Enables remote PRBS bit stream.
loopback on the TX 1
base station and RX Receives the looped
loops back the back PRBS bit stream,
PRBS bit stream. 2 compares it with the
RX one previously sent,
TX 3 and calculates a bit
error rate.
MPLS/IP Core
CE PE1 PE2
Procedure
Step 1 Run:
system-view
Step 2 Run:

test connectivity interface { interface-name | interface-type interface-number }

uni-direction pattern pattern-list interval { hour hour-value | minute minute-
value | second seconde-value } interval-repeat repeat-count
An enhanced PRBS connectivity test on the user-side is started.

test connectivity error-insert interface { interface-name | interface-name
interface-name } { single-bit | insert-ratio ratio-list }
Bit errors are injected into a PRBS bit stream while the enhanced PRBS connectivity test is going
on.

test connectivity abort interface { interface-name | interface-type interface-
number }
The enhanced PRBS connectivity test is ended.
----End
10.2.3 (Optional) Configuring Network-Side PRBS Testing

After PRBS testing is enabled, you can perform a one-click test to check the service connectivity
on the NNI side, that is, whether the PW between PEs is functioning properly.
Context
As shown in Figure 10-4, PW connectivity between PE1 and PE2 can be tested by enabling PE1
to send a PRBS bit stream to PE2, which has local loopback enabled.
Figure 10-4 Network-side RPBS testing

NMS
1
Sends a
PRBS bit
stream. Enables local 2
loopback.
PW
CE PE1 PE2 Local RNC

loopback
Calculates a bit
3 error rate.
Procedure
Step 1 Run:

system-view

Step 2 Run:
test connectivity interface { interface-name | interface-type interface-number }
nni-direction pattern pattern-list interval { hour hour-value | minute minute-
value | second seconde-value } interval-repeat repeat-count
An enhanced PRBS connectivity test on the network-side is started.

test connectivity error-insert interface { interface-name | interface-name
interface-name } { single-bit | insert-ratio ratio-list }
Bit errors are injected into a PRBS bit stream while the enhanced PRBS connectivity test is going
on.
test connectivity abort interface { interface-name | interface-type interface-
number }
The enhanced PRBS connectivity test is ended.
----End

After configuring PRBS testing, check the configurations.
Procedure
l Run the display connectivity-test history interface { interface-name | interface-type
interface-number } [ index index-value ] command to view the results of PRBS test
instances on a specified interface.
l Run the display connectivity-test history command to view PRBS historical test instances.
----End
Example
Run the display connectivity-test command. The command output shows the results of PRBS
test instances on a specified interface. For example:
[HUAWEI] display connectivity-test interface serial1/0/0/1:0
Summary:
Start time Side Pattern Phy-port Total time (Interval*Round)
2013-03-16 14:12:46 UNI PRBS20 CPOS 1/0/0 00:01:40 (10s*10)
Total bits Error bits BER LOS Test progress
136896000 69454 5e-4 0s 69%(00:01:09) finished.
Details:
Round Total bits Error bits BER LOS ES EFS SES UAS
1 19840000 0 0e-0 0s 0s 10s 0s 0s
2 19840000 2 1e-7 0s 2s 8s 0s 0s
3 19840000 6346 3e-4 0s 4s 6s 1s 0s
4 19840000 19940 1e-3 0s 10s 0s 5s 0s
5 19840000 19978 1e-3 0s 10s 0s 6s 0s
6 19840000 19899 1e-3 0s 10s 0s 5s 0s
7(90%) 17856000 3289 1e-4 0s 2s 7s 1s 0s
Error Bits Insert Record (Latest 10):

Start time Type BER Duration Insert in round

2013-03-16 14:12:58 Single N/A N/A 2
2013-03-16 14:12:59 Single N/A N/A 2
2013-03-16 14:13:13 Continuous 1e-3 17s
3 to 5 2013-03-16 14:13:30 Continuous 1e-3 3s 5
2013-03-16 14:13:33 Continuous 1e-3 15s 5 to now
Run the display connectivity-test history command. The command output shows PRBS
historical test instances. For example:
[HUAWEI] display connectivity-test history
Connectivity test history:
Start time Interface Phy-port Interval Side Pattern
2013-03-14 21:17:03 Serial0/2/1:10 E1 0/2/1 100s*10 NNI PRBS15
2013-03-16 09:48:27 Serial0/2/0:0 E1 0/2/0 10s*2 UNI PRBS15

Configuration Guide - WAN Access A Glossary
A Glossary
A list of frequently used terms and concepts in this document.
ATM Asynchronous Transfer Mode (ATM). A data transmission

technology in which data is transferred at high data rates in fixed
length, 53 bytes.
Authentication An act that decides whether a user can be awarded with access right
or 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 a
network through dialup.
Callback A call mode in which both ends of the communication participate

in the call. One end is called the Client, while the other end is caller
the Server. The Client initiates a call, and the Server decides
whether to call back. If a callback is needed, the Server tears down
the connection and then initiates a call to the Client.
Called Number Number of the called party.
Calling Number Number of the calling party.
POS A MAN and LAN technology that provides a point to point

connection. The POS interface is based on SONET.

Configuration Guide - WAN Access A Glossary
SONET Synchronous Optical Network (SONET). A standard for

synchronous data transfer over optical networks. The standard
contains a series of transmission speed, including SDH Transport
Module (STM) -1 (155 Mbit/s), STM-4c (622 Mbit/s) and
STM-16c/STM-16 (2.5 Gbit/s).
WAN Wide Area Network. A network that covers a large geographic

area.

Configuration Guide - WAN Access B Acronyms and Abbreviations
B Acronyms and Abbreviations
A list of frequently used acronyms and abbreviations in this document.
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)
BAS Broadband Access Server
BRI Basic Rate Interface

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
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
EIA Electronics Industry Association
ESF Extended Service Frame
ETSI European Telecommunications Standards Institute

FCS Frame Check Sequence
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
GE Gigabit Ethernet
GPRS General Packet Radio Service
GRE Generic Routing Encapsulation
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 Hypertext Transfer Protocol
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
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 - Telecommunication

Standardization Sector
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
MAP Mobile Application Part
MD5 Message Digest 5
MFR Multiple Frame Relay
MIB Management Information Base
MP Multilink PPP

MTU Maximum Transmission Unit
NAT Network Address Translation
NBMA Non Broadcast Multiple Access
NCP Network Control Protocol
NE NetEngine
NNI Network Node Interface
NT Network Terminal
OAM Operation, Administration and Maintenance
OC-3 OC-3
OSI Open System Interconnection
OSPF Open Shortest Path First
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
QoS Quality of Service

RADIUS Remote Authentication Dial in User Service
RAS Remote Access Server
RFC Request for Comments
RIP Routing Information Protocol
RSOH Regenerator Section Overhead
RSU Routing Switch Unit
RTP Real-time Transport Protocol
RTU Remote Test Unit
SDH Synchronous Digital Hierarchy
SDLC Synchronous Data Link Control
SDSL Symmetrical Digital Subscriber Line
SF Signal Failure
SGSN Serving GPRS Support Node
SHDSL Single-line High Speed Digital Subscriber Line
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
TACACS Terminal Access Controller Access Control System
TCP Transmission Control Protocol

TFTP Trivial File Transfer Protocol
TU Tributary Unit
TUG Tributary Unit Group
UBR Unspecified Bit Rate
UDP User Datagram Protocol
UNI User Network Interface
UP User Plane
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
WWW World Wide Web


NE40E&80E V600R008C10 Configuration Guide - WAN Access 01 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NE40E&80E V600R008C10 Configuration Guide - WAN Access 01 PDF

Uploaded by

Copyright:

Available Formats

HUAWEI NetEngine80E/40E Router

Configuration Guide - WAN Access

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2014-09-30) Huawei Proprietary and Confidential i

About This Document

Issue 02 (2014-09-30) Huawei Proprietary and Confidential ii

Product Name Version

HUAWEI NetEngine80E/40E V600R008C10

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Calls attention to important information, best practices and

Issue 02 (2014-09-30) Huawei Proprietary and Confidential iii

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

{ x | y | ... } Optional items are grouped in braces and separated by

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

{ x | y | ... }* Optional items are grouped in braces and separated by

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

# A line starting with the # sign is comments.

Changes in Issue 02 (2014-09-30)

Changes in Issue 01 (2014-06-30)

Issue 02 (2014-09-30) Huawei Proprietary and Confidential iv

About This Document.....................................................................................................................ii

2 E-Carrier and T-Carrier Interface Configuration....................................................................9

Issue 02 (2014-09-30) Huawei Proprietary and Confidential v

2.3.5 Configuring Frame Format of the CT1 Interface......................................................................................................25

3 POS and CPOS Interface Configuration.................................................................................43

Issue 02 (2014-09-30) Huawei Proprietary and Confidential vi

3.3.4 Configuring the Overhead Byte.................................................................................................................................67

Issue 02 (2014-09-30) Huawei Proprietary and Confidential vii

3.10.3 Configuring Frame Format......................................................................................................................................96

4 PPP and MP Configuration.....................................................................................................155

Issue 02 (2014-09-30) Huawei Proprietary and Confidential viii

4.5.2 Configuring the Callback Function.........................................................................................................................172

Issue 02 (2014-09-30) Huawei Proprietary and Confidential ix

4.11 Configuration Examples...........................................................................................................................................199

5 Frame Relay Configuration.....................................................................................................216

6 HDLC and IP-Trunk Configuration......................................................................................229

Issue 02 (2014-09-30) Huawei Proprietary and Confidential x

8 ATM Configuration.................................................................................................................. 264

Issue 02 (2014-09-30) Huawei Proprietary and Confidential xi

8.2.11 Checking the Configurations.................................................................................................................................275

Issue 02 (2014-09-30) Huawei Proprietary and Confidential xii

9.2.3 Configuring IPoEoA Application Mapping on a PVC............................................................................................317

10 PRBS Testing Configuration.................................................................................................327

Issue 02 (2014-09-30) Huawei Proprietary and Confidential xiii

1 Serial Interface Configuration

About This Chapter

1.2 Configuring the Link Layer Attributes for a Serial Interface

1.3 Maintaining Serial Interface Configuration

Issue 02 (2014-09-30) Huawei Proprietary and Confidential 1

1.1.1 Overview of the Synchronous Serial Interface

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

Table 1-1 Index modes of synchronous serial interfaces

Physical Interface Index Mode

E1 channelized from a slot/card/port/channel:0 or slot/card/port/channel:channel-set

CE1 interface slot/card/port:channel-set or slot/card/port:0

Issue 02 (2014-09-30) Huawei Proprietary and Confidential 2