Skip to content

Commit b6bed51

Browse files
authored
Update how-to-validate-cables.md
Added instructions for creating support ticket to patch fabric
1 parent bcd9801 commit b6bed51

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

articles/operator-nexus/how-to-validate-cables.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,20 @@ For BOM details, refer to [Azure Operator Nexus SKUs](./reference-operator-nexus
2424
- `Storage Blob Data Contributor` role must be assigned to the `Nexus Network Fabric RP` with access assigned to the storage account.
2525
- Microsoft Support must patch the Nexus Network Fabric with an active storage SAS URL before running cabling validation.
2626

27+
## Creating an Azure Support Request for patching Nexus Network Fabric:
28+
- Refer to [Create an Azure support request](https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request)
29+
- Enter `Nexus Network Fabric` for the issue and click `Go`.
30+
- Select `Azure Operator Nexus` as the service you are having issue with.
31+
- Select `Subscription` where the resource is located.
32+
- Select `General` under the resource field and click `Next`.
33+
- Select `Network fabric instance provisioning` under the issue prompt and click `Next`.
34+
- Now select `Create a support request` at the top of the support blade.
35+
- Click `Next` on the `Problem description` tab.
36+
- Wait for the `Recommended solution` and then click the link back to 'Return to support request`
37+
- Click `Next` to continue to the `Additional details`
38+
- Fill in the request to patch Nexus Network Fabric and include resource details, then click `Next`
39+
- Review the information in the `Review + create` tab and then click `Create`.
40+
2741
> [!NOTE]
2842
> The Storage URL (SAS) is short-lived. By default, it is set to expire in eight hours. If the SAS URL expires, then the fabric must be re-patched.
2943

0 commit comments

Comments
 (0)