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

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).
Associating an Internal Communication Interface with a Route Monitoring Group

Associating an Internal Communication Interface with a Route Monitoring Group

This section describes how to associate an internal communication interface with a route monitoring group in a virtual access dual-device hot backup scenario. After the association, changes in the state of network-side routes trigger primary/backup path switchovers, which prevents network congestion and traffic loss.

Usage Scenario

In a virtual access dual-device hot backup scenario, if a network-side route fails, the virtual access system does not detect the fault and therefore does not switch traffic to the secondary master. As a result, traffic overloads or interruptions occur.

As shown in Figure 3-25, each AP is dual-homed to a primary and secondary master, and the masters connect to n PEs on the network side. If the routes between the primary master and PE1 and between the primary master and PE2 fail, the virtual access system does not detect the fault. Upstream traffic from the user side to the network side is still sent to PEn through the primary master. Network congestion may occur because the number of available links on the network side decreases. If the route between the primary master and each PE fails, upstream traffic from the user side to the network side is lost.

To resolve this issue, deploy a route monitoring group on the primary and secondary masters, add multiple network-side routes to the route monitoring group, and associate an internal communication interface with the route monitoring group. If a network-side route fails, the fault weight of the route monitoring group increases. When the fault weight of the route monitoring group reaches a specified value, the internal communication interface on the primary master goes Down. This event triggers a primary/secondary master switchover. Upstream traffic is then switched to the secondary master, preventing network congestion or traffic loss.

Figure 3-25  Associating an internal communication interface with a route monitoring group

Pre-configuration Tasks

Before associating an internal communication interface with a route monitoring group, configure a route monitoring group.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface interface-type interface-number

    The internal communication interface view is displayed.

  3. Run:

    track route-monitor-group monitor-group-name [ trigger-down-weight trigger-down-weight-value ]

    The internal communication interface is associated with a specified route monitoring group.

    When the fault weight of the route monitoring group reaches the value specified by trigger-down-weight-value, the internal communication interface goes Down. This event triggers traffic to be switched to the secondary master. When the fault weight of the route monitoring group falls below the value specified by trigger-down-weight-value, the internal communication interface goes Up. This event triggers traffic to be switched to the primary master.

    You can repeat Step 2 and Step 3 to associate multiple internal communication interfaces with the same route monitoring group.

  4. Run:

    commit

    The configuration is committed.

Checking the Configurations

After associating an internal communication interface with a route monitoring group, check the configurations.
  • Run the display ip route-monitor-group [ group-name ] command to check information about a specified route monitoring group.
  • Run the display ip route-monitor-group track-route [ vpn-instance vpn-instance-name ] dest-address { mask | mask-length } command to check information about all route monitoring groups to which a route has been added.
  • Run the display this command in the internal communication interface view to check the interface's association with route monitoring groups.
Download
Updated: 2018-07-12

Document ID: EDOC1100028541

Views: 7949

Downloads: 92

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