Owners Manual

Monitoring Network Availability | Performance Monitoring
420 OMNM 6.5.2 User Guide
Scheduling Refresh Monitor Targets
Because monitors can address targets that are members of dynamic groups, refreshing these ensures
that group memberships are up-to-date. To do this, you can create or alter the schedule for Monitor
Target Refresh (in most packages, such a scheduled item appears by default). When executed, this
updates monitors with groups as targets based on current memberships. This removes targets no
longer members of a monitored group and adds new group members. A seeded schedule refreshes
these every six hours, by default.
Refresh Monitor manually by right-clicking in the Resource Monitors table.
Refresh Monitor Targets for Newly Discovered Devices
If you discover a new device that is part of a monitored dynamic group, it may take some time
before monitoring includes that device. To provide immediate monitoring, as soon as discovery
finds the device, add the
Refresh Monitor action to the discovery profile. See Actions on page 98
for more about that Discovery Profile capability.
To make sure this refresh occurs, do
not override the following in redcell.properties (This
section defines the actions executed when no default discovery profile exists):
#This shows the default order of Task Activities within Resource Discovery
Options
#The TaskDefOid will be used for identification and true/false will
determine if they are
#on by default
#format: <TaskDefOid>&&true,<TaskDefOid2>&&false,<TaskDefOid3>&&true
redcell.discovery.taskactivity.order=Resync&&true,\
DataCollectionForGroupOfDevices&&false,\
Discover_Links_for_a_Group_of_Devices&&false,\
Scheduled_Resync&&false,\
Refresh_Monitor_Targets&&true
Topological Correlation
A device can appear unresponsive in monitors if devices through which OpenManage Network
Manager must access it are down, even though it may be active independently of the condition of
its access. Topological correlation take this into account, and produces fewer false
MonitorTargetDown events because OpenManage Network Manager attempts to communicate
with adjacent devices to the first device in the network topology. OpenManage Network Manager
calculates adjacency according link configuration. If adjacent devices are unreachable, then
OpenManage Network Manager does not generate a MonitorTargetDown event because this first
device is simply unreachable from OpenManage Network Manager at the moment.
Updating Polling Subscriptions
Polling subscriptions on the mediation agent process can get out of sync with the application server
process. When the application server and mediation agent start running, whichever one comes
online last triggers application server sending the polling subscription and target information to the
mediation server. Enabling or disabling performance monitors also sends this information from the
application server to the mediation server.