Dell OpenManage Network Manager User Manual
Dell OpenManage Network Manager Version 5.3 Service
Pack 2
Web Client Guide
Notes and Cautions
A NOTE indicates important information that helps you make better use of your computer.
A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.
____________________
© 2014 Dell Inc.
Trademarks used in this text: Dell™, the DELL logo, PowerEdge™, PowerVault™, PowerConnect™, OpenManage™, EqualLogic™,
KACE™, FlexAddress™ and Vostro™ are trademarks of Dell Inc. Microsoft
are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat Enterprise Linux
and Enterprise Linux
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.
®
are registered trademarks of Red Hat, Inc. in the United States and/or other countries.
®
, Windows®, Windows Server®, MS-DOS® and Windows Vista®
®
2014-6
Rev. A02
Contents
1 Getting Started with Dell OpenManage Network Manager . .7
Why Dell OpenManage Network Manager?. . . . . . . . . . . . . . . . . . . . . . . . . 1
Key Features
Networks with Dell OpenManage Network Manager
Additional Products
Online Help / Filter
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
A Note About Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
System Basics
. . . . . . . . . . . . . . . . . . . . . . . . . .
Single Server Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Sizing for Standalone Installations
Network Basics
Authentication
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
13
15
17
Device Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Base Driver
Supported PowerConnect Models
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
Windows Management Instrumentation (WMI) Driver
Web-Based Enterprise Management (WBEM) Driver
. . . . . .
. . . . . . .
18
19
19
20
Ports Used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Protocol Flows
. . . . . . . . . . . . . . . . . . . . . . . . . .
Ports and Application To Exclude from Firewall
Installed Third Party Applications
. . . . . . . . . . . . . . . . .
Windows Management Instrumentation Ports
. . . . . . . . . .
. . . . . . . . . .
26
27
27
28
Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Installation and Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Install on Linux
Perl
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting Web Client
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
32
38
38
Secure Connections: SSL & HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Enabling Secure SSL
Install on Linux
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
39
41
Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Admin / [My Account]
[Domain]
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Portal > Users and Organizations
Public / Private Page Behavior
Portal > Roles
Portal > Portal Settings
Portal > [Other]
Redcell > Permission Manager
Redcell > Data Configuration
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
44
44
44
48
49
51
52
52
55
2
3
4
4
8
iii
Redcell > Filter Management
Redcell > Application Settings
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
56
57
Redcell > Database Aging Policies (DAP). . . . . . . . . . . . . . . . . . . . . . . . . . 58
Aging Policies Editor
Aging Policies Options
Sub-Policies
Repositories
Server
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
61
63
63
64
67
LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
LDAP Portal Settings
. . . . . . . . . . . . . . . . . . . . . . .
70
Configuring Pages and User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Page Level Permissions
Portlet Level Permissions
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
72
74
Quick Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Network Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Ping Tool
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MIB Browser Tool
Direct Access Tool
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
78
79
79
License Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
License Expiration Warning Alarms
. . . . . . . . . . . . . . . .
81
Discovery Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Incomplete Discovery
. . . . . . . . . . . . . . . . . . . . . .
86
Managed Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Common Setup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Password Reset
SMTP Configuration
Netrestore File Servers
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
87
88
90
Deploying and Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Deploy Files
Extensions
.ocp and .ddp files
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
Localizing Message Files
. . . . . . . . . . . . . . . . . . . . .
91
91
91
91
2 Portal Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Tooltips
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Refresh
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Back Button
Shift+Click
Show Versions
The Dock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Status Bar Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Chat / Conferencing
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
93
94
94
94
95
99
iv
Menu Bar
. . . . . . . . . . . . . . . . . . . . . . . . . . .
100
See How to: Create a new Page and Rearrange Pages on page 73 for more
information
.Site Map
Graphs / Tooltips
Portlets
Expanded Portlets
Locating Portlets
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
101
101
101
102
106
109
Common Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Import / Export
Sharing
Edit Custom Attributes
View as PDF
Ta g
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
109
110
112
113
114
Audit Trail / Jobs Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Audit Trail Portlet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Schedules Portlet
. . . . . . . . . . . . . . . . . . . . . . .
120
3 Key Portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Expanded Alarm Portlet
Alarm Editor
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
Audible Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Adding Custom MP3 Sounds
. . . . . . . . . . . . . . . . . .
Event History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Event Processing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Rule Editor
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Event Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Event Definition Editor
. . . . . . . . . . . . . . . . . . . . .
Alarm Propagation to Services and Customers: What Happens
Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Vendors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
.
126
131
133
139
158
167
4 Resource Management and Reports . . . . . . . . . . . . . . . . . . . 177
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Resource Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Discovery Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Discovery Profile Editor
. . . . . . . . . . . . . . . . . . . . .
Managed Resource Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Static Group
. . . . . . . . . . . . . . . . . . . . . . . . . .
183
193
v
Dynamic Group
. . . . . . . . . . . . . . . . . . . . . . . . .
194
Managed Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
New Link
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link Discovery
. . . . . . . . . . . . . . . . . . . . . . . . .
207
208
Search by IP or Mac Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Equipment Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Direct Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
MIB Browser
Te rm in a l
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ping (ICMP)
HTTP / HTTPS
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
214
216
217
218
Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Port Editor
. . . . . . . . . . . . . . . . . . . . . . . . . . .
221
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Report Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Report Template Editors
. . . . . . . . . . . . . . . . . . . .
224
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Report Editor
. . . . . . . . . . . . . . . . . . . . . . . . . .
Branding Reports
Group Reports
. . . . . . . . . . . . . . . . . . . . . . . . .
User Login Report
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
235
237
238
239
5 Display Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241
Context
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Container Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Container Editor
Container View
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
Map Context. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Maps and Containers Together
Using Nokia Maps
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
Visualize My Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Configuring Views
Tools
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Design Tools
Linked View
View
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Properties and Settings > Layouts Tab
Properties and Settings > Properties
Legend Tab
Top-Level Nodes Tab
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
242
244
247
251
253
255
257
259
260
261
262
263
265
266
266
vi
Alarms in Visualizations / Topologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Links in Visualization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Visualizer Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
6 File Server / File Management . . . . . . . . . . . . . . . . . . . . . . . . . 269
File Server Editor
Recommended Windows File Servers
File Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Configuration Files
Image Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Firmware Image Editor
Configuration Image Editor
Deploy Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Deploy Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
270
271
278
283
284
7 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Performance and Monitors
Application Server Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Resource Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Retention Policies
Monitor Editor
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
Self Management / Self Monitoring: Default Server Status Monitor 313
Monitor Options Type-Specific Panels
Scheduling Refresh Monitor Targets
Top N [Assets] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Top Configuration Backups
Dashboard Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Performance Dashboard
Dashboard Editor
. . . . . . . . . . . . . . . . . . . . . . . .
Show Performance Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
291
300
302
317
328
331
334
335
8 Traffic Flow Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .347
How does it work?
Setup
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporter Registration
Traffic Flow Portlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Drill Down
Search
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Traffic Flow Snapshot
Traffic Flow Analyzer - Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
348
349
350
354
355
356
vii
9 Change Management / ProScan . . . . . . . . . . . . . . . . . . . . . . .359
ProScan Portlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Compliance Policy Summary
Creating or Modifying a ProScan Policy
Creating or Modifying ProScan Policy Groups
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . .
364
365
381
Change Determination Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Change Determination Process Workflow
. . . . . . . . . . .
Triggering Change Management and ProScan
Change Determination Defaults
. . . . . . . . . . . . . . . . .
. . . . . . . . .
383
384
387
Compliance and Change Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
10 Actions and Adaptive CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393
Using Adaptive CLI
Actions Portlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Adaptive CLI Editor
General
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Attributes
Scripts
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Comparison
External Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Seeded External Scripts
Adaptive CLI Script Language Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Attributes
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conditional Blocks
Perl Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Monitoring Upload / Download Speeds
Regular Expression Testing
Scheduling Actions
Active Performance Monitor Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Troubleshooting Adaptive CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Adaptive CLI Records Aging Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
394
400
400
402
408
413
416
418
419
434
438
439
viii
Dell OpenManage Network Manager can give you automated, consolidated configuration and
control of your network’s resources. It is customizable, unifying multiple systems while still
communicating with other software systems (like billing) in generic WSDL, XML and SOAP.
OpenManage Network Manager’s
runtime features supporting these applications. Consult Release Notes for information about
changes not covered in this
first chapter of theUser Guide
User Guide
.
describes security and some of the
Why Dell OpenManage Network Manager?
Dell OpenManage Network Manager’s benefits:
Productive
Discovery and wizard-driven configuration features within minutes of installing Dell OpenManage
Network Manager, you can monitor your network.
Easy
Dell OpenManage Network Manager provides the network information you need, and offers
advanced capabilities with minimal configuration overhead.
Preface
Valuable
Dell OpenManage Network Manager often costs less to use and maintain than most other
solutions.
Scalability
You can scale Dell OpenManage Network Manager to almost any size.
LinkLight
www.doradosoftware.com/thelinklight/
developed to provide users with useful information, tools and valuable resources related to
OpenManage Network Manager network management solutions.
Online Community
is a community site that OpenManage Network Manager
Why Dell OpenManage Network Manager? |
1
Key Features
The following are some key features of Dell OpenManage Network Manager:
Customizable and Flexible Web Portal
You can customize the web portal, even providing custom designed views of your data assigned to
individual users. You can even create web portal accounts for departments, geographic areas, or
other criteria.
Automate and Schedule Device Discovery
Device discovery populates Dell OpenManage Network Manager’s database and begins network
analysis. You can also create network discovery schedules to automatically run Discovery whenever
you need them.
Dell OpenManage Network Manager Administration
You can now conduct administrative tasks—adding devices, user accounts, and web portal
displays—from a secure console on your network.
Open Integration
Dell OpenManage Network Manager supports industry standards. It comes with an open-source
MySQL database, and supports using Oracle databases. It also uses industry-standard MIBs and
protocols, and even lets you install open-source screen elements like Google gadgets to the web
portal.
Topology
The OpenManage Network Manager topology screen lets you create multi-layered, fully
customizable, web-based maps of your network to track devices wherever they are in your network.
Alarms
You can configure custom alarms to respond to hundreds of possible network scenarios, including
multiple condition checks. Dell OpenManage Network Manager’s alarms help you recognize issues
before your network users experience productivity losses. Alarms can also trigger actions like email,
executing Perl scripts, paging, SNMP traps, Syslog messaging, and external application execution.
Traps and Syslog
Dell OpenManage Network Manager lets you investigate network issues with traps and Syslog
messages. You can use Dell OpenManage Network Manager to set up events / alarms and then
receive, process, forward, and send syslog and trap messages.
2
Why Dell OpenManage Network Manager? |
Reports and Graphs
NOTICE
Dell OpenManage Network Manager comes with many pre-configured reports and graphs to
display data from its database. You can archive and compare reports, or automate creating them
with Dell OpenManage Network Manager’s scheduler.
Modularity
With additional modules, Dell OpenManage Network Manager can analyze network traffic,
manage services and IP address and subnet allocations. OpenManage Network Manager modules
save time adding to existing Dell OpenManage Network Manager deployments to add feature
functionality without requiring additional standalone software.
Networks with Dell OpenManage Network Manager
The beginning of network management with Dell OpenManage Network Manager is Discovery
Profiles of the resources on a network. After that occurs, you can configure
(topology views), Resource Monitors and Performance Dashboards.
Once you have done these initial steps, Dell OpenManage Network Manager helps you understand
and troubleshoot your network. For example: Suppose a OpenManage Network Manager
Performance Dashboard displays something you want to troubleshoot. You can right-click the
impacted device in the
The color of the icon in this view indicates the highest severity alarm on the device or its subcomponents. For example, red indicates a
Displays include right-click access to the Details screen (see Equipment Details on page 210),
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 N [Assets] you may conclude some configuration
changes made memory consumption spike. Right-click to access resource actions under
Management
previous. You can also back up devices (see Backup Configurations on page 274) and restore
previously backed up files (see Restore Configurations on page 276). Finally, you may simply want
to Resync (another right-click menu item) to insure the device and your management system are
up-to-date.
that let you see the current configuration files on devices, and compare current to
Visualize My Network
Critical
topology view to access configuration and actions.
alarm.
Visualize My Network
File
Alternatively, the Alarms portlet also lets you right-click to expose Alarm Actions.
You can right click for Direct Access – Telnet or Direct Access – MIB Browser to display a command
line telnetting to the device, or an SNMP MIB browser to examine SNMP possibilities for it.
Why Dell OpenManage Network Manager? |
3
The Managed Resources portlet can display the anatomy of a Resource with its right-click actions
NOTE:
(see Equipment Details on page 210). 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.
Reports let you take snapshots of network conditions to aid in analysis of trends, and
Portlet
s track message traffic between Dell OpenManage Network Manager and devices.
Audit Trail
Additional Products
The following describes how to increase the power of your Dell OpenManage Network Manager
installation. While the documents mentioned above describe everything available with Dell
OpenManage Network Manager, your installation may provide only a limited subset of those
features.
Updating Your License
If you have a limited license — for example OpenManage Network Manager may limit discovery to
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 OpenManage Network
Manager by putting the updated license file in a convenient directory. Then click
Management
browser (
button. Your updated license should be visible in the
81
for details.)
in the Quick Navigation portlet item to open a screen with a button leading to a file
Register License: Select File
). Locate the license file, and click the
License Viewer
(See
License
Register License
License Viewer on page
If you update your installation from a previous one where you upgraded license, you must also install
new licenses.
Licenses now support three expiration formats: Never, Date certain, and a format that indicates the
license will be valid for a number of days after registration.
Online Help / Filter
Access general online help by clicking
appropriate to each portlet appears when you click question mark icon on the portlet title bar.
4
Why Dell OpenManage Network Manager? |
Help
in the
The Dock
at the top of the screen. Help
By default, this opens a separate browser window which is not necessarily always in front of the
NOTICE
How To:
NOTICE
screen that calls it. Because it is separate, you can arrange the display so the help screen does not
conceal the portlet it describes. Click the
tabs (
Hide
conceals them again), and the
moves to different topics within the helpset.
Sometimes your browser’s cache may interfere with help’s correct appearance. If you see a table of
contents node without contents, you can often repair it by refreshing the panel or whole screen.
Show
button to display the contents, index and search
Prev / Next
buttons, or clicking table of contents topics
Use “How To”
Several sections of what follows contain the “How to” instructions for use. These are typically steps
to follow to produce the desired result. For a look at all such steps available, refer to the
section of the Index.
How to
A Note About Performance
Dell OpenManage Network Manager is designed to help you manage your network with alacrity.
Unfortunately, the devices managed 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 first chapter of the
with filters, but device and network latency limit how quickly your system can respond.
User Guide
and
first chapter of theUser Guide
s), and limit device queries
If you 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.
A Note About Performance |
5
6
A Note About Performance |
Getting Started with Dell OpenManage
NOTICE
Network Manager
This chapter describes how to install and start Dell OpenManage Network Manager for basic
network monitoring and management. For more detailed descriptions of all this software’s features,
consult its other manuals (the OpenManage Network Manager first chapter of the
OMNM User Guide, first chapter of theUser Guide
If you want to find something but are unsure about which manual it is in, you can search all text in the
Acrobat files in a single directory. You can also click on the blue cross-references to go to the target
destination of cross-references in Acrobat, however for such electronic cross-references to the other
documents to work, they 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.
If you are sure your hardware, software and network is correct and just want to get started
immediately, go to Getting Started on page 28.
The Dell OpenManage Network Manager portal delivers powerful solutions to network problems,
and, in addition to the OpenManage Network Manager technology documented in the following
pages, Dell OpenManage Network Manager offers the following capabilities:
• Message Boards, Blogs, Wikis
• Shared Calendars
• Enterprise Chat / Messaging
• RSS Feeds
• Tagging, Ratings, Comments
Because many capabilities are only indirectly related to Dell OpenManage Network Manager’s
operation, this guide does not cover them comprehensively. The section Server on page 67
describes how to set up some of these features.
and
User Guide
) or the online help.
User Guide
,
3
Troubleshooting
Suggested mini-troubleshooting steps:
1
Refresh the browser. If that doesn’t work,
2
Stop and start the web server and/or application server. Command lines for this:
startappserver / stopappserver
| Getting Started with Dell OpenManage Network Manager
7
For Windows, to start the web server manager:
X.X.X\bin\startsynergy.
/etc/init.d/synergy start / /etc/init.d/synergy stop
3
Clear the browser’s cache (Firefox in particular loves persistent old pages), then refresh.
4
Stop and start the browser.
5
If all else fails: Reboot the host and re-start the application server, web server and browser.
For Li n ux.
oware\synergy\tomcat-
When troubleshooting (or contacting technical support), you may find pertinent information in
logs located in the following directories:
..\oware\jboss-3.0.8\server\oware\log
..\oware\temp\soniqmq.log
..\app_setup.log
..\db_setup.log
You can also run
script creates a
logs.jar
getlogs
logs.jar
to
oware\temp. logs.jar
from a command line. The
file in the root installation directory, and moves any existing copy of
getlogs
script packages relevant logs. This
compresses all logs necessary for troubleshooting. Read
the jar yourself, or forward this jar to technical support to help troubleshoot.
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.
Upgrading from a Previous Version
When you upgrade your OpenManage Network Manager installation from a previous version, keep
the following in mind:
Operating System Upgrade
If your operating system is not supported in the upgrade version, upgrade to a supported operating
system before upgrading Dell OpenManage Network Manager. The way to do this is to do the
following:
• Back up the database.
• Upgrade the operating system.
• Install the original Dell OpenManage Network Manager on the new operating system.
• Restore the database.
8
| Getting Started with Dell OpenManage Network Manager
• Proceed with the installation / upgrade of Dell OpenManage Network Manager.
See Database Backup on page 65 and Restoring Databases on page 66 for details.
General Advice
• Make sure you log out of the operating system between installations.
• Upgrading requires a new license to activate new features.
• Close any open browsers when upgrading.
• The following require manual migration (export, then import) from previous versions: SMTP
settings, some scheduled items. Some schedules may require deletion / re-making. If you open
them and they are blank, use this method.
• You must re-create topologies as Visualizations. (suggestion: take a screenshot)
• Group Operations have been deprecated, replaced by Adaptive CLI.
• The default password policy puts no restrictions on password length.
• Adaptive CLI with Perl scripts must contain valid Perl under the “strict” pragma (use strict;).
If you import or migrate from a previous version a Perl script that does not pass this “strict”
criterion, you must rewrite it for “strict” compliance before it can be successfully edited or
copied.
• Any configured color changes to the portal may not persist and must be re-made manually.
Similarly, customized page layouts or page order may not persist and you must typically rearrange them manually.
Handling Missing Users
If you have upgraded your Dell OpenManage Network Manager installation, users and/or their role
associations may not appear. You can fix this by going to one of the following screens:
Roles > Administrator > Actions > Assign members.
Roles > Power users > Actions > Assign members.
Roles > [ROLENAME] > Actions > Assign members.
Then click
Update associations.
Supported Operating System Versions
The following are supported operating system versions:
Microsoft Windows
Windows Vista (Business or Ultimate) forward, with their latest service packs. The supported
operating systems include: Windows 2008 (including R2), Enterprise Edition, Windows
Vista, Windows 7 (Business or better) and Windows 2012.
To install on Windows 2012, click the win_install.exe file (not the shortcut, but the file in
Disk1\instdata directory), and select the
compatibility mode for ...
—This application supports most 64-bit Windows operating systems from
Compatibility
tab. Check
Run this program in
then select either Windows 7 or Vista. Command line installations
| Getting Started with Dell OpenManage Network Manager
9
are supported without any compatibility issues. Do likewise if you must uninstall (find the
NOTE:
CAUTION:
CAUTION:
NOTICE
uninstall program and run it in compatibility mode).
Windows 2008 R2 Enterprise may indicate a PermGen size problem.Workaround: Increase PermGen size
in the Synergy Network Management Properties’ Java tab from the tray icon (XX:MaxPermSize=512m).
Increase the specified memory from from 256m to 512m, then Stop Service and Start Service after rightclicking the tray icon. This is a known issue for Windows 2008, not Dell OpenManage Network Manager.
• 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.
Alternatively, you can run application server as service. Another option is to run as
administrator on startappserver. In Vista, right click the startappserver icon and select run as
administrator.
• Installer may halt when pre-existing bash sessions or cmd sessions are left open. Close all such
sessions before installing.
The Dell OpenManage Network Manager’s installer does not validate operating systems, so it allows
installation on unsupported operating systems
Linux
—This application supports Red Hat (Enterprise version 6.2) Linux, 64-bit only, and 64-bit
CentOS (6.2). See Install on Linux on page 41 for more about how to improve your Linux
experience.
10
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. Make sure to remove
or rename the my.cnf file for that previous installation. If it is on the path, it can interfere with the correct
operation of Dell OpenManage Network Manager. The origin of the configuration in the several my.cnf
files on Linux is /opt/dorado/oware3rd/mysql/5.0.51-pc-linux-i686-64/my.cnf, so be sure to alter that one if
you are reconfiguring OpenManage Network Manager’s MySql.
To determine your Linux system’s version, run the following at a command prompt:
cat /etc/redhat-release
| Getting Started with Dell OpenManage Network Manager
VMware
NOTE:
NOTICE
—Dell OpenManage Network Manager supports the above operating systems on VMware
virtual machines. We test Dell OpenManage Network Manager primarily on Windows
2008R2 and Redhat on virtual machines. For a more extensive discussion of using VMware,
see the first chapter of the
Windows handles upgrading the Windows operating system. Best practice is to export the database,
upgrade the operating system, then upgrade Dell OpenManage Network Manager. See Upgrading from a
Previous Version on page 8 and Upgrade on Linux on page 35 for more details about such upgrades.
User Guide
.
Supported Web Browsers
Supported web browsers include:
• Chrome (v 22 and above)
• Safari (v 6 and above)
• Firefox (v 12 and above)— Some pop-ups may not appear in v. 14 and later.
• Internet Explorer (v 9 and above)
Internet Explorer versions 8 and older have display alignment issues, have slower JavaScript
and Flash processing, and some transparencies do not work. Other anomalies include nonrounded corners, no alpha rendering, scroll bars in performance indicators, non-working
multi-level menus, a too-large OS Images schedule form, and others. To fix these anomalies,
install the Chrome plug-in you can download from the internet. After it installs, close IE and
re-open it. The look and feel should improve.
Internet Explorer 9 or above, if set up in compatibility mode with Internet Explorer 7 or
Internet Explorer 8 has difficulties rendering the user interface.
Screen resolution must equal or exceed 1280 x 1024 pixels. Users running Safari on an Apple
machine must modify Java preference to run applets as their own process. Java Preferences are
under Applications > Utilities on OSX.
You can download and install updates if your browser or version varies from those supported. To
have all Dell OpenManage Network Manager functionality, you must also install the latest version
of Java (v.1.6 or later) 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. If Flash is installed, but the screen still requests it, reload the page in the
browser. Install the latest Flash. Also: Your screen must be at least 1250 pixels wide.
When no cursor or focus is onscreen, some browsers interpret backspace as the Previous button. Also:
Some browsers (Firefox) retain cached pages past their usefulness. To reload a page without cache, for
Firefox, hold Shift while clicking the reload button. You can also use Ctrl+Shift+R or Ctrl+F5 to do this. That
said, recent Firefox builds have still retained cache even after applying those remedies. Your mileage
may vary, but Chrome (or Internet Explorer with the Chrome plug-in) functions correctly now.
| Getting Started with Dell OpenManage Network Manager
11
Best practice/Web portal /Multitasking
You can open multiple tabs to different managers in OpenManage Network Manager. In most cases
this does not cause any issues for read–only browsing of data. Opening multiple tabs is not
recommend when creating, editing or deleting. In these scenarios there may be cases where
Web session information may not be reported back correctly and task completion may appear to
never finish. One example is a job status updates. In this case a job may be submitted and it will
appear to be stuck “running” when in reality it has already finished but the status has not updated
in the browser session. When this occurs the user can manually click the refresh button on the job
status window to manually force and update. It is not productive to watch a long running process in
the job status. The recommended process is to close the job status window and move on to other
tasks. The “My Alerts” feature will alert the user when they have a completed job status.
Single Server Hardware
The following describes hardware and sizing configuration for common Dell OpenManage Network
Manager deployments. Before any deployment, best practice is to review and understand the
different deployment options and requirements. Consider future growth of the network when
estimating hardware sizes. You can often expand modern systems running Dell OpenManage
Network Manager by adding more RAM to the host server(s). Selecting expandable hardware may
also be critical to future growth. For ease of management, deployments selection best practice is to
use the fewest possible servers.
Minimum Hardware
The minimum hardware specification describes the least of what Dell OpenManage Network
Manager needs. In such minimum installations, traffic flowing from the network to OpenManage
Network Manager may exceed the capacity of the hardware. When estimating the size of a
deployment, it is important to understand the applications configurations in the target
environment. For example, the most resource-intensive, demanding applications are typically
Traffic Flow Analyzer (TFA), Event Management and Performance Monitoring.
REQUIRED Minimum hardware
RPM Disk.
Supports
• Standalone installations (Single Server) are supported when you use high-resource demand
RECOMMENDED Minimum hardware:
Supports:
• Standalone installations
:
applications minimally.
GB 10,000 RPM Disk
—6GB RAM, dual core CPU, 3.0GHz or better, 200 GB 7200
8GB RAM, quad core CPU (3.0GHz or better), 400
12
Single Server Hardware | Getting Started with Dell OpenManage Network Manager
CAUTION:
The above assumes you have dedicated a host to OpenManage Network Manager alone. Other
applications may compete for ports or other resources and can impair the system’s performance.
Even OpenManage Essentials should not be on the same machine as Network Manager.
Sizing for Standalone Installations
The following are suggested sizing guidelines for your Dell OpenManage Network Manager system.
2
Operating System / Disks /
RAM / Hardware
64-bit OS with 6GB RAM
All below are 64-bit OS’s:
8GB RAM, single disk,
consumer level PC
12GB RAM, single disk,
business level PC
16GB RAM, multi-disk,
server level PC
32GB RAM, multi-disk,
server level PC,
recommend fast disk array
or SSD drive array for the
many database actions
Network Size Devices
Application Constraints
<5 Users <20 <2Mbs Internet egress and a
1:1000 sample rate
Single-site, less than 10
concurrent users
Single-site, less than 25
concurrent users.
Medium-large network,
up to 50 concurrent
<100 <2Mbs Internet egress and a
1:1000 sample rate
< 500 < 10Gbs Internet egress and
a sample rate of 1:1000
< 1,000 < 50Gbs Internet egress and
a sample rate of 1:1000
users
Large network, up to
100 concurrent users
< 2,000 < 200Gbs Internet egress
and a sample rate of 1:1000
3
Installation Changes to
Heap (RAM) Settings
Use defaults: (1 or 2GB
application server heap (32
v. 64-bit) 512M database
768M Synergy
3GB application server
heap, 2GB database, 1G
Synergy
4GB application server
heap, 3GB database, 3G
Synergy
5G application server heap,
4G database, 4.5G Synergy
10G application server
heap, 8G database, 9G
Synergy
4
,
1
Assumptions: Servers have at least four cores (3.0GHz or better) and are no more than four years old. As
memory and usage increases, the number of CPU cores needs to increase. Two cores can work for the
most basic installations, but such configurations are not recommended.
2
Each device mentioned here is equivalent to a L2 or L3 switch with a total of 48 interfaces per device
being monitored. For each device not being monitored for 48 interfaces, you can add another 50 devices
to the overall inventory for ICMP-only monitoring.
3
Application Constraints are most relevant to Traffic Flow Analysis, Performance Management, and
Event Management.
Traffic Flow Analysis ratings map to constant throughput divided by sample rate, as in bandwidth /
sample rate. 20G / 2000 is easier to manage than 20G / 1000. 20G / 1 is a thousand times more demanding
than 20G / 1000. Best practice is to avoid such high sample rates. The bandwidth the hardware your Dell
OpenManage Network Manager installation can support is dramatically lower in such cases. Best
Single Server Hardware | Getting Started with Dell OpenManage Network Manager
13
practice is to sample a maximum of one traffic flow for every 1000 (1:1000). Higher sampling rates
CAUTION:
NOTE:
degrade database performance and increase network traffic without adding any significant statistical
information.
Performance Management can support 600 inserts per second using a single disk (SSD) Drive. 1 insert =
1 monitored attribute. Expect better performance as you add more drives (and worse performance with
slower drives).
Event Management can support a sustained 1200 traps /sec using a single (SSD) drive. Expect better
performance as you add more drives (and worse performance with slower drives).
4
Database memory settings increase as the number of database hits increases. At the 32GB level best
practice is to use an SSD drive or fast disk array because of the large number of database actions
possible.
Java JVM problems can generate over 10GB of thread dump in case of a memory error. To solve the
problem of such files filling up your hard drive, delete the
5.1/bin
your hardware has enough RAM for the tasks it has been assigned. The Server Statistics portlet displays
performance information.
directory to free up the disk space. You can also clean out
*.hprof
files in the
temp
/oware/jboss-
directories. Finally, ensure
If the network you manage exceeds the parameters outlined above, or your system is balky and
unresponsive because, for one example, it monitors more devices than your hardware can handle,
consult your sales representative about upgrading to a more robust or multi-server version of Dell
OpenManage Network Manager. Also, see Performance and Monitors on page 291 for more about
tuning monitor performance. You can also monitor the application server itself. See Application
Server Statistics on page 295 and Self Management / Self Monitoring: Default Server Status
Monitor on page 313.
14
Tablets and iPads
Dell OpenManage Network Manager detects mobile devices and pads. For smaller screens, the
Navigation bar collapses to the left hand side and the page only displays a single column. Some
limits apply:
• Since touch devices do not support right click, the first time clicking on a row selects it. A
repeat click launches a menu displaying the available actions. Click the one you want.
• All major charts are rendered as HTML 5 which are mobile-friendly. These charts are Line,
Pie, Donut, Bar and Column. Some Gauges and LED charts require flash which is not
compatible with all mobile devices.
• Visualize / Topology is unavailable.
Apple products are most Dell OpenManage Network Manager-friendly. Android is only partly supported.
Single Server Hardware | Getting Started with Dell OpenManage Network Manager
Network Basics
NOTICE
OpenManage Network Manager 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 OpenManage Network Manager, 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.
One simple way to check connectivity from a Windows machine to a device is to open a command shell
cmd
with Start > Run
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.
. Then, type
Name Resolution
OpenManage Network Manager server requires 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
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
ping [device IP address]
on Windows (
/etc/hosts
at the command line. If the
in Linux). Here,
Protocols
OpenManage Network Manager uses the following protocols: TCP/IP, SNMP, HTTP/S, UDP
Multicast.
Overriding Properties
Dell OpenManage Network Manager lets you fine-tune various features of the application. Rather
than lose those changes if and when you upgrade your application, best practice is to override
changes. To do this for the web portal, first rename the provided file
Single Server Hardware | Getting Started with Dell OpenManage Network Manager
15
\oware\synergy\conf\server-overrides.properties.sample
overrides.properties
, and enable the properties within it by uncommenting them, and
to
server-
altering them to fit your needs. The comments in this file provide more information.
You can also override application server-related properties in
\owareapps\installprops\lib\installed.properties
.
Both of these properties files remain as configured if you install an upgrade, but upgrades overwrite
the
server-overrides.properties.sample
, so keep a copy if it has anything you want to
preserve.
Screen names
—A new property requires a minimum length for user screen names. For the existing
user base then any screen names that are shorter than the value must change to the required
length on the next edit/save for that user.
Fixed IP Address
OpenManage Network Manager 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.
If you do change your host’s IP address
1
Change the Virtual host IP to the new IP address in Manage > Control Panel > Portal.
2
Change the host IP address
3
Open a shell and run
4
Run
ipaddresschange -n
5
Restart the application server and the web server service.
6
Open a browser to see the web client at this URL:
To do this without the script:
1
Change the Virtual host IP to the new IP address in Manage > Control Panel > Portal.
2
Change the host IP address
3
Delete the contents of
4
Change your local IP address anywhere it appears in
\owareapps\installprops\lib\installed.properties
5
Change the address on your web server. Change this in
\oware\synergy\tomcat-7.0.40\webapps\ROOT\WEB-INF\classes
Change property:
oware
to set the environment
in the shell followed by the new IP address
\oware\temp
[new IP address]:8080.
.
.
portal-ext.properties
in
16
jdbc.default.url=jdbc:mysql://[IP address]/
lportal?useUnicode\=true&characterEncoding\=UTF8&useFastDateParsing\=false
and
Single Server Hardware | Getting Started with Dell OpenManage Network Manager
oware.appserver.ip=[IP address]
CAUTION:
6
Restart the application server and the web server service.
Open a browser to see the web client at this URL:
Memory Settings
To manually change Dell OpenManage Network Manager web portal heap settings, change the
setenv.sh
set "PORTAL_PERMGEN=256m"
set "PORTAL_MAX_MEM=3072m"
set "PORTAL_INIT_MEM=768m"
set "PORTAL_32BIT_MAX_MEM=768m"
These files are in the
re-start the portal service.
or
setenv.bat
Tomcat***/bin
file:
directory. After you change their settings, run them, then
[new IP address]:8080.
Portal
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, WMI login credentials, 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. See
Authentication on page 177 for more.
If you do not get access to the deepest level of authentications—for example the “enable” user’s—you
cannot access all of Dell OpenManage Network Manager’s functionality.
Device Drivers
For complete communication with devices, Dell OpenManage Network Manager requires a device
driver. For example, to communicate with Dell devices, you must have a Dell driver installed. That
does not mean you cannot discover and communicate with devices without a driver installed. The
Base Driver capabilities appear below. See .ocp and .ddp files on page 91 for driver installation
instructions. The following sections include discussions of these drivers:
• Base Driver
• Windows Management Instrumentation (WMI) Driver
• Web-Based Enterprise Management (WBEM) Driver
Device Drivers | Getting Started with Dell OpenManage Network Manager
17
Base Driver
NOTE:
If you have no driver installed, Dell OpenManage Network Manager still provides the following
functionality. This functionality depends on devices supporting and providing data from the system
group (sysDescr, sysObjectID, sysUpTime, sysContact, sysName, sysLocation) and the ifTable
which provides list of device interface entries from the RFC1213-MIB. Dell OpenManage Network
Manager also depends on the entPhysicalTable in the ENTITY-MIB which provides list of physical
entities contained on device.
If device does not support ENTITY-MIB then Dell OpenManage Network Manager bases sub-component
creation entirely on contents of the ifTable.
Top L ev e l Res our c e
discovered devices with the following attributes: Equipment Name, Description, IP Address,
Location, Contact, Vendor, Model, System Object Id, Date created, Creator, Discovery date,
Last Modified.
Subcomponents
interfaces, power supplies, fans, and so on) for discovered device based on contents of
entPhysicalTable.
Port / Interface Attributes
depending on port/interface type: Name, Port Description, MAC Address, Administrative
State, Operational State, Port Type, Speed, Encapsulation, Operation Type, Switch Mode,
CLI Name, If Index, Port Number, and Slot Number.
Direct Access
Monitors
Reports
Network View
Events
MIBs
Containers
Links
—Discovered device instances are automatically added to the Default ICMP Monitor for
updating its Network Status. Support for SNMP based performance monitors using
discovered ports and interfaces as targets. For example, Bandwidth Utilization.
—You can execute reports like the Port Inventory Report or Device Inventory and results
should include discovered device and device port entities.
—Dell OpenManage Network Manager supports standard MIB-II traps for discovered
device and or sub-components. For example, linkUp, linkDown, coldStart, warmStart, and so
on.
—Dell OpenManage Network Manager can import MIBs for use within MIB Browser so you
can query device-specific OID values on the discovered device.
—Depending on the licensing, device and or contained sub-components are selectable
and manageable in filters and portlets like Containers.
—You can manually create Links using discovered device or device subcomponents as end
points which are then visible in Network View.
—Dell OpenManage Network Manager creates top level resource for
—Dell OpenManage Network Manager creates subcomponents (modules, ports,
—Dell OpenManage Network Manager sets Port/Interface Attributes
—SNMP and Ping (ICMP) are enabled.
—Discovered devices and their sub-components appear.
18
Device Drivers | Getting Started with Dell OpenManage Network Manager
Attributes
NOTE:
—You can manually populate or modify device/port attributes. For example Serial
Number, Firmware Version, Port Type, Notes etc. Attribute values should then be included in
reports based on a given report template.
Supported PowerConnect Models
Refer to release notes for a list of supported devices. You can also look at the HTML files in the
SupportedDevices directory of your installation source for information about supported devices
and operating systems.
Windows Management Instrumentation (WMI) Driver
The Windows Management driver currently supports any Windows based operating system that
supports the Windows Management Instrumentation (WMI).
Windows Management must always install on the Vista (Business) or later.
The login credentials must be for an administrator on the installation host for complete
functionality. Both this and .NET installation are requirements for any installation managing
devices supported by this driver.
This driver supports global group operations.
Discovery may display benign retry warning messages in the application server shell or log. You can
safely ignore these.
Prerequisites
Before installing this software to manage other computers with a Windows Management Interface
driver (assuming you are installing that driver), if you do not already have it installed, you must
download and install the Microsoft .Net framework version 3.0 or later on the application server.
For complete functionality, the WMI login for this software must be a login for a domain user who
also belongs to the administrator group on the WMI device. Both are requirements for any
installation managing WMI devices.
The following are common Windows Base prerequisites:
Credentials
Firewall
License
—You must use administrative credentials to manage the computer system.
— Some firewalls installed on the computer may block Windows Management requests.
Allow those you want to manage. (See Firewall Issues below.)
—Make sure you have the proper Windows Base driver license installed. If you have a Dellonly license and are discovering a non-Dell computer, discovery does not work. Or if you have
a Dell license for desktop discover you cannot discover a server.
License come in the following types:
Device Drivers | Getting Started with Dell OpenManage Network Manager
19
• Major Vendor by Name—For example: Dell, Compaq, HP, Gateway
NOTE:
• Server/Desktop individual license support
• Generic computers—Non-major vendors
• ALL—This gives the driver all capabilities for any computer system
Firewall Issues
Configure the firewall between your server and the Internet as follows:
• Deny all incoming traffic from the Internet to your server.
• Permit incoming traffic from all clients to TCP port 135 (and UDP port 135, if necessary) on
your server.
• Open Port 445 (WMI)
• Permit incoming traffic from all clients to the TCP ports (and UDP ports, if necessary) on
your server in the Ports range(s) specified above.
• If you are using callbacks, permit incoming traffic on all ports where the TCP connection was
initiated by your server.”
WMI queries will succeed only if you add the User account to local admin group. Refer to the
Microsoft knowledgebase articles for the way to do this. For example: Leverage Group Policies with
WMI Filters:
For user rights for WMI access, see:
See also:
(
support.microsoft.com/kb/832017/
support.microsoft.com/kb/555253/en-us
www.mcse.ms/archive68-2005541196.html
Service overview and network port requirements for the Windows Server system
)
20
Web-Based Enterprise Management (WBEM) Driver
The Web-Based Enterprise Management driver currently supports operating systems supporting
the Web-Based Enterprise Management interface (WBEM).
WBEM is always installed on the following operating systems versions (and later):
•Red Hat Linux 6.2.
• VM Ware (ESX) with WBEM installed.
You can install Web-Based Enterprise Management on some other systems if they do not already
use it, but monitored devices must have this installed.
To verify WBEM is running on your system, run the following command:
should see a process labelled
Device Drivers | Getting Started with Dell OpenManage Network Manager
cimserver
.
ps-e | grep cim
. You
Installing WBEM on Red Hat
NOTE:
You can download and install WBEM support for Red Hat linux. For example, for Red Hat 5, a
release for WBEM is
tog-pegasus-2.7.0-2.el5_2.1.i386.rpm
. This is what you need to
download once you have logged into the Red Hat network.
Install this as follows:
Install:
rpm -ih tog-pegasus-2.7.0-2.el5_2.1.i386.rpm
Upgrade:
To determine if wbem is running, run
rpm -Uh tog-pegasus-2.7.0-2.el5_2.1.i386.rpm
ps -ef | grep cimserver
in a shell.
To start | stop | get status of the WBEM service:
tog-pegasus start | stop | status"
If the system is running Fedora, then you can access tog-pegasus updates at this site:
https://
admin.fedoraproject.org/pkgdb/packages/name/tog-pegasus
WBEM Prerequisites
The following are common prerequisites:
Credentials
—WBEM credentials have a role in discovering the device. Your system must have
access to the computer using Administrative only credentials. These are the same credentials
as the user installing WBEM on the device.
Telnet / SSH credentials are necessary for other supported applications.
For full functionality, this WBEM device driver requires administrative (root) access. Many
devices may only allow root logins on a local console.
In such cases, configure the Telnet/SSH authentication for these devices to login as a nonroot user—and, in Authentication Manager, enter
the root user’s password in
Enable User Password
su
in the
Enable User ID
field and enter
in that same authentication. This enables
full device management functionality with root access.
Credentials for Telnet / SSH should have a privilege level sufficient to stop services and to restart the
computer system.
Firewall
— Some firewalls installed on the computer may block Web-Based Enterprise
Management requests. Allow those you want to manage.
License
—Make sure you have the correct WBEM driver license installed. Licenses come in the
following types:
• Major Vendor by Name - Such as Dell, Compaq, HP, Gateway.
• Server/Desktop individual license support.
• Generic computers - non-major vendors.
Device Drivers | Getting Started with Dell OpenManage Network Manager
21
• ALL - this gives the driver all capabilities for any computer system.
CAUTION:
NOTE:
If you discover an Amigopod host that does not have its SNMP agent turned on, Dell OpenManage
Network Manager labels it a WMI or WBEM host rather than an Amigopod host.
Secure WBEM Access
Some monitoring capabilities require root access, even if you securely log into the UNIX host. In
this case, when configuring a secure (SSH) login, configure a telnet authentication with
Enable User ID
configure authentication as an HTTP/HTTPS login / password, and select WBEM as the protocol
after you have selected the WBEM authentication.
, and the root user’s password as the
Enable Password.
For other WBEM access,
su
as an
Ports Used
Initial installation scans the following ports, and reports any conflicts for the following ports:
Database:
Application server:
Web Portal:
SNMP:
Syslog:
When installation encounters a conflict with any of the above ports, a panel appears displaying a
warning and the ports in conflict. You can then elect to continue since you can change the
application ports after installation. If your installation has no port conflicts, then no panel appears.
3306 or user-configured database host, if using MySQL server.
8089, 8162, 8489 [HTTPS], 8082
8080, 8443 [HTTPS]
161, 162
514
22
The installation scans TCP ports to detect potential conflicts. It does not scan UDP port conflicts
including SNMP Ports 161 and 162. No SNMP or other applications should bind to UDP ports 161 and 162
since such bindings interfere with the application. If this conflict exists, the following error appears:
FATAL ERROR - Initializing SNMP Trap Listener
You may also sometimes configure port availability on firewalls. Sometimes, excluding applications
from firewall interference is all that is required (see Ports and Application To Exclude from Firewall
on page 27).
Ports Used | Getting Started with Dell OpenManage Network Manager
Loading...