Skip to content

Commit 0993d29

Browse files
sushantjraosushantjrao
committed
Update howto-enable-micro-bfd.md
1 parent 23f62cb commit 0993d29

File tree

1 file changed

+174
-41
lines changed

1 file changed

+174
-41
lines changed

‎articles/operator-nexus/howto-enable-micro-bfd.md

Lines changed: 174 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -28,61 +28,62 @@ Ensure the following prerequisites are met before enabling Micro-BFD:
2828

2929
## Configuration steps for enabling Micro-BFD
3030

31+
### Steps for existing deployments
32+
3133
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
34+
35+
#### Step 1: Place CE2 in Maintenance Mode
3436

3537
Run the following Azure CLI command to place the CE2 device in maintenance mode:
3638

3739
```Azure CLI
3840
az networkfabric device update-admin-state --resource-group <resource-group> --resource-name <resource-name> --state UnderMaintenance
3941
```
4042

41-
>[!Note]
42-
> For new deployments, maintenance mode is not required.
43-
44-
### Step 2: Configure Micro-BFD on CE2
43+
#### Step 2.1: Configure Micro-BFD on CE2
4544

4645
Use the following Azure CLI command to configure Micro-BFD under Port-Channel1 on CE2.
4746

4847
```Azure CLI
49-
az networkfabric device run-rw --ids /subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/
50-
Microsoft.ManagedNetworkFabric/NetworkDevices/<device>-AggrRack-CE2 --rw-command "interface Port-Channel1
48+
az networkfabric device run-rw \
49+
--ids "/subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.ManagedNetworkFabric/NetworkDevices/<device>-AggrRack-CE2" \
50+
--rw-command "interface Port-Channel1
5151
ip address 10.30.0.69/30
5252
mtu 9124
5353
no switchport
5454
bfd neighbor 10.30.0.70
5555
bfd interval 50 min-rx 50 multiplier 3
5656
bfd per-link rfc-7130
57-
!"
57+
!" \
58+
--debug
5859
```
5960

6061
```Example IP address allocation
61-
NFIPv4Addr: 10.30.0.0/19
62-
CE<->PE MicroBFD: 10.30.0.64/30
63-
CE1: 10.30.0.65/30 & PE1: 10.30.0.66/30
64-
CE2: 10.30.0.69/30 & PE2: 10.30.0.70/30
65-
NFIPv4Addr: 10.30.32.0/19
66-
CE<->PE MicroBFD: 10.30.32.64/30
67-
CE1: 10.30.32.65/30 & PE1: 10.30.32.66/30
68-
CE2: 10.30.32.69/30 & PE2: 10.30.32.70/30
62+
Example1: NFIPv4Addr : 10.30.0.0/19 then 10.30.0.0/24 is reserved for TS<->PE and CE<->PE interaction
63+
CE<->PE MicroBFD : 10.30.0.64/30 --> CE1: 10.30.0.65/30 & PE1: 10.30.0.66/30
64+
10.30.0.68/30 --> CE2: 10.30.0.69/30 & PE2: 10.30.0.70/30
65+
66+
Example2: NFIPv4Addr : 10.30.32.0/19 then 10.30.32.0/24 is reserved for TS<->PE and CE<->PE interaction
67+
CE<->PE MicroBFD : 10.30.32.64/30 --> CE1: 10.30.32.65/30 & PE1: 10.30.32.66/30
68+
10.30.32.68/30 --> CE2: 10.30.32.69/30 & PE2: 10.30.32.70/30
6969
```
7070

7171
Verify the changes using the following command and check that the configured IP address, BFD interval, and neighbor details match the intended configuration.
7272

7373
```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
74+
Example show output after configuring MicroBFD in CE2 :
75+
CE2#show running-config interfaces pox
76+
interface pox
77+
description "Port pox Connected to PE-01"
78+
mtu 9124
79+
no switchport
80+
ip address 10.30.0.69/30
81+
bfd interval 50 min-rx 50 multiplier 3
82+
bfd neighbor 10.30.0.70
83+
bfd per-link rfc-7130
8384
```
8485

85-
### Step 3: Configure Micro-BFD on PE2
86+
#### Step 2.2: Configure Micro-BFD on PE2
8687

8788
Use the following command to configure PE2 with Micro-BFD: Consider min-links under the PE device for the respective port-channel.
8889

@@ -111,52 +112,184 @@ PE2#show running-config interfaces pox
111112
bfd per-link rfc-7130
112113
```
113114

114-
### Step 4: Move device CE2 into enabled state
115+
#### Step 3: Move device CE2 into enabled state
115116

116117
Use the following command to re-enable the device and make it operational after configuration.
117118

118119
```Azure CLI
119120
az networkfabric device update-admin-state --resource-group <resource-group> --resource-name <resource-name> --state Enable
120121
```
121122

122-
>[!Note]
123-
> For new deployments, this step is not required.
123+
```Example show command to check bfd details
124+
CE1#show bfd peers dest-ip 10.30.0.69 detail
125+
```
126+
127+
#### Step 4: Place CE1 in Maintenance Mode
128+
129+
Run the following Azure CLI command to place the CE1 device in maintenance mode:
130+
131+
```Azure CLI
132+
az networkfabric device update-admin-state --resource-group <resource-group> --resource-name <resource-name> --state UnderMaintenance
133+
```
124134

125-
### Step 5: Verify BFD details
135+
#### Step 5.1: Configure Micro-BFD on CE1
126136

127-
Check BFD peer details using the following command:
137+
Use the following Azure CLI command to configure Micro-BFD under Port-Channel1 on CE1.
128138

129-
```Bash
130-
CE2#show bfd peers dest-ip <dest-bfd-peer-ip> detail
139+
```Azure CLI
140+
az networkfabric device run-rw \
141+
--ids "/subscriptions<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.ManagedNetworkFabric/NetworkDevices/<device>-AggrRack-CE1" \
142+
--rw-command "interface Port-Channel1
143+
ip address 10.30.0.65/30
144+
mtu 9124
145+
no switchport
146+
bfd neighbor 10.30.0.66
147+
bfd interval 50 min-rx 50 multiplier 3
148+
bfd per-link rfc-7130
149+
!" \
150+
--debug
151+
```
152+
153+
```Example show output after configuring MicroBFD in CE1 :
154+
CE1#show running-config interfaces pox
155+
interface pox
156+
description "Port pox Connected to PE-01"
157+
mtu 9124
158+
no switchport
159+
ip address 10.30.0.65/30
160+
bfd interval 50 min-rx 50 multiplier 3
161+
bfd neighbor 10.30.0.66
162+
bfd per-link rfc-7130
163+
```
164+
165+
#### Step 5.2: Configure Micro-BFD on PE1
166+
167+
Use the following command to configure PE1 with Micro-BFD: Consider min-links under the PE device for the respective port-channel.
168+
169+
```Azure CLI
170+
az networkfabric device run-rw --ids /subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/
171+
Microsoft.ManagedNetworkFabric/NetworkDevices/<device>-AggrRack-PE1 --rw-command "interface Port-Channel1
172+
ip address 10.30.0.66/30
173+
mtu 9124
174+
no switchport
175+
bfd neighbor 10.30.0.65
176+
bfd interval 50 min-rx 50 multiplier 3
177+
bfd per-link rfc-7130
131178
```
132179

133-
>[!NOTE]
134-
> After verifying the configuration on secondary devices, repeat steps 1 to 5 for primary devices (CE1 and PE1).
180+
Example show output after configuring MicroBFD in CE1 :
135181

136-
### Step 6: Ensure connectivity and BGP sessions
182+
PE1#show running-config interfaces pox
183+
interface xyz
184+
description "Port xyz Connected to CE-01"
185+
mtu 9124
186+
no switchport
187+
ip address 10.30.0.66/30
188+
bfd interval 50 min-rx 50 multiplier 3
189+
bfd neighbor 10.30.0.65
190+
bfd per-link rfc-7130
191+
PE1#
192+
193+
#### Step 6: Move device CE1 into enabled state
194+
195+
Use the following command to re-enable the device and make it operational after configuration.
196+
197+
```Azure CLI
198+
az networkfabric device update-admin-state --resource-group <resource-group> --resource-name <resource-name> --state Enable
199+
```
200+
201+
```Example show command to check bfd details
202+
CE1#show bfd peers dest-ip 10.30.0.66 detail
203+
```
204+
205+
#### Step 7: Ensure connectivity and BGP sessions
137206

138207
Ensure connectivity between CE and PE devices is stable, and BGP sessions are established with the appropriate routes.
139208

140-
### Step 7: Enable Micro-BFD Flag
209+
#### Step 8: Enable Micro-BFD Flag
141210

142211
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.
143212

144-
### Step 8: Verify Connectivity and BGP Sessions
213+
#### Step 9: Verify Connectivity and BGP Sessions
145214

146215
After enabling the feature flag, confirm that connectivity and BGP sessions remain stable.
147216

148-
### Step 9: Remove configuration from RW config
217+
#### Step 10: Remove configuration from RW config
149218

150219
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.
151220

152221
```Azure CLI
153222
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 " "
154223
```
155224

156-
### Step 11: Ensure devices aren't disturbed
225+
#### Step 11: Ensure devices aren't disturbed
157226

158227
Ensure that devices aren't disturbed for Micro-BFD configuration.
159228

229+
### Steps for new deployments
230+
231+
#### **Prerequisites**
232+
233+
Before enabling the **Micro BFD** feature flag, ensure the following:
234+
235+
- The **Provider Edge (PE)** is configured with the required **Micro BFD settings**.
236+
237+
- Inform the **Microsoft Support team** about the planned Micro BFD feature flag enablement.
238+
239+
- Configure **PE devices** to enable Micro BFD and ensure the **min-links** under the PE device for the respective port-channel are considered.
240+
241+
#### **Configuring Micro BFD on PE devices**
242+
243+
Below are example configurations for enabling **Micro BFD** on PE devices.
244+
245+
```Example: PE2 configuration
246+
PE2# show running-config interfaces pox
247+
interface pox
248+
description "Port pox Connected to CE-02"
249+
mtu 9124
250+
no switchport
251+
ip address 10.30.0.70/30
252+
bfd interval 50 min-rx 50 multiplier 3
253+
bfd neighbor 10.30.0.69
254+
bfd per-link rfc-7130
255+
PE2#
256+
```
257+
258+
```Example: PE1 Configuration
259+
PE1# show running-config interfaces pox
260+
interface pox
261+
description "Port xyz Connected to CE-01"
262+
mtu 9124
263+
no switchport
264+
ip address 10.30.0.66/30
265+
bfd interval 50 min-rx 50 multiplier 3
266+
bfd neighbor 10.30.0.65
267+
bfd per-link rfc-7130
268+
```
269+
270+
#### **Step 1: Create the Network Fabric**
271+
272+
Proceed with creating the **Network Fabric** as per the standard provisioning procedures.
273+
274+
#### **Step 2: Customer approval for geneva action**
275+
276+
The customer must approve the **lockbox enabled geneva action** before proceeding further.
277+
278+
#### **Step 3: Network provisioning operation**
279+
280+
Once the **Micro BFD** feature is enabled, validate the **BFD status** on the **CE devices** using the following CLI commands.
281+
282+
```Example: Checking BFD details on CE2
283+
CE2# show bfd peers dest-ip 10.30.0.70 detail
284+
```
285+
286+
```Example: Checking BFD details on CE1
287+
CE1# show bfd peers dest-ip 10.30.0.66 detail
288+
```
289+
290+
>[!Note]
291+
> Check the BFD status using the provided commands on both CE devices or same can be requested from Microsoft support team to share once the configuration is completed.
292+
160293
## Recovery steps if Micro-BFD is misconfigured
161294

162295
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.

0 commit comments

Comments
 (0)