Configuring RUI in Shared Address Pool Mode
The shared address pool mode requires additional links but features flexible networking. RUI in shared IP address mode needs to be configured on both devices that back up each other.
Context
If the exclusive address pool mode is used, a great number of address pools are needed. This wastes addresses. The shared address pool mode resolves this problem. To use the shared address pool mode, ensure that the following requirements are met:
- Address pools are not bound to any RBP.
- Both the master and backup devices need to advertise their network segment routes to address pools and be configured with a routing policy to ensure that the route advertised by the master device has a higher priority. This prevents load balancing on network-side devices.
- A protection tunnel, for example, an LSP, must be set up between the master and backup devices. If the uplink of a user fails, the downstream traffic of the user is diverted to the protection tunnel.
- The primary address pool and the secondary address pool are bound to the RBS by running the ipv6-pool pool-name [ metric metric-value ] command in the RBS view. This ensures that network-side traffic can be forwarded through the protection tunnel before the host route is generated.
Procedure
- Configure a protection tunnel template for both the public network and VPNs.
- Run protect lsp-tunnel for-all-instance peer-ip ip-address
A protection tunnel template is configured for both the public network and VPNs.
The protect lsp-tunnel for-all-instance peer-ip command configures a protection tunnel template for both the public network and VPNs. After the command is run, a public protection tunnel is automatically created, and a VPN protection tunnel is created upon user login. This command does not require you to configure a protection tunnel for each VPN, simplifying tunnel configuration.
To configure a specific public protection tunnel, run the protect tnl-policy policy-name peer-ip ip-address [ interface interface-type interface-number ] command. To configure a specific VPN protection tunnel, run the protect ip-vpn-instance vpn-instance-name peer-ip ip-address [ interface interface-type interface-number ] command. Manual tunnel configuration takes effect only for IPv4. IPv6 still uses simplified tunnels for forwarding.
To configure a specific public protection tunnel, run the protect tnl-policy policy-name peer-ip ip-address [ interface interface-type interface-number ] command. To configure a specific VPN protection tunnel, run the protect ip-vpn-instance vpn-instance-name peer-ip ip-address [ interface interface-type interface-number ] command. If the two commands and the protect lsp-tunnel for-all-instance peer-ip command are all run, the protect lsp-tunnel for-all-instance peer-ip command takes precedence. Manual tunnel configuration takes effect only for IPv4. IPv6 still uses simplified tunnels for forwarding.
- Run protect lsp-tunnel for-all-instance peer-ip ip-address