Owner's Manual

ManualsBrandsDell ManualsSoftwareDell OpenManage Network Manager Version 5.1

2012-5 Rev. A02

Open Manage Network Manager – Release Notes

Package Release Numbering: 5.1

The following is the format for release/version numbers:

<ProductID>.<Major Version>.<Minor Release>.<Maintenance

Release>.<Build #>

When contacting Customer Support, please refer to the complete release number

for components, which is in the Manage > Show Versions Box. The versions men-

tioned below refer to component versions rather than the package. Numbers in

parentheses following comments below identify the issue number (SCR).

NOTE:

You can upgrade to this release only from OMNM 4.4. Upgrades from previous versions of OMNM

are not supported. Upgrade from OMNM 5.0 is also possible.

—If you upgrade, you must re-register any additional licenses you have purchased by opening the

Settings > Permissions > Register Licenses menu, and locating the license upgrades for what you

have installed previously. To get such updated licenses, go to www.doradosoftware.com/dell/

upgrade-info.html (3446)

—Upgrading from version 4.4 to version 5.1 changes the OpenManage Network Manager Admin

user account password to admin (18694)

—J-Series devices are not supported in this release of OpenManage Network Manager

—Desktop shortcuts may open the older application after an upgrade. Best practice is to delete

these icons before upgrading (18926)

—Upgrading from previous versions requires a new license to activate new features. (18747)

Some devices may not appear in the Currently Managed license viewer totals. B-

Series, and W-Series devices do not count toward the Dell totals after an upgrade

installation. (18655)

CAUTION:

Do not install this software when a command or oware shell is open. Close the shell first.

Some notes below refer to OpenManage Network Manager as OMNM.

Significant New Features in This Release

The following sections are describe features and issues with this release. For sup-

ported hardware see Supported Functionality and Equipment on page 7, and Sup-

ported Powerconnect B-Series Devices on page 12. To see a detailed list of supported

devices and their operating systems, open the index.html file in the Supported-

Devices directory of your OMNM installation package.

Some of this release’s new capabilities include the following:

Adaptive CLI for the web—Customize-able scripts to manage devices.

Traffic Flow Analysis —See Traffic Flow Analysis on page 13. The default license

limits the number of devices to five, but you can upgrade. See the OMNM User

Guide for how.

Summary of content (13 pages)

PAGE 1
Open Manage Network Manager – Release Notes Package Release Numbering: 5.1 The following is the format for release/version numbers: .... When contacting Customer Support, please refer to the complete release number for components, which is in the Manage > Show Versions Box. The versions mentioned below refer to component versions rather than the package. Numbers in parentheses following comments below identify the issue number (SCR).
PAGE 2
Change Management / Proscan—See Change Management on page 13 Report templates—In addition to pre-configured reports, you can customize your own. Performance Monitoring—Monitor a variety of customize-able metrics. W-Series devices—Now supported. For issues with these, see W Series on page 6. Consult the OMNM User Guide for more details about these.
PAGE 3
• Custom Debug—For more advanced users, any component under owareapps can define a log4j.xml file for each component matching the following pattern: owareapps\\server\conf\*log4j.xml Consult these files for categories you want to change, and copy those (altered) properties to the file you created in owareapps\installprops. The categories altered in this file override any others. • The internal FTP/TFTP file server is not supported on Linux.
PAGE 4
Installation • Upgrading from previous versions may update device Model numbers. After upgrade is complete, you may need to edit pre-existing filters that refer to model numbers for them to function correctly. Also after the upgrade is complete, the model numbers for Powerconnect B-Series fabric devices may not change until you perform a resync on them. (18794) • Checking Allow Strangers to create accounts may produce a defective login screen.
PAGE 5
• In some cases a single managed object may be discoverable via multiple IP addresses. Each discovered IP creates a new inventory object and will count against any licensed Right To Manage total. Workaround: Network elements should be managed through a single interface/IP. Additional discovered interfaces should be deleted leaving only one managed object in inventory.
PAGE 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 '.
PAGE 7
(main:oware:service=InventoryStateMonitorMBean InventoryStateMonitorMBean) ... (11554) • If you are upgrading from a previous version, you must close all shells in which the oware script is running. (38571) • In Linux, clicking Go makes columns in some managers squeeze to the left. Workaround: Use a Windows Client. (38314) • You cannot give a user permission to configure authentication without giving him permission to access all managers.
PAGE 8
• Dell has discontinued support for the PC3024, PC3048, PC3324, PC3348, PC3248, PC5012, PC5212, and PC5224 models, although this software may still discover and manage these.
PAGE 9
• When you upload a Force 10 image into OpenManage Network Manager, then Deploy it to a group of devices, then you will see five options for image type. Choose only the first option for this to work. (18952) • You may see multiple options for selecting the configuration file to backup for PowerConnect (not Force10) devices.
PAGE 10
• When a restore service error appears for a TI24x it contains no details. No further action is necessary. (14906) • Stacking ports are not visible for 8024/F devices running 4.2.x firmware. (16951) • Adaptive CLI CoS Interface settings: The bandwidth is optional but if you specify a single queue, you must insure the total bandwidth of all queues is 100. (16840) • In OpenManage Network Manager, Adaptive CLIs can be used to reset one or more devices.
PAGE 11
Total Deletes, Total Drops, and Total Ageouts do not appear correct, as they are in the CLI. Workaround: Rebooting switch sets the Last Update back to zero. Once done, the LLDP Stats works again. (8213) • Cable Tests on ports in a stack may fail, producing the message Test has not been preformed. Workaround: Make sure the management (master) switch is set to Unit-1 in the stack. (8129) • Some discrete configuration (Resource editor) screens do not appear or are inoperable in Web client.
PAGE 12
• You must typically increase the timeout for firmware deployment of multistack devices. Stop the Dell OpenManage Network Manager service in Windows., edit the file powerconnect/lib/dellpc.property, and set PC_NR_TIMEOUT = 10000000. (6681) • To disable LAG Spanning Tree on a 62xx, you must set the Path Cost to a minimum of 1. Leaving path cost at 0 will cause an SNMP error. (6304) • Dell devices have an SNMP Management Station entry in their web pages that specifies a destination for SNMP communication.
PAGE 13
device has multiple links, only one of the links can be discovered.The rest are discarded by OMNM as duplicates because the Local Port ID is supposed to be unique. (12464, 12409) • OMNM will not telnet connect to some devices if they use the factory default password. You must set the password to something other than that default. OMNM does not recognize the additional prompt asking that default password be changed each time log in occurs.