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 Configuration Guide - User Access 01

This is NE40E V800R010C10SPC500 Configuration Guide - User Access
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).
Licensing Requirements and Limitations for User Access Multi-Device Backup

Licensing Requirements and Limitations for User Access Multi-Device Backup

Licensing Requirements

This feature is a basic feature and is not under license control.

Restrictions and Guidelines




Restrictions on L2TP hot backup:
  • Only LAC hot backup is supported.
  • The master and backup devices together support 16k L2TP tunnels and 128k sessions in 1:1 hot backup scenarios.
  • The LAC's IP address applies only to L2TP services.
  • Only the loopback interface's IP address can be used as the LAC's source IP address to interact with the LNS.
  • The IP core cannot use static routes to the LAC's IP address.
  • The set l2tp tunnel base-id base-id command must be run on the backup device to change the base value for allocating L2TP tunnel IDs on the backup device, so that different base values are used on the master and backup devices.
  • The RADIUS-delivered No. 66 attribute Tunnel-Client-Endpoint is not supported.
  • The switchback delay for VRRP on the master device must be configured using the vrrp vrid virtual-router-id preempt-mode timer delay delay-value command. Configuring a switchback delay of 30 minutes is recommended.
  • The interval for sending Hello packets for the L2TP tunnel (configured using the tunnel timer hello interval command) must use the default value 60s, and the Hello function cannot be disabled.

Do not deploy features that conflict with LAC hot backup after deploying LAC hot backup.

The function does not take effect on the backup device.

In multi-device hot backup scenarios, the function to redirect users to a specified domain upon quota exhaustion is supported only on the master device or the device switched to the master device.


The redirection function does not take effect on the backup device.

Multi-device hot backup does not support one-to-many mapping between one MAC address and many sessions for PPPoE users.

ARP fast reply is not supported in multi-device hot backup scenarios.

The backup of messages indicating successful redirection of users to a specified portal web page is not supported. After the captive portal function is enabled and users are redirected to a specified portal web page on the master device, the users are redirected to the portal web page again after a master/backup switchover is performed.


The function does not take effect on the backup device.

A maximum of 4:1 backup is supported, that is, a device can establish backup relationships with up to four devices.

Do not establish backup relationships with more than four devices.

Multi-device backup is affected.

When traffic is forwarded through the protection tunnel, enabling URPF on a network-side interface may cause a URPF check failure. Therefore, you are advised to disable URPF on a network-side interface based on the actual deployment scenario. Forwarded traffic includes IPoE/PPP/L2TP user traffic passing through the protection tunnel.

Do not deploy URPF on the network side in RUI scenarios.

Traffic fails to be forwarded.

The backup device fails to ping users (users on the backup device are in the slave state and cannot be pinged but the users can be pinged on the master device).

Do not ping users on the backup device.

Users cannot be pinged on the backup device.

In user access scenarios where inter-board Eth-Trunk interfaces are deployed, VRRP and BFD are operated on Eth-Trunk interfaces. If a fault occurs on the board where Eth-Trunk member interfaces reside and to which BFD is bound, the BFD session may go Down. As a result, a VRRP switchover is triggered, causing a service switchover.


A service switchover is performed.

On a BNG, the master/slave status of the interface functioning as a RADIUS proxy must be the same as that of a RADIUS proxy user's access interface.


Related configurations are required. Otherwise, RADIUS proxy cannot support dual-device hot backup.

When an RUI master/backup switchover occurs during user access, the user fails to go online in the following scenarios: The user completes RADIUS proxy authentication on the original master device, but a master/backup switchover occurs when the user does not complete subsequent access. The user's subsequent access packets are sent to the new master device. The new master device determines that the user is not authenticated and denies the user's access. The affected period is related to the interval between completing RADIUS proxy authentication and subsequent access processing. The typical period is hundreds of milliseconds (the maximum value is not more than 2 minutes). After the user fails to dial up, the user cannot go online through automatic re-dialup. Manual re-dialup is required.


RADIUS proxy users cannot go online in RUI scenarios.

Restrictions on IPv6 hot backup:
  • Multi-device hot backup for static IPv6 users is not supported.
  • In ND mode, only the unshared prefix assignment is supported.
  • IPv6 services' protection tunnels support only the MPLS LSP mode (6PE and 6VPE models).
  • IPv6 address pools do not support inter-chassis borrowing (local RUI-slave address pools cannot be used to assign IP addresses to the master device).
  • IPv6 hot backup does not support exclusively used address pools.
  • IPv6 hot backup does not support the mapping of RADIUS authorization address pool names to the local device.
  • IPv6 multicast does not support hot backup.

Do not deploy features that conflict with IPv6 hot backup after deploying IPv6 hot backup.

The function does not take effect on the backup device.

RBS supports three backup modes, and the backup modes support different services.

Hot backup: All services are supported.

Warm backup: All services are not supported.

Virtual backup: Only BRAS services are supported.

Mutual exclusion between some services and a backup mode is implemented using a command, whereas mutual exclusion between other services and a backup mode is not implemented. For example, virtual backup is not displayed in the current configuration, but does not take effect for other services except BRAS services. This does not affect functions.



Updated: 2019-01-03

Document ID: EDOC1100055031

Views: 17186

Downloads: 69

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