Skip to content

Commit 013508f

Browse files
committed
corrected output in steps per Sushant
1 parent 35c9dc7 commit 013508f

File tree

1 file changed

+17
-19
lines changed

1 file changed

+17
-19
lines changed

articles/operator-nexus/concepts-network-fabric-read-only-commands.md

Lines changed: 17 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: HollyCl
55
ms.author: HollyCl
66
ms.service: azure-operator-nexus
77
ms.topic: concept-article #Required; leave this attribute/value as-is.
8-
ms.date: 04/10/2024
8+
ms.date: 04/15/2024
99

1010
#CustomerIntent: As a <type of user>, I want <what?> so that <why?>.
1111
---
@@ -34,6 +34,8 @@ By using the read-only diagnostic API, network administrators can efficiently tr
3434

3535
## Prerequisites
3636

37+
To use Network Fabric read-only commands, ensure the following steps have been completed:
38+
3739
- Provision the Nexus Network Fabric successfully.
3840
- Generate the storage URL.
3941

@@ -70,39 +72,35 @@ To ensure security and compliance, RO commands must adhere to the following spec
7072

7173
## Troubleshoot using read-only commands
7274

75+
To troubleshoot using read-only commands, follow these steps:
76+
7377
1. Open a Microsoft support ticket. The support engineer makes the necessary updates.
74-
1. Execute the following Azure CLI commands:
78+
1. Execute the following Azure CLI command:
7579

7680
```azurecli
7781
az networkfabric device run-ro --resource-name "<NFResourceName>" --resource-group "<NFResourceGroupName>" --ro-command "show version"
7882
```
7983
8084
Expected output:
8185
86+
`{ }`
87+
88+
1. Enter the following command:
89+
8290
```azurecli
8391
az networkfabric device run-ro --resource-group Fab3LabNF-6-0-A --resource-name nffab3-6-0-A-AggrRack-CE1 --ro-command "show version" --no-wait --debug
92+
```
93+
94+
The following (truncated) output appears. Copy the URl through **private preview**. This portion of the URL is used in the follow step to check the status of the operation.
8495
85-
cli.knack.cli: Command arguments: ['networkfabric', 'device', 'run-ro', '--resource-group', 'ResourceGroupName', '--resource-name', 'ResourceName', '--ro-command', 'show version', '--no-wait', '--debug']
86-
cli.knack.cli: __init__ debug log:
87-
Enable color in terminal.
88-
Enable VT mode.
89-
cli.knack.cli: Event: Cli.PreExecute []
90-
cli.knack.cli: Event: CommandParser.OnGlobalArgumentsCreate [<function CLILogging.on_global_arguments at 0x0198A418>, <function OutputProducer.on_global_arguments at 0x01A8D658>, <function CLIQuery.on_global_arguments at 0x01BA82B0>]
91-
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableCreate []
92-
cli.azure.cli.core: Modules found from index for 'networkfabric': ['azext_managednetworkfabric']
93-
cli.azure.cli.core: Loading command modules:
94-
cli.azure.cli.core: Name Load Time Groups Commands
95-
cli.azure.cli.core: Total (0) 0.000 0 0
96-
cli.azure.cli.core: These extensions are not installed and will be skipped: ['azext_ai_examples', 'azext_next']
97-
cli.azure.cli.core: Loading extensions:
98-
cli.azure.cli.core: Name Load Time Groups Commands Directory
99-
cli.azure.cli.core: managednetworkfabric 0.604 22 26 \XXXXX\XXXXX\.azure\cliextensions\managednetworkfabric
100-
cli.azure.cli.core: Total (1) 0.604 22 26
96+
```azurecli
97+
***https://management.azure.com/subscriptions/9531faa8-8c39-4165-b033-48697fe943db/providers/Microsoft.ManagedNetworkFabric/locations/EASTUS2EUAP/operationStatuses/59fdc0c8-eeb1-4258-9163-3cf096490148*A9E6DB3DF5C58D67BD395F7A608C056BC8219C392CC1CE0AD22E4C36D70CEE5C?api-version=2022-01-15-privatepreview***&t=638485032018035520&c=MIIHHjCCBgagAwIBAgITfwKWMg6goKCq4WwU2AAEApYyDjANBgkqhkiG9w0BAQsFADBEMRMwEQYKCZImiZPyLGQBGRYDR0JMMRMwEQYKCZImiZPyLGQBGRYDQU1FMRgwFgYDVQQDEw9BTUUgSW5mcmEgQ0EgMDIwHhcNMjQwMTMwMTAzMDI3WhcNMjUwMTI0MTAzMDI3WjBAMT4wPAYDVQQDEzVhc3luY29wZXJhdGlvbnNpZ25pbmdjZXJ0aWZpY2F0ZS5tYW5hZ2VtZW50LmF6dXJlLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALMk1pBZQQoNY8tos8XBaEjHjcdWubRHrQk5CqKcX3tpFfukMI0_PVZK-Kr7xkZFQTYp_ItaM2RPRDXx-0W9-mmrUBKvdcQ0rdjcSXDek7GvWS29F5sDHojD1v3e9k2jJa4cVSWwdIguvXmdUa57t1EHxqtDzTL4WmjXitzY8QOIHLMRLyXUNg3Gqfxch40cmQeBoN4rVMlP31LizDfdwRyT1qghK7vgvworA3D9rE00aM0n7TcBH9I0mu-96JE0gSX1FWXctlEcmdwQmXj_U0sZCu11_Yr6Oa34bmUQHGc3hDvO226L1Au-QsLuRWFLbKJ-0wmSV5b3CbU1kweD5LUCAwEAAaOCBAswggQHMCcGCSsGAQQBgjcVCgQaMBgwCgYIKwYBBQUHAwEwCgYIKwYBBQUHAwIwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIhpDjDYTVtHiE8Ys-
10198
```
99+
102100
3. Check the status of the operation programmatically using the following Azure CLI command:
103101
104102
```azurecli
105-
az rest -m get -u "<Azure-operationsstatus-endpoint url>"
103+
az rest -m get -u "<Azure-AsyncOperation-endpoint url>"
106104
```
107105
108106
The operation status indicates if the API succeeded or failed, and appears similar to the following output:

0 commit comments

Comments
 (0)