connect-interface (BMP view)

Usage Scenario

BMP is used to monitor BGP running status of devices in real time, such as the status of BGP peer relationship establishment and termination and route updates.

After a TCP connection is established between a monitoring server and a device to be monitored, the device sends unsolicited BMP messages to the monitoring server to report BGP running statistics. After receiving these BMP messages, the monitoring server parses them and displays the BGP running status in the monitoring view. By analyzing the headers in the BMP messages, the monitoring server can determine from which BGP peer the routes carried in the messages were received. By default, the source interface used to send BMP messages is not specified after a TCP connection is established between a monitoring server and a device to be monitored. If the device encounters a failure, the source interface used to send BMP messages may change. In this case, the monitoring server cannot determine whether the new source interface belongs to a new device. To address this problem, run the connect-interface command to specify a source interface to send BMP messages.

The connect-interface command can be run in both the BMP view and BMP session view. If the command is run in both views, the configuration in the BMP session view takes precedence over that in the BMP view.

Precautions

If the connect-interface command is run more than once, the last configuration overrides the previous one.

In the BMP view, a source IPv4 address to set up a BMP session can be specified using the connect-interface command, whereas no source IPv6 address to set up a BMP session or source interface to send BMP messages can be specified. If the command is run in the BMP view, all IPv4 BMP sessions without a source IP address or source interface configured will be reestablished.