Configuration Guide - Interface Management(V600R003C00_02) (1)

HUAWEI NetEngine80E/40E RouterV600R003C00

Configuration Guide - InterfaceManagement

Issue 02

Date 2011-09-10

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

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

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 02 (2011-09-10) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis manual describes related configurations of various interfaces and interface boardssupported by the NE80E/40E. The contents cover the configurations of common interface types,interface numbering rules, overload and recovery of the FIB module on an interface board, fastsensing of interface status changes, interface flapping control, transmission alarm customizationand suppression, and various configuration examples. This manual also provides glossaries,acronyms, and abbreviations.

This manual helps users to get familiar with common interface types, interface boardintermixing, interface flapping control, and alarm types of an interface board.

NOTE

l This document takes interface numbers and link types of the NE40E-X8 as an example. In workingsituations, the actual interface numbers and link types may be different from those used in thisdocument.

l In NE80E/40E series (except for the NE40E-X1/X2), line processing boards are called Line ProcessingUnits (LPUs) and switching fabric boards are called Switching Fabric Units (SFUs). The NE40E- X1/X2 has no LPU and SFU, and packet switching and forwarding are centrally performed by the NetworkProcessing Unit (NPU).

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

Product Name Version

HUAWEI NetEngine80E/40ERouter

V600R003C00

Intended AudienceThis document is intended for:

l Commissioning Engineerl Data Configuration Engineerl Network Monitoring Engineer

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Interface Management About This Document


ii

l System Maintenance Engineer

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

Symbol Description

DANGERAlerts you to a high risk hazard that could, if not avoided,result in serious injury or death.

WARNINGAlerts you to a medium or low risk hazard that could, ifnot avoided, result in moderate or minor injury.

CAUTIONAlerts you to a potentially hazardous situation that could,if not avoided, result in equipment damage, data loss,performance deterioration, or unanticipated results.

TIP Provides a tip that may help you solve a problem or savetime.

NOTE Provides additional information to emphasize orsupplement important points in the main text.

Command Conventions (Optional)The command conventions that may be found in this document are defined as follows.

Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

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

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.



iii

Convention Description

&<1-n> The parameter before the & sign can be repeated 1 to n times.

# A line starting with the # sign is comments.

Change HistoryChanges between document issues are cumulative. The latest document issue contains all thechanges made in earlier issues.

Changes in Issue 02 (2011-09-10)Second commercial release.

Changes in Issue 01 (2011-06-30)Initial commercial release.



iv

Contents

About This Document.....................................................................................................................ii

1 Interface Basic Configuration.....................................................................................................11.1 Interface Basic Configuration Overview............................................................................................................2

1.1.1 Interface type.............................................................................................................................................21.1.2 Service Interface Numbering Rules...........................................................................................................21.1.3 Interface Views and Prompts.....................................................................................................................41.1.4 Link Layer Protocols and Access Technologies........................................................................................71.1.5 Basic Interface Configurations Supported by the NE80E/40E..................................................................9

1.2 Configuring the Interface Description..............................................................................................................101.2.1 Establishing the Configuration Task.......................................................................................................101.2.2 Configuring the Interface Description.....................................................................................................101.2.3 Checking the Configuration.....................................................................................................................11

1.3 Configuring the Hold-Time Interval After an Interface Becomes Up/Down...................................................111.3.1 Establishing the Configuration Task.......................................................................................................111.3.2 Configuring the Hold-Time Interval After an Interface Becomes Up/Down..........................................121.3.3 Checking the Configuration.....................................................................................................................13

1.4 Configuring the Interval for Collecting the Statistics of Traffic on the Interface............................................131.4.1 Establishing the Configuration Task.......................................................................................................131.4.2 Configuring the Global Interval for Collecting Traffic Statistics............................................................141.4.3 Configuring the Interval for Collecting the Statistics of Traffic on the Interface...................................151.4.4 Configuring Traffic Statistics on Sub-Interfaces.....................................................................................151.4.5 Checking the Configuration.....................................................................................................................16

1.5 Enabling the Statistics for Packets Sent to the CPU.........................................................................................181.5.1 Establishing the Configuration Task.......................................................................................................181.5.2 Enabling the Statistics for Packets Sent to the CPU Globally.................................................................181.5.3 (Optional) Enabling the Statistics for Packets Sent to the CPU Through the VLAN.............................191.5.4 (Optional) Enabling the Statisitcs for Packets Sent to the CPU Through the PVC.................................201.5.5 Checking the Configuration.....................................................................................................................21

1.6 Configuring a Signal Sending Delay on an Interface.......................................................................................211.6.1 Establishing the Configuration Task.......................................................................................................211.6.2 Configuring a Signal Sending Delay on an Interface..............................................................................221.6.3 Checking the Configuration.....................................................................................................................23

1.7 Enabling the Alarm Function on an Interface...................................................................................................23

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Interface Management Contents


v

1.7.1 Establishing the Configuration Task.......................................................................................................231.7.2 Enabling the Alarm Function on an Interface..........................................................................................241.7.3 Checking the Configuration.....................................................................................................................25

1.8 Maintaining Interface Basic Configuration......................................................................................................261.8.1 Clearing Statistics....................................................................................................................................261.8.2 Monitoring Interface Information............................................................................................................27

2 Logical Interface Configuration................................................................................................292.1 Logical Interface Configuration Overview.......................................................................................................30

2.1.1 Introduction to Logical Interfaces...........................................................................................................302.1.2 Features of the Logical Interfaces in the NE80E/40E.............................................................................30

2.2 Creating Sub-interfaces....................................................................................................................................302.2.1 Establishing the Configuration Task.......................................................................................................312.2.2 Creating ATM Sub-interfaces.................................................................................................................312.2.3 Creating FR Sub-interfaces.....................................................................................................................322.2.4 Checking the Configuration.....................................................................................................................33

2.3 Configuring Logical Channel Interfaces..........................................................................................................342.3.1 Establishing the Configuration Task.......................................................................................................342.3.2 Creating a Logical Channel Interface......................................................................................................342.3.3 Checking the Configuration.....................................................................................................................35

2.4 Configuring Virtual-Template Interfaces.........................................................................................................352.4.1 Establishing the Configuration Task.......................................................................................................352.4.2 Configuring the IP Address of a VT Interface.........................................................................................362.4.3 Setting the Maximum Number of Links Supported by a VT Interface...................................................372.4.4 Checking the Configuration.....................................................................................................................37

2.5 Configuring Virtual-Ethernet Interfaces...........................................................................................................392.5.1 Establishing the Configuration Task.......................................................................................................392.5.2 Creating a VE Interface...........................................................................................................................392.5.3 Checking the Configuration.....................................................................................................................40

2.6 Configuring a Loopback Interface....................................................................................................................412.6.1 Establishing the Configuration Task.......................................................................................................412.6.2 Creating a Loopback Interface and Configuring Its IP Address..............................................................422.6.3 Checking the Configuration.....................................................................................................................42

2.7 Configuring a Null Interface.............................................................................................................................432.7.1 Establishing the Configuration Task.......................................................................................................432.7.2 Entering the Null Interface View.............................................................................................................432.7.3 Checking the Configuration.....................................................................................................................44

2.8 Configuration Examples...................................................................................................................................442.8.1 Example for Configuring the Sub-interface............................................................................................442.8.2 Example for Configuring the Virtual-Template Interface.......................................................................472.8.3 Example for Configuring the Loopback Interface...................................................................................47

3 Interface Board Intermixing Configuration...........................................................................503.1 Interface Board Intermixing Configuration Overview.....................................................................................51



vi

3.1.1 Introduction to Interface Board Intermixing............................................................................................513.1.2 Features of Interface Board Intermixing in the NE80E/40E...................................................................51

3.2 Configuring the Public FIB Policy...................................................................................................................513.2.1 Establishing the Configuration Task.......................................................................................................523.2.2 Configuring the Public IPv4 FIB Policy..................................................................................................523.2.3 Configuring the Public IPv6 FIB Policy..................................................................................................533.2.4 Checking the Configuration.....................................................................................................................53

3.3 Configuring the VPN FIB Policy.....................................................................................................................543.3.1 Establishing the Configuration Task.......................................................................................................543.3.2 Configuring the VPN IPv4 FIB Policy....................................................................................................553.3.3 Configuring the VPN IPv6 FIB Policy....................................................................................................563.3.4 Checking the Configuration.....................................................................................................................56

3.4 Configuring the Policy of Discarding All the FIB Entries...............................................................................573.4.1 Establishing the Configuration Task.......................................................................................................573.4.2 Configuring the Policy of Discarding All the IPv4 FIB Entries..............................................................583.4.3 Configuring the Policy of Discarding All the IPv6 FIB Entries..............................................................593.4.4 Checking the Configuration.....................................................................................................................59

3.5 Configuring Overload Suspension Recovery...................................................................................................603.5.1 Establishing the Configuration Task.......................................................................................................603.5.2 Configuring Overload Suspension Recovery..........................................................................................613.5.3 Refreshing the FIB Policy.......................................................................................................................623.5.4 Checking the Configuration.....................................................................................................................62

3.6 Configuring Overload Forwarding Recovery...................................................................................................633.6.1 Establishing the Configuration Task.......................................................................................................633.6.2 Configuring IPv4 FIB Overload Forwarding Recovery..........................................................................643.6.3 Configuring IPv6 FIB Overload Forwarding Recovery..........................................................................643.6.4 Checking the Configuration.....................................................................................................................65

3.7 Configuration Examples...................................................................................................................................663.7.1 Example for Configuring the VPN IPv4 FIB Policy...............................................................................663.7.2 Example for Configuring Overload Suspension Recovery.....................................................................733.7.3 Example for Configuring Overload Forwarding Recovery.....................................................................79

4 Fast Feeling Configuration........................................................................................................874.1 Fast Feeling Configuration Overview..............................................................................................................88

4.1.1 Introduction to Fast Feeling.....................................................................................................................884.1.2 Fast Feeling Features Supported by the NE80E/40E..............................................................................88

4.2 Configuring Fast Feeling..................................................................................................................................884.2.1 Establishing the Configuration Task.......................................................................................................884.2.2 Enabling Fast Feeling..............................................................................................................................894.2.3 Checking the Configuration.....................................................................................................................89

4.3 Maintaining Fast Feeling..................................................................................................................................904.3.1 Monitoring the Running of Fast Feeling.................................................................................................90

5 Flapping Control Configuration...............................................................................................91



vii

5.1 Flapping Control Configuration Overview.......................................................................................................925.1.1 Introduction to the Interface Flapping Control........................................................................................925.1.2 Interface Flapping Control Features Supported in the NE80E/40E........................................................92

5.2 Configuring the Interface Flapping Control.....................................................................................................935.2.1 Establishing the Configuration Task.......................................................................................................935.2.2 Enabling the Flapping Control Feature...................................................................................................945.2.3 Checking the Configuration.....................................................................................................................94

5.3 Maintaining the Flapping Control Feature.......................................................................................................955.3.1 Clearing Flapping Control Information...................................................................................................955.3.2 Monitoring the Flapping Control on the Interface...................................................................................96

6 Transmission Alarm Configuration.........................................................................................976.1 Transmission Alarm Configuration Overview.................................................................................................98

6.1.1 Introduction to Transmission Alarm Customization and Suppression....................................................986.1.2 Features of Transmission Alarm Customization and Suppression in the NE80E/40E............................98

6.2 Configuring Transmission Alarm Customization.............................................................................................996.2.1 Establishing the Configuration Task.......................................................................................................996.2.2 Configuring the Type of the Alarm That Can Affect the Physical Status of the Interface......................996.2.3 (Optional) Configuring the Respective Thresholds of B3TCA, SDBERE, and SFBERE Alarms.......1006.2.4 (Optional) Configuring the Type of the Alarms That Can Be Recorded to Logs.................................1016.2.5 Checking the Configuration...................................................................................................................102

6.3 Configuring the Interval for Filtering Transmission Alarms..........................................................................1036.3.1 Establishing the Configuration Task.....................................................................................................1036.3.2 Configuring the Interval for Filtering Transmission Alarms.................................................................1046.3.3 Checking the Configuration...................................................................................................................105

6.4 Configuring Transmission Alarm Suppression..............................................................................................1056.4.1 Establishing the Configuration Task.....................................................................................................1056.4.2 Configuring Transmission Alarm Suppression.....................................................................................1066.4.3 Checking the Configuration...................................................................................................................107

6.5 Maintaining.....................................................................................................................................................1076.5.1 Clearing Transmission Alarm Information............................................................................................107

A Glossary......................................................................................................................................109

B Acronyms and Abbreviations.................................................................................................111



viii

1 Interface Basic Configuration

About This Chapter

This chapter describes common interface types and how to view the interface information andconfigure the interval for collecting the interface traffic.

1.1 Interface Basic Configuration OverviewThis section describes common interface types and link layer protocols.

1.2 Configuring the Interface DescriptionThis section describes how to configure interface description that helps you to memorize thefunctions of interfaces.

1.3 Configuring the Hold-Time Interval After an Interface Becomes Up/DownWhen the status of an interface frequently changes between Up and Down, flapping may occur.To prevent the problem, you can configure the holt-time interval after an interface changesbetween Up and Down.

1.4 Configuring the Interval for Collecting the Statistics of Traffic on the InterfaceThis section describes how to configure the interval for collecting the statistics about trafficglobally or on the interface, which helps you to monitor network conditions.

1.5 Enabling the Statistics for Packets Sent to the CPUEnabling the statistics for packets sent to the CPU helps you know the type, number, and sourceof packets sent to the CPU.

1.6 Configuring a Signal Sending Delay on an InterfaceWhen an interface on the router is dual-homed to non-Huawei devices, you can configure asignal sending delay on the interface to avoid data loss due to asynchronous link switchover orincomplete configuration restoration.

1.7 Enabling the Alarm Function on an InterfaceIf a large number of alarms are generated on a link, the system is busy dealing with variousalarms and the system performance is thus degraded. To solve this problem, you can enable thealarm function on an interface.

1.8 Maintaining Interface Basic ConfigurationClear interface statistics and monitoring interface information are maintenance tools that helpyou know interface status.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Interface Management 1 Interface Basic Configuration


1

1.1 Interface Basic Configuration OverviewThis section describes common interface types and link layer protocols.

NOTE

The physical interfaces such as POS, E3, T3, T1, and ATM interfaces and logical interfaces such as FRand IP-Trunk interfaces are not supported on the NE40E-X1&X2 series.

1.1.1 Interface typeThis part describes interface types. Through interfaces, a device can exchange data and interactwith other devices on the network. Interfaces can be classified into physical and logicalinterfaces.

Interfaces of routers help in exchange of data and interaction with other devices on thenetwork. Interfaces can be classified into physical and logical interfaces.

Physical Interfaces

Physical interfaces exist physically and have corresponding physical components.

They are further divided into the following types:

l Local Area Network (LAN) interfaces: routers exchange data with devices in a LANthrough LAN interfaces.

Currently, the NE80E/40E supports such LAN interfaces as Ethernet interface. Ethernetinterfaces include Ethernet electrical interfaces, fast Ethernet interfaces, and GigabitEthernet interfaces.

l Wide Area Network (WAN) interfaces: routers exchange data with devices of externalnetworks through WAN interfaces.

Currently, the NE80E/40E supports such WAN interfaces as CE1 interfaces, CT1interfaces, E3 interfaces, T3 interfaces, POS interfaces,CPOS interfaces, and ATMinterfaces.

Logical Interfaces

Logical interfaces can exchange data. It, however, does not physically exist and must be createdthrough configuration.

Currently, the NE80E/40E mainly supports such logical interfaces as sub-interfaces, Eth-Trunkinterfaces, VLANIF interfaces, Virtual-Ethernet (VE) interfaces, loopback interfaces, nullinterfaces, MP-Group interfaces, IP-Trunk interfaces,tunnel interfaces, and MTunnel interfaces.

1.1.2 Service Interface Numbering RulesService interface numbering rules on the NE40E-X series vary with the hardware structures ofthese devices. This section describes the service interface numbering rules on the NE40E-X16&X8&X3 and NE40E-X1&X2.



2

Service Interface Numbering Rules of the NE40E-X16&X8&X3NOTE

The service interface numbering rules of the NE40E-16 and the NE40E-8 are the same as those of theNE40E-X16 and the NE40E-X8 and hence are not mentioned here.

On the NE40E-X16&X8&X3, an interface is numbered in the format of "LPU slot number/subcard number/port number". The following part describes the details:

l LPU slot numberLPU slot numbers begin with 1. The maximum slot number depends on the device type.For example, the maximum slot numbers on the NE40E-X16, the NE40E-X8, and theNE40E-X3 are 16, 8, and 3 respectively.

l Subcard numberThe subcard numbers of services interfaces begin with 0. The value range of the subcardnumber varies on types of boards:– Flexible card: Currently, a maximum of four service cards can be installed to one

motherboard supporting flexible cards. Therefore, the subcard number ranges from 0to 3.

– Finished board: The subcard number is always 0.l Port number

The port numbers of service interfaces on a subcard or on a finished board begin with 0.Port numbering depends on the number of interfaces on the subcard or the finished board.

Service Interface Numbering Rules of the NE40E-X1&X2The NE40E-X1&X2 has two types of service interfaces:

l Service interfaces on an NPU– The NE40E-X1 has only one NPU (in slot 1) and the NPU has two service interfaces,

always numbered GE 1/0/0 and GE 1/0/1.– The NE40E-X2 has two NPUs (in slot 7 and slot 8). The NPU in slot 7 has two service

interfaces, always numbered GE 7/0/0 and GE 7/0/1. The NPU in slot 8 has two serviceinterfaces, always numbered GE 8/0/0 and GE 8/0/1.

l Service interfaces on a subcardThe NE40E-X1&X2 and the NE40E-X16&X8&X3 have differences in hardwarestructures. On the NE40E-X1&X2, data forwarding on service interfaces all needs to beprocessed by the NPUs. Therefore, on the NE40E-X1&X2, an interface is numbered in theformat of "NPU slot number/subcard number/port number".– NPU slot number

It is the slot number of the NPU which is responsible for data forwarding on serviceinterfaces.The NE40E-X1 has only one NPU and therefore the slot number is always 1.The NE40E-X2 has two NPUs. The NPU in slot 7 is responsible for data forwardingon the service interfaces in slots 3 to 6 in the lower chassis. Therefore, on cards in slots3 to 6, the NPU slot numbers in the service interface numbers is always 7. The NPU inslot 8 is responsible for data forwarding on the service interfaces in slots 9 to 12 in theupper chassis. Therefore, on cards in slots 9 to 12, the NPU slot numbers in the serviceinterface numbers is always 8.



3

– Subcard numberIt is the slot number of the subcard where service interfaces reside. The subcard numberson the NE40E-X1 range from 2 to 5 and the subcard numbers on the NE40E-X2 rangefrom 3 to 6 and 9 to 12.

– Port numberThe port numbers of service interfaces on a subcard begin with 0. Port numberingdepends on the number of interfaces on the subcard.

The service interface numbering rules of the NE40E-X1&X2 are special. Therefore, thefollowing two diagrams are provided to illustrate service interface numbering rules.

Figure 1-1 Diagram of the service interface numbering rule of the NE40E-X1

10

FAN

8 PSU 9 PSU

1 NPU

5 FIC/HIC4 FIC/HIC

3 FIC/HIC

6 MPU 7 MPU

2 FIC/HIC

g1/5/1

g1/2/2

g1/0/1

Figure 1-2 Diagram of the service interface numbering rule of the NE40E-X2

15

FAN

13 PSU 14 PSU

11 FIC 12 FIC

10 FIC/HIC9 FIC/HIC

8 NPU

7 NPU

5 FIC/HIC 6 FIC/HIC

4 FIC3 FIC

1 MPU 2 MPU

g7/0/1

g8/9/2

g8/11/2

g7/3/2

1.1.3 Interface Views and PromptsThis part describes command views of physical and logical interfaces, and the commands andprompts used to enter the views of interfaces.

Command views and prompts of physical interfaces supported by the NE80E/40E are shown inTable 1-1; command views and prompts of logical interfaces are shown inTable 1-2.



4

Table 1-1 Command line views and prompts of physical interfaces

Interface CommandLine View

Command Prompt

Ethernetinterface

Ethernetinterface view

Run the interfaceethernet 1/0/0command in thesystem view.

[HUAWEI-Ethernet1/0/0]

GigabitEthernetinterface

GE interfaceview

Run the interfacegigabitethernet1/0/0 command inthe system view.

[HUAWEI-GigabitEthernet1/0/0]

AUX interface(auxiliaryinterface)

AUX interfaceview

Run the interfaceaux 0/0/1 commandin the system view.

[HUAWEI-Aux0/0/1]

Sync serialinterface(channelizedserial interface)

Sync serialinterface view

Run the interfaceserial 1/0/0command in thesystem view (thenumber of achannelized serialinterface is of four-dimensional or five-dimensionalstructure, such as1/0/0:1 or 1/0/0/0:1).

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

CE1 interface CE1 interfaceview

Run the controllere1 1/0/0 command inthe system view.

[HUAWEI-E1 1/0/0]

CT1 interface CT1 interfaceview

Run the controllert1 1/0/0 command inthe system view.

[HUAWEI-T1 1/0/0]

E3 interface orCE3 interface

E3 interfaceview or CE3interface view

Run the controllere3 1/0/0 command inthe system view.

[HUAWEI-E3 1/0/0]

T3 interface T3 interfaceview

Run the controllert3 1/0/0 command inthe system view.

[HUAWEI-T3 1/0/0]

POS interface POS interfaceview

Run the interfacepos 3/0/0 commandin the system view.

[HUAWEI-Pos 3/0/0]

CPOSinterface

CPOSinterface view

Run the controllercpos 3/0/0 commandin the system view.

[HUAWEI-Cpos 3/0/0]



5


Command Prompt

ATM interface ATM interfaceview

Run the interfaceatm 2/0/0 commandin the system view.

[HUAWEI-Atm 2/0/0]

Table 1-2 Command line views and prompts of logical interfaces


Command Prompt

Sub-interface Sub-interfaceview

Run theinterfacegigabitethernet1/0/0.1command in thesystem view.

[HUAWEI-gigabitethernet1/0/0.1]

Logic channelinterface

Logical channelinterface view

Run theinterface logic-channel 100command in thesystem view.

[HUAWEI-Logic-Channel100]

Virtual-Ethernetinterface

Virtual-Ethernetinterface view

Run theinterfacevirtual-ethernet1/0/0 commandin the systemview.

[HUAWEI-Virtual-Ethernet1/0/0]

Eth-Trunkinterface

Eth-Trunkinterface view

Run theinterface eth-trunk 1command in thesystem view.

[HUAWEI-Eth-Trunk1]

Loopbackinterface

Loopbackinterface view

Run theinterfaceloopback 2command in thesystem view.

[HUAWEI-LoopBack2]

NULL interface NULL interfaceview

Run theinterface null 0command in thesystem view.

[HUAWEI-NULL0]

MP-groupinterface

MP-groupinterface view

Run theinterface mp-group 3/0/0 inthe system view.

[HUAWEI-Mp-group 3/0/0]



6


Command Prompt

IP-Trunkinterface

IP-Trunkinterface view

Run theinterface ip-trunk 0 in thesystem view.

[HUAWEI-Ip-Trunk0]

Tunnel interface Tunnel interfaceview

Run theinterface tunnel1/0/6 commandin the systemview.

[HUAWEI-Tunnel1/0/6]

MTunnelinterface

MTunnelinterface view

Run theinterfacemtunnel 0 in thesystem view.

[HUAWEI-MTunnel0]

NOTE

If the interface is disabled by default, run the undo shutdown command to enable the interface.

1.1.4 Link Layer Protocols and Access TechnologiesThis part describes the functions of the link layer and major link layer protocols.

The link layer provides reliable transmission of data from one site to the other. The link layerreceives packets from the network layer, and then encapsulates packets into frames to deliverthem to the physical layer.

Link layer protocols supported by the NE80E/40E are described as follows.

EthernetThe current LAN mainly refers to the Ethernet. The Ethernet is a broadcast network. It is widelyused because it is flexible, simple, and easily extended.

TrunkTrunk interfaces can be divided into Eth-Trunk and IP-Trunk interfaces. Eth-Trunk interfacesconsist of Ethernet links only. IP-Trunk interfaces consist of POS links only.

The trunk technology features the following advantages:

l Increases bandwidth: The bandwidth of an interface is the sum of the bandwidth of allmember interfaces.

l Enhances reliability: When a member link fails, its traffic is automatically switched to otheravailable links. This enhances the reliability of the entire trunk link.

VLANThe Virtual Local Area Network (VLAN) divides a physical LAN into several logical sub-nets,regardless of their physical locations.



7

Data transmission within a VLAN does not interfere with that in other VLANs. This enhancesthe network security.

QinQ

The QinQ technology adds one a layer of 802.1Q tag on the 802.1Q packet to expand the VLANspace. In this way, data of the VLAN can be transparently transmitted in the public network.

MSTP

The Multiple Spanning Tree Protocol (MSTP) divides a switched network into multiple regions.Multiple spanning trees (MST) are generated in each region. Each MST is independent of oneanother.

MSTP provides fast convergence and multiple redundant paths for data forwarding, andimplements load balancing of VLAN data during data forwarding.

RRPP

The Rapid Ring Protection Protocol (RRPP) is a link layer protocol specially used for theEthernet ring. If the Ethernet ring is complete, RRPP can prevent the broadcast storm caused bythe data loop. When a link on the Ethernet ring is disconnected, RRPP helps to quickly enablethe standby link and then recover the communication channels between nodes on the ringnetwork.

RPR

The Resilient Packet Ring (RPR) protocol is a Layer 2 protocol. It provides a better solution forthe MAN by taking the advantages of SDH/SONET and other ring networks, and integratingthe intelligentized IP, the economy of Ethernet and the high reliability of the optical ring network.

RPR offers carrier-class reliability. It provides not only data-oriented transmission but alsointegrated solution for multiple services.

PPP

The Point-to-Point Protocol (PPP) encapsulates an IP datagram over serial links. It supports the8-bit asynchronous mode, free of parity check and bit-oriented synchronous link.

PPP includes link control protocols to create, configure, and authenticate the data links. It alsoincludes network control protocols that are oriented to different network layer protocols.

The NE80E/40E also supports the Multi-link Protocol (MP), which binds multiple PPP linkstogether to provide larger bandwidth.

Frame Relay

Frame Relay (FR) is a technology developed in the early 1980s. It is derived from X.25 packetcommunication technology.

FR is mainly used for data transfer in the form of frames with a set of procedures. FR implementslogical rather than physical connections.



8

Multiple logical connections can be multiplexed onto the same physical connection. Thus,multiple logical channels can be created to achieve bandwidth multiplexing and dynamicallocation.

FR simplifies X.25. It has high processing efficiency, high network throughput, and low delay.

HDLC

High-Level Data Link Control (HDLC) is a group of protocols used for data transmission. HDLCis one of the most widely applied protocols on the data link layer.

HDLC data units (frames) are transmitted through the network and acknowledged by thereceiver. HDLC also manages data flow and data sending intervals.

ATM

Asynchronous Transfer Mode (ATM) takes a cell as the basic unit to implement informationtransportation, multiplexing, and exchange. ATM cells come from different sources without anyspecial mode requirement. There can be space between cells, which is filled with idle cells.

An ATM link is the unidirectional transmission mode and supports multiple rates that arecompatible with SONET. The transfer medium of ATM is generally optical fiber. However,coaxial cable or category 5 twisted pair can be used within 100 m. Therefore, ATM can be usedfor cable television Hybrid Fiber Coaxial Network (HFC).

1.1.5 Basic Interface Configurations Supported by the NE80E/40EAfter familiarizing yourself with basic interface configurations, you can configure commoninformation for interfaces.

Interface Description

Interface descriptions record the use of interfaces, which helps you memorize the use ofinterfaces to rapidly identify interfaces.

Interval for Collecting Interface Traffic Statistics

When you need to know traffic information (including traffic rate) on an interface within aspecific period, you can configure an interval at which interface traffic statistics are collected.

Statistics About Packets Sent to the CPU

CPU resources are limited and thus precious. If a large number of attack packets are sent to theCPU, the CPU will become too busy to process normal packets. This may cause the system tofail to answer real-time demands and fail to implement reliability. Therefore, you need to knowthe accurate number and source of packets to take measures in time.

After enabling the statistics about packets sent to the CPU, you can view the statistics aboutpackets sent to the CPU on the main interface, sub-interface, VLAN, or PVC. This helps youknow the number and source of packets sent to the CPU.



9

1.2 Configuring the Interface DescriptionThis section describes how to configure interface description that helps you to memorize thefunctions of interfaces.

1.2.1 Establishing the Configuration TaskBefore configuring interface description, familiarize yourself with the applicable environment,pre-configuration tasks, and required data. This helps you plan and manage interfacedescriptions.

Applicable Environment

To maintain many interfaces, you need to describe these interfaces to accurately and rapidlyrecognize the interfaces.

Pre-configuration Tasks

Before configuring the interface description, complete the following tasks:

l Powering on the router and starting it normally.

Data Preparation

To configure the interface description, you need the following data.

No. Data

1 Interface type and number

2 Description of the interface

1.2.2 Configuring the Interface DescriptionConfiguring the interface description helps you memorize the functions of interfaces, and thusyou can quickly identify interfaces.

Procedure

Step 1 Run:system-view

The system view is displayed.

Step 2 According to the physical features of the interface, choose different commands to enter thecorresponding interface view.l Run the interface interface-type interface-number command to enter the Ethernet, Eth-

Trunk, POS, IP-Trunk, Virtual-Ethernet,or ATMinterface view.



10

l Run the controller interface-type interface-number command to enter the CE1, E3, CT1,T3, or CPOS interface view.

NOTE

You cannot configure the description of the interface in the user interface view that is displayed by usingthe user-interface interface-type interface-number command.

Step 3 Run:description interface-description

The description of the interface is configured.

You can run the display interface description command to view the description of an interface.

----End

1.2.3 Checking the ConfigurationAfter the interface description is configured, you need to check whether the configuration iscorrect.

PrerequisiteThe configurations of the interface description function are complete.

Procedure

Step 1 Run the display interface description [ interface-type [ interface-number ] | slot slot-id[ card card-number ] ] command to check the description of the interface.

----End

Example

Run the display interface description command. If the description of the interface is displayed,it means that the configuration succeeds. For example:

<HUAWEI> display interface description gigabitethernet1/0/0

Interface DescriptionGigabitEthernet1/0/0 Connected to PE1's GigabitEthernet 1/0/0

1.3 Configuring the Hold-Time Interval After an InterfaceBecomes Up/Down

When the status of an interface frequently changes between Up and Down, flapping may occur.To prevent the problem, you can configure the holt-time interval after an interface changesbetween Up and Down.

1.3.1 Establishing the Configuration TaskBefore configuring the hold-time interval after an interface becomes Up/Down, familiarizeyourself with the applicable environment, complete the pre-configuration tasks, and obtain therequired data. This can help you complete the configuration task quickly and accurately.



11


When the status of an interface frequently alternates between Up and Down, flapping may occur.To prevent the problem, the system responds to the change of the interface status only after aninterval.


Before configuring the interface description, complete the following tasks:

l Powering on the router and starting it normally

Data Preparation

To configure the hold-time interval for an interface, you need the following data.

No. Data

1 Interface type and interface number

2 Hold-time interval after an interface becomes Up/Down

1.3.2 Configuring the Hold-Time Interval After an InterfaceBecomes Up/Down

When the status of an interface frequently changes between Up and Down, flapping may occur.To prevent the problem, you can configure the holt-time interval after an interface changesbetween Up and Down.

Context

Do as follows on the router:

Procedure



Step 2 Run:interface interface-type interface-number

The interface view is displayed.

Step 3 Run the following command as required:l To configure the hold-time interval after an interface becomes Up, run:

carrier up-hold-time interval

l To configure the hold-time interval after an interface becomes Down, run:carrier down-hold-time interval



12

The hold-time interval can be configured on Gigabit Ethernet interfaces.

----End

1.3.3 Checking the ConfigurationAfter the hold-time interval after an interface becomes Up/Down is configured, you need tocheck the configuration and ensure that the configuration is correct.

Prerequisite

Run the following command to check the previous configuration.

Procedure

Step 1 Run display current-configuration [ [ interface-type [ interface-number ] | slot slot-id [ cardcard-number ] ] command to check the hold-time interval set for the interface.

----End

Example

Run the display current-configuration interface GigabitEthernet 1/0/0 command. You canview the hold-time interval set for GE 1/0/0 after GE 1/0/0 goes Up or Down.

<HUAWEI> display current-configuration interface GigabitEthernet 1/0/0interface GigabitEthernet1/0/0carrier down-hold-time 100carrier up-hold-time 10

1.4 Configuring the Interval for Collecting the Statistics ofTraffic on the Interface

This section describes how to configure the interval for collecting the statistics about trafficglobally or on the interface, which helps you to monitor network conditions.

1.4.1 Establishing the Configuration TaskFamiliarizing yourself with the applicable environment, pre-configuration tasks, and requireddata helps you flexibly configure the interval for collecting the statistics about traffic on theinterface, which helps you to monitor network conditions.


To set the interval for collecting the statistics of traffic on the interface so that you can easilycollect the interface traffic and rate, you can configure the function of collecting the statistics oftraffic on the interface.

In the system view and interface view, you can configure the interval for collecting the statisticsof traffic on the interface. In this manner, you can flexibly collect the statistics of the traffic rateof all or partial interfaces.



13

NOTE

l In the NE80E/40E, you can configure the interval for collecting the statistics of traffic on the interfacein the system view and interface view.

l The interval set in the interface view is effective on the current interface.

l The interval set in the system view is effective on all the interfaces whose interval adopts the defaultvalue set in the interface view.


Before configuring the function of collecting the statistics of traffic on the interface, completethe following task:

l Powering on and starting the router normally

Data Preparation

To configure the function of collecting the statistics of traffic on the interface, you need thefollowing data.

No. Data


2 Interval for collecting the statistics of traffic on the interface

1.4.2 Configuring the Global Interval for Collecting TrafficStatistics

The global interval for collecting traffic statistics takes effect on all the interfaces that are notconfigured with an interval for collecting traffic statistics. This helps you configure the intervalfor collecting traffic statistics for multiple interfaces at a time.

Context

Do as follows on the router to be configured with the global interval for collecting the trafficstatistics:

Procedure



Step 2 Run:set flow-stat interval interval

The global interval for collecting traffic statistics is configured.



14

NOTE

The new interval takes effect after the original interval expires. Traffic statistics on logical interfaces aredisplayed in the second periodical update after the new interval takes effect. Traffic statistics on physicalinterfaces are displayed when the new interval takes effect.

----End

1.4.3 Configuring the Interval for Collecting the Statistics of Trafficon the Interface

The interval for collecting traffic statistics on an interface is valid for the interface only. Afterthe interval is configured, you can view the traffic volume and rate on the interface.

ContextDo as follows on the router to be configured with the interval for collecting the statistics of trafficon the interface:

Procedure





NOTE

On a main control board, the Ethernet interfaces that are used to connect the network management stationor the multi-frame cannot be configured with the interval for collecting the statistics of traffic on theinterface.

Step 3 Run:set flow-stat interval interval

The interval for collecting the statistics of traffic on the interface is configured.

NOTE

The new interval takes effect after the original interval expires. Traffic statistics on logical interfaces aredisplayed in the second periodical update after the new interval takes effect. Traffic statistics on physicalinterfaces are displayed when the new interval takes effect.

----End

1.4.4 Configuring Traffic Statistics on Sub-InterfacesYou can configure the traffic statistics function on a main interface to collect the traffic statisticsabout all sub-interfaces of the main interface.

ContextDo as follows on the router that needs to be configured with traffic statistics:



15

ProcedureStep 1 Run:

system-view


Step 2 Run the following command as required.l To collect the traffic statistics about sub-interfaces of all interfaces in the system, run:

subinterface traffic-statistics enablel To collect the traffic statistics about sub-interfaces of an interface, run:

1. Run the interface interface-type interface-number command to enter the view of aspecific interface.

2. Run the subinterface traffic-statistics enable command to enable the traffic statisticsfunction on the sub-interfaces of the specified interface.

l To collect the traffic statistics about a sub-interface, do as follows:

1. Run the interface interface-type interface-number.subinterface-number command toenter the view of a specific interface.

2. Run the statistic enable command to collect the traffic statistics about a specific sub-interface.

By default, the traffic statistics function is enabled on main interfaces.

To enable the traffic statistics function on VLANIF interfaces, you need to run the statisticenable command in the VLAN view.

----End

1.4.5 Checking the ConfigurationAfter configuring traffic statistics on interfaces, you need to check the configuration and ensurethat the configuration is correct.

PrerequisiteRun the following commands to check the previous configuration.

Procedurel Run the display current-configuration configuration system command to check the

global interval for collecting the traffic statistics.l Run the display interface [ interface-type [ interface-number ] ] command to check the

statistics of traffic on an interface.l Run the display interface [ interface-type [ interface-number.subinterface-number ] ]

command to check the statistics of traffic on a sub-interface.

----End

Example# After the traffic statistics function is enabled on a sub-interface, run the display interface[ interface-type [ interface-number.subinterface-number ] ] command. You can view thestatistics of incoming traffic and outgoing traffic.



16

<HUAWEI> display interface gigabitethernet 2/0/1.1GigabitEthernet2/0/1.1 current state : UPLine protocol current state : UPLast up time: 2008-02-18, 06:50:38Description: GigabitEthernet2/0/1.1 InterfaceRoute Port,The Maximum Transmit Unit is 1500Internet Address is 12.1.1.1/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fcd4-7aadEncapsulation dot1q Virtual LAN, The number of Vlan is 1 Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 5 packets,1040 bytes, 10 unicast,0 broadcast,0 multicasts 0 errors,0 drops Output:5 packets,510 bytes, 5 unicast,0 broadcast,0 multicasts 0 errors,0 drops

# Run the display current-configuration configuration system command. If the global intervalfor collecting the traffic statistics is displayed, it means that the configuration succeeds. Run thedisplay interface command, you can view that after the global interval for collecting the trafficstatistics is successfully configured, the interval for collecting the traffic statistics on all theinterfaces whose interval adopts the default value changes to the global interval for collectingthe traffic statistics.

<HUAWEI> display current-configuration configuration system# sysname HUAWEI# set flow-stat interval 100#interface Eth-Trunk2 set flow-stat interval 20 ip address 11.1.1.1 255.255.255.0#return <HUAWEI> display interface Eth-TrunkEth-Trunk1 current state : UPLine protocol current state : UPLast up time: 2008-04-18, 14:00:30Description: Eth-Trunk1 InterfaceRoute Port,Hash arithmetic : According to flow,The Maximum Transmit Unit is 1500Internet Address is 11.1.1.1/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc7f-7258Physical is ETH_TRUNK Last 100 seconds input rate 0 bits/sec, 0 packets/sec Last 100 seconds output rate 0 bits/sec, 0 packets/sec Input: 13 packets,1212 bytes, 12 unicast,1 broadcast,0 multicasts 0 errors,0 drops Output:13 packets,1212 bytes, 11 unicast,2 broadcast,0 multicasts 0 errors,0 drops-----------------------------------------------------PortName Status Weight-----------------------------------------------------GigabitEthernet2/0/2 UP 1-----------------------------------------------------The Number of Ports in Trunk : 1The Number of UP Ports in Trunk : 1Eth-Trunk2 current state : UPLine protocol current state : UPLast up time: 2008-04-21, 11:16:47Description: Eth-Trunk2 InterfaceRoute Port,Hash arithmetic : According to flow,The Maximum Transmit Unit is 1500Internet Address is 13.1.1.1/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc7f-7258



17

Physical is ETH_TRUNK Last 20 seconds input rate 0 bits/sec, 0 packets/sec Last 20 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops-----------------------------------------------------PortName Status Weight-----------------------------------------------------GigabitEthernet2/0/4 UP 1-----------------------------------------------------The Number of Ports in Trunk : 1The Number of UP Ports in Trunk : 1

1.5 Enabling the Statistics for Packets Sent to the CPUEnabling the statistics for packets sent to the CPU helps you know the type, number, and sourceof packets sent to the CPU.

1.5.1 Establishing the Configuration TaskFamiliarizing yourself with the applicable environment, pre-configuration tasks, and requireddata of the statistics for packets sent to the CPU helps you monitor network traffic, analyze trafficsources, and protect the device from attacks.


CPU resources are precious. To know the accurate number and source of packets sent to theCPU, you need to enable the statistics for packets sent to the CPU. Then, you can view thestatistics for packets sent to the CPU as required.


Before enabling the statistics for packets sent to the CPU, complete the following task:

l Switching on the router, which then starts and succeeds in the self-test.

Data Preparation

Before enabling the statistics for packets sent to the CPU, you need the following data.

No. Data


1.5.2 Enabling the Statistics for Packets Sent to the CPU GloballyViewing the statistics for packets sent to the CPU globally helps you know the number andsource of packets sent to the CPU.



18

ContextCPU resources are precious. After enabling the statistics for packets sent to the CPU, you canknow the number and source of packets sent to the CPU by viewing the statistics.

Do as follows on the device that requires the statistics for packets sent to the CPU:

Procedure



Step 2 Run:cpu-packet statistics enable

The statistics for packets sent to the CPU are enabled.

----End

1.5.3 (Optional) Enabling the Statistics for Packets Sent to the CPUThrough the VLAN

Enabling the statistics for packets sent to the CPU from VLANs of interfaces helps you knowinformation about packets in VLANs.

ContextDo as follows on the device that requires the statistics for packets sent to the CPU through theVLAN:

Procedure






The Ethernet interface view, GE interface view, or Eth-Trunk interface view is displayed.

Step 4 Run:cpu-packet statistics vlan enable

The statistics for packets sent to the CPU through the VLAN of the interface are enabled.

NOTE

Currently, a maximum of 64 VLAN-based or PVC-based interfaces on one router can be enabled with thestatistics for packets sent to the CPU.



19

After the configurations, you can view the statistics by running different commands accordingto different situations:

l If the VLAN is the default VLAN of the interface or both the default VLAN and the TrunkVLAN, the statistics for packets sent to the CPU are based on the interface. In this case, youcan use the display cpu-packet statistics interface interface-type interface-number allcommand to view the statistics.

l Otherwise, the statistics are based on both the interface and the VLAN. You can use thedisplay cpu-packet statistics interface interface-type interface-number vlan vlan-idcommand to view the statistics.

----End

1.5.4 (Optional) Enabling the Statisitcs for Packets Sent to the CPUThrough the PVC

Enabling the statistics for packets sent to the CPU from PVCs of ATM interfaces helps youknow information about packets on PVCs of ATM links.

Context

Do as follows on the device that requires the statistics for packets sent to the CPU through thePVC:

Procedure





Step 3 Run:interface atm interface-number

The ATM interface view is displayed.

Step 4 Run:cpu-packet statistics pvc enable

The statistics for packets sent to the CPU through the PVC of the ATM interface are enabled.

NOTE

Currently, a maximum of 64 VLAN-based or PVC-based interfaces on one router can be enabled with thestatistics for packets sent to the CPU.

----End



20

1.5.5 Checking the ConfigurationAfter the statistics for packets sent to the CPU is enabled, you need to check whether theconfiguration is correct. In addition, you can view information about the packets sent to the CPU,know the number and source of packets, and thus analyze network conditions.

PrerequisiteThe configurations are completed for enabling the statistics for packets sent to the CPU.

Procedurel Run the display cpu-packet statistics interface interface-type interface-number all

command to view the statistics for packets sent to the CPU from the specified interface.l Run the display cpu-packet statistics interface interface-type interface-number pvc vpi/

vci command to view the statistics for packets sent to the CPU from the specified PVC ofthe specified interface.

l Run the display cpu-packet statistics interface interface-type interface-number vlanvlan-id command to view the statistics for packets sent to the CPU from the specified VLANof the specified interface.

l Run the display cpu-packet statistics slot { all | slot-id } command to view the statisticsfor packets sent to the CPU from all interfaces in the specified slot.

----End

ExampleRun the display cpu-packet statistics interface interface-type interface-number all commandto view the statistics for packets sent to the CPU from the specified interface.

<HUAWEI> display cpu-packet statistics interface gigabitethernet 1/0/0 allGigabitEthernet1/0/0: 8 packets, 1099 bytes

1.6 Configuring a Signal Sending Delay on an InterfaceWhen an interface on the router is dual-homed to non-Huawei devices, you can configure asignal sending delay on the interface to avoid data loss due to asynchronous link switchover orincomplete configuration restoration.

NOTE

The feature is not supported on the NE80E/40E-X1&X2 series.

1.6.1 Establishing the Configuration TaskBefore configuring a signal sending delay on an interface, familiarize yourself with theapplicable environment, complete the pre-configuration tasks, and obtain the required data. Thiscan help you complete the configuration task quickly and accurately.

Applicable EnvironmentWhen the router configured with VRRP or E-APS services is dual-homed to non-Huaweidevices, the router cannot control traffic switchover between interfaces on the non-Huaweidevices. In this case, link switchover on the router is probably asynchronous with that on the



21

non-Huawei devices. If the interface on the router sends a signal immediately after beinginitialized, certain data is probably discarded.

If an interface on the router is directly connected to a non-Huawei device, when the router isrestarted, the interface sends a signal to the peer immediately after being initialized, whichprobably causes data loss before configurations of the router are restored.

To prevent this problem, you can configure a signal sending delay on the interface.

Pre-configuration TasksBefore configuring a signal sending delay on an interface, complete the following task:

l Powering on the router and ensuring a successful self-check

Data PreparationTo configure a signal sending delay on an interface, you need the following data.

No. Data

1 Delay after which an interface sends a signal after being initialized

1.6.2 Configuring a Signal Sending Delay on an InterfaceWhen an interface on the router is dual-homed to non-Huawei devices, you can configure asignal sending delay on the interface to avoid data loss due to asynchronous link switchover orincomplete configuration restoration.

ContextWhen the router configured with VRRP or E-APS services is dual-homed to non-Huaweidevices, the router cannot control traffic switchover between interfaces on the non-Huaweidevices. In this case, link switchover on the router is probably asynchronous with that on thenon-Huawei devices. If the interface on the router sends a signal immediately after beinginitialized, certain data is probably lost.

If an interface on the router is directly connected to a non-Huawei device, when the router isrestarted, the interface sends a signal to the peer immediately after being initialized, whichprobably causes data loss before configurations of the router are restored.

To prevent the problem, you can do as follows to configure a signal sending delay on therouter.

Procedure






22


Step 3 Run:port-tx-enabling-delay port-tx-delay-time

The signal sending delay function is enabled and a signal sending delay is configured.

You need to consider services that have been configured on the device when configuring a signalsending delay.

----End

1.6.3 Checking the ConfigurationAfter a signal sending delay is configured on an interface, you can restart the board that theinterface belongs to and then check the configured signal sending delay and how manymilliseconds are left before the interface sends a signal to the peer.

PrerequisiteA signal sending delay is configured on an interface and the board that the interface belongs tois restarted.

Procedure

Step 1 Run the display port-tx-enabling-delay command to check the configured signal sending delayon the interface.

----End

Example# Display the signal sending delay configured on GE 1/0/0.

<HUAWEI> display port-tx-enabling-delay interface gigabitethernet 1/0/0GigabitEthernet 1/0/0 setted port-tx-enabling delay time is: 100 msGigabitEthernet 1/0/0 remanent time of enabling port-tx is: 20 ms

1.7 Enabling the Alarm Function on an InterfaceIf a large number of alarms are generated on a link, the system is busy dealing with variousalarms and the system performance is thus degraded. To solve this problem, you can enable thealarm function on an interface.

1.7.1 Establishing the Configuration TaskBefore enabling the alarm function on an interface, familiarize yourself with the applicableenvironment, complete the pre-configuration tasks, and obtain the required data. This can helpyou complete the configuration task quickly and accurately.

Applicable EnvironmentIf a large number of alarms are generated on a link, the system is busy dealing with variousalarms. The system performance is thus degraded. In this manner, you can set the threshold thattriggers the alarm for interfaces. When the number of errors exceeds the set threshold, an alarm



23

is generated. You can then take measures for troubleshooting to ensure the normal transmissionof services.


Before configuring the interface description, complete the following task:

l Powering on the router and ensuring that the self-test is successful

Data Preparation

To configure the alarm function for interfaces, you need the following data.

No. Data

1 Interface type and interface number

2 Thresholds for alarms of the CRC error, SDH error, expiration of the input-rate,and expiration of the output-rate

1.7.2 Enabling the Alarm Function on an InterfaceIf a large number of alarms are generated on a link, the system is busy dealing with variousalarms. To solve this problem can configure the type of alarms to be process by the system, thealarm threshold, and the interval for sending alarm messages to the NMS to release the burdenof the system.

Context

Do as follows on the interface connected to the transmission device:

Procedure



Step 2 Run:snmp-agent trap enable port { crc-error-rising | sdh-error-rising | broadcast-threshold | optical-module-abnormal }

The alarm function is enabled on an interface.

Set the type of alarms as required.

l To enable the alarm function for Cyclic Redundancy Check (CRC) errors, crc-error-rising is set.

l To enable the alarm function for Synchronous Digital Hierarchy (SDH) errors, sdh-error-rising is set.

l To enable the alarm function for broadcast suppression, broadcast-threshold is set.



24

l To enable the alarm function for abnormal optical power of the optical module on an interface,optical-module-abnormal is set.



Set the alarm threshold for the interface as required.

l To set the alarm threshold for CRC errors, run:trap-threshold crc-error threshold interval-second interval-value

l To set the alarm threshold for SDH errors, run:trap-threshold sdh-error threshold interval-second interval-value

NOTEInterfaces that support the alarms of SDH errors are ATM, POS, and 10GE WAN interfaces.

l To set the alarm threshold for the bandwidth utilization of the incoming traffic, run:trap-threshold input-rate ratio

l To set the alarm threshold for the bandwidth utilization of the outgoing traffic, run:trap-threshold output-rate ratio

By default, the alarm threshold for CRC errors is 3 and the interval for generating an alarm forCRC errors is 10 seconds; the alarm threshold for SDH errors is 3 and the interval for generatingan alarm for SDH errors is 10 seconds; the alarm threshold for the bandwidth utilization of theincoming traffic is 100%; the alarm threshold for the bandwidth utilization of the outgoing trafficis 100%.

----End

1.7.3 Checking the ConfigurationAfter the alarm function is enabled on an interface, you need to check the configuration andensure that the configuration is correct.

PrerequisiteRun the following commands to check the previous configuration.

Procedure

Step 1 Run the display current-configuration [ [ interface-type [ interface-number ] | slot slot-id[ card card-number ] ] command to check the alarm messages on the interface.

----End

Example# Display the alarm thresholds for CRC errors, SDH errors, bandwidth utilization of the incomingtraffic, and bandwidth utilization of the outgoing traffic on POS 1/0/0.

<HUAWEI>display current-configuration interface pos 1/0/0interface Pos1/0/0 link-protocol ppp undo shutdown trap-threshold crc-error 1000 interval-second 600



25

trap-threshold sdh-error 1000 interval-second 600 trap-threshold input-rate 80 trap-threshold output-rate 80

# Display the alarm thresholds for the bandwidth utilization of the incoming traffic andbandwidth utilization of the outgoing traffic on GE 1/0/0.

<HUAWEI>display current-configuration interface GigabitEthernet1/0/0interface GigabitEthernet1/0/0 trap-threshold input-rate 80 trap-threshold output-rate 80

1.8 Maintaining Interface Basic ConfigurationClear interface statistics and monitoring interface information are maintenance tools that helpyou know interface status.

1.8.1 Clearing StatisticsAfter interface statistics are cleared, you can start the statistics again, which helps you know thetraffic volume and rate on interfaces at any time.

Context

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

To clear the interface statistics collected through the NMS or with the display interfacecommand, run the following reset counters commands in the user view. After that, you can clearthe traffic statistics on the interfaces again.

NOTE

For details on how to view the traffic statistics collected through the NMS, refer to the related manual aboutthe NMS.

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

user view to clear the interface statistics collected with the display interface command.

l Run the reset reset counters if-mib interface [ interface-type [ interface-number ] ]command in the user view to clear the interface statistics collected through the NMS.

l Run the following command in the user view to clear the statistics of the packets sent tothe CPU.

– Run the reset cpu-packet statistics interface interface-type interface-number allcommand to clear the statistics of all the packets sent to the CPU through the specifiedinterface.



26

– Run the reset cpu-packet statistics interface interface-type interface-number pvc vpi/vci command to clear the statistics of all the packets sent to the CPU through thespecified PVC on the specified interface.

– Run the reset cpu-packet statistics interface interface-type interface-number vlanvlan-id command to clear the statistics of all the packets sent to the CPU through thespecified VLAN on the specified interface.

– Run the reset cpu-packet statistics slot { all | slot-id } command to clear the statisticsof all the packets sent to the CPU in all slots.

----End

1.8.2 Monitoring Interface InformationMonitoring interface statistics helps you know the traffic volume and rate on interfaces, and thusanalyze network conditions.

Context

Running the display interface command, you can view the current status and description of theinterface and the statistics of the received and sent packets. Run the following commands in theuser view.

Procedurel Run the display interface [ interface-type [ interface-number ] | slot slot-id ] command to

check the current operating status of the interface and statistics collected on the interface.

l Run the display interface-statistics { interface-type interface-number } &<1-5>[ interval interval ] [ times times ] or display interface-statistics batch interface-typeinterface-number1 [ to interface-number2 ] [ interval interval ] [ times times ] commandin any view to check statistics about traffic on the interface.

l Run the display interface brief command in any view to check the brief information aboutall the interfaces on the device, including the physical status, protocol status, and bandwidthutilization of the interface.

l Run the display ip interface [ interface-type interface-number ] command in any view tocheck the IP configuration of the interface.

l Run one of the following commands in any view to check brief IP configuration of theinterface.

– display ip interface brief [ interface-type [ interface-number ] ]

– display ip interface brief [ slot slot-number [ card card-number ] ]

– display ip interface brief [ ip-configured [ except interface-type ] ]

l Run the display cpu-packet statistics slot { all | slot-id } command in any view to checkthe statistics for packets sent to the CPU from all interfaces in the specified slot.

l Run the display cpu-packet statistics interface interface-type interface-number allcommand in any view to check the statistics for packets sent to the CPU from the specifiedinterface.

l Run the display cpu-packet statistics interface interface-type interface-number pvc vpi/vci command in any view to check the statistics for packets sent to the CPU from thespecified PVC of the specified interface.



27

l Run the display cpu-packet statistics interface interface-type interface-number vlanvlan-id command in any view to check the statistics for packets sent to the CPU from thespecified VLAN of the specified interface.

l Run the display interface phy-option interface-type interface-number command in userview to check the physical attributes of the specified interface.

----End



28

2 Logical Interface Configuration

About This Chapter

Learning interface types, configuration procedure, and configuration examples of logicalinterfaces helps you make full use of logical interfaces, thus improving the system performance.

2.1 Logical Interface Configuration OverviewThis section describes main types of logical interfaces.

2.2 Creating Sub-interfacesThis part describes how to create sub-interfaces.

2.3 Configuring Logical Channel InterfacesIf you need to provide the backup function for an interface or take an FR VC (or the VC ofanother type) as a main interface or backup interface, you should create a logic channel interface.

2.4 Configuring Virtual-Template InterfacesLearning the applicable environment and basic configurations of Virtual-Template (VT)interfaces helps you know that VT interfaces are used for PPP to bear other link layer protocols.

2.5 Configuring Virtual-Ethernet InterfacesLearning the applicable environment and basic configurations of Virtual-Ethernet (VE)interfaces helps you realize bearing among multiple link layer protocols by using VE interfaces.

2.6 Configuring a Loopback InterfaceLoopback interfaces always remain in the Up state once created and have the loopback function.

2.7 Configuring a Null InterfaceAll the packets sent to null interfaces are discarded.

2.8 Configuration ExamplesThis section provides examples to show how to configure logical interfaces.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Interface Management 2 Logical Interface Configuration


29

2.1 Logical Interface Configuration OverviewThis section describes main types of logical interfaces.

2.1.1 Introduction to Logical InterfacesLogical interfaces do not exist physically. They are manually configured for data exchange.

A logical interface refers to an interface that does not physically exist, and can be created onlythrough manual configuration. Logical interfaces include sub-interfaces, Eth-Trunk interfaces,VLANIF interfaces, Virtual-Ethernet interfaces, loopback interfaces, null interfaces, MP-Groupinterfaces,IP-Trunk interfaces,Tunnel interfaces and MTunnel interfaces.

NOTE

l For the configurations of Eth-Trunk interfaces, VLANIF interfaces, and VE interfaces logicalinterfaces, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - LAN Access &MAN Access.

l For the configurations of MP-Group interfaces, IP-Trunk interfaces, refer to the HUAWEINetEngine80E/40E Router Configuration Guide - WAN Access.

l For the details of the tunnel interface, refer to "VPN Tunnel" in the HUAWEI NetEngine80E/40ERouter Feature Description - VPN. For the configuration of the tunnel interface, refer to the chapter"VPN Tunnel Management Configuration" in the HUAWEI NetEngine80E/40E Router ConfigurationGuide - VPN.

l For the details of MTI interfaces, refer to "Multicast VPN Configuration" in the HUAWEINetEngine80E/40E Router Configuration Guide - IP Multicast.

2.1.2 Features of the Logical Interfaces in the NE80E/40EThis part describes the applicable environment of logical interfaces.

NOTE

ATM sub-interfaces, FR sub-interfaces, and virtual-template (VT) interfaces are not supported on theNE80E/40E-X1&X2 series.

The NE80E/40E mainly supports the following types of logical interfaces:

l Sub-interface: It is mainly used to implement communication between a physical link andmultiple remote ends.

l Logical channel interface: It is mainly used in interface backup.l Virtual-Ethernet (VE) interface: It is mainly used when other data link layer protocols need

to be carried by the Ethernet protocol. l Loopback interface: It is mainly used when the status of the interface needs to be always

Up or the interface needs to be configured with 32-bit subnet mask. l Null interface: It is mainly used in route filtering because any network packets sent to this

interface are discarded.

2.2 Creating Sub-interfacesThis part describes how to create sub-interfaces.



30

NOTE

ATM sub-interfaces and FR sub-interfaces are not supported on the NE40E-X1&X2 series.

2.2.1 Establishing the Configuration TaskLearning the applicable environment, pre-configuration tasks, and required data helps you createsub-interfaces and understand that sub-interfaces realize point-to-multipoint (P2MP)connections.


Sub-interfaces are used to provide multiple links on one physical interface. The followingphysical interfaces support sub-interfaces:

l Ethernet interfacesl FR interfacesl ATM interface

Ethernet sub-interfaces are generally applied to communication between VLANs.

NOTE

For the configuration of an Ethernet sub-interface and its application in VLANs, refer to the HUAWEINetEngine80E/40E Router Configuration Guide - LAN Access & MAN Access.

Logical interfaces such as Eth-Trunk interfaces and VE interfaces also support the creation ofsub-interfaces because these logical interfaces have the characteristics of the FR or Ethernetinterface. For details, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide -LAN Access & MAN Access and HUAWEI NetEngine80E/40E Router Configuration Guide -WAN Access.


Before configuring a sub-interface, complete the following tasks:

l Powering on the router and starting the router normally.l Correctly connecting the physical interface of the sub-interface.

Data Preparation

To create the sub-interface, you need the following data.

No. Data

1 Number of the main interface

2 Number of the sub-interface

2.2.2 Creating ATM Sub-interfacesCreating ATM sub-interfaces realizes P2MP connections on ATM links.



31

ContextFor the detail about ATM sub-interface configuration, refer to the chapter "ATM Configuration"in the HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access.

Procedure



Step 2 Run:interface atm interface-number.subnumber [ p2mp | p2p ]

An ATM sub-interface is configured.

subnumber specifies the number of the ATM Sub-interface. The number ranges from 1 to 1024

In practice, a main interface can support up to 1024 sub-interfaces.

The default type of an ATM sub-interface is P2MP.

NOTE

When an interface is configured with a sub-interface, the interval for consecutively running theshutdown and undo shutdown commands on the main interface needs to be 15 seconds at least.

----End

2.2.3 Creating FR Sub-interfacesCreating FR sub-interfaces realizes P2P connections on FR links.

ContextFor the detail about FR sub-interface configuration, refer to "Frame Relay Configuration" in theHUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access.

Procedure





Step 3 Run:link-protocol fr [ ietf | nonstandard ]

The link layer protocol of the interface is configured as FR.

Step 4 Run:quit



32

Return to the system view.

Step 5 Run:interface interface-type interface-number.subnumber [ p2p ]

An FR sub-interface is configured.

subnumber is the number of the sub-interface. The value ranges from 1 to 1024. In practice, amain interface can support up to 1024 sub-interfaces.

The default type of an FR sub-interface is P2MP.

NOTE

When an interface is configured with a sub-interface, the interval for consecutively running theshutdown and undo shutdown commands on the main interface needs to be 15 seconds at least.

The items described below can be configured on an FR sub-interface.

l Frame Relay address mapping different from the main interfacel IP address which is not in the same network segment as the main interfacel Virtual circuit of the sub-interface

----End

2.2.4 Checking the ConfigurationAfter sub-interfaces are created, you need to check whether the configuration is correct. Inaddition, you can view information about sub-interfaces.

PrerequisiteThe configurations of the creating sub-interfaces function are complete.

Procedurel Run the display atm interface [ atm interface-number ] command to check the status of

the ATM sub-interface.l Run the display fr interface [ interface-type interface-number ] command to check the

status of the FR sub-interface.

----End

ExampleRun the display atm interface command, and you can view that the link layer protocol statusof the ATM sub-interface is Up and the type of the sub-interface is P2MP. Simultaneously, youcan also view PVC information, address mapping, and the statistics of the received and sentpackets on this sub-interface.

<HUAWEI> display atm interface atm 1/0/0.2ATM interface Atm1/0/0.2, multi-point, State UP Sub-interface Information: PVCs: 1, MAPs: 1 input pkts: 5, input bytes: 460, input pkt errors: 5 output pkts: 5, output bytes: 460, output pkt errors: 5

Run the display fr interface command, and you can see the link layer protocol status of the FRsub-interface is Up and the type of the sub-interface is P2MP.



33

<HUAWEI> display fr interfaceSerial1/0/0, DTE, physical up, protocol up Serial1/0/0.2, multi-point, protocol up

2.3 Configuring Logical Channel InterfacesIf you need to provide the backup function for an interface or take an FR VC (or the VC ofanother type) as a main interface or backup interface, you should create a logic channel interface.

2.3.1 Establishing the Configuration TaskThis part describes the applicable environment, pre-configuration tasks, and required data forconfiguring logical channel interfaces.

Applicable EnvironmentCreate a logic channel interface and configure it to provide an interface with backup functionor take an FR (or other) VC as a main interface or backup interface.

Pre-configuration TasksBefore configuring a logical channel interface, power on the router and start the router normally.

Data PreparationTo configure the logical channel interface, you need the following data.

No. Data

1 Number of the logical channel interface

2.3.2 Creating a Logical Channel InterfaceLogical channel interfaces can be created only on the main board.

ContextYou can dynamically create or delete the logical channel interface. Once the logical channelinterface is created, it remains in the Up state, till you delete it.

Procedure



Step 2 Run:interface logic-channel interface-number

A logical channel interface is configured.



34

Note that logical channel interface can only be created on main control board. The value ofinterface-number ranges from 0 to 1023.

----End

2.3.3 Checking the ConfigurationAfter a logical channel interface is configured, you need to check whether the configuration iscorrect. In addition, you can view the status of the logical channel interface.

PrerequisiteThe configurations of the configuring logical channel interfaces function are complete.

Procedure

Step 1 Run the display interface logic-channel [ interface-number ] command to check the status andconfiguration of the logical channel interface.

----End

ExampleRun the display interface logic-channel command. If the status and configuration of the logicalchannel interface are displayed, it means the configuration succeeds.

<HUAWEI> display interface Logic-ChannelLogic-Channel0 current state : UPLine protocol current state :UP (spoofing)Description: Logic-Channel0 InterfaceRoute Port,The Maximum Transmit Unit is 1500Current system time: 2010-09-10 10:03:18-08:00 Input bandwidth utilization : 0.00% Output bandwidth utilization : 0.00%

2.4 Configuring Virtual-Template InterfacesLearning the applicable environment and basic configurations of Virtual-Template (VT)interfaces helps you know that VT interfaces are used for PPP to bear other link layer protocols.

NOTE

The VT interfaces are not supported on the NE80E/40E-X1&X2 series.

2.4.1 Establishing the Configuration TaskWhen PPP is required to bear other link layer protocols, VT interfaces are created to realize theintercommunication.

Applicable EnvironmentThe Virtual-Template (VT) interface is used in VPN, MP and ATM applications. The systemcreates and deletes VA interfaces and the process is transparent to users.

The link layer of VT interfaces only supports the PPP protocol and the network layer onlysupports IP.



35

CAUTIONl The newly configured or modified parameters of a VT interface can take effect only after the

shutdown and the undo shutdown command are run.l To configure or modify services such as MPLS, MTU or IS-IS, configure or modify those

services, and then perform related VT interface configuration on the other interfaces.


Before configuring a VT interface, complete the following tasks:

l Installing and powering on the router properlyl Configuring the physical interface

Data Preparation

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

No. Data

1 Number of the VT interface

2 IP address of the VT interface

3 Number of maximum links for sending multicast or broadcast packets supported bythe VT interface

2.4.2 Configuring the IP Address of a VT InterfaceWhen VT interfaces are used to communicate with other devices, you need to configure IPaddresses for the VT interfaces.

Procedure



Step 2 Run:interface virtual-template vt-number

A VT interface is created and the VT interface view is displayed.

vt-number specifies the number of the VT interface. The value ranges from 0 to 1023.

Before deleting the VT interface, ensure that all of its derived VA interfaces are closed.

Step 3 Run:ip address ip-address { mask| mask-length } [ sub ]



36

The IP address of the VT interface is configured.

----End

2.4.3 Setting the Maximum Number of Links Supported by a VTInterface

When a VT interface has a large number of links, the system performance is affected if multicastor broadcast packets are sent through every link. After the maximum number of links supportedby a VT interface is configured, when the number of links exceeds the upper limit, multicast orbroadcast packets are discarded, which ensures that the system runs normally.

Procedure



Step 2 Run:interface virtual-template vt-number

A VT interface is created and the VT interface view is displayed.

Step 3 Run:broadcast-limit link number

The maximum number of links supported by the VT interface for sending multicast or broadcastpackets is configured.

The multicast or broadcast packets which are sent out from each link may affect the systemperformance if there are too many links in the VT interface.

Using the broadcast-limit link command, you can restrict the packets since the packets aredropped when the link number exceeds the maximum number.

NOTE

It is not recommended to configure multiple services such as MP, L2TP and PPPoE on a VT.

By default, the maximum link number is 30 for the VT interface.

----End

2.4.4 Checking the ConfigurationAfter VT interfaces are configured, you need to check whether the configuration is correct. Inaddition, you can view the statistics about VT interfaces.

PrerequisiteThe configurations of Virtual-Template interfaces are complete.

Procedurel Run the display interface virtual-template [ vt-number ] command to check the status of

a VT interface.



37

l Run the display virtual-access [ va-number | peer peer-address | slot slot-id | user user-name | vt vt-number ] * command to check the status of a VA interface.

----End

Example

Run the display interface virtual-template command. If the configuration of a VT interface isdisplayed, it means the configuration succeeds.

<HUAWEI> display interface Virtual-Template 0Virtual-Template0 current state : UPLine protocol current state :UP (spoofing)Description: Virtual-Template0 InterfaceRoute Port,The Maximum Transmit Unit is 1500Internet Address is 10.1.1.1/24Link layer protocol is PPPLCP initialPhysical is None, baudrate is 64000 bpsQoS max-bandwidth : 64 KbpsOutput queue : (Urgent queue : Size/Length/Discards) 0/50/0Output queue : (Protocol queue : Size/Length/Discards) 0/1000/0Output queue : (FIFO queue : Size/Length/Discards) 0/256/0Current system time: 2010-09-10 10:03:18-08:00Statistics 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 Realtime 0 seconds input rate 0 bits/sec, 0 packets/sec Realtime 0 seconds output rate 0 bits/sec, 0 packets/sec Input: 7 packets,458 bytes, 0 unicast,0 broadcast,0 multicast 0 errors,0 drops,0 unknownprotocol Output:7 packets,458 bytes, 0 unicast,0 broadcast,0 multicast 0 errors,0 drops Input bandwidth utilization : 0.00% Output bandwidth utilization : 0.00%

Run the display virtual-access command. If the status of a VA interface is displayed, it meansthe configuration succeeds. For example:

<HUAWEI> display virtual-access slot 1----------------Slot 1----------------Virtual-Template1:0 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-08, 11:21:34 Description: Virtual-Template1:0 InterfaceRoute Port,The Maximum Transmit Unit is 1500Link layer protocol is PPPLCP opened, MP opened, IPCP openedPhysical is MPQoS max-bandwidth : 64 KbpsOutput queue : (Urgent queue : Size/Length/Discards) 0/50/0Output queue : (Protocol queue : Size/Length/Discards) 0/1000/0Output queue : (FIFO queue : Size/Length/Discards) 0/256/0Current system time: 2010-09-10 10:03:18-08:00Statistics last cleared: 2008-08-02 15:32:27 Last 20 seconds input rate 0 bits/sec, 0 packets/sec Last 20 seconds output rate 0 bits/sec, 0 packets/sec Realtime 0 seconds input rate 0 bits/sec, 0 packets/sec Realtime 0 seconds output rate 0 bits/sec, 0 packets/sec Input: 7 packets,458 bytes, 0 unicast,0 broadcast,0 multicast 0 errors,0 drops,0 unknownprotocol Output:7 packets,458 bytes, 0 unicast,0 broadcast,0 multicast



38

0 errors,0 drops Input bandwidth utilization : 0.00% Output bandwidth utilization : 0.00%

2.5 Configuring Virtual-Ethernet InterfacesLearning the applicable environment and basic configurations of Virtual-Ethernet (VE)interfaces helps you realize bearing among multiple link layer protocols by using VE interfaces.

2.5.1 Establishing the Configuration TaskThis part describes the applicable environment, pre-configuration tasks, and required data forconfiguring VE interfaces.


Virtual-Ethernet (VE) interfaces are mainly used in PPPoEoA and IPoEoA. VE interfaces canalso be used to configure the policy-based routing, firewall,and routes.

Configuration of the VE interface is like that of the Ethernet interface. For details, refer to thechapter "Ethernet Interface Configuration" in the HUAWEI NetEngine80E/40E RouterConfiguration Guide - LAN Access & MAN Access.

In addition, VE interfaces support the following features:

l Routing protocols

l Switching Layer 2 port through the portswitch command

l Supporting the VLAN technology


Before configuring a VE interface, power on the router and start the router normally.

Data Preparation

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

No. Data

1 Number of the VE interface

2 MAC address of the VE interface

2.5.2 Creating a VE InterfaceBefore creating a VE interface, ensure that the physical board in the corresponding slot mustexist.



39

Procedure



Step 2 Run:interface virtual-ethernet ve-number

A VE interface is created and the VE interface view is displayed.

The parameter ve-number specifies the number of a VE interface, including slot/card/serial, theserial number is ranging from 0 to 1023.

If the binding relationship between a VE interface and the permanent virtual channel (PVC) thatbears PPPoEoA or IPoEoA is established, you can successfully delete this VE interface onlywhen you unbind the VE interface from the PVC.

----End

2.5.3 Checking the ConfigurationAfter VE interfaces are configured, you need to check whether the configuration is correct. Inaddition, you can view the statistics about VE interfaces.

PrerequisiteThe configurations of Virtual-Ethernet interfaces are complete.

Procedure

Step 1 Run the display interface virtual-ethernet [ ve-number ] command to check the status of a VEinterface.

----End

ExampleRun the display interface virtual-ethernet command. If the configuration and status of thespecified VE interface are displayed, it means that the configuration succeeds. For example:

<HUAWEI> display interface Virtual-EthernetVirtual-Ethernet1/0/0 current state : DOWNLine protocol current state : DOWNDescription: Virtual-Ethernet1/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 1500Internet protocol processing : disabledIP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc99-9999QoS max-bandwidth : 10000 KbpsOutput queue : (Urgent queue : Size/Length/Discards) 0/50/0Output queue : (Protocol queue : Size/Length/Discards) 0/1000/0Output queue : (FIFO queue : Size/Length/Discards) 0/256/0Current system time: 2010-09-10 10:03:18-08:00 Input bandwidth utilization : 0.00% Output bandwidth utilization : 0.00%Virtual-Ethernet2/0/0 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-03, 17:24:24Description: Virtual-Ethernet2/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 1500



40

Internet Address is 200.1.1.2/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc99-9999Carrier Layer: 1 PVC total, 1 map up, 0 map downQoS max-bandwidth : 10000 KbpsOutput queue : (Urgent queue : Size/Length/Discards) 0/50/0Output queue : (Protocol queue : Size/Length/Discards) 0/1000/0Output queue : (FIFO queue : Size/Length/Discards) 0/256/0Current system time: 2010-09-10 10:03:18-08:00 Input bandwidth utilization : 0.00% Output bandwidth utilization : 0.00% Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 drops 5 packets output, 300 bytes, 0 drops

2.6 Configuring a Loopback InterfaceLoopback interfaces always remain in the Up state once created and have the loopback function.

2.6.1 Establishing the Configuration TaskLearning the applicable environment, pre-configuration tasks, and required data for configuringloopback interfaces helps you know the characteristics of loopback interfaces.


As the loopback interface always remains in the Up state once created and has the loopbackcharacteristic, it can be used to improve the reliability.

The loopback interface is usually used in two situations.

l The IP address of the loopback interface is designated as the source address of packets.

l Controlling the access interface and filtering log based on the IP address simplifyinformation.

Generally, BGP uses the optimal local address to set up the TCP connection with its neighbor.If the interface turns to Down, the BGP neighbor relationship cannot be set up. In practice, oftenmore than one link can reach the same neighbor. In this situation, using the loopback interfaceas the BGP neighbor of the local router can ensure the reliable connection.


Before configuring a Loopback interface, power the router and start the router normally.

Data Preparation

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

No. Data

1 Number of the loopback interface

2 IP address of the loopback interface



41

2.6.2 Creating a Loopback Interface and Configuring Its IP AddressIn most cases, you need to assign IP addresses to loopback interfaces, and then use the loopbackinterfaces that are always Up to communicate with other devices.

Procedure



Step 2 Run:interface loopback loopback-number

A loopback interface is created and the lookback interface view is displayed.

You can create or delete loopback interface dynamically. Once a loopback interface is created,it keeps Up all the time until it is deleted.

Step 3 Run:ip address ip-address [ mask | mask-length ] [ sub ]

The IP address of the loopback interface is configured.

----End

2.6.3 Checking the ConfigurationAfter loopback interfaces are configured, you need to check whether the configuration is correct.In addition, you can view the statistics about loopback interfaces.

PrerequisiteThe configurations of a loopback interface are complete.

Procedure

Step 1 Run the display interface loopback [ loopback-number ] command to check the status of aloopback interface.

----End

ExampleRun the display interface loopback command, and you can view that the link layer protocolstatus of the interface is Up.

<HUAWEI> display interface loopback 6LoopBack6 current state : UPLine protocol current state :UP (spoofing)Description: LoopBack6 InterfaceRoute Port,The Maximum Transmit Unit is 1500Internet Address is 10.10.1.1/24Physical is LoopbackCurrent system time: 2010-09-10 10:03:18-08:00Statistics last cleared: 2008-08-02 15:32:27 Last 20 seconds input rate 0 bits/sec, 0 packets/sec



42

Last 20 seconds output rate 0 bits/sec, 0 packets/sec Realtime 6 seconds input rate 0 bits/sec, 0 packets/sec Realtime 6 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicast 0 errors Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicast 0 errors Input bandwidth utilization : 0.00% Output bandwidth utilization : 0.00%

2.7 Configuring a Null InterfaceAll the packets sent to null interfaces are discarded.

2.7.1 Establishing the Configuration TaskThis part describes the applicable environment, pre-configuration tasks, and data preparationfor configuring null interfaces.

Applicable EnvironmentThe Null interface is like the null devices supported by some operating systems. All packets,which are sent to the Null interface, are dropped. The system creates a Null interface NULL0.

Since all packets sent to the Null interface are dropped, you can directly send packets to befiltered out to the Null interface. In this case, you may not configure an ACL.

For example, using the following command will discard all packets that are sent to the192.101.0.0 network segment.

[HUAWEI] ip route-static 192.101.0.0 255.255.0.0 NULL 0

Pre-configuration TasksBefore configuring a Null interface, power the router and start the router normally.

Data PreparationNone.

2.7.2 Entering the Null Interface ViewThe system automatically creates a Null interface NULL0.

Procedure



Step 2 Run:interface null 0

The null interface view is displayed.



43

The null interface remains in the Up state all the time. It cannot forward data packet. You canneither configure an IP address for it nor encapsulate it with protocols.

----End

2.7.3 Checking the ConfigurationAfter null interfaces are configured, you need to check whether the configuration is correct. Inaddition, you can view statistics about null interfaces.

PrerequisiteThe configurations of a null interface are complete.

Procedure

Step 1 Run the display interface null [ 0 ] command to check the status of a null interface.

----End

ExampleRun the display interface null command, and you can view that the status of the null interfaceis Up.

<HUAWEI> display interface null 0NULL0 current state : UPLine protocol current state :UP (spoofing)Description: NULL0 InterfaceRoute Port,The Maximum Transmit Unit is 1500Internet protocol processing : disabledPhysical is NULL DEVCurrent system time: 2010-09-10 10:03:18-08:00Statistics 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 Realtime 0 seconds input rate 0 bits/sec, 0 packets/sec Realtime 0 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 Input bandwidth utilization : 0.00% Output bandwidth utilization : 0.00%

2.8 Configuration ExamplesThis section provides examples to show how to configure logical interfaces.

2.8.1 Example for Configuring the Sub-interfaceThis example shows how to realize the P2MP connection by configuring FR sub-interfaces.

Networking RequirementsAs shown in Figure 2-1:



44

l POS 1/0/0 of Router A is connected with Router B and Router C through the public FRnetwork.

l A sub-interface is configured on POS 1/0/0 on Router A so that LAN 1 can access bothLAN 2 and LAN 3 through POS 1/0/0.

Figure 2-1 Networking diagram of configuring the sub-interface

LAN3: 129.11.0.0/16

LAN 2: 129.10.0.0/16

DLCI=50

DLCI=60

DLCI=70

DLCI=80

202.38.160.1

POS1/0/0202.38.161.2

202.38.161.1

POS1/0/0202.38.160.2

RouterA

Router B

RouterCLAN1: 129.9.0.0/16

POS1/0/0.2

POS1/0/0.1Frame Relay

network

Configuration Roadmap

The configuration roadmap is as follows:

1. Configure the link protocol of the interface that accesses the FR network.

2. Configure sub-interfaces and allocate IP addresses and VC.

3. Configure the static route to the peer LAN.

Data Preparation

To configure the sub-interface, you need the following data:

l On Router A, the number of the interface that accesses the FR network

l IP addresses of two sub-interfaces on Router A

l DLCIs that connect Router A to the FR network

l Network addresses of three LANs

l On Router B and Router C, the IP addresses of the interfaces that access the FR network



45

Procedure

Step 1 Configure Router A.

# Configure link layer protocol as FR on POS 1/0/0 of Router A.

<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] interface pos 1/0/0[RouterA-Pos1/0/0] link-protocol fr[RouterA-Pos1/0/0] undo shutdown[RouterA-Pos1/0/0] quit

# Configure the sub-interface POS 1/0/0.1 on Router A, and assign VC for it.

[RouterA] interface pos 1/0/0.1 p2p[RouterA-Pos1/0/0.1] ip address 202.38.160.1 255.255.255.0[RouterA-Pos1/0/0.1] undo shutdown[RouterA-Pos1/0/0.1] fr dlci 50[RouterA-fr-dlci-Pos1/0/0.1-50] quit

# Configure the sub-interface POS 1/0/0.2 on Router A, and assign VC for it.

[RouterA] interface pos 1/0/0.2 p2p[RouterA-Pos1/0/0.2] ip address 202.38.161.1 255.255.255.0[RouterA-Pos1/0/0.2] undo shutdown[RouterA-Pos1/0/0.2] fr dlci 60[RouterA-fr-dlci-Pos1/0/0.2-60] quit

# Configure the static routes from Router A to LAN2 and LAN3.

[RouterA] ip route-static 129.10.0.0 255.255.0.0 202.38.160.2[RouterA] ip route-static 129.11.0.0 255.255.0.0 202.38.161.2

NOTE

This example mainly explains sub-interface configuration. Router B and Router C do not need to beconfigured with sub-interfaces.

Step 2 Check the configuration.

After running the ping command, you can see that three LANs can access each other.

----End

Configuration Filesl Configuration file of Router A

#sysname RouterA#interface Pos1/0/0 link-protocol fr undo shutdown#interface Pos1/0/0.1 p2p fr dlci 50 undo shutdown ip address 202.38.160.1 255.255.255.0#interface Pos1/0/0.2 p2p fr dlci 60 undo shutdown ip address 202.38.161.1 255.255.255.0# ip route-static 129.10.0.0 255.255.0.0 202.38.160.2 ip route-static 129.11.0.0 255.255.0.0 202.38.161.2#



46

return

l Configuration file of Router B#sysname RouterB#interface Pos1/0/0 link-protocol frfr dlci 70 undo shutdown ip address 202.38.160.2 255.255.255.0#ip route-static 129.9.0.0 255.255.0.0 202.38.160.1#return

l Configuration file of Router C#sysname RouterC#interface Pos1/0/0 link-protocol frfr dlci 80 undo shutdown ip address 202.38.161.2 255.255.255.0#ip route-static 129.9.0.0 255.255.0.0 202.38.161.1#return

2.8.2 Example for Configuring the Virtual-Template InterfaceVT interfaces are mainly used in the VPN and WAN configurations.

ContextFor configuration example of the VT in VPN, refer to the HUAWEI NetEngine80E/40E RouterConfiguration Guide - VPN.

2.8.3 Example for Configuring the Loopback InterfaceThis example shows how to configure the IP unnumbered function on loopback interfaces.

Networking RequirementsAfter a loopback interface is configured with IP address, it can work as the lending party in theIP unnumbered function. Loopback interface can use 32-bit mask.

Figure 2-2 Networking diagram of configuring the loopback interface

RouterA RouterBPOS1/0/0

10.1.1.2/30

POS1/0/0

Loopback110.1.1.1/32



47



1. Create the loopback interface and configure the IP address.2. Configure the POS interface to borrow the IP address of the loopback interface.

Data Preparation

To configure the loopback interface, you need the following data.

l Loopback interface numberl IP address of the loopback interfacel The number of the interface that borrows the IP address

Procedure

Step 1 Configure Router A.

# Create a loopback interface and allocate an IP address for it.

<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] interface loopback 1[RouterA-LoopBack1] ip address 10.1.1.1 32[RouterA-LoopBack1] quit

Step 2 Configure POS 1/0/0 to borrow the IP address of the created loopback1.[RouterA] interface pos 1/0/0[RouterA-Pos1/0/0] ip address unnumbered interface loopback 1[RouterB-Pos1/0/0] undo shutdown[RouterA-Pos1/0/0] quit

Step 3 Configure Router B<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] interface pos 1/0/0[RouterB-Pos1/0/0] ip address 10.1.1.2 30[RouterB-Pos1/0/0] undo shutdown[RouterB-Pos1/0/0] quit

Step 4 Check the configuration.

# Display the status of Pos 1/0/0.

<RouterA> display interface pos 1/0/0Pos1/0/0 current state : UPLin protocol current state : UPLast line protocol up time: 2007-11-03 15:42:33 UTC-08:00Description: Pos1/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 1500, The keepalive is 10(sec)Internet Address is unnumbered, using address of LoopBack1 (10.1.1.1/32)... ...

From the information in bold, you can view that POS 1/0/0 gets the IP address of loopback1.

If Router A can ping Router B, it indicates that Router A can normally communicate with RouterB.

----End



48

Configuration filesl Configuration files of Router A

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

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



49

3 Interface Board Intermixing Configuration

About This Chapter

When the interface boards and main board of different FIB route prefix capacities are pluggedin the same device, certain traffic is dropped because FIB entries of the interface boards andmain board are inconsistent. This chapter describes how to configure board intermixing toaddress the problem.

NOTE

The interface board intermixing feature is not supported on the NE80E/40E-X1&X2 series because theNE80E/40E-X1 and the NE80E/40E-X2 supports NPUs of one specification of FIB route prefix capacity.

3.1 Interface Board Intermixing Configuration OverviewThis section describes how to process FIB route prefixes received on interface boards.

3.2 Configuring the Public FIB PolicyThe public IPv4 FIB policy or public IPv6 FIB policy enables interface boards to receive FIBroute prefixes of the public network.

3.3 Configuring the VPN FIB PolicyThe VPN IPv4 FIB policy or VPN IPv6 FIB policy enables interface boards to receive FIB routeprefixes of a certain VPN.

3.4 Configuring the Policy of Discarding All the FIB EntriesThe policy of discarding all IPv4 FIB entries and IPv6 FIB entries disables interface boards fromreceiving any FIB route prefix.

3.5 Configuring Overload Suspension RecoveryWhen an interface board is in the overload suspension state, you need to perform overloadsuspension recovery. In this manner, the interface board returns to the normal state.

3.6 Configuring Overload Forwarding RecoveryWhen the interface board is in the overload forwarding state, you need to perform overloadforwarding recovery on the interface board to restore the interface board to the normal state.

3.7 Configuration ExamplesThis section provides the configuration examples of interface board intermixing to show howto configure FIB policies.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Interface Management 3 Interface Board Intermixing Configuration


50

3.1 Interface Board Intermixing Configuration OverviewThis section describes how to process FIB route prefixes received on interface boards.

3.1.1 Introduction to Interface Board IntermixingWhen inserting the main control board with large capacity of FIB route prefixes together withthe interface board with small capacity of FIB route prefixes into the same router, you can adoptthe FIB policy to efficiently solve FIB entry loss.

NOTE

FIB route prefix capacity varies with the hardware and the License file. For details, contact the Huaweitechnical personnel.

After receiving FIB entries, the interface board does as follows according to the FIB policy:

1. According to the FIB policy, the interface board classifies FIB entries and filters theunneeded FIB entries to reduce the FIB entries delivered to the FIB module of the interfaceboard.

2. The interface board judges whether the total number of received FIB route prefixes exceedsthe FIB route prefix capacity of the interface board.l If not, the interface board normally processes these received FIB entries.l If yes, the interface board takes the following measures:

– Overload suspensionWhen one FIB module is overloaded, the interface board automatically shuts downall the physical interfaces on this interface board. The FIB module of the interfaceboard changes to the overload suspension state.

– Overload forwardingWhen one FIB module is overloaded, this module changes to the overloadforwarding state. This does not affect the status of another module.

3.1.2 Features of Interface Board Intermixing in the NE80E/40EThe interface board in the overload suspension or overload forwarding state cannot automaticallyreturn to the normal state.

By default, the interface board is in the overload forwarding state after being overloaded.

After changing to the overload suspension or overload forwarding state, the interface boardcannot automatically return to the normal state.

After the active/standby switchover, the FIB module status and running status of the interfaceboard, which are stored on the main control board, keep unchanged.

3.2 Configuring the Public FIB PolicyThe public IPv4 FIB policy or public IPv6 FIB policy enables interface boards to receive FIBroute prefixes of the public network.



51

3.2.1 Establishing the Configuration TaskThis part describes the applicable environment, pre-configuration tasks, and required data forconfiguring a public FIB policy.

Applicable EnvironmentWhen the interface board on a router uses only the public forwarding entries of the main controlboard, you can use the interface board with less FIB route prefix capacity than the main controlboard. In such case, this interface board must be configured to receive only the public forwardingentries delivered by the main control board.

Through the FIB policy, you can insert the interface board of a different FIB route prefix capacitytogether with the main control board into the same router. FIB entries can be customized anddelivered as required. This ensures that the FIB entries delivered by the main control board canbe correctly processed.

Pre-configuration TasksBefore configuring the public FIB policy, complete the following tasks:

l Powering on and starting the router normally.l Connecting the interface and configuring the physical parameters of the interface.

Data PreparationTo configure the public FIB policy, you need the following data.

No. Data

1 Interface board number

3.2.2 Configuring the Public IPv4 FIB PolicyWhen interface boards need to receive public IPv4 FIB route prefixes, you can configure thepublic IPv4 FIB policy.

ContextWhen the interface board needs to receive the IPv4 FIB entries delivered by the main controlboard, do as follows on the router:


system-view


Step 2 Run:apply fib-policy public slot slot-id

The public IPv4 FIB policy is configured on the interface board.



52

NOTE

After the configuration, you need to refresh the IPv4 FIB policy to ensure that the newly configured policytakes effect.

Step 3 Run:refresh fib slot slot-id

The IPv4 FIB module is refreshed so that this public IPv4 FIB policy is applied to the interfaceboard.

----End

3.2.3 Configuring the Public IPv6 FIB PolicyWhen interface boards need to receive public IPv6 FIB route prefixes, you can configure thepublic IPv6 FIB policy.

Context

When the interface board needs to receive the IPv6 FIB entries delivered by the main controlboard, do as follows on the router:

Procedure



Step 2 Run:apply ipv6 fib-policy public slot slot-id

The public IPv6 FIB policy is configured on the interface board.

NOTE


Step 3 Run:refresh ipv6 fib slot slot-id

The IPv6 FIB module is refreshed so that this public IPv6 FIB policy is applied to the interfaceboard.

----End

3.2.4 Checking the ConfigurationAfter the public FIB policy is configured, you need to check whether the configuration is correct.In addition, you can view information about FIB route prefixes on interface boards.

PrerequisiteThe configurations of the configuring the public FIB policy function are complete.



53

Procedurel Run the display fib-policy slot slot-id command to check the FIB policy applied to the

IPv4 FIB module on the interface board.

l Run the display ipv6 fib-policy slot slot-id command to check the FIB policy applied tothe IPv6 FIB module on the interface board.

l Run the display fib [ slot-id ] statistics allcommand to check the FIB statistics of the IPv4FIB module on the interface board.

l Run the display ipv6 fib [ slot-id ] statistics all command to check the FIB statistics of theIPv6 FIB module on the interface board.

----End

Example

Run the display fib-policy command, and you can view the public IPv4 FIB policy applied tothe specified interface board.

[HUAWEI] display fib-policy slot 1 FIB-policy: public route

Run the display ipv6 fib-policy command, and you can view the public IPv6 FIB policy appliedto the specified interface board.

[HUAWEI] display ipv6 fib-policy slot 1 FIB-policy: public route

Run the display fib statistics all command, and you can view the FIB route prefix capacity andthe FIB policy statistics of the IPv4 FIB module on the specified interface board.

[HUAWEI] display fib 1 statistics allIPv4 FIB Route Prefix Capacity : 1000IPv4 FIB Total Route Prefix Count : 4, Entry Count : 4IPv4 FIB Public Route Prefix Count :4, Entry Count : 4IPv4 FIB Vpn-instance VPNB Route Prefix Count : 0, Entry Count : 0IPv4 FIB Vpn-instance VPNA Route Prefix Count : 0, Entry Count : 0

Run the display ipv6 fib statistics all command, and you can view the FIB route prefix capacityand the FIB policy statistics of the IPv6 FIB module on the specified interface board.

[HUAWEI] display ipv6 fib 1 statistics allIPv6 FIB Route Prefix Capacity : 1000IPv6 FIB Total Route Prefix Count :1,Entry Count : 1IPv6 FIB Public Route Prefix Count :1,Entry Count : 1

3.3 Configuring the VPN FIB PolicyThe VPN IPv4 FIB policy or VPN IPv6 FIB policy enables interface boards to receive FIB routeprefixes of a certain VPN.

3.3.1 Establishing the Configuration TaskThis part describes the applicable environment, pre-configuration tasks, and required data forconfiguring the VPN FIB policy.



54


When the interface board on a router uses only the VPN forwarding entries of the main controlboard, you can use the interface board with less FIB route prefix capacity than the main controlboard. Configure this interface board to receive only the VPN forwarding entries delivered bythe main control board.



Before configuring the VPN FIB policy, complete the following tasks:


l Connecting the interface and configuring the physical parameters of the interface

Data Preparation

To configure the VPN FIB policy, you need the following data.

No. Data


2 Type and name of the VPN instance

3.3.2 Configuring the VPN IPv4 FIB PolicyWhen interface boards need to receive VPN IPv4 FIB route prefixes, you can configure the VPNIPv4 FIB policy.

Context

When the interface board needs to receive the IPv4 VPN forwarding entries delivered by themain control board, do as follows on the router:

Procedure



Step 2 Run:apply fib-policy vpn-instance vpn-instance-name slot slot-id

The VPN IPv4 FIB policy is configured on the interface board.



55

NOTE



The IPv4 FIB policy is refreshed so that this VPN IPv4 FIB policy is applied to the interfaceboard.

----End

3.3.3 Configuring the VPN IPv6 FIB PolicyWhen interface boards need to receive VPN IPv6 FIB route prefixes, you can configure the VPNIPv6 FIB policy.

Context

When the interface board needs to receive the IPv6 VPN forwarding entries delivered by themain control board, do as follows on the router:

Procedure



Step 2 Run:apply ipv6 fib-policy vpn-instance vpn-instance-name slot slot-id

The VPN IPv6 FIB policy is configured on the interface board.

NOTE



The IPv6 FIB policy is refreshed so that this VPN IPv6 FIB policy is applied to the interfaceboard.

----End

3.3.4 Checking the ConfigurationAfter the VPN FIB policy is configured, you need to check whether the configuration is correct.In addition, you can view information about FIB route prefixes on interface boards.

PrerequisiteThe configurations of the configuring the VPN FIB policy function are complete.



56


IPv4 FIB module on the interface board.l Run the display ipv6 fib-policy slot slot-id command to check the FIB policy applied to

the IPv6 FIB module on the interface board.l Run the display fib [ slot-id ] statistics all command to check the FIB statistics of the IPv4

FIB module on the interface board.l Run the display ipv6 fib [ slot-id ] statistics all command to check the FIB statistics of the


----End

Example

Run the display fib-policy command, and you can view the VPN IPv4 FIB policy applied tothe specified interface board.

[HUAWEI] display fib-policy slot 2 FIB-policy: vpn route: VPNA

Run the display ipv6 fib-policy command, and you can view the VPN IPv6 FIB policy appliedto the specified interface board.

[HUAWEI] display ipv6 fib-policy slot 1 FIB-policy: vpn route: VPN6A

Run the display fib statistics all command, and you can view the IPv4 FIB route prefix capacityand the IPv4 FIB policy statistics of the specified interface board.

[HUAWEI] display fib 1 statistics allIPv4 FIB Route Prefix Capacity : 1000IPv4 FIB Total Route Prefix Count :7, Entry Count : 7IPv4 FIB Public Route Prefix Count : 4, Entry Count : 4IPv4 FIB Vpn-instance VPNB Route Prefix Count :3, Entry Count : 3IPv4 FIB Vpn-instance VPNA Route Prefix Count :0, Entry Count : 0

Run the display ipv6 fib statistics all command, and you can view the IPv6 FIB route prefixcapacity and the IPv6 FIB policy statistics of the specified interface board.

[HUAWEI] display ipv6 fib 2 statistics allIPv6 FIB Route Prefix Capacity : 1000IPv6 FIB Total Route Prefix Count :1, Entry Count : 1IPv6 FIB Public Route Prefix Count :1, Entry Count : 1IPv6 Vpn-instance VPN6A Route Prefix Count :0, Entry Count : 0

3.4 Configuring the Policy of Discarding All the FIB EntriesThe policy of discarding all IPv4 FIB entries and IPv6 FIB entries disables interface boards fromreceiving any FIB route prefix.

3.4.1 Establishing the Configuration TaskThis part describes the applicable environment, pre-configuration tasks, and required data forconfiguring the policy of discarding all IPv4 FIB entries and IPv6 FIB entries.



57


When the interface board on a router does not use the IPv4 or IPv6 forwarding entries of themain control board, you can configure this interface board not to receive any IPv4 or IPv6forwarding entries delivered by the main control board.



Before configuring the policy of discarding all the FIB entries, complete the following tasks:


l Connecting the interface and configuring the physical parameters of the interface

Data Preparation

To configure the policy of discarding all the FIB entries, you need the following data.

No. Data


2 Type of the forwarding entries to be discarded

3.4.2 Configuring the Policy of Discarding All the IPv4 FIB EntriesWhen an interface board does not need to receive any IPv4 FIB route prefix, you can configurethe policy of discarding all IPv4 FIB entries.

Context

When the interface board need not receive the IPv4 FIB entries delivered by the main controlboard, do as follows on the router:

Procedure



Step 2 Run:apply fib-policy no-route slot slot-id

The policy of discarding all the IPv4 forwarding entries is configured on the interface.



58

NOTE



The IPv4 FIB policy is refreshed so that this policy is applied to the interface board.

----End

3.4.3 Configuring the Policy of Discarding All the IPv6 FIB EntriesWhen an interface board does not need to receive any IPv6 FIB route prefix, you can configurethe policy of discarding all IPv6 FIB entries.

Context

When the interface board need not receive the IPv6 FIB entries delivered by the main controlboard, do as follows on the router:

Procedure



Step 2 Run:apply ipv6 fib-policy no-route slot slot-id

The policy of discarding all the IPv6 forwarding entries is configured on the interface.

NOTE



The IPv6 FIB policy is refreshed so that this policy is applied to the interface board.

----End

3.4.4 Checking the ConfigurationAfter the policy of discarding all IPv4 FIB entries and IPv6 FIB entries is configured, you needto check whether the configuration is correct. In addition, you can view information about FIBroute prefixes on the interface board.

PrerequisiteThe configurations of the configuring the policy of discarding all the FIB entries function arecomplete.



59


IPv4 FIB module on the interface board.l Run the display ipv6 fib-policy slot slot-id command to check the FIB policy applied to

the IPv6 FIB module on the interface board.l Run the display fib [ slot-id ] statistics all command to check the FIB statistics of the IPv4



----End

Example

Run the display fib-policy command, and you can view that the IPv4 FIB policy applied to thespecified interface board is no-route fib-policy.

[HUAWEI] display fib-policy slot 1 FIB-policy: Have configured no-route FIB policy.

Run the display ipv6 fib-policy command, and you can view that the IPv6 FIB policy appliedto the specified interface board is no-route fib-policy.

[HUAWEI] display ipv6 fib-policy slot 1 FIB-policy: Have configured no-route FIB policy.

Run the display fib statistics all command, and you can view the FIB route prefix capacity andthe FIB policy statistics of the IPv4 FIB module on the specified interface board.

[HUAWEI] display fib 1 statistics allIPv4 FIB Route Prefix Capacity : 1000IPv4 FIB Total Route Prefix Count :0, Entry Count : 0IPv4 FIB Public Route Prefix Count : 0, Entry Count : 0IPv4 FIB Vpn-instance VPNB Route Prefix Count :0, Entry Count : 0IPv4 FIB Vpn-instance VPNA Route Prefix Count :0, Entry Count : 0

Run the display ipv6 fib statistics all command, and you can view the FIB route prefix capacityand the FIB policy statistics of the IPv6 FIB module on the specified interface board.

[HUAWEI] display ipv6 fib 1 statistics allIPv6 FIB Route Prefix Capacity : 1000IPv6 FIB Total Route Prefix Count :0, Entry Count : 0IPv6 FIB Public Route Prefix Count :0, Entry Count : 0IPv6 FIB Vpn-instance VPN6A Route Prefix Count :0, Entry Count : 0

3.5 Configuring Overload Suspension RecoveryWhen an interface board is in the overload suspension state, you need to perform overloadsuspension recovery. In this manner, the interface board returns to the normal state.

3.5.1 Establishing the Configuration TaskThis part describes the applicable environment, pre-configuration tasks, and required data forconfiguring overload suspension recovery.



60


When the interface board is in the overload suspension state, you need to perform overloadsuspension recovery on the interface board to restore the interface board to the normal state.


Before configuring overload suspension recovery, complete the following task:

l Power on and start the router normally.

Data Preparation

To configure overload suspension recovery, you need the following data.

No. Data


3.5.2 Configuring Overload Suspension RecoveryThe interface board in the overload suspension state cannot automatically return to the normalstate. Instead, you need to perform overload suspension recovery to restore the interface boardto the normal state. Overload suspension recovery can take effect on the IPv4 FIB module andIPv6 FIB module at the same time.

Context

Do as follows on the router in the overload suspension state:

Procedure



Step 2 Run:recover fib overload suspend slot slot-id

Overload suspension recovery is configured on the specified interface board.

Overload suspension recovery can take effect on the IPv4 FIB module and IPv6 FIB module.

----End

Follow-up Procedure

After overload suspension recovery is configured, it is recommended to configure Refreshingthe FIB Policy on the IPv4 FIB and IPv6 FIB. In this manner, overload suspension recoverycan take effect on the IPv4 FIB module and IPv6 FIB module.



61

3.5.3 Refreshing the FIB PolicyAfter overload suspension recovery is configured, you must refresh the FIB policy; otherwise,overload suspension recovery cannot take effect.

ContextDo as follows on the router configured with overload suspension recovery:


system-view


NOTE

If the router supports only IPv4 or IPv6, you can select Step 2 or Step 3 accordingly to refresh thecorresponding module. If the router supports IPv4 and IPv6, it is recommended to perform Step 2 andStep 3 to refresh IPv4 FIB and IPv6 FIB.


The IPv4 FIB is refreshed so that overload suspension recovery is applied to the specifiedinterface board.


The IPv6 FIB is refreshed so that overload suspension recovery is applied to the specifiedinterface board.

----End

3.5.4 Checking the ConfigurationAfter overload suspension recovery is configured, you need to check whether the configurationis correct. In addition, you can view the FIB information on the interface board.

PrerequisiteThe configurations of the configuring overload suspension recovery function are complete.

Procedurel Run the display fib overload state slot slot-id command to check the overload status of

the IPv4 FIB module on the interface board.l Run the display ipv6 fib overload state slot slot-id command to check the overload status

of the IPv6 FIB module on the interface board.l Run the display fib [ slot-id ] statistics all command to check the FIB statistics of the IPv4



----End



62

ExampleRun the display fib statistics all command, and you can view the total number of the currentIPv4 FIB entries and the total number of the IPv4 FIB entries of each type on the main controlboard.

[HUAWEI] display fib statistics allIPv4 FIB Total Route Prefix Count : 1008, Entry Count : 1018IPv4 FIB Public Route Prefix Count : 1005, Entry Count : 1005IPv4 FIB Vpn-instance VPNB Route Prefix Count : 3, Entry Count : 13IPv4 FIB Vpn-instance VPNA Route Prefix Count : 0, Entry Count : 0

Run the display fib slot-id statistics all command, and you can view the IPv4 FIB route prefixcapacity of the specified interface board. When the interface board is in the overload suspensionstate, the number of the IPv4 FIB entries of each type received on the interface board is 0.

[HUAWEI] display fib 1 statistics allIPv4 FIB Route Prefix Capacity : 1000IPv4 FIB Total Route Prefix Count : 0, Entry Count : 0IPv4 FIB Public Route Prefix Count :0, Entry Count : 0IPv4 FIB Vpn-instance VPNB Route Prefix Count :0, Entry Count : 0IPv4 FIB Vpn-instance VPNA Route Prefix Count : 0, Entry Count : 0

Run the display fib overload state command, and you can view that the interface board is inthe Overload suspend state. After overload suspension recovery is configured on the interfaceboard, the interface board returns to the normal state.

[HUAWEI] display fib overload state slot 1 Overload mode: Overload suspend mode. Overload state: Overload suspend state.

3.6 Configuring Overload Forwarding RecoveryWhen the interface board is in the overload forwarding state, you need to perform overloadforwarding recovery on the interface board to restore the interface board to the normal state.

3.6.1 Establishing the Configuration TaskThis part describes the applicable environment, pre-configuration tasks, and required data forconfiguring overload forwarding recovery.

Applicable EnvironmentWhen the IPv4 FIB or IPv6 FIB module on the interface board is in the overload forwardingstate, you need to configure overload forwarding recovery on the IPv4 FIB or IPv6 FIB module.In this manner, the IPv4 FIB or IPv6 FIB module on the interface board returns to the normalstate.

Pre-configuration TasksBefore configuring overload forwarding recovery, power on and start the router normally.

Data PreparationTo configure overload forwarding recovery, you need the following data.



63

No. Data


2 Type of the forwarding entries in the overload forwarding state

3.6.2 Configuring IPv4 FIB Overload Forwarding RecoveryThe IPv4 FIB module in the overload forwarding state cannot automatically return to the normalstate. Instead, you need to run the command to restore the interface board to the normal state.After overload forwarding recovery is configured, you must refresh the FIB policy; otherwise,overload suspension recovery cannot take effect.

Context

Do as follows on the router with the IPv4 FIB module in the overload forwarding state:

Procedure



Step 2 Run:recover fib overload forward slot slot-id

Overload forwarding recovery is configured on the specified interface board.

NOTE

After the configuration, you need to refresh the IPv4 FIB module to ensure that the newly configured policytakes effect.


The IPv4 FIB is refreshed so that overload forwarding recovery is applied to the specifiedinterface board.

----End

3.6.3 Configuring IPv6 FIB Overload Forwarding RecoveryThe IPv6 FIB module in the overload forwarding state cannot automatically return to the normalstate. Instead, you need to run the command to restore the interface board to the normal state.After overload forwarding recovery is configured, you must refresh the FIB policy; otherwise,overload suspension recovery cannot take effect.

Context

Do as follows on the router with the IPv6 FIB module in the overload forwarding state:



64

Procedure



Step 2 Run:recover ipv6 fib overload forward slot slot-id

Overload forwarding recovery is configured on the specified interface board.

NOTE

After the configuration, you need to refresh the IPv6 FIB module to ensure that the newly configured policytakes effect.


The IPv6 FIB is refreshed so that overload forwarding recovery is applied to the specifiedinterface board.

----End

3.6.4 Checking the ConfigurationAfter overload forwarding recovery is configured, you need to check whether the configurationis correct. In addition, you can view the FIB information on the interface board.

PrerequisiteThe configurations of the configuring overload forwarding recovery function are complete.

Procedurel Run the display fib overload state slot slot-id command to check the overload status of

the IPv4 FIB module on the interface board.l Run the display ipv6 fib overload state slot slot-id command to check the overload status

of the IPv6 FIB module on the interface board.l Run the display fib [ slot-id ] statistics all command to check the FIB statistics of the IPv4



----End

ExampleRun the display fib statistics all command, and you can view the total number of the currentIPv4 FIB entries and the total number of the IPv4 FIB entries of each type on the main controlboard.

[HUAWEI] display fib statistics allIPv4 FIB Total Route Prefix Count : 1008, Entry Count : 1018IPv4 FIB Public Route Prefix Count : 1005, Entry Count : 1005IPv4 FIB Vpn-instance VPNB Route Prefix Count : 3, Entry Count : 13IPv4 FIB Vpn-instance VPNA Route Prefix Count : 0, Entry Count : 0



65

Run the display fib slot-id statistics all command, and you can view the IPv4 FIB route prefixcapacity of the specified interface board.

[HUAWEI] display fib 1 statistics allIPv4 FIB Route Prefix Capacity : 1000IPv4 FIB Total Route Prefix Count : 1000, Entry Count : 1000IPv4 FIB Public Route Prefix Count : 1000, Entry Count : 1000IPv4 FIB Vpn-instance VPNB Route Prefix Count : 0, Entry Count : 0IPv4 FIB Vpn-instance VPNA Route Prefix Count : 0, Entry Count : 0

Run the display fib overload state command, and you can view that the interface board is inthe Overload forward state. After overload recovery is configured on the interface board, theinterface board changes to the normal state.

[HUAWEI] display fib overload state slot 1 Overload mode: Overload forward mode. Overload state: Overload forward state.

3.7 Configuration ExamplesThis section provides the configuration examples of interface board intermixing to show howto configure FIB policies.

3.7.1 Example for Configuring the VPN IPv4 FIB PolicyThis example shows how to configure devices on the same VPN to intercommunicate and howto isolate devices in different VPNs from intercommunicating.

Networking RequirementsFigure 3-1 shows the network structure.

On PE1, the FIB route prefix capacity of interface board 1 exceeds that of interface board 2 orinterface board 3.

On PE2, the FIB route prefix capacity of interface board 1 exceeds that of interface board 2 orinterface board 3.

VPN A connected to PE1 is required to communicate with VPN A connected to PE2, and VPNB connected to PE1 is also required to communicate with VPN B connected to PE2. In addition,FIB entry loss cannot occur on interface board 2 or interface board 3 on PE1 or PE2.



66

Figure 3-1 Networking diagram of configuring the VPN IPv4 FIB policy

VPNAVPNAVPNA

VPNB

CE1

CE2

CE3

CE4

PPE1 PE2

POS1/0/010.1.1.1/24

POS2/0/010.1.1.2/24

POS3/0/020.1.1.2/24

POS1/0/020.1.1.1/24

POS1/0/030.1.1.2/24

POS1/0/030.1.1.1/24

POS1/0/140.1.1.1/24

POS1/0/040.1.1.2/24

POS1/0/050.1.1.2/24

POS2/0/050.1.1.1/24

POS3/0/060.1.1.1/24

POS1/0/060.1.1.2/24

VPNA

VPNB

Configuration RoadmapTake PE1 as an example for analysis because the networking of PE1 is similar to that of PE2.


1. Configure VPN instances VPN A and VPN B on PE1.2. Configure a policy on interface board 2 to allow only VPN A to pass.3. Configure a policy on interface board 3 to allow only VPN B to pass.

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

l Slot number of each routerl VPN instance name

Procedure

Step 1 Configure the VPN instance.

Configure all the routers shown in Figure 3-1. CE1 is required to communicate with CE3, andCE2 is required to communicate with CE4.

For details, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.



67

Step 2 Take interface board 2 on PE1 as an example to view the public forwarding entries and VPNforwarding entries on this interface board.

# View the number of the public forwarding entries on interface board 2.

[PE1] display fib 2 FIB Table: Total number of Routes : 9Destination/Mask Nexthop Flag TimeStamp Interface TunnelID127.0.0.1/32 127.0.0.1 HU t[55] InLoop0 0x0127.0.0.0/8 127.0.0.1 U t[55] InLoop0 0x01.1.1.1/32 127.0.0.1 HU t[55] InLoop0 0x030.1.1.1/32 127.0.0.1 HU t[2521] InLoop0 0x030.1.1.0/24 30.1.1.1 U t[2521] [No Intf] 0x030.1.1.2/32 30.1.1.2 HU t[2521] [No Intf] 0x040.1.1.0/24 30.1.1.2 DGU t[3554] [No Intf] 0x10020012.1.1.1/32 30.1.1.2 DGHU t[3554] [No Intf] 0x10020003.1.1.1/32 30.1.1.2 DGHU t[44469] [No Intf] 0x1002003

# View the number of the VPN forwarding entries of VPN A on interface board 2.

[PE1] display fib 2 vpn-instance VPNA FIB Table: Total number of Routes : 5Destination/Mask Nexthop Flag TimeStamp Interface TunnelID10.1.1.2/32 127.0.0.1 HU t[47861] InLoop0 0x010.1.1.0/24 10.1.1.2 U t[47861] POS2/0/0 0x010.1.1.1/32 10.1.1.1 HU t[47861] POS2/0/0 0x050.1.1.0/24 30.1.1.2 DGU t[48014] [No Intf] 0x100200550.1.1.2/32 30.1.1.2 DGHU t[48014] [No Intf] 0x1002005

# View the number of the VPN forwarding entries of VPN B on interface board 2.

[PE1] display fib 2 vpn-instance VPNB FIB Table: Total number of Routes : 5Destination/Mask Nexthop Flag TimeStamp Interface TunnelID20.1.1.2/32 127.0.0.1 HU t[51766] InLoop0 0x020.1.1.0/24 20.1.1.2 U t[51766] [No Intf] 0x020.1.1.1/32 20.1.1.1 HU t[51766] [No Intf] 0x060.1.1.0/24 30.1.1.2 DGU t[51766] [No Intf] 0x100200560.1.1.2/32 30.1.1.2 DGHU t[51766] [No Intf] 0x1002005

Step 3 Configure the FIB policy.[PE1] apply fib-policy vpn-instance VPNA slot 2[PE1] apply fib-policy vpn-instance VPNB slot 3

The configuration of PE2 is similar to that of PE1.

Step 4 Refresh the FIB policy[PE1] refresh fib slot 2[PE1] refresh fib slot 3


Step 5 Verify the configuration.

Take interface board 2 on PE1 as an example to view the public forwarding entries and VPNforwarding entries on this interface board.

# View the public forwarding entries on interface board 2. No public forwarding entries existon interface board 2.

[PE1] display fib 2

# View the VPN forwarding entries of VPN A on interface board 2. The VPN forwarding entriesremain unchanged after the policy is configured.



68

[PE1] display fib 2 vpn-instance VPNA FIB Table: Total number of Routes : 5Destination/Mask Nexthop Flag TimeStamp Interface TunnelID10.1.1.2/32 127.0.0.1 HU t[47861] InLoop0 0x010.1.1.0/24 10.1.1.2 U t[47861] POS2/0/0 0x010.1.1.1/32 10.1.1.1 HU t[47861] POS2/0/0 0x050.1.1.0/24 30.1.1.2 DGU t[48014] [No Intf] 0x100200550.1.1.2/32 30.1.1.2 DGHU t[48014] [No Intf] 0x1002005

# View the VPN forwarding entries of VPN B on interface board 2 as follows. After the policyis configured, the forwarding entries of VPN B cannot be generated on interface board 2.

[PE1] display fib 2 vpn-instance VPNB

# CE1 can ping through CE3 because interface board 2 needs only the forwarding entries ofVPN A.

<CE1> ping 50.1.1.2 PING 50.1.1.2: 56 data bytes, press CTRL_C to break Reply from 50.1.1.2: bytes=56 Sequence=1 ttl=253 time=125 ms Reply from 50.1.1.2: bytes=56 Sequence=2 ttl=253 time=94 ms Reply from 50.1.1.2: bytes=56 Sequence=3 ttl=253 time=125 ms Reply from 50.1.1.2: bytes=56 Sequence=4 ttl=253 time=94 ms Reply from 50.1.1.2: bytes=56 Sequence=5 ttl=253 time=125 ms --- 50.1.1.2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 94/112/125 ms

----End

Configuration Filesl Configuration file of CE1

# sysname CE1#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 10.1.1.1 255.255.255.0#bgp 65410 peer 10.1.1.2 as-number 100 # ipv4-family unicast undo synchronization import-route direct peer 10.1.1.2 enable#Return

l Configuration file of CE2# sysname CE2#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 20.1.1.1 255.255.255.0#bgp 65420 peer 20.1.1.2 as-number 100 # ipv4-family unicast undo synchronization



69

import-route direct peer 20.1.1.2 enable#return

l Configuration file of PE1# sysname PE1#ip vpn-instance VPNB route-distinguisher 2:2 vpn-target 2:2 export-extcommunity vpn-target 2:2 import-extcommunity#ip vpn-instance VPNA route-distinguisher 1:1 vpn-target 1:1 export-extcommunity vpn-target 1:1 import-extcommunity# mpls lsr-id 1.1.1.1 mpls#mpls ldp#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 30.1.1.1 255.255.255.0 mpls mpls ldp#interface Pos2/0/0 link-protocol ppp undo shutdown ip binding vpn-instance VPNA ip address 10.1.1.2 255.255.255.0#interface Pos3/0/0 link-protocol ppp undo shutdown ip binding vpn-instance VPNB ip address 20.1.1.2 255.255.255.0#interface LoopBack1 ip address 1.1.1.1 255.255.255.255#bgp 100 peer 3.1.1.1 as-number 100 peer 3.1.1.1 connect-interface LoopBack1 # ipv4-family unicast undo synchronization peer 3.1.1.1 enable # ipv4-family vpnv4 policy vpn-target peer 3.1.1.1 enable # ipv4-family vpn-instance VPNB import-route direct peer 20.1.1.1 as-number 65420 # ipv4-family vpn-instance VPNA import-route direct peer 10.1.1.1 as-number 65410#ospf 1 area 0.0.0.0 network 1.1.1.1 0.0.0.0 network 30.1.1.0 0.0.0.255



70

# apply fib-policy vpn-instance VPNA slot 2 apply fib-policy vpn-instance VPNB slot 3#return

l Configuration file of P# sysname P# mpls lsr-id 2.1.1.1 mpls#mpls ldp#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 30.1.1.2 255.255.255.0 mpls mpls ldp#interface Pos1/0/1 link-protocol ppp undo shutdown ip address 40.1.1.1 255.255.255.0 mpls mpls ldp#interface LoopBack1 ip address 2.1.1.1 255.255.255.255#ospf 1 area 0.0.0.0 network 30.1.1.0 0.0.0.255 network 40.1.1.0 0.0.0.255 network 2.1.1.1 0.0.0.0#return

l Configuration file of PE2# sysname PE2#ip vpn-instance VPNA route-distinguisher 3:3 vpn-target 1:1 export-extcommunity vpn-target 1:1 import-extcommunity#ip vpn-instance VPNB route-distinguisher 4:4 vpn-target 2:2 export-extcommunity vpn-target 2:2 import-extcommunity# mpls lsr-id 3.1.1.1 mpls#mpls ldp#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 40.1.1.2 255.255.255.0 mpls mpls ldp#interface Pos2/0/0 link-protocol ppp undo shutdown ip binding vpn-instance VPNA



71

ip address 50.1.1.1 255.255.255.0#interface Pos3/0/0 link-protocol ppp undo shutdown ip binding vpn-instance VPNB ip address 60.1.1.1 255.255.255.0#interface LoopBack1 ip address 3.1.1.1 255.255.255.255#bgp 100 peer 1.1.1.1 as-number 100 peer 1.1.1.1 connect-interface LoopBack1 # ipv4-family unicast undo synchronization peer 1.1.1.1 enable # ipv4-family vpnv4 policy vpn-target peer 1.1.1.1 enable # ipv4-family vpn-instance VPNA import-route direct peer 50.1.1.2 as-number 65430 # ipv4-family vpn-instance VPNB import-route direct peer 60.1.1.2 as-number 65440#ospf 1 area 0.0.0.0 network 40.1.1.0 0.0.0.255 network 3.1.1.1 0.0.0.0# apply fib-policy vpn-instance VPNA slot 2 apply fib-policy vpn-instance VPNB slot 3#return

l Configuration file of CE3# sysname CE3#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 50.1.1.2 255.255.255.0#bgp 65430 peer 50.1.1.1 as-number 100 # ipv4-family unicast undo synchronization import-route direct peer 50.1.1.1 enable#return

l Configuration file of CE4# sysname CE4#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 60.1.1.2 255.255.255.0#bgp 65440



72

peer 60.1.1.1 as-number 100 # ipv4-family unicast undo synchronization import-route direct peer 60.1.1.1 enable#return

3.7.2 Example for Configuring Overload Suspension RecoveryThis example shows how to restore the interface board in the overload suspension state to thenormal state.


Figure 3-2 Networking diagram of configuring overload suspension recovery

VPNAVPNAVPNA

VPNB

CE1

CE2

CE3

CE4

PPE1 PE2

POS1/0/010.1.1.1/24

POS2/0/010.1.1.2/24

POS3/0/020.1.1.2/24

POS1/0/020.1.1.1/24

POS1/0/030.1.1.2/24

POS1/0/030.1.1.1/24

POS1/0/140.1.1.1/24

POS1/0/040.1.1.2/24

POS1/0/050.1.1.2/24

POS2/0/050.1.1.1/24

POS3/0/060.1.1.1/24

POS1/0/060.1.1.2/24

VPNA

VPNB

The FIB route prefix capacity of either interface board 2 or interface board 3 on PE1 or PE2 issmaller than the sum of the public forwarding entries and VPN forwarding entries. Before a FIBpolicy is configured, the interface board is overloaded immediately after running. Then, whenone FIB module is overloaded, this interface board is in the overload suspension state.

After the interface board is in the overload suspension state, configure related policies andperform overload suspension recovery on the interface board.

Configuration RoadmapTake PE1 as an example for analysis because the networking of PE1 is similar to that of PE2.




73

1. Configure a policy on interface board 2 to allow only VPN A to pass.2. Configure a policy on interface board 3 to allow only VPN B to pass.3. Configure overload suspension recovery on interface board 2.4. Configure overload suspension recovery on interface board 3.

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

l Slot number of each routerl VPN instance name

Procedure


Configure all the routers shown in Figure 3-2. VPN A connected to PE1 is required tocommunicate with VPN A connected to PE2, and VPN B connected to PE1 is also required tocommunicate with VPN B connected to PE2.


Step 2 After the current interface board begins to work, interface board 2 and interface board 3 rapidlychange to the overload suspension state.[PE1] display fib overload state slot 2 Overload mode: Overload suspend mode. Overload state: Overload suspend state.[PE1] display fib overload state slot 3 Overload mode: Overload suspend mode. Overload state: Overload suspend state.

Step 3 On PE1, view the FIB entries on the interface board.

# View the number of FIB entries on the main control board.

[PE1] display fib statistics allIPv4 FIB Total Route Prefix Count : 1003, Entry Count : 1003IPv4 FIB Public Route Prefix Count : 9, Entry Count : 9IPv4 FIB Vpn-instance VPNB Route Prefix Count : 494, Entry Count : 494IPv4 FIB Vpn-instance VPNA Route Prefix Count : 500, Entry Count : 500

# View the FIB route prefix capacity on interface board 2.

[PE1] display fib 2 statistics allIPv4 FIB Route Prefix Capacity : 1000IPv4 FIB Total Route Prefix Count : 0, Entry Count : 0IPv4 FIB Public Route Prefix Count : 0, Entry Count : 0IPv4 FIB Vpn-instance VPNB Route Prefix Count : 0, Entry Count : 0IPv4 FIB Vpn-instance VPNA Route Prefix Count : 0, Entry Count : 0

When the interface board is in the overload suspension state, the FIB entries on the interfaceboard are cleared. Thus, the number of the forwarding entries of each type on the interface boardis 0.

# View the FIB route prefix capacity on interface board 3.

[PE1] display fib 3 statistics all



74

IPv4 FIB Route Prefix Capacity : 1000IPv4 FIB Total Route Prefix Count : 0, Entry Count : 0IPv4 FIB Public Route Prefix Count : 0, Entry Count : 0IPv4 FIB Vpn-instance VPNB Route Prefix Count : 0, Entry Count : 0IPv4 FIB Vpn-instance VPNA Route Prefix Count : 0, Entry Count : 0

Through the preceding display, you can know the following:

l The interface board changes to the overload suspension state because the number offorwarding entries exceeds the FIB route prefix capacity of the interface board.

l The number of forwarding entries on VPN A or VPN B is smaller than the FIB route prefixcapacity of the interface board.

Thus, configure the following FIB policies on the interface board.

Step 4 Configure the FIB policy on the interface board and refresh the FIB policy.[PE1] apply fib-policy vpn-instance VPNA slot 2[PE1] apply fib-policy vpn-instance VPNB slot 3[PE1] refresh fib slot 2[PE1] refresh fib slot 3

NOTE

When the interface board is in the overload suspension state, the system prompts users to configure overloadsuspension recovery, and then run the refresh command.


Step 5 Configure overload suspension recovery on the interface board and refresh the interface board.[PE1] recover fib overload suspend slot 2[PE1] recover fib overload suspend slot 3[PE1] refresh fib slot 2[PE1] refresh fib slot 3



On PE2, view the status of the current interface board and that the interface board returns to theNormal state.

[PE2] display fib overload state slot 2 Overload mode: Overload suspend mode. Overload state: Normal state.

On VPN A, CE1 can ping through CE3.


----End



75


# sysname CE1#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 10.1.1.1 255.255.255.0#bgp 65410 peer 10.1.1.2 as-number 100 # ipv4-family unicast undo synchronization import-route direct peer 10.1.1.2 enable#Return


l Configuration file of PE1# sysname PE1#ip vpn-instance VPNB route-distinguisher 2:2 vpn-target 2:2 export-extcommunity vpn-target 2:2 import-extcommunity#ip vpn-instance VPNA route-distinguisher 1:1 vpn-target 1:1 export-extcommunity vpn-target 1:1 import-extcommunity# mpls lsr-id 1.1.1.1 mpls#mpls ldp#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 30.1.1.1 255.255.255.0 mpls mpls ldp#interface Pos2/0/0 link-protocol ppp undo shutdown



76

ip binding vpn-instance VPNA ip address 10.1.1.2 255.255.255.0#interface Pos3/0/0 link-protocol ppp undo shutdown ip binding vpn-instance VPNB ip address 20.1.1.2 255.255.255.0#interface LoopBack1 ip address 1.1.1.1 255.255.255.255#bgp 100 peer 3.1.1.1 as-number 100 peer 3.1.1.1 connect-interface LoopBack1 # ipv4-family unicast undo synchronization peer 3.1.1.1 enable # ipv4-family vpnv4 policy vpn-target peer 3.1.1.1 enable # ipv4-family vpn-instance VPNB import-route direct peer 20.1.1.1 as-number 65420 # ipv4-family vpn-instance VPNA import-route direct peer 10.1.1.1 as-number 65410#ospf 1 area 0.0.0.0 network 1.1.1.1 0.0.0.0 network 30.1.1.0 0.0.0.255# apply fib-policy vpn-instance VPNA slot 2 apply fib-policy vpn-instance VPNB slot 3#return

l Configuration file of P# sysname P# mpls lsr-id 2.1.1.1 mpls#mpls ldp#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 30.1.1.2 255.255.255.0 mpls mpls ldp#interface Pos1/0/1 link-protocol ppp undo shutdown ip address 40.1.1.1 255.255.255.0 mpls mpls ldp#interface LoopBack1 ip address 2.1.1.1 255.255.255.255#ospf 1 area 0.0.0.0



77

network 30.1.1.0 0.0.0.255 network 40.1.1.0 0.0.0.255 network 2.1.1.1 0.0.0.0#return

l Configuration file of PE2# sysname PE2#ip vpn-instance VPNA route-distinguisher 3:3 vpn-target 1:1 export-extcommunity vpn-target 1:1 import-extcommunity#ip vpn-instance VPNB route-distinguisher 4:4 vpn-target 2:2 export-extcommunity vpn-target 2:2 import-extcommunity# mpls lsr-id 3.1.1.1 mpls#mpls ldp#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 40.1.1.2 255.255.255.0 mpls mpls ldp#interface Pos2/0/0 link-protocol ppp undo shutdown ip binding vpn-instance VPNA ip address 50.1.1.1 255.255.255.0#interface Pos3/0/0 link-protocol ppp undo shutdown ip binding vpn-instance VPNB ip address 60.1.1.1 255.255.255.0#interface LoopBack1 ip address 3.1.1.1 255.255.255.255#bgp 100 peer 1.1.1.1 as-number 100 peer 1.1.1.1 connect-interface LoopBack1 # ipv4-family unicast undo synchronization peer 1.1.1.1 enable # ipv4-family vpnv4 policy vpn-target peer 1.1.1.1 enable # ipv4-family vpn-instance VPNA import-route direct peer 50.1.1.2 as-number 65430 # ipv4-family vpn-instance VPNB import-route direct peer 60.1.1.2 as-number 65440#ospf 1 area 0.0.0.0 network 40.1.1.0 0.0.0.255



78

network 3.1.1.1 0.0.0.0# apply fib-policy vpn-instance VPNA slot 2 apply fib-policy vpn-instance VPNB slot 3#return



3.7.3 Example for Configuring Overload Forwarding RecoveryThis example shows how to restore the interface board in the overload forwarding state to thenormal state.




79

Figure 3-3 Networking diagram of configuring overload forwarding recovery

VPNAVPNAVPNA

VPNB

CE1

CE2

CE3

CE4

PPE1 PE2

POS1/0/010.1.1.1/24

POS2/0/010.1.1.2/24

POS3/0/020.1.1.2/24

POS1/0/020.1.1.1/24

POS1/0/030.1.1.2/24

POS1/0/030.1.1.1/24

POS1/0/140.1.1.1/24

POS1/0/040.1.1.2/24

POS1/0/050.1.1.2/24

POS2/0/050.1.1.1/24

POS3/0/060.1.1.1/24

POS1/0/060.1.1.2/24

VPNA

VPNB

The FIB route prefix capacity of either interface board 2 or interface board 3 on PE1 or PE2 issmaller than the sum of the public forwarding entries and VPN forwarding entries. Before a FIBpolicy is configured, the interface board is overloaded immediately after running.Then, whenone FIB module is overloaded, this interface board is in the overload forwarding state.

After the interface board is in the overload forwarding state, configure related policies andperform overload forwarding recovery on the interface board.


Take PE1 as an example for analysis because the networking of PE1 is similar to that of PE2.


1. Configure a policy on interface board 2 to allow only VPN A to pass.

2. Configure a policy on interface board 3 to allow only VPN B to pass.

3. Configure overload forwarding recovery on interface board 2.

4. Configure overload forwarding recovery on interface board 3.

Data Preparation

To complete the configuration, you need the following data:

l Slot number of each router

l VPN instance name



80

Procedure


Configure all the routers shown in Figure 3-3. VPN A connected to PE1 is required tocommunicate with VPN A connected to PE2, and VPN B connected to PE1 is also required tocommunicate with VPN B connected to PE2.


Step 2 After the current interface board begins to work, interface board 2 and interface board 3 rapidlychange to the overload forwarding state.[PE1] display fib overload state slot 2 Overload mode: Overload forward mode. Overload state: Overload forward state.[PE1] display fib overload state slot 3 Overload mode: Overload forward mode. Overload state: Overload forward state.

Step 3 On PE1, view the FIB entries on the interface board.

# View the number of FIB entries on the main control board.

[PE1] display fib statistics allIPv4 FIB Total Route Prefix Count : 1008, Entry Count : 1008IPv4 FIB Public Route Prefix Count : 7, Entry Count : 7IPv4 FIB Vpn-instance VPNA Route Prefix Count : 503, Entry Count : 503IPv4 FIB Vpn-instance VPNB Route Prefix Count : 498, Entry Count : 498

# View the FIB route prefix capacity and the number of the FIB entries of each type on interfaceboard 2.

[PE1] display fib 2 statistics allIPv4 FIB Route Prefix Capacity : 1000IPv4 FIB Total Route Prefix Count : 1000, Entry Count : 1000IPv4 FIB Public Route Prefix Count : 7, Entry Count : 7IPv4 FIB Vpn-instance VPNA Route Prefix Count : 503, Entry Count : 503IPv4 FIB Vpn-instance VPNB Route Prefix Count : 490, Entry Count : 490

When the interface board is in the overload forwarding state, the number of FIB entries equalsthe FIB route prefix capacity on the interface board.

# View the FIB route prefix capacity and the number of the FIB entries of each type on interfaceboard 3.

[PE1] display fib 3 statistics allIPv4 FIB Route Prefix Capacity : 1000IPv4 FIB Total Route Prefix Count : 1000, Entry Count : 1000IPv4 FIB Public Route Prefix Count : 7, Entry Count : 7IPv4 FIB Vpn-instance VPNA Route Prefix Count : 503, Entry Count : 503IPv4 FIB Vpn-instance VPNB Route Prefix Count : 490, Entry Count : 490

Through the preceding display, you can know the following:

l The interface board changes to the overload forwarding state because the number offorwarding entries exceeds the FIB route prefix capacity of the interface board.

l The number of forwarding entries on VPN A or VPN B is smaller than the FIB route prefixcapacity of the interface board.

Thus, configure the following FIB policies on the interface board.



81

Step 4 Configure the FIB policy on the interface board and refresh the FIB policy.[PE1] apply fib-policy vpn-instance VPNA slot 2[PE1] apply fib-policy vpn-instance VPNB slot 3[PE1] refresh fib slot 2[PE1] refresh fib slot 3

NOTE

When the interface board is in the overload forwarding state, the system prompts users to configure overloadforwarding recovery, and then run the refresh command.


Step 5 Configure overload forwarding recovery on the interface board and refresh the interface board.[PE1] recover fib overload forward slot 2[PE1] recover fib overload forward slot 3[PE1] refresh fib slot 2[PE1] refresh fib slot 3



On PE2, view the status of the current interface board and that the interface board returns to theNormal state.

[PE2] display fib overload state slot 2 Overload mode: Overload forward mode. Overload state: Normal state.

On VPN A, CE1can ping through CE3.


----End


# sysname CE1#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 10.1.1.1 255.255.255.0#bgp 65410 peer 10.1.1.2 as-number 100 # ipv4-family unicast undo synchronization import-route direct peer 10.1.1.2 enable



82

#Return


l Configuration file of PE1# sysname PE1#ip vpn-instance VPNB route-distinguisher 2:2 vpn-target 2:2 export-extcommunity vpn-target 2:2 import-extcommunity#ip vpn-instance VPNA route-distinguisher 1:1 vpn-target 1:1 export-extcommunity vpn-target 1:1 import-extcommunity# mpls lsr-id 1.1.1.1 mpls#mpls ldp#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 30.1.1.1 255.255.255.0 mpls mpls ldp#interface Pos2/0/0 link-protocol ppp undo shutdown ip binding vpn-instance VPNA ip address 10.1.1.2 255.255.255.0#interface Pos3/0/0 link-protocol ppp undo shutdown ip binding vpn-instance VPNB ip address 20.1.1.2 255.255.255.0#interface LoopBack1 ip address 1.1.1.1 255.255.255.255#bgp 100 peer 3.1.1.1 as-number 100 peer 3.1.1.1 connect-interface LoopBack1 # ipv4-family unicast undo synchronization peer 3.1.1.1 enable



83

# ipv4-family vpnv4 policy vpn-target peer 3.1.1.1 enable # ipv4-family vpn-instance VPNB import-route direct peer 20.1.1.1 as-number 65420 # ipv4-family vpn-instance VPNA import-route direct peer 10.1.1.1 as-number 65410#ospf 1 area 0.0.0.0 network 1.1.1.1 0.0.0.0 network 30.1.1.0 0.0.0.255# apply fib-policy vpn-instance VPNA slot 2 apply fib-policy vpn-instance VPNB slot 3#return

l Configuration file of P# sysname P# mpls lsr-id 2.1.1.1 mpls#mpls ldp#interface Pos1/0/0 link-protocol ppp ip address 30.1.1.2 255.255.255.0 mpls mpls ldp#interface Pos1/0/1 link-protocol ppp undo shutdown ip address 40.1.1.1 255.255.255.0 mpls mpls ldp#interface LoopBack1 ip address 2.1.1.1 255.255.255.255#ospf 1 area 0.0.0.0 network 30.1.1.0 0.0.0.255 network 40.1.1.0 0.0.0.255 network 2.1.1.1 0.0.0.0#return

l Configuration file of PE2# sysname PE2#ip vpn-instance VPNA route-distinguisher 3:3 vpn-target 1:1 export-extcommunity vpn-target 1:1 import-extcommunity#ip vpn-instance VPNB route-distinguisher 4:4 vpn-target 2:2 export-extcommunity vpn-target 2:2 import-extcommunity#



84

mpls lsr-id 3.1.1.1 mpls#mpls ldp#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 40.1.1.2 255.255.255.0 mpls mpls ldp#interface Pos2/0/0 link-protocol ppp undo shutdown ip binding vpn-instance VPNA ip address 50.1.1.1 255.255.255.0#interface Pos3/0/0 link-protocol ppp undo shutdown ip binding vpn-instance VPNB ip address 60.1.1.1 255.255.255.0#interface LoopBack1 ip address 3.1.1.1 255.255.255.255#bgp 100 peer 1.1.1.1 as-number 100 peer 1.1.1.1 connect-interface LoopBack1 # ipv4-family unicast undo synchronization peer 1.1.1.1 enable # ipv4-family vpnv4 policy vpn-target peer 1.1.1.1 enable # ipv4-family vpn-instance VPNA import-route direct peer 50.1.1.2 as-number 65430 # ipv4-family vpn-instance VPNB import-route direct peer 60.1.1.2 as-number 65440#ospf 1 area 0.0.0.0 network 40.1.1.0 0.0.0.255 network 3.1.1.1 0.0.0.0# apply fib-policy vpn-instance VPNA slot 2 apply fib-policy vpn-instance VPNB slot 3#return

l Configuration file of CE3# sysname CE3#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 50.1.1.2 255.255.255.0#bgp 65430 peer 50.1.1.1 as-number 100 # ipv4-family unicast



85

undo synchronization import-route direct peer 50.1.1.1 enable#return




86

4 Fast Feeling Configuration

About This Chapter

Fast feeling is used to notify the application of physical faults in real time.

4.1 Fast Feeling Configuration OverviewThis section describes the characteristics and applicable environment of fast feeling.

4.2 Configuring Fast FeelingThis section describes the applicable environment and configuration procedure of fast feeling.

4.3 Maintaining Fast FeelingWhen fast feeling functions abnormally, you can use maintenance tools to locate the fault.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Interface Management 4 Fast Feeling Configuration


87

4.1 Fast Feeling Configuration OverviewThis section describes the characteristics and applicable environment of fast feeling.

4.1.1 Introduction to Fast FeelingAfter fast feeling is enabled, physical faults are rapidly reported to applications, and thus thesystem can rapidly respond to the faults.

Traditionally, the periodic monitoring mechanism is adopted to detect physical componentfaults. This solution, however, cannot meet the requirement for sensitive applications sometimes.

Fast feeling is used to rapidly notify the physical fault to the application in real time.

After the fast feeling function is enabled on an interface, when the shutdown command is runin the interface view, the system can quickly inform the routing module of the event and theninform the device management module after 5 seconds. This ensures that traffic is notinterrupted.

4.1.2 Fast Feeling Features Supported by the NE80E/40EFast feeling is used to rapidly report physical faults.

In the NE80E/40E, fast feeling channels are established to rapidly notify the physical fault tothe application for rapid response.

After the fast feeling function is enabled on an interface, when the shutdown command is runin the interface view, the system can quickly inform the routing module of the event and theninform the device management module after 5 seconds. This ensures that traffic is notinterrupted.

4.2 Configuring Fast FeelingThis section describes the applicable environment and configuration procedure of fast feeling.

4.2.1 Establishing the Configuration TaskFast feeling is applicable to the scenario where the upper layer applications need to sense physicalfaults as soon as the faults occur.


The flapping of routing protocols, MPLS and other protocols caused by the frequent change ofthe interface status may influence the stability of the whole network. To avoid this, you canconfigure the flapping control feature.

Pre-Configuration Tasks

None.



88

Data PreparationTo configure the fast feeling, you need the following data.

No. Data

1 Number of the interface on the router

4.2.2 Enabling Fast FeelingFast feeling can be enabled only in the interface view.

Procedure




The specified interface view is displayed.

Step 3 Run:fastfeeling

The fast feeling is enabled.

----End

4.2.3 Checking the ConfigurationAfter fast feeling is configured, you can view information about fast feeling on the interface tocheck whether the configuration is correct.

PrerequisiteThe configurations of configuring fast feeling function are complete.

Procedure

Step 1 Run the display fastfeeling [ interface interface-type interface-number ] command to checkthe configuration and running status of the fast feeling feature of the interface.

----End

ExampleRun the display fastfeeling command. If you can view the fast feeling feature configured onthe interface, it means that the configuration succeeds. For example:

<HUAWEI> display fastfeeling interface GigabitEthernet 1/2/0 interface GigabitEthernet1/2/0: fastfeeling status : feeling, feeling



89

route interface status: up ISIS interface status: down

4.3 Maintaining Fast FeelingWhen fast feeling functions abnormally, you can use maintenance tools to locate the fault.

4.3.1 Monitoring the Running of Fast FeelingIn routine maintenance, you can monitor and know the running status of fast feeling.

ContextIn routine maintenance, you can run the following command in any view to check the operationof fast feeling.

Procedure

Step 1 Run the display fastfeeling [ interface interface-type interface-number ] command in any viewto check the current running status and statistics of fast feeling on the interface.

----End



90

5 Flapping Control Configuration

About This Chapter

Configuring interface flapping control can minimize the impact of frequent interface statuschanges on the stability of the device and the network.

5.1 Flapping Control Configuration OverviewInterface flapping control is used to effectively minimize the impact of frequently-changedinterface status on the stability of the network.

5.2 Configuring the Interface Flapping ControlThis section describes the applicable environment and configuration procedure of interfaceflapping control.

5.3 Maintaining the Flapping Control FeatureWhen a fault of interface flapping control occurs, you can use maintenance tools to locate thefault.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Interface Management 5 Flapping Control Configuration


91

5.1 Flapping Control Configuration OverviewInterface flapping control is used to effectively minimize the impact of frequently-changedinterface status on the stability of the network.

5.1.1 Introduction to the Interface Flapping ControlAfter interface flapping control is configured, interfaces can be suppressed from changingfrequently between Up and Down. In this manner, the adverse impact on the stability of thedevice and network can be reduced.

In the network application, the device interface may change frequently between Up and Downbecause of interference of the physical signal and error in link layer configuration. This causesfrequent flapping of routing protocols and MPLS and brings severe impacts on the device andnetwork. Some devices even become Down and the network becomes unavailable.

The flapping control feature can suppress the interface flapping to a low frequency. Thisdecreases the effect on the stability of the device and the network.

5.1.2 Interface Flapping Control Features Supported in the NE80E/40E

Interfaces whose status changes between Up and Down at the frequency that is in the thresholdvalue range are suppressed.

The following concepts are important in interface flapping control:

l The suppress penalty value of interfaces (penalty value): This value is calculated bysuppress algorithm according to the status of the interface. The core of the algorithm is thatthe suppress penalty value increases with the changing times of the status of the interfaceand decays by exponential.

l The suppress threshold of interfaces (suppress): When this value is less than the suppresspenalty value, the interface is suppressed. This value must be greater than the reusethreshold and less than the maximum suppress penalty value.

l The reuse threshold value of interfaces (reuse): When this value is greater than the suppresspenalty value, the interface is not suppressed. This value must be less than the suppressthreshold.

l The maximum suppress penalty value of interfaces (ceiling): This value does not increasewhen the maximum suppress penalty value reaches the maximum. This value must begreater than the suppress threshold.

In the NE80E/40E, these parameters can be set to control the event that the interface becomesUp or Down.

The relationships among them are shown in Figure 5-1.



92

Figure 5-1 Diagram of the interface flapping control

Penalty Value

Time

ceiling

suppress

reuse

t1 t2 t3 t4 t5

5.2 Configuring the Interface Flapping ControlThis section describes the applicable environment and configuration procedure of interfaceflapping control.

5.2.1 Establishing the Configuration TaskWhen the link status is unstable, you can configure interface flapping control.


The flapping of routing protocols, MPLS and other protocols caused by the frequent change ofthe interface status may influence the stability of the whole network. To avoid this, you canconfigure the flapping control feature.


Before configuring the flapping control feature, you need to configure the physical attributes forthe router interfaces.

Data Preparation

To configure the flapping control feature, you need the following data.

No. Data

1 Interface number of a router

2 Suppress threshold of the interface

3 Reuse threshold of the interface



93

No. Data

4 Maximum suppress penalty value of the interface

5 Time taken to decay the penalty value to half when the interface is Up

6 Time taken to decay the penalty value to half when the interface is Down

5.2.2 Enabling the Flapping Control FeatureInterface flapping control can be enabled only in the interface view.

Procedure





NOTE

The logic-channel, null interface, and loopback interface do not support flapping control.

Step 3 Run:control-flap [ suppress reuse ceiling decay-ok decay-ng ]

The flapping control feature on the interface is enabled.

The value of suppress is 1000 times the suppress threshold of the interface. It ranges from 1 to20000. The default value is 2000. The value of suppress must be greater than the value ofreuse and smaller than the value of ceiling.

The value of reuse is 1000 times the reuse threshold of the interface. It ranges from 1 to 20000.The default value is 750. The value of reuse must be smaller than the value of suppress.

The value of ceiling is 1000 times the suppress penalty value of the interface. It ranges from1001 to 20000. The default value is 6000. The value of ceiling must be greater than the value ofsuppress.

The value of decay-ok is the time taken to decay the penalty value to half when the interface isUp. It ranges from 1 to 900 seconds. The default value is 54 seconds.

The value of decay-ng is the time taken to decay the penalty value to half when the interface isDown. It ranges from 1 to 900 seconds. The default value is 54 seconds.

----End

5.2.3 Checking the ConfigurationAfter interface flapping control is configured, you need to check whether the configuration iscorrect. In addition, you can view the operation of interface flapping control.



94

PrerequisiteThe configurations of the configuring the interface flapping control function are complete.

Procedure

Step 1 Run the display control-flap [ interface interface-type interface-number ] command to checkthe configuration and running status of the flapping control feature on interfaces.

----End

Example

Running the display control-flap command, you can view the interface flapping control featuresconfigured on the interface.

<HUAWEI> display control-flap#Interface GigabitEthernet3/0/2Control flap(OSI) status:unsuppressedControl flap(IP) status:unsuppressedControl flap parameter: suppress reuse decay-ok decay-ng ceiling 4.000 2.000 54 54 6.000

5.3 Maintaining the Flapping Control FeatureWhen a fault of interface flapping control occurs, you can use maintenance tools to locate thefault.

5.3.1 Clearing Flapping Control InformationBefore re-collecting the statistics about interface flapping control, you need to clear the operationinformation about flapping control on the interface.

Context

CAUTIONRunning the reset control-flap command can cancel the configured penalty value or the flappingtimes. This may disable the suppressed status of the interface.

To clear the running information, run the following command in the user view.

Procedure

Step 1 Run the reset control-flap { penalty | counter } interface interface-type interface-numbercommand in the user view to clear the running status or statistics of the flapping control feature.

----End



95

5.3.2 Monitoring the Flapping Control on the InterfaceIn routine maintenance, you can monitor and know the operation of interface flapping control.

ContextIn routine maintenance, you can run the following commands in any view to check the flappingcontrol on the interface.

Procedure

Step 1 Run the display control-flap [ interface interface-type interface-number ] command in anyview to check the operation of the current running status and statistics of the flapping controlfeature on the interface.

----End



96

6 Transmission Alarm Configuration

About This Chapter

Configuring transmission alarm suppression can reduce the impact of frequently-generatedtransmission alarms on the stability of the network.

NOTE

Only the 10 G WAN interfaces on the NPU on the NE80E/40E-X1&X2 support the transmission alarmfeature.

6.1 Transmission Alarm Configuration OverviewThis section describes the concepts and characteristics of transmission alarm customization andsuppression.

6.2 Configuring Transmission Alarm CustomizationAfter a transmission alarm type is customized, the alarms of this type affect the feature statusof interfaces.

6.3 Configuring the Interval for Filtering Transmission AlarmsConfiguring the interval for filtering transmission alarms can lower the frequency at whichalarms are generated, and thus minimize the impact on the stability of the network.

6.4 Configuring Transmission Alarm SuppressionThis section describes how to configure transmission alarm suppression and specify thesuppression threshold.

6.5 MaintainingWhen a fault of transmission alarm customization or suppression occurs, you can usemaintenance tools to locate the fault.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Interface Management 6 Transmission Alarm Configuration


97

6.1 Transmission Alarm Configuration OverviewThis section describes the concepts and characteristics of transmission alarm customization andsuppression.

6.1.1 Introduction to Transmission Alarm Customization andSuppression

Transmission alarm suppression can efficiently filter and suppress alarm signals. This protectsthe interface from frequently flapping. In addition, alarm customization efficiently controls theimpact of alarms on the status change of interfaces.

At present, the carrier-class network requires higher reliability for the IP network. Thus, thedevice in the network is required to rapidly detect the fault.

If fast detection works on the interface, the physical status of the interface frequently changesbetween Up and Down because alarms are notified faster. As a result, the network flapsfrequently.

Thus, alarms need to be filtered and suppressed to avoid the network from frequently flapping.

Transmission alarm suppression can efficiently filter and suppress the alarm signals. This avoidsthe interface from frequently flapping. In addition, alarm customization efficiently controls theimpact of alarms on the status change of the interface.

Transmission alarm customization and suppression implement the following functions:

l Customize alarms. This can specify the alarms that can cause the status change of theinterface.

l Suppress alarms. This can filter the burr and prevent the network from frequently flapping.

6.1.2 Features of Transmission Alarm Customization andSuppression in the NE80E/40E

Transmission alarm customization and suppression are supported only on the physical interfacesencapsulated with SDH/SONET.

Supported Interface Type

Only the physical interfaces encapsulated with the Synchronous Digital Hierarchy (SDH) andSynchronous Optical Network (SONET) support transmission alarm customization andsuppression. The supported interfaces are Asynchronous Transfer Mode (ATM) interfaces,Packet Over SDH/SONET (POS) interfaces, 10 GE Wide Area Network (WAN) interfaces,CPOS interfaces, E1 interfaces, T3 interfaces, and WDM interfaces.

Active/Standby Switchover

During the active/standby switchover, the system can normally process various alarm signals oftransmission alarms, and the configurations of transmission alarms also take effect.



98

6.2 Configuring Transmission Alarm CustomizationAfter a transmission alarm type is customized, the alarms of this type affect the feature statusof interfaces.

6.2.1 Establishing the Configuration TaskThis part describes the applicable environment, pre-configuration tasks, and required data oftransmission alarm customization.


When the transmission equipment is connected with a router, a large number of burr alarms aregenerated if the network is unstable. These alarms, however, make the physical status of theinterface frequently change between Up and Down. To make the network device ignore theseburr alarms by customizing some alarms, you need to configure transmission alarmcustomization.


Before configuring transmission alarm customization,

l power on and start the router normally.

Data Preparation

To configure transmission alarm customization, you need the following data.

No. Data


2 Type of the alarm that can affect the physical status of the interface

3 (Optional) Respective thresholds of B3TCA, SDBERE, and SFBERE alarms

4 (Optional) Type of the alarm that can record logs

6.2.2 Configuring the Type of the Alarm That Can Affect thePhysical Status of the Interface

Transmission alarm customization can be configured only in the interface view. Alarm typesthat can be customized vary with the hardware.

Procedure




99




The supported interfaces are ATM interfaces, POS interfaces, 10 GE WAN interfaces, and WDMinterfaces.

Step 3 Run:transmission-alarm down { auais | b3tca | lais | lcd | lof | lom | lop | los | lrdi | lrei | odu-ais | odu-lck | odu-oci | oof | otu-ais | otu-lom | otu-sd-ber | otu-sf-ber | pais | pm-bdi | pm-tim | pplm | prdi | prei | puneq | rdool | r-lof | r-los | r-oof | rrool | sdbere | sfbere | sm-bdi | sm-iae | sm-tim | trool } *

The alarm that can affect the physical status of the interface is customized.

The hardware supports different types of alarms. Thus, not all interfaces support the precedingalarms. If the alarm type that the hardware does not support is configured, the configurationfails. In addition, the types of alarms not supported by the interface are displayed. The parameterlcd is displayed only on 10GE WAN interfaces.

Only 10GE WAN interfaces support wlnk alarms. You cannot configure wlnk alarms. You canuse the display transmission-alarm command to check the status and statistics of wlnk alarms.

CAUTIONLAIS, LOF, and LOS alarms provide alarms for the status change of the link. Disabling thesealarms affects the precise forwarding of service data. Thus, it is recommended to enable thesealarms.

----End

6.2.3 (Optional) Configuring the Respective Thresholds of B3TCA,SDBERE, and SFBERE Alarms

Thresholds of B3TCA, SDBERE, and SFBERE alarms can be configured. No alarm is reportedif the number of alarms does not reach the threshold.

ContextDo as follows on the interface connected to the transmission equipment:

Procedure







100

The supported interfaces are ATM interfaces, POS interfaces, 10 GE-WAN interfaces, andWDM interfaces.

Step 3 Run:transmission-alarm threshold { b3tca b3tca | sdbere sdbere | sfbere sfbere } *

The alarm threshold that determines whether B3TCA, SDBERE, and SFBERE alarms can bereported by the transmission equipment to the NE80E/40E is configured.

The threshold of the three types of alarms is expressed in 10-n, in which the exponent n isspecified by the parameter value of each type of alarms configured in the transmission-alarmthreshold command. The value of sdbere cannot be smaller than that of sfbere. That is, thethreshold of SDBERE alarms cannot be greater than that of SFBERE alarms.

By default, the respective thresholds of B3TCA, SDBERE, and SFBERE alarms are 10-6, 10-6,and 10-3.

----End

6.2.4 (Optional) Configuring the Type of the Alarms That Can BeRecorded to Logs

Recording alarms to logs helps you to query if necessary.

Procedure





The supported interfaces are ATM interfaces, POS interfaces, 10 GE WAN interfaces, and WDMinterfaces.

Step 3 Run:transmission-alarm log { auais | b3tca | lais | lcd | lof | lom | lop | los | lrdi | lrei | odu-ais | odu-lck | odu-oci | oof | otu-ais | otu-lom | otu-sd-ber | otu-sf-ber | pais | pm-bdi | pm-tim | pplm | prdi | prei | puneq | rdool | r-lof | r-los | r-oof | rrool | sdbere | sfbere | sm-bdi | sm-iae | sm-tim | trool } *

The alarms recorded to logs after being generated are enabled.

The hardware supports different types of alarms. Thus, not all interfaces support the precedingalarms. If the alarm type that the hardware does not support is configured, the configurationfails. In addition, the types of alarms not supported by the interface are displayed. The parameterlcd is displayed only on 10GE WAN interfaces.

By default, WAN Interface Link Status Alarm (wlnk) alarms are recorded to the log. Only 10GEWAN interfaces support wlnk alarms. You cannot configure wlnk alarms, and wlnk alarms arealways enabled. You can use the display transmission-alarm command to check the status andstatistics of wlnk alarms.

----End



101

6.2.5 Checking the ConfigurationAfter transmission alarm customization is configured, you need to check whether theconfiguration is correct. In addition, you can view the status and statistics about alarms on theinterface.

PrerequisiteThe configurations of the configuring transmission alarm customization function are complete.

Procedurel Run the display transmission-alarm interface-type interface-number [ auais | b3tca |

lais | lcd | lof | lom | lop | los | lrdi | lrei | odu-ais | odu-lck | odu-oci | oof | otu-ais | otu-lom | otu-sd-ber | otu-sf-ber | pais | pm-bdi | pm-tim | pplm | prdi | prei | puneq |rdool | r-lof | r-los | r-oof | rrool | sdbere | sfbere | sm-bdi | sm-iae | sm-tim | trool |wlnk ] * command to check alarm configuration on the interface.

l Run the display transmission-alarm threshold [ interface-type interface-number ]command check the respective thresholds of B3TCA, SDBERE, and SFBERE alarms onthe interface.

----End

ExampleView the status and statistics of the alarms, such as AUAIS, B3TCA, LAIS, LOF, LOS, andTROOL alarms on POS 1/0/0.

<HUAWEI> display transmission-alarm pos 1/0/0 auais b3tca lais lof los trool Interface: Pos1/0/0 Filter function: disabled Damping function: enabled Suppress value: 999 Ceiling value: 6000 Reuse value: 500 OK half decay value: 1000 NG half decay value: 1000 Last reset time: 2006-10-18,17:56:11.1 Alarm auais Status: Up, If down Figure of merit: 0.0000000e+00 Flapping count: 114000 Suppressing count: 37 Alarm b3tca Status: Down Flapping count: 0 Alarm lais Status: Up Figure of merit: 0.0000000e+00 Flapping count: 114001 Suppressing count: 0 Alarm lof Status: Up Figure of merit: 0.0000000e+00 Flapping count: 114001 Suppressing count: 0 Alarm los Status: Up Figure of merit: 0.0000000e+00 Flapping count: 114001 Suppressing count: 0 Alarm trool



102

Status: Up, Log Figure of merit: 0.0000000e+00 Flapping count: 114001 Suppressing count: 0

View the respective thresholds of B3TCA, SDBERE, and SFBERE alarms on POS 1/0/0.

<HUAWEI> display transmission-alarm threshold pos 1/0/0 Interface: Pos1/0/0 b3tca threshold: 10e-7 sdbere threshold: 10e-9 sfbere threshold: 10e-8

6.3 Configuring the Interval for Filtering TransmissionAlarms

Configuring the interval for filtering transmission alarms can lower the frequency at whichalarms are generated, and thus minimize the impact on the stability of the network.

6.3.1 Establishing the Configuration TaskThis part describes the applicable environment, pre-configuration tasks, and required data forconfiguring the interval for filtering transmission alarms.


When the transmission equipment is connected to the network, a large number of burr alarmsare generated if the network is unstable. These alarms, however, make the physical status of theinterface frequently change between Up and Down. If some alarms that are generated and clearedin a certain period can be ignored, the interval for filtering transmission alarms needs to beconfigured.


Before configuring the interval for filtering transmission alarms, complete the following tasks:

l Powering on and starting the router normallyl Configuring Transmission Alarm Customization on the interface

NOTE

The filtering function can be enabled only after the interface is enabled with transmission alarmcustomization.

Data Preparation

To configure the interval for filtering transmission alarms, you need the following data.

No. Data


2 Filtering timer parameter



103

6.3.2 Configuring the Interval for Filtering Transmission AlarmsIf the interval of alarm generating and disappearing is smaller than the set interval, the alarmsignal is regarded as a burr and is filtered. Otherwise, the alarm signal is normal.

ContextTo configure transmission alarm filtering on multiple interfaces, you can repeat Step 2 and Step3.


system-view





Step 3 You can select one or more following configurations according to the alarm message to befiltered out.l Run the transmission-alarm holdoff-timer holdoff-time command to enable the device

management module to filter out the alarm message indicating that the interface goes Downand set the filtering interval.When the interface goes Down, the device management module generates an alarm messageand takes corresponding actions to process the alarm message according to the followingsituations:– If the device management module receives an alarm message indicating that the interface

goes Up within the specified filtering interval, the device management module filter outthe alarm message indicating that the interface goes Down, that is, the device managementmodule does not send the alarm message to the upper-layer application.

– If the device management module does not receive an alarm message indicating that theinterface goes Up within the specified filtering interval, the device management modulesends the alarm message indicating that the interface goes Down to the upper-layerapplication after the filtering interval expires.

l Run the transmission-alarm holdup-timer holdup-time command to enable the devicemanagement module to filter out the alarm message indicating that the interface goes Up andset the filtering interval.When the interface goes Up, the device management module generates an alarm messageand takes corresponding actions to process the alarm message according to the followingsituations:– If the device management module receives an alarm message indicating that the interface

goes Down within the specified filtering interval, the device management module filterout the alarm message indicating that the interface goes Up, that is, the devicemanagement module does not send the alarm message to the upper-layer application.

– If the device management module does not receive an alarm message indicating that theinterface goes Down within the specified filtering interval, the device management



104

module sends the alarm message indicating that the interface goes Up to the upper-layerapplication after the filtering interval expires.

By default, the device management module does not filter out the alarm message indicating thatthe interface goes Up or Down. That is, once the device management module receives the alarmmessage indicating that the interface goes Up or Down, it immediately sends the alarm messageto the upper-layer application.

----End

6.3.3 Checking the ConfigurationAfter the interval for filtering transmission alarms is configured, you need to check whether theconfiguration is correct. In addition, you can view the status and statistics about alarms on theinterface.

PrerequisiteThe configurations of the configuring the interval for filtering transmission alarms function arecomplete.

Procedurel Run the display transmission-alarm interface-type interface-number [ auais | b3tca |

lais | lcd | lof | lom | lop | los | lrdi | lrei | odu-ais | odu-lck | odu-oci | oof | otu-ais | otu-lom | otu-sd-ber | otu-sf-ber | pais | pm-bdi | pm-tim | pplm | prdi | prei | puneq |rdool | r-lof | r-los | r-oof | rrool | sdbere | sfbere | sm-bdi | sm-iae | sm-tim | trool |wlnk ] * command to check the alarm configuration.

----End

Example

If the filtering function is enabled, you can view that the suppression function is enabled.

<HUAWEI> display transmission-alarm configuration pos 1/2/0 Interface: Pos1/2/0 Filter function: enabled (Holdtime is 55) Damping function: enabled Suppress value: 999 Ceiling value: 6000 Reuse value: 500 OK half decay value: 500 NG half decay value: 1000

6.4 Configuring Transmission Alarm SuppressionThis section describes how to configure transmission alarm suppression and specify thesuppression threshold.

6.4.1 Establishing the Configuration TaskThis part describes the applicable environment, pre-configuration tasks, and required data oftransmission alarm suppression.



105

Applicable EnvironmentWhen the transmission equipment is connected to the network, a large number of burr alarmsare generated if the network is unstable. These alarms, however, make the physical status of theinterface frequently change between Up and Down. To prevent these alarms from frequentlyflapping or make the network device ignore these burr alarms, you need to enable alarmsuppression.

Pre-configuration TasksBefore configuring transmission alarm suppression, complete the following tasks:

l Powering on and starting the router normallyl Configuring Transmission Alarm Customization on the interface

NOTE

The suppression function takes effect on interfaces only after alarm customization is enabled on theinterfaces.

Data PreparationTo configure transmission alarm suppression, you need the following data.

No. Data

1 Interface Type and number.

2 Alarm ceiling threshold, alarm reuse threshold, alarm suppression threshold, half-lifeof alarm generation, and half-life of alarm clearance.

6.4.2 Configuring Transmission Alarm SuppressionAfter the suppression threshold of transmission alarms is set, alarms are reported only when thenumber of alarms reaches the threshold.


system-view





Step 3 Run:transmission-alarm damping [ suppress suppress | reuse reuse | ceiling ceiling | decay-ok decay-ok | decay-ng decay-ng ] *

Suppression is enabled and suppression parameters are set.



106

By default, transmission alarm suppression is not enabled.

----End

6.4.3 Checking the ConfigurationAfter transmission alarm suppression is configured, you need to check whether the configurationis correct. In addition, you can view the status and statistics about alarms on the interface.

PrerequisiteThe configurations of the configuring transmission alarm suppression function are complete.

Procedure

Step 1 Run the display transmission-alarm configuration [ interface-type interface-number ]command to check the alarm configuration of the interface.

----End

ExampleRun the display transmission-alarm configuration command, and you can view the alarmconfiguration of the interface. The following is the display of the command:

<HUAWEI> display transmission-alarm configuration pos 1/2/0 Interface: Pos1/2/0 Filter function: enabled (Holdtime is 55) Damping function: enabled Suppress value: 999 Ceiling value: 6000 Reuse value: 500 OK half decay value: 500 NG half decay value: 1000

6.5 MaintainingWhen a fault of transmission alarm customization or suppression occurs, you can usemaintenance tools to locate the fault.

6.5.1 Clearing Transmission Alarm InformationBefore re-collecting the statistics about transmission alarms on an interface, you need to clearall transmission alarm information on the interface.

Context

CAUTIONClearing transmission alarm information on the interface may cause all alarm statistics on theinterface to be reset. Therefore, confirm the action before you use the command.



107

Procedure

Step 1 Run the reset transmission-alarm statistics command in the interface view to clear all thetransmission alarm running statistics on the interface.

----End



108

A Glossary

Collates frequently used glossaries in this document.

A

ATM Asynchronous Transfer Mode (ATM). A data transmissiontechnology in which data is transferred at high data rates in fixedlength, 53 bytes.

Authentication An act that decides whether a user can be awarded with access rightor what kinds of users can access a network.

Authorization An act that accredits a user with access to certain services.

AUX Auxiliary interface that provides an EIA/TIA-232 DTE interface. Byusing the AUX interface and the Modem, a user can access a networkthrough dialup.

C

Callback A call mode in which both ends of the communication participate inthe call. One end is called the Client, while the other end is caller theServer. The Client initiates a call, and the Server decides whether tocallback or not. If a callback is needed, the Server tears down theconnection and then initiates a call to the Client.

Called Number Number of the called party.

Calling Number Number of the calling party.

P

POS A MAN and LAN technology that provides a point to pointconnection. The POS interface is based on SONET.

Q

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Interface Management A Glossary


109

QinQ The QinQ technology adds one a layer of 802.1Q tag on the 802.1Qpacket to expand the VLAN space. In this way, data of the VLAN canbe transparently transmitted in the public network.

S

SONET Synchronous Optical Network (SONET). A standard for synchronousdata transfer over optical networks. The standard contains a series oftransmission speed, including SDH Transport Module (STM) -1(155Mbit/s), STM-4c (622 Mbit/s) and STM-16c/STM-16 (2.5 Gbit/s).

V

VLAN The Virtual Local Area Network (VLAN) divides a physical LAN intoseveral logical sub-nets, regardless of their physical locations.Datatransmission within a VLAN does not interfere with that in otherVLANs. This enhances the network security.

W

WAN Wide Area Network. A network that covers a large geographic area.

X

X.21 ITU-T standard for serial communications over synchronous digitallines. It is mainly used in Europe and Japan.

X.25 A data link layer protocol. A protocol that defines the establishmentand maintenance of connections between the DTE devices and theDCE devices.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Interface Management A Glossary


110

B Acronyms and Abbreviations

Collates frequently used acronyms and abbreviations in this document.

A

AA Anonymous Access

AAA Authentication, Authorization and Accounting

AAL ATM Adaptation Layer

AAL1 ATM Adaptation Layer Type 1




ACL Access Control List

ADSL Asymmetric Digital Subscriber Line

AM Analog Modem

AMI Alternate Mark Inversion

ANSI American National Standard Institute

ARP Address Resolution Protocol

ATM Asynchronous Transfer Mode

AU Administrative Unit

AUG Administrative Unit Group

AUX Auxiliary (port)

AUAIS Administrative Unit Alarm Indication Signal

B

B3TCA B3 Threshold Crossing Alarm

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Interface Management B Acronyms and Abbreviations


111

BAS Broadband Access Server

BGP Border Gateway Protocol

BRI Basic Rate Interface

C

CAR Committed Access Rate

CBR Constant Bit Rate

CC Call Control

CCITT International Telegraph and Telephone Consultative Committee

CD Carrier Detect

CDV Cell Delay Variation

CHAP Challenge Handshake Authentication Protocol

CPE Customer Premises Equipment

CPOS Channelized-POS

CSMA Carrier Sense Multiple Access

CUG Closed User Group

D

DCC Data Communication Channel

DCD Data Carrier Detected

DCE Data Circuit-terminating Equipment

DDN Digital Data Network

DHCP Dynamic Host Configuration Protocol

DIP Dual-In-line Package

DLCI Data Link Control Identifier

DLSw Data Link Switching

DNS Domain Name System

DSL Digital Subscriber Line

DSLAM DSL Access Multiplexer

DSR Data Set Ready

DSS1 Digital Subscriber Signaling No.1

DTE Data Terminal Equipment



112

E

EIA Electronics Industry Association

ESF Extended Service Frame

ETSI European Telecommunications Standards Institute

F

FCS Frame Check Sequence

FDDI Fiber Distributed Digital Interface

FE Fast Ethernet

FIFO First In First Out

FR Frame Relay

FRF Frame Relay Forum

FRMR Frame Rejection

FS Forced Switch

FTP File Transfer Protocol

G

GE Gigabit Ethernet

GPRS General Packet Radio Service

GRE Generic Routing Encapsulation

H

HDB3 High Density Bipolar of Order 3

HDLC High level Data Link Control

HDSL High-bit-rate Digital Subscriber Link

HFC Hybrid Fiber-Coaxial

HIC Highest Incoming-only Channel

HOC Highest Outgoing-only Channel

HTTP Hyper Text Transport Protocol

I



113

IAD Integrated Access Device

IBGP Internal BGP

ICP IMA Control Protocol

ID IDentification

IEEE Institute of Electrical and Electronics Engineers

IETF Internet Engineering Task Force

IF Information Frame

IGMP Internet Group Management Protocol

IMA Inverse Multiplexing on ATM

IP Internet Protocol

IPC Inter-Process Communication

IPCP IP Control Protocol

IPHC IP Header compression

IPoA Internet Protocols over ATM

IPoE IP over Ethernet

IPoEoA IP over Ethernet over AAL5

IPX Internet Packet Exchange

ISDN Integrated Services Digital Network

ISO International Organization for Standardization

ISP Internet Service Provider

ITU-T International Telecommunication Union - Telecommunication StandardizationSector

L

L2TP Layer 2 Tunneling Protocol

LAIS Line Alarm Indication Signal

LAN Local Area Network

LAPB Link Access Procedure, Balanced

LC Line Card

LCD Loss of Code Group Synchronization

LCI Logic Channel Identifier

LCP Link Control Protocol

LDD Laser Detector Diode



114

LED Light Emitting Diode

LFI Link Fragmentation and Interleaving

LIC Lowest Incoming-only Channel

LOC Loss of continuity

LOF Loss of Frame

LOM Loss of Tributary Multiframe

LOS Loss of Signal

LOP Loss of Pointer

LQR Link Quality Reports

LRDI Line Remote Defect Indication

LREI Line Remote Error Indication

LTC Lowest Two-way Channel

M

MAP Mobile Application Part

MD5 Message Digest 5

MIB Management Information Base

MODEM Modulator DEModulator

MP Multilink PPP

MTU Maximum Transmission Unit

MUX Multiplex

N

NAT Network Address Translation

NBMA Non Broadcast Multiple Access

NCP Network Control Protocol

NE NetEngine

NNI Network Node Interface

NT Network Terminal

O

OAM Operation, Administration and Maintenance



115

OC-3 OC-3

OOF Out of Frame

OSI Open System Interconnection

P

PAD Packet Assembler/ Disassembler

PAIS Path Alarm Indication Signal

PAP Password Authentication Protocol

PBX Private Branch Exchange

PC Personal Computer

PCI Protocol Control Information

PCM Pulse-Code Modulation

POH Path Overhead

POS Packet Over SDH/SONET

PPP Point-to-Point Protocol

PPLM Path Signal Label Mismatch

PPPoA PPPoA

PPPoE PPP over Ethernet

PRDI Path Remote Defect Indication

PREI Path Remote Error Indication

PRI Primary Rate Interface

PSE Packet Switching Exchange

PSTN Public Switched Telephone Network

PUNEQ Path Unequipped Indication

PVC Permanent Virtual Circuit

Q

QoS Quality of Service

R

RADIUS Remote Authentication Dial in User Service

RAS Remote Access Server



116

RDOOL Receive Data Out of Lock

RFC Request for Comments

RIP Routing Information Protocol

ROA Recognized operating Agency

RPC Raman Pump Amplifier Unit For C-band

RROOL Receive Reference Out of Lock

RSOH Regenerator Section Overhead

RSU Routing Switch Unit

RTP Real-time Transport Protocol

RTU Remote Test Unit

S

SABM Set Asynchronous Balanced Mode

SDBERE Signal Degrade Threshold Alarm

SDH Synchronous Digital Hierarchy

SDLC Synchronous Data Link Control

SDSL Symmetrical Digital Subscriber Line

SF Signal Failure

SFBERE Signal Fail Threshold Alarm

SGSN Serving GPRS Support Node

SLIP Serial Line Internet Protocol

SNA Systems Network Architecture

SNAP Sub Network Access Point

SNMP Simple Network Management Protocol

SNP Sequence Number PDUs

SOH Section Overhead

SONET Synchronous Optical Network

SP Service Provider

STM-1 SDH Transport Module -1

SVC Switched Virtual Channel

T



117

TA Terminal Adapter

TACACS

Terminal Access Controller Access Control System

TCP Transmission Control Protocol

TFTP Trivial File Transfer Protocol

TROOL Transmit Reference Out of Lock

TU Tributary Unit

TUG Tributary Unit Group

U

UA Unnumbered Acknowledge

UBR Unspecified Bit Rate

UDP User Datagram Protocol

UNI User Network Interface

UP User Plane

V

VA Virtual Access

VBR Variable Bit Rate

VC Virtual Circuit

VCI Virtual Channel Identifier

VCN Virtual Circuit Number

VDSL Very High Speed DSL

VIU Versatile Interface Unit

VLAN Virtual Local Area Network

VP Virtual Path

VPI Virtual Path Identifier

VPLS Virtual Private LAN Service

VPN Virtual Private Network

VRP Versatile Routing Platform

VT Virtual-Template

W



118

WLNK WAN Interface Link Stauts Alarm

WWW World Wide Web

X

XOT X.25 Over TCP



119

Configuration Guide - Interface Management(V600R003C00_02) (1)

Documents

Transcript of Configuration Guide - Interface Management(V600R003C00_02) (1)