HP Storage Essentials V5.1 Installation Guide First Edition (T4283-96025, August 2006)

ManualsBrandsHP ManualsSoftwareHP Storage Essentials SRM Exchange Viewer 1 MAL Tier-2 LTU

*12345-67890*

T4283-96025

Storage Essentials 5.1 Installation Guide

Part number: T4283-96025

First edition: August 2006

Summary of content (340 pages)

PAGE 1
HP Storage Essentials 5.
PAGE 2
Legal and notice information © Copyright 2002-2006 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
PAGE 3
Contents About this guide . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . HP technical support . . . . . . . . . . . . .
PAGE 4
Step 1 - Stop the AppStorManager and HP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2 - Export Your Existing Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3 - Upgrade HP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4 - Upgrade Storage Essentials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5 - Upgrade the HP SIM Connector. . .
PAGE 5
Step 1 - Discover Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 SMI-S Switches Must Be Removed and Rediscovered After Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Discovering Brocade Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Brocade SMI-S Provider Installation Requirements (New Installations of the Management Server) . . . . . .
PAGE 6
Viewing the Status of System Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplicate Logs for Brocade Switches in Same Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2 - Discover Storage Systems, NAS Devices and Tape Libraries . . . . . . . . . . . . . . . . . . . . . Discovering 3PAR Storage Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovery from HP SIM . . . . . . . . . . . . . . . . . . . .
PAGE 7
Discovering HP NAS Devices on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Discovery from HP SE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Discovering NetApp NAS Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Discovery from HP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Discovery from HP SE . . .
PAGE 8
Copying the CIM Extensions to the Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Default Logins for Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the CIM Extensions Management Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Launching the CIM Extensions Management Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Remote Hosts . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 HP-UX 11i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Driver Bundle Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Driver Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 HP-UX 11.0 .
PAGE 10
Additional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding the Version of a CIM Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the CIM Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rolling Over the Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 11
Configuring the CIM Extension to Listen on a Specific Network Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding the Version of a CIM Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the CIM Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 12
Additional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding the Version of a CIM Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combining Start Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the CIM Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rolling Over the Logs . . . . . .
PAGE 13
Step B - Provide the Microsoft SQL Server Name and Port Number . . . . . . . . . . . . . . . . . Removing the APPIQ_USER Account for SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting SQL Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Sybase Adaptive Server Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step A - Create the APPIQ_USER account for Sybase . . . . . . . . . . . . . . . . . . . .
PAGE 14
Adding Storage Volumes to an Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Members from an Organization . . .
PAGE 15
DCOM Unable to Communicate with Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplicate Listings for Brocade Switches in Same Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Element Logs Authentication Errors During Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMC Device Masking Database Does Not Appear in Topology (AIX Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 16
Known Device Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 “mailbox command 17 failure status FFF7” Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 ”Process Has an Exclusive Lock” Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 17
Storage Essentials 5.
PAGE 18
xviii
PAGE 19
About this guide This guide provides information about: • Installing the product • Discovering elements • Creating users • Changing the admin password • Installing JReport Designer Intended audience This guide is intended for: • Network Engineers • Administrators • Any one that needs to monitor and/or manage their file servers Prerequisites Prerequisites for using this product include: • Networking • Storage Area Networks (SANs) • The Common Information Model (CIM) Related documentation In addition to th
PAGE 20
Document conventions and symbols Document conventions Table 1 Convention Element Medium blue text: Figure 1 Cross-reference links and e-mail addresses Medium blue, underlined text (http://www.hp.
PAGE 21
TIP: Provides helpful hints and shortcuts. HP technical support Telephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support/.
PAGE 22
xx
PAGE 23
1 Overview This chapter describes the following: • ”About this Product” on page 3 • ”Software Requirements” on page 4 • ”Web Browser Configuration Requirements” on page 4 Storage Essentials integrates tightly with HP Systems Insight Manager. The installation requires you to install Storage Essentials, HP System Insight Manager, and the HP SIM Connector. It highly recommended you follow the steps outlined in Table 2 on page 1.
PAGE 24
Table 2 Roadmap for Installation and Initial Configurations (continued) Step Description Where to Find 5 Configure Internet Explorer Settings. See ”Step 8 - Configure Microsoft Internet Explorer Settings” on page 18. 6 Import a Storage Essentials License. See ”Step 9 - Import a Storage Essentials License” on page 19. 7 Perform discovery for switches, filers, and storage systems.
PAGE 25
Table 2 Roadmap for Installation and Initial Configurations (continued) Step Description Where to Find 8 Install a CIM Extension on each host (other than the management server) from which you want the management server to be able to obtain information. The CIM Extension gathers information from the operating system and host bus adapters on the host. It then makes the information available to the management server. • IBM AIX - See ”Installing the CIM Extension for IBM AIX” on page 125.
PAGE 26
Table 2 Roadmap for Installation and Initial Configurations (continued) Step Description Where to Find 10 If your license lets you collect disk drive statistics from Engenio storage systems, set up the management server to collect those statistics. See ”Obtaining Disk Drive Statistics from Engenio Storage Systems” on page 239.
PAGE 27
• Quicker deployment of storage infrastructure and business applications • Protection of customer flexibility and investments with a standards-based interface Key Features • End-to-end visibility of business applications - Provides an interface for you to monitor your business applications, including their associated infrastructure and interdependencies. • Integrated storage management - Lowers cost of acquiring and managing a heterogeneous storage environment using multiple disparate, point solutions.
PAGE 28
• To verify if Java is enabled - Click Advanced. • To verify if JavaScript is enabled - Expand the Advanced category, and then click Scripts & Plug-ins. For more information about enabling the items listed above, refer to the online help for your Web browser.
PAGE 29
2 Installing the Management Server on Microsoft Windows If you did not receive a computer with the management server installed on it, first complete the steps in this section. NOTE: The steps in this section are for installing the management server on Microsoft Windows. See ”Upgrading the Management Server” on page 21 for information about how to upgrade the management server. Keep in mind the following: • All steps must be completed for the management server to work properly.
PAGE 30
• Single box deployment - HP Systems Insight Manger and HP Storage Essentials are installed on the same server. Follow the instructions in this chapter. • Dual box deployment - HP Systems Insight Manager (SIM) and HP Storage Essentials (SE) are installed on different servers. When you install HP SIM on a different server, skip ”Step 5 Install HP Systems Insight Manager” on page 14.
PAGE 31
b. Select Properties. c. Click the Computer Name tab to see the fully qualified name of the computer under the label Full Computer Name. The fully qualified name of the HP SIM server (for example, computername.domainname.com) and the short name of the server (for example, computername) must resolve - either through a DNS lookup or through the hosts file on the server. If you are not using the hosts file for the short name to resolve, the DNS suffix has to be appended to the short name for DNS to resolve it.
PAGE 32
• Once you have started the installation, do not exit out of it. Future installations of the management server database may think you have already installed the software if you exit several minutes into the installation and orauser has already been created. • Install the database on the computer on which you plan to install the management server. • For double-byte languages, the Oracle installation provides an extra dialog screen, which is for the Oracle Net Configuration Assistant.
PAGE 33
NOTE: If you are not sure if you have already installed the patch, access the Oracle Universal Installer (Start > Programs > Oracle Installation Products > Universal Installer). In the Oracle Universal Installer, click Installed Products. Then, expand the OraHome tree. The installed products are displayed. Look for the highest patch level. To exit the Oracle Universal Installer, click Close, and then click Exit. When asked if you want to exit, click Yes. To install the Oracle patch: 1.
PAGE 34
Step 3 - Install the Management Server IMPORTANT: Install HP SIM and the SIM Connector before performing a discovery. Keep in mind the following: • Refer to the Support Matrix for operating system requirements on the management server CD-ROM. • Refer to the release notes for late breaking information. • Make sure no other programs are running when you install the management server.
PAGE 35
NOTE: Refer to the Support Matrix for information about supported hardware. 7. Do one of the following: • Click Install if you agree with the pre-installation summary. • Click Previous if you want to modify your selections. The management server is installed. CAUTION: Do not click the Cancel button during the installation. You can always remove an unsatisfactory installation. 8.
PAGE 36
3. Verify that the following services are disabled or not installed by looking under the Status column in the Services window • OracleOraHome92HttpServer • IIS (Internet Information Server) Step 5 - Install HP Systems Insight Manager IMPORTANT: The steps in this section are only if you are installing HP Systems Insight Manager (SIM) on the same server as HP SE. If you are installing HP SIM on a different server, skip this section.
PAGE 37
• Database: appiq • Port: 1521 • Jar File: c:\HP\StorageEssentials\JBossandJetty\server\appiq\lib\ojdbc14.jar. You specify this information in the Jar File window. • Select defaults for the rest of the options and install. It will take about 15 to 45 minutes to create and initialize the database. 6. Reboot. About Service Account Credentials You are asked for service account credentials during the installation of OpenSSH Services for HP SIM and during a typical installation of HP SIM.
PAGE 38
4. Change the user name ("This account") and password on the Log On tab to match the information for the new credentials. If the host is in a domain, specify the account using the domain\username format. Step 6 - Install the HP SIM Connector The HP SIM Connector lets you communicate with HP Systems Insight Manager. Install the HP SIM Connector on the same server running SE. To install the HP SIM Connector: 1. Make sure HP SE is not running.
PAGE 39
IMPORTANT: It is very important that the HP Systems Insight Manager service does not access the Oracle database before you are finished with changing the password for the Oracle database. e. Stop the AppStorManager service. AppStorManager cannot be running when you use the Database Admin Utility. f. Use the Database Admin Utility to change the SIM_MANAGER password in the Oracle database, see ”Using the Database Admin Utility to Change the SIM_MANAGER Password” on page 17.
PAGE 40
Step 7 - Browse to HP Systems Insight Manager Home Page 1. Wait until HP Systems Insight Manager (HP SIM) is fully started. HP SIM has fully started when you can bring up the Systems Insight Manager Home page. 2. Start the Storage Essentials (AppStorManager) service and change to 'Automatic.' 3. You should now be able to access HP SIM from a web browser using the URL https://:50000 (for example https://example.domain.com:50000). The host name must be fully qualified. 4.
PAGE 41
• Select the Advanced button. Then, check the following: Override automatic cookie handling, Accept First-party Cookies, Accept Third-party Cookies, Always allow session cookies. Click OK to accept changes and exit the window for modifying your Internet options in Internet Explorer. 4. Set stored pages settings: a. From Microsoft Internet Explorer, select Tools > Internet Options > General. b. Click the Settings button in the Temporary Internet section. c. Select the Microsoft default of Automatically.
PAGE 42
Navisphere CLI as part of the EMC Navisphere Software Suite. Contact your EMC representative for more information about obtaining the Navisphere CLI. Distribution rights for the Navisphere CLI belong to EMC. For Solaris, you must install the Navisphere Disk Array Management Tool CLI (NAVICLI). Contact your EMC representative for more information about obtaining the Navisphere CLI. Distribution rights for the Navisphere CLI belong to EMC.
PAGE 43
NOTE: You can also use the Oracle DBCA (Database Configuration Assistant) tool to remove OracleServiceAPPIQ. Click Start > Oracle-OraHome92 > Configuration and Management Tools > Database Configuration Assistant. a. Enter the following at a command prompt on the management server: oradim -delete -SID APPIQ b.
PAGE 44
• All files in %MGR_DIST%\JBossandJetty\server\appiq\remoteScripts • All files and subdirectories in %MGR_DIST%\JBossandJetty\server\appiq\fsrm • *All files and subdirectories in %MGR_DIST%\JBossandJetty\server\appiq\reports\customTreeNodes • *All files and subdirectories in %MGR_DIST%\JBossandJetty\server\appiq\reports\custom • *All files and subdirectories in %MGR_DIST%\JBossandJetty\server\appiq\reports\definitions\custom *This directory may not exist if you have not used Report Designer to create custom
PAGE 45
• Single box deployment - Upgrade HP SIM on the same server running HP Storage Essentials. Use the procedure for an Oracle database upgrade as defined by HP SIM. This information can be found in the HP SIM documentation. • Dual box deployment - Upgrade HP SIM on a server that is not running Storage Essentials. Refer to the upgrade instructions in the HP SIM documentation. Follow these steps to upgrade HP SIM: 1. Log in to Windows with a user account that is in the Administrators group for the local OS.
PAGE 46
Step 5 - Upgrade the HP SIM Connector IMPORTANT: HP SIM must be running when you upgrade the SIM Connector. 1. Verify that the service for HP Storage Essentials (AppStorManager) is stopped. 2. Verify that the service for HP SIM is running.Wait until you can browse to the Systems Insight Manager home page (https::50000). 3. Put the CD-ROM for installing the management server (Storage Essentials) in the CD-ROM drive of the server running Storage Essentials. 4.
PAGE 47
the help for your operating system platform for details on how to verify that the service is running. Step 7 - Remove and Rediscover Certain Elements If you previously discovered the following elements, you must remove and rediscover them as described in this section: • File servers - You must remove its access points.
PAGE 48
NOTE: An element may be listed more than once in the table if it was discovered through multiple access points. You must delete all of its access points by removing all the entries of the element in the topology table.You may end up removing other elements from the table as well. For example, if a CNT switch was used to discover host_A and host_B, you will end up removing host_A and host_B from the topology table.
PAGE 49
1. You must modify the listener.ora file at each remote site, as described in the following steps. For example, assume you have three remote sites. You must log onto each of these remote sites and modify the listener.ora file at each remote site, as described in the following steps: a. Log onto the remote site. b. Stop the service for the management server running. c. Stop the listener service for Oracle (OracleOraHome92TNSListener). d.
PAGE 50
28 Installing the Management Server on Microsoft Windows
PAGE 51
3 Discovering NAS Devices, Tape Libraries, Switches and Storage Systems Before you can use the management server, you must make the software aware of the elements on your network. An element is anything on the network that can be detected by the management server, such as a switch. This is done through the discovery process. Discovery obtains a list of discovered elements and information about their management interface and dependencies.
PAGE 52
• ”Overview of Discovery Features” on page 36 • ”Step 1 - Discover Switches” on page 45 • ”Step 2 - Discover Storage Systems, NAS Devices and Tape Libraries” on page 72 • ”Step 3 (Discovery from HP SE Only) - Build the Topology” on page 99 • ”Step 4 - Discovery Data Collection or Get Details” on page 104 • ”Troubleshooting Mode” on page 108 • ”Managing McDATA and EMC Connectrix Switches” on page 109 • ”Assigning a File Extension in Netscape 7” on page 111 • ”Filtering Discovery Groups” on page 112 • ”Moving
PAGE 53
from HP SIM. Credentials are passed from HP SIM to HP SE, so if you perform Discovery from HP SIM, the user names and passwords for discovering those elements appear in HP SE. • Multiple entries in SE may result when modifying username and password in HP SIM - If you use Discovery from HP SIM, the user name and passwords for those elements are forwarded HP SE. If you modify a user name for an element in Discovery from HP SIM, the modification is passed to HP SE as a new discovery entry for that element.
PAGE 54
Selective Discovery Filter The Selective Discovery Filter provides the capability to selectively filter the devices that are passed from HP SIM to HP SE for discovery operations. The filter is a file created by the user that contains a list of the IP addresses that should (or should not) be passed to HP SE. The filter does not impact the device discovery operations within HP SIM. It only restricts the data that is sent from HP SIM to HP SE.
PAGE 55
IMPORTANT: Because of subtle differences between discovery from HP SIM and HP SE, HP strongly recommends you do either all of your discovery steps in HP SIM or HP SE. See ”Differences Between HP SE and HP SIM Discovery” on page 30 for more information about the differences between HP SIM and HP SE discovery. Discovery from HP SIM Steps Discovery of switches, storage systems, NAS devices and tape libraries consists of several steps: 1. Discover your switches by using HP Systems Insight Manager.
PAGE 56
• After you discover an EMC Connectrix or McDATA switch, the IP address displayed next to the name of the switch is actually the IP address of the service processor for the switch in the Get Details/Discovery Data Collection screens. To find the IP address of the switch, click the link for the switch in one of the following screens: • Run Discovery Data Collection screen (Options > Storage Essentials > Discovery > Run Discovery Data Collection) for Discovery from HP SIM.
PAGE 57
as they can be accessed directly. Make sure the proxy service has started. On a computer running Windows, this can be determined by looking in the Services window. EMC Solutions Enabler version 5.1 requires additional steps for discovery. See ”Discovering EMC Solutions Enabler 5.1” on page 76 for more information. NOTE: Before performing any provisioning operations that involve a Brocade switch you must perform Discovery Step 3 for any subset of elements that includes this Brocade switch.
PAGE 58
Use the following table for SE discovery steps. See ”Accessing the Discovery Pages for HP SIM and HP SE” on page 31 if needed. Table 4 HP SE Discovery Steps for Switches, NAS Devices, and Storage Systems Step Description 1 If you have several switches and storage systems that use the same password and user name, set that password and user name as the default. See ”Setting Default User Names and Passwords” on page 37 for more information. 2 Discover your switches.
PAGE 59
This section describes the following: • ”About Entering Credentials for Elements in HP SIM” on page 37 • ”Setting Default User Names and Passwords” on page 37 • ”Adding an IP Range for Scanning” on page 38 • ”Adding a Single IP Address or DNS Name for Discovery” on page 39 • ”Modifying a Single IP Address Entry for Discovery” on page 41 • ”Removing Elements from the Addresses to Discover List” on page 42 About Entering Credentials for Elements in HP SIM For elements you want to discover and manage in HP SI
PAGE 60
another user name and password, you would also enter this user name and password. Do not specify the user name and password for the storage system in the individual range because that overrides the default user name and password. To access a Windows-based device, prefix the user name with domain_name\, as shown in the following example. This is required by the Windows login mechanism.
PAGE 61
Discovery from HP SE Instead of adding each IP address individually for scanning, the management server can detect a range of IP addresses, automatically populating the list of elements to be discovered. Keep in mind the following: • Include in the scanning, the proxy server that has a direct connection or a SAN connection to the management server, such as the EMC Solutions Enabler. Make sure the proxy service has started.
PAGE 62
• The following steps provide general information on how to discover an element. See Table 5 on page 46, Table 10 on page 73, and Table 6 on page 213. • To obtain drive-related statistics, install a proxy host. Ensure the proxy host has at least one LUN rendered by each controller of the array. See ”Obtaining Disk Drive Statistics from Engenio Storage Systems” on page 239 for more information. • (Discovery from HP SE only) The Do Not Authenticate option is for Engenio storage systems.
PAGE 63
• If you do not want to do provisioning on a storage system, leave the Password field blank. For Engenio storage systems, you must also select the Do Not Authenticate option. • If you want to do provisioning on a storage system, type the corresponding password for controller or proxy and make sure the Do Not Authenticate option is not selected. • For all other elements other than storage systems, provide the password if it is necessary for authentication.
PAGE 64
4. To add or change a comment, type a comment in the Comment field. 5. To change the password: a. Click the Change password button. b. Type the new password in the New Password field. c. Type the password again in the Verify Password field. d. Click OK in the Change Password page. 6. Click OK in the Edit Address for Discovery page. 7. Select the option, Step 2 - Topology: Select the discovered elements and build the topology view. 8. Select the element for which you changed the user name and/or password. 9.
PAGE 65
opens in a separate web browser window. Click the Discovery icon in the upper-right pane of the Storage Essentials home page. 2. Click Setup. 3. Select Step 1 at the top of the page. 4. Do one of the following: • Select the IP addresses and/or IP ranges you want to remove from the list. Then, click the Delete button. • Click the button corresponding to the elements you want to remove from the Addresses to Discover list.
PAGE 66
To prevent re-entering the information for each management server instance, you can import the same file for multiple management server instances. IMPORTANT: When you import a file, your previous settings are overwritten. If you are shown an error message when you try to import the discovery settings, verify you are using the right password. If you are using the correct password, there could be a possibility that the file is corrupt. To import discovery settings from a file: 1.
PAGE 67
• System type and then by System name. This option loads the systems being managed by HP Systems Insight Manager into the Contents window. 4. If you did not select Empty File, click Initialize Now to load the hosts file. Otherwise, enter the contents of the hosts file in the Contents section. 5. Click OK to save the hosts file, or click Cancel to cancel any changes you have made.
PAGE 68
Step 1 - Discover Switches This section describes the following: • ”SMI-S Switches Must Be Removed and Rediscovered After Upgrading” on page 47 • ”Discovering Brocade Switches” on page 48 • ”Discovering CNT Switches” on page 52 • ”Discovering Cisco Switches” on page 54 • ”Discovering Sun StorEdge and QLogic Switches” on page 56 • ”Changing the SNMP Trap Listener Port for Sun StorEdge Switches” on page 58 • ”Discovering McDATA and EMC Connectrix Switches” on page 59 • ”(Discovery from SE Only) Excluding McDA
PAGE 69
Table 5 Discovery Requirements for Switches (continued) Element Discovery Requirements Additional Information Cisco switches (SNMP) Enter the IP address/DNS name of the Cisco switch. Enter the SNMP read-only community string as the user name. You do not need to enter a password if you discover it in HP SE. HP SIM requires a password. See ”Discovering Cisco Switches” on page 54.
PAGE 70
IMPORTANT: Refer to the support matrix for information on which models and firmware revisions are supported through SMI-S. HP SIM 1. To remove elements from the HP SIM database: a. On the HP SIM home page, click Systems in the left pane. b. Select the elements you want to delete. c. Click Delete. 2. Rediscover the Brocade, Cisco, QLogic, or CNT switches in HP SIM. See ”Step 1 - Discover Switches” on page 45. 3. Perform Discovery Data Collection.
PAGE 71
IMPORTANT: When using the Brocade Fabric Access API, Brocade recommends that the switch with the most recent version of Brocade API firmware (newer than v.2.6.x) is configured as the proxy switch. When discovering Brocade SMI-S hosts the IP address of the Brocade SMI-S proxy server must be entered for Discovery Step 1. Be sure to see the Support Matrix for the latest details on firmware requirements.
PAGE 72
3. When prompted for the user name and password, supply them. 4. Type the following to see what is supported on the switch or Brocade SMI-S agent: configshow The output is displayed in a page-by-page format. 5. Select all of the output. 6. Paste the output in a text editor, for example Notepad. Use the Find command to search for rpc.rapid. 7. Verify Rapid is set to one, as displayed below: rpc.
PAGE 73
• IP address or system name of the Brocade SMI-S proxy server you want to discover. See ”Adding an IP Range for Scanning” on page 38 or ”Adding a Single IP Address or DNS Name for Discovery” on page 39 for more information. • User Name for the SMI-S proxy server for the Admin account • Password for the SMI-S proxy server for the Admin account NOTE: These instructions specify discovery using the standard port (5988 - non secure or 5989 - secure) for the Brocade SMI-S provider. For example: https://16.18.236.
PAGE 74
• The element does not require authentication. • Fabric Access API This field can be left blank if one or more of the following conditions are fulfilled: • The element's user name and password are one of the default user names and passwords. • The element does not require authentication. 7. In the Password field, do one of the following: • SMI-S Type the password for the SMI-S proxy server.
PAGE 75
This provider communicates with CNT InVsn Enterprise Manager to obtain information about the switch. The provider requires a certain version of InVsn depending on the switch model. See the following table for more information. Table 7 Required Switch Models and InVsn Versions for Discovery Switch Model InVsn Software Version FC/9000 9.0 or later UMD 9.5 or later IMPORTANT: The InVsn credentials are used by the SMI-S provider.
PAGE 76
• IP Address or System name of the primary IP address of the host running the InVsn software you want to discover. See ”Adding an IP Range for Scanning” on page 38 or ”Adding a Single IP Address or DNS Name for Discovery” on page 39 for more information. • Namespace - If the //root/cntfabric namespace for the InVSN software is not already included in the wbemportlist.xml file on the server running HP SIM, add this namespace as described in the HP SIM documentation. • Port number for the InVsn software.
PAGE 77
NOTE: The Cisco MDS 9020 Multilayer Fabric Switch does not support VSANs. Keep in mind the following for Cisco SNMP switches: • When you discover a Cisco SNMP switch, you do not need to provide a password if you discover it in HP SE. HP SIM requires a password. • You can view zones, zone sets and zone aliases on a Cisco switch; however, you cannot use the management server to create, modify or remove them from a Cisco switch.
PAGE 78
• For Cisco switches with SMI-S connections: Provide the SMI-S user name. • HP SIM does not allow blank passwords. Do one of the following: • Enter anything for the password for Cisco SNMP switches. • A password is required on SMI-S switches. Enter the password. Refer to the HP SIM documentation for more details. Discovery from HP SE To discover a Cisco switch: 1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The Storage Essentials home page opens in a separate web browser window.
PAGE 79
• When you discover a Sun StorEdge or QLogic SNMP switch in HP SE, you do not need to provide a password if you discover it in HP SE. HP SIM requires a password. • The management server does not support provisioning for Sun StorEdge and QLogic switches. Only the active zone set and its zone members are reported. • To manage a fabric of Sun StorEdge and/or QLogic switches, every switch in the fabric must be included in the discovery list.
PAGE 80
Discovery from HP SE To discover Sun StorEdge or QLogic switches: 1. Click Tools > Storage Essentials > Home > Discovery > Setup. See ”Accessing the Discovery Pages for HP SIM and HP SE” on page 31 if needed. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, type the DNS name or primary IP address of the Sun StorEdge or QLogic switch you want to discover. 6.
PAGE 81
5. Paste the copied text into the Custom Properties field. How you paste the text depends on your Web browser. If you are using Microsoft Explorer or Netscape Navigator, right-click the field and select Paste. 6. Make your changes in the Custom Properties field. Make sure the property is not commented out by removing the hash (#) symbol in front of the property. 7. Set the cimom.snmpTrapListenerPort property to the port you want, as shown in the following example: cimom.snmpTrapListenerPort=162 8.
PAGE 82
Table 8 Discovery Settings for McDATA and Connectrix Switches (continued) Discovery SWAPI setting through a Proxy SNMP setting Through a Proxy Contacting the switch directly Provisioning Limitations The SWAPI setting lets you activate a zone set, in addition to creating, editing, and deleting zones and zone sets. You cannot manage or view information about zone aliases. This SNMP setting through a proxy does not let you manage or access information about zones, zone sets or zone aliases.
PAGE 83
• If you discovered Connectrix Manager or EFC Manager, only enable SNMP trap forwarding to the management server on the Connectrix Manager or EFC Manager, not on the individual switches.Connectrix Manager or EFC Manager should be configured to forward SNMP traps to the IP address of the management server, and the community string should match the user ID you used to discover Connectrix Manager or EFC Manager.
PAGE 84
Step 2 - Verify the Discovery Setting for McDATA and Connectrix Switches is Set to SWAPI By default the discovery settings for McDATA and Connectrix switches is set to SWAPI. If you believe it has been changed to SNMP, you can perform the following steps to change it back to SWAPI. 1. Click Options > Storage Essentials > Manage Product Health. Then, click Advanced in the Disk Space tree. 2. Click Show Default Properties at the bottom of the page. 3. Copy the following property.
PAGE 85
2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, type the IP address or DNS name of the EFC Manager/Connectrix Manager you want to discover. 6. In the User Name field, type the user name for EFC Manager/Connectrix Manager. This field can be left blank if one or more of the following conditions are fulfilled: • The element's user name and password are one of the default user names and passwords.
PAGE 86
(Discovery from HP SE only) To fix this problem, use the Test button on the discovery screen to check the status of the SWAPI connection. If necessary, re-discover the EFCM to re-establish the SWAPI connection. Once the connection is working, the provisioning operation should succeed. If it continues to fail because the active zone set information is out of date, do a Get Details for this element to update the zoning information.
PAGE 87
• IP address or system name of the EFC Manager/Connectrix Manager you want to discover. See ”Adding an IP Range for Scanning” on page 38 or ”Adding a Single IP Address or DNS Name for Discovery” on page 39 for more information. • User name - The default user name, which is “public” (the read-only community string). This is the user name of the proxy. • HP SIM does not allow blank passwords. Enter anything for the password. See the HP SIM documentation for more detailed information.
PAGE 88
IMPORTANT: To obtain more information about the switch, you need to map the topology and obtain element details. See the topics, ”Building the Topology View” on page 99 and ”Get Details or Discovery Data Collection” on page 104. (Only applies to Discovery from HP SE)Step 3 - Make Sure There Are No Port Conflicts for Receiving SNMP Traps IMPORTANT: This step does not apply to discovery from HP SIM.
PAGE 89
Contacting a McDATA or Connectrix Switch Directly The management server uses SWAPI to discover a McDATA or Connectrix switch by its IP address or DNS name. SWAPI is the default setting. If you want to discover McDATA or Connectrix switches by SNMP, you must change to SNMP before you begin the following steps. See ”(Discovery from HP SE only) Changing the Discovery Settings” on page 68.
PAGE 90
12.To start discovering elements on the network, click the Start Discovery button on the IP Addresses tab. Discovery is complete when the software displays the DISCOVERY COMPLETED message in the Log Messages field. IMPORTANT: To obtain more information about the switch, you need to map the topology and obtain element details. See the topics ”Building the Topology View” on page 99 and ”Get Details or Discovery Data Collection” on page 104.
PAGE 91
(Discovery from HP SE only) Changing the Discovery Settings To change the discovery settings from SWAPI to SNMP or vice versa: 1. Delete all McDATA and Connectrix switches in the application by going to the Get Topology for Discovered Elements table (Tools > Storage Essentials > Home > Discovery > Topology) and selecting the switches you want to delete. Then, click the Delete button. See ”Accessing the Discovery Pages for HP SIM and HP SE” on page 31 if needed. 2.
PAGE 92
(Discovery from SE Only) Excluding McDATA and EMC Connectrix Switches from Discovery IMPORTANT: This step only applies to discovery from SE only. Specific McDATA and Connectrix switches can be excluded from discovery by using system properties. To exclude one or more switches from discovery, you must modify the cimom.mcdata.exclude property. Set the property cimom.mcdata.
PAGE 93
7. Add the Worldwide Names corresponding to the switches you want to exclude from discovery. Separate additional Worldwide Names with a comma, as shown by the following example: cimom.mcdata.exclude=1000080088A07024,1000080088A0D0B6 where 1000080088A07024 and 1000080088A0D0B6 are the Worldwide Names for McDATA and Connectrix switches. 8. When you are done, click Save. While AppStorManager is restarting, users are not able to access the management server.
PAGE 94
The following task statuses are provided by the Task Dashboard: Table 9 Task Status Descriptions Status Description Not Found This task can not be found on this server. Completed This task has been completed successfully. Failed This task failed with an error. Aborted This task has been aborted by the user or other automated actions. In Progress This task is in progress. CPU and disk activities are active on this server. Queued This task is scheduled to be executed in the future.
PAGE 95
• ”Discovering EMC Solutions Enabler 5.
PAGE 96
Table 10 Discovery Requirements for Storage Systems, Tape Libraries & NAS Devices (continued) Element Discovery Requirements Additional Information Engenio storage systems Can be discovered two ways: See ”Discovering Engenio Storage Systems” on page 79. • Entering the IP address/DNS name, user name and password of a controller for an Engenio storage system. Discovers only the corresponding IP address of the controller.
PAGE 97
Table 10 Discovery Requirements for Storage Systems, Tape Libraries & NAS Devices (continued) Element Discovery Requirements Additional Information Xiotech Storage Systems Discover the storage system directly. See ”Discovering Xiotech Storage Systems” on page 92. HP NAS Devices Discover the device directly. See ”Discovering HP NAS Devices on Windows” on page 93 and ”Discovering HP NAS Devices on Linux” on page 94. NetApp Devices Discover the device directly.
PAGE 98
Discovery from HP SE To discover a 3PAR storage system: 1. Click Tools > Storage Essentials > Home. See ”Accessing the Discovery Pages for HP SIM and HP SE” on page 31 if needed. Discovery > Setup. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, the following for the 3PAR storage system you want to discover. where is the IP address or DNS name of the 3PAR storage system you want to discover. 6.
PAGE 99
2. Add the following lines to the nethost file: [management server name] SYSTEM [management server IP] SYSTEM where • [management server name] is the DNS name of the management server • [management server name] is the IP address of the management server 3. Add the following line to the /opt/emc/API/symapi/config/netcnfg file: SYMAPI_SERVER - TCPIP 2707 4. Use the following command to start the daemon: /opt/emc/SYMCLI/V5.5.0/bin/symapisrv -service SYMAPI_SERVER start -background 5.
PAGE 100
If the cimom.symmetrix.exclude property, the management server discovers and obtains details from all EMC Symmetrix Storage Systems managed by discovered Solutions Enablers.
PAGE 101
for the Navisphere CLI belong to EMC. For Solaris, you must install the Navisphere Disk Array Management Tool CLI (NAVICLI). Contact your EMC representative for more information about obtaining the Navisphere CLI. Distribution rights for the Navisphere CLI belong to EMC. IMPORTANT: Before you discover your CLARiiON storage systems, you must have already installed all required software components for your CLARiiON storage system, such as the Navisphere Host Agent.
PAGE 102
Authenticate option. The management server will still monitor the Engenio storage system; however, you will not be able to do provisioning tasks. Discovery from HP SIM To discover Engenio storage systems, provide the following information in HP Systems Insight Manager: • IP address or system name of the controller or proxy you want to discover. See ”Adding an IP Range for Scanning” on page 38 or ”Adding a Single IP Address or DNS Name for Discovery” on page 39 for more information.
PAGE 103
for the server running HiCommand Device Manager. Do not point to the disk array for the storage system. To obtain information about HDS storage systems, the management server must be able to access the port HiCommand Device Manager uses to listen. By default, HiCommand Device Manager listens on port 2001, and the management server assumes this configuration at discovery time. If HiCommand Device Manager uses a different port, specify this other port when you discover HiCommand Device Manager.
PAGE 104
1. Access the Discovery Setup page (Tools > Storage Essentials > Home > Discovery > Setup). 2. Click the Add Address button. 3. In the IP Address/DNS Name field, type the name of the server and the port HiCommand Device Manager uses to listen separated by a colon, as shown in the following example: proxy2:1234 where • proxy2 is the name of the server running HiCommand Device Manager • 1234 is the port HiCommand Device Manager uses to listen 4.
PAGE 105
1. Select Options > Storage Essentials > Manage Product Health. Then, click Advanced in the Disk Space tree. 2. Click Show Default Properties at the bottom of the page. 3. Copy the following command. How you copy the text depends on your Web browser. If you are using Microsoft Explorer or Netscape Navigator, select the text and then right-click the selected text. Then, select Copy. #cimom.hds.exclude=61038,61037 4. Return to the Advanced page. 5. Paste the copied text into the Custom Properties field.
PAGE 106
• IP address or system name of the HP CIMOM you want to discover. See ”Adding an IP Range for Scanning” on page 38 or ”Adding a Single IP Address or DNS Name for Discovery” on page 39 for more information. • User name for accessing the HP CIMOM • Password for accessing HP CIMOM. Discovery from HP SE To discover HP EVA or MSA storage systems: 1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The HP SE home page opens in a separate web browser window.
PAGE 107
• IP address of the server containing the HP CIMOM The following should be installed on a server before you discover an HP XP storage system if you are discovering the storage system by using Command View XP: • HP Storage Management Appliance software • HP OpenView Storage Operations Manager • HP StorageWorks Command View XP Discovery from HP SIM by Using Command View XP To discover HP storage systems by using Command View XP, provide the following information in HP Insight Manager: • IP address or system n
PAGE 108
12.To start discovering elements on the network, click the Start Discovery button on the IP Addresses tab.
PAGE 109
11.Click OK. 12.To start discovering elements on the network, click the Start Discovery button on the IP Addresses tab.
PAGE 110
Discovering IBM Storage Systems Before you can discover an IBM storage system, you must install the IBM CIM Agent. For Enterprise Storage Server (ESS) devices, the CIM Agent is called “CIM Agent for ESS”; for DS devices and mixed DS and ESS environments, use the “CIM Agent for DS Open (API)”. It is recommended not to install the IBM CIM Agent on the management server. Refer to the “CIM Agent for DS Open (API) Installation and Configuration Guide” for details on configuring the CIM Agent.
PAGE 111
NOTE: You do not need to provide the interop namespace because the management server includes the interop namespace for IBM storage systems in its default list. Discovery from HP SIM IMPORTANT: First discover the host running the IBM CIMOM. See ”Adding an IP Range for Scanning” on page 38 or ”Adding a Single IP Address or DNS Name for Discovery” on page 39 for more information. Then, select Options > Protocol Settings > System Protocol Settings and select the host you discovered as a target.
PAGE 112
11.Click OK. 12.To start discovering elements on the network, click the Start Discovery button on the IP Addresses tab. Discovering Sun StorEdge 3510 Storage Systems Before you can discover a Sun StorEdge 3510 storage system, you must set up a Sun StorEdge 3510 SMI-S provider and a Sun StorEdge™ Configuration Service. The provider cannot be installed on the same computer as the management server due to a port conflict.
PAGE 113
• User Name of the system running the Sun StorEdge 3510 SMI-S provider. • Password of the Sun StorEdge 3510 SMI-S provider. Refer to the HP SIM documentation for more information about discovering storage systems with HP SIM. Discovery from HP SE To discover Sun StorEdge 3510 storage systems: 1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The HP SE home page opens in a separate web browser window. Click Discovery > Setup in the upper-right pane of the HP SE home page window. 2.
PAGE 114
1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The HP SE home page opens in a separate web browser window. Click Discovery > Setup in the upper-right pane of the HP SE home page window. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, type the IP address or DNS name of the storage system you want to discover. 6. Enter the User Name of the storage system. 7.
PAGE 115
6. Leave the User Name field blank. 7. Leave the Password field blank if you do not want to do provisioning on the storage systems. If you want to do provisioning, type the corresponding password for controller or proxy. 8. If you typed a password in the previous step, retype the password in the Verify Password field. 9. In the Comment field (optional), type a comment for additional information.
PAGE 116
• /root/cimv2 is its namespace. 6. You can leave the user name and password for the Xiotech storage system blank. 7. In the Comment field (optional), type a comment for additional information. The information typed into this field is displayed under the Comment column in the Addresses to Discover list (Tools > Storage Essentials > Home > Discovery > Setup). 8. Do not select the Do Not Authenticate option. 9. Click OK. 10.
PAGE 117
1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The HP SE home page opens in a separate web browser window. Click Discovery > Setup in the upper-right pane of the HP SE home page. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, type the IP address or DNS name of the HP NAS device you want to discover. 6. Enter the User Name of the HP NAS device. You must provide a privileged login. 7.
PAGE 118
• IP address or system name of the HP NAS device to discover. See ”Adding an IP Range for Scanning” on page 38 or ”Adding a Single IP Address or DNS Name for Discovery” on page 39 for more information. • User name of the HP NAS device. You must provide a privileged login. • Password used to access the HP NAS device. Refer to the HP SIM documentation for more information about HP SIM. Discovery from HP SE To discover an HP NAS device on Linux: 1.
PAGE 119
• the root user • a user belonging to the “Administrators” group. This is a predefined group by NetApp. • a user belonging to a group that has the following roles: api-*, cli-*, login-http-admin, and at least one of the following: login-console, login-telnet, login-rsh, or login-ssh • Administrative HTTP access to the device can be restricted through the httpd.access and httpd.admin.access options. If that is the case, then the management server needs to be registered with the device.
PAGE 120
Discovering Sun NAS Devices NOTE: You do not need to provide the interop namespace because it is included in the management servers list of default namespaces. Discovery from HP SIM To discover a Sun NAS Device, provide the following information in HP Insight Manager: • IP address or system name of the server running the SMI-S provider for the Sun NAS devices you want to discover.
PAGE 121
Discovering HP and IBM Tape Libraries Discovery from HP SIM To discover a tape library, provide the following information in HP Systems Insight Manager: • IP address or system name for the tape library. See ”Adding an IP Range for Scanning” on page 38 or ”Adding a Single IP Address or DNS Name for Discovery” on page 39 for more information. • For HP tape libraries you do not need to provide a namespace. • For IBM tape libraries the namespace (/root/ibm) is already provided in the wbemportlist.
PAGE 122
• ”Modifying the Properties of a Discovered Address” on page 100 • ”Deleting Elements from the Product” on page 101 Building the Topology View After you discover elements, the management server requires you to build a topology view, which is a graphical representation of port-level connectivity information. If a switch has more than one connection to an element, the number of connections is displayed above the line linking the switch and the element.
PAGE 123
5. If you see errors in the topology, look at the log messages, which can provide an indication of what went wrong. See the topic, ”Viewing Log Messages” on page 70 for more information about the messages that appear in this tab. Look at Event Manager for additional information. Access Event Managerby clicking the Event Manager button in the left pane. To obtain troubleshooting information, see the topic, ”Troubleshooting Topology Issues” on page 289.
PAGE 124
1. Click Options > Storage Essentials > Discovery > Run Discovery Data Collection. 2. Click the button corresponding with the element you want to modify. 3. To move an element to another discovery group, select its new discovery group from the Discovery Group drop-down menu. 4. Click OK in the Edit Discovered Element window. Discovery from HP SE To change the discovery properties of an element: 1. Click Tools > Storage Essentials > Home on the HP SIM home page menu.
PAGE 125
proxies that were used to discover the element, the element may reappear the next time you Get Details/Discovery Data Collection. For example, assume you want to delete Switch_A. Switch_B and Switch_C were used to discover Switch_A. If you delete only Switch_B and Switch_A, Switch_A will most likely reappear when you Get Details/Discovery Data Collection because it is still accessible by Switch_C.
PAGE 126
(Discovery from HP SE Only)Deleting Elements Using Discovery Step 2 (Topology) IMPORTANT: These steps are only accessible from Discovery from HP SE. To delete multiple elements using Discovery Step 2 (Topology): 1. Click Tools > Storage Essentials > Home from the HP SIM home page. The Storage Essentials home page opens in a separate web browser window. Click Discovery > Topology in the upper-right pane of the HP Storage Essentials home page. 2.
PAGE 127
• ”Excluding EMC Symmetrix Storage Systems from Force Device Manager Refresh” on page 106 • ”Excluding HDS Storage Systems from Force Device Manager Refresh” on page 107 Get Details or Discovery Data Collection Get Details or Discovery Data Collection is required to obtained detailed information from discovered elements. Get Details/Discovery Data Collection must be performed before you can do provisioning and/or obtain provisioning information, such as data about zone sets and LUN numbers.
PAGE 128
management server then moves onto getting details for the next element in the Get Details/Discovery Data Collection table. These UNIX hosts appear as missing until they are removed from quarantine. See ”Removing an Element from Quarantine” on page 113 for information on how to remove an element from quarantine. To obtain details about the devices on the network: 1. Do one of the following: • Discovery from HP SIM - Click Options > Storage Essentials > Discovery > Run Discovery Data Collection.
PAGE 129
IMPORTANT: If you stop the gathering of details, you should reschedule it. This type of collection obtains detailed information of devices in the network. To stop the gathering of details: 1. Do one of the following: • Discovery from HP SE - Click Tasks & Logs > View Storage Essentials Logs. • Discovery from HP SIM - Click Options > Storage Essentials > Discovery > View Logs. 2. On the View Logs page, click the “Click here” portion of the following message: Click here if you wish to stop getting details.
PAGE 130
6. Make sure the property is not commented out by removing the hash (#) symbol in front of the property. Add the serial numbers corresponding to the Symmetrix storage systems you want the refresh to skip. Separate additional serial numbers with a comma, as shown by the following example: cimom.emc.skipRefresh=000183500570,000183500575 where 000183500570 and 000183500575 are serial numbers for Symmetrix storage systems.
PAGE 131
3. Copy the following command. How you copy the text depends on your Web browser. If you are using Microsoft Explorer or Netscape Navigator, select the text and then right-click the selected text. Then, select Copy. # cimom.HdsSkipRefresh=61038,61037 4. Return to the Advanced page (Options > Storage Essentials > Manage Product Health. Then, click Advanced in the Disk Space tree). 5. Paste the copied text into the Custom Properties field. How you paste the text depends on your Web browser.
PAGE 132
“Discovery->Setup in Troubleshooting mode” link located in the step 1 error message. Clicking this link will bring you to the step 1 page with Troubleshooting Mode enabled. NOTE: Step 3 Troubleshooting Mode only identifies quarantined hosts.
PAGE 133
IMPORTANT: Obtaining details takes some time. You might want to perform this process when the network and the managed elements are not busy. To Get Details/Discovery Data Collection: 1. Do one of the following: • Discovery from HP SE - Start the HP SE home page, click Tools > Storage Essentials > Home. The HP SE home page opens in a separate web browser window. Click Discovery > Details on the HP SE home page.
PAGE 134
(Discovery from HP SE Only)Swapping McDATA and EMC Connectrix Switches After replacing switches in the service processor, you must make the management server aware of your changes by removing the old switches from the user interface and then performing Get Details/Discovery Data Collection so the management server can discover the new switches. If you are adding switches to a service processor that has not been discovered yet, see the topic, ”Discovering McDATA and EMC Connectrix Switches” on page 59.
PAGE 135
1. Click the download file link or button in the software. 2. Click the Advanced button in the lower-left corner. 3. In the Description of type field, delete the existing text and type a description of the file. 4. In the File extension field, delete the existing text and type the file extension. 5. Click OK. The next time Netscape 7 sees the associated MIME type, it will assign the extension you typed in the File Extension field. 6. Click OK.
PAGE 136
Discovery Data Collection for Discovery from HP SIM or Get Details and getting the topology for Discovery from HP SE. For example, you could specify that the management server gets Get Details/Discovery Data Collection for only the elements in Discovery Group 1, thus, saving you time. This feature is sometimes referred to as segmented replication because you can specify gettingGet Details/Discovery Data Collection for a segment of the discovered elements.
PAGE 137
Removing an Element from Quarantine To remove an element from quarantine: 1. Select the check boxes for the elements you want to remove from quarantine on the Discovery Data Collection page for Discovery from HP SIM or Get Details page for Discovery from HP SE. Quarantined elements appear with a flag ( ) in the Quarantined column on the Discovery Data Collection page for Discovery from HP SIM or Get Details page for Discovery from HP SE. 2. Click the Clear Quarantine button. 3.
PAGE 138
topics for more information: ”Excluding EMC Symmetrix Storage Systems from Discovery” on page 77 and ”Excluding EMC Symmetrix Storage Systems from Force Device Manager Refresh” on page 106. 4. Click the Get Details button. 5. View the status of the gathering of element details by looking in the View Logs page. See the topic, ”Viewing Log Messages” on page 70 for more information about the messages viewed in this tab. 6. Verify the topology is displayed correctly by accessing System Manager.
PAGE 139
Notifying the Software of a New Element When you add a new element to the network, such as a host, perform discovery to make the management server aware of the new element. Keep in mind the following while performing discovery: • If you change the password of a host after you discover it, you must change the password for the host in the discovery list. Then, you must stop and restart the CIM Extension running on that host. • If you started a CIM Extension on a Sun Solaris host with the .
PAGE 140
118 Discovering NAS Devices, Tape Libraries, Switches and Storage Systems
PAGE 141
4 Deploying and Managing CIM Extensions This chapter describes the following: • ”About Remote CIM Extensions Management” on page 119 • ”About the CIM Extensions Management Tool” on page 121 About Remote CIM Extensions Management It is possible to install, upgrade, and manage CIM Extensions remotely across any number of hosts. The following operations can be initiated from the management server: • Perform an installation or re-installation of the OpenSSH daemon (sshd) for Windows hosts only.
PAGE 142
• domain1 is the domain name • admin is the username • If you are not using a domain, don’t specify the host name when deploying OpenSSH. For example, enter a user name of where • admin is the user name Copying the CIM Extensions to the Management Server To remotely install the CIM Extensions, you must first copy the CIM Extensions installation files to the management server.
PAGE 143
About the CIM Extensions Management Tool CIM Extensions can be remotely managed through a graphical user interface called the CIM Extensions Management Tool. Each host being managed must be running a supported SSH daemon. See ”About SSH” on page 119 for more information. You must copy the CIM Extensions to the management server before you can use the CIM Extension Management Tool. See ”Copying the CIM Extensions to the Management Server” on page 120 for more information.
PAGE 144
• Download configuration - Downloads the configuration files from the CIM Extensions on the remote system. • Download logs - Downloads the log files from the CIM Extensions on the remote system. • Configure - Configures the CIM Extensions on the remote system. You can configure the TCP port to listen on, the IP address to bind to, and custom credentials for the extensions to use. NOTE: You can only configure the IP address with a specific address if there is only one system in the list.
PAGE 145
NOTE: When setting up the collection of data from the management server, you must use the credentials you configured the extensions with instead of the host’s “root” or “administrator” user. Status Icons A status for each host displays in the column to the right of the host name. The following statuses are possible: Table 11 Icon Status Icons Status The host has been added to the list, but no action as been selected. The action is waiting to begin or in progress. The last action completed with a warning.
PAGE 146
124 Deploying and Managing CIM Extensions
PAGE 147
5 Installing the CIM Extension for IBM AIX This chapter describes the following: • ”About the CIM Extension for IBM AIX” on page 125 • ”Prerequisites” on page 126 • ”Verifying SNIA HBA API Support” on page 126 • ”Installing the CIM Extension” on page 127 • ”Setting Up Monitoring” on page 128 • ”Starting the CIM Extension Manually” on page 128 • ”How to Determine if the CIM Extension Is Running” on page 129 • ”Configuring CIM Extensions” on page 129 • ”Stopping the CIM Extension” on page 132 • ”Stopping the
PAGE 148
• tools - The files to stop, start and show the status of the CIM Extension Prerequisites The installation checks for the following. If the installation fails, see ”Fulfilling the Prerequisites” on page 132. AIX 5.1 • Maintenance level 03 or later • bos.rte.libc.5.1.0.36 or later Both AIX 5.1 and 5.2 xlC.rte.5.0.2.1 or later AIX 5.3 • bos.rte.libc 5.3.0.0 • xlC.rte 6.0.0.0 Required Disk Space The CIM Extension for AIX requires 40 MB.
PAGE 149
program, hbatest, lists the name and number for all HBA's that support the SNIA HBA API. In some instances hbatest may report it cannot find an HBA driver even though an HBA driver is installed. Try installing a different version of the HBA driver that is SNIA compliant. To run hbatest: 1. Go to the Aix/tools directory on the CIM Extension CD-ROM. 2. Enter the following at the command prompt:./hbatest The program runs its diagnostics. IBM Adapters FCXXXX SNIA comes from the package devices.common.IBM.fc.
PAGE 150
11.Unmount the CD-ROM by entering the following at the command prompt: # umount /cdrom where /cdrom is the name of the directory where you mounted the CD-ROM 12.Complete the following: • Turn on Monitoring. See ”Setting Up Monitoring” on page 128. • Start the CIM Extension. See ”Starting the CIM Extension Manually” on page 128. • (Optional) On some versions of AIX, the CIM Extension cannot start automatically after the host is rebooted.
PAGE 151
How to Determine if the CIM Extension Is Running You can determine if the CIM Extension is running by entering the following command at the command prompt: # ./status The CIM Extension is running when the following message is displayed: CIM Extension Running: Process ID: 93 where 93 is the process ID running the CIM Extension Configuring CIM Extensions Configuration information is stored in a configuration text file that is read by the CIM Extension on start-up. The file is named cim.extension.
PAGE 152
Discovery > Setup > Add Address). In the IP Address/DNS Name field, type a colon and then the port number after the IP address or DNS name, as shown in the following example: 192.168.1.2:1234 where • 192.168.1.2 is the IP address of the host • 1234 is the new port number If you have already added the host to the discovery list (Tools > Storage Essentials > Home > Discovery > Setup) on the management server, you must remove it and then re-add it.
PAGE 153
If you change the port number, you must make the management server aware of the new port number in the Add Address for Discovery page (Tools > Storage Essentials > Home > Discovery > Setup > Add Address). In the IP Address/DNS Name field, type a colon and then the port number after the IP address or DNS name, as shown in the following example: 192.168.1.2:1234 where • 192.168.1.
PAGE 154
You are shown the version number of the CIM Extension and the date it was built, as shown in the following example: CXWS for mof/cxws/cxws-aix.mof CXWS version xxxx, built on Fri xx-March-xxxx 12:29:49 by dmaltz Stopping the CIM Extension To stop the background process for the CIM Extension, enter the following at the command prompt in the /opt/APPQcime/tools directory: # ./stop Keep in mind the following: • You must have root privileges to stop the CIM Extension.
PAGE 155
• xlC.rte 6.0.0.0* - The C++ runtime. *Go to the IBM Technical Support Web site at the following URL to obtain information about obtaining these file: https://techsupport.services.ibm.com On the Web page do the following: 1. Under the Refine Your Search Section select Tools/Utilities from the Limit by Type drop-down menu. 2. Select AIX from the Limit by Platform or Operating System drop-down menu. 3. Select 5.0 from the Limit by Version drop-down menu. 4.
PAGE 156
6. In the SOFTWARE name, press Esc+4 and select: APPQcime 7. On the same page you selected APPQcime, select “No” for Preview by pressing the tab key. 8. Press ENTER to remove the software.
PAGE 157
6 Installing the CIM Extension for SGI ProPack for Linux This chapter describes the following: • ”About the CIM Extension for SGI ProPack for Linux” on page 135 • ”Prerequisites” on page 135 • ”Verifying SNIA HBA API Support” on page 136 • ”Installing the CIM Extension” on page 136 • ”Starting the CIM Extension” on page 137 • ”How to Determine if the CIM Extension Is Running” on page 139 • ”Configuring CIM Extensions” on page 139 • ”Rolling Over the Logs” on page 141 • ”Stopping the CIM Extension” on page
PAGE 158
• Blowfish • DES • MD5 NOTE: All ProPacks require that pam-devel rpm is installed. Network Port Must Be Open The CIM Extension uses port 4673 by default to communicate with the management server. Verify the network port is open. Refer to the documentation accompanying your Altix host for more information. If you need to use a different port, see ”Permanently Changing the Port a CIM Extension Uses (UNIX Only)” on page 275.
PAGE 159
1. Go to the /Altix directory on the CIM Extensions CD-ROM by entering the following at the command prompt: # cd /cdrom/Altix where /cdrom is the directory where you mounted the CD-ROM. 2. To install the software, do one of the following: IMPORTANT: If you receive a message saying there is not enough room in the temp directory to perform the installation, set the IATEMPDIR variable to another directory. The installation uses this directory to extract the installation files.
PAGE 160
• To configure UNIX CIM Extensions to run behind a firewall, see ”Configuring UNIX CIM Extensions to Run Behind Firewalls” on page 276. To start the CIM Extension, type the following in the /opt/APPQcime/tools directory: 1.
PAGE 161
• When you start the CIM Extension, you can restrict the user accounts that can discover the host. You can also change the port number the CIM Extension uses. See the following topics for more information. You can also access information about these topics by typing the following: ./start -help How to Determine if the CIM Extension Is Running You can determine if the CIM Extension is running by entering the following command at the command prompt: # .
PAGE 162
If you change the port number, you must make the management server aware of the new port number in the Add Address for Discovery page (Tools > Storage Essentials > Home > Discovery > Setup > Add Address). In the IP Address/DNS Name field, type a colon and then the port number after the IP address or DNS name, as shown in the following example: 192.168.1.2:1234 where • 192.168.1.
PAGE 163
discovered as a target. On the System Protocol Settings page, provide the port number for the host under the WBEM section. Discovery from HP SE If you change the port number, you must make the management server aware of the new port number in the Add Address for Discovery page (Tools > Storage Essentials > Home > Discovery > Setup > Add Address). In the IP Address/DNS Name field, type a colon and then the port number after the IP address or DNS name, as shown in the following example: 192.168.1.
PAGE 164
The logging information for the CIM Extension is contained primarily in the cxws.log file, created by default in the /tools directory. The cxws.log file rolls over once it becomes more than 100 MB. The information in cxws.log is moved to cxws.log.1. When the logs roll over again, cxws.log.1 is renamed to cxws.log.2 and the information that is in cxws.log is moved to cxws.log.1. The numbering for the files continues sequentially, for example, cxws.log.
PAGE 165
7 Installing the CIM Extension for HP-UX This chapter describes the following: • ”About the CIM Extension for HP-UX” on page 143 • ”Prerequisites” on page 143 • ”Verifying SNIA HBA API Support” on page 144 • ”Installing the CIM Extension” on page 145 • ”Starting the CIM Extension Manually” on page 146 • ”How to Determine if the CIM Extension Is Running” on page 146 • ”Configuring CIM Extensions” on page 146 • ”Stopping the CIM Extension” on page 151 • ”Rolling Over the Logs” on page 151 • ”Fulfilling the P
PAGE 166
HP-UX 11i and 11.0 Software Requirements Following software driver bundles must be installed on HP-UX 11i and 11.0 hosts. FC SNIA HBA API software is bundled with the driver and is installed at the same time the driver is installed. HP-UX 11i Driver Bundle Version B.11.11.09 PCI/HSC FibreChannel;Supptd HW=A6684A,A6685A,A5158A,A6795A (FibrChanl-00 Bundle). This driver Bundle is automatically selected for installation with the HP-UX 11i Operating Environments. Driver Version = @(#) PATCH_11.11: libtd.
PAGE 167
1. Go to the HPUX/tools directory on the CIM Extension CD-ROM. 2. Enter the following at the command prompt: ./hbatest The program runs its diagnostics. HP SNIA Adapters AXXXXA comes from fileset FC-FCD, FC-TACHYON-TL. Unless separated purposely during installing the operating system, filesets are there by default. To view the location of the library, enter the following at the command prompt: # more /etc/hba.conf The following is displayed: com.hp.fcms32 /usr/lib/libhbaapihp.
PAGE 168
where /cdrom is the name of the directory where you mounted the CD-ROM 7. Press the Eject button on the CD-ROM drive to take the CD out of the CD-ROM drive. The CIM Extension for HP-UX starts automatically at boot time by using /sbin/rc2.d scripts. The CIM Extension uses port 4673 when it starts automatically after a reboot. Type the following at the command prompt to find the status of the CIM Extension: .
PAGE 169
named cim.extension.parameters-sample. This file contains samples of available parameters and can be copied into the cim.extension.parameters file and used as a template. Restricting the Users Who Can Discover the Host The -users parameter provides greater security by restricting access. When you use the management server to discover the host, provide a user name that was specified in the -users parameter.
PAGE 170
NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. Discovery from HP SIM If you change the port number, you must include the new port number in your discovery. If you have not already done so, discover the host. See ”Adding an IP Range for Scanning” on page 38 or ”Adding a Single IP Address or DNS Name for Discovery” on page 39 for more information.
PAGE 171
NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. The “-on” parameter may include a port specification. In that case, the CIM Extension listens on the indicated port of the indicated NIC, rather than the default port, for example: -on 192.168.2.2:3456 The CIM Extension listens only on the NIC that has the IP address 192.168.2.2 on port 3456.
PAGE 172
Table 14 Parameters for CIM Extensions Parameter Description -user The user defined in this parameter must be a valid user for the host. Only the user needs to be defined. The user name and password are provided from the management server during discovery. The user does not need to have root authority. A colon separated list can be used to specify multiple users.
PAGE 173
• 1234 is the new port Stopping the CIM Extension To stop the CIM Extension, enter the following at the command prompt in the /opt/APPQcime/tools directory, where /opt is the directory into which you installed the CIM Extension: # ./stop Keep in mind the following: • You must have root privileges to stop the CIM Extension. • When you stop the CIM Extension, the management server is unable to gather information about this host.
PAGE 174
Removing the CIM Extension from HP-UX To remove the CIM Extension for HP-UX as root: 1. Login as root. 2. Stop the CIM Extension, as described in ”Stopping the CIM Extension” on page 151. 3. Make sure you are not in the APPQcime directory. As a precaution, go to the root directory. 4. Enter the following at the command prompt: # swremove APPQcime When you see the following message, the CIM Extension has been removed: * Beginning Execution * The execution phase succeeded for hpuxqaX.dnsxxx.com:/".
PAGE 175
8 Installing the CIM Extension for SUSE and Red Hat Linux This chapter describes the following: • ”About the CIM Extension for Red Hat Linux Advanced Server and SUSE Linux” on page 153 • ”Prerequisites” on page 153 • ”Verifying SNIA HBA API Support” on page 154 • ”Installing the CIM Extension” on page 155 • ”Starting the CIM Extension Manually” on page 156 • ”How to Determine if the CIM Extension Is Running” on page 156 • ”Configuring CIM Extensions” on page 156 • ”Stopping the CIM Extension” on page 159 •
PAGE 176
Red Hat Linux Advanced Server 3.0 Update 2 (may just be i386.rpm on certain customer configurations) requires glibc-2.3.2-95.20.i686.rpm (update2 CD2) requires laus-0.1-54RHEL3.i386.rpm (update2 CD2) requires compat-libstdc++-7.3-2.96.128.i386.rpm (update2 CD3) requires libgcc-3.2.3-34.i386.rpm (update2 CD2) Red Hat Linux Advanced Server 2.1 Update 4 (may just be i386.rpm on certain customer configurations) requires glibc-2.2.4-32.15.i686.rpm (update4 CD1) requires compat-libstdc++-6.2-2.9.0.16.i386.
PAGE 177
The following is displayed: com.emulex.emulexapilibrary /usr/lib/libemulexhbaapi.so Driver Information for Verifying QLogic SNIA Adapters on Red Hat Linux QLogic SNIA Adapters comes from package qlapi-vX.XXX-rel.tgz found in the QLogic driver. The adapters are installed separately after driver. To view the location of the library, enter the following at the command prompt: # more /etc/hba.conf The following is displayed: qla2x00 /usr/lib/libqlsdm.
PAGE 178
• For all other servers: # rpm -idvh APPQcime.rpm The installation is done when you are returned to the command prompt. Starting the CIM Extension Manually The management server can only obtain information from this host when the CIM Extension is running. Keep in mind the following: • You must have root privileges to run the CIM Extension. The CIM Extension only provides the information within the privileges of the user account that started the CIM Extension.
PAGE 179
Changing the Port Number The CIM Extension uses port 4673 by default. If the port is already used, follow these steps to change the port the CIM Extension will access: 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.parameters file in a text editor, and provide the following line: -port 1234 where 1234 is the new port for the CIM Extension 3. Save the file. 4. Restart the CIM Extension for your changes to take effect. NOTE: The CIM Extension looks for parameters in the cim.
PAGE 180
NOTE: If you want to configure the CIM Extension to listen on multiple NICs, use a comma to separate multiple addresses. 3. Save the file. 4. Restart the CIM Extension for your changes to take effect. NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. The “-on” parameter may include a port specification.
PAGE 181
Table 15 Parameters for CIM Extensions Parameter Description -user The user defined in this parameter must be a valid user for the host. Only the user needs to be defined. The user name and password are provided from the management server during discovery. The user does not need to have root authority. A colon separated list can be used to specify multiple users.
PAGE 182
Rolling Over the Logs The logging information for the CIM Extension is contained primarily in the cxws.log file, created by default in the /tools directory.The cxws.log file rolls over once it becomes more than 100 MB. The information in cxws.log is moved to cxws.log.1. When the logs roll over again, cxws.log.1 is renamed to cxws.log.2 and the information that is in cxws.log is moved to cxws.log.1. The numbering for the files continues sequentially, for example, cxws.log.
PAGE 183
9 Installing the CIM Extension for OpenVMS This chapter describes the following: • ”About the CIM Extension for OpenVMS” on page 161 • ”Prerequisites” on page 161 • ”Installing the CIM Extension for OpenVMS” on page 163 • ”Starting the CIM Extension Manually” on page 164 • ”Finding the Status of the CIM Extension” on page 165 • ”Configuring CIM Extensions” on page 165 • ”Finding the Version of a CIM Extension” on page 168 • ”Stopping the CIM Extension” on page 169 • ”Rolling Over the Log Files” on page 169
PAGE 184
• Supported OpenVMS (Alpha) versions and required ECOs • To verify installed patches, enter the following at the command prompt: $ prod sh prod/full • OpenVMS 7.3.2 (Alpha) OpenVMS (Alpha) 8.2 is also supported. The requirements for OpenVMS 8.2 are listed later in this Prerequisites section. • Mandatory ECOs for OpenVMS 7.3.
PAGE 185
OpenVMS (Alpha) 7.3-2 and DEC-AXPVMS-VMS82A_FIBRE_SCSI-V0100 for OpenVMS (Alpha) 8.2. To verify HBA API support, check the OpenVMS host for the following files in the path specified. $ dir sys$common:[syslib]hba_vms.exe $ dir sys$common:[syslib]hba.
PAGE 186
9. Press Enter when prompted for confirmation by the PCS as shown in the example below: ********** The following product has been selected: HP AXPVMS APPQCIME V5.0 Layered Product Do you want to continue? [YES] *********** The installation is completed with the default values and the APPQCIME process starts. 10.Verify that the SE Agent process starts properly. You should see the following message: CXWS ready to accept connections 11.
PAGE 187
2. Type the following command to start the CIM Extension. $ @sys$common:[opt.appqcime.tools]start The following message displays: STARTING OpenVMS CIME... Finding the Status of the CIM Extension You can check the status of the CIM Extension by entering the following in the sys$common:[opt.appqcime.tools] directory. $ @status The CIM Extension is running when the following message is displayed: CIM Extension is running. Process id :001B0AEE where 001B0AEE is the process ID running the CIM Extension.
PAGE 188
4. Restart the CIM Extension for your changes to take effect. NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. Changing the Port Number The CIM Extension uses port 4673 by default. If the port is already used, follow these steps to change the port the CIM Extension will access: 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.
PAGE 189
Configuring the CIM Extension to Listen on a Specific Network Card Follow these steps to configure the CIM Extension to listen on a specific network card (NIC): 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.parameters file in a text editor, and provide the following line: -on 127.0.0.1,192.168.0.1 NOTE: If you want to configure the CIM Extension to listen on multiple NICs, use a comma to separate multiple addresses. 3. Save the file. 4.
PAGE 190
If you have already added the host to the discovery list (Tools > Storage Essentials > Home > Discovery > Setup) on the management server, you must remove it and then re-add it. You cannot have more than one listing of the host with different ports. Additional Parameters The following table describes additional parameters that can be specified in the cim.extension.
PAGE 191
Where myname is the user name that must be used to discover this OpenVMS host and 1234 is the new port. Stopping the CIM Extension To stop the CIM Extension: 1. Log in to the system as a superuser. 2. Navigate to the following directory: sys$common:[opt.appqcime.tools] Where sys$common:[opt] is the directory in which you installed the CIM Extension. 3. Type: $ @stop to stop the CIM Extension.
PAGE 192
For example, Set LOG_LEVEL to 3 in cxws_native.cfg and restart the CIM Extension to increase the log level to 3. Removing the CIM Extension from OpenVMS This section includes information on removing (uninstalling) the CIM Extension.
PAGE 193
10 Installing the CIM Extension for HP Tru64 UNIX This chapter describes the following: • ”About the CIM Extension for Tru64 UNIX” on page 171 • ”Prerequisites” on page 171 • ”Installing the CIM Extension” on page 173 • ”Starting the CIM Extension Manually” on page 174 • ”How to Determine if the CIM Extension Is Running” on page 175 • ”Configuring CIM Extensions” on page 175 • ”Finding the Version of a CIM Extension” on page 178 • ”Stopping the CIM Extension” on page 179 • ”Rolling Over the Logs” on page 17
PAGE 194
Also, verify the following before you install the CIM Extension: • ”Software Requirements” on page 172 • ”Required Disk Space” on page 172 • ”SNIA HBA API Support” on page 172 Software Requirements NOTE: You do not need to install the FC-HBA shared libraries if you are running Tru64 UNIX version 5.1B-4. If you are running Tru64 UNIX version 5.1B-3 or version 5.1B-2, you must install one of the following SNIA patches to obtain the FC-HBA shared libraries. • For Tru64 UNIX version 5.
PAGE 195
Installing the CIM Extension IMPORTANT: You must install the CIM Extension for Tru64 in the default directory. You can install the CIM Extension for Tru64 one of two ways: • On a Standalone Host - See ”Installing CIM Extension on a Standalone Host” on page 173. • On a Cluster - See ”Installing the CIM Extension on a Cluster” on page 174. Installing CIM Extension on a Standalone Host To install the CIM Extension using CLI: 1. Login as root. 2.
PAGE 196
8. Type the following at the command prompt to find the status of the CIM Extension: /opt/APPQcime/tools/status Installing the CIM Extension on a Cluster The installation of the CIM Extension on a cluster is similar to the installation of the CIM Extension on a standalone node. However, on a cluster it is required to run the install script on only one node of the cluster. By default the install script (tru64_local_install.
PAGE 197
How to Determine if the CIM Extension Is Running You can determine if the CIM Extension is running by entering the following command at the command prompt: # ./status The CIM Extension is running when the following message is displayed: CIM Extension Running: Process ID: 93 where 93 is the process ID running the CIM Extension Configuring CIM Extensions Configuration information is stored in a configuration text file that is read by the CIM Extension on start-up. The file is named cim.extension.
PAGE 198
NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. Changing the Port Number The CIM Extension uses port 4673 by default. If the port is already used, follow these steps to change the port the CIM Extension will access: 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.
PAGE 199
Configuring the CIM Extension to Listen on a Specific Network Card Follow these steps to configure the CIM Extension to listen on a specific network card (NIC): 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.parameters file in a text editor, and provide the following line: -on 127.0.0.1,192.168.0.1 NOTE: If you want to configure the CIM Extension to listen on multiple NICs, use a comma to separate multiple addresses. 3. Save the file. 4.
PAGE 200
If you have already added the host to the discovery list (Tools > Storage Essentials > Home > Discovery > Setup) on the management server, you must remove it and then re-add it. You cannot have more than one listing of the host with different ports. Additional Parameters The following table describes additional parameters that can be specified in the cim.extension.
PAGE 201
• 4673 is the port used by the CIM extension Stopping the CIM Extension To stop the CIM Extension, enter the following at the command prompt in the /opt/APPQcime/tools directory, where /opt is the directory into which you installed the CIM Extension: # ./stop Keep in mind the following: • You must have root privileges to stop the CIM Extension. • When you stop the CIM Extension, the management server is unable to gather information about this host.
PAGE 202
# setld -i Ensure that the required patches listed in the prerequisites are present Removing the CIM Extension from Tru64 This section describes the following: • ”Removing the CIM Extension from a Standalone Host” on page 180 • ”Removing the CIM Extension from a Cluster” on page 180 Removing the CIM Extension from a Standalone Host To remove the CIM Extension for Tru64: 1. Login as root. 2. Go to the /opt/APPQcime/scripts directory, where /opt is the directory into which you installed the CIM Extension.
PAGE 203
11 Installing the CIM Extension for SGI IRIX This chapter describes the following: • ”About the CIM Extension for SGI IRIX” on page 181 • ”Prerequisites” on page 181 • ”Verifying SNIA HBA API Support” on page 182 • ”Installing the CIM Extension” on page 182 • ”Starting the CIM Extension” on page 183 • ”How to Determine if the CIM Extension Is Running” on page 183 • ”Configuring CIM Extensions” on page 183 • ”Stopping the CIM Extension” on page 187 • ”Rolling Over the Logs” on page 187 • ”Removing the CIM Ex
PAGE 204
• IRIX version 6.5.20, path required. Contact customer support for the patch. Network Port Must Be Open The CIM Extension uses port 4673 by default to communicate with the management server. Verify the network port is open. Refer to the documentation accompanying your IRIX host for more information. If you need to use a different port, see ”Permanently Changing the Port a CIM Extension Uses (UNIX Only)” on page 275.
PAGE 205
9. Enter the following to restart the ELF files and to exit the installation program: Inst> quit You must start the CIM Extension for the management server to obtain information about the host. See ”Starting the CIM Extension” on page 183 Starting the CIM Extension The management server can only obtain information from this host when the CIM Extension is running. Keep in mind the following: • You must have root privileges to run the CIM Extension.
PAGE 206
2. Open the cim.extension.parameters file in a text editor, and provide the following line: -port 1234 where 1234 is the new port for the CIM Extension 3. Save the file. 4. Restart the CIM Extension for your changes to take effect. NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. Discovery from HP SIM If you change the port number, you must include the new port number in your discovery.
PAGE 207
4. Restart the CIM Extension for your changes to take effect. NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. The “-on” parameter may include a port specification. In that case, the CIM Extension listens on the indicated port of the indicated NIC, rather than the default port, for example: -on 192.168.2.2:3456 The CIM Extension listens only on the NIC that has the IP address 192.168.2.
PAGE 208
Table 2 Parameters for CIM Extensions Parameter Description -user The user defined in this parameter must be a valid user for the host. Only the user needs to be defined. The user name and password are provided from the management server during discovery. The user does not need to have root authority. A colon separated list can be used to specify multiple users.
PAGE 209
1. Go to the /opt/APPQcime/tools directory. 2. Type the following at the command prompt: # ./start -version You are shown the version number of the CIM Extension and the date it was built, as shown in the following example: CXWS for mof/cxws/cxws-irix.mof CXWS version x.x.x.x, built on Fri 12-March-xxxx 12:29:49 by dmaltz where • x.x.x.x is the version of the CIM Extension • xxxx is the year.
PAGE 210
3. Enter the following at the Inst command prompt: Inst> remove 4. When you are asked which subsystem you want to remove, enter the following: APPQcime 5. To begin the removal of the CIM Extension, enter the following at the Inst command prompt: Inst> go The CIM Extension is removed from IRIX. 6.
PAGE 211
12 Installing the CIM Extension for Sun Solaris This chapter describes the following: • ”About the CIM Extension for Solaris” on page 189 • ”Prerequisites” on page 189 • ”Verifying SNIA HBA API Support” on page 190 • ”Installing the CIM Extension” on page 191 • ”Starting the CIM Extension Manually” on page 192 • ”How to Determine if the CIM Extension Is Running” on page 193 • ”Configuring CIM Extensions” on page 193 • ”Stopping the CIM Extension” on page 197 • ”Rolling Over the Logs” on page 197 • ”Removing
PAGE 212
1. SUNWlibC - Sun Workshop Compilers Bundled libC 2. SUNWlibCf - SunSoft WorkShop Bundled libC (cfront version) 3. SUNWlibCx - Sun Workshop Bundled 64-bit libC IMPORTANT: Verify you have the latest patches installed. The patches can be obtained from the Sun Microsystems Web site at http://www.sun.com. You must have the following space: • CIM Extension - The CIM Extension requires 90 MB of disk space. • Logs - Make sure you have 100 MB for log files.
PAGE 213
Driver Information for Verifying SNIA Emulex Adapters The SNIA Library comes from a separate package HBAnyware. If you installed SNIA Emulex adapter, you can find its library by entering the following at the command prompt: # more /etc/hba.conf The following is displayed: com.emulex.emulexapilibrary /usr/lib/libemulexhbaapi.so com.emulex.emulexapilibrary /usr/lib/sparcv9/libemulexhbaapi.so Driver Information for QLogic Adapters The SNIA HBA package comes from a separate package QLSDMLIB.
PAGE 214
• The server must be running sh, ksh or bash shell. C shell is not supported. To install the CIM Extension: 1. Login as root. 2. Go to the Solaris directory on the CIM Extension CD-ROM by entering the following at the command prompt: # cd /cdrom/cdrom0/Solaris where /cdrom/cdrom0 is the name of the CD-ROM drive 3. Enter the following at the command prompt: # pkgadd -d APPQcime.pkg APPQcime The APPQcime package is added. 4.
PAGE 215
How to Determine if the CIM Extension Is Running You can determine if the CIM Extension is running by entering the following command at the command prompt: # ./status The CIM Extension is running when the following message is displayed: CIM Extension Running: Process ID: 93 where 93 is the process ID running the CIM Extension Configuring CIM Extensions Configuration information is stored in a configuration text file that is read by the CIM Extension on start-up. The file is named cim.extension.
PAGE 216
NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. Changing the Port Number The CIM Extension uses port 4673 by default. If the port is already used, follow these steps to change the port the CIM Extension will access: 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.
PAGE 217
Configuring the CIM Extension to Listen on a Specific Network Card Follow these steps to configure the CIM Extension to listen on a specific network card (NIC): 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.parameters file in a text editor, and provide the following line: -on 127.0.0.1,192.168.0.1 NOTE: If you want to configure the CIM Extension to listen on multiple NICs, use a comma to separate multiple addresses. 3. Save the file. 4.
PAGE 218
If you have already added the host to the discovery list (Tools > Storage Essentials > Home > Discovery > Setup) on the management server, you must remove it and then re-add it. You cannot have more than one listing of the host with different ports. Additional Parameters The following table describes additional parameters that can be specified in the cim.extension.
PAGE 219
Combining Start Commands You can also combine the -users and -port commands as follows: ./start -users myname -port 1234 or ./start -port 1234 -users myname where myname is the user name that must be used to discover this Solaris host 1234 is the new port Stopping the CIM Extension To stop the CIM Extension, enter the following at the command prompt in the /opt/APPQcime/tools directory, where /opt is the directory into which you installed the CIM Extension: # .
PAGE 220
3. Enter the following at the command prompt: # pkgrm APPQcime 4. Enter y when you are asked if you want to remove the CIM Extension. When you see the following message, the CIM Extension has been removed: Removal of was successful.
PAGE 221
13 Installing the CIM Extension for Microsoft Windows This chapter describes the following: • ”About the CIM Extension for Windows” on page 199 • ”Verifying SNIA HBA API Support” on page 199 • ”Upgrading a Host with the Latest CIM Extension” on page 201 • ”Installation Steps” on page 202 • ”Installing the CIM Extension Using the Silent Installation” on page 203 • ”Configuring CIM Extensions” on page 203 • ”Rolling Over the Logs” on page 205 • ”Removing the CIM Extension from Windows” on page 206 NOTE: This
PAGE 222
• If you have not installed the CIM Extension - Go to the Windows\tools directory on the CIM Extension CD-ROM. • If you have installed the CIM Extension - Go to the \CimExtensions\tools directory on the host running the CIM Extension. 2. Enter the following at the command prompt: hbatest.exe The program lists the name and number for all HBA’s that support the SNIA HBA API. 3.
PAGE 223
C:\Program Files\IBM FASt MSJ\ql2xhai2.dll Driver Information for Verifying QLogic Adapters This section provides information for verifying QLogic adapters. If you have QLogic Adapters: When you install the SNIA HBA, it either came with the driver or SANsurfer, the registry setting is most likely in the following location, which varies by release: HKEY_LOCAL_MACHINE\SOFTWARE\SNIA\HBA\QL2XXX Newer drivers points to C:\WINNT\system32\ql2xhai2.dll, but they also have system32\qlsdm.dll available.
PAGE 224
Do one of the following: • For hosts that are not in the “Default” discovery group - Restart AppStorManager, which is the service for the management server. IMPORTANT: If you do Get Details/Discovery Data Collection immediately after a Windows host is upgraded without restarting the management server, you will have missing/incorrect data. You will also have missing and/or incorrect data until you finish the steps in this section. To avoid having to restart AppStorManager, see the following options.
PAGE 225
• Disk Space Required • Disk Space Available 6. Do one of the following: • Click Install if you agree with the pre-installation summary. • Click Previous if you want to modify your selections. The CIM Extension is installed. 7. When you have been told the installation has been successful, click Done to quit the installation. IMPORTANT: Keep in mind that the CIM Extension automatically starts when the system is restarted.
PAGE 226
1. Go to the [Installation_Directory]\conf directory. 2. Open the cim.extension.parameters file in a text editor, and provide the following line: -port 1234 where 1234 is the new port for the CIM Extension 3. Save the file. 4. Restart the CIM Extension for your changes to take effect. NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted.
PAGE 227
Table 4 Parameters for CIM Extensions Parameter Description -user The user defined in this parameter must be a valid user for the host. Only the user needs to be defined. The user name and password are provided from the management server during discovery. The user does not need to have root authority. A colon separated list can be used to specify multiple users.
PAGE 228
NOTE: If you want to configure the CIM Extension to listen on multiple NICs, use a comma to separate multiple addresses. 3. Save the file. 4. Restart the CIM Extension for your changes to take effect. NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. The “-on” parameter may include a port specification.
PAGE 229
3. From the Currently installed programs list, select Windows CIM Extension. 4. Click the Change/Remove button. 5. When you are told the product is about to be uninstalled, click Uninstall. 6. When the program is done with removing the product, click Done. 7. It is highly recommended you reboot the host. Storage Essentials 5.
PAGE 230
208 Installing the CIM Extension for Microsoft Windows
PAGE 231
14 Discovering Applications, Backup Servers and Hosts IMPORTANT: Information about Systems Insight Manager (SIM), such as discovery instructions, are for SIM version 5.0.
PAGE 232
• Make sure you have reviewed the table, Table 2 on page 1 to make sure you are at the correct step. • (Discovery from HP SE only) If your license lets you discover UNIX and/or Linux hosts, the Test button for discovery reports SUCCESS from any UNIX and/or Linux hosts on which the management server can detect a CIM Extension. The CIM Extension must be running. The management server reports “SUCCESS” even if your license restricts you from discovering certain types of hosts.
PAGE 233
IMPORTANT: Complete the steps in this section if you want to discover backup applications, such as Veritas NetBackup and HP Data Protector, on Windows, HP-UX, and Linux. See the Support Matrix for more information on supported platforms. Modify the jboss.properties file in the %JBOSS4_DIST%\server\appiq\conf directory on the management server as described in the following steps: 1. Confirm that a CIM Extension is installed on the server on which Veritas NetBackup or HP Data Protector is installed.
PAGE 234
8. You can configure the management server to obtain information about your master backup servers at a set interval. See the topic, “Scheduling Backup Collection for Master Servers” in the HP SE User Guide for more information about collectors. Step B - Set Up Discovery for Hosts You can discover your hosts by using two methods: Discovery from HP SIM 1. Discover your hosts. Refer to the HP SIM documentation for more information. See Table 5 on page 212. 2. Run Discovery Data Collection.
PAGE 235
Use the following table as a guideline for SE discovery: Table 6 Making the Management Server Aware of Hosts (SE Discovery Only) Step Description 1 If several of the elements in the same domain use the same name and password, click the Set Default User name and Password link and provide up to three user names and passwords. 2 To enter an IP address range, click the IP Ranges tab and then the Add Range button. If necessary, enter a user name and password for the devices in the range.
PAGE 236
IMPORTANT: If you want to use the HP SIM discovery mechanism, you must provide HP SIM with the credentials required by HP SE for HP SE to be successful. domain_name\username where • domain_name is the domain name of the element • username is the name of the account used to access that element • You can configure the management server to obtain information about your master backup servers at a set interval.
PAGE 237
• domain_name is the domain name of the element • username is the name of the account used to access that element f. In the Password (Optional) field, type the password corresponding to the user name entered in the User Name field. g. Type the password from the previous step in the Verify Password field. h. In the Comment field, type a brief description of the servers. For example, Servers in Marketing. i. Click OK. j. Repeat steps b through i until all of the IP ranges have been entered. k.
PAGE 238
5. To start discovering elements on the network, click the Start Discovery button on the IP Addresses tab. The software discovers the IP addresses selected. During discovery, the following occurs: • The software changes the status light from green to orange. • You are shown the Log Messages page. To view the status of discovery, click Discovery > View Logs. Discovery is complete when the software displays the DISCOVERY COMPLETED message in the Log Messages field.
PAGE 239
The Always option prevents this message from being displayed every time you access System Manager, Capacity Manager, and Performance Manager. The elements are shown connected to each other in the topology. If you see a question mark above a host, the management server cannot obtain additional information about that element. If a switch has more than one connection to an element, the number of connections is displayed above the line linking the switch and the element.
PAGE 240
connected through a switch and storage system. When you Get Details/Discovery Data Collection for Discovery Group 1, you also obtain details from the switch and storage system. • If the management server unable to obtain information from a UNIX host during Get Details/Discovery Data Collection as a result of a CIM Extension hanging, the management server places the access point where the CIM Extension is located in quarantine.
PAGE 241
Then, set up the configurations for your applications on the management server. Some applications may require you to provide additional discovery information about the application. Finally, perform discovery and then obtain Get Details/Discovery Data Collection. Get Details and Discovery Data Collection takes some time. Perform this step when the network is not busy. More details about the steps mentioned above are provided later.
PAGE 242
entering the following at the command prompt: lsnrctl status. If the listener is not running you can start it by typing lsnrctl start on command line. • Make sure you have all the necessary information before you begin the installation. Read through the following steps before you begin. To create the Oracle user for management server: 1.
PAGE 243
Keep in mind the following: • Before you remove the APPIQ_USER account for an Oracle instance, make sure no processes are running APPIQ_USER for that Oracle instance. The management server uses APPIQ_USER to obtain information about the Oracle database. For example, a process would be using APPIQ_USER if someone was using Performance Manager to view monitoring statistics about that Oracle instance.
PAGE 244
• Discovery from HP SE - Select Tools > Storage Essentials > Home > Discovery > Setup. Then, click the Applications tab. • Discovery from HP SIM - Select Options > Protocol Settings > Storage Essentials > Global Application Discovery Settings. The TNS Listener Port setting applies to all Oracle instances you monitor. 2. To assign a new port, click the Create button for the Oracle Information table. 3. Type the new port number and click OK. 4. If necessary, click the button to remove the old port number.
PAGE 245
The port can be found in the following code: LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0)) ) ) ) 6. Select ORACLE from the Database Type menu. 7. Click OK. Discovering Oracle Clusters Perform the following steps for each node in the cluster: 1. Install the CIM Extension on each node in the cluster. 2. Create the appiq_user account on each node in the cluster.
PAGE 246
in the following directory on the host of the monitored database. Do not look for the listener.ora file on the management server for this information. %ORA_HOME%\network\admin\listener.ora d. In the Server Name field, type the Oracle System Identifier (SID) of the Oracle database you want to monitor. e. In the Port Number field, type the monitored port. If you are not sure of the monitored port, check the listener.ora file of the monitored database application. You can find the listener.
PAGE 247
1. Open SQL Server Enterprise Manager (Start Menu > Programs > Microsoft SQL Server > Enterprise Manager). 2. Expand the tree-control until you can see your server. 3. Right-click the server name. The SQL Server Properties (Configure) window appears. 4. Click the Security tab. 5. For “Authentication,” select SQL Server and Windows. 6.
PAGE 248
NOTE: You can use a remote SQL Server isql to run this script. 4. Type the SQL Server instance name, which must be visible to the client, as the first input when running the script. The script prompts you for the name of the SQL Server on which to create user for SQL Server management packages and the password of the SA account. This script does the following in order: • Creates the APPIQ_USER account.
PAGE 249
To add information for discovering a SQL server: 1. Do one of the following: • Discovery from HP SE - Select Tools > Storage Essentials > Home > Discovery > Setup. Then, click the Applications tab. • Discovery from HP SIM - Select Options > Protocol Settings > Storage Essentials > System Application Discovery Settings. To select a target, you must have at least one element designated as a server, workstation or desktop.
PAGE 250
d. The resulting window shows you the TCP/IP port your SQL server uses. Provide this port number in the Port Number field on the management server. 7. Select SQLSERVER from the Database Type menu. 8. Click OK. IMPORTANT: Perform Get Details/Discovery Data Collection for your inputs to take effect. See ”Step 3 - Discovering Applications” on page 233.
PAGE 251
element designated as a server, workstation or desktop. If you see the message, “No Targets Currently Selected,” change your element from unknown to either a server, workstation or desktop. Refer to the documentation for HP Systems Insight Manager. Select a target, and then, click Run Now. 2. In the Database Information table, click the button, corresponding to the SQL Server instance you do not want the management server to monitor. 3.
PAGE 252
• To run the script on IBM AIX, SGI IRIX, or Sun Solaris, log into an account that has administrative privileges, mount the CIM Extensions CD-ROM (if not auto-mounted), and go to the /DBIQ/sybase/unix directory by typing the following: # cd /cdrom/cdrom0/DBIQ/sybase/unix where /cdrom/cdrom0 is the name of the CD-ROM drive • To run the script on Microsoft Windows, go to the \DBIQ\sybase\win directory on the CIM Extensions CD-ROM. IMPORTANT: You must complete the following steps. 2.
PAGE 253
• To run the script on IBM AIX, SGI IRIX, or Sun Solaris, log into an account that has administrative privileges, mount the CD-ROM (if not auto-mounted), and go to the /DBIQ/sybase/unix directory by typing the following: # cd /cdrom/cdrom0/DBIQ/sybase/unix where /cdrom/cdrom0 is the name of the CD-ROM drive • To run the script on Microsoft Windows, go to the \DBIQ\sybase\win directory on the CD-ROM. IMPORTANT: You must complete the following steps. 2. Verify you have the password to the SA user account.
PAGE 254
8. Click OK. IMPORTANT: Perform Get Details/Discovery Data Collection for your inputs to take effect. See ”Step 3 - Discovering Applications” on page 233. Deleting Sybase Information If you do not want the management server to monitor a Sybase instance, you can remove its information, as described in the following steps: 1. Do one of the following: • Discovery from HP SE - Select Tools > Storage Essentials > Home > Discovery > Setup. Then, click the Applications tab.
PAGE 255
1. Do one of the following: • Discovery HP SE - Select Tools > Storage Essentials > Home > Discovery > Setup. Then, click the Applications tab. • Discovery HP SIM - Select Options > Protocol Settings > Storage Essentials > Global Application Discovery Settings. The information you provide for the primary domain controller and backup domain controller apply to all Microsoft Exchange servers you discover. 2. In the Microsoft Exchange Configuration section, click the Edit button. 3.
PAGE 256
• (Discovery from HP SE Only)Obtain topology information about the application (”Step B (Discovery from HP SE Only) Obtain the Topology” on page 235) • Perform Get Details/Discovery Data Collection (”Step C - Obtain Discovery Data Collection or Get Details” on page 235) Keep in mind the following: • This section assumes you have already set up the discovery configurations for your applications as described in ”Step 2 - Setting Up Discovery for Applications” on page 218.
PAGE 257
Step B - (Discovery from HP SE Only) Obtain the Topology IMPORTANT: The following steps apply only to discovery from SE. The user interface in Storage Essentials may load slowly while the topology is being recalculated. It may also take more time to log into the management server during a topology recalculation. To obtain the topology: 1. Click Tools > Storage Essentials > Home > Discovery > Topology. The discovered elements are selected. 2. Click the Get Topology button.
PAGE 258
• You can quarantine elements to exclude them from Discovery Data Collection/Get Details. See ”Placing an Element in Quarantine” on page 114 for more information. Let us assume you want to discover all the elements in a discovery group, except for one. Perhaps the element you want to quarantine is being taken off the network for maintenance. You can use the quarantine feature to exclude one or more elements from discovery.
PAGE 259
You can use discovery groups to break up getting Get Details. For example, instead of Get Details for all of the elements, you could specify that the management server gets the element details for only the elements in Discovery Group 1, thus, saving you time. You add an element to a discovery group by modifying the properties used to discover the element. See ”Modifying the Properties of a Discovered Address” on page 101. 3. Click the Get Details button.
PAGE 260
Keep in mind the following: • The hosts should recognize the management server by name, as a reverse look-up is required by operating system security as well as Microsoft Exchange. • Make sure you provide just the user name and not the domain name when discovering Microsoft Exchange servers. To provide information about the Microsoft Exchange servers: 1. Do one of the following: • Discovery from HP SIM - Click Options > Protocol Settings > Storage Essentials > Global Application.
PAGE 261
• Change the password in all database applications before you change the password through the user interface. The passwords must also match. • You must enter a password in the Password and Verify Password fields. To change the password: 1. Select Options > Protocol Settings > Storage Essentials > Global Application Discovery Settings. 2. Click the Change Password button. 3. Verify you have already changed the password of the databases listed on this page. 4. Type a new password in the Password field.
PAGE 262
The management server displays in the drop-down menu only hosts that are running a CIM Extension version 3.5 or later and have access to the corresponding Engenio storage system. NOTE: You can always change the proxy host by returning to this page or by going to the Properties tab for an Engenio storage system. Double-click the Engenio storage system in System Manager. Click the Properties tab. Then, click the Browse button on the Properties tab. 10.Saving the proxy host may take time.
PAGE 263
15 Managing Security IMPORTANT: Depending on your license, role-based security may not be available. See the “List of Features” to determine if you have access to role-based security. The “List of Features” is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
PAGE 264
IMPORTANT: Roles only apply to features and elements in HP Storage Essentials. For example, assume you assigned a user to the Help Desk role in Storage Essentials. That user will have “view only” privileges only in Storage Essentials.
PAGE 265
• Users created in HP Systems Insight Manager are automatically placed in the SIMViewOnly role. This role does not allow users to access any of the features listed in Table 7 on page 242. See ”Adding Users” on page 248 for more information. • Users with access to Global Reporter can view all the elements throughout the enterprise, including those on the server running Global Reporter. Grant access to Global Reporter only to those, who should be allowed to view all elements.
PAGE 266
Table 8 Default Role Privileges with Elements (continued) Role Application Host Switch Storage System Tape Library Others Application Administrator Full Control View View View View View Help Desk View View View View View View SIMViewOnly View View View View View View By selecting one of the following options, users belonging to that role are restricted access: • Full Control - Lets you view and modify the record for the element (Asset Management tab) and perform provisioning if
PAGE 267
would have access to hosts and switches because those elements are listed in at least one of the organizations. Organizations can also contain other organizations. An organization contained within another is called a child. The organization containing a child organization is called a parent. In the following figure, the BostonWebHosts organization contains two child organizations, BostonWebHost_Windows and BostonWebHost_Solaris. BostonWebHosts is a parent because it contains two organizations.
PAGE 268
• US East Coast Figure 2 Children in Multiple Organizations When you remove an element from an organization, users belonging to that organization or to one of its parents can no longer access that element if it is not a member of any other organization. For example, assume an element named MyHost was not only a member of BostonWebHost_Solaris, but also had mistakenly became a member of BostonWebHost_Windows.
PAGE 269
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.
PAGE 270
• ”Viewing the Properties of an Organization” on page 252 Adding Users To access the management server, users must enter a user name and password. belonging to the Domain Administrator roleKeep in mind the following: • Only users belonging to the Domain Administrator role can add users. • The user name and password should be alpha-numeric. They cannot exceed more than 256 characters. The user name cannot begin with a number.
PAGE 271
9. To enable users access to features in Storage Essentials, assign the user to a different role by doing the following: a. Click the Edit button ( ) corresponding to the user account you want to modify. b. To change the role assign the user account, select a new role from the Role drop-down menu. If you don’t find any roles that fit your needs, you can create a new one, as described in ”Adding Roles” on page 253. c. Click OK.
PAGE 272
The Everything organization is the default organization that lets users access all current and future elements. 11.Click OK. Deleting Users Keep in mind the following: • You cannot delete the admin account. • Only users belonging to the Domain Administrator role can delete users. To delete a user account: 1. Access Storage Essentials through one of the menu options, such as Options > Storage Essentials > Email Settings. 2. In the upper-right corner, select Security > Users. 3.
PAGE 273
3. When you are done with your modifications, click the Save Changes button. Modifying Your User Preferences Use the User Preference tab to modify your user preferences for System Manager, Element Topology, and Event Manager. The User Preference tab controls what is displayed for your user account. To access the User Preferences tab: 1. Click the name of your account in the upper-left corner of Storage Essentials. Figure 4 Accessing the User Preferences Tab 2. Click the User Preferences tab.
PAGE 274
Table 9 Changing User Preferences for Event Manager (continued) If you want... Do the following... Change the severities to be included Select a severity level you want displayed in Event Manager from the Severities to be Included drop-down menu. Change the element types to be included Select the element types you want to be included from the Element types to be included drop-down menu. Events from these elements are displayed in Event Manager.
PAGE 275
Viewing the Properties of an Organization You can quickly determine which elements a user can access by viewing the properties of the user's organization. Only users belonging to the Domain Administrator can view the properties of an organization. 1. Access Storage Essentials through one of the menu options, such as Options > Storage Essentials > Email Settings. 2. In the upper-right corner, select Security > Users. 3. In the Organization column, click the name of a organization. 4.
PAGE 276
3. Click the New Role button. 4. In the Role Name field, type a name for the role. For example: Quality Assurance. The name can contain spaces, but it cannot be longer than 256 characters. 5. In the Description field, type a description for the role. For example: Role for those in quality assurance. You cannot type more than 1024 characters in the Description field. 6.
PAGE 277
2. In the upper-right corner, select Security > Roles. 3. Click the Edit button ( ). 4. To edit the name of the role, change the name In the Role Name field. The name can contain spaces, but it cannot be longer than 256 characters. 5. To edit the description of the role, change the description in the Description field. You cannot type more than 1024 characters in the Description field. 6. To change the access level, change the options selected in the table.
PAGE 278
• ”Editing Organizations” on page 257 • ”Deleting an Organization” on page 258 • ”Removing Members from an Organization” on page 259 • ”Filtering Organizations” on page 259 Adding an Organization You can create new organizations to restrict access to certain elements. For example, assume you do not want the help desk to have access to elements belonging to a certain group. You could create an organization that does not allow access to those elements.
PAGE 279
added to the Organization Members pane. If you would like to add storage volumes to the organization, see the topic ”Adding Storage Volumes to an Organization” on page 257. 8. To add organizations, select the Organizations node. Then, in the right-hand pane, select the organizations you would like to add by clicking the appropriate check boxes. Next, click the Add button and the selected organizations are added to the Organization Members pane.
PAGE 280
When elements are removed from an organization, users belonging only to that organization are no longer able to access the removed elements. Keep in mind the following: • Depending on your license, role-based security may not be available. See the “List of Features” to determine if you have access to role-based security. The “List of Features” is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
PAGE 281
Keep in mind the following: • You cannot remove the Everything organization, which is the default organization. • You cannot delete an organization that contains a user, who belongs to no other organizations. For example, assume you create an organization named Org1 that contains two users: User1 and User2. User1 belongs to two other organizations, while User2 only belongs to the organization you just created.
PAGE 282
organization contains two organizations: “Windows Hosts” and “Solaris Hosts.” If you want to view elements only in “Windows Hosts” and not in “Solaris Hosts” organizations, you could use the filtering feature to activate only the “Windows Hosts” organization. Keep in mind the following: • Users assigned to the “admin” account cannot filter organizations because the “admin” account belongs to the Everything organization by default.
PAGE 283
Changing the Password of System Accounts The management server uses the following accounts to access and manage the database for the management server. You should change the passwords to these accounts to prevent unauthorized access. • SYS - Used for the management server database creation and upgrade. Default password: change_on_install • SYSTEM - Used for management server database creation and upgrade, in addition to database import, export and re-initialization.
PAGE 284
d. Stop the HP Systems Insight Manager service so that it cannot access the database. It is very important that the HP Systems Insight Manager service does not access the database before you are finished with changing the password for the database. 2. Stop the AppStorManager service. 3. To access the database utility, go to the %MGR_DIST%\Tools\dbAdmin directory on the management server and double-click dbAdmin.bat, where [Install_Dir] is the directory into which you installed the management server. 4.
PAGE 285
Step 1 - Configure the Management Server to Use Active Directory or LDAP You must modify the login-handler.xml file if you want to use Active Directory/LDAP. How you modify the login-handler.xml file depends on whether you plan to use LDAP or Active Directory.
PAGE 286
2. In the login-handler.xml file, comment out the section that contains com.appiq.security.server.BasicLoginhandler, which enables internal authentication mode. Only one login handler is allowed at a time. 3. Comment out the Default tag as follows: 4.
PAGE 287
IMPORTANT: AD servers are not case sensitive for user names so changing this tag to “true” for AD authentication is not recommended. The login-handler.xml file contains two sets of tags: one for Active Directory and one for LDAP. Make sure you change the value of the tags that are children of the tag. 9. Provide the Active Directory search base in which you want the management server to look up AD/LDAP user attributes.
PAGE 288
v> --> false false false CN=$NAME$,OU=Engineering,DC=HP,OU=US,DC=COM displayName mail When you are do
PAGE 289
NOTE: If you want to go back and forth between internal and external (AD/LDAP) authentication, rename the login-handler.xml file before you modify it. This way you can easily switch back to internal authentication by changing the file name back to login-handler.xml. b. In the login-handler.
PAGE 290
The login-handler.xml file contains two sets of tags: one for Active Directory and one for LDAP. Make sure you change the value of the tags that are children of the tags. 8. Provide the LDAP search base in which you want the management server to look up AD/LDAP user attributes. Allow no spaces between commas and put in all components of fully qualified domain name, for example, hds.usa.com would be DC=hds,DC=usa,DC=com.
PAGE 291
com.appiq.security.server.LdapLoginHandler LDAP IP address or DNS name of LDAP server