Skip to content

Commit 7e77a3a

Browse files
authored
Merge pull request #300264 from paulth1/network-fabric-articles
[AQ] edit pass: Network fabric articles
2 parents 0f5b98a + 7852dd2 commit 7e77a3a

7 files changed

+326
-350
lines changed
Lines changed: 47 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: BMP log streaming in Azure Operator Nexus Network Fabric
2+
title: BMP Log Streaming in Azure Operator Nexus Network Fabric
33
description: An overview of BGP Monitoring Protocol (BMP), its importance, and key components for effective log monitoring.
44
author: sushantjrao
55
ms.author: sushrao
@@ -11,79 +11,84 @@ ms.custom: template-concept
1111

1212
# Introduction to BMP
1313

14-
The **BGP Monitoring Protocol (BMP)** is a protocol designed to monitor BGP sessions. It provides a standardized method for collecting information about BGP sessions, which can be used for analysis, troubleshooting, and ensuring the stability and security of the network.
14+
The BGP Monitoring Protocol (BMP) is designed to monitor Border Gateway Protocol (BGP) sessions. BMP provides a standardized method for collecting information about BGP sessions. You can use this information for analysis, troubleshooting, and helping to ensure the stability and security of the network.
1515

16-
The BGP Monitoring Protocol (BMP) allows a monitoring station to connect to a router and collect all the BGP announcements received from the router's BGP peers. The announcements are sent to the station in the form of **BMP Route Monitoring messages** formed from path information in the router's **BGP Adj-Rib-In tables**. A BMP speaker may choose to send either **pre-policy routes, post-policy routes, or both**.
16+
BMP allows a monitoring station to connect to a router and collect all the BGP announcements received from the router's BGP peers. The announcements are sent to the station in the form of BMP route monitoring messages formed from path information in the router's BGP Adj-Rib-In tables. A BMP speaker might choose to send either prepolicy routes, post-policy routes, or both.
1717

18-
BMP is **unidirectional**: BMP sends messages only from the router to the monitoring station, never the other way around. The router's configuration controls the information sent. Besides Route Monitoring messages, BMP also sends these messages:
18+
BMP is unidirectional. BMP sends messages only from the router to the monitoring station, never the other way around. The router's configuration controls the information that gets sent. Besides route monitoring messages, BMP also sends these messages:
1919

2020
- **Initiation**: Sent at the beginning of a session and used to identify the router.
2121
- **Termination**: Optionally sent at the end of a session to indicate why the session is being closed.
22-
- **Peer Up**: Used to indicate if a BGP peer is in **Established** state.
23-
- **Peer Down**: Used to indicate that a BGP peer has gone out of **Established** state.
22+
- **Peer Up**: Used to indicate if a BGP peer is in an **Established** state.
23+
- **Peer Down**: Used to indicate that a BGP peer is no longer in an **Established** state.
2424

25-
Connections between the router and BMP stations use **TCP**. The router can either passively listen for incoming connections from a station or actively initiate them, configurable per station. Only **one connection per BMP station** is allowed at a time. If a station reconnects, the router closes the old session and starts a new BMP session with the new connection.
25+
Connections between the router and BMP stations use the Transmission Control Protocol. The router can passively listen for incoming connections from a station or actively initiate them, configurable per station. Only one connection per BMP station is allowed at a time. If a station reconnects, the router closes the old session and starts a new BMP session with the new connection.
2626

2727
## Importance of BMP log monitoring
2828

29-
BMP log monitoring is crucial for maintaining the **health and performance** of BGP sessions. By continuously monitoring BMP logs, network administrators can detect anomalies, identify potential issues, and take proactive measures to prevent network disruptions. Effective BMP log monitoring helps in:
29+
BMP log monitoring is crucial for maintaining the health and performance of BGP sessions. By continuously monitoring BMP logs, network administrators can detect anomalies, identify potential issues, and take proactive measures to prevent network disruptions. Effective BMP log monitoring helps to:
3030

31-
- Ensuring the **stability and reliability** of BGP sessions.
32-
- Detecting and mitigating **security threats**.
33-
- Analyzing **network performance** and identifying optimization opportunities.
34-
- Troubleshooting and resolving **BGP-related issues** promptly.
31+
- Ensure the stability and reliability of BGP sessions.
32+
- Detect and mitigate security threats.
33+
- Analyze network performance and identifying optimization opportunities.
34+
- Troubleshoot and resolve BGP-related issues promptly.
3535

36-
## Key Components of BMP log monitoring
36+
## Key components of BMP log monitoring
3737

38-
### **1. Data collection**
39-
BMP logs provide detailed information about BGP sessions, including **route updates, peer status, and error messages**. Collecting this data is the first step in effective BMP log monitoring.
38+
### Data collection
4039

41-
### **2. Data storage**
42-
Storing BMP logs in a **centralized and secure location** is essential for easy access and analysis. This can be achieved using **log management systems** or **databases**.
40+
BMP logs provide detailed information about BGP sessions, including route updates, peer status, and error messages. Collecting this data is the first step in effective BMP log monitoring.
4341

44-
### **3. Data analysis**
45-
Analyzing BMP logs helps in identifying **patterns, trends, and anomalies**. Advanced analytics tools and techniques, such as **machine learning**, can be used to gain deeper insights into the network's behavior.
42+
### Data storage
4643

47-
### **4. Alerting and reporting**
48-
Setting up **alerts** for specific events or thresholds in BMP logs ensures that network administrators are **promptly notified** of any issues. **Regular reports** provide a comprehensive overview of the network's health and performance.
44+
Storing BMP logs in a centralized and secure location is essential for easy access and analysis. You can use log management systems or databases.
45+
46+
### Data analysis
47+
48+
Analyzing BMP logs helps to identify patterns, trends, and anomalies. You can use advanced analytics tools and techniques like machine learning to gain deeper insights into the network's behavior.
49+
50+
### Alerting and reporting
51+
52+
Setting up alerts for specific events or thresholds in BMP logs ensures that network administrators are promptly notified of any issues. Regular reports provide a comprehensive overview of the network's health and performance.
4953

5054
## Restrictions and limitations of BMP log streaming
5155

52-
### Nexus Network Fabric (NF) restrictions
56+
### Azure Operator Nexus Network Fabric restrictions
5357

54-
Nexus NF shall not enable BMP Log streaming for the following BGP neighbors:
58+
Azure Operator Nexus Network Fabric doesn't enable BMP log streaming for the following BGP neighbors:
5559

56-
- INTERCEGLOBAL
57-
- INTERCEEVPN
58-
- INTERCEOPTION-A
59-
- CETORUNDERLAY
60-
- EVPN_OVERLAY
60+
- `INTERCEGLOBAL`
61+
- `INTERCEEVPN`
62+
- `INTERCEOPTION-A`
63+
- `CETORUNDERLAY`
64+
- `EVPN_OVERLAY`
6165

62-
Nexus NF shall not support BMP Log streaming for RT-Membership and EVPN Address-family.
66+
Azure Operator Nexus Network Fabric doesn't support BMP log streaming for `RT-Membership` and `EVPN Address-family`.
6367

64-
Nexus NF shall not support monitoring address-families at the station level, even though Nexus NF provides ARM API at the station level by facilitating the address-family. This limitation exists because Arista supports BGP Global level rather than BMP Station level.
68+
Azure Operator Nexus Network Fabric doesn't support monitoring address families at the station level, even though Azure Operator Nexus Network Fabric provides the Azure Resource Manager API at the station level by facilitating the address family. This limitation exists because Arista supports the BGP global level rather than the BMP station level.
6569

6670
### L3ISD requirements
6771

68-
- L3ISD must be enabled prior to associating the L3ISDs as Monitored Networks of any Network Monitors.
69-
- L3ISD must be enabled prior to associating the L3ISDs Internal/External Network as Station Network of any Network Monitors.
70-
- L3ISD shall not be disabled if the respective L3ISD internal/external network is associated under Station Network of any Network Monitors.
72+
- Layer 3 isolation domain (L3ISD) must be enabled before the L3ISDs are associated as monitored networks of Network Monitor.
73+
- L3ISD must be enabled before the L3ISDs internal/external networks are associated as the station networks of Network Monitor.
74+
- L3ISD must not be disabled if the respective L3ISD internal/external network is associated under the station network of Network Monitor.
7175

7276
### Unsupported features
7377

74-
Nexus shall not support the following features:
78+
Azure Operator Nexus doesn't support the following features:
7579

76-
- BMP support for VRF Filtering.
77-
- BMP support for local rib VPN imported routes.
80+
- BMP support for virtual routing and forwarding (VRF) filtering.
81+
- BMP support for local rib virtual private network imported routes.
7882
- BMP support for exporting Adj-Rib-Out.
7983

80-
### Peer-Address monitoring
84+
### Peer-address monitoring
85+
86+
Azure Operator Nexus Network Fabric doesn't support excluding the monitoring of peer addresses of neighbor groups where the neighbor group is configured with a BGP listen range. Arista doesn't support excluding the monitoring of certain addresses of neighbors that are configured with a BGP listen range.
8187

82-
Nexus NF shall not support excluding the monitoring of peer-address of neighbor groups where the neighbor group is configured with BGP listen range. This limitation is due to Arista's inability to support excluding the monitoring of certain addresses of neighbors configured with BGP listen-range.
88+
### Network Monitor
8389

84-
### Network monitors
90+
Azure Operator Nexus supports a maximum of four instances of Network Monitor (BMP stations).
8591

86-
Nexus shall support a maximum of four Network Monitors (BMP Stations).
92+
## Related content
8793

88-
## Next steps
89-
[How to enable / disable BMP log streaming](./howto-enable-log-streaming.md)
94+
- [Enable or disable BMP log streaming](./howto-enable-log-streaming.md)

0 commit comments

Comments
 (0)