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-M2 V800R010C10SPC500 Configuration Guide - Interface and Data Link 01

This is NE40E-M2 V800R010C10SPC500 Configuration Guide - Interface and Data Link
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 an Interface Monitoring Group

Configuring an Interface Monitoring Group

In a dual-device backup scenario, you can configure an interface monitoring group to allow the user-side interface status to change with the network-side interface status so that traffic can be switched between the master and backup links.

Usage Scenario

In a dual-device backup scenario, when a network-side interface goes Down, user-side devices cannot detect the Down event and therefore do not switch traffic to the backup link. As a result, traffic overloads or interruptions occur. To prevent these problems, you can configure an interface monitoring group to monitor the network-side interface status and instruct the user-side interface to change its status accordingly. An interface monitoring group allows traffic to be switched between the master and backup links and prevents traffic overloads or interruptions.

On the network shown in Figure 2-4, PE2 backs up PE1. NPE1 through NPEM on the user side are dual-homed to the two PEs to load-balance traffic, and the two PEs are connected to DeviceA through DeviceN on the network side. When only the link between PE1 and DeviceN is available and all the links between PE1 and all the other routers fail, the NPEs do not detect the failure and continue sending packets to DeviceN through PE1. As a result, the link between PE1 and DeviceN becomes overloaded.

Figure 2-4 Typical application of an interface monitoring group

To resolve this problem, you can configure an interface monitoring group and add multiple network-side interfaces on the PEs to the interface monitoring group.

Pre-configuration Tasks

Before configuring an interface monitoring group, configure physical attributes for interfaces on the Router.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run monitor-group monitor-group-name

    An interface monitoring group is created, and the interface monitoring group view is displayed.

  3. Run binding interface interface-type interface-number [ down-weight down-weight-value ]

    An interface is added to the interface monitoring group.

    The interface added to an interface monitoring group is called a binding interface. A binding interface is located on the network side and a track interface on the user side. An interface monitoring group monitors the binding interface status and allows the track interfaces to change their status accordingly.

    You can repeat this step to add multiple binding interfaces to an interface monitoring group.

  4. Run quit

    Exit from the interface monitoring group view.

  5. Run interface interface-type interface-number

    The view of the specified interface on the user side is displayed.

  6. Run track monitor-group monitor-group-name [ trigger-down-weight trigger-down-weight-value ]

    The interface is associated with an interface monitoring group.

    The user-side interface associated with an interface monitoring group is called a track interface.

    You can repeat steps 5 and 6 to associate multiple track interfaces to an interface monitoring group.

  7. Run quit

    Exit from the interface view.

  8. Run monitor-group monitor-group-name

    The view of the created interface monitoring group is displayed.

  9. (Optional) Run trigger-up-delay trigger-up-delay-value

    The delay after which a track interface goes Up is set.

  10. Run monitor enable

    The monitoring function is enabled.

  11. Run commit

    The configuration is committed.

Checking the Configurations

After configuring an interface monitoring group, check the configurations.
  • Run the display monitor-group [ monitor-group-name ] command to view information about an interface monitoring group.

For example, run the display monitor-group group1 command to view information about an interface monitoring group named group1.

<HUAWEI> display monitor-group group1
monitor-group group1
    Index            : 1
    Down weight      : 10
    Weight sum       : 10
    Max track weight : 10
    Trigger-up delay : 100 (s)
    Status           : Inactive
-------------------------------------------------------
  monitor-group binding interface number : 1
-------------------------------------------------------
    Interface name  :  GigabitEthernet0/2/0
    Interface index :  17
    Down-weight     :  10
    Phystatus       :  DOWN
    Bfdstatus       :  -
    LastPhyuptime   :  -
    LastPhydowntime :  2013-02-27 01:20:49+01:00 DST
    LastBFDuptime   :  -
    LastBFDdowntime :  -
    ValidFlag       :  valid
-------------------------------------------------------
monitor-group track interface number : 1
-------------------------------------------------------
    Interface name      :  GigabitEthernet0/1/0
    Interface index     :  12
    Trigger-down-weight :  0 (default)
    TriggerStatus       :  TRIGGER UP
    LastTriggerUpTime   :  2013-02-27 02:51:40+01:00 DST
    LastTriggerDownTime :  2013-02-27 01:20:49+01:00 DST
    ValidFlag           :  valid
Download
Updated: 2019-01-02

Document ID: EDOC1100058380

Views: 1824

Downloads: 15

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