Skip to content

Commit 5864f86

Browse files
authored
Update howto-upgrade-nexus-fabric-template.md
Resolve comments
1 parent 06161f0 commit 5864f86

File tree

1 file changed

+19
-22
lines changed

1 file changed

+19
-22
lines changed

articles/operator-nexus/howto-upgrade-nexus-fabric-template.md

Lines changed: 19 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: how-to
99
ms.custom: azure-operator-nexus, template-include
1010
---
1111

12-
# Fabric Runtime Upgrade Template
12+
# Fabric runtime upgrade template
1313

1414
This how-to guide provides a step-by-step template for upgrading a Nexus Fabric designed to assist users in managing a reproducible end-to-end upgrade through Azure APIs and standard operating procedures. Regular updates are crucial for maintaining system integrity and accessing the latest product improvements.
1515

@@ -125,45 +125,42 @@ If any failures occur, report the <MISE_CID>, <CORRELATION_ID>, status code, and
125125

126126
2. Validate the provisioning status for the Network Fabric Controller (NFC), Fabric, and Fabric Devices.
127127

128-
Set up the subscription, NFC, and NF parameters:
128+
Login to Azure CLI and select or set the `<CUSTOMER_SUB_ID>`:
129129
```
130-
export SUBSCRIPTION_ID=<CUSTOMER_SUB_ID>
131-
export NFC_RG=<NFC_RG>
132-
export NFC_NAME=<NFC_NAME>
133-
export NF_RG=<NF_RG>
134-
export NF_NAME=<NF_NAME>
130+
az login
131+
az account set --subscription <CUSTOMER_SUB_ID>
135132
```
136133

137134
Check that the NFC is in Provisioned state:
138135
```
139-
az networkfabric controller show -g $NFC_RG --resource-name $NFC_NAME --subscription $SUBSCRIPTION_ID -o table
136+
az networkfabric controller show -g <NFC_RG> --resource-name <NFC_NAME> --subscription <CUSTOMER_SUB_ID> -o table
140137
```
141138

142139
Check the NF status:
143140
```
144-
az networkfabric fabric show -g $NF_RG --resource-name $NF_NAME --subscription $SUBSCRIPTION_ID -o table
141+
az networkfabric fabric show -g <NF_RG> --resource-name <NF_NAME> --subscription <CUSTOMER_SUB_ID> -o table
145142
```
146143
Record down the `fabricVersion` and `provisioningState`.
147144

148145
Check the Devices status.
149146
```
150-
az networkfabric device list -g $NF_RG -o table --subscription $SUBSCRIPTION_ID
147+
az networkfabric device list -g <NF_RG> -o table --subscription <CUSTOMER_SUB_ID>
151148
```
152149

153150
>[!Note]
154151
> If `provisioningState` is not `Succeeded`, stop the upgrade until issues are resolved.
155152
156153
3. Check `Microsoft.NexusIdentity` user Resource Provider (RP) is registered on the customer subscription:
157154
```
158-
az provider show --namespace Microsoft.NexusIdentity -o table --subscription $SUBSCRIPTION_ID
155+
az provider show --namespace Microsoft.NexusIdentity -o table --subscription <CUSTOMER_SUB_ID>
159156
Namespace RegistrationPolicy RegistrationState
160157
----------------------- -------------------- -------------------
161158
Microsoft.NexusIdentity RegistrationRequired Registered
162159
```
163160

164161
If not registered, run the following to register:
165162
```
166-
az provider register --namespace Microsoft.NexusIdentity --wait --subscription $SUBSCRIPTION_ID
163+
az provider register --namespace Microsoft.NexusIdentity --wait --subscription <CUSTOMER_SUB_ID>
167164
168165
az provider show --namespace Microsoft.NexusIdentity -o table
169166
Namespace RegistrationPolicy RegistrationState
@@ -175,7 +172,7 @@ If any failures occur, report the <MISE_CID>, <CORRELATION_ID>, status code, and
175172

176173
Verify the available space on each Fabric Devices using the following Azure CLI command.
177174
```
178-
az networkfabric device run-ro --resource-name <ND_DEVICE_NAME> --resource-group <NF_RG> --ro-command "dir flash" --subscription <CUSTOMER_SUB_ID> --debug
175+
az networkfabric device run-ro --resource-name <NF_DEVICE_NAME> --resource-group <NF_RG> --ro-command "dir flash" --subscription <CUSTOMER_SUB_ID> --debug
179176
```
180177

181178
Contact Microsoft support if there isn't enough space to perform the upgrade. Archived Extensible Operating System (EOS) images and support bundle files can be removed at the direction of support.
@@ -210,14 +207,14 @@ If any failures occur, report the <MISE_CID>, <CORRELATION_ID>, status code, and
210207
[How to check current cluster runtime version.](./howto-check-runtime-version.md#check-current-fabric-runtime-version)
211208

212209
```
213-
az networkfabric fabric list -g $NF_RG --query "[].{name:name,fabricVersion:fabricVersion,configurationState:configurationState,provisioningState:provisioningState}" -o table --subscription $SUBSCRIPTION_ID
214-
az networkfabric fabric show -g $NF_RG --resource-name $NF_NAME --subscription $SUBSCRIPTION_ID
210+
az networkfabric fabric list -g <NF_RG> --query "[].{name:name,fabricVersion:fabricVersion,configurationState:configurationState,provisioningState:provisioningState}" -o table --subscription <CUSTOMER_SUB_ID>
211+
az networkfabric fabric show -g <NF_RG> --resource-name <NF_NAME> --subscription <CUSTOMER_SUB_ID>
215212
```
216213

217214
### Initiate Fabric upgrade
218215
Start the upgrade with the following command:
219216
```Azure CLI
220-
az networkfabric fabric upgrade -g [resource-group] --resource-name [fabric-name] --action start --version "5.0.0"
217+
az networkfabric fabric upgrade -g <NF_RG> --resource-name <NF_NAME> --subscription <CUSTOMER_SUB_ID> --action start --version "5.0.0"
221218
{}
222219
```
223220

@@ -262,7 +259,7 @@ Four Rack environments have 17 Devices:
262259
### Follow device-specific upgrade
263260
Run the following command to upgrade the version on each Device:
264261
```
265-
az networkfabric device upgrade --version $NF_VERSION -g $NF_RG --resource-name $NF_DEVICE_NAME --subscription $SUBSCRIPTION_ID --debug
262+
az networkfabric device upgrade --version <NF_VERSION> -g <NF_RG> --resource-name <NF_DEVICE_NAME> --subscription <CUSTOMER_SUB_ID> --debug
266263
```
267264

268265
As part of the upgrade, the Devices are put into maintenance mode. The Device drains all traffic and stops advertising routes so that the traffic flow to the device stops. At completion, the Nexus Network Fabric (NNF) service updates the Device resource version property to the new version.
@@ -277,13 +274,13 @@ Provide this information to Microsoft Support when opening a support ticket for
277274

278275
After Device upgrades are complete, make sure that all the Devices are showing with <NF_VERSION> by running the following command:
279276
```
280-
az networkfabric device list -g $NF_RG --query "[].{name:name,version:version}" -o table --subscription $SUBSCRIPTION_ID
277+
az networkfabric device list -g <NF_RG> --query "[].{name:name,version:version}" -o table --subscription <CUSTOMER_SUB_ID>
281278
```
282279

283280
### Complete Network Fabric Upgrade
284281
Once all the Devices are upgraded, run the following command to take the Network Fabric out of maintenance state.
285282
```
286-
az networkfabric fabric upgrade --action Complete --version $NF_VERSION -g $NF_RG --resource-name $NF_NAME --debug --subscription $SUBSCRIPTION_ID
283+
az networkfabric fabric upgrade --action Complete --version <NF_VERSION> -g <NF_RG> --resource-name <NF_NAME> --debug --subscription <CUSTOMER_SUB_ID>
287284
```
288285

289286
### How to troubleshoot Device update failures
@@ -328,12 +325,12 @@ az networkcloud baremetalmachine list -g <CLUSTER_MRG> --subscription <CUSTOMER_
328325
az networkcloud storageappliance list -g <CLUSTER_MRG> --subscription <CUSTOMER_SUB_ID> -o table
329326
330327
# Tenant Workloads
331-
az networkcloud virtualmachine list --sub $SUBSCRIPTION_ID --query "reverse(sort_by([?clusterId=='$CLUSTER_RID'].{name:name, createdAt:systemData.createdAt, resourceGroup:resourceGroup, powerState:powerState, provisioningState:provisioningState, detailedStatus:detailedStatus,bareMetalMachineId:bareMetalMachineIdi,CPUCount:cpuCores, EmulatorStatus:isolateEmulatorThread}, &createdAt))" -o table
332-
az networkcloud kubernetescluster list --sub $SUBSCRIPTION_ID --query "[?clusterId=='$CLUSTER_RID'].{name:name, resourceGroup:resourceGroup, provisioningState:provisioningState, detailedStatus:detailedStatus, detailedStatusMessage:detailedStatusMessage, createdAt:systemData.createdAt, kubernetesVersion:kubernetesVersion}" -o table
328+
az networkcloud virtualmachine list --sub <CUSTOMER_SUB_ID> --query "reverse(sort_by([?clusterId=='<CLUSTER_RID>'].{name:name, createdAt:systemData.createdAt, resourceGroup:resourceGroup, powerState:powerState, provisioningState:provisioningState, detailedStatus:detailedStatus,bareMetalMachineId:bareMetalMachineIdi,CPUCount:cpuCores, EmulatorStatus:isolateEmulatorThread}, &createdAt))" -o table
329+
az networkcloud kubernetescluster list --sub <CUSTOMER_SUB_ID> --query "[?clusterId=='<CLUSTER_RID>'].{name:name, resourceGroup:resourceGroup, provisioningState:provisioningState, detailedStatus:detailedStatus, detailedStatusMessage:detailedStatusMessage, createdAt:systemData.createdAt, kubernetesVersion:kubernetesVersion}" -o table
333330
```
334331

335332
> [!Note]
336-
> IRT validation provides a complete functional test of networking and workloads across all components of the Nexus Instance. Simple validation does not provide functional tesing.
333+
> IRT validation provides a complete functional test of networking and workloads across all components of the Nexus Instance. Simple validation does not provide functional testing.
337334
338335
</details>
339336

0 commit comments

Comments
 (0)