@@ -54,7 +54,7 @@ You'll create isolation-domains to enable layer 2 and layer 3 connectivity betwe
54
54
| subscriptionId | Your Azure subscriptionId for your Operator Nexus instance. |
55
55
| provisioningState | Indicates provisioning state |
56
56
57
- ## L2 isolation-domain
57
+ ## L2 Isolation-Domain
58
58
59
59
You use an L2 isolation-domain to establish layer 2 connectivity between workloads running on Operator Nexus compute nodes.
60
60
@@ -177,7 +177,7 @@ Expected Output
177
177
This command is used to change the administrative state of the isolation-domain.
178
178
179
179
** Note:**
180
- Only after the isolation-domain is Enabled, that the layer 2 isolation-domain configuration is pushed to the Network fabric devices.
180
+ Only after the Isolation-Domain is Enabled, that the layer 2 Isolation-Domain configuration is pushed to the Network Fabric devices.
181
181
182
182
``` azurecli
183
183
az nf l2domain update-admin-state --resource-group "ResourceGroupName" --resource-name "example-l2domain" --state Enable/Disable
@@ -388,11 +388,11 @@ Expected Output
388
388
389
389
Once the isolation-domain is created successfully, the next step is to create an internal network.
390
390
391
- ## Optional Parameters for Isolation Domain
391
+ ## Optional parameters for Isolation Domain
392
392
393
393
| Parameter| Description| Example| Required|
394
394
| ---| ---| ---| ---|
395
- | redistributeConnectedSubnet | Advertise Connected Subnets Default value is True | True | |
395
+ | redistributeConnectedSubnet | Advertise connected subnets default value is True | True | |
396
396
| redistributeStaticRoutes | Advertise Static Routes can have value of true/False. Defualt Value is False | False | |
397
397
| aggregateRouteConfiguration| List of Ipv4 and Ipv6 route configurations | | |
398
398
@@ -407,7 +407,7 @@ Once the isolation-domain is created successfully, the next step is to create an
407
407
|location|AODS Azure Region used during NFC Creation|eastus | True
408
408
409
409
410
- ## Options to create Internal networks by using
410
+ ## Options to create Internal Networks
411
411
412
412
| Parameter| Description| Example| Required|
413
413
| ---| ---| ---| ---|
@@ -434,10 +434,11 @@ az nf internalnetwork create
434
434
--resource-group "ResourceGroupName"
435
435
--l3-isolation-domain-name "example-l3domain"
436
436
--resource-name "example-internalnetwork"
437
- --location "eastus" --vlan-id 805
437
+ --location "eastus"
438
+ --vlan-id 805
438
439
--connected-ipv4-subnets '[{"prefix":"10.1.2.0/24"}]'
439
440
--mtu 1500
440
- --bgp-configuration '{"defaultRouteOriginate": "True", "allowAS": 2, "allowASOverride": "Enable", "PeerASN": 65535, "ipv4ListenRangePrefixes": ["10.1.2.0/28"]}
441
+ --bgp-configuration '{"defaultRouteOriginate": "True", "allowAS": 2, "allowASOverride": "Enable", "PeerASN": 65535, "ipv4ListenRangePrefixes": ["10.1.2.0/28"]}'
441
442
442
443
```
443
444
@@ -494,7 +495,7 @@ Expected Output
494
495
}
495
496
```
496
497
497
- ## Multiple Static Routes with single next hop
498
+ ## Multiple static routes with single next hop
498
499
499
500
``` azurecli
500
501
az nf internalnetwork create
@@ -660,7 +661,7 @@ This command creates an External network using Azure CLI.
660
661
661
662
** Note:** For Option A You need to create an external network before you enable the L3 isolation Domain. An external is dependent on Internal network, so an external can't be enabled without an internal network. The vlan-id value should be between 501 and 4095.
662
663
663
- ## External Network Creation using OptionB
664
+ ## External Network Creation using Option B
664
665
665
666
``` azurecli
666
667
az nf externalnetwork create
@@ -706,7 +707,7 @@ Expected Output
706
707
"type" : " microsoft.managednetworkfabric/l3isolationdomains/externalnetworks"
707
708
}
708
709
```
709
- ## External Network Creation with OptionA
710
+ ## External Network creation with Option A
710
711
711
712
``` azurecli
712
713
az nf externalnetwork create
@@ -762,14 +763,14 @@ Expected Output
762
763
763
764
``` azurecli
764
765
az nf externalnetwork create
765
- --resource-group "ResourceGroupName" `
766
- --l3-isolation-domain-name "example-l3domain" `
767
- --resource-name "example-externalipv6network" `
768
- --location "eastus" `
769
- --vlan-id 506 `
770
- --peer-asn 65022 `
771
- --primary-ipv6-prefix "10:101:2::0/127" `
772
- --secondary-ipv6-prefix "10:101:3::0/127"
766
+ --resource-group "ResourceGroupName"
767
+ --l3-isolation-domain-name "example-l3domain"
768
+ --resource-name "example-externalipv6network"
769
+ --location "eastus"
770
+ --vlan-id 506
771
+ --peer-asn 65022
772
+ --primary-ipv6-prefix "10:101:2::0/127"
773
+ --secondary-ipv6-prefix "10:101:3::0/127"
773
774
```
774
775
775
776
** Note:** Primary and Secondary IPv6 supported in this release is /127
0 commit comments