21
Chapter 1: Introduction
Step 4. Make sure that the file is in valid JSON format because EVO:RAIL will not validate
the syntax (e.g., a missing comma will cause the configuration file to fail). EVO:RAIL
will validate the content of a correctly formatted JSON file in the same manner that
it validates manual entries, verifying data entry and performing deep validation prior
to building the appliance.
Step 5. Make this file accessible from the EVO:RAIL Configuration and Management
workstation/laptop.
Then deploy EVO:RAIL as usual by configuring your top-of-rack switch, racking and cabling
your new EVO:RAIL appliance, and powering on each EVO:RAIL node. Connect the
EVO:RAIL Configuration and Management workstation/laptop to the network, and continue
with the following steps:
Step 6. Point a browser to the initial IP address in
Row 5
. Click the
Yes, Let’s Go!
button.
Then if you agree, accept the VMware End-User License Agreement.
Step 7. Click the
Customize
button.
Step 8. In the bottom right corner of the page, click
Upload Configuration File
. (See the
red arrow in
Figure 2
.)
Step 9. Upload your new JSON configuration file from your EVO:RAIL Configuration and
Management workstation/laptop.
Step 10. Fix any mistakes that are highlighted with a red dot. The
Passwords
tab should
be highlighted with a red dot because it would not be secure to enter passwords in
clear text in a JSON file.
Step 11. Click the
Validate
button.
Step 12. If the configuration is valid, click the
Build Appliance
button.
Step 13. If you changed the IP address of vCenter Server in the JSON file (i.e.,
Row 6
is not
the same as
Row 5
in the
EVO:RAIL Network Configuration Table
), follow the
on-screen instructions to go to the new IP address for EVO:RAIL Management.
JSON File Format and Valid Values
The JSON configuration file must be properly formatted and the values must be valid for
EVO:RAIL and for your network. The following list contains the field restrictions:
•
minIP, maxIP, netmask, gateway, ip: valid IP addresses and netmask in your network
•
vlanId: valid numeric VLAN ID, configured on your top-of-rack switch
•
name: alphanumeric string to identify a VM network segment
•
prefix: alphanumeric string for the first part of an ESXi hostname
•
separator: “” (no separator) or “-“ (dash)
•
iterator: “NUMERIC_N” or “NUMERIC_NN” or “ALPHA”
•
tld: valid top-level domain name in your network
