edit pass: network-fabric-articles

Author: paulth1

articles/operator-nexus/concepts-bmp-log-streaming.md

@@ -13,14 +13,14 @@ ms.custom: template-concept
 
 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.
 
-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 pre-policy routes, post-policy routes, or both.
+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.
 
 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:
 
 - **Initiation**: Sent at the beginning of a session and used to identify the router.
 - **Termination**: Optionally sent at the end of a session to indicate why the session is being closed.
-- **Peer Up**: Used to indicate if a BGP peer is in **Established** state.
-- **Peer Down**: Used to indicate that a BGP peer is no longer in **Established** state.
+- **Peer Up**: Used to indicate if a BGP peer is in an **Established** state.
+- **Peer Down**: Used to indicate that a BGP peer is no longer in an **Established** state.
 
 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.
 
@@ -69,9 +69,9 @@ Azure Operator Nexus Network Fabric doesn't support monitoring address families
 
 ### L3ISD requirements
 
-- Layer 3 Isolation Domain (L3ISD) must be enabled before associating the L3ISDs as monitored networks of any network monitors.
-- L3ISD must be enabled before associating the L3ISDs internal/external network as the station network of any network monitors.
-- L3ISD must not be disabled if the respective L3ISD internal/external network is associated under the station network of any network monitors.
+- Layer 3 isolation domain (L3ISD) must be enabled before the L3ISDs are associated as monitored networks of Network Monitor.
+- L3ISD must be enabled before the L3ISDs internal/external networks are associated as the station networks of Network Monitor.
+- L3ISD must not be disabled if the respective L3ISD internal/external network is associated under the station network of Network Monitor.
 
 ### Unsupported features
 
@@ -83,11 +83,11 @@ Azure Operator Nexus doesn't support the following features:
 
 ### Peer-address monitoring
 
-Azure Operator Nexus Network Fabric doesn't support excluding the monitoring of peer-address of neighbor groups where the neighbor group is configured with BGP listen range. Arista doesn't support excluding the monitoring of certain addresses of neighbors that are configured with BGP listen range.
+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.
 
-### Network monitors
+### Network Monitor
 
-Azure Operator Nexus supports a maximum of four Network Monitors (BMP stations).
+Azure Operator Nexus supports a maximum of four instances of Network Monitor (BMP stations).
 
 ## Related content
 

articles/operator-nexus/howto-configure-bgp-prefix-limit-on-customer-edge-devices.md

@@ -1,5 +1,5 @@
 ---
-title: Configure BGP Prefix Limit on Customer Edge Devices for Azure Operator Nexus
+title: Configure BGP Prefix Limit on CE Devices for Azure Operator Nexus
 description: Learn the process for configuring a BGP prefix limit on customer edge (CE) devices for Azure Operator Nexus.
 author: sushantjrao 
 ms.author: sushrao
@@ -11,7 +11,7 @@ ms.custom: template-how-to, devx-track-azurecli
 
 # BGP prefix limiting overview
 
-Border Gateway Protocol (BGP) prefix limiting is an essential overload protection mechanism for customer edge (CE) devices. It helps prevent the Nexus fabric from being overwhelmed when a Nexus tenant advertises an excessive number of BGP routes into a Nexus virtual routing and forwarding (VRF) instance. This feature helps to ensure network stability and security by controlling the number of prefixes that are received from BGP peers.
+Border Gateway Protocol (BGP) prefix limiting is an essential overload protection mechanism for customer edge (CE) devices. It helps prevent the Azure Operator Nexus fabric from being overwhelmed when an Azure Operator Nexus tenant advertises an excessive number of BGP routes into an Azure Operator Nexus virtual routing and forwarding (VRF) instance. This feature helps to ensure network stability and security by controlling the number of prefixes that are received from BGP peers.
 
 ## Configuration of BGP prefix limits
 
@@ -176,8 +176,8 @@ The platform supports layer 3 isolation domain (`L3IsolationDomain`) for tenant
 
 For external network configuration, only the hard-limit `warning-only` option is supported. Nexus supports this configuration via the Azure Resource Manager API under `NNI optionBlayer3Configuration` with the `maximumRoutes` parameter.
 
-### Network-to-network interface option A
+### NNI option A
 
-For network-to-network interface option A, only a single peer group is allowed. IPv4 over IPv6 and vice versa aren't supported. The `warning-only` mode is available for handling prefix limits.
+For network-to-network interface (NNI) option A, only a single peer group is allowed. IPv4 over IPv6 and vice versa aren't supported. The `warning-only` mode is available for handling prefix limits.
 
 By following the steps in this article, you can configure BGP prefix limits effectively to protect your network from overload. You can help to ensure that BGP sessions are properly managed for both internal and external networks.

articles/operator-nexus/howto-enable-log-streaming.md

@@ -11,33 +11,33 @@ ms.author: sushrao
 
 # BMP log streaming
 
-This article shows you how to enable or disable Border Gateway Protocol (BGP) Monitoring Protocol (BMP) log streaming for various Azure Operator Nexus Network Fabric resources.
+This article shows you how to enable or disable BGP Monitoring Protocol (BMP) log streaming for various Azure Operator Nexus Network Fabric resources.
 
 ## Enable BMP log streaming for the new deployment
 
-- **Create an Azure Operator Nexus Network Fabric resource:** To begin, create an Azure Operator Nexus Network Fabric resource. This resource serves as the foundation for your deployment.
-- **Create a Network Monitor resource:** Next, create a Network Monitor resource and associate the scope ID with the Azure Operator Nexus Network Fabric resource ID. This step ensures that the monitoring is correctly linked to the network fabric.
-- **Create a network-to-network interface (NNI) with BMP configuration:** Create an NNI by associating it with the Azure Operator Nexus Network Fabric resource ID.
+1. Create an Azure Operator Nexus Network Fabric resource. To begin, create an Azure Operator Nexus Network Fabric resource. This resource serves as the foundation for your deployment.
+1. Create a Network Monitor resource. Next, create a Network Monitor resource and associate the scope ID with the Azure Operator Nexus Network Fabric resource ID. This step ensures that the monitoring is correctly linked to the network fabric.
+1. Create a network-to-network interface (NNI) with BMP configuration. Create an NNI by associating it with the Azure Operator Nexus Network Fabric resource ID.
 
-> [!NOTE]
-> For more information, see the following Azure Resource Manager API payload guide.
+   > [!NOTE]
+   > For more information, see the following Azure Resource Manager API payload guide.
 
-- **Provision Azure Operator Nexus Network Fabric:** Azure Operator Nexus Network Fabric applies the configurations and makes the network operational.
-- **Generate BMP stations configuration:** Azure Operator Nexus Network Fabric configures BMP stations on the CE devices only.
+1. Provision Azure Operator Nexus Network Fabric. Azure Operator Nexus Network Fabric applies the configurations and makes the network operational.
+1. Generate BMP stations configuration. Azure Operator Nexus Network Fabric configures BMP stations on the CE devices only.
 
 ## Enable BMP log streaming for the existing deployment
 
 This case involves enabling BMP log streaming on Azure Operator Nexus Network Fabric, which is already deployed by using the supported Azure Operator Nexus Network Fabric version. This approach is based on an Azure Resource Manager API user-driven input. The supported Azure Operator Nexus Network Fabric version also supports BMP log streaming through the Azure Operator Nexus Network Fabric Patch Update workflow.
 
-- **Create an Azure Operator Nexus Network Fabric resource:** Create the Azure Operator Nexus Network Fabric resource by using the latest supported version. If your version is outdated, upgrade it to the supported version.
-- **Create a Network Monitor resource:** To ensure proper monitoring, create an Azure Operator Nexus Network Fabric resource. Link the scope ID to the Azure Operator Nexus Network Fabric resource ID.
-- **Perform a patch on NNI:** Apply a patch to update the NNI. Under `OptionBLayerConfiguration`, select `bmpConfiguration` and set `configurationState` to `Enabled` for BMP logging of the NNI peer-group neighbor address.
+1. Create an Azure Operator Nexus Network Fabric resource. Create the Azure Operator Nexus Network Fabric resource by using the latest supported version. If your version is outdated, upgrade it to the supported version.
+1. Create a Network Monitor resource. To ensure proper monitoring, create an Azure Operator Nexus Network Fabric resource. Link the scope ID to the Azure Operator Nexus Network Fabric resource ID.
+1. Perform a patch on NNI. Apply a patch to update the NNI. Under `OptionBLayerConfiguration`, select `bmpConfiguration` and set `configurationState` to `Enabled` for BMP logging of the NNI peer-group neighbor address.
 
-> [!NOTE]
-> For more information, see the following Azure Resource Manager API payload guide.
+   > [!NOTE]
+   > For more information, see the following Azure Resource Manager API payload guide.
 
-- **Perform a Fabric Commit operation:** To apply configurations and activate the network, run the `Fabric Commit` operation.
-- **Generate BMP stations configuration:** Azure Operator Nexus Network Fabric configures BMP stations on the CE devices only.
+1. Perform a Fabric Commit operation. To apply configurations and activate the network, run the `Fabric Commit` operation.
+1. Generate BMP stations configuration. Azure Operator Nexus Network Fabric configures BMP stations on the CE devices only.
 
 ## Network Monitor CRUD operations for BMP log streaming