Before You Install

This overview is designed to help you understand the various NetQ deployment and installation options.

Installation Overview

Consider the following deployment options and requirements before you install the NetQ system:

*Exact device support counts can vary based on multiple factors, such as the number of links, routes, and IP addresses in your network. Contact NVIDIA for assistance in selecting the appropriate deployment model for your network.

Deployment Type: On-Premises or Cloud

On-premises deployments are hosted at your location and require the in-house skill set to install, configure, back up, and maintain NetQ. This model is a good choice if you want very limited or no access to the internet from switches and hosts in your network.

In the cloud deployment, you host only a small, local server on your premises that connects to the NetQ cloud service over selected ports or through a proxy server. NetQ cloud supports local data aggregation and forwarding—the majority of the NetQ applications use a hosted deployment strategy, storing data in the cloud. NVIDIA handles the backups and maintenance of the application and storage.

In all deployment models, NetQ agents reside on the switches and hosts they monitor in your network.

Server Arrangement: Single or Cluster

Single Server

A standalone server is easier to set up, configure, and manage, but limits your ability to scale your network monitoring. Deploying multiple servers allows you to limit potential downtime and increase availability by having more than one server that can run the software and store the data. Select the standalone, single-server arrangement for smaller, simpler deployments.

Cluster of Servers

NVIDIA offers two types of cluster deployments: cluster and scale cluster. Both deployments offer high-availability and provide redundancy in case of node failure.

The cluster implementation comprises three servers: one master and two workers nodes. NetQ supports high availability using a virtual IP address. Even if the master node fails, NetQ services remain operational. 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. During the installation process, you configure a virtual IP address that enables redundancy for the Kubernetes control plane. In this configuration, the majority of nodes must be operational for NetQ to function. For example, a three-node cluster can tolerate a one-node failure, but not a two-node failure. For more information, refer to the etcd documentation.

As an alternative to the three-node cluster deployment with a virtual IP address, you can use an external load balancer to provide high availability for the NetQ API and the NetQ UI.

The scale cluster deployment supports large networks and offers the highest level of scalability, allowing you to adjust NetQ’s network monitoring capacity by adding additional nodes to your cluster as your network expands. For example, you can deploy a three-node scale cluster that accommodates up to 1,000 switches. When you add more switches to your network, the extensible framework allows you to add two additional nodes that can accommodate a network of up to 2,000 switches. NVIDIA recommends this on-premises option for networks comprising 100 or more switches with 100 or more interfaces per switch.

Base Command Manager

NetQ is also available through NVIDIA’s cluster management software, Base Command Manager. Refer to the Base Command Manager administrator and containerization manuals for instructions on how to launch and configure NetQ using Base Command Manager.

Next Steps

After you’ve decided on your deployment type, you’re ready to install NetQ.