You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`az networkfabric device run-rw`| Azure CLI command for executing a read-write operation on a network device within Azure Network Fabric. |
151
-
|`--resource-name`| Specifies the name of the resource (network device) on which the RW operation will be performed. |
151
+
|`--resource-name`| Specifies the name of the resource (network device) on which the RW operation is performed. |
152
152
|`--resource-group`| Specifies the name of the resource group that contains the network device. |
153
153
|`--rw-command "router bgp 65055\n neighbor untrustnetwork shutdown"`| Specifies the RW commands to be executed on the network device. These commands configure BGP settings to shut down the neighbor named "untrustnetwork". |
|`az networkfabric device run-rw`| Azure CLI command for executing a read-write operation on a network device within Azure Network Fabric. |
189
-
|`--resource-name`| Specifies the name of the resource (network device) on which the RW operation will be performed. |
189
+
|`--resource-name`| Specifies the name of the resource (network device) on which the RW operation is performed. |
190
190
|`--resource-group`| Specifies the name of the resource group that contains the network device. |
191
191
|`--rw-command "router bgp 65055\n neighbor untrustnetwork shutdown"`| Specifies the RW commands to be executed on the network device. These commands configure BGP settings to shut down the neighbor named "untrustnetwork". |
192
192
|`--no-wait`| Indicates that the command should be executed asynchronously without waiting for the operation to complete. |
|`az networkfabric device run-rw`| Azure CLI command for executing a read-write operation on a network device within Azure Network Fabric. |
250
-
|`--resource-name`| Specifies the name of the resource (network device) on which the RW operation will be performed. |
250
+
|`--resource-name`| Specifies the name of the resource (network device) on which the RW operation is performed. |
251
251
|`--resource-group`| Specifies the name of the resource group that contains the network device. |
252
252
|`--rw-command "router bgp 4444\n vrf gfab1-isd\n niehgbor 10.100.30.18 shudown"`| Specifies the RW commands to be executed on the network device. These commands configure BGP settings to shut down the neighbor with IP address 10.100.30.18 within the VRF named "gfab1-isd". |
253
253
@@ -258,22 +258,6 @@ Expected output:
258
258
Error: Message: \[GNMI SET failed. Error: GNMI SET failed: rpc error: code = config failed to apply.
259
259
```
260
260
261
-
## Command restrictions
262
-
263
-
The RW command feature is open and there are no restrictions on it. However, proceed with caution because incorrect usage of the configuration can bring down the system.
264
-
265
-
- The creation of vLANs ranging from 1 to 500 and 3000 to 4095 isn't recommended as this range is reserved for infrastructure purposes.
266
-
- Don't tamper the Management vLAN configuration.
267
-
- It's imperative not to tamper the Network-to-Network Interconnect (NNI) Ingress and Egress Access Control Lists (ACLs), as any modifications could potentially result in a loss of connectivity to the Azure Operator Nexus instance.
268
-
- There are no schematic or syntax validations performed for RW commands. You must ensure that the configuration is vetted out before executing it.
269
-
- The RW config commands should be an absolute command; short forms and prompts aren't supported.
270
-
For example:
271
-
Enter `router bgp <ASN>\n vrf <name>\n neighbor <IPaddress> shutdown`
272
-
Not `router bgp <ASN>\n vrf <name>\n nei <IPaddress> sh or shut`
273
-
274
-
- It's crucial to thoroughly review the Route Policy configuration before implementation, as any oversight could potentially compromise the existing Route Policy setup.
275
-
- Changing the router BGP configuration and shutting it down brings down the stability of the device.
|`--rw-command " "`| Specifies an empty RW command to be executed on the network device. This command is essentially a placeholder with no action. |
377
377
378
378
> [!NOTE]
379
-
> in the above command, space is required within Quotes.
379
+
> Ensure that there is a space between the quotation marks in the empty RW command.
380
380
381
381
Expected output:
382
382
@@ -468,6 +468,22 @@ show interfaces description
468
468
|Et4 | admin down | down | **"AR-Mgmt2:Et4 to Not-Connected"** |
469
469
```
470
470
471
+
## Command restrictions
472
+
473
+
The RW command feature is open and there are no restrictions on it. However, proceed with caution because incorrect usage of the configuration can bring down the system.
474
+
475
+
- The creation of vLANs ranging from 1 to 500 and 3000 to 4095 isn't recommended as this range is reserved for infrastructure purposes.
476
+
- Don't tamper the Management vLAN configuration.
477
+
- It's imperative not to tamper the Network-to-Network Interconnect (NNI) Ingress and Egress Access Control Lists (ACLs), as any modifications could potentially result in a loss of connectivity to the Azure Operator Nexus instance.
478
+
- There are no schematic or syntax validations performed for RW commands. You must ensure that the configuration is vetted out before executing it.
479
+
- The RW config commands should be an absolute command; short forms and prompts aren't supported.
480
+
For example:
481
+
Enter `router bgp <ASN>\n vrf <name>\n neighbor <IPaddress> shutdown`
482
+
Not `router bgp <ASN>\n vrf <name>\n nei <IPaddress> sh or shut`
483
+
484
+
- It's crucial to thoroughly review the Route Policy configuration before implementation, as any oversight could potentially compromise the existing Route Policy setup.
485
+
- Changing the router BGP configuration and shutting it down brings down the stability of the device.
0 commit comments