Log More Routing Events in the BGP Monitoring Protocol (BMP)

Introduction BGP Adj-RIB-In, Loc-RIB, and Adj-RIB-Out are generated through BGP route exchange and routing policy processing. The BGP Monitoring Protocol (BMP) provides comprehensive monitoring for BGP Adj-RIB-In , BGP Loc-RIB , and BGP Adj-RIB-Out . The Route Event Logging (REL) message defined in is designed to deliver event-driven fault logs and runtime status information from network devices to BMP monitoring servers. In modern networks, BGP FlowSpec and BGP SR Policy are widely deployed for traffic filtering, redirection and segment routing traffic engineering. However, existing BMP REL mechanisms lack dedicated event logging for common failure scenarios of these advanced BGP features. This document supplements new REL event types to cover typical abnormal failures of BGP FlowSpec and BGP SR Policy, filling the monitoring gap for policy control and forwarding execution anomalies.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

BGP FlowSpec Routing Event Extensions The Log Action TLV is defined in . The first byte defines the nature of the logging event, and additional data may follow depending on the code point. The following code points are defined for BGP FlowSpec in this document:

TBD1 = Redirect-to-VRF-Fail. The BGP FlowSpec redirect-to-VRF action is defined in . This event indicates that a received FlowSpec redirect-to-VRF action cannot be resolved, installed, or executed on the monitored device for the target Virtual Routing and Forwarding (VRF) instance. For example, the target VRF instance may be unavailable or the corresponding redirect action may fail during local processing.
TBD2 = Redirect-to-Nexthop-Fail. The BGP FlowSpec redirect-to-IP action is defined in . This event indicates that a received FlowSpec redirect-to-IP action cannot be resolved, installed, or executed on the monitored device for the target IPv4 or IPv6 next hop.
TBD3 = Redirect-to-SR-Policy-Fail. This event indicates that a received FlowSpec action that redirects traffic to an SR Policy cannot be resolved, installed, or executed on the monitored device. For example, the referenced SR Policy may be unavailable or may not provide a usable forwarding behavior when the FlowSpec action is processed.
TBD4 = FlowSpec-Validation-Fail. The BGP FlowSpec validation procedure is defined in . This event indicates that a received FlowSpec route fails the FlowSpec validation procedure on the monitored device. This event is distinct from failures that occur while locally resolving, installing, or executing a FlowSpec traffic action.

BGP SR Policy Routing Event Extensions The Log Action TLV is defined in . The first byte defines the nature of the logging event, and additional data may follow depending on the code point. The following code points are defined for BGP SR Policies in this document:

TBD5 = Invalid-Candidate-Path. This event indicates that a candidate path is considered invalid. The validity of a candidate path is described in Section 5 of .
TBD6 = Invalid-Segment-List. This event indicates that a segment list of a candidate path is considered invalid. The validity of a segment list is described in Section 5 of .
TBD7 = Exceeded-Spec-Limit. This event indicates violations including exceeding the maximum number of SR Policies or Segment Lists.

Operational Considerations A monitored device may receive FlowSpec routes and SR Policy routes from controllers, route reflectors, or adjacent BGP peers. When the device detects a failure while validating or locally processing those routes or their associated actions, it reports the corresponding event and diagnostic information to the configured BMP monitoring collector using a BMP REL message. BMP monitoring collectors SHOULD record, analyze, and correlate these extended routing events with the relevant BMP route or policy context when available. These events can be used for real-time alarming and offline fault diagnosis. Appropriate caution SHOULD be taken when picking routing events to report, as next-hop related updates may produce heavy message loads during network instability. Mitigation measures SHOULD be deployed on both reporting and receiving sides. For example, local endpoints can apply event filtering controls, while receivers maintain corresponding processing mechanisms to handle potential high-volume event bursts gracefully. The failure events defined in this document do not define a corresponding recovery indication. Operators should use these events together with other BMP information and local operational state to determine whether the reported condition is still present.

Security Considerations This document inherits all security requirements and considerations documented in Section 11 of . BMP control sessions SHOULD only be established between authenticated and trusted monitoring devices to prevent unauthorized access to network internal routing information. No new protocol interactions or message modes are introduced in this extension. Therefore, no additional security risks are introduced beyond the baseline BMP protocol.

IANA Considerations This document requests IANA to assign seven new code points in the BMP Log Action TLV Registry established by . The requested code point assignments are as follows:

Redirect-to-VRF-Fail (TBD1)
Redirect-to-Nexthop-Fail (TBD2)
Redirect-to-SR-Policy-Fail (TBD3)
FlowSpec-Validation-Fail (TBD4)
Invalid-Candidate-Path (TBD5)
Invalid-Segment-List (TBD6)
Exceeded-Spec-Limit (TBD7)

After permanent code points are allocated, all TBD markers will be replaced in subsequent document revisions.

Acknowledgements Many thanks to the comments from Jeffrey Haas and Narasimha Prasad.