Dell OpenManage Network Manager User manual

Dell OpenManage Network Manager
Quick Reference Guide

Notes and Cautions
A NOTE indicates important information that helps you make better use of your software.
A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed.
____________________
Information in this document is subject to change without notice.
© 2011 Dell Inc. All rights reserved.
Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Trademarks used in this text: Dell™, the DELL logo, PowerConnect™, OpenManage™, EqualLogic™, KACE™, FlexAddress™ and Vostro™
are trademarks of Dell Inc. Intel
®
, Pentium
®
, Xeon
®
, Core™ and Celeron
®
are registered trademarks of Intel Corporation in the U.S. and other
countries. AMD
®
is a registered trademark and AMD Opteron™, AMD Phenom™, and AMD Sempron™ are trademarks of Advanced Micro
Devices, Inc. Microsoft®, Windows®, Windows Server®, MS-DOS®and Windows Vista®are either trademarks or registered trademarks of
Microsoft Corporation in the United States and/or other countries. Red Hat Enterprise Linux®and Enterprise Linux®are registered trademarks
of Red Hat, Inc. in the United States and/or other countries. Novell®is a registered trademark and SUSE ™ is a trademark of Novell Inc. in
the United States and other countries. Oracle®is a registered trademark of Oracle Corporation and/or its affiliates.
Other trademarks and trade names may be used in this publication to refer to either the entities claiming the marks and names or their products.
Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.
May, 2011 Rev. A00

Contents 3
Contents
1 Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Introducing OpenManage Network Manager . . . . . . . . . . . . . . . . . . . . . . .5
System Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Supported Operating System Versions. . . . . . . . . . . . . . . 6
Hardware Recommendations . . . . . . . . . . . . . . . . . . . 7
Basic Network Considerations . . . . . . . . . . . . . . . . . . 7
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . 8
Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . 8
Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Fixed IP Address . . . . . . . . . . . . . . . . . . . . . . . . 8
Updating Your License . . . . . . . . . . . . . . . . . . . . . 9
The Application Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Managing Multiple Screens . . . . . . . . . . . . . . . . . 10
Screen Layouts . . . . . . . . . . . . . . . . . . . . . . . . 11
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Installation and Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Starting the Client . . . . . . . . . . . . . . . . . . . . . . . . 14
Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 16
Discovering Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Scheduling Discovery . . . . . . . . . . . . . . . . . . . . . . 21
Link Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . 21
Monitoring Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Default Monitors . . . . . . . . . . . . . . . . . . . . . . . . 22
Interface Monitor . . . . . . . . . . . . . . . . . . . . . . . 23
ICMP Monitor. . . . . . . . . . . . . . . . . . . . . . . . . 24
Custom Monitor . . . . . . . . . . . . . . . . . . . . . . . . . 24
Creating a Custom Monitor . . . . . . . . . . . . . . . . . . . 24
Show Performance . . . . . . . . . . . . . . . . . . . . . . . 25
Create a Dashboard View . . . . . . . . . . . . . . . . . . . . 26
Install a Monitor in the View . . . . . . . . . . . . . . . . . . . 26
Reports From Monitors . . . . . . . . . . . . . . . . . . . . . 27

Contents 4
Managing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Alarm Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Alarm Severity & Count. . . . . . . . . . . . . . . . . . . . . . 30
Alarm Manager. . . . . . . . . . . . . . . . . . . . . . . . . . 30
2 Common Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Managing Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Creating and Selecting Screen Layouts. . . . . . . . . . . . . . 34
Minimizing sub-panels . . . . . . . . . . . . . . . . . . . . . 36
Column Drag and Drop . . . . . . . . . . . . . . . . . . . . . 36
Administering the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Users and User Groups . . . . . . . . . . . . . . . . . . . . . . 37
User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Scheduling Operations . . . . . . . . . . . . . . . . . . . . . . 41
Common Management Tasks . . . . . . . . . . . . . . . . . . . 41
Mapping Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3 Backup / Restore / Deploy . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
File Management: Backup / Restore / Deploy . . . . . . . . . . . . . . . . . . . . . . 45
Setting Up FTP / TFTP . . . . . . . . . . . . . . . . . . . . . . . 45
Backup / Restore . . . . . . . . . . . . . . . . . . . . . . . . . 45
Deploy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . 47
Common Issues . . . . . . . . . . . . . . . . . . . . . . . . . 47
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Quick Start 5
1
Quick Start
Introducing OpenManage Network Manager
We created this Quick Start Guide to get you started using your OpenManage Network Manager
program as quickly and productively as possible. After a review of the hardware and software
requirements needed for your installation in
System Basics , you can move on to Installation and
Startup
. To start the first use of the software, consult Discovering Resources .
This software includes reporting capabilities. These are described in online help Key features available
in this software are the following:
• Deep Discovery —Detailed device information retrieved automatically.
• Real time monitoring of Alarms that impact your network. (See Alarm Panels .)
• A Resource inventory available at a glance. (See Managing Resources )
• Configurable Detail Panels below the display of listed devices. These tell you about devices you
select.
For more detailed descriptions of all this software’s features, consult its other manuals or online help.
NOTE:
If you want to find something but are unsure about which manual contains it, you
can search all the Acrobat files in a single directory. For example, in Acrobat v.9,
Shift+Ctrl+F opens this directory-wide, multi-document search.
Supported Powerconnect systems include the following models:
• PC7024-R, PC7024P-R, PC7048-R, PCM8024-K, M8248-K, PC5524, PC5548, PC5524P,
PC5548P, J-SRX100s, J-SRX100su, W-3200, W-3400, W-3600, W-620, W-650, W-651, B-
MLXe-4, B-MLXe-8, B-MLXe-16, B-MLXe-16, B-DCX4S-24, B-FCX624 I/E, B-FCX648 I/E,
B-FCX6xx-S, B-TurboIron
• Support for PowerConnect B-Series B-MLXe-4, B-MLXe-8, B-MLXe-16, B-MLXe-16, B-
DCX4S-24, B-FCX624 I/E, B-FCX648 I/E, B-FCX6xx-S, B-TurboIron, B-RX4, B-RX8, B-
RX16, B-8000/8000e, and B-DCX4. See PowerConnect B-Series on page 16 for more about
these.
• Support for PowerConnect J Series EX8208, EX8216, EX4200-24T, EX4200-48T, EX4200-24F,
SRX100B, SRX100H, SRX210B, SRX210H, SRX210-P, SRX240B, SRX240H, SRX240-P
SRX100S SRX100SU. See PowerConnect J-Series on page 17 for more about those.
• Supported systems also include 3800, 3850, 3900, 200E, 2014, 2016, 2040, 2024, 4100, 4900,
5000, 76000, 12000, 24000, 48000, DCX 8000e, 8000, BigIron RX4, RX8. (See Help > About
for the details of supported firmware.)

6Quick Start
System Basics
System requirements vary depending how you use the application and the operational environment.
Because we do not know your specific network and devices, the recommendations are based on
typical, not definitive figures, and are as much suggestions as requirements.
Base the minimum configuration of any system on its expected peak load. Your installation should
spend 95% of its time idle and 5% of its time trying to keep pace with the resource demands.
Supported Operating System Versions
Disable firewall products during initial installation and testing. The following are recommended
operating system versions: The following are supported operating system versions:
Microsoft Windows —This application supports most Windows operating systems from Windows
XP forward, with their latest service packs. The supported operating systems are: Windows 2003
(Standard, Enterprise and Web), Windows XP (Pro) SP3 or later, Windows Vista (Business or
Ultimate), Windows Server 2008, Enterprise Edition, and Windows 7 (Business or better). This is a
32-bit application, however it has been tested for Windows on both 32- and 64-bit operating system
versions, and supports both in the supported Windows versions.
CAUTION:
Windows 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.
Also: You must disable User Access Control if you are installing on Vista or Windows Server 2008. In
Vista, you must either to disable User Account Control or run application server as service. Another
option is to run as administrator to start application server. In Vista, right click the startappserver icon
and select run as administrator.
Finally: Installer may halt when pre-existing bash sessions or cmd sessions left are open. Close all such
sessions.
CAUTION:
This application cannot co-exist with other installations of Cygwin on the same Windows computer. Do
not install it where Cygwin is already installed, either separately or as part of another application. If
Cygwin is already installed, remove it before installing this application. If you do not see any obvious
indication Cygwin is installed (like an icon on the desktop or program list, or a directory named
c:\Cygwin), but suspect it is, you can open the registry (Start -> Run, then type
regedit ), and look for
HKEY_CURRENT_USER -> Software -> Cygnus Solutions -> Cygwin.
Linux — OpenManage Network Manager supports Redhat (Enterprise version 4 & 5) and Novell
Suse (version 9 and10) Linux, 64-bit only.
CAUTION:
For Linux, you must install no more than a single instance of MySQL—the one installed with this
software. Before you install, remove any MySQL if it exists on your Linux machine.

Quick Start 7
Hardware Recommendations
OpenManage Network Manager contains an Application Server that runs continuously in the
background, and a
Client (the user interface you actually see). You can start and stop the client portion
of the software without impacting the application server. Device monitoring stops when you stop the
application server or turn off its host machine. The client can also be on a different machine than the
application server. Hardware recommendations are based on the different types of installation
available:
Full Installation (Application server + Client) —Pentium 4, 3.2 GHz CPU, 2G RAM, and 20G
available disk space.
Client only —Pentium 4, 2.8 GHz, 2G RAM, and 1G available disk space.
NOTE:
A browser-based client is also available. See Web Client for more information
about using web access to this software.
Basic Network Considerations
OpenManage Network Manager communicates over a network. In fact, the machine it is on must be
connected to a network for the application to start successfully. Firewalls, or even SNMP management
programs using the same port on the same machine where this software is installed can interfere with
communication with your equipment.
Your network may have barriers to communication with this software. Dealing with such barriers,
initial device configuration to accept management, security measures or firewalls is outside the scope
of these instructions. Consult with your network administrator to ensure this software has access to the
devices you want to manage with the
Protocols described below.
NOTE:
One simple way to check connectivity from a Windows machine to a device is to
open a command shell with Start --> Run cmd . Then, type ping [device IP
address]
at the command line. If the device responds, it is connected to the
network. If not, consult your network administrator to correct this. No useful
information comes from disconnected or powered-down devices.
See Chapter 4, Troubleshooting in this guide or see the User Guide or online help, for additional
information about how to troubleshoot this software.
CAUTION:
You can click on the blue cross-references to go to the destination in Acrobat, however for such
electronic cross-references to the User Guide to work, this document and the User Guide must be in the
same directory. Cross-document links do not work between documents for different versions of this
software, but may provide an approximate location to consult.

8Quick Start
Authentication
For successful discovery of the resources on your network, this software requires authenticated
management access to the device. To get this access, you must provide the correct SNMP community
strings, and any other command-line (Telnet / SSH) or browser (HTTP/HTTPS) authentication, and
SNMP must be turned on, if that is not the device’s default. Some devices require pre-configuration to
recognize this management software. Consult your network administrator for this information.
Name Resolution
OpenManage Network Manager server and client require resolution of equipment names to work
completely, whether by host files or domain name system (DNS). The application server cannot
respond to hosts with IP addresses alone. The application server might not even be in the same
network and therefore the host would be unable to connect.
If your network does not have DNS, you can also assign hostnames in
%windir%\system32\drivers\etc\hosts on Windows ( /etc/hosts in Linux). Here, you
must assign a hostname in addition to an IP address somewhere in the system. Here are some example
hosts file contents (including two commented lines where you would have to remove the # sign to
make them effective):
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
CAUTION:
This software supports installation only on the local file system. Avoid installing to shared drives.
Protocols
OpenManage Network Manager uses the following protocols: TCP/IP, SNMP, HTTP/S, UDP
Multicast.
Fixed IP Address
OpenManage Network Manager includes a web server and must be installed to a host with a fixed IP
address or a permanently assigned Dynamic Host Control Protocol (DHCP) lease. For trial purposes,
you can rely on a dynamic IP address assignment with a long lease, but this is not recommended for
production installations.
If you do change your host’s IP address
To accommodate a changed IP address, first delete the contents of \oware\temp . Change your local
IP address anywhere it appears in
\owareapps\installprops\lib\installed.properties . Then restart your machine.
Alternatively, in a shell, after running
oware to set the environment, you can run
ipaddresschange -n followed by the new IP address to which you want to change.

Quick Start 9
Updating Your License
If you have a limited license — for example OpenManage Network Manager by default limits
discovery to ten devices — then your application does not function outside those licensed limits. If
you purchase additional licenses, put the updated license file in a convenient directory, then use the
Settings -> Permissions -> Register License menu item to open a file browser. Locate the license file,
and click the
Register License button. Your updated license should be visible in Settings ->
Permissions -> View Licenses.
NOTE:
You must also re-register licenses if you have updated your installation from a
previous version where you previously upgraded licenses. In any case, you must
restart application server or wait up to 15 minutes before a license modification is
effective.
If you license new features, you must restart the application server and client.
The Application Interface
A typical screen in this software appears in Figure 1:1 . The navigation panel to the left provides quick
access to common functions (discovery, reports, and so on), which can also be accessed through the
menus. When visible the left panel remains on screen while the main panel changes to reflect the
currently selected function.
Figure 1:1. Discovery Screen
Nodes that appear in the navigation panel depend on installed options.
Navigation Panel Main Panel

10 Quick Start
Managing Multiple Screens
The content of the Main Panel is referred to as a window. Just as you can open several documents in
your word processor, you can open several windows in this application. To see the list of windows you
have open, click the
Window menu.
In the
Browser View setting, you can see only one active window at a time. You cannot tile or
minimize these windows unless you select Multiple Document Interface (MDI) View (the default in
OpenManage Network Manager ) from the View -> Launcher menu.
Figure 1:2. Window Menu
If you right-click a device, for example, and select Open , the editor screen that appears does not close
the screen where you selected the device. Both remain open. You can navigate between screens by
selecting them in the Window menu, or with the browser buttons.
Figure 1:3. Browser Buttons and Select Layout / Select Content
The right and left arrows just left of the Select Layout pick list navigate backward and forward
through the open screens. To close a screen layout, click the
Close button to the right of the browser
buttons and layout selectors.
NOTE:
If you open more than 20 windows, the Recommended Open Windows
Exceeded error message appears. To change the recommended number, consult
the User Guide for this software. While you can still open more windows, doing so
may slow performance.