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

Reminder

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

upgrade

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).
Configuring User Information Backup in Shared IP Address Pool Mode

Configuring User Information Backup in Shared IP Address Pool Mode

The sharing address pool mode needs additional links but the networking is flexible.

Context

If the exclusive IP address pool mode is used, a great number of address pools are needed. This wastes addresses. The shared IP address pool mode addresses this problem. To adopt the shared IP address pool mode, the following conditions must be met:

  • Address pools are not bound to an RBP.
  • Both the master and backup devices need to advertise the address pool segment routes and require route policy configuration. In this manner, the address pool segment route advertised by the master device has a higher priority, preventing load balancing on network-side devices.
  • A protection tunnel, such as an LSP, needs to be set up between the master and backup devices. When an uplink fails, the downstream traffic will be introduced to the protection tunnel.
  • The address pool is bound to an RBS, that is, the ip-pool pool-name [ metric metric-num ] or ipv6-pool pool-name [ metric metric-value ] command is configured in the RBS view. This ensures that network-side traffic can be forwarded through the protection tunnel before the host route is generated.
    NOTE:

    Only the primary address, not the secondary address pool, is bound to the RBS.

Perform the following configurations on the devices that back up each other:

Procedure

  • Configure a protection tunnel template for public and private networks.
    1. Run system-view

      The system view is displayed.

    2. Run remote-backup-service service-name

      The RBS view is displayed.

    3. Run protect lsp-tunnel for-all-instance peer-ip ip-address

      The protection tunnel template is configured for both public and private networks.

      NOTE:

      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 VPN protection tunnel creation is triggered by user login. As a result, protection tunnels do not need to be created 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 private 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 private protection tunnel, run the protect ip-vpn-instance vpn-instance-name peer-ip ip-address [ interface interface-type interface-number ] command. These two commands can be configured together with the protect lsp-tunnel for-all-instance peer-ip command, but take precedence over the latter and therefore take effect. Manual tunnel configuration takes effect only for IPv4. IPv6 still uses simplified tunnels for forwarding.

    4. Run ip-pool pool-name [ metric metric-num ] for an IPv4 useripv6-pool pool-name [ metric metric-value ] for an IPv6 user

      The primary address pool is bound to the RBS.

      • For an IPv4 user, run the ip-pool pool-name [ metric metric-num ] command.
      • For an IPv6 user, run the ipv6-pool pool-name [ metric metric-value ] command.

    5. (Optional) Run dhcpv6-server destination destination-ipv6-address source source-ipv6-address [ vpn-instance vpn-instance ]

      Inter-chassis borrowing of IPv6 addresses is configured.

    6. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055031

Views: 17779

Downloads: 72

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