Dell OpenManage Network Manager Version 5.1 Owner's Manual

Open Manage Network Manager – Release Notes

NOTE:

CAUTION:

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).

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)

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.

2012-5 Rev. A02

2

NOTE:

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.

Although JUNOS can be selected from the OpenManage Network Manager firmware download
page, firmware download to JUNOS devices is not supported in this release. (18806)

General

Highlights of the functionality in this release appear listed below. Consult the
OMNM User Guide for more information about these features:

•

• Network views now appear with their (saved) name as a label in the title bar.
Labels appear when you re-load the saved view or load an existing one.
(17905)

Known Issues

General

• Reports—Some reports or templates may appear pre-seeded that are not sup­ported by OpenManage Network Manager. For example, pool reports may
appear for programmatic restrictions on pooled assets like IP addresses, or
Route Targets that may not be supported. (18882)

• Firmware change reports may not always report changes to device firm­ware.(18665,19359)

• The Hardware Change report may erroneously display devices that just had a
firmware upgrade or downgrade (19358)

• SSH with

• Virus Warnings—Two files installed with this product—

md5sum.exe

a virus detection warning for these files during installation, take no action.
You may want to turn off virus detection while installing.

• Installing Perl—This application does not package Perl. If you want to use
the Perl scripting features, you must install it.

You can find information about Perl at www.perl.com. Follow the downloads
link to find the recommended distribution for your specific platform. One of
the recommended Perl packages is from ActiveState which can be found at:

www.activestate.com/activeperl/

Make sure your system has Perl installed on both the application and media­tion server hosts. You must verify the executable is on the system path. If you
install it after you install this application, best practice is to reboot that host
to ensure the path recognition.

stricthostkey checking = yes

—may trigger warnings with some anti-virus software. If you get

is not supported (05350)

bash.exe

or

• Custom Debug—For more advanced users, any component under owareapps
can define a
tern:

owareapps\<component-dir>\server\conf\*log4j.xml

Consult these files for categories you want to change, and copy those
(altered) properties to the file you created in
categories altered in this file override any others.

• The internal FTP/TFTP file server is not supported on Linux. Nevertheless, the
Test button remains active, and will cause an error if used in that context.
(01326)

• Server Start Delay—The Windows tray icon may prematurely indicate appli­cation server has started. Workaround: Wait a little, and the application
server will catch up to the icon. (18778)

• Pool maximum allocations defaults to 0, even though more allocations are
potentially available. Workaround: Enter the correct number in the Max
Allocations field of the Pool editor. (18188)

• Device links to themselves may appear as squares surrounding the device in
“Visualize my network” screens. (18718)

• Performance capabilities have been completely reconfigured. When upgrad­ing from previous versions, you must (re-)create dashboards from scratch.
(18700)

• The following require manual migration (export, then import) from previous
versions: SMTP settings. Some scheduled items, .

Saved topologies / visualization must be re-created. Suggestion: take a screen­shot before you upgrade.

User Names / Passwords, and User Groups (Roles) are not automatically reas­signed and must be created manually.

Group Operations have been deprecated, replaced by Adaptive CLI.

Command monitors must be reconfigured to refer to Adaptive CLIs, which
now can refer to external scripts.

(18693)

• The Organization User in Roles has no description. Its features are covered in
the online help and User Guide. (18669)

• OMNM drops SNMP V3 traps when the V3 traps auth (userid) is unknown.
Workaroun d: Use an SNMP monitor, for example polling sysUptime, to get
data from the device. Once this occurs, the proper auth is then known and
OMNM accepts the trap. (18574)

• Installation may display a JBoss null pointer exception ZipEntryContext
error. This stems from a bug in JBoss 5.1, and is benign. (18612)

• Internet Explorer has a problem importing MIBs. Workar ound: Use a differ­ent browser to import MIBs. (HD-376)

• In the Port report, the Model column refers to the model of the port. This col­umn is not currently supported by Dell devices. (17540)

• Disabling ICMP ping in Discovery Profiles can also disable the Inspect fea­ture. Workaroun d: Enable ICMP Ping Devices (as it is by default). (18146)

log4j.xml

file for each component matching the following pat-

owareapps\installprops

. The

3

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 com­plete, 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. (17364)

• CORBA is no longer supported, but SOAP and Web Services have improved,
and CORBA orbs often support these. (11513)

• Windows 2008 Terminal Server is not supported. The installer becomes non­responsive with Data Execution Prevention enabled. This option is disabled
by default on Windows Server 2008, but is enabled on a Windows Server
2008 machine running Terminal Server. (02310)

• During uninstall on Windows 2008 Server, the uninstaller Java process does
not exit correctly. This leaves files on the machine. Workar ound: Either man­ually kill the Java process in the task manager or restart the system. It is safe
to remove the remaining files after the process has been terminated. (14089)

Web Client

• Audit trails do not always show deleted equipment names after the device
becomes unmanaged. To see such information, use Java client. (17097)

• Audit Trail may show blanks for the Subject column in the Audit Trail portlet.
This is because some audited tasks are targetless (No subject). (17643)

• NoClassDefFoundError errors can occur during application server startup if
the portal tries to access classes in the application server too soon. The portal
does this if portlet calls occur during appserver startup. Workaround: Restart
application server. (15854)

• Adding a page when the focus is on a page with sub-pages does not save it to
the menu bar. Workarou nd: Create pages in the Manage > Page menu or cre­ate one after selecting a page with no submenus. (15909)

• In a Windows 7 environment Internet Explorer may not fully display all
menu items. Workaroun d: Use Firefox, Chrome or Safari as the browser.
(13320)

• Exporting to Excel does not work in Internet Explorer. Workar ound: Ctrl +
click the Excel export button in OpenManage Network Manager. (13456)

• Clicking My Assets in the toolbar repeatedly may halt portlets. Work around :
Restarting the browser, or signing out and signing back in lets things work
again. This is the result of built-in phishing protection. (10942)

• Mutlitab browsing is not supported and may produce unpredictable results.
(10963)

• In a job viewer window, some audit trail messages may appear too narrow to
read in their entirety. Workaroun d(s): Enlarge the browser and the job
viewer window grows bigger (maximized, you will see more of the message).
The job viewer window lets you copy and paste the message text into applica­tions like notepad for less restricted viewing and for additional message anal­ysis. (16320)