This section explains how to enable Nexus Remote Support for your Qumulo cluster.
To let the Qumulo Care Team provide fast support when you need it most, we strongly recommend enabling Nexus Remote Support.
How Nexus Remote Support Works
Nexus 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 register your Qumulo cluster with Nexus, you create a public-private key pair (your cluster holds the public key and Nexus holds the private key). Qumulo Core uses the public key to establish an encrypted outgoing connection that authenticates REST API operations from Nexus securely.
When you register your Qumulo cluster with Nexus to enable Remote Support, Qumulo Core adds and assigns the qumulosupport:everyone trustee to the Qumulo-Support RBAC role. This RBAC role determines the level of REST API access that Nexus gives to the Qumulo Care Team. For more information, see the Qumulo-Support section in Managing Role-Based Access Control (RBAC) for Users and Groups.
- When the Qumulo REST API is unavailable (for example, if your Qumulo cluster is out of quorum), the Qumulo Care Team can't use Nexus Remote Support to troubleshoot issues with your cluster. In this type of scenario, contact the Qumulo Care Team for assistance.
- Nexus Remote isn't compatible with HTTP proxies.
Prerequisites
Before you can use Nexus Remote Support:
-
Enable TCP traffic on port 443 for the
api.nexus.qumulo.comhostname to allow Nexus Monitoring and Nexus Remote Support connectivity
To Enable Nexus Remote Support by Using the qq CLI
Run the qq set_monitoring_conf
with the --nexus-enabled flag and specify your registration key. For example:
qq set_monitoring_conf \
--nexus-enabled
--nexus-registration-key "1A2B3CDEF4"
To disable Nexus Remote Support, run the
qq set_monitoring_conf
command with the --nexus-disabled flag.