This section explains how to enable Cloud-Based Monitoring and Remote Support for your Qumulo cluster.

How Cloud-Based Monitoring Works

Enabling Cloud-Based Monitoring lets the Qumulo Care team monitor your Qumulo cluster proactively.

Qumulo Care Response Times

We use a proprietary application that aggregates diagnostic cluster data and alerts the Qumulo Care team if an issue arises. Depending on the issue severity and cluster state, a member of the Qumulo Care team reaches out. The following table outlines Qumulo Care response times.

Severity Level Service Availability Response Time Description Common Examples
Sev0 24×7 30 minutes

Business Impacting: A Qumulo cluster is offline, impacting regular business operations, with potential productivity or financial losses.
  • A Qumulo cluster is unable to form a quorum
  • A Qumulo cluster is unable to maintain a quorum
Sev1 24×7 1 hour High Priority: A Qumulo cluster is operational. However, a node is offline or the cluster experiences a severe performance degradation.
  • A node in a Qumulo cluster is offline.
  • Multiple business units experience degraded performance.
Sev2 24×5 2 hours Normal Priority: A Qumulo cluster and the Qumulo Core software are operational. However, an issue with the cluster or moderate performance degradation causes applications to operate suboptimally.
  • CPU cores recover to normal operation
  • Drive failures (within expected parameters)
  • Inconsistent performance issues
Sev3 24×5 6 hours Low Priority: A Qumulo cluster or the Qumulo Core software experiences an issue, cosmetic Web UI defect, or minor performance degradation that has minimal or negligible impact on a production system or regular business operations.
  • PSU failure
  • Loss of communication with Cloud-Based Monitoring
  • Upgrade issues
Sev4 24×5 6 hours Informational: Informal inquiries about product functionality
  • Questions about Qumulo Core configuration
  • Documentation requests
  • Qumulo Care Slack channel access permissions

Ways to Get Help

The Qumulo Care team is always here to help you. You can contact us by using any of the following ways.

How Remote Support Works

Enabling Remote Support lets the Qumulo Care team access your Qumulo cluster solely to assist you with a software update or perform diagnostics or troubleshooting on your cluster from the command line.

When you install VPN keys in the /etc/openvpn directory, an authorized member of the Qumulo Care team uses SSH to connect to the ep1.qumulo.com server and then uses SSH through a secure VPN connection to connect to your cluster (normally, this VPN connection is closed).

By default, the VPN tunnel remains open for four hours to allow members of the Qumulo Care team to perform operations such as uploading logs to monitor.qumulo.com or to a secured Amazon S3 bucket and sending diagnostic data to a private Amazon EC2 instance for analysis.

You can configure the connection period and enable or disable Remote Support at any time.

What Data Gets Sent to Qumulo

Cloud-Based Monitoring and Remote Support let your cluster send the following detailed diagnostic data to Qumulo through an encrypted connection.

  • Cluster name

  • Number of nodes in cluster

  • Hardware and software incidents

    • Drives

      • CRC errors

      • S.M.A.R.T. status alerts

      • Capacity triggers

    • Nodes

      • PSU failure

      • Fan failure

      • Recused node

      • Offline node

      • Unreachable cluster

    • Qumulo Core

      • New process core dump

  • Configuration data (such as users, groups, SMB shares, and NFS exports)

  • Logs, stack traces, and code dumps

Prerequisites

Before you can use Cloud-Based monitoring and Remote Support, you must:

  • Install VPN keys on your Qumulo cluster

  • Enable the following destination hostnames for TCP on port 443.

    Hostname Description
    api.nexus.qumulo.com Nexus monitoring
    ep1.qumulo.com

    Remote Support
    api.missionq.qumulo.com Cloud-Based Monitoring connectivity
    missionq-dumps.s3.amazonaws.com Proxy forwarding
    monitor.qumulo.com Cloud-Based Monitoring log uploads

Enabling Cloud-Based Monitoring

You can enable Cloud-Based Monitoring by using the Qumulo Core Web UI or qq CLI.

To Enable Cloud-Based Monitoring by Using the Qumulo Core Web UI

  1. Log in to the Qumulo Core Web UI.

  2. Click Support > Qumulo Care.

  3. On the Qumulo Care page, do the following:

    1. In the Cloud-Based Monitoring section, click Edit.

    2. Click Yes, I want Qumulo Cloud-Based Monitoring and then click Save.

If your configuration is valid, the Qumulo Core Web UI shows the status Enabled | Connected.

To Enable Cloud-Based Monitoring by Using the qq CLI

  • To enable Cloud-Based Monitoring, run the qq set_monitoring_conf --enabled command.

  • To disable Cloud-Based Monitoring, run the qq set_monitoring_conf --disabled command.

  • To check the status of Cloud-Based Monitoring, run the qq monitoring_conf command.

Enabling Remote Support

You can enable Remote Support by using the Qumulo Core Web UI or qq CLI.

To Enable Remote Support by Using the Qumulo Core Web UI

  1. Log in to the Qumulo Core Web UI.

  2. Click Support > Qumulo Care.

  3. On the Qumulo Care page, do the following:

    1. In the Remote Support section, click Edit.

    2. Under Do you want to enable Qumulo Remote Support?, click Yes and then click Save.

If your configuration is valid, the Qumulo Core Web UI shows the status Enabled | Connected.

To Enable Remote Support by Using the qq CLI

  • To enable Remote Support, run the qq set_monitoring_conf --vpn-enabled command.

  • To disable Remote Support, run the qq set_monitoring_conf --vpn-disabled command.

  • To check the status of Remote Support, run the qq set_monitoring_conf command.