Users Guide

Known Issues
43
OMNM 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. (25134)
OMNM now shows the top N exporters if it finds no traffic flow data for a
selected resource in the selected time frame. (22335)
To see if a device is registered to display traffic flow in the Managed Resources
portlet, you must expand the portlet. You can then display the Registered column
in the portlet configuration menu (the wrench). (25101)
• The Freeform page layout may not work correctly, or may stack portlets on top of
one another. Workaround: Best practice is not to use it. (25111)
Limit monitor targets to 10,000 or less per monitor. The User Guide also offers
suggestions about how to manage such limitations. (hd-1940)
With SSL enabled, Firefox (v23.0.1) and Flash (v11.8) do not allow monitor
importing to work. Workaround: Use Chrome. (23671)
Java Security and Direct AccessSome Java installations may block self-signed
websites, interfering with Direct Access. The workaround is to provide a security
exception for the application server, as follows: (24736)
1. Click Start
2. Type
configure java
and hit [Enter]
3. Select the Security tab.
4. Click Edit Site List
5. Click Add
6. Type the Dell OpenManage Network Manager URL (example: http://
192.168.0.51:8080/
7. Click OK and Continue.
8. Apply this change, and/or click OK.
• If Max Items per Page in portlet displays does not retain your settings, it may
require second attempt. (24786)
Saving topology views works on Safari browsers version 6 +, but not older
versions (16336)
When attempting to access a device configured with SNMP v3, if you see an error
message like “unable to read device serial number for selected credential,“
discovery or other access fails. Workaround: This indicates the SNMP v3
credential is faulty. Correct it, and discovery and access should be available.
(19172)
Dell OpenManage Network Manager Traffic flow analyzes only IP-type traffic.
Consequentely the following parse errors can appear in the application server log
for some flow data.
Parse error: Unable to process non IP type flow. Type: <Number>
<Number> represents an Sflow packet type. This application only parses data of
type IP. When Dell OpenManage Network Manager receives non-IP packets, it
drops packets and this error appears. (23218)
You can safely ignore a Solaris shell message saying
solaris_install.bin
not
found. (19108)