No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


NE40E V800R010C10SPC500 Product Description

This is NE40E V800R010C10SPC500 Product Description
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Service Features

Service Features

Level-1 Feature

Level-2 Feature


Link features

Ethernet link features

The HUAWEI NetEngine40E provides Layer 3 Ethernet interfaces, including GE electrical interfaces, GE optical interfaces, 10GE optical interfaces, 40GE optical interfaces, 100GE optical interfaces, and global VE interfaces. These Layer 3 Ethernet interfaces support various IPv4/IPv6, MPLS, QoS, and multicast services.

  • Flow control and rate autonegotiation on GE interfaces

  • Bundling of interfaces into an Eth-Trunk interface that functions like a common Ethernet interface to support various services

  • Bundling of interfaces at different rates

  • Bundling of inter-board Ethernet interfaces into an Eth-Trunk interface

  • Hot backup of Eth-Trunk member interfaces

    A master/backup switchover can be automatically performed based on the link status of interfaces.

  • Addition or deletion of Eth-Trunk member interfaces

  • Layer 2 and Layer 3 Eth-Trunk interfaces

  • Inter-device Eth-Trunk (also known as E-Trunk)

  • BFD for Eth-Trunk

  • Link Aggregation Control Protocol (LACP) defined in 802.3ad

  • Virtual Ethernet (VE) interfaces

  • Ethernet clock synchronization

  • 1588v2 clock

  • VLAN sub-interfaces

  • Local and remote interface loopback

  • Flexible Ethernet (FlexEth)

  • Port extension

Link features

POS link features

POS interfaces support the following features:

  • Synchronous Digital Hierarchy (SDH) and Synchronous Optical Network (SONET) encapsulation

  • Point-to-Point Protocol (PPP)

    • Link Control Protocol (LCP)

    • Internet Protocol Control Protocol (IPCP)

    • Multiprotocol Label Switching Control Protocol (MPLSCP)

    • Password Authentication Protocol (PAP)

    • Challenge Handshake Authentication Protocol (CHAP)

  • High-level Data Link Control (HDLC)

  • IP-Trunk

    The NE40E supports the following IP bundling modes:

    • Inter-board IP bundling

    • IP bundling of channels of different rates

    • Addition of a POS interface to an IP-Trunk interface using commands

  • Local and remote interface loopback
  • Configuration of MTUs for IPv4, IPv6, and MPLS packets

Link features

CPOS link features
  • Channelization
    • CPOS interface channelization granularity: A 155 Mbit/s CPOS interface can be channelized into 63 E1 channels or N×64 kbit/s channels.
    • An E1 interface channelized from a CPOS interface, in compliance with SAToP, can transparently transmit unstructured TDM services through PWs on an MPLS network.
    • An E1 interface channelized from a CPOS interface, in compliance with CESoPSN, can transparently transmit structured TDM services through PWs on an MPLS network.
  • The NE40E provides 155 Mbit/s CPOS interfaces.

    CPOS interfaces support the following link layer protocols:

    • PPP
    • TDM
    • ATM
    • ATM IMA
    PPP on CPOS interfaces supports the following protocols:
    • LCP
    • IPCP
    • MPLSCP
    • ML-PPP
    • PAP
    • CHAP
  • Local and remote interface loopback
Link features LAD

LAD is a flexible link discovery protocol:

  • LAD uniquely identifies a device by its NE ID in decimal integers, facilitating maintenance and management.

  • LAD can discover neighbors for various types of interfaces and therefore is more widely used than LLDP.

  • LAD is triggered by an NMS or commands and therefore can be implemented as needed to avoid network conflicts and a waste of resources.

Ethernet features

Layer 2 Ethernet features

  • Default VLAN

  • VLAN trunk

  • VLANIF interfaces

  • VLAN aggregation

  • VLAN mapping

  • VLAN stacking

  • Intra-VLAN port isolation

  • MAC entry limit

  • Suppression of multicast, broadcast, and unknown unicast traffic

  • Spanning Tree Protocol (STP)/Rapid Spanning Tree Protocol (RSTP)

  • STP over VSI/PW

  • Multiple Spanning Tree Protocol (MSTP)

  • ERPS (G.8032)

  • VPLS


  • Unqualified MAC learning and qualified MAC learning (user MAC addresses are learned based on VSI+VLAN)
  • Y.1731 Eth-LCK, Eth-Test, and Eth-SLM
  • RRPP snooping
Ethernet features

Layer 3 Ethernet features

  • IPv4

  • IPv6

  • MPLS

  • Multicast

  • VLAN sub-interfaces

Ethernet features QinQ
  • QinQ stacking sub-interfaces

  • QinQ and Dot1q VLAN tag termination sub-interfaces

    QinQ and Dot1q VLAN tag termination sub-interfaces configured on the same interface have the same PE VID.

  • QinQ swap

  • QinQ translation

Ethernet features

BPDU tunneling

  • Port-based BPDU tunneling

  • VLAN-based BPDU tunneling

  • QinQ-based BPDU tunneling

  • VLL-based BPDU tunneling

  • VPLS-based BPDU tunneling

Ethernet Features ERPS over VPLS ERPS over VPLS allows an ERPS ring to connect to a VPLS network. This function supports the following VPLS access modes:
  • A VLANIF interface is single-homed to a VPLS network.
  • A VLANIF interface is dual-homed to a VPLS network.
  • A sub-interface is single-homed to a VPLS network. The sub-interfaces can be:
    • QinQ mapping 1:1 and VLAN-type Dot1q sub-interfaces
  • A sub-interface is dual-homed to a VPLS network. The sub-interfaces can be:
    • QinQ mapping 1:1 and VLAN-type Dot1q sub-interfaces
Ethernet Features


  • Layer 3 forwarding between VXLAN tunnels

  • Use of integrated routing and bridging (IRB) routes to advertise host routes between VXLAN tunnels
  • Application of traffic policies to VXLAN tunnels
  • DHCP relay for VXLAN tunnels
  • VNI-based rate limiting
  • VXLAN Layer 2 gateway
  • VXLAN Layer 2 gateway supporting the Spoken split horizon mode
  • MAC address learning using EVPN on the VXLAN control plane
  • BA classification and MF classification
  • VXLAN tunnel encapsulation before forwarding over L3VPN in Ethernet access scenarios
  • Interface-based sampling, packet parsing after sampling, VNI identification, and flow aggregation and output based on VNI and IP
  • VXLAN segments
IP features

IPv4/IPv6 dual stack

The IPv4/IPv6 dual stack is highly interoperable and easy to implement. The following figure shows the IPv4/IPv6 dual stack structure.

Figure 9-1 IPv4/IPv6 dual stack structure

IP features

IPv4 features

  • TCP/IP protocol suite, including ICMP, IP, TCP, UDP, socket (TCP/UDP/Raw IP), and ARP

  • Static DNS and DNS client/server

  • FTP client/server and TFTP client

  • DHCP relay agent/DHCP Server

  • Ping, tracert, and NQA

    NQA can detect the status of ICMP, TCP, UDP, DHCP, FTP, HTTP, and SNMP services and test the service response time.

  • IP policy-based routing (PBR) and flow-based next hop to which packets are forwarded

  • IP PBR-based load balancing

  • Load balancing in unequal cost multiple path (UCMP) mode

  • Dynamic load balancing

  • IPv4 load balancing among QinQ interfaces (including QinQ and Dot1q VLAN tag termination sub-interfaces)

  • Enabling and disabling the rapid ping reply function on interface boards

IP features

IPv6 features

  • IPv6 neighbor discovery (ND)

  • Path MTU (PMTU) discovery

  • TCP6, ping IPv6, tracert IPv6, and socket IPv6

  • DHCPv6 relay

  • IPv6 PBR

IP features

IPv4/IPv6 transition

  • IPv6 over IPv4 tunnels

  • 6PE and 6vPE tunnels

Routing protocols

Unicast routing

  • IPv4 routing protocols, including RIP, OSPF, IS-IS, and BGP4

  • IPv6 routing protocols, including Routing Information Protocol Next Generation (RIPng), OSPFv3, IS-ISv6, and BGP4+

  • Static routes that are manually configured by the network administrator to simplify network configurations and improve network performance

  • Large-capacity routing table that effectively supports the operation of MANs

  • Routing policy

Routing protocols

Multicast routing

  • Multicast protocols, which include:

    • IGMP, including IGMPv1, IGMPv2, and IGMPv3

    • PIM, including Protocol Independent Multicast-Sparse Mode (PIM-SM)and Protocol Independent Multicast-Dense Mode (PIM-DM)

    • Multicast Source Discovery Protocol (MSDP)

    • Multiprotocol Border Gateway Protocol (MBGP)

  • Reverse Path Forwarding (RPF)


  • Anycast RP

  • IPv6 multicast routing protocols that include PIM-IPv6-SM and PIM-IPv6-SSM

  • Multicast Listener Discovery (MLD)

  • Multicast static routes

  • Filtering of routes based on a routing policy in receiving, importing, and advertising multicast routes, and filtering and forwarding of multicast packets based on a routing policy in forwarding IP multicast packets

  • Addition and deletion of dummy entries

  • IGMP snooping (V1/V2/V3)

  • Multicast VLAN

    The NE40E supports only multicast VLANs.

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

  • Basic MPLS functions, service forwarding, and MPLS LDP signaling

  • LDP

  • MPLS ping and tracert operations in which MPLS Echo Request and MPLS Echo Reply packets are exchanged to monitor LSP availability

  • TE LSP-based traffic statistics, which are used to calculate bandwidth usage and trigger LSP bandwidth threshold-crossing alarms

  • MPLS per-packet load balancing

  • Management functions, such as LSP loop detection

  • MPLS QoS, including mapping of the ToS fields in IP packets to the EXP fields in MPLS packets, and MPLS uniform, pipe, and short pipe modes

  • TTL propagation in MPLS uniform mode

  • Traffic-classification-based label forwarding and static CR-LSP configuration

  • MPLS trap

  • Static CR-LSP


  • RSVP-TE authentication in compliance with relevant standards

  • Auto routing

  • FRR

  • One-to-one backup FRR: an MPLS TE FRR mode. After the detour attribute is configured for the primary tunnel, a detour LSP can be automatically established to protect an LSP on the primary tunnel. The detour LSP is a part of the primary tunnel. When the primary tunnel is established, detour LSPs are automatically established as needed. They are changed or deleted together with the primary tunnel.

  • CR-LSP backup

  • P2MP TE

  • 1:1 protection switching

  • CBTS



  • LDP Remote-LFA FRR

    LDP remote LFA FRR is a supplement to LFA LDP FRR. LFA LDP FRR uses the LFA FRR algorithm that can only protect LDP LSPs in 70% of all scenarios. After the remote LFA technique is implemented, FRR takes effect in more than 96% of all scenarios.

    The LDP module receives the remote LFA FRR next-hop address of a route prefix sent by the RM module. The LDP module uses the carried PQ node address to create an LDP remote peer and sends a Target Hello message to its peer to establish a remote LDP session. The PQ node address is used as a next-hop IP address for a remote-LFA FRR LSP. The actual next-hop IP address and outbound interface name are used to establish an LDP LSP destined for the PQ node. This LDP LSP allows for iteration of the remote LFR LSP.

    On the PQ node, the auto-accept function is configured. This function enables the PQ node to use information in the received Target Hello message to automatically establish a remote LDP peer. The PQ node then sends a Target Hello message to its peer to establish a remote LDP session. Label Mapping messages are then transmitted over the remote LDP session to establish a tunnel.

  • LDP over TE

  • mLDP

  • LDP over GRE

  • LDP DoD




Collaborative path computation by an IP PCE and optical PCE

RSVP neighbor authentication and UNI user access authentication

Protection for traffic on a specified UNI tunnel connected to the ingress CN on a transport network

Segment Routing


Segment routing (SR) is a new Multiprotocol Label Switching (MPLS) technique that uses the extended Interior Gateway Protocol (IGP) protocol and MPLS labels on control and forwarding planes, respectively. A routing segment is represented as an MPLS label on the forwarding plane.

SR-Traffic Engineering (SR-TE) is a new Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) tunneling technique implemented based on an Interior Gateway Protocol (IGP) extension. The controller calculates a path for an SR-TE tunnel and forwards a computed label stack to the ingress configured on a forwarder. The ingress uses the label stack to generate an LSP in the SR-TE tunnel. Therefore, the label stack is used to control the path along which packets are transmitted on a network.

The NE40E supports the following SR-TE functions:

  • Strict label stack
  • Stitching label
  • L2VPN, L3VPN, and LDP over SR-TE
  • Hot standby (HSB) LSP, and BFD for SR-TE LSP
  • Class-based tunnel selection (CBTS)
Segment Routing


SR LSPs are established using the segment routing technique, uses prefix or node segments to guide data packet forwarding. Segment Routing Best Effort (SR-BE) uses an IGP to run the shortest path algorithm to compute an optimal SR LSP.


VPN tunnel

  • LSP

  • GRE tunnel

  • TE tunnel


The NE40E supports the following VLL functions:

  • Martini VLL

  • Kompella VLL



  • VLL heterogeneous interworking

  • Transparent transmission of Layer 2 protocol (BPDU, LLDP, UDLD, CDP, or LACP) packets over VLL connections

  • Inter-AS VLL

  • VLL over TE ECMP
  • Single ICB PW

  • Double ICB PWs

  • VLL load balancing

  • Access to VLL by interfaces with the Access attribute

The NE40E supports the following VPLS functions:
  • H-VPLS

  • IGMP snooping for VPLS

  • MLD snooping for VPLS
  • mVPLS

  • Kompella VPLS

  • Transparent transmission of Layer 2 protocol (BPDU, LLDP, LACP, UDLD, or CDP) packets over VPLS connections

  • Load balancing based on source and destination MAC addresses

  • Flexible access to L2VPN based on DSCP or VLAN ID+802.1p priority

  • VPLS access for interfaces with the Access attribute

  • Forwarding of labeled packets by Eth-Trunk member interfaces in load-balancing mode (member interfaces of an Eth-Trunk interface can forward labeled packets in load-balancing mode based on the IP 5-tuple or the source and destination MAC addresses encapsulated in packets)



  • BD access to VPLS


The NE40E supports the following PWE3 functions:

  • VCCV ping

    The NE40E can use VCCV ping to detect LDP PW connectivity on the UPE. It is capable of detecting dynamic PWs, single-segment PWs (SS-PWs), and multi-segment PWs (MS-PWs).

  • VCCV traceroute

    VCCV traceroute can be performed for MS-PWs.

  • PW template

  • PW redundancy


  • CE access to an L3VPN through Layer 3 interfaces, such as Ethernet and VLANIF interfaces

  • Communication between CEs and PEs using static routes, BGP, RIP, OSPF, or IS-IS

  • Inter-AS VPN Option A, inter-AS VPN Option B, and inter-AS VPN Option C

  • Multicast VPN

  • IPv4 NG-MVPN

  • IPv6 NG-MVPN

  • IPv6 VPN

  • HoVPN

  • Seamless MPLS

  • Traffic redirection to a VPN

  • Multi-role host

  • Flexible access to L3VPN based on DSCP or VLAN ID+802.1p priority

  • Popgo action on an IPv4 public network

Ethernet virtual private network (EVPN) is used for Layer 2 internetworking. EVPN is similar to BGP/MPLS IP VPN. Using extended BGP reachability information, EVPN implements MAC address learning and advertisement between Layer 2 networks at different sites on the control plane instead of on the data plane.

EVPN offers the following benefits:
  • Improved link usage and transmission efficiency: EVPN supports load balancing, fully utilizing network resources and reducing network congestion.

  • Reduced network resource consumption: By deploying RRs on the public network, EVPN decreases the number of logical connections required between PEs on the public network. In addition, EVPN enables PEs to use locally stored MAC addresses to respond to ARP Request messages from connected sites, minimizing the number of broadcast ARP Request messages.

The following deployment models are supported:

  • EVPN E-Line


  • EVPN E-Tree, including local AC isolation
  • Access to EVPN through VLL

  • Access to EVPN through VXLAN


The following basic functions are supported:

  • Unicast traffic forwarding

  • BUM traffic forwarding

  • Unicast traffic load-balancing

  • Inter-AS Option B scenario


L2TPv3 over IPv6 establishes an IPv6-based L2TPv3 tunnel that transparently transmits Layer 2 user packets to remote ends over an IPv6 network. L2TPv3 over IPv6, which establishes tunnels based on static configurations, does not require dynamic negotiation for tunnel establishment or teardown.

Users can access an L2TPv3 tunnel in whole-interface mode.

Users can access an L2TPv3 tunnel in C-tag termination mode.

Users can access an L2TPv3 tunnel in S-Tag termination mode.

Users can access an L2TPv3 tunnel in S-tag+C-tag termination mode.

Local packet switching is supported.

Packet injection is supported.

Virtual Access IP RAN Virtual Cluster Access

Virtual cluster access centralizes control planes to allow one or two aggregation nodes to control all access nodes on a virtualized network. Multiple network devices are integrated into one device on the control plane.

IP RAN virtual cluster is deployed on the access network that consists of CSGs and AGGs.

On an IP RAN virtualization network, virtual cluster nodes are classified as master or AP. The master provides the virtual control plane, and APs are controlled by the master.

router is a new type of master at the original AGG location. APs are ATN devices at the original CSG locations.

The IP RAN virtual cluster access offers the following benefits:
  • Simplified network planning

    Access ring planes are centralized on AGGs, and the AGGs calculate forwarding paths and allocate entries for the whole network. The primary and backup paths can be calculated without manual planning.

    IP RAN virtual cluster uses IS-IS to calculate routes. Therefore, IP addresses do not need to be configured for CSG interfaces with the virtual cluster enabled, which simplifies IP address planning.

  • Simplified service deployment

    Dynamic protocols (such as RSVP-TE, LDP, and BGP) no longer run on CSGs on the access ring, which significantly simplifies networking and reduces device loads.

  • Simplified O&M and reduced costs

    The plug-and-play is implemented. Adding or deleting an AP requires only the configurations on this AP and the master to be updated, which dramatically reduces manpower costs.

    IP RAN virtual cluster access requires less dynamic protocols. An AP reports only a few alarms (such as link Up/Down alarms), and a master performs centralized reporting and management for virtual cluster alarms (such as LSP Up/Down and PW Up/Down alarms), which facilitates fault locating.

VPN IP hard pipe

IP hard pipe technology strictly isolates soft and hard pipes by reserving hardware, carrying leased line services of high-value customers, reserving service bandwidth, and ensuring low delay for services. IP hard pipe is an IP-based access technology that provides bandwidth guarantee and low delay as well as service-specific granular OAM and SLA monitoring, allowing IP networks to provide leased line access services through high-quality independent pipes.

The following functions are supported:

  • Point-to-point IP hard pipe (VLL IP hard pipe)

  • Point-to-multipoint IP hard pipe (VPLS IP hard pipe)

Traffic Management QoS
  • DiffServ model

  • BA classification

  • MF classification

  • Traffic policing

  • Queue scheduling

  • Congestion avoidance

  • HQoS

  • QPPB

  • Ethernet QoS

  • VLL HQoS: implements priority-based scheduling and rate limit management for services in a VLL and traffic bandwidth management for the entire VLL.
Traffic Management Load balancing
  • Equal-cost load balancing

  • Unequal-cost load balancing

Traffic Management Traffic statistics
  • URPF traffic statistics

  • ACL traffic statistics

  • CAR traffic statistics

  • HQoS traffic statistics

  • Interface traffic statistics

  • VPN traffic statistics

  • Traffic statistics about TE tunnels

Network reliability

High reliability of interface boards

  • VRRP on Ethernet interfaces.

  • Backup of trunk member interfaces, or backup of trunk member interfaces and non-member interfaces

  • Inter-board trunk bundling

Network reliability Transmission alarm suppression and customization Transmission alarm suppression can efficiently filter and suppress alarms, preventing interfaces from frequent flapping. In addition, transmission alarm customization is provided, which allows you to specify which alarms can cause interface status changes so as to control the impact of alarms on interface status.
Network reliability

Ethernet OAM

  • Fault management (EFM OAM and CFM OAM)
  • Performance management
Network reliability

VRRP (v4&v6)

  • mVRRP

  • E-VRRP

Network reliability


  • BGP/BGP4+ GR




  • Martini VLL GR

  • Martini VPLS GR

  • L3VPN GR



The NE40E can be configured as a GR helper rather than a GR restarter.

Network reliability NSR


Network reliability


  • IP FRR


  • TE FRR



Network reliability


  • BFD for VRRP

  • BFD for FRR, including BFD for LDP FRR, BFD for IP FRR, and BFD for VPN FRR

  • BFD for static routes

  • BFD for IS-IS

  • BFD for OSPF/BGP

  • BFD for PIM

  • BFD for trunk (including IP-Trunk and Eth-Trunk)

  • BFD for LSP

  • BFD for Dot1q sub-interfaces

  • BFD for mVSI

  • Multi-hop BFD

  • BFD for IPv6, including BFD for OSPFv3, BFD for IS-ISv6, and BFD for BGP4+

    BFD for IPv6 supports fault detection in default IPv6 mode.

  • BFD for VPLS PW
  • BFD for VLL PW
  • BFD for BDIF
Network reliability MPLS-TP OAM

MPLS-TP OAM supports the following functions:

  • Fault management

  • Performance monitoring

  • Protection switching

Network reliability MPLS OAM

MPLS OAM is a mechanism that does not depend on any upper or lower layer and implements the following functions:

  • Effectively detects, identifies, and locates faults at the MPLS client layer.

  • Quickly switches traffic if links or nodes fail to reduce the fault duration and improve network reliability.


Time synchronization

  • 1588v2

  • External clock source

  • NTP clock


Frequency synchronization

  • Synchronous Ethernet

  • SDH/PDH clock

  • External clock interface

  • Stratum 3 clock

  • Use of SSM levels in clock source selection

  • 1588 ACR

    • 1588 ACR slave
    • 1588 ACR server
User access IPv4-based IPoX user access
  • IP over Ethernet (IPoE), IP over Ethernet over VLAN (IPoEoVLAN), and IP over Ethernet over QinQ (IPoEoQ) access
  • User login using ARP trigger, IP trigger, or DHCP trigger
  • Bind authentication, fast authentication, and web authentication
  • Default domain and roaming domain
  • Options, such as Option 60 and Option 82
  • IPv4 address allocation
  • IPv4 address allocation
User access IPv6-Based IPoX User Access
  • IPv6 over Ethernet (IPv6oE), IPv6 over Ethernet over VLAN (IPv6oEoVLAN), and IPv6 over Ethernet over QinQ (IPv6oEoQ) access
  • ND trigger online and DHCPv6 trigger online
  • Web authentication, fast authentication, and binding authentication
  • Default domain and roaming domain
  • Typical option code, such as Option18 and Option37
  • IPv6 address, stateless prefix, and PD prefix allocation
User access IPv4-Based PPPoX User Access
  • PPP over Ethernet (PPPoE), PPP over Ethernet over VLAN (PPPoEoV), and PPP over Ethernet over QinQ (PPPoEoQ)

  • Default domain and roaming domain

  • IPv4 address allocation

  • PPPoE+

User access IPv6-Based PPPoX User Access
  • PPPv6oE, PPPv6oEoV, and PPPv6oEoQ
  • Default domain and roaming domain
  • IPv6 stateless prefix and PD prefix allocation
  • PPPv6oE+
User access User management
  • Flexible authentication, authorization, and accounting
    • Authentication policies include non-authentication, local authentication, remote authentication, and combined authentication.
    • Authorization methods include authorization after authentication and online authorization.
    • Accounting policies include non-accounting, post-paid accounting, pre-paid accounting, flexible IPv4/IPv6 dual-stack accounting, and remote accounting (RADIUS/RADIUS+).
  • Domain management
  • IPv4&IPv6 user management
User access User address management
  • User-based IPv4 address pool management on DHCP server, DHCP Proxy, and DHCP relay agent
  • IPv6 prefix pool management through the local prefix, delegation prefix, and proxy prefix
  • IPv6 address pool management through the DHCPv6 server and DHCPv6 relay agent
User access L2TP
  • L2TP sessions and tunnels
  • L2TP tunnel authentication
  • L2TP PPP user authentication and accounting
  • L2TP attributes delivered by the RADIUS server
  • L2TP permanent tunnels
  • LTS
  • L2TP QoS
User access Reliability
  • Trunk user access

  • Multi-device backup for user information

User access Value-added services
  • EDSG

  • BOD

  • DAA

  • Diameter

  • NAT server
  • Distributed deployment
  • Centralized deployment
  • Port pre-allocation and dynamic port allocation
  • Port forwarding (Port forwarding rules are delivered to the BRAS by the RADIUS server when users go online or by the OSS after users go online to create mappings between public network addresses, private network addresses, and interfaces.)
  • Dynamic load balancing for multiple CPUs
  • Global address pool
  • Inter-chassis hot backup
  • Inter-board hot backup
  • PCP
  • MAP-T and MAP-E

Virtual cluster

Virtual cluster

A virtual cluster virtualizes multiple redundant network edge routers into a logical device, reducing the numbers of NEs and IGP routes on the network, improving the network convergence effect, simplifying network design, and lowering O&M costs.

Updated: 2019-01-03

Document ID: EDOC1100055060

Views: 3588

Downloads: 155

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next