HP Storage Essentials V5.00.01 installation guide (T4283-96011, January 2006)

ManualsBrandsHP ManualsSoftwareHP Storage Essentials SRM Provisioning Manager 50 MAP Tier-2 LTU

Table Of Contents

*12345-67890*

T4283-96011

Storage Essentials 5.00.01 Installation Guide

Part number: T4283-96011

First edition: January 2006

Summary of content (312 pages)

PAGE 1
HP Storage Essentials 5.00.
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
Upgrading the Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1 - Stop AppStorManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2 - Export Your Existing Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3 - Verify If You Need to Install the Oracle 9.2.0.6.0 Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 5
Saving Discovery Settings to a File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Discovery from HP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Discovery from HP SE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Step 1 - Discover Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
Discovering 3PAR Storage Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovery from HP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovery from HP SE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovering EMC Solutions Enabler 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
Discovery from HP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Discovery from HP SE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Deleting Elements from the Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Discovery from HP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
Stopping the CIM Extension . . . . . . . . . . . . . . . . How to Determine if the CIM Extension Is Running Fulfilling the Prerequisites. . . . . . . . . . . . . . . . . . Rolling Over the Logs . . . . . . . . . . . . . . . . . . . . Removing the CIM Extension from AIX. . . . . . . . . ................................. ................................. ................................. ................................. .................................
PAGE 9
8 Installing the CIM Extension for SUSE and Red Hat Linux . . . . . . . . . . . . . . . . . 139 About the CIM Extension for Red Hat Linux Advanced Server and SUSE Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying SNIA HBA API Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 10
on a Cluster Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 10Installing the CIM Extension for HP Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . 157 About the CIM Extension for Tru64 UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements . . . . .
PAGE 11
Verifying SNIA HBA API Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Driver Information for Verifying SNIA Emulex Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . Driver Information for QLogic Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Driver Information for AMCC/JNI Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 12
Monitoring Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step A - Create the APPIQ_USER Account for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the APPIQ_USER Account for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step B - Provide the TNS Listener Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step C - Set up Discovery for Oracle 10g . . . . . . . . . . . . . . .
PAGE 13
Event Manager Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings for Slow Systems Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Properties of a Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Properties of an Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Roles . . . . . . . . . . . . . . . . . . . . .
PAGE 14
Increasing the Time-out Period and Number of Retries for Switches in Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . “Connection to the Database Server Failed” Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCOM Unable to Communicate with Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplicate Listings for Brocade Switches in Same Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 15
Known Device Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 “mailbox command 17 failure status FFF7” Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 ”Process Has an Exclusive Lock” Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 16
xvi
PAGE 17
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 18
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 19
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 20
xx
PAGE 21
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 Storage Essentials Connector. It highly recommended you follow the steps outlined in Table 2 on page 1.
PAGE 22
Table 2 Roadmap for Installation and Initial Configurations (continued) Step Description Where to Find 4 Browse to System Insight Manager. See ”Step 6 - Browse to HP Systems Insight Manager Home Page” on page 17. 5 Configure Internet Explorer Settings. See ”Step 7 - Configure Microsoft Internet Explorer Settings” on page 18. 6 Import a Storage Essentials License. See ”Step 8 - Import a Storage Essentials License” on page 19. 7 Perform discovery for switches, filers, and storage systems.
PAGE 23
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 111.
PAGE 24
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 223.
PAGE 25
• 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 26
• 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 27
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 28
• 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 4 - Install HP Systems Insight Manager” on page 14. After you install HP SIM by using the directions provided in the HP SIM documentation, continue the installation steps with ”Step 5 - Install the HP Storage Essentials Connector” on page 16.
PAGE 29
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. d.
PAGE 30
• Install the database on the computer 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. This screen requires the user to select the check box and click Next. Once you clicked Next, a command window appears. The command window will close itself once the operation running inside the command window completes.
PAGE 31
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 32
Step 3 - Install the Management Server IMPORTANT: Install HP SIM and the SE 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 33
• 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. When the installation is complete, you are shown the directory containing the management server and the machine ID, which is used by technical support for licenses. You do not need to write down the machine ID.
PAGE 34
Step 4 - 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. After you install HP SIM by using the directions provided in the HP SIM documentation, continue the installation steps with ”Step 5 - Install the HP Storage Essentials Connector” on page 16.
PAGE 35
• 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. The user name and password you provide is for the user that is installing HP SIM, and this user must have administrative privileges.
PAGE 36
Step 5 - Install the HP Storage Essentials Connector The HP Storage Essentials (SE) Connector lets you communicate with HP Systems Insight Manager. Install the SE Connector on the same server running SE. To install the SE Connector: 1. Make sure HP SE is not running. You can stop the service for HP SE (AppStorManager) from the Services window on the server where you installed Storage Essentials. 2. Make sure the HP Systems Insight Manager process is running. 3.
PAGE 37
e. Stop the AppStorManager service. AppStorManager cannot be running when you use Database Admin Utility. f. Use the Database Admin Utility to change the SIM_MANAGER password in the Oracle database, as mentioned in ”Using the Database Admin Utility to Change the SIM_MANAGER Password” on page 17. IMPORTANT: You must provide the same SIM_MANAGER password for the mxpassword command and the Database Admin Utility.
PAGE 38
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. Supply the login for the user that was used to install HP SIM. Step 7 - Configure Microsoft Internet Explorer Settings Configure the Internet Explorer settings that Systems Insight Manager and Storage Essentials need to function properly.
PAGE 39
b. Click the Settings button in the Temporary Internet section. c. Select the Microsoft default of Automatically. Make sure the option, Every visit to the page, is not selected, since this setting has been known to cause problems. 5. Set encrypted page settings and security options: a. From Microsoft Internet Explorer, select Tools > Internet Options > Advanced > Security > Do not save encrypted pages to disk. b. Use the Microsoft default of unchecked. Checking this option causes the problem.
PAGE 40
In Navisphere add the following to the privilege user section: SYSTEM@name_of_my_management_server SYSTEM@IP_of_my_management_server where • name_of_my_management_server is the DNS name of the computer running the management server software • IP_of_my_management_server is the IP address of the computer running the management server software Removing the Management Server This section describes how to remove the management server. Refer to the appropriate section for your operating system.
PAGE 41
• %ORA_HOME%\rman if applicable The above deletes the database instance. Upgrading the Management Server Keep in mind the following: • Refer to the release notes for late breaking information about upgrading the management server. • Complete the upgrade and its subsequent steps in one session, which may take several hours depending on your network configuration. Completing the steps over several sessions will result in incomplete data until all steps have been completed.
PAGE 42
• All files in %MGR_DIST%\JBossandJetty\server\appiq\remoteScripts - Used in System Manager. • All files and subdirectories in %MGR_DIST%\JBossandJetty\server\appiq\policies Used in Policy Manager. • All files and subdirectories in %MGR_DIST%\JBossandJetty\server\appiq\fsrm Used in File System Viewer. • All files and subdirectories in %MGR_DIST%\JBossandJetty\server\appiq\reports Used in Reporting. • %MGR_DIST%\Cimom\bin\runcim.sh • %MGR_DIST%\Cimom\config\cimomlog4j.
PAGE 43
• OracleOraHome92SNMPPeerMasterAgent • OracleOraHome92TNSListener • OracleServiceAPPIQ NOTE: Before you change the service startup types, make note of the services that are set to automatic, as you will need to restore the service startup settings when you are done with installing the patch. 2. Reboot the server. 3. Insert the Database Patch CD into the CD-ROM drive. 4.
PAGE 44
1. Make sure OracleOraHome92TNSListener and OracleServiceAPPIQ are running before you begin the upgrade of the management server. 2. Make sure AppStorManager is stopped before you begin the upgrade. 3. If you installed the Oracle 9.2.0.6.0 Patch as described in “Step 4 - Install the Oracle 9.2.0.6.0 Patch if Necessary” on page 43, export the database again. See ”Step 2 - Export Your Existing Database” on page 22 for information on how to export your database. 4.
PAGE 45
• Cisco, QLogic, or CNT switches supported through SMI-S • Elements discovered in builds earlier than 4.0: • CNT switches • HP XP storage systems • HP EVA storage systems • Sun 6920 storage systems HP SIM If you are only deleting elements discovered through SMI-S, you only need to delete them in HP SIM. If you are deleting elements not discovered through SMI-S, you must delete them from HP SIM and from HP SE. 1. To remove elements from the SIM database: a. Click Systems in the left pane. b.
PAGE 46
• Discovery from HP SE - Click Tools > Storage Essentials > Home. Then, click Discovery > Details in the upper-right corner. Click Get Details. Step 11 - Run the Virtual Application Restoration Script The virtual application restoration script restores the virtual applications on the hosts the management server has discovered: 1. Go to the %MGR_DIST%\install\upgrade directory. 2. Run the VirtualAppUpgradePost.pl script, as shown in the follow example: perl VirtualAppUpgradePost.
PAGE 47
The text should now appear as follows: LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.10.1)(PORT = 1521)) ) ) ) f. Save the file and exit. g. Start the listener service for Oracle (OracleOraHome92TNSListener). h. Start AppStorManager. 2.
PAGE 48
28 Installing the Management Server on Microsoft Windows
PAGE 49
3 Discovering Filers, 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 50
• ”Step 1 - Discover Switches” on page 45 • ”Step 2 - Discover Storage Systems, Filers and Tape Libraries” on page 67 • ”Step 3 (Discovery from HP SE Only) - Build the Topology” on page 89 • ”Step 4 - Discovery Data Collection or Get Details” on page 94 • ”Managing McDATA and EMC Connectrix Switches” on page 99 • ”Assigning a File Extension in Netscape 7” on page 101 • ”Filtering Discovery Groups” on page 102 • ”Moving Elements to Another Discovery Group” on page 102 • ”Placing an Element in Quarantine” on
PAGE 51
• 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. The entry with the old user name is not removed from HP SE. This is also true for password modification. Unless removed, the invalid entry is included in Discovery from HP SE.
PAGE 52
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, filers and tape libraries consists of several steps: 1. Discover your switches by using HP Systems Insight Manager.
PAGE 53
• 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 54
Enabler version 5.1 requires additional steps for discovery. See ”Discovering EMC Solutions Enabler 5.1” on page 71 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. To make the management server aware of elements on your network follow the steps for discovery outlined in one of the following tables: • Discovery from HP SIM - See Table 3 on page 34.
PAGE 55
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 filers, 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 36 for more information. 2 Discover your switches.
PAGE 56
This section describes the following: • ”About Entering Credentials for Elements in HP SIM” on page 36 • ”Setting Default User Names and Passwords” on page 36 • ”Adding an IP Range for Scanning” on page 37 • ”Adding a Single IP Address or DNS Name for Discovery” on page 38 • ”Modifying a Single IP Address Entry for Discovery” on page 40 • ”Removing Elements from the Addresses to Discover List” on page 41 About Entering Credentials for Elements in HP SIM For elements you want to discover and manage in HP SI
PAGE 57
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 58
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 59
• The following steps provide general information on how to discover an element. See Table 5 on page 45, Table 8 on page 68, and Table 2 on page 196. • 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 223 for more information. • (Discovery from HP SE only) The Do Not Authenticate option is for Engenio storage systems.
PAGE 60
• 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. If the element does not require a password, leave the Password field blank. 7. If you typed a password in the previous step, retype the password in the Verify Password field. 8.
PAGE 61
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. Click the Get Topology button.
PAGE 62
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. IMPORTANT: The elements associated with these addresses are not removed from the management server. See ”Deleting Elements from the Product” on page 92 for information about how to remove an element from the management server.
PAGE 63
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. 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 64
• 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 65
Step 1 - Discover Switches This section describes the following: • ”SMI-S Switches Must Be Removed and Rediscovered After Upgrading” on page 46 • ”Discovering Brocade Switches” on page 47 • ”Discovering CNT Switches” on page 48 • ”Discovering Cisco Switches” on page 50 • ”Discovering Sun StorEdge and QLogic Switches” on page 52 • ”Changing the SNMP Trap Listener Port for Sun StorEdge Switches” on page 54 • ”Discovering McDATA and EMC Connectrix Switches” on page 55 • ”(Discovery from SE Only) Excluding McDA
PAGE 66
Table 5 Discovery Requirements for Switches (continued) Element Discovery Requirements Additional Information Sun StorEdge and QLogic switches (SNMP) Enter the IP address/DNS name of the Sun StorEdge or QLogic switch. You do not need to enter a password if you discover it in HP SE. HP SIM requires a password. See ”Discovering Sun StorEdge and QLogic Switches” on page 52.
PAGE 67
2. Rediscover the Cisco, QLogic, or CNT switches in HP SE. See ”Step 1 - Discover Switches” on page 45. 3. Perform Get Details. See ”Step 4 - Discovery Data Collection or Get Details” on page 94. Discovering Brocade Switches IMPORTANT: Verify that the Rapid program on the switch is set to 1. Rapid must be set to 1 so that the management server can communicate with the switch. See ”Verifying Brocade Rapid Program Is Set to 1” on page 48 for more information.
PAGE 68
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. 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 69
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 6 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 70
• 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 37 or ”Adding a Single IP Address or DNS Name for Discovery” on page 38 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 71
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. • The management server gathers information about the Cisco inactive database during Get Details or Discovery Data Collection.
PAGE 72
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. From the Storage Essentials home page, click Discovery, then click Setup in the upper right pane of the Storage Essentials window. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5.
PAGE 73
• To manage a fabric of Sun StorEdge and/or QLogic switches, every switch in the fabric must be included in the discovery list. If a switch is not included in the discovery list, it may show up as a generic host system. • No ports are reported for uninstalled blades or GBICs. • The default SNMP trap listener port for all Sun StorEdge switches is 162. To change this port, see ”Changing the SNMP Trap Listener Port for Sun StorEdge Switches” on page 54.
PAGE 74
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. Do one of the following: • For Sun StorEdge and QLogic switches with SNMP connections: In the User Name field, type the user name for the switch. This is the public community SNMP string for the switch.
PAGE 75
7. Set the cimom.snmpTrapListenerPort property to the port you want, as shown in the following example: cimom.snmpTrapListenerPort=162 8. When you are done, click Save. 9. Restart the service for the management server for your changes to take effect. While AppStorManager is restarting, users are not able to access the management server. The AppStorManager service must be running for the management server to monitor elements.
PAGE 76
before discovering any McDATA switches. If you must change the configuration, see ”(Discovery from HP SE only) Changing the Discovery Settings” on page 64. • After you discover a McDATA or Connectrix switch through a proxy, the IP address displayed next to the name of the switch is actually the IP address of the proxy for the switch in the Discovery, and Get Details screens.
PAGE 77
IMPORTANT: EMC customers using the EMC Connectrix Manager (EMC’s rebranded EFCM) cannot use the EMC Fibre Zone Bridge (EMC’s rebranded Bridge Agent) to discover EMC switches using SWAPI. The McDATA SWAPI library is incompatible with EMC’s Fibre Zone Bridge Agent. If the Fibre Zone Bridge Agent is not installed or not needed, you can uninstall the Fibre Zone Bridge Agent and install McDATA’s Bridge Agent.
PAGE 78
7. Verify the cimom.useSnmpMcDataProvider property is set to false. cimom.useSnmpMcDataProvider=FALSE 8. When you are done, click Save. 9. Restart the service for the management server for your changes to take effect. While AppStorManager is restarting, users are not able to access the management server. The AppStorManager service must be running for the management server to monitor elements.
PAGE 79
• The element's user name and password are one of the default user names and passwords. • The element does not require authentication. 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. The information typed into this field is displayed under the Comment column in the Addresses to Discover list (Tools > Storage Essentials > Home > Discovery > Setup). 10.Click OK. 11.
PAGE 80
3. Copy the following command: cimom.useSnmpMcDataProvider=false 4. Return to the Advanced page. 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. Comment the property out by adding the hash (#) symbol in front of the property: #cimom.useSnmpMcDataProvider=false 7. When you are done, click Save. 8. Restart the service for the management server.
PAGE 81
5. In the IP Address/DNS Name field, type the IP address or DNS name of the proxy you want to discover. 6. In the User Name field, type the default user name, which is “public” (the read-only community string). This is the user name of the proxy. To access a Windows-based device, prepend the user name with the Windows domain name, as shown in the following example. domain_name\user_name where • domain_name is the domain name of the machine • user_name is the name of your network account 7.
PAGE 82
4. Return to the Advanced page. 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. Set the cimom.snmpTrapListenerPort to another port, as shown in the following example: cimom.snmpTrapListenerPort=1234 where 1234 is the new port 7. When you are done making your changes, click Save. 8.
PAGE 83
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 switch you want to discover. 6. In the User Name field, type the user name for accessing the switch. The default user name is “public” (the read-only community string). 7. Leave the Password (Optional) field blank. The password does not matter since the management server is not doing any configurations through SNMP. 8.
PAGE 84
7. When you are done making your changes, click Save. 8. Restart the service for the management server for your changes to take effect. While AppStorManager is restarting, users are not able to access the management server. The AppStorManager service must be running for the management server to monitor elements. Step 3 - Set Up the Proxy to Send Traps to the Correct Port IMPORTANT: The management server uses the Windows SNMP trap service when Discovery from HP SIM is used.
PAGE 85
• SNMP connection - Enter the IP address of the proxy. The default user name is “public” (the read-only community string). The password does not matter since the management server is not doing any configurations through SNMP. 10.Verify the following on the proxy and the switches accessible from the proxy: • The SNMP agent is enabled. • The read-only community string is configured. 11.Run Discovery. 12.Run Get Details.
PAGE 86
3. Copy the cimom.mcdata.exclude property. 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. 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 87
IMPORTANT: Look at Event Manager for additional information. See ”About Event Manager” on page 532 for more information. Duplicate Logs for Brocade Switches in Same Fabric If you discover more than one Brocade switch in the same fabric, the discovery log displays duplicate listings for the Brocade switches. Each Brocade switch is listed multiple times with the IP address of the other switches and its own.
PAGE 88
• ”Discovering HP Filers” on page 85 • ”Discovering NetApp Filers” on page 86 • ”Discovering Sun NAS Devices” on page 87 • ”Discovering HP and IBM Tape Libraries” on page 88 Table 8 Discovery Requirements for Storage Systems, Tape Libraries and NAS Filers Element Discovery Requirements Additional Information 3PAR storage systems Discover the 3PAR storage system directly. See ”Discovering 3PAR Storage Systems” on page 70.
PAGE 89
Table 8 Discovery Requirements for Storage Systems, Tape Libraries and NAS Filers (continued) Element Discovery Requirements Additional Information IBM Storage Systems Discover the CIMOM that talks to the IBM storage systems you want to monitor. See ”Discovering IBM Storage Systems” on page 79. Sun StorEdge 3510 Discovered through proxy software called Sun StorEdge™ Configuration Service.
PAGE 90
Discovering 3PAR Storage Systems NOTE: You do not need to provide the interop namespace because the management server includes the interop namespace for 3PAR storage systems in its default list. Discovery from HP SIM To discover a 3PAR storage system, provide the following information in HP Systems Insight Manager: • Provide the IP address or system name for the storage system.
PAGE 91
management server to discover the Solutions Enabler and the Symmetrix storage systems that it manages. IMPORTANT: Use a nethost file unless you are running a version of the Solutions Enabler earlier than the 5.1 version. You must have the license installed for the Solutions Enabler. The nethost file provides access to the Solutions Enabler API. Sometimes you can access an EMC Symmetrix storage system through several Solutions Enabler servers.
PAGE 92
• SERVER • DevMasking • Config Manager • Mapping (SOLUTION_4) Excluding EMC Symmetrix Storage Systems from Discovery When multiple EMC Symmetrix storage systems are managed through a single Solutions Enabler, specific storage systems may be excluded from discovery by using system properties. To exclude one or more Symmetrix storage systems from discovery, you must modify the cimom.symmetrix.exclude property. Set the property cimom.symmetrix.
PAGE 93
exclude from discovery. Separate additional serial numbers with a comma, as shown by the following example: cimom.symmetrix.exclude=000183500570,000183500575 where 000183500570 and 000183500575 are serial numbers for Symmetrix storage systems. 7. When you are done, click Save. 8. Restart the service for the management server for your changes to take effect. While AppStorManager is restarting, users are not able to access the management server.
PAGE 94
• The management server must have the User Name field populated to discover the Engenio storage system. If your Engenio storage system does not have a user name set, you must enter something in the User Name field, even though the storage system has no user name. • Discover both controllers for the Engenio storage system. Each controller has its own IP address.
PAGE 95
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. The information typed into this field is displayed under the Comment column in the Addresses to Discover list (Tools > Storage Essentials > Home > Discovery > Setup). 10.Select the Do Not Authenticate option. 11.If you do not plan to use provisioning in the product, select the Do Not Authenticate option. 12.Click OK. 13.
PAGE 96
IMPORTANT: First discover the IP address of the server running HiCommand Device Manager. See ”Adding an IP Range for Scanning” on page 37 or ”Adding a Single IP Address or DNS Name for Discovery” on page 38 for more information. Then, select Options > Protocol Settings > System Protocol Settings and select the host you discovered as a target. On the System Protocol Settings page, provide the port number for the server under the WBEM section.
PAGE 97
Excluding HDS Storage Systems from Discovery When multiple HDS storage systems are managed through a single HiCommand Device Manager, specific storage systems may be excluded from discovery by using system properties. To exclude one or more HDS storage systems from discovery, you must modify the cimom.hds.exclude property. Set the property cimom.hds.exclude to a comma separated list of serial numbers of the storage systems you want excluded, as shown in the following example: cimom.hds.
PAGE 98
While AppStorManager is restarting, users are not able to access the management server. The AppStorManager service must be running for the management server to monitor elements.
PAGE 99
(XP arrays only) If you have Command View version 2.0 or later, the default password is administrator. If you have Command View earlier than version 2.0, refer to the documentation that shipped with Command View for the default password. 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 100
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 37 or ”Adding a Single IP Address or DNS Name for Discovery” on page 38 for more information. Then, select Options > Protocol Settings > System Protocol Settings and select the host you discovered as a target.
PAGE 101
9. 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). 10.Do not select the Do Not Authenticate option. 11.Click OK. 12.To start discovering elements on the network, click the Start Discovery button on the IP Addresses tab.
PAGE 102
IMPORTANT: The management server is unable to display logical volumes configured on Sun StorEdge 3510 storage systems. Any logical volumes as well as the logical drives that comprise them will not appear in the UI. There will be no indication that this happened. Discovery from HP SIM To discover Sun StorEdge 3510 storage systems, provide the following information in HP Insight Manager: • IP address or system name of the system running the Sun StorEdge 3510 SMI-S provider you want to discover.
PAGE 103
Discovering Sun StorEdge 6920 Storage Systems Discovery from HP SIM To discover Sun StorEdge 6920 storage systems, provide the following information in HP Insight Manger: • IP address or system name of the Sun StorEdge 6920 you want to discover. See ”Adding an IP Range for Scanning” on page 37 or ”Adding a Single IP Address or DNS Name for Discovery” on page 38 for more information. • User name of the Sun StorEdge 6920 you want to discover. • Password of the Sun StorEdge 6920 you want to discover.
PAGE 104
• HP SIM does not allow blank user names. Enter anything for the user name. • Password for the controller or proxy. Refer to the HP SIM documentation for more information on working with HP SIM. Discovery from HP SE To discover Sun StorEdge 6130 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 105
Discovery from HP SE To discover an Xiotech storage system: 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 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, enter the IP address or DNS name for the storage system and its namespace.
PAGE 106
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 Filer you want to discover. 6. Enter the User Name of the HP Filer. You must provide a privileged login. 7. Enter the Password used to access the HP Filer. 8. Retype the password in the Verify Password field. 9. In the Comment field (optional), type a comment for additional information.
PAGE 107
Discovery from HP SE To discover a NetApp Filer: 1. Click Tools > Storage Essentials > Home > 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, type the IP address or DNS name of the NetApp Filer you want to discover. 6. Enter the User Name of the NetApp Filer. You must provide a privileged login. 7. Enter the Password used to access the NetApp Filer. 8.
PAGE 108
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 server running the SMI-S provider for the Sun NAS Devices you want to discover. 6. Enter the User Name of the CIMOM/provider for the Sun NAS Devices you want to discover. You must provide a privileged login. 7. Enter the Password used to access the CIMOM/provider for the Sun NAS Devices you want to discover. 8.
PAGE 109
For example: 192.168.1.1:root/ibm, where 192.168.1.1 is the IP address of the tape library and root/ibm is its namespace. 6. Enter the User Name of the system running the tape library. 7. Enter the Password of the system running the tape library. 8. Retype the password in the Verify Password field. 9. In the Comment field (optional), type a comment for additional information.
PAGE 110
IMPORTANT: You must perform this step to view elements connected in the topology. To obtain enough information to display the topology in System Manager: 1. Click the Discovery menu in the upper-right corner of the Store Essentials home page. 2. Click Topology in the upper-right corner. The discovered elements are selected. 3. Select the File Server SRM option corresponding to host file systems you want to monitor.
PAGE 111
• User name and password - You can change the user name and password the management server uses to access a device. Whenever a user name and/or password has changed on a device the management server monitors, the management server must be made aware of the change. For example, assume the password for a host was changed. You would need to updated the management server database with the new password. See ”Modifying a Single IP Address Entry for Discovery” on page 40.
PAGE 112
Deleting Elements from the Product The way you delete an element from the product depends on whether you are using discovery from HP SIM or discovery from HP SE. Discovery from HP SIM IMPORTANT: This step removes elements from the discovery list and from the HP SIM database. The deleted element can reappear if the following occurs: • If a scheduled automatic discovery task includes the deleted element, HP SIM will rediscover the deleted element again during the next discovery.
PAGE 113
• In System Manager - Right-click an element and select Delete Element from the drop-down menu. Right-click an element and select Delete Element from the drop-down menu. If you are blocking pop-ups and you use the right-click menu to delete an element from System Manager, the Delete window is blocked and you are unable to delete the element. You must disable the popup blocker before you can delete the element. • In Chargeback Manager - Click the button for the element you want to delete. 2.
PAGE 114
both access points to completely remove the element. As a result, the QBrocade5 switch will also be removed because it has the same access points as QBrocade2. Figure 1 Deleting Elements from the Management Server 3. Select all of the access points for the element you want to delete. Then, click the Delete button just above the table. For example, assume you want to delete QBrocade2 in the previous figure.
PAGE 115
• Get Details/Discovery Data Collection takes some time. You might want to perform this process when the network and the managed elements are not busy. (Discovery from HP SE only)To obtain a picture of device connectivity quickly, click the Get Topology button on the Topology tab. • If you have problems obtaining information from Connectrix and McDATA switches during Get Details/Discovery Data Collection, see the topic, ”Step 2 - Discover Storage Systems, Filers and Tape Libraries” on page 67.
PAGE 116
select Include backup details unless you have already discovered hosts running backup applications and installed CIM Extensions on those hosts. See ”Step 1 - Discovering Your Hosts and Master Backup Servers” on page 193 for more information about discovering master backup servers. The Include backup details option gathers the latest information about your backup applications. 3.
PAGE 117
2. On the View Logs page, click the “Click here” portion of the following message: Click here if you wish to stop getting details. 3. When you are asked if you are sure you want to stop Get Details/Discovery Data Collection, click OK. The management server stops gathering details. 4. Schedule a time to resume getting details.
PAGE 118
a. Go to the Services window on the management server. b. Right-click AppStorManager. c. Select Restart from the drop-down menu. While AppStorManager is restarting, users are not able to access the management server. The AppStorManager service must be running for the management server to monitor elements. 9. To perform the forced refresh, select the Force Device Manager Refresh option on the Get Details/Discovery Data Collection page. 10.Click Get Details.
PAGE 119
where 61038 and 61037 are serial numbers for HDS storage systems. One of the ways to find the serial number is to double-click the storage system in System Manager. Then, click the Properties tab. 7. When you are done, click Save. 8. Restart the service for the management server for your changes to take effect: a. Go to the Services window on the management server. b. Right-click AppStorManager. c. Select Restart from the drop-down menu.
PAGE 120
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 121
(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 55.
PAGE 122
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.
PAGE 123
Moving Elements to Another Discovery Group All elements are initially placed in the Default discovery group. You can then move elements from the Default discovery group to other discovery groups. You can use discovery groups to break up Discovery Data Collection for Discovery from HP SIM or Get Details and getting the topology for Discovery from HP SE.
PAGE 124
The elements are excluded from discovery until you clear them from quarantine. 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.
PAGE 125
your storage systems to obtain the latest information. If you do not select Force Device Manager Refresh, the management server gathers information from the external databases with the assumption the information in the external database is up to date. See the following topics for more information: ”Excluding EMC Symmetrix Storage Systems from Discovery” on page 72 and ”Excluding EMC Symmetrix Storage Systems from Force Device Manager Refresh” on page 97. 5. Click the Get Details button. 6.
PAGE 126
• From HP SIM - Select Tools > Storage Essentials > System Manager. • From the HP SE Home page (Tools > Storage Essentials > Home) - Click the button for System Manager in the left pane. 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.
PAGE 127
4 Deploying CIM Extensions This chapter describes the following: • ”About the HP Storage Essentials Agent Deployment Pack” on page 107 • ”Installing the HP Storage Essentials Agent Deployment Pack” on page 107 • ”Using the Deployment Pack” on page 108 About the HP Storage Essentials Agent Deployment Pack You can quickly install CIM Extensions remotely by using the HP Storage Essentials Agent Deployment Pack.
PAGE 128
10.When you are shown the Information window, read the information presented and then click Next. 11.Select a destination location. The default is the following: C:\Program Files\HP\Systems Insight Manager. NOTE: Select the default if you have placed the Extensions directory under C:\Program Files\HP\Systems Insight Manager. 12.Click Next. 13.Click Install. 14.Click Finish.
PAGE 129
username and/or password provided in Step 5. You can override the default options by deselecting the following options: • Attempt authorization using Systems Insight Manager private key and passphrase If this option is selected, the trust relationship established by the SIM private key and phrase set up using the 'mxagentconfig' tool is used to authenticate with the remote systems.
PAGE 130
110 Deploying CIM Extensions
PAGE 131
5 Installing the CIM Extension for IBM AIX This chapter describes the following: • ”About the CIM Extension for IBM AIX” on page 111 • ”Prerequisites” on page 111 • ”Verifying SNIA HBA API Support” on page 112 • ”Installing the CIM Extension” on page 113 • ”Setting Up Monitoring” on page 114 • ”Starting the CIM Extension Manually” on page 114 • ”Modifying the Boot Time RC Start Script (Optional)” on page 117 • ”Stopping the CIM Extension” on page 117 • ”How to Determine if the CIM Extension Is Running” on
PAGE 132
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. 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 AIX 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 249. bos.perf.
PAGE 133
IBM Adapters FCXXXX SNIA comes from the package devices.common.IBM.fc.hba-api. To find its library, enter the following at the command prompt: # more /etc/hba.conf The following is displayed: com.ibm.df1000f7 /usr/lib/libHBAAPI.a com.ibm.df1000f9 /usr/lib/libHBAAPI.a Installing the CIM Extension IMPORTANT: The following steps assume you know how to use smit. If you are unfamiliar with smit, refer to the documentation that accompanies the AIX host. To install the CIM Extension for AIX: 1.
PAGE 134
• (Optional) On some versions of AIX, the CIM Extension cannot start automatically after the host is rebooted. To see if your version of AIX supports the automatic startup, see ”Fulfilling the Prerequisites” on page 118. Setting Up Monitoring If you want the management server to be able to monitor the AIX host, iostat must be set to true. When iostat is set to true, disk activity history is retained for all disks.
PAGE 135
• 192.168.1.5 is the IP address of the host NOTE: Depending on your terminal type and processor speed, the message, “CXWS x.x.x.x on /192.168.1.5 now accepting connections,” may not display all the network interface IPs on the host. Use the /opt/APPQcime/tools/cxws.out file to view the output from the CIM Extension. Changing the Port Number The CIM Extension uses port 4673 by default. If the port is already used, use the ./start -port port_number command to change the port the CIM Extension will access.
PAGE 136
• 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. You cannot have more than one listing of the host with different ports.
PAGE 137
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 138
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. 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 process for the CIM Extension is displayed.
PAGE 139
• bos.rte.libc 5.3.0.0* - This is required for Java 1.4 support. • 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.
PAGE 140
120 Installing the CIM Extension for IBM AIX
PAGE 141
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 121 • ”Prerequisites” on page 121 • ”Verifying SNIA HBA API Support” on page 122 • ”Installing the CIM Extension” on page 122 • ”Starting the CIM Extension” on page 123 • ”Stopping the CIM Extension” on page 127 • ”How to Determine if the CIM Extension Is Running” on page 127 • ”Removing the CIM Extension from SGI ProPack for Linux” on page 127 Make su
PAGE 142
information. If you need to use a different port, see ”Permanently Changing the Port a CIM Extension Uses (UNIX Only)” on page 249. Verifying SNIA HBA API Support The management server can only talk to host bus adapters (HBAs) that support the SNIA HBA API. You can run the hbatest program, which is accessible from the CIM Extension CD-ROM. The program, hbatest, lists the name and number for all HBA's that support the SNIA HBA API.
PAGE 143
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. Refer to the documentation for your operating system for information on how to set this variable. • Interactive Installation (Without X Windows or telnet terminal session) - You must type -i console; otherwise, you are shown a NoClassDefFoundError message.
PAGE 144
1. Before starting the CIM Extension, make sure PCP is enabled by executing the following command: ps -ef | grep pmcd This should display a message resembling the following: root root 2699 2831 1 1988 0 14:42 ? 0 14:44 pts/1 00:00:00 /usr/share/pcp/bin/pmcd 00:00:00 grep pmcd The first line above indicates that pmcd is running.
PAGE 145
IMPORTANT: The steps provided in the section provide information about temporarily changing the port of the CIM Extension. If you want to permanently change the port the CIM Extension uses, see ”Permanently Changing the Port a CIM Extension Uses (UNIX Only)” on page 249. To change the port, enter the following: .
PAGE 146
The “-on” command line option may be repeated as often as desired to direct the CIM Extension to listen on multiple NICs, for example: ./start -on 192.168.2.2 -on 192.168.1.1 The CIM Extension listens only on the NICs that have the IP address 192.168.2.2 or 192.168.1.1. The “-on” command line option 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: ./start -on 192.168.2.
PAGE 147
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. • When you stop the CIM Extension, the management server is unable to gather information about this host.
PAGE 148
128 Installing the CIM Extension for SGI ProPack for Linux
PAGE 149
7 Installing the CIM Extension for HP-UX This chapter describes the following: • ”About the CIM Extension for HP-UX” on page 129 • ”Prerequisites” on page 129 • ”Verifying SNIA HBA API Support” on page 130 • ”Installing the CIM Extension” on page 131 • ”Starting the CIM Extension Manually” on page 132 • ”Finding the Status of the CIM Extension” on page 136 • ”Modifying the Boot Time RC Start Script (Optional)” on page 136 • ”Stopping the CIM Extension” on page 137 • ”Rolling Over the Logs” on page 137 • ”F
PAGE 150
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.a : Jun 28 2002, 11:08:35, PHSS_26799 or later Driver Patch Tachyon Fibre Channel Driver Patch: PHKL_23626 or later (only for HP-UX 11i) HP-UX 11.0 Driver Bundle Versions B.11.00.10 PCI Tachyon TL/TS Fibre Channel (Bundle A5158A). B.11.00.
PAGE 151
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.sl #32 bit lib names end in '32' com.hp.fcms64 /usr/lib/pa20_64/libhbaapihp.sl #64 bit lib names end in '64' • com.hp.fcd32 /usr/lib/libhbaapifcd.sl • com.hp.
PAGE 152
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. Only root has enough privileges to provide the information the management server needs.
PAGE 153
name that was specified in the -users parameter in the start command. The following is an example of the command: ./start -users myname where myname is a valid HP-UX user name that must be used to discover this HP-UX host. For example, assume you want to use the management server to discover a HP-UX host, but you do not want to provide the password to the root account. You can provide the password to another valid HP-UX user account that has less privileges, for example jsmythe.
PAGE 154
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 37 or ”Adding a Single IP Address or DNS Name for Discovery” on page 38 for more information. Then, select Options > Protocol Settings > System Protocol Settings and select the host you discovered as a target. On the System Protocol Settings page, provide the port number for the host under the WBEM section.
PAGE 155
The “-port” command line option may be used in conjunction with the “-on” option. Any “-on” arguments that do not specify an explicit port number use the “-port” option argument as the port number, for example: ./start -on 192.168.1.1:3456 -on 192.168.2.2 -port 1170 This command tells the CIM Extension to listen on the following ports: • Port 3456 on the NIC with the IP address 192.168.1.1 • Port 1170 on the NIC with the IP address 192.168.2.
PAGE 156
• xxxx is the year. • x.x.x.x is the version of the CIM Extension Combining Start Commands You can also combine the -users and -port commands as follows: ./start -users myname -port 1234 or .
PAGE 157
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 158
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:/". * Execution succeeded.. 5.
PAGE 159
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 139 • ”Prerequisites” on page 139 • ”Verifying SNIA HBA API Support” on page 140 • ”Installing the CIM Extension” on page 141 • ”Starting the CIM Extension Manually” on page 141 • ”Finding the Status of the CIM Extension” on page 145 • ”Stopping the CIM Extension” on page 146 • ”Rolling Over the Logs” on page 146 • ”Removing the
PAGE 160
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.rpm (update4 CD1) SUSE 8 compat-2003.1.10-0 SUSE 9 compat-2004.7.1-1.2 Required Disk Space 75 MB 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.
PAGE 161
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.so Driver Information for Verifying QLogic SNIA Adapters on SUSE Linux QLogic SNIA Adapters comes from package qlapi-vX.XXX-rel.tgz found in the QLogic driver. The adapters are installed separately after driver.
PAGE 162
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. Only root has enough privileges to provide the information the management server needs. If you do not start the CIM Extension with root privileges, the management server will display messages resembling the following: Data is late or an error occurred.
PAGE 163
IMPORTANT: The steps provided in the section provide information about temporarily changing the port of the CIM Extension. If you want to permanently change the port the CIM Extension uses, see ”Permanently Changing the Port a CIM Extension Uses (UNIX Only)” on page 249. To change the port, enter the following: .
PAGE 164
The “-on” command line option may be repeated as often as desired to direct the CIM Extension to listen on multiple NICs, for example: ./start -on 192.168.2.2 -on 192.168.1.1 The CIM Extension listens only on the NICs that have the IP address 192.168.2.2 or 192.168.1.1. The “-on” command line option 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: ./start -on 192.168.2.
PAGE 165
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-linux.mof CXWS version 3.6.0.
PAGE 166
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 167
9 Installing the CIM Extension for OpenVMS This chapter describes the following: • ”About the CIM Extension for OpenVMS” on page 147 • ”Prerequisites” on page 147 • ”Installing the CIM Extension for OpenVMS” on page 149 • ”Starting the CIM Extension Manually” on page 150 • ”Restricting the Users Who Can Discover the Host” on page 151 • ”Manually Starting the CIM Extension to Specify Multiple Users in a Colon-separated List” on page 151 • ”Temporarily Changing the Port Number” on page 152 • ”Configuring the
PAGE 168
$ 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.2 (Alpha): • DEC-AXPVMS-VMS732_PCSI-V0100 • DEC-AXPVMS-VMS732_UPDATE-V0400 • DEC-AXPVMS-VMS732_SYS-V0700 • DEC-AXPVMS-VMS732_FIBRE_SCSI-V0700 (Note that the FC SNIA HBA API software is bundled with the fibre_scsi patch.
PAGE 169
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 170
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.Verify that the APPQCIME process is running by typing: $ @sys$common:[opt.appqcime.tools]status 12.Dismount the CD-ROM by typing: $ DISMOUNT 13.Remove the CD. Press the Eject button on the CD-ROM drive to take the CD out of the CD-ROM drive.
PAGE 171
The CIM Extension is ready to be contacted by the management server when it displays a message resembling the following: Thu Sep 21 14:46:47 EDT xxxx CXWS x.x.x.x on /192.168.1.5 now accepting connections Where xxxx is the year, x.x.x.x is the version of CIM Extension, and 192.168.1.5 is the IP address of the host. NOTE: Depending on your terminal type and processor speed, the message, CXWS x.x.x.x on /192.168.1.5 now accepting connections, may not list all of the network interface IP addresses on the host.
PAGE 172
One of the names listed (myname or jsmythe) must be used to discover the OpenVMS host. Other user names and passwords, including “system” account will not work. Temporarily Changing the Port Number This section provides instructions on temporarily changing the port number used by the CIM Extension for OpenVMS. The CIM Extension uses port 4673 by default. If this port is already in use, use the following command to change the port number the CIM Extension will access: @sys$common:[opt.appqcime.
PAGE 173
NOTE: If you specify a port with the start command, the host can be discovered by any account that has access to the OpenVMS host. Configuring the CIM Extension to Listen on a Specific Network Card You can configure the CIM Extension to listen only on a specific network interface card (NIC) by using the -on command line option in the start command, for example: @sys$common:[opt.appqcime.tools]start -on 192.168.2.2 The CIM Extension listens only on the NIC that has the IP address 192.168.2.2.
PAGE 174
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. You cannot have more than one listing of the host with different ports. If you have already added the NIC to the discovery list on the management server, you must remove it and then add it again.
PAGE 175
$ @ sys$common:[opt.appqcime.tools]start Parameters you can add when you manually start the CIM Extension, such as -port, and -users can be enabled using the above command. To modify the sys$startup:systartup_vms.com file: 1. Open sys$startup:systartup_vms.com in a text editor. 2. Find the following line of code: $ EXIT 3. Add the following line before the line containing $ EXIT $ @ sys$common:[opt.appqcime.tools]start 4. Save the file.
PAGE 176
Increasing the Native Logging Level The configuration information for cxws_native.log is maintained in sys$specific:[opt.appqcime.config]cxws_native.cfg. In order to increase the logging level, choose the log level accordingly in this file. 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 177
10 Installing the CIM Extension for HP Tru64 UNIX This chapter describes the following: • ”About the CIM Extension for Tru64 UNIX” on page 157 • ”Prerequisites” on page 157 • ”Installing the CIM Extension” on page 158 • ”Starting the CIM Extension Manually” on page 160 • ”Restricting the Users Who Can Discover the Host” on page 161 • ”Finding the Version of a CIM Extension” on page 163 • ”Combining Start Commands” on page 163 • ”Finding the Status of the CIM Extension” on page 163 • ”(Optional) Modifying th
PAGE 178
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 the FC-HBA shared libraries. Refer to the IT Resource Center Web site at the following URL: http://www1.itrc.hp.com/. To access the FC-HBA shared libraries on the Web site, select the following in order and then search by keyword for FC-HBA: 1. maintenance and support for HP products 2.
PAGE 179
Installing CIM Extension on a Standalone Host To install the CIM Extension using CLI: 1. Login as root. 2. Place the CIM Extension CD-ROM into the CD-ROM on the Tru64 server. 3. Create the /cdrom directory on Tru64 host by entering the following at the command prompt: # mkdir /cdrom 4. Mount the CIM Extension CD-ROM by enter the following at the command prompt: # mount /dev/disk/cdromxx /cdrom where xx corresponds to the cdrom device number.
PAGE 180
1. Go to the /cdrom/tru64/ directory, as shown in the following example: # cd /cdrom/tru64/ 2. Run the command ./tru64_local_install.sh –curnode at the command prompt: #./tru64_local_install.sh –curnode 3. You must start the CIM Extension manually as described in ”Starting the CIM Extension Manually” on page 160. Starting the CIM Extension Manually The management server can only obtain information from this host when the CIM Extension is running.
PAGE 181
• 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 Restricting the Users Who Can Discover the Host The ./start -users user_name command provides greater security by restricting access.
PAGE 182
You can tell the port is in use by entering the following at the command prompt: netstat -a | grep 1234 The management server assumes the CIM Extension is running on port 4673. The management server also listens on port 17000 for CIM Extensions from build 4.0. If you change the port number, you must make the management server aware of the new port number. 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 183
Finding the Version of a CIM Extension You can find the version number of a CIM Extension: 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: Starting CIM Extension for Tru64 Thu Sep 21 14:46:47 EDT xxxx CXWS x.x.x.x on /192.168.1.5:4673 now accepting connections where • xxxx is the year. • x.x.x.
PAGE 184
script if you want to add parameters. Any parameter you can add when you manually start the CIM Extension, such as -port, can be added to the start script. To modify the file: 1. Open S99appqcime in a text editor. 2. Find the following line of code: ${APPIQ_HOME}/tools/start 3. Add the parameter after /start. For example, assume you want to change the port for the CIM Extension to port 1234. You would add -port 1234 after /start, as shown in the following example: ${APPIQ_HOME}/tools/start -port 1234 4.
PAGE 185
/opt/APPQcime/config/cxws_native.cfg where /opt is the directory into which you installed the CIM extension. More detailed logging information can be obtained by increasing the log level. Set LOG_LEVEL to 3 in cxws_native.cfg and restart the CIM extension to increase the log level. Fulfilling the Prerequisites Use the commands mentioned in this section to determine if you have the required software.
PAGE 186
166 Installing the CIM Extension for HP Tru64 UNIX
PAGE 187
11 Installing the CIM Extension for SGI IRIX This chapter describes the following: • ”About the CIM Extension for SGI IRIX” on page 167 • ”Prerequisites” on page 167 • ”Verifying SNIA HBA API Support” on page 168 • ”Installing the CIM Extension” on page 168 • ”Starting the CIM Extension” on page 169 • ”Modifying the Boot Time RC Start Script (Optional)” on page 172 • ”Stopping the CIM Extension” on page 173 • ”Rolling Over the Logs” on page 173 • ”How to Determine if the CIM Extension Is Running” on page 17
PAGE 188
Verifying SNIA HBA API Support The management server can only talk to host bus adapters (HBAs) that support the SNIA HBA API. You can run the hbatest program, which is accessible from the CIM Extension CD-ROM. The 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. 1.
PAGE 189
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. The CIM Extension only provides the information within the privileges of the user account that started the CIM Extension. Only root has enough privileges to provide the information the management server needs.
PAGE 190
IMPORTANT: The steps provided in the section provide information about temporarily changing the port of the CIM Extension. If you want to permanently change the port the CIM Extension uses, see ”Permanently Changing the Port a CIM Extension Uses (UNIX Only)” on page 249. To change the port, enter the following: .
PAGE 191
The “-on” command line option may be repeated as often as desired to direct the CIM Extension to listen on multiple NICs, for example: ./start -on 192.168.2.2 -on 192.168.1.1 The CIM Extension listens only on the NICs that have the IP address 192.168.2.2 or 192.168.1.1. The “-on” command line option 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: ./start -on 192.168.2.
PAGE 192
Starting the CIM Extension by chkconfig After installation, appqcime chkconfig is on by default. This means the appqcime service starts automatically after the host is rebooted. The appqcime service must be running for the management server to obtain information about the host. You can disable the appqcime service so that it does not start automatically after a reboot. NOTE: You can only disable appqcime from starting automatically after a reboot if you are at run level 2.
PAGE 193
1. Open S99appqcime in a text editor. 2. Find the following line of code: ${APPIQ_HOME}/tools/start 3. Add the parameter after /start. For example, assume you want to change the port for the CIM Extension to port 1234. You would add -port 1234 after /start, as shown in the following example: ${APPIQ_HOME}/tools/start -port 1234 4. Save the file. The changes take effect the next time the script executed when the host reboots.
PAGE 194
2. Enter the following at the command prompt: inst 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 195
12 Installing the CIM Extension for Sun Solaris This chapter describes the following: • ”About the CIM Extension for Solaris” on page 175 • ”Prerequisites” on page 175 • ”Verifying SNIA HBA API Support” on page 176 • ”Installing the CIM Extension” on page 177 • ”Starting the CIM Extension Manually” on page 178 • ”Finding the Status of the CIM Extension” on page 182 • ”Stopping the CIM Extension” on page 183 • ”Rolling Over the Logs” on page 183 • ”Removing the CIM Extension from Solaris” on page 183 Make su
PAGE 196
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. • File SRM - If you plan to have File SRM scan this host, make sure you have 220 to 230 MB for each set of 1 million files.
PAGE 197
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. If you installed the QLogic Adapter, you can find its library by entering the following at the command prompt: # more /etc/hba.conf The following is displayed: qla2x00 /usr/lib/libqlsdm.
PAGE 198
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 . The APPQcime package is added. 4. When you are asked for the name of the package to install, type the corresponding number for the APPQcime package. 5.
PAGE 199
The CIM Extension is ready to be contacted by the management server when it displays a message resembling the following: Thu Sep 21 14:46:47 EDT xxxx CXWS x.x.x.x on /192.168.1.5 now accepting connections where • xxxx is the year. • x.x.x.x is the version of CIM Extension • 192.168.1.5 is the IP address of the host NOTE: Depending on your terminal type and processor speed, the message, “CXWS x.x.x.x on /192.168.1.5 now accepting connections,” may not display all the network interface IPs on the host.
PAGE 200
Changing the Port Number The CIM Extension uses port 4673 by default. If the port is already used, use the ./start -port port_number command to change the port the CIM Extension will access. For example, if you are running a J2EE server, such as BEA WebLogic or IBM WebSphere, the J2EE server might already be using the 4673 port. IMPORTANT: The steps provided in the section provide information about temporarily changing the port of the CIM Extension.
PAGE 201
Specifying the CIM Extension to Listen on a Specific Network Card You can specify the CIM Extension to listen on only on a specific network interface card (NIC) by using the “-on” command line option in the start command, for example: ./start -on 192.168.2.2 The CIM Extension listens only on the NIC that has the IP address 192.168.99.37. The “-on” command line option may be repeated as often as desired to direct the CIM Extension to listen on multiple NICs, for example: ./start -on 192.168.2.2 -on 192.168.
PAGE 202
• 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. You cannot have more than one listing of the host with different ports. Finding the Version of a CIM Extension You can find the version number of a CIM Extension: 1. Go to the /opt/APPQcime/tools directory. 2. Type the following at the command prompt: # .
PAGE 203
Modifying the Boot Time RC Start Script (Optional) When you install the CIM Extension, its start scrip is put in the /etc/rc3.d directory with the file name S99appqcime. The CIM Extension uses this script to start at boot time. You can modify this script if you want to add parameters. Any parameter you can add when you manually start the CIM Extension, such as -port, can be added to the start script. To modify the file: 1. Open S99appqcime in a text editor. 2.
PAGE 204
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 205
13 Installing the CIM Extension for Microsoft Windows This chapter describes the following: • ”About the CIM Extension for Windows” on page 185 • ”Finding Applications Dependent on WMI” on page 186 • ”How to Determine If WMI Is Running” on page 186 • ”Verifying SNIA HBA API Support” on page 187 • ”Installation Steps” on page 189 • ”Installing the CIM Extension Using the Silent Installation” on page 190 • ”Removing the CIM Extension from Windows” on page 190 Make sure you have reviewed Table 2 on page 1 to e
PAGE 206
Finding Applications Dependent on WMI The installation restarts WMI to make it aware of the CIM Extension. Services or applications using WMI are shut down. You need to restart those applications manually. To find applications dependent on WMI: 1. Right-click My Computer. 2. Select Manage from the drop-down menu. 3. In the left pane of the Computer Management window, select Services and Applications. 4. In the right pane, double-click Services. 5.
PAGE 207
NOTE: You can start the service by right-clicking Windows Management Instrumentation and selecting Start from the drop-down menu. Figure 1 Starting WMI (Microsoft Windows 2000) Verifying SNIA HBA API Support The management server can only talk to host bus adapters (HBAs) that support the SNIA HBA API. You can run the hbatest program, which is accessible from the CIM Extension CD-ROM. The program, hbatest, lists the name and number for all HBA’s that support the SNIA HBA API.
PAGE 208
When you install the SNIA HBA that comes from HBAnyware, the SNIA registry setting is most likely in the following location: HKEY_LOCAL_MACHINE\SOFTWARE\SNIA\HBA\org.emulex.emulexhbaapi The following lists the possible locations for the various drivers: • Microsoft Windows 2003 Service Pack 1 drivers point to emulexhbaapi.dll. The emulexhbaapi.dll file can be found at C:\Program Files\HBAnyware\emulexhbaapi.dll • Windows 2003 drivers have registry point to emulexhbaapi.dll. The emulexhbaapi.
PAGE 209
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. Earlier drivers points to C:\WINNT\System32\qlsdm.
PAGE 210
Management Service. You will need to restart those services or reboot your system when the installation is complete. Then, click Next. 6. Check the pre-installation summary. You are shown the following: • Product Name • Installation Folder • Disk Space Required • Disk Space Available 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 CIM Extension is installed. 8.
PAGE 211
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.00.
PAGE 212
192 Installing the CIM Extension for Microsoft Windows
PAGE 213
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 214
• 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 215
IMPORTANT: Complete the steps in this section if you want to discover backup applications, such as Veritas NetBackup, on HP-UX and Linux. 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 has been installed on the server that is your NetBackup Master Server. See Table 2 on page 1 for information about installing SIM Extensions. 2. Go to the %JBOSS4_DIST%\server\appiq\conf directory.
PAGE 216
Table 1 (Discovery from HP SIM) Discovering Hosts Step Description 1 If you have several hosts that use the same password and user name, set that password and user name as the default. Use the Global Settings (Options > Protocol Settings > Global Settings) feature to set your default passwords. Refer to the documentation that ships with SIM for more information. 2 Discover your host (Options > Discovery > Automatic). One way to detect multiple IP addresses at once is to add an IP range for scanning.
PAGE 217
Table 2 Making the Management Server Aware of Hosts (SE Discovery Only) (continued) Step Description 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. During a scan of an IP range, the software uses ping; however, ping is not guaranteed to return a response from all devices.
PAGE 218
Discovery from HP SE To make the software aware of the devices on the network: 1. Click Tools > Storage Essentials > Home > Discovery > Setup. 2. If several of the elements in the same domain use the same name and password, click the Set Default User Name and Password link. Provide up to three user names and passwords. The management server tries the default user names and passwords for elements during discovery.
PAGE 219
The elements the management server detects during the scan are added to the Addresses to Discover list on the IP Addresses tab. 4. To add a single IP address or DNS name to discover: a. Click the IP Address tab. b. Click the Add Address button. c. In the IP Address/DNS Name field, type the IP address or DNS name of the device you want to discover. d. In the User Name (Optional) field, type the user name.
PAGE 220
Step C - (Discovery from HP SE Only)Build the Topology After you discover elements, the management server requires you build a topology view, which is a graphical representation of port-level connectivity information. If you purchased the license for monitoring file servers, make the management server aware of these servers by selecting the File SRM option. The File SRM option appears for hosts that have the CIM Extension and that have operating systems that support File SRM.
PAGE 221
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. For example, assume the number two is shown between a switch and a storage system. This means the elements have two connections to each other. To view the port details for the connection, right-click the element and select Show Port Details from the drop-down menu.
PAGE 222
To obtain details: 1. Do the following: • Discovery from HP SE - Click Tools > Storage Essentials > Home > Discovery > Details • Discovery from HP SIM - Click Options > Storage Essentials > Discovery > Run Discovery Data Collection. 2. Verify the File SRM option is selected. The File SRM option appears for hosts that have the CIM Extension and an operating system that supports File System Viewer. 3.
PAGE 223
• ”Monitoring Microsoft SQL Server” on page 208 • ”Monitoring Sybase Adaptive Server Enterprise” on page 212 • ”Monitoring Microsoft Exchange” on page 215 Monitoring Oracle To monitor and manage Oracle, you must do the following: • ”Step A - Create the APPIQ_USER Account for Oracle” on page 203 • ”Step B - Provide the TNS Listener Port” on page 205 • ”Step C - Set up Discovery for Oracle 10g” on page 205 After you complete these steps, you must discover Oracle,and perform Discovery Data Collection or Get D
PAGE 224
auto-mounted), and go to the /DBIQ/Oracle/unix directory by typing the following: # cd /cdrom/cdrom0/DBIQ/Oracle/unix where /cdrom/cdrom0 is the name of the CD-ROM drive • To run the script on Microsoft Windows, go to the DBIQ\Oracle\win directory on the CIM Extensions CD-ROM. IMPORTANT: You must complete the following steps. 2. Verify you have the password to the SYS user account. You are prompted for the password for this user account when you run the script. 3. Run the CreateOracleAct.
PAGE 225
you removed the APPIQ_USER account for Oracle, discover and perform Discovery Data Collection/Get Details for the host if you want to continue monitoring it. • If you receive a message about not being able to drop a user that is currently connected while you are removing the APPIQ_USER account for Oracle, re-run the script for removing APPIQ_USER. To remove the APPIQ_USER account for that Oracle instance: 1. If you plan to remove the management software for Oracle from a Solaris host, do the following: a.
PAGE 226
IMPORTANT: Monitoring Oracle 10g and Oracle clusters require an additional step. If you are not monitoring Oracle 10g and Oracle clusters, see ”Step 3 - Discovering Applications” on page 216. Step C - Set up Discovery for Oracle 10g NOTE: If you are discovering an Oracle cluster, see ”Discovering Oracle Clusters” on page 206. To monitor Oracle 10g, provide additional information as described in the following steps: 1.
PAGE 227
Discovering Oracle Clusters Perform the following steps for each node in the cluster: 1. Install the CIM Extension on each node in the cluster. See the Installation Guide for information on how to install the CIM Extensions. See ”Roadmap for Installation and Initial Configurations” on page 1 for information about the CIM Extensions available. 2. Create the appiq_user account on each node in the cluster. See ”Step A - Create the APPIQ_USER Account for Oracle” on page 203. 3.
PAGE 228
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)) ) ) ) f. Select ORACLE from the Database Type menu. g. Click OK. 5. Repeat Steps 4 and 5 for each node in the cluster.
PAGE 229
• Create APPIQ_USER account on SQL Server database you want to monitor. • You should have already installed the database for the management server. • Make sure you have all the necessary information before you begin the installation. Read through the following steps before you begin. To create the APPIQ_USER account for SQL Server: 1. To run the script on Microsoft Windows, go to the DBIQ\sqlserver\win directory on the CIM Extensions CD-ROM. IMPORTANT: You must complete the following steps. 2.
PAGE 230
IMPORTANT: You must provide the host name in the Host IP/DNS Name field. You cannot use localhost or parenthesis. If you have name resolutions issues, your server may be discovered; however, your applications will not be discovered. You can addressed the name resolution issues by adding entries within the hosts file on the management server for the systems in question.
PAGE 231
• Host IP/DNS Name: 192.168.2.10 • Database Server: SQLTEST • Port Number: 1433 • Database Type: SQLSERVER 6. In the Port Number field, type the port that SQL is using. If you do not provide a port number, the management server assumes the SQL server is using port 1433 (default). To determine the correct SQL Port Number that the SQL Server is using, follow these steps: a. Open SQL Server Enterprise Manager. b.
PAGE 232
5. Type the password for the server administrator account. The account for APPIQ_USER is removed. The management server can no longer monitor the SQL Server databases on this host. Deleting SQL Server Information If you do not want the management server to monitor a SQL Server 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.
PAGE 233
• Obtain the Sybase server name before you run the script • Create APPIQ_USER account on Sybase Database you want to monitor. • You should have already installed the database for the management server. • Make sure you have all the necessary information before you begin the installation. Read through the following steps before you begin. To create the APPIQ_USER account for the Sybase server: 1.
PAGE 234
Removing the APPIQ_USER Account for Sybase IMPORTANT: Before you remove the APPIQ_USER account for the Sybase databases on a host, make sure no processes are running APPIQ_USER for that Sybase database. The management server uses APPIQ_USER to obtain information about a Sybase database. (Discovery from HP SE) One of the ways to make sure APPIQ_USER is not being used is to temporarily remove the host running Sybase (Discovery > Topology).
PAGE 235
desktop. Refer to the documentation for HP Systems Insight Manager. Select a target, and then, click Run Now. 2. Click the Create button for the Database Information table. 3. In the Host IP/DNS Name field, type the IP address or DNS name of the host running Sybase. 4. You can leave the Management IP/DNS Name field blank. This field is for Oracle clusters.
PAGE 236
• Discover the application. Adding Microsoft Exchange Domain Controller Access To obtain information about your Microsoft Exchange servers, you must provide the user name and password for at least a primary domain controller, in addition to a DNS name, as described in the following steps. IMPORTANT: 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.
PAGE 237
• 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. 2. Click the button, corresponding to the domain controller you want to remove. 3. Perform Get Details/Discovery Data Collection for your changes to take effect.
PAGE 238
• 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. Keep in mind the following: • If DNS records for your Microsoft Exchange Servers are outdated or missing, the discovery of Microsoft Exchange may fail because Microsoft Exchange is dependant on Active Directory, which is dependant on DNS.
PAGE 239
• Discovery Data Collection/Get Details takes some time. You might want to perform this process when the network and the managed elements are not busy. • (Discovery from HP SE) To obtain a picture of device connectivity quickly, click the Get Topology button on the Topology tab. • If you want to enable File SRM for a host, make sure the File SRM option is selected.
PAGE 240
IMPORTANT: If the management server cannot communicate with an application, it labels the application as “Discovered”. The management server could find the application, but it could not obtain additional information about it. 5. Refer to the topic, “Adding a Discovery Schedule” in the User Guide for information about automating the gathering of Discovery Data Collection. If you run into problems with discovery, see ”Troubleshooting” on page 247. Discovery from HP SE To obtain details: 1.
PAGE 241
IMPORTANT: The hosts should recognize the management server by name, as a reverse look-up is required by operating system security as well as the Oracle Transparent Name Substrate (TNS). To change this port number or to add ports: 1. Select Options > Protocol Settings > Storage Essentials > Global Application Discovery Settings. 2. To assign a new port, click the Create for the Oracle Information table. 3. Type the new port number and click OK. 4.
PAGE 242
4. Under the Backup Domain Controller section, perform the following steps: a. In the Host Name field, type the fully qualified DNS name for the domain controller. b. In the User Name field, type the user name for accessing the Microsoft Exchange server. c. In the Domain Password field, type the corresponding password for accessing the Microsoft Exchange server. d. In the Verify Password field, retype the password for verification. 5. Click the OK button. 6. Update the database with element changes.
PAGE 243
Obtaining Disk Drive Statistics from Engenio Storage Systems IMPORTANT: Depending on your license, the ability to obtain disk drives statistics from Engenio storage systems may not be available. See the “List of Features” to determine if you have access to the additional statistics. The “List of Features” is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
PAGE 244
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. For example, in the following figure, the zip extension was assigned to a MIME type of application/unknown.
PAGE 245
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 246
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 247
• 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. You may want to disable this functionality for some users. • If the System Configuration option is selected for a role, all users assigned to that role will have administration capabilities, as shown in the following list.
PAGE 248
• Element Control - Lets you view and modify the record for the element (Asset Management tab). Provisioning cannot be performed. • View - Lets you only view element properties. For example, if a user belongs to a role that only lets you view the element properties on storage systems, that user would not be allowed to perform provisioning on storage systems because their role does not have the Full Control option selected for storage systems.
PAGE 249
BostonWebHost_Windows and BostonWebHost_Solaris. BostonWebHosts is a parent because it contains two organizations. Figure 2 Parent-Child Hierarchy for Organizations If a child contains organizations, it is also a parent. Let's assume you add two organizations called BostonWebMarketing and BostonWebProduction to BostonWebHost_Windows. BostonWebHost_Windows would become a parent because it now contains two organizations. It would also be a child because it is contained in BostonWebHosts.
PAGE 250
Figure 3 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 251
• Reports only display elements assigned to the user's organization, including child organizations. For example, if you attempt to view a Host Summary report and you do not have permission to access hosts through your organization, you are not given information about the hosts in the report. This is also true for e-mailing reports. Let's assume again you do not have permission to access hosts. The reports you e-mail will not contain information about hosts, including the host specific reports.
PAGE 252
Managing User Accounts This section discusses the following topics: • ”Adding Users” on page 232 • ”Editing a User Account” on page 233 • ”Deleting Users” on page 233 • ”Modifying Your User Profile” on page 234 • ”Modifying Your User Preferences” on page 234 • ”Viewing the Properties of a Role” on page 236 • ”Viewing the Properties of an Organization” on page 236 Adding Users To access the management server, users must enter a user name and password.
PAGE 253
e. In the Select Systems list box, select the systems you want the user to be able to manage. Select CMS (Central Management Server) if you want to access information about the server running HP Systems Insight Manager. f. Click OK. 7. Access Storage Essentials through one of the menu options, such as Options > Storage Essentials > Email Settings. 8. In the upper-right corner, select Security > Users. Notice that the users you created in HP Systems Insight Manager are put in the SIMViewOnly Role.
PAGE 254
9. Change or remove information from the Notes field if necessary. 10.To change the organizations to which the user belongs, select or deselect the organizations from the table in the user interface. The Everything organization is the default organization that lets users access all current and future elements. 11.Click OK. Deleting Users IMPORTANT: You cannot delete the admin account. To delete a user account: 1.
PAGE 255
• E-mail address • Phone number 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 5 Accessing the User Preferences Tab 2.
PAGE 256
Table 5 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 257
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: 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. To determine which elements are in a child organization, click the link of the child organization. 5.
PAGE 258
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. Select an access level for each element type: • Full Control - Lets you view and modify the record for the element (Asset Management tab) and perform provisioning. • Element Control - Lets you view and modify the record for the element (Asset Management tab). • View - Lets you view element properties.
PAGE 259
6. To change the access level, change the options selected in the table. • Full Control - Lets you view and modify the record for the element (Asset Management tab) and perform provisioning. • Element Control - Lets you view and modify the record for the element (Asset Management tab). • View - Lets you view element properties.
PAGE 260
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. Once you assign users to that organization, they would only be able to access the elements you specified.
PAGE 261
• Select all organizations - Select the Organizations (top-level node). The selected organizations appear in the Organization Members pane. • Select individual organizations - Expand the Organizations node. Then, select the organization. The selected organization appears in the Organization Members pane. The organizations in the Organization Members pane are listed as child organizations because they are now contained within the organization you are creating.
PAGE 262
• The Name and Description fields in the Edit Organization window do not accept special characters, except spaces and the following characters: $, -, ., and _ • The organization name can contain spaces, but it cannot be longer than 256 characters. • You cannot edit the Everything organization. • When adding a child to an organization, do not add the organization's parent as a child. For example, assume you created an organization named Child1, which is contained in a parent organization named Parent1.
PAGE 263
2. Click the button corresponding to the organization you want to remove. The software removes the organization. Removing Members from an Organization 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 264
5. Select the elements and/or organizations you want to remove in the right panel and then click the Remove from Organization button. 6. Click OK. Filtering Organizations The management server provides a filtering feature that lets you designate which organizations are active in your view. For example, assume you belong to an organization name Hosts and this organization contains two organizations: “Windows Hosts” and “Solaris Hosts.
PAGE 265
You can now only obtain information about elements in the active organizations. The active organizations are listed in the link next to the filter button, as shown in the following figure. Figure 8 Active Organization 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.
PAGE 266
a. Log onto the server running HP Systems Insight Manager. b. Stop the AppStorManager service if it is started. c. Enter the following at the command prompt: C:\> mxpassword -m -x MxDBUserPassword=mynewPass where mynewPass is your new password for the database. 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.
PAGE 267
16 Troubleshooting This chapter describes the following: • ”“Data is late or an error occurred” Message” on page 247 • ”appiq.
PAGE 268
NOTE: While the service is stopped, the management server cannot monitor elements and users cannot access the management server. 2. To find the corrupt log file, look in the alert_APPIQ.log file, which can be found in \oracle\admin\APPIQ\bdump, where ORACLE_BASE is c:\oracle You can verify if the REDO log listed in the alert_APPIQ.log file is corrupt by looking for a “redo block corruption” error in the REDO log. 3. On the management server, enter the following at the command prompt: Sqlplus /nolog 4.
PAGE 269
IMPORTANT: If you are starting the services manually, start the Oracle service before the service for the management server. Errors in the Logs If you access the logs, you are shown messages resembling the following. The complete text has been shorten as a result of space constraints: Aug 04 2004 11:59:07] INFO [com.appiq.service.policyManager.policyService.PolicyService] Creating [Aug 04 2004 11:59:07] INFO [com.appiq.service.policyManager.policyService.
PAGE 270
• password is the password of username. • 1234 the new port for the CIM Extension 4. Save the file. 5. Restart the CIM Extension for your changes to take effect. NOTE: The CIM Extension looks for parameters in the cxws.host.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. 6. The management server assumes the CIM Extension is running on port 4673. If you change the port number, you must make the management server aware of the new port number.
PAGE 271
mind that when a port other than 4673 is used for the CIM Extension, the port must be included in the discovery IP. For example, 192.168.1.1:1234, where 192.168.1.1 is the IP for the host and 1234 is the port the CIM Extension uses. Table 6 Troubleshooting Firewalls Configuration Manual Start Parameters for CIM Extension Firewall port 4673 opened between host and management server start If Mentioned in cxws.host.parameters Step 1 Discovery and RMI Registry Port 10.250.250.10 OR 172.31.250.10 OR 192.
PAGE 272
Table 6 Troubleshooting Firewalls (continued) Configuration Manual Start Parameters for CIM Extension If Mentioned in cxws.host.parameters Step 1 Discovery and RMI Registry Port Firewall port 1234 opened between host and management server on the 192.168.250.x subnet start -on 192.168.250.10:1234 -on 172.31.250.10:1234 172.31.250.10 :1234 With 3 firewall ports opened on different ports respectively 1234, 5678, 9012. -on 10.250.250.10:1234 start -on -on 172.31.250.10: 5678 10.250.250.
PAGE 273
Table 6 Troubleshooting Firewalls (continued) Configuration Manual Start Parameters for CIM Extension If Mentioned in cxws.host.parameters Step 1 Discovery and RMI Registry Port With firewall port 1234 opened between a host and management server. NAT environment where 10.250.250.10 subnet is translated to 172.16.10.10 when it reaches other side of the firewall start -port 1234 -port 1234 172.16.10.10 With 3 firewall ports opened on different ports respectively 1234, 5678, 9012.
PAGE 274
Table 6 Troubleshooting Firewalls (continued) Configuration Manual Start Parameters for CIM Extension No DNS, never resolve No firewall. Don't want to use root credentials. Want to discover with a non-existent user. start -credentials abcuser:passwd With 3 firewall ports opened on different ports respectively 1234, 5678, 9012. Don't want to use root credentials. Want to discover with a non-existent user. start -on 10.250.250.10:1234 -on 172.31.250.10:5678 -on192.168.250.
PAGE 275
automounts because it cannot determine if the comma separate strings that are part of the mounted volume name are host names or part of the name of a remote volume. The following example is a comma separate string that is part of a mounted volume name. The management server cannot tell whether test and three are host names or part of the name of a remote volume. As a result, the management server does not display the volume name.
PAGE 276
Installing the Certificate by Using Netscape Navigator 7 1. Access the management server by typing the following: https://machinename where machinename is the name of the management server. 2. When the security alert message appears, click the Always button. 3. When you are told you are requesting an encrypted page, click OK. 4. Click the Always button when you are asked if you want to accept the certificate. 5. When asked if you wanted to trust the signed applet, click the Always button.
PAGE 277
The new certificate is copied to the correct location. Troubleshooting After Upgrading This section provides information on troubleshooting after upgrading. It includes the following topics: ”SMI-S Switches Must Be Removed and Rediscovered After Upgrading” on page 257 SMI-S Switches Must Be Removed and Rediscovered After Upgrading You must remove and rediscover Cisco, QLogic, or CNT switches supported through SMI-S after you upgrade the management server.
PAGE 278
• ”“Connection to the Database Server Failed” Error” on page 261 • ”DCOM Unable to Communicate with Computer” on page 261 • ”Duplicate Listings for Brocade Switches in Same Fabric” on page 261 • ”Element Logs Authentication Errors During Discovery” on page 262 • ”EMC Device Masking Database Does Not Appear in Topology (AIX Only)” on page 262 • ”Management Server Does Not Discover Another Management Server's Database” on page 262 • ”Microsoft Exchange Drive Shown as a Local Drive” on page 262 • ”Unable to Di
PAGE 279
The management server lets you send status reports about Discovery Data Collection/Get Details to users. The status reports that are sent to users can also be found in the GAEDSummary.log file in the [Install_DIR]\logs directory on the management server. To configure the management server to send status reports on Discovery Data Collection/Get Details to your e-mail account: 1. Enable e-mail notification for the management server. Refer to the User Guide for more information. 2.
PAGE 280
To change the time-out period and number of retries for switches, modify the properties specified Table 7 on page 260 and Table 8 on page 260 as described in the following steps: 1. Access the management server. 2. Select Options > Storage Essentials > Manage Product Health. Then, click Advanced in the Disk Space tree. 3. Click Show Default Properties at the bottom of the page. 4. Copy the commands specified in Table 7 on page 260. How you copy the text depends on your Web browser.
PAGE 281
change the number of retries to five for a McDATA switch, set the cimom.McData.Snmp.Retries properties as shown in the following example: cimom.McData.Snmp.Retries=5 Table 8 Retry Properties Switch Property McDATA/Connectrix cimom.McData.Snmp.Retries discovered through SNMP Cisco cimom.Cisco.Snmp.Retries Other switches discovered through SNMP: cimom.snmp.switch.retries • Sun StorEdge • QLogic 9. When you are done, click Save. 10.
PAGE 282
Duplicate Listings for Brocade Switches in Same Fabric If you discover more than one Brocade switch in the same fabric, the Targets tab displays duplicate listings for the Brocade switches. Each Brocade switch is listed multiple times with the IP address of the other switches and its own. For example, assume you discovered Brocade switches QBrocade2 and QBrocade5 in the same fabric, the switches are listed twice on the Targets tab.
PAGE 283
displaying it in the topology. Refer to Oracle documentation for information on how to remove the deleted Oracle instance from the TNS listener port. Requirements for Discovering Oracle To discover Oracle: • The management software for Oracle must be installed. For information about installing the management software for Oracle, refer to the Installation Guide. • By default, the software sets the TNS Listener Port to 1521.
PAGE 284
• ”Unable to Find Elements on the Network” on page 267 • ”Device Locking Mechanism for Brocade Element Manager Query/Reconfiguration” on page 268 • ”A Discovered Sun StorEdge A5000 JBOD Does Not Display Its WWN Properly” on page 268 • ”Unable to Monitor McDATA Switches” on page 268 • ”Unable to Detect a Host Bus Adapter” on page 268 • ”Navigation Tab Displays Removed Drives as Disk Drives” on page 268 • ”Unable to Obtain Information from a CLARiiON Storage System” on page 269 • ”Discovery Fails Too Slowly f
PAGE 285
Table 9 Troubleshooting Discovery and Discovery Data Collection/Get Details (continued) Scenario Description What to do The switch was previously made aware of the host, but it can no longer contact it. Verify that the host is on and the network cables are connected to it. If the steps provided do not work, see ”Link Between a Brocade Switch and a Host Disappears from the Topology” on page 267. Discovery from HP SIM Try discovering the element again in HP SIM. Then, run Discovery Data Collection.
PAGE 286
Troubleshooting Discovery and Discovery Data Collection/Get Details (continued) Table 9 Scenario Description What to do The switch has not been discovered. Try discovering the switch again. 1. Click the Discovery menu. Click the Setup tab and the Add Address button on the IP Addresses tab. The element appears discovered, but a connected switch does not appear. 2. Type the IP address or DNS Name of the switch. Then, type its user name and password. Click OK. 3. Verify the element is selected. 4.
PAGE 287
IMPORTANT: One way to determine what is happening is to look at the log messages during discovery and getting element details. See ”Viewing Log Messages” on page 66 for more information. No Stitching for Brocade Switches with Firmware 3.2.0 Stitching does not appear for hosts attached to Brocade switches running firmware 3.2.0. There is no stitching when the PID format is 0. The port setting must be the same for all Brocade switches in the fabric or the fabric will become segmented.
PAGE 288
Device Locking Mechanism for Brocade Element Manager Query/Reconfiguration Please keep in mind that the configuration for Brocade switches is locked while getting all details for elements in a zones. The software ensures that each CIM query locks out any reconfiguration. For example, if you are getting details for elements in all zones, you cannot add a new Brocade switch while you are doing it (the discovery or configuration process waits until the collection of details is finished before proceeding).
PAGE 289
cfgadmn command makes the software realize the drive has been removed. Refer to the documentation that shipped with the Solaris operating system for more information about the cfgadm command. Unable to Obtain Information from a CLARiiON Storage System If you are having difficulty obtaining topology information or element details from a CLARiiON storage system, the NaviCLI might have timed out as a result of the service processor being under a heavy load.
PAGE 290
9. When you are done, click Save. 10.Restart the service for the management server for your changes to take effect. While AppStorManager is restarting, users are not able to access the management server. The AppStorManager service must be running for the management server to monitor elements.
PAGE 291
While AppStorManager is restarting, users are not able to access the management server. The AppStorManager service must be running for the management server to monitor elements. Re-establishing Communication with EFCM To re-establish communication with EFCM, perform the following steps: 1. To check the status of the connection, click the Test button on the Discovery Setup screen. If the McDATA provider reports that it can connect to EFCM, the connection has been restored.
PAGE 292
HiCommand Device Manager over a secure socket layer (SSL) connection by doing one of the following: • Use HTTPS in the discovery address - Prepend https:// to the discovery address to force the connection to HTTPS mode, for example, https://192.168.1.1, where 192.168.1.1 is the IP address of the host running HiCommand Device Manager.
PAGE 293
Unable to Discover a UNIX Host Because of DNS or Routing Issues If the management server is unable to discover a UNIX host because of a DNS or routing issues, you will need increase the amount of time that passes before the management server times out for that CIM Extension. By default, the management server waits 1,000 ms before it times out. It is recommended you increasing the time before the management server times out to 200000 ms (3.33 minutes), as described in the following steps.
PAGE 294
• ”Changes in EFC Manager Requiring Discovery Data Collection/Get Details” on page 274 Cannot Access a Resource Owned by Another Controller You received the message about not being able to access a resource owned by another controller because you tried to access a controller that has not been discovered. You should discover all controllers on the Engenio storage system. For example, assume you discovered only one of the controllers on an Engenio storage system with two controllers.
PAGE 295
with an error in the Windows Event Log about being unable to retrieve data from the PerfLib subkey in the Registry. To solve this problem, reinstall the operating system. “Fork Function Failed” Message on AIX Hosts If a CIM Extension running on AIX detects low physical or virtual memory while starting, a “Fork Function Failed” message appears. A CIM Extension on AIX uses additional memory and CPU resources at start time.
PAGE 296
Table 10 Known Device Issues (continued) Device Software Description AIX host using an IBM Storage System NA If you have an AIX host using an IBM storage system, not all bindings may be displayed on the bindings page on the Navigation tab. For example, assume diskA on host123 has six paths. All six bindings may not be displayed. NA Hosts running SGI IRIX version 6.5.22 or 6.5.24 If a host running SGI IRIX version 6.5.22 or 6.5.
PAGE 297
Table 10 Known Device Issues (continued) Device Software Description Solaris host HDLM If you sync the Solaris host by itself without the switches and storage, the storage volume page reports all drive types as local. Once you discover the host with the switches and storage, it reports its drives as being external. It was the same result with Active-Active and Active-Standby. Solaris host HDLM Solaris HDLM disks cannot be monitored.
PAGE 298
Table 10 Known Device Issues (continued) Device Software Description Any host NA The Unmounted Volume field under Capacity Summary automatically displays 0 MB if you discovered the host but not the storage system connected to it. This may occur if you did not enter the IP address of the storage system when performing discovery and/or your license does not allow you to discover a particular storage system.
PAGE 299
After the management server has detected the lock on the Symmetrix storage system, it tries to access the storage system for 15 minutes and logs the errors. If you receive the error message, determine if someone is performing an operation that requires a lock, such as LUN mapping, LUN masking or Discovery Data Collection/Get Details. This also applies even if one of the processes is being used by a third-party product, such as for LUN masking. If so, wait until the process is complete.
PAGE 300
280 Troubleshooting
PAGE 301
Index 3PAR storage systems 70 A about AIX CIM Extension 111 Altix CIM Extension 121 HP-UX CIM Extension 129 IRIX CIM Extension 167 management server 1 security 225 Solaris CIM Extension 157, 175 Windows CIM Extension 185 accessing discovery page from HP SE 31 discovery page from HP SIM 31 discovery page from HP Storage Essentials 31 domain controller 202 account password 233 accounts users 232 Active Directory 262 adding domain controller 202, 221 elements 240, 241 IP address 38 IP range 37 new elements 10
PAGE 302
user account 233 user name 90 user preferences 235 user profile 234 child organizations 225 CIM xvii, 1 OpenVMS 147 CIM Extension installing 129, 157, 175, 185 port 249 Solaris 129, 157, 175 Windows 185 CIM Extensions about 111, 121, 129, 157, 167, 175, 185 AIX 111 Altix 121 HP-UX 129 IRIX 167 Solaris 157, 175 Windows 185 cimom.CimXmlClientHttpConnectTimeout 269 cimom.emc.skipRefresh 97 cimom.hds.exclude 77 cimom.symmetrix.
PAGE 303
Microsoft Exchange 202, 215, 262 NetApp filers 86 new elements 106 Oracle 202, 203 Oracle clusters 203 passwords 36 SQL servers 208 storage system 29 storage systems 73, 81 Sun StorEdge storage systems 81, 83 Sun StorEdge switches 52 switches 29, 47 Sybase 202, 212 Symmetrix systems 72 troubleshooting 262, 263, 278 user names 36 discovery authentication errors 262 quarantine 103, 104 time-out 269 troubleshooting 261 Discovery Data Collection Cisco SMI-S switch 258 discovery groups 90 discovery page accessin
PAGE 304
switches 65 Symmetrix systems 72 exclusive lock error message 278 Extension CIM 129, 157, 175 F features key 1 file extension assigning 101, 223 filtering organizations 244 finding applications 202 hosts 202 IP address 38 IP range 37 new elements 106 storage systems 29 switches 29 fixing drivers 275 full name changing 234 G getting element details 94 getting details 45, 94 applications 202 hosts 202 H HBAs swapping 275 HDS storage systems discovering 75 HdsSkipRefresh 98 Help Desk role 225 help, obtainin
PAGE 305
internal drives 269 IP range 37 IRIX CIM Extension installing 167 prerequisites 167 removing 167 starting 167 stopping 167 issues devices 275 J Java 1 Java plug-in installing 20 K key benefits 1 key features 1 L local drives 262 locating storage systems 29 switches 29 log messages viewing 67 login name modifying 234 M management server about 1 database 7 installing 7 porting across operating systems 26 security 225 managing elements 240, 241, 243 switches 99 McDATA switches 268 adding 99 discovering 55
PAGE 306
installing 147 OpenVMS CIM installation prerequisites 147 Oracle deleted instances 262 discovering 202, 203 discovery requirements 263 Oracle TNS Listener Port 220 organizations about 225 adding 240 deleting 242 editing 241, 243 elements 240, 241, 243 filtering 244 properties 237 users 237 viewing 241 P parent organizations 225 password changing 90, 222, 233, 234 phone number editing 234 planning organizations 225 port CIM Extension 249 Prerequisites OpenVMS CIM installation 147 prerequisites xvii AIX CIM
PAGE 307
Help Desk 225 privileges 225 properties 236 Server Administrator 225 Storage Administrator 225 users 236 View privilege 225 S SAN xvii saving discovery settings 43 settings to a file 43 scanning IP range 37 security Management server 225 roles 237, 238 security certificate installing 7 Server Administrator role 225 setting discovery passwords 36 discovery user name 36 silent installation Windows 190 SMI-S Cisco SMI-S switches 258 SMI-S support troubleshooting 257 SMI-S switches see the support matrix 46, 2
PAGE 308
System Manager can’t access 274 T technical support, HP xix terms storage 1 text symbols xviii time-out period changing 67 TNS Listener Port changing 220 topology AIX 262 building 89 host not appearing 263, 267 topology issues 263 troubleshooting Cisco SMI-S switches switch names 258 discovery 261 discovery and getting element details 261, 262, 263, 267, 278 Microsoft Exchange 262 provisioning 274, 278 SMI-S switches 46, 257 U unable to discover 261 Unable to access resource 274 unable to detect host bus
PAGE 309
Figures 1 1 2 3 4 5 6 7 8 Deleting Elements from the Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Starting WMI (Microsoft Windows 2000). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Parent-Child Hierarchy for Organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Children in Multiple Organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 310
PAGE 311
Tables 1 2 3 4 5 6 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Roadmap for Installation and Initial Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 HP SIM Discovery Steps for Switches, NAS filers, and Storage Systems . . . . . . . . . . . . . . 34 HP SE Discovery Steps for Switches, NAS filers, and Storage Systems . . . . . . . . . . . . . . . 35 Discovery Requirements for Switches . . . . . . . . . . .
PAGE 312