Configuring Multi-Device Backup for IPv4 User Information

After multi-device backup of IPv4 user information is enabled, users do not need to re-dial up, QoS scheduling remains unchanged, accounting information is not lost, and users can go online through new locations after a master/backup BRAS switchover.

Establishing a Multi-Device Backup Platform: A multi-device backup platform runs Huawei proprietary Redundancy User Information (RUI) protocol to back up user information between devices in a Virtual Router Redundancy Protocol (VRRP) group. This allows fast service switching to be performed if a network node or link fails, enhancing service reliability.

(Optional) Disabling User Information Remote Backup in a Specified Domain: User information remote backup can be disabled for users who get online from a specified domain as required.

(Optional) Configuring a Domain Mapping List: In a hot backup scenario where a domain name is delivered by the RADIUS server or carried in a packet from a user terminal, the backup device must map the domain name into different domain names for different RBSs to ensure resource independency in the RBSs.

Setting NAS Parameters: By setting NAS parameters, you can ensure that the master and backup BRASs send the same information to the remote servers, which allows users to log in through the backup device without authentication again.

(Optional) Setting a Traffic Backup Interval or Traffic Threshold: If the traffic backup interval and traffic threshold are both set to 0, user traffic is not backed up.

Controlling Advertisement of Address Pool UNRs: If BRASs work in load balancing mode, the BRASs must be configured to control advertisement of UNRs of configured address pools.

Configuring User Information Backup in Shared IP Address Pool Mode: In shared address pool mode, links need to be added, and the networking mode is flexible.

Configuring RUI in Exclusive Address Pool Mode: In BRAS multi-device backup scenarios, proper address pool configuration helps achieve efficient use of addresses.

(Optional) Configuring IP Addresses for Web Authentication and RADIUS Authorization Servers: The source IP address of the master and backup devices is the same as the BAS-IP address of the web authentication server and the NAS-IP address of the RADIUS authorization server.

Binding an RBP to a User Access Interface: Only an RBP that has been created in the system view can be bound to a user access interface. The binding needs to be configured on both devices that back up each other.

(Optional) Enabling the Backup Device to Discard DHCPv4 Release Messages in RUI Scenarios: This section describes how to enable the backup device to discard DHCPv4 Release messages sent by users, so that the logout reasons recorded on the master and backup devices are the same.

(Optional) Configuring an Upper Threshold for the User Access Rate on the Backup Device: This section describes how to configure an upper threshold for the user access rate on the backup device in a dual-device hot backup scenario.

(Optional) Binding a Static Route Tag to the RBS: In a dual-device hot backup scenario, if IP addresses are allocated using a RADIUS server instead of an address pool, you need to bind a static route tag to the remote backup service (RBS) to switch traffic between the master and backup devices.

(Optional) Configuring a Session ID Range for PPPoE Users: This section describes how to configure a range of session IDs that can be assigned to PPPoE users. This configuration prevents hot backup failures caused by session ID conflicts in an RUI scenario where one MAC address is mapped to multiple sessions.

Verifying the Configuration: After configuring multi-device backup, verify the configuration. You can view details about the remote server and the remote backup service type, which is BRAS.