Run the VAST Web UI Installer

1. In the Scheme Settings (Step 1 out of 4) screen, select a scheme file from the All Schemes dropdown. If the predefined scheme files are not suitable for the installation, click the Upload scheme button and upload a customized scheme file. Then select the uploaded scheme from the All Schemes dropdown.

   For help selecting or creating a scheme file, see Prepare a Scheme File.

   When the file is uploaded, the fields defined in the scheme appear with the values set in the scheme file pre-filled.

2. Optionally make changes if needed to those of the following fields that were loaded from the scheme:

   Field	Description
   cnode fields:
   eth-mtu	MTU size for all CNode Ethernet interfaces on the CNodes. Default: 9216 If the MTU on the client data network is greater than 9000, set eth-mtu to the same as on the client data network. If the MTU on the client data network is less than 9000, set eth-mtu to 9216.
   ext-interface	The interface on each CNode assigned for connectivity to the management network. For out of band management, this must be specified. The default if unspecified is bondo, which correct for inband management. Example: eno1
   external_interfaces	Two physical interfaces to assign for connectivity to the client data network. These are automatically inferred if left blank. For installations with one NIC per CNode, these will be inferred correctly as both of the two physical interfaces on the NIC. Separate interface names by a comma. Example: ib0,ib1
   internal_interfaces	Two interfaces to assign for connectivity to the VAST internal network. These are automatically inferred if left blank. For installations with one NIC per CNode, these will be inferred correctly as both of the two physical interfaces on the NIC. Separate interface names by a comma. Example: ens785f0,ens785f1
   internal_virtual_interfaces	Two virtual interfaces over which to configure a bond interface, which is used for internal management traffic between the VMS and the CNodes and DNodes. Each of the two virtual interfaces should be bound to a different physical interface to enable fail over. These are automatically inferred if left blank. For installations with one NIC per CNode, these will be inferred correctly as both of the two virtual interfaces that are created during OS installation. Separate interface names by a comma. Example: ens785f2,ens785f3
   port-mode	Specifies the interface modes of the physical interfaces on the CNode NICs. If there is one NIC per CNode. Others have two NICs per CNode, which may be separately dedicated to the VAST internal or client data network. Valid values: eth. Sets both the internal and external interfaces to Ethernet mode. ib. Sets both the internal and the external interfaces to Infiniband mode. Comma separated list of type=mode pairs in order of PCI enumeration where type is the traffic type (internal or external) and mode is the interface mode (eth or ib). For example: external=ib,internal=eth. internal=eth,external=ib
   technician-interface	Specifies the interface on each CNode to use for onsite technician connection. Example: eno2
   ib_mode	The mode of the IB network, if applicable: datagram connected (default)
   ib_mtu	The MTU of the IB network, in bytes, if applicable. Example: 2044
   template	The template for the subnets. In an IB configuration, there could be an IP address collision within our subnets (172.16.1.x, 172.16.2.x, 172.16.3.x). In such a case, enter a different template.
   data_vlan	For Ethernet configurations VAST internal data is isolated from the client data network using this VLAN. In case of a conflicting use of the default VLAN (69), enter a different VLAN that is already not used on the client network.
   dnode fields:
   ext-interface	The interface on each DNode assigned for connectivity to the management network. For out of band management, this must be specified. The default if unspecified is bondo, which correct for inband management. Example: ens4
   technician_interface	The interface on each CNode to use for onsite technician connection.
   port_mode	The interface mode of the interfaces on the DNodes, which are connected to the VAST internal network. Valid values: eth. Sets the interfaces to Ethernet mode. ib. Sets the interfaces to Infiniband mode.
   eth_mtu	MTU size for all CNode Ethernet interfaces on the CNodes. Default: 9216 Set to the same MTU as on the CNodes.
   internal_interfaces	Two interfaces over which to configure the "VAST internal" network. This is inferred automatically if left blank. If you choose to specify it, separate interface names by a comma.
   external_interfaces	If this appears, leave it blank. It is not needed.
   internal_virtual_interfaces	Two virtual interfaces over which the bond interface is configured. Each virtual interface should be bound to a different physical interface to enable fail over. The bond intewhich is used for internal management traffic between the VMS and the CNodes and DNodes. This is inferred automatically if left blank. If you choose to specify it, separate interface names by a comma.
   ib_mode	The mode of the IB network, if applicable: datagram connected (default)
   ib_mtu	The MTU of the IB network, in bytes, if applicable. Example: 2044
   template	The template for the subnets. In an IB configuration, there could be an IP address collision within our subnets (172.16.1.x, 172.16.2.x, 172.16.3.x). In such a case, enter a different template.
   data_vlan	For Ethernet configurations VAST internal data is isolated from the client data network using this VLAN. In case of a conflicting use of the default VLAN (69), enter a different VLAN that is already not used on the client network.
   general fields
   mgmt
   mode

3. Click Next.

   If switches were already configured before you ran the bootstrap script, continue with Define Hosts (Step 2 out of 4) (Switches Configured).

   If switches are not yet configured, continue with Define Hosts (Step 2 out of 4) (Switches Not Yet Configured).

Proceed as follows:

1. Review any host validation errors that may be listed to the right of the discovered host list under Errors(#). Consider identifying affected hardware components and doing field replacements to resolve errors. The error text refers to the affected host's factory default host name and IP address, enabling you to match each error to a host listed on the left. Using the MAC address included in the discovered hosts list, you can identify the affected host in the field.

2. After doing any field replacements, click Refresh Hardware to repeat host discovery and validation checks. Wait for the refresh to complete and then review validation errors again.

3. In case of validation errors that cannot be resolved on site before continuing and are critical, you can identify the affected host and exclude it from the installation. In this case, please report the errors to Support and arrange return and replacement of hardware. Replacement nodes can be added to the cluster once it is already active.

   To exclude a host:

   1. Select the host you want to exclude and click Exclude.

   2. Verify that the host(s) you need to exclude is/are now listed in the list of Excluded Hosts.

4. Click Next and continue with Required fields (Step 3 out of 4).

1. Configure each switch's management port with IP 192.168.15.15.

   On each switch:

   1. Detach the management cable from the switch management port.

   2. Connect the laptop to the switch management port.

   3. Run the following commands to configure the IP:

      enable
      conf t
      interface mgmt0
      no dhcp
      ip addr 192.168.15.15 /24
      exit

      Note

      The user name and password for accessing the switch are admin and admin.

   4. Reconnect the management cable to the switch management port.

2. Click Configure Switches. A button appears for configuring each switch pair in the scheme. The button names reflect the role of each switch pair:

   • Spine. A pair of switches that will be connected to the client network. (All schemes have at least one switch pair in this role.)

   • Leaf. A pair of switches that will not to be connected to the client network.

3. Click one of the buttons and complete the following fields to configure one switch pair:

   Field	Description
   Switches External IPs	Two external IPs to configure on the switch pair. Separate the two IPs with a comma. For example: 192.0.2.2,192.0.2.3
   Switch VIP	A single virtual IP for managing the switch pair. Optional for spine pairs. Not relevant for leaf pairs in a spine and leaf topology. For example: 192.0.2.4 To find this IP in a VAST installation plan, look under IP Details, and then the MLNX MLAG table row. The Switch VIP is usually listed as MLNXMLAG in the IPs column.
   Management CIDR	The subnet mask, in CIDR notation, on which the Switch VIP resides. In CIDR notation, the subnet is expressed as the number of bits of each IP address that represent the subnet address. For example, the subnet mask 255.255.255.0 is expressed as 24 in CIDR notation. (Enter only the trailing CIDR decimal number that indicates the subnet mask. e.g. If the Switch VIP is 192.0.2.3 and the CIDR subnet is 24, enter 24 in this field. Do not enter 192.0.2.3/24.) To find this value in a VAST installation plan, look under IP Details, and then the VMS VIP table row. This value is usually listed as MCIDR in the Netmask column.
   Management gateway	The gateway through which to route management traffic to/from the switch VIP. For example: 192.0.2.1 To find this IP in a VAST installation plan, look under IP Details, and then the VMS VIP row of the table. The Management gateway is usually listed as MGW in the GW column.
   CNode ports	The ports on both switches in the pair that will connect to CNode ports. Enter the port numbers as a comma separated list without spaces. Add the notation '/2' to each port number to indicate that each 100Gb switch port is split for connection to two 50 Gig CNode ports. For example: 7/2,8/2,9.2,10/2,11/2,12/2
   DNode ports	The ports on both switches in the pair that will connect to DNode ports. Enter the port numbers as a comma separated list without spaces. For example: 1,2,3,4,5,6
   External ports	(Usually spine only) The ports on both switches in the pair that will uplink to the customer's network. Enter the port numbers as a comma separated list without spaces. For example: 15,16
   Interconnect ports	The ports on both switches that will interconnect the two switches in the pair. Enter the port numbers as a comma separated list without spaces. For example: 13,14
   Interswitch ports	The ports on both switches in the pair that will be used for connection between the switch pair and other switch pairs (if there is more than one switch pair). Enter the port numbers as a comma separated list without spaces. For example: 25,26,27,28,29,30,31,32
   MTU	N/A (please ignore)
   External MTU	The MTU on external ports. Set this always to be the same as the MTU on the client data network. For example: 9216

4. Click Set.

5. Repeat the previous two steps for each switch pair.

6. When you've completed all switch pair configurations, click Set.

   The following message appears:

   

7. Temporarily disconnect any cables from the management port of the management CNode and from the management port of data switch 1.

8. Connect a cable from the management port of the management CNode to the management port of data switch 1 and then click Apply.

   Wait while VAST Cluster applies the configuration to the switch. While you're waiting, the screen displays "Applying...".

9. When a request to connect the cable to switch 2 appears, disconnect the cable from data switch 1. Disconnect the management switch cable from the management port of data switch 2 and connect the cable from the CNode management port to data switch 2.

10. Click Apply.

    Wait while VAST Cluster applies the configuration to the switch. While you're waiting, the screen displays "Applying...".

11. Remove the cable you used to configure the data switches from the management port of the management CNode.

12. In the Define hosts (Step 2 out of 4) screen, click Refresh Hardware.

    This runs host discovery.

13. Proceed now with Define Hosts (Step 2 out of 4) (Switches Configured).

1. Complete these fields:

   Field	Description
   Cluster Name	A name for the cluster. For example: CompanyCluster1
   Management External IP Pool	The IP pool from which to assign IPs to all CNodes and DNodes. The pool should contain enough IPs for all CNodes and DNodes in the cluster. The first IPs in the pool are assigned to the CNodes. Subsequent IPs in the pool are assigned to the DNodes. List all IPs in the range as a comma separated list (no spaces). For example: 198.51.100.202,198.51.100.204,198.51.100.206,198.51.100.208,198.51.100.210,198.51.100.212
   CNodes IPMI Pool	Optional. The IP pool from which to assign an IP to the IPMI of each CNode. The CNodes will be assigned IPMI IPs in the same order as they are assigned management external IPs. The CNode that receives the first IP in the management external IP pool receives the first IP in the CNodes IPMI pool and so on. For example: 198.51.100.203,198.51.100.205,198.51.100.207,198.51.100.209
   DNodes IPMI Pool	Optional. The DNodes will be assigned IPMI IPs in the same order as they are assigned management external IPs. The DNode that receives the first DNode IP in the management external IP pool receives the first IP in the DNodes IPMI pool and so on. For example: 198.51.100.211,198.51.100.213
   Management VIP	A single VIP for management interfaces. For example: 198.51.100.214 To find this value in a VAST installation plan, look under IP Details and then the VMS VIP table row. The Management VIP is usually listed as VMSVIP in the IPs column.
   Management Subnet CIDR	The subnet mask for the external IPs, specified in CIDR notation. In CIDR notation, the subnet is expressed as the number of bits of each IP address that represent the subnet address. For example, the subnet mask 255.255.255.0 is expressed as 24 in CIDR notation. (Enter only the trailing CIDR decimal number that indicates the subnet mask. e.g. If the Switch VIP is 192.0.2.3 and the CIDR subnet is 24, enter 24 in this field. Do not enter 192.0.2.3/24.) To find this value in a VAST installation plan, look under IP Details, and then the VMS VIP table row. This value is usually listed as MCIDR in the Netmask column.
   External Gateway	The gateway through which to route traffic to the external IPs provided. For example: 198.51.100.1 To find this IP in a VAST installation plan, look under IP Details, and then the VMS VIP row of the table. The Management gateway is usually listed as MGW in the GW column.
   IPMI Default Gateway	The gateway through which to route traffic to the IPMI IPs provided. For example: 198.51.100.1
   NTP Server	The IP(s) of any NTP server(s) that you want to use for time keeping. Enter as a comma separated list. For example: 192.0.2.0
   DNS IPs	The IP(s) of your DNS server. Enter as a comma separated list. For example: 198.51.100.2,198.51.100.3
   DNS Search Domains	Optional. Enter the domains on your data network on which client hosts may reside. If you provide these, you will be able to specify hosts by name instead of IP when setting up export policies, callhome settings, webhook definitions and so on. VAST Cluster will use these domains to look up host IPs on the DNS server. For example: .local,.localdomain,.corp

2. If the installation requires a change from any other parameter from its default on the VMS server, click Advanced Settings.

   Several parameters appear under Common advanced settings. Enter values as needed for any of those parameters.

   If you want to set a different parameter, add the parameter name and value in the Advanced settings - added by you section.

3. If you are in Advanced settings, click Set & Back.

4. Click Finish. Review the summary and then click Install.

5. Monitor the task progress from the Activities page.

6. When the task is complete, the Activities page indicates that the VMS is available on the VMS VIP. Redirect your browser to the management VIP.

   The cluster comes online. You'll see the cluster name at the top left of the page with the status "Online":