Configuration Guide - Interface Management (V600R003C00 - 02) PDF

HUAWEI NetEngine80E/40E Router
V600R003C00
Configuration Guide - Interface

Management
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 written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address:
Huawei Industrial Base

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

Copyright Huawei Technologies Co., Ltd.

Configuration Guide - Interface Management
About This Document
About This Document

Purpose
This manual describes related configurations of various interfaces and interface boards
supported 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, fast
sensing of interface status changes, interface flapping control, transmission alarm customization
and 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 board
intermixing, 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 working
situations, the actual interface numbers and link types may be different from those used in this
document.
l In NE80E/40E series (except for the NE40E-X1/X2), line processing boards are called Line Processing
Units (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 Network
Processing Unit (NPU).
Related Versions
The following table lists the product versions related to this document.
Product Name
Version
HUAWEI NetEngine80E/40E
Router
V600R003C00
Intended Audience
This document is intended for:
l
Commissioning Engineer
Data Configuration Engineer
Network Monitoring Engineer
Issue 02 (2011-09-10)

ii

About This Document
System Maintenance Engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
DANGER
WARNING
CAUTION
Alerts you to a high risk hazard that could, if not avoided,

result in serious injury or death.
Alerts you to a medium or low risk hazard that could, if
not avoided, result in moderate or minor injury.
Alerts 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 save

time.
NOTE
Provides additional information to emphasize or

supplement important points in the main text.
Command Conventions (Optional)

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

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

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

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

vertical bars. Several items or no item can be selected.
iii

About This Document
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 History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Changes in Issue 02 (2011-09-10)

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

Initial commercial release.
Issue 02 (2011-09-10)

iv

Contents
Contents
About This Document.....................................................................................................................ii
1 Interface Basic Configuration.....................................................................................................1
1.1 Interface Basic Configuration Overview............................................................................................................2
1.1.1 Interface type.............................................................................................................................................2
1.1.2 Service Interface Numbering Rules...........................................................................................................2
1.1.3 Interface Views and Prompts.....................................................................................................................4
1.1.4 Link Layer Protocols and Access Technologies........................................................................................7
1.1.5 Basic Interface Configurations Supported by the NE80E/40E..................................................................9
1.2 Configuring the Interface Description..............................................................................................................10
1.2.1 Establishing the Configuration Task.......................................................................................................10
1.2.2 Configuring the Interface Description.....................................................................................................10
1.2.3 Checking the Configuration.....................................................................................................................11
1.3 Configuring the Hold-Time Interval After an Interface Becomes Up/Down...................................................11
1.3.2 Configuring the Hold-Time Interval After an Interface Becomes Up/Down..........................................12
1.4 Configuring the Interval for Collecting the Statistics of Traffic on the Interface............................................13
1.4.2 Configuring the Global Interval for Collecting Traffic Statistics............................................................14
1.4.3 Configuring the Interval for Collecting the Statistics of Traffic on the Interface...................................15
1.4.4 Configuring Traffic Statistics on Sub-Interfaces.....................................................................................15
1.5 Enabling the Statistics for Packets Sent to the CPU.........................................................................................18
1.5.2 Enabling the Statistics for Packets Sent to the CPU Globally.................................................................18
1.5.3 (Optional) Enabling the Statistics for Packets Sent to the CPU Through the VLAN.............................19
1.5.4 (Optional) Enabling the Statisitcs for Packets Sent to the CPU Through the PVC.................................20
1.6 Configuring a Signal Sending Delay on an Interface.......................................................................................21
1.6.2 Configuring a Signal Sending Delay on an Interface..............................................................................22
1.7 Enabling the Alarm Function on an Interface...................................................................................................23
Issue 02 (2011-09-10)


Contents

1.7.2 Enabling the Alarm Function on an Interface..........................................................................................24
1.8 Maintaining Interface Basic Configuration......................................................................................................26
1.8.1 Clearing Statistics....................................................................................................................................26
1.8.2 Monitoring Interface Information............................................................................................................27
2 Logical Interface Configuration................................................................................................29

2.1 Logical Interface Configuration Overview.......................................................................................................30
2.1.1 Introduction to Logical Interfaces...........................................................................................................30
2.1.2 Features of the Logical Interfaces in the NE80E/40E.............................................................................30
2.2 Creating Sub-interfaces....................................................................................................................................30
2.2.2 Creating ATM Sub-interfaces.................................................................................................................31
2.2.3 Creating FR Sub-interfaces.....................................................................................................................32
2.3 Configuring Logical Channel Interfaces..........................................................................................................34
2.3.2 Creating a Logical Channel Interface......................................................................................................34
2.4 Configuring Virtual-Template Interfaces.........................................................................................................35
2.4.2 Configuring the IP Address of a VT Interface.........................................................................................36
2.4.3 Setting the Maximum Number of Links Supported by a VT Interface...................................................37
2.5 Configuring Virtual-Ethernet Interfaces...........................................................................................................39
2.5.2 Creating a VE Interface...........................................................................................................................39
2.6 Configuring a Loopback Interface....................................................................................................................41
2.6.2 Creating a Loopback Interface and Configuring Its IP Address..............................................................42
2.7 Configuring a Null Interface.............................................................................................................................43
2.7.2 Entering the Null Interface View.............................................................................................................43
2.8 Configuration Examples...................................................................................................................................44
2.8.1 Example for Configuring the Sub-interface............................................................................................44
2.8.2 Example for Configuring the Virtual-Template Interface.......................................................................47
2.8.3 Example for Configuring the Loopback Interface...................................................................................47
3 Interface Board Intermixing Configuration...........................................................................50

3.1 Interface Board Intermixing Configuration Overview.....................................................................................51
Issue 02 (2011-09-10)

vi

Contents
3.1.1 Introduction to Interface Board Intermixing............................................................................................51

3.1.2 Features of Interface Board Intermixing in the NE80E/40E...................................................................51
3.2 Configuring the Public FIB Policy...................................................................................................................51
3.2.2 Configuring the Public IPv4 FIB Policy..................................................................................................52
3.2.3 Configuring the Public IPv6 FIB Policy..................................................................................................53
3.3 Configuring the VPN FIB Policy.....................................................................................................................54
3.3.2 Configuring the VPN IPv4 FIB Policy....................................................................................................55
3.3.3 Configuring the VPN IPv6 FIB Policy....................................................................................................56
3.4 Configuring the Policy of Discarding All the FIB Entries...............................................................................57
3.4.2 Configuring the Policy of Discarding All the IPv4 FIB Entries..............................................................58
3.4.3 Configuring the Policy of Discarding All the IPv6 FIB Entries..............................................................59
3.5 Configuring Overload Suspension Recovery...................................................................................................60
3.5.2 Configuring Overload Suspension Recovery..........................................................................................61
3.5.3 Refreshing the FIB Policy.......................................................................................................................62
3.6 Configuring Overload Forwarding Recovery...................................................................................................63
3.6.2 Configuring IPv4 FIB Overload Forwarding Recovery..........................................................................64
3.6.3 Configuring IPv6 FIB Overload Forwarding Recovery..........................................................................64
3.7 Configuration Examples...................................................................................................................................66
3.7.1 Example for Configuring the VPN IPv4 FIB Policy...............................................................................66
3.7.2 Example for Configuring Overload Suspension Recovery.....................................................................73
3.7.3 Example for Configuring Overload Forwarding Recovery.....................................................................79
4 Fast Feeling Configuration........................................................................................................87

4.1 Fast Feeling Configuration Overview..............................................................................................................88
4.1.1 Introduction to Fast Feeling.....................................................................................................................88
4.1.2 Fast Feeling Features Supported by the NE80E/40E..............................................................................88
4.2 Configuring Fast Feeling..................................................................................................................................88
4.2.2 Enabling Fast Feeling..............................................................................................................................89
4.3 Maintaining Fast Feeling..................................................................................................................................90
4.3.1 Monitoring the Running of Fast Feeling.................................................................................................90
5 Flapping Control Configuration...............................................................................................91

Issue 02 (2011-09-10)

vii

Contents
5.1 Flapping Control Configuration Overview.......................................................................................................92

5.1.1 Introduction to the Interface Flapping Control........................................................................................92
5.1.2 Interface Flapping Control Features Supported in the NE80E/40E........................................................92
5.2 Configuring the Interface Flapping Control.....................................................................................................93
5.2.2 Enabling the Flapping Control Feature...................................................................................................94
5.3 Maintaining the Flapping Control Feature.......................................................................................................95
5.3.1 Clearing Flapping Control Information...................................................................................................95
5.3.2 Monitoring the Flapping Control on the Interface...................................................................................96
6 Transmission Alarm Configuration.........................................................................................97

6.1 Transmission Alarm Configuration Overview.................................................................................................98
6.1.1 Introduction to Transmission Alarm Customization and Suppression....................................................98
6.1.2 Features of Transmission Alarm Customization and Suppression in the NE80E/40E............................98
6.2 Configuring Transmission Alarm Customization.............................................................................................99
6.2.2 Configuring the Type of the Alarm That Can Affect the Physical Status of the Interface......................99
6.2.3 (Optional) Configuring the Respective Thresholds of B3TCA, SDBERE, and SFBERE Alarms.......100
6.2.4 (Optional) Configuring the Type of the Alarms That Can Be Recorded to Logs.................................101
6.2.5 Checking the Configuration...................................................................................................................102
6.3 Configuring the Interval for Filtering Transmission Alarms..........................................................................103
6.3.1 Establishing the Configuration Task.....................................................................................................103
6.3.2 Configuring the Interval for Filtering Transmission Alarms.................................................................104
6.4 Configuring Transmission Alarm Suppression..............................................................................................105
6.4.1 Establishing the Configuration Task.....................................................................................................105
6.4.2 Configuring Transmission Alarm Suppression.....................................................................................106
6.5 Maintaining.....................................................................................................................................................107
6.5.1 Clearing Transmission Alarm Information............................................................................................107
A Glossary......................................................................................................................................109
B Acronyms and Abbreviations.................................................................................................111
Issue 02 (2011-09-10)

viii

1 Interface Basic Configuration
Interface Basic Configuration
About This Chapter

This chapter describes common interface types and how to view the interface information and
configure the interval for collecting the interface traffic.
1.1 Interface Basic Configuration Overview
This section describes common interface types and link layer protocols.
1.2 Configuring the Interface Description
This section describes how to configure interface description that helps you to memorize the
functions of interfaces.
1.3 Configuring the Hold-Time Interval After an Interface Becomes 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 changes
between Up and Down.
1.4 Configuring the Interval for Collecting the Statistics of Traffic on the Interface
This section describes how to configure the interval for collecting the statistics about traffic
globally or on the interface, which helps you to monitor network conditions.
1.5 Enabling the Statistics for Packets Sent to the CPU
Enabling the statistics for packets sent to the CPU helps you know the type, number, and source
of packets sent to the CPU.
1.6 Configuring a Signal Sending Delay on an Interface
When an interface on the router is dual-homed to non-Huawei devices, you can configure a
signal sending delay on the interface to avoid data loss due to asynchronous link switchover or
incomplete configuration restoration.
1.7 Enabling the Alarm Function on an Interface
If a large number of alarms are generated on a link, the system is busy dealing with various
alarms and the system performance is thus degraded. To solve this problem, you can enable the
alarm function on an interface.
1.8 Maintaining Interface Basic Configuration
Clear interface statistics and monitoring interface information are maintenance tools that help
you know interface status.
Issue 02 (2011-09-10)


1.1 Interface Basic Configuration Overview

This 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 FR
and IP-Trunk interfaces are not supported on the NE40E-X1&X2 series.
1.1.1 Interface type

This part describes interface types. Through interfaces, a device can exchange data and interact
with other devices on the network. Interfaces can be classified into physical and logical
interfaces.
Interfaces of routers help in exchange of data and interaction with other devices on the
network. 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 LAN
through LAN interfaces.
Currently, the NE80E/40E supports such LAN interfaces as Ethernet interface. Ethernet
interfaces include Ethernet electrical interfaces, fast Ethernet interfaces, and Gigabit
Ethernet interfaces.
Wide Area Network (WAN) interfaces: routers exchange data with devices of external
networks through WAN interfaces.
Currently, the NE80E/40E supports such WAN interfaces as CE1 interfaces, CT1
interfaces, E3 interfaces, T3 interfaces, POS interfaces,CPOS interfaces, and ATM
interfaces.
Logical Interfaces
Logical interfaces can exchange data. It, however, does not physically exist and must be created
through configuration.
Currently, the NE80E/40E mainly supports such logical interfaces as sub-interfaces, Eth-Trunk
interfaces, VLANIF interfaces, Virtual-Ethernet (VE) interfaces, loopback interfaces, null
interfaces, MP-Group interfaces, IP-Trunk interfaces,tunnel interfaces, and MTunnel interfaces.
1.1.2 Service Interface Numbering Rules

Service interface numbering rules on the NE40E-X series vary with the hardware structures of
these devices. This section describes the service interface numbering rules on the NE40EX16&X8&X3 and NE40E-X1&X2.
Issue 02 (2011-09-10)


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

NOTE
The service interface numbering rules of the NE40E-16 and the NE40E-8 are the same as those of the
NE40E-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 number

LPU 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 the
NE40E-X3 are 16, 8, and 3 respectively.
Subcard number
The subcard numbers of services interfaces begin with 0. The value range of the subcard
number 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 0
to 3.
Finished board: The subcard number is always 0.
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&X2

The 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 service
interfaces, always numbered GE 8/0/0 and GE 8/0/1.
Service interfaces on a subcard

The NE40E-X1&X2 and the NE40E-X16&X8&X3 have differences in hardware
structures. On the NE40E-X1&X2, data forwarding on service interfaces all needs to be
processed by the NPUs. Therefore, on the NE40E-X1&X2, an interface is numbered in the
format 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 service
interfaces.
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 forwarding
on the service interfaces in slots 3 to 6 in the lower chassis. Therefore, on cards in slots
3 to 6, the NPU slot numbers in the service interface numbers is always 7. The NPU in
slot 8 is responsible for data forwarding on the service interfaces in slots 9 to 12 in the
upper chassis. Therefore, on cards in slots 9 to 12, the NPU slot numbers in the service
interface numbers is always 8.
Issue 02 (2011-09-10)


Subcard number
It is the slot number of the subcard where service interfaces reside. The subcard numbers
on the NE40E-X1 range from 2 to 5 and the subcard numbers on the NE40E-X2 range
from 3 to 6 and 9 to 12.
Port number
The port numbers of service interfaces on a subcard begin with 0. Port numbering
depends on the number of interfaces on the subcard.
The service interface numbering rules of the NE40E-X1&X2 are special. Therefore, the
following 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
6 MPU
7 MPU
4 FIC/HIC
5 FIC/HIC
2 FIC/HIC
3 FIC/HIC
g1/5/1
g1/2/2
g1/0/1
1 NPU
Figure 1-2 Diagram of the service interface numbering rule of the NE40E-X2
13 PSU
14 PSU
11 FIC
12 FIC
9 FIC/HIC
10 FIC/HIC
g8/11/2
g8/9/2
15
8 NPU
FAN
g7/0/1
7 NPU
5 FIC/HIC
6 FIC/HIC
3 FIC
4 FIC
1 MPU
2 MPU
g7/3/2
1.1.3 Interface Views and Prompts

This part describes command views of physical and logical interfaces, and the commands and
prompts used to enter the views of interfaces.
Command views and prompts of physical interfaces supported by the NE80E/40E are shown in
Table 1-1; command views and prompts of logical interfaces are shown inTable 1-2.
Issue 02 (2011-09-10)


Table 1-1 Command line views and prompts of physical interfaces
Issue 02 (2011-09-10)
Interface
Command
Line View
Command
Prompt
Ethernet
interface
Ethernet
interface view
Run the interface

ethernet 1/0/0
command in the
system view.
[HUAWEI-Ethernet1/0/0]
Gigabit
Ethernet
interface
GE interface
view
Run the interface

gigabitethernet
1/0/0 command in
the system view.
[HUAWEIGigabitEthernet1/0/0]
AUX interface
(auxiliary
interface)
AUX interface
view
Run the interface

aux 0/0/1 command
in the system view.
[HUAWEI-Aux0/0/1]
Sync serial
interface
(channelized
serial interface)
Sync serial
interface view
Run the interface

[HUAWEI-Serial1/0/0:1]
serial 1/0/0
[HUAWEI-Serial1/0/0/0:1]
command in the
system view (the
number of a
channelized serial
interface is of fourdimensional or fivedimensional
structure, such as
1/0/0:1 or 1/0/0/0:1).
CE1 interface
CE1 interface
view
Run the controller

e1 1/0/0 command in
the system view.
[HUAWEI-E1 1/0/0]
CT1 interface
CT1 interface
view
Run the controller

t1 1/0/0 command in
the system view.
[HUAWEI-T1 1/0/0]
E3 interface or
CE3 interface
E3 interface
view or CE3
interface view
Run the controller

e3 1/0/0 command in
the system view.
[HUAWEI-E3 1/0/0]
T3 interface
T3 interface
view
Run the controller

t3 1/0/0 command in
the system view.
[HUAWEI-T3 1/0/0]
POS interface
POS interface
view
Run the interface

pos 3/0/0 command
in the system view.
[HUAWEI-Pos 3/0/0]
CPOS
interface
CPOS
interface view
Run the controller

[HUAWEI-Cpos 3/0/0]
cpos 3/0/0 command
in the system view.


Interface
Command
Line View
Command
Prompt
ATM interface
ATM interface
view
Run the interface

atm 2/0/0 command
in the system view.
[HUAWEI-Atm 2/0/0]
Table 1-2 Command line views and prompts of logical interfaces
Issue 02 (2011-09-10)
Interface
Command
Line View
Command
Prompt
Sub-interface
Sub-interface
view
Run the
interface
gigabitethernet
1/0/0.1
command in the
system view.
[HUAWEIgigabitethernet1/0/0.1]
Logic channel
interface
Logical channel
interface view
Run the
interface logicchannel 100
command in the
system view.
[HUAWEI-Logic-Channel100]
Virtual-Ethernet
interface
Virtual-Ethernet
interface view
Run the
interface
virtual-ethernet
1/0/0 command
in the system
view.
[HUAWEI-VirtualEthernet1/0/0]
Eth-Trunk
interface
Eth-Trunk
interface view
Run the
interface ethtrunk 1
command in the
system view.
[HUAWEI-Eth-Trunk1]
Loopback
interface
Loopback
interface view
Run the
interface
loopback 2
command in the
system view.
[HUAWEI-LoopBack2]
NULL interface
NULL interface
view
Run the
interface null 0
command in the
system view.
[HUAWEI-NULL0]
MP-group
interface
MP-group
interface view
Run the
interface mpgroup 3/0/0 in
the system view.
[HUAWEI-Mp-group 3/0/0]


Interface
Command
Line View
Command
Prompt
IP-Trunk
interface
IP-Trunk
interface view
Run the
interface iptrunk 0 in the
system view.
[HUAWEI-Ip-Trunk0]
Tunnel interface
Tunnel interface
view
Run the
interface tunnel
1/0/6 command
in the system
view.
[HUAWEI-Tunnel1/0/6]
MTunnel
interface
MTunnel
interface view
Run the
interface
mtunnel 0 in the
system 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 Technologies

This 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 layer
receives packets from the network layer, and then encapsulates packets into frames to deliver
them to the physical layer.
Link layer protocols supported by the NE80E/40E are described as follows.
Ethernet
The current LAN mainly refers to the Ethernet. The Ethernet is a broadcast network. It is widely
used because it is flexible, simple, and easily extended.
Trunk
Trunk interfaces can be divided into Eth-Trunk and IP-Trunk interfaces. Eth-Trunk interfaces
consist 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 all
member interfaces.
Enhances reliability: When a member link fails, its traffic is automatically switched to other
available links. This enhances the reliability of the entire trunk link.
VLAN
The Virtual Local Area Network (VLAN) divides a physical LAN into several logical sub-nets,
regardless of their physical locations.
Issue 02 (2011-09-10)


Data transmission within a VLAN does not interfere with that in other VLANs. This enhances
the network security.
QinQ
The QinQ technology adds one a layer of 802.1Q tag on the 802.1Q packet to expand the VLAN
space. 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 one
another.
MSTP provides fast convergence and multiple redundant paths for data forwarding, and
implements load balancing of VLAN data during data forwarding.
RRPP
The Rapid Ring Protection Protocol (RRPP) is a link layer protocol specially used for the
Ethernet ring. If the Ethernet ring is complete, RRPP can prevent the broadcast storm caused by
the data loop. When a link on the Ethernet ring is disconnected, RRPP helps to quickly enable
the standby link and then recover the communication channels between nodes on the ring
network.
RPR
The Resilient Packet Ring (RPR) protocol is a Layer 2 protocol. It provides a better solution for
the MAN by taking the advantages of SDH/SONET and other ring networks, and integrating
the 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 also
integrated solution for multiple services.
PPP
The Point-to-Point Protocol (PPP) encapsulates an IP datagram over serial links. It supports the
8-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 also
includes 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 links
together to provide larger bandwidth.
Frame Relay
Frame Relay (FR) is a technology developed in the early 1980s. It is derived from X.25 packet
communication technology.
FR is mainly used for data transfer in the form of frames with a set of procedures. FR implements
logical rather than physical connections.
Issue 02 (2011-09-10)


Multiple logical connections can be multiplexed onto the same physical connection. Thus,
multiple logical channels can be created to achieve bandwidth multiplexing and dynamic
allocation.
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. HDLC
is one of the most widely applied protocols on the data link layer.
HDLC data units (frames) are transmitted through the network and acknowledged by the
receiver. HDLC also manages data flow and data sending intervals.
ATM
Asynchronous Transfer Mode (ATM) takes a cell as the basic unit to implement information
transportation, multiplexing, and exchange. ATM cells come from different sources without any
special 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 are
compatible 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 used
for cable television Hybrid Fiber Coaxial Network (HFC).
1.1.5 Basic Interface Configurations Supported by the NE80E/40E

After familiarizing yourself with basic interface configurations, you can configure common
information for interfaces.
Interface Description
Interface descriptions record the use of interfaces, which helps you memorize the use of
interfaces to rapidly identify interfaces.
Interval for Collecting Interface Traffic Statistics

When you need to know traffic information (including traffic rate) on an interface within a
specific 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 the
CPU, the CPU will become too busy to process normal packets. This may cause the system to
fail to answer real-time demands and fail to implement reliability. Therefore, you need to know
the 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 about
packets sent to the CPU on the main interface, sub-interface, VLAN, or PVC. This helps you
know the number and source of packets sent to the CPU.
Issue 02 (2011-09-10)


1.2 Configuring the Interface Description

This section describes how to configure interface description that helps you to memorize the
functions of interfaces.
1.2.1 Establishing the Configuration Task

Before configuring interface description, familiarize yourself with the applicable environment,
pre-configuration tasks, and required data. This helps you plan and manage interface
descriptions.
Applicable Environment
To maintain many interfaces, you need to describe these interfaces to accurately and rapidly
recognize 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
Interface type and number
Description of the interface
1.2.2 Configuring the Interface Description

Configuring the interface description helps you memorize the functions of interfaces, and thus
you 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 the
corresponding interface view.
l Run the interface interface-type interface-number command to enter the Ethernet, EthTrunk, POS, IP-Trunk, Virtual-Ethernet,or ATMinterface view.
Issue 02 (2011-09-10)

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 using
the 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 Configuration

After the interface description is configured, you need to check whether the configuration is
correct.
Prerequisite
The 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
GigabitEthernet1/0/0
Description
Connected to PE1's GigabitEthernet 1/0/0
1.3 Configuring the Hold-Time Interval After an Interface

Becomes Up/Down

Before configuring the hold-time interval after an interface becomes Up/Down, familiarize
yourself with the applicable environment, complete the pre-configuration tasks, and obtain the
required data. This can help you complete the configuration task quickly and accurately.
Issue 02 (2011-09-10)

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 an
interval.
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
Interface type and interface number
Hold-time interval after an interface becomes Up/Down
1.3.2 Configuring the Hold-Time Interval After an Interface

Becomes Up/Down
Context
Do as follows on the router:
Procedure
Step 1 Run:
system-view

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
Issue 02 (2011-09-10)

12

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

----End

After the hold-time interval after an interface becomes Up/Down is configured, you need to
check 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 [ card
card-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 can
view 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/0
interface GigabitEthernet1/0/0
carrier down-hold-time 100
carrier up-hold-time 10
1.4 Configuring the Interval for Collecting the Statistics of

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

Familiarizing yourself with the applicable environment, pre-configuration tasks, and required
data helps you flexibly configure the interval for collecting the statistics about traffic on the
interface, which helps you to monitor network conditions.
To set the interval for collecting the statistics of traffic on the interface so that you can easily
collect the interface traffic and rate, you can configure the function of collecting the statistics of
traffic on the interface.
In the system view and interface view, you can configure the interval for collecting the statistics
of traffic on the interface. In this manner, you can flexibly collect the statistics of the traffic rate
of all or partial interfaces.
Issue 02 (2011-09-10)

13

NOTE
l In the NE80E/40E, you can configure the interval for collecting the statistics of traffic on the interface
in 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 default
value set in the interface view.
Before configuring the function of collecting the statistics of traffic on the interface, complete
the 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 the
following data.
No.
Data
Interval for collecting the statistics of traffic on the interface
1.4.2 Configuring the Global Interval for Collecting Traffic

Statistics
The global interval for collecting traffic statistics takes effect on all the interfaces that are not
configured with an interval for collecting traffic statistics. This helps you configure the interval
for 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 traffic
statistics:
Procedure
Step 1 Run:
system-view

Step 2 Run:
set flow-stat interval interval
The global interval for collecting traffic statistics is configured.
Issue 02 (2011-09-10)

14

NOTE
The new interval takes effect after the original interval expires. Traffic statistics on logical interfaces are
displayed in the second periodical update after the new interval takes effect. Traffic statistics on physical
interfaces are displayed when the new interval takes effect.
----End
1.4.3 Configuring the Interval for Collecting the Statistics of Traffic

on the Interface
The interval for collecting traffic statistics on an interface is valid for the interface only. After
the interval is configured, you can view the traffic volume and rate on the interface.
Context
Do as follows on the router to be configured with the interval for collecting the statistics of traffic
on the interface:
Procedure
Step 1 Run:
system-view

Step 2 Run:

NOTE
On a main control board, the Ethernet interfaces that are used to connect the network management station
or the multi-frame cannot be configured with the interval for collecting the statistics of traffic on the
interface.
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 are
displayed in the second periodical update after the new interval takes effect. Traffic statistics on physical
interfaces are displayed when the new interval takes effect.
----End
1.4.4 Configuring Traffic Statistics on Sub-Interfaces

You can configure the traffic statistics function on a main interface to collect the traffic statistics
about all sub-interfaces of the main interface.
Context
Do as follows on the router that needs to be configured with traffic statistics:
Issue 02 (2011-09-10)

15

Procedure
Step 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 enable
l 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 a

specific interface.
2.
Run the subinterface traffic-statistics enable command to enable the traffic statistics
function 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 to

enter the view of a specific interface.
2.
Run the statistic enable command to collect the traffic statistics about a specific subinterface.
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 statistic
enable command in the VLAN view.
----End

After configuring traffic statistics on interfaces, you need to check the configuration and ensure
that the configuration is correct.
Prerequisite
Run the following commands to check the previous configuration.
Procedure
l
Run the display current-configuration configuration system command to check the

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

statistics of traffic on an interface.
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 the
statistics of incoming traffic and outgoing traffic.
Issue 02 (2011-09-10)

16

<HUAWEI> display interface gigabitethernet 2/0/1.1

GigabitEthernet2/0/1.1 current state : UP
Line protocol current state : UP
Last up time: 2008-02-18, 06:50:38
Description: GigabitEthernet2/0/1.1 Interface
Route Port,The Maximum Transmit Unit is 1500
Internet Address is 12.1.1.1/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fcd4-7aad
Encapsulation 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,
0 errors,0 drops
# Run the display current-configuration configuration system command. If the global interval
for collecting the traffic statistics is displayed, it means that the configuration succeeds. Run the
display interface command, you can view that after the global interval for collecting the traffic
statistics is successfully configured, the interval for collecting the traffic statistics on all the
interfaces whose interval adopts the default value changes to the global interval for collecting
the 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-Trunk
Eth-Trunk1 current state : UP
Last up time: 2008-04-18, 14:00:30
Description: Eth-Trunk1 Interface
Route Port,Hash arithmetic : According to flow,The Maximum Transmit Unit is 1500
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc7f-7258
Physical is ETH_TRUNK
0 errors,0 drops
0 errors,0 drops
----------------------------------------------------PortName
Status
Weight
----------------------------------------------------GigabitEthernet2/0/2
UP
1
----------------------------------------------------The Number of Ports in Trunk : 1
The Number of UP Ports in Trunk : 1
Eth-Trunk2 current state : UP
Last up time: 2008-04-21, 11:16:47
Description: Eth-Trunk2 Interface
Route Port,Hash arithmetic : According to flow,The Maximum Transmit Unit is 1500
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc7f-7258
Issue 02 (2011-09-10)

17

Physical is ETH_TRUNK
0 errors,0 drops
0 errors,0 drops
----------------------------------------------------PortName
Status
Weight
----------------------------------------------------GigabitEthernet2/0/4
UP
1
----------------------------------------------------The Number of Ports in Trunk : 1
The Number of UP Ports in Trunk : 1
1.5 Enabling the Statistics for Packets Sent to the CPU

Enabling the statistics for packets sent to the CPU helps you know the type, number, and source
of packets sent to the CPU.

Familiarizing yourself with the applicable environment, pre-configuration tasks, and required
data of the statistics for packets sent to the CPU helps you monitor network traffic, analyze traffic
sources, and protect the device from attacks.
CPU resources are precious. To know the accurate number and source of packets sent to the
CPU, you need to enable the statistics for packets sent to the CPU. Then, you can view the
statistics 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 Globally
Viewing the statistics for packets sent to the CPU globally helps you know the number and
source of packets sent to the CPU.
Issue 02 (2011-09-10)

18

Context
CPU resources are precious. After enabling the statistics for packets sent to the CPU, you can
know 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 1 Run:
system-view

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 CPU
Through the VLAN
Enabling the statistics for packets sent to the CPU from VLANs of interfaces helps you know
information about packets in VLANs.
Context
Do as follows on the device that requires the statistics for packets sent to the CPU through the
VLAN:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
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 the
statistics for packets sent to the CPU.
Issue 02 (2011-09-10)

19

After the configurations, you can view the statistics by running different commands according
to different situations:
l If the VLAN is the default VLAN of the interface or both the default VLAN and the Trunk
VLAN, the statistics for packets sent to the CPU are based on the interface. In this case, you
can use the display cpu-packet statistics interface interface-type interface-number all
command to view the statistics.
l Otherwise, the statistics are based on both the interface and the VLAN. You can use the
display cpu-packet statistics interface interface-type interface-number vlan vlan-id
command to view the statistics.
----End
1.5.4 (Optional) Enabling the Statisitcs for Packets Sent to the CPU
Through the PVC
Enabling the statistics for packets sent to the CPU from PVCs of ATM interfaces helps you
know 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 the
PVC:
Procedure
Step 1 Run:
system-view

Step 2 Run:

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 the
statistics for packets sent to the CPU.
----End
Issue 02 (2011-09-10)

20


After the statistics for packets sent to the CPU is enabled, you need to check whether the
configuration 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.
Prerequisite
The configurations are completed for enabling the statistics for packets sent to the CPU.
Procedure
l
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.
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 of
the specified interface.
Run the display cpu-packet statistics interface interface-type interface-number vlan

vlan-id command to view the statistics for packets sent to the CPU from the specified VLAN
of the specified interface.
Run the display cpu-packet statistics slot { all | slot-id } command to view the statistics
for packets sent to the CPU from all interfaces in the specified slot.
----End
Example
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.
<HUAWEI> display cpu-packet statistics interface gigabitethernet 1/0/0 all
GigabitEthernet1/0/0: 8 packets, 1099 bytes
1.6 Configuring a Signal Sending Delay on an Interface

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

Before configuring a signal sending delay on an interface, familiarize yourself with the
applicable environment, complete the pre-configuration tasks, and obtain the required data. This
can help you complete the configuration task quickly and accurately.
When the router configured with VRRP or E-APS services is dual-homed to non-Huawei
devices, the router cannot control traffic switchover between interfaces on the non-Huawei
devices. In this case, link switchover on the router is probably asynchronous with that on the
Issue 02 (2011-09-10)

21

non-Huawei devices. If the interface on the router sends a signal immediately after being
initialized, certain data is probably discarded.
If an interface on the router is directly connected to a non-Huawei device, when the router is
restarted, the interface sends a signal to the peer immediately after being initialized, which
probably causes data loss before configurations of the router are restored.
To prevent this problem, you can configure a signal sending delay on the interface.
Before configuring a signal sending delay on an interface, complete the following task:
l
Powering on the router and ensuring a successful self-check
Data Preparation
To configure a signal sending delay on an interface, you need the following data.
No.
Data
Delay after which an interface sends a signal after being initialized
1.6.2 Configuring a Signal Sending Delay on an Interface

Context
When the router configured with VRRP or E-APS services is dual-homed to non-Huawei
devices, the router cannot control traffic switchover between interfaces on the non-Huawei
devices. In this case, link switchover on the router is probably asynchronous with that on the
non-Huawei devices. If the interface on the router sends a signal immediately after being
initialized, certain data is probably lost.
If an interface on the router is directly connected to a non-Huawei device, when the router is
restarted, the interface sends a signal to the peer immediately after being initialized, which
probably 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 the
router.
Procedure
Step 1 Run:
system-view

Step 2 Run:
Issue 02 (2011-09-10)

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 signal
sending delay.
----End

After a signal sending delay is configured on an interface, you can restart the board that the
interface belongs to and then check the configured signal sending delay and how many
milliseconds are left before the interface sends a signal to the peer.
Prerequisite
A signal sending delay is configured on an interface and the board that the interface belongs to
is restarted.
Procedure
Step 1 Run the display port-tx-enabling-delay command to check the configured signal sending delay
on 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/0
GigabitEthernet 1/0/0 setted port-tx-enabling delay time is: 100 ms
GigabitEthernet 1/0/0 remanent time of enabling port-tx is: 20 ms
1.7 Enabling the Alarm Function on an Interface

alarms and the system performance is thus degraded. To solve this problem, you can enable the
alarm function on an interface.

Before enabling the alarm function on an interface, familiarize yourself with the applicable
environment, complete the pre-configuration tasks, and obtain the required data. This can help
you complete the configuration task quickly and accurately.
alarms. The system performance is thus degraded. In this manner, you can set the threshold that
triggers the alarm for interfaces. When the number of errors exceeds the set threshold, an alarm
Issue 02 (2011-09-10)

23

is generated. You can then take measures for troubleshooting to ensure the normal transmission
of 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
Interface type and interface number
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 Interface

alarms. To solve this problem can configure the type of alarms to be process by the system, the
alarm threshold, and the interval for sending alarm messages to the NMS to release the burden
of the system.
Context
Do as follows on the interface connected to the transmission device:
Procedure
Step 1 Run:
system-view

Step 2 Run:
snmp-agent trap enable port { crc-error-rising | sdh-error-rising | broadcastthreshold | 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-errorrising is set.
l To enable the alarm function for Synchronous Digital Hierarchy (SDH) errors, sdh-errorrising is set.
l To enable the alarm function for broadcast suppression, broadcast-threshold is set.
Issue 02 (2011-09-10)

24

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

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
NOTE
Interfaces 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 for
CRC errors is 10 seconds; the alarm threshold for SDH errors is 3 and the interval for generating
an alarm for SDH errors is 10 seconds; the alarm threshold for the bandwidth utilization of the
incoming traffic is 100%; the alarm threshold for the bandwidth utilization of the outgoing traffic
is 100%.
----End

After the alarm function is enabled on an interface, you need to check the configuration and
ensure that the configuration is correct.
Prerequisite
Run 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 incoming
traffic, and bandwidth utilization of the outgoing traffic on POS 1/0/0.
<HUAWEI>display current-configuration interface pos 1/0/0
interface Pos1/0/0
link-protocol ppp
undo shutdown
trap-threshold crc-error 1000 interval-second 600
Issue 02 (2011-09-10)

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 and
bandwidth utilization of the outgoing traffic on GE 1/0/0.
<HUAWEI>display current-configuration interface GigabitEthernet1/0/0
interface GigabitEthernet1/0/0
trap-threshold input-rate 80
trap-threshold output-rate 80
1.8 Maintaining Interface Basic Configuration

Clear interface statistics and monitoring interface information are maintenance tools that help
you know interface status.
1.8.1 Clearing Statistics

After interface statistics are cleared, you can start the statistics again, which helps you know the
traffic volume and rate on interfaces at any time.
Context
CAUTION
Statistics cannot be restored after you clear it. So, confirm the action before you use the
command.
To clear the interface statistics collected through the NMS or with the display interface
command, run the following reset counters commands in the user view. After that, you can clear
the 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 about
the NMS.
Procedure
l
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.
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.
Run the following command in the user view to clear the statistics of the packets sent to
the CPU.
Run the reset cpu-packet statistics interface interface-type interface-number all
command to clear the statistics of all the packets sent to the CPU through the specified
interface.
Issue 02 (2011-09-10)

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 the
specified PVC on the specified interface.
Run the reset cpu-packet statistics interface interface-type interface-number vlan
vlan-id command to clear the statistics of all the packets sent to the CPU through the
specified VLAN on the specified interface.
Run the reset cpu-packet statistics slot { all | slot-id } command to clear the statistics
of all the packets sent to the CPU in all slots.
----End
1.8.2 Monitoring Interface Information

Monitoring interface statistics helps you know the traffic volume and rate on interfaces, and thus
analyze network conditions.
Context
Running the display interface command, you can view the current status and description of the
interface and the statistics of the received and sent packets. Run the following commands in the
user view.
Procedure
l
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.
Run the display interface-statistics { interface-type interface-number } &<1-5>

[ interval interval ] [ times times ] or display interface-statistics batch interface-type
interface-number1 [ to interface-number2 ] [ interval interval ] [ times times ] command
in any view to check statistics about traffic on the interface.
Run the display interface brief command in any view to check the brief information about
all the interfaces on the device, including the physical status, protocol status, and bandwidth
utilization of the interface.
Run the display ip interface [ interface-type interface-number ] command in any view to

check the IP configuration of the interface.
Run one of the following commands in any view to check brief IP configuration of the
interface.
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 ] ]
Run the display cpu-packet statistics slot { all | slot-id } command in any view to check
the statistics for packets sent to the CPU from all interfaces in the specified slot.
Run the display cpu-packet statistics interface interface-type interface-number all

command in any view to check the statistics for packets sent to the CPU from the specified
interface.
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 the
specified PVC of the specified interface.
Issue 02 (2011-09-10)

27

Run the display cpu-packet statistics interface interface-type interface-number vlan

vlan-id command in any view to check the statistics for packets sent to the CPU from the
specified VLAN of the specified interface.
Run the display interface phy-option interface-type interface-number command in user

view to check the physical attributes of the specified interface.
----End
Issue 02 (2011-09-10)

28

2 Logical Interface Configuration
Logical Interface Configuration
About This Chapter

Learning interface types, configuration procedure, and configuration examples of logical
interfaces helps you make full use of logical interfaces, thus improving the system performance.
2.1 Logical Interface Configuration Overview
This section describes main types of logical interfaces.
2.2 Creating Sub-interfaces
This part describes how to create sub-interfaces.
2.3 Configuring Logical Channel Interfaces
If you need to provide the backup function for an interface or take an FR VC (or the VC of
another type) as a main interface or backup interface, you should create a logic channel interface.
2.4 Configuring Virtual-Template Interfaces
Learning 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 Interfaces
Learning 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 Interface
Loopback interfaces always remain in the Up state once created and have the loopback function.
2.7 Configuring a Null Interface
All the packets sent to null interfaces are discarded.
2.8 Configuration Examples
This section provides examples to show how to configure logical interfaces.
Issue 02 (2011-09-10)

29

2.1 Logical Interface Configuration Overview

This section describes main types of logical interfaces.
2.1.1 Introduction to Logical Interfaces

Logical 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 only
through manual configuration. Logical interfaces include sub-interfaces, Eth-Trunk interfaces,
VLANIF interfaces, Virtual-Ethernet interfaces, loopback interfaces, null interfaces, MP-Group
interfaces,IP-Trunk interfaces,Tunnel interfaces and MTunnel interfaces.
NOTE
l For the configurations of Eth-Trunk interfaces, VLANIF interfaces, and VE interfaces logical
interfaces, 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 HUAWEI
NetEngine80E/40E Router Configuration Guide - WAN Access.
l For the details of the tunnel interface, refer to "VPN Tunnel" in the HUAWEI NetEngine80E/40E
Router Feature Description - VPN. For the configuration of the tunnel interface, refer to the chapter
"VPN Tunnel Management Configuration" in the HUAWEI NetEngine80E/40E Router Configuration
Guide - VPN.
l For the details of MTI interfaces, refer to "Multicast VPN Configuration" in the HUAWEI
NetEngine80E/40E Router Configuration Guide - IP Multicast.
2.1.2 Features of the Logical Interfaces in the NE80E/40E

This part describes the applicable environment of logical interfaces.
NOTE
ATM sub-interfaces, FR sub-interfaces, and virtual-template (VT) interfaces are not supported on the
NE80E/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 and

multiple remote ends.
Logical channel interface: It is mainly used in interface backup.
Virtual-Ethernet (VE) interface: It is mainly used when other data link layer protocols need
to be carried by the Ethernet protocol.
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.
Null interface: It is mainly used in route filtering because any network packets sent to this
interface are discarded.
2.2 Creating Sub-interfaces

This part describes how to create sub-interfaces.
Issue 02 (2011-09-10)

30

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

Learning the applicable environment, pre-configuration tasks, and required data helps you create
sub-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 following
physical interfaces support sub-interfaces:
l
Ethernet interfaces
FR interfaces
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 HUAWEI
NetEngine80E/40E Router Configuration Guide - LAN Access & MAN Access.
Logical interfaces such as Eth-Trunk interfaces and VE interfaces also support the creation of
sub-interfaces because these logical interfaces have the characteristics of the FR or Ethernet
interface. 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.
Correctly connecting the physical interface of the sub-interface.
Data Preparation
To create the sub-interface, you need the following data.
No.
Data
Number of the main interface
Number of the sub-interface
2.2.2 Creating ATM Sub-interfaces

Creating ATM sub-interfaces realizes P2MP connections on ATM links.
Issue 02 (2011-09-10)

31

Context
For 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 1 Run:
system-view

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 the
shutdown and undo shutdown commands on the main interface needs to be 15 seconds at least.
----End
2.2.3 Creating FR Sub-interfaces

Creating FR sub-interfaces realizes P2P connections on FR links.
Context
For the detail about FR sub-interface configuration, refer to "Frame Relay Configuration" in the
HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
link-protocol fr [ ietf | nonstandard ]
The link layer protocol of the interface is configured as FR.

Step 4 Run:
quit
Issue 02 (2011-09-10)

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, a
main 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 the
shutdown 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 interface
l IP address which is not in the same network segment as the main interface
l Virtual circuit of the sub-interface
----End

After sub-interfaces are created, you need to check whether the configuration is correct. In
addition, you can view information about sub-interfaces.
Prerequisite
The configurations of the creating sub-interfaces function are complete.
Procedure
l
Run the display atm interface [ atm interface-number ] command to check the status of
the ATM sub-interface.
Run the display fr interface [ interface-type interface-number ] command to check the

status of the FR sub-interface.
----End
Example
Run the display atm interface command, and you can view that the link layer protocol status
of the ATM sub-interface is Up and the type of the sub-interface is P2MP. Simultaneously, you
can also view PVC information, address mapping, and the statistics of the received and sent
packets on this sub-interface.
<HUAWEI> display atm interface atm 1/0/0.2
ATM 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 FR
sub-interface is Up and the type of the sub-interface is P2MP.
Issue 02 (2011-09-10)

33

<HUAWEI> display fr interface

Serial1/0/0, DTE, physical up, protocol up
Serial1/0/0.2, multi-point, protocol up
2.3 Configuring Logical Channel Interfaces

If you need to provide the backup function for an interface or take an FR VC (or the VC of
another type) as a main interface or backup interface, you should create a logic channel interface.

This part describes the applicable environment, pre-configuration tasks, and required data for
configuring logical channel interfaces.
Create a logic channel interface and configure it to provide an interface with backup function
or take an FR (or other) VC as a main interface or backup interface.
Before configuring a logical channel interface, power on the router and start the router normally.
Data Preparation
To configure the logical channel interface, you need the following data.
No.
Data
Number of the logical channel interface
2.3.2 Creating a Logical Channel Interface

Logical channel interfaces can be created only on the main board.
Context
You can dynamically create or delete the logical channel interface. Once the logical channel
interface is created, it remains in the Up state, till you delete it.
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface logic-channel
interface-number
A logical channel interface is configured.

Issue 02 (2011-09-10)

34

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

After a logical channel interface is configured, you need to check whether the configuration is
correct. In addition, you can view the status of the logical channel interface.
Prerequisite
The 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 and
configuration of the logical channel interface.
----End
Example
Run the display interface logic-channel command. If the status and configuration of the logical
channel interface are displayed, it means the configuration succeeds.
<HUAWEI> display interface Logic-Channel
Logic-Channel0 current state : UP
Line protocol current state :UP (spoofing)
Description: Logic-Channel0 Interface
Current 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 Interfaces

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

When PPP is required to bear other link layer protocols, VT interfaces are created to realize the
intercommunication.
The Virtual-Template (VT) interface is used in VPN, MP and ATM applications. The system
creates 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 only
supports IP.
Issue 02 (2011-09-10)

35

CAUTION
l 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 properly
Configuring the physical interface
Data Preparation
To configure a VT interface, you need the following data.
No.
Data
Number of the VT interface
IP address of the VT interface
Number of maximum links for sending multicast or broadcast packets supported by

the VT interface
2.4.2 Configuring the IP Address of a VT Interface

When VT interfaces are used to communicate with other devices, you need to configure IP
addresses for the VT interfaces.
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface virtual-template vt-number
A VT interface is created and the VT interface view is displayed.

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 ]
Issue 02 (2011-09-10)

36

The IP address of the VT interface is configured.

----End
2.4.3 Setting the Maximum Number of Links Supported by a VT

Interface
When a VT interface has a large number of links, the system performance is affected if multicast
or broadcast packets are sent through every link. After the maximum number of links supported
by a VT interface is configured, when the number of links exceeds the upper limit, multicast or
broadcast packets are discarded, which ensures that the system runs normally.
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface virtual-template
vt-number
A VT interface is created and the VT interface view is displayed.

Step 3 Run:
broadcast-limit link
number
The maximum number of links supported by the VT interface for sending multicast or broadcast
packets is configured.
The multicast or broadcast packets which are sent out from each link may affect the system
performance if there are too many links in the VT interface.
Using the broadcast-limit link command, you can restrict the packets since the packets are
dropped 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

After VT interfaces are configured, you need to check whether the configuration is correct. In
addition, you can view the statistics about VT interfaces.
Prerequisite
The configurations of Virtual-Template interfaces are complete.
Procedure
l
Issue 02 (2011-09-10)
Run the display interface virtual-template [ vt-number ] command to check the status of
a VT interface.
37

Run the display virtual-access [ va-number | peer peer-address | slot slot-id | user username | 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 is
displayed, it means the configuration succeeds.
<HUAWEI> display interface Virtual-Template 0
Virtual-Template0 current state : UP
Description: Virtual-Template0 Interface
Link layer protocol is PPP
LCP initial
Physical is None, baudrate is 64000 bps
QoS max-bandwidth : 64 Kbps
Output queue : (Urgent queue : Size/Length/Discards) 0/50/0
Output queue : (Protocol queue : Size/Length/Discards) 0/1000/0
Output queue : (FIFO queue : Size/Length/Discards) 0/256/0
Statistics last cleared: 2008-08-02 15:32:27
Realtime 0 seconds input rate 0 bits/sec, 0 packets/sec
Realtime 0 seconds output rate 0 bits/sec, 0 packets/sec
0 unicast,0 broadcast,0 multicast
0 errors,0 drops,0 unknownprotocol
0 errors,0 drops
Run the display virtual-access command. If the status of a VA interface is displayed, it means
the configuration succeeds. For example:
<HUAWEI> display virtual-access slot 1
----------------Slot 1---------------Virtual-Template1:0 current state : UP
Last line protocol up time: 2007-11-08, 11:21:34
Description: Virtual-Template1:0 Interface
Link layer protocol is PPP
LCP opened, MP opened, IPCP opened
Physical is MP
Issue 02 (2011-09-10)

38

0 errors,0 drops
2.5 Configuring Virtual-Ethernet Interfaces

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

configuring VE interfaces.
Virtual-Ethernet (VE) interfaces are mainly used in PPPoEoA and IPoEoA. VE interfaces can
also 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 the
chapter "Ethernet Interface Configuration" in the HUAWEI NetEngine80E/40E Router
Configuration Guide - LAN Access & MAN Access.
In addition, VE interfaces support the following features:
l
Routing protocols
Switching Layer 2 port through the portswitch command
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
Number of the VE interface
MAC address of the VE interface
2.5.2 Creating a VE Interface

Before creating a VE interface, ensure that the physical board in the corresponding slot must
exist.
Issue 02 (2011-09-10)

39

Procedure
Step 1 Run:
system-view

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, the
serial number is ranging from 0 to 1023.
If the binding relationship between a VE interface and the permanent virtual channel (PVC) that
bears PPPoEoA or IPoEoA is established, you can successfully delete this VE interface only
when you unbind the VE interface from the PVC.
----End

After VE interfaces are configured, you need to check whether the configuration is correct. In
addition, you can view the statistics about VE interfaces.
Prerequisite
The 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 VE
interface.
----End
Example
Run the display interface virtual-ethernet command. If the configuration and status of the
specified VE interface are displayed, it means that the configuration succeeds. For example:
<HUAWEI> display interface Virtual-Ethernet
Virtual-Ethernet1/0/0 current state : DOWN
Line protocol current state : DOWN
Description: Virtual-Ethernet1/0/0 Interface
Internet protocol processing : disabled
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc99-9999
Virtual-Ethernet2/0/0 current state : UP
Last line protocol up time: 2007-11-03, 17:24:24
Description: Virtual-Ethernet2/0/0 Interface
Issue 02 (2011-09-10)

40


IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc99-9999
Carrier Layer: 1 PVC total, 1 map up, 0 map down
0 packets input, 0 bytes, 0 drops
5 packets output, 300 bytes, 0 drops
2.6 Configuring a Loopback Interface

Loopback interfaces always remain in the Up state once created and have the loopback function.

Learning the applicable environment, pre-configuration tasks, and required data for configuring
loopback interfaces helps you know the characteristics of loopback interfaces.
As the loopback interface always remains in the Up state once created and has the loopback
characteristic, 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.
Controlling the access interface and filtering log based on the IP address simplify
information.
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, often
more than one link can reach the same neighbor. In this situation, using the loopback interface
as 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.
Issue 02 (2011-09-10)
No.
Data
Number of the loopback interface
IP address of the loopback interface

41

2.6.2 Creating a Loopback Interface and Configuring Its IP Address

In most cases, you need to assign IP addresses to loopback interfaces, and then use the loopback
interfaces that are always Up to communicate with other devices.
Procedure
Step 1 Run:
system-view

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

After loopback interfaces are configured, you need to check whether the configuration is correct.
In addition, you can view the statistics about loopback interfaces.
Prerequisite
The configurations of a loopback interface are complete.
Procedure
Step 1 Run the display interface loopback [ loopback-number ] command to check the status of a
loopback interface.
----End
Example
Run the display interface loopback command, and you can view that the link layer protocol
status of the interface is Up.
<HUAWEI> display interface loopback 6
LoopBack6 current state : UP
Description: LoopBack6 Interface
Physical is Loopback
Issue 02 (2011-09-10)

42


0 errors
0 errors
2.7 Configuring a Null Interface

All the packets sent to null interfaces are discarded.

This part describes the applicable environment, pre-configuration tasks, and data preparation
for configuring null interfaces.
The 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 be
filtered 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 the
192.101.0.0 network segment.
[HUAWEI] ip route-static 192.101.0.0 255.255.0.0 NULL 0
Before configuring a Null interface, power the router and start the router normally.
Data Preparation
None.
2.7.2 Entering the Null Interface View

The system automatically creates a Null interface NULL0.
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface null 0
The null interface view is displayed.

Issue 02 (2011-09-10)

43

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

After null interfaces are configured, you need to check whether the configuration is correct. In
addition, you can view statistics about null interfaces.
Prerequisite
The 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
Example
Run the display interface null command, and you can view that the status of the null interface
is Up.
<HUAWEI> display interface null 0
NULL0 current state : UP
Description: NULL0 Interface
Internet protocol processing : disabled
Physical is NULL DEV
0 errors,0 drops

This section provides examples to show how to configure logical interfaces.
2.8.1 Example for Configuring the Sub-interface

This example shows how to realize the P2MP connection by configuring FR sub-interfaces.
Networking Requirements
As shown in Figure 2-1:
Issue 02 (2011-09-10)

44

POS 1/0/0 of Router A is connected with Router B and Router C through the public FR
network.
A sub-interface is configured on POS 1/0/0 on Router A so that LAN 1 can access both
LAN 2 and LAN 3 through POS 1/0/0.
Figure 2-1 Networking diagram of configuring the sub-interface

LAN 2: 129.10.0.0/16
Router B
POS1/0/0
202.38.160.2
RouterA
POS1/0/0.1
202.38.160.1
DLCI=50
DLCI=70
Frame Relay
network
POS1/0/0.2
202.38.161.1
DLCI=60
LAN1: 129.9.0.0/16
DLCI=80
POS1/0/0
202.38.161.2
RouterC
LAN3: 129.11.0.0/16
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
IP addresses of two sub-interfaces on Router A
DLCIs that connect Router A to the FR network
Network addresses of three LANs
On Router B and Router C, the IP addresses of the interfaces that access the FR network
Issue 02 (2011-09-10)

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 be
configured 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 Files
l
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
#
Issue 02 (2011-09-10)

46

return
Configuration file of Router B

#
sysname RouterB
#
interface Pos1/0/0
link-protocol fr
fr 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
Configuration file of Router C

#
sysname RouterC
#
interface Pos1/0/0
link-protocol fr
fr 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 Interface

VT interfaces are mainly used in the VPN and WAN configurations.
Context
For configuration example of the VT in VPN, refer to the HUAWEI NetEngine80E/40E Router
Configuration Guide - VPN.
2.8.3 Example for Configuring the Loopback Interface

This example shows how to configure the IP unnumbered function on loopback interfaces.
After a loopback interface is configured with IP address, it can work as the lending party in the
IP unnumbered function. Loopback interface can use 32-bit mask.
Figure 2-2 Networking diagram of configuring the loopback interface
Loopback1
10.1.1.1/32
POS1/0/0
RouterA
Issue 02 (2011-09-10)
POS1/0/0
10.1.1.2/30 RouterB

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 number
IP address of the loopback interface
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] 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] 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/0
Pos1/0/0 current state : UP
Lin protocol current state : UP
Last line protocol up time: 2007-11-03 15:42:33 UTC-08:00
Description: Pos1/0/0 Interface
Route 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 Router
B.
----End
Issue 02 (2011-09-10)

48

Configuration files
l
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
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
Issue 02 (2011-09-10)

49

3 Interface Board Intermixing Configuration
Interface Board Intermixing Configuration
About This Chapter

When the interface boards and main board of different FIB route prefix capacities are plugged
in the same device, certain traffic is dropped because FIB entries of the interface boards and
main board are inconsistent. This chapter describes how to configure board intermixing to
address the problem.
NOTE
The interface board intermixing feature is not supported on the NE80E/40E-X1&X2 series because the
NE80E/40E-X1 and the NE80E/40E-X2 supports NPUs of one specification of FIB route prefix capacity.
3.1 Interface Board Intermixing Configuration Overview

This section describes how to process FIB route prefixes received on interface boards.
3.2 Configuring the Public FIB Policy
The public IPv4 FIB policy or public IPv6 FIB policy enables interface boards to receive FIB
route prefixes of the public network.
3.3 Configuring the VPN FIB Policy
The VPN IPv4 FIB policy or VPN IPv6 FIB policy enables interface boards to receive FIB route
prefixes of a certain VPN.
3.4 Configuring the Policy of Discarding All the FIB Entries
The policy of discarding all IPv4 FIB entries and IPv6 FIB entries disables interface boards from
receiving any FIB route prefix.
3.5 Configuring Overload Suspension Recovery
When an interface board is in the overload suspension state, you need to perform overload
suspension recovery. In this manner, the interface board returns to the normal state.
3.6 Configuring Overload Forwarding Recovery
When the interface board is in the overload forwarding state, you need to perform overload
forwarding recovery on the interface board to restore the interface board to the normal state.
This section provides the configuration examples of interface board intermixing to show how
to configure FIB policies.
Issue 02 (2011-09-10)

50

3.1 Interface Board Intermixing Configuration Overview

This section describes how to process FIB route prefixes received on interface boards.
3.1.1 Introduction to Interface Board Intermixing

When inserting the main control board with large capacity of FIB route prefixes together with
the interface board with small capacity of FIB route prefixes into the same router, you can adopt
the 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 Huawei
technical 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 the
unneeded FIB entries to reduce the FIB entries delivered to the FIB module of the interface
board.
2.
The interface board judges whether the total number of received FIB route prefixes exceeds
the 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 suspension
When one FIB module is overloaded, the interface board automatically shuts down
all the physical interfaces on this interface board. The FIB module of the interface
board changes to the overload suspension state.
Overload forwarding
When one FIB module is overloaded, this module changes to the overload
forwarding state. This does not affect the status of another module.
3.1.2 Features of Interface Board Intermixing in the NE80E/40E

The interface board in the overload suspension or overload forwarding state cannot automatically
return 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 board
cannot automatically return to the normal state.
After the active/standby switchover, the FIB module status and running status of the interface
board, which are stored on the main control board, keep unchanged.
3.2 Configuring the Public FIB Policy

The public IPv4 FIB policy or public IPv6 FIB policy enables interface boards to receive FIB
route prefixes of the public network.
Issue 02 (2011-09-10)

51


configuring a public FIB policy.
When the interface board on a router uses only the public forwarding entries of the main control
board, you can use the interface board with less FIB route prefix capacity than the main control
board. In such case, this interface board must be configured to receive only the public forwarding
entries delivered by the main control board.
Through the FIB policy, you can insert the interface board of a different FIB route prefix capacity
together with the main control board into the same router. FIB entries can be customized and
delivered as required. This ensures that the FIB entries delivered by the main control board can
be correctly processed.
Before configuring the public FIB policy, complete the following tasks:
l
Powering on and starting the router normally.
Connecting the interface and configuring the physical parameters of the interface.
Data Preparation
To configure the public FIB policy, you need the following data.
No.
Data
Interface board number
3.2.2 Configuring the Public IPv4 FIB Policy

When interface boards need to receive public IPv4 FIB route prefixes, you can configure the
public IPv4 FIB policy.
Context
When the interface board needs to receive the IPv4 FIB entries delivered by the main control
board, do as follows on the router:
Procedure
Step 1 Run:
system-view

Step 2 Run:
apply fib-policy public slot slot-id
The public IPv4 FIB policy is configured on the interface board.

Issue 02 (2011-09-10)

52

NOTE
After the configuration, you need to refresh the IPv4 FIB policy to ensure that the newly configured policy
takes 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 interface
board.
----End
3.2.3 Configuring the Public IPv6 FIB Policy

When interface boards need to receive public IPv6 FIB route prefixes, you can configure the
public IPv6 FIB policy.
Context
When the interface board needs to receive the IPv6 FIB entries delivered by the main control
Procedure
Step 1 Run:
system-view

Step 2 Run:
apply ipv6 fib-policy public slot slot-id
The public IPv6 FIB policy is configured on the interface board.

NOTE
takes effect.
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 interface
board.
----End

After 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.
Prerequisite
The configurations of the configuring the public FIB policy function are complete.
Issue 02 (2011-09-10)

53

Procedure
l
Run the display fib-policy slot slot-id command to check the FIB policy applied to the
IPv4 FIB module on the interface board.
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.
Run the display fib [ slot-id ] statistics allcommand to check the FIB statistics of the IPv4
FIB module on the interface board.
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 public IPv4 FIB policy applied to
the 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 applied
to 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 and
the FIB policy statistics of the IPv4 FIB module on the specified interface board.
[HUAWEI]
IPv4 FIB
IPv4 FIB
IPv4 FIB
IPv4 FIB
IPv4 FIB
display fib 1 statistics all

Route Prefix Capacity : 1000
Total Route Prefix Count : 4, Entry Count
Public Route Prefix Count :4, Entry Count
Vpn-instance VPNB Route Prefix Count : 0,
Vpn-instance VPNA Route Prefix Count : 0,
: 4
: 4
Entry Count : 0
Entry Count : 0
Run the display ipv6 fib statistics all command, and you can view the FIB route prefix capacity
and the FIB policy statistics of the IPv6 FIB module on the specified interface board.
[HUAWEI]
IPv6 FIB
IPv6 FIB
IPv6 FIB
display ipv6 fib 1 statistics all

Total Route Prefix Count :1,Entry Count : 1
Public Route Prefix Count :1,Entry Count : 1
3.3 Configuring the VPN FIB Policy

The VPN IPv4 FIB policy or VPN IPv6 FIB policy enables interface boards to receive FIB route
prefixes of a certain VPN.

configuring the VPN FIB policy.
Issue 02 (2011-09-10)

54

When the interface board on a router uses only the VPN forwarding entries of the main control
board, you can use the interface board with less FIB route prefix capacity than the main control
board. Configure this interface board to receive only the VPN forwarding entries delivered by
the 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
Type and name of the VPN instance
3.3.2 Configuring the VPN IPv4 FIB Policy

When interface boards need to receive VPN IPv4 FIB route prefixes, you can configure the VPN
IPv4 FIB policy.
Context
When the interface board needs to receive the IPv4 VPN forwarding entries delivered by the
main control board, do as follows on the router:
Procedure
Step 1 Run:
system-view

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.

Issue 02 (2011-09-10)

55

NOTE
takes effect.
Step 3 Run:
refresh fib slot
slot-id
The IPv4 FIB policy is refreshed so that this VPN IPv4 FIB policy is applied to the interface
board.
----End
3.3.3 Configuring the VPN IPv6 FIB Policy

When interface boards need to receive VPN IPv6 FIB route prefixes, you can configure the VPN
IPv6 FIB policy.
Context
When the interface board needs to receive the IPv6 VPN forwarding entries delivered by the
main control board, do as follows on the router:
Procedure
Step 1 Run:
system-view

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
takes effect.
Step 3 Run:
slot-id
The IPv6 FIB policy is refreshed so that this VPN IPv6 FIB policy is applied to the interface
board.
----End

After 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.
Prerequisite
The configurations of the configuring the VPN FIB policy function are complete.
Issue 02 (2011-09-10)

56

Procedure
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 the VPN IPv4 FIB policy applied to
the specified interface board.
FIB-policy:
vpn route: VPNA
Run the display ipv6 fib-policy command, and you can view the VPN IPv6 FIB policy applied
to the specified interface board.
FIB-policy:
vpn route: VPN6A
Run the display fib statistics all command, and you can view the IPv4 FIB route prefix capacity
and the IPv4 FIB policy statistics of the specified interface board.
[HUAWEI]
IPv4 FIB
IPv4 FIB
IPv4 FIB
IPv4 FIB
IPv4 FIB

Total Route Prefix Count :7, Entry Count : 7
Public Route Prefix Count : 4, Entry Count : 4
Vpn-instance VPNB Route Prefix Count :3, Entry Count : 3
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 prefix
capacity and the IPv6 FIB policy statistics of the specified interface board.
[HUAWEI] display ipv6 fib 2 statistics all
IPv6 FIB Route Prefix Capacity : 1000
IPv6 FIB Total Route Prefix Count :1, Entry Count : 1
IPv6 FIB Public Route Prefix Count :1, Entry Count : 1
IPv6 Vpn-instance VPN6A Route Prefix Count :0, Entry Count : 0
3.4 Configuring the Policy of Discarding All the FIB Entries

The policy of discarding all IPv4 FIB entries and IPv6 FIB entries disables interface boards from
receiving any FIB route prefix.

configuring the policy of discarding all IPv4 FIB entries and IPv6 FIB entries.
Issue 02 (2011-09-10)

57

When the interface board on a router does not use the IPv4 or IPv6 forwarding entries of the
main control board, you can configure this interface board not to receive any IPv4 or IPv6
forwarding 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
Type of the forwarding entries to be discarded
3.4.2 Configuring the Policy of Discarding All the IPv4 FIB Entries
When an interface board does not need to receive any IPv4 FIB route prefix, you can configure
the policy of discarding all IPv4 FIB entries.
Context
When the interface board need not receive the IPv4 FIB entries delivered by the main control
Procedure
Step 1 Run:
system-view

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.
Issue 02 (2011-09-10)

58

NOTE
takes effect.
Step 3 Run:
refresh fib slot
slot-id
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 Entries
When an interface board does not need to receive any IPv6 FIB route prefix, you can configure
the policy of discarding all IPv6 FIB entries.
Context
When the interface board need not receive the IPv6 FIB entries delivered by the main control
Procedure
Step 1 Run:
system-view

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
takes effect.
Step 3 Run:
slot-id
The IPv6 FIB policy is refreshed so that this policy is applied to the interface board.
----End

After the policy of discarding all IPv4 FIB entries and IPv6 FIB entries is configured, you need
to check whether the configuration is correct. In addition, you can view information about FIB
route prefixes on the interface board.
Prerequisite
The configurations of the configuring the policy of discarding all the FIB entries function are
complete.
Issue 02 (2011-09-10)

59

Procedure
l
----End
Example
Run the display fib-policy command, and you can view that the IPv4 FIB policy applied to the
specified interface board is no-route fib-policy.
FIB-policy:
Have configured no-route FIB policy.
Run the display ipv6 fib-policy command, and you can view that the IPv6 FIB policy applied
to the specified interface board is no-route fib-policy.
FIB-policy:
Have configured no-route FIB policy.
Run the display fib statistics all command, and you can view the FIB route prefix capacity and
the FIB policy statistics of the IPv4 FIB module on the specified interface board.
[HUAWEI]
IPv4 FIB
IPv4 FIB
IPv4 FIB
IPv4 FIB
IPv4 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 capacity
and the FIB policy statistics of the IPv6 FIB module on the specified interface board.
[HUAWEI]
IPv6 FIB
IPv6 FIB
IPv6 FIB
IPv6 FIB
display ipv6 fib 1 statistics all

Public Route Prefix Count :0, Entry Count : 0
Vpn-instance VPN6A Route Prefix Count :0, Entry Count : 0
3.5 Configuring Overload Suspension Recovery

When an interface board is in the overload suspension state, you need to perform overload
suspension recovery. In this manner, the interface board returns to the normal state.

configuring overload suspension recovery.
Issue 02 (2011-09-10)

60

When the interface board is in the overload suspension state, you need to perform overload
suspension 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 Recovery

The interface board in the overload suspension state cannot automatically return to the normal
state. Instead, you need to perform overload suspension recovery to restore the interface board
to the normal state. Overload suspension recovery can take effect on the IPv4 FIB module and
IPv6 FIB module at the same time.
Context
Do as follows on the router in the overload suspension state:
Procedure
Step 1 Run:
system-view

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 Refreshing
the FIB Policy on the IPv4 FIB and IPv6 FIB. In this manner, overload suspension recovery
can take effect on the IPv4 FIB module and IPv6 FIB module.
Issue 02 (2011-09-10)

61

3.5.3 Refreshing the FIB Policy

After overload suspension recovery is configured, you must refresh the FIB policy; otherwise,
overload suspension recovery cannot take effect.
Context
Do as follows on the router configured with overload suspension recovery:
Procedure
Step 1 Run:
system-view

NOTE
If the router supports only IPv4 or IPv6, you can select Step 2 or Step 3 accordingly to refresh the
corresponding module. If the router supports IPv4 and IPv6, it is recommended to perform Step 2 and
Step 3 to refresh IPv4 FIB and IPv6 FIB.
Step 2 Run:
refresh fib slot
slot-id
The IPv4 FIB is refreshed so that overload suspension recovery is applied to the specified
interface board.
Step 3 Run:
slot-id
The IPv6 FIB is refreshed so that overload suspension recovery is applied to the specified
interface board.
----End

After overload suspension recovery is configured, you need to check whether the configuration
is correct. In addition, you can view the FIB information on the interface board.
Prerequisite
The configurations of the configuring overload suspension recovery function are complete.
Procedure
l
Run the display fib overload state slot slot-id command to check the overload status of
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.
----End
Issue 02 (2011-09-10)

62

Example
Run the display fib statistics all command, and you can view the total number of the current
IPv4 FIB entries and the total number of the IPv4 FIB entries of each type on the main control
board.
[HUAWEI]
IPv4 FIB
IPv4 FIB
IPv4 FIB
IPv4 FIB
display fib statistics all

Total Route Prefix Count : 1008, Entry Count : 1018
Vpn-instance VPNB Route Prefix Count : 3, Entry Count : 13
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 prefix
capacity of the specified interface board. When the interface board is in the overload suspension
state, the number of the IPv4 FIB entries of each type received on the interface board is 0.
[HUAWEI]
IPv4 FIB
IPv4 FIB
IPv4 FIB
IPv4 FIB
IPv4 FIB

Public Route Prefix Count :0, Entry Count : 0
Run the display fib overload state command, and you can view that the interface board is in
the Overload suspend state. After overload suspension recovery is configured on the interface
board, 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 Recovery

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

configuring overload forwarding recovery.
When the IPv4 FIB or IPv6 FIB module on the interface board is in the overload forwarding
state, 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 normal
state.
Before configuring overload forwarding recovery, power on and start the router normally.
Data Preparation
To configure overload forwarding recovery, you need the following data.
Issue 02 (2011-09-10)

63

No.
Data
Type of the forwarding entries in the overload forwarding state
3.6.2 Configuring IPv4 FIB Overload Forwarding Recovery

The IPv4 FIB module in the overload forwarding state cannot automatically return to the normal
state. 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,
Context
Do as follows on the router with the IPv4 FIB module in the overload forwarding state:
Procedure
Step 1 Run:
system-view

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 policy
takes effect.
Step 3 Run:
refresh fib slot
slot-id
The IPv4 FIB is refreshed so that overload forwarding recovery is applied to the specified
interface board.
----End
3.6.3 Configuring IPv6 FIB Overload Forwarding Recovery

The IPv6 FIB module in the overload forwarding state cannot automatically return to the normal
state. 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,
Context
Do as follows on the router with the IPv6 FIB module in the overload forwarding state:
Issue 02 (2011-09-10)

64

Procedure
Step 1 Run:
system-view

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 policy
takes effect.
Step 3 Run:
refresh ipv6 fib slot slot-id
The IPv6 FIB is refreshed so that overload forwarding recovery is applied to the specified
interface board.
----End

After overload forwarding recovery is configured, you need to check whether the configuration
is correct. In addition, you can view the FIB information on the interface board.
Prerequisite
The configurations of the configuring overload forwarding recovery function are complete.
Procedure
l
Run the display fib overload state slot slot-id command to check the overload status of
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.
----End
Example
Run the display fib statistics all command, and you can view the total number of the current
IPv4 FIB entries and the total number of the IPv4 FIB entries of each type on the main control
board.
[HUAWEI]
IPv4 FIB
IPv4 FIB
IPv4 FIB
IPv4 FIB
Issue 02 (2011-09-10)
display fib statistics all

Total Route Prefix Count : 1008, Entry Count :
Public Route Prefix Count : 1005, Entry Count :
Vpn-instance VPNB Route Prefix Count : 3, Entry
Vpn-instance VPNA Route Prefix Count : 0, Entry

1018
1005
Count : 13
Count : 0
65

Run the display fib slot-id statistics all command, and you can view the IPv4 FIB route prefix
capacity of the specified interface board.
[HUAWEI]
IPv4 FIB
IPv4 FIB
IPv4 FIB
IPv4 FIB
IPv4 FIB

Run the display fib overload state command, and you can view that the interface board is in
the Overload forward state. After overload recovery is configured on the interface board, the
interface board changes to the normal state.
[HUAWEI] display fib overload state slot 1
Overload mode:
Overload forward mode.
Overload state:
Overload forward state.

This section provides the configuration examples of interface board intermixing to show how
to configure FIB policies.
3.7.1 Example for Configuring the VPN IPv4 FIB Policy

This example shows how to configure devices on the same VPN to intercommunicate and how
to isolate devices in different VPNs from intercommunicating.
Figure 3-1 shows the network structure.
On PE1, the FIB route prefix capacity of interface board 1 exceeds that of interface board 2 or
interface board 3.
On PE2, the FIB route prefix capacity of interface board 1 exceeds that of interface board 2 or
interface board 3.
VPN A connected to PE1 is required to communicate with VPN A connected to PE2, and VPN
B 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.
Issue 02 (2011-09-10)

66

Figure 3-1 Networking diagram of configuring the VPN IPv4 FIB policy
VPNA
VPNA
VPNA
VPNA
CE1
POS2/0/0
10.1.1.2/24
POS1/0/0
30.1.1.2/24
POS1/0/0
POS3/0/0
30.1.1.1/24
20.1.1.2/24 PE1
CE2
POS1/0/0
50.1.1.2/24
POS1/0/0
10.1.1.1/24
POS1/0/0
20.1.1.1/24
POS2/0/0
50.1.1.1/24
POS1/0/1
40.1.1.1/24
CE3
POS1/0/0
40.1.1.2/24
PE2
POS3/0/0
60.1.1.1/24
POS1/0/0
60.1.1.2/24
CE4
VPNB
VPNB
Take 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 Preparation
To complete the configuration, you need the following data:
l
Slot number of each router
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, and
CE2 is required to communicate with CE4.
For details, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.
Issue 02 (2011-09-10)

67

Step 2 Take interface board 2 on PE1 as an example to view the public forwarding entries and VPN
forwarding 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 : 9
Destination/Mask
Nexthop
127.0.0.1/32
127.0.0.1
127.0.0.0/8
127.0.0.1
1.1.1.1/32
127.0.0.1
30.1.1.1/32
127.0.0.1
30.1.1.0/24
30.1.1.1
30.1.1.2/32
30.1.1.2
40.1.1.0/24
30.1.1.2
2.1.1.1/32
30.1.1.2
3.1.1.1/32
30.1.1.2
Flag
HU
U
HU
HU
U
HU
DGU
DGHU
DGHU
TimeStamp
t[55]
t[55]
t[55]
t[2521]
t[2521]
t[2521]
t[3554]
t[3554]
t[44469]
Interface
InLoop0
InLoop0
InLoop0
InLoop0
[No Intf]
[No Intf]
[No Intf]
[No Intf]
[No Intf]
TunnelID
0x0
0x0
0x0
0x0
0x0
0x0
0x1002001
0x1002000
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:
Destination/Mask
Nexthop
Flag
10.1.1.2/32
127.0.0.1
HU
10.1.1.0/24
10.1.1.2
U
10.1.1.1/32
10.1.1.1
HU
50.1.1.0/24
30.1.1.2
DGU
50.1.1.2/32
30.1.1.2
DGHU
TimeStamp
t[47861]
t[47861]
t[47861]
t[48014]
t[48014]
Interface
InLoop0
POS2/0/0
POS2/0/0
[No Intf]
[No Intf]
TunnelID
0x0
0x0
0x0
0x1002005
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:
Destination/Mask
Nexthop
Flag
20.1.1.2/32
127.0.0.1
HU
20.1.1.0/24
20.1.1.2
U
20.1.1.1/32
20.1.1.1
HU
60.1.1.0/24
30.1.1.2
DGU
60.1.1.2/32
30.1.1.2
DGHU
TimeStamp
t[51766]
t[51766]
t[51766]
t[51766]
t[51766]
Interface
InLoop0
[No Intf]
[No Intf]
[No Intf]
[No Intf]
TunnelID
0x0
0x0
0x0
0x1002005
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 VPN
forwarding entries on this interface board.
# View the public forwarding entries on interface board 2. No public forwarding entries exist
on interface board 2.
[PE1] display fib 2
# View the VPN forwarding entries of VPN A on interface board 2. The VPN forwarding entries
remain unchanged after the policy is configured.
Issue 02 (2011-09-10)

68

[PE1] display fib 2 vpn-instance VPNA
FIB Table:
Destination/Mask
Nexthop
Flag
10.1.1.2/32
127.0.0.1
HU
10.1.1.0/24
10.1.1.2
U
10.1.1.1/32
10.1.1.1
HU
50.1.1.0/24
30.1.1.2
DGU
50.1.1.2/32
30.1.1.2
DGHU
TimeStamp
t[47861]
t[47861]
t[47861]
t[48014]
t[48014]
Interface
InLoop0
POS2/0/0
POS2/0/0
[No Intf]
[No Intf]
TunnelID
0x0
0x0
0x0
0x1002005
0x1002005
# View the VPN forwarding entries of VPN B on interface board 2 as follows. After the policy
is 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 of
VPN 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
--- 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 Files
l
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

#
sysname CE2
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 20.1.1.1 255.255.255.0
#
bgp 65420
#
ipv4-family unicast
Issue 02 (2011-09-10)

69

import-route direct
#
return
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
#
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 connect-interface LoopBack1
#
ipv4-family unicast
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
#
ipv4-family vpn-instance VPNA
import-route direct
#
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
Issue 02 (2011-09-10)

70

#
apply fib-policy vpn-instance VPNA slot 2
apply fib-policy vpn-instance VPNB slot 3
#
return
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

#
sysname PE2
#
#
#
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
Issue 02 (2011-09-10)

71

ip address 50.1.1.1 255.255.255.0

#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 60.1.1.1 255.255.255.0
#
interface LoopBack1
ip address 3.1.1.1 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.1 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.1 enable
#
import-route direct
#
import-route direct
#
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
#
#
return

#
sysname CE3
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 50.1.1.2 255.255.255.0
#
bgp 65430
#
ipv4-family unicast
import-route direct
#
return

#
sysname CE4
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 60.1.1.2 255.255.255.0
#
bgp 65440
Issue 02 (2011-09-10)

72


#
ipv4-family unicast
import-route direct
#
return
3.7.2 Example for Configuring Overload Suspension Recovery

This example shows how to restore the interface board in the overload suspension state to the
normal state.
Figure 3-2 Networking diagram of configuring overload suspension recovery
VPNA
VPNA
CE1
VPNA
VPNA
POS1/0/0
10.1.1.1/24
POS2/0/0
10.1.1.2/24
POS3/0/0
20.1.1.2/24
CE2
POS1/0/0
50.1.1.2/24
POS1/0/0
30.1.1.2/24
POS1/0/0
PE1 30.1.1.1/24
POS1/0/1
40.1.1.1/24
POS1/0/0
40.1.1.2/24 PE2
POS1/0/0
20.1.1.1/24
VPNB
CE3
POS2/0/0
50.1.1.1/24
POS3/0/0
60.1.1.1/24
POS1/0/0
60.1.1.2/24
CE4
VPNB
The FIB route prefix capacity of either interface board 2 or interface board 3 on PE1 or PE2 is
smaller than the sum of the public forwarding entries and VPN forwarding entries. Before a FIB
policy is configured, the interface board is overloaded immediately after running. Then, when
one 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 and
perform overload suspension recovery on the interface board.
Issue 02 (2011-09-10)

73

1.
2.
3.
Configure overload suspension recovery on interface board 2.
4.
Configure overload suspension recovery on interface board 3.
Data Preparation
l
VPN instance name
Procedure
Configure all the routers shown in Figure 3-2. VPN A connected to PE1 is required to
communicate with VPN A connected to PE2, and VPN B connected to PE1 is also required to
communicate with VPN B connected to PE2.
Step 2 After the current interface board begins to work, interface board 2 and interface board 3 rapidly
change to the overload suspension state.
[PE1] display fib overload state slot 2
Overload mode:
Overload state:
Overload mode:
Overload 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 all
IPv4 FIB Total Route Prefix Count : 1003, Entry Count : 1003
IPv4 FIB Public Route Prefix Count : 9, Entry Count : 9
IPv4 FIB Vpn-instance VPNB Route Prefix Count : 494, Entry Count : 494
IPv4 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 all
When the interface board is in the overload suspension state, the FIB entries on the interface
board are cleared. Thus, the number of the forwarding entries of each type on the interface board
is 0.
# View the FIB route prefix capacity on interface board 3.
Issue 02 (2011-09-10)

74

IPv4
IPv4
IPv4
IPv4
IPv4
FIB
FIB
FIB
FIB
FIB

Through the preceding display, you can know the following:

l The interface board changes to the overload suspension state because the number of
forwarding 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 prefix
capacity 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]
[PE1]
[PE1]
[PE1]
apply fib-policy
apply fib-policy
refresh fib slot
refresh fib slot
vpn-instance VPNA slot 2

vpn-instance VPNB slot 3
2
3
NOTE
When the interface board is in the overload suspension state, the system prompts users to configure overload
suspension recovery, and then run the refresh command.

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

overload suspend slot 3
slot 2
slot 3

On PE2, view the status of the current interface board and that the interface board returns to the
Normal state.
Overload mode:
Overload state:
Normal state.
On VPN A, CE1 can ping through CE3.

<CE1> ping 50.1.1.2
0.00% packet loss
----End
Issue 02 (2011-09-10)

75

Configuration Files
l

#
sysname CE1
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
bgp 65410
#
ipv4-family unicast
import-route direct
#
Return

#
sysname CE2
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 20.1.1.1 255.255.255.0
#
bgp 65420
#
ipv4-family unicast
import-route direct
#
return

#
sysname PE1
#
#
#
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
Issue 02 (2011-09-10)

76


ip address 10.1.1.2 255.255.255.0
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 20.1.1.2 255.255.255.0
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 3.1.1.1 enable
#
ipv4-family vpnv4
policy vpn-target
peer 3.1.1.1 enable
#
import-route direct
#
import-route direct
#
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
#
#
return
#
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
Issue 02 (2011-09-10)

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

#
sysname PE2
#
#
#
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 address 50.1.1.1 255.255.255.0
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 60.1.1.1 255.255.255.0
#
interface LoopBack1
ip address 3.1.1.1 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.1 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.1 enable
#
import-route direct
#
import-route direct
#
ospf 1
area 0.0.0.0
network 40.1.1.0 0.0.0.255
Issue 02 (2011-09-10)

78

network 3.1.1.1 0.0.0.0

#
#
return

#
sysname CE3
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 50.1.1.2 255.255.255.0
#
bgp 65430
#
ipv4-family unicast
import-route direct
#
return

#
sysname CE4
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 60.1.1.2 255.255.255.0
#
bgp 65440
#
ipv4-family unicast
import-route direct
#
return
3.7.3 Example for Configuring Overload Forwarding Recovery

This example shows how to restore the interface board in the overload forwarding state to the
normal state.
Issue 02 (2011-09-10)

79

Figure 3-3 Networking diagram of configuring overload forwarding recovery
VPNA
VPNA
VPNA
VPNA
POS1/0/0
CE1 10.1.1.1/24
POS2/0/0
10.1.1.2/24
POS3/0/0
20.1.1.2/24
POS1/0/0
50.1.1.2/24
POS1/0/0
30.1.1.2/24
POS1/0/0
PE1 30.1.1.1/24
POS1/0/1
40.1.1.1/24
CE3
POS2/0/0
50.1.1.1/24
POS3/0/0
POS1/0/0
40.1.1.2/24 PE2 60.1.1.1/24
CE2 POS1/0/0
20.1.1.1/24
POS1/0/0
60.1.1.2/24
VPNB
CE4
VPNB
The FIB route prefix capacity of either interface board 2 or interface board 3 on PE1 or PE2 is
smaller than the sum of the public forwarding entries and VPN forwarding entries. Before a FIB
policy is configured, the interface board is overloaded immediately after running.Then, when
one 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 and
perform overload forwarding recovery on the interface board.
1.
2.
3.
Configure overload forwarding recovery on interface board 2.
4.
Configure overload forwarding recovery on interface board 3.
Data Preparation
l
VPN instance name
Issue 02 (2011-09-10)

80

Procedure
Configure all the routers shown in Figure 3-3. VPN A connected to PE1 is required to
communicate with VPN A connected to PE2, and VPN B connected to PE1 is also required to
communicate with VPN B connected to PE2.
Step 2 After the current interface board begins to work, interface board 2 and interface board 3 rapidly
change to the overload forwarding state.
Overload mode:
Overload state:
Overload mode:
Overload 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 all
# View the FIB route prefix capacity and the number of the FIB entries of each type on interface
board 2.
When the interface board is in the overload forwarding state, the number of FIB entries equals
the 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 interface
board 3.
Through the preceding display, you can know the following:

l The interface board changes to the overload forwarding state because the number of
forwarding 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 prefix
capacity of the interface board.
Thus, configure the following FIB policies on the interface board.
Issue 02 (2011-09-10)

81

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

vpn-instance VPNB slot 3
2
3
NOTE
When the interface board is in the overload forwarding state, the system prompts users to configure overload
forwarding recovery, and then run the refresh command.

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

overload forward slot 3
slot 2
slot 3

On PE2, view the status of the current interface board and that the interface board returns to the
Normal state.
Overload mode:
Overload state:
Normal state.
On VPN A, CE1can ping through CE3.

<CE1> ping 50.1.1.2
0.00% packet loss
----End
Configuration Files
l

#
sysname CE1
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
bgp 65410
#
ipv4-family unicast
import-route direct
Issue 02 (2011-09-10)

82

#
Return

#
sysname CE2
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 20.1.1.1 255.255.255.0
#
bgp 65420
#
ipv4-family unicast
import-route direct
#
return

#
sysname PE1
#
#
#
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 address 10.1.1.2 255.255.255.0
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 20.1.1.2 255.255.255.0
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 3.1.1.1 enable
Issue 02 (2011-09-10)

83

#
ipv4-family vpnv4
policy vpn-target
peer 3.1.1.1 enable
#
import-route direct
#
import-route direct
#
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
#
#
return
#
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

#
sysname PE2
#
#
#
Issue 02 (2011-09-10)

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 address 50.1.1.1 255.255.255.0
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 60.1.1.1 255.255.255.0
#
interface LoopBack1
ip address 3.1.1.1 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.1 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.1 enable
#
import-route direct
#
import-route direct
#
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
#
#
return

#
sysname CE3
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 50.1.1.2 255.255.255.0
#
bgp 65430
#
ipv4-family unicast
Issue 02 (2011-09-10)

85

import-route direct
#
return

#
sysname CE4
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 60.1.1.2 255.255.255.0
#
bgp 65440
#
ipv4-family unicast
import-route direct
#
return
Issue 02 (2011-09-10)

86

4 Fast Feeling Configuration
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 Overview
This section describes the characteristics and applicable environment of fast feeling.
4.2 Configuring Fast Feeling
This section describes the applicable environment and configuration procedure of fast feeling.
4.3 Maintaining Fast Feeling
When fast feeling functions abnormally, you can use maintenance tools to locate the fault.
Issue 02 (2011-09-10)

87

4.1 Fast Feeling Configuration Overview

This section describes the characteristics and applicable environment of fast feeling.
4.1.1 Introduction to Fast Feeling

After fast feeling is enabled, physical faults are rapidly reported to applications, and thus the
system can rapidly respond to the faults.
Traditionally, the periodic monitoring mechanism is adopted to detect physical component
faults. 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 run
in the interface view, the system can quickly inform the routing module of the event and then
inform the device management module after 5 seconds. This ensures that traffic is not
interrupted.
4.1.2 Fast Feeling Features Supported by the NE80E/40E

Fast feeling is used to rapidly report physical faults.
In the NE80E/40E, fast feeling channels are established to rapidly notify the physical fault to
the application for rapid response.
After the fast feeling function is enabled on an interface, when the shutdown command is run
in the interface view, the system can quickly inform the routing module of the event and then
inform the device management module after 5 seconds. This ensures that traffic is not
interrupted.
4.2 Configuring Fast Feeling

This section describes the applicable environment and configuration procedure of fast feeling.

Fast feeling is applicable to the scenario where the upper layer applications need to sense physical
faults as soon as the faults occur.
The flapping of routing protocols, MPLS and other protocols caused by the frequent change of
the interface status may influence the stability of the whole network. To avoid this, you can
configure the flapping control feature.
Pre-Configuration Tasks
None.
Issue 02 (2011-09-10)

88

Data Preparation
To configure the fast feeling, you need the following data.
No.
Data
Number of the interface on the router
4.2.2 Enabling Fast Feeling

Fast feeling can be enabled only in the interface view.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The specified interface view is displayed.

Step 3 Run:
fastfeeling
The fast feeling is enabled.

----End

After fast feeling is configured, you can view information about fast feeling on the interface to
check whether the configuration is correct.
Prerequisite
The configurations of configuring fast feeling function are complete.
Procedure
Step 1 Run the display fastfeeling [ interface interface-type interface-number ] command to check
the configuration and running status of the fast feeling feature of the interface.
----End
Example
Run the display fastfeeling command. If you can view the fast feeling feature configured on
the 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
Issue 02 (2011-09-10)

89

route interface status: up

ISIS interface status: down
4.3 Maintaining Fast Feeling

When fast feeling functions abnormally, you can use maintenance tools to locate the fault.
4.3.1 Monitoring the Running of Fast Feeling

In routine maintenance, you can monitor and know the running status of fast feeling.
Context
In routine maintenance, you can run the following command in any view to check the operation
of fast feeling.
Procedure
Step 1 Run the display fastfeeling [ interface interface-type interface-number ] command in any view
to check the current running status and statistics of fast feeling on the interface.
----End
Issue 02 (2011-09-10)

90

5 Flapping Control Configuration
Flapping Control Configuration
About This Chapter

Configuring interface flapping control can minimize the impact of frequent interface status
changes on the stability of the device and the network.
5.1 Flapping Control Configuration Overview
Interface flapping control is used to effectively minimize the impact of frequently-changed
interface status on the stability of the network.
5.2 Configuring the Interface Flapping Control
This section describes the applicable environment and configuration procedure of interface
flapping control.
5.3 Maintaining the Flapping Control Feature
When a fault of interface flapping control occurs, you can use maintenance tools to locate the
fault.
Issue 02 (2011-09-10)

91

5.1 Flapping Control Configuration Overview

Interface flapping control is used to effectively minimize the impact of frequently-changed
interface status on the stability of the network.
5.1.1 Introduction to the Interface Flapping Control

After interface flapping control is configured, interfaces can be suppressed from changing
frequently between Up and Down. In this manner, the adverse impact on the stability of the
device and network can be reduced.
In the network application, the device interface may change frequently between Up and Down
because of interference of the physical signal and error in link layer configuration. This causes
frequent flapping of routing protocols and MPLS and brings severe impacts on the device and
network. Some devices even become Down and the network becomes unavailable.
The flapping control feature can suppress the interface flapping to a low frequency. This
decreases 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 threshold
value 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 by
suppress algorithm according to the status of the interface. The core of the algorithm is that
the suppress penalty value increases with the changing times of the status of the interface
and decays by exponential.
The suppress threshold of interfaces (suppress): When this value is less than the suppress
penalty value, the interface is suppressed. This value must be greater than the reuse
threshold and less than the maximum suppress penalty value.
The reuse threshold value of interfaces (reuse): When this value is greater than the suppress
penalty value, the interface is not suppressed. This value must be less than the suppress
threshold.
The maximum suppress penalty value of interfaces (ceiling): This value does not increase
when the maximum suppress penalty value reaches the maximum. This value must be
greater than the suppress threshold.
In the NE80E/40E, these parameters can be set to control the event that the interface becomes
Up or Down.
The relationships among them are shown in Figure 5-1.
Issue 02 (2011-09-10)

92

Figure 5-1 Diagram of the interface flapping control

Penalty Value
ceiling
suppress
reuse
t1
t2
t3
t4
t5
Time
5.2 Configuring the Interface Flapping Control

This section describes the applicable environment and configuration procedure of interface
flapping control.

When 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 of
the interface status may influence the stability of the whole network. To avoid this, you can
configure the flapping control feature.
Before configuring the flapping control feature, you need to configure the physical attributes for
the router interfaces.
Data Preparation
To configure the flapping control feature, you need the following data.
Issue 02 (2011-09-10)
No.
Data
Interface number of a router
Suppress threshold of the interface
Reuse threshold of the interface

93

No.
Data
Maximum suppress penalty value of the interface
Time taken to decay the penalty value to half when the interface is Up
Time taken to decay the penalty value to half when the interface is Down
5.2.2 Enabling the Flapping Control Feature

Interface flapping control can be enabled only in the interface view.
Procedure
Step 1 Run:
system-view

Step 2 Run:

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 to
20000. The default value is 2000. The value of suppress must be greater than the value of
reuse 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 from
1001 to 20000. The default value is 6000. The value of ceiling must be greater than the value of
suppress.
The value of decay-ok is the time taken to decay the penalty value to half when the interface is
Up. 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 is
Down. It ranges from 1 to 900 seconds. The default value is 54 seconds.
----End

After interface flapping control is configured, you need to check whether the configuration is
correct. In addition, you can view the operation of interface flapping control.
Issue 02 (2011-09-10)

94

Prerequisite
The 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 check
the 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 features
configured on the interface.
<HUAWEI> display control-flap
#
Interface GigabitEthernet3/0/2
Control flap(OSI) status:unsuppressed
Control flap(IP) status:unsuppressed
Control flap parameter: suppress
reuse
4.000
2.000
decay-ok
54
decay-ng
54
ceiling
6.000
5.3 Maintaining the Flapping Control Feature

When a fault of interface flapping control occurs, you can use maintenance tools to locate the
fault.
5.3.1 Clearing Flapping Control Information

Before re-collecting the statistics about interface flapping control, you need to clear the operation
information about flapping control on the interface.
Context
CAUTION
Running the reset control-flap command can cancel the configured penalty value or the flapping
times. 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-number
command in the user view to clear the running status or statistics of the flapping control feature.
----End
Issue 02 (2011-09-10)

95

5.3.2 Monitoring the Flapping Control on the Interface

In routine maintenance, you can monitor and know the operation of interface flapping control.
Context
In routine maintenance, you can run the following commands in any view to check the flapping
control on the interface.
Procedure
Step 1 Run the display control-flap [ interface interface-type interface-number ] command in any
view to check the operation of the current running status and statistics of the flapping control
feature on the interface.
----End
Issue 02 (2011-09-10)

96

6 Transmission Alarm Configuration
Transmission Alarm Configuration
About This Chapter

Configuring transmission alarm suppression can reduce the impact of frequently-generated
transmission 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 alarm
feature.
6.1 Transmission Alarm Configuration Overview

This section describes the concepts and characteristics of transmission alarm customization and
suppression.
6.2 Configuring Transmission Alarm Customization
After a transmission alarm type is customized, the alarms of this type affect the feature status
of interfaces.
6.3 Configuring the Interval for Filtering Transmission Alarms
Configuring the interval for filtering transmission alarms can lower the frequency at which
alarms are generated, and thus minimize the impact on the stability of the network.
6.4 Configuring Transmission Alarm Suppression
This section describes how to configure transmission alarm suppression and specify the
suppression threshold.
6.5 Maintaining
When a fault of transmission alarm customization or suppression occurs, you can use
maintenance tools to locate the fault.
Issue 02 (2011-09-10)

97

6.1 Transmission Alarm Configuration Overview

This section describes the concepts and characteristics of transmission alarm customization and
suppression.
6.1.1 Introduction to Transmission Alarm Customization and

Suppression
Transmission alarm suppression can efficiently filter and suppress alarm signals. This protects
the interface from frequently flapping. In addition, alarm customization efficiently controls the
impact of alarms on the status change of interfaces.
At present, the carrier-class network requires higher reliability for the IP network. Thus, the
device in the network is required to rapidly detect the fault.
If fast detection works on the interface, the physical status of the interface frequently changes
between Up and Down because alarms are notified faster. As a result, the network flaps
frequently.
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 avoids
the interface from frequently flapping. In addition, alarm customization efficiently controls the
impact 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 the
interface.
Suppress alarms. This can filter the burr and prevent the network from frequently flapping.
6.1.2 Features of Transmission Alarm Customization and

Suppression in the NE80E/40E
Transmission alarm customization and suppression are supported only on the physical interfaces
encapsulated with SDH/SONET.
Supported Interface Type

Only the physical interfaces encapsulated with the Synchronous Digital Hierarchy (SDH) and
Synchronous Optical Network (SONET) support transmission alarm customization and
suppression. 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 of
transmission alarms, and the configurations of transmission alarms also take effect.
Issue 02 (2011-09-10)

98

6.2 Configuring Transmission Alarm Customization

After a transmission alarm type is customized, the alarms of this type affect the feature status
of interfaces.

This part describes the applicable environment, pre-configuration tasks, and required data of
transmission alarm customization.
When the transmission equipment is connected with a router, a large number of burr alarms are
generated if the network is unstable. These alarms, however, make the physical status of the
interface frequently change between Up and Down. To make the network device ignore these
burr alarms by customizing some alarms, you need to configure transmission alarm
customization.
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
Type of the alarm that can affect the physical status of the interface
(Optional) Respective thresholds of B3TCA, SDBERE, and SFBERE alarms
(Optional) Type of the alarm that can record logs
6.2.2 Configuring the Type of the Alarm That Can Affect the
Physical Status of the Interface
Transmission alarm customization can be configured only in the interface view. Alarm types
that can be customized vary with the hardware.
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)

99


Step 2 Run:
interface
interface-type interface-number

The supported interfaces are ATM interfaces, POS interfaces, 10 GE WAN interfaces, and WDM
interfaces.
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 preceding
alarms. If the alarm type that the hardware does not support is configured, the configuration
fails. In addition, the types of alarms not supported by the interface are displayed. The parameter
lcd is displayed only on 10GE WAN interfaces.
Only 10GE WAN interfaces support wlnk alarms. You cannot configure wlnk alarms. You can
use the display transmission-alarm command to check the status and statistics of wlnk alarms.
CAUTION
LAIS, LOF, and LOS alarms provide alarms for the status change of the link. Disabling these
alarms affects the precise forwarding of service data. Thus, it is recommended to enable these
alarms.
----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 reported
if the number of alarms does not reach the threshold.
Context
Do as follows on the interface connected to the transmission equipment:
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface

Issue 02 (2011-09-10)

100

The supported interfaces are ATM interfaces, POS interfaces, 10 GE-WAN interfaces, and
WDM 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 be
reported 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 is
specified by the parameter value of each type of alarms configured in the transmission-alarm
threshold command. The value of sdbere cannot be smaller than that of sfbere. That is, the
threshold 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 Be

Recorded to Logs
Recording alarms to logs helps you to query if necessary.
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface

The supported interfaces are ATM interfaces, POS interfaces, 10 GE WAN interfaces, and WDM
interfaces.
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 | otusf-ber | pais | pm-bdi | pm-tim | pplm | prdi | prei | puneq | rdool | r-lof | rlos | 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 preceding
alarms. If the alarm type that the hardware does not support is configured, the configuration
fails. In addition, the types of alarms not supported by the interface are displayed. The parameter
lcd is displayed only on 10GE WAN interfaces.
By default, WAN Interface Link Status Alarm (wlnk) alarms are recorded to the log. Only 10GE
WAN interfaces support wlnk alarms. You cannot configure wlnk alarms, and wlnk alarms are
always enabled. You can use the display transmission-alarm command to check the status and
statistics of wlnk alarms.
----End
Issue 02 (2011-09-10)

101


After transmission alarm customization is configured, you need to check whether the
configuration is correct. In addition, you can view the status and statistics about alarms on the
interface.
Prerequisite
The configurations of the configuring transmission alarm customization function are complete.
Procedure
l
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 | otulom | 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.
Run the display transmission-alarm threshold [ interface-type interface-number ]

command check the respective thresholds of B3TCA, SDBERE, and SFBERE alarms on
the interface.
----End
Example
View the status and statistics of the alarms, such as AUAIS, B3TCA, LAIS, LOF, LOS, and
TROOL 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
Alarm lof
Status: Up
Alarm los
Status: Up
Alarm trool
Issue 02 (2011-09-10)

102

Status: Up, Log

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 Transmission

Alarms
Configuring the interval for filtering transmission alarms can lower the frequency at which
alarms are generated, and thus minimize the impact on the stability of the network.

configuring the interval for filtering transmission alarms.
When the transmission equipment is connected to the network, a large number of burr alarms
are generated if the network is unstable. These alarms, however, make the physical status of the
interface frequently change between Up and Down. If some alarms that are generated and cleared
in a certain period can be ignored, the interval for filtering transmission alarms needs to be
configured.
Before configuring the interval for filtering transmission alarms, complete the following tasks:
l
Configuring Transmission Alarm Customization on the interface

NOTE
The filtering function can be enabled only after the interface is enabled with transmission alarm
customization.
Data Preparation
To configure the interval for filtering transmission alarms, you need the following data.
Issue 02 (2011-09-10)
No.
Data
Filtering timer parameter

103

6.3.2 Configuring the Interval for Filtering Transmission Alarms

If the interval of alarm generating and disappearing is smaller than the set interval, the alarm
signal is regarded as a burr and is filtered. Otherwise, the alarm signal is normal.
Context
To configure transmission alarm filtering on multiple interfaces, you can repeat Step 2 and Step
3.
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface

WDM interfaces.
Step 3 You can select one or more following configurations according to the alarm message to be
filtered 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 Down
and set the filtering interval.
When the interface goes Down, the device management module generates an alarm message
and takes corresponding actions to process the alarm message according to the following
situations:
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 out
the alarm message indicating that the interface goes Down, that is, the device management
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 the
interface goes Up within the specified filtering interval, the device management module
sends the alarm message indicating that the interface goes Down to the upper-layer
application after the filtering interval expires.
l Run the transmission-alarm holdup-timer holdup-time command to enable the device
management module to filter out the alarm message indicating that the interface goes Up and
set the filtering interval.
When the interface goes Up, the device management module generates an alarm message
and takes corresponding actions to process the alarm message according to the following
situations:
If the device management module receives an alarm message indicating that the interface
goes Down within the specified filtering interval, the device management module filter
out the alarm message indicating that the interface goes Up, that is, the device
management 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 the
interface goes Down within the specified filtering interval, the device management
Issue 02 (2011-09-10)

104

module sends the alarm message indicating that the interface goes Up to the upper-layer
application after the filtering interval expires.
By default, the device management module does not filter out the alarm message indicating that
the interface goes Up or Down. That is, once the device management module receives the alarm
message indicating that the interface goes Up or Down, it immediately sends the alarm message
to the upper-layer application.
----End

After the interval for filtering transmission alarms is configured, you need to check whether the
configuration is correct. In addition, you can view the status and statistics about alarms on the
interface.
Prerequisite
The configurations of the configuring the interval for filtering transmission alarms function are
complete.
Procedure
l
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 | otulom | 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)
Suppress value: 999
Ceiling value: 6000
Reuse value: 500
6.4 Configuring Transmission Alarm Suppression

This section describes how to configure transmission alarm suppression and specify the
suppression threshold.

This part describes the applicable environment, pre-configuration tasks, and required data of
transmission alarm suppression.
Issue 02 (2011-09-10)

105

When the transmission equipment is connected to the network, a large number of burr alarms
are generated if the network is unstable. These alarms, however, make the physical status of the
interface frequently change between Up and Down. To prevent these alarms from frequently
flapping or make the network device ignore these burr alarms, you need to enable alarm
suppression.
Before configuring transmission alarm suppression, complete the following tasks:
l
Configuring Transmission Alarm Customization on the interface

NOTE
The suppression function takes effect on interfaces only after alarm customization is enabled on the
interfaces.
Data Preparation
To configure transmission alarm suppression, you need the following data.
No.
Data
Interface Type and number.
Alarm ceiling threshold, alarm reuse threshold, alarm suppression threshold, half-life
of alarm generation, and half-life of alarm clearance.
6.4.2 Configuring Transmission Alarm Suppression

After the suppression threshold of transmission alarms is set, alarms are reported only when the
number of alarms reaches the threshold.
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface

WDM interfaces.
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.

Issue 02 (2011-09-10)

106

By default, transmission alarm suppression is not enabled.

----End

After transmission alarm suppression is configured, you need to check whether the configuration
is correct. In addition, you can view the status and statistics about alarms on the interface.
Prerequisite
The 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
Example
Run the display transmission-alarm configuration command, and you can view the alarm
configuration 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)
Suppress value: 999
Ceiling value: 6000
Reuse value: 500
6.5 Maintaining
When a fault of transmission alarm customization or suppression occurs, you can use
maintenance tools to locate the fault.
6.5.1 Clearing Transmission Alarm Information

Before re-collecting the statistics about transmission alarms on an interface, you need to clear
all transmission alarm information on the interface.
Context
CAUTION
Clearing transmission alarm information on the interface may cause all alarm statistics on the
interface to be reset. Therefore, confirm the action before you use the command.
Issue 02 (2011-09-10)

107

Procedure
Step 1 Run the reset transmission-alarm statistics command in the interface view to clear all the
transmission alarm running statistics on the interface.
----End
Issue 02 (2011-09-10)

108

A Glossary
Glossary
Collates frequently used glossaries in this document.

A
ATM
Asynchronous Transfer Mode (ATM). A data transmission

technology in which data is transferred at high data rates in fixed
length, 53 bytes.
Authentication
An act that decides whether a user can be awarded with access right
or what kinds of users can access a network.
Authorization
An act that accredits a user with access to certain services.
AUX
Auxiliary interface that provides an EIA/TIA-232 DTE interface. By

using the AUX interface and the Modem, a user can access a network
through dialup.
C
Callback
A call mode in which both ends of the communication participate in

the call. One end is called the Client, while the other end is caller the
Server. The Client initiates a call, and the Server decides whether to
callback or not. If a callback is needed, the Server tears down the
connection and then initiates a call to the Client.
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 point

connection. The POS interface is based on SONET.
Issue 02 (2011-09-10)

109

QinQ
A Glossary
The QinQ technology adds one a layer of 802.1Q tag on the 802.1Q
packet to expand the VLAN space. In this way, data of the VLAN can
be transparently transmitted in the public network.
S
SONET
Synchronous Optical Network (SONET). A standard for synchronous

data transfer over optical networks. The standard contains a series of
transmission speed, including SDH Transport Module (STM) -1
(155Mbit/s), STM-4c (622 Mbit/s) and STM-16c/STM-16 (2.5 Gbit/
s).
V
VLAN
The Virtual Local Area Network (VLAN) divides a physical LAN into
several logical sub-nets, regardless of their physical locations.Data
transmission within a VLAN does not interfere with that in other
VLANs. This enhances the network security.
W
WAN
Wide Area Network. A network that covers a large geographic area.
Issue 02 (2011-09-10)
X.21
ITU-T standard for serial communications over synchronous digital

lines. It is mainly used in Europe and Japan.
X.25
A data link layer protocol. A protocol that defines the establishment

and maintenance of connections between the DTE devices and the
DCE devices.

110

B Acronyms and Abbreviations
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
AAL2
AAL3
AAL5
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
Issue 02 (2011-09-10)
B3 Threshold Crossing Alarm

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
Issue 02 (2011-09-10)
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
Issue 02 (2011-09-10)

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 Standardization

Sector
Issue 02 (2011-09-10)
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
Issue 02 (2011-09-10)
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
Issue 02 (2011-09-10)
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
Issue 02 (2011-09-10)

117

TA
Terminal Adapter
TACAC
S
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
Issue 02 (2011-09-10)

118

WLNK
WAN Interface Link Stauts Alarm
WWW
World Wide Web
X
XOT
Issue 02 (2011-09-10)
X.25 Over TCP

119

Configuration Guide - Interface Management (V600R003C00 - 02) PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuration Guide - Interface Management (V600R003C00 - 02) PDF

Uploaded by

Copyright:

Available Formats

HUAWEI NetEngine80E/40E Router