|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 |
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.
Once you know device counts and have an idea of the virtual server (yes you can use physical servers) specifications, it is a good idea to get an idea of baseline performance.
The baseline is to establish how NMIS and the virtual server are performing, add ~50 nodes and see how it is performing. We have a customer polling ~200 nodes and the average poll cycle is about 20 seconds. So if you are able to poll 50 nodes in less than 20 seconds your performance should be OK, if it is longer than this, then you might need to look at CPU and Disk performance. This will also give you an idea of memory footprint.
Adding Nodes to NMIS
If you want to stop the polling and then run an update cycle, then a collect cycle manually, then start the polling.
To stop polling modify the configuration option global_collect to false or stopping polling in the crontab, comment out this line:
Then add nodes, all of them at once or in batches. Restart fpingd so that it reloads all the nodes you added.
Then run an update manually with nohup, if you have 12GB of memory you can give it lots of threads, probably 20 should do it, but watch your memory usage you can probably get to 30 threads.
This will take a while to run the first time, when it finishes, run a collect cycle the same way
Now all the big disk activity is done and you should be able to start NMIS polling by letting the poller go again.
The other BIG consideration is what is your polling policy, the more interfaces you collect on, the more disk, cpu and memory you will consume, just collecting more data may not help you operationally, collect the right data, which is how NMIS has been configured.
If you hare having problems scaling your NMIS installation, you could contact Opmantek for assistance.
Using JSON for NMIS Database
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 server in an NMIS cluster and this should be co-ordinated to run very close together.
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.