track monitor-group

Usage Scenario

To configure the remote backup service to track the monitor group status so that the TCP connection failure or failure rectification can be detected, run the track monitor-group command.

When the link on the network-side device fails, terminals cannot access the network. Therefore, when hot backup is deployed, a device must monitor the status of the link on the network side. If the link fails, a master/slave switchover is triggered on the access side, ensuring that terminals can properly access the network.

Generally, multiple links are deployed on the network side. If some links fail, downstream traffic may be congested. In this situation, a master/slave switchover must also be promptly triggered on the access side.

Configuration Impact

After you run the track interface-group command in the remote backup service view in which the track interface command has been run, the device automatically deletes the track interface and switchover uplink configurations and then controls service switchover based on the track interface-group configuration.

After you run the track interface-group command in the remote backup service view, you can no longer run the track interface or switchover uplink command.

An RBS can be configured to track two interface groups. When an interface in an interface group fails and conditions for a master/slave switchover are met (that is, the link bandwidth fault threshold percentage reaches the value specified by failure-ratio):

• A master/slave switchover is triggered for all RBP protocol groups associated with the RBS. You can run the backup-id <backup-id> remote-backup-service <name> command in the remote backup profile view to view the association between the RBP and RBS. The RBP with the backup ID specified by<backup-id> is associated with the RBS with the name specified by <name>.
• The network segment route selection of the IPv4/IPv6 address pool bound to the RBS is affected. During a master/slave switchover, a device automatically withdraws the network routes in the master address pool or changes the cost value of the network segment route in the master address pool to the maximum so that downstream traffic cannot reach the device. The device does not advertise address pool routes until the fault is rectified and traffic is switched back. (You can run the peer-backup route-cost advertising command in the system view to change the cost value to the maximum. If you do not perform configurations, the device withdraws network routes in the address pool by default.)