Dell OpenManage Network Manager Instruction Manual

2012-4 Rev. A01
Open Manage Network Manager – Release Notes
Package Release Numbering: 5.0
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.
—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.0 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 10, and Sup-
ported Powerconnect B-Series Devices on page 14. 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 15.
Change Management / Proscan—See Change Management on page 16

2
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 9.
Consult the OMNM User Guide for more details about these.
NOTE:
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
• This release includes a driver enabling Windows Management Interface com-
munication with computers on the network (16082)
Highlights of the functionality in this release appear listed below. Consult the
OMNM User Guide for more information about these features:
• Renamed pre-processing rule selection menu items (from Frequency to Fre-
quency Throttle, for example), and updated editor screen labels (18605)
• Job screens that follow the execution of Actions like Show Adaptive CLIs now
contain a Results panel to display messages that result from the execution of
the Action. (17966)
• Selecting the type of device for filters now includes more user-friendly names
for types. (16984)
• Email Actions now include a checkbox option labeled Notify Associated Con-
tact. When enabled, notification emails go to the Contact associated with the
Managed Equipment for the notification event. For the contact's email
address, mail goes to the first specified address from either the Work Email,
Home Email or Other Email fields in the Contact editor. SMS messages go to
the Pager Email field for the contact. If a Contact was not found or the
required addresses are not specified for the Contact, then OpenManage Net-
work Manager uses the Recipient addresses configured in the Email Action.
(15639)
• Clicking Search now automatically puts the cursor in the search field. When
you click Search, the columns filtered in the database also appear indented.
For example, Name and Model appear indented in the Managed Resource por-
tal. (17982)
• 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)
• You can now Assign Labels context menu item for the Configuration Files
portlet. (17339)
• You can now mark a filter as Shared when creating a new filter from the Con-
tainer Membership panel. Shared Filters are available for selection by other
users along with System- and admin-created filters. (15302)
• Filter export and import is now supported. (17624)
• This version includes a dramatically re-designed web client. It includes move-
able portlets for OMNM functionality, texting and conferencing among users,
dramatically improved graphics, and many other features (11373).

3
• Direct Access / Cut thru now permits cut and paste to/from the screen, reset-
ting of font size, control of the history and page buffer (in 50-line incre-
ments), and changing the color of font/background (4001). It also can ping
the selected device, or open the default browser, pointed to the selected
device. (14887)
• You must download the latest Adobe Flash to see all the new features. (11014)
In addition to Adobe Acrobat Reader, and Perl, web client requires a browser
that is current. Best practice is to use the most recent Firefox, Safari or
Chrome, but Internet Explorer 9 or later works too.
• SuSe Linux is no longer a supported platform. (13610)
• This version includes support for Red Hat 6.
NOTE:
When installing to Redhat 6.0, you must install the Redhat “compatibility libraries” from Redhat's
package manager before OMNM can successfully install. (12964)
• Beginning with this package, OMNM supports only 64-bit Linux, and no
longer supports 32-bit Linux. The installation classes now appear in the file
linux64.jar .
• CORBA is no longer supported, but SOAP and Web Services have been
improved with Ajax technology, and CORBA orbs often support Web Ser-
vices. (11513)
• Web Service Port Change: Web Services now use port 8089 (not 80). (18051)
• This release now includes JBoss 5.1, and the HA-JNDI port has been changed
from 3100 to 1100.
As an Administrator, you can configure a portlet's default display filter, then
click the portlet name and re-name it. For example, make the default filter in
Managed Resources display only Dell Routers, then click Managed Resources
in the upper left corner of the portlet to rename it Dell Routers. (15971)
Device Support
This version of OMNM supports the Dell Force10 switches. It supports the follow-
ing capabilities:
• SNMP— Supports SNMP-based default device/resync using the ifTable - cre-
ates interface sub-components.
• Event Management—SNMP Trap Definitions (Tip: search for event definitions
with Notification OID containing “6027”).
• Reports—Run any default OMNM reports against Dell Force10 inventory.
• Any CLI-based functionality (NetRestore, CLI Cut-Thru, and MIB Browser)
• Link Discovery
• Port creation (14564)
• VLANs
Configuration File Management
• The application now selects the file server protocol for backup, restore or
deploy based on the most secure protocol the device supports. (15443)
• The File server can have an internal and external IP address. (11650)

4
• Configuration Changes comparisons work like this:
–If you select a config file that is version 1, no comparison option appears on
the menu since the selected version does not have a prior version.
– If you select a single config file of version 2 or higher, comparison is an
option. When selected, OMNM automatically compares against the prior ver-
sion for that device and file name.
–If you select two config files of any version, comparison is performed
between those two versions.
–If you select three or more config files, no comparison option appears.
–View option appears for on single selection only.
Event/Alarm Management
• New user interface.
• Collaboration lets you share alarms between logged-in users, or create confer-
ences to discuss them.
Known Issues
• Authenticating OpenManage Network Manager user accounts with Facebook
is not supported in this release (18671)
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)
• SSH with
stricthostkey checking = yes is not supported (05350)
• Virus Warnings—Two files installed with this product—
bash.exe or
md5sum.exe —may trigger warnings with some anti-virus software. If you get
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.
• Custom Debug—For more advanced users, any component under owareapps
can define a
log4j.xml file for each component matching the following pat-
tern:
owareapps\<component-dir>\server\conf\*log4j.xml

5
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. 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)
• User Account Control—This Application requires User Account Control be
disabled in Vista or any other operating systems with this capability (like
Windows Server 2008). (02311) Alternatively, you can run application server
as service. Another option is to run as administrator on startappserver. In
Vista, right click the startappserver icon and select run as administrator.
(08779)
• Telnet sessions—Telnet sessions are synchronous. You cannot interrupt a
command in progress with another command you send, unless you have
enabled something that periodically prompts for additional commands (for
example enabling line continuation prompts).
• 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.
Workaround: 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. Workaround: 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)

6
• Disabling ICMP ping in Discovery Profiles can also disable the Inspect fea-
ture. Workaround: Enable ICMP Ping Devices (as it is by default). (18146)
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)
• Suse Linux is no longer a supported platform. (13610)
• 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. Workaround: 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)
• [You can uninstall] by running the following on Linux:
$OWARE_USER_ROOT/_uninst/uninstall.sh
NOTE:
You must uninstall from Linux as root. No graphic wizard appears, and you must respond to the
command-line prompts as they appear.
(14597)
• Uninstalling—The uninstaller deletes
uninstall.exe if you press the cancel
button. After the canceling uninstallation, several directories and files remain
on disk that require manual deletion to completely uninstall. (00606)
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. Workaround: 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. Workaround: Use Firefox, Chrome or Safari as the browser.
(13320)

7
• Exporting to Excel does not work in Internet Explorer. Workaround: Ctrl +
click the Excel export button in OpenManage Network Manager. (13456)
• Clicking My Assets in the toolbar repeatedly may halt portlets. Workaround:
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. Workaround(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)
• 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 inter-
faces should be deleted leaving only one managed object in inventory.
(11540)
• Discovery—When specifying network addresses using the Subnet type, you
must specify the Network address at the beginning of the subnet since Open-
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)

8
• 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 view and marking it as default prevents reverting to the original
default view without deleting the saved default view. (15463)
• Intermittent issues and error messages appear related to Window 2008 plat-
form. (17143)
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)
• 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.
• Northbound action can now send as proxy. With this option set, there are no
issues with XP’s security patch, Vista or Server 2008. The application attempts
to spoof sourceIP on packet only when the proxy option is not selected.
(01737)
• Trap listener, Inform listener and all outbound SNMP requests must bind to a
specific interface in a multi-homed environment. This interface is considered
appropriate to use for all network-facing SNMP activity. By default, this is
localhost, interpreted as the application's local IP value (the NIC selected at
installation time). The following text in installed.properties provides a spe-

9
cific IP address to control outbound SNMP interface binding on the local
machine (22258):
#
# specific interface used for all NMS initated
# communications to the network
com.dorado.mediation.outbound.address=localhost
Include the following text and provide a specific IP address to control
inbound (listener) interface binding on the local machine:
#
# specific interface used for binding mediation
# listeners such as SNMP trap listener
com.dorado.mediation.listener.address=localhost
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
• 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]
(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. (24302)
(This is effectively resolved since Solaris 9 support ended with 5.7.6)

10
• The cursor position onscreen may temporarily conceal field contents in, for
example, the Equipment Editor screen (24224)
Event / Alarm Management
• The default database aging policy (DAP) exists for Events in Event History,
but is not scheduled, again by default. Events can come into the system at
fairly high rates, and as a result can consume space in the database at similar
rates.
Review the default DAP and default schedule to ensure that it is aggressive
enough for your deployed system. (38213)
Supported Functionality and Equipment
The following section contains release notes for functionality and equipment
supported in this product.
Supported PowerConnect Devices
• New User Interface
• Resources editor configuration screens in previous versions have been
replaced with the Details Screen and Adaptive CLI.
Supported PowerConnect Hardware
• Supported PowerConnect devices include: 5524, 5548, 5524P, 5548P, 7024,
7024P, 7024F, 7048, 7048P, 7048R, 7048R-RA, M8428-K, M8024-K, 62xx,
62xxP, 62xxF, 8024F, 8024, M8024, M6348, M6220?, 54xx, 53xx, 35xx,
35xxP, 34xx, 34xxP.
• Supported Powerconnect W-series systems include the following models: W-
3200, W-3400, W-3600, W-620, W-650, W-651.
• Supported Powerconnect B-series systems include the following models: W-
6000 Controller Chassis, W-6000M3 modules, W-AP-92/93, W-AP-105, W-AP-
124/125, W-AP-68/175P, W-AP-134/135, W-iAP-92/93/105, W-iAP 134/135,
W-ClearPass GuestConnect.
• 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.
Supported Force10 Devices
The following are supported Force10 models:
• S4810, S60, S55, Z9000, C300, C150, S50N, S50V, S25N, S25P, S25V, E1200i
(Exascale and Terascale), E1200 (Terascale), E600i (Exascale and Terascale),
E300 Terascale
The following are supported Force10 S-Series models supported in a stacking con-
figuration:
• S60, S55, S50N, S50V, S25N, S25P, S25V

11
Known Issues
• In the Image Repository portlet, clicking on Download > Firmware for Dell
PowerConnect may download out of date firmware for Dell PowerConnect
classic devices. Workaround: OpenManage Network Manager has pre-seeded
firmware for devices and you can download firmware for each device from
the Dell support site. (16561)
• Some Dell devices and firmware revisions may not support the collection of
Service Tag and Asset Tag by OpenManage Network Manager. This includes
recent firmware revisions of Force10, PowerConnect B-Series, and PowerCon-
nect W-series along with older revisions of PowerConnect firmware. (16098)
• For Force10 S50V devices OpenManage Network Manager may show total
memory to be less than memory used. (18301)
• JUNOS event definitions are not supported in this release. (18869)
• When ACLs are configured on Force10 S4810 devices, when copying a
restored configuration to the running configuration, an error may appear
during restoration. (18905)
• 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. Layer 2 Powerconnect switches have
just running and startup options while the Layer 3 router has running, star-
tup and backup options, so different options appear for the two sets of
switches. When you do file backup for a group of devices, all those options
are combined. Select only the top entry selection for execution. (18944)
• For C series and E series devices, the management interlace appears as a port,
though it should appear as an interface. (18949 18945)
• Sometimes Force10 devices may not respond to ICMP pings. Reports or appli-
cations would appear without data if you are only monitoring Force10. For
example, the performance portlet for “Top Ping Response” would appear
without data if you are only monitoring Force10 devices. To monitor the net-
work status of the Force 10 devices, you can create “Force10 SNMP” monitor
to poll Force10 devices using SNMP (sysUpTime). When this “Force10 SNMP”
monitor receives a valid response, the network status appears as Responding.
(18881)
• Combining the discovery of different kinds of links may produce errors. So
discovering Fiber Channel alone or Ethernet alone is problem free. However,
combining discovery of both makes Ethernet link discovery display an error.
Workaround: run the types of link discovery by themselves. (18819)
• OMNM supports downloading OS images for all devices it supports. Down-
loading OS images for one device downloads OS images for all devices.
(18777)
• The firmware report displays unnecessary entries showing firmware changes
from empty to a firmware number. (18719)
• sFlow data captured may not appear, or may appear incorrectly. For this
build, sFlow data is for representational purposes and the issues will be
resolved in a future build (17935, 18212)

12
• The Add Stack Management ACLI is not supported for PowerConnect 35xx
models (13793)
• CPU and Memory usage values do not appear for PC 5524P (17505)
• The Dell Force10 S50AC device appears as a Dell Force10 S50DC device
(17890).
• For Dell Force10 devices, interfaces like management and loopback may
appear as both ports and interfaces. (18309)
• For Dell PowerConnect 8024/F, restoring a configuration for a stack of devices
may fail (16953)
• The OS image portlet may report “Invalid Device class” for the devices.
(17114)
• For Dell PowerConnect M8024-k and 8024/F user ports that are used for
stacking ports do not appear in the Network View (16944, 16951)
• 8024/F fibre channel link discovery is not supported. (16943)
• Some devices do not respond to commands unless they are in the correct
state. For example, some Dell devices must not be in “Simple” mode to
respond to Adaptive CLIs. Take account of this as you create Adaptive CLIs.
(17153)
• When a restore service error appears for a TI24x it contains no details. No fur-
ther 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. As the device resets, timing of connection lost between the
device and OpenManage Network Manager may result in OpenManage Net-
work Manager reporting a failure for executing the Adaptive CLI. Device
resets can be confirmed through the OpenManage Network Manager event
log or status polling. For best results when creating Adaptive CLI scripts, users
should move the usage of device reload/reset commands to a different Adap-
tive CLI that only uses the device reload or other device reset commands.
(18324)
• Some devices, including the Dell Force10 C-Series and E-Series, will allow
then drop telnet connections during deployment or file restoration when you
select restart as part of the process. This can take from six to eight minutes,
though it can take as long as fifteen minutes for a fully populated chassis.
During that time, you can pint the device; however, OpenManage Network
Manager cannot log in to the device until the reboot is complete. (18277)
• Restoring configurations to Dell Force10 devices may produce errors when
individual commands already exist in the running config and cannot be over-
written. OpenManage Network Manager ignores such errors and reports suc-
cess by default since the errors indicate a command was not applied, not that
restoration was unsuccessful. Best practice is to restore to startup config to
avoid these errors, especially when scheduling backup or backing up a group
on such devices. (17991)

13
• If you use the “backup to flash” option when backing up configuration files,
the filename must have the extension
*.tar.gz. If not, restore fails with a
“failed to decompress” error. (15283)
• 55xx devices echo command lines sent to them, so Adaptive CLI commands
display echoed characters in their Audit Trails. This is not an error and does
not mean the configuration failed. (14796)
• Upgrading from switch to router firmware on an FCX device upgrades an L2
Switch with L3 firmware, so the IP commands/configuration changes and the
L2 configuration are ignored. The device needs to be reconfigured from the
console. (14369)
• M8024-K does not support ethernet link discovery unless you update the
firmware to 4.2. (14853)
• PowerConnect 62xx users must be running 3.x.x.x firmware (or later) on
their switch before they can do a standard firmware upgrade. Attempting to
upgrade the firmware while at version 2.x or 1.x fails. To upgrade from these
versions, see the special instructions provided in the Release Notes and
Readme for the firmware itself. (8507)
• OMNM receives all data from the Dell 62xx device, but if the Last Update day
is more than a single digit, then the entire data table disappears, and OMNM
displays a Form Error. One other symptom: the Last Update, Total Inserts,
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.
• Stacked switches change IP addresses when the master is moved. Moving
master does not function properly in stack configuration. (7002)
• When editing any interface set to disabled mode, and choosing vlan tagging
from the combo box, you will not be able to add a VLAN ID. The field is
grayed out. Workaround: Switch the selection to another item and then back
to the desired one. (6355)
• You must use the command-line interface to deploy new firmware for the
5324 model (4739)
• LLDP modification through this application may not work on M8024
devices, therefore you must setup LLDP through the telnet CLI. (2583)
• When one of the three banners already configured on a 35xx or 54xx device
is longer than 500 characters, you must modify that banner in OMNM before
you can create a different banner. (2411)
• If directory locks during upgrade, check task manager and close all
ftp.exe
processes.(2455)
• Web client does not show IPv6 information when older firmware is installed
on the switch. (2967)
• OSPF Areas cannot be deleted for M6220 devices. (44464)

14
• 35xx models do not support rfc 1042 and IIec, even though these frame types
appear in the screen that includes Vlan protocol group. Currently when you
select these options in Group ops and execute a group operation against a
35xx model device, an error message appears. (6268)
• The Home button returns the user to the Begin Discovery page rather than
the Quickview as documents promise. Workaround: Select Quickview as the
home page manually. (6297)
• Banners are supported only up to 256 characters in length. (2265)
• To set up alarms or events for user login or logout, you must set up the device
syslog server and syslog level. For example, for the 35XX model, you must
issue the following command lines:
logging 192.168.0.117
logging file informational
(6695)
• You must wait more than three minutes to deploy another firmware version
after you successfully deploy the first firmware version. Deploying firmware
can also fail with the default timeout value. You can increase the timeout
value from the Management interface and also in \owareapps\dellpoewr-
connet\dellpc.properties. (6680)
• You must typically increase the timeout for firmware deployment of multi-
stack devices. Stop the Dell OpenManage Network Manager service in Win-
dows., 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 min-
imum 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. If this does not include
the address of the mediation server (in single host installations this is the
application server), discovery will fail on the SNMP get step. (6689)
• No support for firmware v4.1.x or greater on the following devices: PC8024,
PCM6220, PCM6348, PCM8024
• For PowerConnect 62xx series devices, Editing Managed Equipment does not
display the correct values for Power over Ethernet (PoE) Port Settings parame-
ters. Workaround: Use the PowerConnect 62xx command line interface or
Web Console to view Power over Ethernet (PoE) Port Setting parameters.
(13107)
•
Supported Powerconnect B-Series Devices
Supported Powerconnect B-series systems include the following models: Sup-
ported PowerConnect B-series systems include the following models: B-MLXe4,
B-MLXe8, B-MLXe16, B-FCOE1024, B-FCX624, B-FCX624S, B-FCX648, B-
FCX648S, B-TI24X, B-RX4, B-RX8, B-RX16, B-8000/8000e, B-DCX4S
Supports is included for firmware versions 5.2.0 or higher.

15
Known Issues
• M8428K does not display the correct model number, performance indicators
and serial number in the details panel. (17447)
• A limited amount of interface data is collected from Powerconnect B-Series
Ethernet capable switches. As a result, interface reports and the Interfaces
portlet do not contain Ethernet Link data for these devices. This also means
Ethernet Links do not appear for these devices.(18800, 18802)
• Right-click menu in Performance - Top Ping Response portlet does not appear.
Workaround: Right-click in the Managed Resources portlet. (18827)
• Network Details VLAN screen for B-RX devices does not display VLAN infor-
mation since required MIBs are not supported or populated by the device.
(16419)
• Informs are not supported on these devices. If you check the checkbox to
send informs to v3 trap recipients it will send informs rather that v3 traps.
Workaround: Don’t check the checkbox. (18435)
• MLXe does not support ethernet link discovery. (PV-14912)
• Deploying firmware to these devices requires an external file server. (12512)
• Even though restoring a file is successful, a 4xS device does not send an indi-
cation the internal file server can interpret as a successful conclusion to the
restore action. In this case, the timeout emitted by the file server can be
benign. (12584)
• RX devices cannot discover links between the two RX devices or between an
RX and a Dell device.
This occurs because the device does not populate the LLDP-MIB LocPortTable
with unique port IDs. Therefore, link discovery cannot accurately get the port
used for a link and hence the end point is the top level device itself. When a
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 pass-
word be changed each time log in occurs. (12240)
Traffic Flow Analysis
OMNM’s Traffic Flow Analyzer listens on UDP ports for NetFlow, or JFlow data-
grams. A flow is a unidirectional stream of packets between two network nodes.
The following key parameters appear in flows:
• Source IP address
• Destination IP address
• Source port number
• Destination port number
• Layer 3 protocol type

16
• ToS byte (Type of Service)
• Input logical interface
Using that data, Traffic Flow Analyzer can help you visualize network traffic,
troubleshoot and anticipate bottlenecks.
Change Management
OpenManage Network Manager’s change management utility is ProScan, which
lets you scan stored configurations to verify managed devices compliance with
company, department or industry standards. This application automatically
tracks all changes occurring to managed devices. You can report on user-specified
values found in persisted backup configuration files for a group of devices. This
lets network managers, security officers and external auditors generate detailed
audit trail documents to validate compliance with both internal standards (ISO
17799, NSA Guidelines) as well as industry regulations (Sarbanes-Oxley, GLBA,
HIPAA).
Compliance reporting lets you specify a text string, regular expression, or option-
ally the generated configlet from File Management (NetConfig) for matching.
Group results must be separated by device like Adaptive CLI Manager. When
ProScan policies run, the application emits notifications whose contents depend
on whether compliance was or was not maintained.