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.
Call home includes the following data collections:
Logs which are collected into compressed bundles at a configurable interval (call home bundles).
Metrics data objects that are converted into CSV files and uploaded for analysis.
Heartbeats, a small set of metrics collected from the cluster and used to monitor cluster health.
Call home bundles are sent over HTTPS via port 443. There is an option to use a proxy server. If you need to configure firewall rules in order to enable outbound traffic on port 443, see How to allow Vast CallHome through a firewall .
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 General Setup fields:
Your customer name.
The name of the site where the cluster is installed.
The location of the site.
Max upload concurrency
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 call home bundles. It's essential to enable this setting.
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:
Optionally, register the cluster with VAST Uplink. For more information, see Registering the Cluster with Uplink.
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.
To fill out your call home settings via CLI, use the following commands.
For full CLI command syntax, including VAST arguments, enter the command at the CLI prompt in the <command> <subcommand> format provided in the table, followed by ?.