HP Storage Essentials V5.00.01 installation guide (T4283-96011, January 2006)
Table Of Contents
- HP
- Storage Essentials 5.00.01 Installation Guide
- Contents
- Overview
- Installing the Management Server on Microsoft Windows
- Discovering Filers, Tape Libraries, Switches and Storage Systems
- Deploying CIM Extensions
- Installing the CIM Extension for IBM AIX
- Installing the CIM Extension for SGI ProPack for Linux
- Installing the CIM Extension for HP-UX
- Installing the CIM Extension for SUSE and Red Hat Linux
- Installing the CIM Extension for OpenVMS
- Installing the CIM Extension for HP Tru64 UNIX
- Installing the CIM Extension for SGI IRIX
- Installing the CIM Extension for Sun Solaris
- Installing the CIM Extension for Microsoft Windows
- Discovering Applications, Backup Servers and Hosts
- Managing Security
- Troubleshooting
Storage Essentials 5.00.01 Installation Guide 231
• Reports only display elements assigned to the user's organization, including child organizations.
For example, if you attempt to view a Host Summary report and you do not have permission to
access hosts through your organization, you are not given information about the hosts in the
report. This is also true for e-mailing reports. Let's assume again you do not have permission to
access hosts. The reports you e-mail will not contain information about hosts, including the host
specific reports. If the users receiving your reports want to be able to view information about
hosts, one of the following must happen:
• The hosts in question must be added to your organization.
• Someone else, who has the hosts in question already in their organization, must send the
reports.
IMPORTANT: When adding a child to an organization, do not add the organization's parent as a
child. For example, assume you created an organization named Child1 that has a parent
organization named Parent1. When you are adding child organizations to Child1, do not select
Parent1, as this creates a loop.
Planning Your Hierarchy
Before you begin creating organizations, plan your hierarchy. Do you want the hierarchy to be
based on location, departments, hardware, software or tasks? Perhaps you want a combination of
these options.
To help you with your task, create a table of users who manage elements on the network and the
elements they must access to do their job. You might start seeing groups of users who oversee the
same or similar elements. This table may help you in assigning users to the appropriate
organizations.
Once you are done with planning your hierarchy, draw the hierarchy in an graphics illustration
program, so you can keep track of which organizations are parents and children.
Create the child organizations first, then their parents. See the topic, ”Adding an Organization” on
page 239 for more information.
Naming Organizations
When you create an organization, give it a name that reflects its members. For example, you might
want to use one or more of the following as a guideline:
• Type of elements that are members of the organization, such as switches, Sun Solaris hosts
• Location of the elements, such as San Jose
• Task, such as backup machines
You may find that it is easy to forget which containers are parents and children. When you name an
organization, you might want to include a portion of the name of the dominant parent organization.
For example, assume you have two types of Web hosts in Boston: Microsoft Windows and Sun
Solaris. You might name the two children organizations BostonWebHost_Windows and
BostonWebHost_Solaris and their parent, BostonWebHosts.