Dell OpenManage Network Manager Release Notes 5.2 - Page 4

File Management, Event Management

Page 4 highlights

4 Manage Network Manager assumes it is the starting IP address for the range. If you specify an address in the middle of the subnetwork then OpenManage Network Manager may discover devices outside of that subnetwork. This also means that IP addresses in the network that precede the specified address are not discovered. To avoid these issues, use the CIDR specification of the network to discover rather that the subnet ID. (16803) • Link discovery currently does not find one-ended links. (16305) • Devices not implementing LLDP MIBs with complete and correct data will prevent OMNM from discovering links for the device. Also some devices encode STP data collected via SNMP in a way that is difficult to decipher. In these cases, the algorithm OMNM logs a warning message "Problem determining designated port encoding algorithm" during device link discovery. (16438) • The Red Hat system clock can differ one hour from the application server clock. (15524) • When OMNM status icon in the tray is green and you select procman ("process manager") restart from Windows' Control Panel services, an error message appears saying the service did not stop properly. The tray icon then turns white. Since the application server is still running, when you try to restart procman again from control panel, the icon turns red. Workaround: Stop all Java and WMI processes in the process manager. A system reboot also re-initializes the OWProcMan (process monitor). Note that the service name may be different if your package has been specifically branded. The executable path for the service is \....\oware\bin\owprocman.exe. (16335) • The password confirmation field in the user account (My Account) settings always says claims entered passwords do not match. Workaround: Save an empty password, then enter the new password and resave. (13504) • After rebooting the web server host, you may have to manually restart the Tomcat/Synergy Service manager that appears in the system tray. To get the manager back into the system tray, navigate to the Menu item under OMNM > Synergy Manager. This puts the manager back into the system tray if you want to actively monitor the service. (14386) • Saving a network view (topology) and marking it as default prevents reverting to the original default view without deleting the saved default view. (15463) File Management • In some circumstances the File Server test produces a narrow window. Workaround: Right-click the listed server in the File Servers portlet and select Test. (18870) • Backing up W-Series iAP devices is not supported. (18560) Event Management • OpenManage Network Manager keeps a record in the My Alerts/Action History when you change Event Definitions. Those entries' Details field is blank in the My Alerts/Action History.(18942) • OMNM supports multiple IP addresses per resource. During event processing, filters that include IP address criteria may behave incorrectly when OMNM

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9

4
Manage Network Manager assumes it is the starting IP address for the range.
If you specify an address in the middle of the subnetwork then OpenManage
Network Manager may discover devices outside of that subnetwork. This also
means that IP addresses in the network that precede the specified address are
not discovered. To avoid these issues, use the CIDR specification of the net-
work to discover rather that the subnet ID. (16803)
• Link discovery currently does not find one-ended links. (16305)
• Devices not implementing LLDP MIBs with complete and correct data will
prevent OMNM from discovering links for the device. Also some devices
encode STP data collected via SNMP in a way that is difficult to decipher. In
these cases, the algorithm OMNM logs a warning message "Problem deter-
mining designated port encoding algorithm" during device link discovery.
(16438)
• The Red Hat system clock can differ one hour from the application server
clock. (15524)
• When OMNM status icon in the tray is green and you select procman (“pro-
cess manager”) restart from Windows’ Control Panel services, an error mes-
sage appears saying the service did not stop properly. The tray icon then turns
white. Since the application server is still running, when you try to restart
procman again from control panel, the icon turns red.
Workaround:
Stop all Java and WMI processes in the process manager. A sys-
tem reboot also re-initializes the OWProcMan (process monitor). Note that
the service name may be different if your package has been specifically
branded. The executable path for the service is
\
....
\oware\bin\owprocman.exe
. (16335)
• The password confirmation field in the user account (My Account) settings
always says claims entered passwords do not match.
Workaround:
Save an
empty password, then enter the new password and resave. (13504)
• After rebooting the web server host, you may have to manually restart the
Tomcat/Synergy Service manager that appears in the system tray. To get the
manager back into the system tray, navigate to the Menu item under OMNM
> Synergy Manager. This puts the manager back into the system tray if you
want to actively monitor the service. (14386)
• Saving a network view (topology) and marking it as default prevents reverting
to the original default view without deleting the saved default view. (15463)
File Management
• In some circumstances the File Server test produces a narrow window.
Workaround: Right-click the listed server in the File Servers portlet and select
Test. (18870)
• Backing up W-Series iAP devices is not supported. (18560)
Event Management
• OpenManage Network Manager keeps a record in the My Alerts/Action His-
tory when you change Event Definitions. Those entries’ Details field is blank
in the My Alerts/Action History.(18942)
• OMNM supports multiple IP addresses per resource. During event processing,
filters that include IP address criteria may behave incorrectly when OMNM