EOC Polling does not finish

eI recently installed Enterprise Operations Console 1.4.1 concurrently on a server hosting NPM 10.4 and NTA 3.10.

It is working as expected, except for gathering information from the NPM/NTA instance installed on the same server. In that case, the polling/processing gets stuck at 75%. It is showing the number of interfaces in that NPM instance, but not the number of nodes.

I am not seeing any errors in any server event logs that would show why this is failing. Also, utilization on the server is less than 50% on both memory and cpu, and disk I/O has not increased noticeably since installation of EOC. I saw a notice about EOC 1.3 and NPM 10.3 not being compatible when using IIS6. Is that still the case and should I follow the steps to resolve that?

Any suggestions would be greatly appreciated.

Thanks!

Find more posts tagged with

eoc

npm

Polling

eoc_orion_comunication

Accepted answers

kmmorey

It is now working. I set the polling interval to 2400 seconds overnight, and it finally finished sometime between midnight and this morning. I'm going to monitor it today to see if I can lower that polling interval to something a little more useful.

If I run into any further issues with it, I will contact support. Thanks!

All comments

jan.tauwinkl

I would suggest opening a support ticket for this.

kmmorey

If I run into any further issues with it, I will contact support. Thanks!

jan.tauwinkl

Can you check how many traps or sylogs do you have in that Orion? Some devices on the network can generate a lot of traps or syslogs (hundred of thousands per day) and EOC then needs some time to download this data into its database.

kmmorey

Our syslog database keeps sending threshold alerts. It's consistently between 19 million and 21 million rows. Our retention policy is set for 30 days. We recently made some network changes which appear to be sending a lot of syslog messages. I'll be looking at that to see if we can't lower the number of messages we're getting.

I have been able to get the polling time back down to 5 minutes without running into any issues with the polling cycle finishing, so it may have needed that extra time at the beginning for initial processing.