You can configure an interface monitoring group in a dual-device backup scenario 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.
When a network-side interface goes Down in a dual-device backup scenario, 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 1, PE2 backs up PE1. NPE1 through NPEM on the user side is 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.
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. When a link failure occurs on the network side and the interface monitoring group detects that the status of a certain proportion of network-side interfaces changes, the system instructs the user-side interfaces associated with the interface monitoring group to change their status accordingly and allows traffic to be switched between the master and backup links. Therefore, the interface monitoring group can be used to prevent traffic overloads or interruptions.
Before configuring an interface monitoring group, configure physical attributes for interfaces on the router.
The system view is displayed.
An interface monitoring group is created, and the interface monitoring group view is displayed.
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.
Exit from the interface monitoring group view.
The view of the specified interface on the user side is displayed.
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.
If the down weight sum of all the binding interfaces in the monitoring group is greater than or equal to the value specified using trigger-down-weight-value on the track interface, the track interface goes down, and service traffic is switched to the backup link. Otherwise, the track interface goes up, and service traffic is switched back to the primary link.
Exit from the interface view.
The view of the created interface monitoring group is displayed.
The delay after which a track interface goes Up is set.
The monitoring function is enabled.
The configuration is committed.
Run the display monitor-group [ monitor-group-name ] command to view information about an interface monitoring group.