You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operator-nexus/concepts-bmp-log-streaming.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.date: 04/01/2025
9
9
ms.custom: template-concept
10
10
---
11
11
12
-
##Introduction to BMP
12
+
# Introduction to BMP
13
13
14
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.
15
15
@@ -86,4 +86,4 @@ Nexus NF shall not support excluding the monitoring of peer-address of neighbor
86
86
Nexus shall support a maximum of four Network Monitors (BMP Stations).
87
87
88
88
## Next steps
89
-
[How to enable \ disable BMP log streaming](./howto-enable-disable-log-streaming.md)
89
+
[How to enable \ disable BMP log streaming](./howto-enable-log-streaming.md)
Copy file name to clipboardExpand all lines: articles/operator-nexus/howto-configure-bgp-prefix-limit-on-CE-devices.md
+21-20Lines changed: 21 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,19 +17,20 @@ BGP (Border Gateway Protocol) prefix limiting is an essential overload protectio
17
17
18
18
BGP prefix limits can be configured using two primary parameters:
19
19
20
-
-**max-routes (hard limits)**: This parameter sets the maximum number of prefixes a BGP router will accept from a neighbor. If the limit is exceeded, the BGP session with that neighbor is terminated to prevent overloading the router.
20
+
-**max-routes (hard limits)**: This parameter sets the maximum number of prefixes a BGP router accepts from a neighbor. If the limit is exceeded, the BGP session with that neighbor is terminated to prevent overloading the router.
21
21
22
-
-**warn-threshold (soft limits)**: The warn-threshold parameter sets a warning threshold below the max-routes limit. When the number of prefixes received from a neighbor exceeds this threshold, a warning is generated, but the BGP session is not terminated. This allows network administrators to take corrective action before the hard limit is reached.
22
+
-**warn-threshold (soft limits)**: The warn-threshold parameter sets a warning threshold below the max-routes limit. When the number of prefixes received from a neighbor exceeds this threshold, a warning is generated, but the BGP session isn't terminated. This policy allows network administrators to take corrective action before the hard limit is reached.
23
23
24
24
### Hard limits (max-routes)
25
25
26
-
The `max-routes` parameter specifies the maximum number of prefixes that a BGP router can accept from a neighbor. If the number exceeds this limit, the BGP session with that neighbor is terminated. This is a "hard" limit to protect the router from excessive load and to maintain network stability.
26
+
The `max-routes` parameter specifies the maximum number of prefixes that a BGP router can accept from a neighbor. If the number exceeds this limit, the BGP session with that neighbor is terminated. This threshold is a "hard" limit to protect the router from excessive load and to maintain network stability.
27
27
28
28
### Soft limits (warn-threshold)
29
29
30
-
The `warn-threshold` parameter is a "soft" limit. When the number of prefixes exceeds this threshold, a warning is triggered, but the BGP session remains active. This serves as a precautionary measure, allowing administrators to intervene before reaching the hard limit.
30
+
The `warn-threshold` parameter is a "soft" limit. When the number of prefixes exceeds this threshold, a warning is triggered, but the BGP session remains active. This safeguard serves as a precautionary measure, allowing administrators to intervene before reaching the hard limit.
31
+
32
+
To configure **BGP Prefix Limit** on **Customer Edge (CE)** devices for **Azure Operator Nexus**, follow the steps below. This configuration includes setting the prefix limits for BGP sessions to manage network stability and prevent the Nexus fabric from being overwhelmed when a tenant advertises excessive BGP routes.
31
33
32
-
To configure **BGP Prefix Limit** on **Customer Edge (CE)** devices for **Azure Operator Nexus**, follow the steps below. This includes configuring the prefix limits for BGP sessions to manage network stability and prevent the Nexus fabric from being overwhelmed when a tenant advertises excessive BGP routes.
33
34
34
35
### Prerequisites
35
36
@@ -45,9 +46,9 @@ To configure **BGP Prefix Limit** on **Customer Edge (CE)** devices for **Azure
45
46
46
47
You need to configure the BGP prefix limits using the parameters `maximumRoutes` and `threshold`.
47
48
48
-
-**`maximumRoutes`**: This defines the maximum number of BGP prefixes the router will accept from a BGP peer.
49
+
-**`maximumRoutes`**: This parameter defines the maximum number of BGP prefixes the router accepts from a BGP peer.
49
50
50
-
-**`threshold`**: This defines the warning threshold as a percentage of the `maximumRoutes`. When the number of prefixes exceeds this threshold, a warning is generated.
51
+
-**`threshold`**: This parameter defines the warning threshold as a percentage of the `maximumRoutes`. When the number of prefixes exceeds this threshold, a warning is generated.
51
52
52
53
#### Step 2: Configure on the CE device
53
54
@@ -67,15 +68,15 @@ This configuration will automatically restart the session after a defined idle t
67
68
68
69
-**Explanation**:
69
70
70
-
-**maximumRoutes**: 5000 routes is the limit for the BGP session.
71
+
-**maximumRoutes**: 5,000 routes are the limit for the BGP session.
71
72
72
-
-**threshold**: A warning is triggered when the prefix count reaches 80% (4000 routes).
73
+
-**threshold**: A warning is triggered when the prefix count reaches 80% (4,000 routes).
73
74
74
75
-**idleTimeExpiry**: If the session is shut down, it will restart automatically after 100 seconds of idle time.
75
76
76
77
##### Example 2: BGP prefix limit without automatic restart
77
78
78
-
This configuration will shut down the session when the maximum prefix limit is reached, but manual intervention is required to restart the session.
79
+
This configuration shuts down the session when the maximum prefix limit is reached, but manual intervention is required to restart the session.
79
80
80
81
```json
81
82
{
@@ -88,15 +89,15 @@ This configuration will shut down the session when the maximum prefix limit is r
88
89
89
90
-**Explanation**:
90
91
91
-
-**maximumRoutes**: 5000 routes is the limit for the BGP session.
92
+
-**maximumRoutes**: 5,000 routes are the limit for the BGP session.
92
93
93
-
-**threshold**: A warning is triggered when the prefix count reaches 80% (4000 routes).
94
+
-**threshold**: A warning is triggered when the prefix count reaches 80% (4,000 routes).
94
95
95
96
- No automatic restart; manual intervention is required to restart the session.
96
97
97
98
##### Example 3: Hard-Limit drop BGP sessions
98
99
99
-
This configuration will drop additional routes if the prefix limit is exceeded without maintaining a cache of the dropped routes.
100
+
This configuration drops extra routes if the prefix limit is exceeded without maintaining a cache of the dropped routes.
100
101
101
102
```json
102
103
{
@@ -108,13 +109,13 @@ This configuration will drop additional routes if the prefix limit is exceeded w
108
109
109
110
-**Explanation**:
110
111
111
-
-**maximumRoutes**: 5000 routes is the limit for the BGP session.
112
+
-**maximumRoutes**: 5,000 routes are the limit for the BGP session.
112
113
113
-
- Once the limit is reached, the CE device will drop any additional prefixes received from the BGP peer.
114
+
- Once the limit is reached, the CE device drops any extra prefixes received from the BGP peer.
114
115
115
116
##### Example 4: Hard-Limit warning only
116
117
117
-
This configuration will generate a warning once the prefix count reaches a certain percentage of the maximum limit but will not shut down the session.
118
+
This configuration generates a warning once the prefix count reaches a certain percentage of the maximum limit but does not shut down the session.
118
119
119
120
```json
120
121
{
@@ -128,11 +129,11 @@ This configuration will generate a warning once the prefix count reaches a certa
128
129
129
130
-**Explanation**:
130
131
131
-
-**maximumRoutes**: 8000 routes is the limit for the BGP session.
132
+
-**maximumRoutes**: 8,000 routes are the limit for the BGP session.
132
133
133
-
-**threshold**: A warning is generated when the prefix count reaches 75% (6000 routes).
134
+
-**threshold**: A warning is generated when the prefix count reaches 75% (6,000 routes).
134
135
135
-
- The session is not shut down. This configuration is used to only generate a warning without taking any session-terminating action.
136
+
- The session isn't shut down. This configuration is used to only generate a warning without taking any session-terminating action.
136
137
137
138
#### Step 3: Apply Configuration Using Azure CLI
138
139
@@ -190,6 +191,6 @@ For external network configuration, only the **hard-limit warning-only** option
190
191
191
192
### NNI Option A:
192
193
193
-
For NNI Option A, only a single peer group is allowed. IPv4 over IPv6 and vice versa are not supported. Warning-only mode is available for handling prefix limits.
194
+
For NNI Option A, only a single peer group is allowed. IPv4 over IPv6 and vice versa aren't supported. Warning-only mode is available for handling prefix limits.
194
195
195
196
By following this guide, you can configure BGP prefix limits effectively to protect your network from overload and ensure that BGP sessions are properly managed for both internal and external networks.
description: instructions on enabling \ disabling BMP log streaming various Network Fabric resource.
4
4
ms.service: azure-operator-nexus
5
5
ms.custom: template-how-to, devx-track-azurecli
6
6
ms.topic: how-to
7
7
ms.date: 11/14/2024
8
-
author: susantjrao
8
+
author: sushantjrao
9
9
ms.author: sushrao
10
10
---
11
11
12
12
# BMP log streaming
13
+
13
14
This guide provides you with instructions on enabling \ disabling BMP log streaming various Network Fabric resources.
14
15
15
-
## Enabling BMP Log Streaming for the New Deployment
16
+
## Enabling BMP log streaming for the new deployment
16
17
17
18
-**Create Network Fabric resource:** Begin by creating Network Fabric (NF) resource. This will serve as the foundation for your deployment.
18
19
19
20
-**Create Network Monitor resource:** Next, create a Network Monitor resource and associate the Scope ID with the NF Resource ID. This step ensures that the monitoring is correctly linked to the network fabric.
20
21
21
-
-**Create NNI with BMP Configuration:** Create a Network-to-Network Interface (NNI) by associating it with the NF Resource ID. *(Please refer to the below detailed ARM API payload guide for more information)*
22
+
-**Create NNI with BMP configuration:** Create a Network-to-Network Interface (NNI) by associating it with the NF Resource ID.
23
+
24
+
> [!Note]
25
+
> Refer to the below detailed ARM API payload guide for more information
22
26
23
27
-**Provision Network Fabric:** Provision the Network Fabric to apply the configurations and make the network operational.
24
28
25
-
-**Generate BMP Stations Configuration** The Nexus NF will generate the BMP stations configuration on the Customer Edge (CE) devices only.
29
+
-**Generate BMP stations configuration** The Nexus NF will generate the BMP stations configuration on the Customer Edge (CE) devices only.
26
30
27
-
## Enabling BMP Log Streaming for the Existing Deployment
31
+
## Enabling BMP log streaming for the existing deployment
28
32
29
33
This case involves enabling BMP log streaming on NF, which has already been deployed using the supported NF Version. Since this is based on an ARM API user-driven input, the supported NF Version will also support BMP Log Streaming through the NF Patch Update workflow.
30
34
@@ -33,7 +37,10 @@ This case involves enabling BMP log streaming on NF, which has already been depl
33
37
-**Create Network Monitor resource:**
34
38
Create a Network Monitor resource and link the Scope ID to the NF Resource ID to ensure proper monitoring.
35
39
36
-
-**Perform Patch on NNI:** Update the Network-to-Network Interface (NNI) by applying a patch. Select `bmpConfiguration` under `OptionBLayerConfiguration` and set `configurationState` to "Enabled" for BMP logging of the NNI peer-group neighbor address. *(Please refer to the below detailed ARM API payload guide for more information)*
40
+
-**Perform Patch on NNI:** Update the Network-to-Network Interface (NNI) by applying a patch. Select `bmpConfiguration` under `OptionBLayerConfiguration` and set `configurationState` to "Enabled" for BMP logging of the NNI peer-group neighbor address.
41
+
42
+
> [!Note]
43
+
> Refer to the below detailed ARM API payload guide for more information
37
44
38
45
-**Perform `Fabric Commit` operation:** Execute the "Fabric Commit" operation to apply configurations and activate the network.
39
46
@@ -46,7 +53,28 @@ This section provides a detailed guide on how to perform CRUD (Create, Read, Upd
46
53
The following property is defined under ARM API version `2024-06-15-preview`
connection mode active port <example-port> >>> Example for BMP Monitoring station with connection mode active
70
98
```
71
99
72
-
## How to Enable/Disable BMP Log Streaming under NNI
100
+
## How to Enable/Disable BMP log streaming under NNI
101
+
102
+
### Enabling BMP log streaming for NNI
73
103
74
-
### Enabling BMP Log Streaming for NNI
75
104
To enable BMP Log streaming under NNI, run the following Azure CLI command. This example enables BMP Log streaming for **infra-vpn** (vrf **INFRA-MGMT**), **workload-vpn** (vrf **WORKLOAD-MGMT**) with **OptionB**, and **L3ISD External Network OptionB**.
## How to Enable/Disable BMP Log Streaming for L3ISD External Network OptionA
105
144
106
145
### Enabling BMP Log Streaming for L3ISD External Network OptionA
146
+
107
147
To enable BMP Log streaming for L3ISD External Network OptionA, run the following Azure CLI command. This example enables BMP Log streaming for the specified external network.
0 commit comments