Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

NCM scripts dont run on devices configured to Polling Engines

I have been hitting my head against the wall on this. I have run jobs over and over and get no results. I am finding that if the device that I want to run a script or a job against is configured on a polling engine and not the main app server, it wont run. I get "No devices to run job on this engine" with the jobs. I configured a script to execute and it ran against the switches that were configured on the main engine, but is stuck on initializing for all the switches that are configured to a polling engine.

Am I doing something wrong? How do I run a script against a switch that is configured to a polling engine?

Find more posts tagged with

disa_stig

Compliance

Accepted answers

usuee

We upgraded to NCM 7.3 and now it is working correctly. Switches that are configured to a polling engine are being configured with that polling engine.

Yeah!

All comments

zackm

It sounds like you have your NCM setup to run all jobs from the primary polling engine.

http://www.solarwinds.com/NetPerfMon/SolarWinds/wwhelp/wwhimpl/js/html/wwhelp.htm#href=OrionNCMPHPollerEngineNodeHelp.ht…

Settings > NCM Settings > Polling Engine Configuration for NCM

If you are load balancing your NCM nodes across additional polling engines, you need to setup those polling engines to run NCM jobs as well. The other option would be to locate all of your 'NCM Nodes' on you primary engine and then use you additional polling engines to load balance all of the devices not managed through NCM.

-ZackM

Loop1 Systems: SolarWinds Training and Professional Services

LinkedIN: Loop1 Systems
Facebook: Loop1 Systems
Twitter: @Loop1Systems

usuee

Just checked the NCM settings. I have additional polling engines checked under the Polling Engine Configuration for NCM. I have to run the scripts off the polling engines as I have a firewall between the main poller and the additional polling engines.

I checked by trying to execute a script on a switch that is polled by a polling engine and it is stuck on initializing.

zackm

Make sure that the target nodes are native the the originating engine.

For example:

Polling Engine A has Router1
Polling Engine B has Firewall3

Any script(s) that run against Router1 MUST be run from Polling Engine A.

Likewise, script(s) for Firewall3 MUST be run from Polling Engine B.

You can easily edit polling engine assignments in bulk through Manage Nodes > Edit Settings

usuee

How do you run a script from a polling engine? Maybe that is what I am doing wrong.

I am going under Config to Configuration Manager. Selecting Execute Script and entering my script. When I hit Next, I get to pick out the nodes I want to execute the script on. I never get to say from where.

Another question about this, how do I cancel tasks that are stuck at initializing under Transfer Status? I have quite a few stuck now.

Thanks for your help, too.

jeffnorton

SO if you upgraded to NCM 7.3, the only option now is run NCM distributed across all pollers. The jobs set up now has a validate function to insure that all job results destinations land in a working directory. The only hitch here is that the landing spot requires that the main poller and all additional pollers have a landing spot that is in the same directory structure for all servers, there is no option to specify directory structure on a server by server basis. In our case our main poller was on a server with a C: and drive where C: contains the os and the os dependent Orion files and d: contains the non os dependent Orion files. We were trying to land results on the and because none of the additional poller have a drive it was failing