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).
(Optional) Binding a Static Route Tag to the RBS

(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 implement master/backup traffic switchover.

Context

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 RBS and specify a cost for the static route. If an NNI on the master device fails, the outbound interface of the static route can be directed to the protection tunnel to switch traffic to the backup device. This reduces the impact of the fault on user services.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run remote-backup-service service-name

    The RBS view is displayed.

  3. Run static-route if-match NULL interface-number tag tag-num [ metric metric-num ] [ rui-slave ]

    A static route tag is bound to the RBS, and a cost is specified for the static route.

    This command must be run on both the master and backup devices. In addition, rui-slave must be configured on the backup device. Otherwise, traffic flaps between the two devices.

    If metric metric-num is configured, the cost configured on the master device must be less than that configured on the backup device, so that the route on the master device is preferentially selected.

  4. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055031

Views: 19213

Downloads: 79

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