Netgear NMS200 Owner's Manual
ProSafe Network Management Software NMS200
User Guide
350 East Plumeria Drive
San Jose, CA 95134
USA
January 2012
202-10838-04
v1.1
ProSafe Network Management Software NMS200
©2012 NETGEAR, Inc. All rights reserved
No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated
into any language in any form or by any means without the written permission of NETGEAR, Inc.
Tech nic al Suppo rt
Thank you for choosing NETGEAR. T o register your product, get the latest product updates, get support online, or
for more information about the topics covered in this manual, visit the Support website at
http://support.netgear.com .
Phone (US & Canada only): 1-888-NETGEAR
Phone (Other Countries): Check the list of
http://support.netgear.com/app/answers/detail/a_id/984
phone numbers at
Trademarks
NETGEAR, the NETGEAR logo, and Connect with Innovation are trademarks and/or registered trademarks of
NETGEAR, Inc. and/or its subsidiaries in the United States and/or other countries. Information is subject to change
without notice. Other brand and product names are registered trademarks or trademarks of their respective
holders. © 2011 NETGEAR, Inc. All rights reserved.
Statement of Conditions
To improve internal design, operational function, and/or reliability, NETGEAR reserves the right to make changes
to the products described in this document without notice. NETGEAR does not assume any liability that may occur
due to the use, or application of, the product(s) or circuit layout(s) described herein.
Revision History
Publication Part Number Version Publish Date Comments
202-10838-01 v1.1 May 2011 First publication
202-10838-04 v1.1 January 2012 Second publication
2
Contents
Chapter 1 Introduction
Chapter 2 Getting Started
Why NMS200? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Networks with NMS200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Additional Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Online Help / Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Expand / Collapse options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
A Note About Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
System Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Network Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Updating Your License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Installation and Startup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Starting Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Portal > Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Portal > Communities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Database Aging Policies (DAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Aging Policies Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Aging Policies Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Sub-Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Quick Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
License Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Managed Resources . . . . . . . . . . . . . . . . . .
Common Setup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
SMTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Netrestore File Servers. . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
. . . . . . . . . . . . . . . . . . . . . . .28
Chapter 3 Portal Conventions
Help / Tooltips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
The Back Butt
Show Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
The Dock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
3
ProSafe Network Management Software NMS2 00
Status Bar Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chat / Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Common Menu Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Import / Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Sharing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
View as PDF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Audit Trail / Jobs Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Audit Trail Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Audit Trail Portlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Schedules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Schedules Portlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Chapter 4 NMS200 Portlets
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Event History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Event Processing Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Rule Editor Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Rule Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
File Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
File Server Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
OS Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
OS Image Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Deploy OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Contacts Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Visualize My Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Control and Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Data / Node Finder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Alarms in Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Vendors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Chapter 5 Monitoring
Resource Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Monitor Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Monitor Options Type-Specific Panels . . . . . . . . . . . . . . . . . . . . . . . . .106
Scheduling Refresh Monitor Targets . . . . . .
Top [Asset] Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Top Configuration Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Dashboard Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Performance Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Dashboard Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
4
. . . . . . . . . . . . . . . . . . . .113
ProSafe Network Management Software NMS200
Key Metric Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Chapter 6 Resource Management
Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Resource Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Discovery Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Managed Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Static Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
Dynamic Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
Managed Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
New Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
Link Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
Equipment Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
Performance Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Live Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154
Scheduling Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154
Direct Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
MIB Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156
Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158
Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
Branding Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Chapter 7 File Server / File Management
File Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
File Server Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
Image Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
Firmware Image Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
Configuration Image Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
Deploy Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Deploy Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
Chapter 8 Storage Arrays
Storage Array Portlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
Storage Array Portlet Expanded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
5
ProSafe Network Management Software NMS2 00
Appendix A Glossary
Index
6
1. Introduction
NMS200 can give you automated, consolidated configuration and control of your network’s
resources.
NMS200’s Administration Guide describes some of the runtime features supporting these
applications. The NMS200 Installation Guide and Administration Guide discuss licensing.
Consult Release Notes for information about changes not covered in this Synergy User Guide.
Why NMS200?
NMS200’s benefits:
1
• Productive. Discove
installing NMS200, you can monitor your network.
• Easy. NMS20
capabilities with minimal configuration overhead.
• V
aluable. NMS200 often costs less to use and maintain than most other solutions.
• Scalab
ility. You can scale NMS200 to almost any size.
0 provides the network information you need, and offers advanced
ry and wizard-driven configuration features within minutes of
Key Features
The following are some key features of NMS200:
• Automate
database and begins network analysis. You can also create network discovery schedules
to automatically run Discovery whenever you need them.
• Op
• T
• Alarms. Y
en Integration. NMS200 supports industry standards. It comes with an open-source
MySQL database. It also uses industry-standard MIBs and protocols.
opology. The NMS200 topology screen lets you create multi-layered, fully
customizable, web-based maps of your network to track devices wherever they are in
your network in real time.
scenarios, including multiple condition checks. NMS200’s alarms help you recognize
issues before your network users experience productivity losses. Alarms can also trigger
and Schedule Device Discovery. Device discovery populates NMS200’s
ou can configure custom alarms to respond to hundreds of possible network
7
ProSafe Network Management Software NMS200
actions like email, paging, SNMP traps, Syslog messaging, and external application
execution.
• T
raps and Syslog. NMS200 lets you investigate network issues with traps and Syslog
messages. You can use NMS200 to set up events / alarms and then receive, process,
forward, and send syslog and trap messages.
• Report
display data from its database. You can archive and compare reports, or automate
creating them with NMS200’s scheduler.
s and Graphs. NMS200 comes with many pre-configured reports and graphs to
Networks with NMS200
The beginning of network management with NMS200 is Discovery of the resources on a
network. After that occurs, you can configure Visualize My Network , Resource Monitors and
Performance Dashboards.
Once you have done these initial steps, NMS200 helps you understand and troubleshoot
your network. For example: Suppose a NMS200 Performance Dashboard displays
something you want troubleshoot. You can right-click the impacted device in the Visualize My
Network to access configuration and actions. The color of the icon in topology indicates the
highest severity alarm on the device or its sub-components. For example, read indicates a
Critical alarm.
Displays include right-click access to the Details screen (see Equipment Details on
page 146), where you can examine each section of device information and right-click to see
further applicable actions. For example right-click to Show Performance, and edit and/or save
that view of performance as another Performance Dashboard. Performance can also display
portlets that Show Top Talkers (the busiest devices) or Show Key Metrics.
From looking at Performance Dashboards or Top [Asset] Monitors you may conclude some
configuration changes made memory consumption spike. Right-click to access resource
actions under File Management that let you see the current configuration files on devices,
and compare current to previous. You can also back up devices (see How To Backup on
page 141) and restore previously backed up files (see How To Restore on page 142). Finally,
you may simply want to Resync (another right-click menu item) to insure the device and your
management system are up-to-date.
Tip: Alternatively
Actions.
You can right click for Direct Access – Telnet or Di
command line telnetting to the device, or an SNMP MIB browser to examine SNMP
possibilities for it.
The Managed Resources portlet can display the anatomy of a Resource with its right-click
actions (see Equipment Details on page 146). Click the plus in the upper right corner to see
Managed Resources Expanded. This displays detail or “Snap-in” panels with additional
information about a selected resource.
, the Alarms portlet also lets you right-click to expose Alarm
rect Access – MIB Browser to display a
Introduction
8
ProSafe Network Management Software NMS200
Reports let you take snapshots of network conditions to aid in analysis of trends, and Audit
Trail Portlets track message traffic between NMS200 and devices.
Additional Products
The following describes how to increase the power of your NMS200 installation. While the
documents mentioned above describe everything available with NMS200, your installation
may provide only a limited subset of those features.
Updating Your License
If you have a limited license — for example NMS200 may limit discovery t o a certain number
of devices— then your application does not function outside those licensed limits.
You can purchase additional capabilities, and can update your license for NMS200 by putting
the updated license file in a convenient directory. Then click License Management in the
Quick Navigation portlet item to open a screen with a button leading to a file browser
(Register License: Select File). Locate the license file, and click the Register License button.
Your updated license should be visible in the License Viewer (See License Viewer on
page 25 for details.)
Note: If you update your installation from a previous one where you
upgraded license, you must also re-register those licenses.
You must restart application server or wait up to 15 minutes before a license modification
takes effect. If you import a license that, for example, changes the application’s expiration
date, it does not immediately take effect. You must restart application server or wait at least
15 minutes.
Online Help / Filter
You can access online help for each portlet by clicking the question mark icon at the bottom
of each portlet.
Introduction
9
ProSafe Network Management Software NMS200
This opens an online help screen with information about the portlet in which you click.
By default, this opens a separate browser window. You can arrange the display so the help
screen does not conceal the portlet it describes. By default it also appears without the table of
contents, index and search tabs. Click the Show button to display those tabs (Hide conceals
them again), and the Prev / Next buttons, or clicking table of contents topics moves to
different topics within the helpset.
Expand / Collapse options
Clicking the Expand / Collapse options button to the right of the question mark expands the
display of buttons so you can click to Refresh Data for the current portlet, or toggle the
display filter and number of items to display, for example. Clicking Expand / Collapse options
again returns to the original display.
A Note About Performance
These applications are designed to help you manage your network with alacrity.
Unfortunately , the devices they manage or the networks that communicate with those devices
are not always as fast as this software. If discovery takes a long time (it can), often network
and device latency is the culprit. You can also optimize installations to be faster (see the
recommendations in the installation and administration guides), and limit device queries with
filters, but device and network latency limit how quickly your system can respond.
Tip: If yo
u use management systems other than this one, you must perform a
device level resync before performing configuration actions. Best
practice is to use a single management tool whenever possible.
Introduction
10
2. Getting Started
This chapter describes how to install and start NMS200 for basic network monitoring and
management.
If you are sure your hardware, software and network is correct and just want to get started
immediately, go to Getting Started on page 15.
The NMS200 portal delivers powerful solutions to network problems, and, in addition to the
NMS200 technology documented in the following pages, NMS200 offers the following
capabilities:
• Message Boards, Blogs, Wikis
2
• Shared
• Enterp
• RSS Feeds
• T
Calendars
rise Chat / Messaging
agging, Ratings, Comments
System Basics
System requirements depend on how you use the application and the operational
environment. Your specific network and devices may require something different from the
recommendations for typical installations.
Generally, 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
The following are supported operating system versions:
• Mi
crosoft 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.
11
ProSafe Network Management Software NMS200
Note: 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.
- You must disable User Account Control if you are installing on Vista or Windows
Server 2008.
- In V
ista, you must either to disable User Account Control or run application server as
service. Another option is to run as administrator on startapp server . In V ista, right click
the startappserver icon and select run as administrator.
- Inst
aller may halt when pre-existing bash sessions or cmd sessions left are open.
Close all such sessions.
Supported Web Browsers
Supported web browsers include:
• Chrome (v 6 and
• Safa
ri (v 5 and above)
• Firefox (v 3.
ternet Explorer (v 8 and above)
• In
Note: Internet Explorer has some minor alignment issues, slower
JavaScript and flash processing. Overall page processing is slower
and some transparencies do not work. You will also see other
anomalies like non-rounded corners, no alpha rendering and others.
above)
6 and above)
You can download and install updates if your browser or version varies from those supported.
To have all NMS200 functionality, you must also install the latest version of Adobe’s Flash™
and Adobe’s Acrobat® that works with these browsers. Flash for 64-bit browsers is currently
a preliminary version, but you can typically run a 32-bit browser even in a 64-bit operating
system, so Flash features will still be available even if you do not want to run Adobe’s beta
software.
Note: If Flash is installed, but the screen still request s it, reload the page in
the browser. Also: Your screen must be at least 1250 pixels wide.
Tip: When no cursor or focus is onscreen, some browsers interpret
backspace as the Previous button.
Getting Started
12
ProSafe Network Management Software NMS200
Hardware Recommendations
NMS200 contains an Application Server that runs continuously in the background, and a
Client (the user interface you actually see). The stand-alone installation runs a Web Serve r in
addition to the application server. Minimum hardware recommendations are based on the
different types of installation available:
ull Installation (Application server + W eb Server) — 2.8 GHz dual core CPU, 4G RAM
• F
(8G for 64-bit operating systems), and 20G available disk space.
• W
eb Server Installation —2.8 GHz dual core CPU, 4G. If you want to serve more than
10 web clients, upgrade your hardware.
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.
Note: See Starting Web Client on page 16 for more information about
using web access to this software.
Network Basics
NMS200 communicates over a network. In fact, the machine where you install it 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.
Dealing with any network barriers to communicating with NMS200, any required initial device
configuration to accept management, and managing security measures or firewalls—all are
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.
Tip: One simple way
device is to open a command shell with S tart > Run
[device IP address]
connected to the network. If not, consult your network administrator to
correct this. No useful information comes from disconnected or
powered-down devices.
Name Resolution
NMS200 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.
to check connectivity from a Windows machine to a
cmd
. Then, type
at the command line. If the device responds, it is
ping
Getting Started
13
ProSafe Network Management Software NMS200
If your network does not have DNS, you can also assign hostnames in
%windir%\system32\drivers\etc\hosts
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
on Windows. Here, you must assign a
Protocols
NMS200 uses the following protocols: TCP/IP, SNMP, HTTP/S, UDP Multicast.
Fixed IP Address
NMS200 includes a web server and application server which must be installed to hosts with
fixed IP addresses or permanently assigned Dynamic Host Control Protocol (DHCP) leases.
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
your local IP address anywhere it appears in
\owareapps\installprops\lib\installed.properties
Alternatively, in a shell, after running
ipaddresschange -n
If you do change your server’s IP address, you must also change the URL for web client
access in your browser.
followed by the new IP address.
oware
to set the environment, you can run
\oware\temp
. Then restart your machine.
. Change
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 or the device’s manuals for instructions about how to
enable those.
Updating Your License
If you have a limited license 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 click License Management in the Quick Navigation menu item. Click Select
Getting Started
14
ProSafe Network Management Software NMS200
File and choose the file. Your updated license should be visible in the License Viewer. See
License Viewer on page 25 for details.
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 import
a license that, for example, changes the application’s expiration
date, it does not immediately take effect. You must restart
application server or wait at least 15 minutes. If you license new
features, restart the application server and client.
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 Guide refers to
those descriptions elsewhere in the NMS200 Installation Guide, Ad min istra tion Guide, User
Guide or online help.
A typical installation means doing the following:
• Installation and Startup— Installation and Startup on
instructions for a basic installation. If you have a large network, or anticipate a large
umber of web clients, then best practice is to install NMS200 as the Installation Guide
n
guide instructs.
• Discovery — After you first install the application, you mu
want to manage. See Discovery on p
• Resource Management — See Managed Resources on p
Guide.
• Configuration
configuration files. See Top Configuration Backups on
• Pro
• Netwo
• Reports — Run reports to clarify the state of your network and devices. See Reports on
• Real-time
blem Diagnosis — See Alarms on page 51 for information about Fault Management.
rk Troubleshooting — See Alarms on page 51, and Chapter 5 for details of
NMS200’s performance management capabilities.
page 161 for details.
issues, both by sending them messages that display the device conditions of concern,
and with online chat within NMS200. See Sharing o
on page 34 for details.
Management — Use NMS200 to backup, restore, and compare
Diagnosis thru Collaboration — Collaborate with others about network
age 26.
page 16 below includes
st discover the equipment you
age 28, and Chapter 6 in this
page 114.
n page 43, and St atus Bar Messaging
Getting Started
15
ProSafe Network Management Software NMS200
CAUTION:
• Unified View — You can scale your NMS200 installation to handle the largest, most
complex environments with distributed deployment. Consult the Installation Guide for
more about installing distributed, and even high availability systems.
• Finally do not n
eglect what Common Setup Tasks on page 28 describes.
Installation and Startup
Application server produces the NMS200 information for web clients. It monitors devices, and
produces the output which the web server then makes available for those web clients.
To manage Windows systems—in single server deployments, you must
install this application on a Windows host. In distributed deployments, a
mediation server installed on Windows must communicate to managed
Windows systems.
Windows installation also installs Internet Information Services (IIS)—
formerly called Internet
IIS on by default. Do not enable IIS on the host(s) running NMS200.
Also: do not install if you are logged in as user “admin.”
Information Server. That installation does not turn
Installation and startup include:
• Running the installer, responding to its prompts.
•
•
• Starting the Client.
• Start using NMS200 as summarized in Getting S
Starting application server. In Windows, you can use the Start button (Start >
Redcell > Start application server), or type
right-click the server manager tray icon and select Start if you have installed NMS200 as
a service and that icon is red, not green.
Starting web server. You can use the Start button (Start > Redcell > Synergy
Manager), or right click th
icon and automate web server startup.
address
application server (or it’s IP address).
hostname:8080
e web server’s tray icon to start it. Y ou can also double-click this
After starting the web server, open a browser and go to the web
where
hostname
startappserver
is the name of the machine running
tarted on page 15, or below.
in a command shell, or
Starting Web Client
You can also open the client user interface in a browser. See Supported Web Browsers on
page 12. The URL is
http://[application server hostname or IP address]:8080
Getting Started
16
ProSafe Network Management Software NMS200
The default login user is netgear, with a password of netgear.
The application server hostname is the name of the system where NMS200 is installed.
A Printer Management - Web layout also comes with the application. Use this for better
performance from web clients.
HTTPS
You can connect to application server securely b
y configuring the included Apache Tomcat
server for secure access. See http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html,
among other resources.
The following sections discuss typical administrative steps in getting started, once you have
installed NMS200. See Getting S t arted on p age 15 for a list of, and links to, other initial t asks
once you have installed NMS200.
Changing the Session Timeout Period
You must modify two
controls the overall server and the other is the push servers for Async-based views. These
web.xml
files are in the following directories:
/dorado/oware/synergy/tomcat-XX/webapps/ROOT/WEB-INF/web.xml
And
/dorado/oware/synergy/tomcat-xx/webapps/netview/WEB-INF/web.xml
The xml element that contains the session timeout is
<session-config>
<session-timeout>30</session-timeout>
</session-config>
web.xml
files with the same values to alter the session timeout. One
The
portal.properties
file is in
/portal/portal-impl/classes
. The property
containing the session timeout (in minutes) is:
session.timeout=30
Control Panel
To configure access to NMS200, you must be signed in as a user with the Administrator role’s
permissions. (The default admin user has such permissions.) The Manage > Control Panel
menu item opens a screen with the tabs of interest.
Tooltips describing these screens and fields appear when you hover the cursor over fields, or
the blue circle surrounding a question mark next to them.
Getting Started
17
ProSafe Network Management Software NMS200
CAUTION:
When you create users with less-than-Administrator permissions, those
users may not see all of the features described in this guide.
Portal > Users
Add users with the following steps:
1. Click Manage
2. Click the Ad
3. Enter th
4. Af
e details of the new user (Name, Job Title, and so on).
ter you click Save notice that the right panel expands to include additional information.
> Control Panel > Portal Users.
d tab under the Users heading at the top of the page.
Make sure you specify a Password. Organizations, Communities, and Roles let you
specify those for the new user.
5. Af
ter clicking the Portal > Users item on the left, click Actions > Manage Pages to the right
of the user to specify which pages this user will see.
6. Y
ou can also click Action > Permissions to configure
ou can also specify contact information and Instant Messenger information. The built-in
7. Y
instant messaging is available to users in NMS200 in addition to such instant messaging.
8. Fin
ally, notice the Miscellaneous information that specifies Announcements to which this
user subscribes, Display Settings and Comments.
Once you have configured a user
, you can click the View All tab and use the Action > menu to
the right of the user listed in Portal > Users on the Control Panel page to do the following:
• Edit — Re-configure the selected user.
• Permis
• Manage Pa
sions — Manage the user’s access to and control over various parts of the portal.
ges — Configure the Public or Private pages for a user, depending on the
selected tab. Possible actions here include changing the look and feel of pages (for
computers and mobile browsers), adding pages and child pages, and importing or
exporting page configurations. Notice that you can configure meta t ags, and javascript on
these pages too.
Exports are in
you are using. The export screen lets you select specific features, and the date range of
pages to export.
• Deac
click the Deactivate button above the listed users.
.lar
format, and go to the download location configured in the browser
Tip: If
you want to set up several pages already configured elsewhere for
another user, or even for an entire community of users, export those
pages from their origin, then Manage Pages from the Action menu for the
user or community.
tivate — Retires a user configured on your system. You can also check users and
Getting Started
18
ProSafe Network Management Software NMS200
Your organization has a number of geographic locations and you plan to manage the network
infrastructure for all these locations using RC7 Synergy. You can define the geographic
locations to which devices can be associated. This will help you manage and view your
network, grouped by location or branches. See Locations on page 83 for the specifics about
the portlet where you can set up locations.
Tip: To edit your own information as a signed-in user, simply click your login
name in the upper right corner of the portal screen.
Portal > Communities
Add Communities with the following steps:
1. Click Man
2. Click the Add t
3. Ente
4. By clicking Actio
permissions, viewable pages and so on.
age > Control Panel and navigate to Portal > Communities.
ab under the Communities heading at the top of the page.
r the details of the new community (Name, Description).
ns to the right of any listed Community, you can also select its membership,
Database Aging Policies (DAP)
Database Aging Policies prevent the NMS200 database from filling up by saving designated
contents to an archive file on a specified cycle. Database Aging Policies configure which
contents to archive, the archive location, and the configuration of that archive file.
To view and manage such policies, right click an item with them (for example, an alarm), and
under Redcell click Database Aging Policies.
Policies appear in the Aging Policies tab of this screen, with columns that indicate whether
the policy is Enabled, the Policy Name, Details (description), Scheduled Intervals and icons
Getting Started
19
ProSafe Network Management Software NMS200
triggering three Actions (Edit, Delete and Execute). Notice that the bottom right corner of this
page also lets you Enable / Disable / Execute All policies listed.
DAP Workflow
The following are steps typical for implementing DAP:
1. From the screen list
ing Database Aging Policies (DAP), click Add Policy, and select a
policy from the displayed list of alternatives.
2. Th
3. In
is opens Aging Policies Editor.
the Aging Policies > General tab, specify the name, schedule interval, whether this policy
is Enabled, and so on.
pecify the Archive Location. Those listed are the Repositories listed on the Repositories
4. S
tab. You can manage those on tha t tab.
5. In
the Aging Policies Options tab, specify either the archiving and retention you want, or
further specify Sub-Policies that refine the items archived, and specify archiving and
retention for those sub-policy elements. Which one you can specify depends on t he type of
DAP you
6. Click Apply
are configuring.
until the displayed screen is the DAP manager.
Aging Policies Editor
When you click Add Policy in the upper right corner of the Database Aging Policies (DAP)
screen, first a selector appears where you can click on the kind of policy you want to create,
then the editor appears. If you click the Edit icon to the right of a listed policy, the Aging
Policies Editor appears with that policy’s information already filled out, ready to modify.
The General screen has the following fields:
• Name — An identifier for the policy
Getting Started
20
ProSafe Network Management Software NMS200
• Description — A text description of the policy
• Enabled — Check to enable the policy.
• Sc
• Base Archive
• Compress Archiv
hedule Interval — Use the pick list to select an interval. Once you have configured an
interval here, you can re-configure it in the Schedules Portlet.
Name — The prefix for the archived file.
e — Check to compress the archive file.
• Arc
hive Location — Select from the available Repositories in the pick list.
Aging Policies Options
The Options tab in this editor can vary, depending on the type of policy.
Typical fields can include the following:
• Keep [Aged
before archiving it.
• Arc
hive [Aged Item] — Check this to activated archiving according to this policy.
Item] for this many days — The number of days to keep the aged item
Getting Started
21
ProSafe Network Management Software NMS200
Sub-Policies
Some types of Database Aging Policies can have sub-policies that further refine the aging f or
their type of contents.
These appear listed in the Aging Policies Options tab. Click Add Sub Policy to create them.
Notice that you can Edit or Delete listed policies with the icons in the far-right Action column
in this list.
Such sub-policies contain the following types of fields:
• Compo
• Action
• Reten
nent — Select the component for the sub-policy from the pick list.
Type — This further sub-classifies the Component.
tion (Days) — The number of days to keep the aged item before archiving it.
Getting Started
22
ProSafe Network Management Software NMS200
• Archive — Check this to activated archiving according to this policy.
Repositories
When you select a repository in the Aging Policies Editor, the available policies come from
what is configured in this tab of the editor.
Available repositories appear listed in the initial screen. Like the Aging Policies Editor, you
can click Add Repository to create a new repository, and Edit or Delete selected, listed
policies with the icons in the Action column. Notice the listed policies indicated whether the
archiving destination is Online with a green icon (this is red, when the destination is offline).
When you Add Repository or Edit an existing one, the following fields appear in the editor:
Getting Started
23
ProSafe Network Management Software NMS200
• Repository Name — An identifier for the archiving destination.
• Desc
• Vi
• Online — Check this to put this repository online.
ription — A text comment.
rtual Path — This is the path relative to the installation root directory.
Quick Navigation
The Quick Navigation portlet lets you quickly perform some basic tasks:
• Resource Discovery—Discover devices in your network with the Quick Discovery
defaults, or lets you construct a Quick Discove
Discovery on
• Link Discovery — After you have discovered resources, this discovers their connections.
See Link Discovery on p
• Back
• OS Image
• Deplo
up Config Files — This lets you back up discovered devices’ configuration files.
Before you can use this feature, you must have servers configured as described in
Netrestore File Servers on p
Management on
page 78 for more about these capabilities.
y OS Image — This deploys firmware updates. To deploy images, you must have
File Servers configured, as described above for Backup. See Deploy OS on p
page 123 for details.
age 145.
age 30 and/or File Servers on page 74. See also File
page 138.
Upload — Upload firmware updates for devices. See OS Image Editor on
Getting Started
24
ry profile if none exists. See Resource
age 80.
ProSafe Network Management Software NMS200
• View / Add Licenses — This lets you see and manage the licensed capabilities of
NMS200. See License Viewer below for details.
License Viewer
This screen appears when you click View / Add Licenses in the Quick Navigation portlet.
Register License
To register a license click the Sele
select a license file.
You must restart application server or wait up to 15 minutes before a license modification
takes effect. If you import a license that, for example, changes the application’s expiration
date, it does not immediately take effect. You must restart application server or wait at least
15 minutes.
Product Licenses
This portion of the License Viewer lists the
displaying the Product, Edition, Expire Date, whether the license is Valid, any IP restrictions,
the User who installed the product and/or license, and the Version of product for which the
license is valid.
License Details: [Product]
This portion of the screen displays the details of a license selected in the Registered Prod uct
Licenses portion of the License Viewer screen. It is blank if you have not select ed a license in
the list above this panel.
ct File button at the top, and use the subsequent screen to
products for which you have licenses already,
Getting Started
25
Device Licenses
ProSafe Network Management Software NMS200
This tab displays the M
the Variance between maximum and managed, and Type of license.
aximum Allowed number of licenses for devices, the Count Managed
Discovery
To begin managing resources in your network, you must discover them to store their
information in the application database. This begins with Discovery Profiles portlet. By
default, this appears in the Admin page.
Discovery profiles configure equipment discovery for NMS200.
The summary view displays the Name, Description, Default (the green check indicates the
default profile), whether the profile is Scheduled and Next Execution Date for scheduled
discovery.
To Begin
1. Right click th
2. Th
e Discovery Profile Editor appears, with a step-by-step set of screens to configure
resource discovery. You can navigate through it by clicking the screen tab names at the top,
by clicking the Next button at the bottom of the page.
or
e Discovery Profiles list and select New.
Discovery Profile Editor
Use this editor to configure discovery . Baseline discovery is the initial discovery to compare to
later discoveries. Follow these steps to discover equipment on your network:
3. General Par
default.
4. Profile Options — Select the Device Naming Fo
discovered), whether to Manage by IP address or hostname, and check whether to Resolve
Hostname(s), ICMP Ping Device(s), Manage ICMP-only Device(s), or Manage
Unclassified Device(s). This last checkbox determines whether NMS200 attempts to
manage devices that have no device driver installed. Management may be possible, but
more limited than for devices with drivers installed, provided this capability is one you have
licensed.
ameters — Set the Name, Description and whether this profile is the baseline
rmat (how the device appears in lists, once
Getting Started
26
ProSafe Network Management Software NMS200
Network
5. Af
ter you click Next, the Network screen appears.
• Network
Type and Addresses — Select the type of entry in the pick list (IP
Address(es), CIDR Address, Hostname, SNMP Broadcast, Subnet).
Tip: Y
ou can specify an IP Address range by separating the beginning and
end with a dash. For example: 192.168.1.1 - 192.168.1.240.
The tooltips in the data entry field describe what valid entries look like.
6. Authenticati
on — You can create new, or add existing authentications. See for details.
Notice that authentications appear with Edit / Delete icons and Up / Down arrows on their
right. The Edit icon opens the authentication editor. Click the arrows to arrange the order in
which credentials are tried (top first). Ordering only applies when two credentials are of the
same type.
Inspect
7. Inspe
ct — This screen lets you preview the discovery profile’s actions and access to
devices. If you clicked Next rather than Inspect at the bottom of the previous screen, click
Start Inspection in the top right corner of this screen to begin the inspection process that
validates the device’s credentials.
Notice that the I
nspection Status fields at the bottom of the screen indicate the success or
failure of Ping, Hostname resolution, and Authentications.
If the device does not match all required authentications, you can click the Fix it icon
left) to edit them for the selected device.
When authentications are unsuccessful, yo
u can click Previous to go to the Network
screen and remove or edit them.
(far
8. Save — Click Save to preserve the pro
file. You can then right -click it to select Execute and
begin discovery. If you select Execute from the profile editor, NMS200 does not save the
profile to execute later.
Results
9. Execu
te — Clicking Execute begins discovery, and the message traffic between NMS200
and the device appears on the Results screen.
This is a standard Audit screen.
See Audit Trail / Jobs Screen on page 45 for more about
it.
10. A message
(Discovery Profile Execute is complete) appears in the Messages at the
bottom left of the status bar.
Tip: Y
ou can also schedule discovery profiles to run periodically, updating
your NMS200 database with any network changes. For more, see
Schedules on p
age 48.
Getting Started
27
ProSafe Network Management Software NMS200
11. The devices in your network now appear in the Managed Resources portlet, and elsewhere
(in Topology, for example).
See Discovery Pro
files on page 124 for more details about this process.
Managed Resources
This portlet displays all the devices you have discovered.
See Managed Resources on page 133 for the details of this screen’s capabilities.
See also Managed Resource Groups on page 130.
Common Setup Tasks
By default this portlet appears on the first page after you sign in, and reminds you of the
following common tasks:
• SMTP Configuration
• Netrestore File Servers
• Netre
A red flag appears with the “Setup required” message in the S
not configured. Configuring them displays a green flag with the “Setup complete” message.
Click the edit link in the Action column to open editors for each of these.
store OS Images
tatus column when these are
SMTP Configuration
You can use NMS200’s messaging capabilities to communicate with other users, but if you
want to receive e-mails automated by actions like configuration file backups, NMS200 must
Getting Started
28
ProSafe Network Management Software NMS200
have a mail account. This screen configures the e-mail server so NMS200 can send such
automated e-mails.
This screen contains the following fields:
• SMTP Server Host — The IP address or hostname of your SMTP server.
• SMTP Server Port — The port for your SMTP server (110 is typical).
• Authentic
ation Enabled — Check this to enable authentication for this server. Checking
enables the next two fields.
• User Name — The login ID for the SMTP server, if authentication is enabled.
• Password — The password for the SMTP server, if authentication is enabled.
• Use SSL — Enable Secure Sockets Layer protocol to in
teract with your SMTP server.
• Return Address — The return address for mail sent from NMS200.
• Default Subj
ect — Text that appears by default in the subject line of mail sent by
NMS200.
• Connectio
• Max
Per Minute — The maximum number of e-mails NMS200 can send per minute.
n / Send Timeout — The time-outs for mail sent by NMS200.
• SMTP Server Host — The IP address or hostname of your SMTP server.
• SMTP Server Host — The IP address or hostname of your SMTP server.
Two settings for e-mail servers appear in Control Panel, one in the Control Panel > Portal >
Settings Mail Host Names edit screen, and another in Control Panel > Server Administration
> Mail. The Portal-based e-mail settings help Administrators limit signups to e-mails only
existing in their organization. The screen in that panel provides a list of allowed domain
names, if that feature is enabled.
Control Panel > Server Administration > Mail is where to configure the Main server and
authentication for routing mail
Getting Started
29
ProSafe Network Management Software NMS200
Netrestore File Servers
The Netrestore file servers provide FTP connections for retrieving and deploying devices’
configuration files, and for deploying firmware updates to devices on your network. See File
Servers on page 74 for a description of the portlet that manages file servers. If you want to
configure servers from the Common Setup Tasks portlet, a slightly different screen appears
when you click Edit.
This displays configured file servers. Configure new servers by clicking the new file server
link in the upper right corner. The editing process after that is as described in File Server
Editor on page 76.
Getting Started
30
Loading...