HUAWEI Configuration Guide - WAN Access (V600R001C00 - 03)

HUAWEI NetEngine80E/40E Router V600R001C00
Configuration Guide - WAN Access

Issue Date 03 2010-03-31
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Issue 03 (2010-03-31)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
HUAWEI NetEngine80E/40E Router 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 provides 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.
Related Versions
The following table lists the product versions related to this document. Product Name HUAWEI NetEngine80E/40E Router Version V600R001C00
Intended Audience
The intended audience of this document is:
l l l l
Commissioning Engineer Data Configuration Engineer Network Monitoring Engineer System Maintenance Engineer
Organization
This document consists of eight chapters and is organized as follows.
Issue 03 (2010-03-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
About This Document
Chapter 1 Serial Interface Configuration 2 E-Carrier and T-Carrier Interface Configuration 3 POS and CPOS Interface Configuration
Description This chapter describes synchronous serial interfaces. It also describes the configuration steps of serial interface, along with typical examples. This chapter describes E-Carrier and T-Carrier interface related concepts, the configuration steps of various interfaces including CE1, CT1, E3, T3, along with typical examples. This chapter describes Synchronous Digital Hierarchy (SDH), Synchronous Optical Network (SONET), Packet over SONET/SDH (POS), and Channelized POS interface (CPOS interface) related concepts. It also describes the configuration steps of various interfaces including POS, STM-1 CPOS, E1/T1 channels of the CPOS interface, STM-16 CPOS, Channelized POS interface, along with typical examples. This chapter describes Point-to-Point Protocol (PPP) and MultiLink PPP (MP) related concepts including authentication and link operation. This chapter describes frame relay related concepts and configuration steps for frame function, LMI type and MFR, along with typical examples. This chapter describes how to encapsulate an interface with HDLC protocol, IP-Trunk interface and how to set the HDLC parameters and IP-Trunk interface. This chapter describes Asynchronous Transfer Mode (ATM) broadband networking technologies and configuration steps for ATM interface, IPoA application, PVC service mapping, and service type of a PVC, along with typical examples. This chapter describes 1483B technologies and configuration steps for IPoEoA application, along with typical examples. This appendix collates frequently used glossaries in this document. This appendix collates frequently used acronyms and abbreviations in this document.
4 PPP and MP Configuration 5 Frame Relay Configuration 6 HDLC and IP-Trunk Configuration 7 ATM Configuration
8 1483B Configuration A Glossary B Acronyms and Abbreviations
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
iv
Issue 03 (2010-03-31)
About This Document
Symbol
Description Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows. Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Examples of information displayed on the screen are in Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows. Convention boldface Italic [] { x | y | ... } Description The keywords of a command line are in boldface. Command arguments are in italic. Items (keywords or arguments) in square brackets [ ] are optional. Alternative items are grouped in braces and separated by vertical bars. One is selected.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
Issue 03 (2010-03-31)
About This Document
Convention [ x | y | ... ] { x | y | ... }*
Description Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected. Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected. Optional alternative items are grouped in square brackets and separated by vertical bars. Many or none can be selected. This parameter before the & sign can be repeated 1 to n times. A line starting with the # sign is comments.
[ x | y | ... ]*
&<1-n> #
GUI Conventions
The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
Keyboard Operation
The keyboard operations that may be found in this document are defined as follows. Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.
Mouse Operation
The mouse operations that may be found in this document are defined as follows.
vi
Issue 03 (2010-03-31)
About This Document
Action Click Double-click Drag
Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions.
Updates in Issue 03 (2010-03-31)

The third commercial release.

The second commercial release.

Initial commercial release.
Issue 03 (2010-03-31)
vii
Contents
Contents
About This Document...................................................................................................................iii 1 Serial Interface Configuration.................................................................................................1-1
1.1 Introduction to the Serial Interface..................................................................................................................1-2 1.1.1 Overview of the Synchronous Serial Interface.......................................................................................1-2 1.1.2 Features of the Synchronous Serial Interface on the NE80E/40E..........................................................1-2 1.2 Configuring the Link Layer Attributes for a Serial Interface..........................................................................1-2 1.2.1 Establishing the Configuration Task......................................................................................................1-3 1.2.2 Configuring Link Layer Protocol Type..................................................................................................1-3 1.2.3 Configuring Hold-Interval of the Link Layer Protocol of the Synchronous Serial Interface................ 1-4 1.2.4 Configuring the MTU.............................................................................................................................1-5 1.2.5 Configuring the Parity Bit......................................................................................................................1-5 1.2.6 Checking the Configuration...................................................................................................................1-6 1.3 Maintaining Serial Interface Configuration.................................................................................................... 1-7 1.3.1 Clearing the Interface Statistics..............................................................................................................1-7
2 E-Carrier and T-Carrier Interface Configuration.................................................................2-1

2.1 Introduction to the E-Carrier and T-Carrier Interface.....................................................................................2-2 2.1.1 E-Carrier and T-Carrier Overview.........................................................................................................2-2 2.1.2 Features of E-Carrier and T-Carrier Interfaces in the NE80E/40E........................................................2-4 2.2 Configuring CE1 Interfaces............................................................................................................................ 2-4 2.2.1 Establishing the Configuration Task......................................................................................................2-5 2.2.2 Creating Synchronous Serial Interface for CE1 Interface......................................................................2-5 2.2.3 Configuring Coding or Decoding Format of CE1 Interface...................................................................2-7 2.2.4 Configuring Clock Mode of CE1 Interface............................................................................................2-7 2.2.5 Configuring Frame Format of the CE1 Interface...................................................................................2-8 2.2.6 Checking the Configuration...................................................................................................................2-9 2.3 Configuring CT1 Interfaces..........................................................................................................................2-10 2.3.1 Establishing the Configuration Task....................................................................................................2-10 2.3.2 Creating Synchronous Serial Interface for CT1 Interface....................................................................2-11 2.3.3 Configuring Coding or Decoding Format of the CT1 Interface...........................................................2-12 2.3.4 Configuring Clock Mode of the CT1 Interface....................................................................................2-12 2.3.5 Configuring Frame Format of the CT1 Interface.................................................................................2-13 2.3.6 Checking the Configuration.................................................................................................................2-14 Issue 03 (2010-03-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
2.4 Configuring E3 Interfaces.............................................................................................................................2-14 2.4.1 Establishing the Configuration Task....................................................................................................2-15 2.4.2 Creating Synchronous Serial Interface for E3 Interface......................................................................2-15 2.4.3 Checking the Configuration.................................................................................................................2-16 2.5 Configuring CT3 Interfaces..........................................................................................................................2-17 2.5.1 Establishing the Configuration Task....................................................................................................2-17 2.5.2 Creating Synchronous Serial Interface for CT3 Interface....................................................................2-18 2.5.3 Configuring Frame Format of the CT3 Interface.................................................................................2-19 2.5.4 Checking the Configuration.................................................................................................................2-20 2.6 Configuring a T1 Channel of CT3 Interfaces................................................................................................2-21 2.6.1 Establishing the Configuration Task....................................................................................................2-21 2.6.2 Configuring Clock Mode of a T1 Channel...........................................................................................2-22 2.6.3 Configuring Frame Format of a T1 Channel........................................................................................2-22 2.6.4 Checking the Configuration.................................................................................................................2-23 2.7 Maintaining E-Carrier and T-Carrier Interface Configuration......................................................................2-24 2.7.1 Setting Loopback to Detect Whether the Interface Is Normal.............................................................2-24 2.7.2 Clearing the Interface Statistics............................................................................................................2-25 2.8 Configuration Examples................................................................................................................................2-25 2.8.1 Example for Configuring Communication over CE1 Interfaces Bundle.............................................2-25
3 POS and CPOS Interface Configuration...............................................................................3-1

3.1 Introduction to the POS and CPOS Interfaces................................................................................................3-2 3.1.1 Overview of POS and CPOS Interfaces.................................................................................................3-2 3.1.2 Features of POS and CPOS Interfaces on the NE80E/40E....................................................................3-7 3.2 Configuring POS Interfaces............................................................................................................................3-9 3.2.1 Establishing the Configuration Task......................................................................................................3-9 3.2.2 Configuring the Link Layer Protocol...................................................................................................3-10 3.2.3 Configuring Clock Mode.....................................................................................................................3-11 3.2.4 Configuring the Overhead Byte...........................................................................................................3-11 3.2.5 Configuring Frame Format...................................................................................................................3-12 3.2.6 Configuring the Scramble Function.....................................................................................................3-13 3.2.7 Configuring the Length of the CRC Check Character.........................................................................3-13 3.2.8 Configuring MTU................................................................................................................................3-14 3.2.9 Checking the Configuration.................................................................................................................3-15 3.3 Configuring STM-1 CPOS Interfaces...........................................................................................................3-17 3.3.1 Establishing the Configuration Task....................................................................................................3-17 3.3.2 Configuring Clock Mode.....................................................................................................................3-18 3.3.3 Configuring Frame Format...................................................................................................................3-18 3.3.4 Configuring the Overhead Byte...........................................................................................................3-19 3.3.5 Configuring AUG Multiplexing Route................................................................................................3-20 3.3.6 Checking the Configuration.................................................................................................................3-21 3.4 Configuring E1 Channels of the CPOS Interface..........................................................................................3-21 3.4.1 Establishing the Configuration Task....................................................................................................3-21 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-03-31)
Contents
3.4.2 Creating Synchronous Serial Interface of E1 Channel.........................................................................3-22 3.4.3 Configuring Frame Format...................................................................................................................3-23 3.4.4 Configuring Clock Mode.....................................................................................................................3-23 3.4.5 Checking the Configuration.................................................................................................................3-24 3.5 Configuring T1 Channels of the CPOS Interface..........................................................................................3-25 3.5.1 Establishing the Configuration Task....................................................................................................3-25 3.5.2 Creating Synchronous Serial Interface of T1 Channel.........................................................................3-26 3.5.3 Configuring Frame Format...................................................................................................................3-26 3.5.4 Configuring Clock Mode.....................................................................................................................3-27 3.5.5 Checking the Configuration.................................................................................................................3-27 3.6 Configuring E3 Channels of an STM-1 CPOS Interface..............................................................................3-28 3.6.1 Establishing the Configuration Task....................................................................................................3-28 3.6.2 Creating Synchronous Serial Interface of E3 Channels.......................................................................3-29 3.6.3 Configuring Clock Mode.....................................................................................................................3-30 3.6.4 Checking the Configuration.................................................................................................................3-30 3.7 Configuring T3 Channels of an STM-1 CPOS Interface..............................................................................3-31 3.7.1 Establishing the Configuration Task....................................................................................................3-31 3.7.2 Creating T3 Channels...........................................................................................................................3-32 3.7.3 Configuring Frame Format...................................................................................................................3-33 3.7.4 Configuring Clock Mode.....................................................................................................................3-33 3.7.5 Checking the Configuration.................................................................................................................3-34 3.8 Maintaining POS and CPOS Interface Configuration...................................................................................3-35 3.8.1 Configuring the Self-loop to Detect Whether the Interface Is Normal................................................3-35 3.8.2 Clearing the Interface Statistics............................................................................................................3-36 3.9 Configuration Examples ...............................................................................................................................3-37 3.9.1 Example for Directly Connecting Devices Through POS Interfaces...................................................3-37 3.9.2 Example for Connecting Devices with POS Interfaces Through FR Network....................................3-39 3.9.3 Example for Configuring an STM-1 CPOS Interface..........................................................................3-42
4 PPP and MP Configuration......................................................................................................4-1

4.1 Introduction to PPP and MP............................................................................................................................4-2 4.1.1 PPP and MP Overview...........................................................................................................................4-2 4.1.2 Features of PPP and MP on the NE80E/40E..........................................................................................4-2 4.2 Encapsulating an Interface with PPP and MRU Negotiation..........................................................................4-3 4.2.1 Establishing the Configuration Task......................................................................................................4-3 4.2.2 Encapsulating the Interface with PPP.................................................................................................... 4-3 4.2.3 Enabling PPP MRU Negotiation............................................................................................................4-4 4.2.4 Checking the Configuration...................................................................................................................4-5 4.3 Configuring Unidirectional PAP.....................................................................................................................4-5 4.3.1 Establishing the Configuration Task......................................................................................................4-6 4.3.2 Configuring a Local Router to Authenticate Its Peer in PAP Mode......................................................4-6 4.3.3 Configuring the Peer to Be Authenticated by the Local Router in PAP Mode......................................4-7 4.3.4 Checking the Configuration...................................................................................................................4-8 Issue 03 (2010-03-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
4.4 Configuring Unidirectional CHAP..................................................................................................................4-9 4.4.1 Establishing the Configuration Task......................................................................................................4-9 4.4.2 Configuring a Local Device with a User Name to Authenticate Its Peer in CHAP Mode..................4-10 4.4.3 Configuring a Local Device Without a User Name to Authenticate Its Peer in CHAP Mode............4-11 4.4.4 Checking the Configuration.................................................................................................................4-13 4.5 Configuring PPP Optional Parameters..........................................................................................................4-14 4.5.1 Establishing the Configuration Task....................................................................................................4-14 4.5.2 Configuring the Callback Function......................................................................................................4-15 4.5.3 Configuring Packet or Packet Header Compression............................................................................4-16 4.5.4 Configuring the Timeout Period of Negotiation..................................................................................4-17 4.5.5 Configuring the Polling Interval..........................................................................................................4-17 4.5.6 Configuring DNS Server Address Negotiation....................................................................................4-17 4.5.7 Configuring the PPP Link Quality Detection.......................................................................................4-18 4.5.8 Preventing the Peer Host Route from Being Added to the Local Routing Table of Direct Routes.....4-19 4.5.9 Checking the Configuration.................................................................................................................4-19 4.6 Configuring MP Binding Using an MP-Group.............................................................................................4-21 4.6.1 Establishing the Configuration Task....................................................................................................4-21 4.6.2 Adding an Interface to an MP-Group...................................................................................................4-22 4.6.3 Disabling the Endpoint Discriminator Negotiation..............................................................................4-23 4.6.4 Checking the Configuration.................................................................................................................4-24 4.7 Configuring MP Limiting Parameters...........................................................................................................4-25 4.7.1 Establishing the Configuration Task....................................................................................................4-26 4.7.2 Configuring the MRRU of an MP Group.............................................................................................4-26 4.7.3 Configuring the Damping Function for MP Subchannels....................................................................4-27 4.7.4 Configuring the Minimum Number of Subchannels in the Up State in an MP Link...........................4-28 4.7.5 Checking the Configuration.................................................................................................................4-28 4.8 Configuring MP Fragmentation....................................................................................................................4-29 4.8.1 Establishing the Configuration Task....................................................................................................4-29 4.8.2 Configuring the MP Fragment Function..............................................................................................4-29 4.8.3 Checking the Configuration.................................................................................................................4-30 4.9 Maintaining PPP and MP Configuration.......................................................................................................4-30 4.10 Configuration Examples..............................................................................................................................4-31 4.10.1 Example for Configuring PAP Authentication..................................................................................4-32 4.10.2 Example for Configuring Unidirectional CHAP Authentication.......................................................4-34 4.10.3 Example for Configuring Bidirectional CHAP Authentication.........................................................4-37 4.10.4 Example for Binding MPs into an MP-group....................................................................................4-39
5 Frame Relay Configuration......................................................................................................5-1

5.1 Introduction to Frame Relay...........................................................................................................................5-2 5.1.1 FR Protocol Overview............................................................................................................................5-2 5.1.2 Features of FR on the NE80E/40E.........................................................................................................5-2 5.2 Configuring FR...............................................................................................................................................5-2 5.2.1 Establishing the Configuration Task......................................................................................................5-2 xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-03-31)
Contents
5.2.2 Configuring Basic FR Functions............................................................................................................5-3 5.2.3 Checking the Configuration...................................................................................................................5-5 5.3 Configuring FR LMI Type and Related Parameters.......................................................................................5-5 5.3.1 Establishing the Configuration Task......................................................................................................5-5 5.3.2 Configuring FR LMI and Related Parameters of DTE..........................................................................5-6 5.3.3 Configuring FR LMI and Related Parameters of DCE..........................................................................5-7 5.3.4 Checking the Configuration...................................................................................................................5-7 5.4 Maintaining Frame Relay Configuration........................................................................................................5-8 5.4.1 Clearing the Statistics of FR and Dynamic Address Mapping Entries..................................................5-8 5.4.2 Debugging FR........................................................................................................................................5-8 5.5 Configuration Examples..................................................................................................................................5-9 5.5.1 Example for Connecting Devices with POS Interfaces Through FR Network......................................5-9
6 HDLC and IP-Trunk Configuration.......................................................................................6-1

6.1 Introduction to HDLC and IP-Trunk...............................................................................................................6-2 6.1.1 HDLC and IP-Trunk Interface Overview...............................................................................................6-2 6.1.2 Features of HDLC and IP-Trunk interfaces on the router......................................................................6-2 6.2 Configuring HDLC.........................................................................................................................................6-3 6.2.1 Establishing the Configuration Task......................................................................................................6-3 6.2.2 Encapsulating an Interface with HDLC.................................................................................................6-3 6.2.3 Configuring the IP Address of the Interface..........................................................................................6-4 6.2.4 Setting the Polling Interval.....................................................................................................................6-4 6.2.5 Checking the Configuration...................................................................................................................6-5 6.3 Configuring an IP-Trunk Interface..................................................................................................................6-6 6.3.1 Establishing the Configuration Task......................................................................................................6-6 6.3.2 Creating an IP-Trunk and adding POS Interfaces into the IP-Trunk.....................................................6-7 6.3.3 Configuring an IP Address for the IP-Trunk Interface...........................................................................6-8 6.3.4 (Optional) Configuring the Lower Threshold of Up Links....................................................................6-9 6.3.5 (Optional) Configuring Load-balancing Mode for the IP-Trunk Interface............................................6-9 6.3.6 (Optional) Configuring Weights for Member Links............................................................................6-10 6.3.7 (Optional) Configuring the Method of Sending Trap Messages from an IP-Trunk Member Interface .......................................................................................................................................................................6-10 6.3.8 Checking the Configuration.................................................................................................................6-11 6.4 Maintaining HDLC and IP-Trunk Configuration..........................................................................................6-12 6.4.1 Clearing the statistics of the HDLC or IP-Trunk interfaces.................................................................6-13 6.4.2 Debugging HDLC................................................................................................................................6-13 6.5 Configuration Examples................................................................................................................................6-14 6.5.1 Example for Configuring HDLC..........................................................................................................6-14 6.5.2 Example for Configuring IP Address Unnumbered for HDLC...........................................................6-16 6.5.3 Example for Configuring an IP-Trunk.................................................................................................6-18
7 ATM Configuration...................................................................................................................7-1
7.1 Introduction to ATM.......................................................................................................................................7-2 7.1.1 ATM Overview......................................................................................................................................7-2 Issue 03 (2010-03-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access 7.1.2 Features of ATM Supported by the NE80E/40E...................................................................................7-2
7.2 Configuring Parameters for an ATM OC-3/STM-1 Interface or an ATM OC-12/STM-4 Interface..............7-3 7.2.1 Establishing the Configuration Task......................................................................................................7-3 7.2.2 Configuring the Clock Mode..................................................................................................................7-4 7.2.3 Configuring the Frame Format...............................................................................................................7-5 7.2.4 Configuring the Overhead Byte.............................................................................................................7-5 7.2.5 Configuring the MTU.............................................................................................................................7-6 7.2.6 Configuring the Scrambling...................................................................................................................7-7 7.2.7 Configuring the Interval of Flow Statistics............................................................................................7-8 7.2.8 Checking the Configuration...................................................................................................................7-9 7.3 Configuring ATM Services on a Serial Interface..........................................................................................7-10 7.3.1 Establishing the Configuration Task....................................................................................................7-10 7.3.2 Configuring the ATM Protocol on a Serial Interface...........................................................................7-11 7.3.3 (Optional) Configuring the ATM Interface Type for a Serial Interface...............................................7-12 7.3.4 Creating a PVC on a Serial Interface................................................................................................... 7-12 7.3.5 Creating a PVP on a Serial Interface....................................................................................................7-13 7.3.6 Checking the Configuration.................................................................................................................7-14 7.4 Configuring IMA Groups..............................................................................................................................7-14 7.4.1 Establishing the Configuration Task....................................................................................................7-15 7.4.2 Creating an IMA Group....................................................................................................................... 7-15 7.4.3 Setting the Number of the Cells Contained in an IMA Frame.............................................................7-16 7.4.4 Configuring Bandwidth for an IMA Group......................................................................................... 7-16 7.4.5 Setting the Maximum Link Differential Delay for the IMA Group.....................................................7-17 7.4.6 Adding an Interface to an IMA Group.................................................................................................7-17 7.4.7 (Optional) Configuring the ATM Interface Type for an IMA Group..................................................7-18 7.4.8 Creating a PVC for an IMA Group......................................................................................................7-19 7.4.9 Creating a PVP for an IMA Group.......................................................................................................7-20 7.4.10 Checking the Configuration...............................................................................................................7-20 7.5 Configuring the IPoA Application................................................................................................................7-21 7.5.1 Establishing the Configuration Task....................................................................................................7-21 7.5.2 Configuring IPoA Mapping on a PVC.................................................................................................7-22 7.5.3 Checking the Configuration.................................................................................................................7-23 7.6 Configuring the Service Type and Optional Parameters of a PVC...............................................................7-25 7.6.1 Establishing the Configuration Task....................................................................................................7-25 7.6.2 Configuring the Service Type of a PVC.............................................................................................. 7-26 7.6.3 Configuring the Service Type of a PVP...............................................................................................7-27 7.6.4 (Optional) Configure the Overload Bandwidth Value of an ATM Interface.......................................7-28 7.6.5 Checking the Configuration.................................................................................................................7-28 7.7 Configuring ATM OAM...............................................................................................................................7-30 7.7.1 Establishing the Configuration Task....................................................................................................7-30 7.7.2 (Optional) Activating the CC Function................................................................................................7-31 7.7.3 (Optional) Configuring OAM End-to-End Loopback..........................................................................7-32 xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-03-31)
Contents
7.7.4 (Optional) Configuring the Cell Loopback..........................................................................................7-33 7.7.5 Checking the Configuration.................................................................................................................7-34 7.8 Maintaining ATM Configuration..................................................................................................................7-35 7.8.1 Setting Loopback to Detect Whether an Interface Is Normal..............................................................7-35 7.8.2 Clearing the ATM Interface Statistics..................................................................................................7-36 7.8.3 Debugging ATM..................................................................................................................................7-36 7.9 Configuration Examples................................................................................................................................7-37 7.9.1 Example for Configuring IPoA............................................................................................................7-37 7.9.2 Example for Configuring ATM OAM.................................................................................................7-40 7.9.3 Example for Configuring IMAoPSN...................................................................................................7-44
8 1483B Configuration..................................................................................................................8-1
8.1 Introduction of 1483B.....................................................................................................................................8-2 8.1.1 1483B Overview....................................................................................................................................8-2 8.2 Configuring IPoEoA Services.........................................................................................................................8-3 8.2.1 Establishing the Configuration Task......................................................................................................8-3 8.2.2 Creating a VE Interface..........................................................................................................................8-3 8.2.3 Configuring IPoEoA Application Mapping on a PVC...........................................................................8-4 8.2.4 Configuring Services on the VE Interface.............................................................................................8-5 8.2.5 Checking the Configuration...................................................................................................................8-5 8.3 Configuration Examples..................................................................................................................................8-6 8.3.1 Example for Configuring a Routing VE Interface to Work as an IPoEoA Gateway.............................8-7 8.3.2 Example for Configuring ATM Bridged Ethernet.................................................................................8-9 8.3.3 Example for Configuring a VLANIF Interface to Work as an IPoEoA Gateway...............................8-11
A Glossary.....................................................................................................................................A-1 B Acronyms and Abbreviations.................................................................................................B-1
Issue 03 (2010-03-31)
xv
Figures
Figures
Figure 2-1 Schematic diagram of CE1 interface configuration..........................................................................2-25 Figure 3-1 STM-N frame structure......................................................................................................................3-4 Figure 3-2 Process of multiplexing E1 to STM-1................................................................................................3-5 Figure 3-3 Process of multiplexing T1 to STM-1................................................................................................3-5 Figure 3-4 Sequence of arrangement of TUG-3, TUG-2 and TU-12 in VC-4.....................................................3-6 Figure 3-5 Networking diagram of connecting devices directly through POS interfaces..................................3-37 Figure 3-6 Networking diagram of connecting routers using the POS interface through FR network..............3-40 Figure 3-7 Networking diagram of an STM-1 CPOS interface.........................................................................3-42 Figure 4-1 Networking diagram of PAP authentication.....................................................................................4-32 Figure 4-2 Networking diagram of unidirectional CHAP authentication..........................................................4-34 Figure 4-3 Networking diagram of bidirectional CHAP authentication............................................................4-37 Figure 4-4 Networking diagram of the MP-group binding................................................................................4-39 Figure 5-1 Networking diagram of connecting routers using the POS interface through FR network................5-9 Figure 6-1 Networking diagram of the HDLC functions...................................................................................6-14 Figure 6-2 Networking diagram of the HDLC basic function...........................................................................6-16 Figure 6-3 Configuring an IP-Trunk..................................................................................................................6-18 Figure 7-1 Networking diagram for IPoA configuration...................................................................................7-38 Figure 7-2 Networking diagram for ATM OAM configuration.........................................................................7-41 Figure 7-3 Networking diagram of IMAoPSN configurations..........................................................................7-45 Figure 8-1 Stack protocol of 1483B.....................................................................................................................8-2 Figure 8-2 Networking diagram of IPoEoA configuration..................................................................................8-7 Figure 8-3 Networking diagram of ATM bridged Ethernet.................................................................................8-9 Figure 8-4 Networking diagram of IPoEoA configuration................................................................................8-12
Issue 03 (2010-03-31)
xvii
Tables
Tables
Table 1-1 Index modes of the synchronous serial interface.................................................................................1-2 Table 3-1 Relationship between common transmission rates of SONET and SDH............................................3-2 Table 3-2 Link layer conditions of the E1/T1/E3/T3 supported by the NE80E/40E...........................................3-8 Table 3-3 Working modes of the E1/T1/E3/T3 channels supported by the NE80E/40E.....................................3-9
Issue 03 (2010-03-31)
xix
1 Serial Interface Configuration
1
About This Chapter
Serial Interface Configuration
This chapter describes the physical attributes and configuration procedures of synchronous serial interfaces. 1.1 Introduction to the Serial Interface Describes the basic concepts and features of serial interfaces supported by the NE80E/40E. 1.2 Configuring the Link Layer Attributes for a Serial Interface Describes how to configure link layer attributes for a serial interface. 1.3 Maintaining Serial Interface Configuration Describes how to maintain serial interfaces.
Issue 03 (2010-03-31)
1-1
1.1 Introduction to the Serial Interface

Describes the basic concepts and features of serial interfaces supported by the NE80E/40E. 1.1.1 Overview of the Synchronous Serial Interface 1.1.2 Features of the Synchronous Serial Interface on the NE80E/40E
1.1.1 Overview of the Synchronous Serial Interface

A serial interface is one of the most commonly used WAN interfaces. It can be classified into synchronous serial interfaces and asynchronous serial interfaces. At present, synchronous serial interfaces are widely used. Serial interfaces in this chapter refer to synchronous serial interfaces unless otherwise specified. The serial interfaces, which are channelized by E-carrier, T-carrier, and 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

On the NE80E/40E, various synchronous serial interfaces formed by channelizing physical interfaces support the configuration of the MTU and link layer protocols. Table 1-1 shows the index modes of synchronous serial interfaces. Table 1-1 Index modes of the synchronous serial interface Physical Interface E1/T1 channelized by CPOS E3/T3 channelized by CPOS CE1 and CT1 E3 and CT3 Index Mode slot/card/port/channel:0 or slot/card/port/channel:channel-set slot/card/port/channel:0 slot/card/port:channel-set or slot/card/port:0 slot/card/port/0:0 or slot/card/port/channel:0 or slot/card/port/ channel:channel-set
1.2 Configuring the Link Layer Attributes for a Serial Interface

Describes how to configure link layer attributes for a serial interface. 1.2.1 Establishing the Configuration Task 1.2.2 Configuring Link Layer Protocol Type 1.2.3 Configuring Hold-Interval of the Link Layer Protocol of the Synchronous Serial Interface 1.2.4 Configuring the MTU
1-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-03-31)
The MTU of a serial interface affects the assembling and disassembling of IP packets on the interface. 1.2.5 Configuring the Parity Bit 1.2.6 Checking the Configuration
1.2.1 Establishing the Configuration Task

Applicable Environment
To configure link layer attributes for a serial interface, ensure that the link layer protocol of the serial interface is Up when it is used to bear upper layer services.
Pre-configuration Tasks
Before configuring link layer attributes for a serial interface, complete the following tasks:
l l
Powering on and starting the router normally Connecting the serial interface, configuring physical parameters for the interface, and ensuring that the physical layer of the interface is Up
Data Preparation
To configure link layer attributes for a serial interface, you need the following data. No. 1 2 3 4 5 Data Number of the synchronous serial interface on the router Link layer protocol type of the interface Hold-interval of the link layer protocol MTU of the interface Check bit of CRC of the interface
1.2.2 Configuring Link Layer Protocol Type

Context
The type of link layer protocols affects the format of link layer frames of the data that passes from the synchronous serial interface. For detailed configurations of each link layer protocol, refer to the chapters PPP and MP Configuration, ATM Configuration, FR Configuration, and HDLC and IP-Trunk Configuration. Do as follows on the routers:
Issue 03 (2010-03-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-3
Procedure
Step 1 Run:
system-view
The system view is displayed. Step 2 Run:

interface serial interface-number
The serial interface view is displayed. Step 3 Run:

link-protocol { atm | fr | hdlc | ppp | tdm }
The type of link layer protocols is configured on the interface. By default, PPP is adopted as the link layer protocol.
NOTE
The link layer protocol can be configured as ATM or TDM only on CE1 interfaces and synchronization serial interfaces channelized from CPOS interfaces. You can create a PW tunnel on an interface with the link layer protocol being TDM. For specific configurations, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.
NOTE
The link layer protocol can be configured as ATM or TDM only on CE1 interfaces and synchronization serial interfaces channelized from CPOS interfaces. You can create a PW tunnel on an interface with the link layer protocol being TDM. For specific configurations, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN. A synchronous serial interface formed by E3 and CT3 interfaces supports only PPP and HDLC as link layer protocols.
----End
1.2.3 Configuring Hold-Interval of the Link Layer Protocol of the Synchronous Serial Interface
Context
Do as follows on the routers:
Procedure
Step 1 Run:
system-view

The synchronous serial interface view is displayed. Step 3 Run:

timer hold hold-interval
1-4
Issue 03 (2010-03-31)
The hold-interval of the link layer protocol is configured. Both ends of a link send detection packets to each other to detect and maintain the connectivity of the link. By default, the hold-interval of the link layer protocol is 10 seconds. If the hold-interval is configured as 0, it means that the detection packets are no longer sent or detected. ----End
1.2.4 Configuring the MTU

The MTU of a serial interface affects the assembling and disassembling of IP packets on the interface.
Procedure
Step 1 Run:
system-view


mtu mtu
The MTU is configured for a serial interface. ----End
1.2.5 Configuring the Parity Bit

Context
Procedure
Step 1 Run:
system-view

The synchronous serial interface view is displayed. Step 3 Run:

crc { 16 | 32 }
The CRC check word length of the synchronous serial interface is configured.
When configuring the check word length of CRC on a synchronous serial interface, ensure that the configurations on the devices at both ends are consistent. By default, the length of a CRC check word is 32 bits. ----End
1.2.6 Checking the Configuration

Procedure
l l l Run the display interface serial [ interface-number ] [ | { begin | exclude | include } regular-expression ] command to check the status and statistics of a serial interface. Run the display interface brief [ | { begin | include | exclude } regular-expression ] command to check the brief information about a serial interface. Run the display ip interface brief serial interface-number command to check Check the network layer configuration of a serial interface.
----End
Example
Run the following commands to check the previous configuration. Action Check the status and statistics of a serial interface. Check the brief information about a serial interface. Check the network layer configuration of a serial interface. Command display interface serial [ interface-number ] [ | { begin | exclude | include } regular-expression ] display interface brief [ | { begin | include | exclude } regular-expression ] display ip interface brief serial interface-number
Run the display interface serial command. You can view the status and statistics of the serial interface. For example:
<HUAWEI> display interface serial 1/0/0/1:0 Serial1/0/0/1:0 current state : UP Line protocol current state : UP Last line protocol up time : 2009-01-20 15:55:16 Description: Serial1/0/0/1:0 Interface Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec) Derived from Cpos1/0/0 t1 1, Timeslot(s) Used: 0-23, baudrate is 1536000 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
1-6
Issue 03 (2010-03-31)
Input: 33 packets, 426 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 30 packets, 372 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
Run the display interface brief [ | { begin | include | exclude } regular-expression ] command. You can view the brief information, including the physical status of the serial interface, status of the link protocol, bandwidth utilization, and the number of errored 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 outErrors Serial1/0/0:0 up down 0.01% 0%
inErrors 599493799 0
Run the display ip interface brief command. You can view the IP configuration of the interface. For example:
<HUAWEI> display ip interface brief serial 1/0/0:0 *down: administratively down !down: FIB overload down (l): loopback (s): 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 Aux0/0/1 GigabitEthernet0/0/0 Serial1/0/0:0 IP Address/Mask unassigned 1.1.1.2/24 10.1.1.1/24 Physical *down up up Protocol down up up
1.3 Maintaining Serial Interface Configuration

Describes how to maintain serial interfaces. 1.3.1 Clearing the Interface Statistics
1.3.1 Clearing the Interface Statistics

Context
CAUTION
The statistics cannot be restored after you clear it. So, confirm the action before you use the command. To clear the interface statistics in the Network Management System (NMS) or those displayed by running the display interface command, run the following commands in the user view.

NOTE
For the display of interface statistics in the NMS, refer to related NMS manuals.
Procedure
l l Run the reset counters interface [ serial [ interface-number ] ] command to clear the interface statistics displayed by running the display interface command. Run the reset counters if-mib interface [ serial [ interface-number ] ] command to clear the interface statistics in the NMS.
----End
1-8
Issue 03 (2010-03-31)
2 E-Carrier and T-Carrier Interface Configuration
E-Carrier and T-Carrier Interface Configuration
About This Chapter

Describes the basic concepts, configuration procedures, and configuration examples of E-Carrier and T-Carrier interfaces. 2.1 Introduction to the E-Carrier and T-Carrier Interface Describes the fundamentals and concepts of E-Carrier and T-Carrier interfaces. 2.2 Configuring CE1 Interfaces Describes how to configure CE1 interfaces. 2.3 Configuring CT1 Interfaces Describes how to configure CT1 interfaces. 2.4 Configuring E3 Interfaces Describes how to configure E3 interfaces. 2.5 Configuring CT3 Interfaces Describes how to configure CT3 interfaces. 2.6 Configuring a T1 Channel of CT3 Interfaces Describes how to configure a T1 channel of a CT3 interface. 2.7 Maintaining E-Carrier and T-Carrier Interface Configuration Describes how to maintain E-Carrier and T-Carrier interfaces. 2.8 Configuration Examples Provides a configuration example of the E3 interface.
Issue 03 (2010-03-31)
2-1
2.1 Introduction to the E-Carrier and T-Carrier Interface

Describes the fundamentals and concepts of E-Carrier and T-Carrier interfaces. 2.1.1 E-Carrier and T-Carrier Overview 2.1.2 Features of E-Carrier and T-Carrier Interfaces in the NE80E/40E
2.1.1 E-Carrier and T-Carrier Overview

Basic Concepts of E-Carrier and T-Carrier
The present digital transmission system adopts Pulse Code Modulation (PCM). PCM was initially designed to enable a trunk line among telephone exchanges to transfer multiple telephones. PCM has the following mutually incompatible international standards:
l
European 30-channel PCM is called E1. 30 channels indicate that E1 has 32 timeslots, in which 30 timeslots are used to transmit data. Timeslot 0 is used to transmit frame synchronization and warning signals. Timeslot 15 is used to transmit control signaling. The rate of E1 is 2.048 Mbit/s. E1 supported by the NE80E/40E is 31-channel PCM. Timeslot 15 also transmits data. The 24-channel PCM of North America is called T1. 24 channels indicate that T1 has 24 timeslots that can be used to transmit data. The rate of T1 is 1.544 Mbit/s.
E-carrier is a digital communication system recommended by International Telecommunication Union-Telecommunication Standardization Sector (ITU-T). It starts from E1 and has been applied in regions except North America. The American National Standards Institute (ANSI) set up the T-carrier system standard in the T1.107 Specification. The standard starts from T1 and has been widely applied in North American region. Similar to T1, Japan's J1 also belongs to the T-carrier system standard. The primary features of T-carrier and E-carrier are mostly the same although they differ in details of the protocols used by them.
Digital Carrier System

With the carrier system, a single physical communication channel can contain multiple logical channels. Therefore, it 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

The operation mode of E-carrier and T-carrier interfaces involves the following concepts:
l
Channelized: In framed mode, all timeslots except the frame header in data stream can be allocated to different channels. Unchannelized: In framed mode, all timeslots except the frame header in data stream are allocated to only one channel and are bound only once.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-03-31)
2-2

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

When a physical interface formed by E1 works in clear channel mode or channelized mode only, this interface is called a CE1 interface. A CE1 interface has the following characteristics:
l
In clear channelized mode, also called the unframed mode, the CE1 interface functions like an interface with no divided timeslot and the data bandwidth of 2.048 Mbit/s. It has the same logical features as a synchronous serial interface, supporting network protocols such as IP, link layer protocols such as PPP, HDLC and MP binding. In channelized mode, also called the framed mode, the CE1 interface is physically divided into 32 timeslots numbered from 0 to 31, which can be freely bound into a logical channel of N x 64 kbit/s. Each bound channel-set of timeslots is used as an interface with the same logical features as a synchronous serial interface, supporting network protocols such as IP, link layer protocols such as PPP, HDLC, ATM, TDM and MP binding.
Introduction to CT1 Interfaces

When a physical interface formed by T1 works in clear channel mode or channelized mode only, this interface is called a CT1 interface. A CT1 interface has the following characteristics:
l
In clear channelized mode, also called the unframed mode, the CT1 interface functions like an interface with no divided timeslot and the data bandwidth of 1.544 Mbit/s. The interface has the same logical features as a synchronous serial interface, supporting network protocols such as IP, link layer protocols such as PPP, HDLC and MP binding. In channelized mode, also called the framed mode, the CT1 interface is physically divided into 24 timeslots numbered from 0 to 23, which can be freely bound into a logical channel of N x 64 kbit/s. When being used as CT1 mode, all timeslots can be freely divided into several channelsets. Each bound channel-set of timeslots is used as an interface with the same logical features as a synchronous serial interface, supporting network protocols such as IP, link layer protocols such as PPP, HDLC and MP binding.
Introduction to E3 Interfaces
An E3 interface has two working modes:
l
In clear channelized mode, also called the unframed mode, the E3 interface functions like an interface with no divided timeslot and the data bandwidth of 34.368 Mbit/s. When the E3 interface works in unchannelized mode, a type of the framed mode, data is transmitted in the channel in the form of frames. All timeslots are bound to form a channel that functions as an interface with the data bandwidth of 33.831 M without timeslot division. The logical feature of the channel is the same as that of a synchronous serial interface.
An E3 interface supports network protocols such as IP and link layer protocols such as PPP and HDLC.
Introduction to CT3 Interfaces

A CT3 interface has three working modes:
l
In clear channelized mode, also called the unframed mode, the CT3 interface functions like an interface with no divided timeslot and the data bandwidth of 44.736 Mbit/s. When the CT3 interface works in unchannelized mode, one type of the framed mode, data is transmitted in the channel in the form of frames. All timeslots are bound to form a channel that functions as an interface with the data bandwidth of 44.210 M without timeslot division. The logical feature of the channel is the same as that of a synchronous serial interface. When working in channelized mode, the other type of the framed mode, a CT3 interface can multiplex or demultiplex 28 T1 signals. Each T1 can be configured separately. Each serial interface can function as an interface whose logical feature is the same as that 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

Types of E-Carrier and T-Carrier Interfaces
The E-carrier interface types supported by the NE80E/40E are as follows:
l l
CE1 interfaces E3 interfaces
The T-carrier interface types supported by the NE80E/40E are as follows:

l l
CT1 interfaces CT3 interfaces
Introduction to the Channelized Serial Interface

The serial interface formed by the E-carrier or T-carrier interface is called the channelized serial interface. A channelized serial interface has the same logical features as a synchronous serial interface. The method of configuring link layer attributes of a channelized serial interface is the same as that of a synchronous serial interface. For details, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - Serial Interface Configuration.
2.2 Configuring CE1 Interfaces

Describes how to configure CE1 interfaces. 2.2.1 Establishing the Configuration Task 2.2.2 Creating Synchronous Serial Interface for CE1 Interface 2.2.3 Configuring Coding or Decoding Format of CE1 Interface
2.2.4 Configuring Clock Mode of CE1 Interface 2.2.5 Configuring Frame Format of the CE1 Interface 2.2.6 Checking the Configuration

An CE1 interface should be configured when it bears upper layer services.
CAUTION
l
When a physical interface is not installed with any cable, run the shutdown command to disable this interface to avoid interference. After configuring the interface service, run the shutdown and undo shutdown commands in the current interface view to ensure that the configured service is loaded to the interface successfully. Disabling the CE1 interface may affect the normal operation of its channel-set.
Before configuring CE1 interfaces, complete the following task:
l
Powering on the router and starting it normally
Data Preparation
To configure CE1 interfaces, you need the following data. No. 1 2 3 Data CE1 interface number of the router Number of the channel into which the timeslots of the CE1 interface are bound Number or range of the timeslot bound into a channel set
2.2.2 Creating Synchronous Serial Interface for CE1 Interface

Context
Create the synchronous serial interface with the specific rate on a CE1 interface:
l
When the CE1 interface works in clear channel mode, a synchronous serial interface can be configured for the CE1 interface. The synchronous serial interface transmits data in the speed of 2.048 Mbit/s, without timeslot division.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-5
Issue 03 (2010-03-31)

l
When the CE1 interface works in channelized mode, timeslots 1 to 31 of the CE1 interface can be randomly bound together to function as one or multiple logical channels, that is, synchronous serial interfaces, with the rate of each interface calculated as N x 64 kbit/s. N stands for the number of timeslots.
NOTE
By default, a CE1 interface works in channelized mode.
Procedure
l Create the synchronous serial interface in clear channel mode. 1. Run:
system-view
The system view is displayed. 2. Run:

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

using e1
The CE1 interface is configured to the clear channel mode, and then a synchronous serial interface is configured for the CE1 interface. The synchronous serial interface transmits data in the speed of 2.048 Mbit/s, without timeslot division. You can run the interface serial controller-number: 0 command to access the synchronous serial interface. l Create the synchronous serial interface in channelized mode. 1. Run:
system-view

The CE1 interface view is displayed. 3. Run:

using ce1
The CE1 interface is configured to the channelized mode. 4. Run:

channel-set set-number timeslot-list { ts0 | slot-list [ ts0 ] }
The timeslots of the CE1 interface are bound together to function as a synchronous serial interface with the rate as N x 64 kbit/s. N stands for the number of bound timeslots. 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, you need delete all configurations in CE1 mode and all synchronous serial interfaces, and then run the using e1 command.
2-6
To change an interface from the E1 mode to the CE1 mode, you need delete all the configurations in E1 mode and all the configurations of synchronous serial interfaces, but need not delete these interfaces. Then you can run the using ce1 orundo using command.
In channelized mode, timeslot 0 alone can be bound to form a serial interface; timeslots 0 to 31 can also be randomly bound to form one or multiple serial interfaces. In this case, timeslot 0 needs to be specified in the command as the parameter ts0. Timeslot 0 is used to transmit frame synchronization and alarm information. After timeslot 0 is bound to form a serial interface, frame synchronization and alarm information can be transparently transmitted between the client and the server through the serial interface. ----End
2.2.3 Configuring Coding or Decoding Format of CE1 Interface

Context
An CE1 interface supports the following coding or decoding formats:
l l
AMI format: Alternate Mark Inversion HDB3 format: High Density Bipolar of Order 3
Procedure
Step 1 Run:
system-view

The CE1 interface view is displayed. Step 3 Run:

code { ami | hdb3 }
The coding or decoding format of the CE1 interface is configured. By default,a CE1 interface works in HDB3 coding or decoding format. ----End
2.2.4 Configuring Clock Mode of CE1 Interface

Context
A CE1 interface supports the following clock modes:
l l
Master clock mode: uses internal clock signals. Slave clock mode: uses line clock signals.
Issue 03 (2010-03-31)
When CE1 interfaces of two routers are connected directly, configure one interface to work in master clock mode and the other interface in slave clock mode. When the CE1 interface of a router is connected with a transmission device, configure this interface to work in slave clock mode and use the clock signals provided by the transmission device. Do as follows on the routers:
Procedure
Step 1 Run:
system-view


clock { master | slave }
Clock mode of the CE1 interface is configured.

NOTE
When being used as a synchronous serial interface, the CE1 interface also has two working modes: DTE and DCE. In this case, you need to choose the clock mode.
By default, a CE1 interface works in master clock mode. ----End
2.2.5 Configuring Frame Format of the CE1 Interface

Context
The interface can be configured with the frame format only when it works in channelized mode. Do as follows on the routers:
Procedure
Step 1 Run:
system-view

controller e1controller-number

frame-format { crc4 | no-crc4 }
The frame format of the CE1 interface is configured.


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

Procedure
l l Run the display interface serial [ interface-number ] [ | { begin | exclude | include } regular-expression ] command to check the configuration and status of the channel-set. Run the display controller e1 [ controller-number ] command to check the configuration and status of the CE1 interface.
----End
Example
Run the display interface serial command. You can view the configuration of the channel-set and status of the CE1 interface.
<HUAWEI> display interface serial 1/0/0:2 Serial1/0/0:2 current state : UP Line protocol current state : UP Last line protocol up time : 2009-01-20 15:55:16 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 Link layer protocol is PPP LCP opened 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 controller e1 command. You can view the configuration and status information of the CE1 interface.
<HUAWEI> display controller e1 1/0/0 E1 1/0/0 current state : DOWN Description : E1 1/0/0 Interface Physical layer is Packet Over NO-CRC4 clock master, linecode hdb3 , loopback none section layer: alarm: LOS line layer: alarm: none path layer: alarm: none
Issue 03 (2010-03-31)
2-9
2.3 Configuring CT1 Interfaces

Describes how to configure CT1 interfaces. 2.3.1 Establishing the Configuration Task 2.3.2 Creating Synchronous Serial Interface for CT1 Interface 2.3.3 Configuring Coding or Decoding Format of the CT1 Interface 2.3.4 Configuring Clock Mode of the CT1 Interface 2.3.5 Configuring Frame Format of the CT1 Interface 2.3.6 Checking the Configuration

A CT1 interface needs to be configured when it bears upper layer services.
CAUTION
l
When a physical interface is not installed with any cable, run the shutdown command to disable this interface to avoid interference. After configuring the interface service, run the shutdown and the undo shutdowncommands in the current interface view to ensure that the configured service is loaded to the interface successfully. Disabling the CT1 interface may affect the normal operation of its channel-set.
Before configuring CT1 interfaces, complete the following task:
l
Data Preparation
To configure a CT1 interface, you need the following data. No. 1 2 3 Data CT1 interface number of the router Number of the channel into which the timeslots of the CT1 interface timeslot are bound Number or range of the timeslot bound into a channel-set
2-10
Issue 03 (2010-03-31)
2.3.2 Creating Synchronous Serial Interface for CT1 Interface

Context
Create the synchronous serial interface with the specific rate on a CT1 interface:
l
When the CT1 interface works in clear channel mode, a synchronous serial interface can be configured on the CT1 interface. The synchronous serial interface transmits data in the speed of 1.544 Mbit/s, without timeslot division. When the CT1 interface works in channelized mode, timeslots 0 to 23 of the CT1 interface can be randomly bound together to function as one or several logical channels, that is, synchronous serial interfaces, with the rate of each interface calculated as N x 64 kbit/s. N stands for the number of timeslots.
Procedure
l Create the synchronous serial interface in clear channel mode. 1. Run:
system-view

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

using t1
The CT1 interface is configured to the clear channel mode, and then a synchronous serial interface is configured for the CT1 interface. The synchronous serial interface transmits data in the speed of 1.544Mbit/s, without timeslot division. You can run the interface serial controller-number:0 command to access the synchronous serial interface. l Create the synchronous serial interface in channelized mode. 1. Run:
system-view


using ct1
The CT1 interface is configured to the channelized mode. 4. Run:

channel-set set-number timeslot-list slot-list
The timeslots of the CT1 interface are bound together to function as a synchronous serial interface with the rate as N x 64 kbit/s. N stands for the number of bound timeslots.
You can run the interface serial controller-number:set-number command to access the synchronous serial interface.
To change an interface from the CT1 mode to the T1 mode, you need delete all configurations in CT1 mode and all synchronous serial interfaces, and then run the using t1 command. To change an interface from the T1 mode to the CT1 mode, you need delete all the configurations in T1 mode and all the configurations of synchronous serial interfaces, but need not delete these interfaces. Then you can run the using t1 command.
----End
2.3.3 Configuring Coding or Decoding Format of the CT1 Interface

Context
A CT1 supports the following coding or decoding formats:
l l
AMI: Alternate Mark Inversion B8ZS: Bipolar with 8-Zero Substitution
Procedure
Step 1 Run:
system-view

The CT1 interface view is displayed. Step 3 Run:

code { ami | b8zs }
The coding or decoding format of the CT1 interface is configured. By default, b8zs is used on CT1 interface. ----End
2.3.4 Configuring Clock Mode of the CT1 Interface

Context
A CT1 interface supports the following clock modes:
l l
When a CT1 interface is used as the DCE device, configure the CT1 interface to work in master clock mode. Configure the CT1 interface to work in slave clock mode when it is used as the
DTE device. When CT1 interfaces of two routers are connected directly, configure one interface to work in master clock mode and the other interface in slave clock mode. Do as follows on the routers:
Procedure
Step 1 Run:
system-view


The clock mode of the CT1 interface is configured. ----End
2.3.5 Configuring Frame Format of the CT1 Interface

Context
A CT1 interface supports the following frame formats:
l l
ESF: Extended Super Frame SF: Super Frame
Procedure
Step 1 Run:
system-view


frame-format { esf | sf }
Frame format of the CT1 interface is configured. By default, the frame format of the CT1 interface is ESF. ----End

Procedure
l Run the display interface serial [interface-number ] [ | { begin | exclude | include } regular-expression ] command to check the status and statistics of the serial interface bound by timeslots. Run the display controller t1 [ controller-number ] command to check configuration and status of the CT1 interface.
----End
Example
Run the display interface serial command. You can view the information about the channelset configuration and interface status.
<HUAWEI> display interface serial 1/0/0:2 Serial1/0/0:2 current state : UP Line protocol current state : UP Last line protocol up time : 2009-01-20 15:55:16 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 Internet protocol processing : disabled Link layer protocol is PPP LCP opened Physical layer is Channelized T1 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 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 30 packets, 372 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
Run the display controller t1 command. You can view the information about the coding format, frame format and clock mode of the CT1 interface.
<HUAWEI> display controller t1 1/0/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,workmode:CT1
2.4 Configuring E3 Interfaces

Describes how to configure E3 interfaces. 2.4.1 Establishing the Configuration Task 2.4.2 Creating Synchronous Serial Interface for E3 Interface 2.4.3 Checking the Configuration

A E3 interface needs to be configured when it bears upper layer services.
CAUTION
l
When a physical interface is not installed with any cable, run the shutdown command to disable this interface to avoid interference. After configuring the interface service, run the shutdown and the undo shutdown commands in current interface view to ensure that the configured service is loaded to the interface successfully. Disabling or enabling a E3 interface is valid on the CE3 channel and the serial interface formed by the E3 interface.
Before configuring E3 interfaces, complete the following task:
l
Data Preparation
To configure E3 interfaces, you need the following data. No. 1 Data E3 interface number of the router
2.4.2 Creating Synchronous Serial Interface for E3 Interface

Context
E3 interfaces work in either of the following modes:
l
Clear channel mode (also known as E3 mode) When a E3 interface is configured to work in clear channel mode, a synchronous serial interface that operates at 34.368 Mbit/s is generated and named serial slot/card/port/0:0.
Unchannelized mode (also known as CE3 mode) When a E3 interface is configured to work in unchannelized mode, a framed E3 channel must be manually created to form a synchronous serial interface named serial slot/card/ port/0:0.
By default, a E3 interface works in unchannelized mode. Do as follows on routers:

Procedure
l Configure a E3 interface to work in clear channel mode. 1. Run:
system-view

The E3 interface view is displayed. 3. Run:

using e3
The E3 interface is configured to work in clear channel mode. l Configure a E3 interface to work in unchannelized mode. 1. Run:
system-view

The E3 interface is displayed. 3. Run:

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

e3 framed
A framed E3 channel is created. Then a synchronous serial interface is generated and named serial slot/card/port/0:0. ----End

Procedure
Step 1 Run the display controller e3 [ controller-number ] command to check the status of the E3 interface. ----End
Example
Run the display controller e3 command. You can view the clock mode and frame format of the E3 interface.
<HUAWEI> display controller e3 6/0/0 E3 6/0/0 current state : UP Description : E3 6/0/0 Interface Physical layer is Packet Over G.751, clock master, loopback local section layer:
2-16
Issue 03 (2010-03-31)

alarm: none line layer: alarm: none path layer: alarm: none
2.5 Configuring CT3 Interfaces

Describes how to configure CT3 interfaces. 2.5.1 Establishing the Configuration Task 2.5.2 Creating Synchronous Serial Interface for CT3 Interface 2.5.3 Configuring Frame Format of the CT3 Interface T1 corresponds to the digital signal level DS-1. With bit multiplexing, 28 T1s form T3. Two frame formats are used: C-bit and M23. 2.5.4 Checking the Configuration

A CT3 interface needs to be configured when it bears upper layer services.
CAUTION
l
When a physical interface is not installed with any cable, run the shutdown command to disable this interface to avoid interference. After configuring the interface service, run the shutdown and undo shutdown commands in the current interface view to ensure that the configured service is loaded to the interface successfully. Disabling or enabling a CT3 interface is valid on the serial interface formed by the CT3 channel, the T1 channel demultiplexed by the CT3 channel, and the serial interface formed by binding the CT3 channel.
Before configuring CT3 interfaces, complete the following task:
l
Data Preparation
To configure a CT3 interface, you need the following data. No. 1 Data CT3 interface number of the router
Issue 03 (2010-03-31)
2-17
2.5.2 Creating Synchronous Serial Interface for CT3 Interface

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.
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, the T1 channel without timeslot division forms a 1.544 Mbit/s serial interface. When a T1 channel works in channelized mode, timeslots 0 to 23 of a T1 channel can be randomly bound to form a serial interface. The default rate of the channelset that is formed by binding T1 timeslots is N x 64 kbit/s (N represents the number of timeslots that are bound).
By default, a CT3 interface works in channelized mode. Do as follows on routers:
Procedure
l Configure a CT3 interface to work in clear channel mode. 1. Run:
system-view


using t3
The CT3 interface is configured to work in clear channel mode. Then a synchronous serial interface can be configured for the CT3 interface. The synchronous serial interface transmits data in the speed of 44.736 Mbit/s, without timeslot division. You can run the interface serial controller-number:0 command to access the synchronous serial interface. l Configure a CT3 interface to work in unchannelized mode. 1. Run:
system-view
The system view is displayed.

2.
Run:

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

t3 framed
A framed T3 channel is created. Then a synchronous serial interface can be configured for the CT3 interface. You can run the interface serial controller-number:0 command to access the synchronous serial interface. l Configure a CT3 interface to work in channelized mode. 1. Run:
system-view


using ct3
The CT3 interface is configured to work in framed mode. 4. Run either of the following commands to create the synchronous serial interface of the T1 channel.
Run the t1 t1-number unframed command to create the synchronous serial interface with the rate as 1.544 Mbit/s. You can run the interface serial controller-number/t1-number:0 command to access the synchronous serial interface.
Run the t1 t1-number channel-set set-number timeslot-list slot-list command to bind N timeslots of the T1 channel of the CT3 interface together to create a synchronous serial interface with the rate as N x 64kbit/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

T1 corresponds to the digital signal level DS-1. With bit multiplexing, 28 T1s form T3. Two frame formats are used: C-bit and M23.
Context
l
C-bit is also called the C-bit parity check. When C-bit is set, the stuffing indication bit can be used for maintenance.
Issue 03 (2010-03-31)

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


frame-format { c-bit | m23 }
Frame format of the CT3 interface is configured. ----End

Procedure
l l Run the display controller t3 [ controller-number ] command to check the status of the CT3 interface. 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 of the CT3 interface.
<HUAWEI> display controller t3 1/0/0 T3 1/0/0 current state : Administratively DOWN Description : T3 1/0/0 Interface Physical layer is Packet Over C-Bit, clock master, loopback none section layer: alarm: OOF LOF line layer: alarm: none path layer: alarm: none
Run the display interface serial command. You can view the status of the serial interface.
<HUAWEI> display interface serial 1/0/0/0:0 Serial1/0/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:0 Interface Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec) Derived from T3 1/0/0, Unchannelized mode, baudrate is 44210000 bps Internet protocol processing : disabled Link layer protocol is PPP
2-20
Issue 03 (2010-03-31)
LCP opened clock slave, loopback none CRC: CRC-16 Scramble disabled Statistics last cleared:2008-08-27 16:42:19 Traffic statistics: Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
2.6 Configuring a T1 Channel of CT3 Interfaces

Describes how to configure a T1 channel of a CT3 interface. 2.6.1 Establishing the Configuration Task 2.6.2 Configuring Clock Mode of a T1 Channel 2.6.3 Configuring Frame Format of a T1 Channel 2.6.4 Checking the Configuration

Before using a CT3 interface to bear upper layer services, you need to configure parameters for the CT3 interface. When a CT3 interface works in channelized mode, the T1 channels on the CT3 interface need to be configured.
Before configuring a T1 channel on the CT3 interface, complete the following tasks:
l l l
Powering on the router and starting it normally Connecting the CT3 interface and configuring physical attributes for the CT3 interface Connecting the CT3 interface to work in the channelized mode
Data Preparation
To configure a T1 channel of the CT3 interface, you need the following data. No. 1 2 3 Data CT3 interface number of the router T1 channel number Timeslot number, timeslot range, or number of the channel of the T1 interface
Issue 03 (2010-03-31)
2-21
2.6.2 Configuring Clock Mode of a T1 Channel

Context
A T1 interface supports the following clock modes:
l l
The selection of the clock mode depends on the connected peer device. When a T1 interface is connected to a transmission device, configure the T1 interface to work in slave clock mode. If the CT3 interfaces of two routers are directly connected, configure one interface to work in master clock mode and the other interface in slave clock mode. By default, the CT3 interface works in master clock mode. Do as follows on the routers:
Procedure
Step 1 Run:
system-view


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

Context
A T1 channel supports the following frame formats:
l l
ESF: Extended Super Frame SF: Super Frame
By default, a T1 channel uses ESF. Do as follows on the routers:
Procedure
Step 1 Run:
system-view

Step 2 Run:

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

Procedure
l l Run the display controller t3 [ controller-number ] command to check the status of the CT3 interface. 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 of the CT3 interface.
<HUAWEI> display controller t3 1/0/0 T3 1/0/0 current state : DOWN Description : T3 1/0/0 Interface Physical layer is Packet Over C-Bit, clock slave, loopback none section layer: alarm: none line layer: alarm: none path layer: alarm: none
Run the display interface serial command. You can view the status of the serial interface.
<HUAWEI> display interface serial 1/0/0/1:0 Serial1/0/0/1:0 current state : DOWN Line protocol current state : UP Last line protocol up time : 2009-01-20 15:55:16 Description:Serial1/0/0/1:0 Interface Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec) Derived from T3 1/1/0 t1 1, Timeslot(s) Used: 0-23, baudrate is 1536000 bps Internet protocol processing : disabled Link layer protocol is PPP LCP opened Physical layer is Packet Over ESF clock master, loopback none CRC: CRC-16 Scramble disabled Alarm: None Statistics last cleared:2008-08-27 16:50:02 Traffic statistics: Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket
Issue 03 (2010-03-31)
2-23
Output: 0 packets, 0 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
2.7 Maintaining E-Carrier and T-Carrier Interface Configuration

Describes how to maintain E-Carrier and T-Carrier interfaces. 2.7.1 Setting Loopback to Detect Whether the Interface Is Normal 2.7.2 Clearing the Interface Statistics
2.7.1 Setting Loopback to Detect Whether the Interface Is Normal

Context
CAUTION
After you configure the self-loop (run the loopback command), the interface on a router or the link cannot run normally. Thus, you must check whether to set the self-loop. After the detection, run the undo loopback command to disable the self-loop. Do as follows on the routers to be detected:
Procedure
Step 1 Run:
system-view

controller controller-type controller-number
The view of the interface to be detected is displayed. Step 3 According to the interface type, choose one of the following commands to enable the self-loop.
l
In the case of an CE1, CT1, E3 or CT3 interface, run the loopback { local | remote } command. When configuring the loopback of an interface, note the following:
To enable the local loopback of the interface, the interface must be in the master clock mode. To enable the remote loopback of the interface, the interface must be in the slave clock mode.
In the case of the T1 channel of the CT3 interface, run the t1 t1-number set loopback { local | remote }
By default, the self-loop is disabled on the interface. ----End


Context
CAUTION
The interface statistics cannot be restored after you run the reset command to clear it. So, confirm the action before you use the command. To reset the interface statistics of the Network Management System (NMS) or those displayed by running the display interface command, run the following commands in the user view. Clear the interface statistics before collecting the traffic.
NOTE
For the interface statistics in the NMS, refer to related NMS manuals.
Procedure
l l Run the reset counters interface [ interface-type [ interface-number ] ] command to clear the interface statistics displayed by running the display interface command. Run the reset counters if-mib interface [ interface-type [ interface-number ] ] command to clear the interface statistics in the NMS.
----End
2.8 Configuration Examples

Provides a configuration example of the E3 interface. 2.8.1 Example for Configuring Communication over CE1 Interfaces Bundle
2.8.1 Example for Configuring Communication over CE1 Interfaces Bundle

Networking Requirements
Two routers connect with each other through two CE1 links and communicate with each other by bundling these CE1 links. Figure 2-1 Schematic diagram of CE1 interface configuration
RouterA
CE1 4/0/0 Link bundling CE1 4/0/1
RouterB CE1 4/0/0 CE1 4/0/1
Issue 03 (2010-03-31)
2-25
Configuration Roadmap
The configuration roadmap is as follows: 1. 2. 3. 4. Configure a CE1 interface channel. Create an interface to be bound. Add the interface channel to the bound interface. Configure the IP address of the bound interface and re-enabling it.
Data Preparation
To configure a CE1 interface, you need the following data:
l l l l
Name of the bound interface IP address of the bound interface Index number of the interface when the timeslots of the CE1 interface are bound Number and range of the timeslots to be bound
NOTE
On the NE80E/40E, the slot ID and the card ID of the interfaces added to the MP-group must be consistent with the slot ID and card ID of the MP-group interface. That is, the trans-card binding is not supported. The interfaces added to the MP-group can only be the serial interfaces instead of other interfaces.
Procedure
Step 1 Configure Router A. # Configure the working mode and channel group of CE1.
<HUAWEI> system-view [HUAWEI] sysname RouterA [RouterA] controller e1 4/0/0 [RouterA-E1 4/0/0] shutdown [RouterA-E1 4/0/0] channel-set 0 timeslot-list 1-31 [RouterA-E1 4/0/0] undo shutdown [RouterA-E1 4/0/0] quit [RouterA] controller e1 4/0/1 [RouterA-E1 4/0/1] shutdown [RouterA-E1 4/0/1] channel-set 0 timeslot-list 1-31 [RouterA-E1 4/0/1] undo shutdown [RouterA-E1 4/0/1] quit
# Create a bound interface.

[RouterA] interface mp-group 4/0/1 [RouterA-Mp-group4/0/1] shutdown [RouterA-Mp-group4/0/1] quit
# Add the CE1 channel to the binding group.

[RouterA] interface serial 4/0/0:0 [RouterA-Serial4/0/0:0] shutdown [RouterA-Serial4/0/0:0] ppp mp mp-group 4/0/1 [RouterA-Serial4/0/0:0] quit [RouterA] interface serial 4/0/1:0 [RouterA-Serial4/0/1:0] shutdown [RouterA-Serial4/0/1:0] ppp mp mp-group 4/0/1 [RouterA-Serial4/0/1:0] quit
2-26
Issue 03 (2010-03-31)
# Restart the sub-channel on Router A.

[RouterA] interface serial4/0/0:0 [RouterA-Serial4/0/0:0] undo shutdown [RouterA-Serial4/0/0:0] quit [RouterA] interface serial4/0/1:0 [RouterA-Serial4/0/1:0] undo shutdown [RouterA-Serial4/0/1:0] quit
# Configure the IP address for the bound interface and restart the interface.
[RouterA] interface mp-group 4/0/1 [RouterA-Mp-group4/0/1] ip address 5.0.0.1 255.255.255.0 [RouterA-Mp-group4/0/1] undo shutdown
Step 2 Configure Router B. # Configure the working mode and channel group of CE1.
<HUAWEI> system-view [HUAWEI] sysname RouterB [RouterB] controller e1 4/0/0 [RouterB-E1 4/0/0] shutdown [RouterB-E1 4/0/0] channel-set 0 timeslot-list 1-31 [RouterB-E1 4/0/0] undo shutdown [RouterB-E1 4/0/0] quit [RouterB] controller e1 4/0/1 [RouterB-E1 4/0/1] shutdown [RouterB-E1 4/0/1] channel-set 0 timeslot-list 1-31 [RouterB-E1 4/0/1] undo shutdown [RouterB-E1 4/0/1] quit
# Create a bound interface.

[RouterB] interface mp-group 4/0/1 [RouterB-Mp-group4/0/1] shutdown [RouterB-Mp-group4/0/1] quit
# Add tge CE1 channel to the binding group.

[RouterB] interface serial 4/0/0:0 [RouterB-Serial4/0/0:0] shutdown [RouterB-Serial4/0/0:0] ppp mp mp-group 4/0/1 [RouterB-Serial4/0/0:0] quit [RouterB] interface serial 4/0/1:0 [RouterB-Serial4/0/1:0] shutdown [RouterB-Serial4/0/1:0] ppp mp mp-group 4/0/1 [RouterB-Serial4/0/1:0] quit
# Restart the sub-channel on Router B.

[RouterB] interface serial4/0/0:0 [RouterB-Serial4/0/0:0] undo shutdown [RouterB-Serial4/0/0:0] quit [RouterB] interface serial4/0/1:0 [RouterB-Serial4/0/1:0] undo shutdown [RouterB-Serial4/0/1:0] quit
# Configure the IP address for the binding interface and restart the interface.
[RouterB] interface mp-group 4/0/1 [RouterB-Mp-group4/0/1] ip address 5.0.0.2 255.255.255.0 [RouterB-Mp-group4/0/1] undo shutdown
Step 3 Vefify the configuration. Run the display interface command to view the binding status. The link negotiation succeeds. Take Router A as an example:
<RouterA> display interface mp-group 4/0/1 Mp-group4/0/1 current state : UP Line protocol current state : UP Description: Mp-group4/0/1 Interface Route Port,The Maximum Transmit Unit is 1500 Internet Address is 5.0.0.1/24 Link layer protocol is PPP LCP opened, MP opened, IPCP opened Physical is MP, baudrate is 3968000 bps Traffic statistics: Last 300 seconds input rate 1352 bits/sec, 0 packets/sec Last 300 seconds output rate 824 bits/sec, 0 packets/sec Input: 21395674 packets, 2048796674 bytes 0 errors, 0 drops Output: 96504 packets, 3084968 bytes 0 errors, 0 drops
----End
Configuration Files
l
Configuration file of Router A

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

# sysname RouterB # controller e1 4/0/0 channel-set 0 timeslot-list 1-31 # controller e1 4/0/1 channel-set 0 timeslot-list 1-31 # interface Serial4/0/0:0 link-protocol ppp ppp mp Mp-group 4/0/1 # interface Serial4/0/1:0 link-protocol ppp ppp mp Mp-group 4/0/1 # interface Mp-group4/0/1 ip address 5.0.0.2 255.255.255.0 # return
2-28
Issue 03 (2010-03-31)
3 POS and CPOS Interface Configuration
POS and CPOS Interface Configuration
About This Chapter

Describes the basic concepts, configuration procedures, and configuration examples of Packet over SONET/SDH (POS) interfaces and Channelized POS (CPOS) interfaces. 3.1 Introduction to the POS and CPOS Interfaces Describes the basic concepts of POS interfaces and CPOS interfaces. 3.2 Configuring POS Interfaces Describes how to configure a POS interface. 3.3 Configuring STM-1 CPOS Interfaces This section describes how to configure a STM-1 CPOS interface. 3.4 Configuring E1 Channels of the CPOS Interface Describes how to configure E1 channels of CPOS interfaces. 3.5 Configuring T1 Channels of the CPOS Interface This section describes how to configure T1 channels of CPOS interfaces. 3.6 Configuring E3 Channels of an STM-1 CPOS Interface This section describes how to configure the E3 channels of the STM-1 CPOS interfaces. 3.7 Configuring T3 Channels of an STM-1 CPOS Interface This section describes how to configure T3 channels of an STM-1 CPOS interfaces. 3.8 Maintaining POS and CPOS Interface Configuration This section describes how to maintain POS interfaces and CPOS interfaces. 3.9 Configuration Examples This section provides several configuration examples of POS and CPOS interfaces.
Issue 03 (2010-03-31)
3-1
3.1 Introduction to the POS and CPOS Interfaces

Describes the basic concepts of POS interfaces and CPOS interfaces. 3.1.1 Overview of POS and CPOS Interfaces 3.1.2 Features of POS and CPOS Interfaces on the NE80E/40E
3.1.1 Overview of POS and CPOS Interfaces

Introduction to SONET and SDH
Synchronous Optical Network (SONET) is the synchronous digital transmission standard defined by the American National Standards Institute (ANSI) and mainly used in North America and Japan. Clocks at each level in an entire network are provided by a very precise master clock. SONET defines the line rate hierarchical structure of synchronous transmission for the optical transmission system. The basic transmission rate of the SONET is 51.84 Mbit/s and approximately equals the transmission rate of E3/T3.
l
For an electrical signal, the transmission rate is called Level 1 Synchronous Transport Signal, namely, STS-1. For an optical signal, the transmission rate is called Level 1 Optical Carrier, namely, OC-1.
Adopting synchronous signals, SONET can easily multiplex multiple signals. Based on SONET, Synchronous Digital Hierarchy (SDH) is an international standard defined by the ITU-T and mainly used in Europe. The corresponding standard of SDH is the proposals from G.707 to G.709 passed in 1988 and the proposals added in 1992. SDH is similar to SONET to a great extent. The basic rate of SDH is 155.52 Mbit/s, which is called Level 1 Synchronous Transfer Module, STM-1. This rate equals the OC-3 rate in SONET. Adopting synchronous multiplexing and flexible mapping, SDH can multiplex or demultiplex low-speed tributary signals from SDH signals without using multiplexing or demultiplexing devices. This reduces signal consumption and equipment investment. Table 3-1 lists the common transmission rates of SONET and SDH. The hierarchical relationship between common transmission rates is four times. For convenience, the approximations in the parentheses are often used to express transmission rates. Table 3-1 Relationship between common transmission rates of SONET and SDH SONET Electrical Signal STS-1 STS-3 STS-9
3-2
SDH Optical Signal OC-1 OC-3 OC-9 Optical Signal STM-1 STM-3
Transmission Rate (Mbit/s)
51.840 155.520 (155) 466.560

Issue 03 (2010-03-31)
SONET Electrical Signal STS-12 STS-18 STS-24 STS-36 STS-48 STS-96 STS-192 STS-768 Optical Signal OC-12 OC-18 OC-24 OC-36 OC-48 OC-96 OC-192 OC-768
SDH Optical Signal STM-4 STM-6 STM-8 STM-12 STM-16 STM-32 STM-64 STM-256
Transmission Rate (Mbit/s)
622.080 (622) 933.120 1244.160 1866.240 2488.320 (2.5 Gbit/s) 4876.640 9953.280 (10 Gbit/s) 39813.120(40Gbit/s)
Channelization and Unchannelization

When SDH signals are formed by multiplexing low-speed tributary signals, these signals are called channels. Channelization indicates that multiple independent channels of data are transmitted over an optical fiber by using low-speed tributary STM-N signals. During the 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 by using all STM-N signals. During the 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 l l l
Perform refined division of bandwidth. Reduce the demand for the quantity of low-speed physical ports on a router in networking. Enhance the convergence capability of low-speed ports of a router. 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 in the frame equably and regularly. The ITU-T 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 2 3 4 5 6 7 8 9
Regenerator Section Overhead AUPTR Payload Multiplex Section Overhead
9*N
261*N
STM-N is the 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). Administration Unit Pointer (AU-PTR): is the pointer that specifies the first byte of the payload. The receiving end can correctly extract the payload according to the location of the pointer. Payload
Terms
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. 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.
3-4

l
VC: It is used to support connections between channel layers of the SDH and is an information terminal of SDH channels. VCs are classified into lower-order VCs and higherorder VCs. VC-3 in AU-3 and VC-4 are higher-order VCs. 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 higherorder VC, is called a TUG. 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
1 STM-1 AUG-1
1 AU-4 VC-4 3 3 TUG-3
AU-3 Mapping Multiplexing Mapping
VC-3 7
7 C-12:2.048Mb/s TUG-2 3 TU-12 VC-12 C-12
Figure 3-3 Process of multiplexing T1 to STM-1
1 STM-1 AUG-1
1 AU-4 VC-4 3 3 TUG-3
AU-3 Mapping Multiplexing Mapping
VC-3 7
C-11:1.544Mb/s TU-11 VC-11 C-11
TUG-2 4
Issue 03 (2010-03-31)
3-5
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.
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 of calculating the TU number. The multiplexing process in Figure 3-2 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: VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12 number - 1) x 21 In a VC-4, all TUG-3s are numbered the same; all TUG-2s are numbered the same; the difference between two TU-12 numbers is 1. These two TU-12s are adjacent.
NOTE
l l l
The numbers listed in the preceding formula stand for the positions in a VC-4 frame. The TUG-3 number ranges from 1 to 3; the TUG-2 number ranges from 1 to 7; the TU-12 number ranges from 1 to 3. 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-4 Sequence of arrangement of TUG-3, TUG-2 and TU-12 in VC-4
1 VC-4 TUG-3
1 TUG-2
TU-12 TU-12 TU-12 TU-12
1 2 3 1 2 3 1 2 3
2 TUG-2 2 TUG-3 TU-12 3 TUG-3 7 TUG-2 TU-12 TU-12 TU-12 TU-12
3-6
Issue 03 (2010-03-31)
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 configuration. For details, refer to a 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 lowspeed 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 networks of a carrier, whereas the J0 byte of the receiver and the transmitter must match each other at the border of networks between two carriers. With the JO byte, a carrier can locate and rectify faults in advance to speed up the network recovery.
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. J1 bytes of the receiver and transmitter must match each other. C2, the path signal label byte, is contained in higher-order path overhead. C2 is used 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 the mapping mode. C2 bytes of the receiver and transmitter must match each other.
3.1.2 Features of POS and CPOS Interfaces on the NE80E/40E
Issue 03 (2010-03-31)
3-7
POS
The POS can map packets of variable length directly into the payload of SONET. The POS uses the physical layer transmission standard of SONET. 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: STM-1 (155Mbit/s), STM-4c (622Mbit/s), STM-16c (2.5Gbit/s), and STM-64c (10Gbit/s). The NE80E/40E provides various rates of POS interfaces, which can be divided into three kinds based on the rate: STM-1 (155Mbit/s), STM-4c (622Mbit/s), STM-16c (2.5Gbit/s), STM-64c (10Gbit/s), and STM-256c(40Gbit/s).
CPOS
CPOS is mainly used to improve aggregation capacity of the router on low speed access. The STM-1 CPOS is suitable for aggregating multiple E1/T1s. The physical port of the STM-1 CPOS interface is not used as a service port, it is called a controller. E1/T1/E3/T3 channels are used as synchronous serial interfaces and configured in serial interface view. The indexing method of the interface number is four-dimension index, namely, slot number/card number/port number/channel number:channel number. The STM-1 CPOS service board can provide the following channels:
l l l l
63 E1 channels (2.048M, DS-1) 84 T1 channels (1.544M, DS-1) 3 E3 channels (34.368M, DS-3) 3 T3 channels (44.736M, DS-3)
NOTE
The channelization type of STM-1 CPOS should take the specifications of the service board as the standards.
The NE80E/40E only supports the channels on the same service board to be bound to be the binding group, and the binding group is numbered from 1. The link layer protocols of the channelized E1/T1/E3/T3 are as follows: Table 3-2 Link layer conditions of the E1/T1/E3/T3 supported by the NE80E/40E Channel E1 T1 E3 T3 Link Layer Protocol PPP, HDLC PPP, HDLC PPP, HDLC PPP, HDLC MP Binding Support. Support. Not support Not support
The working modes of the E1/T1/E3/T3 channels supported by the NE80E/40E are as follows:
Table 3-3 Working modes of the E1/T1/E3/T3 channels supported by the NE80E/40E Channel Unframed Framed Unchannelized E1 The serial interface with rate 2.048Mbit/s. The serial interface with rate 1.544Mbit/s The serial interface with rate 34.368Mbit/ s The serial interface with rate 44.736Mbit/ s Not support Channelized The 31 timeslots except timeslot 0 can be bound as the serial interfaces of Nx64Kbit/s The 24 timeslots can be bound as the serial interfaces of Nx64Kbit/s Not support
T1 E3
Not support The rate is 33.831Mbit/s The rate is 44.210Mbit/s
T3
Not support
3.2 Configuring POS Interfaces

Describes how to configure a POS interface. 3.2.1 Establishing the Configuration Task 3.2.2 Configuring the Link Layer Protocol 3.2.3 Configuring Clock Mode 3.2.4 Configuring the Overhead Byte 3.2.5 Configuring Frame Format 3.2.6 Configuring the Scramble Function A POS interface supports the scrambling function for the payload data to avoid excessive consecutive 1s or 0s and facilitate line clock signal extraction for the receiver. 3.2.7 Configuring the Length of the CRC Check Character A POS interface supports two types of CRC check characters: 16 bits and 32 bits. 3.2.8 Configuring MTU The Maximum Transmission Unit (MTU) of a POS interface is used for the assembly and disassembly of the IP packets received and sent from the interface. 3.2.9 Checking the Configuration

Before using a SONET/SDH optical interface to bear packet data, you need to configure parameters for the POS interface.
Before configuring a POS interface, complete the following task:
l
Data Preparation
To configure a POS interface, you need the following data. No. 1 2 3 4 5 6 7 8 Data Number of the POS interface on the router Link layer protocol of the POS interface Clock mode of the POS interface Values of overload bytes C2, J0, and J1 Frame format of the POS interface Length of the CRC check character MTU of the POS interface Alarm threshold of the POS interface
3.2.2 Configuring the Link Layer Protocol

Context
Procedure
Step 1 Run:
system-view

interface pos interface-number
The POS interface view is displayed. Step 3 Run:

link-protocol { ppp | hdlc | fr [ ietf | nonstandard ] }
The link layer protocol of the POS interface is configured.

NOTE
The POS interface supports only the basic functions of FR P2P sub-interfaces, excluding other FR functions.
----End
3.2.3 Configuring Clock Mode

Context
A POS interface supports the following clock modes:
l l
Master clock mode: uses internal clock signal. Slave clock mode: uses line clock signal.
Similar to a synchronous serial interface working in DTE and DCE modes, a POS also works in different clock modes.
l
When the POS interfaces of two routers are connected directly or through the Wavelength Division Multiplexing (WDM) device, configure one interface to work in master clock mode and the other interface in slave clock mode to avoid link flapping. 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


Clock mode of the POS interface is configured. By default, a POS interface works in master clock mode. ----End
3.2.4 Configuring the Overhead Byte

Context
The SONET/SDH provides a variety of overhead bytes, which perform the monitoring function of different levels. The C2 (Path signal label byte) is included in higher order path overhead. C2 indicates the multiplex structure of VC frame and the property of information payload. The J0 (Regeneration section Trace Message) is included in section overhead. It is used to test the continuous connection of the two ports on the section level. The J1 (Higher-Order VC-N path trace byte) is used to test the connectivity of two interfaces.
Procedure
Step 1 Run:
system-view

The POS interface view is displayed. 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 j0value | peer }
To configure the path trace byte J1, run:

To configure path signal label byte C2, run:

flag j2 c2-value
The configuration of C2, J0 and J1 should be consistent. Otherwise an alarm is generated. For the POS interface, the default value of C2 is 22 (0x16), the default value of J0 and J1 is "NetEngine". ----End
3.2.5 Configuring Frame Format

Context
A POS interface supports the following types of frame formats:
l l
SDH SONET
By default, the frame format of a POS interface is SDH. Do as follows on the routers:
Procedure
Step 1 Run:
system-view

The POS interface view is displayed.

Step 3 Run:
frame-format { sdh | sonet }
Frame format of the POS interface is configured. ----End
3.2.6 Configuring the Scramble Function

A POS interface supports the scrambling function for the payload data to avoid excessive consecutive 1s or 0s and facilitate line clock signal extraction for the receiver.
Context
The scrambling function of the directly connected interfaces must be configured the same. By default, the scrambling function is enabled on the payload. Do as follows on the routers:
Procedure
Step 1 Run:
system-view


scramble
The scrambling function of the payload is configured for the POS interface. ----End
3.2.7 Configuring the Length of the CRC Check Character

A POS interface supports two types of CRC check characters: 16 bits and 32 bits.
Context
By default, 32-bit CRC is adopted.
Procedure
Step 1 Run:
system-view

Issue 03 (2010-03-31)
3-13

crc { 16 | 32}
The length of the CRC check character is configured for the POS interface.
NOTE
The 10G POS interfaces do not support this configuration.
----End
3.2.8 Configuring MTU

The Maximum Transmission Unit (MTU) of a POS interface is used for the assembly and disassembly of the IP packets received and sent from the interface.
Context
A router reassembles and fragments the sent and received packets according to the MTU.
CAUTION
After changing the MTU of the interface by running the mtu command, restart the interface to validate the configuration by running the shutdown and undo shutdown commands consecutively. Do as follows on the routers:
Procedure
l Configuring IPv4 MTU 1. Run:
system-view

The POS interface view is displayed. 3. Run:

mtu mtu
The IPv4 MTU of the POS interface is configured. The MTU is expressed in bytes, and its value ranges from 46 to 9600. By default, the MTU is 4470 bytes. l Configuring IPv6 MTU 1. Run:
system-view

2.
Run:
The POS interface view is displayed. 3. Run:

ipv6 mtu mtu
The IPv6 MTU of the POS interface is configured. The MTU is expressed in bytes, and its value range from 1280 to 9660. By default, the MTU is 4470 bytes.
CAUTION
After configuring the IPv6 MTU, run the ppp mru-negotiate ipv6 command to start negotiation of the IPv6 MTU. ----End

Procedure
l l l Run the display interface pos [ interface-number ] [ | { begin | exclude | include } regularexpression ] command to check the configuration and status of the POS interface. Run the display interface brief [ | { begin | include | exclude } regular-expression ] command to check the brief information about the POS interface. 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 Line protocol current state : UP Description : Pos1/0/0 Interface Route Port,The Maximum Transmit Unit is 4470 bytes, Hold timer is 10(sec) Internet Address is 1.1.1.1/24 Link layer protocol is PPP LCP opened, IPCP opened 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 J1 "NetEngine " Flag C2 22(0x16) SDH alarm: section layer: none line layer: none
Issue 03 (2010-03-31)
3-15
path layer: none SDH error: section layer: B1 0 line layer: B2 0 REI 0 path layer: B3 0 REI 0 Statistics last cleared:2006-12-20 09:20:21 Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 24 packets, 12593 bytes Input error: 4 shortpacket, 0 longpacket, 80 CRC, 0 lostpacket Output: 604 packets, 9688 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
Run the display interface brief [ | { begin |include |exclude } regular-expression ] command. If you can view the brief information about the physical status, link protocol status, bandwidth utilization, and number of the error packets, it means that the configuration succeeds. For example:
<HUAWEI> display interface brief | include Pos *down: administratively down ^down: standby (l): loopback (s): spoofing (b): BFD down (d): DampeningSuppressed InUti/OutUti: input utility/output utility Interface Physical Protocol InUti OutUti inErrors/ outErrors Pos4/0/0 down down 0% 0% 831745956 0 Pos5/0/0 up up 0.01% 0.01% 3795064053 0 Pos5/0/1 down down 0% 0% 343911292 0 Pos5/0/2 down down 0% 0% 343913408 0 Pos5/0/3 down down 0% 0% 343915353 0
Run the display pos interface command, you can view the detailed information about the physical layer. For example:
<HUAWEI> display pos interface pos 6/0/0 Pos6/0/0 current state:DOWN Line protocol current state:DOWN Physical layer is Packet Over SDH Scramble enabled, clock master, CRC-32, loopback: none SDH alarm: section layer: OOF LOF LOS line layer: none path layer: PAIS PRDI SDH error: section layer: B1 306207965 line layer: B2 39944626237 REI 9861843785 path layer: B3 1641810669 Last 30 seconds input rate 0 Bits/sec, 0 packets/sec Last 30 seconds output rate 0 Bits/sec, 0 packets/sec Input: 0 packets, 75870759 bytes Input error: 0 shortpacket, 3 longpacket, 48 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets SFP Transp Infomation: The Vendor PN is FTRJ1321P1BTL The Vendor name is FINISAR CORP. address : 3 4 5 6 7 8 9 10 12 14 15 16 17 18 60 61 value(hex): 0 1 22 2 12 10 1 5 19 5 32 0 0 0 5 1e Port BW: 2.5G, Transceiver max BW: 2.5G, Transceiver Mode: SingleMode WaveLength: 1310nm, Transmission Distance: 5km PIC Packet Statics Per Sencond: Rxd: 0x0 Packets 0x0 FCS 0x0 Receiv Abort Packets 0x0 Long Packets 0x0 Short Packets
3-16
Issue 03 (2010-03-31)

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 Tx J0 String :NetEngine Tx J1 ASCII : f8 4e 65 74 45 6e 67 69 6e 65 20 Tx J1 String :NetEngine
20 20
20 20
20 20
20 20
20 20
3.3 Configuring STM-1 CPOS Interfaces

This section describes how to configure a STM-1 CPOS interface. 3.3.1 Establishing the Configuration Task 3.3.2 Configuring Clock Mode 3.3.3 Configuring Frame Format 3.3.4 Configuring the Overhead Byte 3.3.5 Configuring AUG Multiplexing Route In the SDH, the payload has the following mapping and multiplexing solutions. 3.3.6 Checking the Configuration

Before using a SONET/SDH optical interface to bear packet data and using low-speed ports for access, you need to configure parameters for the CPOS interface.
Before configuring a CPOS interface, complete the following task:
l
Data Preparation
To configure a CPOS interface, you need the following data. No. 1 2 Data Number of the CPOS interface on the router Overhead bytes C2, J0, and J1 of the CPOS interface
Issue 03 (2010-03-31)
3-17

Context
A CPOS interface supports the following clock modes:
l l
Master clock mode: uses internal clock signal. Slave clock mode: uses line clock signal.
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 the 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. Do as follows on the routers:
Procedure
Step 1 Run:
system-view

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

Context
Procedure
Step 1 Run:
system-view

3-18
Issue 03 (2010-03-31)

Frame format of the CPOS interface is configured. The frame format determines whether a CPOS interface works in SONET mode or SDH mode. By default, the frame type of a CPOS interface varies with the hardware:
l l
For the CPOS interface that can be channelized into E1 or E3, the default frame type is SDH. For the CPOS interface that can be channelized into T1 or T3, the default frame type is SONET.
----End

Context
The SONET/SDH provides a variety of overhead bytes, which perform the monitoring function of different levels. The C2 is used to indicate the multiplex structure of VC frame and the property of information payload. The J0 is a section overhead byte which is used to detect the connectivity of two ports on the section layer. The J1 is higher order path overhead bytes and is used to detect the connectivity of two ports on the path layer. Do as follows on the routers:
Procedure
Step 1 Run:
system-view

The CPOS interface view is displayed. 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:

l
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".
To configure the path trace byte J1, run:

flag j1 j1
Issue 03 (2010-03-31)
3-19
By default, the value of J1 is "NetEngine".

l
To configure path signal label byte C2, run:

flag c2 c2
The C2 is mainly used for international interconnection and 0x02 is used in China. By default, c2 is 02 (in hexadecimal system). The C2, J0, J1, on the receiving end and the sending end must be consistent; otherwise, an alarm is generated. ----End
3.3.5 Configuring AUG Multiplexing Route

In the SDH, the payload has the following mapping and multiplexing solutions.
Context
l
In the ANSI multiplexing, the lower-order payload is aggregated into the VC-3 higherorder path. An AU-3 consists of a VC-3 and an AU pointer. Three AU-3s are multiplexed into an AUG. In the 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. Do as follows on the routers:
Procedure
Step 1 Run:
system-view


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

Procedure
Step 1 Run the display controller cpos [ cpos-number ] command to check information about all channels of the 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 Physical layer is Packet Over SDH clock master, Multiplex AU-4, loopback none TX:Flag J0: "NetEngine ", Flag J1: "NetEngine RX:Flag J0: "NetEngine ", Flag J1: "NetEngine section layer: alarm: none error: B1 0 line layer: alarm: none error: B2 0 REI 0 path layer: alarm: none error: B3 0 REI 0
", Flag C2: 2(0x2) ", Flag C2: 2(0x2)
3.4 Configuring E1 Channels of the CPOS Interface

Describes how to configure E1 channels of CPOS interfaces. 3.4.1 Establishing the Configuration Task 3.4.2 Creating Synchronous Serial Interface of E1 Channel 3.4.3 Configuring Frame Format 3.4.4 Configuring Clock Mode 3.4.5 Checking the Configuration

Before using the low-speed interface channelized from the CPOS interface for access, you need to configure parameters for the E1 channel.
Before configuring the E1 channel on a CPOS interface, complete the following tasks:

l l
Powering on the router and starting it normally Connecting the CPOS interface and configuring physical attributes for the CPOS interface
Data Preparation
To configure the E1 channel of a CPOS interface, you need the following data. No. 1 2 3 Data Number of the CPOS interface on the router Number of the E1 channel Number of the CE1 channel whose timeslots are bound into the channel-set, and number and range of timeslots
3.4.2 Creating Synchronous Serial Interface of E1 Channel

Context
NOTE
One channel cannot work in both the clear channel mode and the channelized mode simultaneously. To switch the working mode between these two modes, cancel the current serial interface and re-create a new one.
Procedure
Step 1 Run:
system-view

The CPOS interface view is displayed. Step 3 To create the synchronous serial interface of the E1 channel, do as follows:
l
To create the E1 channel in clear channel mode, run:

e1 e1-number unframed
To create the E1 channel in channelized mode, run:

e1 e1-number channel-set set-number timeslot-list { ts0 | slot-list [ ts0 ] }
In channelized mode, timeslot 0 alone can be bound to form a serial interface; timeslots 0 to 31 can also be randomly bound to form one or multiple serial interfaces. In this case, timeslot 0 needs to be specified in the command as the parameter ts0. Timeslot 0 is used to transmit frame synchronization and alarm information. After timeslot 0 is bound to form a serial interface, frame synchronization and alarm information can be transparently transmitted between the client and the server through the serial interface.
The channel-set after the timeslot binding of the E1 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. ----End

Context
An E1 channel supports the frame format with 4-bit CRC. By default, the frame format of an E1 channel is no-CRC4. Do as follows on the routers:
Procedure
Step 1 Run:
system-view


e1 e1-number set frame-format { crc4 | no-crc4 }
The frame format of the E1 channel is configured. ----End

Context
You can configure the clock mode for each E1 channel separately. The clock mode of an E1 channel depends on the device connecting the E1 channel. For example:
l
If the E1 interface is connected to a SONET or SDH device, configure the E1 interface to work in slave clock mode. If two routers are connected directly through the 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. Do as follows on the routers:
Procedure
Step 1 Run:
system-view
Issue 03 (2010-03-31)
3-23


e1 e1-number set clock { master | slave }
The clock mode of the E1 channel is configured. ----End

Procedure
l 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. 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 E1 channel of a CPOS interface.
<HUAWEI> display interface serial 1/0/0/1:1 Serial1/0/0/1:1 current state : UP Line protocol current state : UP Last line protocol up time : 2009-01-20 15:55:16 Description : Serial1/0/0/1:1 Interface Route Port, The Maximum Transmit Unit is 1500, Hold timer is 10(sec) Derived from Cpos1/0/0 e1 1, Timeslot(s) Used: 1-24, baudrate is 1536000 bps Internet protocol processing : disabled Link layer protocol is PPP LCP opened 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 controller cpos command, you can view the information about the status and clock mode of CPOS interface. For example:
<HUAWEI> display controller cpos 1/0/0 Cpos1/0/0 current state : UP Description : Cpos1/0/0 Interface 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
3-24
Issue 03 (2010-03-31)
Physical layer is Packet Over SDH clock master, Multiplex AU-3, loopback none TX:Flag J0: "NetEngine ", Flag J1: "NetEngine RX:Flag J0: "", Flag J1: "NetEngine section layer: alarm: none error: B1 0 line layer: alarm: none error: B2 0 path layer: alarm: none error: B3 0
", Flag C2: 2(0x2)
", Flag C2: 2(0x2)
REI 27 REI 24
3.5 Configuring T1 Channels of the CPOS Interface

This section describes how to configure T1 channels of CPOS interfaces. 3.5.1 Establishing the Configuration Task 3.5.2 Creating Synchronous Serial Interface of T1 Channel 3.5.3 Configuring Frame Format 3.5.4 Configuring Clock Mode 3.5.5 Checking the Configuration

Before using the low-speed port channelized from the CPOS interface for access, you need to configure parameters the T1 channel.
Before configuring the T1 channel of the CPOS interface, complete the following tasks:
l l
Powering on the router and starting it normally Connecting the CPOS interface and configuring physical attributes for the CPOS interface
Data Preparation
To configure T1 channels of the CPOS interface, you need the following data. No. 1 2 3 Data Number of the CPOS interface on the router Number of the T1 channel Number of the CT1 channel whose timeslots are bound as the channel-set, timeslot number, or timeslot range
Issue 03 (2010-03-31)
3-25
3.5.2 Creating Synchronous Serial Interface of T1 Channel

Context
NOTE
One channel cannot work in both the clear channel mode and the channelized mode simultaneously. To switch the working mode between these two modes, cancel the current serial interface and re-create a new one.
Procedure
Step 1 Run:
system-view

The CPOS interface view is displayed. Step 3 To create the synchronous serial interface of the T1 channel, do as follows:
l
To create the T1 channel in clear channel mode, run:

t1 t1-number unframed
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 to be used. 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

Context
A T1 channel supports two types of frame formats: super frame (SF) and extended super frame (ESF). Do as follows on the routers:
Procedure
Step 1 Run:
system-view
3-26
Issue 03 (2010-03-31)


t1 t1-number set frame-format { esf | sf }
The frame format of the T1 channel is configured. By default, the frame format of a T1 channel is ESF. ----End

Context
You can configure the clock mode for each T1 channel separately. The clock mode of a T1 channel depends on the device connecting 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 the optical fiber, configure one end to work in master clock mode and the other end in slave clock mode. By default, a T1 channel works in master clock mode. Do as follows on the routers:
Procedure
Step 1 Run:
system-view


The clock mode of the T1 channel is configured. ----End

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 T1 channels.
Issue 03 (2010-03-31)
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.
<HUAWEI> display interface serial 1/0/0/1:0 Serial1/0/0/1:0 current state : UP Line protocol current state : UP Last line protocol up time : 2009-01-20 15:55:16 Description:Serial1/0/0/1:0 Interface Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec) Derived from Cpos1/0/0 t1 1, Timeslot(s) Used: 0-23, baudrate is 1536000 bps Internet protocol processing : disabled Link layer protocol is PPP LCP opened Physical layer is Packet Over ESF clock master, loopback none CRC: CRC-32 Scramble disabled Alarm: none Statistics last cleared:2009-01-13 19:03:08 Traffic statistics: Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
3.6 Configuring E3 Channels of an STM-1 CPOS Interface

This section describes how to configure the E3 channels of the STM-1 CPOS interfaces. 3.6.1 Establishing the Configuration Task 3.6.2 Creating Synchronous Serial Interface of E3 Channels 3.6.3 Configuring Clock Mode 3.6.4 Checking the Configuration

When the accessing is performed through the low speed port channelized by the CPOS interface, you need to configure the E3 channels.
Before configuring E3 channels on a CPOS interface, complete the following tasks:
l
Powering on and starting the router normally

3-28

l
Connecting the CPOS interface and configuring the physical attributes of the CPOS interface
Data Preparation
To configure E3 channels of a CPOS interface, you need the following data. No. 1 2 Data Number of CPOS interface of the router Number of the E3 channel
3.6.2 Creating Synchronous Serial Interface of E3 Channels

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 in the E3 channel. The E3 channel without timeslot division functions as a synchronous serial interface named serial slot/card/port/0:0.
Unchannelized mode When an E3 channel works in unchannelized mode, data is transmitted in the form of frames in the E3 channel. 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

The CPOS interface view is displayed. Step 3 To create the synchronous serial interface, perform the following as required:
l
To create the serial interface of the unchannelized mode, run the e3 e3-number framed command. To create the serial interface of the clear channel mode, run the e3 e3-number unframed command.
After the creation is successful, the number of the formed synchronous serial interface is: slot/ card/port/0:0. ----End

Context
You can configure the clock mode for each E3 channel separately. The clock mode of an E3 channel depends on the device connecting the E3 channel. 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 the 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


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

Procedure
l l Run the display controller cpos cpos-number command to check the configuration and status of the CPOS interface. Run the display interface serial slot/card/port/channel-number:set-number command to checks the information about the serial interface bound by E3 channels.
----End
Example
<HUAWEI> display controller cpos 1/0/0 Cpos1/0/0 current state : Administratively DOWN Description : Cpos1/0/0 Interface The Vendor Name is AGILENT
3-30
Issue 03 (2010-03-31)
The Vendor PN is HFBR-5710LP-H3C Port BW: 155M, Transceiver max BW: 1G, Transceiver Mode: MultiMode WaveLengh: 850nm, Transmission Distance: 550m Physical layer is Packet Over SDH clock master, Multiplex AU-3, loopback none TX:Flag J0: "NetEngine ", Flag J1: "NetEngine ", Flag C2: 2(0x2) RX:Flag J0: unknown, Flag J1: unknown, Flag C2: 255(0xff) section layer: alarm: LOS error: B1 306431763 line layer: alarm: LAIS LREI SF error: B2 511275881 REI 1175934524 path layer: alarm: PPLM error: B3 2711 REI 1451
You can view information about the status and clock information by checking information about the serial interface.
<HUAWEI> display interface serial 2/0/0/1:0 Serial2/0/0/1:0 current state : UP Line protocol current state : UP Last line protocol up time : 2009-01-20 15:55:16 Description: Serial2/0/0/1:0 Interface Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec) Derived from Cpos2/0/0 e3 1, Unframed mode, baudrate is 34368000 bps Internet protocol processing : disabled Link layer protocol is PPP LCP opened clock master, loopback none CRC: CRC-32 Scramble disabled Alarm: None Statistics last cleared:2009-01-23 10:56:33 Traffic statistics: Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
3.7 Configuring T3 Channels of an STM-1 CPOS Interface

This section describes how to configure T3 channels of an STM-1 CPOS interfaces. 3.7.1 Establishing the Configuration Task 3.7.2 Creating T3 Channels 3.7.3 Configuring Frame Format 3.7.4 Configuring Clock Mode 3.7.5 Checking the Configuration

When the accessing is performed through the low speed port channelized by the CPOS interface, you need to configure the T3 channels.
Before configuring T3 channels on a CPOS interface, complete the following tasks:
l l
Powering on and starting the router normally Connecting the CPOS interface and configuring the physical attributes of the CPOS interface
Data Preparation
To configure T3 channels of a CPOS interface, you need the following data. No. 1 2 Data Number of CPOS interface of the router Number of the T3 channel
3.7.2 Creating T3 Channels

Context
T3 channels work in either of the following modes:
l
Clear channel mode (also known as unframed mode) When a T3 channel works in clear channel mode, data is transmitted in the form of bit flows in the T3 channel. The T3 channel without timeslot division functions as a synchronous serial interface named serial slot/card/port/channel-number:0.
Unchannelized mode When a T3 channel works in unchannelized mode, data is transmitted in the form of frames in the T3 channel. 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

The CPOS interface view is displayed. Step 3 To create the synchronous serial interface, perform the following as required:
l
To create the serial interface of the unchannelized mode, run the t3 t3-number framed command.
3-32

l
To create the serial interface of the 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

Context
T1 corresponds to the digital signal level DS-1. 28 T1s form a T3 through the bit multiplexing. There are two kinds of frame format:
l
C-bit: is also called C-bit parity check. In this frame format, the padding field can be used in maintenance. 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


t3 t3-number set frame-format { c-bit | m23 }
The frame format of the T3 channel is configured. It is recommended that the frame formats of the T3 channel and the CPOS interface be the same. ----End

Context
You can configure the clock mode for each T3 channel separately. The clock mode of an T3 channel depends on the device connecting the T3 channel. 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 the optical fiber, configure one end to work in master clock mode and the other end in slave clock mode. By default, an T3 channel works in master clock mode.
NOTE
Procedure
Step 1 Run:
system-view


The clock mode of the T3 channel is configured. ----End

Procedure
l l Run the display controller cpos [ cpos-number ] command to check the status and statistics of the CPOS interface. Run the display interface serial slot/card/port/channel-number:set-number command to checks the information about the serial interface bound by T3 channels.
----End
Example
<HUAWEI> display controller cpos 1/0/0 Cpos1/0/0 current state : Administratively DOWN Description : Cpos1/0/0 Interface The Vendor Name is AGILENT The Vendor PN is HFBR-5710LP-H3C Port BW: 155M, Transceiver max BW: 1G, Transceiver Mode: MultiMode WaveLengh: 850nm, Transmission Distance: 550m Physical layer is Packet Over SDH clock master, Multiplex AU-3, loopback none TX:Flag J0: "NetEngine ", Flag J1: "NetEngine ", Flag C2: 2(0x2) RX:Flag J0: unknown, Flag J1: unknown, Flag C2: 255(0xff) section layer: alarm: LOS error: B1 306431763 line layer: alarm: LAIS LREI SF
3-34
Issue 03 (2010-03-31)

error: B2 511275881 REI 1175934524 path layer: alarm: PPLM error: B3 2711 REI 1451
You can view information about the status and clock information by checking information about the serial interface.
<HUAWEI> display interface serial 2/0/0/1:0 Serial2/0/0/1:0 current state : UP Line protocol current state :UP Last line protocol up time : 2009-01-20 15:55:16 Description: Serial2/0/0/1:0 Interface Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec) Derived from Cpos2/0/0 t3 1, Unframed mode, baudrate is 44736000 bps Internet protocol processing : disabled Link layer protocol is PPP LCP opened clock master, loopback none CRC: CRC-32 Scramble disabled Alarm: None Statistics last cleared:2009-01-23 11:04:14 Traffic statistics: Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
3.8 Maintaining POS and CPOS Interface Configuration

This section describes how to maintain POS interfaces and CPOS interfaces. 3.8.1 Configuring the Self-loop to Detect Whether the Interface Is Normal 3.8.2 Clearing the Interface Statistics
3.8.1 Configuring the Self-loop to Detect Whether the Interface Is Normal

Context
CAUTION
After you configure the self-loop or run the loopback command, the interface on a router or the link may not run normally. Thus, you must check whether to set the self-loop. After the detection is complete, run the undo loopback command to disable the self-loop.
Procedure
Step 1 Run:
system-view
Issue 03 (2010-03-31)
3-35
The system view is displayed. 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:

In the case of a STM-1 CPOS interface or E1/T1/E3/T3 channel of STM-1 CPOS interface, run:
controller cpos interface-number
Step 3 Choose one of the following commands according to the interface type to enable the self-loop.
l
In the case of a POS interface, STM-1 CPOS interface or STM-16 CPOS interface, run:
loopback { local | remote }
In the case of an E1 channel of STM-1 CPOS interface, run:

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

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

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

t3 t3-number set loopback { local | remote }
By default, the self-loop is disabled. When configuring the loopback of the interface, note the following points:
l
For the POS interface, the configurations of the loopback differ with different service boards. The following cases may occur in the actual configurations:
Take the prompt information as the standards.

l
For the STM-1 CPOS interface or E1/T1/E3/T3 channel of STM-1 CPOS interface
----End

Context
CAUTION
The interface statistics cannot be restored after you run the reset command to clear it. So, confirm the action before you use the command.
3-36
Issue 03 (2010-03-31)
To reset the interface statistics of the Network Management System (NMS) or those displayed by running the display interface command, run the following commands in the user view. Clear the interface statistics before collecting the traffic.
NOTE
For the interface statistics in the NMS, refer to related NMS manuals.
Procedure
----End

This section provides several configuration examples of POS and CPOS interfaces. 3.9.1 Example for Directly Connecting Devices Through POS Interfaces 3.9.2 Example for Connecting Devices with POS Interfaces Through FR Network 3.9.3 Example for Configuring an STM-1 CPOS Interface
3.9.1 Example for Directly Connecting Devices Through POS Interfaces

As shown in Figure 3-5, 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-5 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
The configuration roadmap is as follows: 1.
Issue 03 (2010-03-31)
Configure PPP as the link layer protocol.

2.
Configure IP addresses.
Data Preparation
To complete the configuration, you need the following data:
l l
IP address of POS 1/0/0 on Router A IP address of POS 1/0/0 on Router B
Procedure
Step 1 Configure Router A. # Configure POS 1/0/0, and set default values for all physical parameters.
<HUAWEI> system-view [HUAWEI] sysname A [RouterA] interface pos 1/0/0 [RouterA-Pos1/0/0] ip address 10.1.1.1 30 [RouterA-Pos1/0/0] undo shutdown [RouterA-Pos1/0/0] quit
Step 2 Configure Router B. # Configure POS 1/0/0, set the clock mode to slave, and set default values for other physical parameters.
<HUAWEI> system-view [HUAWEI] sysname B [RouterB] interface pos 1/0/0 [RouterB-Pos1/0/0] clock slave [RouterB-Pos1/0/0] ip address 10.1.1.2 30 [RouterB-pos1/0/0] undo shutdown [RouterB-Pos1/0/0] quit
Step 3 Verify the configuration. Run the display interface pos command to check the connectivity of the POS interface on Router A.
<RouterA> display interface pos 1/0/0 Pos1/0/0 current state : UP Line protocol current state : UP Last line protocol up time : 2009-01-20 11:35:15 Description: Pos1/0/0 Interface Route Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Internet Address is 10.1.1.1/30 Link layer protocol is PPP LCP opened, IPCP opened 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 J1 "NetEngine " Flag C2 22(0x16) SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1 0 line layer: B2 0 REI 0 path layer: B3 0 REI 0
3-38
Issue 03 (2010-03-31)
Statistics last cleared:2009-01-20 15:55:04 Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 24 bits/sec, 0 packets/sec Input: 604 packets, 9640 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 604 packets, 9688 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
Run the ping command to check the network connectivity.

[RouterA] ping 10.1.1.2 PING 10.1.1.2: 56 data bytes, press CTRL_C to break Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=255 time=3 Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=255 time=2 Reply from 10.1.1.2: bytes=56 Sequence=3 ttl=255 time=2 Reply from 10.1.1.2: bytes=56 Sequence=4 ttl=255 time=2 Reply from 10.1.1.2: bytes=56 Sequence=5 ttl=255 time=2 --- 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
ms ms ms ms ms
----End
Configuration Files
l

# 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.9.2 Example for Connecting Devices with POS Interfaces Through FR Network
As shown in Figure 3-6, routers are interconnected through POS interfaces on the FR network,and routers work in DTE mode as user devices. Router A connects Router B and Router C, which reside on different network segments from Router A, through sub-interfaces.
Figure 3-6 Networking diagram of connecting routers using the POS interface through FR network
POS1/0/0.1 DLCI=21 10.1.1.1/30
POS1/0/0.1 DLCI=21 10.1.1.2/30 Frame Relay network POS1/0/0.2 DLCI=22 10.2.1.2/30
Router B
Router A POS1/0/0.2 DLCI=22 10.2.1.1/30
Router C
The configuration roadmap is as follows: 1. 2. 3. 4. Configure FR as the link protocol. Configure the working mode for interfaces. Configure IP addresses for interfaces. Configure the address mapping.
Data Preparation
l l l l
IP address and DLCI of POS 1/0/0.1 on Router A IP address and DLCI of POS 1/0/0.2 on Router A IP address and DLCI of POS 1/0/0.1 on Router B IP address and DLCI of POS 1/0/0.2 on Router C
Procedure
Step 1 Configure Router A.
<HUAWEI> system-view [HUAWEI] sysname RouterA [RouterA] interface pos 1/0/0
# Encapsulate the FR protocol.

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

[RouterA] interface pos 1/0/0.1 [RouterA-Pos1/0/0.1] shutdown
3-40
Issue 03 (2010-03-31)

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

[RouterA] interface pos 1/0/0.2 [RouterA-Pos1/0/0.2] shutdown [RouterA-Pos1/0/0.2] fr dlci 22 [RouterA-fr-dlci-Pos1/0/0.2-22] quit [RouterA-Pos1/0/0.2] ip address 10.2.1.1 30 [RouterA-Pos1/0/0.2] undo shutdown [RouterA-Pos1/0/0.2] quit
Step 2 Configure Router B and Router C. The method of configuring Router B and Router C is the same as the method of configuring Router A. The configuration details are not mentioned here. Step 3 Verify the configuration. Run the display interface pos command on each router. You can find that the connectivity of POS interfaces is Up. Run the ping command on each router. Each router can ping through the network. ----End
Configuration Files
l

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

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

# sysname RouterC
Issue 03 (2010-03-31)
3-41

# interface Pos1/0/0 link-protocol fr undo shutdown # interface Pos1/0/0.2 fr dlci 22 ip address 10.2.1.2 255.255.255.252 # return
3.9.3 Example for Configuring an STM-1 CPOS Interface

As shown in Figure 3-7, certain mid-range-and-low-end devices access the transmission network through E1/T1 leased cable. All the bandwidths converge to the CPOS interface 3/0/1 on Router A through 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 deivce. Other transmission methods can also be adopted.
NOTE
The configurations of the T1 channel and the E1 channel are consistent. Take the E1 channel as an example.
Figure 3-7 Networking diagram of an STM-1 CPOS interface
E1/T1 .. ADM E1/T1 ADM STM-4/16 ADM nx E1/T1 .. ADM Router A CPOS 3/0/1 OC-3/STM-1
Internet
The configuration roadmap is as follows: 1. 2. 3.
3-42
Create the channel. Create the bound group. Configure the channel to join the bound group.
Data Preparation
l l
Channel number and slot number of each E1 channel Number of the bound group on each interface
NOTE
l l
The slot number and card number of the added Mp-group interface and the Mp-group interface must be consistent. That is, trans-board binding is not supported. The interfaces added to the MP-group can only be the serial interfaces instead of other interfaces.
Procedure
Step 1 Configure RouterA # Create a channel on the CPOS interface.
<HUAWEI> system-view [HUAWEI] sysname RouterA [RouterA] controller cpos 3/0/1 [RouterA-Cpos3/0/1] e1 1 channel-set [RouterA-Cpos3/0/1] e1 2 channel-set [RouterA-Cpos3/0/1] e1 3 channel-set [RouterA-Cpos3/0/1] e1 4 channel-set [RouterA-Cpos3/0/1] undo shutdown [RouterA-Cpos3/0/1] quit
1 2 3 4
timeslot-list timeslot-list timeslot-list timeslot-list
1-10 11-15 16-20 21-30
# Configure a bundle group and the terminal authenticator.

[RouterA] interface Mp-group 3/0/1 [RouterA-Mp-group3/0/1] discriminator [RouterA-Mp-group3/0/1] shutdown [RouterA-Mp-group3/0/1] quit
# Bind the channel to the bundle group.

[RouterA] interface Serial 3/0/1/1:1 [RouterA-Serial3/0/1/1:1] shutdown [RouterA-Serial3/0/1/1:1] ppp mp Mp-group [RouterA-Serial3/0/1/1:1] quit [RouterA] interface Serial 3/0/1/2:2 [RouterA-Serial3/0/1/2:2] shutdown [RouterA-Serial3/0/1/2:2] ppp mp Mp-group [RouterA-Serial3/0/1/2:2] quit [RouterA] interface Serial 3/0/1/3:3 [RouterA-Serial3/0/1/3:3] shutdown [RouterA-Serial3/0/1/3:3] ppp mp Mp-group [RouterA-Serial3/0/1/3:3] quit [RouterA] interface Serial 3/0/1/4:4 [RouterA-Serial3/0/1/4:4] shutdown [RouterA-Serial3/0/1/4:4] ppp mp Mp-group [RouterA-Serial3/0/1/4:4] quit
3/0/1
3/0/1
3/0/1
3/0/1
# Restart the channel and MP-group.

[RouterA] interface Mp-group 3/0/1 [RouterA-Mp-group3/0/1] undo shutdown [RouterA-Mp-group3/0/1] quit [RouterA] interface Serial 3/0/1/1:1 [RouterA-Serial3/0/1/1:1] undo shutdown [RouterA-Serial3/0/1/1:1] quit [RouterA] interface Serial 3/0/1/2:2 [RouterA-Serial3/0/1/2:2] undo shutdown [RouterA-Serial3/0/1/2:2] quit
Issue 03 (2010-03-31)
3-43

[RouterA] interface Serial 3/0/1/3:3 [RouterA-Serial3/0/1/3:3] undo shutdown [RouterA-Serial3/0/1/3:3] quit [RouterA] interface Serial 3/0/1/4:4 [RouterA-Serial3/0/1/4:4] undo shutdown [RouterA-Serial3/0/1/4:4] quit
----End
Configuration Files
# sysname RouterA # controller Cpos3/0/1 undo shutdown e1 1 channel-set 1 timeslot-list e1 2 channel-set 2 timeslot-list e1 3 channel-set 3 timeslot-list e1 4 channel-set 4 timeslot-list # interface Serial3/0/1/1:1 undo shutdown link-protocol ppp ppp mp Mp-group 3/0/1 # interface Serial3/0/1/2:2 undo shutdown link-protocol ppp ppp mp Mp-group 3/0/1 # interface Serial3/0/1/3:3 undo shutdown link-protocol ppp ppp mp Mp-group 3/0/1 # interface Serial3/0/1/4:4 undo shutdown link-protocol ppp ppp mp Mp-group 3/0/1 # interface Mp-group3/0/1 undo shutdown # return
1-10 11-15 16-20 21-30
3-44
Issue 03 (2010-03-31)
4 PPP and MP Configuration
4
About This Chapter
PPP and MP Configuration
This chapter describes the basic concepts, configuration procedures, configuration examples, and troubleshooting of Point-to-Point Protocol (PPP) and MultiLink PPP (MP). 4.1 Introduction to PPP and MP This section describes the basic concepts and principle of PPP and MP. 4.2 Encapsulating an Interface with PPP and MRU Negotiation This section describes how to encapsulate an interface with PPP and configure the PPP MRU negotiation. 4.3 Configuring Unidirectional PAP This section describes how to configure PAP authentication. 4.4 Configuring Unidirectional CHAP This section describes how to configure CHAP authentication. 4.5 Configuring PPP Optional Parameters This section describes how to configure optional parameters of PPP. 4.6 Configuring MP Binding Using an MP-Group This section describes how to configure MP binding by using an MP-group. 4.7 Configuring MP Limiting Parameters This section describes how to configure MP parameters. 4.8 Configuring MP Fragmentation Describes how to configure the length of the MP fragment on the MP-Group interface. 4.9 Maintaining PPP and MP Configuration Describes how to maintain PPP and MP. 4.10 Configuration Examples Provides several configuration examples of PPP and MP.
Issue 03 (2010-03-31)
4-1
4.1 Introduction to PPP and MP

This section describes the basic concepts and principle of PPP and MP. 4.1.1 PPP and MP Overview 4.1.2 Features of PPP and MP on the NE80E/40E
4.1.1 PPP and MP Overview

A point-to-point (P2P) connection is a simple WAN connection. Link layer protocols of a PPP link are as follows:
l l
Point-to-Point Protocol (PPP): supports synchronous and asynchronous transmission. 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 l l
It provides user authentication. It supports synchronous and asynchronous communications. It can be easily expanded.
PPP defines a set of protocols, including:

l l
Link Control Protocol (LCP): is used to establish, monitor, and terminate data links. Network Control Protocol (NCP): is used to establish and configure different network-layer protocols, and negotiate the format and type of packets transmitted over data links. Authentication protocols: include Password Authentication Protocol (PAP) and ChallengeHandshake Authentication Protocol (CHAP), which are used for network security authentication.
The Multilink PPP (MP) technology binds multiple PPP links into a logical channel to increase bandwidth. MP can be applied to the low-speed interfaces supporting PPP, such as serial interfaces.
4.1.2 Features of PPP and MP on the NE80E/40E

The NE80E/40E supports the configuration of PPP on the serial interface or POS interface to implement the following functions:
l l l
Supporting the Maximum Receive Unit (MRU) negotiation Performing the PAP or CHAP authentication Compressing the IP, UDP or RTP packet header
The MP is supported to be configured in the MP-group type on the NE80E/40E. On the NE80E/40E, the interfaces supporting the MP binding are as follows:
l l
Synchronous serial interface formed by E1/T1 channelized by the STM-1 CPOS. Synchronous serial interface formed by T1 channelized by the T3.
4-2

l
Synchronous serial interface formed by CE1 and CT1.
The NE80E/40E does not support the trans-board or trans-card MP binding. When you configure MP in the MP-group mode, you can directly add the serial interface to the MP-group.
4.2 Encapsulating an Interface with PPP and MRU Negotiation

This section describes how to encapsulate an interface with PPP and configure the PPP MRU negotiation. 4.2.1 Establishing the Configuration Task 4.2.2 Encapsulating the Interface with PPP 4.2.3 Enabling PPP MRU Negotiation 4.2.4 Checking the Configuration

As a link layer protocol that bears network-layer packets over P2P links, PPP supports the MRU negotiation. If a link is configured with the MTU value, apply the MRU negotiation to make the MTU values on both ends of the PPP link consistent so that data can be transmitted.
Before configuring PPP, complete the following task: Connecting the interface and configuring physical parameters for the interface to ensure that the physical layer status of the interface is Up.
Data Preparation
To configure PPP or PPP MRU negotiation, you need the following data. No. 1 Data Number of the interface
4.2.2 Encapsulating the Interface with PPP

Context
Procedure
Step 1 Run:
system-view

interface interface-type interface-number
The interface view is displayed. Step 3 Run:

link-protocol ppp
The link layer protocol is configured as PPP. By default, the link layer protocol of serial interfaces and POS interfaces is PPP. ----End
4.2.3 Enabling PPP MRU Negotiation

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 negotiation value of MRU is the MTU set by users or the default MTU on an interface. After the negotiation, the MTU on an interface is the smaller value between the MTUs on both ends, whereas the MRUs on both ends remain unchanged. Thus, 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. Do as follows on the routers:
Procedure
Step 1 Run:
system-view


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

Prerequisite
The configurations of the encapsulating an interface with PPP and MRU negotiation are complete.
Procedure
l Run the display interface [ interface-type [ interface-number ] ] [ | { begin | exclude | include } regular-expression ] 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 of the interface is displayed, it means that the configuration succeeds. For example:
<HUAWEI> display interface pos 1/0/0 Pos1/0/0 current state : UP Line protocol current state : UP Last line protocol up time : 2009-01-20 11:35:15 Description: Pos1/0/0 Interface Route Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Internet Address is 10.1.1.1/30 Link layer protocol is PPP LCP opened, IPCP opened 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 J1 "NetEngine " Flag C2 22(0x16) SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1 0 line layer: B2 0 REI 0 path layer: B3 0 REI 0 Statistics last cleared:2009-01-20 15:55:04 Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 24 bits/sec, 0 packets/sec Input: 604 packets, 9640 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 604 packets, 9688 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
4.3 Configuring Unidirectional PAP

This section describes how to configure PAP authentication. 4.3.1 Establishing the Configuration Task 4.3.2 Configuring a Local Router to Authenticate Its Peer in PAP Mode
4.3.3 Configuring the Peer to Be Authenticated by the Local Router in PAP Mode 4.3.4 Checking the Configuration

In PAP authentication, passwords are sent over the link in plain text. 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 two communication parties functions as the authenticator, while the other as the authenticated. Bidirectional authentication: 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
Connecting interfaces and configuring physical attributes for these interfaces to ensure that the physical layer of the interfaces is Up Configuring PPP as the link layer protocol of interfaces
Data Preparation
To configure PAP authentication, you need the following data. No. 1 2 Data Number of the interface Username and password of the authenticated
4.3.2 Configuring a Local Router to Authenticate Its Peer in PAP Mode

Context
Procedure
Step 1 Run:
system-view
4-6
Issue 03 (2010-03-31)

aaa
The AAA view is displayed. Step 3 Run:

local-user user-name password { simple | cipher } password
The username and password of the authenticated are added to the local user list. Step 4 Run:
quit
Return to the system view. Step 5 Run:


ppp authentication-mode pap [ call-in ]
The local end authenticates the peer end using PAP. Step 7 Run:
restart
The interface is restarted.

NOTE
After changing the username and password, run the restart command, or the shutdown and undo shutdownv commands in the interface view to validate the configuration.
----End
4.3.3 Configuring the Peer to Be Authenticated by the Local Router in PAP Mode
Context
Procedure
Step 1 Run:
system-view


ppp pap local-user user-name password { cipher | simple } password
Issue 03 (2010-03-31)
4-7
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, use the restart command, or the shutdown and undo shutdown commands in the interface view to validate the configuration.
----End

Prerequisite
The configurations of the unidirectional PAP function are complete.
Procedure
l Run the display interface [ interface-type [ interface-number ] ] command to check the link status of the interface and the running status of the LCP.
----End
Example
Run the display interface command. If the LCP status is Opened, it means that the PAP authentication succeeds. For example:
<HUAWEI> display interface pos 6/0/0 Pos6/0/0 current state : UP Line protocol current state : UP Last up time: 2007-11-03, 12:36:19 Description : Pos6/0/0 Interface Route Port, The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Internet Address is 10.1.1.1/30 Link layer protocol is PPP LCP opened, IPCP opened Transponder Information: Not in position Physical layer is Packet Over SDH, Scramble enabled, clock master, CRC-32, loopback: none Flag J0 "NetEngine " Flag J1 "NetEngine " Flag C2 22(0x16) SDH alarm: section layer: OOF LOF LOS line layer: none path layer: PAIS PRDI SDH error: section layer: B1 31470839 line layer: B2 6140811495 REI 1021746943 path layer: B3 251087875 Statistics last cleared:never Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets
4-8
Issue 03 (2010-03-31)
4.4 Configuring Unidirectional CHAP

This section describes how to configure CHAP authentication. 4.4.1 Establishing the Configuration Task 4.4.2 Configuring a Local Device with a User Name to Authenticate Its Peer in CHAP Mode 4.4.3 Configuring a Local Device Without a User Name to Authenticate Its Peer in CHAP Mode 4.4.4 Checking the Configuration

In CHAP authentication, passwords are sent over the link in encrypted text. The username and password of the authenticated can be authenticated in AAA mode or through the RADIUS server and then added into the user list of the authenticator. CHAP authentication is classified into the following types:
l
Unidirectional: One of two communication parties functions as the authenticator, while the other as the authenticated. 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:
l
Connecting interfaces and configuring physical attributes for these interfaces to ensure that the physical layer of the interfaces is Up Configuring PPP as the link layer protocol of interfaces
Data Preparation
To configure CHAP authentication, you need the following data. No. 1 2 3 Data Number of the interface (Optional) Username of the authenticator Username and password of the authenticated
Issue 03 (2010-03-31)
4-9
4.4.2 Configuring a Local Device with a User Name to Authenticate Its 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 Do as follows on the routers: 1. Run:
system-view

aaa
The AAA view is displayed. 3. Run:

The username and password of the authenticated are added to the local user list. 4. Run:
quit
Return to the system view. 5. Run:

The interface view is displayed. 6. Run:

ppp authentication-mode chap [ pap ] [ call-in ]
The local end authenticates the peer end by using CHAP. You can run the ppp authentication-mode chap pap command to perform 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.
Configuring the authenticated Do as follows on the routers: 1. Run:

system-view

aaa

quit



restart

NOTE
----End
4.4.3 Configuring a Local Device Without a User Name to Authenticate Its Peer in CHAP Mode
Procedure
l Configuring the authenticator Do as follows on the routers: 1. Run:
system-view

2.
Run:
aaa

quit


ppp authentication-mode chap [ pap ] [ call-in ]
The local end authenticates the peer end using CHAP. You can run the ppp authentication-mode chap pap command to perform 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
The interface is restarted. 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 succeeds. l Configuring the authenticated Do as follows on the routers: 1. Run:
system-view



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

Prerequisite
The configurations of uidirectional CHAP are complete.
Procedure
l Run the display interface [ interface-type [ interface-number ] ] command to check the PPP configuration and the status of the interface.
----End
Example
Run the display interface command. You can view the status of PPP, LCP, and IPCP. If the status of the LCP and IPCP is opened, it means that CHAP authentication succeeds. For example:
<HUAWEI> display interface pos 6/0/0 Pos6/0/0 current state : UP Line protocol current state : UP Last up time: 2007-11-03, 12:36:19 Description : Pos6/0/0 Interface Route Port, The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Internet Address is 10.1.1.1/30 Link layer protocol is PPP LCP opened, IPCP opened Transponder Information: Not in position Physical layer is Packet Over SDH, Scramble enabled, clock master, CRC-32, loopback: none Flag J0 "NetEngine " Flag J1 "NetEngine " Flag C2 22(0x16) SDH alarm: section layer: OOF LOF LOS line layer: none path layer: PAIS PRDI SDH error: section layer: B1 31470839 line layer: B2 6140811495 REI 1021746943 path layer: B3 251087875 Statistics last cleared:never Last 30 seconds input rate 0 bits/sec, 0 packets/sec Last 30 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 0 packets, 0 bytes Output error: 0 lostpackets
Issue 03 (2010-03-31)
4-13
4.5 Configuring PPP Optional Parameters

This section describes how to configure optional parameters of PPP. 4.5.1 Establishing the Configuration Task 4.5.2 Configuring the Callback Function 4.5.3 Configuring Packet or Packet Header Compression 4.5.4 Configuring the Timeout Period of Negotiation 4.5.5 Configuring the Polling Interval 4.5.6 Configuring DNS Server Address Negotiation 4.5.7 Configuring the PPP Link Quality Detection 4.5.8 Preventing the Peer Host Route from Being Added to the Local Routing Table of Direct Routes 4.5.9 Checking the Configuration

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.
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 header, UDP header, and RTP header.
Interval for the negotiation timeout In PPP negotiation, if no response is received from the peer end within the interval, PPP resends a request for negotiation.
Polling interval Link layer protocols such as PPP, FR, and HDLC use a polling timer to check whether a link works normally. In the case of 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 polling interval.
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.
4-14
Issue 03 (2010-03-31)
If you access a router through a PC, you can run the winipcfg (windows 98) or the ipconfig/ all (windows 2000/XP) command to view the DNS server addresses that are provided by the router. The NE80E/40E can provide the peer device with two server addresses, a primary DNS server address and a secondary DNS server address.
l
Link quality parameter PPP link quality detection is to detect the quality of a PPP link in real time, including 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 restores 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
Connecting interfaces and configuring physical attributes for the interfaces to ensure that the physical layer of the interfaces is Up Configuring PPP as the link layer protocol of the interfaces Configuring interfaces to adopt PAP or CHAP authentication, which is required only during the configuration of the negotiation timeout interval
l l
Data Preparation
To configure optional parameters of PPP, you need the following data. No. 1 2 3 4 5 6 Data Dial string used for calling back the router Maximum number of RTP connections and maximum number of TCP connections in the IPHC function Timeout interval of PPP negotiation Polling interval Primary DNS server address and secondary DNS server address Quality percentage of the forbidden link and quality percentage of the recovered link
4.5.2 Configuring the Callback Function

Context
Procedure
Step 1 Run:
system-view

The interface view is displayed. Step 3 Choose one of the following commands to configure the interface as the callback server or the callback client:
l l
Run the ppp callback server command to set the interface as the callback server. Run the ppp callback client command to set the interface as the callback client.
NOTE
l l
Only the low-speed serial interface and the AUX interface support the callback function. 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

Procedure
l Enabling IPHC on the interface 1. Run:
system-view

The interface view is displayed. 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 the HUAWEI NetEngine80E/40E Router Configuration Guide - QoS. ----End
4.5.4 Configuring the Timeout Period of Negotiation

Procedure
Step 1 Run:
system-view


ppp timer negotiate seconds
The timeout period of negotiation is configured on the interface.

NOTE
The MP-Group interface does not support this configuration.
----End
4.5.5 Configuring the Polling Interval

Procedure
Step 1 Run:
system-view


timer hold seconds
The polling interval is configured on the interface.

NOTE
The GE interfaces and MP-Group interfaces do not support this configuration.
----End
4.5.6 Configuring DNS Server Address Negotiation

Procedure
l Admitting any DNS server address proposed by the peer Do as follows on routers: 1.
Issue 03 (2010-03-31)
Run:

system-view


ppp ipcp dns admit-any
Any DNS server address proposed by the peer is admitted. l Configuring the DNS server address of the local negotiation Do as follows on routers: 1. Run:
system-view


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

Procedure
Step 1 Run:
system-view


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.

4-18

l
Run the restart command.
After enabling or disabling the PPP link quality detection, restart the interface to validate the configuration. ----End
4.5.8 Preventing the Peer Host Route from Being Added to the Local Routing Table of Direct Routes
Context
The PPP link does not strictly require that the peer route and local route exist at 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 is 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 this 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


ppp peer hostroute-suppress
The peer host route is prevented from being added to the local routing table of direct routes.
NOTE
After enabling or disabling the function of preventing the peer host route from being added to the local routing table of direct routes, restart the interface to validate the configuration.
Step 4 Choose one of the following methods to restart the interface.

l l
Run the shutdown and undo shutdown commands. Run the restart command.
----End

Prerequisite
The configurations of the PPP otional prameters are complete.
Procedure
l Run the display interface [ interface-type [ interface-number ] ] [ | { begin | exclude | include } regular-expression ] command to check the PPP configuration and the status of the interface. Run the display ppp compression iphc rtp [ interface-type interface-number ] command to check the statistics on the IP header compression on the PPP link.
----End
Example
Run the display interface command to check the PPP configuration and the status of the interface. For example:
<HUAWEI> display interface pos 6/0/1 Pos6/0/1 current state : UP Line protocol current state : UP Last line protocol up time : 2009-08-17 00:19:56 Description: Pos6/0/1 Interface Route Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Internet Address is 192.168.20.2/24 Link layer protocol is PPP LCP opened, IPCP opened The Vendor Name is FINISAR CORP. , The Vendor PN is FTRJ8519P1BNL-HW Transceiver BW: 1G, Transceiver Mode: Multi Mode WaveLength: 850nm, Transmission Distance: 550m Rx Optical Power: -4.95dBm, Tx Optical Power: -3.30dBm Physical layer is Packet Over SDH Scramble enabled, clock master, CRC-32, loopback: none Flag J0 "NetEngine " Flag J1 "NetEngine " Flag C2 22(0x16) SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1 0 line layer: B2 0 REI 16777215 path layer: B3 0 REI 0 Statistics last cleared:never Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 24 bits/sec, 0 packets/sec Input: 14861 packets, 237808 bytes Input error: 0 shortpacket, 0 longpacket, 1 CRC, 0 lostpacket Output: 14859 packets, 237762 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
Run the display ppp compression iphc rtp command to check the statistics on the IP header compression on the PPP link. For example:
<HUAWEI> display ppp compression iphc rtp IPHC: RTP/UDP/IP header compression Interface: Serial1/0/0:0 Received: Compress/Error/Discard/Total: 0/0/0/0 (Packets) Sent: Compress/Total: 0/0 (Packets) Send/Save/Total: 0/0/0 (Bytes) Connect: Rx/Tx: 300/300
4-20
Issue 03 (2010-03-31)
4.6 Configuring MP Binding Using an MP-Group

This section describes how to configure MP binding by using an MP-group. 4.6.1 Establishing the Configuration Task 4.6.2 Adding an Interface to an MP-Group 4.6.3 Disabling the Endpoint Discriminator Negotiation 4.6.4 Checking the Configuration

When configuring MP binding using MP-Group, the slot number and card number of MP-Group interface must be consistent with the slot number and card number of the interface added to the MP-Group. The interfaces added to the MP-Group can only be the channelized synchronous serial interfaces. In MP negotiation, different carriers complements differently. By default, the endpoint discriminator needs to be negotiated in NE80E/40E MP negotiation. If no endpoint discriminator is sent, MP negotiation fails. Then the endpoint discriminator negotiation can not be configured on the local side.
NOTE
You need to configure the local and the peer ends separately. The methods of configuration are the same.
Before configuring MP binding using MP-Group, complete the following tasks:
l l
Configuring physical attributes of the router interface. Configuring the link layer protocol of the interface as PPP.
Data Preparation
To configure MP binding using MP-Group, you need the following data. No. 1 2 3 4 Data Interface number of the router Interface number of MP-Group IP addresses and subnet masks of the MP-Group interface Username and password of the peer device
Issue 03 (2010-03-31)
4-21
4.6.2 Adding an Interface to an MP-Group

Context
When using an MP-group to bind an interface, consider the following items:
l l
Physical interfaces must be bound into one MP-group in the same mode. All physical interfaces in one MP-group must be at the same interface card as the router does not support trans-board and trans-card MP binding. Number of the physical interfaces bound in one MP-group that are used to interwork at two ends must be the same. 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

interface mp-group number
The MP-group interface is created. Step 3 Run:

ip address ip-address { mask | mask-length } [ sub ]
The IP address is assigned for the MP-group interface. Step 4 Run:

shutdown
The MP-group interface is shutdown. Step 5 Run:

quit


shutdown
The interface is shutdown. Step 8 Run:

ppp mp mp-group number
The interface is added to the MP-group.

Step 9 Run:
undo shutdown
The interface is restarted. Step 10 Run:

quit

The MP-group interface view is displayed. Step 12 Run:

undo shutdown
The MP-group is restarted. ----End
4.6.3 Disabling the Endpoint Discriminator Negotiation

Procedure
Step 1 Run:
system-view

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. The configuration of the endpoint discriminator negotiation on both ends must be the same. If one end is configured with the undo discriminator command whereas the other end is configured with the discriminator command, the parameters sent by the end configured with the undo discriminator command do not contain the endpoint discriminator, and this end 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 to enable the configuration. Step 4 Run:
quit

Issue 03 (2010-03-31)
4-23
The interface view is displayed. Step 6 Choose one of the following methods to restart the interface.
l l
Run the shutdown and undo shutdown commands. Run the restart command.
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. 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.
After the undo ppp mp command is successfully run in the interface view, the interface is unbound from the MP. At this time, the interface need not be restarted because PPP can automatically perform negotiation until the link layer protocol status of the interface changes to Up. The whole process lasts about 40 seconds. ----End

Procedure
l l l Run the display ppp mp [ interface interface-type interface-number ] command to check the MP binding information. Run the display interface mp-group [ number ] [ | { begin | exclude | include } regularexpression ] command to check the status of the MP-group interface. Run the display interface brief [ | { begin | include | exclude } regular-expression ] 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:2 physical UP,protocol UP Serial1/0/1:3 physical UP,protocol DOWN Serial1/0/1:4 physical UP,protocol DOWN ===========Sublinks status end======== Bundle Multilink, 2 member, slot 1, Master link is Mp-group1/0/1 0 lost fragments, 0 reordered, 0 unassigned, 0 interleaved, sequence 0/0 rcvd/sent The bundled son channels are: Serial1/0/1:1 Serial1/0/1:2
4-24
Issue 03 (2010-03-31)
After running the display interface mp-group command, you can check the status of the MPGroup interface. The following is the display of the command:
<HUAWEI> display interface mp-group Mp-group1/0/1 current state : UP Line protocol current state : UP Last line protocol up time : 2009-01-20 11:01:43 Description:Mp-group1/0/1 Interface Route Port,The Maximum Transmit Unit is 1500 Internet Address is 1.2.2.1/24 Link layer protocol is PPP LCP opened, MP opened, IPCP reqsent Physical is MP, baudrate is 1984000 bps Traffic statistics: Last 300 seconds input rate 16 bits/sec, 0 packets/sec Last 300 seconds output rate 16 bits/sec, 0 packets/sec Input: 117 packets, 1440 bytes 0 errors, 0 drops Output: 118 packets, 1475 bytes 0 errors, 0 drops
After running the display interface brief [ | { begin | include | exclude } regular-expression ] command, you can check brief information about the physical status, link layer protocol status, bandwidth utilization, and number of incorrect packets of the MP-Group interface and its member interfaces. The following is the display of the command:
<HUAWEI> display interface brief | include 1/0/ PHY: Physical *down: administratively down ^down: standby (l): loopback (s): spoofing (b): BFD down (e): EFM down (d): Dampening Suppressed InUti/OutUti: input utility/output utility Interface PHY Protocol outErrors Mp-group1/0/1 up up 0 Serial1/0/0:0 up up 0 Serial1/0/1:0 up up 0 Serial1/0/2:0 *down down 0 Serial1/0/5:0 up down 0
InUti OutUti 0% 1% 1% 0% 0% 0% 1% 1% 0% 0.01%
inErrors 0 5 2 0 21
4.7 Configuring MP Limiting Parameters

This section describes how to configure MP parameters. 4.7.1 Establishing the Configuration Task 4.7.2 Configuring the MRRU of an MP Group 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. 4.7.4 Configuring the Minimum Number of Subchannels in the Up State in an MP Link After the LCP negotiation succeeds, 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. 4.7.5 Checking the Configuration

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
Connecting the interface and configuring the physical parameters of the interface to make the physical layer status of the interface change to Up Configuring MP binding
Data Preparation
To configure MP limiting parameters, you need the following data. No. 1 2 3 4 5 Data The MRRU of MP Time period during which the MP subchannel status is detected Maximum number of times of the flappings occuring on the MP subchannel within the detection time Minimum time during which the MP subchannel keeps Up to be released from damping Minimum number of subchannels in the Up state in an MP
NOTE
l l l
After changing the parameters configured in the MP-group view, you need to use the shutdown command in all the bound sub-channels to disable the MP binding. Then use the undo shutdown command in all the bound sub-channels to bind MP again. Finally, all the configured commands will be effective.
4.7.2 Configuring the MRRU of an MP Group

Context
Max-Receive-Reconstructed Unit (MRRU) refers to the maximum size of the packet reassembled with the received fragment packets, and MP must negotiate MRRU with the remote before performing IP packet fragmentation. Do as follows on the routers:
Procedure
Step 1 Run:
system-view

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
Do as follows on the routers configured with MP-Group interfaces:
Procedure
Step 1 Run:
system-view

The MP-Group interface view is displayed. Step 3 Run:

ppp mp damping detect-time detect-time flapping-count flapping-count damp-time damp-time
The damping function is configured for the MP subchannels. ----End

4.7.4 Configuring the Minimum Number of Subchannels in the Up State in an MP Link

After the LCP negotiation succeeds, 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
Do as follows on the routers configured with MP-Group interfaces:
Procedure
Step 1 Run:
system-view

The MP-Group interface view is displayed. Step 3 Run:

ppp mp threshold-least number
The minimum number of subchannels in the Up state in the MP link is set. Step 4 Run:
shutdown
The MP-Group interface is shut down. Step 5 Run:

undo shutdown
The MP-Group interface is restarted. ----End

Procedure
Step 1 Run the display current-configuration interface [ interface-type [ interface-number ] ] command to check the configuration of MP-Group interface. ----End
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 #
4-28
Issue 03 (2010-03-31)
interface Mp-group1/0/1 mrru 1200 ppp mp threshiold 2 ppp mp damping detect-time 32 flapping-count 32 damping-time 62# # return
4.8 Configuring MP Fragmentation

Describes how to configure the length of the MP fragment on the MP-Group interface. 4.8.1 Establishing the Configuration Task 4.8.2 Configuring the MP Fragment Function 4.8.3 Checking the Configuration

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
Connecting the interface and configuring the physical parameters of the interface to make the physical layer status of the interface change to Up. Configuring MP binding
Data Preparation
To configure MP fragmentation, you need the following data. No. 1 Data Length of the MP packet to be fragmented
4.8.2 Configuring the MP Fragment Function

Context
Using the MP fragment function, you can adjust the value of the MP fragment packets. By default, no fragment value is configured. Do as follows on the routers:
Procedure
Step 1 Run:
system-view

The MP group interface is displayed. Step 3 Run:

fragment-threshold threshold
The fragment value of MP data packet is configured. ----End

Procedure
Step 1 Run the display ppp mp [ interface interface-type interface-number ] command to check the MP binding information. ----End
Example
Run the display ppp mp command, you can view the binding information about the MP-Group. For example:
<HUAWEI> display ppp mp interface mp-group 1/0/1 Mp-group is Mp-group1/0/1 ===========Sublinks status begin====== Serial1/0/1:1 physical UP,protocol UP Serial1/0/1:2 physical UP,protocol UP Serial1/0/1:3 physical UP,protocol DOWN(damping) Serial1/0/1:4 physical UP,protocol DOWN ===========Sublinks status end======== Bundle Multilink, 2 member, slot 1, Master link is Mp-group1/0/1 0 lost fragments, 0 reordered, 0 unassigned, 0 interleaved, sequence 0/0 rcvd/sent The bundled son channels are: Serial1/0/1:1 Serial1/0/1:2
4.9 Maintaining PPP and MP Configuration

Describes how to maintain PPP and MP.
4-30
Issue 03 (2010-03-31)
Context
CAUTION
Debugging affects on the performance of the system. So, after the debugging, run the undo debugging all command to disable it immediately. When the operation faults of PPP and MP occur, use the debugging command in the user view to debug the PPP and MP link protocol and locate the fault. For the operation of the debugging, refer to the chapter "Information Center Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - System Management. For the debugging commands, refer to the HUAWEI NetEngine80E/40E Router Debugging Reference.
Procedure
l l Run the debugging ppp all [ verbose ] [ interface interface-type interface-number ] command to enable the debugging of PPP. Run the debugging ppp { ccp | chap | ipcp | lcp | mplscp | osicp | pap } { all | error | event | packet [ verbose ] | state } [ interface interface-type interface-number ] command to enable the debugging of the PPP control protocols. Run the debugging ppp mp { all | error | event | packet [ verbose ] } [ interface interfacetype interface-number ] command to enable the debugging of MP. Run the debugging ppp ipv6cp { all | error | event | packet | state } [ interface interfacetype interface-number ] command to enable the debugging of the IPv6 control protocol. Run the debugging ppp { cbcp | ip | mpls-multicast | mpls-unicast | osi-npdu | scp | vjcomp } packet [ verbose ] [ interface interface-type interface-number ] command to enable the debugging of the PPP packets. Run the debugging ppp ipv6 packet [ interface interface-type interface-number ] command to enable the debugging of the IPv6 packets. Run the debugging ppp core event [ interface interface-type interface-number ] command to enable the debugging of the PPP core events. Run the debugging ppp compression iphc { rtp | tcp } command to enable the debugging of the IPHC compression of PPP.
l l l
l l l
----End

Provides several configuration examples of PPP and MP. 4.10.1 Example for Configuring PAP Authentication 4.10.2 Example for Configuring Unidirectional CHAP Authentication 4.10.3 Example for Configuring Bidirectional CHAP Authentication 4.10.4 Example for Binding MPs into an MP-group
4.10.1 Example for Configuring PAP Authentication

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 diagram of PAP authentication
RouterA
POS1/0/0 RouterB 10.110.0.2/24
POS1/0/0 10.110.0.1/24
The configuration roadmap is as follows: 1. 2. 3. Add the user name and password of Router B to the local user list of Router A. Configure Router A to authenticate Router B in PAP mode. Configure the local user name and password on Router B.
Data Preparation
l l l
The user name and password of Router B The IP address of the interface on Router A The IP address of the interface on Router B
Procedure
Step 1 Configure Router A # Add the username and password of Router B to the local user list of Router A.
<HUAWEI> system-view [HUAWEI] sysname RouterA [RouterA] aaa [RouterA-aaa] local-user rtb password simple quidway [RouterA-aaa] quit
# Configure an IP address for POS 1/0/0 and configure the link-layer encapsulation protocol as PPP.
[RouterA] interface pos 1/0/0 [RouterA-Pos1/0/0] ip address 10.110.0.1 255.255.255.0 [RouterA-Pos1/0/0] link-protocol ppp
# Authenticate Router B in the PAP mode.


[RouterA-Pos1/0/0] ppp authentication-mode pap [RouterA-Pos1/0/0] undo shutdown
Step 2 Configure Router B. # Configure an IP address for POS 1/0/0 and configure the link-layer encapsulation protocol as PPP.
<HUAWEI> system-view [HUAWEI] sysname RouterB [RouterB] interface pos 1/0/0 [RouterB-Pos1/0/0] ip address 10.110.0.2 255.255.255.0 [RouterB-Pos1/0/0] link-protocol PPP
# Configure the username and password sent to the authentication object in the PAP mode.
[RouterB-Pos1/0/0] ppp pap local-user rtb password simple quidway [RouterB-Pos1/0/0] undo shutdown
Step 3 Verify the configuration. After the configuration is completed, executing the display interface command on every router, you can see the LCP status is Opened. Take Router A as an example.
<RouterA-Pos1/0/0] display interface pos 1/0/0 Pos1/0/0 current state : UP Line protocol current state : UP Last up time: 2007-11-03, 12:36:19 Description: Pos1/0/0 Interface Route Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Internet Address is 10.110.0.1/24 Link layer protocol is PPP LCP opened, IPCP opened The Vendor PN is FTRJ1321P1BTL Port BW: 2.5G, Transceiver max BW: 2.5G, Transceiver Mode: SingleMode WaveLength: 1310nm, Transmission Distance: 5km Rx Power: -3.91dBm, Tx Power: -1.87dBm Physical layer is Packet Over SDH Scramble enabled, clock master, CRC-32, loopback: none Flag J0 "NetEngine " Flag J1 "NetEngine " Flag C2 22(0x16) SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1 21424008 line layer: B2 1093838510 REI 705143440 path layer: B3 45521365 Statistics last cleared:never Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 152 bits/sec, 0 packets/sec Input: 18791 packets, 490767 bytes Input error: 10 shortpacket, 0 longpacket, 143 CRC, 0 lostpacket Output: 30960 packets, 1408202 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
----End
Configuration Files
l

# sysname RouterA
Issue 03 (2010-03-31)
4-33

# interface Pos 1/0/0 link-protocol ppp ppp authentication-mode pap undo shutdown ip address 10.110.0.1 255.255.255.0 # aaa local-user rtb password simple quidway # return l

# sysname RouterB # interface Pos1/0/0 link-protocol ppp ppp pap local-user rtb password simple quidway undo shutdown ip address 10.110.0.2 255.255.255.0 # return
4.10.2 Example for Configuring Unidirectional CHAP Authentication

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 diagram of unidirectional CHAP authentication
RouterA
POS1/0/0 RouterB 10.110.0.2/24
POS1/0/0 10.110.0.1/24
The configuration roadmap is as follows: 1. 2. 3. 4. 5. Add the user name and password of Router B to the local user list of Router A. Configure the local user name for Router A. Configure Router A to authenticate the peer in CHAP mode. Configure the local user list on Router B. Configure the local user name for Router B.
Data Preparation

l l l l
Local user name of Router A Local user name and password of Router B IP address of the interface on Router A IP address of the interface on Router B
Procedure
Step 1 Configure Router A. # Add the username and password of Router B to the local user list of Router A.
<HUAWEI> system-view [HUAWEI] sysname RouterA [RouterA] aaa [RouterA-aaa] local-user rtb password simple hello [RouterA-aaa] quit
# Configure the local to authenticate the peer in CHAP mode.

[RouterA-Pos1/0/0] ppp authentication-mode chap
# Configure the local username of RouterA

[RouterA-Pos1/0/0] ppp chap user rta
# Enable the interface.

[RouterA-Pos1/0/0] undo shutdown
Step 2 Configure Router B # Add the user name of Router A and the local password to the local user list of Router B.
<HUAWEI> system-view [HUAWEI] sysname RouterB [RouterB] aaa [RouterB-aaa] local-user rta password simple hello [RouterB-aaa] quit
# Configure the IP address for POS 1/0/0 and configure the link-layer encapsulation protocol as PPP.
[RouterB] interface pos 1/0/0 [RouterB-Pos1/0/0] ip address 10.110.0.2 255.255.255.0 [RouterB-Pos1/0/0] link-protocol ppp
# Configure the peer to authenticate the local in CHAP mode.

[RouterB-Pos1/0/0] ppp chap user rtb [RouterB-Pos1/0/0] undo shutdown
Step 3 Verify the configuration. After the configuration is complete, running the display interface command on every router, you can find the LCP state is LCP opened. Take the Router A as the example.
[RouterA] display interface pos 1/0/0 Pos1/0/0 current state : UP
Issue 03 (2010-03-31)
4-35
Line protocol current state : UP Last up time: 2007-11-03, 12:36:19 Description: Pos1/0/0 Interface Route Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Internet Address is 10.110.0.1/24 Link layer protocol is PPP LCP opened, IPCP opened The Vendor PN is FTRJ1321P1BTL Port BW: 2.5G, Transceiver max BW: 2.5G, Transceiver Mode: SingleMode WaveLength: 1310nm, Transmission Distance: 5km Rx Power: -3.91dBm, Tx Power: -1.87dBm Physical layer is Packet Over SDH Scramble enabled, clock master, CRC-32, loopback: none Flag J0 "NetEngine " Flag J1 "NetEngine " Flag C2 22(0x16) SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1 21424008 line layer: B2 1093838510 REI 705143440 path layer: B3 45521365 Statistics last cleared:never Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 152 bits/sec, 0 packets/sec Input: 18791 packets, 490767 bytes Input error: 10 shortpacket, 0 longpacket, 143 CRC, 0 lostpacket Output: 30960 packets, 1408202 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
----End
Configuration Files
l

# sysname RouterA # interface Pos1/0/0 link-protocol ppp ppp authentication-mode chap ppp chap user rta undo shutdown ip address 10.110.0.1 255.255.255.0 # aaa local-user rtb password simple hello # return

# sysname RouterB # interface Pos1/0/0 link-protocol ppp ppp chap user rtb undo shutdown ip address 10.110.0.2 255.255.255.0 # aaa local-user rta password simple hello # return
4-36
Issue 03 (2010-03-31)
4.10.3 Example for Configuring Bidirectional CHAP Authentication

As shown in Figure 4-3, Router A and Router B need to perform bidirectional CHAP authentication. Figure 4-3 Networking diagram of bidirectional CHAP authentication
RouterA
POS1/0/0 RouterB 10.110.0.2/24
POS1/0/0 10.110.0.1/24
The configuration roadmap is as follows: 1. 2. 3. Configure the local user lists on Router A and Route B. Configure local user names for Router A and Router B. Enable CHAP authentication on the interfaces of Router A and Route B.
Data Preparation
l l l l
The user names of Router A and Router B The passwords of Router A and Router B The IP address of the interface on Router A The IP address of the interface onRouter B
NOTE
Router A and Router B must be configured with the same password, or the authentication fails.
Procedure
<HUAWEI> system-view [HUAWEI] sysname RouterA [RouterA] aaa [RouterA-aaa] local-user rtb password simple hello [RouterA-aaa] quit
Issue 03 (2010-03-31)
4-37
# Configure the username of Router A used in its authentication by Router B in the CHAP mode.
[RouterA-Pos1/0/0] ppp chap user rta
# Configure the authentication in CHAP mode.

[RouterA-Pos1/0/0] ppp authentication-mode chap [RouterA-Pos1/0/0] undo shutdown
Step 2 Configure Router B. # Add the username of Router A and the local password to the local user list of Router B.
<HUAWEI> system-view [HUAWEI] sysname RouterB [RouterB] aaa [RouterB-aaa] local-user rta password simple hello [RouterB-aaa] quit
[RouterB] interface pos 1/0/0 [RouterB-Pos1/0/0] ip address 10.110.0.2 255.255.255.0 [RouterB-Pos1/0/0] link-protocol ppp
# Configure the user name of Router B used in its authentication by Router A in the CHAP mode.
[RouterB-Pos1/0/0] ppp chap user rtb
# Configure the authentication in CHAP mode.

[RouterB-Pos1/0/0] ppp authentication-mode chap [RouterB-Pos1/0/0] undo shutdown
Step 3 Verify the configuration. After the configuration is completed, running the display interface command on every router, you can see the LCP status is Opened.
[RouterA] display interface pos 1/0/0 Pos1/0/0 current state : UP Line protocol current state : UP Last up time: 2007-11-03, 12:36:19 Description: Pos1/0/0 Interface Route Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Internet Address is 10.110.0.1/24 Link layer protocol is PPP LCP opened, IPCP opened The Vendor PN is FTRJ1321P1BTL Port BW: 2.5G, Transceiver max BW: 2.5G, Transceiver Mode: SingleMode WaveLength: 1310nm, Transmission Distance: 5km Rx Power: -3.91dBm, Tx Power: -1.87dBm Physical layer is Packet Over SDH Scramble enabled, clock master, CRC-32, loopback: none Flag J0 "NetEngine " Flag J1 "NetEngine " Flag C2 22(0x16) SDH alarm: section layer: none line layer: none path layer: none SDH error:
4-38
Issue 03 (2010-03-31)
section layer: B1 21424008 line layer: B2 1093838510 REI 705143440 path layer: B3 45521365 Statistics last cleared:never Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 152 bits/sec, 0 packets/sec Input: 18791 packets, 490767 bytes Input error: 10 shortpacket, 0 longpacket, 143 CRC, 0 lostpacket Output: 30960 packets, 1408202 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
----End
Configuration Files
l

# sysname RouterA # interface Pos1/0/0 link-protocol ppp ppp authentication-mode chap ppp chap user rta undo shutdown ip address 10.110.0.1 255.255.255.0 # aaa local-user rtb password simple hello # return

# sysname RouterB # interface Pos1/0/0 link-protocol ppp ppp authentication-mode chap ppp chap user rtb undo shutdown ip address 10.110.0.2 255.255.255.0 # aaa local-user rta password simple hello # return
4.10.4 Example for Binding MPs into an MP-group

For the two serial interfaces of Router A and Router B are connected respectively with each other, you can bind MP group to configure MP binding. Figure 4-4 Networking diagram of the MP-group binding
Mp-group1/0/1 111.1.1.1/24 Serial1/0/0:0

Router A
Mp-group2/0/1 111.1.1.2/24 Serial2/0/0:0 Serial2/0/1:0 Router B

4-39
Serial1/0/1:0
Issue 03 (2010-03-31)
The configuration roadmap is as follows: 1. 2. 3. 4. Configure the local user lists on Router A and Router B. Enable PAP authentication on Router A and Router B. Create MP-group interface and add related interfaces to MP-group. Restart interfaces to validate the configuration.
Data Preparation
l l l
The IP addresses of the Mp-groups on Router A The IP addresses of the Mp-groups on Router B The bound sub-tunnel is authenticated by the PAP
NOTE
l l l
The slot number and card number of MP-Group interface must be consistent with the slot number and card number of the interface added to the MP-Group. The interfaces added to the MP-group can only be the serial interfaces instead of other interfaces. PAP or CHAP authentication is unnecessarily configured when you configure MP binding by using MP-group.
Procedure
<RouterA> system-view [RouterA] aaa [RouterA-aaa] local-user rtb password simple rtb [RouterA-aaa] quit
# Create an Mp-group interface and configure the corresponding interface.

[RouterA] interface mp-group1/0/1 [RouterA-Mp-group1/0/1] ip address 111.1.1.1 255.255.255.0 [RouterA-Mp-group1/0/1] shutdown [RouterA-Mp-group1/0/1] quit
# Configure Serial 1/0/0:0 to perform the PAP authentication.

[RouterA] interface serial1/0/0:0 [RouterA-Serial1/0/0:0] link-protocol ppp [RouterA-Serial1/0/0:0] ppp authentication-mode pap [RouterA-Serial1/0/0:0] ppp pap local-user rta password simple rta [RouterA-Serial1/0/0:0] shutdown
# Add Serial 1/0/0:0 to the Mp-group interface.

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

[RouterA] interface Serial1/0/1:0
4-40
Issue 03 (2010-03-31)

[RouterA-Serial1/0/1:0] [RouterA-Serial1/0/1:0] [RouterA-Serial1/0/1:0] [RouterA-Serial1/0/1:0]

link-protocol ppp ppp authentication-mode pap ppp pap local-user rta password simple rta shutdown

[RouterA-Serial1/0/1:0] ppp mp mp-group1/0/1 [RouterA-Serial1/0/1:0] quit
Step 2 Configure Router B. # Add the username and password of Router A to the local user list of Router B.
<RouterB> system-view [RouterB] aaa [RouterB-aaa] local-user rta password simple rta [RouterB-aaa] quit
# Create an Mp-group interface and configure the corresponding IP address.

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

[RouterB] interface serial2/0/0:0 [RouterB-Serial2/0/0:0] link-protocol ppp [RouterB-Serial2/0/0:0] ppp authentication-mode pap [RouterB-Serial2/0/0:0] ppp pap local-user rtb password simple rtb [RouterB-Serial2/0/0:0] shutdown

[RouterB-Serial2/0/0:0] ppp mp mp-group2/0/1 [RouterB-Serial2/0/0:0] quit
# Configure Serial 2/0/1:0 and perform the PAP authentication.

[RouterB] interface serial2/0/1:0 [RouterB-Serial2/0/1:0] link-protocol ppp [RouterB-Serial2/0/1:0] ppp authentication-mode pap [RouterB-Serial2/0/1:0] ppp pap local-user rtb password simple rtb [RouterB-Serial2/0/1:0] shutdown

[RouterB-Serial2/0/1:0] ppp mp mp-group2/0/1 [RouterB-Serial2/0/1:0] quit
Step 3 Bind the sub-tunnel. # Restart the sub-tunnel on Router A.

[RouterA] interface serial1/0/0:0 [RouterA-Serial1/0/0:0] undo shutdown [RouterA-Serial1/0/0:0] quit [RouterA] interface serial1/0/1:0:0 [RouterA-Serial1/0/1:0:0] undo shutdown [RouterA-Serial1/0/1:0:0] quit [RouterA] interface mp-group1/0/1 [RouterA-Mp-group1/0/1] undo shutdown [RouterA-Mp-group1/0/1] quit
# Restart the sub-tunnel on Router B.

[RouterB] interface serial2/0/0:0 [RouterB-Serial2/0/0:0] undo shutdown
Issue 03 (2010-03-31)
4-41

[RouterB-Serial2/0/0:0] quit [RouterB] interface serial2/0/1:0 [RouterB-Serial2/0/1:0] undo shutdown [RouterB-Serial2/0/1:0] quit [RouterB] interface mp-group2/0/1 [RouterB-Mp-group2/0/1] undo shutdown [RouterB-Mp-group2/0/1] quit
Step 4 Verify the configuration. # Check the configuration on Router A.

[RouterA] display ppp mp interface Mp-group1/0/1 Mp-group is Mp-group1/0/1 ===========Sublinks status begin====== Serial1/0/0:0 physical UP,protocol UP Serial1/0/1:0 physical UP,protocol UP ===========Sublinks status end======== Bundle Multilink, 2 member, slot 0, Master link is Mp-group1/0/1 0 lost fragments, 0 reordered, 0 unassigned, 0 interleaved, sequence 0/0 rcvd/sent The bundled son channels are: Serial1/0/0:0 Serial1/0/1:0
# Check the Mp-group 2/0/1 status on Router B.

[RouterB] display ppp mp interface Mp-group2/0/1 Mp-group is Mp-group2/0/1 ===========Sublinks status begin====== Serial2/0/0:0 physical UP,protocol UP Serial2/0/1:0 physical UP,protocol UP ===========Sublinks status end======== Bundle Multilink, 2 member, slot 2, Master link is Mp-group2/0/ 0 lost fragments, 0 reordered, 0 unassigned, 0 interleaved, sequence 0/0 rcvd/sent The bundled son channels are: Serial2/0/0:0 Serial2/0/1:0
You can ping through the IP address of the MP-group 2/0/1 on Router A.
ms ms ms ms ms
----End
Configuration Files
l

# sysname RouterA # interface Serial1/0/0:0 undo shutdown link-protocol ppp ppp authentication-mode pap ppp pap local-user rta password simple rta
4-42
Issue 03 (2010-03-31)

ppp mp Mp-group 1/0/1 # interface Serial1/0/1:0 undo shutdown link-protocol ppp ppp authentication-mode pap ppp pap local-user rta password simple rta ppp mp Mp-group 1/0/1 # interface Mp-group1/0/1 undo shutdown ip address 111.1.1.1 255.255.255.0 # aaa local-user rtb password simple rtb # return l

# sysname RouterB # interface Serial2/0/0:0 undo shutdown link-protocol ppp ppp authentication-mode pap ppp pap local-user rtb password simple rtb ppp mp Mp-group 2/0/1 # interface Serial2/0/1:0 undo shutdown link-protocol ppp ppp authentication-mode pap ppp pap local-user rtb password simple rtb ppp mp Mp-group 2/0/1 # interface Mp-group2/0/1 undo shutdown ip address 111.1.1.2 255.255.255.0 # aaa local-user rta password simple rta # return
Issue 03 (2010-03-31)
4-43
5 Frame Relay Configuration
5
About This Chapter
Frame Relay Configuration
Describes frame relay related concepts and configuration steps for frame relay compression, LMI type, frame relay switching, and PVC standby groups, along with typical examples. 5.1 Introduction to Frame Relay Describes concepts and fundamentals of FR. 5.2 Configuring FR Describes how to configure FR. 5.3 Configuring FR LMI Type and Related Parameters Describes how to configure FR LMI. 5.4 Maintaining Frame Relay Configuration Describes how to maintain FR . 5.5 Configuration Examples Provides several configuration examples of FR.
Issue 03 (2010-03-31)
5-1
5.1 Introduction to Frame Relay

Describes concepts and fundamentals of FR. 5.1.1 FR Protocol Overview 5.1.2 Features of FR on the NE80E/40E
5.1.1 FR Protocol Overview

A Frame Relay (FR) network provides data communication between user devices (such as routers and hosts). According to different functions, 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 the NNI interface. For the equipment used for FR switching, its FR interface type should be NNI or DCE. A 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

On the NE80E/40E, the POS interfaces support the frame relay.
5.2 Configuring FR
Describes how to configure FR. 5.2.1 Establishing the Configuration Task 5.2.2 Configuring Basic FR Functions 5.2.3 Checking the Configuration

FR is a fast packet switching technology developed on the basis of X.25 technology. It implements bandwidth multiplexing and dynamic allocation, provides a reasonable bandwidth management and congestion avoidance mechanism, and is widely used. FR has two kinds of protocols: Internet Engineering Task Force (IETF) and nonstandard.
IETF is used to encapsulate the packets according to RFC 1490 specifications and nonstandard is used to interconnect with routers of other vendors. In FR, both parties in communication are distinguished as DTE and DCE and they configure the interface with DTE or DCE format according to their respective location in a network. The FR module has two types of interfaces: main interface and sub-interface. The NE80E/40E can communicate with other devices only through P2P sub-itnerfaces if the link layer protocol is FR. For the network layer, the sub-interface can be used to configure the PVC. This PVC is used to connect with 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. 1 2 3 4 Data FR interface number of a router and IP addresses to be allocated Interface number of multilink FR bundle DLCI to be allocated to the interface Interface number of the FR sub-interfaces
5.2.2 Configuring Basic FR Functions

Context
Procedure
Step 1 Run:
system-view

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. A FR sub-interface can be created only after the FR main interface is configured.
NOTE
After the FR encapsulation format of the interface is changed, the system automatically deletes all the FR configurations on the interface. Then, you need to delete all the sub-interfaces to re-configure the FR. After modifying the link layer protocol, you need to 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.
Step 4 ( Optional )Run:

fr interface-type { dte |dce }
The type of the FR interface is configured. By default, the FR interface type is DTE. Step 5 Run:
quit

interface interface-type interface-number.subnumber
An FR sub-interface is created.
NOTE
l l l
NE80E/40E supports the FR sub-itnerfaces only in P2P mode. An FR sub-interface must be of the same type as that of its main interface. 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


Prerequisite
The configurations of FR are complete.
Procedure
l 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. Run the display fr map-info [ interface interface-type interface-number[.subnumber ] ] command to check the mapping between the protocol address and the FR address.
----End
Example
Run the display fr interface command. If the status of the FR protocol and information about the interface are displayed, it means the configuration succeeds.
<HUAWEI> display fr interface Pos1/0/0, DTE, physical up, protocol up Pos1/0/0.1, point-to-point, protocol up Pos1/0/0.2, point-to-point, protocol up
Run the display fr map-info command. If the mapping between the protocol address and the FR address is displayed, it means the configuration succeeds. Detailed address mapping information is not displayed for P2P sub-interfaces.
<HUAWEI> display fr map-info Map Statistics for interface Pos2/1/0 (DCE) DLCI 20, Point-to-Point DLCI, Pos2/1/0.1 created at: 2009/02/12 11:17:37, status: ACTIVE
5.3 Configuring FR LMI Type and Related Parameters

Describes how to configure FR LMI. 5.3.1 Establishing the Configuration Task 5.3.2 Configuring FR LMI and Related Parameters of DTE 5.3.3 Configuring FR LMI and Related Parameters of DCE 5.3.4 Checking the Configuration

When the LMI protocol is needed to maintain link status and PVC status of FR as well as optimize the running of the device, you need to configure the LMI type and related parameters.
Before configuring FR LMI type and related parameters, complete the following tasks:

l l
Configuring physical parameters for Frame Relay interfaces Configuring Frame Relay interfaces
Data Preparation
To configure the FR LMI type and related parameters, you need the following data: No. 1 2 3 Data FR interface number of a router and IP addresses to be allocated Required n391, n392 and n393 parameters as well as polling interval on DTE Required n392, n393 and t392 parameters on DCE
5.3.2 Configuring FR LMI and Related Parameters of DTE

Procedure
Step 1 Run:
system-view


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:

5-6
Issue 03 (2010-03-31)
The DTE N393 parameter is configured. ----End
5.3.3 Configuring FR LMI and Related Parameters of DCE

Procedure
Step 1 Run:
system-view


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

Prerequisite
The configurations of FR LMI type and related parameters are complete.
Procedure
l Run the display fr lmi-info [ interface interface-type interface-number ] command to check statistics about FR LMI packets.
----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 Maintaining Frame Relay Configuration

Describes how to maintain FR . 5.4.1 Clearing the Statistics of FR and Dynamic Address Mapping Entries 5.4.2 Debugging FR
5.4.1 Clearing the Statistics of FR and Dynamic Address Mapping Entries

Procedure
l Run the reset counters interface [ interface-type [ interface-number ] ] command to check the interface statistics displayed by running the display interface command.
----End
5.4.2 Debugging FR
Context
CAUTION
Debugging affects the performance of the system. So, after the debugging, run the undo debugging all command to disable it immediately. When a fault of FR occurs, execute the following debugging commands in user view to debug FR and to locate the fault. For detailed steps, refer to the "Information Center Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - System Management. For the description of debugging commands, refer to the HUAWEI NetEngine80E/40E Router Debugging Reference.
NOTE
l l l
If the debugging is enabled globally, running the same debugging command on the interface does not take effect. If the debugging is disabled globally, running the same undo debugging command on the interface does not take effect. If the verbose option has been selected, to disable it, use the undo debugging command. For example, after the debugging fr packet ip verbose command is executed, the debugging fr packet ip command does not take effect, and the previous output of the debugging fr packet ip verbose command remains.
5-8
Issue 03 (2010-03-31)
Procedure
l Run the debugging fr { all | compress | congestion | de | lmi | transmit-rate } [ interface interface-type interface-number ] debugging fr { event | ipc } command in the user view to enable the FR debugging. Run the debugging fr fragment interface interface-type interface-number dlci-number command in the user view to enable the packet fragment debugging. Run the debugging fr inarp [ verbose ] [interface interface-type inertface-number [ dlci dlci-number] ] command in the user view to enable the FR inverse ASP. (The 64byte packets can be output if the verbose is chosen.) Run the debugging fr packet [ ip | mpls | isis | switch | error ] [ verbose ] [ interface interface-type inertface-number [ dlci dlci-number ] ] command in the user view to enable the FR packets debugging and output the debugging information according to different packets.
l l
----End

Provides several configuration examples of FR. 5.5.1 Example for Connecting Devices with POS Interfaces Through FR Network
5.5.1 Example for Connecting Devices with POS Interfaces Through FR Network
As shown in Figure 5-1, routers are interconnected through POS interfaces on the FR network,and routers work in DTE mode as user devices. Router A connects Router B and Router C, which reside on different network segments from Router A, through sub-interfaces. Figure 5-1 Networking diagram of connecting routers using the POS interface through FR network
POS1/0/0.1 DLCI=21 10.1.1.1/30
POS1/0/0.1 DLCI=21 10.1.1.2/30 Frame Relay network POS1/0/0.2 DLCI=22 10.2.1.2/30
Router B
Router A POS1/0/0.2 DLCI=22 10.2.1.1/30
Router C
Issue 03 (2010-03-31)
5-9
The configuration roadmap is as follows: 1. 2. 3. 4. Configure FR as the link protocol. Configure the working mode for interfaces. Configure IP addresses for interfaces. Configure the address mapping.
Data Preparation
l l l l
IP address and DLCI of POS 1/0/0.1 on Router A IP address and DLCI of POS 1/0/0.2 on Router A IP address and DLCI of POS 1/0/0.1 on Router B IP address and DLCI of POS 1/0/0.2 on Router C
Procedure
<HUAWEI> system-view [HUAWEI] sysname RouterA [RouterA] interface pos 1/0/0
# Encapsulate the FR protocol.

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


Step 2 Configure Router B and Router C. The method of configuring Router B and Router C is the same as the method of configuring Router A. The configuration details are not mentioned here.
Step 3 Verify the configuration. Run the display interface pos command on each router. You can find that the connectivity of POS interfaces is Up. Run the ping command on each router. Each router can ping through the network. ----End
Configuration Files
l

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

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

# sysname RouterC # interface Pos1/0/0 link-protocol fr undo shutdown # interface Pos1/0/0.2 fr dlci 22 ip address 10.2.1.2 255.255.255.252 # return
Issue 03 (2010-03-31)
5-11
6 HDLC and IP-Trunk Configuration
HDLC and IP-Trunk Configuration
About This Chapter

Describes how to encapsulate an interface with HDLC protocol, how to configuration IP-Trunk interface and how to set the polling interval. 6.1 Introduction to HDLC and IP-Trunk Describes the concepts of HDLC and IP-Trunk interfaces. 6.2 Configuring HDLC Describes how to configure HDLC. 6.3 Configuring an IP-Trunk Interface Describes how to configure an IP-Trunk interface and the basic parameters of the interface. 6.4 Maintaining HDLC and IP-Trunk Configuration Describes how to maintain HDLC and IP-Trunk interfaces. 6.5 Configuration Examples Provides several configuration examples of HDLC.
Issue 03 (2010-03-31)
6-1
6.1 Introduction to HDLC and IP-Trunk

Describes the concepts of HDLC and IP-Trunk interfaces. 6.1.1 HDLC and IP-Trunk Interface Overview 6.1.2 Features of HDLC and IP-Trunk interfaces on the router
6.1.1 HDLC and IP-Trunk Interface Overview

The High-level Data Link Control (HDLC) is a bit-oriented link layer protocol. HDLC is featured by its transparent transmission of any kind of bit flow. The data is not required to be a character set. A trunk is aggregated by multiple ports among which load balancing is carried out. A trunk can enhance the connection reliability. Trunk interfaces are divided into Eth-Trunk interface and IP-Trunk interface. The IP-Trunk consists of POS links only. The Eth-Trunk consists of Ethernet links only. For configuration of the Eth-Trunk interface, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - LAN Access & MAN Access. The IP-Trunk technology has the following advantages:
l
Increasing bandwidth: Bandwidth of an IP-Trunk interface is the sum of all the bandwidth of member ports. Enhancing reliability: If a member link failed, traffic is automatically switched to other available links.
6.1.2 Features of HDLC and IP-Trunk interfaces on the router

The protocols in standard HDLC suite operate on the synchronous serial lines. The IP-Trunk consists of POS links only. The link layer protocol of the member interface joining the IP-Trunk interface must be HDLC. Up to 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:
l
Supports configured IP addresses. When forwarding packets, each member interface uses the IP address of the IP-Trunk interface. Supports MPLS forwarding, and Layer 3 forwarding (including unicast and multicast). The Hash algorithm can be used in load balancing by flow. Supports QoS based on physical ports rather than logical ports. Supports MPLS and binding VPN instances. Supports hot backup and hot swap.
l l l
6-2
Issue 03 (2010-03-31)

NOTE
If member ports of the Trunk are not on the same LPU, you need to configure the BFD session to detect the links between member ports and configure the association between process pst and interfaces in the BFD session. Otherwise, in some scenarios (for example, restarting the LPU where member ports of the Trunk locate), traffic loss can be caused. For detailed configurations of BFD, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - Reliability.
6.2 Configuring HDLC

Describes how to configure HDLC. 6.2.1 Establishing the Configuration Task 6.2.2 Encapsulating an Interface with HDLC 6.2.3 Configuring the IP Address of the Interface 6.2.4 Setting the Polling Interval 6.2.5 Checking the Configuration

When you need to enable the bits synchronous transmission using the link layer protocol, you can adopt the HDLC protocol.
Before configuring the basic HDLC functions, configure the physical attributes of the interface to make the physical status of the interface become Up.
Data Preparation
To configure HDLC, you need the following data. No. 1 Data Numbers of the interfaces on the router
6.2.2 Encapsulating an Interface with HDLC

Procedure
Step 1 Run:
system-view

Issue 03 (2010-03-31)
6-3

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

Procedure
Step 1 Run:
system-view

The interface view is displayed. Step 3 Choose one of the following steps to configure the IP address or IP unnumbered address of the interface as required.
l
Run the ip address ip-address { mask | mask-length } [ sub ] command to configure the IP address of the interface. Run the ip address unnumbered interface interface-type interface-number command to configure the IP unnumbered address.
NOTE
If you configure IP address unnumbered on an interface encapsulated with HDLC, the borrower must have the ability to learn the route to the remote end. Otherwise, it cannot reach the remote end.
When you use IP address unnumbered, you can configure static route or dynamic routing protocol to make the borrower learn the route to the remote end. Note the following principles:
l
If you use dynamic routing protocol, ensure the length of the learned route mask is longer than that of the lender's IP address mask, because the NE80E/40E adopts the principle of longest match in routing lookup. If you use static route and the IP address of the lender adopts 32-bit mask, the length of the static route mask should be shorter than 32 bits. If you use static route and the IP address of the lender adopts a mask less than 32 bits, the length of the static route mask should be longer than that of the lender's IP address mask.
----End
6.2.4 Setting the Polling Interval

Procedure
Step 1 Run:
system-view
6-4
Issue 03 (2010-03-31)


timer hold seconds
The polling interval is configured. By default, the pooling interval is 10 seconds. If it is set to 0, then link detection is prohibited. The link layer protocols such as PPP, FR, and HDLC adopt a polling timer to check the status of a link. Configure identical polling interval on the both ends. You can adopt the default polling interval or adjust the polling interval as required. In the case of long network delay or high congestion, you can prolong the polling interval to reduce the possibility of network flapping.
NOTE
The GE interfaces, MP-Group interfaces do not support this configuration.
----End

Prerequisite
The configurations of HDLC are complete.
Procedure
l Run the display interface [ interface-type [ interface-number ] ] [ | { begin | exclude | include } regular-expression ] command to check the status, link layer protocol and configuration of the interface.
----End
Example
Run the display interface command, you can view the status, link layer protocol and configuration of the interface.
<HUAWEI> display interface pos 1/0/0 Pos1/0/0 current state : UP Line protocol current state : UP Last line protocol up time : 2003-01-28 11:19:00 Description: Pos1/0/0 Interface Route Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Internet Address is 192.168.19.2/24 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 Physical layer is Packet Over SDH Scramble enabled, clock master, CRC-32, loopback: none Flag J0 "NetEngine " Flag J1 "NetEngine "
Issue 03 (2010-03-31)
6-5
Flag C2 22(0x16) SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1 0 line layer: B2 0 REI 16802934 path layer: B3 0 REI 66775 Statistics last cleared:never Last 300 seconds input rate 72 bits/sec, 0 packets/sec Last 300 seconds output rate 24 bits/sec, 0 packets/sec Input: 1642 packets, 35940 bytes Input error: 0 shortpacket, 0 longpacket, 3 CRC, 0 lostpacket Output: 1475 packets, 24008 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
6.3 Configuring an IP-Trunk Interface

Describes how to configure an IP-Trunk interface and the basic parameters of the interface. 6.3.1 Establishing the Configuration Task 6.3.2 Creating an IP-Trunk and adding POS Interfaces into the IP-Trunk 6.3.3 Configuring an IP Address for the IP-Trunk Interface 6.3.4 (Optional) Configuring the Lower Threshold of Up Links 6.3.5 (Optional) Configuring Load-balancing Mode for the IP-Trunk Interface 6.3.6 (Optional) Configuring Weights for Member Links 6.3.7 (Optional) Configuring the Method of Sending Trap Messages from an IP-Trunk Member Interface 6.3.8 Checking the Configuration

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 bandwidth of all the member interfaces. IP-Trunk interfaces can realize load balancing. Traffic to the same destination is transported on different member links to avoid congestion. In addition, IP-Trunk interfaces can improve link reliability. If a member port is Down, traffic is switched to other available ports.
None
Data Preparation
To create an IP-Trunk interface, you need the following data.
No. 1 2 3 4 5 6
Data IP-Trunk ID IP address of the IP-Trunk interface Lower threshold of Up links Load balancing mode Type and number of the backup port Weight of the member port
6.3.2 Creating an IP-Trunk and adding POS Interfaces into the IPTrunk
Context
Procedure
Step 1 Run:
system-view

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. By default, the link layer protocol of a POS interface is PPP. You need to run the linkprotocol hdlc command in the POS interface view to change the link layer protocol to HDLC. Before adding an interface to an IP-Trunk, ensure the interface is not configured with any Layer 3 feature or service. A POS interface can join only one IP-Trunk interface. To add the POS interface to another IP-Trunk interface, you must remove it from the original IP-Trunk first. Member interfaces of an IP-Trunk cannot be IP-Trunks. The POS interfaces of different interface boards can be added into the same IP-Trunk. Do not bind interfaces with different forwarding capabilities to an IP-Trunk. 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 is 5 Gbit/s rather than 12.5 Gbit/s. If an IP-Trunk is created on a local device, the peer device interfaces that are directly connected with the member interfaces must be bound to an IP-Trunk interface. Otherwise, the two ends cannot communicate.
l l l l
Step 7 Run:
undo shutdown
The interface is enabled. ----End
6.3.3 Configuring an IP Address for the IP-Trunk Interface

Context
Do as follows on the routers that are configured with IP-Trunk interfaces.
Procedure
Step 1 Run:
system-view

The IP-Trunk interface view is displayed. Step 3 Run:

ip address ip-address { mask | mask-length } [ sub ]
The IP address is configured for the IP-Trunk interface. ----End

6.3.4 (Optional) Configuring the Lower Threshold of Up Links

Context
Do as follows on the routers configured with IP-Trunk interfaces.
Procedure
Step 1 Run:
system-view

The view of the IP-Trunk interface is displayed. Step 3 Run:

least active-linknumber link-number
The lower threshold of the member links in the Up state is configured. By default, the lower threshold is 1. That is, an IP-Trunk remains Up as long as one member interface is Up.
NOTE
To ensure normal forwarding, it is recommended to configure the same lower threshold on the Trunk interfaces at both ends of the same Trunk link.
----End
6.3.5 (Optional) Configuring Load-balancing Mode for the IPTrunk Interface

Context
Do as follows on the routers configured with IP-Trunk interfaces.
Procedure
Step 1 Run:
system-view

The view of the IP-Trunk interface is displayed. Step 3 Run:

load-balance { ip | packet-all }
The load-balancing mode of the IP-Trunk interface is configured. By default, load balancing is carried out among IP-Trunk member interfaces based on ip.

l
Load balancing based on IP addresses can guarantee the packet order, but cannot improve the bandwidth usage. Packet-by-packet load balancing can improve the bandwidth usage, but cannot guarantee the packet order.
----End
6.3.6 (Optional) Configuring Weights for Member Links

Context
For an IP-Trunk interface, sum of weights of all its member interfaces cannot be greater 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 is, the heavier the traffic on the member link is. Do as follows on the routers configured with IP-Trunk interfaces.
Procedure
Step 1 Run:
system-view

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, you need to run the shutdown and undo shutdown commands to restart the member interface so that the configuration can take effect.
----End
6.3.7 (Optional) Configuring the Method of Sending Trap Messages from an IP-Trunk Member Interface
Context
Do as follows on the device where IP-Trunk interfaces are created:
Procedure
Step 1 Run:
system-view

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

Prerequisite
The configurations of an IP-Trunk Interface are complete.
Procedure
l l l Run the display interface ip-trunk [ trunk-id ] [ | { begin | exclude | include } regularexpression ] command to check the status of the IP-Trunk interface. Run the display trunkmembership ip-trunk trunk-id [ slot slot-id ] command to check information about the IP-Trunk member interface. 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 Line protocol current state : UP Last line protocol up time: 2007-11-03, 17:45:06 Description : HUAWEI, Quidway Series, Ip-Trunk1 Interface Route Port,Hash arithmetic : According to IP,The Maximum Transmit Unit is 4470 Internet Address is 10.2.1.1/19 Link layer protocol is nonstandard HDLC Physical is IP_TRUNK Statistics last cleared: 2008-08-02 15:32:27 Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets,0 bytes,
Issue 03 (2010-03-31)
6-11
0 unicast,0 broadcast,0 multicast 0 errors,0 drops,0 unknownprotocol Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicast 0 errors,0 drops ----------------------------------------------------PortName Status Weight ----------------------------------------------------Pos1/0/0 UP 1 ----------------------------------------------------The Number of Ports in Trunk : 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 standby interface NULL
Run the display trunkfwdtbl ip-trunk command. You can view the forwarding table of an IPTrunk 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

Describes how to maintain HDLC and IP-Trunk interfaces. 6.4.1 Clearing the statistics of the HDLC or IP-Trunk interfaces 6.4.2 Debugging HDLC
6-12
Issue 03 (2010-03-31)
6.4.1 Clearing the statistics of the HDLC or IP-Trunk interfaces

Context
CAUTION
The previous statistics cannot be restored after you clear them. So, confirm the action before you use the command. To reset the interface statistics of the Network Management System (NMS) or that displayed by running the display interface command, run the following commands in the user view.
NOTE
Procedure
----End
6.4.2 Debugging HDLC

Context
CAUTION
Debugging affects the performance of the system. So, after debugging, run the undo debugging all command to disable it immediately. When an HDLC fault occurs, run the following debugging commands in the user view to debug HDLC, view the debugging information, and locate and analyze the fault. For the procedure of displaying the debugging information, refer to the "Information Center Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - System Management. For the description of debugging commands, refer to the HUAWEI NetEngine80E/40E Router Debugging Reference.
NOTE
l l
If a debugging is enabled globally, running the same debugging command on the interface does not take effect. If a debugging is disabled globally, running the same undo debugging command on the interface does not take effect.
Issue 03 (2010-03-31)
6-13
Procedure
l l l Run the debugging hdlc all command in the user view to enable all HDLC debugging. Run the debugging hdlc event [ interface interface-type interface-number ] command in the user view to enable HDLC event debugging. Run the debugging hdlc { ip | ipv6 | isis | keepalive } { in | in-out | out } [ interface interface-type interface-number ] command in the user view to enable HDLC packet debugging.
----End

Provides several configuration examples of HDLC. 6.5.1 Example for Configuring HDLC 6.5.2 Example for Configuring IP Address Unnumbered for HDLC 6.5.3 Example for Configuring an IP-Trunk
6.5.1 Example for Configuring HDLC

Router A and Router B are connected by POS interfaces, and the interfaces are required to run HDLC. Figure 6-1 Networking diagram of the HDLC functions
POS1/0/0 100.1.1.1/24
POS1/0/0 100.1.1.2/24
RouterA
RouterB
The configuration roadmap is as follows: 1. 2. Configure the link protocol of each interface to HDLC. Configure the IP address of each interface.
Data Preparation
To configure DHCP, you need the following data:
l l
IP address of the interface on Router A IP address of the interface on Router B

6-14

NOTE
The IP addresses of Router A and Router B must be in the same network segment, or the link layer cannot be Up.
Procedure
<HUAWEI> system-view [HUAWEI] sysname RouterA [RouterA] interface pos 1/0/0 [RouterA-Pos1/0/0] link-protocol hdlc [RouterA-Pos1/0/0] ip address 100.1.1.1 24 [RouterA-Pos1/0/0] undo shutdown [RouterA-Pos1/0/0] quit
Step 2 Configure Router B.

<HUAWEI> system-view [HUAWEI] sysname RouterB [RouterB] interface pos 1/0/0 [RouterB-Pos1/0/0] link-protocol hdlc [RouterB-Pos1/0/0] ip address 100.1.1.2 24 [RouterB-Pos1/0/0] undo shutdown [RouterB-Pos1/0/0] quit
Step 3 Verify the configuration. After the configuration is completed, Router A and Router B can ping through each other. Take Router A as an example.
ms ms ms ms ms
Run the display ip routing-table command to check the correctness 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 100.1.1.0/24 Direct 0 0 D 100.1.1.1 Pos1/0/0 100.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0 127.0.0.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0
----End
Configuration Files
l

# sysname RouterA # interface Pos1/0/0
Issue 03 (2010-03-31)
6-15

link-protocol hdlc undo shutdown ip address 100.1.1.1 255.255.255.0 # return l

# sysname RouterB # interface Pos1/0/0 link-protocol hdlc undo shutdown ip address 100.1.1.2 255.255.255.0 # return
6.5.2 Example for Configuring IP Address Unnumbered for HDLC

Router A and Router B are connected through POS interfaces, and the interfaces are required to run HDLC. POS 1/0/0 of Router A borrows the IP address of Loopback interface. The mask of Loopback interface is 32 bits. Figure 6-2 Networking diagram of the HDLC basic function
Loopback1 100.1.1.1/24 POS1/0/0 100.1.1.2/24
POS1/0/0
RouterA
RouterB
The configuration roadmap is as follows: 1. 2. 3. 4. 5. Configure the link protocol of each interface to HDLC. On Router A, configure the IP address of the loopback interface whose IP address is unnumbered. Configure the POS interface on Router A to adopt the IP address unnumbered. Configure Router A to learn the opposite routing information through the static route. Configure the IP address of Router B.
Data Preparation
To configure the IP address unnumbered, you need the following data:

l l
IP address of the loopback interface on Router A IP address of the POS interface on Router B
NOTE
These two IP addresses must be in the same network segment, or the link layer cannot be Up.
Procedure
<HUAWEI> system-view [HUAWEI] sysname RouterA [RouterA] interface loopback1 [RouterA-LoopBack1] ip address 100.1.1.1 32 [RouterA-LoopBack1] quit [RouterA] interface pos 1/0/0 [RouterA-Pos1/0/0] link-protocol hdlc [RouterA-Pos1/0/0] ip address unnumbered interface loopback1 [RouterA-Pos1/0/0] undo shutdown [RouterA-Pos1/0/0] quit

<HUAWEI> system-view [HUAWEI] sysname RouterB [RouterB] interface pos 1/0/0 [RouterB-Pos1/0/0] link-protocol hdlc [RouterB-Pos1/0/0] ip address 100.1.1.2 24 [RouterB-Pos1/0/0] undo shutdown [RouterB-Pos1/0/0] quit
Step 3 Configure the static routing on Router A.

[RouterA] ip route-static 100.1.1.0 24 pos 1/0/0
Step 4 Verify the configuration. After the configuration is completed, Router A and Router B can ping through each other. Take Router A as an example.
ms ms ms ms ms
Run the display ip routing-table command to check the correctness 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 100.1.1.0/24 Static 60 0 D 100.1.1.1 Pos1/0/0 100.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0 127.0.0.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0
----End
Configuration Files
l

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

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

Create an IP-Trunk between Router A and Router B. Figure 6-3 Configuring an IP-Trunk
IP-Trunk1 POS1/0/0 100.1.1.1/24 POS2/0/0
POS1/0/0
RouterA
IP-Trunk1 POS2/0/0 100.1.1.2/24 RouterB
The configuration roadmap is as follows: 1. 2. Create an IP-Trunk interface. Add the POS interfaces to the IP-Trunk interface.
Data Preparation
l
Router A and Router B are connected through the POS interfaces.

6-18

l l
IP address of the IP-Trunk interface at Router A IP address of the IP-Trunk interface at Router B
Procedure
<HUAWEI> system-view [HUAWEI] sysname RouterA
# Create IP-Trunk 1 and configure an IP address for it.

[RouterA] interface [RouterA-Ip-Trunk1] [RouterA-Ip-Trunk1] [RouterA-Ip-Trunk1] ip-trunk 1 ip address 100.1.1.1 255.255.255.0 undo shutdown quit
# Add POS 1/0/0 and POS 2/0/0 to IP-Trunk 1.

[RouterA] interface pos 1/0/0 [RouterA-Pos1/0/0] link-protocol hdlc [RouterA-Pos1/0/0] ip-trunk 1 [RouterA-Pos1/0/0] undo shutdown [RouterA-Pos1/0/0] quit [RouterA] interface pos 2/0/0 [RouterA-Pos2/0/0] link-protocol hdlc [RouterA-Pos2/0/0] ip-trunk 1 [RouterA-Pos2/0/0] undo shutdown [RouterA-Pos2/0/0] quit

<HUAWEI> system-view [HUAWEI] sysname RouterB
# Create IP-Trunk 1 and configure an IP address for it.

[RouterB] interface [RouterB-Ip-Trunk1] [RouterB-Ip-Trunk1] [RouterB-Ip-Trunk1] Ip-Trunk 1 ip address 100.1.1.2 255.255.255.0 undo shutdown quit
# Add POS 1/0/0 and POS 2/0/0 to IP-Trunk 1.

[RouterB] interface pos 1/0/0 [RouterB-Pos1/0/0] link-protocol hdlc [RouterB-Pos1/0/0] ip-trunk 1 [RouterB-Pos1/0/0] undo shutdown [RouterB-Pos1/0/0] quit [RouterB] interface pos 2/0/0 [RouterB-Pos2/0/0] link-protocol hdlc [RouterB-Pos2/0/0] ip-trunk 1 [RouterB-Pos2/0/0] undo shutdown [RouterB-Pos2/0/0] quit
Step 3 Check the configuration. Run the display interface ip-trunk command on Router A or Router B, and you can find that the interface is Up. Take Router A as an example.
[RouterA] display interface ip-trunk 1 Ip-Trunk1 current state : UP Line protocol current state : UP Last line protocol up time: 2007-11-03, 17:45:06 Description: Ip-Trunk1 Interface Route Port,Hash arithmetic : According to flow,The Maximum Transmit Unit is 4470
Issue 03 (2010-03-31)
6-19
Internet Address is 100.1.1.1/24 Link layer protocol is nonstandard HDLC Physical is IP_TRUNK Statistics last cleared: 2008-08-02 15:32:27 Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicast 0 errors,0 drops,0 unknownprotocol Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicast 0 errors,0 drops ----------------------------------------------------PortName Status Weight ----------------------------------------------------Pos1/0/0 UP 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, standby interface NULL Interface Pos2/0/0, valid, selected, operate up, weight=1, standby interface NULL
The IP-Trunk interface of Router A and that of Router B can ping each other successfully.
[RouterA] ping -a 100.1.1.1 100.1.1.2 PING 100.1.1.2: 56 data bytes, press CTRL_C to break Reply from 100.1.1.2: bytes=56 Sequence=1 ttl=255 time=62 Reply from 100.1.1.2: bytes=56 Sequence=2 ttl=255 time=62 Reply from 100.1.1.2: bytes=56 Sequence=3 ttl=255 time=62 Reply from 100.1.1.2: bytes=56 Sequence=4 ttl=255 time=62 Reply from 100.1.1.2: bytes=56 Sequence=5 ttl=255 time=62 --- 100.1.1.2 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 62/62/62 ms
ms ms ms ms ms
----End
Configuration Files
l

# sysname RouterA # interface Ip-Trunk1 undo shutdown ip address 100.1.1.1 255.255.255.0 # interface Pos1/0/0 link-protocol hdlc undo shutdown ip-trunk 1 # interface Pos2/0/0 link-protocol hdlc
6-20
Issue 03 (2010-03-31)

undo shutdown ip-trunk 1 # return l

# sysname RouterB # interface Ip-Trunk1 undo shutdown ip address 100.1.1.2 255.255.255.0 # interface Pos1/0/0 link-protocol hdlc undo shutdown ip-trunk 1 # interface Pos2/0/0 link-protocol hdlc undo shutdown ip-trunk 1 # return
Issue 03 (2010-03-31)
6-21
7 ATM Configuration
7
About This Chapter
7.1 Introduction to ATM Describes concepts and applications of ATM.
ATM Configuration
Describes Asynchronous Transfer Mode (ATM) broadband networking technologies and configuration steps for ATM interface, IMA groups, IPoA application, IPoEoA application, PPPoA application, PPPoEoA application, PVC service mapping, and service type of a PVC, OAM and VP, along with typical examples.
7.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 interface or an ATM OC-12/STM-4 interface. 7.3 Configuring ATM Services on a Serial Interface This section describes how to configure the ATM protocol on a serial interface, set the ATM interface type, and create a PVC. 7.4 Configuring IMA Groups Describes how to configure an IMA group. 7.5 Configuring the IPoA Application Describes how to configure IPoA. 7.6 Configuring the Service Type and Optional Parameters of a PVC This section describes how to configure service type and optional parameters of a PVC or PVP. 7.7 Configuring ATM OAM This section describes how to configure the ATM OAM. 7.8 Maintaining ATM Configuration Describes how to maintain ATM. 7.9 Configuration Examples Provides several configuration examples of ATM.
Issue 03 (2010-03-31)
7-1
7 ATM Configuration
7.1 Introduction to ATM

Describes concepts and applications of ATM. 7.1.1 ATM Overview 7.1.2 Features of ATM Supported by the NE80E/40E
7.1.1 ATM Overview

Asynchronous Transfer Mode (ATM) is designated as the transmission and switching mode for broadband ISDN services by the ITU-T in June, 1992. Due to its high flexibility and support to the multi-media service, ATM is considered as the key to realizing broadband communications. Defined by ITU-T, ATM implements transmission and switching of data based on cells. An ATM cell has a fixed length of 53 bytes. The first 5 bytes make up the cell header that contains the cell routing and priority information. The remaining 48 bytes are used for payloads. ATM is connection-oriented. Each virtual circuit (VC) is identified by a Virtual Path Identifier (VPI) and a Virtual Channel Identifier (VCI) together. One VPI/VCI value has local significance on a segment of the link between ATM nodes. When a connection is released, the relevant VPI/ VCI values are also released. Broadband-Integrated Services Digital Network (ITU-T B-ISDN) I.610 defines the OAM function on the ATM network and classifies the OAM function into five layers. The two types of operation flows are defined in the ATM layer: F4 and F5.
l
F4 flow is the OAM cell flow in the Virtual Path Connect (VPC) and provides the operation management and maintenance of the VP layer. F5 flow is the Virtual Channel Connect (VCC) and provides the operation management and maintenance of the VC layer.
After the OAM is activated in the F4 and F5 flows, the specified OAM cells are inserted into the user cells to occupy certain bandwidth and to be transmitted in the same physical channel with the cells of the other users. The F4 and F5 flows support four types of OAM cells: FM OAM cell, PM OAM cell, active/ deactive OAM cell, and SM OAM cell. On the ATM network, the three types of the OAM functional nodes are: end point, segment point and middle point.The nodes having the different OAM attributes process the AIS/RDI cells differently and indicate the information about the faults occurring in the ATM layer or the physical layer to implement the fault management.
7.1.2 Features of ATM Supported by the NE80E/40E

NE80E/40E supports the ATM interface that carries ATM service over SONET/SDH. These ATM interfaces supported by the NE80E/40E have the following features:
l l l
Supports Permanent Virtual Circuit (PVC). Supports traffic shaping based on VP/VC. Supports User-to-Network Interface (UNI) signaling.
7-2

l l l l l l l l
7 ATM Configuration
Supports RFC1483: Multiprotocol Encapsulation over ATM Adaptation Layer 5. Supports RFC1577: Classical IP and ARP over ATM. Supports F5 End to End Loopback OAM. Supports AAL5 (ATM Adaptation Layer 5). Supports Non-real Time Variable Bit Rate (nrt_VBR). Supports Unspecified Bit Rate (UBR). Supports Real Time Variable Bit Rate (rt_VBR). Supports Constant Bit Rate(CBR)
The ATM interface supports PVCs and two applications namely, IPoA and IPoEoA. The NE80E/40E supports the transparent transmission of ATM cells. For details, refer to 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.
7.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 interface or an ATM OC-12/STM-4 interface. 7.2.1 Establishing the Configuration Task 7.2.2 Configuring the Clock Mode 7.2.3 Configuring the Frame Format 7.2.4 Configuring the Overhead Byte 7.2.5 Configuring the MTU 7.2.6 Configuring the Scrambling 7.2.7 Configuring the Interval of Flow Statistics 7.2.8 Checking the Configuration

In order to make the parameters of the ATM interface consistent well with physical network, you can configure the parameters according to the actual ATM network. The parameters of the ATM interface mainly include the clock mode, frame format, scramble function, loopback mode, and interval of flow statistics. All these parameters have default configurations.
7 ATM Configuration
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 to the sub interface, it needs to be configured independently on the sub interface. When using an ATM interface to encapsulate the upper layer protocol, you need to configure its attributes.
Before configuring an ATM interface, complete the following task:
l
Powering on and starting the router normally
Data Preparation
To configure an ATM interface, you need the following data. No. 1 Data Number of the ATM interface on the router
7.2.2 Configuring the Clock Mode

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

interface atm interface-number
The ATM interface view is displayed. Step 3 Run:

The clock mode is configured. By default, the clock modes of ATM OC-3/STM-1 are master.

l l
7 ATM Configuration
Master mode: indicates that the interface uses the internal clock signals. Slave mode: indicates that the interface uses the line clock signals.
When the ATM interface is used as a DTE device, use the slave clock mode. When the 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, do the following. One port should be configured to use the master clock mode, and the other port should use the slave clock mode. When the router is connected to the SDH/SONET device, use the slave clock mode. ----End
7.2.3 Configuring the Frame Format

Context
Procedure
Step 1 Run:
system-view


The frame format is configured. ATM interface uses SDH frame format when the optical interface is STM-1 . The ATM interface uses SONET frame format when the interface is OC-3 or . By default, SDH frame format is used. ----End

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.
7 ATM Configuration
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. Do as follows on the routers:
Procedure
Step 1 Run:
system-view

The ATM interface view is displayed. Step 3 Perform the following as required:
l
Run:
The regenerator section trace byte J0 is configured.

l
Run:
The regenerator section trace byte J1 is configured.

NOTE
On the NE80E/40E, only the LPUF-10 ATM FPIC supports the 64byte-or-null-mode and peer parameters in the flag j0 and flag j1 commands.
l
Run:
flag c2 c2-value
The signal label byte C2 is configured. The C2, J0, and J1 on the receiving and sending ends should be consistent. Otherwise, an 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
7.2.5 Configuring the MTU

Context
The MTU of the ATM interface is used for the assembly and fragmentation of IP packet in receiving and sending packets on the interface.
7-6
Issue 03 (2010-03-31)
7 ATM Configuration
CAUTION
After changing the MTU of the interface by running the mtu command, restart the interface to validate the configuration by running the shutdown and undo shutdown commands consecutively. Do as follows on the routers:
Procedure
Step 1 Run:
system-view


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 MTU of the interface by using the mtu command, you need to restart the interface to validate the MTU. ----End
7.2.6 Configuring the Scrambling

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. Do as follows on the routers:
Procedure
Step 1 Run:
7 ATM Configuration
system-view


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
7.2.7 Configuring the Interval of Flow Statistics

Context
NOTE
The NE80E/40E supports the flow and rate statistics based on the ATM interface and the ATM subinterface. Before configuring the interval of rate statistics, you need to 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
The system view is displayed. Step 2 Perform the following as required:

l
To enter the ATM interface view, run:

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
7 ATM Configuration

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. Run the display interface brief [ | { begin | include | exclude } regular-expression ] 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 succeeds.
<HUAWEI> display interface atm 1/0/0 Atm1/0/0 current state : UP Line protocol current state : UP Last line protocol up time: 2008-11-03, 17:24:24 Description : Atm1/0/0 Interface Route Port, The Maximum Transmit Unit is 1500 Internet protocol processing : disabled AAL enabled: AAL5, Maximum VCs: 2048 VCs on main-interface: 1 (Total VCs: 1) VPs on main-interface: 0 (Total VPs: 1 ) The Vendor Name is FINISAR CORP. , The Vendor PN is FTRJ1321P1BTL Transceiver BW: 2.5G, Transceiver Mode: Single Mode WaveLength: 1310nm, Transmission Distance: 5km Rx Optical Power: -24.95dBm, Tx Optical Power: -1.99dBm Physical layer is Packet Over SDH UBR: 1, CBR: 0, VBR: 0, USED BandWidth: 0Kbps VPI Max: 255, VCI Max: 2047 Scramble enabled, clock master, CRC-32, loopback: none Flag: J0 "NetEngine " Flag: J1 "NetEngine " Flag: C2 19(0x13) SDH alarm: section layer: OOF LOF LOS line layer: AIS path layer: AIS RDI SDH error: section layer: B1: 24 line layer: B2: 0 M1: 0 path layer: B3: 0 G1: 0 Statistics last cleared:never Send good cell: 0 cells Send idle cell: 25099462530 cells Receive idle cell: 0 cells Receive corrected cell: 0 Receive uncorrected cell: 97 Dropped receive cell: 0 cells Last dropped receive cell connection: 0/0 Last 30 seconds input rate: 0 bits/sec, 0 Packets/sec Last 30 seconds output rate: 0 bits/sec, 0 Packets/sec Input: 0 Bytes, 0 Packets Output: 0 Bytes, 0 Packets
Run the display 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 succeeds. For example:
7 ATM Configuration
<HUAWEI> display interface brief | include 1/0/ PHY: Physical *down: administratively down ^down: standby (l): loopback (s): spoofing (b): BFD down (e): EFM down (d): Dampening Suppressed InUti/OutUti: input utility/output utility Interface PHY Protocol InUti OutUti outErrors Atm1/0/1 up up 0.08% 0.08% 0 Atm1/0/1.1 up up 0.03% 0.03% 0 Atm1/0/1.2 up up 0.03% 0.03% 0
inErrors 0 0 0
7.3 Configuring ATM Services on a Serial Interface

This section describes how to configure the ATM protocol on a serial interface, set the ATM interface type, and create a PVC. 7.3.1 Establishing the Configuration Task 7.3.2 Configuring the ATM Protocol on a Serial Interface 7.3.3 (Optional) Configuring the ATM Interface Type for a Serial Interface 7.3.4 Creating a PVC on a Serial Interface 7.3.5 Creating a PVP on a Serial Interface 7.3.6 Checking the Configuration

Traditional ATM services can run only on ATM interfaces, which leads to high cost of ATM transmission and very limited applications of ATM services. By using the Time Division Multiplexing (TDM) technology, a CE1/CPOS interface enables you to choose different transmission channels according to bandwidth requirements to fully utilize bandwidth resources. A CE1/CPOS interface can be channelized to multiple synchronization serial interfaces. The CE1/CPOS interface, thus, can be configured with different types of protocols, which decreases communication cost, increases configuration flexibility, and enables the CE1/CPOS interface to support various services. Currently, the synchronization serial interfaces on the NE80E/40E can be configured wih the ATM protocol and PVCs, and can be added to an IMA group.
NOTE
For how to add a serial interface to an IMA group, see Configuring an IMA Group in this chapter.
Pre-configuration Task
Before configuring ATM services on a serial interface, complete the following tasks:

l
7 ATM Configuration
Configuring physical parameters for the CE1/CPOS interface to ensure that the physical layer status of the interfaces is Up Channelizing the CE1/CPOS interface on the router to synchronization serial interfaces
NOTE
For configurations of a CE1/CPOS interface, refer to E-Carrier and T-Carrier Interface Configuration and POS and CPOS Interface Configuration.
Data Preparation
To configure ATM services on a serial interface, you need the following data. No. 1 2 Data Number of the synchronization serial interface PVC name (optional) and VPI/VCI
7.3.2 Configuring the ATM Protocol on a Serial Interface

Context
After the link layer protocol of a serial interface is configured to ATM, the ATM status is Up only when the physical status of the interface is Up. A serial interface can be added to an IMA group only after the link layer protocol of this interface is configured to ATM. By default, the link layer protocol of a serial interface is PPP. Do as follows on the router:
Procedure
Step 1 Run:
system-view


link-protocol atm
The ATM protocol is configured to be the link layer protocol on the serial interface. ----End
Issue 03 (2010-03-31)
7-11
7 ATM Configuration
7.3.3 (Optional) Configuring the ATM Interface Type for a Serial Interface
Context
After the link layer protocol of a serial interface is configured to ATM, you can configure the ATM interface type to User-to-Network Interface (UNI) or Network-to-Network Interface (NNI).
l
If a device needs to work as a user side device, you need to set the ATM interface type of the interface connecting the peer device to UNI. If a device needs to work as a network side device, you need to set the ATM interface type of the interface connecting the peer device to NNI.
By default, the ATM interface type on a serial interface is UNI.

NOTE
The ATM interface type on a serial interface can be configured only after the link layer protocol of the serial interface is set to ATM. The VPI value range of the PVC/PVP on the serial sub-interface varies with the ATM interface type on a serial interface. For detailed information, refer to the PVC/PVP commands in the HUAWEI NetEngine80E/ 40E Router Command Reference.
Do as follows on the router:
Procedure
Step 1 Run:
system-view


atm interface-type { uni | nni }
The type of the ATM interface is configured on the serial interface. ----End
7.3.4 Creating a PVC on a Serial Interface

Context
ATM transmission can be implemented only after a PVC is created. PVCs support Point-toMultipoint (P2MP) ATM transmission. As for creating a PVC, note the following:
l
A PVC can be created on a serial interface only after the link layer protocol of the interface is configured to ATM.
7-12

l
7 ATM Configuration
Currently, in the NE80E/40E, a PVC can be created on a serial sub-interface rather than a serial main interface.
Procedure
Step 1 Run:
system-view

interface serial interface-number.subinterface-number
The serial sub-interface is created and the sub-interface view is displayed. If the sub-interface already exists, the sub-interface view is displayed. Step 3 Run:
pvc vpi/vci
The PVC is created and the PVC view is displayed. ----End
7.3.5 Creating a PVP on a Serial Interface

Context
The ATM VP monitoring function can be implemented only after a PVP is created. As for creating a PVP, note the following:
l
A PVP can be created on a serial interface only after the link layer protocol of the interface is configured to ATM. Currently, in the NE80E/40E, a PVP can be created only on a serial sub-interface rather than a serial main interface.
Procedure
Step 1 Run:
system-view

interface serial interface-number.subinterface-number
The serial sub-interface is created and the sub-interface view is displayed. If the sub-interface already exists, the sub-interface view is displayed. Step 3 Run:
pvp vpi
The PVP is created and the PVP view is displayed. ----End

7 ATM Configuration

Prerequisite
The configurations of all ATM services on a serial interface are complete.
Procedure
l l l Run the display interface serial interface-number [ | { begin | exclude | include } regularexpression ] command to check the configurations on the serial interface. Run the display atm pvc-info [ interface serial interface-number [ pvc vpi/vci ] ] command to check information about the PVC on the serial interface. Run the display atm pvp-info [ interface serial interface-number [ pvp vpi ] command to check information about the PVP on the serial interface.
----End
Example
Run the display atm pvc-info command, and you can view information such as PVC status and interface status.
<HUAWEI> display atm pvc-info VPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE --------|-----|----------------|--------|-----|-----|----------------------100/1 |DOWN | |0 |SNAP |None |Atm1/1/0.1 (DOWN) 1/1 |DOWN | |1 |SNAP |None |Atm1/1/1.1 (DOWN) VPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE --------|-----|----------------|--------|-----|-----|----------------------1/100 |DOWN | |65536 |None |None |Ima-group13/0/2.1 (DOWN) 0/1 |DOWN | |65537 |None |None |Serial13/0/3:4.1 (DOWN)
7.4 Configuring IMA Groups

Describes how to configure an IMA group. 7.4.1 Establishing the Configuration Task 7.4.2 Creating an IMA Group 7.4.3 Setting the Number of the Cells Contained in an IMA Frame 7.4.4 Configuring Bandwidth for an IMA Group 7.4.5 Setting the Maximum Link Differential Delay for the IMA Group 7.4.6 Adding an Interface to an IMA Group 7.4.7 (Optional) Configuring the ATM Interface Type for an IMA Group 7.4.8 Creating a PVC for an IMA Group 7.4.9 Creating a PVP for an IMA Group 7.4.10 Checking the Configuration
7-14
Issue 03 (2010-03-31)
7 ATM Configuration

When users want to access the ATM network at a rate between T1/E1 and T3/E3, using T3/E3 is not cost-effective. Using multiple T1/E1 lines is a better solution that can be realized by IMA. An IMA group is a logical link having one or more links. Its bandwidth is approximately equal to the sum of all the member links' bandwidth.
NOTE
IMA group interfaces do not support Layer 3 protocols.
Before configuring an IMA group, complete the following task:
l
Creating a synchronization serial interface channelized from CE1 or CPOS interfaces and configuring the ATM protocol on the serial interface if an IMA group needs to be configured on the serial interface of the router
Data Preparation
To configure an IMA group, you need the following data. No. 1 2 3 Data Number of the IMA group Interface number of the IMA group Bandwidth of the IMA group
7.4.2 Creating an IMA Group

Context
Creating an IMA group is the prerequisite to performing group-related configurations and adding interfaces to the IMA group. Do as follows on the router:
Procedure
Step 1 Run:
system-view

interface ima-group interface-number
Issue 03 (2010-03-31)
7-15
7 ATM Configuration
An IMA group is created and the IMA group interface view is displayed. ----End
7.4.3 Setting the Number of the Cells Contained in an IMA Frame

Context
By default, the number of the cells contained in an IMA frame is 128. Do as follows on the router:
Procedure
Step 1 Run:
system-view

The IMA group interface view is displayed. Step 3 Run:

frame-length { 32 | 64 | 128 | 256 }
The number of the cells contained in an IMA frame is set. ----End
7.4.4 Configuring Bandwidth for an IMA Group

Context
The bandwidth for an IMA group is determined by the minimum number of available member links in the group. An IMA group can work only if the number of available member links is larger than or equal to the minimum number of available member links. The minimum number of available member links cannot be larger than the total number of member links in an IMA group. By default, the minimum number of available member links in an IMA group is 1. That is, an IMA group can work as long as one member link is available. Do as follows on the router:
Procedure
Step 1 Run:
system-view

7-16
Issue 03 (2010-03-31)
7 ATM Configuration

min-active-links number
The minimum number of available member links in the IMA group is set. ----End
7.4.5 Setting the Maximum Link Differential Delay for the IMA Group
Context
By default, the maximum differential delay of member links in an IMA group is 25 ms. Do as follows on the router:
Procedure
Step 1 Run:
system-view


differential-delay milliseconds
The maximum differential delay of member links in an IMA group is set, in milliseconds. ----End
7.4.6 Adding an Interface to an IMA Group

Context
Synchronization serial interfaces channelized from a CE1/CPOS interface can be added to an IMA group. As for adding an interface to an IMA group, note the following:
l l
An interface can be added to only one IMA group at one time. After an interface is added to an IMA group, the network layer configurations on the interface do not take effect any more. The interface that joins an IMA group firstly can quit the group lastly.
As for adding a synchronization serial interface to an IMA group, besides the preceding information, note the following:
l
A synchronization serial interface can be added to an IMA group only after the link layer protocol of the interface is configured to ATM.
Issue 03 (2010-03-31)
7 ATM Configuration
l
After a synchronization serial interface is added to an IMA group, the link layer protocol of the interface can be changed only after the interface is removed from the group. After a synchronization serial interface is added to an IMA group, no sub-interfaces can be created on the interface and the ATM interface type does not take effect any more. You can re-configure sub-interfaces and ATM interface type on the IMA group interface.
By default, no links are added to IMA groups, and each link can independently run various services.
NOTE
An interface can be added to an IMA group only after the group is created.
Procedure
Step 1 Run:
system-view
The system view is displayed. Step 2 Run the following command as required:
l
To enter the synchronization serial interface view, run the interface serialinterfacenumber command.
Step 3 Run:
ima ima-group interface-number
The interface is added to the IMA group.

NOTE
The interface can be added only to one IMA group with the slot number and card number being the same as those of the interface.
----End
7.4.7 (Optional) Configuring the ATM Interface Type for an IMA Group
Context
After a serial interface is added to an IMA group, the ATM interface type of the serial interface does not take effect any more. You can re-configure the ATM interface type on the IMA group interface.
l
If a device needs to work as a user side device, you need to set the ATM interface type of the interface connecting the peer device to UNI. If a device needs to work as a network side device, you need to set the ATM interface type of the interface connecting the peer device to NNI.
By default, the ATM interface type of an IMA group is UNI.


NOTE
7 ATM Configuration
The VPI value range of the PVC/PVP on the IMA sub-interface varies with the ATM interface type of an IMA group. For detailed information, refer to pvc and pvp in the HUAWEI NetEngine80E/40E Router Command Reference.
Procedure
Step 1 Run:
system-view


atm interface-type { uni | nni }
The ATM interface type is configured on the IMA group interface. ----End
7.4.8 Creating a PVC for an IMA Group

Context
ATM transmission can be implemented only after a PVC is created. PVCs support Point-toMultipoint (P2MP) ATM transmission. Currently, in the NE80E/40E, a PVC can be created on an IMA group sub-interface rather than an IMA group interface. Do as follows on the router:
Procedure
Step 1 Run:
system-view

interface ima-group interface-number.subinterface-number
The IMA group sub-interface is created and the sub-interface view is displayed. Step 3 Run:
pvc vpi/vci
The PVC is created and the PVC view is displayed. ----End

7 ATM Configuration
7.4.9 Creating a PVP for an IMA Group

Context
The ATM VP monitoring function can be implemented only after a PVP is created. Currently, in the NE80E/40E, a PVP can be created on an IMA group sub-interface rather than an IMA group interface. Do as follows on the router:
Procedure
Step 1 Run:
system-view

interface ima-group interface-number.subinterface-number
The IMA group sub-interface is created and the sub-interface view is displayed. Step 3 Run:
pvp vpi
The PVP is created and the PVP view is displayed. ----End

Prerequisite
The configurations of the IMA groups are complete.
Procedure
l Run the display interface [ atm | serial ] [ interface-number ] [ | { begin | exclude | include } regular-expression ] [interface-type ] command to check the configuration and status of the ATM interface. Run the display interface brief [ | { begin | include | exclude } regular-expression ] command to check brief information about the IMA-Group interface and its member interfaces. Run the display interface ima-group [ group-number ] command to check configuration and status of the IMA group.
----End
Example
After running the display interface brief [ | { begin | include | exclude } regular-expression ] command, you can view brief information about the physical status, link layer protocol status, bandwidth utilization, and number of incorrect packets of the IMA-Group interface and its member interfaces. The following is the display of the command:
7 ATM Configuration
<HUAWEI> display interface brief | include Ima-group *down: administratively down ^down: standby (l): loopback (s): spoofing (b): BFD down (d): DampeningSuppressed InUti/OutUti: input utility/output utility Interface Physical Protocol InUti OutUti inErrors outErrors Ima-group1/0/0 UP UP 0.04% 0.04% 0 0
After running the display interface ima-group command, you can view the status of the IMAGroup interface and the number of VCs.
<HUAWEI> display interface ima-group 1/0/1 Ima-group1/0/1 current state : UP Line protocol current state : UP Last line protocol up time: 2007-11-03, 17:24:24 Description: Ima-group1/0/1 Interface Route Port,The Maximum Transmit Unit is 1500 Internet Address is 21.161.163.2/24 AAL enabled: AAL5, Maximum VCs: 128 Current VCs: 1 (1 on main interface) Physical layer is ATM over IMA IMA-clock: CTC, differential-delay-maximum: 25, active-links-minimum: 1 Frame-length: 128, symmetry: symmetrical configuration and operation IMA_GRP_NE_STATE OPERATIONAL IMA_GRP_FE_STATE OPERATIONAL IMA links: 1 ,First Link: 0 Link 0: Alarm: none Error: 0 FERR, 0 LCV, 0 CERR, 0 FEBE Defect: none F5 end-end loopback oam sends 0, F5 end-end loopback oam receives 0 my oam back 0, oam forward 0 oam send drops 0, oam forward drops 0 Statistics last cleared: 2007-09-17 11:21:50 Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 1902 packets, 55496 bytes 0 errors, 0 CRC, 0 giants, 0 pads, 0 aborts, 0 overflows Output:1903 packets, 49760 bytes 0 errors, 0 underflows, 0 overflows
7.5 Configuring the IPoA Application

Describes how to configure IPoA. 7.5.1 Establishing the Configuration Task 7.5.2 Configuring IPoA Mapping on a PVC 7.5.3 Checking the Configuration

To make ATM bear IP packets, you need to create PVC first. You can configure the IPoA application mapping on the PVC to make AAL5 bear IP packets.
7 ATM Configuration
Pre-configured Tasks
Before configuring IPoA applications, complete the following tasks:
l l
Configuring physical attributes for the ATM interface Configuring an IP address and mask for the ATM interface (or sub-interface)
Data Preparation
To configure the IPoA applications, you need the following data. No. 1 2 3 4 5 6 Data Number of the ATM interface (or sub-interface) IP address and mask of the ATM interface (or sub-interface) PVC name, ATM network VPI and VCI AAL5 encapsulation type IP address and mask of the peer mapped to PVC Interval of sending InARP packets
7.5.2 Configuring IPoA Mapping on a PVC

Procedure
Step 1 Run:
system-view

interface atm interface-number[.subinterface ]
The ATM interface or the sub-interface view is displayed. Step 3 Run:

pvc { pvc-name [ vpi/vci ] | vpi/vci }
A PVC is created and the PVC view is displayed.

NOTE
l l
In normal cases, the VCI values 3 and 4 are reserved for special usage. You are recommended not to use these two values. The values of VPI and VCI cannot be 0 at the same time.
Step 4 Run:
encapsulation aal5-encap
The encapsulation type of the PVC is configured as AAL5.

7 ATM Configuration
The AAL5 encapsulation type for PVC can be aal5snap, aal5mux or aal5nlpid. By default, it is aal5snap.
NOTE
On the NE80E/40E, only the LPUF-10 FPIC supports the aal5nlpid encapsulation type.
InARP is not supported when aal5mux and aal5nlpid encapsulations are adopted. To change the encapsulation type for PVC to aal5mux or aal5nlpid, delete InARP first. Step 5 Run:
map ip { ip-address | inarp [ minutes ] } [ broadcast ]
The IPoA mapping on the PVC is configured.

NOTE
IP addresses assigned to different ATM interfaces or ATM sub-interfaces on the local router cannot be identical. Otherwise, packets cannot be forwarded.
When configuring the ip-address, if the specified address is the network segment address or the multicast address, the key word broadcast must be chosen. When broadcast packets need to be processed on a PVC, the key word broadcast need to be specified. On one ATM interface, configure one PVC with InARP.
CAUTION
The IP address specified by running the map ip command must be the IP address of the interface on the peer. Otherwise, data cannot be forwarded normally. ----End

Prerequisite
The configurations of the IPoA application are complete.
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 interface or sub-interface. Run the display atm pvc-info [ interface interface-type interface-number[.subinterface ] [ pvc { pvc-name [ vpi/vci ] | vpi/vci } ] ] command to check information about the PVC. Run the display atm map-info [ interface interface-type interface-number [.subinterface ] [ pvc { pvc-name [ vpi/vci ] | vpi/vci } ] ] command to check information about the PVC mapping. Run the display atm { pvc | pvp } statistics interface atm interface-number [ pvc vpi/ vci | pvp vpi ] command to check statistics about the PVC or PVP.
l l
Issue 03 (2010-03-31)
7 ATM Configuration
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 succeeds.
<HUAWEI> display interface atm 1/0/0 Atm1/0/0 current state : UP Line protocol current state : UP Last line protocol up time: 2008-11-03, 17:24:24 Description: Atm1/0/0 Interface Route Port, The Maximum Transmit Unit is is 1500 Internet protocol processing : disabled AAL enabled: AAL5, Maximum VCs: 2048 VCs on main-interface: 1 (Total VCs: 1) VPs on main-interface: 0 (Total VPs: 0) The Vendor Name is FINISAR CORP. , The Vendor PN is FTRJ1321P1BTL Transceiver BW: 2.5G, Transceiver Mode: Single Mode WaveLength: 1310nm, Transmission Distance: 5km Rx Optical Power: -24.95dBm, Tx Optical Power: -1.99dBm Physical layer is Packet Over SDH UBR: 1, CBR: 0, VBR: 0, USED BandWidth: 0Kbps VPI Max: 4095, VCI Max: 65535 Scramble enabled, clock master, CRC-32, loopback: none Flag: J0 "NetEngine " Flag: J1 "NetEngine " Flag: C2 19(0x13) SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1: 0 line layer: B2: 0 M1: 0 path layer: B3: 0 G1: 0 Statistics last cleared:never Send good cell: 0 cells Send idle cell: 25099462530 cells Receive correct cell: 0 cells Receive idle cell: 0 cells Receive corrected cell: 0 cells Receive uncorrected cell: 0 cells Dropped receive cell: 0 cells Last dropped receive cell connection: 0/0 Last 30 seconds input rate: 0 bits/sec, 0 packets/sec Last 30 seconds output rate: 0 bits/sec, 0 packets/sec Input: 0 bytes, 0 packets Output: 0 bytes, 0 packets
Run the display atm pvc-info command. If you can view the status of the PVC and the corresponding interface, it means that the configuration succeeds.
<HUAWEI> display atm pvc-info VPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE --------|-----|------------------|--------|-----|-----|----------------------0/40 |UP | |1 |SNAP |IP |Atm1/0/0 (UP)
Run the display atm map-info command. If you can view information about the PVC mapping, it means that the configuration succeeds.
<HUAWEI> display atm map-info Atm1/0/0, PVC 0/40, IP, State UP 10.0.0.1, vlink 65537
7-24
Issue 03 (2010-03-31)
7 ATM Configuration
Run the display atm pvc statistics command, you can view the statistics of the packets discarded on the PVC due to congestion.
<HUAWEI> dispaly atm pvc statistics interface atm 1/0/0 pvc 10/10: input drop pkts : 0, input drop rate 0 packets/sec output drop pkts : 0, output drop rate 0 packets/sec pvc 10/20: input drop pkts : 0, input drop rate 0 packets/sec output drop pkts : 0, output drop rate 0 packets/sec
7.6 Configuring the Service Type and Optional Parameters of a PVC

This section describes how to configure service type and optional parameters of a PVC or PVP. 7.6.1 Establishing the Configuration Task 7.6.2 Configuring the Service Type of a PVC 7.6.3 Configuring the Service Type of a PVP 7.6.4 (Optional) Configure the Overload Bandwidth Value of an ATM Interface 7.6.5 Checking the Configuration

In the practical networking, to manage the traffic of PVC, 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 l l
Configuring physical attributes for the ATM interface Configuring an IP address and mask for the ATM interface or sub-interface Creating 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. 1 2 3 4
Issue 03 (2010-03-31)
Data Number of the ATM interface or sub-interface IP address and mask of the ATM interface or sub-interface PVC name, the network VPI and VCI cbr: Peak rate of outputting ATM cells, variation range of cell delays
7 ATM Configuration
No. 5 6 7
Data nrt-vbr: Peak rate of outputting ATM cells, maintainable rate, variation range of cell delays and the maximum burst size rt-vbr: Peak rate of outputting ATM cells, maintainable rate, variation range of cell delays and the maximum burst size (Optional)overload bandwidth value of the ATM interface
7.6.2 Configuring the Service Type of a PVC

Context
When configuring the service type of PVC, you need to first create service type template in the system view and apply the service type to the concrete PVC. Do as follows on the routers:
Procedure
Step 1 Run:
system-view
The system view is displayed. Step 2 Run: atm service service-name {cbr output-pcr cdvt-value |nrt-vbr output-pcr output-scr outputmbs cdvt-value |rt-vbr output-pcr output-scr output-mbs cdvt-value | ubr output-pcr cdvtvalue | ubr-plus output-mcr output-pcr output-mbs cdvt-value} The service type template and rate parameters are created. By default, the service type of PVP is UBR. The service type can be configured as CBR, NRT-VBR, UBR, UBR-plus or RT-VBR. Step 3 Run:

pvc [ pvc-name ] vpi/vci
The PVC is created and the PVC view is displayed. Step 5 Run:
shutdown
The PVC is disabled. Step 6 Run:

service { output | input } service-name
7-26
Issue 03 (2010-03-31)
7 ATM Configuration
The service type of PVP is set. Step 7 Run:

undo shutdown
The PVC is enabled. ----End
7.6.3 Configuring the Service Type of a PVP

Context
When configuring the service type of PVP, you need to first create the service type template in the system view and apply the service type to the concrete PVP. Do as follows on the routers:
Procedure
Step 1 Run:
system-view
The system view is displayed. Step 2 Run: atm service service-name {cbr output-pcr cdvt-value |nrt-vbr output-pcr output-scr outputmbs cdvt-value |rt-vbr output-pcr output-scr output-mbs cdvt-value | ubr output-pcr cdvtvalue | ubr-plus output-mcr output-pcr output-mbs cdvt-value} The service type template and rate parameters are created. By default, the service type of PVP is UBR. The service type can be configured as CBR, NRT-VBR, UBR, UBR-plus or RT-VBR. Step 3 Run:
interface atm interface-number.subinterface

pvp vpi
The PVP is created and the PVP view is displayed. The PVP is only supported to be configured in the ATM sub interface view. Step 5 Run:
shutdown
The PVP is shut down. Step 6 Run:

service { output | input } service-name
The service type of PVP is set.

7 ATM Configuration
Step 7 Run:
undo shutdown
The PVP is enabled. ----End
7.6.4 (Optional) Configure the Overload Bandwidth Value of an ATM Interface

Context
NOTE
On the NE80E/40E, the LPUF-10 ATM FPIC does not support the configuration.
Procedure
Step 1 Run:
system-view

interface atm interface-number [.subinterface ]
The ATM interface or the sub-interface view is displayed. Step 3 Run:

service bandwidth-overload peek-rate
The overload bandwidth value of the ATM interface is set. Using the service bandwidth-overload command, you can set the overload bandwidth of the PVCs and PVPs of all services on the ATM interface. ----End

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 Run the display atm service [ service-name ] command to check the configuration of the service type template. 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.
l l
7-28
Issue 03 (2010-03-31)

NOTE
7 ATM Configuration
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 succeeds.
<HUAWEI> display interface atm 1/0/0 Atm1/0/0 current state : UP Line protocol current state : UP Last line protocol up time: 2008-11-03, 17:24:24 Description:Atm1/0/0 Interface Route Port, The Maximum Transmit Unit is is 1500 Internet protocol processing : disabled AAL enabled: AAL5, Maximum VCs: 2048 VCs on main-interface: 1 (Total VCs: 1) VPs on main-interface: 0 (Total VPs: 0) The Vendor Name is FINISAR CORP. , The Vendor PN is FTRJ1321P1BTL Transceiver BW: 2.5G, Transceiver Mode: Single Mode WaveLength: 1310nm, Transmission Distance: 5km Rx Optical Power: -24.95dBm, Tx Optical Power: -1.99dBm Physical layer is Packet Over SDH UBR: 1, CBR: 0, VBR: 0, USED BandWidth: 0Kbps VPI Max: 255, VCI Max: 2047 Scramble enabled, clock master, CRC-32, loopback: none Flag: J0 "NetEngine " Flag: J1 "NetEngine " Flag: C2 19(0x13) SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1: 0 line layer: B2: 0 M1: 0 path layer: B3: 0 G1: 0 Statistics last cleared:never Send good cell: 0 cells Send idle cell: 25099462530 cells Receive idle cell: 0 cells Receive corrected cell: 0 Receive uncorrected cell: 97 Dropped receive cell: 0 cells Last dropped receive cell connection: 0/0 Last 30 seconds input rate: 0 bits/sec, 0 packets/sec Last 30 seconds output rate: 0 bits/sec, 0 packets/sec Input: 0 bytes, 0 packets Output: 0 bytes, 0 packets
Run the display atm service command. If you can view the configuration of the service type template, it means that the configuration succeeds.
<HUAWEI> display atm service Atm Service Config: Service Name: aa State: VALID Index: 0 ServiceType: CBR PCR: 120 SCR: 0 MBS: 0 CDVT: 3
Issue 03 (2010-03-31)
7-29
7 ATM Configuration
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 succeeds.
<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
7.7 Configuring ATM OAM

This section describes how to configure the ATM OAM. 7.7.1 Establishing the Configuration Task 7.7.2 (Optional) Activating the CC Function 7.7.3 (Optional) Configuring OAM End-to-End Loopback 7.7.4 (Optional) Configuring the Cell Loopback 7.7.5 Checking the Configuration

OAM provides various methods of detecting and locating the faults of an ATM link. The OAM configurations are optional. 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 function of end-to-end loopback detection:
The CC function detects the link status in real time by sending CC cells periodically and does not restrict 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 of which the connection point attribute is end-point.
Check whether the device supports CC cells or loopback cells and then choose configurations according to the connection point attribute of the OAM. The CC function and the loopback function cannot be configured on the same PVP/PVC.
l l
To locate and remove the faults of a link, configure the cell loopback. To debug and detect whether the ATM OAM mechanism works normally, inserting OAM cells manually. To response the OAM F5 loopback cells on the peer, configure the response of the OAM F5 loopback cells.
7-30
7 ATM Configuration
Before configuring ATM OAM, complete the following tasks:
l l l
Configuring physical attributes for the ATM interface Configuring an IP address and mask for the ATM interface Configuring ATM PVC
Data Preparation
To configure ATM OAM, you need the following data. No. 1 2 3 4 5 Data Number of the ATM interface or sub-interface PVC name, the network VPI and VCI Interval for sending loopback cells Interval for sending OAM end-to-end Loopback cells Number of delayed intervals for responding after the status of the PVP/PVC changes
7.7.2 (Optional) Activating the CC Function

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

interface interface-type interface-number [.subinterface ]

oam
The OAM view is displayed. Step 4 Run:

attribute {start-vpi [ end-vpi ] | vpi/start-vci [ vpi/end-vci ] } { end-point | seg-point }
Issue 03 (2010-03-31)
7-31
7 ATM Configuration
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 l l
IPoA or IPoEoA Transparent transmission of frames 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 configurations of OAM attributes on the both ends. The type of the CC function and the OAM attributes must be consistent. During the recovery stage, you cannot cancel the CC function. Before deleting the OAM connection, if the board is not faulty, you must cancel the CC function first.
l l l
----End
7.7.3 (Optional) Configuring OAM End-to-End Loopback

Context
When configuring the function of OAM end-to-end loopback detection, note the following:
l l l l
Set the attribute of the OAM connection point of the PVP/PVC to end-point. The CC function and the loopback function cannot be configured on the same PVP/PVC. During fault recovery, the undo oam-loopback command cannot be run. 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
Step 1 Run:
system-view

The ATM interface view is displayed.

7 ATM Configuration
Step 3 Run:
oam
The OAM interface view is displayed. Step 4 Run:

attribute {start-vpi [ end-vpi ] | vpi/start-vci [ vpi/end-vci ] } end-point
The attribute of the OAM connection point is set to end-point. Step 5 Run:
oam-loopback { start-vpi [ end-vpi ] | vpi/start-vci [ vpi/end-vci }end-to-end
The function of OAM end-to-end loopback detection of the PVP/PVC is enabled. Step 6 (Optional) Run:
oam-loopback { start-vpi [ end-vpi ] | vpi/start-vci cycle-number down-cycle cycle-number [ vpi/end-vci }up-cycle
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 keeps being Down or Up in consecutive delayed intervals of the specified number, the system responds to the change. ----End
7.7.4 (Optional) Configuring the Cell Loopback

Context
NOTE
On the NE80E/40E, only the LPUF-10 ATM FPIC supports the cell loopback function.
Procedure
Step 1 Run:
system-view


oam
An OAM view is displayed.

7 ATM Configuration
Step 4 Run:
attribute {start-vpi [ end-vpi ] | vpi/start-vci [ vpi/end-vci ] } { end-point | seg-point }
The OAM attributes of the connection point is configured. When the following services are configured on a PVC, the PVC attribute can be configured only as end-point.
l l l
IPoA or IPoEoA Transparent transmission of frames 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 the convenient fault location and test. The loopback test refers to that the loopback cells is inserted in the VC/VP link of a certain connection point and is looped back in another connection point. The system detects and locates the faults of the link through the received loopback cells. The loopback includes the following two types: segment loopback and end loopback.
l
Before configuring the loopback of the segment point, you need to configure the end loopback point as the segment point. Before configuring the loopback of the end point, you need to configure the end loopback point as the end point. The loopback in one board fails.
----End

Procedure
l l l Run the display atm oam statistics atm interface-number { vpi | vpi/vci } command to check the statistics of the ATM OAM. Run the display atm oam alarm-status atm interface-number [ vpi | vpi/vci ] command to check the alarm status of the ATM OAM. 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 succeeds.
<HUAWEI> display atm oam statistics atm 3/0/1 10/10
7-34
Issue 03 (2010-03-31)
7 ATM Configuration
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> system-view [HUAWEI] interface atm 3/0/1 [HUAWEI-Atm3/0/1] oam [HUAWEI-Atm3/0/1-fatm-oam] display atm oam alarm-status atm 3/0/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 Current displayed item(s) is : 1
7.8 Maintaining ATM Configuration

Describes how to maintain ATM. 7.8.1 Setting Loopback to Detect Whether an Interface Is Normal 7.8.2 Clearing the ATM Interface Statistics 7.8.3 Debugging ATM
7.8.1 Setting Loopback to Detect Whether an Interface Is Normal

Context
CAUTION
After you configure the self-loop (run the loopback command), the interface on a router or the link cannot run normally. Thus, you must check whether to set the self-loop. After the detection is complete, run the undo loopback command to disable the self-loop. Do as follows on the device to be detected:
Procedure
Step 1 Run:
system-view

The view of the interface to be detected is displayed.

7 ATM Configuration
Step 3 Run:
loopback { local | remote }
The self-loop of the interface is enabled. By default, the self-loop is disabled on the interface. ----End
7.8.2 Clearing the ATM Interface Statistics

Context
CAUTION
All the statistics data cannot be restored after you clear it. Thus, confirm the action before you use the command. To reset the interface statistics of the Network Management System (NMS) or that displayed by running the display interface command, run the following commands in the user view.
NOTE
Procedure
Step 1 Run the reset counters interface [ atm [ interface-number ] ] command to clear the interface statistics displayed by running the display interface command. Step 2 Run the reset counters if-mib interface [ atm [ interface-number ] ] command to clear the interface statistics in the NMS. Step 3 Run the reset atm interface [ atm interface-number ] command to clear the ATM interface statistics. ----End
7.8.3 Debugging ATM

Context
CAUTION
Debugging affects the system performance. So, after the debugging, run the undo debugging all command to disable it immediately. When ATM runs abnormally, run the debugging command in user view to debug the ATM interface and locate the fault.
7 ATM Configuration
For the procedure of outputting the debugging information, refer to the chapter "Information Center Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide System Management. For the detailed debugging commands, refer to the HUAWEI NetEngine80E/40E Router Debugging Reference.
Procedure
Step 1 Run the debugging atm error [ interface atm interface-number[.subinterface ] [ pvc { pvcname [ vpi/vci ] | vpi/vci } ] ] command to enable ATM error debugging. Step 2 Run the debugging atm event [ interface atm interface-number[.subinterface ] [ pvc { pvcname [ vpi/vci ] | vpi/vci } ] ] command to enable ATM event debugging. Step 3 Run the debugging atm packet [ interface atm interface-number[.subinterface ] [ pvc { pvcname [ vpi/vci ] | vpi/vci } ] ] command to enable ATM packet debugging. Step 4 Run the debugging atm all command to enable all ATM debugging. ----End

Provides several configuration examples of ATM. 7.9.1 Example for Configuring IPoA 7.9.2 Example for Configuring ATM OAM 7.9.3 Example for Configuring IMAoPSN ATM IMAoPSN enables the transmission of ATM cells of a 3G wireless bearer network in a packet-switched network (PSN) without the need of deploying an extra ATM network for 3G services.
7.9.1 Example for Configuring IPoA

In Figure 7-1, Router A, Router B and Router C are connected to the ATM network. All the PVCs on ATM interfaces of the three routers employ IPoA application mode.
Issue 03 (2010-03-31)
7-37
7 ATM Configuration
Figure 7-1 Networking diagram for IPoA configuration
RouterB
RouterA
ATM network
IP:202.38.160.2/24 To A:0/40 To C:0/42 Interface:ATM1/0/0
IP:202.38.160.1/24 To B:0/40 To C:0/41 Interface:ATM1/0/0
RouterC
IP:202.38.160.3/24 To A:0/41 To B:0/42 Interface:ATM1/0/0
The configuration roadmap is as follows: 1. 2. Create the PVC of ATM interfaces on each router. Specify the protocol to bear the IP protocol.
Data Preparation
To configure IPoA, you need the following data:
l l l l
IP addresses of their ATM interfaces of the three routers VPI/VCI of Router A connecting with Router B and Router C VPI/VCI of Router B connecting with Router A and Router C VPI/VCI of Router C connecting with Router A and Router B
Procedure
Step 1 Configure Router A. # Enter the ATM interface view, and configure an IP address for it.
<HUAWEI> system-view [HUAWEI] sysname RouterA [RouterA] interface atm 1/0/0 [RouterA-Atm1/0/0] ip address 202.38.160.1 255.255.255.0
# Establish PVC to bear IP.


[RouterA-Atm1/0/0] pvc to_b 0/40 [RouterA-atm-pvc-Atm1/0/0-0/40-to_b] [RouterA-atm-pvc-Atm1/0/0-0/40-to_b] [RouterA-Atm1/0/0] pvc to_c 0/41 [RouterA-atm-pvc-Atm1/0/0-0/41-to_c] [RouterA-atm-pvc-Atm1/0/0-0/41-to_c] [RouterA-Atm1/0/0] undo shutdown
7 ATM Configuration
map ip 202.38.160.2 quit map ip 202.38.160.3 quit
Step 2 Configure Router B. # Enter the ATM interface, and configure an IP address for it.
<HUAWEI> system-view [HUAWEI] sysname RouterB [RouterB] interface atm 1/0/0 [RouterB-Atm1/0/0] ip address 202.38.160.2 255.255.255.0

[RouterB-Atm1/0/0] pvc to_a 0/40 [RouterB-atm-pvc-Atm1/0/0-0/40-to_a] [RouterB-atm-pvc-Atm1/0/0-0/40-to_a] [RouterB-Atm1/0/0] pvc to_c 0/42 [RouterB-atm-pvc-Atm1/0/0-0/42-to_c] [RouterB-atm-pvc-Atm1/0/0-0/42-to_c] [RouterB-Atm1/0/0] undo shutdown map ip 202.38.160.1 quit map ip 202.38.160.3 quit
Step 3 Configure Router C. # Enter the ATM interface view, and configure an IP address for it.
<HUAWEI> system-view [HUAWEI] sysname RouterC [RouterC] interface atm 1/0/0 [RouterC-Atm1/0/0] ip address 202.38.160.3 255.255.255.0

[RouterC-Atm1/0/0] pvc to_a 0/41 [RouterC-atm-pvc-Atm1/0/0-0/41-to_a] [RouterC-atm-pvc-Atm1/0/0-0/41-to_a] [RouterC-Atm1/0/0] pvc to_b 0/42 [RouterC-atm-pvc-Atm1/0/0-0/42-to_b] [RouterC-atm-pvc-Atm1/0/0-0/42-to_b] [RouterC-Atm1/0/0] undo shutdown map ip 202.38.160.1 quit map ip 202.38.160.2 quit
Step 4 Verify the configuration. # Check the PVC status information on Router A.
[RouterA] display atm pvc-info VPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE --------|-----|--------------|--------|-----|-----|--------------------0/40 |UP |to_b |1 |SNAP |IP |Atm1/0/0 (UP) 0/41 |UP |to_c |2 |SNAP |IP |Atm1/0/0 (UP)
# Check the PVC mapping information on Router A.

[RouterA] display atm map-info Atm1/0/0, PVC 0/40, IP, State UP 202.38.160.2, vlink 393217 Atm1/0/0, PVC 0/41, IP, State UP 202.38.160.3, vlink 393218
Similarly, check the PVC status information and the PVC mapping information on Router B and Router C. # Router A can ping through Router B.
[RouterA] ping 202.38.160.2
Issue 03 (2010-03-31)
7-39
7 ATM Configuration

PING 202.38.160.2: 56 data bytes, press CTRL_C to break Reply from 202.38.160.2: bytes=56 Sequence=1 ttl=255 time=62 Reply from 202.38.160.2: bytes=56 Sequence=2 ttl=255 time=31 Reply from 202.38.160.2: bytes=56 Sequence=3 ttl=255 time=31 Reply from 202.38.160.2: bytes=56 Sequence=4 ttl=255 time=31 Reply from 202.38.160.2: bytes=56 Sequence=5 ttl=255 time=31 --- 202.38.160.2 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 31/37/62 ms
ms ms ms ms ms
After performing similar operation, you observe the following:

l l l
Router A can ping through Router C. Router B can ping through Router A and Router C. Router C can ping through Router A and Router B.
----End
Configuration Files
l

# 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
7.9.2 Example for Configuring ATM OAM

7 ATM Configuration
In Figure 7-2, Router A, Router B and Router C are connected to the ATM network. IPoA services are configured in all the PVCs on ATM interfaces of the three routers. To implement the real-time and continuous detection without interrupting services, you need to configure the OAM CC function. Figure 7-2 Networking diagram for ATM OAM configuration
Router B
ATM Network
Router A IP:202.38.160.1/24 To B: 0/40 To C:0/41 Interface:ATM 1/0/0
IP:202.38.160.2/24 To A: 0/40 To C:0/42 Interface:ATM 1/0/0 Router C
IP:202.38.160.3/24 To A: 0/41 To B:0/42 Interface:ATM 1/0/0
The configuration roadmap is as follows: 1. 2. 3. Configure IPoA services. Configure the OAM attributes of the connection point. Activate the CC function.
Data Preparation
To configure IPoA, you need the following data:
l l
The IP addresses of the ATM interfaces of the three routers In ATM network, the VPI/VCI of Router A connecting with Router B and Router C respectively The VPI/VCI of Router B connecting with Router A and Router C respectively The VPI/VCI of Router C connecting with Router A and Router B respectively
l l
Issue 03 (2010-03-31)
7 ATM Configuration
Procedure
Step 1 Configure IPoA. # Configure Router A.
<HUAWEI> system-view [HUAWEI] sysname RouterA [RouterA] interface atm 1/0/0 [RouterA-Atm1/0/0] ip address 202.38.160.1 255.255.255.0 [RouterA-Atm1/0/0] pvc to_b 0/40 [RouterA-atm-pvc-Atm1/0/0-0/40-to_b] map ip 202.38.160.2 [RouterA-atm-pvc-Atm1/0/0-0/40-to_b] quit [RouterA-Atm1/0/0] pvc to_c 0/41 [RouterA-atm-pvc-Atm1/0/0-0/41-to_c] map ip 202.38.160.3 [RouterA-atm-pvc-Atm1/0/0-0/41-to_c] quit
# Configure Router B.
<HUAWEI> system-view [HUAWEI] sysname RouterB [RouterB] interface atm 1/0/0 [RouterB-Atm1/0/0] ip address 202.38.160.2 255.255.255.0 [RouterB-Atm1/0/0] pvc to_a 0/40 [RouterB-atm-pvc-Atm1/0/0-0/40-to_a] map ip 202.38.160.1 [RouterB-atm-pvc-Atm1/0/0-0/40-to_a] quit [RouterB-Atm1/0/0] pvc to_c 0/42 [RouterB-atm-pvc-Atm1/0/0-0/42-to_c] map ip 202.38.160.3 [RouterB-atm-pvc-Atm1/0/0-0/42-to_c] quit
# Configure Router C.
<HUAWEI> system-view [HUAWEI] sysname RouterC [RouterC] interface atm 1/0/0 [RouterC-Atm1/0/0] ip address 202.38.160.3 255.255.255.0 [RouterC-Atm1/0/0] pvc to_a 0/41 [RouterC-atm-pvc-Atm1/0/0-0/41-to_a] map ip 202.38.160.1 [RouterC-atm-pvc-Atm1/0/0-0/41-to_a] quit [RouterC-Atm1/0/0] pvc to_b 0/42 [RouterC-atm-pvc-Atm1/0/0-0/42-to_b] map ip 202.38.160.2 [RouterC-atm-pvc-Atm1/0/0-0/42-to_b] quit
Step 2 Configure the OAM attributes of the connection point. # Configure Router A.
[RouterA] interface atm 1/0/0 [RouterA-Atm1/0/0] oam [RouterA-Atm1/0/0-fatm-oam] attribute 0/40 0/41 end-point
[RouterB] interface atm 1/0/0 [RouterB-Atm1/0/0] oam [RouterB-Atm1/0/0-fatm-oam] attribute 0/40 end-point [RouterB-Atm1/0/0-fatm-oam] attribute 0/42 end-point
[RouterC] interface atm 1/0/0 [RouterC-Atm1/0/0] oam [RouterC-Atm1/0/0-fatm-oam] attribute 0/41 0/42 end-point
Step 3 Activate the CC function. # Configure Router A.

[RouterA] interface atm 1/0/0
7-42
Issue 03 (2010-03-31)

[RouterA-Atm1/0/0] oam [RouterA-Atm1/0/0-fatm-oam] cc 0/40 0/41 end-to-end both
7 ATM Configuration
[RouterB] interface atm 1/0/0 [RouterB-Atm1/0/0] oam [RouterB-Atm1/0/0-fatm-oam] cc 0/40 end-to-end both [RouterB-Atm1/0/0-fatm-oam] cc 0/42 end-to-end both
[RouterC] interface atm 1/0/0 [RouterC-Atm1/0/0] oam [RouterC-Atm1/0/0-fatm-oam] cc 0/41 0/42 end-to-end both
Step 4 Verify the configuration. # Check information about the OAM configuration on the router. Take the display on Router A as an example:
<RouterA> system-view [RouterA] interface atm 1/0/0 [RouterA-Atm1/0/0] oam [RouterA-Atm3/0/1-fatm-oam] display atm oam configuration atm 1/0/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 Current displayed item(s) is : 2
# Check the OAM statistics on the PVC. Take the display on Router A as an example:
<RouterA> display atm oam statistics Total number of received OAM Cells : Number of received AIS Cells : Number of received RDI Cells : Number of received loopback cells : Number of received CC cells : Number of received crc error cells : Number of received other cells : Total number of sent OAM Cells : Number of sent AIS Cells : Number of sent RDI Cells : Number of sent loopback cells : Number of sent CC cells : atm 1/0/0 0/40 0 0 0 0 0 0 0 88 0 44 0 44
----End
Configuration Files
l

# 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 #
Issue 03 (2010-03-31)
7-43
7 ATM Configuration
return l

# 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
7.9.3 Example for Configuring IMAoPSN

ATM IMAoPSN enables the transmission of ATM cells of a 3G wireless bearer network in a packet-switched network (PSN) without the need of deploying an extra ATM network for 3G services.
The bearer protocol for services between a NodeB and an RNC defined by UMTS R99/R4 is ATM. But the actual situation of an operator is that between the majority of its NodeBs and RNCs, no ready ATM network is available. By deploying the ATM IMAoPSN service, an operator can achieve transparent transmission of ATM cells through PWE3 tunnels in the PSN. The traditional solution is transparently transmitting some E1s of a NodeB to the RNC directly through a pure TDM SDH network. This method cannot achieve multiplexing of bandwidth resources, and requires a large number of E1 interfaces on the RNC. The traditional solution requires enormous construction and maintenance cost. With ATM IMAoPSN, the PE router at the side of NodeB uses the E1 IMA interface to dynamically allocate bandwidth resources and transparently transports PWE3 ATM cells after the E1 IMA termination. In this way, bandwidth resources can be multiplexed. After ATM STM-1s (or other high-speed links) are deployed on routers at the RNC side, RNCs and routers at the RNC side no longer need a larger number of E1 interfaces. In this way, construction and maintenance cost is reduced. As shown in Figure 7-3, it is required that NodeB and PE1 should be connected through multiple E1 links On PE1, add the multiple E1 links to an IMA group. Configure a VC on an interface of the IMA group. The RNC and PE2 are connected through the ATM interface. Configure a
7 ATM Configuration
VC on the ATM interface. Then, a PW is set up between PE1 and PE2 to transparently transmit ATM cells. Figure 7-3 Networking diagram of IMAoPSN configurations
E12/0/1 E12/0/2 2IMA E1 GE2/0/0 GE1/0/0 PE1 GE2/0/0 GE2/0/0 PE2 STM-1
ATM3/0/1 RNC
P PWE3 ATM Transparent Cell Transport
NodeB
Router PE1 Interface GE2/0/0 Loopback0 P GE1/0/0 GE2/0/0 Loopback0 PE2 GE2/0/0 Loopback0 IP Address 10.1.1.1/24 192.2.2.2/32 10.1.1.2/24 10.2.1.1/24 192.4.4.4/32 10.2.1.2/24 192.3.3.3/32
The configuration roadmap is as follows: 1. 2. Run the IGP protocol on the backbone network so that devices can communicate with each other. Configure basic MPLS functions on the backbone network, and configure MPLS L2VPN functions on PE devices. Establish the remote MPLS LDP peer relationship between PEs at both ends of the PW. Set parameters for the serial interface. Configure the PW template. Establish MPLS L2VC connections on PEs.
3. 4. 5.
Data Preparation
l
Identical L2VC IDs at both ends of the PW

Issue 03 (2010-03-31)
7 ATM Configuration
l l l l
MPLS LSR IDs of the PEs and P router IP address of the remote peer of the PE Coding mode and frame format of the E1/CE1 interface IMA group number and IMA interface number
Procedure
Step 1 Run the IGP protocol on the backbone network so that devices can communicate with each other. For detailed configurations, see the following configuration. Step 2 Configure basic MPLS functions on the backbone network, and configure MPLS L2VPN functions on PE devices. Then, establish the remote MPLS LDP peer relationship between PEs at both ends of the PW. For detailed configurations, see the following configuration: The remote MPLS LDP peer relationship is required only for the dynamic PW. Step 3 Set parameters for the serial interface on PE1 and then add the serial interface to the IMA group. Set parameters for the ATM interface on PE2. 1. Configure PE1. # Configure the channelized mode, AMI code, and no-CRC4 frames for CE1 2/0/1 and CE1 2/0/2 on PE1.
[PE1] controller e1 2/0/1 [PE1-E1 2/0/1] using ce1 [PE1-E1 2/0/1] code ami [PE1-E1 2/0/1] channel-set 1 timeslot-list 1-15 [PE1] controller e1 2/0/2 [PE1-E1 2/0/2] using ce1 [PE1-E1 2/0/2] code ami [PE1-E1 2/0/2] channel-set 1 timeslot-list 16-30 [PE1-E1 2/0/2] quit
# Create an IMA interface and configure the interface with transparent transmission.
[PE1] interface ima-group 2/0/1 [PE1-Ima-group2/0/1] atm cell transfer [PE1-Ima-group2/0/1] quit
# Add the channelized serial interface to the IMA group.

[PE1] interface serial2/0/1:1 [PE1-Serial2/0/1:1] link-protocol [PE1-Serial2/0/1:1] ima ima-group [PE1-Serial2/0/1:1] quit [PE1] interface serial2/0/2:1 [PE1-Serial2/0/2:1] link-protocol [PE1-Serial2/0/2:1] ima ima-group [PE1-Serial2/0/2:1] quit atm 2/0/1 atm 2/0/1
2.
Configure PE2.
[PE2] interface atm 3/0/1 [PE2-Atm3/0/1] atm cell transfer [PE2-Atm3/0/1] quit
Step 4 Configuring the PW. 1. Configure PE1.

[PE1] pw-template 1to3 [PE1-pw-template-1to3] peer-address 192.3.3.3 [PE1-pw-template-1to3] atm-pack-overtime 1000 [PE1-pw-template-1to3] quit [PE1] interface ima-group 2/0/1 [PE1-Ima-group2/0/1] mpls l2vc pw-template 1to3 100
7-46
Issue 03 (2010-03-31)

[PE1-Ima-group2/0/1] undo shutdown [PE1-Ima-group2/0/1] quit
7 ATM Configuration
2.
Configure PE2.
[PE2] pw-template 3to1 [PE2-pw-template-3to1] peer-address 192.2.2.2 [PE2-pw-template-3to1] quit [PE2] interface atm 3/0/1 [PE2-Atm3/0/1] mpls l2vc pw-template 3to1 100 [PE2-Atm3/0/1] undo shutdown [PE2-Atm3/0/1] quit
Step 5 Verify the configuration. Run the display mpls l2vc command on PEs. You can view that the status of the PW is Up. # The display on PE1 is as follows:
<PE1> display mpls l2vc interface ima-group 2/0/1 *Client Interface : Ima-group 2/0/1 is up Session State : up AC State : up VC State : up VC ID : 7 VC Type : ATM transparent cell destination : 192.3.3.3 local group ID : 0 remote group ID : 0 local VC label : 146433 remote VC label : 21504 max ATM cells : 28 ATM pack overtime : 1000 seq-number : disable local AC OAM State : up local PSN State : up local forwarding state : forwarding local status code : 0x0 remote AC OAM state : up remote PSN state : up remote forwarding state: forwarding remote statuscode : 0x0 BFD for PW : unavailable manual fault : not set active state : active forwarding entry : not exist link state : up local ATM cells : 28 remote ATM cells : 28 local VCCV : cw alert lsp-ping bfd remote VCCV : none local control word : enable remote control word : enable tunnel policy name : -traffic behavior name : -PW template name : -primary or secondary : primary VC tunnel/token info : 0 tunnels/tokens create time : 0 days, 0 hours, 0 minutes, 21 seconds up time : 0 days, 0 hours, 0 minutes, 0 seconds last change time : 0 days, 0 hours, 0 minutes, 21 seconds VC last up time : 0000/00/00 00:00:00 VC total up time : 0 days, 0 hours, 0 minutes, 0 seconds CKey : 11 NKey : 10
# The display on PE2 is as follows:

<PE2> display mpls l2vc interface atm 3/0/1 *client interface : Atm3/0/1 is up session state : up AC state : up VC state : up
Issue 03 (2010-03-31)
7-47
7 ATM Configuration

VC ID : 101 VC type : ATM transparent cell destination : 192.2.2.2 local group ID : 0 remote group ID : 0 local VC label : 140289 remote VC label : 140289 local AC OAM State : up local PSN State : up local forwarding state : forwarding local status code : 0x0 remote AC OAM state : up remote PSN state : up remote forwarding state: forwarding remote statuscode : 0x0 BFD for PW : unavailable manual fault : not set active state : active forwarding entry : exist link state : up local ATM cells : 1 remote ATM cells : 1 local VCCV : cw alert lsp-ping bfd remote VCCV : cw alert lsp-ping bfd local control word : enable remote control word : enable tunnel policy : -traffic behavior : -PW template name : -primary or secondary : primary VC tunnel/token info : 1 tunnels/tokens NO.0 TNL type : lsp , TNL ID : 0x208000 create time : 0 days, 0 hours, 16 minutes, 54 up time : 0 days, 0 hours, 16 minutes, 54 last change time : 0 days, 0 hours, 16 minutes, 54 VC last up time : 2008/07/24 12:31:31 VC total up time : 0 days, 2 hours, 12 minutes, 51 CKey : 11 NKey : 10
seconds seconds seconds seconds
----End
Configuration Files
l
Configuration file of PE1:

# sysname PE1 # mpls lsr-id 192.2.2.2 mpls # mpls l2vpn # pw-template 1to3 peer-address 192.3.3.3 atm-pack-overtime 1000 # mpls ldp # mpls ldp remote-peer 192.3.3.3 remote-ip 192.3.3.3 # controller e1 2/0/1 using ce1 code ami channel-set 1 timeslot-list 1-15 undo shutdown # controller e1 2/0/2 using ce1 code ami
7-48
Issue 03 (2010-03-31)

channel-set 1 timeslot-list 16-30 undo shutdown # interface serial2/0/1:1 link-protocol atm ima ima-group 2/0/1 undo shutdown # interface serial2/0/2:1 link-protocol atm ima ima-group 2/0/1 undo shutdown # interface ima-group 2/0/1 atm cell transfer mpls l2vc pw-template 1to3 100 # interface GigabitEthernet2/0/0 undo shutdown ip address 10.1.1.1 255.255.255.0 mpls mpls ldp # interface LoopBack0 ip address 192.2.2.2 255.255.255.255 # ospf 1 area 0.0.0.0 network 192.2.2.2 0.0.0.0 network 10.1.1.0 0.0.0.255 # return l
7 ATM Configuration
Configuration file of PE2:

# sysname PE2 # mpls lsr-id 192.3.3.3 mpls # mpls l2vpn # pw-template 3to1 peer-address 192.2.2.2 atm-pack-overtime 1000 # mpls ldp # mpls ldp remote-peer 192.2.2.2 remote-ip 192.2.2.2 # interface GigabitEthernet2/0/0 undo shutdown ip address 10.2.2.2 255.255.255.0 mpls mpls ldp # interface Atm3/0/1 undo shutdown atm cell transfer mpls l2vc pw-template 3to1 100 # interface LoopBack0 ip address 192.3.3.3 255.255.255.255 # ospf 1 area 0.0.0.0 network 192.3.3.3 0.0.0.0 network 10.2.2.0 0.0.0.255
Issue 03 (2010-03-31)
7-49
7 ATM Configuration
# return l
Configuration file of the P router:

# sysname P # mpls lsr-id 192.4.4.4 mpls # mpls ldp # interface GigabitEthernet1/0/0 undo shutdown ip address 10.1.1.2 255.255.255.0 mpls mpls ldp # interface GigabitEthernet2/0/0 undo shutdown ip address 10.2.2.1 255.255.255.0 mpls mpls ldp # interface LoopBack0 ip address 192.4.4.4 255.255.255.255 # ospf 1 area 0.0.0.0 network 192.4.4.4 0.0.0.0 network 10.1.1.0 0.0.0.255 network 10.2.2.0 0.0.0.255 # return
7-50
Issue 03 (2010-03-31)
8 1483B Configuration
8
About This Chapter
8.1 Introduction of 1483B Introduction of 1483B
1483B Configuration
This chapter describes 1483B technologies and configuration steps for IPoEoA application, along with typical examples.
8.2 Configuring IPoEoA Services This section describes how to configure IPoEoA services by using an ATM network. 8.3 Configuration Examples This section provides several configuration examples of IPoEoA.
Issue 03 (2010-03-31)
8-1
8.1 Introduction of 1483B

Introduction of 1483B 8.1.1 1483B Overview
8.1.1 1483B Overview

RFC 1483 defines the standards of transmitting multi-protocol data unit on an ATM network in the following manners:
l l
The 1483 Bridged: It is applied to the bridged protocol data unit. The 1483 Routing: It is applied to the routing protocol data unit.
RFC 1483 Bridged encapsulates the data packet of the network layer in the data link layer. 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 8-1 shows the stack protocol of 1483B. Figure 8-1 Stack protocol of 1483B
TCP/UDP IP Ethernet 1438B TCP/UDP IP Ethernet AAL5 ATM
ATM Network Access Router Router A
The IPoE Ethernet stack protocol is used to connect the device at the users' side. After 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 network and the IP network. It also supports Ethernet protocols and IP protocols.
8.2 Configuring IPoEoA Services

This section describes how to configure IPoEoA services by using an ATM network. 8.2.1 Establishing the Configuration Task 8.2.2 Creating a VE Interface 8.2.3 Configuring IPoEoA Application Mapping on a PVC 8.2.4 Configuring Services on the VE Interface 8.2.5 Checking the Configuration

Applicable Environments
The NE80E/40E support the VE interface as the gateway of IPoEoA. The core task of configuring IPoEoA on the NE80E/40E is to configure the mapping between PVC and the VE interface on the incoming interface of 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, complete the following task:
l
Configuring 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. 1 2 3 Data Number of the VE interface Number of the ATM interface VPI/VCI value of PVC
8.2.2 Creating a VE Interface

Context
Procedure
Step 1 Run:
system-view

interface virtual-ethernet interface-number
A VE interface is created and the VE interface view is displayed. ----End
8.2.3 Configuring IPoEoA Application Mapping on a PVC

Context
Procedure
Step 1 Run:
system-view


pvc { pvc [ vpi/vci ] | vpi/vci }
A PVC is created and the PVC interface view is displayed. Step 4 Run:
encapsulation aal5-encap
The AAL5 encapsulation protocol type of PVC is configured. The AAL5 encapsulation type for PVC can be aal5snap, aal5mux or aal5nlpid. By default, the encapsulation type is aal5snap.
NOTE
On the NE80E/40E, only the LPUF-10 ATM FPIC supports the aal5nlpid encapsulation type.
NOTE
Only aal5snap encapsulation supports InARP. InARP cannot be configured when aal5mux 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:
map bridge virtual-ethernet interface-number
The application mapping from PVC to VE interface is configured.

PVC and the VE interface which it is mapped to must on the same interface board, that is, numbers of the interface boards must be the same. When configuring the IPoEoA application mapping, ensure that there is no other mapping on the PVC. When configuring other mappings, ensure that there is no IPoEoA configuration on the PVC. ----End
8.2.4 Configuring Services on the VE Interface

The method for configuring VE interfaces is the same as that for configuring common Ethernet interfaces. VE interfaces support the routing mode and switching mode and support 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.

Procedure
l l l l Run the display interface atm interface-number command to check the statistic information and status of the ATM interface. Run the display atm pvc-info [ interface atm interface-number pvc [ vpi/vci ] ] command to check the related information about PVC. Run the display atm map-info command to check the mapping between PVC and the peer address. 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 of the ATM interface, it means that the configuration succeeds.
<HUAWEI> display atm interface atm 1/0/0 Atm1/0/0 current state : UP Line protocol current state : UP Last line protocol up time: 2008-11-03, 17:24:24 Description : Atm1/0/0 Interface Route Port, The Maximum Transmit Unit is 1500 bytes Internet Address is 21.1.1.1/24 AAL enabled: AAL5, Maximum VCs: 2048 VCs on main-interface: 1 (Total VCs: 1) VPs on main-interface: 0 (Total VPs: 1 ) The Vendor Name is FINISAR CORP. , The Vendor PN is FTRJ1321P1BTL Transceiver BW: 2.5G, Transceiver Mode: Single Mode WaveLength: 1310nm, Transmission Distance: 5km Rx Optical Power: -24.95dBm, Tx Optical Power: -1.99dBm Physical layer is Packet Over SDH
Issue 03 (2010-03-31)
8-5
UBR: 4, CBR: 0, VBR: 0, USED BandWidth: 0Kbps VPI Max: 255, VCI Max: 2047 Scramble enabled, clock master, CRC-32, loopback: none Flag: J0 "NetEngine " Flag: J1 "NetEngine " Flag: C2 19(0x13) SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1: 356 line layer: B2: 0 M1: 0 path layer: B3: 143 G1: 0 Statistics last cleared:never Send good cell: 0 cells Send idle cell: 25099462530 cells Receive idle cell: 0 cells Receive corrected cell: 0 Receive uncorrected cell: 97 Dropped receive cell: 0 cells Last dropped receive cell connection: 0/0 Last 30 seconds input rate: 2872 bits/sec, 0 Packets/sec Last 30 seconds output rate: 3024 bits/sec, 0 Packets/sec Input: 91929764 Bytes, 96982 Packets Output: 110681532 Bytes, 250553 Packets
Run the display atm pvc-info command. If you can view the PVC status and the interface status, it means that the configuration succeeds.
<HUAWEI> display atm pvc-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 map-info command. If you can view the mapping between the PVC and the peer address, it means that the configuration succeeds.
<HUAWEI> display atm map-info Atm1/0/0, PVC 1/33, IP, State UP 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 statistic information and status of the virtual ethernet interface, it means that the configuration succeeds.
<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 Route Port, The Maximum Transmit Unit is 1500 Internet protocol processing : disabled 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 several configuration examples of IPoEoA. 8.3.1 Example for Configuring a Routing VE Interface to Work as an IPoEoA Gateway 8.3.2 Example for Configuring ATM Bridged Ethernet
8.3.3 Example for Configuring a VLANIF Interface to Work as an IPoEoA Gateway
8.3.1 Example for Configuring a Routing VE Interface to Work as an IPoEoA Gateway

Networking Requirments
As shown in Figure 8-2, each host in two Ethernets 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 network directly through the ADSL method. The detailed networking conditions are as follows:
l l
IP address of VE of the Router C is 202.38.160.1. VPI/VCI values of 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 8-2 Networking diagram of IPoEoA configuration
Workstation
Ethernet
ADSL Router A
Workstation
DSLAM
IP:202.38.160.1
Server
Ethernet
ADSL Router B
Router C TO ADSL Router A:0/60 TO ADSL Router B:0/61 Interface:Virtual-ethernet1/0/0
Workstation
Server
The configuration roadmap is as follows: 1. 2. 3. 4.
Issue 03 (2010-03-31)
Create a VE interface. Configure an IP address for the VE interface. Create a PVC and enter the PVC view. Create the IPoEoA mapping on PVC.
Data Preparation
l l
IP address of the VE interface VPI/VCI value of PVC
Procedure
Step 1 Configure Router C. # Create a VE interface and configure an IP address for it.
<RouterC> system-view [RouterC] interface virtual-ethernet 1/0/0 [RouterC-Virtual-Ethernet1/0/0] ip address 202.38.160.1 255.255.255.0 [RouterC-Virtual-Ethernet1/0/0] quit
# Create a PVC and specify it to carry the IPoEoA protocol.

[RouterC] interface atm 1/0/0 [RouterC-Atm1/0/0] pvc to_adsl_a 0/60 [RouterC-atm-pvc-Atm1/0/0-0/60-to_adsl_a] [RouterC-atm-pvc-Atm1/0/0-0/60-to_adsl_a] [RouterC-Atm1/0/0] pvc to_adsl_b 0/61 [RouterC-atm-pvc-Atm1/0/0-0/61-to_adsl_b] [RouterC-atm-pvc-Atm1/0/0-0/61-to_adsl_b] [RouterC-Atm1/0/0] undo shutdown
map bridge virtual-ethernet 1/0/0 quit map bridge virtual-ethernet 1/0/0 quit
Step 2 Verify the configuration. # Check the PVC status information on Router C.
[RouterC] display atm pvc-info VPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE --------|-----|----------------|--------|-----|-----|--------------------0/60 |UP |to_adsl_a |60 |SNAP |ETH |Atm1/0/0 (UP) 0/61 |UP |to_adsl_b |61 |SNAP |ETH |Atm1/0/0 (UP)
The PCs connected Router A and the PCs connected Router B can ping through the VE interfaces on Router C. ----End
Configuration Files
Configuration file of RouterC
# Sysname RouterC # interface Atm1/0/0 pvc to_adsl_a 0/60 map bridge Virtual-Ethernet1/0/0 # pvc to_adsl_b 0/61 map bridge Virtual-Ethernet1/0/0 # # interface Virtual-Ethernet1/0/0 ip address 202.38.160.1 255.255.255.0 # return
8-8
Issue 03 (2010-03-31)
8.3.2 Example for Configuring ATM Bridged Ethernet

As shown in Figure 8-3, Router A and Router B are in the ATM network. The Ethernets of an enterprise 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 8-3 Networking diagram of ATM bridged Ethernet
VLAN 10
VLAN 10
Ethernet3/0/1 Router A Ethernet3/0/2 ATM1/0/0
PVC 100/1 ATM PVC 100/2 ATM1/0/0
Ethernet3/0/1 Router B Ethernet3/0/2
VLAN 20
VLAN 20
The configuration roadmap is as follows: 1. 2. 3. 4. 5. 6. Create a VLAN. Add Ethernet interfaces to the VLAN. Create a VE interface. Add the VE to the VLAN. Create a PVC and enter the PVC view. Create the IPoEoA mapping on PVC.
Data Preparation
l l l
Number of the interface added to the VLAN VLAN ID to be accessed to the ATM network VPI/VCI value of PVC that transparently transmit layer 2 packets
Issue 03 (2010-03-31)
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/0] quit
# Create a PVC and configure the IPoEoA service mapping.

[HUAWEI] interface Atm1/0/0 [HUAWEI-Atm1/0/0] undo shutdown [HUAWEI-Atm1/0/0] pvc 100/1 [HUAWEI-atm-pvc-Atm1/0/0-100/1-1] [HUAWEI-atm-pvc-Atm1/0/0-100/1-1] [HUAWEI-atm-pvc-Atm1/0/0-100/1-1] [HUAWEI-Atm1/0/0] pvc 100/2 [HUAWEI-atm-pvc-Atm1/0/0-100/2-2] [HUAWEI-atm-pvc-Atm1/0/0-100/2-2] [HUAWEI-atm-pvc-Atm1/0/0-100/2-2] [HUAWEI-Atm1/0/0] quit
encapsulation aal5snap map bridge Virtual-Ethernet1/0/0 quit encapsulation aal5snap map bridge Virtual-Ethernet1/0/1 quit
Step 2 Verify the configuration. # View the pvc status information on Router A and Router B.
[HUAWEI] display atm pvc-info VPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE --------|-----|----------------|--------|-----|-----|----------------------100/1 |UP | |0 |SNAP |ETH |Atm1/0/0 (UP) 100/2 |UP | |0 |SNAP |ETH |Atm1/0/0 (UP)
The PCs connected Router A and PC s connected Router B can ping through each other. ----End
Configuration Files
Configuration files of Router A and Router B
# Sysname HUAWEI #
8-10
Issue 03 (2010-03-31)

interface Ethernet3/0/1 portswitch port default vlan 10 # interface Ethernet3/0/2 portswitch port default vlan 20 # interface Atm1/0/0 pvc 100/1 map bridge Virtual-Ethernet1/0/0 # pvc 100/2 map bridge Virtual-Ethernet1/0/1 # # interface Virtual-Ethernet1/0/0 portswitch port default vlan 10 # interface Virtual-Ethernet1/0/1 portswitch port default vlan 20 # return
8.3.3 Example for Configuring a VLANIF Interface to Work as an IPoEoA Gateway

As shown in Figure 8-4, each host in two Ethernets 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 Ethernets on Router C. The detailed networking conditions are as follows:
l l l
The VE interface of Router C is added to VLAN 100. IP address of VLANIF 100 is 202.38.160.1. VPI/VCI values of two PVCs connecting the router and DSLAM are 0/60 and 0/61, which belong to ADSL Router A and ADSL Router B respectively.
Issue 03 (2010-03-31)
8-11
Figure 8-4 Networking diagram of IPoEoA configuration
Workstation
Ethernet
ADSL Router A
Workstation
DSLAM
IP:202.38.160.1
Server
Ethernet
ADSL Router B
Router C TO ADSL Router A:0/60 TO ADSL Router B:0/61 Interface:Virtual-ethernet1/0/0
Workstation
Server
The configuration roadmap is as follows: 1. 2. 3. 4. 5. 6. 7. Create VLAN 100. Create a VLANIF interface. Configure an IP address for the interface. Create a VE interface. Add the VE to the VLAN. Create a PVC and enter PVC view. Create the IPoEoA mapping on PVC.
Data Preparation
l l
IP address of the VLANIF interface VPI/VCI value of PVC
Procedure
Step 1 Configure Router C. # 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
8-12
Issue 03 (2010-03-31)
# Create a VE interface and add it to VLAN 100.

[RouterC] interface virtual-ethernet 1/0/0 [RouterC-Virtual-Ethernet1/0/0] portswitch [RouterC-Virtual-Ethernet1/0/0] port default vlan 100 [RouterC-Virtual-Ethernet1/0/0] quit
# Create a PVC and specify it to carry the IPoEoA protocol.

[RouterC] interface atm 1/0/0 [RouterC-atm1/0/0] pvc to_adsl_a 0/60 [RouterC-atm-pvc-atm1/0/0-0/60-to_adsl_a] [RouterC-atm-pvc-atm1/0/0-0/60-to_adsl_a] [RouterC-atm1/0/0] pvc to_adsl_b 0/61 [RouterC-atm-pvc-atm1/0/0-0/61-to_adsl_b] [RouterC-atm-pvc-atm1/0/0-0/61-to_adsl_b] [RouterC-atm1/0/0] quit
map bridge virtual-ethernet1/0/0 quit map bridge virtual-ethernet1/0/0 quit
Step 2 Verify the configuration. # View the pvc status information on Router C.
[HUAWEI] display atm pvc-info VPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE --------|-----|----------------|--------|-----|-----|------------0/60 |UP |to_adsl_a |60 |SNAP |ETH |Atm1/0/0 (UP) 0/61 |UP |to_adsl_b |61 |SNAP |ETH |Atm1/0/0 (UP)
The PCs connected Router A and the PCs connected Router B can ping through the VE interfaces on Router C. ----End
Configuraion Files
# Sysname RouterC # vlan batch 100 # interface Vlanif100 ip address 202.38.160.1 255.255.255.0 # interface Atm1/0/0 pvc to_adsl_a 0/60 map bridge Virtual-Ethernet1/0/0 # pvc to_adsl_b 0/61 map bridge Virtual-Ethernet1/0/0 # # interface Virtual-Ethernet1/0/0 portswitch port default vlan 100 # return
Issue 03 (2010-03-31)
8-13
A Glossary
A
Collates frequently used glossaries in this document. A ATM Authentication Authorization AUX
Glossary
Asynchronous Transfer Mode (ATM). A data transmission technology in which data is transferred at high data rates in fixed length, 53 bytes. An act that decides whether a user can be awarded with access right or what kinds of users can access a network. An act that accredits a user with access to certain services. 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.
C 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 callback or not. If a callback is needed, the Server tears down the connection and then initiates a call to the Client. Number of the called party. Number of the calling party.
Called Number Calling Number
P POS A MAN and LAN technology that provides a point to point connection. The POS interface is based on SONET.
Issue 03 (2010-03-31)
A-1
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 (155Mbit/s), STM-4c (622 Mbit/s) and STM-16c/STM-16 (2.5 Gbit/s).
W WAN Wide Area Network. A network that covers a large geographic area.
A-2
Issue 03 (2010-03-31)
B Acronyms and Abbreviations
B
A AA AAA AAL AAL1 AAL2 AAL3 AAL5 ACL ADSL AMI ANSI ARP ATM AU AUG AUX
Acronyms and Abbreviations
Collates frequently used acronyms and abbreviations in this document.
Anonymous Access Authentication, Authorization and Accounting ATM Adaptation Layer ATM Adaptation Layer Type 1 ATM Adaptation Layer Type 2 ATM Adaptation Layer Type 3 ATM Adaptation Layer Type 5 Access Control List Asymmetric Digital Subscriber Line Alternate Mark Inversion American National Standard Institute Address Resolution Protocol Asynchronous Transfer Mode Administrative Unit Administrative Unit Group Auxiliary (port)
B BAS BRI Broadband Access Server Basic Rate Interface
Issue 03 (2010-03-31)
B-1
C CAR CBR CCITT CD CDV CHAP CPE CPOS CSMA CUG Committed Access Rate Constant Bit Rate International Telegraph and Telephone Consultative Committee Carrier Detect Cell Delay Variation Challenge Handshake Authentication Protocol Customer Premises Equipment Channelized-POS Carrier Sense Multiple Access Closed User Group
D DCC DCD DCE DDN DHCP DLCI DLSw DNS DSL DSLAM DTE Data Communication Channel Data Carrier Detected Data Circuit-terminating Equipment Digital Data Network Dynamic Host Configuration Protocol Data Link Control Identifier Data Link Switching Domain Name System Digital Subscriber Line DSL Access Multiplexer Data Terminal Equipment
E EIA ESF ETSI Electronics Industry Association Extended Service Frame European Telecommunications Standards Institute
F FCS Frame Check Sequence
B-2
Issue 03 (2010-03-31)
FDDI FE FIFO FR FRF FRMR FS FTP
Fiber Distributed Digital Interface Fast Ethernet First In First Out Frame Relay Frame Relay Forum Frame Rejection Forced Switch File Transfer Protocol
G GE GPRS GRE Gigabit Ethernet General Packet Radio Service Generic Routing Encapsulation
H HDB3 HDLC HDSL HFC HIC HOC HTTP High Density Bipolar of Order 3 High level Data Link Control High-bit-rate Digital Subscriber Link Hybrid Fiber-Coaxial Highest Incoming-only Channel Highest Outgoing-only Channel Hyper Text Transport Protocol
I IAD IBGP ID IEEE IETF IF IGMP IP Integrated Access Device Internal BGP IDentification Institute of Electrical and Electronics Engineers Internet Engineering Task Force Information Frame Internet Group Management Protocol Internet Protocol
Issue 03 (2010-03-31)
B-3
IPC IPCP IPHC IPoA IPoE IPoEoA ISDN ISO ISP ITU-T
Inter-Process Communication IP Control Protocol IP Header compression Internet Protocols over ATM IP over Ethernet IP over Ethernet over AAL5 Integrated Services Digital Network International Organization for Standardization Internet Service Provider International Telecommunication Union - Telecommunication Standardization Sector
L L2TP LAN LAPB LCP LFI LIC LOC LQR LTC Layer 2 Tunneling Protocol Local Area Network Link Access Procedure, Balanced Link Control Protocol Link Fragmentation and Interleaving Lowest Incoming-only Channel Loss of continuity Link Quality Reports Lowest Two-way Channel
M MAP MD5 MFR MIB MP MTU Mobile Application Part Message Digest 5 Multiple Frame Relay Management Information Base Multilink PPP Maximum Transmission Unit
N NAT
B-4
Network Address Translation

NBMA NCP NE NNI NT
Non Broadcast Multiple Access Network Control Protocol NetEngine Network Node Interface Network Terminal
O OAM OC-3 OSI OSPF Operation, Administration and Maintenance OC-3 Open System Interconnection Open Shortest Path First
P PAP PC PCI PCM POH POS PPP PRI PSE PSTN PVC Password Authentication Protocol Personal Computer Protocol Control Information Pulse-Code Modulation Path Overhead Packet Over SDH/SONET Point-to-Point Protocol Primary Rate Interface Packet Switching Exchange Public Switched Telephone Network Permanent Virtual Circuit
Q QoS Quality of Service
R RADIUS RAS RFC Remote Authentication Dial in User Service Remote Access Server Request for Comments
Issue 03 (2010-03-31)
B-5
RIP RSOH RSU RTP RTU
Routing Information Protocol Regenerator Section Overhead Routing Switch Unit Real-time Transport Protocol Remote Test Unit
S SDH SDLC SDSL SF SGSN SLIP SNA SNMP SNP SOH SONET SP STM-1 SVC Synchronous Digital Hierarchy Synchronous Data Link Control Symmetrical Digital Subscriber Line Signal Failure Serving GPRS Support Node Serial Line Internet Protocol Systems Network Architecture Simple Network Management Protocol Sequence Number PDUs Section Overhead Synchronous Optical Network Service Provider SDH Transport Module -1 Switched Virtual Channel
T TACACS TCP TFTP TU TUG Terminal Access Controller Access Control System Transmission Control Protocol Trivial File Transfer Protocol Tributary Unit Tributary Unit Group
U UBR UDP Unspecified Bit Rate User Datagram Protocol
B-6
Issue 03 (2010-03-31)
UNI UP
User Network Interface User Plane
V VBR VC VCI VLAN VP VPI VPLS VPN VRP Variable Bit Rate Virtual Circuit Virtual Channel Identifier Virtual Local Area Network Virtual Path Virtual Path Identifier Virtual Private LAN Service Virtual Private Network Versatile Routing Platform
W WWW World Wide Web
Issue 03 (2010-03-31)
B-7

HUAWEI Configuration Guide - WAN Access (V600R001C00 - 03)

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

HUAWEI Configuration Guide - WAN Access (V600R001C00 - 03)

Enviado por

Direitos autorais:

Formatos disponíveis

HUAWEI NetEngine80E/40E Router V600R001C00

Configuration Guide - WAN Access

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

About This Document

About This Document

About This Document

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

8 1483B Configuration A Glossary B Acronyms and Abbreviations

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

About This Document

About This Document

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

Convention [ x | y | ... ] { x | y | ... }*

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

About This Document

Action Click Double-click Drag

Updates in Issue 03 (2010-03-31)

Updates in Issue 02 (2009-12-10)

Updates in Issue 01 (2009-09-05)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

2 E-Carrier and T-Carrier Interface Configuration.................................................................2-1

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

3 POS and CPOS Interface Configuration...............................................................................3-1

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

4 PPP and MP Configuration......................................................................................................4-1

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

5 Frame Relay Configuration......................................................................................................5-1

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

6 HDLC and IP-Trunk Configuration.......................................................................................6-1

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

A Glossary.....................................................................................................................................A-1 B Acronyms and Abbreviations.................................................................................................B-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

1 Serial Interface Configuration

Serial Interface Configuration

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1 Serial Interface Configuration

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

1.1 Introduction to the Serial Interface

1.1.1 Overview of the Synchronous Serial Interface

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

1.2 Configuring the Link Layer Attributes for a Serial Interface

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

1 Serial Interface Configuration

1.2.1 Establishing the Configuration Task

1.2.2 Configuring Link Layer Protocol Type

1 Serial Interface Configuration

HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access

The system view is displayed. Step 2 Run:

The serial interface view is displayed. Step 3 Run:

The system view is displayed. Step 2 Run: