Users Guide

Troubleshooting Your Application | Troubleshooting
706 OMNM 6.5.3 User Guide
Using this software’s features, you can create alarms and reports for each. Best practice is to use
both polling and event-based protocols. Tune the polling frequency and event granularity for the
specific environment, topology, bandwidth, and notification needs. See the specific Monitor
performance recommendations.
NOTE:
Creating a baseline performance measurement report of availability, capacity and performance can
provide the basis of capacity planning and proactive network management.
Reachability may vary by protocol (for example, Telnet works, but not ping), so test multiple
protocols. If it is remote, try phoning the affected site and asking for information.
Missing Performance Data/Monitor Stops Polling
This is a problem related to missing performance monitor data accompanied by logs errors like the
following:
2014-02-12 11:23:45,357 705304239 ERROR
[com.dorado.core.mediation.base.OWMediationDeploymentHelper]
(WorkManager(2)-63:) The currently deployed targets for polling
subscription oware.polling.PollingSubscriptionDO::59x8vSybkeEj6I2 on
mediation partition MED_PART-medPartition have somehow become out of
synch with the application server and database.
Actual target count, coming from the database: 184 meditation server
currently has: 0
We are now resynching this information from the appliation server to the
mediation server so that it will once again be accurate.
This error indicates that your mediation servers have no current performance monitor subscription
targets when 184 targets were expected. This could possibly be due to a mediation server fail-over
to another cluster member or a mediation server coming back on-line, etc. This is an expected error
when a difference is detected in the expected (database) monitor subscriptions and actual
subscriptions in the mediation server. A periodic process executes to ensure performance monitor
subscriptions remain in sync.
Solution(s):
• Verify connectivity between application servers and mediation servers.
• Verify mediation server state/health and cluster member status (active/inactive).
• Verify polling subscriptions in the Monitor Editor.
• Verify polling skip/miss counts in the Monitor Editor.
• Review number of targets in each monitor, verify each has 10,000 or fewer targets. Monitor
any targets over that figure in a new monitor.
• Restart the mediation server process if subscription problems persist.