Professional Documents
Culture Documents
V600R003C00
Product Description
Issue
02
Date
2011-08-12
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 02 (2011-08-12)
Related Versions
The following table lists the product versions related to this document.
Product Name
Version
HUAWEI NetEngine40E
Universal Service Router
V600R003C00
Intended Audience
This document is intended for:
l
Commissioning engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Issue 02 (2011-08-12)
ii
Symbol
Description
DANGER
WARNING
CAUTION
TIP
NOTE
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Service Features
7.14 Clock. The performance monitoring function on Passive ports of a 1588v2 device
is added.
Issue 02 (2011-08-12)
iii
Contents
Contents
About This Document.....................................................................................................................ii
1 New Features of V600R003C00...................................................................................................1
2 Product Positioning.......................................................................................................................3
2.1 Product Positioning.............................................................................................................................................4
3 Product Architecture.....................................................................................................................5
3.1 Physical Architecture..........................................................................................................................................6
3.2 Logical Architecture...........................................................................................................................................6
3.3 Software Architecture.........................................................................................................................................7
3.4 Data Forwarding Process....................................................................................................................................9
4 Technical Specifications.............................................................................................................11
5 Boards............................................................................................................................................14
5.1 FPIC..................................................................................................................................................................15
5.2 LPUI-40............................................................................................................................................................18
5.3 LPUI-41............................................................................................................................................................18
5.4 LPUI-100..........................................................................................................................................................19
5.5 LPUS-41...........................................................................................................................................................19
5.6 SPU...................................................................................................................................................................20
6 Link Features................................................................................................................................21
6.1 E1/CE1/T1/CT1/E3/T3/CT3 Link Features.....................................................................................................22
6.2 Ethernet Link Features......................................................................................................................................22
6.3 POS Link Features............................................................................................................................................23
6.4 CPOS Link Features.........................................................................................................................................24
6.5 ATM Link Features..........................................................................................................................................25
6.6 FR Link Features..............................................................................................................................................26
7 Service Features...........................................................................................................................27
7.1 Ethernet Features..............................................................................................................................................28
7.1.1 Layer 2 Ethernet Features........................................................................................................................28
7.1.2 Layer 3 Ethernet Features........................................................................................................................28
7.1.3 QinQ Features..........................................................................................................................................28
7.1.4 Flexible Access to VPNs.........................................................................................................................29
Issue 02 (2011-08-12)
iv
Contents
8 Applicable Environment............................................................................................................66
8.1 Application on an IP Bearer Network..............................................................................................................67
8.2 Application on an IPTV Bearer Network.........................................................................................................68
8.3 Application on a Multi-Service IP MAN.........................................................................................................69
8.4 Application on an IPv6 Backbone Network.....................................................................................................70
8.5 IP RAN Solution...............................................................................................................................................71
8.6 iVSE Solution...................................................................................................................................................73
Contents
9.7 NQA..................................................................................................................................................................80
9.8 In-Service Debugging.......................................................................................................................................80
9.9 Upgrade Features..............................................................................................................................................81
9.10 License............................................................................................................................................................81
9.11 Other Operation and Maintenance Features...................................................................................................81
10 NMS.............................................................................................................................................83
A Acronyms and Abbreviations..................................................................................................85
Issue 02 (2011-08-12)
vi
Where to Place
5.1 FPIC
Issue 02 (2011-08-12)
Where to Place
5.3 LPUI-41
5.4 LPUI-100
5.5 LPUS-41
Issue 02 (2011-08-12)
5.6 SPU
IPSEC
7.2.6 IPSEC
IP RAN
NSR
2 Product Positioning
Product Positioning
Issue 02 (2011-08-12)
2 Product Positioning
Rich services
Large capacity
High performance
High availability
The NE40E can be classified into the NE40E-X16, NE40E-X8, NE40E-X3, and NE40E-8.
Issue 02 (2011-08-12)
NE40E-X16
NE40E-X8
NE40E-X3(AC)
NE40E-8
NE40E-X3(DC)
3 Product Architecture
Product Architecture
Issue 02 (2011-08-12)
3 Product Architecture
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 comprises the system backplane, /Main Processing Units (MPUs),
Line Processing Units (LPUs), and Switch and Fabric Units (SFUs). It is connected to the NMS
through NMS interfaces. The functional host system processes data as well as monitors and
manages the entire system, including the power distribution system and heat dissipation system.
Figure 3-1 shows the functional host system of the NE40E.
Figure 3-1 Functional host system
Backplane
Monitoring unit
Management unit
POS/
Ethernet
Physical
interface unit
Forwarding
unit
Monitoring
bus
System
Management monitoring unit
Management bus
bus
Management
switching unit
bus
MPU
(1)
System
contorlling unit (Master)
Monitoring
bus
Serial link
group
Monitoring
System
bus
Management monitoring unit
Management bus
bus
switching unit
(1)
Monitoring unit
Management unit
POS/
Ethernet Physical
interface unit
Monitoring
bus
MPU
System
controlling unit (Slave)
Monitoring
Switching network
bus
Management
bus
Management monitoring unit
Switching network
bus
control unit
Forwarding
unit
Switching
network
Serial link
group
SFU module
(1) The link connects to the managment bus switching unit of another MPU
Data plane
Issue 02 (2011-08-12)
3 Product Architecture
Monitoring plane
LPU
Monitoring
unit
Monitoring
unit
Monitoring
plane
Monitoring
unit
Control and
management
plane
MPU
Management
unit
Management
unit
System
monitoring unit
Monitoring
unit
Management
unit
System
controlling unit
Switching
network
control unit
Management
unit
Forwarding
unit
Data plane
Forwarding
unit
LPU
Forwarding
unit
Switching
network
Forwarding
unit
LPU
The data plane is responsible for high speed processing and non-blocking switching of data
packets. It encapsulates or decapsulates packets, forwards IPv4/IPv6/MPLS packets,
performs QoS as well as scheduling and internal high-speed switching, and collects
statistics.
The control and management plane completes all control and management functions for
the system and is the core of the entire system. Control and management units process
protocols and signals, and maintain, manage, report on, and control system status.
The monitoring plane monitors the ambient environment to ensure secure and stable
operation 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 plane
isolates the faulty unit promptly so that other parts of the system can continue to run
normally.
Issue 02 (2011-08-12)
3 Product Architecture
SNMP
FAN
Monitoring
RPS
Master
RPS
Slave
IPC
LPU
FSU
FSU
EFU
EFU
LPU
LPU
FSU
FSU
EFU
EFU
LPU
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 MPU
and 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,
generate unicast, multicast, and MPLS forwarding tables, and they deliver information
concerning all the preceding mentioned to the LPU.
The FSU implements the functions of the link layer and some functions of the IP protocol
stack on interfaces.
Issue 02 (2011-08-12)
3 Product Architecture
PIC
Datagram
Datagram
Processing on the incoming
interface
PFE
QoS in the
upstream
IPv4 unicast
IPv4 multicast
MPLS
IPv6
Packet
encapsulation
and forwarding
in the
downstream
Queue
scheduling
Congestion
management
QoS in the
downstream
Congestion
management
Queue
scheduling
Multicast replication
TM
Packet fragmentation
Packet reassembly
Micro cell
Micro cell
SFU
As shown in Figure 3-4, 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 Random
Access 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 on
the direction of the data flow.
l
Issue 02 (2011-08-12)
Upstream process: The Physical Interface Card (PIC) encapsulates packets to frames and
then sends them to the PFE. On the PFE of the inbound interface, the system decapsulates
the frames and identifies the packet types. It then classifies traffic according to the QoS
configurations on the inbound interface. After traffic classification, the system searches the
Forwarding Information Base (FIB) for the outbound interfaces and next hops of packets
to be forwarded. To forward an IPv4 unicast packet, for instance, the system searches the
FIB for the outbound interface and next hop according to the destination IP address of the
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
3 Product Architecture
packet. Finally, the system sends the packets containing information about outbound
interfaces and next hops to the traffic management (TM) module.
l
Issue 02 (2011-08-12)
Downstream process: Information about packet types that have been identified in the
upstream process and about the outbound interfaces is encapsulated through the link layer
protocol and the packets are stored in corresponding queues for transmission. If an IPv4
packet whose outbound interface is an Ethernet interface, the system needs to obtain the
MAC address of the next hop. Outgoing traffic is then classified according to the QoS
configurations on the outbound interfaces. Finally, the system encapsulates the packets
with new Layer 2 headers on the outbound interfaces and sends them to the PIC.
10
4 Technical Specifications
Technical Specifications
NE40E-X16
NE40E-X8
NE40E-X3
NE40E-8
Dimensions (width x
depth x height, chassis
main body dimensions)
442 mm x 650
mm x 1420
mm (17.40 in.
x 25.59 in. x
55.91 in.)
442 mm x 650
mm x 620 mm
(17.40 in. x
25.59 in. x
24.41 in.)
DC chassis:
442 mm x 650
mm x 175 mm
(17.40 in. x
25.59 in. x
6.89 in.)
442 mm x 669
mm x 886 mm
(17.40 in. x
26.34 in. x
34.88 in.)
AC chassis:
442 mm x 650
mm x 220 mm
(17.40 in. x
25.59 in. x
8.66 in.)
Dimensions (width x
depth x height, chassis
dimensions including
the chassis's front and
rear assembly and cable
racks)
442 mm x 770
mm x 1420
mm (17.40 in.
x 30.31 in. x
55.91 in.)
442 mm x 770
mm x 620 mm
(17.40 in. x
30.31 in. x
24.41 in.)
DC chassis:
442 mm x 750
mm x 175 mm
(17.40 in. x
29.53 in. x
6.89 in.)
AC chassis:
442 mm x 750
mm x 220 mm
(17.40 in. x
29.53 in. x
8.66 in.)
Installation
Issue 02 (2011-08-12)
11
Item
4 Technical Specifications
NE40E-X16
267 kg
(588.74 lb)
NE40E-X8
130 kg
(286.65 lb)
NE40E-X3
DC chassis:
l 36kg
(79.38 lb)
(LPUF-21
)
NE40E-8
147 kg (324.14
lb)
l 41kg
(90.41 lb)
(LPUF-40
)
AC chassis:
l 46kg
(101.43 lb)
(LPUF-21
)
l 51kg
(112.46 lb)
(LPUF-40
)
Issue 02 (2011-08-12)
Maximum power
6500 W
3300 W
1100 W
2200 W
Heat dissipation
21089 BTU/
hour
10707 BTU/
hour
3569 BTU/
hour
7137 BTU/
hour
MTBF(year)
22.53
22.41
22.78
21.82
MTTR(hour)
0.5
0.5
0.5
0.5
Reliability
0.999997467
0.999997453
0.9999975
0.999997384
22
11
12
16
Forwarding capacity
3200 Mpps
1600 Mpps
300 Mpps
400 Mpps
Switching capacity
12.58Tbit/s
(bidirectional)
7.08Tbit/s
(bidirectional)
1.08 Tbit/s
(bidirectional)
640 Gbit/s
(bidirectional)
Backplane bandwidth
30 Tbit/s
15 Tbit/s
1.35 Tbit/s
2 Tbit/s
Interface capacity
(bidirectional)
3.2 Tbit/s
(bidirectional)
1.6 Tbit/s
(bidirectional)
240 Gbit/s
(bidirectional)
320 Gbit/s
(bidirectional)
SDRAM
2 GB (The
capacity can
be extended to
4 GB.)
2 GB (The
capacity can
be extended to
4 GB.)
2 GB
2 GB
Flash
32 MB
32 MB
32 MB
32 MB
12
Item
CF Card
DC input
voltage
AC input
voltage
Ambient
temperature
Issue 02 (2011-08-12)
4 Technical Specifications
NE40E-X16
NE40E-X8
NE40E-X3
NE40E-8
Two 1-GB CF
cards on each
MPU
Two 1-GB CF
cards on each
MPU
Two 1-GB CF
cards on each
MPU
Two 512-MB
CF cards on
each MPU
Rated
voltage
-48 V
Maxim
um
voltage
range
-38 V to -72 V
Rated
voltage
220 V
Maxim
um
voltage
range
90 V to 275 V
90 V to 275 V
90 V to 275 V
90 V to 275 V
175 V to 275
V
(recommend)
175 V to 275 V
(recommend)
175 V to 275
V
(recommend)
175 V to 275
V
(recommend)
Longterm
Shortterm
Storage
temperature
Relative
ambient
humidity
Longterm
Shortterm
Relative
storage
humidity
Elevation
limit for
long-term
work
Storage
elevation
limit
13
5 Boards
Boards
Issue 02 (2011-08-12)
14
5 Boards
5.1 FPIC
LPUF-10 and Its FPICs
The LPUF-10 provides four sub-slots and supports a maximum of 10 Gbit/s bandwidth.
The LPUF-10 FPICs support hot swapping and automatic configuration restoration. The
LPUF-10 support installation of different types of FPICs.
Table 5-1 LPUF-10 FPICs
Issue 02 (2011-08-12)
FPIC Name
Remarks
15
5 Boards
FPIC Name
Remarks
Issue 02 (2011-08-12)
FPIC Name
Remarks
16
5 Boards
Remarks
Issue 02 (2011-08-12)
FPIC
Remarks
17
5 Boards
FPIC
Remarks
5.2 LPUI-40
The LPUI-40 can be used only on the NE40E-X16, NE40E-X8 and NE40E-X3.
Table 5-5 LPUI-40
Board Name
Remarks
5.3 LPUI-41
The LPUI-41 can be used only on the NE40E-X16, NE40E-X8, NE40E-X3.
Table 5-6 LPUI-41
Board Name
Issue 02 (2011-08-12)
Remarks
18
5 Boards
Board Name
Remarks
5.4 LPUI-100
The LPUI-100 can be used only on the NE40E-X16 and NE40E-X8.
Table 5-7 LPUI-100
Board Name
Remarks
5.5 LPUS-41
The LPUS-41 can be used only on the NE40E-X16, NE40E-X8 and NE40E-X3.
Table 5-8 LPUS-41
Board Name
Issue 02 (2011-08-12)
Remarks
19
5 Boards
5.6 SPU
Table 5-9 SPU
Board Name
Issue 02 (2011-08-12)
Remarks
20
6 Link Features
Link Features
Issue 02 (2011-08-12)
21
6 Link Features
PPP
HDLC
CRTP/ECRTP
E1/CE1/T1/CT1 interfaces and their serial interfaces support the following link protocols:
l
ATM
TDM
ATM IMA
LCP
IPCP
MPLSCP
PAP
CHAP
The formed Eth-Trunk interface functions the same as a common Ethernet interface in
supporting services.
l
Issue 02 (2011-08-12)
22
6 Link Features
E-Trunk, that is, Eth-Trunk interface whose member interfaces reside on different devices
l
1588v2 clock
VLAN sub-interfaces
SDH/SONENT encapsulation
FR on POS interfaces
POS sub-interfaces
POS sub-interfaces support point-to-point (P2P) .
IP-Trunk
The NE40E supports the following IP bundling modes:
Inter-board IP bundling
Inter-chassis IP bundling
IP bundling of channels of different rates
Dynamic creating and removing of IP-Trunk interfaces
Bundling of a physical channel into an IP-Trunk by using commands on physical
interfaces
POS interfaces support SDH alarms at the section layer, line layer, and path layer.
Issue 02 (2011-08-12)
23
6 Link Features
A POS interface prompts a fault and then notifies the control software on the board of the
fault.
The control software of the board confirms the fault, updates the interface status, and then
notifies the MPU of the interface status.
To ensure fast route convergence and network stability, the SPF timer and LSP timer need to be
configured on the POS interface to function together with route convergence.
Channelization
The channelization granularity of CPOS interfaces is as follows:
A 155 Mbit/s CPOS interface can be channalized into 63 E1 channels, 84 T1 channels,
or N x 64 kbit/s channels.
A 155 Mbit/s CPOS interface can be channelized into 3 E3/T3 channels.
The E1 interface channalized from a CPOS interface, in compliance with SAToP, can
transparently transmit unstructured TDM services through PWs on an MPLS network.
The E1 interface channalized from a CPOS interface, in compliance with CESoPSN, can
transparently transmit structured TDM services through PWs on an MPLS network.
PPP/HDLC/ATM/TDM/ATM IMA
The NE40E provides CPOS interfaces at 155 Mbit/s. At the link layer, CPOS interfaces
support the following protocols:
PPP
HDLC
TDM
ATM
ATM IMA
FR
PPP on CPOS interfaces supports the following protocols:
LCP
IPCP
MPLSCP
MP
PAP
CHAP
CRTP/ECRTP on 155 Mbit/s CPOS interfaces and 64 kbit/s, E1, T1, T3, and E3 interfaces
channelized from a 155 Mbit/s CPOS interface
Issue 02 (2011-08-12)
24
6 Link Features
SDH/SONENT encapsulation
ATM interfaces on the NE40E support SONET/SDH encapsulation and the SONET/SDH
overhead configuration and physical layer alarms.
IPoA
The NE40E supports the following modes in setting up the mapping between a PVC and
the IP address of the peer device:
Static mapping
Inverse Address Resolution Protocol (InARP)
IPoEoA access
ATM sub-interfaces
1483B
1483B supported by the NE40E is applicable to IPoEoA. IPoEoA indicates that Ethernet
packets are carried over AAL5 and IP packets are carried over the Ethernet. This
implements Layer 2 forwarding of IPoEoA packets between the Ethernet and PVC. By
converging the ATM backbone network and the IP network, IPoEoA supports various
Ethernet and IP services.
Issue 02 (2011-08-12)
25
6 Link Features
Line clocks
Cell relay and IWF on different sub-interfaces of the same ATM interface
PVC
FR address mapping
FR sub-interfaces
The NE40E supports sub-interfaces on 10G POS interfaces and inter-AS VPN Option A.
Issue 02 (2011-08-12)
26
7 Service Features
Service Features
Issue 02 (2011-08-12)
27
7 Service Features
Default VLAN
VLAN trunk
VLANIF interfaces
VLAN aggregation
Ethernet sub-interfaces
VLAN mapping
VLAN stacking
IPv4
IPv6
MPLS
Multicast
VLAN sub-interfaces
QoS
Ethernet sub-interfaces
Identification of double VLAN tags (inner VLAN tag and outer VLAN tag)
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
28
7 Service Features
Removal of double VLAN tags and then addition of new double VLAN tags
Change of the EtherType value and 802.1p priority in the outer VLAN tag; copy of the
802.1p priority in the inner VLAN tag to the outer VLAN tag of double-tagged packets
Traffic classification based on the 802.1p priorities in the outer VLAN tags of packets
Rate limit on interfaces based on the 802.1p priorities in both inner and outer VLAN tags
Interface-based QinQ
Interface-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
VLAN-based QinQ
QinQ termination
EType in the outer tag of QinQ packets used for interoperation with devices of other vendors
Multicast QinQ
Translation sub-interface supporting 1to1, 1to2, 2to1, 2to2 VLAN tag translation
Sub-interface for QinQ VLAN tag termination supporting VLAN tag swapping
Sub-interface for dot1q VLAN tag termination, sub-interface for QinQ VLAN tag
termination, QinQ stacking sub-interface, and translation sub-interface supporting the
block action
Sub-interfaces for QinQ VLAN tag termination accessing a VPLS network in symmetrical
mode supporting HQoS
Sub-interface for QinQ VLAN tag termination and sub-interface for dot1q VLAN tag
termination supporting IPv6 routing protocols
Sub-interface for QinQ VLAN tag termination and sub-interface for dot1q VLAN tag
termination supporting BFDv6
Sub-interface for QinQ VLAN tag termination and sub-interface for dot1q VLAN tag
termination supporting VRRPv6
29
7 Service Features
tag is used for multiple services. In this case, the access device may add service access
information to the 802.1p or DSCP field. Then, the NE40E connected to the access device needs
to use the 802.1p or DSCP value to identify access users. This helps configure the accesses to
different VPNs and set up different QoS scheduling policies.
Polling mechanism
Mechanism of checking the channel status of the sub-ring protocol packets on the major
ring
RSTP
MSTP
MSTP provides BPDU protection to defend against such attacks. After the BPDU protection is
enabled, the switch shuts down the edge port that receives BPDUs. At the same time, the switch
informs 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 DHCP
through CP-CAR. This avoids influencing device performance.
7.2 IP Features
7.2.1 IPv4/IPv6 Dual Stack
The IPv4/IPv6 dual stack can be easily implemented and can smoothly interoperate with other
protocols. Figure 7-1 shows the structure of the IPv4/IPv6 dual stack.
Issue 02 (2011-08-12)
30
7 Service Features
TCP
UDP
IPv4
IPv6
Link Layer
IPv4/IPv6 dual stack (including dual-stack VPN) is supported on the same interface.
TCP/IP protocol suite, including ICMP, IP, TCP, UDP, socket (TCP/UDP/Raw IP), and
ARP
IP policy-based routing (PBR) and flow-based next hop to which packets are forwarded
Issue 02 (2011-08-12)
31
IPv6 PBR
7 Service Features
7.2.4 GRE
Generic Routing Encapsulation (GRE) is applicable to the following:
l
When applying a GRE tunnel, ensure that the NE40E is installed with a GRE license file and an
SPUC, and the service mode of the SPUC is set to tunnel. GRE tunnels are independent of
physical interfaces.
7.2.6 IPSEC
The NE40E supports the following functions:
l
NAT Traversal
VPN IPSec
Pre-share-key
Issue 02 (2011-08-12)
32
7 Service Features
IPv6 routing protocols, including Routing Information Protocol Next Generation (RIPng),
OSPFv3, IS-ISv6, and BGP4+
Static routes that are manually configured by the administrator to simplify network
configurations and improve network performance
Use of routing policies in advertising and receiving routes and filtering of routes through
route attributes
Support for load balancing and configuring the maximum number of equal-cost routes 32channel load balancing of IPv6 routes on the LPUF-10/LPUF-21/LPUF-40/LPUF-41
Advertisement of a default route from a RIP-enabled device to its peers and setting of the
metric of this route
RIP-triggered updates
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)
OSPF PRC
l
Issue 02 (2011-08-12)
33
7 Service Features
IS-IS GR, OSPF GR and BGP GR, which ensure high reliability with Non-Stop Forwarding
(NSF)
Policy-based route selection by BGP when there are multiple routes to the same destination
BGP route reflector (RR), which addresses the problem of high costs of full-mesh
requirement when there are many IBGP peers
Route dampening, which suppresses unstable routes (unstable routes are neither added to
the BGP routing table nor advertised to other BGP peers)
Routing protocol
The formula for calculating the bandwidth occupies by LSAs on interfaces in the same area is
as follows:
Assume that there are 10000 routes, Ethernet interfaces are used, and the MTU of the Ethernet
interfaces is 1500 bytes. In this case, the Ethernet frame header is of 18 bytes, and each LSA is
of 44 bytes. Each LSA carries information about a route.
(1500-18)/44=44. The preceding formula indicates that an Ethernet frame can carry information
about 33 routes. In this case, 228 Ethernet frames are required to carry information about 10000
routes.
Multicast protocols
Multicast protocols include the Internet Group Management Protocol (IGMP) ( IGMPv1,
IGMPv2 and IGMPv3), Protocol Independent Multicast-Dense Mode (PIM-DM), Protocol
Independent Multicast-Sparse Mode (PIM-SM), Multicast Source Discovery Protocol
(MSDP), and Multi-protocol Border Gateway Protocol (MBGP).
PIM-SSM
Anycast RP
Issue 02 (2011-08-12)
34
7 Service Features
MLD
Multicast Listener Discovery (MLD) has the following versions:
MLDv1 defined in RFC 2710
MLDv1 supports Any-Source Multicast (ASM) directly and supports Source-Specific
Multicast (SSM) together with SSM mapping.
MLDv2 defined in RFC 3810
MLDv2 supports ASM and SSM directly.
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 packets
based on the routing policy when IP multicast packets are forwarded
Multicast VPN
The multicast domain (MD) scheme is used to implement this function.
Filtering of PIM neighbors, control of the forwarding boundary, and control of the BSR
service and management boundary
MSDP authentication
Prompt leave of IGMP and MLD group members and the use of group-policies to restrict
the setup of forwarding entries
Multicast group-based, multicast source-based, multicast source/group-based, stablepreferred, and balance-preferred load splitting
IGMP snooping
The NE40E supports IGMP snooping on Layer 2 interfaces, Layer 3 interfaces, QinQ
interfaces, STP topologies, RRPP rings, and VPLS PWs.
Distributed multicast
Maximum delay of less than 4 ms for multicast fast join and fast leave
Issue 02 (2011-08-12)
35
7 Service Features
Multicast VLAN
The NE40E supports multicast VLAN and VLAN-based 1+1 protection of multicast traffic.
Multicast VPN
For details, see section "7.5 VPN Features".
Multicast CAC
The NE40E supports multicast Call Admission Control (CAC). When multicast CAC rules
are configured, the number of multicast groups and bandwidth are restricted for IGMP
snooping on interfaces or the entire system.
7.4 MPLS
The NE40E supports MPLS features, and static and dynamic LSPs. Static LSPs require that the
administrator configure the Label Switch Routers (LSRs) along the LSPs and set up LSPs
manually. Dynamic LSPs are set up dynamically in accordance with the routing information
through the Label Distribution Protocol (LDP) and RSVP-TE.
The delay for MPLS packets can be controlled in the following aspects:
l
In the case that there is no traffic congestion, the NE40E adopts a high-speed processor to
ensure line-rate forwarding and low delay.
In the case of traffic congestion, the NE40E ensures preferential forwarding and low delay
for traffic with high priority through mechanisms such as QoS, HQoS, MPLS TE, and DSTE.
LDP
Downstream Unsolicited (DU) and Downstream on Demand (DoD) label advertisement
modes
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 sessions
MPLS ping and tracert and detection of the availability of an LSP through the exchange of
MPLS Echo Request packets and MPLS Echo Reply packets
LSP bandwidth alarm function and LSP-based traffic statistics function that is used to
calculate bandwidth usage
Configuration of 32-channel or 64-channel load balancing (on the ingress and transit nodes)
that is controlled by the PAF file, with 64-channel load balancing applicable to IP
Issue 02 (2011-08-12)
36
7 Service Features
forwarding, IP packet forwarding over LDP LSPs (including L3VPN), and packet
forwarding on P nodes
l
MPLS QoS, mapping from the ToS field in IP packets to the EXP field in MPLS packets,
and MPLS uniform, pipe, and short pipe modes
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 faults
Establishment of LSPs between NE40Es of different IS-IS levels and between the
NE40E and non-Huawei devices through LDP
MPLS TE
The MPLS TE technology combines the MPLS technology with traffic engineering. It can
reserve resources by setting up LSP tunnels for a specified path in an attempt to avoid network
congestion and balance network traffic.
In the case of resource scarcity, MPLS TE allows the preemption of bandwidth resources of
LSPs with low priorities. This meets the demands of important services or the LSPs with large
bandwidth. When an LSP fails or a node is congested, MPLS TE can ensure smooth network
communication through the backup path and the fast reroute (FRR) function. Through automatic
re-optimization and bandwidth adjustment, MPLS TE improves the self-adaptation capability
of tunnels and properly allocates network resources.
The process of updating the network topology through the TEDB is as follows: When a link
goes Down, the CSPF failed link timer is enabled. If the IGP route is deleted or the link is changed
within the timeout period of the CSPF failed link timer, CSPF deletes the timer and then updates
the TEDB. If the IGP route is not deleted or the link is not changed after the timeout period of
the CSPF failed link timer expires, the link is considered Up.
MPLS TE provides the following functions:
Issue 02 (2011-08-12)
37
7 Service Features
Processing of Constrained Route-Label Switched Path (CR-LSP) of various types and route
calculation through the CSPF algorithm
RSVP-TE
RSVP authentication complies with RFC 3097.
Auto routing
Auto 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.
Auto FRR
Auto FRR is an extension to MPLS TE FRR. You can create a bypass tunnel that meets
the requirement on the LSP by configuring the attributes of the bypass tunnel, global auto
FRR, and auto FRR on the interface of the primary tunnel. With the change of the primary
tunnel, the previous bypass tunnel is deleted automatically. Then, a new bypass tunnel that
meets the requirement is set up.
Backup CR-LSP
The 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 backup
CR-LSP.
Ordinary backup
A backup CR-LSP is set up when the primary CR-LSP fails.
LDP over TE
In existing networks, not all devices support MPLS TE. It is possible that only the devices
at the network core support TE and the devices at the network edge use LDP. The
application of LDP over TE is therefore put forward. With LDP over TE, the TE tunnel is
considered as a hop of the entire LDP LSP. Through forwarding adjacency, one MPLE TE
tunnel can be considered as a virtual link and advertised to an IGP network.
Make-before-break
Make-before-break is a technology for ensuring highly reliable CR-LSP switchover. The
original path is not deleted until a new path has been created. Before a new CR-LSP is
created, the original CR-LSP is not deleted. After a new CR-LSP has been created, the
traffic is switched to the new CR-LSP first, and then the original CR-LSP is deleted. This
ensures non-stop traffic forwarding.
DS-TE
DS-TE implemented on the NE40E supports the Non-IETF mode and the IETF mode.
Issue 02 (2011-08-12)
38
7 Service Features
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 here
refers 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 traffic
statistics collection.
MPLS OAM
MPLS OAM functions are as follows:
l
Protection switching
LSPs
GRE tunnels
TE tunnels
Issue 02 (2011-08-12)
39
7 Service Features
VLL
The NE40E supports the following VLL functions:
l
Martini VLL
The Martini mode supports double labels. The inner label adopts extended LDP for
signaling 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.
Kompella VLL
VC encapsulation types of Kompella VLL include ATM-1to1-VCC, ATM-1to1-VPC,
ATM-AAL5-SDU, ATM-nto1-VCC, ATM-nto1-VPC, ATM-trans-cell, FR, Ethernet,
HDLC, 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.
CCC VLL
CCC VLL supports the local inter-board switching of packets in 802.1Q mode
SVC VLL
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.
VPLS
In a VPLS network, PEs can be all connected to each other and enabled with split horizon to
prevent Layer 2 loops.
Issue 02 (2011-08-12)
40
7 Service Features
The implementations of VPLS control plane through BGP and LDP are called Kompella VPLS
and Martini VPLS respectively.
l
Kompella VPLS
Kompella 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.
Martini VPLS
Martini VPLS has poor scalability. With Martini VPLS, LDP is adopted for signaling, and
the peers of a PE need to be manually specified. PEs in a VPLS network are all connected
to each other. Therefore, adding a new PE requires configurations on all the other associated
PEs to be modified.A pseudo wire (PW) is actually a point-to-point link. This means that
using LDP to create, maintain, and delete the PW is more effective.
HVPLS
mVPLS
STP over PW
PWE3
The NE40E supports the following PWE3 functions:
l
PW template
The NE40E supports the binding between a PW and a PW template, and the reset of PWs.
The NE40E supports heterogeneous interworking.
Issue 02 (2011-08-12)
41
7 Service Features
Currently, the NE40E supports the transparent transmission of the following packets
through PWE3: ATM AAL5 SDU VCC transport, Ethernet, HDLC, ATM n-to-one VCC
cell transport, IP Layer 2 transport, and ATM one-to-one VCC cell mode.
l
PW redundancy
ATM IWF
ATM IWF runs on an L2VPN in CCC local connection mode or an L2VPN in PW mode.
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 Packet
Switched Network (CESoPSN) and Structure-Agnostic TDM over Packet (SAToP)
service.
Carrier's carrier
Inter-AS VPN
The 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 Backbones
Option B
In Option B, ASBRs advertise labeled VPN-IPv4 routes to each other through MPEBGP.
Multihop EBGP redistribution of labeled VPN-IPv4 routes, also called Inter-Provider
Backbones Option C
In Option C, PEs advertise labeled VPN-IPv4 routes to each other through Multihop
MP-EBGP.
Multicast VPN
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
Issue 02 (2011-08-12)
HoVPN
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
42
Multi-role host
7 Service Features
7.6 QoS
On the NE40E, you can collect traffic statistics on the packets on which QoS is performed and
view 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 processed
based on the same Per-Hop Behavior (PHB). This simplifies the processing and storage of
services.
On the Diff-Serv core network, packet-specific QoS is provided. Therefore, signaling processing
is not required.
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, fragmentation
flag, TCP SYN flag, TCP/UDP source port number or port range, and TCP/UDP destination
port number or port rang of IPv4 packets
Traffic Policing
CAR is mainly used for rate limit. In the implementation of CAR, a token bucket is used to
measure the data flows that pass through the interfaces on a router so that only the packets
assigned with tokens can go through the router in the specified time period. In this manner, the
rates of both incoming and outgoing traffic are controlled. In addition, the rate of certain types
of 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 specified
conditions, 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 network
process data properly. The NE40E supports CAR for both incoming and outgoing traffic.
Issue 02 (2011-08-12)
43
7 Service Features
Queue Scheduling
The 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, and
bottom PQs. They are ordered in descending order of priorities. When packets leave queues, PQ
allows the packets in the top PQ to go first. Packets in the top PQ are sent as long as there are
packets in this PQ. The NE40E sends packets in the middle PQ only when all packets in the top
PQ are sent. Similarly, the NE40E sends packets in the normal PQ only when all packets in the
middle PQ are sent; the NE40E sends packets in the bottom PQ only when all packets in the
normal PQ are sent. As a result, the packets in the PQ of a higher priority are always sent
preferentially, which ensures that packets of key services are processed preferentially when the
network is congested. Packets of common services are processed when the network is idle. In
this manner, the quality of key services is guaranteed, and the network resources are fully
utilized.
Weight Fair Queuing (hereinafter referred to as WFQ) is a complex queuing process, which
ensures that the services with the same priority are fairly treated and the services with different
priorities are weighted. The number of WFQ queues can be pre-set and is allowed to range from
16 to 4096. WFQ weights services based on their requirements for the bandwidth and delay. The
weights are determined by the IP precedence in the IP packet headers. With WFQ, the NE40E
implements dynamic traffic classification based on quintuples or ToS values. The packets with
the same quintuple (source IP address, destination IP address, source port number, destination
port number, and protocol number) or ToS value belong to the same flow. Packets in one flow
are placed in one queue through the Hash algorithm. When flows enter queues, WFQ
automatically places different flows into different queues based on the Hash algorithm. When
flows leave queues, WFQ allocates bandwidths to flows on the outbound interface based on
different IP precedence of the flows. The smaller the precedence value of a flow, the smaller the
bandwidth of the flow. In this manner, services of the same precedence are treated fairly; services
of different precedence are treated based on their weights.
Congestion Avoidance
Congestion avoidance is a traffic control mechanism used to avoid network overload by adjusting
network 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 congestion
intensifies.
Random Early Detection (RED) or Weighted Random Early Detection (WRED) algorithms are
frequently used in congestion avoidance.
The RED algorithm sets the upper and lower limits for each queue and specifies the following
rules:
l
When the length of a queue is below the lower limit, no packet is discarded.
When the length of a queue exceeds the upper limit, all the incoming packets are discarded.
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 random
number is compared with the drop probability of the current queue. The packet is discarded
when the random number is larger than the drop probability. The longer the queue, the
higher the drop probability. The drop probability, however, has an upper limit.
Issue 02 (2011-08-12)
44
7 Service Features
Unlike RED, the random number in WRED is based on the IP precedence of IP packets. WRED
keeps 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 an
interface. The WRED template is applied in the outbound direction; the default scheduling policy
in the system is applied in the inbound direction. In addition, WRED can be applied to the
Multicast Tunnel interface (MTI) that is bound to the distributed multicast VPN on the
NE40E.
The NE40E supports congestion avoidance based on services. The NE40E reserves on each
interface eight service queues, that is, BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The
NE40E colors packets with red, yellow, and green to identify the priorities of packets and discard
certain packets.
HQoS
The NE40E supports the following HQoS functions:
l
Sets parameters such as the maximum queue length, WRED, low delay, SP/WRR, CBS,
PBS, and statistics function for each queue.
Sets parameters such as the CIR, PIR, number of queues, and algorithm for scheduling
queues for each user.
Provides the traffic statistics function. Users can learn the bandwidth usage of services and
properly distribute the bandwidth by analyzing traffic.
QPPB
QPPB 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 on
the attributes of the route.
Classifies traffic according to QoS parameters and sets the QoS policy for the classified
traffic.
Forwards packets according to the locally configured QoS policies to propagate QoS
policies through BGP.
The receiver of BGP routes can set QoS parameters (IP precedence and associated traffic
behavior) based on the following attributes:
l
ACL
IP prefix list
Issue 02 (2011-08-12)
45
7 Service Features
ATM QoS
The NE40E supports the following ATM QoS functions:
l
Issue 02 (2011-08-12)
46
7 Service Features
MPLS HQoS
MPLS QoS is a complete L2VPN/L3VPN QoS solution. It resorts to various QoS techniques to
meet the diversified and delicate QoS demands of VPN users. MPLS QoS provides relative QoS
on the MPLS Diff-Serv network and end-to-end QoS on the MPLE TE network. In actual
applications, the following QoS policies are supported.
l
The NE40E can balance traffic between physical interfaces or between physical interfaces and
logical interfaces. In addition, the NE40E can detect the changes of logical interface bandwidth
Issue 02 (2011-08-12)
47
7 Service Features
due to manual configuration of new member links or the status changes of member links. When
the bandwidth of a logical interface changes, traffic is automatically load-balanced based on the
new bandwidth proportion.
Provides reference data for carriers to deploy and maintain Diff-Serv TE.
In traffic classification, the system can collect statistics on the traffic that matches rules
and fails to match rules.
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 applied
to different interfaces.
Statistics on the number of forwarding packets, bytes, and discarded packets of a user queue
which includes eight flow queues of different priorities
Statistics on the number of forwarded packets, bytes, and discarded packets of a user group
queue
Issue 02 (2011-08-12)
48
7 Service Features
Statistics on the number of forwarded packets, bytes, and discarded packets of eight queues
of different priorities on an interface
Users that access the network through interfaces including logical interfaces
Multi-role hosts
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.
7.9 MSE
IPv4-Based IPoX User Access
The NE40E supports the following IPv4-based IPoX user access functions:
l
IP over Ethernet over VLAN (IPoEoVLAN) and IP over Ethernet over QinQ (IPoEoQ)
ARP trigger, IP trigger, and DHCP trigger, which indicate the modes for triggering user
access by sending ARP packets, IP packets, and DHCP packets respectively
Issue 02 (2011-08-12)
49
Static users
Captive portal
7 Service Features
AAA
The NE40E supports the following Authentication, Authorization, and Accounting (AAA)
functions:
l
Domain management
Local billing
RADIUS
The NE40E supports flexible RADIUS/RADIUS+ authentication, authorization, and
accounting.
Address Management
The NE40E supports the following address management functions:
l
IPv4 address pool management through the DHCP server, DHCP relay agent, and DHCP
proxy
Reliability
The NE40E supports the following reliability functions:
l
User access through a trunk interface whose member interfaces reside on the same LPU
User Security
The NE40E supports the following user security functions:
l
7.10 iVSE
The NE40E supports the following iVSE functions:
Issue 02 (2011-08-12)
50
7 Service Features
Fast channel change (FCC) and retransmission (RET) of BTV programs on L3/L3VPN/
VPLS networks
Video Quality of Experience (VQE), including Media Delivery Index (MDI) and V-MOS
2.0
Distributed MDI quality monitoring of BTV and VOD programs on the LPUF-21/
LPUF-40/LPUF-41 on L3/L3VPN/L2VPN networks
Distributed VMOS2.0 quality monitoring of BTV and VOD programs on the LPUF-41 on
L3/L3VPN/L2VPN networks
AAA
Plain text authentication and MD5 encrypted text authentication supported by routing
protocols that include RIPv2, OSPF, IS-IS, and BGP
URPF
The NE40E supports URPF for IPv4/IPv6 traffic.
Issue 02 (2011-08-12)
51
7 Service Features
MAC entries in a MAC address table are classified into three types:
l
Dynamic entries
Dynamic entries are learnt by interfaces and stored in hardware of LPUs. Dynamic entries
age. Dynamic entries will be lost in the case of the system reset, LPU hot swap, or LPU
reset.
Static entries
Static entries are configured by users and delivered to LPUs. Static entries do not age. After
static entries are configured and saved, they are not lost in the case of the system reset, LPU
hot swap, or LPU reset.
Blackhole entries
Blackhole entries are used to filter out the data frames that contain specific destination
MAC addresses. Blackhole entries are configured by users and delivered to LPUs.
Blackhole entries do not age. After blackhole entries are configured and saved, they will
not be lost in the case of the system reset, LPU hot swap, or LPU reset.
In this manner, the network bandwidth is reasonably used and the network security is guaranteed.
IGMP Snooping
The NE40E supports IGMP snooping on Layer 2 interfaces, Layer 3 interfaces, QinQ interfaces,
STP topologies, RRPP rings, and VPLS PWs.
DHCP Snooping
DHCP snooping is mainly used to prevent DHCP Denial of Service (DoS) attacks, bogus DHCP
server attacks, ARP middleman attacks, and IP/MAC spoofing attacks when DHCP is enabled
on the NE40E.
The working mode of DHCP snooping varies with the attack type, as shown in Table 7-1.
Issue 02 (2011-08-12)
52
7 Service Features
Trusted/untrusted
Whitelist
Blacklist
User-defined flow
Local URPF
Issue 02 (2011-08-12)
53
7 Service Features
The NE40E provides defense measures against attacks by sending the following types of
packets on TCP/IP networks:
Malformed packets
Null IGMP packets, packets with invalid TCP flag bits, LAND attack packets, IP packets
whose payloads are null, and smurf attack packets.
Fragmented packets
Packets 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
GTSM
On the current network, attackers forge valid packets to attack routers, which overloads the
routers and consumes limited resources such as the CPU on the MPU. For example, an attacker
forges BGP protocol packets and continuously sends them to a router. After the LPU of the
router receives the packets, it finds that the packets are destined to itself and then sends the
packets directly to the BGP processing module on the MPU without checking the validity of the
packets. As a result, the system is abnormally busy processing these forged valid packets and
the CPU usage is high.
To guard against the preceding attacks, the NE40E provides the Generalized TTL Security
Mechanism (GTSM). The GTSM protects services above the IP layer by checking whether the
TTL value in the IP header is within a specified range. In actual applications, the GTSM is mainly
used to protect the TCP/IP-based control plane such as the routing protocol against attacks of
the CPU-utilization type such as CPU overload.
The NE40E supports BGP GTSM, OSPF GTSM, and LDP GTSM.
Issue 02 (2011-08-12)
54
7 Service Features
The system checks whether the destination IP address of the ARP packet received on the
interface is correct. If the destination IP address is correct, the packet is sent to the CPU;
otherwise, the packet is discarded.
l
Local Mirroring
In local mirroring, an LPU can be configured with a physical observing port, multiple logical
observing ports, and multiple mirrored ports.
Local mirroring can be inter-LPU mirroring, which means that the observing port and mirrored
port reside on different LPUs.
Remote Mirroring
The NE40E provides MPLS LSPs, MPLS TE tunnels, and GRE 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.
Netstream
NetStream provides the following functions:
l
Accounting
Network monitoring
NetStream involves three devices: the NetStream Data Exporter (NDE), the NetStream Collector
(NSC), and the NetStream Data Analyzer (NDA).
The NE40E functions as an NDE to sample packets and aggregate and output flows. NetStream
on the NE40E is classified into distributed NetStream and integrated NetStream based on where
to collect packets and process flows.
l
Distributed NetStream
Certain LPUs can sample packets and aggregate and output flows by themselves.
Issue 02 (2011-08-12)
55
7 Service Features
Integrated NetStream
Certain LPUs do not process flows. They only sample packets and send the sampled packets
to the NetStream SPU for integrated flow aggregation and output.Integrated NetStream
supports load balancing among multiple NetStream boards.
Sampling of the IPv4 unicast/multicast packets, fragmented packets, MPLS packets, MPLS
L3VPN packets, and L2VPN VLL packets
Regular packet sampling, random packet sampling, sampling at regular time, and sampling
at random time
Sampling on various types of physical and logical interfaces such as POS interfaces,
Ethernet interfaces, VLAN sub-interfaces, serial/MP/FR PVC/FR MP interfaces
channelized from CPOS interfaces, ATM interfaces, FR interfaces, trunk interfaces,
VLANIF interfaces, and GRE interfaces
The NE40E provides the following functions in terms of aggregation and output:
l
IPv4 packets can be aggregated based on the AS number, AS-ToS, protocol-port, protocolport-ToS, source-prefix, source-prefix-ToS, destination-prefix, destination-prefix-ToS,
prefix, prefix-ToS, and VLAN ID.
The generated statistics can be output in v5, v8, or v9 format with 16-bit or 32-bit AS
numbers, which can be set through commands. When packets are output in the v9 format,
both the 16-bit and 32-bit interface indexes are supported, and can be set through commands
as required.
Each type of aggregated flows can be output to two NMS servers if configured.
Lawful Interception
Lawful interception indicates that law enforcement agencies lawfully intercept user information
after being authorized.
Lawful interception on the NE40E is used to listen to the devices on operators' networks. The
NE40E provides X1 and X3 interfaces that are connected to the signaling and data interfaces
respectively on Lawful Interception Gateways (LIGs). The X3 interfaces on the NE40E can be
connected to a maximum of 10 LIGs.
SSHv2
The NE40E supports the STelnet client and server and the SFTP client and server. Both support
SSH 1.5 and SSH 2.0.
Issue 02 (2011-08-12)
56
7 Service Features
The plug-and-play function only can be configured on the X3 models of the NE40E.
Plug-and-Play (PNP) enables new devices to be automatically identified by the NMS and be
commissioned 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 growth
of profits. To address this issue, Huawei puts forward the PNP solution.
The PNP feature effectively reduces the on-site software commissioning time, frees engineers
from working in bad outdoor environments, and greatly speeds up the project process and
improves project quality.
Y.1731
Y.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
MPLS-TP OAM
MPLS-TP OAM supports the following functions:
l
LoopBack (LB)
Single-ended frame loss statistics collection and two-ended frame loss statistics collection
APS 1:1
NSR OSPF
NSR LDP
NSR RSVP-TE
Issue 02 (2011-08-12)
57
NSR PIM
NSR PPP
NSR ARP
NSR LACP
ISIS/ISIS6 NSR
BGP/BGP4+ NSR
7 Service Features
APS
The NE40E supports the following Automatic Protection Switching (APS) functions:
l
Interface-based APS
Addition of the working and protect interfaces of an APS group to a trunk so that all services
are configured on the trunk
FRR
The NE40E provides multiple fast reroute (FRR) features. You can deploy FRR as required to
improve network reliability.
l
IP FRR
FRR switching can be complete in 50 ms. In this manner, the data loss caused by network
failures is minimized to a great extend.
FRR supported by the NE40E enables the system to monitor and save the status of LPUs
and 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 preset route, thus reducing time between failures and the packet loss ratio.
LDP FRR
LDP FRR switching can be complete in 50 ms.
Hybrid FRR
Hybrid FRR is a combination of IP FRR and VPN FRR of IP routes and VPN routes in a
same VPN instance.
On a bearer network where a CE is dual-homed to two PEs, IP FRR is deployed between
the CE and each PE. If there are multiple voice VPNs and the two PEs are connected through
a POS link, you cannot bind sub-interfaces to different VPN instances to provide a backup
link for the traffic, because the NE40E does not support POS sub-interfaces.
Issue 02 (2011-08-12)
58
7 Service Features
In this case, a BGP VPNv4 peer relationship can be set up between the two PEs. Therefore,
the backup path, in the form of a private route, is exchanged between the two PEs. The
VPNv4 route then functions as a backup of the IP routes between the CE and each PE. This
implements FRR and switches traffic within 50 ms.
l
TE FRR
TE FRR is an MPLS TE technology used to protect local networks. Only the interfaces
with a transmission rate of over 100 Mbit/s support TE FRR. TE FRR switching can be
complete 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 a
new LSP is established, traffic is switched back to the original protected LSP or the newly
established LSP.
When a link or a node on the LSP fails, traffic is switched to the protection link and the
ingress node of the LSP attempts to establish a new LSP, if an LSP is configured with TE
FRR.
With different protected objects, TE FRR is classified into the following types:
Link protection
Node protection
Auto FRR
Auto FRR is an extension of MPLS TE FRR. It automatically creates a bypass tunnel that
meets the requirements for the LSP through the configuration of the attributes of the bypass
tunnel, global auto FRR attributes, and interface-based auto FRR attributes on the interface
of the primary tunnel. When the primary tunnel changes to another path, the previous bypass
tunnel is automatically deleted. Then, a bypass tunnel that meets the requirements is set up.
VLL FRR
VLL FRR switching can be complete in 50 ms.
VPN FRR
VPN FRR switching can be complete in 50 ms.
The NE40E-X16 has two MPUs that work in 1:1 backup mode.
The NE40E-X16 has four SFUs that work in 3+1 backup mode. When one SFU becomes
faulty, the other three are responsible for data switching on the device. Traffic switching
on SFUs does not cause LPUs to be reset, or trigger the re-calculation of routes.
The NE40E-X16 has eight PEMs on the back, working in 4+4 backup mode.
NE40E-X16 has four fan modules. Each fan module contains a fan. The NE40E-X16 has
two heat dissipation areas. Each heat dissipation area has two fan modules working in 1+1
backup mode. If one of the fan modules becomes faulty and the ambient temperature is
below 40C, the system can still work properly in a short period.
The NE40E-X8 has two SRUs that work in 1:1 backup mode.
The NE40E-X8 has three SFUs working in 2+1 backup mode. Two of the SFUs are
integrated on two SRUs. When one SFU becomes faulty, the other two are responsible for
Issue 02 (2011-08-12)
59
7 Service Features
data switching on the device. Traffic switching on SFUs does not cause LPUs to be reset,
or trigger the re-calculation of routes.
l
The NE40E-X8 has four PEMs on the back, working in 2+2 backup mode.
NE40E-X8 has two fan modules. Each fan module contains a fan. The fan modules work
in 1+1 backup mode. When one module becomes faulty and the ambient temperature is
below 40C, the system can still work properly in a short period.
The NE40E-X3 has two MPUs that work in 1:1 backup mode.
The NE40E can be equipped with one MPU/SRU or two MPUs/SRUs. The MPUs support hot
backup. If the device is configured with two MPUs/SRUs, the master MPU/SRU works and the
slave MPU/SRU is in the standby state. The management network interface on the slave MPU/
SRU cannot be accessed by users, and the console and AUX interfaces cannot be configured
with any command. The slave MPU/SRU exchanges information (including heartbeat messages
and backup data) with only the master MPU/SRU.
The system supports two types of master/slave switchover of MPUs/SRUs: failover and
switchover. The failover is triggered by serious faults in the master MPU/SRU or the reset of
the master MPU/SRU. The switchover is triggered by commands that are run on the console
interface. You can also forbid the master/slave switchover of the MPUs/SRUs 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 system diagnosis information base for users to analyze.
The system provides two clock boards in master/slave backup mode. If the system detects that
the master clock board becomes faulty or is reset through a command, the system automatically
performs the master/slave switchover of clock boards. The master/slave switchover of clock
boards does not result in phase offsets or interrupt services.
The master/slave switchover time of each key part is less than 100 us.
Supports VRRP on Ethernet interfaces. With extended VRRP, two interfaces located on a
same NE40E or two NE40Es can back up each other. This ensures high reliability of the
interfaces.
Through extended protocols, the NE40E backs up key service interfaces. In this manner, core
routers 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 backup
interface needs to be changed and services recover rapidly.
Issue 02 (2011-08-12)
60
7 Service Features
Customizes alarms. This can specify the alarms that can cause the change of the interface
status.
Suppresses alarms. This can filter out the burr and prevent the network from frequently
flapping.
61
7 Service Features
By using performance management tools, the ISP can monitor the network status in real time
through the NMS. The ISP then check whether the forwarding capacity of the network complies
with the Service Level Agreement (SLA) signed with users and locate faults. The ISP does not
need to carry out detection on the user side, which greatly decreases maintenance costs.
VRRP
VRRP dynamically associates the virtual router with a physical router that carries services. When
the physical router fails, another router is elected to take over services. Failover is transparent
to users and thus the internal network and the external network can communicate without
interruption.
The NE40E supports the following VRRP functions:
l
mVRRP
VGMP
E-VRRP
GR
Graceful 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 by
faults. GR neither deletes the routing information from the routing table or the FIB nor resets
the board during the switchover when faults occur. This prevents the service interruption of the
entire system.
The NE40E supports system-level GR and protocol-level GR. Protocol-based GR includes:
l
BGP GR
OSPF GR
IS-IS GR
MPLS LDP GR
Martini VLL GR
Martini VPLS GR
L3VPN GR
RSVP GR
PIM GR
BFD
BFD is a detection mechanism used uniformly in an entire network. It is used to rapidly detect
and 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 both
directions. The defect detection is implemented at the millisecond level. The NE40E supports
single-hop BFD and multi-hop BFD.
BFD of the NE40E supports the following applications.
l
Issue 02 (2011-08-12)
62
7 Service Features
The system uses BFD to detect and monitor the connectivity of links or IP routes in a
network. The rapid VRRP switchover is thus triggered.
l
Multi-hop BFD
7.14 Clock
The NE40E supports the following clock features:
l
CES ACR
CES DCR
The Ethernet interfaces on the LPUF-10 and LPUF-21 of the NE40E provide Ethernet clock
synchronization so that the clock quality and stratum of the network can be guaranteed.
1588v2
Issue 02 (2011-08-12)
63
7 Service Features
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 networking
and 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.
Issue 02 (2011-08-12)
64
7 Service Features
Access authority
The NE40E provides four levels of access control. After receiving an NTP access
request packet, the NE40E matches it from the lowest access control level to the highest
access control level. The first successfully matched access control level takes effect.
The matching order is as follows:
peer: indicates the minimum access control. The remote end can send a time request
and a control query to the local end. The local clock can also be synchronized with the
clock of the remote server.
server: indicates that the remote end can send a time request and a control query to the
local end. The local clock, however, is not synchronized with the clock of the remote
server.
synchronization: indicates that the remote end can only send a time request to the local
end.
query: indicates the maximum access control. The remote end can only send a control
query to the local end.
l
Authentication
When 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 be
configured and declared reliable.
The server and the client must be configured with the same key.
Internal clock
The NE40E provides an internal clock and can extract clock information from LPUs. The
clock precision reaches 4.6 ppm, that is, 0.00002s.
Issue 02 (2011-08-12)
65
8 Applicable Environment
Applicable Environment
Issue 02 (2011-08-12)
66
8 Applicable Environment
CR
NE5000E
BR
NE80E
SoftX3000
AR
NE40E
SoftX3000
UMG8900
CR:Core Router
Directed at the condition of the existing bearer network and oriented at the NGN bearer network
and the 3G services, it is necessary for carriers to set up a core bearer network to carry NGN
multi-services. In the new market competition environment, with the development of new
services and technologies, the newly built bearer network will become the next-generation multiservice bearer platform that supports voice, data, and video transmission. Specifically, the newly
built bearer network will carry NGN, video conference, video phone, streaming media, enterprise
interconnection, and 3G services. It will bring about the milestone of network transformation
and network convergence for carriers.
In this solution, the NE5000E acts as the core router to forward data at a high speed and ensure
high reliability; the NE80E/40E acts as the convergence router to converge NGN voice,
signaling, NMS, and customer services.
This application has the following characteristics:
l
The core layer uses double planes. The NE5000Es are fully meshed.
MPLS VPN is uniformly planned, which implements user isolation and service isolation.
Issue 02 (2011-08-12)
67
8 Applicable Environment
High reliability technologies such as TE FRR, GR, BFD for VRRP, and IGP fast
convergence are used on the network.
NMS
Dynamic IP+MAC+VLAN
binding, strict URPF,
ensuring access security
Core bearer
network
BAS
ES
NE80E
/NE40E
QinQ, 4K x 4K VLANs,
isolated unicast services,
secure access
Convergence
switch
Multicast replication on
the edge, ensuring high
efficiency and
controllable multicast
DSLAM
Multicast switch,
saving reconstruction
expense
Multicast switch
End switch
Home
gateway
TV
Home
gateway
PC
TV
PC
The IPTV bearer network and the original MAN access network share the same platform.
The IPTV bearer network is thus integrated in the entire network structure of carriers.
At the core layer, the high-end router NE80E/40E is used to build an MPLS VPN and
construct the logical plane for various services. In addition, the NE80E/40E forwards data
at a high speed and provides high-performance QoS.
Issue 02 (2011-08-12)
68
8 Applicable Environment
In the early phase of the development of IPTV services, normal services and IPTV
services access the same BRAS and traffic streams are distributed. In this manner, little
change is performed on the entire network and new services are deployed promptly.
With the deployment of large-scale services, dedicated IPTV BRASs are required.
Broadband access services access the original BRAS; IPTV services access the
dedicated IPTV BRAS. In this manner, IPTV services and other services are free from
interacting on each other; the requirements of high-volume traffic of IPTV services are
satisfied. In addition, the powerful control capability of the BRAS ensures the secure
access of IPTV services. IPTV services and other services are distributed on the
convergence-layer devices.
Internet
backbone
network
IP bearer
network
Egress router
IP MAN
MAN core
network
ASBR-PE
BRAS
USR
Broadband
access
Access
network
Customer
service
NGN service
As shown in Figure 8-3, an IP MAN is classified into the core layer, service control layer, and
access layer.
The NE40E is usually deployed as the core node on IP backbone networks, IP MANs, and largescale IP networks. In this application, the NE80E is deployed on the egress of an IP MAN core
network.
The NE40E is usually deployed as the core or convergence node on IP MANs. In this application,
theNE40E is deployed as the convergence node on an IP MAN core network. The core layer is
responsible for high-performance and large-capacity data forwarding. It requires a simple
Issue 02 (2011-08-12)
69
8 Applicable Environment
network structure and secure and reliable transmission of multiple services. Huawei enables IP/
MPLS at the core layer and allows a physical network to implement multiple logical service
bearer planes through the MPLS VPN technology. To ensure network security and reliability,
Huawei adopts many reliability techniques at the core layer, such as high reliability of devices
and networks, and inter-AS high reliability. Huawei provides core-layer devices of large
capacities, high-density interfaces, and high forwarding performance, answering the
requirements of the core layer.
The NE40E provides the following features that can answer the demands of the core layer of
the MAN:
l
The NE40E has a powerful switching capacity. The interface capacity of a single system
reaches 640 Gbit/s. The NE40E provides 10-Gbit/s interfaces at line speed and high-density
GE interfaces. This meets the requirements for large-capacity and high-performance
forwarding on the core network.
The NE40E provides powerful routing capabilities and various routing protocols. The
NE40E supports IP/MPLS and provides multiple VPN solutions such as BGP/MPLS
L3VPN and MPLS L2VPN. In this manner, multiple services are carried over the logical
bearer plane of the core network. Service isolation and security are thus implemented.
The NE40E supports inter-AS VPN Option A/B/C. This guarantees the reliable running of
inter-AS services.
The NE40E provides carrier-class reliability, such as redundancy of key modules and inservice patching. In addition, the NE40E provides various FRR techniques, such as IP FRR,
LDP FRR, and TE FRR.
PE
NE80E
NE80E
IPv6 Internet
NE80E
IPv6/IPv4
NE5000E/80E
IPv6 Core
PE
IPv6
SOHO IPv6
Issue 02 (2011-08-12)
5000E/80E
NE5000E/80E
NE80E/40E
NE80E/40E
IPv6 EDGE
PE
IPv4 Internet
L3 Switch
L3 Switch
MA 5200
L2 Switch
SOHO IPv6
70
8 Applicable Environment
The IPv6 application on a backbone network does not affect the original IPv4 services such as
IPv4 forwarding and MPLS VPN. The application needs to solve the following problems:
l
To address the preceding problems, The NE40E applies IPv6 key technologies in the following
combinations:
l
All the routers on the backbone network support the IPv4/IPv6 dual stack. In this case, IPv4
services are forwarded over IPv4, whereas IPv6 services are forwarded over IPv6. Both
problems can be solved.
The interconnection between IPv6 islands can be implemented through MPLS L2 tunnels
by applying MPLS L2VPN techniques such as VPLS and CCC. The core router needs to
support only MPLS forwarding. The interworking between IPv6 and IPv4 networks can be
implemented by configuring NAT-PT on gateways.
Issue 02 (2011-08-12)
71
8 Applicable Environment
E1
TD
M*
Router
Router
E1 TDM
E1 TDM*N
BSC
MPLS over SDH/ME
N *E1(ATM IMA)
N *E1(ATM IMA)
Node B
T
(A
E1
IM
A)
Router
Router
RNC
Transparent transmission
of ATM cells through PWE3
Transparent transmission
of TDM services
Node B
Deploying devices on a Metro Ethernet-based MPLS network can solve the problem of
bandwidth multiplexing. Node B is connected to the NE40E that supports E1 IMA interfaces.
After the NE40E terminates IMA, the high-speed ATM cell flow is transparently transmitted
through ATM PWE3 to the NE40E at the RNC side. Then, the NE40E at the RNC side divides
the high-speed ATM cell flow into n x E1 links, and sends multiple channels of low-speed cells
to the RNC. For the Node B and RNC, the NE40E and MPLS network are transparent. That is,
multiple E1 interfaces on the Node B and RNC are directly connected through the TDM link.
Issue 02 (2011-08-12)
72
8 Applicable Environment
GPS
GPS
POS
BC
1588v2
BC
1588v2
GE
FE
GE
BC
BC
E1
E1
1588v2
Node B
with 1588v2
Node B
without 1588v2
FE
1588v2
Node B
without 1588v2
Node B
with 1588v2
Issue 02 (2011-08-12)
73
8 Applicable Environment
AAA server
Policy server
IP/MPLS Core
NE40E
IP/MPLS Edge
NE40E
NE40E
soft switch
VoIP
gateway
VoD server
Metro
Network
PSTN
L3
DSLAM
IAD
DSLAM
IAD
After detecting packet loss according to received channel data, the STB sends the retransmission
request to the NE40E. Then, the NE40E searches the cached channel data for the packets to be
retransmitted and retransmits these packets to the STB.
The iVSE-capable NE40E can monitor video quality by calculating the quality data of video
from the source and then drawing a conclusion on video quality on the NE40E. The result
contains the quality of video flows on the NE40E.
Issue 02 (2011-08-12)
74
8 Applicable Environment
Ethernet Aggregation
Edge
Core
Application
I n t e rn e t
Distribution
node
BRAS
DSLAM
CMTS
Aggregafion
Node
Internet
P/PE
P/PE
SoftX
VoD ES
P/PE
Distribution
node
AccSwitch
PE
VoD CS
As the aggregation node and distribution node, the NE40E accesses the IPTV service and
forwards IPTV packets on Layer 3. In this scenario, after iVSE is applied to the aggregation
node and distribution node, fast switchover of videos, retransmission of lost video packets, and
monitoring of video quality can be provided.
l
When the user switches channels, the STB sends a fast switchover request to the iVSEcapable NE40E. Then, the NE40E fast pushes channel data to the STB and reports new
channels. The STB sends the IGMP adding request to the DSLAM or multicast switch.
Finally, the DSLAM or multicast switch pushes multicast data of new channels to the STB.
After detecting packet loss according to received channel data, the STB sends the
retransmission request to the NE40E. Then, the NE40E searches the cached channel data
for the packets to be retransmitted and retransmits these packets to the STB.
In addition, the iVSE-capable NE40E can monitor video quality by calculating the quality
data of program flows from the source and then drawing a conclusion on video quality on
the NE40E.
As the aggregation node and distribution node, the NE40E accesses the IPTV service and then
transparently transmits IPTV packets to the BRAS or integrated PEs through VPLS. In this
scenario, after monitoring of video quality is applied to the aggregation nodes and distribution
nodes separately, end-to-end monitoring of video quality can be provided.
l
When monitoring of video quality is deployed on a distribution node, the IPTV flows are
monitored and calculated before they enter the VPLS tunnel. The calculated result shows
the quality of the IPTV flows on the distribution node.
When monitoring of video quality is deployed on an aggregation node, the IPTV flows are
monitored and calculated after they leave the VPLS tunnel. The calculated result shows the
quality of the IPTV flows on the aggregation node.
When monitoring of video quality is deployed on both distribution nodes and aggregation
nodes, you can deploy monitoring of video quality on the ingress and egress of VPLS
tunnels, that is, distribution nodes and aggregation nodes, to check video quality on each
segment. By checking video quality on each segment, you can locate the causes of poor
video quality.
Issue 02 (2011-08-12)
75
Issue 02 (2011-08-12)
76
Console interface
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 the
control plane and data plane, and deliver debugging commands and control commands.
The NMS configuration supports the configuration through the SNMP-based NMS.
Board detection, hot swap detection, Watchdog, board resetting, RUN indicator and
debugging indicator control, fan and power supply control, master/slave switchover
control, and version query
Local and remote loading and upgrade of software and data, and functions such as version
rollback, backup, saving, and clearing of version information
Hierarchical user authority management, operation log management, command line online
help, and comments after the commands
Multi-user operation
Support of the shutdown and undo shutdown commands on interfaces and optical modules
77
Log information
Debugging information
Trap information
Information is classified into eight severity levels. The lower the level, the higher the severity.
The following table shows the detailed information.
Lev
el
Seve
rity
Description
Emer
gency
Alert
Critic
al
Error
Warn
ing
Notic
e
Infor
matio
nal
Debu
gging
The information center supports 10 channels, of which channels 0 through 5 each have a default
channel name. By default, the six channels correspond to six directions in which information is
output. 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 to
different log hosts through one channel or multiple channels. For example, you can configure
some log information to be output to a log host through Channel 2 (loghost), and some log
information to a log host through Channel 6. In addition, you can change the name of Channel
6 to implement the desired channel management.
Issue 02 (2011-08-12)
78
The NE40E stores all alarms in a log file, and provides the CF card to store the log file. How
long the alarms can be stored depends on the number of the alarms. Generally, the alarms can
be stored for months.
9.4 HGMP
The NE40E supports the Huawei Group Management Protocol (HGMP). HGMP is a cluster
management protocol developed by Huawei.
HGMP is used to group Layer 2 devices that are connected to the NE40E into a unified
management domain, that is, a cluster. HGMP supports automatic collection of network
topologies and provides integrated maintenance and management channels. In this manner, a
cluster uses only one IP address for external communications, simplifying device management
and saving IP addresses.
Monitors the types of protocol packets sent by the forwarding engine to the control plane
and displays detailed information about packets by enabling debugging.
Supports HGMP.
79
When voice services on the network deteriorate, or mosaics appear in some videos, the
NE40E may have sent or received incorrect packets or have lost packets. You can capture packets
to locate the problems. The packet capture function can be used to capture the packets sent to
the CPU, and the packets forwarded in the inbound or outbound direction. Compared with the
port mirroring function, the packet capture function is easier and faster to configure.
9.7 NQA
The NE40E supports Network Quality Analysis (NQA).NQA measures the performance of
different protocols running on the network. In that case, carriers can collect the operation index
of networks in real time, such as:
l
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 for
diagnosing and locating a network fault.
PWE3 tracert
Multicast ping
Multicast tracert
Issue 02 (2011-08-12)
80
9.10 License
With the variation of the NE40E software functions and higher ratio of software cost occupying
the overall cost, the current service mode cannot satisfy the development requirements of
customers and carriers.
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 flexible
authorization to service modules.
For the authorization control of service modules, the NE40E provides the License authorization
management platform through the Global Trotter License (GTL). Through the License
authorization mode:
l
Common users can purchase service modules as required and reduce the purchase cost.
Upgrade and expansion users can expand the capacity, and support and maintain the
functions by applying for a new License.
Issue 02 (2011-08-12)
81
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 display
command.
Issue 02 (2011-08-12)
82
10 NMS
10
NMS
SNMP
The NE40E supports device operation and management by the network management station
through SNMP.
The NE40E supports SNMPv1, SNMPv2c, and SNMPv3.
l
SNMPv1
SNMPv1 supports community name-based and MIB view-based access control.
SNMPv2c
SNMPv2c supports community name-based and MIB view-based access control.
SNMPv3
SNMPv3 inherits the basic functions of SNMPv2c, defines a management frame, and
introduces a User-based Security Model (USM) to provide a more secure access control
mechanism for users.
SNMPv3 supports user groups, user group-based access control, user-based access control,
and authentication and encryption mechanisms.
NMS
The NE40E adopts Huawei iManager U2000 network management system. It supports
SNMPv1/v2c/v3 and the client/server architecture. The network management system can run
independently on many operation systems, such as Windows NT/2000/XP, UNIX (Sun, HP, and
IBM). The NE40E also provides a multi-lingual graphical user interface.
LLDP
The 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 its
status to the neighbor stations. The interfaces can also send information about changes in the
status to the neighbor stations as required. The neighbor stations then store the received
information in the standard SNMP MIB. The NMS can search for Layer 2 information in the
MIB. As specified in the IEEE 802.1ab standard, the NMS can also discover unreasonable Layer
2 configurations based on information provided by LLDP.
When LLDP runs on the devices, the NMS can obtain Layer 2 information about all the devices
to which it connects and detailed network topology information. This is helpful to the rapid
Issue 02 (2011-08-12)
83
10 NMS
expansion of the network and acquirement of detailed network topologies and changes. LLDP
also helps discover unreasonable configurations on networks and reports the configurations to
the NMS. This removes incorrect configurations in time.
Issue 02 (2011-08-12)
84
A
AAA
AAL5
AC
Access Controller
ACL
AF
Assured Forwarding
ANSI
AP
Access Point
ARP
ASBR
ASIC
ATM
AUX
Auxiliary (port)
B
BE
Best-Effort
BGP
BGP4
BGP Version 4
Issue 02 (2011-08-12)
CAR
CBR
CE
Customer Edge
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
85
CHAP
CoS
Class of Service
CPU
CR-LDP
D
DAA
DC
Direct Current
DHCP
DNS
DS
Differentiated Services
E
EACL
EF
Expedited Forwarding
EMC
EElectroMagnetic Compatibility
F
FCC
FE
Fast Ethernet
FEC
FIB
FIFO
FR
Frame Relay
FTP
G
GE
Gigabit Ethernet
GRE
GTS
Issue 02 (2011-08-12)
86
HA
High availablity
HDLC
HTTP
I
iVSE
ICMP
IDC
IEEE
IETF
IGMP
IGP
IP
Internet Protocol
IPoA
IP Over ATM
IPTN
IP Telephony Network
IPTV
IPv4
IP version 4
IPv6
IP version 6
IPX
IS-IS
ISP
ITU
Issue 02 (2011-08-12)
LAN
LCD
LCP
LDP
LER
LPU
LSP
LSR
87
M
MAC
MBGP
MD5
Message Digest 5
MIB
MP
Multilink PPP
MPLS
MSDP
MSTP
MTBF
MTTR
MTU
N
NAT
NLS
NP
Network Processor
NTP
NVRAM
O
OSPF
Issue 02 (2011-08-12)
PAP
PE
Provider Edge
PFE
PIC
PIM-DM
PIM-SM
POP
Point Of Presence
88
POS
PPP
Point-to-Point Protocol
PQ
Priority Queue
PT
Protocol Transfer
PVC
Q
QoE
Quality of Experience
QoS
Quality of Service
R
RADIUS
RAM
Random-Access Memory
RED
RFC
RH
Relative Humidity
RIP
RMON
Remote Monitoring
ROM
RP
Rendezvous Point
RPR
RSVP
RSVP-TE
RSVP-Traffic Engineering
Issue 02 (2011-08-12)
SAP
SCSR
SDH
SDRAM
SFU
SLA
SNAP
89
SNMP
SONET
SP
Strict Priority
SPI4
SSH
Secure Shell
STM-16
SVC
T
TCP
TE
Traffic Engineering
TFTP
TM
Traffic Manager
ToS
Type of Service
TP
U
UBR
UDP
UNI
UTP
Issue 02 (2011-08-12)
VBR-NRT
VBR-RT
VC
Virtual Circuit
VCI
VDC
VLAN
VLL
VPI
VPLS
90
VPN
VRP
VRRP
Issue 02 (2011-08-12)
WAN
WFQ
WRED
WRR
91