Skip to content

Commit 96be87b

Browse files
Merge pull request #303021 from MicrosoftDocs/main
Auto Publish – main to live - 2025-07-19 22:00 UTC
2 parents e254621 + aafbb8b commit 96be87b

19 files changed

+420
-152
lines changed

articles/operator-nexus/.openpublishing.redirection.operator-nexus.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,11 @@
4040
"redirect_url": "howto-apply-access-control-list-to-network-to-network-interconnects",
4141
"redirect_document_id": false
4242
},
43+
{
44+
"source_path": "howto-replace-a-device-in-azure-operator-nexus-network-fabric.md",
45+
"redirect_url": "howto-replace-network-devices",
46+
"redirect_document_id": false
47+
},
4348
{
4449
"source_path": "howto-use-azure-policy-for-aks-cluster-security.md",
4550
"redirect_url": "howto-use-azure-policy",

articles/operator-nexus/TOC.yml

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -219,8 +219,6 @@
219219
href: howto-delete-layer-3-isolation-domains.md
220220
- name: Cross-subscription deployments and required RBAC for Network Fabric
221221
href: concepts-cross-subscription-deployments-required-rbac-for-network-fabric.md
222-
- name: How to replace network devices in Azure Operator Nexus Network Fabric
223-
href: howto-replace-network-devices.md
224222
- name: How to put a device into maintenance mode
225223
href: howto-put-device-in-maintenance-mode.md
226224
- name: How to set up break glass access
@@ -241,8 +239,8 @@
241239
href: howto-append-custom-suffix-to-interface-descriptions.md
242240
- name: How to reboot Network Device in Azure Operator Nexus Network Fabric
243241
href: howto-reboot-network-device.md
244-
- name: How to replace a device in Azure Operator Nexus Network Fabric
245-
href: howto-replace-a-device-in-azure-operator-nexus-network-fabric.md
242+
- name: How to replace network devices in Azure Operator Nexus Network Fabric
243+
href: howto-replace-network-devices.md
246244
- name: How to Configure NNF with Bring Your Own (BYO) Storage
247245
href: howto-configure-bring-your-own-storage-network-fabric.md
248246
- name: How to upgrade OS of terminal server

articles/operator-nexus/concepts-commit-workflow-v2.md

Lines changed: 6 additions & 6 deletions
Large diffs are not rendered by default.

articles/operator-nexus/howto-replace-a-device-in-azure-operator-nexus-network-fabric.md

Lines changed: 0 additions & 125 deletions
This file was deleted.

articles/operator-nexus/howto-replace-network-devices.md

Lines changed: 112 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -9,34 +9,129 @@ ms.date: 08/12/2024
99
ms.custom: template-how-to, devx-track-azurecli
1010
---
1111

12-
# Azure Operator Nexus Network Fabric device replacement guide
12+
# Replace a device in Azure Operator Nexus Network Fabric (NNF)
1313

14-
This document provides a guide for replacing devices in the Azure Operator Nexus Network Fabric. The supported devices include CE devices, TOR switches, Network Packet Brokers (NPB), and Management switches. Note that the Nexus Network Fabric currently supports CE devices and TORs in maintenance mode; NPBs and Management switches do not support maintenance mode.
14+
This article describes how to replace a faulty or underperforming device in Azure Operator Nexus Network Fabric (NNF) using the RMA (Return Material Authorization) process which ensures minimal disruption and safe reintegration of the replacement hardware into the fabric.
1515

16-
## Putting a device in maintenance mode
16+
## Scenarios for device replacement
1717

18-
For the identified device, you can perform a post-action to keep the device in maintenance mode to drain out the traffic. Follow these steps to put the device in maintenance mode:
18+
Device replacement may be required in the following situations:
1919

20-
### Steps to put a device in maintenance mode
20+
- Inconsistent Performance (Flakiness): The device shows intermittent connectivity or performance degradation.
2121

22-
1. **Identify the device**: Determine the device that needs to be put into maintenance mode.
22+
- Hardware Failure: The device experiences critical hardware malfunctions that can't be fixed through standard troubleshooting.
2323

24-
2. **Execute maintenance mode command**: Follow the instructions on how to put the device in maintenance mode as defined in [How to put a network device in maintenance mode](howto-put-device-in-maintenance-mode.md).
24+
- Persistent Unreachability: The device is permanently unreachable despite repeated recovery attempts.
2525

26-
3. **Verify maintenance mode**: Confirm that the device is successfully in maintenance mode by checking its status as detailed in the documentation.
26+
## Prerequisites
2727

28-
> [!NOTE]
29-
> - **CE Devices and TORs**: These devices support maintenance mode in the Nexus Network Fabric.
30-
> - **NPBs and Management Switches**: These devices do not support maintenance mode and will require direct intervention for replacement without maintenance mode capabilities.
28+
- Azure CLI installed and configured.
3129

32-
## Device replacement process
30+
- Required permissions to manage Microsoft.ManagedNetworkFabric resources.
3331

34-
For the replacement of CE devices, TORs, Network Packet Brokers (NPBs), and Management switches, follow the process below:
32+
- Replacement device powered on and connected physically.
3533

36-
1. **Raise a support ticket**: Contact Microsoft Support to initiate the device replacement process. Provide all necessary details about the device and the issue.
34+
- Replacement device must support Zero Touch Provisioning (ZTP).
3735

38-
2. **Coordinate with support**: Work with Microsoft Support to plan and execute the replacement. They will guide you through the necessary steps and ensure minimal disruption to your network operations.
36+
- To ensure a smooth and timely RMA process, please verify the following before initiating deployment:
37+
38+
- Interface Speed Validation
3939

40-
3. **Device replacement**: Follow the instructions provided by Microsoft Support to physically replace the device.
40+
- Confirm that the ma1 interface speed is set to 100 Mbps or higher.
4141

42-
4. **Post-replacement verification**: After replacing the device, verify that it is functioning correctly and that network traffic is flowing as expected.
42+
- If the speed is below 100 Mbps, update it accordingly to prevent delays or potential timeouts during the RMA process.
43+
44+
- Device Storage Check
45+
- Ensure the device has a minimum of 2 GB of free space available.
46+
47+
- This is required to successfully download and stage the necessary image files.
48+
49+
50+
## Steps to replace a device
51+
52+
1. Disable administrative state.
53+
54+
Use the following command to disable the administrative state of the device:
55+
56+
```Azure CLI
57+
az networkfabric device update-admin-state \
58+
--state Disable \
59+
--resource-name "nf-device-name" \
60+
--resource-group "resource-group-name"
61+
```
62+
63+
This action:
64+
65+
- Moves the device to a degraded state: EnabledDegraded.
66+
67+
- Excludes the device from all control plane actions such as:
68+
69+
- Certificate rotations
70+
71+
- Password rotations
72+
73+
- Fabric upgrades
74+
75+
2. Update the serial number.
76+
77+
Once the replacement device is physically installed, update its serial number in the fabric resource:
78+
79+
```Azure CLI
80+
az networkfabric device update \
81+
--serial-number "replacement-serial-number" \
82+
--resource-name "nf-device-name" \
83+
--resource-group "resource-group-name"
84+
```
85+
86+
3. Ensure device is in ZTP Mode.
87+
88+
Verify that the replacement device is in ZTP mode. If not, configure the device for ZTP before continuing.
89+
90+
> [!Note]
91+
> ZTP enables automatic configuration retrieval during the RMA process.
92+
93+
4. Set RMA State.
94+
95+
Initiate the RMA process using the following command:
96+
97+
```Azure CLI
98+
az networkfabric device update-admin-state \
99+
--state RMA \
100+
--resource-name "nf-device-name" \
101+
--resource-group "resource-group-name"
102+
```
103+
104+
This will:
105+
106+
- Trigger the Network Fabric Controller to push all required configuration files to the replacement device.
107+
108+
- Retry the operation if there is transient failures until success is confirmed.
109+
110+
5. Refresh configuration
111+
112+
This step pushes the latest configuration to the device after it enters maintenance mode (applicable only for CE and TOR).
113+
114+
```Azure CLI
115+
az networkfabric device refresh-configuration --resource-name <resource-name> --resource-group <rg-name>
116+
```
117+
118+
This will push the latest config to the device.
119+
120+
6. Enable administrative state.
121+
122+
Once configuration is applied successfully, bring the device back into active service:
123+
124+
```Azure CLI
125+
az networkfabric device update-admin-state \
126+
--state Enable \
127+
--resource-name "nf-device-name" \
128+
--resource-group "resource-group-name"
129+
```
130+
131+
This will:
132+
133+
- Sets device state to Enabled once it's fully healthy and synchronized with the fabric.
134+
135+
## Summary
136+
137+
The RMA workflow in Network Fabric ensures seamless device replacement with controlled state transitions and full configuration synchronization. This helps maintain service continuity and operational consistency across the network.

articles/vpn-gateway/TOC.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -166,6 +166,10 @@
166166
href: vpn-gateway-modify-local-network-gateway.md
167167
- name: Azure CLI
168168
href: vpn-gateway-modify-local-network-gateway-cli.md
169+
- name: Advanced Connectivity
170+
items:
171+
- name: High Bandwidth tunnels
172+
href: site-to-site-high-bandwidth-tunnel.md
169173
- name: VPN devices
170174
items:
171175
- name: About VPN devices and parameters
49.2 KB
Loading
56.7 KB
Loading
58 KB
Loading
26.3 KB
Loading

0 commit comments

Comments
 (0)