What are the requirements for adding a new poller to NPM? Do I require to purchase a second NPM license?
Thanks
System requirements for an Additional Polling Engine are the same as system requirements for a primary NPM polling engine. Yes you will need an additional license.
Hardware
SL100, SL250, or SL500
SL2000
SLX
CPU Speed
2.0 GHz
2.4 GHz
3.0 GHz
Note: Dual processor, dual core is recommended. Physical Address Extension (PAE) should not be enabled.
Hard Drive Space
2.5 GB
5 GB
20 GB
Note: A RAID 1 drive for server operating system, Orion installation, and tempdb files is recommended. Orion requires at least 1.5GB for job engine, information service, collector service, MIB database and other required files. The Orion installer needs 1GB on the drive where temporary Windows system or user variables are stored. Per Windows standards, some common files may need to be installed on the same drive as your server operating system. For more information, see “Working with Temporary Directories”.
Memory
3 GB
4 GB
Hope this helps!
I want to recycle this question from 2012 for an actual 10.6 multiple polling engine deployment...
There is now this feature "stackable" additional polling engines - supporting multiple (up to 3) pollers to be installed on the same single NPM server (I think since 10.4)
Now with this feature, do I also have to multiply the NPM hardware requirements for a single poller as described above?
So for 3 pollers I would need a server like:
3x dual core cpu @ 3GHz ?
12 GB RAM ?
60GB Hard Drive ?
Cannot find a documentation clarifying this - and it's not in the "Scalability Engine Guidelines" Doc....
Those specs would be a good starting point. Are you only collecting information for NPM or do you have other modules riding on the APE too? Typically we recommend a Dual Quad Core & 16GB of RAM.
Jeff
Thanks jeff.stewart, at the moment it's a pure NPM installation.
Looks like currently only NPM supports Stackable Poller feature?
This brings me to another question:
If I run multiple modules like SAM with NPM and only NPM reached a limit e.g. >12k elements, but SAM is still under SLX counts...
Is it still supported to run the Scalability Engine in stacked mode on the same hardware with same IP?
Does it make sense in general to do Stackable mode in multiple module operation?
Maybe it's better to use always a seperate polling servers, so no additional migration step is necessary when another module reaches hardware SLX limits?
-Herwig
You are correct that NPM is the only product that support stackable polling engines today. You can still stack APEs even if you have other modules, however those modules won't be able to take advantage of the increased element counts. For example you could have a single server with NPM and SAM and add a stacked APE to get the following element counts;
NPM ~20,000-24,000
SAM ~8500-10,000
Hope that helps.
Please share URL.
