Configuration Guide - Interface Management (V300R007C00 - 02)

HUAWEI NetEngine5000E Core Router
V300R007C00
Configuration Guide - Interface

Management
Issue 02
Date 2009-12-10
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2009. 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 (2009-12-10) Huawei Proprietary and Confidential i

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 NE5000E. 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.
CAUTION
On a single NE5000E, an interface is numbered in the format of slot number/card number/
interface number. On an NE5000E cluster, an interface is numbered in the format of chassis ID/
slot number/card number/interface number. This requires the chassis ID to be specified along
with the slot number.
Related Versions
The following table lists the product versions related to this document.
Product Name Version
HUAWEI NetEngine5000E V300R007C00
Intended Audience
This document is intended for:
l Commissioning engineer
l Data configuration engineer
Issue 02 (2009-12-10) Huawei Proprietary and Confidential iii

About This Document Configuration Guide - Interface Management
l Network monitoring engineer

l System maintenance engineer
Organization
This document is organized as follows.
Chapter Description
1 Interface Basic This chapter describes common interface types, how to view
Configuration the interface information, and how to set the interval for
collecting statistics about the interface traffic.
2 Logical Interface This chapter describes common logical interfaces and how
Configuration to configure logical interfaces, and provides various
configuration examples.
3 Interface Board This chapter describes the fundamentals and configuration

Intermixing Configuration procedures of interface board intermixing.
4 Fast Feeling This chapter describes the principles and configuration

Configuration procedures of fast fault sensing.
5 Flapping Control This chapter describes the principles and configuration

Configuration procedures of interface flapping control.
6 Transmission Alarm This chapter describes the fundamentals and configuration

Configuration procedures of transmission alarm customization and
suppression.
A Glossary This appendix collates frequently-used terms in this

document.
B Acronyms and This appendix collates frequently used acronyms and

Abbreviations abbreviations in this document.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.
iv Huawei Proprietary and Confidential Issue 02 (2009-12-10)

Symbol Description
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save

time.
Provides additional information to emphasize or supplement

important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
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.
Issue 02 (2009-12-10) Huawei Proprietary and Confidential v

About This Document Configuration Guide - Interface Management
{ x | y | ... }* Optional items are grouped in braces and separated by

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

vertical bars. Several items or no item can be selected.
&<1-n> The parameter before the & sign can be repeated 1 to n times.
# A line starting with the # sign is comments.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
vi Huawei Proprietary and Confidential Issue 02 (2009-12-10)

Action Description
Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Update History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Updates in Issue 02 (2009-12-10)

This is the second release.
Updates in Issue 01 (2009-09-05)

This is the first release.
Issue 02 (2009-12-10) Huawei Proprietary and Confidential vii

Configuration Guide - Interface Management Contents
Contents
About This Document...................................................................................................................iii

1 Interface Basic Configuration..................................................................................................1-1
1.1 Interface Basic Configuration Overview.........................................................................................................1-2
1.1.1 Interface type..........................................................................................................................................1-2
1.1.2 Interface Views and Prompts................................................................................................................. 1-2
1.1.3 Link Layer Protocols and Access Technologies.................................................................................... 1-4
1.2 Configuring the Interface Description.............................................................................................................1-5
1.2.1 Establishing the Configuration Task......................................................................................................1-5
1.2.2 Configuring the Interface Description....................................................................................................1-6
1.2.3 Checking the Configuration...................................................................................................................1-6
1.3 Configuring the Hold-Time Interval After an Interface Becomes Up/Down................................................. 1-7
1.3.2 Configuring the Hold-Time Interval After an Interface Becomes Up/Down........................................ 1-7
1.4 Configuring the Interval for Collecting the Statistics of Traffic on the Interface...........................................1-8
1.4.2 Configuring Traffic Statistics on Interfaces...........................................................................................1-9
1.4.3 Configuring the Global Interval for Collecting Traffic Statistics........................................................1-10
1.4.4 Configuring the Interval for Collecting the Statistics of Traffic on the Interface................................1-10
1.4.5 Checking the Configuration.................................................................................................................1-11
1.5 Configuring the Alarm Function for Interfaces.............................................................................................1-13
1.5.1 Establishing the Configuration Task....................................................................................................1-13
1.5.2 Configuring the Alarm Function for Interfaces....................................................................................1-13
1.6 Maintaining Interface Basic Configuration...................................................................................................1-15
1.6.1 Clearing Statistics.................................................................................................................................1-15
1.6.2 Monitoring Interface Information........................................................................................................1-16
1.6.3 Debugging Interfaces...........................................................................................................................1-17
2 Logical Interface Configuration..............................................................................................2-1

2.1 Logical Interface Configuration Overview..................................................................................................... 2-2
2.1.1 Introduction to Logical Interfaces..........................................................................................................2-2
2.1.2 Features of the Logical Interfaces in the NE5000E............................................................................... 2-2
Issue 02 (2009-12-10) Huawei Proprietary and Confidential ix

Contents Configuration Guide - Interface Management
2.2 Configuring Logical Channel Interfaces.........................................................................................................2-2

2.2.2 Creating a Logical Channel Interface.....................................................................................................2-3
2.3 Configuring a Loopback Interface..................................................................................................................2-4
2.3.2 Creating a Loopback Interface and Configuring Its IP Address............................................................2-5
2.4 Configuring a Null Interface...........................................................................................................................2-6
2.4.2 Entering the Null Interface View...........................................................................................................2-6
2.5 Configuration Examples..................................................................................................................................2-7
2.5.1 Example for Configuring the Loopback Interface.................................................................................2-8
3 Interface Board Intermixing Configuration..........................................................................3-1

3.1 Interface Board Intermixing Configuration Overview....................................................................................3-2
3.1.1 Introduction to Interface Board Intermixing..........................................................................................3-2
3.1.2 Features of Interface Board Intermixing in the NE5000E.....................................................................3-2
3.2 Configuring the Public FIB Policy..................................................................................................................3-2
3.2.2 Configuring the Public IPv4 FIB Policy................................................................................................3-3
3.2.3 Configuring the Public IPv6 FIB Policy................................................................................................3-4
3.3 Configuring the VPN FIB Policy....................................................................................................................3-5
3.3.2 Configuring the VPN IPv4 FIB Policy..................................................................................................3-6
3.3.3 Configuring the VPN IPv6 FIB Policy..................................................................................................3-7
3.4 Configuring the Policy of Discarding All the FIB Entries..............................................................................3-8
3.4.2 Configuring the Policy of Discarding All the IPv4 FIB Entries............................................................3-9
3.4.3 Configuring the Policy of Discarding All the IPv6 FIB Entries..........................................................3-10
3.5 Configuring Overload Suspension Recovery................................................................................................3-11
3.5.2 Configuring Overload Suspension Recovery.......................................................................................3-12
3.5.3 Refreshing the FIB Policy....................................................................................................................3-13
3.6 Configuring Overload Forwarding Recovery...............................................................................................3-14
3.6.2 Configuring IPv4 FIB Overload Forwarding Recovery.......................................................................3-15
3.6.3 Configuring IPv6 FIB Overload Forwarding Recovery.......................................................................3-15
x Huawei Proprietary and Confidential Issue 02 (2009-12-10)

Configuration Guide - Interface Management Contents

3.7 Configuration Examples................................................................................................................................3-17
3.7.1 Example for Configuring the VPN IPv4 FIB Policy............................................................................3-17
3.7.2 Example for Configuring Overload Suspension Recovery..................................................................3-24
3.7.3 Example for Configuring Overload Forwarding Recovery..................................................................3-31
4 Fast Feeling Configuration.......................................................................................................4-1

4.1 Fast Feeling Configuration Overview.............................................................................................................4-2
4.1.1 Introduction to Fast Feeling................................................................................................................... 4-2
4.1.2 Fast Feeling Features Supported by the NE5000E.................................................................................4-2
4.2 Configuring Fast Feeling.................................................................................................................................4-2
4.2.2 Enabling Fast Feeling.............................................................................................................................4-3
4.3 Maintaining Fast Feeling.................................................................................................................................4-4
4.3.1 Debugging Fast Feeling......................................................................................................................... 4-4
4.3.2 Monitoring the Running of Fast Feeling................................................................................................4-4
5 Flapping Control Configuration.............................................................................................5-1

5.1 Flapping Control Configuration Overview.....................................................................................................5-2
5.1.1 Introduction to the Interface Flapping Control...................................................................................... 5-2
5.1.2 Interface Flapping Control Features Supported in the NE5000E...........................................................5-2
5.2 Configuring the Interface Flapping Control....................................................................................................5-3
5.2.2 Enabling the Flapping Control Feature..................................................................................................5-4
5.3 Maintaining the Flapping Control Feature......................................................................................................5-5
5.3.1 Clearing Flapping Control Information..................................................................................................5-5
5.3.2 Debugging the Flapping Control............................................................................................................5-6
5.3.3 Monitoring the Flapping Control on the Interface.................................................................................5-6
6 Transmission Alarm Configuration.......................................................................................6-1

6.1 Transmission Alarm Configuration Overview................................................................................................6-2
6.1.1 Introduction to Transmission Alarm Customization and Suppression...................................................6-2
6.1.2 Features of Transmission Alarm Customization and Suppression in the NE5000E..............................6-2
6.2 Configuring Transmission Alarm Customization...........................................................................................6-2
6.2.2 Configuring the Type of the Alarm That Can Affect the Physical Status of the Interface....................6-3
6.2.3 (Optional) Configuring the Respective Thresholds of B3TCA, SDBERE, and SFBERE Alarms........6-4
6.2.4 (Optional) Configuring the Type of the Alarms That Can Be Recorded to Logs..................................6-5
6.3 Configuring the Interval for Filtering Transmission Alarms..........................................................................6-7
6.3.2 Configuring the Interval for Filtering Transmission Alarms.................................................................6-7
Issue 02 (2009-12-10) Huawei Proprietary and Confidential xi

Contents Configuration Guide - Interface Management

6.4 Configuring Transmission Alarm Suppression...............................................................................................6-8
6.4.2 Configuring Transmission Alarm Suppression......................................................................................6-9
6.5 Maintaining...................................................................................................................................................6-10
6.5.1 Clearing Transmission Alarm Information..........................................................................................6-10
6.5.2 Debugging Transmission Customization and Suppression..................................................................6-11
A Glossary.....................................................................................................................................A-1
B Acronyms and Abbreviations.................................................................................................B-1
xii Huawei Proprietary and Confidential Issue 02 (2009-12-10)

Configuration Guide - Interface Management Figures
Figures
Figure 2-1 Networking diagram of configuring the loopback interface...............................................................2-8

Figure 3-1 Networking diagram of configuring the VPN IPv4 FIB policy.......................................................3-18
Figure 3-2 Networking diagram of configuring overload suspension recovery.................................................3-24
Figure 3-3 Networking diagram of configuring overload forwarding recovery................................................3-31
Figure 5-1 Diagram of the interface flapping control..........................................................................................5-3
Issue 02 (2009-12-10) Huawei Proprietary and Confidential xiii

Configuration Guide - Interface Management Tables
Tables
Table 1-1 Command line views and prompts of physical interfaces....................................................................1-3

Table 1-2 Command line views and prompts of logical interfaces......................................................................1-3
Issue 02 (2009-12-10) Huawei Proprietary and Confidential xv

Configuration Guide - Interface Management 1 Interface Basic Configuration
1 Interface Basic Configuration
About 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

Describes interfaces and link layer protocols.
1.2 Configuring the Interface Description
Describes how to configure the interface description that helps users to manage the interfaces.
1.3 Configuring the Hold-Time Interval After an Interface Becomes Up/Down
Configuring the Hold-Time Interval After an Interface Becomes Up/Down.
1.4 Configuring the Interval for Collecting the Statistics of Traffic on the Interface
Describes how to configure the interval for collecting the statistics of traffic on the interface.
1.5 Configuring the Alarm Function for Interfaces
This section describes how to configure the alarm function for interfaces.
1.6 Maintaining Interface Basic Configuration
Describes how to clear the statistics of the interface and debug the interface.
Issue 02 (2009-12-10) Huawei Proprietary and Confidential 1-1

1 Interface Basic Configuration Configuration Guide - Interface Management
1.1 Interface Basic Configuration Overview

Describes interfaces and link layer protocols.
1.1.1 Interface type

1.1.2 Interface Views and Prompts
1.1.3 Link Layer Protocols and Access Technologies
1.1.1 Interface type

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 NE5000E supports such LAN interfaces as Ethernet interfaces. Ethernet
interfaces only include GigabitEthernet interfaces.
l Wide Area Network (WAN) interfaces: routers exchange data with devices of external
networks through WAN interfaces.
Currently, the NE5000E supports such WAN interfaces as POS interfaces .
Logical Interfaces
Logical interfaces can exchange data. It, however, does not physically exist and must be created
through configuration.
Currently, the NE5000E mainly supports such logical interfaces as sub-interfaces, Eth-Trunk
interfaces, loopback interfaces, null interfaces, IP-Trunk interfaces,tunnel interfaces, and
MTunnel interfaces.
1.1.2 Interface Views and Prompts

Command views and prompts of physical interfaces supported by the NE5000E are shown in
Table 1-1; command views and prompts of logical interfaces are shown inTable 1-2.
1-2 Huawei Proprietary and Confidential Issue 02 (2009-12-10)

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

Interface Command Command Prompt
Line View
Gigabit GE interface Run the interface [HUAWEI-

Ethernet view gigabitethernet GigabitEthernet1/0/0]
interface 1/0/0 command in
the system view.
AUX interface AUX interface Run the interface [HUAWEI-Aux0/0/1]

(auxiliary view aux 0/0/1 command
interface) in the system view.
POS interface POS interface Run the interface [HUAWEI-Pos 3/0/0]

view pos 3/0/0 command
in the system view.
Table 1-2 Command line views and prompts of logical interfaces

Line View
Sub-interface Sub-interface Run the [HUAWEI-Serial1/0/0.1]

view interface serial
1/0/0.1
command in the
system view.
Eth-Trunk Eth-Trunk Run the [HUAWEI-Eth-Trunk1]

interface interface view interface eth-
trunk 1
command in the
system view.
Loopback Loopback Run the [HUAWEI-LoopBack2]

interface interface view interface
loopback 2
command in the
system view.
NULL interface NULL interface Run the [HUAWEI-NULL0]

view interface null 0
command in the
system view.
IP-Trunk IP-Trunk Run the [HUAWEI-Ip-Trunk0]

interface interface view interface ip-
trunk 0 in the
system view.


Line View
Tunnel interface Tunnel interface Run the [HUAWEI-Tunnel1/0/6]

view interface tunnel
1/0/6 command
in the system
view.
MTunnel MTunnel Run the [HUAWEI-MTunnel0]

interface interface view interface
mtunnel 0 in the
system view.
NOTE
By default, whether an interface is in the starting state depends on products or versions. If the interface is
disabled by default, run the undo shutdown command to validate the configuration.
1.1.3 Link Layer Protocols and Access Technologies

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 NE5000E 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.
l 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.
Data transmission within a VLAN does not interfere with that in other VLANs. This enhances
the network security.

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 NE5000E also supports the Multi-link Protocol (MP), which binds multiple PPP links
together to provide larger bandwidth.
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.
1.2 Configuring the Interface Description

Describes how to configure the interface description that helps users to manage the interfaces.
1.2.1 Establishing the Configuration Task

1.2.2 Configuring the Interface Description
1.2.3 Checking the Configuration
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
1 Interface type and number
2 Description of the interface

1.2.2 Configuring the Interface Description
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, Eth-
Trunk, POS, IP-Trunkinterface view.
The parameter interface-type specifies the interface type, and interface-number specifies the
interface number. For the details of interface numbering, refer to the Installation Manual of the
specific product.
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 regular-expression
The description of the interface is configured.
You can run the display interface description command to view the description of an interface.
----End
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 ] ] [ | { begin | exclude | include } regular-expression ] 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 GigabitEthernet2/0/2
Interface Description
GigabitEthernet2/0/2 Connected to PE1's GigabitEthernet 2/0/2

1.3 Configuring the Hold-Time Interval After an Interface

Becomes Up/Down
Configuring the Hold-Time Interval After an Interface Becomes Up/Down.
1.3.2 Configuring the Hold-Time Interval After an Interface Becomes Up/Down
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
1 Interface type and interface number
2 Hold-time interval after an interface becomes Up/Down
1.3.2 Configuring the Hold-Time Interval After an 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
The hold-time interval can be configured on Gigabit Ethernet interfaces.
----End
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
Describes how to configure the interval for collecting the statistics of traffic on the interface.

1.4.2 Configuring Traffic Statistics on Interfaces
1.4.3 Configuring the Global Interval for Collecting Traffic Statistics
1.4.4 Configuring the Interval for Collecting the Statistics of Traffic on the Interface

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.
NOTE
l In the NE5000E, 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
2 Interval for collecting the statistics of traffic on the interface
1.4.2 Configuring Traffic Statistics on Interfaces
Context
Do as follows on the router that needs to be configured with traffic statistics:
Procedure
Step 1 Run:
system-view

Step 2 Run the following command as required.

l To enable the traffic statistics function on all sub-interfaces, run:
subinterface traffic-statistics enable
l To enable the traffic statistics function on the sub-interfaces of a specific interface, do as

follows:
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.
By default, the traffic statistics function is enabled on main interfaces.
----End
1.4.3 Configuring the Global Interval for Collecting Traffic

Statistics
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.
NOTE
The new interval takes effect after the original interval expires. Traffic statistics are displayed in the second
periodical update after the new interval takes effect.
----End
1.4.4 Configuring the Interval for Collecting the Statistics of Traffic

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 are displayed in the second
periodical update after the new interval takes effect.
----End

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.
l Run the display interface [ interface-type [ interface-number ] ] command to check the
statistics of traffic on an interface.
l Run the display interface [ interface-type [ interface-number.subinterface-number ] ]
command to check the statistics of traffic on a sub-interface.
----End
Example
# After the traffic statistics function is enabled on a sub-interface, run the display interface
[ interface-type [ interface-number.subinterface-number ] ] command. You can view the
statistics of incoming traffic and outgoing traffic.
<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
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 Configuring the Alarm Function for Interfaces

This section describes how to configure the alarm function for interfaces.
1.5.2 Configuring the Alarm Function for Interfaces

If a large number of alarms are generated on a link, the system is busy dealing with various
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
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
1 Interface type and interface number
2 Thresholds that trigger the alarms
1.5.2 Configuring the Alarm Function for Interfaces
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 | sdh-error | input-rate | output-rate |
broadcast-threshold }
The alarm function is enabled on an interface.
Set the type of alarms as required.
l To enable the alarm function of Cyclic Redundancy Check (CRC) errors, crc-error is set.
l To enable the alarm function of Synchronous Digital Hierarchy (SDH) errors, sdh-error is
set.
l To enable the alarm function when the bandwidth utilization of the incoming traffic exceeds
the threshold, input-rate is set.
l To enable the alarm function of the bandwidth utilization of the outgoing traffic, output-
rate is set.
l To enable the alarm function of broadcast suppression, broadcast-threshold is set.
Step 3 Run:
Interfaces that support the preceding types of alarms are POS, and 10 G-WAN interfaces.
Interfaces that support the alarms of bandwidth utilization of the incoming traffic and bandwidth
utilization of the outgoing traffic are POS, 10 G-WAN, and GE interfaces.
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
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
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 6/0/0.
<HUAWEI>display current-configuration interface pos 6/0/0
interface Pos6/0/0
link-protocol ppp
undo shutdown
trap-threshold crc-error 1000 interval-second 600
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 3/0/0.
<HUAWEI>display current-configuration interface GigabitEthernet3/0/0
interface GigabitEthernet3/0/0
trap-threshold input-rate 80
trap-threshold output-rate 80
1.6 Maintaining Interface Basic Configuration

Describes how to clear the statistics of the interface and debug the interface.
1.6.1 Clearing Statistics

1.6.2 Monitoring Interface Information
1.6.3 Debugging Interfaces
1.6.1 Clearing Statistics
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.
l Run the reset reset counters if-mib interface [ interface-type [ interface-number ] ]
command in the user view to clear the interface statistics collected through the NMS.
l Run the following command in the user view to clear the statistics of the packets sent 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.
– 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.6.2 Monitoring Interface Information

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-number ] [ |
{ begin | exclude | include } regular-expression ] command to check the current operating
status of the interface and statistics collected on the interface.
l Run the display interface-statistics { interface-type interface-number } &<1-5>
[ interval interval ] [ times times ] command in any view to check statistics about traffic
on the interface.
l Run the display interface brief [ | { begin | include | exclude } regular-expression ]
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.
l Run the display ip interface [ interface-type interface-number ] command in any view to
check the IP configuration of the interface.
l 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 ] ]
l Run the display cpu-packet statistics slot { all | slot-number } command in any view to
check the statistics for packets sent to the CPU from all interfaces in the specified slot.
l Run the display cpu-packet statistics interface interface-type interface-number all
command in any view to check the statistics for packets sent to the CPU from the specified
interface.
l Run the display cpu-packet statistics interface interface-type interface-number pvc vpi/
vci command in any view to check the statistics for packets sent to the CPU from the
specified PVC of the specified interface.
l 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.
----End
1.6.3 Debugging Interfaces

Context
CAUTION
Debugging affects the performance of the system. So, after debugging, run the undo debugging
all command to disable it immediately.
When a fault occurs on an interface, run the debugging command in the user view to locate the
fault.
For the debugging commands of interfaces, refer to the HUAWEI NetEngine5000E Core Router
Configuration Guide - LAN Access & MAN Access, HUAWEI NetEngine5000E Core Router
Configuration Guide - WAN Access, and HUAWEI NetEngine5000E Core Router Debugging
Reference.

Configuration Guide - Interface Management 2 Logical Interface Configuration
2 Logical Interface Configuration
About This Chapter
Describes common logical interfaces and how to logical interfaces and provides various
configuration examples.
2.1 Logical Interface Configuration Overview

Describes various logical interfaces.
2.2 Configuring Logical Channel Interfaces
Describes how to configure a logical channel interface.
2.3 Configuring a Loopback Interface
Describes how to configure a loopback interface.
2.4 Configuring a Null Interface
Describes how to configure a null interface.
2.5 Configuration Examples
Provides several configuration examples of logical interfaces.

2 Logical Interface Configuration Configuration Guide - Interface Management
2.1 Logical Interface Configuration Overview

Describes various logical interfaces.
2.1.1 Introduction to Logical Interfaces

2.1.2 Features of the Logical Interfaces in the NE5000E
2.1.1 Introduction to Logical Interfaces

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,
loopback interfaces, null interfaces, MP-Group interfaces,IP-Trunk interfaces,Tunnel interfaces
and MTunnel interfaces.
NOTE
For the configurations of Eth-Trunk interfaces, refer to the HUAWEI NetEngine5000E Core Router
Configuration Guide - LAN Access & MAN Access.
NOTE
For the configurations of IP-Trunk interfaces, refer to the HUAWEI NetEngine5000E Core Router
Configuration Guide - WAN Access.
NOTE
For the details of the tunnel interface, refer to "VPN Tunnel" in the HUAWEI NetEngine5000E Core Router
Feature Description - VPN. For the configuration of the tunnel interface, refer to the chapter "VPN Tunnel
Management Configuration" in the HUAWEI NetEngine5000E Core Router Configuration Guide -
VPN.
NOTE
For the details of MTI interfaces, refer to "Multicast VPN Configuration" in the HUAWEI
NetEngine5000E Core Router Configuration Guide - IP Multicast.
2.1.2 Features of the Logical Interfaces in the NE5000E

The NE5000E 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.
l Loopback interface: It is mainly used when the status of the interface needs to be always
Up or the interface needs to be configured with 32-bit subnet mask.
l Null interface: It is mainly used in route filtering because any network packets sent to this
interface are discarded.
2.2 Configuring Logical Channel Interfaces

Describes how to configure a logical channel interface.

2.2.2 Creating a Logical Channel Interface

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
1 Number of the logical channel interface
2.2.2 Creating a Logical Channel Interface
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.
Note that logical channel interface can only be created on main control board. The value of
interface-number ranges from 0 to 1023.
----End
Prerequisite
The configurations of the configuring logical channel interfaces function are complete.

Procedure
Step 1 Run the display interface logic-channel [ interface-number ] [ | { begin | exclude | include }
regular-expression ] 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 : DOWN
Line protocol current state :UP (spoofing)
Description: Logic-Channel0 Interface
2.3 Configuring a Loopback Interface

Describes how to configure a loopback interface.

2.3.2 Creating a Loopback Interface and Configuring Its IP Address
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.
l 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.

No. Data
1 Number of the loopback interface
2 IP address of the loopback interface
2.3.2 Creating a Loopback Interface and Configuring Its IP Address

Procedure
Step 1 Run:
system-view

Step 2 Run:
interface loopback loopback-number
A loopback interface is created.

The number of loopback interface ranges from 0 to 1023. You can create up to 1024 loopback
interfaces.
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 ]
The IP address of the loopback interface is configured.
----End

Prerequisite
The configurations of the configuring a loopback interface function are complete.
Procedure
Step 1 Run the display interface loopback [ loopback-number ] [ | { begin | exclude | include }
regular-expression ] 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
Statistics last cleared: 2008-08-02 15:32:27
0 unicast,0 broadcast,0 multicast
0 errors,0 drops,0 unknownprotocol
0 errors,0 drops
2.4 Configuring a Null Interface

Describes how to configure a null interface.

2.4.2 Entering the Null Interface View

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.4.2 Entering the Null Interface View

Procedure
Step 1 Run:
system-view

Step 2 Run:
interface null 0

The null interface view is displayed.

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

Prerequisite
The configurations of the configuring a null interface function are complete.
Procedure
Step 1 Run the display interface null [ 0 ] [ | { begin | exclude | include } regular-expression ]
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
Statistics last cleared: 2008-08-02 15:32:27
0 errors,0 drops,0 unknownprotocol
0 errors,0 drops

Provides several configuration examples of logical interfaces.
2.5.1 Example for Configuring the Loopback Interface

2.5.1 Example for Configuring the Loopback Interface

Networking Requirements
CAUTION
For the NE5000E, the interface is numbered as slot number/card number/interface number. For
the NE5000E cluster, the interface is numbered as chassis ID/slot number/card number/interface
number. The chassis ID must be specified along with the slot number.
After a loopback interface is configured with IP address, it can work as the lending party in the
IP unnumbered. Loopback interface can use 32-bit mask.
Figure 2-1 Networking diagram of configuring the loopback interface

Loopback1
10.1.1.1/32
POS1/0/0
POS1/0/0
RouterA
10.1.1.2/30 RouterB
Configuration Roadmap
The configuration roadmap is as follows:
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
l IP address of the loopback interface
l Interface that borrows the IP address
Procedure
Step 1 Configure Router A.
# Create a loopback interface and allocate an IP address for it.
<HUAWEI> system-view
[HUAWEI] sysname RouterA
[RouterA] interface loopback 1
[RouterA-LoopBack1] ip address 10.1.1.1 32
[RouterA-LoopBack1] quit

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

<HUAWEI> system-view
[HUAWEI] sysname RouterB
[RouterB] interface pos 1/0/0
[RouterB-Pos1/0/0] ip address 10.1.1.2 30
[RouterB-Pos1/0/0] undo shutdown
[RouterB-Pos1/0/0] quit
Step 4 Check the configuration.

# Display the status of Pos 1/0/0.
<RouterA> display interface pos 1/0/0
Pos1/0/0 current state : UP
Lin protocol current state : UP
Last line protocol up time: 2007-11-03, 15:27:37
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 through Router B, it indicates that Router A can normally communicate
with Router B.
----End
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
l Configuration files of Router B

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

Configuration Guide - Interface Management 3 Interface Board Intermixing Configuration
3 Interface Board Intermixing Configuration
About This Chapter
Describes the fundamentals and configuration procedures of interface board intermixing.
3.1 Interface Board Intermixing Configuration Overview

This section describes how to process the FIB and the principle of the FIB processing when the
interface boards of different FIB route prefix capacities are plugged in the same router.
3.2 Configuring the Public FIB Policy
Describes how to configure the public IPv4 Forwarding Information Base (FIB) policy and
public IPv6 FIB policy.
3.3 Configuring the VPN FIB Policy
Describes how to configure the VPN IPv4 FIB policy and VPN IPv6 FIB policy.
3.4 Configuring the Policy of Discarding All the FIB Entries
Describes how to configure the policy of discarding all the IPv4 FIB entries and IPv6 FIB entries.
3.5 Configuring Overload Suspension Recovery
Describes how to configure overload suspension recovery.
3.6 Configuring Overload Forwarding Recovery
Describes how to configure overload forwarding recovery.
Provides several configuration examples of interface board intermixing.

3 Interface Board Intermixing Configuration Configuration Guide - Interface Management
3.1 Interface Board Intermixing Configuration Overview

This section describes how to process the FIB and the principle of the FIB processing when the
interface boards of different FIB route prefix capacities are plugged in the same router.
3.1.1 Introduction to Interface Board Intermixing

3.1.2 Features of Interface Board Intermixing in the NE5000E
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 NE5000E

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

Describes how to configure the public IPv4 Forwarding Information Base (FIB) policy and
public IPv6 FIB policy.


3.2.2 Configuring the Public IPv4 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.

l 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
1 Interface board number
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-number
The public IPv4 FIB policy is configured on the interface board.
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-number
The IPv4 FIB module is refreshed so that this public IPv4 FIB policy is applied to the interface
board.
----End
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-number
The public IPv6 FIB policy is configured on the interface board.
NOTE
takes effect.
Step 3 Run:
refresh ipv6 fib slot slot-number
The IPv6 FIB module is refreshed so that this public IPv6 FIB policy is applied to the interface
board.
----End
Prerequisite
The configurations of the configuring the public FIB policy function are complete.

Procedure
l Run the display fib-policy slot slot-number command to check the FIB policy applied to
the IPv4 FIB module on the interface board.
l Run the display ipv6 fib-policy slot slot-number command to check the FIB policy applied
to the IPv6 FIB module on the interface board.
l Run the display fib [ slot-number ] statistics allcommand to check the FIB statistics of the
IPv4 FIB module on the interface board.
l Run the display ipv6 fib [ slot-number ] statistics all [ | count ] [ | { begin | include |
exclude } regular-expression ] command to check the FIB statistics of the IPv6 FIB module
on the interface board.
----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] display fib 1 statistics all
IPv4 FIB Route Prefix Capacity : 1000
IPv4 FIB Total Route Prefix Count : 4, Entry Count : 4
IPv4 FIB Public Route Prefix Count :4, Entry Count : 4
IPv4 FIB Vpn-instance VPNB Route Prefix Count : 0, Entry Count : 0
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] display ipv6 fib 1 statistics all
IPv6 FIB Total Route Prefix Count :1,Entry Count : 1
IPv6 FIB Public Route Prefix Count :1,Entry Count : 1
3.3 Configuring the VPN FIB Policy

Describes how to configure the VPN IPv4 FIB policy and VPN IPv6 FIB policy.

3.3.2 Configuring the VPN IPv4 FIB Policy

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
2 Type and name of the VPN instance
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-number
The VPN IPv4 FIB policy is configured on the interface board.

NOTE
takes effect.
Step 3 Run:
The IPv4 FIB policy is refreshed so that this VPN IPv4 FIB policy is applied to the interface
board.
----End

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 vpn6-instance vpn-instance-name slot slot-number
The VPN IPv6 FIB policy is configured on the interface board.
NOTE
takes effect.
Step 3 Run:
The IPv6 FIB policy is refreshed so that this VPN IPv6 FIB policy is applied to the interface
board.
----End

Prerequisite
The configurations of the configuring the VPN FIB policy function are complete.
Procedure

l Run the display fib [ slot-number ] statistics all command to check the FIB statistics of
----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.
IPv4 FIB Total Route Prefix Count :7, Entry Count : 7
IPv4 FIB Public Route Prefix Count : 4, Entry Count : 4
IPv4 FIB Vpn-instance VPNB Route Prefix Count :3, Entry Count : 3
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 IPv6 FIB route prefix
capacity and the IPv6 FIB policy statistics of the specified interface board.
IPv6 Vpn-instance VPN6A Route Prefix Count :0, Entry Count : 0
3.4 Configuring the Policy of Discarding All the FIB Entries

Describes how to configure the policy of discarding all the IPv4 FIB entries and IPv6 FIB entries.

3.4.2 Configuring the Policy of Discarding All the IPv4 FIB Entries

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
2 Type of the forwarding entries to be discarded
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-number
The policy of discarding all the IPv4 forwarding entries is configured on the interface.

NOTE
takes effect.
Step 3 Run:
The IPv4 FIB policy is refreshed so that this policy is applied to the interface board.
----End
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-number
The policy of discarding all the IPv6 forwarding entries is configured on the interface.
NOTE
takes effect.
Step 3 Run:
The IPv6 FIB policy is refreshed so that this policy is applied to the interface board.
----End
Prerequisite
The configurations of the configuring the policy of discarding all the FIB entries function are
complete.
Procedure

----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.
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.
IPv6 FIB Vpn-instance VPN6A Route Prefix Count :0, Entry Count : 0
3.5 Configuring Overload Suspension Recovery

Describes how to configure overload suspension recovery.

3.5.2 Configuring Overload Suspension Recovery
3.5.3 Refreshing the FIB Policy

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
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-number
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
Postrequisite
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.

3.5.3 Refreshing the FIB Policy
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:
The IPv4 FIB is refreshed so that overload suspension recovery is applied to the specified
interface board.
Step 3 Run:
The IPv6 FIB is refreshed so that overload suspension recovery is applied to the specified
interface board.
----End
Prerequisite
The configurations of the configuring overload suspension recovery function are complete.
Procedure
l Run the display fib overload state slot slot-number command to check the overload status
of the IPv4 FIB module on the interface board.
l Run the display ipv6 fib overload state slot slot-number 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] display fib statistics all
Run the display fib slot-number 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.
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

Describes how to configure overload forwarding recovery.

3.6.2 Configuring IPv4 FIB 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.
No. Data
2 Type of the forwarding entries in the overload forwarding state
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-number
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:
The IPv4 FIB is refreshed so that overload forwarding recovery is applied to the specified
interface board.
----End
Context
Do as follows on the router with the IPv6 FIB module in the overload forwarding state:
Procedure
Step 1 Run:
system-view

Step 2 Run:
recover ipv6 fib overload forward slot slot-number
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:
The IPv6 FIB is refreshed so that overload forwarding recovery is applied to the specified
interface board.
----End

Prerequisite
The configurations of the configuring overload forwarding recovery function are complete.
Procedure
l Run the display fib overload state slot slot-number command to check the overload status
of the IPv4 FIB module on the interface board.
l Run the display ipv6 fib overload state slot slot-number 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] display fib statistics all
Run the display fib slot-number statistics all command, and you can view the IPv4 FIB route
prefix capacity of the specified interface board.

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.

Provides several configuration examples of interface board intermixing.
3.7.1 Example for Configuring the VPN IPv4 FIB Policy

3.7.2 Example for Configuring Overload Suspension Recovery
3.7.3 Example for Configuring Overload Forwarding Recovery
3.7.1 Example for Configuring the VPN IPv4 FIB Policy

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

Figure 3-1 Networking diagram of configuring the VPN IPv4 FIB policy
VPNA
VPNA VPNA
VPNA
POS1/0/0
POS1/0/0
50.1.1.2/24
CE1 10.1.1.1/24 CE3
POS2/0/0 POS1/0/0 POS1/0/1 POS2/0/0

10.1.1.2/24 30.1.1.2/24 40.1.1.1/24 50.1.1.1/24
POS1/0/0 POS1/0/0
POS3/0/0 30.1.1.1/24 POS3/0/0
P 40.1.1.2/24
20.1.1.2/24 PE1 PE2 60.1.1.1/24
POS1/0/0 POS1/0/0
CE2 CE4
20.1.1.1/24 60.1.1.2/24
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
l 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 NetEngine5000E Core Router Configuration Guide - VPN.

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 Flag TimeStamp Interface TunnelID
127.0.0.1/32 127.0.0.1 HU t[55] InLoop0 0x0
127.0.0.0/8 127.0.0.1 U t[55] InLoop0 0x0
1.1.1.1/32 127.0.0.1 HU t[55] InLoop0 0x0
30.1.1.1/32 127.0.0.1 HU t[2521] InLoop0 0x0
30.1.1.0/24 30.1.1.1 U t[2521] [No Intf] 0x0
30.1.1.2/32 30.1.1.2 HU t[2521] [No Intf] 0x0
40.1.1.0/24 30.1.1.2 DGU t[3554] [No Intf] 0x1002001
2.1.1.1/32 30.1.1.2 DGHU t[3554] [No Intf] 0x1002000
3.1.1.1/32 30.1.1.2 DGHU t[44469] [No Intf] 0x1002003
# View the number of the VPN forwarding entries of VPN A on interface board 2.
[PE1] display fib 2 vpn-instance VPNA
FIB Table:
10.1.1.2/32 127.0.0.1 HU t[47861] InLoop0 0x0
10.1.1.0/24 10.1.1.2 U t[47861] POS2/0/0 0x0
10.1.1.1/32 10.1.1.1 HU t[47861] POS2/0/0 0x0
50.1.1.0/24 30.1.1.2 DGU t[48014] [No Intf] 0x1002005
50.1.1.2/32 30.1.1.2 DGHU t[48014] [No Intf] 0x1002005
# View the number of the VPN forwarding entries of VPN B on interface board 2.
[PE1] display fib 2 vpn-instance VPNB
FIB Table:
20.1.1.2/32 127.0.0.1 HU t[51766] InLoop0 0x0
20.1.1.0/24 20.1.1.2 U t[51766] [No Intf] 0x0
20.1.1.1/32 20.1.1.1 HU t[51766] [No Intf] 0x0
60.1.1.0/24 30.1.1.2 DGU t[51766] [No Intf] 0x1002005
60.1.1.2/32 30.1.1.2 DGHU t[51766] [No Intf] 0x1002005
Step 3 Configure the FIB policy.

[PE1] apply fib-policy vpn-instance VPNA slot 2
[PE1] apply fib-policy vpn-instance VPNB slot 3
The configuration of PE2 is similar to that of PE1.

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

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.

[PE1] display fib 2 vpn-instance VPNA

FIB Table:
10.1.1.2/32 127.0.0.1 HU t[47861] InLoop0 0x0
10.1.1.0/24 10.1.1.2 U t[47861] POS2/0/0 0x0
10.1.1.1/32 10.1.1.1 HU t[47861] POS2/0/0 0x0
50.1.1.0/24 30.1.1.2 DGU t[48014] [No Intf] 0x1002005
50.1.1.2/32 30.1.1.2 DGHU t[48014] [No Intf] 0x1002005
# View the VPN forwarding entries of VPN B on interface board 2 as follows. After the 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

import-route direct
#
return
l Configuration file of PE1
#
sysname PE1
#
ip vpn-instance VPNB
route-distinguisher 2:2
vpn-target 2:2 export-extcommunity
vpn-target 2:2 import-extcommunity
#
ip vpn-instance VPNA
#
mpls lsr-id 1.1.1.1
mpls
lsp-trigger all
#
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

#
apply fib-policy vpn-instance VPNA slot 2
apply fib-policy vpn-instance VPNB slot 3
#
return
l Configuration file of P
#
sysname P
#
mpls lsr-id 2.1.1.1
mpls
lsp-trigger all
#
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
lsp-trigger all
#
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
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.2 Example for Configuring Overload Suspension Recovery
CAUTION
Figure 3-2 Networking diagram of configuring overload suspension recovery
VPNA
VPNA VPNA
VPNA
POS1/0/0 POS1/0/0
10.1.1.1/24 50.1.1.2/24
CE1 CE3
POS1/0/0 POS1/0/1
POS2/0/0
POS2/0/0 30.1.1.2/24 40.1.1.1/24
50.1.1.1/24
10.1.1.2/24
POS3/0/0 POS1/0/0 POS1/0/0 POS3/0/0
20.1.1.2/24 PE1 30.1.1.1/24 P 40.1.1.2/24 PE2 60.1.1.1/24
CE2 POS1/0/0 POS1/0/0 CE4
20.1.1.1/24 60.1.1.2/24
VPNB 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.
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
# 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.
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.
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] recover fib overload suspend slot 2
[PE1] recover fib overload suspend 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
Configuration Files
#
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
lsp-trigger all
#
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
#
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
lsp-trigger all
#
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
lsp-trigger all
#
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
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

CAUTION
Figure 3-3 Networking diagram of configuring overload forwarding recovery
VPNA
VPNA VPNA
VPNA
POS1/0/0 POS1/0/0
50.1.1.2/24
CE1 10.1.1.1/24 CE3
POS1/0/0 POS1/0/1
POS2/0/0 POS2/0/0
30.1.1.2/24 40.1.1.1/24
10.1.1.2/24 50.1.1.1/24
POS3/0/0 POS1/0/0 POS1/0/0 POS3/0/0
20.1.1.2/24 PE1 30.1.1.1/24 P 40.1.1.2/24 PE2 60.1.1.1/24
CE2 POS1/0/0 POS1/0/0 CE4

20.1.1.1/24 60.1.1.2/24
VPNB 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.


3. Configure overload forwarding recovery on interface board 2.
4. Configure overload forwarding recovery on interface board 3.
Data Preparation
l VPN instance name
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.
Step 4 Configure the FIB policy on the interface board and refresh the FIB policy.
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] recover fib overload forward slot 2
[PE1] recover fib overload forward 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
#
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
lsp-trigger all
#
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
#
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
lsp-trigger all
#
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
#
#
#
mpls lsr-id 3.1.1.1
mpls
lsp-trigger all
#
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
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

Configuration Guide - Interface Management 4 Fast Feeling Configuration
4 Fast Feeling Configuration
About This Chapter
Describes the fundamentals and configuration procedures of fast fault sensing.
4.1 Fast Feeling Configuration Overview

Describes the concepts of the fast feeling.
4.2 Configuring Fast Feeling
Describes how to configure the fast feeling.
4.3 Maintaining Fast Feeling
Describes how to maintain the fast feeling feature.

4 Fast Feeling Configuration Configuration Guide - Interface Management
4.1 Fast Feeling Configuration Overview

Describes the concepts of the fast feeling.
4.1.1 Introduction to Fast Feeling

4.1.2 Fast Feeling Features Supported by the NE5000E
4.1.1 Introduction to Fast Feeling

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 NE5000E

In the NE5000E, 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

Describes how to configure the fast feeling.

4.2.2 Enabling Fast Feeling
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.

Configuration Guide - Interface Management 4 Fast Feeling Configuration
Data Preparation
To configure the fast feeling, you need the following data.
No. Data
1 Number of the interface on the router
4.2.2 Enabling Fast Feeling
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
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
route interface status: up
ISIS interface status: down

4 Fast Feeling Configuration Configuration Guide - Interface Management
4.3 Maintaining Fast Feeling

Describes how to maintain the fast feeling feature.
4.3.1 Debugging Fast Feeling

4.3.2 Monitoring the Running of Fast Feeling
4.3.1 Debugging Fast Feeling
Context
CAUTION
When a fast feeling fault occurs, run the following debugging command in the user view to
locate the fault.
For the procedure of displaying the debugging information, refer to "Information Center
Configuration" in the HUAWEI NetEngine5000E Core Router Configuration Guide - System
Management. For the description of debugging commands, refer to the HUAWEI
NetEngine5000E Core Router Debugging Reference.
Procedure
Step 1 Run the debugging ifnet fastfeeling [ interface interface-type interface-number ] command in
the user view to debug the fast feeling of the interface.
----End
4.3.2 Monitoring the Running 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

Configuration Guide - Interface Management 5 Flapping Control Configuration
5 Flapping Control Configuration
About This Chapter
Describes the fundamentals and configuration procedures of interface flapping control.
5.1 Flapping Control Configuration Overview

Describes the principle and concepts of the interface flapping control.
5.2 Configuring the Interface Flapping Control
Describes how to configure the interface flapping control.
5.3 Maintaining the Flapping Control Feature
Describes how to maintain the flapping control feature.

5 Flapping Control Configuration Configuration Guide - Interface Management
5.1 Flapping Control Configuration Overview

Describes the principle and concepts of the interface flapping control.
5.1.1 Introduction to the Interface Flapping Control

5.1.2 Interface Flapping Control Features Supported in the NE5000E
5.1.1 Introduction to the Interface Flapping Control

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 NE5000E

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.
l 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.
l 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.
l 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 NE5000E, 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.

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

Describes how to configure the interface flapping control.
5.2.2 Enabling the Flapping Control Feature
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.
No. Data
1 Interface number of a router
2 Suppress threshold of the interface

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

Procedure
Step 1 Run:
system-view

Step 2 Run:
NOTE
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

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 decay-ok decay-ng ceiling
4.000 2.000 54 54 6.000
5.3 Maintaining the Flapping Control Feature

Describes how to maintain the flapping control feature.
5.3.1 Clearing Flapping Control Information

5.3.2 Debugging the Flapping Control
5.3.3 Monitoring the Flapping Control on the Interface
5.3.1 Clearing Flapping Control Information
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

5.3.2 Debugging the Flapping Control

Context
CAUTION
When an interface flapping control fault occurs, run the following debugging command in the
user view to locate the fault.
For the procedure of displaying the debugging information, refer to "Information Center
Configuration" in the HUAWEI NetEngine5000E Core Router Configuration Guide - System
Management. For the description of debugging commands, refer to the HUAWEI
Procedure
Step 1 Run the debugging ifnet control-flap [interface interface-type interface-number ] command
in the user view to debug the flapping control on the interface.
----End
5.3.3 Monitoring the Flapping Control on the Interface

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

Configuration Guide - Interface Management 6 Transmission Alarm Configuration
6 Transmission Alarm Configuration
About This Chapter
Describes the fundamentals and configuration procedures of transmission alarm customization

and suppression.
6.1 Transmission Alarm Configuration Overview

Describes the concepts, implementation, and application of transmission alarm customization
and suppression.
6.2 Configuring Transmission Alarm Customization
Describes how to configure transmission alarm customization.
6.3 Configuring the Interval for Filtering Transmission Alarms
Describes how to configure transmission alarm filtering.
6.4 Configuring Transmission Alarm Suppression
Describes how to configure transmission alarm suppression.
6.5 Maintaining
Describes how to maintain transmission alarm customization and suppression.

6 Transmission Alarm Configuration Configuration Guide - Interface Management
6.1 Transmission Alarm Configuration Overview

Describes the concepts, implementation, and application of transmission alarm customization
and suppression.
6.1.1 Introduction to Transmission Alarm Customization and Suppression

6.1.2 Features of Transmission Alarm Customization and Suppression in the NE5000E
6.1.1 Introduction to Transmission Alarm Customization and

Suppression
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.
l 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 NE5000E
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 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.
6.2 Configuring Transmission Alarm Customization

Describes how to configure transmission alarm customization.


6.2.2 Configuring the Type of the Alarm That Can Affect the Physical Status of the Interface
6.2.3 (Optional) Configuring the Respective Thresholds of B3TCA, SDBERE, and SFBERE
Alarms
6.2.4 (Optional) Configuring the Type of the Alarms That Can Be Recorded to Logs

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
2 Type of the alarm that can affect the physical status of the interface
3 (Optional) Respective thresholds of B3TCA, SDBERE, and SFBERE alarms
4 (Optional) Type of the alarm that can record logs
6.2.2 Configuring the Type of the Alarm That Can Affect the
Physical Status of the Interface
Procedure
Step 1 Run:
system-view

Step 2 Run:


The supported interfaces are 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
Context
Do as follows on the interface connected to the transmission equipment:
Procedure
Step 1 Run:
system-view

Step 2 Run:

The supported interfaces are 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 NE5000E 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
Procedure
Step 1 Run:
system-view

Step 2 Run:

The supported interfaces are 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 | otu-
sf-ber | pais | pm-bdi | pm-tim | pplm | prdi | prei | puneq | rdool | r-lof | r-
los | r-oof | rrool | sdbere | sfbere | sm-bdi | sm-iae | sm-tim | trool } *
The alarms recorded to logs after being generated are enabled.

The hardware supports different types of alarms. Thus, not all interfaces support the 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

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 | otu-

lom | otu-sd-ber | otu-sf-ber | pais | pm-bdi | pm-tim | pplm | prdi | prei | puneq |
rdool | r-lof | r-los | r-oof | rrool | sdbere | sfbere | sm-bdi | sm-iae | sm-tim | trool |
wlnk ] * command to check alarm configuration on the interface.
l Run the display transmission-alarm threshold [ interface-type interface-number ]
command check the respective thresholds of B3TCA, SDBERE, and SFBERE alarms 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
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
Describes how to configure transmission alarm filtering.

6.3.2 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.
No. Data
2 Filtering timer parameter
6.3.2 Configuring the Interval for Filtering Transmission Alarms
Procedure
Step 1 Run:
system-view


Step 2 Run:

Step 3 Run:
transmission-alarm holdoff-timer holdoff-time
Filtering function is enabled and the filtering timer is set.

If the interval for generating and clearing the alarms is smaller than the set interval, the alarm
signal is regarded as the burr and is filtered. Otherwise, the alarm signal is normal.
By default, transmission alarm filtering is not enabled.
To configure transmission alarm filtering on multiple interfaces, you can repeat Step 2 and Step
3.
----End

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 | otu-
lom | otu-sd-ber | otu-sf-ber | pais | pm-bdi | pm-tim | pplm | prdi | prei | puneq |
rdool | r-lof | r-los | r-oof | rrool | sdbere | sfbere | sm-bdi | sm-iae | sm-tim | trool |
wlnk ] * command to check the alarm configuration.
----End
Example
If the filtering function is enabled, you can view that the suppression function is enabled.
<HUAWEI> display transmission-alarm configuration pos 1/2/0
Interface: Pos1/2/0
Filter function: enabled (Holdtime is 55)
Suppress value: 999
Ceiling value: 6000
Reuse value: 500
6.4 Configuring Transmission Alarm Suppression

Describes how to configure transmission alarm suppression.


6.4.2 Configuring Transmission Alarm Suppression

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
1 Interface Type and number.
2 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

Procedure
Step 1 Run:
system-view

Step 2 Run:


Step 3 Run:
transmission-alarm damping [ ceiling ceiling | reuse reuse | suppress suppress |
decay-ok decay-ok | decay-ng decay-ng ] *
Suppression is enabled and suppression parameters are set.

By default, transmission alarm suppression is not enabled.
----End

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
Describes how to maintain transmission alarm customization and suppression.
6.5.1 Clearing Transmission Alarm Information

6.5.2 Debugging Transmission Customization and Suppression
6.5.1 Clearing Transmission Alarm Information

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.

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
6.5.2 Debugging Transmission Customization and Suppression

Context
CAUTION
When transmission alarm customization and suppression malfunction, run the following
debugging commands in the user view to view the debugging, and locate and analyze the fault.
For the procedure of displaying the debugging information, refer to the chapter "Information
Center Configuration" in the HUAWEI NetEngine5000E Core Router Configuration Guide -
System Management. For the description of debugging commands, refer to the HUAWEI
Procedure
l Run the debugging transmission-alarm configuration process command in the user view
to debug alarm configuration processing.
l Run the debugging transmission-alarm damping process command in the user view to
debug alarm suppression processing .
----End

Configuration Guide - Interface Management A Glossary
A 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 (2009-12-10) Huawei Proprietary and Confidential A-1

A Glossary Configuration Guide - Interface Management
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.
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.
X
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.
A-2 Huawei Proprietary and Confidential Issue 02 (2009-12-10)

Configuration Guide - Interface Management B Acronyms and Abbreviations
B Acronyms and Abbreviations
Collates frequently used acronyms and abbreviations in this document.

A
AA Anonymous Access
AAA Authentication, Authorization and Accounting
AAL ATM Adaptation Layer
AAL1 ATM Adaptation Layer Type 1
ACL Access Control List
ADSL Asymmetric Digital Subscriber Line
AM Analog Modem
AMI Alternate Mark Inversion
ANSI American National Standard Institute
ARP Address Resolution Protocol
ATM Asynchronous Transfer Mode
AU Administrative Unit
AUG Administrative Unit Group
AUX Auxiliary (port)
AUAIS Administrative Unit Alarm Indication Signal
B
B3TCA B3 Threshold Crossing Alarm
Issue 02 (2009-12-10) Huawei Proprietary and Confidential B-1

B Acronyms and Abbreviations Configuration Guide - Interface Management
BAS Broadband Access Server

BGP Border Gateway Protocol
BRI Basic Rate Interface
C
CAR Committed Access Rate
CBR Constant Bit Rate
CC Call Control
CCITT International Telegraph and Telephone Consultative Committee
CD Carrier Detect
CDV Cell Delay Variation
CHAP Challenge Handshake Authentication Protocol
CPE Customer Premises Equipment
CPOS Channelized-POS
CSMA Carrier Sense Multiple Access
CUG Closed User Group
D
DCC Data Communication Channel
DCD Data Carrier Detected
DCE Data Circuit-terminating Equipment
DDN Digital Data Network
DHCP Dynamic Host Configuration Protocol
DIP Dual-In-line Package
DLCI Data Link Control Identifier
DLSw Data Link Switching
DNS Domain Name System
DSL Digital Subscriber Line
DSLAM DSL Access Multiplexer
DSR Data Set Ready
DSS1 Digital Subscriber Signaling No.1
DTE Data Terminal Equipment
B-2 Huawei Proprietary and Confidential Issue 02 (2009-12-10)

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

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
L
L2TP Layer 2 Tunneling Protocol
LAIS Line Alarm Indication Signal
LAN Local Area Network
LAPB Link Access Procedure, Balanced
LC Line Card
LCD Loss of Code Group Synchronization
LCI Logic Channel Identifier
LCP Link Control Protocol
LDD Laser Detector Diode

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
MFR Multiple Frame Relay
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

OAM Operation, Administration and Maintenance

OC-3 OC-3
OOF Out of Frame
OSI Open System Interconnection
P
PAD Packet Assembler/ Disassembler
PAIS Path Alarm Indication Signal
PAP Password Authentication Protocol
PBX Private Branch Exchange
PC Personal Computer
PCI Protocol Control Information
PCM Pulse-Code Modulation
POH Path Overhead
POS Packet Over SDH/SONET
PPP Point-to-Point Protocol
PPLM Path Signal Label Mismatch
PPPoA PPPoA
PPPoE PPP over Ethernet
PRDI Path Remote Defect Indication
PREI Path Remote Error Indication
PRI Primary Rate Interface
PSE Packet Switching Exchange
PSTN Public Switched Telephone Network
PUNEQ Path Unequipped Indication
PVC Permanent Virtual Circuit
Q
QoS Quality of Service
R
RADIUS Remote Authentication Dial in User Service

RAS Remote Access Server

RDOOL Receive Data Out of Lock
RFC Request for Comments
RIP Routing Information Protocol
ROA Recognized operating Agency
RPC Raman Pump Amplifier Unit For C-band
RROOL Receive Reference Out of Lock
RSOH Regenerator Section Overhead
RSU Routing Switch Unit
RTP Real-time Transport Protocol
RTU Remote Test Unit
S
SABM Set Asynchronous Balanced Mode
SDBERE Signal Degrade Threshold Alarm
SDH Synchronous Digital Hierarchy
SDLC Synchronous Data Link Control
SDSL Symmetrical Digital Subscriber Line
SF Signal Failure
SFBERE Signal Fail Threshold Alarm
SGSN Serving GPRS Support Node
SLIP Serial Line Internet Protocol
SNA Systems Network Architecture
SNAP Sub Network Access Point
SNMP Simple Network Management Protocol
SNP Sequence Number PDUs
SOH Section Overhead
SONET Synchronous Optical Network
SP Service Provider
STM-1 SDH Transport Module -1
SVC Switched Virtual Channel

T
TA Terminal Adapter
TACAC Terminal Access Controller Access Control System
S
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
WLNK WAN Interface Link Stauts Alarm
WWW World Wide Web
X
XOT X.25 Over TCP


Configuration Guide - Interface Management (V300R007C00 - 02)

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 (V300R007C00 - 02)

Uploaded by

Copyright:

Available Formats

HUAWEI NetEngine5000E Core Router

Configuration Guide - Interface

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2009-12-10) Huawei Proprietary and Confidential i

About This Document

Product Name Version

HUAWEI NetEngine5000E V300R007C00

Issue 02 (2009-12-10) Huawei Proprietary and Confidential iii

l Network monitoring engineer

3 Interface Board This chapter describes the fundamentals and configuration

4 Fast Feeling This chapter describes the principles and configuration

5 Flapping Control This chapter describes the principles and configuration

6 Transmission Alarm This chapter describes the fundamentals and configuration

A Glossary This appendix collates frequently-used terms in this

B Acronyms and This appendix collates frequently used acronyms and

Indicates a hazard with a high level of risk, which if not

iv Huawei Proprietary and Confidential Issue 02 (2009-12-10)

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

Indicates a tip that may help you solve a problem or save

Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

Issue 02 (2009-12-10) Huawei Proprietary and Confidential v

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

# A line starting with the # sign is comments.

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

vi Huawei Proprietary and Confidential Issue 02 (2009-12-10)

Double-click Press the primary mouse button twice continuously and

Updates in Issue 02 (2009-12-10)

Updates in Issue 01 (2009-09-05)

Issue 02 (2009-12-10) Huawei Proprietary and Confidential vii

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

2 Logical Interface Configuration..............................................................................................2-1

Issue 02 (2009-12-10) Huawei Proprietary and Confidential ix

2.2 Configuring Logical Channel Interfaces.........................................................................................................2-2

3 Interface Board Intermixing Configuration..........................................................................3-1

x Huawei Proprietary and Confidential Issue 02 (2009-12-10)

3.6.4 Checking the Configuration.................................................................................................................3-16

4 Fast Feeling Configuration.......................................................................................................4-1

5 Flapping Control Configuration.............................................................................................5-1

6 Transmission Alarm Configuration.......................................................................................6-1

Issue 02 (2009-12-10) Huawei Proprietary and Confidential xi

6.3.3 Checking the Configuration...................................................................................................................6-8

xii Huawei Proprietary and Confidential Issue 02 (2009-12-10)

Figure 2-1 Networking diagram of configuring the loopback interface...............................................................2-8

Issue 02 (2009-12-10) Huawei Proprietary and Confidential xiii

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

Issue 02 (2009-12-10) Huawei Proprietary and Confidential xv

1 Interface Basic Configuration

About This Chapter

1.1 Interface Basic Configuration Overview

Issue 02 (2009-12-10) Huawei Proprietary and Confidential 1-1