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 bundles are sent over HTTPS via port 443. There is an option (below) 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 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 General Setup fields:
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.
To fill out your call home settings via CLI, use the following commands.
For full CLI command syntax, including arguments, enter the command at the CLI prompt in the <command> <subcommand> format provided in the table, followed by ?.
Article is closed for comments.