- Cisco BGP Overview
- BGP 4
- Configuring a Basic BGP Network
- BGP 4 Soft Configuration
- BGP Support for 4-byte ASN
- IPv6 Routing: Multiprotocol BGP Extensions for IPv6
- IPv6 Routing: Multiprotocol BGP Link-Local Address Peering
- IPv6 Multicast Address Family Support for Multiprotocol BGP
- Configuring Multiprotocol BGP (MP-BGP) Support for CLNS
- Connecting to a Service Provider Using External BGP
- BGP Route-Map Continue
- BGP Route-Map Continue Support for Outbound Policy
- Removing Private AS Numbers from the AS Path in BGP
- Configuring BGP Neighbor Session Options
- BGP Neighbor Policy
- BGP Dynamic Neighbors
- BGP Support for Next-Hop Address Tracking
- BGP Restart Neighbor Session After Max-Prefix Limit Reached
- BGP Support for Dual AS Configuration for Network AS Migrations
- Configuring Internal BGP Features
- BGP VPLS Auto Discovery Support on Route Reflector
- BGP FlowSpec Route-reflector Support
- BGP Flow Specification Client
- BGP NSF Awareness
- BGP Graceful Restart per Neighbor
- BGP Support for BFD
- IPv6 NSF and Graceful Restart for MP-BGP IPv6 Address Family
- BGP Link Bandwidth
- iBGP Multipath Load Sharing
- BGP Multipath Load Sharing for Both eBGP and iBGP in an MPLS-VPN
- Loadsharing IP Packets over More Than Six Parallel Paths
- BGP Policy Accounting
- BGP Policy Accounting Output Interface Accounting
- BGP Cost Community
- BGP Support for IP Prefix Import from Global Table into a VRF Table
- BGP Support for IP Prefix Export from a VRF Table into the Global Table
- BGP per Neighbor SoO Configuration
- Per-VRF Assignment of BGP Router ID
- BGP Next Hop Unchanged
- BGP Support for the L2VPN Address Family
- BGP Event-Based VPN Import
- BGP Best External
- BGP PIC Edge for IP and MPLS-VPN
- Detecting and Mitigating a BGP Slow Peer
- Configuring BGP: RT Constrained Route Distribution
- Configuring a BGP Route Server
- BGP Diverse Path Using a Diverse-Path Route Reflector
- BGP Enhanced Route Refresh
- Configuring BGP Consistency Checker
- BGP—Origin AS Validation
- BGP MIB Support
- BGP 4 MIB Support for Per-Peer Received Routes
- BGP Support for Nonstop Routing (NSR) with Stateful Switchover (SSO)
- BGP NSR Auto Sense
- BGP NSR Support for iBGP Peers
- BGP Graceful Shutdown
- BGP — mVPN BGP sAFI 129 - IPv4
- BGP-MVPN SAFI 129 IPv6
- BFD—BGP Multihop Client Support, cBit (IPv4 and IPv6), and Strict Mode
- BGP Attribute Filter and Enhanced Attribute Error Handling
- BGP Additional Paths
- BGP-Multiple Cluster IDs
- BGP-VPN Distinguisher Attribute
- BGP-RT and VPN Distinguisher Attribute Rewrite Wildcard
- VPLS BGP Signaling
- Multicast VPN BGP Dampening
- BGP—IPv6 NSR
- BGP-VRF-Aware Conditional Advertisement
- BGP—Selective Route Download
- BGP—Support for iBGP Local-AS
- eiBGP Multipath for Non-VRF Interfaces (IPv4/IPv6)
- L3VPN iBGP PE-CE
- BGP NSR Support for MPLS VPNv4 and VPNv6 Inter-AS Option B
- BGP-RTC for Legacy PE
- BGP PBB EVPN Route Reflector Support
- BGP Monitoring Protocol
- VRF Aware BGP Translate-Update
- BGP Support for MTR
- BGP Accumulated IGP
- BGP MVPN Source-AS Extended Community Filtering
- BGP AS-Override Split-Horizon
- BGP Support for Multiple Sourced Paths Per Redistributed Route
- Finding Feature Information
- Prerequisites for BGP Monitoring Protocol
- Information About BGP Monitoring Protocol
- How to Configure BGP Monitoring Protocol
- Verifying BGP Monitoring Protocol
- Monitoring BGP Monitoring Protocol
- Configuration Examples for BGP Monitoring Protocol
- Additional References for BGP Monitoring Protocol
- Feature Information for BGP Monitoring Protocol
BGP Monitoring Protocol
- Configure devices to function as BMP servers, and set up parameters on the servers, that are required for monitoring of the BGP neighbors.
- Establish connectivity of the BMP servers with BGP neighbors for monitoring.
- Generate statistics report from monitoring the BGP neighbors.
- Perform appropriate error handling on the BGP neighbors.
- Graceful scale up and degradation to the point of closing connectivity between the BMP servers and BGP neighbors.
- Finding Feature Information
- Prerequisites for BGP Monitoring Protocol
- Information About BGP Monitoring Protocol
- How to Configure BGP Monitoring Protocol
- Verifying BGP Monitoring Protocol
- Monitoring BGP Monitoring Protocol
- Configuration Examples for BGP Monitoring Protocol
- Additional References for BGP Monitoring Protocol
- Feature Information for BGP Monitoring Protocol
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for BGP Monitoring Protocol
Before you configure BGP Monitoring Protocol (BMP) servers, you must configure Border Gateway Protocol (BGP) neighbors, which function as BMP clients, and establish a session with its peers using either IPv4/IPv6 or VPNv4/VPNv6 address-family identifiers.
Information About BGP Monitoring Protocol
BGP Monitoring Protocol Overview
The BGP Monitoring Protocol (BMP) feature enables monitoring of BGP neighbors (called BMP clients). You can configure a device to function as a BMP server, which monitors either one or several BMP clients, which in turn, has several active peer sessions configured. You can also configure a BMP client to connect to one or more BMP servers. The BMP feature enables configuration of multiple BMP servers (configured as primary servers) to function actively and independent of each other, simultaneously to monitor BMP clients.
Each BMP server is specified by a number and you can use command-line interface (CLI) to configure parameters such as IP address, port number, and so on. Upon activation of a BMP server, it attempts to connect to BMP clients by sending an initiation message. The CLI enables multiple—independent and asynchronous—BMP server connections.
BGP neighbors, called BMP clients, are configured to send data to specific BMP servers for monitoring purposes. These clients are configured in a queue. When a request for a connection arrives from BMP clients to BMP servers, the connection is established based on the order in which the requests arrived. Once the BMP server connects with the first BMP neighbor, it sends out refresh requests to monitor the BMP clients and starts monitoring those BMP clients with whom the connection is already established.
The session connection requests from the other BMP clients in queue to the BMP servers initiates after an initial delay that you can configure using the initial-delay command. If a connection establishes but fails later, due to some reason, the connection request is retried after a delay, which you can configure using failure-retry-delay command. If there is repeated failure in connection establishment, the connection retries are delayed based on the delay configured using the flapping-delay command. Configuring the delay for such requests becomes significant because the route refresh requests that are sent to all connected BMP clients causes considerable network traffic and load on the device.
To avoid excessive load on the device, the BMP servers sends route refresh requests to individual BMP clients at a time, in the order in which connections are established in the queue. Once a BMP client that is already connected is in the “reporting” state, it sends a “peer-up” message to the BMP server. After the client receives a route-refresh request, route monitoring begins for that neighbor. Once the route refresh request ends, the next neighbor in the queue is processed. This cycle continues until all “reporting” BGP neighbors are reported and all routes sent by these “reporting” BGP neighbors are continuously monitored. If a neighbor establishes after BMP monitoring has begun, it does not require a route-refresh request. All received routes from that client is sent to BMP servers.
It is advantageous to batch up refresh requests from BMP clients, if several BMP servers are activated in quick succession. Use the bmp initial-refresh delay command to configure a delay in triggering the refresh mechanism when the first BMP server comes up. If other BMP servers come online within this time-frame, only one set of refresh requests is sent to the BMP clients. You can also configure the bmp initial-refresh skip command to skip all refresh requests from BMP servers and just monitor all incoming messages from the peers.
In a client-server configuration, it is recommended that the resource load of the devices be kept minimal and adding excessive network traffic must be avoided. In the BMP configuration, you can configure various delay timers on the BMP server to avoid flapping during connection between the server and client. To avoid excessive message throughput or high usage of system resources, you can configure the maximum buffer limit for the BMP session.
How to Configure BGP Monitoring Protocol
- Configuring a BGP Monitoring Protocol Session
- Configuring BGP Monitoring Protocol on BGP Neighbors
- Configuring BGP Monitoring Protocol Servers
Configuring a BGP Monitoring Protocol Session
Perform this task to configure BGP Monitoring Protocol (BMP) session parameters for the BMP servers to establish connectivity with BMP clients.
1.
enable
2.
configure
terminal
3.
router
bgp
as-number
4.
bmp {buffer-size
buffer-bytes
|
initial-refresh {delay
refresh-delay
|
skip}
|
server
server-number-n
5.
end
DETAILED STEPS
Configuring BGP Monitoring Protocol on BGP Neighbors
Perform this task to activate BGP Monitoring Protocol (BMP) on BGP neighbors (also called BMP clients) so that the client activity is monitored by the BMP server configured on the neighbor.
1.
enable
2.
configure
terminal
3.
router
bgp
as-number
4.
neighbor {ipv4-addr
|
neighbor-tag
|
ipv6-addr}
bmp-activate {all
|
server
server-number-1 [server
server-number-2 . . . [server
server-number-n]]}
5.
end
DETAILED STEPS
Configuring BGP Monitoring Protocol Servers
Perform this task to configure BGP Monitoring Protocol (BMP) servers and its parameters in BMP server configuration mode.
1.
enable
2.
configure
terminal
3.
router
bgp
as-number
4.
bmp {buffer-size
buffer-bytes
|
initial-refresh {delay
refresh-delay
|
skip}
|
server
server-number-n
5.
activate
6.
address {ipv4-addr
|
ipv6-addr}
port-number
port-number
7.
description
LINE
server-description
8.
failure-retry-delay
failure-retry-delay
9.
flapping-delay
flap-delay
10.
initial-delay
initial-delay-time
11.
set ip dscp
dscp-value
12.
stats-reporting-period
report-period
13.
update-source
interface-type
interface-number
14.
exit-bmp-server-mode
15.
end
DETAILED STEPS
Verifying BGP Monitoring Protocol
Perform the following steps to verify the configuration for the BGP Monitoring Protocol (BMP) servers and BMP clients:
1.
enable
2.
show ip bgp bmp
3.
show running-config
DETAILED STEPS
Monitoring BGP Monitoring Protocol
Perform the following steps to enable debugging and monitor the BGP Monitoring Protocol (BMP) servers.
1.
enable
2.
debug ip bgp bmp
3.
show debugging
DETAILED STEPS
Configuration Examples for BGP Monitoring Protocol
Examples for Configuring, Verifying, and Monitoring BGP Monitoring Protocol
Examples: Configuring BGP Monitoring Protocol
Note | There are two levels of configuration required for the BGP Monitoring Protocol (BMP) to function as designed. You must enable BMP monitoring on each BGP neighbor (also called BMP client) to which several peers are connected in a network, and establish connectivity between the BMP servers and clients. Then, configure each BMP server in BMP server configuration mode for a specific server with the parameters required for monitoring the associated BMP clients. |
The following example shows how to activate BMP on a neighbor with IP address 30.1.1.1, which is monitored by BMP servers (in this case, server 1 and 2):
Device> enable Device# configure terminal Device(config)# router bgp 65000 Device(config-router)# neighbor 30.1.1.1 bmp-activate server 1 server 2 Device(config-router)# end
The following example shows how to configure initial refresh delay of 30 seconds for BGP neighbors on which BMP is activated using the neighbor bmp-activate command:
Device> enable Device# configure terminal Device(config)# router bgp 65000 Device(config-router)# bmp initial-refresh delay 30 Device(config-router)# bmp buffer-size 2048 Device(config-router)# end
The following example show how to enter BMP server configuration mode and initiate connection between a specific BMP server with the BGP BMP neighbors. In this example, connection to clients is initiated from BMP servers 1 and 2 along with configuration of the monitoring parameters:
Device> enable Device# configure terminal Device(config)# router bgp 65000 Device(config-router)# bmp server 1 Device(config-router-bmpsrvr)# activate Device(config-router-bmpsrvr)# address 10.1.1.1 port-number 8000 Device(config-router-bmpsrvr)# description LINE SERVER1 Device(config-router-bmpsrvr)# failure-retry-delay 40 Device(config-router-bmpsrvr)# flapping-delay 120 Device(config-router-bmpsrvr)# initial-delay 20 Device(config-router-bmpsrvr)# set ip dscp 5 Device(config-router-bmpsrvr)# stats-reporting-period 30 Device(config-router-bmpsrvr)# update-source ethernet 0/0 Device(config-router-bmpsrvr)# exit-bmp-server-mode Device(config-router)# bmp server 2 Device(config-router-bmpsrvr)# activate Device(config-router-bmpsrvr)# address 20.1.1.1 port-number 9000 Device(config-router-bmpsrvr)# description LINE SERVER2 Device(config-router-bmpsrvr)# failure-retry-delay 40 Device(config-router-bmpsrvr)# flapping-delay 120 Device(config-router-bmpsrvr)# initial-delay 20 Device(config-router-bmpsrvr)# set ip dscp 7 Device(config-router-bmpsrvr)# stats-reporting-period 30 Device(config-router-bmpsrvr)# update-source ethernet 2/0 Device(config-router-bmpsrvr)# exit-bmp-server-mode Device(config-router)# end
The following is sample output from the show ip bgp bmp server command for server number 1. The attributes displayed are configured in the BMP server configuration mode:
Device# show ip bgp bmp server 1 Print detailed info for 1 server number 1. bmp server 1 address: 10.1.1.1 port 8000 description SERVER1 up time 00:06:22 session-startup route-refresh initial-delay 20 failure-retry-delay 40 flapping-delay 120 activated
The following is sample output from the show ip bgp bmp server command for server number 2. The attributes displayed are configured in the BMP server configuration mode:
Device# show ip bgp bmp server 2 Print detailed info for 1 server number 2. bmp server 2 address: 20.1.1.1 port 9000 description SERVER2 up time 00:06:23 session-startup route-refresh initial-delay 20 failure-retry-delay 40 flapping-delay 120 activated
The following is sample output from the show ip bgp bmp server summary command after deactivating the BMP server 1 and 2 connections:
Device# show ip bgp bmp server summary Number of BMP servers configured: 2 Number of BMP neighbors configured: 10 Number of neighbors on TransitionQ: 0, MonitoringQ: 0, ConfigQ: 0 Number of BMP servers on StatsQ: 0 BMP Refresh not in progress, refresh not scheduled Initial Refresh Delay configured, refresh value 30s BMP buffer size configured, buffer size 2048 MB, buffer size bytes used 0 MB ID Host/Net Port TCB Status Uptime MsgSent LastStat 1 10.1.1.1 8000 0x0 Down 0 2 20.1.1.1 9000 0x0 Down 0
The following is sample output from the show ip bgp bmp neighbors command, which shows the status of the BGP BMP neighbors after reactivating the BMP server 1 and 2 connections:
Device# show ip bgp bmp server neighbors Number of BMP neighbors configured: 10 BMP Refresh not in progress, refresh not scheduled Initial Refresh Delay configured, refresh value 30s BMP buffer size configured, buffer size 2048 MB, buffer size bytes used 0 MB Neighbor PriQ MsgQ CfgSvr# ActSvr# RM Sent 30.1.1.1 0 0 1 2 1 2 16 2001:DB8::2001 0 0 1 2 1 2 15 40.1.1.1 0 0 1 2 1 2 26 2001:DB8::2002 0 0 1 2 1 2 15 50.1.1.1 0 0 1 2 1 2 16 60.1.1.1 0 0 1 2 1 2 26 2001:DB8::2002 0 0 1 1 9 70.1.1.1 0 0 2 2 12 Neighbor PriQ MsgQ CfgSvr# ActSvr# RM Sent 80.1.1.1 0 0 1 1 10 2001:DB8::2002 0 0 1 2 1 2 16
The following is sample output from the show ip bgp bmp server command for BMP server number 1 and 2. The statistics reporting interval on BMP server 1 and 2 has been set to 30 seconds, therefore each server receives statistics messages from its connected BGP BMP neighbor in each cycle of 30 seconds:
Device# show ip bgp bmp server summary Number of BMP servers configured: 2 Number of BMP neighbors configured: 10 Number of neighbors on TransitionQ: 0, MonitoringQ: 0, ConfigQ: 0 Number of BMP servers on StatsQ: 0 BMP Refresh not in progress, refresh not scheduled Initial Refresh Delay configured, refresh value 30s BMP buffer size configured, buffer size 2048 MB, buffer size bytes used 0 MB ID Host/Net Port TCB Status Uptime MsgSent LastStat 1 10.1.1.1 8000 0x2A98B07138 Up 00:38:49 162 00:00:09 2 20.1.1.1 9000 0x2A98E17C88 Up 00:38:49 46 00:00:04 Device# show ip bgp bmp server summary Number of BMP servers configured: 2 Number of BMP neighbors configured: 10 Number of neighbors on TransitionQ: 0, MonitoringQ: 0, ConfigQ: 0 Number of BMP servers on StatsQ: 0 BMP Refresh not in progress, refresh not scheduled Initial Refresh Delay configured, refresh value 30s BMP buffer size configured, buffer size 2048 MB, buffer size bytes used 0 MB ID Host/Net Port TCB Status Uptime MsgSent LastStat 1 10.1.1.1 8000 0x2A98B07138 Up 00:40:19 189 00:00:07 2 20.1.1.1 9000 0x2A98E17C88 Up 00:40:19 55 00:00:02
Note | If we configure several BGP BMP neighbors to be monitored by the BMP servers, for example 10, then 10 statistics messages are received by both servers in each periodic cycle that is configured. |
The following is sample output from the show running-config command, which shows the running configuration on the device:
Device# show running-config | section bmp bmp server 1 address 10.1.1.1 port-number 8000 description SERVER1 initial-delay 20 failure-retry-delay 40 flapping-delay 120 update-source Ethernet0/0 set ip dscp 3 activate exit-bmp-server-mode bmp server 2 address 20.1.1.1 port-number 9000 description SERVER2 initial-delay 20 failure-retry-delay 40 flapping-delay 120 update-source Ethernet2/0 set ip dscp 5 activate exit-bmp-server-mode bmp initial-refresh delay 30 bmp-activate all
The following example shows how to enable debugging of the various BMP attributes:
Device# debug ip bgp bmp event BGP BMP events debugging is on Device# debug ip bgp bmp neighbor BGP BMP neighbor debugging is on Device# debug ip bgp bmp server BGP BMP server debugging is on
The following is sample output from the show debugging command after you enable the BGP BMP server debugging:
Device# show debugging IP routing: BGP BMP server debugging is on Device# *Apr 8 21:04:13.164: BGPBMP: BMP server connection attempt timer expired for server 1 - 10.1.1.1/8000 *Apr 8 21:04:13.165: BGPBMP: BMP server 1 active open process success - 10.1.1.1/8000 *Apr 8 21:04:13.165: BGPBMP: TCP KA interval is set to 15 Device# *Apr 8 21:04:15.171: BGPBMP: Register read/write notification callbacks with BMP server 1 TCB - 10.1.1.1/8000 *Apr 8 21:04:15.171: BGPBMP: Initiation msg sent to BMP server 1 - 10.1.1.1/8000 *Apr 8 21:04:15.171: BGPBMP: BMP server 1 connection - 10.1.1.1/8000 up, invoke refresh event Device# *Apr 8 21:04:16.249: BGPBMP: BMP server connection attempt timer expired for server 2 - 20.1.1.1/9000 *Apr 8 21:04:16.249: BGPBMP: BMP server 2 active open process success - 20.1.1.1/9000 *Apr 8 21:04:16.249: BGPBMP: TCP KA interval is set to 15 *Apr 8 21:04:16.250: BGPBMP: Register read/write notification callbacks with BMP server 2 TCB - 20.1.1.1/9000 *Apr 8 21:04:16.250: BGPBMP: Initiation msg sent to BMP server 2 - 20.1.1.1/9000 *Apr 8 21:04:16.250: BGPBMP: BMP server 2 connection - 20.1.1.1/9000 up, invoke refresh event
Additional References for BGP Monitoring Protocol
Related Documents
Related Topic | Document Title |
---|---|
Cisco IOS commands |
|
BGP commands |
Technical Assistance
Description | Link |
---|---|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
Feature Information for BGP Monitoring Protocol
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.