Skip to main content
Cisco Meraki Documentation

Dynamic Protocol Status

Dynamic Protocol Status

  • Dynamic Protocol Status page requires a minimum MX firmware version of 18.2.
  • Currently only BGP peers are tracked within the Dynamic Protocol Status page. Hence, BGP must be configured to enable this page.

The Security & SD-WAN > Monitor > Dynamic Protocol Status page provides status information about configured dynamic routing peers.

Screenshot 2024-08-13 at 1.54.34 PM.png

BGP Peers

The peers are displayed in a table containing the following columns, the table can be filtered either via name, status or type of peer.

Screenshot 2024-08-13 at 1.50.14 PM.png 

  • Peer status: Indicates the current status of the peer, supports the following states:

    • Established
      • Once the BGP neighbor adjacency is established. BGP routers exchange routing information by sending update packets. Each time MX receives a keepalive or update message, the hold timer is reset. However, if the MX receive a notification message, the link goes back to the idle state.
    • Idle
      • In the idle state, BGP awaits a 'start event'. This event occurs when a new BGP neighbor neighbor is configured or an established BGP peering is reset. Local MX will establish a three-way TCP handshake to the remote BGP neighbor. If successful, BGP transitions to the Connect state.
    • Connect
      • If the three-way TCP handshake fails, the link will continue to Active state (retry) . If successful, the link status will proceed to OpenSent state.
    • Active
    • OpenSent
      • Open messages are exchanged between the neighbors to check for errors. This interaction will determine whether to use EBGP or IBGP. After verifying neighbor parameters, the link will move to OpenConfirm state, and BGP will initate keepalive messages.
    • OpenConfirm
      • When the neighbor sends and receives the keepalive messages (ACK), the link will proceed to Established state.
    • Close
    • Down
    • Passive
    • Removed
    • Unreachable
    • Absent
  • Peer: The IPv4 or IPv6 address of the peer. 
  • AS Number: AS Number of the peer.
  • Peer type: iBGP or eBGP relationship to the peer.
  • # Routes: Number of routes learned from peer. 
    • When eBGP is enabled the MX and the peer is IPv6 enabled, will have a peer entry for both the IPv4 and IPv6 address.
  • Status changes:
    • Status change state tracked across the time period specified at the top of the page. 

Monitoring

Users have the option to filter, search, and find historical details about their BGP peers:

Screenshot 2024-08-13 at 4.20.06 PM.png 

Screenshot 2024-08-13 at 4.17.37 PM.png

  • Was this article helpful?