Articles in this section

Run Easy Install

Sara Levy
  • Updated
Follow

Follow this guide to run the Easy Install utility after racking and cabling the cluster hardware.

Caution

Before you run Easy Install, verify the best way to configure the cluster's switches with your VAST Support Engineer. Easy Install detects switch configuration if it is already done and includes switch configuration if it is not already done. Configuring switches via Easy Install is not always recommended.

Important

Follow a prepared plan for the specific installation when completing all fields. The field descriptions below are intended as guidance to help you implement a planned configuration.

For a general understanding of the deployment options that might be planned for your installation, see VAST Cluster Installation Options and Settings

  1. Configure the Ethernet interface on your laptop to be on the following subnet: 192.168.2.0/24.

  2. Connect your laptop to the technician port on any one of the CNodes. This CNode will become the Management CNode.

    QuickInstallGraphics_12.png

    Technician Port Location: Cascade Lake model CNode
    CNode_Tech_Port_Right_Temp.png

    Technician Port Location: Broadwell model CNode

  3. Run the following commands to copy the VAST Cluster package file (e.g. release-3.6.0-123456.vast.tar.gz) and the vast_bootstrap.sh script to the CNode.

    scp <package file> vastdata@192.168.2.2:/vast/bundles/
scp <bootstrap file path> vastdata@192.168.2.2:/vast/bundles/

    where <package file path> is the local path to the package file and <bootstrap file path> is the local path to the file vast_bootstrap.sh.

    Note

    Make sure there is only one VAST Cluster package file located at /vast/bundles/ since vast_bootstrap.sh cannot select from multiple package files.

    You'll be prompted for the password on running each command. The default password is vastdata.

  4. Log into the management CNode via SSH and run the vast_bootstrap.sh script:

    username@host:~$ ssh vastdata@192.168.2.2
[vastdata@localhost ~]$ cd /vast/bundles
[vastdata@localhost bundles]$ ./vast_bootstrap.sh

    Note

    The file vast_bootstrap.sh needs to be executable. In some cases, depending on how it is copied to the CNode, you'll need to make it executable before running it.

  5. Confirm the action:

    Are you sure you want to reimage? this will wipe the current system [Y/n] Y
unpacking release-3.6.0-123456.vast.tar.gz, this may take a while

    The script extracts the package files and runs the Vast Management Server (VMS) container.

  6. When the bootstrap script is complete, the following message is displayed. 

    bootstrap finished, please connect at https://192.168.2.2

    While still connected to the tech-port, open a web browser on your laptop and browse to https://192.168.2.2.

    The VAST Web UI opens and displays the VAST DATA - End User License Agreement.

  7. Click I Agree.

    The login page appears.

  8. Log in using the default admin user and password:

    • Username: admin

    • Password: 123456

  9. The Cluster Installation dialog appears.

    At this stage, the Easy Install utility attempts to discover the CNodes and DNodes that comprise the cluster. Nodes are only discoverable if the switches were configured before you began running Easy Install.

    • If node discovery is successful, Easy Install skips switch configuration and moves onto Included Nodes.

    • Otherwise, Easy Install continues with configuring Switches.

Switches

  1. Complete the Switches Common fields. These settings are applied to all switches:

    Management gateway

    The management network default gateway IP.

    For example: 172.30.200.1

    Management Subnet

    The subnet mask for the management network.

    Specify the subnet in CIDR notation, which is the number of bits of each IP address that represent the subnet.

    For example, 24 (which is equivalent to 255.255.255.0)

    Ethernet MTU

    The MTU (Maximum Transmission Unit) to set on the external ports of all the switches. Set it to match the MTU of the client network. For more information, see Switch Topologies and Switch Roles.

    For example: 1500

    NTP

    The IP of the NTP server that you want the switches to connect to.

    For example: 172.30.100.10

    Data vlan

    Optional.

    The VLAN used to isolate VAST internal data from the data network. If there is a conflicting use of the default VLAN on the data network, specify a different VLAN that doesn't have a conflicting use on the data network. For more information, see The Internal Network.

    Default: 69

  2. Configure each and every pair of switches in turn. For each switch pair:

    1. Click Add Pair.

    2. Enter the correct settings for the switch pair.

      Number of ports

      Select the number of QSFP28 ports on each switch in the pair. The following numbers of ports are supported:

      • 16 (for Mellanox MSN2100 switches)

      • 32 (for Mellanox MSN2700 switches)

      Role

      Set the role of the switch pair as follows:

      • If the switch pairs are connected using a uniform topology in which all switches are connected to the data network, select leaf as the role for every pair.

      • If the switch pairs are connected in a spine-leaf topology in which some switch pairs are connected to the data network and others are not, select as follows:

        • leaf. For each pair of switches that has no external ports assigned.

        • spine. For each pair of switches that has external ports assigned.

      For information about switch roles and topologies, see Switch Topologies and Switch Roles.

      Switches External IPs

      Two IP addresses, one to assign to each switch in the pair, as described here. Separate the two IPs with a comma. These are management IPs and should be on the management subnet.

      For example: 172.30.200.10,172.30.200.11

      Switch VIP

      One IP address on the management subnet to assign to a single virtual interface for managing the switch pair, as described here. This is needed specifically if there are ports assigned as interconnect ports on each switch.

      For example: 172.30.200.12

      Tip

      The next several fields below specify which ports are assigned to which connections. Default values are entered based on the Number of Ports and Role field selections above. Port assignments vary per installation.

      CNode ports

      Specify any switch ports assigned for connection to CNodes.

      Enter the port numbers separated by commas. Use the notation '/2' to indicate port splitting. Typically, 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

      Specify any switch ports assigned for connection to DNodes.

      Enter the port numbers separated by commas.

      For example: 1,2,3,4,5,6

      External ports

      Specify any switch ports assigned for uplinks to the client data network.

      Enter the port numbers separated by commas.

      For example: 15,16

      Interconnect ports

      Specify any switch ports assigned for interconnecting the two switches in the pair.

      Enter the port numbers separated by commas.

      For example: 13,14

      Interswitch ports

      Specify any switch ports used for connection between leaf and spine pairs. For leaf-spine topologies only.

      Enter the port numbers separated by commas.

      For example: 23,24,25,26,27,28,29,30

      Management interface

      The management interface on the management CNode which you will connect to the switch when you apply the configuration to the switch. Set this to eno1.

      External speed

      The port speed to configure on any external ports on the switch pair.

      Default: 100G

      The default value is the default switch port speed of 100Gb/s. If needed, set the speed to a lower speed to match the speed of the switch ports on the data network.

      VLAN Tagging

      VLAN tagging is optional. These settings are available for the external ports. They enable you to activate specific VLANs and enable VLAN traffic on those ports.

      After installation, you will need to configure virtual interfaces (called VIPs) to provide data clients with access to the cluster. There will be an option to set VLAN tags on those interfaces. If you choose to use VLAN tagging, you will need to do some manual steps to activate the same VLAN tags on the switch external ports. This can be done now if you know which VLANs you will use. Otherwise, it is also possible to do it later, after the cluster is already installed.

      If you want to activate VLAN tags on the external switch ports now:

      • Enter the number of each VLAN that you want to create in the field provided for each external port. If there are multiple VLANs, separate them with commas.

      • From the VLAN tag dropdown, select a port mode that allows VLAN-tagged traffic through the interface:

        • Hybrid. To allow VLAN tagged traffic through the interface as well as non-tagged traffic.

        • Trunk. To allow ONLY VLAN tagged traffic through the interface.

        • Access. This is the default mode, which drops tagged packets and only allows untagged traffic. Don't set this mode if you want to enable tagged traffic.

  3. When you have added all switch pairs in the cluster, click Continue.

    The next task is to apply the switch configuration to each switch.

    A card appears per switch, showing a red port icon:

    SwitchApplyConfigCard.png

  4. For each switch in turn (one at a time):

    1. Connect an Ethernet cable from the eno1 port on the management CNode to the management port on the switch.

      Tip

      In some installations, there is a cable connecting the eno1 port on the management CNode to the eno1 port on another Cnode or to a management switch. If this is the case, remove that cable from that port until you are done configuring switches.

      CascadeLakeEno1.png

      eno1 Port Location: Cascade Lake model CNode
      BroadwellEno1.png

      eno1 Port Location: Broadwell model CNode

    2. Click Connect and Confirm.

      The configuration is applied to the switch. This will take some time. A spinning icon indicates that the task is in progress:

      SwitchApplyConfigCardSpinner.png

    3. Wait for the task to complete before proceeding with the next switch. When the task is done for a switch, a green port icon replaces the switch's red port icon:

      EverythingConnected.png

  5. When all switches are configured, remove the cable you used to apply the configuration to the switches, and reconnect any cable you disconnected from the eno1 port on the management CNode.

  6. Click Continue to Include Nodes.

Included Nodes

This screen displays all connected nodes and all hardware errors detected on the discovered nodes. Errors may pertain to CPU, memory, disks, NVRAMs, port connectivity, or licensing issues.

IncludedHosts1.png

1

Included Nodes. Displays all discovered nodes grouped by the CBox and DBox in which they are housed. By default, they are all included in the installation.

2

Errors panel. Displays any and all detected errors.

Do the following:

  1. Under Included Nodes, review the details of the discovered nodes and verify that all nodes are discovered:

    DiscoveredNodes.png

    1

    Each CBox and DBox is listed, with the final six digits of the CBox's or DBox's serial number.

    Expand each CBox and DBox to see the CNodes and DNodes housed in each one.

    2

    Node type:

    • CNode

    • DNode

    3

    IP address. Usually an IPv6 address.

    4

    Host name

    5

    OS version

    6

    Vendor. Possible values:

    • CNode:

      • Broadwell, single dual-port NIC

      • CascadeLake, two dual-port NICs

      • CascadeLake, single dual-port NIC

    • DNode:

      • Sanmina, single dual-port NIC

      • Sanmina, two single-port NICs

      • Supermicro, single dual-port NIC

  2. In the Errors Panel, review any errors that may have been detected during validation.

    The error text refers to the affected node, enabling you to match each error to a node listed above. In order to identify the position of the affected node, you can hover over a node to see where it is located in its CBox or DBox:

    Identify_Node_in_Rack.png

  3. Resolve any issues before continuing with the installation. In the event that faulty hardware was received in the shipment, consult VAST Support on how to proceed.

    The following options are available:

    • You can remove and either fix and reinsert, or replace a faulty component with a new one. After replacing, click Refresh Hardware to repeat host discovery and validation. Check again the discovered hosts and errors.

    • Exclude nodes. In case of validation errors that cannot be resolved on site before continuing and are critical, you can identify the affected node 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 node:

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

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

  4. When no errors remain, or when any remaining errors are determined not to be critical to the installation, click Continue to General Settings.

General Settings

  1. Complete the Required settings:

    Cluster Name

    A name for the cluster.

    Management VIP

    A single virtual IP configured on the management interfaces on all CNodes. VAST Management System (VMS) listens on this IP. This IP should be on the management subnet.

    Management Subnet CIDR

    The subnet for the management network in CIDR notation.

    External Gateway

    The default gateway of the management network.

    CNode Network Topology

    This field sets the modes of each CNode interface to the required transport protocol depending on the network infrastructure topology. The options available vary with the CNode model.

    All models:

    • Ethernet. Sets all interfaces to Ethernet mode. For Ethernet infrastructure on both the internal network and the data network.

    • Infiniband. Sets all interfaces to Infiniband mode. For Infiniband infrastructure on both the internal and external networks.

    Available only for CascadeLake CNodes with two dual-port NICs:

    • Internal ethernet external infiniband. Sets the interfaces connected to the internal network to Ethernet mode and the interfaces connected to the data network to Infiniband mode.

      Note

      This option is not yet supported.

    • Internal infiniband external ethernet. Sets the interfaces connected to the internal network to Infiniband mode and the interfaces connected to the data network to Ethernet mode.

      Note

      This option is not yet supported.

    DNode Network Topology

    This field sets the modes of the DNode interfaces to work with the network infrastructure topology. Select one of the following:

    • Ethernet. Sets the DNode interfaces to Ethernet mode. Supports Ethernet infrastructure for the internal network.

    • Infiniband. Sets the DNode interfaces to Infiniband mode. Supports Infiniband infrastructure for the internal network.

    Management Network

    This field specifies the the management network topology:

    • Inband. Management is on the data network.

    • Outband. Management is isolated from the management network.

    DNS IPs

    The IP(s) of any DNS servers that will forward DNS queries to the cluster. Enter one IP address or a comma separated list of IP addresses.

    For example: 172.30.100.20,172.30.100.20

    Cnode Management External IP Pool

    The IP pool from which to assign IPs for the management network to all CNodes (see ???). The pool should contain enough IPs for all CNodes in the cluster.

    To add IPs:

    1. Click inside the field. A Management CNode External IP Pool dialog appears in the IP pool area.

    2. Click Add new IP. Add one IP or a series of IPs separated by commas.

    3. Click Add.

    4. Repeat the previous two steps as needed until all IPs in the pool are entered.

    5. Click Save Changes.

      The IPs are added, and appear in the field as a comma separated list of IPs.

    For example, for an installation with one CBox, there are four CNodes, so you need to supply four IPs that were designated for the management external IP pool in the installation plan.

    Example: 173.30.200.100,173.30.200.101,173.30.200.102,173.30.200.103

    Dnode Management External IP Pool

    The IP pool from which to assign IPs for the management network to all DNodes (see ???). The pool should contain enough IPs for all DNodes in the cluster.

    To add IPs:

    1. Click inside the field. A Management External IP Pool dialog appears in the IP pool area.

    2. Click Add new IP. Add one IP or a series of IPs separated by commas.

    3. Click Add.

    4. Repeat the previous two steps as needed until all IPs in the pool are entered.

    5. Click Save Changes.

      The IPs are added, and appear in the field as a comma separated list of IPs.

    For example, for an installation with one DBox, there are two DNodes, so you need to supply two IPs that were designated for the management external IP pool in the installation plan.

    Example: 173.30.200.104,173.30.200.105

  2. From the dropdown below the required settings, select General Settings, and set those that are needed for your installation:

    CNodes IPMI Pool

    An IP pool from which to assign an IP to the IPMI interface of each CNode.

    Set this IP pool if and only if the planned deployment uses the standard IPMI network configuration .

    If you are deploying the B2B IPMI networking option, do not configure this IP pool. Configure a B2B template instead (see step 4).

    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.

    To add IPs:

    1. Click inside the field. A CNodes IPMI Pool dialog appears in the IP pool area.

    2. Click Add new IP. Add one IP or a series of IPs separated by commas.

    3. Click Add.

    4. Repeat the previous two steps as needed until all IPs in the pool are entered.

    5. Click Save Changes.

      The IPs are added, and appear in the field as a comma separated list of IPs.

    Example, : 173.30.200.110,173.30.200.111,173.30.200.112,173.30.200.113

    DNodes IPMI Pool

    An IP pool from which to assign an IP to the IPMI interface of each DNode.

    Set this IP pool if and only if the planned deployment uses the standard IPMI network configuration .

    If you are deploying the B2B IPMI networking option, do not configure this IP pool. Configure a B2B template instead (see step 4).

    Add IPs as described for CNodes IPMI Pool.

    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.

    Example, : 173.30.200.114,173.30.200.115

    IPMI default gateway

    The IP of a default gateway for the IPMI interfaces on the CNodes and DNodes, if different from the management network default gateway.

    For example: 173.30.200.1

    DNS Search Domains

    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.

    Ethernet MTU

    MTU size for any and all CNode and DNode Ethernet interfaces. Default: 9216

    If the MTU on the client data network is greater than 9000, set Ethernet MTU to be the same as on the client data network.

    If the MTU on the client data network is less than 9000, leave Ethernet MTU at the default value of 9216.

    IB MTU

    MTU size for any and all CNode and DNode Infiniband interfaces. Default: 2044

    NTP Server

    The IP(s) of any NTP server(s) that you want to use for time keeping. Enter as a comma separated list of IPs.

    For example: 172.30.100.10

    Management inner VIP

    A virtual IP on the internal network that is used for mounting the VMS database.

    Default: 172.16.4.254

    Encryption

    Enables encryption on the cluster.

    Warning

    This feature cannot be enabled or disabled after installation. If the feature is needed, it must be enabled at this stage.

    Similarity

    Enables similarity data reduction on the cluster. This can also be enabled or disabled after installation.

    Warning

    This feature is only supported with explicit approval from VAST Support.

    DBox HA

    Enables NVRAM high availability (HA) for DBoxes. Support for DBox NVRAM HA is limited. Make sure this feature is supported for your DBoxes before you enable it.

    Warning

    This feature cannot be enabled or disabled after installation. If the feature is needed, it must be enabled at this stage.

  3. From the dropdown, select Call Home and complete these settings to enable VAST Link, the remote call home service that enables VAST’s Support team to monitor and troubleshoot clusters.

    VAST Link sends non sensitive data securely from your VAST Cluster to our central support server to enable us to provide proactive analysis and fast response on critical issues. The data we collect is sent by HTTPS to a VAST Data AWS S3 bucket that we maintain for this purpose.  

    General Setup

    Customer

    Your customer name.

    Example: BigCorp

    Site

    The name of the site where the cluster is installed.

    Example: Miami

    Location

    A further specification of the location where the cluster is installed.

    Example: Lab1

    Max upload concurrency

    The maximum number of parts of a file to upload simultaneously to the AWS S3 bucket.

    Valid: Positive integer, 1 or more

    Default: 5

    Example: 10

    Intervals Setup

    Log Frequency (minutes)

    The frequency with which system state data is sent to the support server. Disabling the setting stops system state data being sent.

    Bundle Frequency

    The frequency with which debug data is sent to the support server. Disabling the setting stops debug data being sent.

    The frequency with which debug data is sent to the support server. Disabling the setting stops debug data being sent.

    Enabled

    Enable this setting to enable the VAST Link service.

    Proxy Setup

    Enter proxy server details if you would like the data to be sent through your own proxy server.

    Misc

    Verify SSL

    Enables SSL verification. Disable if, for example, you are sending the call home data through a proxy server that does not have an SSL certificate recognized by VAST Cluster. VAST Cluster recognizes SSL certificates from a large range of widely recognized certificate authorities (CAs). VAST Cluster may not recognize an SSL certificate signed by your own in-house CA.

    Prod mode

    Enable this setting.

    This setting sets the production support server as the destination for VAST Link bundles. It's essential to enable this setting for the service to work as expected.

    Support channel

    Enables VAST Data Support to run remote bundle collection commands on the cluster.

  4. From the same dropdown, select Customized Network Settings and set any of the following settings that are needed for the installation:

    Data vlan

    For Ethernet configurations, the internal network is isolated from the data network using this VLAN. In case of a conflicting use of the default VLAN, enter a different VLAN that is already not used on the client network.

    Default: 69

    Example: 108

    Subnet

    Sets a custom subnet for the internal network.

    The Data VLAN isolates the internal network from the external network. If you anticipate IP address collisions with the default subnet, such as in an IB configuration, you can set a custom subnet.

    IPs are generated on the nodes as subnet.[1,2,3].x, where x is an index per node.

    If you set, for example, 10.200 as the subnet, the following internal IPs are generated for internal traffic on each CNode and DNode: 10.200.1.x, 10.200.2.x, and 10.200.3.x.

    Default: 176.16

    B2B template

    B2B is a networking configuration option that isolates the IPMI network from the management network. A B2B IP is generated per node as 192.168.3.x, where x is a node index. Optionally, you can set a different B2B template. For example, if you set the B2B template to be 10.250.100 then the B2B IPs will be 10.250.100.x.

    Default: 192.168.3

    B2B IPMI

    Enables auto configuring the IPMI ports on the nodes with IP addresses according to the B2B template.

    Technician Interface Cnode

    Changes the IP configured on the technician interface on the CNodes.

    Default: 192.168.2.2

    Start index cnode

    Sets the start value for the indexes appended to internal IPs for the CNodes (see also Subnet). Default: 1

    Technician Interface Dnode

    Changes the IP configured on the technician interface on the DNodes.

    Start index dnode

    Sets the start value for the indexes appended to internal IPs for the DNodes (see also Subnet).

    Default: 100

  5. If needed, select Advanced settings from the same dropdown and set additional parameters.

    Caution

    Do not change Advanced settings unless guided to do so by VAST Support.

  6. Click Review Installation Before Executing.

    The Summary page appears.

  7. Review the summary of all the configurations you set. Check that your settings match the installation plan.

  8. If any settings are incorrect, use the To Step links from the configuration summaries to return to earlier steps, make the necessary changes, and proceed back to the Summary page.

  9. When you're ready to proceed, click Install.

  10. Select Activities from the left navigation menu to navigate to the Activities page and monitor the task progress.

    The task name is cluster_deploy.

    When installation is done, the cluster_deploy task state changes to COMPLETED and the cluster status displayed at the top left of the page changes to Online:

    cluster_online.png

    You can now disconnect from the technician port. The cluster's VAST Web UI is now accessible by browsing to the configured VMS VIP from network locations that have network access to the VMS VIP.

    To begin managing the cluster, browse to the VMS VIP and log in using the default user name admin and password 123456.

Related articles

Comments

0 comments

Article is closed for comments.