Skip to content

Commit 7a4b83f

Browse files
committed
Learn Editor: Update system-requirements.md
1 parent 3a2c194 commit 7a4b83f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-arc/resource-bridge/system-requirements.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ The gateway IP is the IP of the gateway for the network where Arc resource bridg
132132

133133
The following example shows valid configuration values that can be passed during configuration file creation for Arc resource bridge.
134134

135-
Notice that the IP addresses for the gateway, control plane, appliance VM and DNS server (for internal resolution) are within the IP address prefix. This key detail helps ensure successful deployment of the appliance VM.
135+
Notice that the IP addresses for the gateway, control plane, appliance VM and DNS server (for internal resolution) are within the IP address prefix. The VM IP Pool Start/End are sequential. This key detail helps ensure successful deployment of the appliance VM.
136136

137137
IP Address Prefix (CIDR format): 192.168.0.0/29
138138

@@ -163,9 +163,9 @@ There are several different types of configuration files, based on the on-premis
163163

164164
### Appliance configuration files
165165

166-
Three configuration files are created when the `createconfig` command completes (or the equivalent commands used by Azure Stack HCI): `<appliance-name>-resource.yaml`, `<appliance-name>-appliance.yaml` and `<appliance-name>-infra.yaml`.
166+
Three configuration files are created when deploying the Arc resource bridge: `<appliance-name>-resource.yaml`, `<appliance-name>-appliance.yaml` and `<appliance-name>-infra.yaml`.
167167

168-
By default, these files are generated in the current CLI directory when `createconfig` completes. These files should be saved in a secure location on the management machine, because they're required for maintaining the appliance VM. Because the configuration files reference each other, all three files must be stored in the same location. If the files are moved from their original location at deployment, open the files to check that the reference paths to the configuration files are accurate.
168+
By default, these files are generated in the current CLI directory of where the deployment commands are run. These files should be saved on the management machine because they're required for maintaining the appliance VM. The configuration files reference each other and should be stored in the same location.
169169

170170
### Kubeconfig
171171

0 commit comments

Comments
 (0)