Dell OpenManage Network Manager version 5.2
Web Client Guide
Notes, and Cautions
A NOTE indicates important information that helps you make better use of your computer or software. A CAUTION indicates potential harm to your data or hardware if you proceed as indicated.
____________________
Information in this document is subject to change without notice. © 2010-2012 Dell Inc. All rights reserved.
Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Trademarks used in this text: Dell™, the DELL logo, PowerEdge™, PowerVault™, PowerConnect™, OpenManage™, EqualLogic™, KACE™, FlexAddress™ and Vostro™ are trademarks of Dell Inc. Microsoft®, Windows®, Windows Server®, MS-DOS® and Windows Vista® are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat Enterprise Linux® and Enterprise Linux® are registered trademarks of Red Hat, Inc. in the United States and/or other countries.
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.
1 Preface . . . .9
Why Dell OpenManage Network Manager?. . . 9
Key Features. . . 9
Networks with Dell OpenManage Network Manager. . . . 11
Additional Products . . . . 11
Online Help / Filter . . . . 12
How to: Use “How To” . . . 12
Feedback. . . 13
A Note About Performance . . . 13
2 Getting Started with Dell OpenManage Network Manager .15
Overview . . . 15System Basics . . . . 15
Single Server Sizing . . . 20
Sizing for Standalone Installations. . . 21
Network Basics . . . . 22
Authentication . . . . 24
Supported PowerConnect Models . . . . 24
Windows Management Interface. . . . 24
Getting Started . . . 27
Installation and Startup . . . 28
How to: Set Linux Permissions . . . 31
Perl. . . . 32
Starting Web Client. . . . 32
Control Panel . . . 33
Search Indexes. . . . 34
[My Account]. . . . 34
RCSynergy / [Domain] . . . . 35
Portal > Users and Organizations. . . . 35
How to: Add Users and connect them to Roles . . . 36
How to: Configure Organizations . . . 38
Public / Private Page Behavior. . . . 40
How to: Add and Configure User Roles / Permissions . . . 40
Portal > Roles . . . . 41
Portal > Portal Settings. . . . 41
Portal > [Other]. . . . 42
Redcell > Permission Manager. . . . 42
Redcell > Data Configuration. . . . 45
Redcell > Mediation . . . . 45
Redcell > Filter Management. . . . 48
Contents
How to: DAP Workflow . . . 51
Aging Policies Editor. . . . 52
Aging Policies Options . . . . 54
Sub-Policies . . . . 55
Repositories . . . . 57
Portlet Level Permissions. . . . 58
How to: Configure Portlet Permissions . . . 59
How to: Configure Resource Level Permissions . . . 59
Quick Navigation . . . 62
License Viewer. . . 63
How to: Register a License . . . 64
Discovery Profiles . . . 65
How to: Discover Your Network . . . 65
Managed Resources. . . 67
Common Setup Tasks . . . 68
SMTP Configuration . . . . 68
Netrestore File Servers. . . . 70
3 Portal Conventions . . . .71
Portal Overview . . . 71
Tooltips. . . . 72
Refresh. . . . 72
The Back Button . . . . 72
Show Versions. . . . 72
The Dock . . . 73
Status Bar Alerts . . . 75
Chat / Conferencing . . . . 76 Menu Bar . . . . 77 Site Map. . . . 77 Graphs. . . . 77 Portlets. . . . 78 Expanded Portlets . . . . 82
How to: Show / Hide / Reorder Columns . . . 84
How to: Filter Expanded Portlet Displays . . . 85
Common Menu Items . . . 86
Import / Export . . . . 86
Sharing. . . . 87
How to: Share a Resource . . . 88
Edit Custom Attributes . . . . 89
View as PDF . . . . 90
Tag. . . . 90
Audit Trail / Jobs Screen . . . 91
Audit Trail Portlet. . . 93
Schedules . . . 95
Schedules Portlet . . . . 95
4 Key Portlets . . . .99
Overview of Key Portlets . . . 99
Alarms . . . 100
Expanded Alarm Portlet . . . 102
Event History. . . 106
Event Processing Rules . . . 108
How to: Create Event Processing Rules . . . 109
Rule Editor . . . 111
Event Definitions . . . 128
Event Definition Editor . . . 128
Contacts . . . 133 Locations. . . 135 Tag. . . 138 Vendors . . . 139
5 Resource Management . . . .143
Introduction . . . 143 Authentication . . . 143 Container Manager . . . 146Container Manager Expanded . . . 146
Container View. . . 147
How to: Use Containers . . . 147
Container Editor . . . 148
Map Context . . . 151
Resource Discovery . . . 152
How to: Discover Resources . . . 152
Discovery Profiles . . . 153
Discovery Profile Editor. . . 154
How to: Edit Discovery Profiles . . . 154
Managed Resource Groups. . . 162
Static Group . . . 164 Dynamic Group. . . 165 Managed Resources. . . 166 New Link. . . 175 Link Discovery . . . 176 Equipment Details . . . 178 Performance Indicators . . . 179 Interfaces 180
Details . . . 185
How to: Schedule Actions . . . 186
Direct Access. . . 188 MIB Browser. . . 188 Terminal . . . 190 Ping (ICMP) . . . 191 HTTP / HTTPS . . . 191 Ports. . . 191 Port Editor . . . 194 Report Templates. . . 195
How to: Create a Report Template . . . 195
Report Template Editors . . . 196
Reports . . . 200
How to: Generate a Report . . . 204
Report Editor. . . 204
Branding Reports. . . 206
6 Visualize . . . .207
Visualize My Network. . . 207
How to: Create a Visualization . . . 207
Configuring Views . . . 208
Control and Styles . . . 210
Data / Node Finder. . . 213
Layout . . . 216
OVERVIEW. . . 219
Alarms in Visualizations / Topologies. . . 219
Links in Visualization . . . 220
7 File Server / File Management . . . .221
File Servers . . . 221
File Server Editor. . . 222
File Management. . . 223
How to: Backup Configurations . . . 225
How to: Restore Configurations . . . 227
Configuration Files . . . 229
Image Repository. . . 233
Firmware Image Editor. . . 235
Configuration Image Editor. . . 236
Deploy Firmware . . . 238
How to: Deploy Firmware . . . 239
Deploy Configuration. . . 240 How to: Restore a single configuration to many target devices . 241
8 Monitoring . . . .243
How to’s. . . 243
OpenManage Network Manager Server Statistics. . . 244
Resource Monitors . . . 245
Retention Policies . . . 248
Monitor Editor . . . 251
How to: Create an SNMP Interface Monitor . . . 262
How to: Create an ICMP Monitor . . . 263
How to: Create a Key Metrics Monitor . . . 264
How to: Create a Monitor Report . . . 265
Monitor Options Type-Specific Panels . . . 266
Scheduling Refresh Monitor Targets . . . 276
Top [Asset] Monitors. . . 276
Top Configuration Backups. . . 277
Dashboard Views. . . 277
How to: Create a Simple Dashboard View . . . 279
Performance Dashboard. . . 279
Dashboard Editor. . . 281
How to: Create a Custom Dashboard View . . . 282
Show Performance Templates . . . 286
How to: Create A Performance Template . . . 286
Key Metric Editor. . . 289
9 Traffic Flow Analyzer . . . .293
How does it work?. . . 293
Setup. . . 294
How to: Use Traffic Flow Analyzer . . . 294
Exporter Registration. . . 295
Traffic Flow Portlet . . . 295
Drill Down . . . 298
Search. . . 300
Traffic Flow Analyzer - Example . . . 300
10 Change Management / ProScan . . . .303
Introducing ProScan and Change Management . . . 303
How to: Use ProScan / Change Management . . . 303
How to: Configure ProScan Groups . . . 304
How to: Do Change Management (Example) . . . 305
ProScan Portlet . . . 306
Compliance Policy Summary. . . 308
Change Determination Process . . . 326
Change Determination Process Workflow . . . 327
How to: Run Change Determination . . . 329
Change Determination Defaults. . . 329
Compliance and Change Reporting . . . 329
How to: Report on Change Determination . . . 331
11 Actions and Adaptive CLI . . . .333
Introducing Actions and Adaptive CLI . . . 333
Using Adaptive CLI. . . 334
Actions Portlet . . . 335
Adaptive CLI Editor. . . 340
General. . . 341 Attributes. . . 342 Scripts. . . 347 Comparison . . . 352 External Commands. . . 352 Seeded Scripts. . . 354
How to: Create a Monitor for an External Script . . . 356
Adaptive CLI Script Language Syntax . . . 358
Attributes. . . 358
Conditional Blocks . . . 359
Perl Scripts . . . 360
How to: Create Adaptive CLI Example . . . 361
Scheduling Actions. . . 361
Active Performance Monitor Support . . . 363
Adaptive CLI Records Archiving Policy . . . 365
Glossary. . . 367
Preface
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 Administration Section describes security and some of the runtime features supporting these applications. The OpenManage Network Manager
Administration Section of the User Guide and Administration Section discuss licensing. Consult Release Notes for information about changes not covered in this Synergy User Guide.
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.
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.
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.
Reports and Graphs
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 Visualize (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 Visualize topology view to access configuration and actions. The color of the icon in this view indicates the highest severity alarm on the device or its sub-components. For example, red indicates a Critical alarm.
Displays include right-click access to the Details screen (see Equipment Details on page 178), 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 Backup Configurations on page 225) and restore previously backed up files (see Restore Configurations on page 227). 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, 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. The Managed Resources portlet can display the anatomy of a Resource with its right-click actions (see Equipment Details on page 178). 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 Audit Trail Portlets track message traffic between Dell OpenManage Network Manager and devices.
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
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 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
63 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. (see Installation and Startup on page 28). 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 Help in the The Dock at the top of the screen. Help appropriate to each portlet appears when you click question mark icon on the portlet title bar. By default, this opens a separate browser window which is not necessarily always in front of the 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 Show button to display the contents, index and search tabs (Hide conceals them again), and the Prev / Next buttons, or clicking table of contents topics moves to different topics within the helpset.
Tip
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.
How To:
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 How to section of the Index.
Feedback
To provide your input about this software click the Feedback link in the lower left corner of the Dell OpenManage Network Manager screen. Provide your contact information, enter Questions, Likes,
New Ideas, or a Problem, in the screen that appears next, then click Send.
Dorado Software responds, and often uses customer suggestions in future versions of the software.
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 Administration Section of the User Guide and Administration Sections), and limit device queries with filters, but device and network latency limit how quickly your system can respond.
Tip
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.
1
Getting Started with Dell OpenManage
Network Manager
Overview
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 Administration Section of the User Guide, Synergy User Guide, Administration Section and User Guide) or the online help.
Tip
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 27.
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
The section Server on page 49 describes how to set up some of these features.
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:
• Upgrading requires a new license to activate new features.
• Performance capabilities have been completely reconfigured. When upgrading from previous versions, you must (re-)create dashboards from scratch.
• The following require manual migration (export, then import) from previous versions: SMTP settings. Some scheduled items.
• You must re-create topologies as Visualizations. (suggestion: take a screenshot) • Group Operations have been deprecated, replaced by Adaptive CLIs.
• Command monitors must be recreated, and monitors must be re-configured to monitor Adaptive CLIs that run external scripts.
• User Names / Passwords, and User Groups (Roles) are not automatically reassigned and must be created manually.
Supported Operating System Versions
The following are supported operating system versions:
Microsoft Windows—The supported operating systems are: Windows 2003 (Standard,Enterprise
and Web) and Windows Server 2008 (including R2 and Enterprise Edition). This is a 64-bit application, it has been tested for Windows on 64-bit operating system versions.
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 Windows Server 2008.
• Installer may halt when pre-existing bash sessions or cmd sessions are left open. Close all such sessions.
Linux—This application supports Red Hat (Enterprise version 5.5 or 6.0) Linux, 64-bit only. (See
32-bit Linux Libraries on page 18 for additional requirements)
CAUTION:
For Linux, you must install no more than a single instance of MySQL®—the one installed with this software. Before you install, remove any MySQL if it exists on your Linux machine.
Linux Installation Best Practices
How you install Linux has an impact on Dell OpenManage Network Manager’s installation. Here are some tested best practices:
• You can install Linux in its Desktop option, or if you select Basic Server (default) - choose additional packages: XWindows, Basic / Core Gnome Desktop without Gnome utilities, although we suspect any Gnome will work).
• Turn off SE Linux in /etc/selinux/config. Change SELINUX=disabled. This typically requires a reboot.
• You must install compatibility library from installation media (so it is compatible with installation)
compat-libstdc++-33.x86_64 3.2.3-69.el6 @InstallMedia.
Also: verify that /etc/hosts points to new name-use the following command and you should see similar output.
[qa@rh6Test Desktop]$ cat /etc/hosts
10.18.0.241rh6Test.localrh6Test# Added by NetworkManager 127.0.0.1localhost.localdomainlocalhost
::1 rh6Test.localrh6Testlocalhost6.localdomain6localhost6 Upgrading on Linux
The following are best practices for upgrading from a previous OpenManage Network Manager version on a Linux machine:
1 Make sure Red Hat is not installed with a MySql database option (or remove the Linux MySql
first).
2 Ensure you have installed the 32-bit Linux Libraries, as described below.
3 Verify your previous version’s installation application server starts without excpetions
4 Back up the database, and any other resources that need manual installation. Consult Release
notes for a list of these.
5 Proceed with the upgrade. Disable Firewalls
System->Administration->Firewall - You may be prompted to enter the root password; the password dialog may be hidden behind the Firewall Configuration Startup dialog.
Directories and Permissions
Create the directory for the installation:
mkdir /opt/
chown [your login name] /opt/[your installation directory] chmod 775 /opt/[your installation directory]
NOTE:
[your login name] is the original non-root user available when you imported the machine. Replace [your login name] with whichever user you are logged in as or will be installing as.
You may need to change the permissions on the installer in our package in order to give it execute rights. If you have used the shared folder method from above, you can give the Linux installer rights as follows:
chmod uga+x /[Install Media Path]/install/linux_install
Make sure that there is no other my.cnf file under the /etc directory. If there is, do the following:
mv /etc/my.cnf /etc/my.cnf.original 32-bit Linux Libraries
For Red Hat Enterprise 64 bit installations, you must identify the appropriate package containing 32-bit libtcl8.4.so (for the example below: tcl-8.4.13-3.fc6.i386.rpm for Red Hat).
NOTE:
Do not use any x86_x64 rpms; these would not install the 32-bit libraries.
Any 32-bit tcl rpm that is of version 8.4 and provides libtcl8.4.so works. You can download them from Sourceforge: http://sourceforge.net. Download these, then issue the command:
rpm -ivh --force tcl-8.4.13-3.fc6.i386.rpm
This forces the installation of the 32-bit libraries on a 64-bit system. Ensure that your expect executable in your installation directory is properly linked by issuing the following commands:
[someone@RHEL5-64bit ~]$ which expect
/opt/dorado/oware3rd/expect/linux/bin/expect [someone@RHEL5-64bit ~]$ ldd /opt/dorado/oware3rd/expect/linux/bin/expect linux-gate.so.1 => (0xffffe000) libexpect5.38.so => /opt/dorado/oware3rd/expect/linux/bin/ libexpect5.38.so (0xf7fd2000) libtcl8.4.so => /usr/lib/libtcl8.4.so (0x0094c000) libdl.so.2 => /lib/libdl.so.2 (0x0033e000)
libm.so.6 => /lib/libm.so.6 (0x00315000) libutil.so.1 => /lib/libutil.so.1 (0x00b8d000) libc.so.6 => /lib/libc.so.6 (0x001ba000) /lib/ld-linux.so.2 (0x0019d000)
Make sure that libtcl8.4.so maps to /lib/libtcl8.4.so An Alternative for Red Hat Linux:
1 Copy /usr/lib/libtcl8.4.so from a 32-bit RH system to /usr/local/lib/32bit
on your 64-bit Red Hat system
2 As root, execute: ln –s /usr/local/lib/32bit/libtcl8.4.so /usr/lib/
libtcl8.4.so
Supported Web Browsers
Supported web browsers include: • Chrome (v 6 and above) • Safari (v 5 and above) • Firefox (v 3.6 and above)
• Internet Explorer (v 9 and above)
Screen resolution should equal or exceed 1280 x N 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.
NOTE:
Internet Explorer versions 8 and older display alignment issues, have slower JavaScript and Flash processing, and some transparencies do not work. Other anomalies include non-rounded 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 at http:// code.google.com/chrome/chromeframe/. After it installs, close IE and re-open it. The look and feel should improve.
Tip
You can often resolve problems by refreshing the browser’s display.
CAUTION:
Opening Dell OpenManage Network Manager, or links originating within it in multiple tabs on multi-tab browsers is not supported. To see “multiple” screens, configure Dell OpenManage Network Manager’s Menu Bar.
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.
NOTE:
If Flash is installed, but the screen still requests 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.
Single Server Sizing
The following describes hardware and sizing configuration for common Dell OpenManage Network Manager deployments. Before any deployment, administrators should review and understand the different deployment options and requirements. Consider future growth of the network when estimating hardware sizing. You can generally 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. Standalone (single server) deployment offer the simplest and easiest management solution. Where high availability (HA) is required, you can produce the simplest deployment with as few as two servers.
Minimum Hardware
The minimum hardware specification describes what Dell OpenManage Network Manager needs at a minimum. 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. Applications that are typically the most demanding of resources are Traffic Flow Analyzer (TFA), Event Management and Performance Monitoring.
REQUIRED Minimum hardware—6GB RAM, dual core CPU, 200 GB 7200 RPM Disk. Supports:
• Standalone installations (Single Server) is supported when high-resource demand applications are used minimally.
RECOMMENDED Minimum hardware: 8GB RAM, quad core CPU, 400 GB 10,000 RPM Disk Supports:
Sizing for Standalone Installations
The following are suggested sizing guidelines for your Dell OpenManage Network Manager system.
1 Assumptions: Servers have at least four cores and are no more than four years old. As memory and
usage increases, the number of CPU cores increase. Two cores can work for the most basic installations, but are not recommended.
2 Each device is equivalent to a L2 or L3 switch with a total of 48 interfaces per device being monitored.
For each of devices not being monitored for 48 interfaces, one can add another 50 devices to the overall inventory for ICMP-only monitoring.
3 Application Constraints are most relevent to Traffic Flow Analysis, Peformance 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
Operating System / Disks /
RAM / Hardware Network Size Devices
2 Application Constraints3 Installation Changes to
Heap (RAM) Settings
64-bit OS with 6GB RAM or 32-bit OS with 4GB RAM
All below are 64-bit OS’s:
<5 Users <20 <2Mbs Internet egress and a
1:1000 sample rate Use defaults: (1 or 2GB application server heap (32 v. 64-bit) 512M database4,
768M Synergy 8GB RAM, single disk,
consumer level PC Single-site, less than 10 concurrent users <100 <2Mbs Internet egress and a 1:1000 sample rate 3GB application server heap, 2GB database, 1G Synergy
12GB RAM, single disk,
business level PC Single-site, less than 25 concurrent users. < 500 < 10Gbs Internet egress and a sample rate of 1:1000 4GB application server heap, 3GB database, 3G Synergy
16GB RAM, multi-disk,
server level PC Medium-large network, up to 50 concurrent users
< 1,000 < 50Gbs Internet egress and
a sample rate of 1:1000 5G application server heap, 4G database, 4.5G Synergy 32GB RAM, multi-disk,
server level PC,
recommend fast disk array or SSD drive array for the many database actions
Large network, up to
100 concurrent users < 2,000 < 200Gbs Internet egress and a sample rate of 1:1000 10G application server heap, 8G database, 9G Synergy
practice is to sample a maximum of one traffic flow for every 1000 (1:1000). Higher sampling rates 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.
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 32 for more information about using web access to this software.
64-bit
Since Dell OpenManage Network Manager has a web server, demands on 32-bit system resources are near their limits. A standalone 32-bit system with Application server, Web server, and database requires nearly all addressable memory, and is therefore not supported. Applications like Traffic Flow Analyzer and Performance Monitoring require even more memory. For these reasons, and for future scalability, do not install the this software on 32-bit systems.
Tablets, phones 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. • Charts that require flash may not work (some have HTML5 backup).
• Visualize / Topology is unavailable. • Phones may limit views further
Network Basics
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.
Tip
One simple way to check connectivity from a Windows machine to a device is to open a command shell with Start > Run cmd. Then, type ping [device IP address] at the command line. If the
device responds, it is connected to the network. If not, consult your network administrator to correct this. No useful information comes from disconnected or powered-down devices.
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 on Windows (/etc/hosts in Linux). Here, you must assign a hostname in addition to an IP address somewhere in the system. Here are some example hosts file contents (including two commented lines where you would have to remove the # sign to make them effective):
# 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost
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, first change the provided file \oware\synergy\conf\server-overrides.properties.sample to server-overrides.properties, and enable the properties within it by uncommenting them, and altering them to fit your needs. The comments in this file provide more information.
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
To accommodate a changed IP address, first delete the contents of \oware\temp. Change your local IP address anywhere it appears in
\owareapps\installprops\lib\installed.properties. Then restart your machine. Alternatively, in a shell, after running oware to set the environment, you can run
ipaddresschange -n followed by the new IP address.
NOTE:
If you change your host’s IP address, you must also change the Virtual host IP to the new IP address in Manage > Control Panel > Portal.
If you do change your server’s IP address, you must also change the URL for web client access in your browser.
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 143 for more.
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 Interface
The Windows Management driver currently supports any Windows based operating system that supports the Windows Management Interface (WMI).
Windows Management is always installed on the following operating systems (or later): • Windows XP Professional (with a browser other than Internet Explorer)
• Windows 2003 All Editions • Windows Vista
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.
NOTE:
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—You must use administrative credentials to manage the computer system.
Firewall— Some firewalls installed on the computer may block Windows Management requests.
Allow those you want to manage. (See Firewall Issues below.)
License—Make sure you have the proper Windows Base driver license installed. If you have a
Dell-only 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:
• Major Vendor by Name—For example: Dell, Compaq, HP, Gateway • 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.
• 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: support.microsoft.com/kb/555253/en-us
For user rights for WMI access, see: www.mcse.ms/archive68-2005541196.html
See also: Service overview and network port requirements for the Windows Server system (support.microsoft.com/kb/832017/)
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 5.5 or 6.0
• 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.
NOTE:
To verify WBEM is running on your system, run the following command: ps-e | grep cim. You
should see a process labelled cimserver.
Installing WBEM on Red Hat
For Red Hat 5, the latest supported release for WBEM is
tog-pegasus-2.7.0-2.el5_2.1.i386.rpm and 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: rpm -Uh tog-pegasus-2.7.0-2.el5_2.1.i386.rpm
To determine if wbem is running, run 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 non-root user—and, in Authentication Manager, enter su in the Enable User ID field and enter the root user’s password in Enable User Password in that same authentication. This enables full device management functionality with root access.
NOTE:
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.
• ALL - this gives the driver all capabilities for any computer system.
CAUTION:
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.
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 OpenManage Network Manager User Guide or online help.
Installation and Startup below includes instructions for a basic installation. If you have a large
network, or anticipate a large number of web clients, then best practice is to install Dell OpenManage Network Manager as the Administration Section of the User Guide guide instructs.
Administering User Permissions—You can also set up users, device access passwords, and groups
for users, as you begin to use it. See Control Panel on page 33.
Discovering Resources—After you install the application, you must discover the equipment you
want to manage, and model it in the Dell OpenManage Network Manager database. See Discovery Profiles on page 65.
Resource Management—See Managed Resources on page 67, and Chapter 4, Resource
Management in this Guide.
Configuration Management—Use Dell OpenManage Network Manager to backup, restore, and
compare configuration files. See Top Configuration Backups on page 277.
Problem Diagnosis—See Alarms on page 100 for information about Fault Management. Network Troubleshooting—See Alarms on page 100, and Chapter 7, Monitoring for details of
Dell OpenManage Network Manager’s performance management capabilities.
Reports—Run reports to clarify the state of your network and devices. See Reports on page 200 for
details.
Real-time Diagnosis thru Collaboration—Collaborate with others about network issues, both by
sending them messages that display the device conditions of concern, and with online chat within Dell OpenManage Network Manager. See Sharing on page 87, and Status Bar Alerts on page 75 for details.
Unified View—You can scale your Dell OpenManage Network Manager installation to handle the
largest, most complex environments with distributed deployment. Consult the
Administration Section of the User Guide for more about installing distributed, and even high availability systems.
Finally do not neglect what Common Setup Tasks on page 68 describes.
Installation and Startup
Application server produces the Dell OpenManage Network Manager information for web clients. It monitors devices, and produces the output which the web server then makes available for those web clients. See Linux Prerequisites on page 30 for advice about installing to Linux.
Initiate installation by executing win_install.exe (Windows) or linux_install (Linux). Click through the installation wizard, accepting the license and making the appropriate entries. During some installations, one screen lets you select the application’s memory size. Best practice is to select the largest available on your hardware while leaving sufficient memory for the operating system.
Heap
Memory on a single machine installation serves the operating system, database and web server. You can configure the selected application server heap memory size any time, with the following properties in \owareapps\installprops\lib\installed.properties:
oware.server.min.heap.size=8192m oware.server.max.heap.size=8192m
To manually change Dell OpenManage Network Manager web portal heap settings, change the setenv.sh file:
JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=UTF8 -Xmx1024m -XX:MaxPermSize=256m"
The file is in /opt/dorado/oware/synergy/tomcat-x.x.x/bin . Add the export directive in front of the line and change the -Xmx[max memory] setting as appropriate. For example, for 8G:
export JAVA_OPTS="$JAVA_OPTS Dfile.encoding=UTF8 Xmx8192m -XX:MaxPermSize=256m"
CAUTION:
To manage Windows systems—in single server deployments, you must install this application on a Windows host. In distributed deployments, a mediation server that supports WMI must communicate to managed Windows systems.
Windows installation also installs Internet Information Services (IIS)—formerly called Internet Information Server. That installation does not turn IIS on by default. Do not enable IIS on the host(s) running Dell OpenManage Network Manager.
Also: Do not install if you are logged in as user “admin.”
Installation and startup include:
• Running the installer, responding to its prompts.
• Starting application server. In Windows, you can use the Start button (Start >
OpenManage Network Manager > Start application server), or type startappserver in a command shell, or right-click the server manager tray icon and select Start (if you have installed Dell OpenManage Network Manager as a service and that icon is red, not green). • Starting web server. If this does not auto-start, you can use the Start button (Start >
OpenManage Network Manager > Synergy Manager), or right click the web server’s tray icon to start it. You can also double-click this icon and automate web server startup.
On Linux start (or stop) the web server with scripts startportal.sh start (or startportal.sh stop) located in the oware/synergy/tomcat-x.x.x/bin directory.
• Starting the Client. The client provides the user interface. In Windows, click Start > OpenManage Network Manager > Synergy, or after starting the web server, open a browser and go to the web address hostname:8080 where hostname is the name of the machine running application server (or it’s IP address). See Starting Web Client on page 32 for more information.
CAUTION:
If you are using Dell OpenManage Network Manager in an environment with a firewall, ports 8080 and 80 must be open for it to function correctly. If you want to use cut-thru outside of your network then ports 8082 – 8089 must be open. Dell OpenManage Network Manager uses the first one available, so typically 8082, but if another application uses 8082, Dell OpenManage Network Manager uses 8083 and so on.
• Start using Dell OpenManage Network Manager as outlined in Getting Started on page 27, or below.
See the Troubleshooting chapter of the Administration Section of the User Guide to solve Dell OpenManage Network Manager problems.
Linux Prerequisites
If you are installing on Linux, you must log in as a non-root user. Linux installation prompts you to run some additional scripts as root.
When installing to Linux, ensure you are installing as a user with the correct permissions, and are in the correct group. You must configure the installation directory so this user and group have all permissions (770, at least). You may install without any universal (“world”) permissions. However, you must create a home directory for the installing user.
NOTE:
All files created during installation respect a umask of 007. All files from setup.jar are 770. Files from ocpinstall -x are set for 660. Bin scripts from ocpinstall -x are 770.
Best practice is to install as the user designated as DBA and admin of the system (not root user). If necessary, create the appropriate user and login as this user for running the install program. The installing user must have create privileges for the target directory. By default, this directory is / dell/openmanage/networkmanager.
CAUTION:
Linux sometimes installs a MySQL database with the operating system. Before you install this application, remove any MySQL if it exists on your Linux machine.
NOTE:
To set the environment correctly for command line functions, after installation, type oware (or . / etc/.dsienv in UNIX—[dot][space]/etc/[dot]dsienv) before running the specified command.
Also: This application can run on any Linux desktop environment (CDE, KDE, Gnome, and so on) but the installer will only install shortcuts for CDE.
File Handles
Best practice is to modify file handles for Linux. If you do not do this, exceptions appear in application server log every fifth minute. To prevent this, alter /etc/security/
limits.conf. Here, administrators can set hard and soft limits for the file handles for users and user groups. These settings take effect on reboot. Best practice is to set the following for
OpenManage Network Manager on a single machine:
<Installing User> soft nofile 65536 <Installing User> hard nofile 65536
<Installing User> is the installing user login. Set these higher for more heavily used systems. You can also check/set file handles temporarily using the ulimit -H/Sn command. Like the following:
$ ulimit -Hn $ ulimit -Sn
How To:
Set Linux Permissions
These following ensures appropriate permissions exist so that the install succeeds on Linux. Your steps may vary slightly depending on the version on which you install.
1 Create a user, for example “redcell.”
2 Typically the redcell user’s home directory resembles /export/home/redcell. 3 In any case, ensure that user redcell owns its home directory (the /export/home/
redcell directory).
4 Create /dell/openmanage/networkmanager, and ensure that your user (redcell)
owns /dell/openmanage/networkmanager
/dell/openmanage/networkmanager is Dell OpenManage Network Manager’s installation root.
5 If necessary, unzip the downloaded installation package into a subdirectory under user
redcell’s home directory.
6 Ensure the unzipped script file linux_install has execute permissions. 7 Log in as user redcell
CAUTION:
Do not install root. During the installation a prompt appears to execute a script as root. This means you need root password and must open another shell where you act as root.
Perl
If you install Perl to take advantage of this application’s use of Perl Scripting capabilities, you must install it on the path on the application server and mediation server host. Best practice is to use Perl version 5.10 or later because some applications also require Perl as well as the Perl module
Net::Telnet.
This application does not package Perl. If you want to use the Perl scripting features, you must make sure your system has Perl installed. You can find information about Perl at www.perl.com. Follow the downloads link to find the recommended distribution for your specific platform. (See Adaptive CLI Script Language Syntax on page 358)
One of the recommended Perl packages is from ActiveState which can be found at: www.activestate.com/activeperl/
Starting Web Client
You can also open the client user interface in a browser. See Supported Web Browsers on page 19. The URL is
http://[application server hostname or IP address]:8080
The default login user is admin, with a password of admin. The first time you log in, you can select a password reminder. If you have forgotten your password, click the Forgot Password link in the initial screen to begin a sequence that concludes by mailing your user’s e-mail address a password.
CAUTION:
For this forgotten password sequence to work, you must configure users’ e-mails correctly. Click the link that is your user name in the upper right corner of the portal to configure your account’s settings for this and other things. The same configuration settings are available in Control Panel’s tabs labeled as your login.
The application server hostname is the name of the system where OpenManage Network Manager is installed.
HTTPS
You can connect to application server securely by configuring the included Apache Tomcat server for secure access. Consult your favorite search engine for more detailed information about setting up SSL with Tomcat web servers.
The following sections discuss typical administrative steps in getting started, once you have installed OpenManage Network Manager. See Getting Started on page 27 for a list of, and links to, other initial tasks once you have installed Dell OpenManage Network Manager.
Changing the Session Timeout Period
The timeout for the web portal extends automatically if data is changing onscreen. Nevertheless, you can change the timeout period with (non-override-able) properties in some files, as follows: You must modify two web.xml files with the same values to alter the session timeout. One 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>
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 Dell OpenManage Network Manager, you must be signed in as a user with the permissions. (The default admin user has such permissions.) The Go to > Control Panel menu item opens a screen with the following tabs of interest:
• [My Account]
• RCSynergy / [Domain]
• Portal > Users and Organizations • Portal > Roles
• Portal > Portal Settings • Portal > [Other]
• Redcell > Permission Manager
• Redcell > Database Aging Policies (DAP)) • Redcell > Data Configuration
• Redcell > Mediation
• Redcell > Filter Management • Server
Tips describing these screens and fields appear when you hover the cursor over fields, or click the blue circle around a question mark next to them. This blue circle can also toggle the appearance / disappearance of the tip.
Users with less-than-Administrator permissions may not see all of the features described in this guide.
Search Indexes
Sometimes Dell OpenManage Network Manager may display Control Panel objects like users, roles, and organizations inaccurately. This occurs because search Indexes need to be re-indexed every so often, especially when changes to roles, users and organizations are frequent.
To re-index go to Control Panel > Server Administration and then click on the Reindex all search
indexes. This takes little time.
[My Account]
To configure information for your login, look for the bar titled with your account login’s name. It has the following lines beneath it:
My Account—This configures your information as a user, including your e-mail address, password,
and so on.
My Pages—This manages public and private pages visible to you as a user. Use the tree of pages
that appears on the left of this screen to drag and drop pages in the order you want. Notice that you can also configure the look and feel, the logo that appears and other settings with the editor screens on the right.
Contacts Center—This configures contacts, in other words, people within your system that you
are following. Click the Find People link to see a list of potential contacts within your system. You must click Action > Follow to see them listed in the Contacts Home. Use the Action button to explore other possibilities.
The contact has to approve you in their requests. To Follow means you want to receive the followed person’s activity stream, blog postings, and so on. Friending means your friends can see your activity and you can see theirs. They have to accept any Friend request.
Tip
You can export vCards for all contacts in the system to use with other software that uses contacts. For example: e-mail clients.
RCSynergy / [Domain]
RCSynergy appears as a default domain name in Control Panel. Global and [My Login’s] Site configurations appear as additional items to configure when you click the down arrow to the right of RCSynergy.
The items under this label configure the overall look and feel of the portal, reference information, and so on. See the tooltips for more complete descriptions. This also configures pages, documents, calendars, blogs, wikis, polls and so on.
Social equity lets you alter measurements for user participation in organizations. Equity values
determine the reward value of an action; equity lifespans determine when to age the reward of action.
Portal > Users and Organizations
Create organizations and locations in addition to groups with the appropriate permissions (operators, administrators, and so on) in these screens. Users are individuals who performs tasks using the portal. Administrators can create new users or deactivate existing users. Users can be organized in a hierarchy of organizations and delegate its administration.
After creating them, add Users to roles which configure their permissions for access and action.
NOTE:
By default, every user is assigned to the role User. To assign a new user to specific permissions only, remove all rights on the User role, or confine its permissions to those that are universal first. Even though you don't see that user assigned to the User role, Best practice to spend some time designing your system’s security before creating users, organizations and roles.
When you are signed in, edit your user information by clicking the link with your username in the top right corner of the screen. Your user name does not appear in this screen.
Notice that if you select View > Hierarchy you can see organizations, grouped together with their component locations, groups and users.
How To:
Add Users and connect them to Roles
Add Users with the following steps:
1 Click Go to > Control Panel and navigate to Portal > Users and Organizations. 2 Click the Add > User menu item at the top of the Users and Organizations screen.
3 Enter the details of the new user. If you are editing an existing user, more fields appear. Screen
Name, and Email Address are required. Optionally, you can enter Name, Job Title, and so on.
4 After you click Save notice that the right panel expands to include additional information.
5 Notice that if you are editing an existing user, or creating a new one, you can use the links on
the right to configure connections with Roles. Roles, in particular, configure the OpenManage Network Manager functional permissions for that user. For example the group of Operators would likely have more limited capabilities than Administrators.
6 Click Save again, and the user you just configured should appear listed in the Users and
Organizations screen when you select View > All Users.
7 To assign a user to a role, click Action > Permissions and check the appropriate box next to
the role. Configure OpenManage Network Manager functional permissions for these roles in Roles (see Redcell > Permission Manager on page 42).
Tip
You can Export Users to a comma-separated value (CSV) file.
Once you have configured a user, you can click Action and to do the following:
Edit—Re-configure the selected user. Select the user’s Role in the editor, too. Roles configure
access and action permissions.
Permissions—Manage the user’s access to and control over various parts of the portal.
Manage Pages—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 tags, and javascript on these pages too.
Exports are in .lar format, and go to the download location configured in the browser you are using. The export screen lets you select specific features, and the date range of pages to export.
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 menu for the user or community.
Impersonate User—Open a web client with the same permissions as the user configured here. Impersonate User (Opens New Window)—This allows you to see the effect of any configuration
changes you have made on a user. The new window (typically a new tab) also lets you click the
Sign Out link in the upper right corner where you can return to your original identity
impersonation concealed.
Deactivate—Retires a user configured on your system. You can also check users and click the
Deactivate button above the listed users. Such users are not deleted, but are in a disabled
state. You can do an Advanced search for inactive users and Activate them or permanently delete them.
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 135 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.
Organizations
Create Organizations just as you would create Users. You can create a Regular or Location type of organization.
NOTE:
You must first create a Regular organization to be the parent for a Location.
How To:
Configure Organizations
Follow these steps to configure organizations. Associating organizational roles with organization members empowers them to exercise the associated permissions within the organization’s site(s).
1 Create a new Regular organization (Add > Regular Organization named MyCorp) as the
parent of location organizations.
2 Notice that you can add much more identifying information once you have saved the basics
(Name and Description) for the organization. This includes an Organization Site (a
checkbox) that would create a separate portal for the organization, to which you can add and configure pages, portlets, and so on.
3 Create two Location organizations (Add > Location, for example Admin and Headquarters).
Select MyCorp as the parent when you create the organization.
