Hardware requirements

Contents

Hardware requirements

Hardware requirements

Nexthink Appliance

The Appliance consists of a Linux-based 64-bit operating system and all the packages needed to run one of the server components of Nexthink: the Portal or the Engine. The Portal and the Engine must be installed in separate physical or virtual machines, except for some small setups, where they can share the same appliance. When installed in virtual machines, hardware requirements may vary depending on the load of the infrastructure. Color codes in some of the given figures indicate the minimum requirements for new installations (red), and the recommended settings (blue) for the current version of Nexthink.

Nexthink officially supports VMware and Hyper-V as virtualization platforms, but both the Portal and the Engine may run on any other virtualization platform of your choice. In all cases, your server must be powered by a 64-bit compatible processor (AMD64 or Intel 64 -not Itanium- architecture). The vast majority of AMD and Intel processors currently available in the market comply with this requirement.

Beware that some versions of popular virtualization platforms may impose particular limits on the number of CPUs and amount of RAM that you can assign to a virtual machine. In installations with many devices, the possible maximum values may not reach the specified requirements. Likewise, in virtualized environments with high load, the performance of IO operations may not be sufficient for the Portal or the Engine to write to disk normally. In case of doubt, please contact Nexthink Customer Success Services to validate your virtualized setup.

Portal complexity

To help you size the Appliance for hosting the Portal, we define a metric called complexity. The complexity of a setup, along with the number of licensed devices, gives you an idea of the computation power required by the Portal for that particular setup:

complexity = entities * hierarchies * (max_levels + 2)

Where:

  • entities is the total number of entities across all Engines;
  • hierarchies is the total number of hierarchies;
  • max_levels is the number of user-defined hierarchy levels for the hierarchy which has the largest number of levels (excluding both the root level and the entity level).

Physical Appliances

For an Appliance built with dedicated hardware, find below the tables with the hardware requirements for hosting either the Portal or the Engine. The following definitions apply:

CPU cores
Number of CPU cores required by the Appliance. The reference model for a CPU core in a physical Appliance is a single CPU core of an Intel Xeon E5-2695 v3 @ 2.3 GHz. Fewer CPU cores may be required when using newer or faster CPUs in an Appliance. Please, contact Nexthink Support for more information. Likewise, depending on the measured performance of a specific setup and its particular CPU models, Nexthink may ask customers to increase the number of CPU cores in the Appliance to keep system usability up to acceptable levels.
Memory
The amount of RAM required by the Appliance. As for the type of RAM, the minimal requirement for all configurations is DDR3-1600 with data rate of 1600 MT/s.
Nexthink Portal
Max devices Max complexity Memory Disk Details (90 days) CPU cores Network
500 500 6 GB 40 GB 8 GB 2 100 Mbps
5k 500 8 GB 60 GB 60 GB 2 100 Mbps
10k 500 8 GB 100 GB 120 GB 4 100 Mbps
20k 1 000 12 GB 200 GB 220 GB 4 100 Mbps
50k 3 000 16 GB 300 GB 450 GB 6 100 Mbps
100k 10 000 32 GB 600 GB 700 GB 6 1 Gbps
150k 15 000 48 GB 1 TB 1 TB 8 1 Gbps
>150k Ask Ask Ask Ask Ask Ask
  • The Portal requires at least 10 MB/s of disk throughput.
  • The total maximum number of entities across all Engines is limited to 2 000.
  • The maximum number of enabled metrics is limited to 500. If you define more than 500 metrics, those in excess are disabled (not computed).

The quantities in the Details column correspond approximately to the additional disk space required to store 90 days of historical details of count metrics. Add the value in the Disk column to the value in the Details column to get the total disk space required. For more information, see the article about data retention in the Portal.

Configure the Portal to make the most out of your hardware resources.

Nexthink Engine
Max Events Max devices / with Web & Cloud Max entities Memory Disk CPU cores Network Disk throughput
20M 500 / 500 20

5 GB
5 GB

80 GB

2
3

100 Mbps 5 MB/s
50M 3k / 2k 100

9 GB
10 GB

100 GB

5
6

100 Mbps 10 MB/s
50M 5k / 3-4k 100

9 GB
10 GB

120 GB

5
6

1 Gbps recommended 15 MB/s
100M 10k / 6-8k 100

14 GB
16 GB

200 GB

10
12

1 Gbps recommended 25 MB/s
  • Color codes:
    Red: Minimum requirements for a new installation.
    Blue: Recommended settings.
  • The maximum number of supported devices for each configuration depends on the amount of web activity and the Web & Cloud privacy configuration.
  • If you install the Collector in servers, take into account for the sizing of the Engine that a single server is roughly equivalent to 20 normal devices.
  • The indicated number of cores include 20 simultaneous Finder users. If more than 20 users access Nexthink Engine simultaneously, 1 additional core is required for each 5 users (up to a maximum of 24 cores).
  • Tests under controlled conditions have demonstrated that the Engine is capable of dealing with up to 100 normalized Finder users when run on a 24 cores appliance (20 users for the first 8 cores + 16 cores * 5 users per core).
  • A normalized user is characterized for querying the Engine once every 25 seconds with a query that takes 10% of a core dedicated to the Engine. If Finder users deviate too much from this behavior, the number of supported users may vary drastically. Note as well that any other kind of query to the Engine (such as queries to the Web API) reduces the number of supported users.
  • The maximum number of entities per Engine is described in the table above.
  • The maximum number of supported mobile devices for all Engine configurations is 5 000.

Virtual Appliances

As virtualized hardware behaves differently from physical hardware and it is modeled with more flexible settings, find below a separate list of hardware requirements and range of settings for virtual Appliance to support the operation of the Engine, which is the component where the differences between virtual and physical environments is more noticeable.

It is important to note that many aspects of the usage of Nexthink and your infrastructure can affect the performance and requirements of the VMs. Any of the following points must be taken into account to derive the hardware requirements:

  • Infrastructure
    • Type of hypervisor
    • Load on the physical host by other VMs
    • vCPU to pCPU ratio
    • IOPS
  • Nexthink usage
    • Complexity (as described above)
    • Concurrent Finder sessions
    • Traffic sent by devices (activity on the devices)
    • Total number of:
      • Devices
      • Metrics
      • Services
      • Scores
      • Categories
      • Remote actions

As the number of possible combinations is unmanageable, Nexthink simply recommends and supports the following hardware requirements for a virtual Appliance that hosts Engine:

Nexthink Engine
Max Events Max devices / with Web & Cloud Max entities Memory Disk vCPUs CPU shares Mhz allocation to resource pool Network Disk throughput
20M 500 / 500 20 5 GB 80 GB 2 normal from 0.5 to 2 Ghz per vCPU 100 Mbps 5 MB/s
50M 3k / 2k 100 8-10 GB 100 GB 4 normal from 1 to 2 Ghz per vCPU 100 Mbps 10 MB/s
50M 5k / 3-4k 100 8-10 GB 120 GB 4-6 normal from 1 to 2 Ghz per vCPU 1 Gbps recommended 15 MB/s
100M 10k / 6-8k 100 14-16 GB 200 GB 8-10 normal from 1 to 2 Ghz per vCPU 1 Gbps recommended 25 MB/s

For vCPUs and their allocated MHz, it is fine to go with the lower value of the range if there is proper monitoring of the infrastructure in place. In case of performance issues, Support will ask you the monitoring information (CPU ready ratio, co-stop, RAM usage, ...) and will most probably ask you to increase your settings.

Regarding memory requirements, as the Engine is an in-memory database, it really depends on the way the hypervisor will address memory overcommitment with our appliance OS and Engine process. If the hypervisor can find and consolidate memory pages with identical content from the Engine VMs on the same host, it could be ok to overcommit. Again, in case of performance issues, Support will ask you the monitoring information about memory usage and overcommitment and may ask you to increase your settings.

Running Nexthink in a single appliance

For very small installations the Portal and the Engine can run on the same physical and virtual appliance.

Max devices 1 000
Max complexity 500
Events 20M
Memory

14 GB
16 GB

Disk capacity 120 GB
Disk write speed 10 MB/s
CPU cores

5
6

Network 100 Mbps
  • Color codes:
    Red: Minimum requirements for a new installation.
    Blue: Recommended settings.

Nexthink traffic redirection service

The Collector traffic redirection service (nxredirect) is a tool included in the Engine appliance that resends activity information (UDP traffic) received from the Collectors to one or more additional Engines. Optionally, the redirection service is able to anonymize sensitive Collector data on the fly.

The hardware requirements of nxredirect depend on the service being run alongside the Engine or in an appliance where the Engine has been stopped:

Nxredirect is run alongside the Engine
The maximum number of supported devices is 10 000 without anonymization, or 5 000 if anonymization is switched on. The hardware requirements of the Engine apply (see table above). No additional hardware is needed.
Nxredirect is run independently (i.e. the Engine has been stopped)
The maximum number of supported devices depends heavily on anonymization being switched on or off, ranging from 5 000 up to 350 000 devices.

Assuming an average traffic per device as indicated in the product overview of the Collector, the hardware requirements of nxredirect are as follows:

  Max devices Anonymization CPU cores Memory Disk
Nxredirect + Engine 5 000 On Engine reqs Engine reqs N/A
10 000 Off
Nxredirect alone 5 000 On 2 5 GB N/A
350 000 Off

External backups

The disk space requirements given for the Appliance already take into account the amount of space needed to keep up to ten internal backups of either the Portal or the Engine.

In the case that you activate external backups, Nexthink recommends you to reserve the following quantities of external storage, depending on the size of your setup. The figures indicate the file size for each individual backup.

Nexthink Portal

The backup size for the Portal depends on the number of devices, the complexity, the amount of history and the number of widgets and reports. We recommend regularly monitoring the used capacity and adapting it based on actual needs.

Max devices External backup size
5k 3 GB
10k 5 GB
20k 10 GB
50k 15 GB
100k 30 GB
150k 50 GB

Nexthink Engine

The disk requirements for the backup of the Engine are more predictable than those of the Portal and only depend on the number of events stored in the Engine.

Max events External backup size Network throughput
20M 2 GB 5 MB/s
50M 4 GB 15 MB/s
100M 8 GB 25 MB/s

Mobile Bridge

To collect information from mobile devices synchronized via ActiveSync with Microsoft Exchange, the Mobile Bridge uses a Remote PowerShell connection to your Exchange Server.

Install the Mobile Bridge on a dedicated Windows Server 2008 R2 or later. The hardware requirements for the Mobile Bridge are those same ones recommended by Microsoft for installing their operating system. The Mobile Bridge is compatible with Exchange 2010 SP2 or 2013.

Nexthink Collector

Without Web & Cloud With Web & Cloud
Disk 1 MB
Network card Any, wireless or wired
Average network bandwidth 100-150 bps 150-250 bps

Nexthink Finder

Starting from Nexthink V6.3, the Finder supports high DPI screens. When setting DPI scaling in Windows, the Finder adapts its size properly.

Memory 4 GB system memory, at least 2 GB available
Disk capacity 50 MB
CPU 2 cores, 2 GHz
Network 100 Mbps recommended


Mobile Bridge

To collect information from mobile devices synchronized via ActiveSync with Microsoft Exchange, the Mobile Bridge uses a Remote PowerShell connection to your Exchange Client Access server.

Install the Mobile Bridge on a dedicated Windows Server 2008 R2 or later. The hardware requirements for the Mobile Bridge are those same ones recommended by Microsoft for installing their operating system. The Mobile Bridge is compatible with Exchange 2010 SP2 or 2013.

Nexthink Collector

Without Web & Cloud With Web & Cloud
Disk 1 MB
Network card Any, wireless or wired
Average network bandwidth 100-150 bps 150-250 bps

Nexthink Finder

Starting from Nexthink V6.3, the Finder supports high DPI screens. When setting DPI scaling in Windows, the Finder adapts its size properly.

Memory 4 GB system memory, at least 2 GB available
Disk capacity 50 MB
CPU 2 cores, 2 GHz
Network 100 Mbps recommended

Certified Hardware List

Nexthink V6 appliances include a Linux-based operating system that is derived from the freely distributed sources of a major North American Enterprise Linux vendor. This vendor maintains a list of supported hardware that has been tested and is certified to work with its Linux distribution. To help you choose your hardware for your appliances (the Portal and one or more Engines), verify that it is in the following list: