HP Storage Essentials SRM 6.
Legal and notice information © Copyright 2002-2008 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.
Contents About this guide . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . HP technical support . . . . . . . . . . . . .
Manually Install HP Systems Insight Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Step 3 – Install Storage Essentials on the Storage Essentials Server . . . . . . . . . . . . . . . . . . 19 Step 4 – Verify that HP SIM is Running on the Remote Server . . . . . . . . . . . . . . . . . . . . . . 24 Step 5 – Complete the Storage Essentials Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Step 6 – Configure Browser Settings . . . . . . . . . . . . . . . . . .
(Required Only When HP SIM is Running on a Separate Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5 – Manually Export the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6 – Start the Storage Essentials Upgrade Wizard and Resolve Any Minimum Requirement Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7 – Customize Database Passwords. . . . . . . . . . . . . . . . . . . . . . .
Step 8 - Configure Firefox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Step 9 - Import a Storage Essentials License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Installing the Java Plug-in on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Configurations Required for Discovering EMC CLARiiON Storage Systems . . . . . . . . . . . . . . . .
Testing your SMI-S Providers (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Configuring the Selective Discovery Filter (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Configuring the HP SIM Connector to Pass Devices with the DNS Name (Optional) . . . . . . . . 110 Signing in to HP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Enabling Product Health Monitoring. . . . . . . . .
Discovery Information for an MSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovering HP StorageWorks EVA Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovery Information for an EVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining SNMP Traps using Command View EVA . . . . . . . . . . . . . . . . . . . . . . . . . . . Community String Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing a Hosts File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Log Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Status of System Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Discovery Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 Installing the CIM Extension for IBM AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 About the CIM Extension for IBM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying SNIA HBA API Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the CIM Extension . . .
Additional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding the Version of a CIM Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combining Start Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the CIM Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rolling Over the Log Files . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NonStop G06.27 or later Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the CIM Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the CIM Extension on a Standalone Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the CIM Extension on a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying SNIA HBA API Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the CIM Extension Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a New Port Number to Discovery . . . . . . . . . . . . . . . . . Configuring the CIM Extension to Listen on a Specific Network Card . Defining UNC Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rolling Over the Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the CIM Extension from Windows . . . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. . . .
Step B — Create APPIQ_USER Account on the Caché Instance. . . . . . . . . . . . . . . . . . . . Locked Down Security Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the APPIQ_USER Account from the Caché Instance. . . . . . . . . . . . . . . . . . . . . Step C — Provide the Caché Instance Name and Port Number . . . . . . . . . . . . . . . . . . . Deleting Caché Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Permanently Changing the Port a CIM Extension Uses (UNIX Only). . . . . . . . . . . . . . . . . . . . . . Configuring UNIX CIM Extensions to Run Behind Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . Volume Names from Ambiguous Automounts Are Not Displayed . . . . . . . . . . . . . . . . . . . . . . . Installing the Software Security Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Certificate by Using Microsoft Internet Explorer 6.0 .
Discovery Fails Too Slowly for a Nonexistent IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . 409 “CIM_ERR_FAILED” Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 Re-establishing Communication with EFCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 CIM_ERR_FAILED When Trying to Activate a Zone Set Using McDATA SWAPI . . . . . . . . . . . 412 Communicating with HiCommand Device Manager Over SSL . . . . . . . . . . .
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Missing Xvfb Package Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Setting Kernel Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Oracle User Account Not Enabled Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Discovery Setup page . . . . . . . . . . . . . . . . . . . .
xx
Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv Roadmap for Installation and Initial Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Pre-installation Requirements to Install or Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Overview of Switch Discovery Requirements . . . . . . . . . . . . . . . . .
xxii
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
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.
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/.
xxvi
1 Overview This chapter contains the following topics: • Supported Platforms for Installing HP Storage Essentials, page 1 • Roadmap for Installation and Initial Configurations, page 1 • About this Product, page 4 Supported Platforms for Installing HP Storage Essentials This chapter provides a general overview of the installation steps for the various operating systems on which HP Storage Essentials is supported: • Linux • Microsoft Windows NOTE: The Linux management server is not available with Storage E
IMPORTANT: If you access HP Systems Insight Manager through HTTP over SSL (HTTPS), you must provide the full DNS name for the host to be able to access HP Storage Essentials. For example, you could access HP Systems Insight Manager by using https://mycomputer.domainname.com:50000, but you could not use https://mycomputer:50000. For non-secure connections (HTTP), the full DNS name does not need to be provided.
Table 2 Roadmap for Installation and Initial Configurations (continued) Step Description Where to Find 3 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 191.
1If you install CIM extensions on the management server, the Database Admin Utility returns the following error and does not run correctly: [isAppIQCIMOMAlive] - false About this Product This product can simplify your complex environment and lower your cost of management with CIM-based integrated storage management. The management software integrates the management of applications, servers, storage networks and storage subsystems in a single, easy to implement and intuitive solution.
• Reporting - Offers flexible, in-depth report generation in both predefined and user defined formats, or export data to other management applications. • Integrated asset management and chargeback - Centralizes all aspects of storage inventory for maximum asset utilization. Improves accountability and budgeting with cost accounting based chargeback on user defined utilization characteristics.
6 Overview
2 Installing the Management Server on Microsoft Windows Follow the steps in this chapter to install the management server on the Windows operating system. See the following topic if you are installing the management server on another supported operating system: • ”Installing the Management Server on Linux” on page 59 Important Information About Upgrading Please contact your Account Representative for upgrades. Upgrading requires assistance from HP Services.
Keep in Mind the Following • All steps must be completed for the management server to work properly. • Before beginning any installation or upgrade steps, refer to the support matrix for your edition to determine the minimum software and hardware requirements. The support matrix can be found on the top level of the management server CD-ROM. • During the management server for Windows installation, double-byte characters are not allowed in the installation path.
• How to Verify Networking, page 14 • Be Sure to Install a Supported Browser, page 14 Installation and Upgrade Requirements (Cannot Proceed with Install/Upgrade if Not Met) The requirements listed in Table 3 on page 10 must be met or the installation or upgrade will stop.
IMPORTANT: Contact Customer Support if you are upgrading. Upgrades require assistance from Customer Support. Table 3 Pre-installation Requirements to Install or Upgrade Requirement: Must Meet or Exceed or the Installation or Upgrade Will Stop: NTFS File System: Installations: The NTFS file system is required to install the product. Upgrades: If Oracle 9i is installed on a volume using the FAT32 file system, you must convert the volume to NTFS before you can upgrade.
Table 3 Pre-installation Requirements to Install or Upgrade Requirement: Must Meet or Exceed or the Installation or Upgrade Will Stop: HP Systems Insight Manager Credentials: Valid HP Systems Insight Manager credentials must be entered on the Storage Essentials HP Systems Insight Manager Service Account Credentials screen or the Storage Essentials installation wizard will stop during a single-server installation (HP SIM and Storage Essentials installed on the same server).
• With ARCHIVING and RMAN backup off: minimum disk space: 100 GB, recommended disk space: 200 GB. • With ARCHIVING and RMAN backup on: minimum disk space: 200 GB, recommended disk space: 350 GB. The installation or upgrade will not continue if the disk space requirements are not met. Operating System — Windows 2003 Server SP1, SP2, R2, R2 SP2. The installation or upgrade will not continue if the operating system requirement is not met. • Processor — A dual Intel XEON (or AMD equivalent) 3.
NOTE: These instructions may vary depending on the version of Windows you are running. 2. Go to Control Panel > Add or Remove Programs > Add/Remove Windows Components. 3. Select the Management and Monitoring Tools line and click Details. 4. Unselect everything except Simple Network Management Protocol. Click OK. 5. Select Next, then select Next again. Keep Remote administration mode selected. 6. Ensure that you deselect Internet Information Services (IIS) – it is enabled by default when installing SNMP.
How to Verify Networking The management server must have static or dynamic host name resolution. To verify that the server’s name can be resolved through DNS: 1. Right click My Computer in the Start menu. 2. Select Properties. 3. Click on the Computer Name tab to see the fully qualified name of the computer under the label Full Computer Name. The server must be in the domain in which it is going to be used. 4. From a command prompt, type nslookup .
the Storage Essentials installation files—(the HP SIM Connector) provides the integration between Storage Essentials and HP SIM. The Storage Essentials installation wizard automatically installs the HP SIM Connector on the Storage Essentials server (along with the other software components described later).
Storage Essentials Installation Wizard Options This release of the HP Storage Essentials management server for Windows provides the following options for installing the Storage Essentials management server: IMPORTANT: The server must meet or exceed the minimum requirements listed in the support matrix for your edition.
IMPORTANT: Do not install the Oracle database separately. With this release of the product, you must first install the management server for Windows CD. The installation wizard automatically installs the Oracle database and prompts you for the Oracle CD during the installation at the appropriate time. Installing the Oracle database used by the management server manually is no longer recommended. Be sure to see ”Installation/Upgrade Process is Now Automated” on page 8.
2. Put the HP SIM 5.1 CD in the CD drive of the designated HP SIM server. The HP SIM installation wizard program starts automatically. If the HP SIM installation does not start, double-click setup.exe found in the hpsim directory. 3. Follow the instructions on the HP SIM 5.1 installation screens. As a best practice, install only the HP SIM components that are required to install and set up Storage Essentials: • System Management Homepage • HP Systems Insight Manager 4.
• Do not enable IP Binding. You can optionally install other HP SIM components at a later time by running the HP SIM CD again on the HP SIM server and following the instructions in the HP SIM documentation once the Storage Essentials installation is complete. 5. Reboot the HP SIM server when prompted at the end of the HP SIM installation. 6. Do not set up discovery when prompted by the HP SIM First Time User wizard.
NOTE: The drive on which you install Storage Essentials must be NTFS format or the installation will fail. The directory in which you install the Storage Essentials management server must have write access for the local Administrators group. Be aware that installing the management server in a directory created by another program (for example: the Proliant Support Pack) is not recommended. Follow these steps to install Storage Essentials (for the HP SIM-integrated separate server installation option): 1.
\\cimext2 (Copy the CIM Extensions CD 2 installation files to this directory. Note that the CIM Extensions CD 2 is not required as part of this Storage Essentials management server installation.) b. Double-click setup.exe in the srm directory to which you copied the Storage Essentials installation files. The Storage Essentials for Windows installation wizard starts and the Welcome screen is displayed. 3. Click Next to continue. The Getting Started screen is displayed.
• Memory — The minimum RAM requirement varies depending on your installation option: • When HP SIM and Storage Essentials are installed on separate servers the minimum RAM requirement for the Storage Essentials server is 4 GB with 6 GB recommended. • When HP SIM and Storage Essentials are installed on the same server together the minimum RAM requirement for the Storage Essentials server is 6 GB with 8 GB recommended.
• 8009 • 8083 • 8093 If you see a warning in the Ports Availability requirement you need to check to be sure that the ports listed are not currently in use and make any changes that are necessary. Be aware that the installation will continue even if a required port is not available. NOTE: During upgrades, the Port Availability check may falsely indicate that the port for the management server is currently in use.
Step 4 – Verify that HP SIM is Running on the Remote Server Before the Storage Essentials installation wizard installs the HP SIM Connector component, you must verify that HP SIM is currently running on the remote HP SIM server you specified in the Installation Options screen.
IMPORTANT: You must have your license ready to import before you can set up discovery using the HP Systems Insight Manager’s First Time wizard. If you do not import your Storage Essentials license before setting up discovery using the HP SIM First Time User wizard, Storage Essentials cannot run its discovery and the Storage Essentials discovery will fail. 4. Click Finish accepting the default setting: Yes, reboot the system now. The Storage Essentials server must be rebooted.
IMPORTANT: Be sure to apply your Storage Essentials license before setting up discovery with the HP SIM First Time User wizard. See Step 8 – Obtain and Apply a Storage Essentials License Key Before Setting Up Discovery on HP SIM, page 26. Step 8 – Obtain and Apply a Storage Essentials License Key Before Setting Up Discovery on HP SIM If you see the HP Systems Insight Manager First Time User wizard, do not click the Do not automatically display this dialog again check box.
Step 11 – Install Your CIM Extensions and Set Up Discovery Before you can discover all of the elements (systems) on your network, you must install the CIM extensions that were copied to the management server during the installation as mentioned in the previous step. For more information about CIM extensions and setting up discovery, see the following chapters: See ”Deploying and Managing CIM Extensions” on page 181. See ”Discovery Steps” on page 109.
To install from the CDs do the following: a. Put the Storage Essentials CD in the CD drive of the designated Storage Essentials server. The Storage Essentials installation wizard program should start automatically. b. If it does not start, double-click setup.exe found in the root directory on the Storage Essentials CD. To install from a network or local hard drive, do the following: a.
IMPORTANT: The directory in which you install the management server must have write access for the local Administrators group. Be aware that installing the management server in a directory created by another program (for example: the Proliant Support Pack) is not recommended. 3. Read the information on the Welcome screen. Click the hypertext links on the screen to learn about service packs and other important requirements and click Next when you are ready to continue.
NOTE: In Storage Essentials, the HP SIM Administrator will be assigned the HP Storage Essentials Administrator role (Domain Admin). See ”About Security for the Management Server” on page 349 for more information. The installation wizard scans the system to verify that it meets the requirements specified in the support matrix and the Verify System Requirements screen is displayed showing the current status of the system. 7.
• Operating System — Windows 2003 Server SP1, SP2, R2, R2 SP2. The Storage Essentials installation or upgrade will not continue if the operating system requirement is not met. • Processor — A dual Intel XEON (or AMD equivalent) 3.4 GHz or higher CPU is required. If the CPU is close to the requirement, the installation wizard continues. • DNS Resolution — The installation wizard verifies the IP Address and DNS name of the server using nslookup.
NOTE: Because you are installing Storage Essentials and HP Systems Insight Manager on the same server, the CIM extension files are copied to the management server so that you can install the extensions on the hosts in your network at a later time. The CIM extensions are not installed, only copied to the management server during this installation. If you click Cancel during the installation, the installation wizard completes the installation of the current component before stopping.
b. Click the Import License File button. c. Click the Browse button. You are shown the file system of the computer being used to access the management server. d. Select the license file. e. Click OK. IMPORTANT: See ”Checking Installation Log Files” on page 380 for more information about installations and upgrades. Step 5 – Configure Browser Settings Configure your browser settings for HP SIM and Storage Essentials to function properly.
IMPORTANT: Be sure to apply your Storage Essentials license key before setting up discovery with the HP SIM First Time User wizard. See ”Step 4 – Obtain a License Key (Required to Start the Management Server for the First Time)” on page 32. Step 7 – Check for Required Service Packs and Hot Fix Files Check with your Sales Engineer to obtain and install the latest required service packs and hot fix files for Storage Essentials and HP Systems Insight Manager.
• CIM Extension files (Build 6.0—Common Information Module files that you install on the hosts and other network elements you want to manage and for which you want to automate discovery) • CIM Extension Management tool for installing some of the supported CIM extensions in batch mode, remotely, onto multiple hosts.
a. Put the Storage Essentials CD in the CD drive of the designated Storage Essentials server. The Storage Essentials installation wizard program should start automatically. b. If it does not start, double-click setup.exe found in the root directory on the Storage Essentials CD. To install from a network or local hard drive, do the following: a.
6. Choose the installation location. You can change the installation location of the management server and the Oracle database if you prefer. IMPORTANT: Valid locations must be entered on the Installation Options screen. Path information can only contain the following characters: A-z, 0-9, hyphen, underscore, period, back slash. Storage Essentials and the Oracle database paths cannot contain spaces. Drive letters must be fixed drives.
• With ARCHIVING and RMAN backup on: minimum disk space: 200 GB, recommended disk space: 350 GB. The installation or upgrade will not continue if the disk space requirements are not met. See the HP Storage Essentials 6.0 SRM User Guide for information about the archiving and RMAN backup features. • Operating System — Windows 2003 Server SP1, SP2, R2, R2 SP2. The Storage Essentials installation or upgrade will not continue if the operating system requirement is not met.
installation. The Storage Essentials installation wizard Status screen is displayed in the background. If you click Cancel during the installation, the installation wizard completes the installation of the current component before stopping. Once the component installation is complete, the installation wizard prompts you to confirm that you want to cancel. Click Yes to cancel or No to continue with the installation.
e. Select the license file. f. Click OK. Step 5 – Check for Required Service Packs and Hot Fix Files Check with your Sales Engineer to obtain and install the latest required service packs and hot fix files for Storage Essentials. Step 6 – Install Your CIM Extensions and Set Up Discovery Before you can discover elements (systems) on your network, you must install the CIM extensions that were copied to the management server during the installation.
are migrated to the Brocade SMI-S provider (note that the Brocade SMI-S provider is called the SMI-Agent in the Brocade documentation). Data such as topology and zoning from the Brocade switch will be stale and you will be unable to use the Brocade switch to perform provisioning or to gather port performance statistics through the Brocade switch.
HP SIM globalsettings.props file from True to false. This file can be found in the following directory on the HP SIM server: [SIM_Installation_Directory]\config\globalsettings.props • Windows 2000 is no longer supported. See the support matrix for your edition for complete information on supported Windows versions. • After upgrading, hosts are managed directly from the application server, and will no longer be managed by our internal CIMOMs.
About CIM Extensions and Backup Manager Hosts After Upgrading Upgrade CIM extensions on servers with the following functionality: • Backup Manager Hosts – Backup information is not gathered from legacy CIM extensions. In order for backup information to be gathered by the management server, the CIM extensions on the Backup Manager Host must be at the same build number as the management server.
Step 4 – Manually Upgrade HP SIM (Required Only When HP SIM is Running on a Separate Server) Skip this step to manually upgrade HP SIM if Storage Essentials and HP SIM are installed on the same server. When the two are installed on the same server, the Storage Essentials installation wizard automatically checks for HP SIM and walks you through the upgrade. Upgrade HP SIM in this step if HP SIM is running on a separate server. IMPORTANT: Stop the AppStorManager service prior to starting this step.
Step 5 – Manually Export the Database Manually export the database and create an image of the server. Export the database and create an image as described in the following steps. Make sure you select Export HPSIM Schema so that HP System Insight Manager data is exported. IMPORTANT: Make sure you save the backup in a directory structure that is not part of the management server installation directory. 1.
• The server must be running a supported operating system or the upgrade will fail. Refer to the support matrix for a valid operating system. • Microsoft Internet Explorer 6.0 SP1 or later must be installed or the upgrade will fail. • TCP/IP must be installed or the upgrade will fail. • *The upgrade will fail if SNMP and the SNMP trap service is not installed and enabled. The upgrade program tells you SNMP must be enabled and SNMP trap services must be installed.
If you click Cancel during the upgrade, the Storage Essentials upgrade wizard completes the upgrade of the current component before stopping. Once that component upgrade is complete, the Storage Essentials upgrade wizard prompts you to confirm that you want to cancel. Click Yes to cancel or No to continue with the installation.You can resume the upgrade by running the Storage Essentials upgrade wizard again.
Step 8 – Enable RMAN Backup if Desired RMAN Backup is disabled by default as part of the upgrade process. When you log into the management server after upgrading, you see a message informing you that RMAN Backup is disabled. You should re-enable RMAN backup as soon as possible to continue backing up your data.
Re-add Remote Sites in Global Reporter IMPORTANT: After the upgrade, all remote sites in the Global Reporters are removed. This is done so you can upgrade the remote sites to the same version before Global Reporter attempts to gather data. Before you re-add the remote sites, be sure to upgrade them to the same build number as the management server (Build 6.0 CIM extensions). All sites that provide global reports must be upgraded to the latest build of the management server.
4. Add desired remote sites, by clicking the New Site button and providing the appropriate information. Refer to the User Guide and online help for more information. 5. To upgrade the database with data from the added sites, click the Refresh Now button at the bottom of the page. Upgrade Your Storage Essentials CLI Clients CLI clients earlier than Build 6.0 do not work with Build 6.0 of the management server. Refer to the CLI Guide for more information about upgrading your CLI clients.
2. Install the Brocade SMI Agent with a minimum version of 120.6.0a and configure the proxy servers on the server with which you will manage your Brocade access points following the installation and configuration instructions included in the Brocade v120.6.0a Installation Guide. Refer to the Brocade document for SMI-A requirements. 3. Log on to the management server. HP Storage Essentials alerts you to migrate your Brocade Fabric Access API switches when you first log on.
4. Run HP SIM discovery for the Brocade proxy server. See the chapter, “Discovering Switches, Storage Systems, NAS Devices, and Tape Libraries.” 5. Run Discovery Data Collection. See the chapter, “Discovering Switches, Storage Systems, NAS Devices, and Tape Libraries.” The Brocade switches are migrated to the SMI-A provider.
Configurations Required for Discovering EMC CLARiiON Storage Systems The EMC Navisphere CLI is required for the management server to communicate with the CLARiiON storage system. At the time this documentation was created, EMC distributed the Navisphere CLI as part of the EMC Navisphere Software Suite. Contact your EMC representative for more information about obtaining the Navisphere CLI. Distribution rights for the Navisphere CLI belong to EMC.
Manager service aware of these changes. If you do not, the HP Systems Insight Manager service will not start and you will not be able to use HP SIM. To change the service account credentials for the HP Systems Insight Manager service: 1. Right-click the HP Systems Insight Manager service from the services panel. 2. Select Properties from the drop-down menu. 3. Click the Log On tab. 4. Change the user name (This account) and password on the Log On tab to match the information for the new credentials.
6. Use the Database Admin Utility to change the SIM_MANAGER password in the Oracle database. IMPORTANT: You must provide the same SIM_MANAGER password for the mxpassword command and the Database Admin Utility. a. To access the Database Admin Utility, go to the %MGR_DIST%\Tools\dbAdmin directory on the Storage Essentials management server and double-click dbAdmin.bat. If you are shown an error message when you start the Database Admin Utility, stop the AppStorManager service and click the Refresh button. b.
IMPORTANT: Use the Continue option only if you do not intend to use this installation of SIM either on its own or integrated with Storage Essentials. To remove Storage Essentials: 1. Stop the service for the management server (make sure HP SIM is/remains running) by doing the following: a. Go to the Services window (Start > Control Panel > Administrative Tools > Services). b. Right-click the AppStorManager service in the Services window. c. Select Stop from the drop-down menu. 2.
a. Open a Command Prompt window on the Storage Essentials management server (Start > Run > cmd.exe, click OK). b. Put the Oracle DVD in the DVD drive of the Storage Essentials management server. c. Change directory (CD) to the root of the Oracle DVD. d. Enter the following at the command prompt window on the management server to remove Oracle and the Storage Essentials management server database instance: cscript removeOracle10g.vbs Oracle is removed from the management server. 7.
58 Installing the Management Server on Microsoft Windows
3 Installing the Management Server on Linux NOTE: The Linux management server is not available with Storage Essentials Standard Edition. See the following topic if you are installing the management server on another supported operating system: • ”Installing the Management Server on Microsoft Windows” on page 7 Important Information About Upgrading Please contact your Account Representative for upgrades. Upgrading requires assistance from HP Services.
• Step 5 - Install the HP SIM Connector, page 85 • Step 6 - Configure SUSE Linux for Use with Business Tools, page 86 • Step 7 - Browse to HP SIM Home Page, page 87 • Step 8 - Configure Firefox, page 87 • Step 9 - Import a Storage Essentials License, page 88 • Installing the Java Plug-in on Linux, page 88 • Configurations Required for Discovering EMC CLARiiON Storage Systems, page 89 • Removing the Management Server, page 89 • Upgrading the Linux Management Server from Build 5.1 to Build 6.
Install any missing components from the Linux operating system CD before continuing with the installation. Pre-requisite RPMs for Oracle on Linux Verify that your system includes the required packages by using the following command: # rpm –q Required RPMs for Oracle 10g on RHEL systems: • binutils-2.15.92.0.2-10.EL4 • compat-db-4.1.25-9 • control-center-2.8.0-12 • gcc-3.4.3-9.EL4 • gcc-c++-3.4.3-9.EL4 • glibc-2.3.4-2 • glibc-common-2.3.4-2 • gnome-libs-1.4.1.2.90-44.1 • libstdc++-3.4.3-9.
• libaio-devel • libstdc++ • make-3.80 • openmotif-libs • sysstat-6.0.2 • orarun-1.9-21 The preceding information is taken from http:/www.novell.com/products/server/oracle/oracle10g_install.html. RPMs for SLES 9 can be found at http://www.novell.com/products/server/oracle/software.html and RPMs for SLES 10 can be found in the SLES 10 product CD. NOTE: The orarun-1.9 package is available from http://ftp.novell.com/partners/oracle/sles-10/orarun-1.9-21.15.i586.rpm.
package named “XFree86-Xvfb” and then re-run the management server installation. This package is available on the SUSE 9 CD’s. The following shows a representative example of the error message that would be displayed. Figure 1 Missing Xvfb Package Message Verify Network Settings Verify the network configuration for the management server: 1. Verify that the appropriate DNS server entries are present in /etc/resolv.conf.
NOTE: If the ping command fails to ping the IP address and instead pings the loopback address, the oracle listener process will fail to start and therefore, the CIMOM process will also fail. 3. Enter the following command: nslookup where is the hostname (without domain name) of the management server. 4. Enter the following command: nslookup where is the IP address of the server. 5.
Install the database for the management server on a computer that does not already have Oracle installed. In later steps, you will install the management server on the same machine that you installed Oracle. Before Installing the Oracle Database Keep in mind the following: • Refer to the support matrix for your edition for system requirements. • Once you start the installation, do not exit. The Oracle installer creates the orauser file within the first few minutes of the installation.
NOTE: If the Oracle installation fails, a re-install will not run successfully because of existing files or existing Oracle user. In such a case, uninstall Oracle using the Oracle uninstall script. Refer to step 6 of ”Removing the Management Server” on page 89. Installing the Database To install the database: 1. Login to the Linux host as root user. 2.
6. The oracle installer script checks for required RPMs and terminates if any required RPM is missing. In such case, install the missing RPMs and restart the installation. INFO: Checking for required packages... ERROR: sysstat is not installed. ERROR: Please install missing pre-requisite packages before proceeding with installation. Terminating installation. If the installer finds a different version of a pre-requisite RPM, it will prompt the user to confirm continuing the installation.
8. The temporary disk space in /tmp is checked. If the disk space in /tmp is less that 400 MB, the installation will abort with the below message. ERROR: You need at least 400MB in the /tmp directory. You only have 100 MB. Terminating installation. 9. Appropriate kernel parameters are automatically set by the installation script. Figure 2 Setting Kernel Parameters 10.On SUSE systems, the oracle user account should be enabled prior to starting the installation.
13.If you are running Red Hat Enterprise Linux AS 4 or RHEL 4.0, you will be asked to enter the password for oracle user. Enter the password when prompted. 14.Enter “y” when asked to start the Oracle Universal Installer. For RHEL 4.0, text similar to the following console output may display. (Representative console output for SUSE 10 and SUSE 10 SP1 is also included at the end of this example following the “Note” information.) Starting Oracle Installer... Starting Oracle Universal Installer...
NOTE: The warning messages in the above console output can safely be ignored. NOTE: The Oracle Installer that comes with the Oracle Database Server Patch 10.2.0.1 does not officially support SUSE 10; however, the Oracle database is supported on SUSE 10. The resulting error messages can be safely ignored. Also, “Failed” and “Not Executed” check complete messages in the pre-requisites result can be safely ignored.
Installer, Version 10.2.0.1.0 Production Copyright (C) 1999, 2005, Oracle. All rights reserved. You can find a log of this install session at: /opt/oracle/oraInventory/logs/installActions2007-09-29_07-40-00PM.log Starting execution of Prerequisites... Total No of checks: 11 Performing check for CertifiedVersions Checking operating system requirements ... Expected result: One of redhat-3,redhat-4,SuSE-9,asianux-1,asianux-2 Actual Result: SuSE-SUSE Linux Enterprise Server 10 (i586) Check complete.
The following is the output of the script. Your output may differ slightly based on the file paths you entered. Oracle Database 10g Installation : OK ---------------------------------------------------------------------INFO: Running root.sh... ----------------------------------------------------------------------Runni ng Oracle10 root.sh script... The following environment variables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /opt/oracle/product/10.2.0.
After upgrading to Oracle 10.2.0.3, the installer will execute root.sh from $ORACLE_HOME. The user does not have to open a new terminal window and run the script as mentioned in the following representative example. The following configuration scripts need to be executed as the "root" user. /opt/oracle/product/10.2.0.1/root.sh To execute the configuration scripts: 1. Open a terminal window 2. Log in as "root" 3. Run the scripts The installation of Oracle Database 10g Release 2 Patch Set 2 was successful.
The installation is done in silent mode and output similar to the following displays when the installation begins: INFO : Checking the OS Release... Found SUSE LINUX Enterprise Server 9. Installing Oracle 10g Release 2 Critical Patch INFO: Installing Oracle 10g Release 2, October Patch 6121183 installed successfully. INFO: Installing Oracle 10g Release 2, October Patch 6121242 installed successfully. INFO: Installing Oracle 10g Release 2, October Patch 6121243 installed successfully.
Patch 6397929 installed successfully. INFO: Installing Oracle 10g Release 2, October 2007 CPU : 6397937 Patch 6397937 installed successfully. INFO: Installing Oracle 10g Release 2, October 2007 CPU : 6397938 Patch 6397938 installed successfully. INFO: Installing Oracle 10g Release 2, October 2007 CPU : 6397939 Patch 6397939 installed successfully. INFO: Installing Oracle 10g Release 2, October 2007 CPU : 6397940 Patch 6397940 installed successfully.
b. Verify that the line for the screen number 0 (the line containing :0 local) does not contain the -nolisten tcp option. Remove the -nolisten tcp option if present. The line should look like: :0 local /usr/X11R6/bin/X c. Enable TCP connections on the X server of the remote client: SUSE - Edit /etc/sysconfig/displaymanager and set the following options to yes: DISPLAYMANAGER_REMOTE_ACCESS and DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN.
• When you install the management server on Linux, you must install the software using a POSIX (Portable Operating System Interface) shell, such as sh. C Shell is not supported. • 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.
2. If installing from CD-ROM: Insert the CD-ROM for installing the management server in the CD-ROM drive of the server and mount it by using the following commands: # mkdir -p /mnt/installer # mount /dev/cdrom /mnt/installer where /dev/cdrom is the CD device.
CAUTION: Do not select 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. You can obtain it easily from the management server (Security > Licenses). 9. Enter the following at the command prompt: # /etc/init.
Output resembling the following is displayed: ########################################################################## # Begin of O R A C L E status section # ########################################################################## Kernel Parameters Shared memory: SHMMAX= 3294967296 SHMMNI= 4096 SHMALL= 2097152 Semaphore values: SEMMSL, SEMMNS, SEMOPM, SEMMNI: 1250 32000 100 256 Database-Instances Instance * is down \(autostart: N\) Instance APPIQ is up \(autostart: Y\) TNS-Listener: up Process list for
IMPORTANT: If you are starting the processes manually, start the Oracle process before the process for the management server. 3. To verify that the required processes for the management server have started, enter the following at the command prompt: # /etc/init.d/appstormanager status The following is displayed if the processes have started: Checking for Cimom Service... Cimom Service - RUNNING. Checking for appstormanager service... appstormanager service - RUNNING. 4.
4. Check to see if the file /etc/oratab has an entry that looks like APPIQ:/opt/oracle/product/10.2.0.1:Y If it does, then as the root user, delete the line and save the file. 5. If they exist, as root user, delete the APPIQ directories under /opt/oracle/product/ 10.2.0.1/oradata and /opt/oracle/product/10.2.0.1/admin: rm -rf /opt/oracle/product/10.2.0.1/oradata/APPIQ rm -rf /opt/oracle/product/10.2.0.1/admin/APPIQ Do not remove the Oracle Software.
NOTE: This path may differ if Oracle is not installed in the default path • Force[N]: For fresh installations, select the default [N]. If the initial installation fails, select [Y] for subsequent installations. • Select defaults for the rest of the options and install. 5. Initialize and configure HP SIM by executing the following command: #/opt/mx/bin/mxinitconfig -a NOTE: The initialization is done in the background and takes several minutes. 6.
3. Enter the following at the command prompt: [/opt/mx/bin]# ./mxpassword -m -x MxDBUserPassword=mynewPass where mynewPass is your new password for the Oracle database. 4. Run the following command to stop the HP Systems Insight Manager service so that it cannot access the database: # /opt/mx/bin/mxstop IMPORTANT: It is very important that the HP Systems Insight Manager service does not access the Oracle database before you are finished with changing the password for the Oracle database. 5.
Step 5 - Install the HP SIM Connector The HP SIM Connector lets Storage Essentials communicate with HP SIM. Install the HP SIM Connector on the same server running Storage Essentials. To install the HP SIM Connector: 1. Stop the appstormanager process with the following command: # /etc/init.d/appstormanager stop 2. Make sure these three HP SIM mxdomainmgr, mxdtf, and mxinventory processes are running on the HP SIM server by using the following command: # ps -ef | grep mx 3.
10.Verify that the HP SIM mxdomainmgr, mxdtf, and mxinventory processes are running by entering the following command: # ps -ef | grep mx NOTE: You can also verify that the HP SIM processes are running by waiting until you can browse to the HP SIM server (https://:50000). 11.Start the Storage Essentials process by entering the following command: # /etc/init.d/appstormanager start 12.Verify that the Storage Essentials process has started by entering the following command: # /etc/init.
2. Restart Storage Essentials by entering the following command: # /etc/init.d/appstormanager restart 3. Enter the following command: # . /install/setvars.sh where is the directory containing the software, the default value being /opt/HP_Storage_Essentials 4. Run appiqconfig and input the HP SIM credentials. Use the default settings when applicable.
5. Launch Firefox by entering the following command: # /usr/sbin/firefox/firefox 6. Open Firefox Preferences by selecting Edit > Preferences. 7. Select Connection Settings and set the Manual proxy configuration appropriately. Select the Use this proxy server for all protocols checkbox. 8. Select the Content tab and disable the pop-up blocker.
NOTE: Remember the dot at the end of the command. NOTE: If you create this symbolic link in any directory other than $HOME/.mozilla/plugins, your browser will not be able to use this new Java plug-in. 7. If you are a root user on the server and you want to make the plug-in available to all users, create a symbolic link to the Java plug-in that is in the plugins directory under the browser's installation directory.
where is the directory containing the software, the default value being /opt/ 3. To remove leftover files from the management server, remove the directory for the management server by entering the following at the command prompt: # rm -rf where is the directory containing the software, the default value being /opt/ 4.
removed. Console output similar to the following displays and you will see a message similar to that shown: “Removing database...”. INFO : Checking the OS Release... Found SUSE LINUX Enterprise Server 9. INFO: Checking System architecture... OK. #### This script uninstalls Oracle 10.2.0.
no crontab for oracle Done. 7. Verify that the directory /opt/oracle AND the account “oracle” do not exist. NOTE: Files created during Oracle install are removed along with the oracle user account. Since SLES systems require an oracle user account to be present before installing, make sure the correct version orarun RPM is installed before installing Oracle 10g again. For SLES9, orarun RPM can be found at: http://ftp.novell.com/partners/oracle/sles-9/ For SLES10, orarun RPM can be found in the product CD.
• The latest build of the software requires you to upgrade some of your CIM Extensions. Please refer to “About Upgrading Your CIM Extensions” (in the Deploying and Managing CIM Extensions chapter) for details. • The installation will fail if there is insufficient temporary space. You must have at least 2 GB in the /tmp directory. • After you upgrade the software, you are required to run HP SIM Discoveryand do Discovery Data Collection on all new and existing managed elements.
• The Brocade switch manufacturer no longer supports the Brocade Fabric Access API provider and as a result, this release of the management server does not support the Brocade Fabric Access API after updating.
Table 1: Upgrade New Install Description migrateData.sh Not Applicable Verifies if the database is created properly and imports database exported by upgradeAppStorManager.sh Install HP SIM Connector Install HP SIM connector for Build 6.0.0 Install SIM connector for Build 6.0.0 Steps to Upgrade the Management Server Step 1 - Read the Support Matrix and Release Notes Read the support matrix and release notes.
Step 5 - Run the upgradeAppStorManager Script Run the upgradeAppStorManager.sh script from the Oracle disk to begin the upgrade process. • The script upgradeAppStorManager.sh initiates the upgrade process. It checks for prerequisite conditions and exits if any condition is not satisfied. It stops running services and exports the current database to a temporary location. All output will be logged to a time stamped file named upgradeAppStorManager_.log in /var/tmp/.appstor.
Continue if the password is reset [y/n] At this time, you should login to the remote SIM system and run the mxpassword command to reset the password at the SIM end, and then continue the upgrade procedure by typing 'y' at the prompt. Step 6 - Run the uninstallOracle9i Script NOTE: Before running uninstallOracle9i.sh, make sure that AppStormanager service is not running. You should also make sure that the HP SIM service is not running. Run the uninstall script to uninstall the Oracle 9i installation.
• An Oracle account is created automatically for Red Hat Linux machines. If the Oracle account is not enabled for SUSE Linux machines, then the InstallDatabase script will exit with an error. To enable the account on SUSE Linux machines, edit /etc/passwd and set the path to the shell. • Once Oracle 10g is installed, source the orahome created after the Oracle 10g installation by running . /var/opt/oracle/orahome and note there is a space between the period (.) and /var.
IMPORTANT: It is critical that you start SIM before you start Storage Essentials.
• Host for which you want to retrieve cluster information (i.e., Veritas Cluster Server on Solaris cluster and Microsoft Cluster Server). (This is new functionality that requires version 6.0 of the CIM extension.) • Linux hosts that support QLogic failover. (This is new functionality that requires version 6.0 of the CIM extension.) Step 15 - Rediscover All Elements You should rediscover all elements after you do an upgrade by doing HP SIM Discoveryand Discovery Data Collection.
switch will be stale and you will be unable to use the Brocade switch to perform provisioning or gather port performance statistics through the Brocade switch. Any Brocade switches that are managed with the Brocade Fabric Access API provider will be quarantined after upgrading the management server. The management server retains the data for the API switches after upgrading, but you cannot do Discovery Data Collection until you migrate Brocade switches to the Brocade SMI Agent provider.
installation and configuration instructions included in the Brocade v120.6.0a Installation Guide. Refer to the Brocade document for SMI-A requirements. 3. Log on to the management server. HP Storage Essentials alerts you to migrate your Brocade Fabric Access API switches when you first log on. Your Brocade switches are quarantined until you migrate to the SMI-A provider.
The Brocade switches are migrated to the SMI-A provider. IMPORTANT: Before performing any provisioning operations that involve a Brocade switch you must perform Discovery Data Collection for any subset of elements that includes the Brocade switch. 6.
104 Installing the Management Server on Linux
4 Discovering Switches, Storage Systems, NAS Devices, and Tape Libraries Before you can use the management server, you must execute the Discovery process to make the software aware of the elements on your network, such as switches, storage systems, NAS devices, and tape libraries. Discovery obtains a list of elements and information about their management interface and dependencies. NOTE: The management server can discover only elements with a suitable management interface.
About Discovery When HP Storage Essentials is integrated with HP SIM, Discovery and Discovery Data Collection are performed using HP SIM’s discovery user interface pages. This allows you to use credentials and perform discovery and data collection tasks in HP SIM and enables hardware and software health status polling, monitoring, and event management for storage, servers, switches, infrastructure, and other elements on your network, such as enclosures, racks, clients and printers.
Note the following: • Storage systems managed by HP Storage Essentials show a subtype of Storage Essentials Managed, and do not show the SMI subtype on the HP SIM System tab. • Storage systems managed by HP Storage Essentials are listed in the HP SIM Storage Essentials Systems collection. • HP SIM data collection from SMI-S devices is disabled to avoid duplicate data collection.
4. A host containing a Host Bus Adapter (HBA). All Fibre Channel host bus adapters look for available elements attached to the HBA. This information is gathered by CIM extensions and sent to the management server. NOTE: Since CIM extensions have not been installed yet, the management server will not be able to obtain this data when you perform discovery for elements.
For example, in the phased discovery described in ”Discovering Elements” on page 113, you could discover your switches first. In this case, you would enter only the global credentials that apply to the switches. After successfully running the switch discovery task, you would replace the switch credentials with the global protocol settings for the next set of elements you want to discover. • Some elements lock you out without warning after multiple failed login attempts.
selective discovery filter to configure the environment so only that subset of servers is processed by both HP Storage Essentials and HP SIM. For more information, see ”Selective Discovery Filter” on page 155. Configuring the HP SIM Connector to Pass Devices with the DNS Name (Optional) By default, HP SIM passes IP addresses to HP Storage Essentials. You can configure the HP SIM Connector to pass elements to HP Storage Essentials so that the DNS name is displayed in HP Storage Essentials discovery lists.
SIM) and set up your HP SIM discovery. See Step 8 – Obtain and Apply a Storage Essentials License Key Before Setting Up Discovery on HP SIM, page 26. • Enter the requested information including SNMP Read community strings. • Do not enter global WBEM user names and passwords on the WBEM page. • Do not run the initial discovery process at the end of the wizard. See the HP Systems Insight Manager User Guide for more information about the First Time Wizard.
The Discovery Setup, Step 1 - Setup page shows the HP Storage Essentials management server as localhost. Figure 6 HP Storage Essentials Management Server “localhost” Discovering the HP Storage Essentials Management Server You do not need to install a CIM extension on the management server because it is monitored through a built in CIM extension that is installed automatically during the HP Storage Essentials installation. Built-in credentials are used to access the localhost.
e. In the WBEM settings section, select Update values for this protocol and Use values specified below. f. Enter the user name and password for the HP Storage Essentials management server (the administrator account) in the format domain\administrator or servername\administrator. 9. Select Options > Discovery. 10.Select the discovery task you created in step 2, and then click Run Now. 11.
IMPORTANT: For best results, enter only global credentials that apply to the set of elements for the current discovery task. When this discovery task is complete, you can delete the element-specific global credentials and enter global credentials for the next set of elements you want to discover. 3. Select Options > Discovery. 4. Click New on the HP SIM Discovery page Automatic tab. 5. Enter a name for the discovery task in the Name box. 6. Clear the Automatically execute discovery every check box. 7.
11.Select the discovery task created in step 4, and then click Run Now. When complete, the task monitor shows 100%. Within two minutes, the status in the SE Identification column changes from Pending to Running. You can click the Running link to view the HP Storage Essentials Discovery progress table. Figure 7 HP Storage Essentials Discovery progress table NOTE: SE discovery processing might finish before the SE Identification column shows status as Running.
the Discovery process. For more information on switch support, see the support matrix in the Documentation Center (Help > Documentation Center in HP Storage Essentials). IMPORTANT: Table 4 All SMI-S switches require a user name and password. Overview of Switch Discovery Requirements Element Discovery Requirements For More Information Brocade switches (SMI-S) IP address and the user name and password from the Brocade SMI Agent security setup. See Discovering Brocade Switches, page 116.
periodically to verify that you are running a current version of the Brocade SMI Agent. For more information on Brocade SMI Agent versions, see the support matrix. IMPORTANT: With this release, discovery of Brocade switches through the Fabric Access API is not supported. For information on migrating existing Brocade API switches to SMI-S, see ”Migrating Brocade API Switches to SMI-S After Upgrading” on page 117.
Comply with the installation notes included in the following document: ftp://ftp.compaq.com/pub/products/storageworks/smisproviders/brocade_provider.pdf This document is written for an earlier version of the Brocade SMI Agent, but the installation notes and other information also apply to v120.6.0a of the Brocade SMI Agent software. 3. Log on to HP Systems Insight Manager and access the Storage Essentials management server (from HP SIM, select Tools > Storage Essentials).
4. Run HP SIM discovery for the Brocade proxy server. See the chapter, “Discovering Switches, Storage Systems, NAS Devices, and Tape Libraries.” 5. Run Discovery Data Collection. See the chapter, “Discovering Switches, Storage Systems, NAS Devices, and Tape Libraries.” The Brocade switches are migrated to the SMI-A provider.
• If you selected Yes in the Brocade SMI Agent Enabling Security window, and you disabled Windows domain authentication, the username and password are the Windows local administrator account username and password. • If you selected No in the Brocade SMI Agent Enabling Security window, you can enter any username and password because security for the proxy server was not enabled.
a. Open the file ProductInfo.ini in a text editor, such as Notepad. If the software was installed in the default directory, this file should be in the following directory: \Program Files\CNT\inVSN_EM b. Make the following entry in the file: cimomenabled=TRUE c. Save the file, and then restart the InVsn software. 3. Enter the following information in HP SIM: • Primary IP address of the host running the InVsn software you want to discover. • Namespace.
• Before you can discover Cisco switches with SMI-S, you must download and install the Cisco cimserver software. See the HP StorageWorks C-Series document for instructions. You can access this document at: http://www.hp.com/go/hpsim/providers. • Enable the CIM Server for Cisco switches discovered through the SMI-S provider. a. On the Cisco switch, enter the following command to display the Common Information Models (CIM) configurations and settings: cisco_switch# show cimserver b.
Discovering Sun StorEdge, QLogic and HP StorageWorks M-Series for p-Class BladeSystems The management server discovers Sun StorEdge switches through an SNMP connection and QLogic and HP M-Series switches are discovered through SNMP or SMI-S. See the support matrix for your edition for details on supported switch models and firmware versions. Note the following when discovering these switches with SNMP: • HP SIM does not allow blank passwords.
IMPORTANT: Provide the SNMP credentials in the WBEM settings section on the System Protocol Settings page (Options > Protocol Settings > System Protocol Settings). Only the WBEM default credentials are passed from HP SIM to HP Storage Essentials. Any default credential information you set up in regards to SNMP is not passed from HP SIM to HP Storage Essentials. • System name or primary IP address of the switch you want to discover.
Table 5 Discovery Settings for McDATA and Connectrix Switches Method Description Provisioning limitations SNMP setting Through a Proxy Contact the switch through a proxy. You can use this option with EMC Connectrix™ Manager and EFC Manager to contact the switch. For more information, see ”Discovering McDATA and Connectrix Switches through a Proxy with SNMP” on page 128. This SNMP setting through a proxy does not let you manage or access information about zones, zone sets, or zone aliases.
Discovery Data Collection), and then click the Properties tab. The Properties tab can also be accessed by double-clicking the switch in System Manager. • If you want to add, remove, or replace McDATA or Connectrix switches after you have discovered the service processor, you must perform additional steps, see ”Managing McDATA and EMC Connectrix Switches” on page 132. • All McDATA or Connectrix switches in a fabric must be managed by the same EFC Manager or Connectrix Manager.
• If you selected direct mode during the SMI-S provider installation, when you add switches, you must enter the switch type based on the McDATA model number even if your switch is an OEM model. For more information about the switch type, see your McDATA documentation. • The SMI-S provider can be installed on the same server as EFC Manager or Connectrix Manager. • If you selected coexist mode during the SMI-S provider installation you can have only one EFC Manager or Connectrix Manager server.
IMPORTANT: EMC customers using the EMC Connectrix Manager (EMC’s rebranded EFC Manager) 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 it and install McDATA’s Bridge Agent.
IMPORTANT: Provide the SNMP credentials in the WBEM settings section on the System Protocol Settings page (Options > Protocol Settings > System Protocol Settings). Only the WBEM default credentials are passed from HP SIM to HP Storage Essentials. Any default credential information you set up in regards to SNMP is not passed from HP SIM to HP Storage Essentials. 1. Change the discovery setting for McDATA and Connectrix switches to SNMP following the steps in ”Changing the Discovery Settings” on page 130. 2.
1. Make sure there are no port conflicts for receiving SNMP traps. When the management server is configured to contact the proxy by SNMP, it receives events from the proxy in the form of SNMP traps. By default, the management server uses port 162 to receive SNMP traps. If another software package is using that port, the management server is unable to receive the traps.
b. Change the cimom.mcdata.dontUseSmis property as follows: cimom.mcdata.dontUseSmis=true NOTE: The cimom.mcdata.dontUseSmis property exists only in upgrade installations. If the property does not exist on your system, enter it manually. To enable SMI-S: a. Comment out the cimom.useSnmpMcDataProvider property by placing a pound sign (#) in front of it. b. Change the cimom.mcdata.dontUseSmis property as follows: cimom.mcdata.dontUseSmis=false. 1. Click Save. 2. Discover the switch.
IMPORTANT: The IP addresses of excluded elements appear in the discovery (Tools > Storage Essentials > Home > Discovery > Setup), topology (Tools > Storage Essentials > Home > Discovery > Topology), and Discovery Data Collection (Options > Storage Essentials > Discovery > Run Discovery Data Collection), lists. The management server does not display additional information about excluded elements in the user interface.
IMPORTANT: Obtaining details takes some time. You might want to perform this process when the network and the managed elements are not busy. To run Discovery Data Collection: 1. Select Options > Storage Essentials > Discovery > Run Discovery Data Collection. 2. Click Get Details. During Discovery Data Collection, the software status light changes from green to red. You can view the progress of gathering details by accessing the logs. For more information, see ”Viewing Log Messages” on page 160.
7. Click Save. Discovering Storage Systems Use the workflow in ”Discovering Elements” on page 113 to discover storage systems. This section provides information about supported storage systems, including the information to enter in HP SIM during the discovery process. For more information on device support, see the support matrix. The support matrix is accessible from the Documentation Center (Help > Documentation Center in HP Storage Essentials).
Table 6 Discovery Requirements for Storage Systems (continued) Element Discovery Requirements For Additional Information HP EVA storage systems Discover the server running Command View EVA. See Discovering HP StorageWorks EVA Arrays, page 143. HP XP storage systems Discover the server running the SMI-S provider or the built-in provider. See Discovering HP StorageWorks XP Arrays, page 145. IBM storage systems and System Storage SAN Volume Controller Discover the IBM CIMOM or SVC.
Discovering EMC Solutions Enabler If you are using a nethost file, edit it to allow the management server to discover the Solutions Enabler and the Symmetrix storage systems that it manages. See the EMC documentation for details. To discover Symmetrix storage systems, you must create and configure a VCM volume on the storage system. The VCM database on the Solutions Enabler host must also be configured. For more information, see the EMC Solutions Enabler Symmetrix CLI Command Reference.
If the cimom.symmetrix.exclude property is not specified, the management server discovers and obtains details from all EMC Symmetrix Storage Systems managed by discovered Solutions Enablers. IMPORTANT: The IP addresses of excluded elements appear in the discovery (Tools > Storage Essentials > Home > Discovery > Setup), topology (Tools > Storage Essentials > Home > Discovery > Topology), and Discovery Data Collection (Options > Storage Essentials > Discovery > Run Discovery Data Collection), lists.
To exclude EMC Symmetrix storage systems from a forced refresh: 1. Select Options >Storage Essentials > Manage Product Health > Advanced. 2. Click Show Default Properties at the bottom of the page. 3. Copy the following command. #cimom.emc.skipRefresh=000183500570,000183500575 4. Click Close to return to the Advanced page. 5. Paste the copied text into the Custom Properties box. 6. Remove the pound (#) symbol in front of the property to make sure it is not commented out.
• IP_of_my_management_server is the IP address of the computer running the management server software When you use the management server to discover the CLARiiON storage system, provide the IP address for the CLARiiON storage system and the user name and password used to log into Navisphere. Discovering LSI Storage Systems When discovering LSI storage systems, note the following: • Discover all controllers on an LSI storage system by entering the IP address of each controller.
Discovering HDS Storage Systems HiCommand Device Manager is required for the management server to communicate with an HDS storage system. To discover an HDS storage system, enter the IP address, user name, and password for the server running HiCommand Device Manager. Do not point to the disk array for the storage system. To obtain information about HDS storage systems, the management server must be able to access the port that HiCommand Device Manager uses to listen.
Storage Essentials > Home > Discovery > View Logs) that a provider instance has been created for an excluded element. You can ignore this message in the logs. To modify the cimom.hds.exclude property: 1. Select Options > Storage Essentials > Manage Product Health, and then click Advanced in the Disk Space tree. 2. Click Show Default Properties at the bottom of the page. 3. Copy the following command. #cimom.hds.exclude=61038,61037 4. Click Close to return to the Advanced page. 5.
4. Click Close to return to the Advanced page. 5. Paste the copied text into the Custom Properties box. 6. Remove the pound (#) symbol in front of the property to make sure it is not commented out. Add the serial numbers corresponding to the HDS storage systems you want the refresh to skip. Separate additional serial numbers with a comma, as shown by the following example: cimom.HdsSkipRefresh=61038,61037 where 61038 and 61037 are serial numbers for HDS storage systems.
• The MSA SMI-S provider updates its cache every four minutes. If the array is managed by an application other than HP Storage Essentials, changes to the array configuration might not be reflected by a Discovery Data Collection task that ran before the cache update.
NOTE: login. The user name and password are the credentials of the Command View EVA administrator Obtaining SNMP Traps using Command View EVA You must configure Command View EVA so it can send SNMP traps from the EVA to HP Storage Essentials. When the management server receives these SNMP traps, it converts them to WBEM Indications for display in its Event Manager. HP Storage Essentials then forwards the events to HP SIM's event console.
5. Click Close to return to the Advanced page. 6. Paste the copied text into the Custom Properties box. 7. Change the value by entering cimom.snmpTrapListenerCommunityString= where is the desired community string value. 8. Click Save. Viewing or Changing the Community String in Command View EVA 6.x To view or change the community string: 1. Open the c:\hsvmafiles\nsaserver.ini file in a text editor on the Command View EVA server. 2.
NOTE: HP StorageWorks Command View XP should be installed on a server before you discover an HP XP storage system. Discovering HP XP Arrays by Using Command View XP and SMI-S Before you can discover XP arrays, you must download and install the XP SMI-S Provider software. For instructions, see the HP StorageWorks XP Disk Array and Command View XP document for your version of Command View XP. You can access this document at: http://www.hp.com/go/hpsim/providers.
NOTE: The user name and password must be for a Partition Storage Administrator account. Discovering IBM Storage Systems or IBM SVCs Before you can discover an IBM storage system or an IBM System Storage SAN Volume Controller, you must have the IBM CIM Agent installed. For Enterprise Storage Server (ESS) devices, the IBM CIM Agent is called “CIM Agent for ESS”; for DS devices and mixed DS and ESS environments, use the “CIM Agent for DS Open (API)”.
7. Verifying that the CIM Agent is able to communicate with the storage devices. Enter the following command to verify communication: verifyconfig -u username -p password where username and password are the credentials to access CIM Agent and were created by setuser.
• Sun StorEdge CIM/WBEM Provider SDK (SUNWagsdk package) - Follow the instructions in the readme file that is installed with the SUNWagsdk package. • Sun StorEdge 3510 SMI-S Provider (SUNW3x10a package) - Follow the instructions in the readme file that is installed with the SUNW3x10a package. 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.
Discovering NAS Devices and Tape Libraries Use the workflow in ”Discovering Elements” on page 113 to discover NAS devices and tape libraries. This section provides information about supported NAS devices and tape libraries, including the information to enter in HP SIM during the discovery process. For more information on device support, see the support matrix. The support matrix is accessible from the Documentation Center (Help > Documentation Center in HP Storage Essentials).
5. Open the file and locate the following line: # Set to true to enable NAS data collection; “false” is the default nas=false 6. Change the value to true to enable NAS support, as shown in the following example: nas=true 7. Save your changes and close the file. 8. Restart the CIM extension. Discovery Information for HP NAS Devices on Windows To discover an HP NAS device, enter the following information in HP SIM: • IP address or system name of the HP NAS device to discover. • User name of the HP NAS device.
• If you want to communicate with the NetApp NAS device through SSL you must set the cimom.providers.netapp.useSSL property to true. This is a global setting and will cause all NetApp NAS devices to communicate using SSL. For more information, see ”Enabling SSL Communication with a NetApp NAS Device” on page 152. • If you want the management server to be able to receive events from a NetApp NAS device, you must add the IP address of the management server to the NetApp configuration.
Discovering Sun NAS Devices NOTE: You do not need to provide the interop namespace because it is included in the management server’s list of default namespaces. To discover a Sun NAS device, enter the following information in HP SIM: • IP address or system name of the server running the provider for the Sun NAS devices you want to discover. • User name of the provider for the Sun NAS devices you want to discover. You must provide a privileged login.
About Discovery Data Collection Discovery Data Collection is required to obtain detailed information from discovered elements. Discovery Data Collection must be performed before you can do provisioning and/or obtain provisioning information, such as data about zone sets and LUN numbers. Keep in mind the following: • Running Discovery Data Collection takes time. You might want to perform this process when the network and the managed elements are not busy.
discovering master backup servers, see ”Step 1 — Discovering Your Hosts and Backup Manager Hosts” on page 297. 3. Select Force Device Manager Refresh if you want the management server to tell the device managers for your storage systems to obtain the latest information.
Other Discovery Features This section contains the following topics: • Selective Discovery Filter, page 155 • Discovering a Single Element using the Manual Tab, page 158 • Changing Credentials for Discovery, page 159 • Saving Discovery Settings to a Hosts File, page 159 • Viewing Log Messages, page 160 • Viewing the Status of System Tasks, page 161 • Using Discovery Groups, page 162 • Deleting Discovered Elements, page 164 • Working with Quarantined Elements, page 166 • Updating the Database with Element Ch
NOTE: The globalsetting.props file is located in /config on Windows and /etc/opt/mx/config on Linux. This setting allows the HP SIM Connector to access the new filter file without being restarted. After the HP SIM Connector accesses the file, you can change this setting to false if there will not be any changes in the future. With the false setting the file will not get loaded again when the filter is needed because the HP SIM Connector uses the cached and compiled filter.
• If an IP address exists in both the exclusive and inclusive lists, the exclusive filter takes priority and the IP address is not passed to HP Storage Essentials. • If the inclusive and exclusive flags are missing from the file, any IP addresses in the file will be considered inclusive. • Any IP addresses, ranges, or patterns that follow the inclusive flag are considered part of the inclusive list until the end of the file or the exclusive flag.
NOTE: When entering filters, follow the ”Editing Rules for the Selective Discovery Filter” on page 156. 4. Save the file in the following directory on the HP SIM management server. • Windows: /config • Linux: /etc/opt/mx/config Discovering a Single Element using the Manual Tab IMPORTANT: When HP Storage Essentials is integrated with HP SIM, running discovery from the Automatic tab provides the best feedback for HP Storage Essentials discovery.
IMPORTANT: These procedures change only the user name and password stored in the database for HPSIM. They do not change an element user name and password. If you change a credential through the HP SIM CLI, you must run discovery to pass the credential to HP Storage Essentials. To change a system protocol setting: 1. Select Options > Protocol Settings > System Protocol Settings. 2. Select the target system, and then click Next. 3.
6. Click OK to save the hosts file. The saved file appears on the Hosts Files page. NOTE: See the HP SIM documentation for more information about hosts files. Importing a Hosts File NOTE: If you import a Hosts file and use it for discovery in HP SIM, you must discover the HP Storage Essentials management server as described in ”Enabling Product Health Monitoring” on page 111 and ”Discovering the HP Storage Essentials Management Server” on page 112.
For example, if a host was not discovered, the log messages might indicate that the provider configuration for that device was never created. This could mean the software was given the wrong user name and/or password for that host. As a result, the software logged onto the host with a guest account, which does not have enough permissions to start Windows Management Instrumentation (WMI). NOTE: The logs show data from the most recent discovery, test, or data collection task.
NOTE: For more about data collection, see ”About Discovery Data Collection” on page 153. When planning discovery groups, consider the following requirements and capabilities: • By default, HP Storage Essentials is configured with a default discovery group plus four additional groups. • Discovery groups affect the amount of memory needed for HP Storage Essentials.
IMPORTANT: Do not run Discovery Data Collection for all discovery groups simultaneously. 5. Click OK to save and return to the previous window. The elements are selected in the elements table. 6. Click Get Details. Managing Discovery Groups You can manage discovery groups from the Discovery Data Collection page. NOTE: The Default discovery group cannot be edited. To edit a discovery group: 1. Select Options > Storage Essentials > Discovery > Run Discovery Data Collection. 2.
IMPORTANT: Do not move elements between discovery groups when Discovery Data Collection is running. If you do this, an error will occur when Discovery Data Collection tries to discover elements that were moved. Method 1: Select Discovery Group To select a new discovery group for an element: 1. Select Options > Storage Essentials > Discovery > Run Discovery Data Collection. The Discovery Data Collection page appears. 2. Select the check box for the element you want to move. 3. Click Move to Discovery Group.
delete 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 9 Deleting Discovered Elements from the Management Server NOTE: If HP Storage Essentials and HP SIM are installed on the same computer, you cannot delete the HP Storage Essentials management server from HP SIM. Removing an Element 1.
Switch_B, you will no longer have access to Switch_D. This option would list Switch_D as one of the other elements that need to be deleted. • Delete the element. The element may reappear the next time you obtain element details. This is because not all switches and proxies connected to the element have been removed. For example, assume you want to delete Switch_A. Switch_B is connected to Switch_A.
1. Select the check boxes for the elements you want to remove from quarantine on the Discovery Data Collection page. Quarantined elements appear with a flag ( Data Collection page. ) in the Quarantined column on the Discovery 2. Click Clear Quarantine. 3. When you are asked if you want to remove the selected elements from quarantine, click OK. The next time you perform Discovery Data Collection for the element, the management server gathers data from the element.
6. Select Tools > Storage Essentials > System Manager to access System Manager and verify that the topology is displayed correctly. HP Storage Essentials SRM 6.
170 Discovering Switches, Storage Systems, NAS Devices, and Tape Libraries
5 Managing Licenses Some of the features described in this chapter are not included in HP Storage Essentials Standard Edition. To determine which features apply to your product, see the List of Features. Standard Edition supports a subset of the devices supported by Enterprise Edition. For a list of the devices supported by Standard Edition, see your product’s Support Matrix.
Table 10 License Restrictions Type of Restriction Description Unit of Measurement Backup Size The management server determines licensing for Backup Manager through gigabytes (GB). The management server compares the number of gigabytes for Backup Manager with what you are backing up. If you are backing up more than your license allows, you are warned the next time you log onto the management server.
Table 10 License Restrictions Type of Restriction Description Unit of Measurement For File System Viewer The management server determines licensing for File System Viewer through terabytes (TB). When you purchased File System Viewer, you were given a number of TB you were allowed by the management server to monitor. Terabytes (TB) The management server detects the number of TB that are being monitored on file servers and verifies that number is at or below the purchased amount.
Table 11 Determining Managed Access Points (continued) Element Managed Access Point Storage systems The MAPs are the sum of all front-facing ports. Storage systems with FA ports the software does not support, such as mainframe attached FICON, are still counted as MAPs. However, the management server does not count MAPs from storage systems it does not support. See the release notes for information about supported storage systems.
Assume you have the same configuration as the first example, with two Windows 2000 hosts that are directly attached to storage systems, with no Fibre Channel (FC) connections and with a total of 0 FC ports, as shown in the following figure: Figure 10 An Example of Direct Attached Storage The software calculates four MAPs (see the figure), since we assume one MAP for each host, even though it has no Fibre Channel ports. The storage systems are counted, since they are supported by the management server.
To import a license file, 1. Select Deploy > Storage Essentials > License Manager > Manage Storage Essentials Keys in HP Systems Insight Manager or select Security > Licenses in HP Storage Essentials. 2. Select Import License File. 3. Select Browse. You are shown the file system of the computer being used to access the management server. 4. Select the license file. 5. Select OK.
The license’s name and file name are listed, along with its properties. You can determine how many MAPs and/or managed application licenses (MALs) this license supports by looking at the properties in the license file. However, that can be misleading if you have other licenses that also provide support for MAPs and MALs. It is suggested you look at the cumulative licenses to obtain a total of the MAPs and MALs that are supported.
IMPORTANT: You must complete a Discovery Data Collection for the EVA arrays before importing the license and starting the collectors. After importing the license, you can start the data collectors from the Performance Data Collection page (Optimize > Storage Essentials > Performance Data Collection). Although EVA arrays are displayed after you run discovery (Options > Discovery), you must run a Discovery Data Collection for the collectors to run properly.
Select Enhanced Performance Collection Enabling to select the EVA arrays you want to include for enhanced performance data collection and reporting.
2. Go to the Webware Licensing website to use the HP Password Delivery Service, and redeem the license key for your product order. Webware Licensing will send you a link from which to download a license key. 3. Access the Storage Essentials License Manager in System Insight Manager. Do this by using the Deploy > Storage Essentials > License Manager > Manage Storage Essentials License Keys menu choices. 4. Select Import License File to download the file. 5.
6 Deploying and Managing CIM Extensions HP Storage Essentials Standard Edition supports a subset of the devices supported by Enterprise Edition. See the HP Storage Essentials Standard Edition Support Matrix for a list of supported devices. The support matrix is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
About SSH Each host being managed must be running a supported SSH daemon. The root or Administrator user must be allowed to log in for most operations. The product ships with OpenSSH for Windows hosts, but we do not have rights to offer an SSH package for other hosts.
The following error message is displayed if you attempt to install CIM extensions before they have been copied to the management server: CIM Extensions directory: ..\Extensions is missing or incomplete IMPORTANT: Do not install the CIM extension on the Management Server. A built-in CIM extension is automatically installed on the Management Server during the installation process. If you install a standard CIM extension on the management server, the management server will not operate correctly.
For example, to create a default login for Windows with a user ID of “myname” and a password of “password” you would create the following file: %JBOSS4_DIST%\Extensions\Windows\cxws.default.login The cxws.default.login file would contain the following: -credentials myname:password The CIM Extensions Management Tool CIM extensions can be remotely managed through a graphical user interface called the CIM Extensions Management Tool. Each host being managed must be running a supported SSH daemon.
4. Click Add to add the host to the table. 5. Repeat steps 1 through 4 for each additional host you want to add. 6. Click the Edit ( ) button if you want to edit the entry for a host. 7. Click the Delete ( ) button if you want to delete a host from the list. Host Lists Host lists allow you to save your list of hosts with associated username and password information for subsequent import.
• Display host operating system - Attempts to determine the remote operating system. • Display Installed CIM Extension Version - Contacts the remote system and displays the version of the CIM extension currently installed on it. • Deploy CIM Extensions - Installs the CIM extension on the remote system. • Deploy OpenSSH (Windows Hosts Only) - Deploys OpenSSH on the remote Windows system. This action is only available from a Windows management server.
NOTE: You cannot use the IP Address box when multiple hosts are listed. The Start Extensions on Custom Port checkbox will start the CIM extension on the specified port. NOTE: If you configure a CIM extension to use a custom port, you must specify the custom port when setting up data collection from the management server for that host. The Use Custom Credentials checkbox configures the CIM extensions to use a user name and password that you specify.
The HP SIM Plug-in CIM extensions can be remotely managed with the use of the HP SIM Plug-in, which integrates the deployment options into the HP SIM menus. NOTE: The HP SIM Plug-in is only supported on Windows management servers. Each host being managed must be running a supported SSH daemon. See ”About SSH” on page 182 for more information. You must copy the CIM extensions to the Storage Essentials management server before you can use the HP SIM Plug-in.
3. Insert the management server CD-ROM. 4. Double-click the SEDeploy_SIM_Plugin.exe file in the HPtools directory. 5. Close and restart the HP SIM browser for the new menu options to display.
Keep in mind the following: • After you upgrade a CIM extension on a Backup Manager Host, you must run HP SIM Discovery, and then Discovery Data Collection. The order of these steps is important. If you do Discovery Data Collection first, and then HP SIM Discovery, Backup Manager data becomes corrupted. • The HP SIM Discovery and Discovery Data Collection is required for Backup Collections to work. 1. Upgrade the CIM extension as described in the Installation Guide. 2. Run HP SIM Discovery.
7 Installing the CIM Extension for IBM AIX HP Storage Essentials Standard Edition does not support IBM AIX hosts. See the HP Storage Essentials Standard Edition Support Matrix for a list of supported devices. The support matrix is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
For more information about the HBA API, see the following Web page at the SNIA Web Site: http://www.snia.org/tech_activities/hba_api/ The installation creates the following directories in the /opt/APPQcime directory: • jre - The Java runtime necessary to run the CIM extension • lib - The executables for the CIM extension • tools - The files to stop, start, and show the status of the CIM extension Prerequisites The installation checks for the following.
• Statistics on the operating system • Disk (disk utilization, disk read, disk write) • CPU (processor utilization) Verifying SNIA HBA API Support The management server can only talk to host bus adapters (HBAs) that support the SNIA HBA API. The hbatest program, which is accessible from the CIM Extension CD-ROM, lists the name and number for all HBAs 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.
IMPORTANT: You must install the CIM extension for IBM AIX to the default directory. If there are space issues, such as large CIM extension binary files, create a symbolic link to a folder with more space. 1. Insert the CIM Extension 1 CD-ROM into the CD-ROM drive. 2. Mount the CD-ROM drive by entering the following at the command prompt: # mount -rv cdrfs /dev/cd0 /cdrom where /dev/cd0 is the name of the CD-ROM drive. If necessary, create a /cdrom directory first. 3.
2. If you see the message “Disk history since boot not available,” enter the following at the command prompt to enable the retention of disk activity history: # chdev -l sys0 -a iostat=true Starting the CIM Extension Manually The management server can only obtain information from this host when the CIM extension is running. To start the CIM extension, enter the following in the /opt/APPQcime/tools directory: # ./start Keep in mind the following: • You must have root privileges to run the CIM extension.
1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.parameters file in a text editor, and enter the following line: -port 1234 where 1234 is the new port for the CIM extension 3. Save the file. 4. Restart the CIM extension for your changes to take effect. NOTE: The CIM extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted.
Additional Parameters The following table describes the parameters that can be specified in the cim.extension.parameters file: Table 13 Parameters for CIM Extensions Parameter Description -port The CIM extension uses port 4673 by default. Use this command to change the port the CIM extension will access. See ”Changing the Port Number” on page 195. -on Use this command to configure the CIM extension to listen on a specific network card (NIC).
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. Rolling Over the Log Files The logging information for the CIM extension is contained primarily in the cxws.
• Maintenance level 03 or later - This is required for the HBA API. The operating system level can be found by entering the following command at the command prompt: oslevel -r • bos.rte.libc.5.1.0.36 or later - This is required for Java 1.4 support. The file can be downloaded from the IBM Technical Support Web site at the following URL: https://techsupport.services.ibm.com Both AIX 5.1 and 5.2 xlC.rte.5.0.2.1 or later - The C++ runtime.
200 Installing the CIM Extension for IBM AIX
8 Installing the CIM Extension for SGI ProPack for Linux HP Storage Essentials Standard Edition does not support SGI ProPack for Linux hosts. See the HP Storage Essentials Standard Edition Support Matrix for a list of supported devices. The support matrix is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
Prerequisites The CIM Extension authenticates using PAM (Pluggable Authentication Module) and supports the following password encryption mechanisms: • Blowfish • DES • MD5 NOTE: All ProPacks require that pam-devel rpm is installed. Network Port Must Be Open The CIM Extension uses port 4673 by default to communicate with the management server. Verify the network port is open. Refer to the documentation accompanying your Altix host for more information.
Installing the CIM Extension IMPORTANT: You must have root privileges to install this software. You are provided several installation options. One is an interactive option, which lets you select the installation directory. Another is a silent installation, which installs with no user input. The silent installation assumes the default installation directory. Both options install on computers with or without X Windows.
IMPORTANT: You must install the CIM extension for SGI ProPack for Linux to the default directory. If there are space issues, such as large CIM extension binary files, create a symbolic link to a folder with more space. 3. During the installation you are asked for the installation directory. Choose the default installation directory for best results. 4. Go to a directory other than one on the CD-ROM. 5.
The following is displayed: ./start The CIM extension is ready to be contacted by the management server when it displays a message resembling the following: Thu Jan 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 A similar message is now displayed in the cxws.out file when the CIM extension has completed startup.
parameters and can be copied into the cim.extension.parameters file and used as a template. Changing the Port Number The CIM extension uses port 4673 by default. If this port is already in use, follow these steps to change the port the CIM extension will access: 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.parameters file in a text editor, and enter the following line: -port 1234 where 1234 is the new port for the CIM extension. 3. Save the file. 4.
NOTE: The CIM extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually, or when the host is rebooted. The -on parameter may include a port specification. In that case, the CIM extension listens on the indicated port of the indicated NIC, rather than the default port, for example: -on 192.168.2.2:3456 The CIM extension listens only on the NIC that has the IP address 192.168.2.2 on port 3456.
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. Rolling Over the Log Files The logging information for the CIM extension is contained primarily in the cxws.
9 Installing the CIM Extension for HP-UX HP Storage Essentials Standard Edition does not support HP-UX hosts. See the HP Storage Essentials Standard Edition Support Matrix for a list of supported devices. The support matrix is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
Prerequisites Refer to the HP tab of the support matrix for the prerequisites. If the installation fails, see ”Fulfilling the Prerequisites” on page 216. FC SNIA HBA API software is bundled with the driver and is installed at the same time the driver is installed. Network Port Must Be Open The CIM extension uses port 4673 by default to communicate with the management server. Verify the network port is open. Refer to the documentation accompanying your HP-UX host for more information.
• The instructions in this section apply if you are doing a local installation of the CIM extension, as opposed to a scripted or push installation. If you want to perform a scripted or push installation of the CIM extension, first install the CIM extension locally by following the instructions in this section, and then performing the scripted or push installation. The instructions in this section only need to be performed once if you are doing a scripted or push installation.
• 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.
user to the parameters file. You would then log on to the management server, access the Discovery page, and provide the user name and password for jsmythe. Only the user name and password for jsmythe can be used to discover the HP-UX host. Follow these steps to add a user to the parameters file: 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.parameters file in a text editor, and enter the following line: -users myname where myname is a valid HP-UX user name.
1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.parameters file in a text editor, and enter the following line: -on 127.0.0.1,192.168.0.1 NOTE: If you want to configure the CIM extension to listen on multiple NICs, use a comma to separate multiple addresses. 3. Save the file. 4. Restart the CIM extension for your changes to take effect. NOTE: The CIM extension looks for parameters in the cim.extension.
Table 15 Parameters for CIM Extensions (continued) Parameter Description -user The user defined in this parameter must be a valid existing user for the host. Only the user needs to be defined. The user name and password are provided from the management server during discovery. The user does not need to have root authority. A colon-separated list can be used to specify multiple users.
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.
Removing the CIM Extension from HP-UX To remove the CIM extension for HP-UX as root: 1. Login as root. 2. Stop the CIM extension, as described in ”Stopping the CIM Extension” on page 216. 3. Make sure you are not in the APPQcime directory. As a precaution, go to the root directory. 4. Enter the following at the command prompt: # swremove APPQcime When you see the following message, the CIM extension has been removed: * Beginning Execution * The execution phase succeeded for hpuxqaX.dnsxxx.com:/".
218 Installing the CIM Extension for HP-UX
10 Installing the CIM Extension for SGI IRIX HP Storage Essentials Standard Edition does not support SGI IRIX hosts. See the HP Storage Essentials Standard Edition Support Matrix for a list of supported devices. The support matrix is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
• IRIX version 6.5.22, limited to internal processors 27 and 35. • IRIX version 6.5.20, patch required. Contact customer support for the patch. Network Port Must Be Open The CIM extension uses port 4673 by default to communicate with the management server. Verify the network port is open. Refer to the documentation accompanying your IRIX host for more information. If you need to use a different port, see ”Permanently Changing the Port a CIM Extension Uses (UNIX Only)” on page 388.
3. Enter the following at the command prompt: inst 4. Enter the following at the Inst command prompt: Inst> open 5. When you are asked for the location of the installation, enter the following: Inst> /CDROM/Irix 6. Enter the following: Inst> install 7. When asked which subsystem, enter the following: APPQcime 8. To begin the installation, enter the following: Inst> go The IRIX CIM extension is installed in the /opt/APPQcime directory.
How to Determine if the CIM Extension Is Running You can determine if the CIM extension is running by entering the following command at the command prompt: # ./status The CIM extension is running when a message resembling the following is displayed: CIM Extension Running Configuring CIM Extensions Configuration information is stored in a configuration text file that is read by the CIM extension on start-up. The file is named cim.extension.
NOTE: If you want to configure the CIM extension to listen on multiple NICs, use a comma to separate multiple addresses. 3. Save the file. 4. Restart the CIM extension for your changes to take effect. NOTE: The CIM extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually, or when the host is rebooted. The -on parameter may include a port specification.
Table 16 Parameters for CIM Extensions (continued) Parameter Description -credentials : The credentials defined by this parameter must match the values entered from the management server during discovery. They are not used as authentication on the host itself. -mgmtServerIP This parameter restricts the CIM extension to listen only to a specific management server IP address.
• xxxx is the year • x.x.x.x is the version of the CIM extension 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.
6.
11 Installing the CIM Extension for SUSE and Red Hat Linux IMPORTANT: Do not install the CIM extension onto the management server.
IMPORTANT: Install the CIM extension on each host you want the management server to manage. The CIM extension communicates with an HBA by using the Host Bus Adapter Application Programming Interface (HBAAPI) created by the Storage Network Industry Association (SNIA). The management server only supports communication with HBAs that are compliant with the HBA API. For more information about the HBA API, see the following Web page at the SNIA Web site: http://www.snia.
The library name is listed first and then the path, as shown in the following example: com.emulex.emulexapilibrary /usr/lib64/libemulexhbaapi.so com.emulex.emulexapilibrary /usr/lib/libemulexhbaapi.so For 32-bit hosts running the Linux operating system, the following is displayed in hba.conf file: To view the hba.conf file, enter the following: cat /etc/hba.conf The library name is listed first and then the path, as shown in the following example: com.emulex.emulexapilibrary /usr/lib/libemulexhbaapi.
2. Go to the Linux/requires_rpm directory on the CIM ExtensionCD1 CD-ROM by entering the following at the command prompt: # cd /cdrom/linux/requires_rpm where /cdrom is the name of the CD-ROM drive. 3. Use the appropriate "requires” rpm from the list below for the version of the OS you are installing. NOTE: The version and release number of the “requires” rpm will change based on the version and release. Redhat EL/AS 3 • 32 bit on x86: RHEL3/APPQcime-Requires- .i386.
• IA64: SLES10/APPQcime-Requires--.ia64.rpm After running this “requires” rpm you will get one or more dependency errors. A dependency on the rpm package APPQcime is expected. For example: APPQcime is needed by APPQcime-Requires-6.0.0-224.i386.rpm If you get an additional dependency error, you must install the required packages before continuing. 4.
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.
2. Open the cim.extension.parameters file in a text editor, and enter the following line: -port 1234 where 1234 is the new port for the CIM extension 3. Save the file. 4. Restart the CIM extension for your changes to take effect. NOTE: The CIM extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted.
Additional Parameters The following table describes additional parameters that can be specified in the cim.extension.parameters file: Table 17 Parameters for CIM Extensions Parameter Description -port The CIM extension uses port 4673 by default. Use this command to change the port the CIM extension will access. See ”Changing the Port Number” on page 232. -on Use this command to configure the CIM extension to listen on a specific network card (NIC).
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.
236 Installing the CIM Extension for SUSE and Red Hat Linux
12 Installing the CIM Extension for NonStop This chapter describes the following: • About the CIM Extension for NonStop, page 237 • Prerequisites, page 237 • Installing the CIM Extension, page 238 • Verifying SNIA HBA API Support, page 239 • Starting the CIM Extension Manually, page 240 • Stopping the CIM Extension, page 244 • Finding the Status of the CIM Extension, page 244 • Rolling Over the Logs, page 244 • Fulfilling the Prerequisites, page 245 • Increasing the native logging level, page 245 • Removing
• Ensure that adequate swap space is available. Network Port By default, the CIM extension uses port 4673 to communicate with the management server. To ensure that your network port is working properly: • Verify that the network port is open. Refer to the documentation accompanying your NonStop 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 388.
9. Create a directory on the NonStop host to store the depots and scripts, and transfer the files to that directory by entering the following commands: ftp> ftp> ftp> ftp> ftp> ftp> mkdir /tmp/NonStopdepots cd /tmp/NonStopdepots put APPQCIMENSR.pax put APPQJAVANSR.pax put nsk_local_install.sh put nsk_local_uninstall.sh NOTE: Ensure that the directory on the NonStop host is part of the OSS layer. Do not transfer the depots to a Guardian volume or subvolume.
IMPORTANT: The Emulex driver does not contain the required library that is required by HP Storage Essentials. You must install Emulex HBAnywhere software so that HP Storage Essentials can discover hosts configured with HBAnywhere and hbatest can detect the Emulex host bus adapter. To run hbatest: 1. Verify that you have installed the CIM extension. 2. Go to the /opt/APPQcime/tools/hbatest directory on the host where you installed the CIM extension. 3. Enter the following at the command prompt: .
• Depending on your terminal type and processor speed, the message CXWS x.x.x.x on /192.168.1.5:4673 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. • When you start the CIM extension, you can restrict the user accounts that are allowed to discover the host. You can also change the port number the CIM extension uses. See the following topics for more information.
IMPORTANT: The steps in this section provide information about temporarily changing the port of the CIM extension. If you want to make the change permanent, see ”Permanently Changing the Port a CIM Extension Uses (UNIX Only)” on page 388. To change the port, enter the following: ./start -port 1234 The variable 1234 is the port the CIM extension will listen on for all available network cards The management server assumes the CIM extension is running on port 4673.
Table 18 TCP/IP Process Display Commands Command or Argument Definitions and Output Examples info_define all Displays the default TCP/IP process scf info subnet $*.* Uses GTACL commands to check and set the TCP/IP process for the IP address. alter define Displays multiple IP addresses on a host, along with their TCP/IP processes. alter define= TCPIP^PROCESS^NAME,FILE $ZTC4 NOTE: ZTC4 is the TCP/IP process of an IP. The following table lists port arguments.
The CIM extension and build date are displayed, as shown in the following example: CXWS for mof/cxws/cxws-nsk.mof CXWS version x.x.x.x, built on Mon 19-March-xxxx 17:28:30 by Administrator where X.X.X.X represents the version of the CIM extension and the letters XXXX represent the year of the build. Combining Start Commands You can also combine the -users and -port commands. Select from one of the following options: • ./start -users myname -port 1234 • .
The cxws_native.log contains logging information for NonStop system calls. The configuration information for cxws_native.log is maintained in /opt/APPQcime/conf/cxws_native.cfg. When the log file size exceeds the LOG_SIZE specified in the configuration file, the cxws_native.log file rolls over. The information in cxws_native.log is moved to cxws_native.log.old. If cxws_native.log.old already exists, it is deleted. Increasing the native logging level The cxws_native.
Handling Daylight Savings Time Changes for the NonStop CIM Extension The NonStop JDK packaged together with the NonStop CIM extension for S series does not contain daylight savings time (DST) changes. In order to obtain the DST changes, you must install conversion tool TZUPdater 1.1 which can be downloaded from www.hp.com/go/javaDSTtool. This tool allows installed HP NonStop servers for Java (NSJ) JDK/JRE images to be updated with time zone data. TZupdater 1.1 accommodates the U.S.
8. Restart the NonStop CIM extension: ../tools/start HP Storage Essentials SRM 6.
248 Installing the CIM Extension for NonStop
13 Installing the CIM Extension for OpenVMS HP Storage Essentials Standard Edition does not support OpenVMS hosts. See the HP Storage Essentials Standard Edition Support Matrix for a list of supported devices. The support matrix is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
IMPORTANT: The Emulex driver does not contain the required library that is required by HP Storage Essentials. You must install Emulex HBAnywhere software so that HP Storage Essentials can discover hosts configured with HBAnywhere and hbatest can detect the Emulex host bus adapter. Prerequisites The prerequisites are as follows: Supported OpenVMS (Alpha) versions and required ECOs NOTE: To verify installed patches, enter the following at the command prompt: $ PRODUCT SHOW PRODUCT/FULL • OpenVMS Alpha 7.
By default, the CIM extension uses port 4673 to communicate with the management server. Verify the network port is open. If you need to use a different port, see ”Changing the Port Number” on page 254.
Check for an entry similar to the following: ------------------------------------------------------SYS$PIPEDRIVER MPA 814D9F80 814DA000 814DA080 0 814D8F40 -------------------------------------------------------- If SYS$PIPEDRIVER is not listed, then the PIPE driver is not loaded. Run the following command to load the driver: $ MCR SYSMAN IO CONNECT MPA0:/DRIVER=SYS$PIPEDRIVER/NOADAPTER 5. If the CD is already mounted, dismount it by entering: $ DISMOUNT 6.
The CIM extension provides information within the privileges of the user account that started the CIM extension. Only the system account has enough privileges to provide the information the management server needs. To manually start the CIM extension: 1. Log in as system on the OpenVMS host on which you want to start the CIM extension. 2. Enter the following command to start the CIM extension. $ @SYS$COMMON:[OPT.APPQCIME.TOOLS]START The following message is displayed: STARTING OpenVMS CIME...
another valid OpenVMS user account that has fewer privileges, for example jsmythe. First, you would add the user to the parameters file. You would then log on to the management server, access the Discovery page, and provide the user name and password for jsmythe. Only the user name and password for jsmythe can be used to discover the OpenVMS host. Follow these steps to add a user to the parameters file: 1. Go to SYS$SPECIFIC:[OPT.APPQCIME.CONF] by entering the following command: SET DEF SYS$SPECIFIC:[OPT.
System Protocol Settings, and select the host you discovered as a target. On the System Protocol Settings page, enter the port number for the host under the WBEM section. Configuring the CIM Extension to Listen on a Specific Network Card Follow these steps to configure the CIM extension to listen on a specific network card (NIC): 1. Go to SYS$SPECIFIC:[OPT.APPQCIME.CONF] by entering the following command: SET DEFAULT SYS$SPECIFIC:[OPT.APPQCIME.CONF] 2. Open the CIMEXTENSION.
Table 20 Parameters for CIM Extensions (continued) Parameter Description -on Use this command to configure the CIM extension to listen on a specific network card (NIC). You can also specify the port you used. See ”Configuring the CIM Extension to Listen on a Specific Network Card” on page 255. -user The user defined in this parameter must be a valid existing user for the host. Only the user needs to be defined.
Modifying the Boot Time Start Script (Optional) When you install the CIM extension, its start script is put in the SYS$COMMON:[OPT.APPQCIME.TOOLS] directory with the file name START.COM. Optionally, this script can be used to start the CIM extension at boot time. The following command must be included as the last line in the START.COM file: $ @ SYS$COMMON:[OPT.APPQCIME.
• CXWS_LOG.3 - contains logging information that was previously in cxws.log.2 The CXWS.OUT file contains some logging information, such as the CIM extension starting, which is recorded in case something unexpected happens with the Java Virtual Machine. The CIM extension appends the CXWS.OUT file and rolls it over. The CXWS_NATIVE.LOG contains logging information relative to OpenVMS native operations. The configuration information for CXWS_NATIVE.LOG is maintained in SYS$SPECIFIC:[OPT.APPQCIME.
Uninstalling the OpenVMS CIM Extension on a Cluster Host The OpenVMS CIM extension must be uninstalled from all nodes on the cluster. Follow the steps in ”Uninstalling the OpenVMS CIM Extension on a Standalone Host” on page 258 for each node on the cluster. HP Storage Essentials SRM 6.
260 Installing the CIM Extension for OpenVMS
14 Installing the CIM Extension for HP Tru64 UNIX HP Storage Essentials Standard Edition does not support HP Tru64 UNIX hosts. See the HP Storage Essentials Standard Edition Support Matrix for a list of supported devices. The support matrix is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
management server only supports communication with HBAs that are compliant with the HBA API. For more information about the HBA API, see the following Web page at the SNIA Web site: http://www.snia.org/tech_activities/hba_api/ Prerequisites The installation for the CIM extension verifies that the host is running at least Tru64 5.1B. If the installation fails, see ”Fulfilling the Prerequisites” on page 269.
• On a Cluster - See ”Installing the CIM Extension on a Cluster” on page 263. Installing the 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 drive on the Tru64 server. 3. Create the /cdrom directory on Tru64 host by entering the following at the command prompt: # mkdir /cdrom 4.
To install the CIM extension on just the current node: 1. Go to the /cdrom/tru64/ directory, as shown in the following example: # cd /cdrom/tru64/ 2. Run the following command 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 264. Verifying SNIA HBA API Support The management server can only talk to host bus adapters (HBAs) that support the SNIA HBA API.
To start the CIM extension, enter the following in the /opt/APPQcime/tools directory, where /opt is the directory into which you installed the CIM extension: # ./start The following is displayed: Starting CIM Extension for Tru64... 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: # .
NOTE: You can enter multiple users by separating them with a colon. For example -users myname:jsymthe. 3. Save the file. 4. Restart the CIM extension for your changes to take effect. NOTE: The CIM extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. Changing the Port Number The CIM extension uses port 4673 by default.
4. Restart the CIM extension for your changes to take effect. NOTE: The CIM extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually, or when the host is rebooted. The -on parameter may include a port specification. In that case, the CIM extension listens on the indicated port of the indicated NIC, rather than the default port, for example: -on 192.168.2.2:3456 The CIM extension listens only on the NIC that has the IP address 192.168.2.
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. Enter the following at the command prompt: # ./start -version The version number of the CIM extension and the date it was built are displayed, 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.
The cxws_native.log file contains logging information relative to Tru64 native operations. The configuration information for cxws_native.log is maintained in /opt/APPQcime/conf/cxws_native.cfg. When the log file size exceeds the LOG_SIZE parameter specified in the configuration file for the cxws_native.log, the file rolls over. The information in cxws_native.log is moved to cxws_native.log.old. If cxws_native.log.old already exists, it is deleted. Increasing the Native Logging Level The cxws_native.
The node specific directory /cluster/member/{memb}/opt/APPQcime needs to be cleaned up on each node explicitly.
15 Installing the CIM Extension for Sun Solaris HP Storage Essentials Standard Edition does not support Sun Solaris hosts. See the HP Storage Essentials Standard Edition Support Matrix for a list of supported devices. The support matrix is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
Prerequisites The management server requires certain packages and patches. The installation checks for the required packages listed in the following section and verifies that the Solaris operating system has been installed. You need the core set SUNWCreq. If you have only the core environment packages installed, install the following manually in the order listed: 1. SUNWlibC - Sun Workshop Compilers Bundled libC 2. SUNWlibCf - SunSoft WorkShop Bundled libC (cfront version) 3.
• The Emulex driver does not contain the required library that is required by HP Storage Essentials. You must install Emulex HBAnywhere software so that HP Storage Essentials can discover hosts configured with HBAnywhere and hbatest can detect the Emulex host bus adapter. To run hbatest: 1. Go to the Solaris/tools directory on the CIM Extension 1 CD-ROM. 2. Enter the following at the command prompt: ./hbatest The program runs its diagnostics.
• To upgrade the CIM extension, first remove the previous version before installing the latest version. Builds 4.2 and later of the CIM extension are compatible with this build of the management server. You must upgrade your CIM extension if you want the latest functionality, as described in ”About Upgrading Your CIM Extensions” on page 189. • You must install the CIM extension for Sun Solaris to the default directory.
To start the CIM extension, enter the following in the /opt/APPQcime/tools directory, where /opt is the directory into which you installed the CIM extension: # ./start The following is displayed: Starting CIM Extension for Solaris... 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: # .
valid Solaris user account that has fewer privileges, for example jsmythe. First, you would add the user to the parameters file. You would then log on to the management server, access the Discovery page, and provide the user name and password for jsmythe. Only the user name and password for jsmythe can be used to discover the Solaris host. Follow these steps to add a user to the parameters file: 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.
Configuring the CIM Extension to Listen on a Specific Network Card Follow these steps to configure the CIM Extension to listen on a specific network card (NIC): 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.parameters file in a text editor, and enter the following line: -on 127.0.0.1,192.168.0.1 NOTE: If you want to configure the CIM extension to listen on multiple NICs, use a comma to separate multiple addresses. 3. Save the file. 4.
Table 22 Parameters for CIM Extensions (continued) Parameter Description -user The user defined in this parameter must be a valid existing user for the host. Only the user needs to be defined. The user name and password are provided from the management server during discovery. The user does not need to have root authority. A colon-separated list can be used to specify multiple users.
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.
280 Installing the CIM Extension for Sun Solaris
16 Installing the CIM Extension for Microsoft Windows IMPORTANT: Do not install the CIM extension onto the management server.
• The management server supports communication with HBAs that are compliant with the HBA API. For more information about the HBA API, see the following Web page at the SNIA website: http://www.snia.org/tech_activities/hba_api/ • The appiq_hbaapi.dll file is installed as part of the CIM extension to provide access to the SNIA HBA API and it can be found in \CimExtensions\lib\.
Emulex setupelxhbaapi program, which modifies the registry so that SNIA libraries can be detected by the CIM extension. To install the setupelxhbaapi program, download it from the Emulex website: http://www.emulex.com The setupelxhbaapi program installs the hbaapi.dll and Emulex emulexhbaapi.dll files into the program files\emulex\hbaapi folder and creates a registry key with the absolute path to the emulexhbaapi.dll file.
IMPORTANT: Keep in mind that the CIM extension automatically starts when the system is restarted. The management server can only obtain information from this host when the CIM extension is running. Installing the CIM Extension Using the Silent Installation The CIM extension for Windows provides a silent installation, which installs the CIM extension with no user interaction. All default settings are used. Keep in mind the following: • You must have administrator privileges to install this software.
NOTE: You do not need to upgrade the CIM extensions all at once. Keep in mind, however, that CIM extensions from earlier versions do not return all information; for example they don't return FSRM data. It is strongly recommended you upgrade your CIM extensions on Windows as soon as possible. 3. Perform a discovery in HP SIM (Options > Discovery) for a re-discovery of the upgraded hosts. See ”Discovering Applications, Backup Hosts and Hosts” on page 297 for more information about discovering hosts. 4.
4. Restart the CIM extension for your changes to take effect. NOTE: The CIM extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. Adding a New Port Number to Discovery 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.
2. Go to the \CimExtensions\conf directory. 3. Open the UncShares.xml-sample file in a text editor. 4. Identify the host through which the UNC shares' scan is planned. This is the host through which you will be scanning UNC shares from a different/remote host. 5.
Table 23 Parameters for CIM Extensions Parameter Description -user The user defined in this parameter must be a valid existing user for the host. Only the user needs to be defined. The user name and password are provided from the management server during discovery. The user does not need to have root authority. A colon-separated list can be used to specify multiple users.
2. Double-click Add or Remove Programs. 3. From the Currently installed programs list, select Windows CIM Extension. 4. Click Change/Remove. 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. HP Storage Essentials SRM 6.
290 Installing the CIM Extension for Microsoft Windows
17 Installing and Discovering the Windows Proxy This chapter describes the following: • Installing the Windows Proxy, page 291 • Discovering the Windows Proxy, page 292 • Configuring Windows Proxy Authentication, page 293 • Decreasing the Maximum Java Heap Size, page 294 • Removing the Windows Proxy, page 294 The Windows Proxy is required when the management server is on Linux and you want to obtain information from Microsoft Windows hosts that do not have a CIM extension installed.
4. Read the important notes. Then, click Next. 5. Check the pre-installation summary. You are shown the following: • Product Name • Installation Folder • Disk Space Required • Disk Space Available 6. Do one of the following: • Click Install if you agree with the pre-installation summary. • Click Previous if you want to modify your selections. The Windows Proxy is installed. 7. When you have been told the installation has been successful, click Done to quit the installation.
IMPORTANT: A primary key violation error is displayed when you have the same IP address or DNS name listed in both the Discovery list (Discovery > Setup) and in the Windows Proxy list. If you have already entered the IP address for a host into the discovery list (Discovery > Setup), provide its DNS name in the Windows Proxy list. Likewise, if the DNS name for a host is listed in the Discovery list, provide its IP address in the Windows Proxy list.
See the following steps for more information on how to set a user name and password in the winproxy.conf file. To set a user name and password in the winproxy.conf file: 1. Open the [install_directory]\WindowsProxy\winproxy.conf file in a text editor, such as Notepad. 2. Add the following underlined examples after the last line in put in the application parameters as follows: # Application parameters. Add parameters as needed starting from 1 wrapper.app.parameter.1=com.appiq.cxws.main.WmiMain wrapper.app.
1. Go to the Control Panel in Microsoft Windows. 2. Double-click Add or Remove Programs. 3. From the Currently installed programs list, select HP Windows Proxy. 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. HP Storage Essentials SRM 6.
296 Installing and Discovering the Windows Proxy
18 Discovering Applications, Backup Hosts and Hosts HP Storage Essentials Standard Edition supports a subset of the devices supported by Enterprise Edition. See the HP Storage Essentials Standard Edition Support Matrix for a list of supported devices. The support matrix is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
• After installing the CIM extension on a DataProtector system on Windows, check the Logon account for the DataProtector CRS service and verify that it matches the AppStorWin32Agent service. To determine the Logon account for the DataProtector CRS service, go to Control Panel > Administrative Tools > Services, select the DataProtector CRS service, access its Properties page, and select the Logon tab.
• You can configure the management server to obtain information about your backup manager hosts at a set interval. See the topic, “Scheduling Backup Collection for Backup Managers” in the HP SE User Guide for more information about collectors. Discovery of hosts consists of these steps: • ”Step A — Set Up Discovery for Hosts” on page 299. • ”Step B — Discovery Data Collection” on page 301 Step A — Set Up Discovery for Hosts HP recommends a phased discovery process.
NOTE: To use a hosts file to specify systems for an automatic discovery, add the hosts file name to the Ping inclusion ranges, templates and/or hosts files section on the Discovery page, Automatic tab, Configure general settings section. Use the following statement: $Hosts_filename where Hosts_filename is the name of the hosts file that you want to use. NOTE: Refer to Creating a new discovery task in the HP SIM online help for more information. 8. Select the discovery task and click Run Now.
NOTE: SE discovery processing might finish before the SE Identification column shows the Running status. From HP SIM, select Tasks & Logs > View Storage Essentials Logs to see the HP Storage Essentials discovery progress. 12.To obtain details about your discovered elements, click the Run SE Discovery Data Collection Now link in the For Storage Essentials (SE) discoveries section above the list of tasks.
• During Discovery Data Collection the data you see in the user interface is not updated until the data collection is finished. • During Discovery Data Collection, the topology in System Manager is recalculated. While the topology is being recalculated, the loading of the user interface in Storage Essentials may be slow. • You can use discovery groups to break up Discovery Data Collection.
See ”Step 1 — Discovering Your Hosts and Backup Manager Hosts” on page 297, then set up the configurations for your applications on the management server. Some applications may require you to provide additional discovery information about the application. Finally, perform discovery and then run Discovery Data Collection. Discovery Data Collection takes some time. Perform this step when the network is not busy. More details about the steps mentioned above are provided later.
After changing the password on all managed database instances, the password must be changed on the Storage Essentials management server. To change the password on the Storage Essentials management server: 1. Select Discovery > Setup. 2. Click the Applications tab. 3. Click Change Password in the Change Password for Managed Database Account section. 4. Enter the password that was used for creating APPIQ_USER on the managed database instances.
• Create the APPIQ_USER account on the Oracle Database you want to monitor, not on the management server. • You should have already installed the database for the management server. • Verify that the instance TNS (Transparent Name Substrate) listener is running so that the management server can find the Oracle installation and its instances. For example, on Microsoft Windows 2000, you can determine if the instance TNS listener is running by looking in the Services window for OracleOraHome92TNSListener.
$ @CRACCT.COM The script creates a user with create session and select dictionary privilege on a managed Oracle instance. NOTE: You can use a remote Oracle client to run this script. 4. Specify the Oracle instance name, which must be visible to the client, as the first input when running the script. The script prompts you for the name of the Oracle instance on which to create the user for Oracle management packages and the password of the SYS account.
c. Go to the /DBIQ/oracle/unix directory by typing the following: # cd /cdrom/DBIQ/oracle/unix where /cdrom is the name of the directory where you mounted the CD-ROM. 2. If you plan to remove the management software for Oracle from a computer running Windows, go to the \DBIQ\oracle\win directory on the CD-ROM. 3. If you plan to remove the management software for Oracle from a computer running OpenVMS do the following: a.
IMPORTANT: Monitoring Oracle 10g or Oracle clusters requires an additional step. If you are not monitoring Oracle 10g or Oracle clusters, go to ”Step 3 — Discovering Applications” on page 335. Step C — Set up Discovery for Oracle 10g NOTE: If you are discovering an Oracle cluster, see ”Discovering Oracle Real Application Clusters (RAC)” on page 309. NOTE: By default discovery of Oracle is not supported through auto scan.
The port can be found in the following code: LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0)) ) ) ) 6. Select ORACLE from the Database Type menu. 7. Click OK. Discovering Oracle Real Application Clusters (RAC) Since Oracle RAC is an active-active application cluster, one RAC instance can provide information for the whole RAC.
is listening on TNS port LP2, then it is possible to automatically discover SID2, provided that TNS port LP2 is part of the default port list in the Application Setup page. To discover Oracle RAC: 1. Install the CIM extension on each node in the cluster. 2. If the cluster is not automatically discovered by the management server, create the cluster using Cluster Manager. For more information about Cluster Manager, see ”Host and Application Clustering” on page 341. 3.
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. 6.
Monitoring Microsoft SQL Server NOTE: If you are planning to monitor Microsoft SQL Server clusters, see ”Monitoring Microsoft SQL Server Clusters” on page 318 To manage and monitor Microsoft SQL Servers, you must do the following: • ”Step A — Create the appiq_user Account for the Microsoft SQL Server” on page 313 • ”Step B — Provide the Microsoft SQL Server Name and Port Number” on page 316 IMPORTANT: Make sure the Microsoft SQL Server database is in “Mixed Mode authentication.
5. For “Server Authentication,” select SQL Server and Windows Authentication Mode, and then click OK. You may be prompted to restart the SQL server. 6. Open SQL Server Configuration Manager (Start Menu > Programs > Microsoft SQL Server 2005 > SQLServer Configuration Manager). Make sure that the SQL instance is logged on with a Domain Administrator account if it is a clustered instance and System Account if it is a non-clustered instance.
if the instance is non-clustered and the SQLNetwork Name if the instance is clustered. If you are creating the account on a named instance, enter the host name and the instance name as follows: For a non-clustered instance: \ For a clustered instance: \ 5. If you are running the CreateSQLServerActCustom.bat script, you will be prompted for a password for the appiq_user account.
• 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 Microsoft 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. Verify you have the password to the SA user account. You are prompted for the password for this user account when you run the script. 3.
b. Create a sample ODBC datasource for the SQL Server installation using the appiq_user account. c. Click the Test button to test the datasource. 9. Repeat these steps for each Microsoft SQL Server 2005 instance you want to manage.
Manager/SQL Server Management Studio, the correct system application discovery settings on the management server would be the following: • Host IP/DNS Name: 192.168.2.10 • Database Server: SQLTEST • Port Number: 1433 • Database Type: SQLSERVER 6. In the Port Number box, enter the port that SQL is using. To determine the correct SQL Port Number that the SQL Server is using, follow these steps: Microsoft SQL Server 2000 a. Open SQL Server Enterprise Manager. b.
IMPORTANT: You must complete the following steps. 2. Verify you have the password to the server administrator user account. You are prompted for the password for this user account when you run the script. 3. Run the DropSQLServerAct.bat script on Microsoft Windows on the computer with the SQL Server database. 4. Enter the name of the SQL Server server. 5. Enter the password for the server administrator account. The account for appiq_user is removed.
Provide the Microsoft SQL Server Name and Port Number for a Cluster The server name for the Microsoft SQL Server and port number for managing a Microsoft SQL Server cluster database must be provided in the following steps: IMPORTANT: If you have name resolutions issues, your server may be discovered; however, your applications will not be discovered. You can address the name resolution issues by adding entries within the hosts file on the management server for the systems in question.
• Database Type: SQLSERVER Or • Host IP/DNS Name: 192.168.2.11 • Database Server: SQLCLUSTER • Port Number: 1433 • Database Type: SQLSERVER 6. In the Port Number box, enter the port that SQL is using. To determine the correct SQL Port Number that the SQL Server is using, follow these steps: Microsoft SQL Server 2000 Cluster a. Open SQL Server Enterprise Manager. b. Expand the user interface for SQL Server Enterprise Manager, and then select the specific SQL server.
IMPORTANT: Before you begin these steps, make sure you purchased Sybase IQ, which is the module that lets you monitor Sybase Adaptive Server Enterprise. Contact your customer support if you are unsure if you purchased this module. Step A — Create the APPIQ_USER account for Sybase The management server accesses Sybase through the APPIQ_USER account. This account is created when you run the CreateSybaseAct.bat script on the computer running the Sybase database you want to monitor.
NOTE: You can use a remote Sybase isql to run this script. 4. Enter the Sybase instance name, which must be visible to the client, as the first input when running the script. The script prompts you for the name of the sybase server on which to create user for Sybase management packages and the password of the SA account. 5. Repeat the previous step for each Sybase server you want to manage. This script does the following in order: • Creates the APPIQ_USER account.
To add information for discovering Sybase Adaptive Server Enterprise: 1. Select Options > Protocol Settings > Storage Essentials > System Application Discovery Settings. To select a target, you must have at least one element designated as a server, workstation or desktop. If you see the message, “No Targets Currently Selected,” change your element from unknown to either a server, workstation or desktop. See the documentation for HP Systems Insight Manager. Select a target, and then, click Run Now. 2.
perform Discovery Data Collection. To save time, delay these steps until you have added the configurations for your other applications and hosts. To monitor Microsoft Exchange, you must: • Add information for Microsoft Exchange Domain Controller Access • Discover the application (”Step 3 — Discovering Applications” on page 335).
IMPORTANT: You must discover the host running Microsoft Exchange. See ”Step 3 — Discovering Applications” on page 335. Editing a Microsoft Exchange Domain Controller To provide information about your domain controllers: 1. Select Options > Protocol Settings > Storage Essentials > Global Application Discovery Settings. 2. Click the Edit button next to the Exchange domain controller you want to edit. 3. Enter a new User Common Name or Domain Password. 4. Click Edit.
• ”Step C — Provide the Caché Instance Name and Port Number” on page 334 After you complete these steps, you must discover Caché. See ”Step 3 — Discovering Applications” on page 335. NOTE: The required drivers for Caché were automatically installed along with the management server. IMPORTANT: Before you begin these steps, make sure you purchased Caché IQ, which is the module that lets you monitor Caché. Contact your customer support if you are unsure if you purchased this module.
Figure 15 Selecting Import from Disk 4. Browse the CIM Extension CD, select the wrapper xml file, and click Open. • On IBM AIX, Linux, or HP-UX, log into an account that has administrative privileges, and mount the CIM Extensions CD-ROM (if not auto-mounted). The wrapper file is /cdrom/DBIQ/cachedb/unix/cachedb50_sqlprojs.xml where /cdrom is the name of the directory where you mounted the CD-ROM • On Microsoft Windows, the wrapper file on the CIM Extensions CD-ROM is \DBIQ\cachedb\win\cachedb50_sqlprojs.
Figure 16 Enabling Compile Class 5. In the Import Classes pop-up window, select appiq.cls, and click Import.
Figure 17 Selecting appiq.cls For Caché 5.2 and Caché 2007.1 1. Launch the Caché System Management Portal by right-clicking the Caché Cube icon in the system tray area of the Windows toolbar and selecting System Management Portal. 2. Click the Classes link under Data Management. 3. On the Classes page, select the Namespaces radio button, and then select %SYS. 4. Click Import. 5. Browse the CIM Extension CD, select the wrapper xml file, and click Open.
where DKA0 is a local drive on the OpenVMS host. c. Browse to $DKA0 and specify SQLPROJS.XML within $DKA0 as the import file. 6. After the file is opened, click Select All. 7. Select Check here to compile imported items, and click Import. The wrapper class definitions are imported into the Caché %SYS namespace.
NOTE: If you are running Caché 5.2 or later, and the Caché instance was installed using “Locked Down” security mode, see ”Locked Down Security Mode” on page 332 before creating the APPIQ_USER account. To create APPIQ_USER for the Caché instance: 1.
enter the custom password as the fourth argument. When invoking the scripts on OpenVMS, enclose the arguments in double quotes: $ @CRUSER.COM "" "" "" 5. Repeat the previous step for each Caché instance you want to manage. Locked Down Security Mode For Caché 5.2 and later versions, if the Caché instance was installed using “Locked Down” security mode, the following steps must be carried out before creating the APPIQ_USER account: 1.
For Caché 5.2 and later versions, if the Caché instance was installed using “Locked Down” security mode, ensure that the _SYSTEM user has been enabled before trying to remove the APPIQ_USER account. To ensure that the _SYSTEM user has been enabled: 1. Launch the System Management Portal 2. Click the Security Management link under System Administration. 3. On the Security Management page, click the Users link. 4. Click the Edit link for _SYSTEM user. 5.
4. Enter the Caché server name, the Super Server port number and the password of the _SYSTEM user account as arguments for the script. When invoking the scripts on OpenVMS, enclose the arguments in double quotes: $ @DROPUSER.COM "" "" " 5. Repeat the previous step for each Caché instance you want to manage. After deleting the APPIQ_USER account from the Caché instance, you can also delete the wrapper class definitions. For Caché 5.0 (5.0.
8. Click OK. IMPORTANT: Perform Discovery Data Collection for your inputs to take effect. See ”Step 3 — Discovering Applications” on page 335. Deleting Caché Information If you do not want the management server to monitor a Caché instance, you can remove its information, as described in the following steps: 1. Select Options > Protocol Settings > Storage Essentials > System Application Discovery Settings. To select a target, you must have at least one element designated as a server, workstation or desktop.
1. Click Tools > Storage Essentials > Home > Discovery > Setup. 2. To start discovering elements on the network, click the Start Discovery button on the IP Addresses tab. The software discovers the IP addresses selected. During discovery, the following occurs: • The software changes the status light from green to orange. • The Log Messages page is displayed. To view the status of discovery, click Discovery > View Logs.
The software obtains just enough information about where the element is connected in the topology, for example a switch connected to a host. Step C — Run Discovery Data Collection Obtain detailed information from the discovered applications as described in this section. Keep in mind the following: • Discovery Data Collection takes some time. You might want to perform this process when the network and the managed elements are not busy. • During Discovery Data Collection the topology is recalculated.
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. 4. See 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 379.
4. Enter a new password in the Password box. The management server requires the password to have the following characteristics: • a minimum of three characters • starts with a letter • contains only letters, numbers and underscores (_) • does not start or end with an underscore (_) 5. Re–enter the password in the Verify Password box. 6. Click OK. HP Storage Essentials SRM 6.
340 Discovering Applications, Backup Hosts and Hosts
19 Host and Application Clustering Some of the features described in this chapter are not included in HP Storage Essentials Standard Edition. To determine which features apply to your product, see the List of Features, which is accessible from the Documentation Center (Help > Documentation Center in HP Storage Essentials).
Automatic Discovery of Host Clusters MSCS on Windows 2003 and Veritas Clusters on Solaris support automatic discovery. To discover hosts using either of these cluster services: 1. Discover your hosts and applications as described in ”Discovering Applications, Backup Hosts and Hosts” on page 297. The clusters are automatically recognized by the management server. NOTE: The following optional steps describe how to select a preferred host from which shared resource capacity data will be collected. 2.
b. In the Available Hosts section, select the hosts to add to the Cluster Members table. If desired, use the filter to assist in the selection of hosts. For details about the filtering functionality, see ”Filtering Hosts” on page 343. You may also use the Select Related Hosts button to facilitate the selection of hosts. Select a host in the table, and click Select Related Hosts to automatically select any related hosts. c.
3. Select an operating system from the Operating System menu. 4. Enter all or part of a vendor name in the Vendor Contains box. 5. Enter a number in the Processors (>=) box. Hosts with at least as many processors as specified will display in the table. 6. Enter a number in the HBAs (>=) box. Hosts with at least as many HBAs as specified will display in the table. 7. Enter a number in the Ports (>=) box. Hosts with at least as many ports as specified will display in the table. 8. Click Filter.
In this figure, the box on the left of the topology canvas shows a cluster with two hosts, and the box on the right shows a cluster with four hosts. Both clusters are in the expanded view mode, so all of the nodes are displayed. To minimize the view of a cluster, click the (-) button. Figure 19 System Manager Cluster Representation In the minimized view of a cluster, all of the nodes of the cluster are collapsed into a single box. To expand the display to show all of the nodes, click on the (+) button.
In the following figure, individual instances of Microsoft Exchange Server 2003 share HP EVA virtual disk array group shared resources: Figure 20 Cluster Element Topology Representation Clustering in Capacity Manager In Capacity Manager, it is possible to see the whole capacity utilization by the cluster. Clusters are represented as managed elements, and the capacity calculator intelligently avoids double counting of the capacity from individual nodes at the cluster level.
• Whole cluster capacity • Individual application instance capacity • Individual cluster node capacity • Capacity trending over a period of time • Shared resources of individual nodes The following figure shows an example of how clusters are represented in Capacity Manager: Figure 21 Capacity Manager Cluster Representation HP Storage Essentials SRM 6.
348 Host and Application Clustering
20 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).
IMPORTANT: These roles apply only to features and elements in HP Storage Essentials. For example, assume you assigned a user to the Help Desk role in Storage Essentials. For example, assigning a user to the Help Desk role in Storage Essentials will not give the user that role in any other product.
Table 25 Default Role Privileges (continued) Feature Role CIO System Configuration Domain Administrator Storage Administrator Server Administrator Application Administrator Help Desk X SIMViewOnly Users created in HP Systems Insight Manager are automatically placed in the SIMViewOnly role. This role does not allow users to access any of the features listed in Table 25 on page 350. See ”Adding Users” on page 356 for more information.
Roles Used to Restrict Access Roles also restrict access to element properties, element records, and Provisioning Manager, as shown in Table 26 on page 351.
About Organizations IMPORTANT: Organizations only apply to elements in HP Storage Essentials. For example, a user assigned to an organization containing only hosts will only be able to view hosts in Storage Essentials; however, that user may be able to view all other elements in HP Systems Insight Manager. You can use organizations to specify which elements users can access. For example, you can specify that some users have only access to certain switches and hosts.
the parent organizations containing BostonWebHost_Windows. For example, users assigned to BostonWebHosts would also see the addition because it contains BostonWebHost_Windows; users assigned to only BostonWebHost_Solaris would not see the addition. A child organization can be in multiple parent organizations. As shown in the following figure BostonWebHosts and NYWebHosts are not only children of the WebHosts organization, but they are also children of the US East Coast organization.
Keep in mind the following: • You cannot edit the Everything organization. • Users can view all elements only in the Discovery pages. In all other pages, only the members of the active organization are available. Discovery lists in HP SE (Discovery tab on the SE Home page) are not filtered. Users can see all elements in the discovery lists regardless of their affiliation with an organization. • Events from all elements regardless of the user’s organization are displayed by Event Manager.
Managing User Accounts This section contains the following topics: • Adding Users, page 356 • Editing a User Account, page 357 • Deleting Users, page 358 • Modifying Your User Profile, page 358 • Modifying Your User Preferences, page 359 • Viewing the Properties of a Role, page 359 • Viewing the Properties of an Organization, page 360 Adding Users This section contains procedures for adding users and authorizing privileges. Only users belonging to the Domain Administrator role can add or modify users.
2. In the New Authorizations table, select the user. 3. Select Manually assign toolbox and system/system group authorizations. 4. In the Selected Toolbox(es) section, select HP SE Tools. 5. In the Select Systems list box, select the systems you want the user to be able to manage. IMPORTANT: You must select CMS (Central Management Server) as one of the systems. 6. Click OK. The users you created in HP SIM are put in the SIMViewOnly Role.
5. To change the name assigned to the user account, enter a new name for the account in the Full Name box. This information is used to provide a correlation between an account name and a user. 6. To change the role assigned to the user account, select a new role from the Role menu. 7. To change the e-mail address listed, enter a new e-mail address in the E-mail box. 8. To change the phone number listed, enter the user's new phone number in the Phone box. 9.
1. Click the name of your account in the upper-left corner in the HP SE Home page, (Tools > Storage Essentials > Home in HP SIM). Figure 25 Clicking the Name of Your User Account 2. On the User Profile tab, modify one or more of the following: • Full Name • E-mail address • Phone number 3. When you are done with your modifications, click Save Changes. Modifying Your User Preferences Use the User Preference tab to modify your user preferences for System Manager and Element Topology.
Viewing the Properties of a Role If you are assigned the Domain Administrator role, you can determine which components a user can access by viewing the properties of the user's role. To view the properties of a role: 1. Access Storage Essentials through one of the menu options, such as Options > Storage Essentials > Email Settings. 2. In the upper-right corner, click Security > Users. 3. In the Role column, click the name of the role.
Managing Roles This section contains the following topics: • Adding Roles, page 360 • Editing Roles, page 361 • Deleting Roles, page 362 Adding Roles The management server ships with several roles. You can add roles to accommodate your organization. For example, you might want to add a role for quality assurance. See ”About Security for the Management Server” on page 349 for more information about roles and organizations.
Editing Roles The software lets you modify the default roles and/or the roles you have created. See ”About Security for the Management Server” on page 349 for more information about roles and organizations. Keep in mind the following: • Only users belonging to the Domain Administrator role can modify roles. • Domain administrators can change the user names and roles of other domain administrators, but they cannot modify their own user name and roles while logged into the management server.
To delete a role: 1. Access Storage Essentials through one of the menu options, such as Options > Storage Essentials > Email Settings. 2. In the upper-right corner, click Security > Roles. 3. Select Roles from the menu. 4. Click the corresponding Delete button ( ). The role is deleted.
3. Click the New Organizations button. 4. In the Name box, enter a name for the organization. The name of an organization has the following requirements: • Can contain spaces. • Can add digits to the beginning of an organization’s name. • Cannot be longer than 256 characters. • Cannot contain the caret (^) symbol—currently the system allows the caret symbol to be entered, but the caret symbol should not be included in an organization’s name. 5.
5. Select the storage volumes you want to add to the organization. Click the +Ports link in the Ports column to see a list of the ports associated with a particular volume. 6. When you are finished selecting volumes, click the Add button located at the top of the pane. 7. Click OK. The selected volumes are added to the Organization Members pane. Viewing Organizations The Setup Organizations page lists the organizations with their descriptions.
• Cannot include special characters, except spaces and the following characters: $, -, ., and _ • Cannot contain the carot (^) symbol. 5. To change the description of the organization, enter a new description in the Description box. You cannot enter more than 1024 characters in the Description box. 6. Click Add or Remove Members. 7. Add or remove elements as described in ”Adding an Organization” on page 363 and ”Removing Members from an Organization” on page 366. 8.
• In the Edit Organization window, click the Delete ( ) button corresponding to the element or child organization you want to remove from the organization. • In the Add or Remove Organization Members window, select the element or child organization you want to remove by clicking the appropriate check box, and then click Remove. • Only users belonging to the Domain Administrator role can remove members from an organization.
You can now only obtain information about elements in the active organizations. These active organizations are listed in the link next to the filter button, as shown in the following figure. Figure 26 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.
To change the password of a system account: 1. If you are changing the SIM_MANAGER password and HP SIM and HP SE are using the same Oracle database, you must complete the following steps.: 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.
• ”Step 1 — Configure the Management Server to Use AD or LDAP” on page 369 • ”Step 2 — Restart the AppStorManager Service and Login as the Designated Admin Account” on page 376 • ”Step 3 — Add Users to the Management Server” on page 377 • ”Step 4 — Provide Login Information to Your Users” on page 377 Step 1 — Configure the Management Server to Use AD or LDAP If you want to use AD/LDAP, you must modify the login-handler.xml file. How you modify the login-handler.
3. Comment out the Default tag as follows: 4. Uncomment the line containing the class name and login handler type so that it appears as follows: com.appiq.security.server.ActiveDirectoryLoginHandler ActiveDirectory 5. Replace directory.hp.
9. Provide the AD search base in which you want the management server to look up AD/LDAP user attributes. Allow no spaces between commas and put in all components of fully qualified domain name, for example, hds.usa.com would be DC=hds,DC=usa,DC=com. The search base is used to specify the starting point for the search. It points to a distinguished name of an entry in the directory hierarchy. dc=MyCompanyName,dc=COM 10.Save the login-handler.xml file with your changes.
displayName mail When you are done with your changes, the login-handler.xml file, may resemble the following: domain\primaryuser com.appiq.security.server.
2. In the login-handler.xml file, comment out the section that contains com.appiq.security.server.BasicLoginhandler, which enables internal authentication mode. Only one login handler is allowed at a time. 3. Comment out the Default tag as follows: 4.
CN=$NAME$,OU=NetworkAdministration, dc=MyCompanyName,ou=US,dc=COM The management server searches only those users in the company who are part of the NetworkAdministration organization (OU=NetworkAdministration) and in the United States (ou=US). IMPORTANT: Different LDAP implementations may be using different keynames for CN. The appropriate keyname should be named in login-handler.xml.
false false false CN=$NAME$,OU=Engineering,DC=mycompanyname,OU=US,DC=COM displayName mail When you a
b. Enter the following at the command prompt to stop the management server: /etc/init.d/appstormanager stop c. To start the management server, enter the following at the command prompt: /etc/init.d/appstormanager start 2. Login as the designated administrator account you specified in ”Step 1 — Configure the Management Server to Use AD or LDAP” on page 369.
378 Managing Security
21 Troubleshooting HP Storage Essentials Standard Edition supports a subset of the devices supported by Enterprise Edition. See the HP Storage Essentials Standard Edition Support Matrix for a list of supported devices. The support matrix is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials). This chapter contains the following topics: • Troubleshooting Installation/Upgrade, page 379 • Configuring the Java Console, page 385 • java.lang.
• Storage Essentials Menus Are Not Shown in HP SIM, page 384 • NoSuchElement Error, page 384 • Difficulty Displaying Storage Essentials Pages After Generating a Custom Certificate, page 384 • Troubleshooting the Oracle Database (Windows), page 384 If Your Installation or Upgrade Failed, Capture the Logs (Windows management servers only) You can quickly gather system information and log files for troubleshooting by running the srmCapture.cmd program in /tools.
• srmInstall.log — This is the master log file of the installation wizard session. It provides information for troubleshooting installation of the management server and related components. • srmInstallOracle10g.log — Log file that provides information about the Oracle 10g database installation. • srmInstallSrm.log — Log file that provides information about the management server installation. • srmOraclePatch.
“SEVERE: OUI-10029...” Message The installation wizard lets you specify an installation location for Oracle 10g. If you specify a location that is being used by another program or if you specify the Oracle DVD drive, Oracle displays the following message: SEVERE: OUI-10029: You have specified a non-empty directory to install this product. It is recommended to specify either an empty or a non-existent directory.
1. Enter the following at the command prompt, where mycomputer is the shortened DNS name of the machine: nslookup mycomputer The fully qualified domain name and IP address is displayed, as shown in the following example: Server: server.yourcompany.net Address: 192.168.135.52 Name: mycomputer.domain.my.net Address: 192.92.12.131 2. Open the following file in a text editor, such as Microsoft Notepad: C:\windows\srmwiz.ini 3. Assign the fully qualified domain name to the FQDN property in the srmwiz.
management-server-domain\administrator true false MINUTES Set MINUTES to an appropriate value for your system (like 30, 60, or 90) based on the startup time of HP SIM.
IMPORTANT: Do not install the Oracle database separately, the management server Installation Wizard (or Unix scripts) automatically configures the Oracle database for use with the management server. If you install the Oracle database separately, the database will not meet the configuration settings required by the management server.
To correct this problem, stop the management server and Oracle, and then remove the corrupted redo log, as described in the following steps: 1. Stop the AppStorManager service, which is the service the management server uses. 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_appstorm..
If the OracleOraHome92TNSListener service has not started, but the AppStorManager service has started, start the OracleOraHome92TNSListener service, and then restart AppStorManager. Unix systems To verify the Oracle service has started, enter the following at the command prompt: # ps -ef | grep ora If the service has started, output resembling the following is displayed: /opt/oracle/product/9.2.0.1.0/bin/tnslsnr LISTENER -inherit ./appstormservice /opt/productname/ManagerData/conf/solaris-wrapper.
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. To save space, the text has been shortened: 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.PolicyService] Created [Aug 04 2004 11:59:07] INFO [com.appiq.service.
3. Save the file. 4. Restart the CIM extension for your changes to take effect. NOTE: The CIM extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. 5. 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.
Table 27 Troubleshooting Firewalls (continued) Configuration Manual Start Parameters for CIM Extension If Mentioned in cim.extension.parameters Step 1 Discovery and RMI Registry Port Firewall port 1234 opened between host and management server. start -port 1234 -port 1234 10.250.250.10:1 234 OR 172.31.250.10:1 234 OR 192.168.250.10: 1234 Communication Port: 1234 Firewall port 4673 opened between host and management server on the 172.31.250.x subnet. start -on 172.31.250.10 172.31.250.
Table 27 Configuration Troubleshooting Firewalls (continued) Manual Start Parameters for CIM Extension If Mentioned in cim.extension.parameters start With firewall port 4673 opened between 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 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.
Table 27 Troubleshooting Firewalls (continued) Configuration Manual Start Parameters for CIM Extension If Mentioned in cim.extension.parameters Step 1 Discovery and RMI Registry Port With 3 firewall ports opened on different ports respectively 1234, 5678, 9012. NAT environment where all 3 NICs are translated to different 172.16.x.x subnets. start -on 10.250.250.10:1234 -on 172.31.250.10:5678 -on 192.168.250.10:9012 -on10.250.250.10:1234 -on172.31.250.10:5678 -on 192.168.250.10:9012 172.16.10.
Table 27 Troubleshooting Firewalls (continued) Configuration Manual Start Parameters for CIM Extension If Mentioned in cim.extension.parameters Step 1 Discovery and RMI Registry Port 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.10:9012 -credentials abcuser:passwd -on10.250.250.10:1234 -on172.31.250.10:5678 -on 192.168.250.
• Changing the Security Certificate to Match the Name of the Server, page 394 Installing the Certificate by Using Microsoft Internet Explorer 6.0 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 OK. 3. When you are told there is a problem with the site's security certificate, click View Certificate. 4.
3. To create a new certificate containing the DNS name of the management server, enter the following at the command prompt: %MGR_DIST%\Tools> generateAppiqKeystore.bat 4. If the program is unable to detect a DNS name, enter the following at the command prompt: %MGR_DIST%\Tools> generateAppiqKeystore.bat mycomputername where mycomputername is the DNS name of the computer 5.
• Troubleshooting Mode, page 396 • Unable to discover Emulex host bus adapters, page 397 • CIMOM Service Not Starting After Trying to Discover Sybase or SQL Server Applications, page 397 • Configuring E-mail Notification for Discovery Data Collection, page 398 • Increasing the Time-out Period and Number of Retries for Switches in Progress, page 398 • “Connection to the Database Server Failed” Error, page 400 • An Element is Not Listed on the Discovery Data Collection Page, page 400 • DCOM Unable to Communic
1. If errors occur during discovery, an error message will display at the top of the screen below the discovery step where the errors occurred. If you receive an error message, enable Troubleshooting Mode by selecting the Enable Troubleshooting Mode check box located near the top of the page for each discovery step. 2. A red icon will display in the Problems column for each host for which a problem was detected.
2. Restart Oracle with the following command: /etc/init.d/dbora restart 3. Restart the appstormanager service. 4. After the service has started, delete any Sybase or SQL entries from the Application tab in the discovery setup page. This is necessary to prevent them from being re-added to the listener.ora on further discoveries. Configuring E-mail Notification for Discovery Data Collection The management server lets you send status reports about Discovery Data Collection to users.
By default, the management server gives a switch five seconds to respond to its requests for information during Discovery Data Collection. If the switch does not respond the first time, the management server tries again. If it does not receive a response from the switch a second time, the management server says it cannot contact the switch. To change the time-out period and number of retries for switches, modify the properties as described in the following steps: 1. Access the management server. 2.
Table 29 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 1. When you are done, click Save. “Connection to the Database Server Failed” Error If you received an error message resembling the following after getting all element details, verify that the database instance is running: The connection to the database server failed.
5. Click Test. 6. When you are finished, select the IP address or DNS name you added and click the Delete icon. 7. Repeat the steps to discover the element. See ”Discovering Elements” on page 113 for instructions. DCOM Unable to Communicate with Computer Sometimes the following error message appears in the event log of the management server when the software is monitoring a Brocade switch: DCOM was unable to communicate with the computer 192.168.10.21 using any of the configured protocols where 192.168.
Duplicate entries for the same element on the Discovery Data Collection page If an element is discovered through two different protocols, it may be listed twice on the Discovery Data Collection page. If you want to change the protocol used to discover an element that has already been discovered, delete the element before attempting to rediscover it. See ”Discovery Data Collection” on page 153 for more information.For some elements, duplicate entries may result if a second protocol is available.
displaying it in the topology. See 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, see the Installation Guide. • By default, the software sets the TNS listener port to 1521. If you use another port, you can change the port number on the Discovery Targets tab.
• No Stitching for Brocade Switches with Firmware 3.2.
Table 30 Troubleshooting Discovery and Discovery Data Collection Scenario Description What to do The software is aware of the host, but it cannot obtain additional information about it. Verify that a CIM extension is installed on the host. 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.
Table 30 Troubleshooting Discovery and Discovery Data Collection (continued) Scenario Description What to do There is a problem with Discovery Data Collection from the host. Try Discovery Data Collection again. If the steps provided do not work, see ”Link Between a Brocade Switch and a Host Disappears from the Topology” on page 407. 1. The host appears managed, but it is not connected to the switch. The switch has not been discovered. Try discovering the switch again.
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 161 for more information. Undiscovered Hosts Display as Storage Systems On rare occasions, the management server displays undiscovered hosts as storage systems in System Manager. To resolve this issue, provide the host’s world wide name (WWN) as described in the following steps: 1. Determine the host’s WWN.
some instances, the API of the Brocade switch has been known to hang. Rebooting the switch clears the switch of the API hang. Incorrect Topology Sometimes Displayed for CNT Switches The CNT SMI-S provider for CNT switches does not return the correct topology information when more than one fabric is managed by the same InVSN™ Storage Network Manager. McDATA, which completed its acquisition of CNT in the summer of 2005, has been made aware of this issue.
McDATA switch, other management servers and third-party software are not able to communicate with the switch using SWAPI. Use Enterprise Fabric Connectivity (EFC) Manager to communicate with the McDATA switch. EFC Manager versions 7.0 and later can communicate with the management server and the switch. This configuration lets multiple instances of the management server or other clients contact EFC Manager, which in turn provides information about the switch.
NOTE: The management server does not accept a period longer than its default setting. lf you set the cimom.CimXmlClientHttpConnectTimeout property to more than 20 seconds on Windows or three minutes and 45 seconds on Unix systems, the management server ignores the values of this property and reverts back to the default settings. To modify the default time-out: 1. Access the management server. 2. Select Options > Storage Essentials > Manage Product Health, and then click Advanced in the Disk Space tree. 3.
1. Select Options > Storage Essentials > Manage Product Health, and then click Advanced in the Disk Space tree. 2. Click Show Default Properties at the bottom of the page. 3. Copy cimom.mcData.swapiThrottle=200. 4. Return to the Advanced page. 5. Paste the copied text into the Custom Properties box. 6. Make your changes in the Custom Properties box by changing the value of cimom.mcData.swapiThrottle. For example, the default is 200 ms.
d. Reboot the EFCM server. Repeat Step 1 through 3. If the connection is still down, proceed to Step e. e. Stop and restart the service for the management server. Repeat Step 1 through 3. If the connection is still down, proceed to Step f. f. Reboot the management server. Repeat Step 1 through 3. If the connection is still down, proceed to Step g. g.
To set all connections with HiCommand Device Manager to SSL: 1. Select Options > Storage Essentials > Manage Product Health, and then click Advanced in the Disk Space tree. 2. Click Show Default Properties at the bottom of the page. 3. Copy the cimom.provider.hds.useSecureConnection property. 4. Return to the Advanced page. 5. Paste the copied text into the Custom Properties box. 6. Make your changes in the Custom Properties box.
property, the entity concludes that the connection is no longer functioning. The CIM extension stops attempting to make a connection. When this occurs on the side of the management server, the management server attempts to re-connect (and continues the attempt until the host becomes available). The default value is 1,000 ms. You are modifying it to wait 200,000 ms or 3.33 minutes. 3. Click Save.
See ”Discovering Switches, Storage Systems, NAS Devices, and Tape Libraries” on page 105 for more information on how to discover a controller. Error -56 If you see error -56, the switch has network connection failures or problems. To solve the problem, make sure the switch is physically connected to the network, and then redo the task you were originally trying to complete. If you now see -21(OBJECT_NOT_FOUND) errors, the switch needs to be rediscovered.
• Known Driver Issues, page 416 • Known Device Issues, page 416 • “mailbox command 17 failure status FFF7” Message, page 419 • ”Process Has an Exclusive Lock” Message, page 419 About Swapping Host Bus Adapters Swapping brands of host bus adapters (HBA) on a Microsoft Windows 2000 host may have undesirable side effects. For example, after swapping out one brand of an HBA for another (including driver installation), WinMgmt.
Table 31 Known Device Issues Device Software Description AIX host NA If you are receiving replication errors for an AIX host, the provider may be trying to connect to the host using the 0.0.0.0 IP address instead of the real host IP address. If this situation occurs, you see a message containing the following when you start the CIM extension: CXWS 3.1.0.144 on 0.0.0.0/0.0.0.
Table 31 Known Device Issues (continued) Device Software Description SGI IRIX host CXFS file systems The management server can only monitor CXFS file systems from the host generating the input/output. For example, assume the elements are part of a CXFS file system. When you generate input/output into the metadata server into /folder, only the metadata server is able to monitor the file system.
Table 31 Known Device Issues (continued) Device Software Description Solaris host VxVM If you discover a host with any typical SAN disk groups off line, the storage volume page shows SAN mount points as local instead of external. These disks, however, are not accessible. When you perform Discovery Data Collection with all disk groups online, disks on the SAN are shown as external. Hosts connected directly to a storage system are shown as local, except for hosts connected by fibre.
Table 31 Known Device Issues (continued) Device Software Description IBM Storage Systems Subsystem Device Driver (SDD) or MPIO (multipath I/O) If you discover an IBM storage system without SDD, incorrect stitching is displayed in System Manager for the storage system. You are shown only one path if the storage system is using MPIO instead of SDD.
If a provisioning failure has caused the Symmetrix storage system to remain locked, you are alerted to this situation in Event Manager and on the Properties tab. You may receive a message resembling the following: Unable to end device masking session. Symmetrix '000001835005700' may be locked. HP Storage Essentials SRM 6.
422 Troubleshooting
Index 3PAR 135 A about AIX CIM Extension 191 Altix CIM Extension 201 discovery 106 Discovery Data Collection 154 HP-UX CIM Extension 209 IRIX CIM Extension 219 management server 2 NonStop CIM Extension 237 OpenVMS CIM Extension 249 security 349 Solaris CIM Extension 261, 271 SUSE and Red Hat Linux CIM Extension 227 Windows CIM Extension 281 accessing domain controller 302 account password 357 accounts users 356 Active Directory 402 adding domain controller 302, 338 elements 363, 365 license 175 organizatio
user account 357 user preferences 359 user profile 358 child organizations 349 CIM xxiii, 2 CIM Extension installing 209, 261, 271, 281 port 388 Solaris 209, 261, 271 Windows 281 CIM Extensions about 191, 201, 209, 219, 227, 237, 249, 261, 271, 281 AIX 191 Altix 201 HP-UX 209 IRIX 219 NonStop 237 OpenVMS 249 Solaris 261, 271 SUSE and Red Hat Linux 227 Windows 281 cimom.CimXmlClientHttpConnectTimeout 409 cimom.emc.skipRefresh 137 cimom.hds.exclude 140 cimom.symmetrix.
HP XP storage systems 143, 145 IBM storage systems 147 IBM SVCs 147 LSI storage systems 139 McDATA switches 124 changing the discovery settings 130 SMI-S 126 SNMP, direct connection 129 SNMP, proxy 128 SWAPI 127 Microsoft Exchange 302, 323, 402 NetApp NAS devices 151 Oracle 302, 304 Oracle clusters 304 QLogic switches 123 SQL servers 312 storage systems 148 Sun NAS devices 153 Sun StorEdge storage systems 148, 149 Sun StorEdge switches 123 Sybase 302, 320 tape libraries 153 troubleshooting 402, 403, 420 Xio
login name 358 organizations 365, 366 password 358 phone number 358 roles 362 selective discovery filter 156 user account 357 user preferences 359 user profile 358 EFC Manager 124, 415 elements adding 363, 365 deleting 165 discovering 113 element changes 168 managing 365 moving between discovery groups 164 organization 365 quarantined 167 removing 366 unable to find 403 e-mail address changing 358 EMC CLARiiON 138 EMC Connectrix storage systems excluding from discovery 136 EMC Connectrix switches 124 exclud
importing 161 saving discovery settings in HP SIM 160 hot-swapped drives 409 HP authorized reseller xxv storage web site xxv Subscriber’s choice web site xxv technical support xxv HP MSA arrays 142 HP M-Series switches 123 HP NAS devices 150, 151 HP SIM Connector passing devices with DNS name 110 HP tape libraries 153 HP XP arrays 145 HP XP storage systems 143, 145 HP-UX CIM Extension installing 209 prerequisites 209 removing 209 starting 209 stopping 209 HTTP Error 503 386 HTTPS 7, 89 OpenVMS CIM Extensio
about 2 database 7 discovering 112 installing 7 security 349 managing elements 363, 365, 366 MAPs 171 McDATA switches 124, 408 Bridge Agent 124 changing the discovery settings 130 discovering 124 excluding from discovery 131 managing 132 adding 132 removing 133 replacing 133 messages data is late 385 Microsoft Exchange Adding domain controllers 324 deleting domain controllers 325 discovering 302, 323, 402 drive M 402 failover clusters 325 mixed mode authentication 312 modifying credentials 159 domain contro
phone number editing 358 planning organizations 349 points managed access 171 port CIM Extension 388 prerequisites xxiii AIX CIM Extension 191 Altix CIM Extension 201 HP-UX CIM Extension 209 IRIX CIM Extension 219 NonStop 237 OpenVMS 250 Solaris CIM Extension 261, 271 SUSE and Red Hat Linux 228 Windows CIM Extension 281 privileges roles 349 problems drivers 416 process exclusive lock 420 product health monitoring enabling 111 profile user 358 properties organizations 360 roles 360 provisioning troubleshooti
selective discovery filter 109, 156 configuring 158 editing rules 156 Server Administrator role 349 silent installation Windows 284 SMI-S devices discovery 106 testing SMI-S providers 109 SNMP authentication errors 402 SNMP trap listener port 133 software requirements 2 Solaris CIM Extension installing 261, 271 prerequisites 261, 271 removing 261, 271 starting 261, 271 stopping 261, 271 SQL Server authentication modes 312 SQL servers discovering 312 starting AIX CIM Extension 191 Altix CIM Extension 201 HP-
unable to monitor 408 Sybase discovering 302, 320 symbols in text xxiv System Manager can’t access 414 system tasks 162 T tape libraries discovery 150 HP 153 IBM 153 technical support, HP xxv terms storage 2 text symbols xxiv TNS Listener Port changing 338 topology AIX 402 host not appearing 403 topology issues 403 troubleshooting CLI errors 415 discovery 400 discovery and getting element details 400, 401, 402, 403, 420 Microsoft Exchange 402 NoSuchElement 415 provisioning 414, 415, 420 U unable to discov
432
