The NetQ software contains several components that must be installed, including the NetQ applications, the database, and the NetQ Agents. NetQ can be deployed two ways:
- Hosted on premises: This deployment model is used when you want to host a single NetQ site and have it be entirely contained on your premises. In this implementation, all NetQ components including the NetQ Platform software, hardware, and database are located on your premises. The NetQ applications and database are installed as a single entity, called the NetQ Platform, and are run on the NetQ On-premises Appliance or NetQ On-premises virtual machine (VM). Note that you are responsible for installing, configuring and maintaining all NetQ components. This deployment model is called the on-premises solution in this documentation. It is suitable for organizations with data residency requirements like GDPR (general data protection regulation).
- Hosted remotely: This deployment model is used when you want to either set up multiple NetQ premises or use the NetQ Cloud service. In this implementation the NetQ aggregation and forwarding application software, called the NetQ Collector, is installed and run on the NetQ Cloud Appliance or NetQ Cloud VM on premises with a common database and all other applications installed in a single NetQ site or in the NetQ Cloud. In the multi-site implementation, you are responsible for all software, hardware, and the database. In the cloud service implementation, you are responsible for the on-premises NetQ Collector and NVIDIA is responsible for the data storage in the NetQ Cloud. This deployment model is called the remote solution in this documentation.
With either deployment model, the NetQ Agents reside on the switches and hosts being monitored in your network.
NetQ Data Flow
For the on-premises solution, the NetQ Agents collect and transmit data from the switches and hosts back to the NetQ On-premises Appliance or virtual machine running the NetQ Platform software, which in turn processes and stores the data in its database. This data is then provided for display through several user interfaces.
For the remote solution, multi-site NetQ implementation, the NetQ Agents at each premises collect and transmit data from the switches and hosts at that premises to its NetQ Cloud Appliance or virtual machine running the NetQ Collector software. The NetQ Collectors then transmit this data to the common NetQ Cloud Appliance or virtual machine and database at one of your premises for processing and storage.
For the remote solution, cloud service implementation, the NetQ Agents collect and transmit data from the switches and hosts to the NetQ Cloud Appliance or virtual machine running the NetQ Collector software. The NetQ Collector then transmits this data to the NVIDIA cloud-based infrastructure for further processing and storage.
For either remote solution, telemetry data is then provided for display through the same user interfaces as the on-premises solution. When using the cloud service implementation of the remote solution, the browser interface can be pointed to the local NetQ Cloud Appliance or VM, or directly to netq.cumulusnetworks.com.
You must make several choices to determine what steps you need to perform to install the NetQ system:
- You must determine whether you intend to deploy the solution fully on your premises or if you intend to deploy the remote solution.
- You must decide whether you are going to deploy a virtual machine on your own hardware or use one of the NetQ appliances.
- You must determine whether you want to install the software on a single server or as a server cluster.
- If you have an existing on-premises solution and want to save your existing NetQ data, you must back up that data before installing the new software.
The documentation walks you through these choices and then provides the instructions specific to your selections.
Deploying the NetQ servers in a cluster arrangement has many benefits even though it’s a more complex configuration. The primary benefits of having multiple servers that run the software and store the data are reduced potential downtime and increased availability.
The default clustering implementation has three servers: 1 master and 2 workers. However, NetQ supports up to 10 worker nodes in a cluster, and up to 5000 devices in total (switches, servers and hosts). When you configure the cluster, configure the NetQ Agents to connect to these three nodes in the cluster first by providing the IP addresses as a comma-separated list. If you later add more nodes to the cluster, you do not need to configure these nodes again.
The Agents connect to the server using gRPC.
Cluster Deployments and Kubernetes
NetQ also monitors Kubernetes containers. If the master node ever goes down, all NetQ services should continue to work. However, keep in mind that the master hosts the Kubernetes control plane so anything that requires connectivity with the Kubernetes cluster — such as upgrading NetQ or rescheduling pods to other workers if a worker goes down — will not work.
Cluster Deployments and Load Balancers
You need a load balancer for high availability for the NetQ API and the NetQ UI.
However, you need to be mindful of where you install the certificates for the admin UI (port 8443) and the NetQ UI (port 443); otherwise, you cannot access the NetQ UI.
If you are using a load balancer in your deployment, we recommend you install the certificates directly on the load balancer for SSL offloading. However, if you install the certificates on the master node, then configure the load balancer to allow for SSL passthrough.
Installation Workflow Summary
No matter which choices you made above, the installation workflow can be summarized as follows:
- Prepare the physical server or virtual machine.
- Install the software (NetQ Platform or NetQ Collector).
- Install and configure the NetQ Agents on switches and hosts.
- Install and configure the NetQ CLI on switches and hosts (optional, but useful).
Where to Go Next
Follow the instructions in Install the NetQ System to begin installing NetQ.