Follow these essential post-installation steps to get VAST Cluster configured and ready to use.
Important
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).
-
Browse to:
https://<VMS_VIP>/, where<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 VMS user account credentials:
-
username:
admin -
password:
123456
Note
VAST Cluster has one factory default VMS user account. You cannot delete the factory default VMS user account or reduce its permissions. After first time login, you can change the password for the default VMS user, create additional VMS users, and/or configure role based access with LDAP groups. For all options, see Authorizing VMS Access and Permissions.
-
-
Click Login.
You're now logged into the VAST Web UI and you're viewing the Dashboard.
Important
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.
-
Click Update.
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.
Note
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.
-
On the Virtual IP Pools tab, click + Create VIP Pool and complete the fields:
Field
Description
Tenant
Specifies which tenant the VIP pool should serve.
Name
Enter a name for the VIP pool.
Gateway IPv4
Enter an IPv4 address for the gateway.
The gateway IPv4 address is required if your storage clients are on multiple IPv4 subnets and you are routing the client storage traffic through a local gateway.
Gateway IPv6
Enter an IPv6 address for the gateway.
The gateway IPv6 address is required if your storage clients are on multiple IPv6 subnets and you are routing the client storage traffic through a local gateway.
Subnet CIDR IPv4 (required if using IPv4)
Specify the subnet in Classless Inter-Domain Routing (CIDR) notation for IPv4.
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.
Subnet CIDR IPv6 (required if using IPv6)
Specifies the subnet in Classless Inter-Domain Routing (CIDR) notation for IPv6.
In CIDR notation, the subnet is expressed as the number of bits of each IP address that represent the subnet address. For IPv6, this is known as IPv6 prefix length. For example, the prefix length of /32 in 2001:db8::/32 would include IP addresses from 2001:db8:: to 2001:db8:ffff:ffff:ffff:ffff:ffff:ffff.
VLAN
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.
CNodes
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.
If Port Membership for the VIP pool is set to RIGHT or LEFT, only right or left ports on the selected CNodes will be used for load balancing in this VIP pool.
Role
Select a role for the VIP pool:
-
Protocols to enable network access to data stored on the VAST cluster.
-
Replication to create a VIP pool dedicated to VAST native replication.
-
Big Catalog to create a VIP pool dedicated to Big Catalog.
Note
If you are going to use Big Catalog but do not create a dedicated VIP pool for it, a single internal IP will be used.
VMS Preferred
Enable this setting if you would like the CNodes that are assigned VIPs from this pool to belong to a preferred domain for VMS failover. For more details, see Configuring Network Access.
Port Membership
Determines which port (right or left) in a group of CNodes is allocated to the VIP pool. For more information, see Configuring Network Access. By default, all ports on the pool's CNodes are included in the VIP pool.
Enable L3
Reserved for future use. Must be disabled.
VAST ASN
Reserved for future use.
Peer ASN
Reserved for future use.
VAST DNS Configuration: VIP Pool Domain Name
If you are using the VAST Cluster DNS server, specify a domain name to associate with the VIP pool. The domain suffix is defined in the DNS server configuration, is appended to the VIP pool domain name to form a fully qualified domain name (FQDN). Requests for that FQDN will be allocated VIPs from this pool.
The FQDN formed from the current value entered into the field and the domain suffix is displayed below the field as the DNS Service FQDN.
IP Ranges List
A set of IPv4 or IPv6 addresses that belong to the VIP pool, which can include multiple different contiguous ranges. For each range, add the Start IP and End IP in the fields provided. To add a range, click the Add IP Range button.
To remove a range, click the Remove button for that range.
-
-
Click Create.
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 VIP Distribution, choose how you would like to set up load distribution and DNS forwarding 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.
The data we collect is sent by HTTPS to a VAST Data AWS S3 bucket that we maintain for this purpose. For details, see the VAST Data Security Guidelines.
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 call home bundles. If needed, set up firewall rules to allow the VMS to send call home bundles.
-
From the left navigation menu, select Settings and then Call Home.
-
Complete the settings:
Field
Description
General Setup
Customer
Your customer name.
Site
The name of the site where the cluster is installed.
Location
The location of the site.
Max upload concurrency
The maximum number of parts of a file to upload simultaneously to the AWS S3 bucket.
Intervals Setup
Log frequency
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.
Enabled
Switch this to the ON position.
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
Sets the production support server as the destination for call home bundles. It's essential to enable this setting.
Support channel
Enables VAST Data Support to run remote bundle collection commands on the cluster.
Obfuscates data in call home bundles, metrics and heartbeats. The following types of information are replaced with a non-reversible hash: file and directory names, IP addresses, host names, user names, passwords, MAC addresses.
Sets the compression method used to compress call home bundles:
Cloud
Optionally, register the cluster with VAST Uplink. For more information, see Registering the Cluster with Uplink.
-
Click Save.
-
Click Test Call Home. A test call home 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 call home message was received in our #support slack channel.
If the call home bundle is not sent successfully, you may need to set up firewall rules to allow the call home bundle to be sent.
-
You can continue to manage the VAST Cluster via the VAST Web UI or the VAST CLI.
Comments
0 comments
Article is closed for comments.