Owners Manual

Troubleshooting Your Application | Troubleshooting
OMNM 6.5.2 User Guide 705
Alarm/Performance/Retention
If you install your system to monitor alarms, and experience sluggish performance or a rapidly
filling database, several remedies are available.
• Configure “chatty” devices emitting many alarms to stop doing so.
• Configure your system’s Suppress Alarms feature to keep performance the database’s capacity
at acceptable levels
• Reconfigure your system’s database archiving policy feature to archive alarms more often so
the database does not fill up.
Retention Policies
Retention policies tune how long your system retains data. These policies also have built-in limits
(raw, hourly, daily) that help to avoid potential performance/storage problems. The potential
impact when going outside these thresholds is significant and generally not recommended.
Configure retention policies with the following limits in mind:
• Maximum # of days to retain daily data: 180
• Maximum # of days to retain hourly data: 14
• Maximum # of days to retain raw data: 1
Network Monitoring
You can monitor your network’s performance two ways.
• Scheduled polling-based monitoring is more reliable, and specific. It also has a lower impact
on network. It may, however, lag behind network events.
• Event-based monitoring (typically Traffic Flow Analysis, syslog and SNMP) is more up-to-
date, but, can be less reliable. It also often does not disclose the root cause of a problem.
• This software does not support Traffic flow analysis on sFlows from devices using sFlow earlier
than v5. Typical error content reads “Data array too short” if you have an unsupported sFlow
version.
• Traffic Flow Analyzer support in OpenManage Network Manager collects and process flows
with source and destination IP address. Switches or devices that only support L2 flow payloads
with MAC address as the source and destination payload are not currently supported.
Example: Juniper XE devices.
NOTE:
Typical packages come with a default limit to the number of monitored devices. Upgrade your license if
you want to exceed the package limit. Because of the performance demands they make, Traffic Flow
exporters are licensed separately from the managed resource license count, so a license to manage 50
devices does not necessarily let you have 50 Traffic flow exporters.
Also: The application discards IP v6 flow packets.
NOTE:
Does Traffic flow not appear when it’s expected? Have you made sure the device is registered to display
traffic flow (right-click in resources Traffic Flow Analyzer > Register)?
• Each monitor should have 10,000 or fewer targets. Use a new monitor to track any targets
exceeding that number. The general best practice is to have fewer targets distributed across
several monitors.