Skip to content

Commit a28c4ae

Browse files
Merge pull request #273820 from sushantjrao/patch-27
Update howto-configure-network-fabric-controller.md
2 parents 90859c6 + eda065b commit a28c4ae

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

articles/operator-nexus/howto-configure-network-fabric-controller.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -169,6 +169,26 @@ Expected output:
169169
}
170170
```
171171

172+
## Update Network Fabric Controller
173+
174+
The PATCH feature in the Network Fabric Controller provide users the ability to effortlessly add or replace additional Express Routes circuits. This functionality is particularly useful during periods of failure or potential migration events. In such cases, the Network Operator has the flexibility to modify an active Network Fabric Controller by adding or removing Express Routes and Keys, all while ensuring the operation remains unaffected.
175+
176+
> [!NOTE]
177+
> When initiating an update command, it's crucial to supply all the parameters provided during the creation process. This is because the update command will overwrite the existing content, necessitating the inclusion of all relevant parameters to ensure comprehensive and accurate modifications.
178+
179+
```Azure CLI
180+
az networkfabric controller update \
181+
--resource-group "NFCResourceGroupName" \
182+
--location "eastus" \
183+
--resource-name "nfcname" \
184+
--ipv4-address-space "10.0.0.0/19" \
185+
--infra-er-connections '[{"expressRouteCircuitId":"/subscriptions/xxxxxx-xxxxxx-xxxx-xxxx-xxxxxx/resourceGroups/ER-Dedicated-WUS2-AFO-Circuits/providers/Microsoft.Network/expressRouteCircuits/MSFT-ER-Dedicated-PvtPeering-WestUS2-AFO-Ckt-01", "expressRouteAuthorizationKey": "<auth-key>"}]'
186+
--workload-er-connections '[{"expressRouteCircuitId":"/subscriptions/xxxxxx-xxxxxx-xxxx-xxxx-xxxxxx/resourceGroups/ER-Dedicated-WUS2-AFO-Circuits/providers/Microsoft.Network/expressRouteCircuits/MSFT-ER-Dedicated-PvtPeering-WestUS2-AFO-Ckt-01"", "expressRouteAuthorizationKey": "<auth-key>"}]'
187+
```
188+
189+
> [!NOTE]
190+
> Run az networkfabric controller show to retrieve information about a network fabric controller.
191+
172192
## Delete Network Fabric Controller
173193

174194
You should delete an NFC only after deleting all associated network fabrics.

0 commit comments

Comments
 (0)