Dell OpenManage Network Manager Release Notes 5.1 - Page 6

Issues Resolved

Page 6 highlights

6 • 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) • If a problem occurs during firmware deployment, the error message displayed may not specify the cause. Failed connectivity may produce a message like "Error pattern '.*(is required ' matched 'already full'" Workaround: For such messages, the content of the error message, visible at the bottom of the audit screen, may provide more information. Click the message in the top of the audit screen to read its contents in the bottom of the screen. (18636) • Backing up W-Series iAP devices is not supported (18560) • You may experience difficulties when using 3CServer as your FTP server. Workaround: Use 3CDaemon (08525) 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 evaluates the filter. Workaround: Best practice is using resource name(s) instead of IP addresses. (12532) • Events with no corresponding definition appear as alarms of indeterminate severity. The only way to change behavior of an unknown event in this version would be to locate the missing MIB and load it into the system. This creates the missing event definition(s) needed to specify explicit behaviors. W Series • For IAP configured as Virtual controllers and with multiple IP addresses, the Device may appear more that once in the resource manager with the additional IP addresses as configured on the device. (18895) • Deploying a firmware image on an Access Point is not supported, regardless of any error message that may encourage you to try again. (18637) • Because of a device limitation, the Network Details snap panel is empty for these devices. (16418) • When a device does not have the enable mode enabled, a benign error may appear on login. You can safely ignore this error. (18492) Issues Resolved General • Editing and saving a port's status changes OpenManage Network Manager's database, not the port itself. (19230) • Application server no longer conflicts with IIS. Workaround: Stop the IIS process. (14367, 16248) • The first time you start a fresh installation, a benign error message may appear that begins as follows: 2010-07-28 13:36:13,286 160972 WARN [com.dorado.redcell.ddi.common.DDIDefinitionEventFactory]

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13

6
• 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)
• If a problem occurs during firmware deployment, the error message displayed
may not specify the cause. Failed connectivity may produce a message like
"Error pattern '.*(is required ' matched 'already full'"
Workaround:
For such
messages, the content of the error message, visible at the bottom of the audit
screen, may provide more information. Click the message in the top of the
audit screen to read its contents in the bottom of the screen. (18636)
• Backing up W-Series iAP devices is not supported (18560)
• You may experience difficulties when using 3CServer as your FTP server.
Workaround:
Use 3CDaemon (08525)
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
evaluates the filter.
Workaround:
Best practice is using resource name(s)
instead of IP addresses. (12532)
• Events with no corresponding definition appear as alarms of indeterminate
severity. The only way to change behavior of an unknown event in this ver-
sion would be to locate the missing MIB and load it into the system. This cre-
ates the missing event definition(s) needed to specify explicit behaviors.
W Series
• For IAP configured as Virtual controllers and with multiple IP addresses, the
Device may appear more that once in the resource manager with the addi-
tional IP addresses as configured on the device. (18895)
• Deploying a firmware image on an Access Point is not supported, regardless
of any error message that may encourage you to try again. (18637)
• Because of a device limitation, the Network Details snap panel is empty for
these devices. (16418)
• When a device does not have the enable mode enabled, a benign error may
appear on login. You can safely ignore this error. (18492)
Issues Resolved
General
• Editing and saving a port’s status changes OpenManage Network Manager’s
database, not the port itself. (19230)
• Application server no longer conflicts with IIS.
Workaround
: Stop the IIS
process. (14367, 16248)
• The first time you start a fresh installation, a benign error message may
appear that begins as follows:
2010-07-28 13:36:13,286 160972 WARN
[com.dorado.redcell.ddi.common.DDIDefinitionEventFactory]