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.

Quick Start 11
Screen Layouts
When you select Resources in the Navigation Panel, for example, the default view looks like Figure
1:4
.
Figure 1:4. Default View
The lower portion of such screens displays detail panels with information about the equipment
selected in the upper panel. For details about changing and managing screen layouts, see
Managing
Layouts
.
Getting Started
The following section outlines the steps in a typical installation and subsequent first use. Because the
software described here is both flexible and powerful, this section does not exhaustively describe all
the details of available installations. Instead, this Quick Start Guide refers to those descriptions
elsewhere in the
User Guide or online help. A typical installation will go through the following (in
order):
1. Installation and Startup —See the other manuals for this product for a more detailed
description of installation.
2. Discovering Resources —After you first install the application, you must discover the
equipment you want to manage.
3. Alarm Panels —See Alarm Panels for a discussion of alarms and events managed by the
application.
A list of all
Equip-
ment and
their
attributes
Detail Panels:
Information fo
the selected
device and
associated
infrastructure
Navigation Panel Main Panel

12 Quick Start
You can also set up users, device access passwords, and groups for both users and devices, as you
begin to use it. For example, use Group Operations to act or schedule operations on multiple devices.
Consult the
User Guide for details about administration and the many additional discovery,
management, and reporting options available with this software beyond those discussed in this Quick
Start Guide.
NOTE:
Best practice is to use the default Admin user unless security concerns dictate
otherwise. If you must add a new user, best practice is to add that user to a User
Group and modify that group’s permissions rather than adding permissions user-
by-user
Also: We have noticed that bash.exe or md5sum.exe (two files that are installed
with this product) have triggered false positives with some anti-virus software. If
you get a virus detection warning for these files during installation, take no action.
OpenManage Network Manager includes several new ACLI group operations in this version.
Installation and Startup
For a basic installation, install and start your OpenManage Network Manager software with these
steps:
1. Unzip (decompress) the file if you downloaded the application in .zip format, and close any
applications that might interfere with this installation.
2. To install this software, log in as an administrator-type user that can install software, and run
either
win_install.exe (for Windows), or linux_install (for Linux). Do not install as
a user named “admin” or as the root user.
In Linux, the installing user must have a home directory, and must have permissions to write
both there and in the installation’s target directory. At one point the Linux installation stops and
asks the installing user to run a script in a separate shell as root user. Other than these differences,
to install on both Windows and Linux, you must follow these steps. After initiating installation,
click
Next .
CAUTION:
You must install as a non-root user with the permission to create directories in the selected installation
target path. Installing to a directory that requires root level access fails.
Also: Using the login “admin” to do the installation wipes out any pre-configured “admin” permissions
that come with the application. Therefore, do not use “admin” as the installing user account.
3.
Confirm your hardware meets the displayed Minimum System Requirements . Click Next .
4. Accept the license agreement after reading it, otherwise, installation cannot proceed. Click Next .
5. Confirm or alter the installation path. Click Next .
6. Select either Full installation or Client installation. (You must install the Full installation on at
least one machine before
Client will work on any others.) Click Next .

Quick Start 13
7. View the final confirmation of components to install. Click Next .
Observe the progress bar as files are copied for installation.
8. The database size typically defaults to 2G with unlimited expansion. Some installations display
this default and let you modify it in a database installation screen that appears during this
process. If you do not want the default, you can consult the other application manuals for
database sizing suggestions, but the default size should be an acceptable starting place for most
installations. Click
Next to continue with the installation.
NOTE:
Regardless of the initial database size, post-installation configuration of Database
Aging Policies (DAP) and monitoring retention policies can have a significant
impact on how fast it reaches its capacity. The default DAP for alarms, for
example, never cleans open alarms from the database. Similarly, defaults for
archiving event history may not suit your environment. Consult the User Guide or
online help for details about tuning these policies.
9.
If you are installing on Linux, you must run a setup script in a separate shell, after logging in as
root user there. Installation prompts you to run a generated script after the installation phase
finishes. This script records information in case you need technical assistance and installs some
files as root. Open a new shell, log in as root, and run the script requested by the installer (It
should be
$OWARE_USER_ROOT/install/root/setup.sh ).
10. Click Finish .
11. In a Windows installation, notice the Server Monitor icon in the system tray. When the icon
turns green, you can start your application client. This icon indicates the application server’s
status. Green is running, red is stopped, yellow is starting or stopping. Application server
monitors your devices even when the client is not visible, or you are not logged into your
machine. Best practice is to install application server to a host you do not turn off if you want
constant monitoring of your devices.
Linux installations do not have a system tray, so you can run ps -ef | grep java.exe to
see whether the application server’s Java Virtual Machine is running.
NOTE:
This software is a Java application. Virtual memory use increases when you install
it. This is normal. If you monitor memory use over time it may appear that it is
growing. This is a normal function of Java's memory management.
You can also uninstall this product as you would any other. Go to Add/Remove Programs in
Windows’ Control Panel, for example. Uninstalling removes all installed files and files created by
using the installed system (that it has permission to delete). It does not remove directories that were
not created by this application’s installation or runtime. User-created directories in the product’s
directory path remain after product removal.

14 Quick Start
Starting the Client
After you verify that the application server is started (in Windows, the monitor icon in the system tray
turns green), use the
Start button (or its Linux equivalent) to find OpenManage Network Manager
among your programs. Click that icon to start the client. In Linux, if you do not see a
OpenManage
Network Manager
icon on your desktop first set the environment in a shell with . /etc/.dsienv
([dot][space][foreslash][dot]dsienv), then type
redcell at a command line
Figure 1:5. Login Screen

Quick Start 15
A login screen appears. The default login user is admin , with a blank password. After logging in as
admin , you are prompted to change the password. See the other manuals or online help for more
information about options for adding and configuring user privileges and the kind of password
constraints that appear on the
Change Password dialog.
Figure 1:6. Change Password
See Screen Layouts for more about managing the user interface. See Troubleshooting Tips to solve
application problems.
Web Client
You can also open the client user interface in a browser. Supported browsers include Mozilla Firefox
v.2 and 3 and Internet Explorer v.6 and 7. In Windows, the URL is
http://[application server hostname]
For non-windows installations:
http://[application server hostname]:8080
If you encounter the Change Password dialog that appears when you first log in, you must re-start the
browser and re-log in to a web client. This behavior is normal.
The
application server hostname is the name of the system where OpenManage Network Manager is
installed.

16 Quick Start
HTTPS
To limit connections to the application server to HTTPS (secure) only, you can use the -e option when
starting the application server from the command line, or add the following line to
owareapps/
installprops/lib/installed.properties:
oware.appserver.web.enable.https=true
To force the client to use HTTPS (secure) for web connections to the server add the following line to
owareapps/installprops/lib/installed.properties (the same file as above when the
client is on the application server).
appserver.enable.https=true
See online help for more about secure web access.
Troubleshooting
If startup fails, see Troubleshooting or consult the other application manuals.
The following sections discuss typical steps in getting started, once you have installed
OpenManage
Network Manager
.
Discovering Resources
To begin managing resources in your network, you must discover them to store their information in the
application database. You can discover manually, as described in this section, or automatically (see
online help or the
User Guide for the latter). Once you have discovered devices, you can manage
them.
NOTE:
Third party devices on your network may appear as Dell Powerconnect switches
during OpenManage Network Manager discovery. While you may be able to
manage these devices with OpenManage Network Manager, they are not
supported, and count against your licensed limit of ten devices to manage free.
You may choose to delete the non-supported devices from OpenManage Network
Manager Resources or continue to manage these third party devices without
support from Dell.
The initial screen for the admin user displays a link to begin discovery
Consult the section about
Advanced Discovery in online help for details beyond what is outlined
below. Follow these steps to discover your network resources:
1. The next Discovery Wizard screen that appears is where you determine what devices you are
going to discover. Here, you can specify the IP address ranges to include or exclude, the SNMP
authentication to use, and the ports to query, among other things.
At the top of this screen’s work area, select an address type from the drop-down list (options
include
IP Range, IP address, Hostname, Subnet, CIDR, File Name, Multicast SLP, SNMP
Broadcast
) and enter the appropriate information in the box(es) directly to the right of that list

Quick Start 17
and click Apply . Then click Add to add the address(es) to the processing queue, or click Remove
to delete a previously created range you selected. You can add several such criteria.
NOTE:
If you are managing in a DNS / DHCP environment, be sure to select Manage by
Hostname in the Options tab. For this to be effective, however, the association
between hostname and the correct IP address for the discovered equipment must
be accurate.
2. New / Edit Authentication
. You can select authentication(s) to go with a selected discovery
target with the checkboxes that appear in the list of existing authentications in the
Select
Authentication
panel. In addition, you can Add or Edit authentications to associate with that
target. When you
Add an authentication, or Edit an existing one, an authentication editor opens
in the bottom of the screen.
Select or create the
Name for the authentication, and select the Type from the pick list. See the
Administration Section for details about what to expect for the different types.
NOTE:
Ensure the type selected matches the management interface on the equipment
you want to discover. You can use some single authentications in different types,
for example: Telnet and SSH.
Notice that you can also alter the Timeout, Retries, and Port for the authentication at the bottom
of this screen, so the authentication fits with your network’s connection speed.
3. Select Devices for Discovery. Click Apply to accept your authentication, then click Apply on the
initial screen to accept the combination of device(s) and authentications. The screen then
displays the discovery target devices and authentications you have selected and configured.
You can
Add more devices with that button to the right of the list, or Edit a selected target to
reconfigure the authentication. Doing so opens the
Select Network Type and Address screen
again. Click
Remove to delete a listed target, and use the up/down/top/bottom buttons to re-order
selected targets.
After you have configured this tab, you can configure global discovery
Options with that tab,
click the
Inspect button or click the Discover button
4. Options . This screen lets you configure a variety of global discovery options for the targets
configured in the
Discovery tab.
NOTE:
In addition to discovering devices by themselves, you can now discover links
between them as an activity that follows discovering the devices. Click the
checkbox next to the link discovery task appropriate to your network in the lower
part of this screen to do link discovery too. (See Link Discovery for an alternative)
Consult the User Guide or online help for details about the options available in the upper portion
of this screen.

18 Quick Start
5. Select Discovery Activities (Listed in Execution Order) —The lower portion of the screen
lists activities to perform after discovery. Use the
Select Activity field along with the command
(...) and search buttons to its right to find activities. Selecting here lets you select from those
listed by default, and from those that appear in the
Activities Manager . Click Add to list a
selected activity below, checked as
Select ed. Some activities appear automatically (from the
default discovery profile). Check those you want to activate.
The
Edit button lets you configure the selected Activity’s parameters, if that is available and
appropriate. The editor also appears if you
Add a task with configurable parameters. If you select
an activity that requires user input, the standard attribute selection screen(s) for that activity
appear during Discovery. Fill in the required attributes, and Discovery continues.
Remove deletes the selected activity from the list.
NOTE:
You can add a task to add discovered devices to OpenManage Network Manager’s
heartbeat. You can configure what appears by default as described in the User
Guide.
You can also use the up/down/top/bottom arrows to reorder selected rows, reordering what
activities discovery executes. Regardless of the row order, however, device-based tasks run first,
and group-based tasks (like link discovery) run last, since groups depend on their member
information. See the
User Guide for more about available activities.
Clicking
Reorder moves the activities with Select checked to the top of the list.
6. After you have configured this tab, you can click the Inspect button or click the Discover button.
7. Inspect . Clicking the Inspect button lets you validate the selected authentication credentials,
displaying the devices’ responses to the credentials you have set up in the
Resource Discovery
screen. Columns in the listed devices let you select which devices to Discover (by checking that
checkbox), the
IP Address, Hostname, Vendor, Status, whether the device was Pinged (and
responded), whether OpenManage Network Manager management is
Licensed for the device,
the
Valid Auths , and the status of selected authentications ( Auth Status ) .
NOTE:
Inspection simplifies some manual steps that you can still do yourself. You can
manually telnet to a device to verify that you have the correct authentication
information. You can also examine the device’s config file and verify that the SNMP
community string is correct.
You can filter the results that appear listed in this screen by entering the text to search for in
Filter Results at its top. You can also Select or Deselect Device(s) , and Change Authentication
with the icons to the right of the filter. You can also use the Discover column’s checkbox to
select items to discover.
The columns in this screen display the
IP Address, Hostname, and Vendor of inspected devices.
It also displays
Status (like New, or No Response), whether the device responded when Pinged ,
whether it is
Licensed to be managed by OpenManage Network Manager, the list of Valid

Quick Start 19
Auth(s) (validated authentication credentials), and the Auth Status that lets you know whether a
device is ready to discover, or has missing or invalid auths. In this last case of missing or invalid
credentials, you can click the
Change Authentication icon.
From left to right, the icons let you select all devices for discovery, unselect them, select and
unselect a single device, and change authentications. When you click
Change Authentication , a
screen like
Select Devices for Discovery screen appears. Use this screen to repair or replace
invalid authentications.
All available authentications appear, with those connected to the device selected appearing
checked. You can
Add, Select Edit, and re-order these with the buttons above the list.
8. If you click Test , OpenManage Network Manager tests the selected authentication on the
selected device. A green check icon appears next to working authentications, a red octagon
appears next to those that fail, the yellow triangle icon indicates partial success—an option with
multiple targets and authentications.
Click
Apply after you have corrected or modified any invalid authentications with the Change
Authentications
button, or click Close to close this panel without modification. Notice that you
can also change ports, timeouts and retries in the existing authentications with
Edit .
9. After you have configured what is necessary in this screen, you can click the Back button to
return to discovery setup (in
Resource Discovery or Options ) or click the Discover button.
10. Discover . Clicking the Discover button actually executes the discovery you have configured,
storing the information retrieved from devices in the OpenManage Network Manager database.
Clicking this button displays a standard OpenManage Network Manager audit screen. This
displays the messages between OpenManage Network Manager and the discovered devices,
including the post-discovery activities. Select a message in the top of the screen to see the time
and date it occurred in mid-screen, and the contents of some messages in the
Message Details
panel at the bottom of this screen. See the User Guide ’s discussion of Audit Trails for details of
how to revisit this screen after discovery is complete.
You can click
Close at any time. If you click it before the Equipment Discovery Finished
message appears, discovery continues in the background.
The final discovery panel, whether appearing for a Resource Discovery Profile or at the end of
the a conventional basic / advanced discovery process presents asynchronous information. If you
click
Finish before the process is done , the discovery process still continues. While that is
occurring you may not see elements being discovered in their resync schedule until the discovery
job is actually complete. Executing scheduled resync while discovery is still ongoing may result
in exceptions.

20 Quick Start
11. When discovery is done for the user admin , and you click Close , the following Layout screen
appears by default.
This screen displays alarms received from discovered devices, the devices themselves, and
details about devices you select in the lowest panel. See
Managing Resources for more about
the resource management portion of this screen. See Alarm Panels for information about the
alarms, and
Managing Layouts for a description about how you can customize your user
interface.
NOTE:
You can toggle the appearance / disappearance of the navigation pane that leads
to most available application functions with the Show / Hide Navigation Window
button.
To clarify the origin of application features, the navigation window often appears
throughout the rest of the manuals for this software.
12.
After you click Finish , a QuickView screen appears.
Resources: A
list of all
Equipment
and their
attributes
Detail Panels:
Information for
the selected
device and
associated
infrastructure
Navigation Panel Main Panel
Alarms: Totals
followed by a
list of alarms
from the dis-
covered
devices.