We’re running a primary polling engine, four auxiliary polling engines and a dedicated web server to a separate physical SQL2005 server. All the polling engines are running on VMware platforms and are performing well. We will be deploying additional servers soon, but it takes time to get approval! We currently track about 20000 NPM elements and 2000 APM components. We’re running NPM 9.5 SP4 with APM modules loaded across all of the engines. Additionally NCM, NTA & VoIP are loaded on the primary polling engine and the web server. All product is SLX/ALX/DLX
We are looking at continuing the expansion and need to better understand the “unlimited” limits so that I can pre-arrange budget for when it is needed. My management do not like shocks!
I realise that physical polling engine servers top out around 8000 elements while VMs should be limited to 7000 and that adding more elements can be achieved by installing another auxiliary polling engine.
I understand that the recommended count is 2000 per ALX instance, but what is an instance? I have APM polling engine modules on every one of my NPM polling engines and they are set as Poller Bound, but does this count as one instance or multiple instances. The Admin > APM Settings > Licence Summary only shows the total count and the fact that it is “unlimited”. Is it 2000 per auxiliary polling engine or 2000 per primary NPM/APM. If this counts as only one instance, how do I expand the APM component polling?
I understand that the recommendation for NetFlow is a max of around 400 source interfaces per NetFlow instance. But I only see my primary polling engine listed as a NetFlow Collector. How can I distribute collectors across my auxiliary polling engines to expand this limit?
As more users access Orion from more locations, it could be useful to deploy a second additional web server. Is this possible?
I realise that I could deploy multiple primary engines and then consolidate with the EOC, but that seems an expensive and over–complex solution. Being able to expand by just adding another engine has to be the simplest and most scalable option.
I’d appreciate any guidance on scalability of these modules.