| Table of Contents |
|---|
Overview
Opmantek gets many questions on how to scale NMIS8 for very large networks. There are many factors impacting polling performance and the upper limits of polling is really only limited by the number of processor cores, available memory and disk IO performance. We have customers managing 10's of 1000's of nodes using NMIS.
| Table of Contents |
|---|
Related Articles
- Scaling NMIS polling - how NMIS handles long running processes
- Configuration Options for Server Performance Tuning
Server Specifications
| Small | Medium | Large | Massive | |
|---|---|---|---|---|
| OS Storage | 20GB | 20GB | 20GB | 20GB |
| Data Storage | 40GB | 60GB | 140GB | 280GB |
| Memory | 2GB | 4-8GB | 8GB | 16GB+ |
| CPU | 2 x vCPU | 2 to 4 x vCPU | 4 to 6 x vCPU | 8+ vCPU |
| Device Count | < 500 devices | < 1500 devices | < 2500 devices | A very large |
| Element Count | 2000 elements | 8000 elements | 14000 elements | A very large number of elements |
Elements are additional data being collected, an interface is an element, a CBQoS class is an element.
An element requires additional SNMP polling to collect the values and then storage on the disk to save the data.
...
| Code Block |
|---|
*/2 * * * * /usr/local/nmis8/bin/nmis.pl type=summary 4-59/5 * * * * /usr/local/nmis8/bin/nmis.pl type=threshold |
In Config.nmis:
| Code Block |
|---|
'threshold_poll_cycle' => 'false', 'nmis_summary_poll_cycle' => 'false', 'disable_interfaces_summary' => 'true', |
...
To optimise how NMIS files are saved, you can use the JSON database, this will require NMIS 8.4.8g or greater. The following needs to be run on every master and slave poller server in an NMIS cluster and this should be co-ordinated to run very close together.
| Code Block |
|---|
/usr/local/nmis8/admin/convert_nmis_db.pl |
This script will stop NMIS polling, convert the database files, update the NMIS configuration to use the new database format, then start the polling again.
...