Skip to content

Commit 317a3d4

Browse files
authored
Update howto-upgrade-nexus-fabric-template.md
1 parent 155e90e commit 317a3d4

File tree

1 file changed

+14
-12
lines changed

1 file changed

+14
-12
lines changed

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

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.custom: azure-operator-nexus, template-include
1111

1212
# Fabric runtime upgrade template
1313

14-
This how-to guide provides a step-by-step template for upgrading a Fabric. It is designed to assist users in enhancing their network infrastructure through Azure APIs, which facilitate the lifecycle management of various network devices. Regular updates are crucial for maintaining system integrity and accessing the latest product improvements.
14+
This how-to guide provides a step-by-step template for upgrading a Nexus Fabric. It is designed to assist users in managing a reproducable end-to-end upgrade through Azure APIs. Regular updates are crucial for maintaining system integrity and accessing the latest product improvements.
1515

1616
## Overview
1717

@@ -49,6 +49,10 @@ Runtime changes are categorized as follows:
4949
- [Operator Nexus Releases and Notes](./release-notes-2402.2)
5050
- [Network Fabric Upgrade](./howto-upgrade-nexus-fabric)
5151

52+
## Prerequisites
53+
- Install Azure CLI
54+
- Install Azure CLI Extensions
55+
5256
## Pre-Checks before executing the Fabric upgrade
5357

5458
1. The following role permissions should be assigned to end users responsible for Fabric create, upgrade, and delete operations. These permissions can be granted temporarily, limited to the duration required to perform these operations.
@@ -118,7 +122,7 @@ Runtime changes are categorized as follows:
118122

119123
If any taps are "not found", failed" or "error" status, do not start the upgrade until the network taps issues are cleared.
120124

121-
7. Run cabling validation report:
125+
6. Run cabling validation report:
122126

123127
#Link
124128
```
@@ -136,11 +140,11 @@ Runtime changes are categorized as follows:
136140

137141
List all port connection and cabling issues in the iTrack and notify AT&T Nitro/Team
138142

139-
11. Notify SRE of Upgrade and ETA:
143+
7. Notify Operations of upgrade and ETA:
140144

141-
DE will send notification to SRE of production resource upgrade and ETA using the following template:
145+
Send notification to Operations of production Fabric upgrade and ETA using the following template:
142146
```
143-
Title: <ENVIRONMENT> <REGION> <FABRIC_NAME> Runtime upgrade to <FABRIC_RUNTIME_VERSION> <START_TIME> -
147+
Title: <ENVIRONMENT> <AZURE_REGION> <FABRIC_NAME> Runtime upgrade to <FABRIC_RUNTIME_VERSION> <START_TIME> -
144148
Completion ETA <DURATION>
145149
146150
@@ -155,21 +159,19 @@ Runtime changes are categorized as follows:
155159
Cluster: <CLUSTER_NAME>
156160
Region: <AZURE_REGION>
157161
Version: <NEXUS_VERSION>
158-
159-
cc: aods-de-
160-
162+
163+
CC: stakeholder-list
161164
```
162165

163-
12. Azure Resource Tags on Deployment Resources:
166+
8. Azure Resource Tags on Deployment Resources:
164167

165168
```
166-
To help track customer deployments, DE will add tags to DE created Azure resources in Azure portal for
167-
Fabric:
169+
To help track upgrades, the DE can add a tag to the Fabric resources in Azure portal:
168170
|Name | Value |
169171
---------------|-----------------
170172
|BF in progress|<DE_CUSTOMER_ID>|
171173
172-
When deployment is complete or issue is resolved, the DE will remove the tag.
174+
When deployment is complete, the DE will remove the tag.
173175
```
174176

175177

0 commit comments

Comments
 (0)