Follow these essential post-installation steps to get VAST Cluster configured and ready to use.
The following steps are assumed done:
All VAST Cluster hardware components are rack mounted and cabled.
The VAST Cluster is configured in the VAST Management System (VMS) as a manageable entity, such as through the VAST Web UI installer.
Make sure your PC has network access to all of the VAST Cluster compute servers (CNodes).
<VMS_VIP>is the management VIP that you provided during installation. This is the IP used to connect to the VAST Cluster management server (VMS).
The VAST Web UI opens.
If this is your first time connecting to the VAST Web UI, click I agree to accept the VAST Data End User License Agreement.
Enter your Username and Password to log in.
For first time login, use the factory default management user account credentials:
VAST Cluster has one factory default management user account. You cannot delete the factory default management user account or reduce its permissions. After first time login, you can change the password and create additional management accounts.
You're now logged into the VAST Web UI and you're viewing the Dashboard.
For good security practice, we recommend you change your management password immediately.
From the left navigation menu, select Administrator and then Managers.
Find the manager named admin, click the Actions button () for the manager and select Edit.
In the Password field, enter a new password.
In the Retype Password field, enter the password again.
Your new password is saved.
VIP pools are ranges of IP addresses that VAST Cluster can use for listening for data traffic.
VAST Data recommends a minimum of two VIPs per CNode. For optimal load balancing, we encourage four VIPs per CNode for clusters with one Cbox (four CNodes); and four or more VIPs per CNode for larger clusters.
To learn more about VIP pools, see Configuring Network Access.
Configure one or more VIP pools to provide a recommended number of VIPs.
If you would like your DNS server to resolve different subdomains to different VIP pools, set up a VIP pool per subdomain. In step 4, you will be able to set up load balancing and DNS service to complete the configuration.
From the left navigation menu, select Network Access and then Virtual IP Pools.
Click + Create VIP Pool and complete the fields:
Enter a name for the VIP Pool.
If your storage clients are on multiple subnets and you are routing your client storage traffic through a local gateway device, enter the gateway IP.
Start IP (required)
Enter the IP at the start of the range.
End IP (required)
Enter the IP at the end of the range.
Subnet CIDR (required)
Specify the subnet in Classless Inter-Domain Routing (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.
If you want to tag the VIP pool with a specific VLAN on the data network, enter the VLAN number (0-4096). See also Tagging VIP Pools with VLANs.
Optionally specify a domain name to associate with the VIP pool for DNS resolution by the VAST Cluster DNS server. If a domain suffix is defined in the Step 4: Configure DNS-Based Load Balancing and Forwarding, it is appended to the domain name to form a FQDN.
Set this to Protocols for data network access.
If you want to dedicate a specific group of CNodes to the VIP pool, open the drop-down and select all the CNodes you want to include in the group. The VIPs in this pool will only be distributed among the selected CNodes.
If you do not specify any CNodes, the pool will be distributed among all active CNodes.
The virtual IP pool is saved. IP addresses from the pool are assigned automatically to the CNodes. You can view the assigned virtual IPs per CNode on the Virtual IPs tab.
Please read DNS-Based Load Balancing, choose how you would like to set up load balancing and follow one of the suggested configurations.
The call home feature sends non sensitive data from your VAST Cluster to our central support server to enable us to provide proactive analysis and fast response on critical issues.
Follow these steps to:
Complete your call home settings. This is the only way we can ever know that the data we collect from your VAST Cluster is yours!
Run our test to make sure that your VMS can send callhome bundles. If needed, set up firewall rules to allow the VMS to send callhome bundles.
From the left navigation menu, select Settings and then Call home.
Complete the settings:
Your customer name.
The name of the site where the cluster is installed.
The location of the site.
Max upload concurrency
The maximum number of parts of a file to upload simultaneously to the AWS S3 bucket.
The frequency with which system state data is sent to the support server. Disabling the setting stops system state data being sent.
The frequency with which debug data is sent to the support server. Disabling the setting stops debug data being sent.
Switch this to the ON position.
Enter proxy server details if you would like the data to be sent through your own proxy server.
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.
Sets the production support server as the destination for callhome bundles. It's essential to enable this setting.
Enables VAST Data Support to run remote bundle collection commands on the cluster.
Click Test Call Home. A test callhome bundle is sent.
Check the test bundle is sent successfully:
Go to the Activities page (open the menu again and select Activities). Find a task named send_interactive_callhome. When the task is done, its status should change to Completed and its log should record Callhome bundle sent.
Contact Support and check that the test callhome message was received in our #support slack channel.
If the callhome bundle is not sent successfully, you may need to set up firewall rules to allow the callhome bundle to be sent.