NE40E-X1&NE40E-X2 Product Description(V600R003C00_02) (1)

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterV600R003C00

Product Description

Issue 02

Date 2011-08-12

HUAWEI TECHNOLOGIES CO., LTD.

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

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

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

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

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

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis document describes the product positioning and features, product architecture, link features,service features, application scenarios, operation and maintenance, and technical specificationsof the HUAWEI NE40E-X1 & NE40E-X2 device.

This document provides an overall description of the HUAWEI NE40E-X1 & NE40E-X2device, which helps intended readers get a general understanding of all the product features.

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

Product Name Version

HUAWEI NE40E-X1 &NE40E-X2 Universal ServiceRouter

V600R003C00

Intended AudienceThis document is intended for:

l Network planning engineersl Hardware installation engineersl Commissioning engineersl Data configuration engineersl On-site maintenance engineersl Network monitoring engineersl System maintenance engineers

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

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description About This Document


ii

Symbol Description

DANGERIndicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

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

NOTE Provides additional information to emphasize or supplementimportant points of the main text.

Change HistoryUpdates between document issues are cumulative. Therefore, the latest document issue containsall updates made in previous issues.

Changes in Issue 02 (2011-08-12)The second commercial release has the following updates:

l Service Features– 7.12 Clock. The performance monitoring function on Passive ports of a 1588v2 device

is added.l Operation and Maintenance

– 9.6 System Test and Diagnosis. The packet capture function is added.

Changes in Issue 01 (2011-05-30)Initial field trial release.

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description About This Document


iii

Contents

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

1 New Features of V600R003C00...................................................................................................1

2 Product Positioning.......................................................................................................................22.1 Positioning..........................................................................................................................................................3

3 Product Architecture.....................................................................................................................43.1 Physical Architecture..........................................................................................................................................53.2 Logical Architecture...........................................................................................................................................53.3 Software Architecture.........................................................................................................................................63.4 Data Forwarding Process....................................................................................................................................8

4 Technical Specifications.............................................................................................................10

5 FPIC................................................................................................................................................12

6 Link Features................................................................................................................................156.1 E1 Link Features...............................................................................................................................................166.2 Ethernet Link Features......................................................................................................................................166.3 CPOS Link Features.........................................................................................................................................16

7 Service Features...........................................................................................................................187.1 Ethernet Features..............................................................................................................................................19

7.1.1 Layer 2 Ethernet Features........................................................................................................................197.1.2 Layer 3 Ethernet Features........................................................................................................................197.1.3 QinQ Features..........................................................................................................................................197.1.4 Flexible Access to VPNs.........................................................................................................................207.1.5 RRPP Link Features................................................................................................................................207.1.6 RSTP/MSTP Features..............................................................................................................................207.1.7 BPDU Tunneling Features.......................................................................................................................21

7.2 IP Features........................................................................................................................................................217.2.1 IPv4/IPv6 Dual Stack..............................................................................................................................217.2.2 IPv4 Features...........................................................................................................................................217.2.3 IPv6 Features...........................................................................................................................................227.2.4 IPv4/IPv6 Transition Technology...........................................................................................................22

7.3 Routing Protocol...............................................................................................................................................22

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description Contents


iv

7.3.1 Unicast Routing.......................................................................................................................................227.3.2 Multicast Routing....................................................................................................................................24

7.4 MPLS................................................................................................................................................................257.5 VPN Features....................................................................................................................................................29

7.5.1 Tunnel Policy...........................................................................................................................................297.5.2 VPN Tunnel.............................................................................................................................................297.5.3 MPLS L2VPN.........................................................................................................................................297.5.4 BGP/MPLS L3VPN................................................................................................................................31

7.6 QoS...................................................................................................................................................................327.7 Load Balancing.................................................................................................................................................367.8 Traffic Statistics................................................................................................................................................377.9 Security Features..............................................................................................................................................387.10 IP RAN Features.............................................................................................................................................437.11 Network Reliability........................................................................................................................................437.12 Clock...............................................................................................................................................................48

8 Applicable Environment............................................................................................................518.1 Metro Ethernet Solution...................................................................................................................................52

9 Operation and Maintenance......................................................................................................559.1 System Configuration Modes...........................................................................................................................569.2 System Management and Maintenance............................................................................................................569.3 Device Running Status Monitoring..................................................................................................................569.4 HGMP...............................................................................................................................................................589.5 System Service and Status Tracking................................................................................................................589.6 System Test and Diagnosis...............................................................................................................................589.7 NQA..................................................................................................................................................................599.8 In-Service Debugging.......................................................................................................................................599.9 Upgrade Features..............................................................................................................................................609.10 License............................................................................................................................................................609.11 Other Operation and Maintenance Features...................................................................................................60

10 NMS.............................................................................................................................................62

A Acronyms and Abbreviations..................................................................................................64

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description Contents


v

1 New Features of V600R003C00

New Features Where to Place

Flexible access to VPNs 7.1.4 Flexible Access to VPNs

License 9.10 License

IP RAN 7.10 IP RAN Features

Clock 7.12 Clock

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 1 New Features of V600R003C00


1

2 Product Positioning

About This Chapter

2.1 Positioning

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 2 Product Positioning


2

2.1 Positioning

Huawei NE40E-X1&NE40E-X2 Universal Service Router (hereinafter referred to as theNE40E-X1&NE40E-X2) are a high-end network product used to access, converge, and transmitcarrier-class Ethernet services on Fixed-Mobile Convergence (FMC) Metropolitan AreaNetworks (MANs).

The NE40E-X1&NE40E-X2 operate on the Versatile Routing Platform (VRP) operating systemdeveloped by Huawei and adopts the hardware-based forwarding and non-blocking dataswitching technology. The NE40E-X1&NE40E-X2 feature carrier-class reliability, line-speedforwarding capability, perfect Quality of Service (QoS) mechanism, service processingcapability, and good expansibility.

The NE40E-X1&NE40E-X2 provide strong capabilities in network access, Layer 2 switching,and transmission of Ethernet over Multi-Protocol Label Switching (EoMPLS) services. TheNE40E-X1&NE40E-X2 also support rich IP services and provides broadband access, triple play,IP leased line, and Virtual Private Network (VPN) services. The NE40E-X1&NE40E-X2 canalso work in conjunction with the CX200/300, NE80E, NE40E, ME60, and MA5200Gdeveloped by Huawei to set up a hierarchical metro Ethernet that provides rich services forcustomers.

NE40E-X1 NE40E-X2

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 2 Product Positioning


3

3 Product Architecture

About This Chapter

3.1 Physical Architecture

3.2 Logical Architecture

3.3 Software Architecture

3.4 Data Forwarding Process

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 3 Product Architecture


4

3.1 Physical ArchitectureThe physical architecture includes the following systems:

l Power distribution systeml Functional host systeml Heat dissipation systeml Network management system

All systems except the network management system (NMS) are located in an integrated cabinet.The power distribution system consists of power modules working in 1+1 backup mode.

The following describes only the functional host system.

The functional host system is composed of the system backplane, MPUs, NPUs, and PICs. Thefunctional host system processes data. In addition, it monitors and manages the entire system,including the power distribution system, heat dissipation system, and NMS through NMSinterfaces. Figure 3-1 shows the functional host system of the NE40E.

Figure 3-1 Functional host system

Data Bus

-48 V PSU(Power Support

Unit)

MPU(Master)

MPU

PIC 0-7(Physical

Interface Card)

NPU

NPU

FANMonitor Bus

GE/FE/E1etc

Control Bus

GE/Console/Bits/USBMonitor Bus

Control Bus

Monitor Bus

Control Bus

Data BusMonitor BusControl Bus

Monitor Bus

Control Bus

Monitor Bus

Control Bus

Monitor Bus

Control Bus

Data BusMonitor Bus

Control Bus

PSU(Power Support

Unit)

Backplane

(Slave)

-48 V

2*10G

2*10GGE/Console/

Bits/USB

NOTE

The NE40E-X1 has only one NPU and four PICs.

3.2 Logical ArchitectureThe logical architecture of the NE40E consists of the following planes:



5

l Data planel Control and management planel Monitoring plane

Figure 3-2 shows the logical architecture.

Figure 3-2 Logical architecture

MPU

NPUI PIC * N

Forwarding unit

Management unit

NPUI

MPU

Data channel

Monitoring plane

Control and management plane

Data plane

System monitoring unit

PICs management unit

Forwarding unit

Management unit




l The data plane is responsible for high speed processing and non-blocking switching of datapackets. It encapsulates or decapsulates packets, forwards IPv4/IPv6/MPLS packets,performs QoS as well as scheduling and internal high-speed switching, and collectsstatistics.

l The control and management plane completes all control and management functions forthe system and is the core of the entire system. Control and management units processprotocols and signals, and maintain, manage, report on, and control system status.

l The monitoring plane monitors the ambient environment to ensure secure and stableoperation of the system. It detects voltage levels, controls system power-on and-off,monitors temperature, and controls fan modules. When a unit fails, the monitoring planeisolates the faulty unit promptly so that other parts of the system can continue to runnormally.

3.3 Software ArchitectureFigure 3-3 and Figure 3-4shows the software architecture of the NE40E.



6

Figure 3-3 Software architecture of NE40E-X1

Power Monitoring

FAN Monitoring

SNMP RPSMaster

RPSSlave

IPC

NPUP

IC

PIC

PIC

PIC

Figure 3-4 Software architecture of NE40E-X2

Power Monitoring

FAN Monitoring

SNMP RPSMaster

RPSSlave

IPC

NPU

PIC

PIC

PIC

PIC

NPU

PIC

PIC

PIC

PIC

Software of the NE40E consists of the Routing Process System (RPS), power monitoring system,fan monitoring system, Forwarding Support Unit (FSU), and Express Forwarding Unit (EFU).

l The RPS, which includes IPOS software, VRP software, and product-adaptation software,is the control and management module that runs on the MPU. The RPS on the active MPUand the one on the standby MPU back up each other. RPSs support IPv4/IPv6, MPLS, LDP,and routing protocols, calculate routes, establish LSPs and multicast distribution trees,



7

generate unicast, multicast, and MPLS forwarding tables, and they deliver informationconcerning all the preceding mentioned to the LPU.

l The FSU implements the functions of the link layer and some functions of the IP protocolstack on interfaces.

l The EFU performs hardware-based IPv4/IPv6 forwarding, multicast forwarding, MPLSforwarding, and has a statistics functions.

3.4 Data Forwarding Process

Figure 3-5 Data forwarding process

PIC

DatagramDatagram

Processing on the incominginterface

Upstream traffic classification

Searching therouting table toforward packets

QoS in theupstream

Congestionmanagement

Queuescheduling

IPv4 unicastIPv4 multicastMPLSIPv6MAC

Packet fragmentation

SFU

Micro cell Micro cell

Packet reassembly

Multicast replication

QoS in thedownstreamCongestion

management

Queuescheduling

Packetencapsulationand forwardingin thedownstream

IPv4 unicastIPv4 multicastMPLSIPv6

Processing on the outgoinginterface

Downstream trafficclassification

PFE

TM

As shown in Figure 3-5, the Packet Forwarding Engine (PFE) adopts a Network Processor (NP)or an Application Specific Integrated Circuit (ASIC) to implement high-speed packet routing.External memory types include Static Random Access Memory (SRAM), Dynamic RandomAccess Memory (DRAM), and Net Search Engine (NSE). The SRAM stores forwarding entries;the DRAM stores packets; the NSE performs non-linear searching.

Data forwarding processes can be divided into upstream and downstream processes based onthe direction of the data flow.



8

l Upstream process: The Physical Interface Card (PIC) encapsulates packets to frames andthen sends them to the PFE. On the PFE of the inbound interface, the system decapsulatesthe frames and identifies the packet types. It then classifies traffic according to the QoSconfigurations on the inbound interface. After traffic classification, the system searches theForwarding Information Base (FIB) for the outbound interfaces and next hops of packetsto be forwarded. To forward an IPv4 unicast packet, for instance, the system searches theFIB for the outbound interface and next hop according to the destination IP address of thepacket. Finally, the system sends the packets containing information about outboundinterfaces and next hops to the traffic management (TM) module.

l Downstream process: Information about packet types that have been identified in theupstream process and about the outbound interfaces is encapsulated through the link layerprotocol and the packets are stored in corresponding queues for transmission. If an IPv4packet whose outbound interface is an Ethernet interface, the system needs to obtain theMAC address of the next hop. Outgoing traffic is then classified according to the QoSconfigurations on the outbound interfaces. Finally, the system encapsulates the packetswith new Layer 2 headers on the outbound interfaces and sends them to the PIC.



9

4 Technical Specifications

Physical Specifications

Table 4-1 Physical Specifications

Item NE40E-X2 NE40E-X1

Dimensions (width xdepth x height)

442 mm x 220 mm x 222 mm(17.4 in. x 8.66 in. x 8.74 in.)(5U (222.25 mm or 8.75 in.)height)

442 mm x 220 mm x 132 mm(17.4 in. x 8.66 in. x 5.20 in.)(3U (133.35 mm or 5.25 in.)height)

Installation Mounted in an N63E cabinet, a standard 19-inch cabinet, or a 23-inch North American open rack

Weight (in fullconfiguration)

22 kg (48.51 lb) 14 kg (30.87 lb)

Typical power 650 W 350 W

Heat dissipation 2109 BTU/hour 1136 BTU/hour

DC inputvoltage

Ratedvoltage

-48 V

Maximumvoltagerange

-38 V to -72 V

Ambienttemperature

Long-term -5°C to 50°C (23°F to 122°F)

Short-term -20°C to 60°C (-4°F to 140°F) (Short-term refers to a period of notmore than 96 consecutive hours and a total of not more than 15 daysin 1 year.)

Remarks Restriction on the temperature variation rate: 30°C (86°F)per hour

Storage temperature -40°C to 70°C (-40°F to 158°F)

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 4 Technical Specifications


10


Relativeambienthumidity

Long-term 5% to 85% RH, non-condensing

Short-term 5% to 95% RH, non-condensing

Relative storagehumidity

0% to 95% RH, non-condensing

Altitude for permanentwork

Within 3000 meters (Within 9842.40 ft)

Storage altitude Within 5000 meters (Within 16404 ft)

System Configuration

Table 4-2 System Configuration


SDRAM 2 GB 2 GB

CF card 1 GB 1 GB

USB interface USB2.0 Host USB2.0 Host

Switching capacity 40 Gbit/s 20 Gbit/s

Forwarding capacity 60 Mpps 30 Mpps

Backplane bandwidth 450 Gpbs 285 Gpbs

Interface capacity Non-line-rate: 75.2 Gbit/sLine-rate: 40Gbit/s

Non-line-rate: 52 Gbit/sLine-rate: 20Gbit/s

Number of subcard slots 8 4

Number of MPU slots 2 2

Number of NPU slots 2 1

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 4 Technical Specifications


11

5 FPIC

The NE40E-X2 has eight slots for subcards. Subcards are hot swappable and support automaticconfiguration recovery.

The NE40E-X1 has four slots for subcards. Subcards are hot swappable and support automaticconfiguration recovery.

Table 5-1 Subcards supported by the NE40E-X2 and NE40E-X1

Interface Name Description Remarks

8-Port 100/1000Base-X-SFPHigh-speed Interface Card A(HIC, Supporting 1588v2)

Supports synchronizationEthernet feature and multipletypes of optical modules, andcomplies with the 1588v2standard.l Supports the GE optical

module to provide GEoptical interfaces.

l Supports the FE opticalmodule to provide FEoptical interfaces.

l Supports the SFPelectrical module toprovide 100 M/1000 Mauto-sensing electricalinterfaces. (In this case,the synchronizationEthernet feature is notsupported.)

l Supports the mixed use ofthe preceding modules.

Supports hot swapping.

Subcards of this type can beinserted in the slots 5, 6, 9,and 10 on the NE40E-X2,and the slots 2, 3, 4 and 5 onthe NE40E-X1.

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 5 FPIC


12


8-Port 100/1000Base-X-SFPHigh-speed Interface Card(HIC)

Supports the synchronizationEthernet feature and multipletypes of optical modules.l Supports the GE optical

module to provide GEoptical interfaces.

l Supports the FE opticalmodule to provide FEoptical interfaces.

l Supports the SFPelectrical module toprovide the features of100 M/1000 M auto-sensing electricalinterfaces.

l Supports the mixed use ofthe preceding modules.

Supports hot swapping.

Subcards of this type can beinserted in the slots 5, 6, 9,and 10 on the NE40E-X2,and the slots 2, 3, 4 and 5 onthe NE40E-X1.

Auxiliary Flexible InterfaceCard with 4-Port 100Base-RJ45(FIC, Supporting1588v2)

Supports on-site ambientmonitoring, including themonitoring of burglarproofswitches and smoke sensors.Supports hot swapping.

Only one subcard of this typecan used on a device.

8-Port 100Base-RJ45Flexible Interface Card (FIC,Supporting 1588v2)

Supports hot swapping. Subcards of this type can beinserted in the slots 3, 4, 5, 6,9, 10, 11, and 12 on theNE40E-X2, and in the slots 2,3, 4 and 5 on the NE40E-X1.

8-Port 100Base-X-SFPFlexible Interface Card (FIC,Supporting 1588v2)


1-Port Channelized OC3c/STM1c POS-SFP FlexibleInterface Card (FIC)

Supports hot swapping, theclock synchronizationfeature, and three protocols:Circuit Emulation Service(CES), Inverse Multiplexingfor ATM (IMA), and Multi-link Point-to-Point Protocol(ML-PPP).

Subcards of this type can beinserted in the slots 3, 4, 5, 6,9, 10, 11, and 12 on theNE40E-X2, and in the slots 2,3, 4 and 5 on the NE40E-X1.



13


16-Port E1(75ohm) FlexibleInterface Card (FIC)


16-Port E1(120ohm)Flexible Interface Card (FIC)


4-port OC-3c/STM-1 ATMSFP FPIC




14

6 Link Features

About This Chapter

6.1 E1 Link Features

6.2 Ethernet Link Features

6.3 CPOS Link Features

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 6 Link Features


15

6.1 E1 Link FeaturesThe NE40E provides an E1 interface.

The E1 interface supports the following link protocols:

l ML-PPPl ATM IMAl TDM

The E1 interface supports the loopback function on an interface, including local loopback andremote loopback.

PPP on serial interfaces supports the following:

l MP

6.2 Ethernet Link FeaturesThe NE40E provides the following features on Ethernet interfaces:

l Flow control and auto negotiation of ratesl The formed Eth-Trunk interface functions the same as a common Ethernet interface in

supporting services.l Bundling of interfaces of different ratesl Binding of interfaces on different boards into one Eth-Trunkl Eth-Trunk member interfaces in active/standby mode

The NE40E can perform active/standby switchover automatically on Eth-Trunk memberinterfaces when the link status of interfaces changes.

l Addition or deletion of member interfaces to or from an Eth-Trunk interfaceThe NE40E can sense the Up or Down status of member interfaces, thus dynamicallychanging the bandwidth of the Eth-Trunk.

l Layer 2 and Layer 3 Eth-Trunk interfacesE-Trunk, that is, Eth-Trunk interface whose member interfaces reside on different devices

l Association between Eth-Trunk links and BFDl LACP defined in 802.3ad

The Link Aggregation Control Protocol (LACP) maintains link status according to interfacestatus. LACP adjusts or disables link aggregation in the case of aggregation changes.

l Ethernet clock synchronizationl 1588v2 clockl VLAN sub-interfacesl Interface loopback, including local loopback and remote loopback

6.3 CPOS Link FeaturesThe NE40E provides the following CPOS features:



16

l ChannelizationThe E1 interface channalized from a CPOS interface, in compliance with SAToP, cantransparently transmit unstructured TDM services through PWs on an MPLS network.The E1 interface channalized from a CPOS interface, in compliance with CESoPSN, cantransparently transmit structured TDM services through PWs on an MPLS network.

l ML-PPP/TDM/ATM IMAThe NE40E provides CPOS interfaces at 155 Mbit/s. At the link layer, CPOS interfacessupport the following protocols:– ML-PPP– TDM– ATM IMA

l Interface loopback, including local loopback and remote loopback



17

7 Service Features

About This Chapter

7.1 Ethernet Features

7.2 IP Features

7.3 Routing Protocol

7.4 MPLS

7.5 VPN Features

7.6 QoS

7.7 Load Balancing

7.8 Traffic Statistics

7.9 Security Features

7.10 IP RAN Features

7.11 Network Reliability

7.12 Clock

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 7 Service Features


18

7.1 Ethernet Features7.1.1 Layer 2 Ethernet Features

On the NE40E, Ethernet interfaces can work in switched mode at Layer 2 and support VLAN,VPLS, and QoS services. Functioning as UNIs, Layer 2 Ethernet interfaces support MPLS VPNservices.

The NE40E provides the following Layer 2 Ethernet features:

l Default VLANl VLAN trunkl VLANIF interfacesl VLAN aggregationl Inter-VLAN port isolationl Ethernet sub-interfacesl VLAN aggregated sub-interfacesl Port number-based VLAN divisionl VLAN mappingl VLAN stackingl MAC address limitl Unknown unicast/multicast/broadcast suppressionl Spanning Tree Protocol (STP)/Rapid Spanning Tree Protocol (RSTP)l Multiple Spanning Tree Protocol (MSTP)l RRPP with switching time less than 50 ms

7.1.2 Layer 3 Ethernet FeaturesThe NE40E provides the following Layer 3 Ethernet features:

l IPv4l IPv6l MPLSl Multicastl VLAN sub-interfacesl QoSl Ethernet sub-interfacesl VLAN aggregation sub-interfaces

7.1.3 QinQ FeaturesThe NE40E provides abundant QinQ features to satisfy different networking requirements. TheQinQ features are as follows:

l Identification of double VLAN tags (inner VLAN tag and outer VLAN tag)



19

l Change of the outer VLAN ID

l Removal of double VLAN tags and then addition of new double VLAN tags

l QinQ mapping for the outer VLAN tag

l Change of the EtherType value and 802.1p priority in the outer VLAN tag; copy of the802.1p priority in the inner VLAN tag to the outer VLAN tag of double-tagged packets

l Traffic classification based on the 802.1p priorities in the outer VLAN tags of packets

l Rate limit on interfaces based on the 802.1p priorities in both inner and outer VLAN tags

l Interface-based QinQInterface-based QinQ is applicable to the following scenarios:

– Access to a VPLS network to transparently transmit VLAN packets

– Access to an L2VPN or PWE3 to transparently transmit VLAN packets

l VLAN-based QinQ

l QinQ termination

l EType in the outer tag of QinQ packets used for interoperation with devices of other vendors

l Multicast QinQ

l QinQ-based VLAN swapping

l VLAN stacking can be applied in the following scenarios:

– Access to VPLS

– Access to VLL or PWE3

7.1.4 Flexible Access to VPNsIn traditional access identification, user information or service information is identified througha single tag or double tags. For example, the inner tag indicates user information and the outertag indicates service information. Different interfaces are configured with different double tagsto access different VPNs. In some scenarios, the access device does not support QinQ or a singletag is used for multiple services. In this case, the access device may add service accessinformation to the 802.1p or DSCP field. Then, the NE40E connected to the access device needsto use the 802.1p or DSCP value to identify access users. This helps configure the accesses todifferent VPNs and set up different QoS scheduling policies.

7.1.5 RRPP Link FeaturesThe Rapid Ring Protection Protocol (RRPP) supports the following functions:

l Polling mechanism

l Link status change notification

l Mechanism of checking the channel status of the sub-ring protocol packets on the majorring

7.1.6 RSTP/MSTP FeaturesThe NE40E supports the following:

l RSTP

l MSTP



20

MSTP provides BPDU protection to defend against such attacks. After the BPDU protection isenabled, the switch shuts down the edge port that receives BPDUs. At the same time, the switchinforms the NMS of the situation. The edge port can be enabled by the network administrator.

NE40E can restrict the sending of Layer 2 and Layer 3 protocol packets such as RSTP and DHCPthrough CP-CAR. This avoids influencing device performance.

7.1.7 BPDU Tunneling FeaturesThe NE40E supports BPDU tunneling in the following modes:

l Port-based BPDU tunnelingl VLAN-based BPDU tunnelingl QinQ-based BPDU tunnelingl VLL-based transparent transmission of BPDUsl VPLS-based transparent transmission of BPDUs

7.2 IP Features7.2.1 IPv4/IPv6 Dual Stack

The IPv4/IPv6 dual stack can be easily implemented and can smoothly interoperate with otherprotocols. Figure 7-1 shows the structure of the IPv4/IPv6 dual stack.

Figure 7-1 IPv4/IPv6 dual stack

IPv4 IPv6

TCP UDP

IPv4/IPv6 Application

Link Layer

IPv4/IPv6 dual stack (including dual-stack VPN) is supported on the same interface.

7.2.2 IPv4 FeaturesThe NE40E supports the following IPv4 features:

l TCP/IP protocol suite, including ICMP, IP, TCP, UDP, socket (TCP/UDP/Raw IP), andARP

l Static DNS and specified DNS serverl FTP server/client and TFTP clientl DHCP relay agent and DHCP serverl Suppression of DHCP flooding



21

l Ping, tracert, and NQANQA can detect the status of ICMP, TCP, UDP, DHCP, FTP, HTTP, and SNMP servicesand test the response time of the services. The system supports NQA in UDP jitter andICMP jitter tests by sending and receiving packets on LPUs. The minimum interval at whichpackets are transmitted can be 10 ms. Each LPU supports up to 100 concurrent jitter tests.The entire system supports up to 1000 concurrent jitter tests.

l IP policy-based routing (PBR) and flow-based next hop to which packets are forwardedl IP PBR-based load balancingl Load balancing in unequal cost multiple path (UCMP) model Configuration of secondary IP addresses for all physical and logical interfaces

Each interface can be configured with a maximum of 255 secondary IP addresses with 31-bit masks.

7.2.3 IPv6 FeaturesThe NE40E supports the following IPv6 features:

l IPv6 Neighbor Discovery (ND)l Path MTU Discovery (PMTU)l TCP6, ping IPv6, tracert IPv6, and socket IPv6l Static IPv6 DNS and specified IPv6 DNS serverl TFTP IPv6 clientl IPv6 PBRl Telnet and SSH

7.2.4 IPv4/IPv6 Transition TechnologyThe NE40E provides the following IPv4/IPv6 transition technologies:

l IPv6 over IPv4 tunnelThe NE40E adopts the following IPv6 over IPv4 tunnel modes:– IPv6 manual tunnel– IPv4 over IPv6 automatic tunnel– 6 to 4 tunnel

l 6PE and 6vPE

7.3 Routing Protocol7.3.1 Unicast Routing

The NE40E supports the following unicast routing features:

l IPv4 routing protocols, including RIP, OSPF, IS-IS, and BGP4l IPv6 routing protocols, including Routing Information Protocol Next Generation (RIPng),

OSPFv3, IS-ISv6, and BGP4+l Static routes that are manually configured by the administrator to simplify network

configurations and improve network performance



22

l Large-capacity routing table to effectively support the operation of a MAN.l Selection of the optimal route through the perfect routing policyl Import of routing information of other protocolsl Use of routing policies in advertising and receiving routes and filtering of routes through

route attributesl Password authentication and MD5 authentication to improve network securityl Restart of protocol processes through command linesl RIP-1 (classful routing protocol) and RIP-2 (classless routing protocol)l Advertisement of a default route from a RIP-enabled device to its peers and setting of the

metric of this routel RIP-triggered updatesl Disabling a specified interface from sending or receiving OSPF or RIP packetsl Association between OSPF and BGPl Association between OSPF and LDPl Fast OSPF convergence, which can be implemented in the following manners:

– Adjusting the interval at which LSAs are sent

– Enabling OSPF GR

– Configuring BFD for OSPFl OSPF I-SPF and IS-IS I-SPF (I-SPF re-calculates only the affected routes of a shortest path

tree (SPT) rather the entire SPT)l OSPF PRCl OSPF calculation of link costs based on the reference bandwidth

Link costs can be manually configured or automatically calculated by the system based onthe reference bandwidth by using the following formula:Link cost = Reference bandwidth/Interface bandwidthThe integer of the calculated result is the link cost. If the calculated result is smaller than1, the cost is 1. The link cost can be changed by changing the reference bandwidth. Bydefault, the reference bandwidth of the NE40E is 100 Mbit/s. The value can be changed toone in the range of 1 to 2147483648 in Mbit/s by running commands.

l Two-level IS-IS in a routing domainl Association between IS-IS and LDPl IS-IS GR, OSPF GR and BGP GR, which ensure high reliability with Non-Stop Forwarding

(NSF)l BGP indirect next hop and dynamic update peer-groupsl Policy-based route selection by BGP when there are multiple routes to the same destinationl BGP route reflector (RR), which addresses the problem of high costs of full-mesh

requirement when there are many IBGP peersl Sending of BGP Update packets that carry no private AS numberl Route dampening, which suppresses unstable routes (unstable routes are neither added to

the BGP routing table nor advertised to other BGP peers)l Routing protocoll BGP fast convergence



23

The NE40E adopts a new route convergence mechanism and algorithm, which speeds upconvergence of BGP routes. The features are as follows:

– Indirect next hop

– On-demand route iteration

l BGP load balancing in multi-homing networking

l Non-Stop Routing (NSR)

The NE40E supports the following NSR modes:

– IS-IS NSR

– BGP NSR

The formula for calculating the bandwidth occupies by LSAs on interfaces in the same area isas follows:

Assume that there are 10000 routes, Ethernet interfaces are used, and the MTU of the Ethernetinterfaces is 1500 bytes. In this case, the Ethernet frame header is of 18 bytes, and each LSA isof 44 bytes. Each LSA carries information about a route.

(1500-18)/44=44. The preceding formula indicates that an Ethernet frame can carry informationabout 33 routes. In this case, 228 Ethernet frames are required to carry information about 10000routes.

7.3.2 Multicast RoutingThe NE40E provides the following multicast features:

l Multicast protocols

Multicast protocols include the Internet Group Management Protocol (IGMP) ( IGMPv1,IGMPv2 and IGMPv3), Protocol Independent Multicast-Dense Mode (PIM-DM), ProtocolIndependent Multicast-Sparse Mode (PIM-SM), Multicast Source Discovery Protocol(MSDP), and Multi-protocol Border Gateway Protocol (MBGP).

l Reverse Path Forwarding (RPF)

l PIM-SSM

l Anycast RP

l IPv6 multicast routing protocols

l IPv6 multicast routing protocols include PIM-IPv6-DM, PIM-IPv6-SM, and PIM-IPv6-SSM.

l MLD

Multicast Listener Discovery (MLD) has the following versions:

– MLDv1 defined in RFC 2710

MLDv1 supports Any-Source Multicast (ASM) directly and supports Source-SpecificMulticast (SSM) together with SSM mapping.

– MLDv2 defined in RFC 3810

MLDv2 supports ASM and SSM directly.

l Multicast static routes

l Configuration of multicast protocols on physical interfaces such as Ethernet, and Trunkinterfaces.



24

l Filtering of routes based on the routing policy when the multicast routing module receives,imports, or advertises multicast routes and filtering and forwarding of multicast packetsbased on the routing policy when IP multicast packets are forwarded

l Multicast VPNThe multicast domain (MD) scheme is used to implement this function.

l Addition and deletion of dummy entriesl Query of PIM neighbors and number of control messagesl Filtering of PIM neighbors, control of the forwarding boundary, and control of the BSR

service and management boundaryl Filtering and suppression of PIM Register messagesl MSDP authenticationl IGMP packet rate limiting and IGMP proxyl Prompt leave of IGMP and MLD group members and the use of group-policies to restrict

the setup of forwarding entriesl Configuration of ACLs, including source address-based packet filtering, control of

multicast group number, setup of multicast forwarding entries, and Switch-MDT switching,to ensure multicast security

l Multicast group-based, multicast source-based, multicast source/group-based, stable-preferred, and balance-preferred load splitting

l IGMP snoopingThe NE40E supports IGMP snooping on Layer 2 interfaces, Layer 3 interfaces, QinQinterfaces, STP topologies, RRPP rings, and VPLS PWs.

l Multicast flow controlThe NE40E discards or broadcasts unknown multicast packets in the VLAN to which thereceiving interface belongs. Unknown multicast packets are packets that have nocorresponding forwarding entries in the multicast forwarding table.In addition, the NE40E restricts the maximum percentage of multicast flows on Ethernetinterfaces to control multicast traffic.

l Multicast VLANThe NE40E supports multicast VLAN and VLAN-based 1+1 protection of multicast traffic.

l Multicast VPNFor details, see section "7.5 VPN Features".

l Multicast CACThe NE40E supports multicast Call Admission Control (CAC). When multicast CAC rulesare configured, the number of multicast groups and bandwidth are restricted for IGMPsnooping on interfaces or the entire system.

7.4 MPLSThe NE40E supports MPLS features, and static and dynamic LSPs. Static LSPs require that theadministrator configure the Label Switch Routers (LSRs) along the LSPs and set up LSPsmanually. Dynamic LSPs are set up dynamically in accordance with the routing informationthrough the Label Distribution Protocol (LDP) and RSVP-TE.

The delay for MPLS packets can be controlled in the following aspects:



25

l In the case that there is no traffic congestion, the NE40E adopts a high-speed processor toensure line-rate forwarding and low delay.

l In the case of traffic congestion, the NE40E ensures preferential forwarding and low delayfor traffic with high priority through mechanisms such as QoS, HQoS, MPLS TE, and DS-TE.

MPLS is supported on all interfaces of the NE40E.

Basic MPLS Functions

The NE40E supports the following MPLS functions:

l Basic MPLS functions, service forwarding, and LDPMPLS distributes labels, sets up LSPs, and transfers parameters used for setting up LSPs.

l A maximum of four MPLS labelsl LDP

– Downstream Unsolicited (DU) and Downstream on Demand (DoD) label advertisementmodes

– Independent and ordered label distribution control modes

– Liberal and conservative label retention modes

– Loop detection mechanism by using the maximum number of hops and path vector

– Basic discovery mechanism and extended discovery mechanism of LDP sessionsl MPLS ping and tracert and detection of the availability of an LSP through the exchange of

MPLS Echo Request packets and MPLS Echo Reply packetsl LSP bandwidth alarm function and LSP-based traffic statistics function that is used to

calculate bandwidth usagel Management functions such as the LSP loop detection mechanisml MPLS QoS, mapping from the ToS field in IP packets to the EXP field in MPLS packets,

and MPLS uniform, pipe, and short pipe modesl Static configuration of LSPs and label forwarding based on traffic classificationl MPLS trap functionl Association between LDP and IGP, which shortens traffic loss to the minimum through the

synchronization between the LDP status and IGP status in case of network faultsl NE40E functioning as a Label Edge Router (LER) or an LSR

An LER is an edge device on an MPLS network that connects the MPLS network to othernetworks. The LER classifies services, distributes labels, encapsulates or removes multi-layer labels. When functioning as an egress, the NE40E supports PHP. That is, theNE40E allocates an explicit null label or an implicit null label to the penultimate hop.An LSR is a core router on an MPLS network. The LSR switches and distributes labels.

l Establishment of LSPs between NE40Es of different IS-IS levels and between theNE40E and non-Huawei devices through LDP

l MPLS supported by the NE40E complies with the following standards:

– RFC 3031

– RFC 3032

– RFC 3034



26

– RFC 3035– RFC 3036– RFC 3037The NE40E supports CR-LDP and RSVP-TE and can interoperate with non-Huaweidevices through CR-LDP or RSVP-TE.

MPLS TEThe MPLS TE technology combines the MPLS technology with traffic engineering. It canreserve resources by setting up LSP tunnels for a specified path in an attempt to avoid networkcongestion and balance network traffic.

In the case of resource scarcity, MPLS TE allows the preemption of bandwidth resources ofLSPs with low priorities. This meets the demands of important services or the LSPs with largebandwidth. When an LSP fails or a node is congested, MPLS TE can ensure smooth networkcommunication through the backup path and the fast reroute (FRR) function. Through automaticre-optimization and bandwidth adjustment, MPLS TE improves the self-adaptation capabilityof tunnels and properly allocates network resources.

The process of updating the network topology through the TEDB is as follows: When a linkgoes Down, the CSPF failed link timer is enabled. If the IGP route is deleted or the link is changedwithin the timeout period of the CSPF failed link timer, CSPF deletes the timer and then updatesthe TEDB. If the IGP route is not deleted or the link is not changed after the timeout period ofthe CSPF failed link timer expires, the link is considered Up.

MPLS TE provides the following functions:

l Processing of static LSPsMPLS can create and delete static LSPs, which require bandwidth but are manuallyconfigured.

l Processing of Constrained Route-Label Switched Path (CR-LSP) of various types and routecalculation through the CSPF algorithm

CR-LSPs are classified into the following types:

l RSVP-TERSVP authentication complies with RFC 3097.

l Auto routingAuto routing works in either of the following modes:– IGP shortcut: An LSP is not advertised to neighboring routers. Therefore, other routers

cannot use the LSP.– Forwarding adjacency: An LSP is advertised to neighboring routers. Therefore, other

routers can use the LSP.l Fast reroute (FRR)

The switchover through FRR is within 50 ms, which minimizes the data loss when networkfaults occur.

l Auto FRRAuto FRR is an extension to MPLS TE FRR. You can create a bypass tunnel that meetsthe requirement on the LSP by configuring the attributes of the bypass tunnel, global autoFRR, and auto FRR on the interface of the primary tunnel. With the change of the primary



27

tunnel, the previous bypass tunnel is deleted automatically. Then, a new bypass tunnel thatmeets the requirement is set up.

l Backup CR-LSPThe NE40E supports the following backup modes:– Hot backup

A backup CR-LSP is established immediately after the primary CR-LSP is established.When the primary CR-LSP fails, MPLS TE switches traffic immediately to the backupCR-LSP.

– Ordinary backupA backup CR-LSP is set up when the primary CR-LSP fails.

l LDP over TEIn existing networks, not all devices support MPLS TE. It is possible that only the devicesat the network core support TE and the devices at the network edge use LDP. Theapplication of LDP over TE is therefore put forward. With LDP over TE, the TE tunnel isconsidered as a hop of the entire LDP LSP. Through forwarding adjacency, one MPLE TEtunnel can be considered as a virtual link and advertised to an IGP network.

l Make-before-breakMake-before-break is a technology for ensuring highly reliable CR-LSP switchover. Theoriginal path is not deleted until a new path has been created. Before a new CR-LSP iscreated, the original CR-LSP is not deleted. After a new CR-LSP has been created, thetraffic is switched to the new CR-LSP first, and then the original CR-LSP is deleted. Thisensures non-stop traffic forwarding.

l DS-TEDS-TE implemented on the NE40E supports the Non-IETF mode and the IETF mode.– The Non-IETF (non-standard) mode supports two CTs (CT0 and CT1), eight priorities

(0-7), and two bandwidth constraint models (RDM and MAM).The CT here refers to the class type of a corresponding service flow. The priority hererefers to the LSP preemption priority.

– The IETF (standard) mode supports eight CTs (CT0 through CT7), eight priorities (0-7),and three bandwidth constraint models (RDM, MAM, and Extended).DS-TE supports TE FRR, hot standby, protection switchover, and CT-based trafficstatistics collection.

MPLS OAMMPLS OAM functions are as follows:

l MPLS OAM detectionMPLS OAM sends CV/FFD and BDI packets along an LSP to be detected and its reverseLSP to detect its connectivity.

l OAM auto protocoll Protection switching



28

7.5 VPN Features7.5.1 Tunnel Policy

Tunnel policies are used to select tunnels according to destination IP addresses. Tunnels areselected according to tunnel policies as required. If no tunnel policy is created, the tunnelmanagement module searches for a tunnel according to the default tunnel policy.

The NE40E supports the following tunnel policies:

l Tunnel policy in select-sequence modeIn this mode, you need to specify the sequence in which the tunnel types are selected andthe number of tunnels carrying out load balancing. If a tunnel listed earlier is Up, it isselected regardless of whether other services have selected it. The tunnels listed later arenot selected except in case of load balancing or when the preceding tunnels are all Down.

l VPN tunnel bindingVPN tunnel binding means that the peer end of the VPN on the PE of the VPN backbonenetwork is associated with a certain MPLS TE tunnel. The data from the VPN to the peerPE is transmitted through the dedicated TE tunnel. The bound TE tunnel carries onlyspecified VPN services. This ensures QoS of the specified VPN services.

7.5.2 VPN TunnelThe NE40E supports the following types of VPN tunnels:

l LSPsl TE tunnels

7.5.3 MPLS L2VPNThe NE40E provides L2VPN services over an MPLS network where the ISP can provideL2VPNs over different media.

VLLThe NE40E supports the following VLL functions:

l Martini VLLThe Martini mode supports double labels. The inner label adopts extended LDP forsignaling in compliance with RFC 4096.The type of VC FEC is 128. VC encapsulation types include 0x0004 Ethernet Tagged Mode,0x0005 Ethernet, and 0x000B IP Layer2 Transport.

l Kompella VLLVC encapsulation types of Kompella VLL include Ethernet, PPP, VLAN, and IP-interworking.Kompella VLL supports the local inter-board switching of packets in 802.1Q mode.Kompella VLL supports inter-AS VPN.

l CCC VLL



29

CCC VLL supports the local inter-board switching of packets in 802.1Q model SVC VLLl VLL heterogeneous interworking

VLL heterogeneous IP-interworking is used when the link types of CEs on both ends of anL2VPN link are different. In MPLS L2VPN heterogeneous IP-interworking, after receivinga frame from a CE, a PE decapsulates the link-layer packet and transmits the IP packetacross an MPLS network. The IP packet is transparently transmitted to the peer PE. Thepeer PE re-encapsulates IP packet according to its link layer protocol and transmits thepacket to the connected CE. The link-layer control packet sent by the CE is processed bythe PE and is not transmitted through the MPLS network. All non-IP packets such as MPLSand IPX packets are discarded.

l Transparent transmission of certain types of link layer protocol packetsInterfaces can be configured to transparently transmit certain types of link layer protocolpackets, such as BPDUs, STP packets, LLDP packets, UDLD packets, CDP packets, andHGMP packets.

l Inter-AS VLL– SVC VLL, Martini VLL, and Kompella VLL can implement inter-AS L2VPN Option

A (VRF-to-VRF).– Option B requires the switching of both inner and outer labels on the ASBR, and is

therefore not suitable for the VLL.– Option C is the best solution.

l VLL over TE ECMP

VPLSIn a VPLS network, PEs can be all connected to each other and enabled with split horizon toprevent Layer 2 loops.

The implementations of VPLS control plane through BGP and LDP are called Kompella VPLSand Martini VPLS respectively.

l Kompella VPLSKompella VPLS has good scalability. With Kompella VPLS, BGP is adopted for signaling,and VPN targets are configured to implement automatic discovery of VPLS members.Therefore, the addition or deletion of PEs requires few additional operations.

l Martini VPLSMartini VPLS has poor scalability. With Martini VPLS, LDP is adopted for signaling, andthe peers of a PE need to be manually specified. PEs in a VPLS network are all connectedto each other. Therefore, adding a new PE requires configurations on all the other associatedPEs to be modified.A pseudo wire (PW) is actually a point-to-point link. This means thatusing LDP to create, maintain, and delete the PW is more effective.

The NE40E supports the following VPLS functions:

l Access to the VPLS network in QinQ model HVPLSl IGMP snooping for VPLSl One MAC address space for each VSIl VPLS learns MAC addresses in the following modes:



30

– Unqualified mode: In this mode, a VSI can contain multiple VLANs sharing a MACaddress space and a broadcast domain. When learning MAC addresses, VPLS also needsto learn VLAN IDs.

– Qualified mode: In this mode, a VSI has only one VLAN, which has an independentMAC address space and a broadcast domain. When learning MAC addresses, VPLSdoes not need to learn VLAN IDs.

l VPLS/HVPLS equal-cost load balancingl Fast switching of multicast trafficl mVPLSl STP over PWl STP over VPLSl Transparent transmission of certain types of link layer protocol packets

Interfaces can be configured to transparently transmit certain types of link layer protocolpackets, such as BPDUs, STP packets, LLDP packets, UDLD packets, CDP packets, andHGMP packets.

l Ethernet loop detection

PWE3The NE40E supports the following PWE3 functions:

l Virtual Circuit Connectivity Verification PING (VCCV-PING)The NE40E supports the manual LDP PW connectivity detection on the UPE, includingthe connectivity of static PWs, dynamic PWs, single-hop PWs, and multi-hop PWs.

l PW templateThe NE40E supports the binding between a PW and a PW template, and the reset of PWs.The NE40E supports heterogeneous interworking.Currently, the NE40E supports the transparent transmission of the following packetsthrough PWE3: ATM AAL5 SDU VCC transport, Ethernet, ATM n-to-one VCC celltransport, IP Layer 2 transport, and ATM one-to-one VCC cell mode.

l PW redundancyl The NE40E supports the circuit emulation service (CES) by using Pseudo-Wire Emulation

Edge to Edge (PWE3).The CES is classified into the Structure-aware TDM Circuit Emulation Service over PacketSwitched Network (CESoPSN) and Structure-Agnostic TDM over Packet (SAToP)service.

7.5.4 BGP/MPLS L3VPNThe NE40E supports MPLS/BGP L3VPN, providing an end-to-end VPN solution for carriers.Carriers can provide VPN services for users as a new value-added service. The NE40E supportsthe following BGP/MPLS L3VPN functions:

l Access of a CE to an L3VPN through Layer 3 interfaces such as Ethernet, and VLANIFinterfaces

l Static routes, BGP, RIP, OSPF, or IS-IS running between a CE and a PEl Carrier's carrier



31

l Inter-AS VPNThe NE40E supports the following inter-AS VPN solutions described in RFC 2547bis:– VPN instance to VPN instance, also called Inter-Provider Backbones Option A

In Option A, sub-interfaces connecting the Autonomous System Boundary Routers(ASBRs) manage VPN routes.

– EBGP redistribution of labeled VPN-IPv4 routes, also called Inter-Provider BackbonesOption BIn Option B, ASBRs advertise labeled VPN-IPv4 routes to each other through MP-EBGP.

– Multihop EBGP redistribution of labeled VPN-IPv4 routes, also called Inter-ProviderBackbones Option CIn Option C, PEs advertise labeled VPN-IPv4 routes to each other through MultihopMP-EBGP.

l Multicast VPNl IPv6 VPN

The NE40E supports the following IPv6 VPN networking solutions:– Intranet VPN– Extranet VPN– Hub&Spoke– Inter-AS or multi-AS backbones VPN– Carriers' carrier

l HoVPNl Resource reservation VPN (RRVPN)l Multi-role host

7.6 QoSOn the NE40E, you can collect traffic statistics on the packets on which QoS is performed andview the statistics result through corresponding display commands.

The NE40E supports the following QoS functions:

Diff-Serv Model

Multiple service flows can be aggregated into a Behavior Aggregate (BA) and then processedbased on the same Per-Hop Behavior (PHB). This simplifies the processing and storage ofservices.

On the Diff-Serv core network, packet-specific QoS is provided. Therefore, signaling processingis not required.

Simple Traffic Classification

Currently, the NE40E supports simple traffic classification not only on physical interfaces andsub-interfaces but also on logical interfaces such as member interfaces of VLANIF and trunkinterfaces.



32

Complex Traffic ClassificationThe NE40E performs complex traffic classification based on the following information:

l Layer 2 and Layer 3 information of packetsl Source MAC address, destination MAC address, link layer protocol number, and 802.1p

value (of tagged packets) in the Ethernet frame header; IP precedence, DSCP, or ToS value,source IP address prefix, destination IP address prefix, protocol number, fragmentationflag, TCP SYN flag, TCP/UDP source port number or port range, and TCP/UDP destinationport number or port rang of IPv4 packets

l Information carried in IPv6 packetsl In addition to physical interfaces, traffic classification can be performed on logical

interfaces, including sub-interfaces and trunk interfaces.

Traffic PolicingCAR is mainly used for rate limit. In the implementation of CAR, a token bucket is used tomeasure the data flows that pass through the interfaces on a router so that only the packetsassigned with tokens can go through the router in the specified time period. In this manner, therates of both incoming and outgoing traffic are controlled. In addition, the rate of certain typesof data flows can be controlled based on the information such as the IP address, port number,and priority. Rate limit is not performed on the data flows that do not meet the specifiedconditions, and such data flows are forwarded at the original interface rate.

CAR is mainly implemented at the edge of a network to ensure that core devices on the networkprocess data properly. The NE40E supports CAR for both incoming and outgoing traffic.

Queue SchedulingThe NE40E supports FIFO, PQ, and WFQ for queue scheduling on interfaces.

The NE40E maps packets of different priorities to different queues and adopts Round Robin(RR) on each interface for queue scheduling.

Priority Queues (PQs) are classified into four types: top PQs, middle PQs, normal PQs, andbottom PQs. They are ordered in descending order of priorities. When packets leave queues, PQallows the packets in the top PQ to go first. Packets in the top PQ are sent as long as there arepackets in this PQ. The NE40E sends packets in the middle PQ only when all packets in the topPQ are sent. Similarly, the NE40E sends packets in the normal PQ only when all packets in themiddle PQ are sent; the NE40E sends packets in the bottom PQ only when all packets in thenormal PQ are sent. As a result, the packets in the PQ of a higher priority are always sentpreferentially, which ensures that packets of key services are processed preferentially when thenetwork is congested. Packets of common services are processed when the network is idle. Inthis manner, the quality of key services is guaranteed, and the network resources are fullyutilized.

Weight Fair Queuing (hereinafter referred to as WFQ) is a complex queuing process, whichensures that the services with the same priority are fairly treated and the services with differentpriorities are weighted. The number of WFQ queues can be pre-set and is allowed to range from16 to 4096. WFQ weights services based on their requirements for the bandwidth and delay. Theweights are determined by the IP precedence in the IP packet headers. With WFQ, the NE40Eimplements dynamic traffic classification based on quintuples or ToS values. The packets withthe same quintuple (source IP address, destination IP address, source port number, destinationport number, and protocol number) or ToS value belong to the same flow. Packets in one flow



33

are placed in one queue through the Hash algorithm. When flows enter queues, WFQautomatically places different flows into different queues based on the Hash algorithm. Whenflows leave queues, WFQ allocates bandwidths to flows on the outbound interface based ondifferent IP precedence of the flows. The smaller the precedence value of a flow, the smaller thebandwidth of the flow. In this manner, services of the same precedence are treated fairly; servicesof different precedence are treated based on their weights.

Congestion AvoidanceCongestion avoidance is a traffic control mechanism used to avoid network overload by adjustingnetwork traffic. With this mechanism, the NE40E can monitor the usage of network resources(such as queues and buffers in the memory) and discard packets when the network congestionintensifies.

Random Early Detection (RED) or Weighted Random Early Detection (WRED) algorithms arefrequently used in congestion avoidance.

The RED algorithm sets the upper and lower limits for each queue and specifies the followingrules:

l When the length of a queue is below the lower limit, no packet is discarded.l When the length of a queue exceeds the upper limit, all the incoming packets are discarded.l When the length of a queue is between the lower and upper limits, the incoming packets

are discarded randomly. A random number is set for each received packet, and the randomnumber is compared with the drop probability of the current queue. The packet is discardedwhen the random number is larger than the drop probability. The longer the queue, thehigher the drop probability. The drop probability, however, has an upper limit.

Unlike RED, the random number in WRED is based on the IP precedence of IP packets. WREDkeeps a lower drop probability for the packets that have a higher IP precedence.

RED and WRED employ the random packet drop policy to avoid global TCP synchronization.The NE40E adopts WRED to implement congestion avoidance.

The NE40E supports congestion avoidance in both inbound and outbound directions of aninterface. The WRED template is applied in the outbound direction; the default scheduling policyin the system is applied in the inbound direction. In addition, WRED can be applied to theMulticast Tunnel interface (MTI) that is bound to the distributed multicast VPN on theNE40E.

The NE40E supports congestion avoidance based on services. The NE40E reserves on eachinterface eight service queues, that is, BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. TheNE40E colors packets with red, yellow, and green to identify the priorities of packets and discardcertain packets.

HQoSThe NE40E supports the following HQoS functions:

l Provides five levels of scheduling modes to ensure diverse services.l Sets parameters such as the maximum queue length, WRED, low delay, SP/WRR, CBS,

PBS, and statistics function for each queue.l Sets parameters such as the CIR, PIR, number of queues, and algorithm for scheduling

queues for each user.



34

l Provides the traffic statistics function. Users can learn the bandwidth usage of services andproperly distribute the bandwidth by analyzing traffic.

l Supports HQoS in the VPLS, L3VPN, VLL, and TE scenarios.l Supports interface-based, VLAN-based, user-based, and service-based HQoS.

QPPBQPPB is the abbreviation of QoS Policy Propagation Through the Border Gateway Protocol.

The receiver of BGP routes performs the following operations:

l Sets QoS parameters such as IP precedence and traffic behavior for a BGP route based onthe attributes of the route.

l Classifies traffic according to QoS parameters and sets the QoS policy for the classifiedtraffic.

l Forwards packets according to the locally configured QoS policies to propagate QoSpolicies through BGP.

The receiver of BGP routes can set QoS parameters (IP precedence and associated trafficbehavior) based on the following attributes:

l ACLl AS path list in routing informationl Community attribute list in routing informationl Metrics in routing informationl IP prefix list

QoS for Ethernetl Layer 2 simple traffic classification

The NE40E performs simple traffic classification according to the 802.1p field in VLANpackets. On the ingress PE, the 802.1p priority in a Layer 2 packet is mapped to theprecedence defined by the upper layer protocol, such as the IP DSCP value or the MPLSEXP value. In this manner, Diff-Serv is implemented for the packets on the backbonenetwork. On the egress PE, the precedence of the upper layer protocol is mapped back tothe 802.1p priority.

l QinQ simple traffic classificationIn the QinQ implementation, the 802.1p values in both inner and outer VLAN tags need tobe detected. The NE40E can detect the 802.1p value by the following means:– Ignores the 802.1p value in the inner VLAN tag and sets a new 802.1p value in the outer

VLAN tag.– Automatically converts the 802.1p value in the inner VLAN tag into the 802.1p value

in the outer VLAN tag.– Sets a new 802.1p value in the outer VLAN tag according to the 802.1p value in the

inner VLAN tag.Based on the preceding methods and the mapping of the inner VLAN tag to the outer VLANtag, QinQ supports 802.1p re-marking in the following modes:– Specifying a given value.– Adopting the 802.1p value in the inner VLAN tag.



35

– Mapping the 802.1p value in the inner VLAN tag to the 802.1p value in the outer VLANtag. The 802.1p values in multiple inner VLAN tags of different packets can be mappedto the 802.1p value in one outer VLAN tag; whereas the 802.1p value in one innerVLAN tag cannot be mapped to the 802.1p values in multiple outer VLAN tags ofdifferent packets.

MPLS HQoS

MPLS QoS is a complete L2VPN/L3VPN QoS solution. It resorts to various QoS techniques tomeet the diversified and delicate QoS demands of VPN users. MPLS QoS provides relative QoSon the MPLS Diff-Serv network and end-to-end QoS on the MPLE TE network. In actualapplications, the following QoS policies are supported.

l QPPB applied to an L3VPNl MPLS Diff-Serv applied to an L2VPN/L3VPNl MPLS TE applied to an L2VPN/L3VPNl MPLS DS-TE applied to an L2VPN/L3VPNl VPN-based QoS applied to the network side of an L2VPN/L3VPN

7.7 Load BalancingIn a scenario where there are multiple equal-cost routes to the same destination, the NE40E canbalance traffic among these routes. The NE40E provides equal-cost load balancing and unequal-cost load balancing, which can be selected as required. In equal-cost load balancing mode, trafficis evenly load-balanced among different routes. In unequal-cost load balancing mode, traffic isload-balanced among different routes based on the proportion of bandwidth of each interface.

Equal-Cost Load Balancing

The NE40E can implement equal-cost load balancing on the traffic transmitted through themember links of an IP-Trunk or an Eth-Trunk. When there are multiple equal-cost routes to thesame destination, the NE40E can evenly balance traffic among these routes.

Load balancing can be implemented in session-by-session mode.

Unequal-Cost Load Balancing

The NE40E supports the following unequal-cost load balancing modes:

l Load balancing based on routesWhen the costs of different direct routes are the same, you can configure a weight for eachroute for load balancing.

l Load balancing based on interfacesFor an IP-Trunk or an Eth-Trunk, you can configure a weight for each member link forload balancing.

l Load balancing based on link bandwidth for IGPIn this mode, unequal-cost session-by-session load balancing is performed on the outboundinterfaces of paths carrying out load balancing. The proportion of traffic transmitted alongeach path is approximate to or equal to the proportion of bandwidth of each link. This mode



36

fully considers the link bandwidth. In this manner, the case that links with low bandwidthare overloaded whereas links with high bandwidth are idle does not exist.

The NE40E can balance traffic between physical interfaces or between physical interfaces andlogical interfaces. In addition, the NE40E can detect the changes of logical interface bandwidthdue to manual configuration of new member links or the status changes of member links. Whenthe bandwidth of a logical interface changes, traffic is automatically load-balanced based on thenew bandwidth proportion.

7.8 Traffic StatisticsThe NE40E collects the statistics on access services for various users with multiple statisticfunctions. The traffic statistics functions are as follows:

The traffic statistics functions are as follows:

l Helps carriers analyze the traffic model of the network.l Provides reference data for carriers to deploy and maintain Diff-Serv TE.l Supports traffic-based accounting for non-monthly rental users.

URPF Traffic Statistics

The NE40E collects statistics on the forwarded traffic based on URPF and the traffic discardedduring the URPF check.

ACL Traffic Statistics

The NE40E supports the ACL traffic statistics function. When the created ACLs are applied toQoS and PBR, the NE40E can collect statistics based on ACLs after the ACL traffic statisticsfunction is enabled. The NE40E also provides commands to query the number of matchedpackets and bytes.

CAR Traffic Statistics

The NE40E provides diverse QoS functions such as traffic classification, traffic policing (CAR),and queue scheduling. For these specific functions, the NE40E provides the following QoStraffic statistics functions:

l In traffic classification, the system can collect statistics on the traffic that matches rulesand fails to match rules.

l The traffic statistics function for traffic policing is implemented in the following manners:

– Collects the statistics on the total traffic that matches the CAR rule.

– Collects the statistics on the traffic that is permitted or discarded by the CAR rule.

– Supports the interface-based traffic statistics.

– Supports interface-based CAR traffic statistics when the same traffic policy is appliedto different interfaces.

HQoS Traffic Statistics

The NE40E can collect the following HQoS traffic statistics:



37

l Statistics on the number of forwarding packets, bytes, and discarded packets of a user queuewhich includes eight flow queues of different priorities

l Statistics on the number of forwarded packets, bytes, and discarded packets of a user groupqueue

l Statistics on the number of forwarded packets, bytes, and discarded packets of eight queuesof different priorities on an interface

Interface-Based Traffic Statistics

Traffic statistics can be collected on all interfaces, including physical interfaces, sub-interfaces,loopback interfaces, null interfaces, logical channel interfaces, and virtual Ethernet interfaces.

Statistics on IPv4 and IPv6 packets, including unicast packets, multicast packets, and broadcastpackets, can also be collected.

Statistics on all protocol packets that are supported can be collected, such as MPLS packets,ARP packets, IGP packets, BGP packets, PIM packets, and DHCP packets.

The NE40E uses the 64-bit register to store the interface-based traffic statistics. For example,the register can store the traffic statistics on a 10G interface for 58.5 years.

VPN Traffic Statistics

On a VPLS network, the NE40E, functioning as a PE, can collect statistics on incoming andoutgoing traffic of L2VPN users that are connected to the NE40E.

On an L3VPN, the NE40E, functioning as a PE, can collect statistics on incoming and outgoingtraffic of various types of access users. The access users include:

l Users that access the network through interfaces including logical interfacesl Multi-role hostsl Users that access the network through the VPLS/VLLl When MPLS HQoS services are configured, the NE40E, functioning as an ingress PE, can

collect statistics on the traffic that is sent by the network side.

Traffic Statistics on TE Tunnels

The NE40E, functioning as a PE on an MPLS TE network, can collect statistics on incomingand outgoing traffic of a tunnel. When a VPN is statically bound to a TE tunnel, the NE40E cancollect statistics on traffic of each RRVPN over the TE tunnel and the total traffic over the TEtunnel.

Statistics can be collected on traffic of each CT on a DS-TE tunnel.

7.9 Security Features

Security Authentication

The NE40E supports the following security authentication functions:

l AAA



38

l Plain text authentication and MD5 encrypted text authentication supported by routingprotocols that include RIPv2, OSPF, IS-IS, and BGP

l MD5 encrypted text authentication supported by LDP and RSVPl SNMPv3 encryption and authentication

URPFThe NE40E supports URPF for IPv4/IPv6 traffic.

MAC Address LimitThe NE40E supports the following MAC address limit functions:

l Limit on the number of MAC addresses that can be learnedl Limit on the speed of MAC address learningl Limit on interface-based MAC address learningl Limit on PW-based MAC address learningl Limit on VLAN+interface-based MAC address learningl Limit on interface+VSI-based MAC address learningl Limit on QinQ-based MAC address learning

MAC entries in a MAC address table are classified into three types:

l Dynamic entriesDynamic entries are learnt by interfaces and stored in hardware of LPUs. Dynamic entriesage. Dynamic entries will be lost in the case of the system reset, LPU hot swap, or LPUreset.

l Static entriesStatic entries are configured by users and delivered to LPUs. Static entries do not age. Afterstatic entries are configured and saved, they are not lost in the case of the system reset, LPUhot swap, or LPU reset.

l Blackhole entriesBlackhole entries are used to filter out the data frames that contain specific destinationMAC addresses. Blackhole entries are configured by users and delivered to LPUs.Blackhole entries do not age. After blackhole entries are configured and saved, they willnot be lost in the case of the system reset, LPU hot swap, or LPU reset.

MAC Entry DeletionThe NE40E provides the following MAC entry deletion functions:

l Interface+VSI-based MAC entry deletionl Interface+VLAN-based MAC entry deletionl Trunk-based MAC entry deletionl Outbound QinQ interface-based MAC entry deletion

Unknown Traffic LimitWith the unknown traffic limit, the NE40E implements the following operations on a VPLS orLayer 2 network:



39

l Manages user traffic.Boards that are not LPUI-41s or LPUF-100s manage only the traffic of VSI and VLANusers.

l Allocates bandwidth to users.

In this manner, the network bandwidth is reasonably used and the network security is guaranteed.

IGMP SnoopingThe NE40E supports IGMP snooping on Layer 2 interfaces, Layer 3 interfaces, QinQ interfaces,STP topologies, RRPP rings, and VPLS PWs.

DHCP SnoopingDHCP snooping is mainly used to prevent DHCP Denial of Service (DoS) attacks, bogus DHCPserver attacks, ARP middleman attacks, and IP/MAC spoofing attacks when DHCP is enabledon the NE40E.

The working mode of DHCP snooping varies with the attack type, as shown in Table 7-1.

Table 7-1 Attack types and DHCP snooping working modes

Attack Type DHCP Snooping Anti-Attack WorkingMode

DHCP exhaustion attack MAC address limit

Bogus DHCP server attack Trusted/untrusted

Middleman attack and IP/MAC spoofingattack

DHCP snooping binding table

DoS attack by changing the value of theClient Hardware Address (CHADDR) field

Check on the CHADDR field in DHCP packets

Local Attack DefenseThe NE40E provides a uniform local attack defense module to manage and maintain the attackdefense policies of the whole system, thus offering an all-around attack defense solution that isoperable and maintainable to users.

The NE40E supports the following attack defense functions:

l Whitelistl Blacklistl CPU Total CARl IGMP VLAN CARl User-defined flowl Active link protection (ALP)

The NE40E protects the TCP-based application-layer data such as session data with thewhitelist function.



40

l Uniform configuration of CAR parametersThe NE40E provides the following methods of configuring CAR parameters:– Same CAR parameters configured on different LPUs– Same configuration interface for users– Configuration of protocol-specific CAR parameters, making the user interface more

friendlyl Smallest packet compensation

The NE40E can efficiently defend the network against the attacks of small packets withthe smallest packet compensation function. After receiving packets, the system checks thelengths of packets before sending them to the CPU.– If the packet length is smaller than the preset minimum packet length, the system

calculates the sending rate with the pre-set minimum length.– If the packet length is greater than the pre-set minimum packet length, the system

calculates the sending rate with the actual packet length.l Association between the application layer and lower layersl Local URPFl Management and service plane protectionl Defense against TCP/IP packet attacks

The NE40E provides defense measures against attacks by sending the following types ofpackets on TCP/IP networks:– Malformed packets

Null IGMP packets, packets with invalid TCP flag bits, LAND attack packets, IP packetswhose payloads are null, and smurf attack packets.

– Fragmented packetsPackets with a huge number of fragments or packets that have a large offset value,repetitive fragmented packets, tear Drop, syndrop, nesta, fawx, bonk, NewTear, Rose,ping of death, and Jolt attacks

– TCP SYN– UDP flood

l Attack source tracingWhen the NE40E is attacked, it obtains and stores suspicious packets, and then displaysthe packets in a certain form through command lines or offline tools. This helps locate theattack source easily.When attacks occur, the system automatically removes the data encapsulated at upper layersof the transmission layer and then caches the packets in memory. When there are a certainnumber of packets in the cache, for example, 20000 packets on each LPU, the earliestcached packets are overridden when more packets are cached.

GTSMOn the current network, attackers forge valid packets to attack routers, which overloads therouters and consumes limited resources such as the CPU on the MPU. For example, an attackerforges BGP protocol packets and continuously sends them to a router. After the LPU of therouter receives the packets, it finds that the packets are destined to itself and then sends thepackets directly to the BGP processing module on the MPU without checking the validity of thepackets. As a result, the system is abnormally busy processing these forged valid packets andthe CPU usage is high.



41

To guard against the preceding attacks, the NE40E provides the Generalized TTL SecurityMechanism (GTSM). The GTSM protects services above the IP layer by checking whether theTTL value in the IP header is within a specified range. In actual applications, the GTSM is mainlyused to protect the TCP/IP-based control plane such as the routing protocol against attacks ofthe CPU-utilization type such as CPU overload.

The NE40E supports BGP GTSM, OSPF GTSM, and LDP GTSM.

ARP Attack DefenseThe NE40E supports the following ARP attack defense functions:

l Interface-based ARP entry restrictionl Timestamp suppression based on the destination IP address and source IP address of an

ARP packetl The destination address check for the ARP packet

The system checks whether the destination IP address of the ARP packet received on theinterface is correct. If the destination IP address is correct, the packet is sent to the CPU;otherwise, the packet is discarded.

l ARP bidirectional isolationl Filtration of invalid ARP packets

The NE40E filters out the following types of ARP packets:– Invalid ARP packets

Invalid ARP packets include ARP request packets with the destination MAC addressesbeing unicast addresses, ARP request packets with the source MAC addresses beingnon-unicast addresses, and ARP reply packets with the destination MAC addressesbeing non-unicast addresses.

– Gratuitous ARP packets– ARP request packets with valid MAC addressesYou can use commands to filter out one or more previously mentioned invalid packets.

Local MirroringIn local mirroring, an LPU can be configured with a physical observing port, multiple logicalobserving ports, and multiple mirrored ports.

Local mirroring can be inter-LPU mirroring, which means that the observing port and mirroredport reside on different LPUs.

Remote MirroringThe NE40E provides MPLS LSPs, MPLS TE tunnels for remote mirroring.

In remote mirroring, an LPU can be configured with multiple observing ports and mirrored ports.

In remote mirroring, mirroring packets can be intercepted.

SSHv2The NE40E supports the STelnet client and server and the SFTP client and server. Both supportSSH 1.5 and SSH 2.0.



42

7.10 IP RAN Features

PNPPlug-and-Play (PNP) enables new devices to be automatically identified by the NMS and becommissioned remotely by using the NMS.

On an IP RAN network deployed with a large number of devices, the device deployment costs,especially the costs of on-site software commissioning, are high. This greatly harms the growthof profits. To address this issue, Huawei puts forward the PNP solution.

The PNP feature effectively reduces the on-site software commissioning time, frees engineersfrom working in bad outdoor environments, and greatly speeds up the project process andimproves project quality.

Y.1731Y.1731 supports the following functions:

l Single-ended frame loss statistics collection, two-ended frame loss statistics collection,one-way frame delay, two-way frame delay and one-way jitter

l VLL Alarm Indication Signal (AIS) and VPLS AISl Multicast MAC ping

MPLS-TP OAMMPLS-TP OAM supports the following functions:

l Basic connectivity detectionl LoopBack (LB)l Remote Defect Indication (RDI)l Single-ended frame loss statistics collection and two-ended frame loss statistics collectionl One-way frame delay and two-way frame delayl APS 1:1

7.11 Network Reliability

NSRNE40Esupports the following techniques of Non-Stop Routing (NSR).

l NSR OSPFl NSR LDPl NSR RSVP-TEl NSR PIMl NSR PPP



43

l NSR ARPl NSR LACPl NSR for L2VPNl NSR for L3VPNl ISIS/ISIS6 NSRl BGP/BGP4+ NSRl Multicast (PIM/MSDP) NSRl NSR for IPv6

APSThe NE40E supports the following Automatic Protection Switching (APS) functions:

l 1+1 unidirectional modeand 1:1 bidirectional model Manual switching of APS groupsl Forcible switching of APS groupsl Locking of traffic on the working link of an APS groupl Interface-based APSl Intra-LPU or inter-LPU APSl Inter-device APS, that is, Enhanced APS (E-APS)l Addition of the working and protect interfaces of an APS group to a trunk so that all services

are configured on the trunk

FRRThe NE40E provides multiple fast reroute (FRR) features. You can deploy FRR as required toimprove network reliability.

l IP FRRFRR switching can be complete in 50 ms. In this manner, the data loss caused by networkfailures is minimized to a great extend.FRR supported by the NE40E enables the system to monitor and save the status of LPUsand interfaces in real time and to check the status of interfaces during packet forwarding.When faults occur on an interface, the system can rapidly switch the traffic to another pre-set route, thus reducing time between failures and the packet loss ratio.

l LDP FRRLDP FRR switching can be complete in 50 ms.

l TE FRRTE FRR is an MPLS TE technology used to protect local networks. Only the interfaceswith a transmission rate of over 100 Mbit/s support TE FRR. TE FRR switching can becomplete within 50 ms. It can minimize data loss when network failures occur.TE FRR protects traffic only temporarily. When the protected LSP becomes normal or anew LSP is established, traffic is switched back to the original protected LSP or the newlyestablished LSP.When a link or a node on the LSP fails, traffic is switched to the protection link and theingress node of the LSP attempts to establish a new LSP, if an LSP is configured with TEFRR.



44

With different protected objects, TE FRR is classified into the following types:

– Link protection

– Node protectionl Auto FRR

Auto FRR is an extension of MPLS TE FRR. It automatically creates a bypass tunnel thatmeets the requirements for the LSP through the configuration of the attributes of the bypasstunnel, global auto FRR attributes, and interface-based auto FRR attributes on the interfaceof the primary tunnel. When the primary tunnel changes to another path, the previous bypasstunnel is automatically deleted. Then, a bypass tunnel that meets the requirements is set up.

l VLL FRRVLL FRR switching can be complete in 50 ms.

l VPN FRRVPN FRR switching can be complete in 50 ms.

Backup of Key Parts

The NE40E can be equipped with one MPU or two MPUs. The MPUs support hot backup. Ifthe device is configured with two MPUs, the master MPU works and the slave MPU is in thestandby state. The management network interface on the slave MPU cannot be accessed by users,and the console and AUX interfaces cannot be configured with any command. The slave MPUexchanges information (including heartbeat messages and backup data) with only the masterMPU.

The system supports two types of master/slave switchover of MPUs: failover and switchover.The failover is triggered by serious faults in the master MPU or the reset of the master MPU.The switchover is triggered by commands that are run on the console interface. You can alsoforbid the master/slave switchover of the MPUs by using commands on the console interface.The system generates alarms, records the faults in the log file, and reports the alarms to the NMS.The cause of the master/slave switchover and the associated operations are recorded in the systemdiagnosis information base for users to analyze.

The system provides two clock boards in master/slave backup mode. If the system detects thatthe master clock board becomes faulty or is reset through a command, the system automaticallyperforms the master/slave switchover of clock boards. The master/slave switchover of clockboards does not result in phase offsets or interrupt services.

The master/slave switchover time of each key part is less than 100 us.

High Reliability of LPUs

The NE40E supports backup of key service interfaces of the same type through protocols.

l Supports VRRP on Ethernet interfaces. With extended VRRP, two interfaces located on asame NE40E or two NE40Es can back up each other. This ensures high reliability of theinterfaces.

l Supports backup of Eth-Trunk member interfaces, or backup of Eth-Trunk or IP-Trunkmember interfaces and non-member interfaces.

l Supports the bundling of interfaces on different LPUs into a trunk.You can access different LPUs through double links and bundle interfaces on differentLPUs into a trunk to ensure high reliability of services.



45

Inter-LPU bundling is implemented by high-performance hardware engines, thus ensuringload balancing of packets among different links.

The Hash algorithm based on the combination of the source and destination IP addressesload-balances traffic evenly on links.

Seamless switchover is implemented in the case of a link failure so that services areforwarded without interruption.

Through extended protocols, the NE40E backs up key service interfaces. In this manner, corerouters can monitor and back up the running status of interfaces when they carry LAN, MAN,or WAN services. Therefore, the routing table is not affected when the status of the backupinterface needs to be changed and services recover rapidly.

Transmission Alarm Suppression

Transmission alarm suppression can efficiently filter and suppress alarm signals. This preventsinterfaces from frequently flapping. In addition, transmission alarm customization enables thecontrol over the impact brought by alarms on the interface status.

Transmission alarm customization and suppression implement the following functions:

l Customizes alarms. This can specify the alarms that can cause the change of the interfacestatus.

l Suppresses alarms. This can filter out the burr and prevent the network from frequentlyflapping.

Ethernet OAM Fault Management

Ethernet OAM fault management includes the following functions:

l Ethernet in the First Mile OAM (EFM OAM)

Conforming to IEEE 802.3ah, the NE40E supports point-to-point Ethernet faultmanagement to detect faults in the last mile of the direct link on the user side of the Ethernet.Currently, the NE40E supports OAM discovery, link monitoring, remote fault notification,and remote loopback, as defined in IEEE 802.3ah.

l Connectivity Fault Management OAM (CFM OAM)

The following describes end-to-end Ethernet fault management in two aspects.

– Hierarchical MD

Each MD has a level that ranges from 0 to 7. The greater the value, the higher the level.The 802.1ag packets from a low-level MD are discarded when entering a high-levelMD. The 802.1ag packets from a high-level MD can be transmitted through a low-levelMD.

– End-to-end fault detection and location

The NE40E realizes end-to-end Ethernet fault management by conforming to IEEE802.1ag or not.

The NE40E supports MAC ping and MAC trace by transmitting Loop Back (LB) andLink Trace (LT) messages defined in IEEE 802.1ag to locate faults.

Fault detection and location not conforming to IEEE 802.1ag include general MAC pingand general MAC trace.



46

VRRPVRRP dynamically associates the virtual router with a physical router that carries services. Whenthe physical router fails, another router is elected to take over services. Failover is transparentto users and thus the internal network and the external network can communicate withoutinterruption.

The NE40E supports the following VRRP functions:

l mVRRPl VGMPl E-VRRPl VRRP For IPv6

GRGraceful Restart (GR) is a key technology in implementing HA. It is designed based on NSF.GR switchover and subsequent restart can be performed by the administrator or triggered byfaults. GR neither deletes the routing information from the routing table or the FIB nor resetsthe board during the switchover when faults occur. This prevents the service interruption of theentire system.

The NE40E supports system-level GR and protocol-level GR. Protocol-based GR includes:

l BGP GRl OSPF GRl IS-IS GRl MPLS LDP GRl Martini VLL GRl Martini VPLS GRl L3VPN GRl RSVP GRl PIM GR

BFDBFD is a detection mechanism used uniformly in an entire network. It is used to rapidly detectand monitor the connectivity of links or IP routes in a network.

BFD sends detection packets at both ends of a bidirectional link to check the link status in bothdirections. The defect detection is implemented at the millisecond level. The NE40E supportssingle-hop BFD and multi-hop BFD.

BFD of the NE40E supports the following applications.

l BFD for VRRPThe system uses BFD to detect and monitor the connectivity of links or IP routes in anetwork. The rapid VRRP switchover is thus triggered.

l BFD for FRR– BFD for LDP FRR– LDP FRR switchover is triggered after BFD detects faults on protected interfaces.



47

– BFD for IP FRR and BFD for VPN FRR– IP FRR and VPN FRR are triggered after BFD detects faults and reports fault

information to the upper layer applications.l BFD for static routesl BFD for IS-IS

The NE40E supports detection on the IS-IS adjacency by using the BFD session that isconfigured statically.BFD detects the fault of the link between the adjacent IS-IS nodes and rapidly reports thefault to IS-IS. Thus fast convergence of IS-IS routes is performed.

l BFD for OSPF/BGPThe NE40E supports OSPF and BGP in dynamically setting up and deleting the BFDsession.

l BFD for PIMBFD detection on IP-Trunks and Eth-TrunksOn the NE40E, BFD can detect a trunk and the member links of the trunk independently.That is, it can detect the connectivity of the trunk and that of an important member link ofthe trunk.

l BFD for LSPBFD for LSP performs fast fault detection of the LSP, the TE tunnel, and the PW. In thismanner, BFD for LSP implements fast switchover of MPLS services such as VPN FRR,TE FRR, and VLL FRR.

l BFD for Dot1q sub-interfacel BFD for mVSIl Multi-hop BFDl BFD For IPv6

BFD for OSPFv3, BFD for ISISv6, BFD for BGP4+, and BFDv6 for default IPv6l BFD for VPLS PWl BFD for VPLS/VLL PWl VPLS over LDP FRR/FW unicast

7.12 ClockThe NE40E supports the following clock features:

l Ethernet clock synchronizationl The Ethernet interfaces of the NE40E provide Ethernet clock synchronization so that the

clock quality and stratum of the network can be guaranteed.l 1588v2

The 1588v2 feature:– Supports the input and output of the externally synchronized time.– Supports 10M/100M/1000M/10G Ethernet interfaces and auto sensing of 10M/100M/

1000M Ethernet interfaces.– Supports Eth-Trunk.– Supports OC, BC, E2ETC, P2PTC, E2ETCOC, P2PTCOC and TCandBC.



48

– Allows the NE40E to function as a GrandMaster.

– Supports slave-only when functioning as an OC.

– Supports the dynamic BMC algorithm.

– Supports two delay measurement methods: Delay and PDelay

– Supports one-step mode and two-step mode in which 1588v2 packets that are used by1588v2 devices to perform time synchronization are timestamped..

– Supports multicast MAC encapsulation (the VLAN and 802.1p priority areconfigurable).

– Supports multicast UDP encapsulation (the source IP address, VLAN, and DSCPpriority are configurable).

– Supports unicast MAC encapsulation (the destination MAC, VLAN, and 802.1p priorityare configurable).

– Supports the performance monitoring function on Passive ports of a 1588v2 device.

– Supports unicast UDP encapsulation (the source IP address, destination IP address,destination MAC, VLAN, and DSCP priority are configurable).

– Uses the clock recovered through the Precision Time Protocol (PTP) as the clock sourceand supports the algorithm for dynamic clock source selection (based on the priorityand clock stratum).

– Implements clock recovery that complies with G.813.

– Implements frequency recovery that meets the requirements of the SDH equipmentclock (SEC) in G.823.

l 1588 ACR

– Supports frequency synchronization only.

– Supports the change of selected clock sources.

– Supports unicast UDP encapsulation (and the DSCP field).

– Complies with Recommendation G.8261 in terms of service modeling and networkingand performs clock recovery with accuracy that is prescribed by G.823.

– Supports 1588v2 header overlapping without affecting forwarding capabilities.

– Supports switchover between master and slave MPUs/SRUs without affecting services.

– Supports hot swapping of LPUs and sub-cards.

l Network Time Protocol (NTP) clock

The NE40E supports the following working modes of NTPv4:

– Server/client mode

– Peer mode

– Broadcast mode

– Multicast mode

The NE40E supports two NTP security mechanisms:

– Access authority

The NE40E provides four levels of access control. After receiving an NTP accessrequest packet, the NE40E matches it from the lowest access control level to the highestaccess control level. The first successfully matched access control level takes effect.The matching order is as follows:



49

peer: indicates the minimum access control. The remote end can send a time requestand a control query to the local end. The local clock can also be synchronized with theclock of the remote server.server: indicates that the remote end can send a time request and a control query to thelocal end. The local clock, however, is not synchronized with the clock of the remoteserver.synchronization: indicates that the remote end can only send a time request to the localend.query: indicates the maximum access control. The remote end can only send a controlquery to the local end.

l AuthenticationWhen configuring NTP authentication, note the following rules:The NTP authentication must be configured on both the client and the server; otherwise,the authentication does not take effect. If NTP authentication is enabled, keys must beconfigured and declared reliable.The server and the client must be configured with the same key.

l Internal clockThe NE40E provides an internal clock and can extract clock information from LPUs. Theclock precision reaches 4.6 ppm, that is, 0.00002s.



50

8 Applicable Environment

About This Chapter

8.1 Metro Ethernet Solution

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 8 Applicable Environment


51

8.1 Metro Ethernet SolutionA metro Ethernet consists of the core layer, edge layer, convergence layer, and access layer. Thecore layer is responsible for the high-speed forwarding of service data. The edge layer and theconvergence layer serve as the access point of various services. The services access the networkfor forwarding through the BRAS, the centralized PE, or the convergence node, based on theservice type. The access layer is responsible for the user access, and the devices at the accesslayer include a DSLAM, the converged switch, AG, and NodeB. Figure 8-1 shows thenetworking of the MAN.

Figure 8-1 MAN deployment

Access Ethernet Aggregation Edge Core Application

DSLAMCMTS

AccSwitch

Distributionnode

Distributionnode

AggregafionNode

BRAS

VoD ES

PE

P/PE

P/PE

P/PE

Internet

SoftX

VoD CS

InternetInternetInternetInternet

The convergence layer device accesses and forwards the services through the IP or MPLStechnologies. Personal services are accessed to the convergence node through the DSLAM, andcorporate services are converged at Layer 2 through a switch or are directly accessed to theconvergence node.

l DSLAM: is short for the Digital Subscriber Line Access Multiplexer that accesses thepersonal services through the permanent virtual circuit (PVC). The DLSAM adds theVLAN or QinQ tag based on the types of users and services, and is generally connected tothe aggregation node.

l Switch: refers to the access switch that converges the Layer 2 corporate services to theaggregation node.

l Aggregation node: refers to the aggregation node connected to the distributed service node(PE). The aggregation node distinguishes the VLAN or QinQ user services, forwards Layer3 services or VPN services, or transparently transmits services to the BRAS or thecentralized PE through the IP or MPLS technologies.

l Distribution node: refers to the distribution node that converges the services in the metroEthernet. The distribution node terminates the IP or MPLS technologies and transparentlytransmits the services to the BRAS or the centralized PE.

l BRAS: refers to a device that processes PPPoE login services of individual users.l PE: refers to the centralized service node, which can also serve as the distribution node. PE

accesses the services that should be converged and processed, such as centralized L3VPNservices.



52

l P/PE: refers to the core forwarding node or the edge node on the backbone network. P orPE rapidly forwards the services or accesses the services to the backbone network.

The NE40E is applicable to the aggregation node and the distribution node to guarantee theaccess of individual services and corporate services.

Individual Service SolutionThe NE40E supports the following individual services:

l HSI service: The DSLAM adds QinQ tags to distinguish user services. The outer VLANtag indicates the service type. The NE40E at the aggregation node transparently transmitsthe services to the NE40E at the distribution node through VLL or VPLS. The distributionnode terminates the transmission and then transparently transmits the QinQ data to theBRAS.

l VoD/VoIP: The NE40E at the aggregation node terminates the VLAN or QinQ tag addedby the DSLAM, and forwards the services to Layer 3 network or accesses the services toL3VPN for forwarding.

l BTV: The NE40E at the aggregation node serves as the designated router (DR) of theProtocol Independent Multicast (PIM). The aggregation node receives the multicast datadistributed through the PIM protocol, and then sends the data to the DSLAM throughmulticast VLAN. The user joins or withdraws a group through IGMP, and sends the hotchannels to DR.

Enterprise Service SolutionThe NE40E supports the following enterprise services:

l Corporate dedicated line: The corporate dedicated line is connected to the Layer 3 networkthrough the NE40E at the aggregation node.

l E-LINE: The PW, an end-to-end L2VPN tunnel, is set up between the NE40E at theaggregation node and the peer end. The E-LINE services are transmitted to the peer endthrough different tunnels based on the VLAN or QinQ tag identified at the aggregationnode.

l E-LAN: The NE40E at the aggregation node creates the VSI, and forwards the service datato different VSIs for forwarding after the VLAN or QinQ tag is identified. The service datacan also be accessed to the E-LAN services through H-PVLS, during which the VSI iscreated by the distribution node.

l L3VPN: The services are accessed to the Virtual Route Forwarding (VRF) at theaggregation node, or accessed to the centralized service node for VRF forwarding throughHoVPN.

1588v2 Clock SolutionAs shown in Figure 8-2, the bearer network synchronizes its time through the GPS or externaltime sources, and then provides the clock or time externally; the nodes support multicast MACencapsulation.

The nodes in the bearer network can trace a BITS clock. All the nodes on the network serve asboundary clocks (BCs), and all the BCs support the peer delay mechanism to be adapted to fastswitchover of links. The nodes that do not support IEEE 1588 can be configured to support GPSif these nodes are connected through POS or ATM links. BCs send clock signals to the Node Bthat support IEEE 1588 through multicast MAC addresses. The Node B that does not support



53

IEEE 1588 synchronizes frequency through Ethernet clock synchronization or through WANinterfaces.

Figure 8-2 1588v2 clock solution

POSBC BC

BCBC

FE

GEGE

FE E1

1588v2

1588v2 1588v2

1588v2

Node Bwith

1588v2

Node Bwith 1588v2

Node Bwithout 1588v2

GPS GPS

Node Bwithout 1588v2

E1



54

9 Operation and Maintenance

About This Chapter

9.1 System Configuration Modes

9.2 System Management and Maintenance

9.3 Device Running Status Monitoring

9.4 HGMP

9.5 System Service and Status Tracking

9.6 System Test and Diagnosis

9.7 NQA

9.8 In-Service Debugging

9.9 Upgrade Features

9.10 License

9.11 Other Operation and Maintenance Features

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 9 Operation and Maintenance


55

9.1 System Configuration ModesThe NE40E supports two configuration modes: command line configuration and NMSconfiguration.

You can configure the NE40E by using command lines through the following:

l Console interfacel Auxiliary (AUX) portl Telnet

As a command input interface, the console interface can send command lines to the control plane.

As a debugging interface, the console interface can receive debugging information from thecontrol plane and data plane, and deliver debugging commands and control commands.

The NMS configuration supports the configuration through the SNMP-based NMS.

9.2 System Management and MaintenanceThe NE40E provides powerful system management and maintenance functions:

l Board detection, hot swap detection, Watchdog, board resetting, RUN indicator anddebugging indicator control, fan and power supply control, master/slave switchovercontrol, and version query

l Local and remote loading and upgrade of software and data, and functions such as versionrollback, backup, saving, and clearing of version information

l Hierarchical user authority management, operation log management, command line onlinehelp, and comments after the commands

l Supports inband and outband NMS interfaces.l Three user authentication modes: local authentication, RADIUS authentication, and

HWTACACS authentication, which authenticate and authorize users through commandlines and SNMP.

l Plug and Playl Multi-user operationl Query on Layer 2 or Layer 3 interfacesl Hierarchical management, alarm classification, and alarm filteringl Support of the shutdown and undo shutdown commands on interfaces and optical modules

9.3 Device Running Status MonitoringThe running status of the NE40E can be monitored through the information center.

Syslog is a sub-function of the information center. Syslog is over UDP. It outputs log informationto the log host through port 514.

The information center receives and processes the following types of information:

l Log information



56

l Debugging informationl Trap information

Information is classified into eight severity levels. The lower the level, the higher the severity.The following table shows the detailed information.

Level

Severity

Description

0 Emergency

A fatal exception occurs on the device. The system is unable to functionproperly and must be restarted. For example, the device is restarted due toprogram exceptions or memory usage errors are detected.

1 Alert A serious exception occurs on the device, which requires immediate actions.For example, the memory usage of the device reaches the upper threshold.

2 Critical

A critical exception occurs on the device, which needs to be handled andanalyzed. For example, the memory usage exceeds the alarm threshold; thetemperature exceeds the alarm threshold; and Bidirectional ForwardingDetection (BFD) detects that a device is unreachable or detects error messagesgenerated by the local device.

3 Error Improper operation is performed or abnormal process occurs on the device,which does not affect subsequent services but requires attention and causeanalysis. For example, users enter incorrect commands or passwords; errorprotocol packets are received by other devices.

4 Warning

An abnormality that may cause the device to malfunction occurs on thedevice, which requires attention. For example, a routing process is disabledby the user; BFD detects packet loss; and error protocol packets are detected.

5 Notice

A key operation is performed to keep the device running normally. Forexample, the user runs the shutdown command on the interface, a neighboris discovered, and the protocol state machine changes status.

6 Informational

A routine operation is performed. For example, the user runs a displaycommand.

7 Debugging

A routine operation is performed, which requires no action.

The information center supports 10 channels, of which channels 0 through 5 each have a defaultchannel name. By default, the six channels correspond to six directions in which information isoutput. The log information on the CF card is output to log files through Channel 9 by default.This means that a total of seven default output directions are supported.

When multiple log hosts are configured, you can configure log information to be output todifferent log hosts through one channel or multiple channels. For example, you can configuresome log information to be output to a log host through Channel 2 (loghost), and some loginformation to a log host through Channel 6. In addition, you can change the name of Channel6 to implement the desired channel management.



57

The NE40E stores all alarms in a log file, and provides the CF card to store the log file. Howlong the alarms can be stored depends on the number of the alarms. Generally, the alarms canbe stored for months.

9.4 HGMPThe NE40E supports the Huawei Group Management Protocol (HGMP). HGMP is a clustermanagement protocol developed by Huawei.

HGMP is used to group Layer 2 devices that are connected to the NE40E into a unifiedmanagement domain, that is, a cluster. HGMP supports automatic collection of networktopologies and provides integrated maintenance and management channels. In this manner, acluster uses only one IP address for external communications, simplifying device managementand saving IP addresses.

9.5 System Service and Status TrackingThe NE40E provides the following functions for tracking system services and status:

l Monitors the change of the state machine of routing protocols.l Monitors the change of the state machine of MPLS LDP.l Monitors the change of the state machine of a VPN.l Monitors the types of protocol packets sent by the forwarding engine to the control plane

and displays detailed information about packets by enabling debugging.l Detects and collects the statistics on malformed packets.l Supports HGMP.l Displays a notification when the processing of abnormality starts.l Collects the statistics on the resources used by each feature.

9.6 System Test and DiagnosisThe NE40E supports the debugging of running services, including online recording of keyevents, packet processing, packet parsing, and status switching of services at specified time,which serves as powerful support for device commissioning and networking. Debugging can beenabled or disabled through the console interface for specific service (information about arouting protocol) or specific interface (information about a routing protocol on a specificinterface).

The NE40E provides the system-based trace function to detect and diagnose running software,online recording of important events such as task switchover and interruption, queue readingand writing, and system abnormality. If the system is restarted after a fault occurs, the NE40Ecan read trace information that functions as a reference for fault location. Trace can be enabledand disabled through commands on the console interface.

In addition, the NE40E supports real-time query about CPU usage of the MPU and LPU.

Debugging and trace information provided by the NE40E is classified into different levels.Sensitive information with different levels can be output to different destinations as configured.For example, information can be output to the console interface, Syslog server, or SNMP agentto trigger traps.



58

When voice services on the network deteriorate, or mosaics appear in some videos, theNE40E may have sent or received incorrect packets or have lost packets. You can capture packetsto locate the problems. The packet capture function can be used to capture the packets sent tothe CPU, and the packets forwarded in the inbound or outbound direction. Compared with theport mirroring function, the packet capture function is easier and faster to configure.

9.7 NQAThe NE40E supports Network Quality Analysis (NQA).NQA measures the performance ofdifferent protocols running on the network. In that case, carriers can collect the operation indexof networks in real time, such as:

l Total delay of the HTTPl Delay in TCP connectionl Delay in DNS resolutionl File transmission speedl Delay in FTP connectionl DNS resolution error ratio Taking control of these indexes, carriers can provide network

services of different levels and charge differently. NQA is also an effective tool fordiagnosing and locating a network fault.

NQA supports the following functions:

l PWE3 tracertl Multicast pingl Multicast tracertl CE-ping (ping the host from a VPLS PW)l VPLS MAC ping and VPLS MAC tracel VPLS MAC purge and VPLS MAC populatel LSP ping, LSP tracerout, and MPLS jitterl Verification of DNS functions through DISMAN-NSLOOKUP-MIBl NMS management over all NQA functions through NQA-MIBl Transmission of consecutive 3000 simulated voice packets in one testl Minimum transmission intervals at 10 ms

9.8 In-Service DebuggingThe NE40E provides port mirroring to map specific traffic to a certain monitoring interface. Inthis case, in-service debugging can be performed for the advanced maintenance engineers todebug and analyze the operation status of the network.



59

9.9 Upgrade Features

In-Service UpgradeThe NE40E supports in-service upgrade of software. At the same time, the NE40E providesonline patching for the system software. You can upgrade only the features that need to beimproved.

One-Command System UpgradeThe upgrade process of the NE40E is optimized. You can use one command to complete theupgrading. Thus, you can save time. During the upgrading process, the progress is displayed.After the upgrading is complete, you can view the results.

Software Version RollbackDuring the upgrading process, if the system fails to start by using the new system software, thesystem software in the last successful startup is adopted.

The rollback function provided by the NE40E prevents the services from being affected by thefailure in system upgrade.

9.10 LicenseWith the variation of the NE40E software functions and higher ratio of software cost occupyingthe overall cost, the current service mode cannot satisfy the development requirements ofcustomers and carriers.

l Common users need to reduce the purchase cost.l Upgrade and expansion users need to effectively control the capacity and functions.

To satisfy the requirements of different users, the NE40E needs to implement the flexibleauthorization to service modules.

For the authorization control of service modules, the NE40E provides the License authorizationmanagement platform through the Global Trotter License (GTL). Through the Licenseauthorization mode:

l Common users can purchase service modules as required and reduce the purchase cost.l Upgrade and expansion users can expand the capacity, and support and maintain the

functions by applying for a new License.

9.11 Other Operation and Maintenance FeaturesThe NE40E supports the following configuration features in addition to the preceding features:

l Provides hierarchical commands to prevent unauthorized users from logging in to a device.l Users can type in a question mark "?" to obtain online help.l Provides detailed debugging information to diagnose network faults.



60

l Provides DosKey-like functions to run a history command.l Provides command line descriptors for partial match of keywords not conflicting with

keywords of other command lines. For example, you can enter "disp" for the displaycommand.



61

10 NMS

SNMPThe NE40E supports device operation and management by the network management stationthrough SNMP.

The NE40E supports SNMPv1, SNMPv2c, and SNMPv3.

l SNMPv1SNMPv1 supports community name-based and MIB view-based access control.

l SNMPv2cSNMPv2c supports community name-based and MIB view-based access control.

l SNMPv3SNMPv3 inherits the basic functions of SNMPv2c, defines a management frame, andintroduces a User-based Security Model (USM) to provide a more secure access controlmechanism for users.SNMPv3 supports user groups, user group-based access control, user-based access control,and authentication and encryption mechanisms.

NMSThe NE40E adopts Huawei iManager U2000 network management system. It supportsSNMPv1/v2c/v3 and the client/server architecture. The network management system can runindependently on many operation systems, such as Windows NT/2000/XP, UNIX (Sun, HP, andIBM). The NE40E also provides a multi-lingual graphical user interface.

LLDPThe Link Layer Discovery Protocol (LLDP) is a Layer 2 protocol defined in IEEE 802.1ab.LLDP specifies that the status information is stored on all interfaces and the device can send itsstatus to the neighbor stations. The interfaces can also send information about changes in thestatus to the neighbor stations as required. The neighbor stations then store the receivedinformation in the standard SNMP MIB. The NMS can search for Layer 2 information in theMIB. As specified in the IEEE 802.1ab standard, the NMS can also discover unreasonable Layer2 configurations based on information provided by LLDP.

When LLDP runs on the devices, the NMS can obtain Layer 2 information about all the devicesto which it connects and detailed network topology information. This is helpful to the rapid

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 10 NMS


62

expansion of the network and acquirement of detailed network topologies and changes. LLDPalso helps discover unreasonable configurations on networks and reports the configurations tothe NMS. This removes incorrect configurations in time.

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description 10 NMS


63

A Acronyms and Abbreviations

A

AAA Authentication, Authorization and Accounting

AAL5 ATM Adaptation Layer 5

AC Access Controller

ACL Access Control List

AF Assured Forwarding

ANSI American National Standard Institute

AP Access Point

ARP Address Resolution Protocol

ASBR Autonomous System Boundary Router

ASIC Application Specific Integrated Circuit

ATM Asynchronous Transfer Mode

AUX Auxiliary (port)

B

BE Best-Effort

BGP Border Gateway Protocol

BGP4 BGP Version 4

C

CAR Committed Access Rate

CBR Constant Bit Rate

CE Customer Edge

HUAWEI NE40E-X1 & NE40E-X2 Universal ServiceRouterProduct Description A Acronyms and Abbreviations


64

CHAP Challenge Handshake Authentication Protocol

CoS Class of Service

CPU Center Processing Unit

CR-LDP Constrained Route - Label Distribution Protocol

D

DAA Destination Address Accounting

DC Direct Current

DHCP Dynamic Host Configuration Protocol

DNS Domain Name Server

DS Differentiated Services

E

EACL Enhanced Access Control List

EF Expedited Forwarding

EMC EElectroMagnetic Compatibility

F

FCC Fast Channel Change

FE Fast Ethernet

FEC Forwarding Equivalence Class

FIB Forward Information Base

FIFO First In First Out

FR Frame Relay

FTP File Transfer Protocol

G

GE Gigabit Ethernet

GRE Generic Routing Encapsulation

GTS Generic Traffic Shaping

H



65

HA High availablity

HDLC High level Data Link Control

HTTP Hyper Text Transport Protocol

I

iVSE Integrated Value-added Service Engine

ICMP Internet Control Message Protocol

IDC Internet Data Center

IEEE Institute of Electrical and Electronics Engineers

IETF Internet Engineering Task Force

IGMP Internet Group Management Protocol

IGP Interior Gateway Protocol

IP Internet Protocol

IPoA IP Over ATM

IPTN IP Telephony Network

IPTV Internet Protocol Television

IPv4 IP version 4

IPv6 IP version 6

IPX Internet Packet Exchange

IS-IS Intermedia System-Intermedia System;

ISP Interim inter-switch Signaling Protocol

ITU International Telecommunication Union - TelecommunicationStandardization Sector

L

LAN Local Area Network

LCD Liquid Crystal Display

LCP Link Control Protocol

LDP Label Distribution Protocol

LER Label switching Edge Router

LPU Line Processing Unit

LSP Label Switched Path

LSR Label Switch Router



66

M

MAC Media Access Control

MBGP Multiprotocol Border Gateway Protocol

MD5 Message Digest 5

MIB Management Information Base

MP Multilink PPP

MPLS Multi-protocol Label Switch;

MSDP Multicast Source Discovery Protocol

MSTP Multiple Spanning Tree Protocol

MTBF Mean Time Between Failures

MTTR Mean Time To Repair

MTU Maximum Transmission Unit

N

NLS Network Layer Signaling

NP Network Processor

NTP Network Time Protocol

NVRAM Non-Volatile Random Access Memory

O

OSPF Open Shortest Path First

P

PAP Password Authentication Protocol

PE Provider Edge

PFE Packet Forwarding Engine

PIC Parallel Interference Cancellation

PIM-DM Protocol Independent Multicast-Dense Mode

PIM-SM Protocol Independent Multicast-Sparse Mode

POP Point Of Presence

POS Packet Over SDH/SONET



67

PPP Point-to-Point Protocol

PQ Priority Queue

PT Protocol Transfer

PVC Permanent Virtual Channel

Q

QoE Quality of Experience

QoS Quality of Service

R

RADIUS Remote Authentication Dial in User Service

RAM Random-Access Memory

RED Random Early Detection

RFC Requirement for Comments

RH Relative Humidity

RIP Routing Information Protocol

RMON Remote Monitoring

ROM Read Only Memory

RP Rendezvous Point

RPR Resilient Packet Ring

RSVP Resource Reservation Protocol

RSVP-TE RSVP-Traffic Engineering

S

SAP Service Advertising Protocol

SCSR Self-Contained Standing Routing

SDH Synchronous Digital Hierarchy

SDRAM Synchronous Dynamic Random Access Memory

SFU Switch Fabric Unit

SLA Service Level Agreement

SNAP SubNet Attachment Point

SNMP Simple Network Management Protocol



68

SONET Synchronous Optical Network

SP Strict Priority

SPI4 SDH Physical Interface

SSH Secure Shell

STM-16 SDH Transport Module -16

SVC Switching Virtual Connection

T

TCP Transfer Control Protocol

TE Traffic Engineering

TFTP Trivial File Transfer Protocol

TM Traffic Manager

ToS Type of Service

TP Topology and Protection packet

U

UBR Unspecified Bit Rate

UDP User Datagram Protocol

UNI User Network Interface

UTP Unshielded Twisted Pair

V

VBR-NRT Non-Real Time Variable Bit Rate

VBR-RT Real Time Variable Bit Rate

VC Virtual Circuit

VCI Virtual Channel Identifier

VDC Variable Dispersion Compensator

VLAN Virtual Local Area Network

VLL Virtual Leased Line

VPI Virtual Path Identifier

VPLS Virtual Private LAN Service

VPN Virtual Private Network



69

VRP Versatile Routing Platform

VRRP Virtual Router Redundancy Protocol

W

WAN Wide Area Network

WFQ Weighted Fair Queuing

WRED Weighted Random Early Detection

WRR Weighted Round Robin



70

Documents

NE40E-X1&NE40E-X2 Product Description(V600R003C00_02) (1)