Configuring BMP

The BGP Monitoring Protocol (BMP) monitors BGP4+ running status of devices in real time, such as the establishment and termination status of BGP4+ peer relationships and route update status.

Usage Scenario

Without BMP, you have to run a query command on a BGP4+ device if you want to learn the BGP4+ running status of the device, which is inconvenient. To improve the network monitoring efficiency, you can configure BMP so that the BGP4+ running status of a client can be monitored by servers.

Pre-configuration Tasks

Before configuring BMP, configure basic BGP4+ functions.

Procedure

Run system-view
The system view is displayed.
Run bmp
BMP is started, and the BMP view is displayed.
(Optional) Run statistics-timer time
An interval is set. It determines the frequency at which the device sends BGP4+ running statistics to a monitoring server.

Configure the interval based on BGP4+ stability requirements. In the case of high BGP4+ stability requirements, configure a short interval. However, if the device frequently sends BGP4+ running statistics, a large number of bandwidth resources will be consumed.
Run bmp-session [ vpn-instance vrf-name ] ipv6-address [ alias alias-name ]
An IPv6 BMP session address is specified for the TCP connection to be established between the device and the monitoring server.

alias alias-name specifies an alias for a BMP session. If the device needs to establish multiple TCP connections with the same monitoring server through different port numbers, specify one IPv6 address and different session aliases (through the alias alias-name parameter) for differentiation.
Set the type of route whose statistics are to be sent by the device to the monitoring server.
- Configure the device to send statistics about RIB-in routes (all received routes or only accepted routes) of BGP4+ peers in a specified address family to the monitoring server.
  1. Run one of the following commands to enter the BMP-Monitor view:
    - monitor public: displays the BMP-Monitor view and allows the BGP4+ running status of all BGP4+ peers in the public network address family to be monitored.
    - monitor all-vpn-instance: displays the BMP-Monitor view and allows the BGP4+ running status of BGP4+ peers in all VPN instance address families to be monitored.
    - monitor peer: displays the BMP-Monitor view and allows the BGP4+ running status of a specified BGP4+ peer in the public address family to be monitored.
    - monitor vpn-instance: displays the BMP-Monitor view and allows the BGP4+ running status of all BGP4+ peers in a specified VPN instance address family to be monitored.
    - monitor vpn-instance peer: displays the BMP-Monitor view and allows the BGP4+ running status of a specified BGP4+ peer in a specified VPN instance address family to be monitored.
  2. Run the route-mode { ipv6-family unicast | ipv6-family vpnv6 } adj-rib-in { pre-policy | post-policy } command to configure the device to send statistics about RIB-in routes of BGP4+ peers in a specified address family to the monitoring server.
    
    To configure the device to send statistics about all received routes to the monitoring server, specify pre-policy in the command. To configure the device to send statistics about only accepted routes to the monitoring server, specify post-policy in the command.
    
    If pre-policy is specified in the command, run the keep-all-routes command in the BGP view to save the routes carried in the BGP4+ Update messages that are received from all BGP4+ peers or peer groups after BGP4+ connections are established, or run the peer keep-all-routes command to save the routes carried in the BGP4+ Update messages that are received from a specified BGP4+ peer or peer group after the BGP4+ connection is established.
- Configure the device to send statistics about RIB-out routes of BGP4+ peers in a specified address family to the monitoring server.
  1. Run one of the following commands to enter the BMP-Monitor view:
    - monitor public: displays the BMP-Monitor view and allows the BGP4+ running status of all BGP4+ peers in the public network address family to be monitored.
    - monitor all-vpn-instance: displays the BMP-Monitor view and allows the BGP4+ running status of BGP4+ peers in all VPN instance address families to be monitored.
    - monitor peer: displays the BMP-Monitor view and allows the BGP4+ running status of a specified BGP4+ peer in the public address family to be monitored.
    - monitor vpn-instance: displays the BMP-Monitor view and allows the BGP4+ running status of all BGP4+ peers in a specified VPN instance address family to be monitored.
    - monitor vpn-instance peer: displays the BMP-Monitor view and allows the BGP4+ running status of a specified BGP4+ peer in a specified VPN instance address family to be monitored.
  2. Run the route-mode { ipv6-family unicast | ipv6-family vpnv6 } adj-rib-out { pre-policy | post-policy } command to configure the device to send statistics about RIB-out routes of BGP4+ peers in a specified address family to the monitoring server.
    
    If you want the monitoring server to monitor all the routes to be advertised, regardless of whether they match the export policy, specify pre-policy in the command. If you want the monitoring server to monitor only the advertised routes (those that match the export policy), specify post-policy in the command.
- Configure the device to send statistics about Local-RIB routes of BGP4+ peers in a specified address family to the monitoring server.
  1. Run one of the following commands to enter the BMP-Monitor view:
    - monitor public: displays the BMP-Monitor view and allows the BGP4+ running status of all BGP4+ peers in the public address family to be monitored.
    - monitor vpn-instance: displays the BMP-Monitor view and allows the BGP4+ running status of all BGP4+ peers in a specified VPN instance address family to be monitored.
  2. Run the route-mode { ipv6-family unicast | ipv6-family vpnv6 } local-rib [ add-path ] command to configure the device to send statistics about Local-RIB routes of BGP4+ peers in a specified address family to the monitoring server.
Run quit
The BMP session view is displayed.
Run tcp connect port port-number [ password md5 cipher-password | keychain keychain-name ]
Parameters are configured for the TCP connection to be established between the device and the monitoring server.

To ensure high security, do not use the MD5 algorithm.
(Optional) Run connect-interface { interface-type interface-number | ipv6-source-address | interface-type interface-number ipv6-source-address }
The source interface for sending BMP messages is specified.
Run commit

The configuration is committed.

If a configuration of a BMP session is changed and the new configuration needs to take effect immediately, run the reset bmp session command to reset the BMP session.

Verifying the Configuration

After configuring BMP, verify the configuration.

Run the display bmp session [ vpn-instance vrf-name ] [ ipv6-address [ alias alias-name ] verbose ] command to check the configuration of the BMP session.
Run the display bgp bmp-monitor { all | vpnv6 ipv4-address | ipv6 { ipv4-address | ipv6-address } | vpnv6 vpn-instance vpn-instance-name { ipv4-address | ipv6-address } } command to check information about all BGP4+ peers or a specified BGP4+ peer monitored through BMP in all address families or in a specified address family.