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
Micro-BFD (Bidirectional Forwarding Detection) is a lightweight protocol designed to quickly detect failures between adjacent network devices, such as routers or switches, with minimal overhead. This guide provides step-by-step instructions to enable Micro-BFD on Customer Edge (CE) and Provider Edge (PE) devices.
14
+
Micro-BFD (Bidirectional Forwarding Detection) is a lightweight protocol designed to rapidly detect failures between adjacent network devices, such as routers or switches, with minimal overhead. This guide provides step-by-step instructions to enable Micro-BFD on Customer Edge (CE) and Provider Edge (PE) devices.
15
15
16
16
## Prerequisites
17
17
18
-
Before enabling Micro-BFD, perform the following steps:
18
+
Ensure the following prerequisites are met before enabling Micro-BFD:
19
19
20
-
- Both CE and PE devices are configured with the required Micro-BFD settings.
20
+
- Both CE and PE devices are preconfigured with the required Micro-BFD settings.
21
21
22
22
- The feature flag `MicroBFDEnabled` is turned off by default.
23
23
24
-
>[!Note]
25
-
> Contact Microsoft support through a support incident to enable the feature flag.
24
+
>[!Note]
25
+
> It is required to contact Microsoft support through a support incident to enable the feature flag once necessary configurations has been performed to devices as explained in this article.
26
26
27
-
- It is necessary to [put the device in maintenance mode](.\howto-put-device-in-maintenance-mode.md) to apply below the configuration changes.
27
+
- It's necessary to [put the device in maintenance mode](.\howto-put-device-in-maintenance-mode.md) to apply below the configuration changes.
28
28
29
-
## Configuration steps
29
+
## Configuration steps for enabling Micro-BFD
30
30
31
-
### Step 1: Configure CE devices
31
+
Follow these steps to enable Micro-BFD, starting with the secondary devices. Once verified, proceed with the primary devices using the instructions provided.
32
+
33
+
### Step 1: Place CE2 in Maintenance Mode
32
34
33
-
1. Access the CE device and enter the configuration mode.
35
+
Run the following Azure CLI command to place the CE2 device in maintenance mode:
34
36
35
-
2. Add the following configuration to enable Micro-BFD on the CE-PE interface:
37
+
```Azure CLI
38
+
az networkfabric device update-admin-state --resource-group <resource-group> --resource-name <resource-name> --state UnderMaintenance
39
+
```
40
+
41
+
>[!Note]
42
+
> For new deployments, maintenance mode is not required.
43
+
44
+
### Step 2: Configure Micro-BFD on CE2
45
+
46
+
Use the following Azure CLI command to configure Micro-BFD under Port-Channel1 on CE2.
47
+
48
+
```Azure CLI
49
+
az networkfabric device run-rw --ids /subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/
Verify the changes using the following command and check that the configured IP address, BFD interval, and neighbor details match the intended configuration.
72
+
73
+
```Example show output after configuring MicroBFD on CE2
74
+
CE2#show running-config interfaces pox
75
+
interface pox
76
+
description "Port pox Connected to PE-02"
77
+
mtu 9124
78
+
no switchport
79
+
ip address 10.30.0.69/30
80
+
bfd interval 50 min-rx 50 multiplier 3
81
+
bfd neighbor 10.30.0.70
82
+
bfd per-link rfc-7130
83
+
```
84
+
85
+
### Step 3: Configure Micro-BFD on PE2
86
+
87
+
Use the following command to configure PE2 with Micro-BFD: Consider min-links under the PE device for the respective port-channel.
88
+
89
+
```Azure CLI
90
+
az networkfabric device run-rw --ids /subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/
Verify the changes using the following command and check that the configured IP address, BFD interval, and neighbor details match the intended configuration.
101
+
102
+
```Example Show Output After Configuring MicroBFD on PE2
103
+
PE2#show running-config interfaces pox
104
+
interface pox
105
+
description "Port pox Connected to CE-02"
106
+
mtu 9124
107
+
no switchport
108
+
ip address 10.30.0.70/30
109
+
bfd interval 50 min-rx 50 multiplier 3
110
+
bfd neighbor 10.30.0.69
111
+
bfd per-link rfc-7130
112
+
```
36
113
37
-
```bash
38
-
ip address 10.30.0.65/30
39
-
bfd interval 50 min-rx 50 multiplier 3
40
-
bfd neighbor 10.30.0.66
41
-
bfd per-link rfc-7130
42
-
```
114
+
### Step 4: Move device CE2 into enabled state
43
115
44
-
### Step 2: Configure PE devices
116
+
Use the following command to re-enable the device and make it operational after configuration.
45
117
46
-
1. Access the PE device and enter the configuration mode.
118
+
```Azure CLI
119
+
az networkfabric device update-admin-state --resource-group <resource-group> --resource-name <resource-name> --state Enable
120
+
```
47
121
48
-
2. Add the following configuration to enable Micro-BFD on the PE-CE interface:
122
+
>[!Note]
123
+
> For new deployments, this step is not required.
49
124
50
-
```bash
51
-
ip address 10.30.0.66/30
52
-
bfd interval 50 min-rx 50 multiplier 3
53
-
bfd neighbor 10.30.0.65
54
-
bfd per-link rfc-7130
55
-
```
125
+
### Step 5: Verify BFD details
126
+
127
+
Check BFD peer details using the following command:
> After verifying the configuration on secondary devices, repeat steps 1 to 5 for primary devices (CE1 and PE1).
58
135
59
-
1. Request the DE team to enable the `MicroBFDEnabled` feature flag.
136
+
### Step 6: Ensure connectivity and BGP sessions
60
137
61
-
2. Verify the configuration by checking the status of Micro-BFD sessions on both CE and PE devices.
138
+
Ensure connectivity between CE and PE devices is stable, and BGP sessions are established with the appropriate routes.
62
139
63
-
### Step 4: Validate configuration
140
+
### Step 7: Enable Micro-BFD Flag
64
141
65
-
Use the following command to check the status of Micro-BFD sessions on the PE device:
142
+
Contact Microsoft support through a support incident to enable the Micro-BFD feature flag. After enabling the feature flag, a full reconciliation with the base configuration is required, ensuring the NPB property is set to true.
66
143
67
-
```bash
68
-
show bfd status dest-ip 10.30.0.65 detail
144
+
### Step 8: Verify Connectivity and BGP Sessions
145
+
146
+
After enabling the feature flag, confirm that connectivity and BGP sessions remain stable.
147
+
148
+
### Step 9: Remove configuration from RW config
149
+
150
+
After the BFD sessions are up, run the following Azure CLI command to remove BFD configurations. This process ensures that every full reconcile request avoids reapplying configurations to the devices.
151
+
152
+
```Azure CLI
153
+
az networkfabric device run-rw --ids /subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.ManagedNetworkFabric/NetworkDevices/<device-name>-AggrRack-CE1\PE1\CE2\PE2 --rw-command " "
69
154
```
70
-
Ensure that the Micro-BFD sessions are established and operational.
155
+
156
+
### Step 11: Ensure devices aren't disturbed
157
+
158
+
Ensure that devices aren't disturbed for Micro-BFD configuration.
71
159
72
160
## Recovery steps if Micro-BFD is misconfigured
73
161
74
-
In scenarios such as reconfiguration, where Micro-BFD is disabled by default, and the Provider Edge (PE) device is configured with Micro-BFD settings from a previous deployment, it is crucial to remove the Micro-BFD configuration from the PE device.
162
+
In cases like reconfiguration, where Micro-BFD is disabled by default but the Provider Edge (PE) device still has settings from a previous deployment, it's important to remove the Micro-BFD configuration from the PE device.
75
163
76
164
Follow these steps to ensure that Micro-BFD is disabled on your PE devices:
0 commit comments