HP Storage Essentials V5.1 Installation Guide Second Edition (Linux Release) (T4283-96055, November 2006)

ManualsBrandsHP ManualsSoftwareHP Storage Essentials Storage Resource Management Backup Mgr 1 TB Tier-2 LTU

Storage Essentials 5.1 Installation Guide

Part number: T4283-96055

Second edition: November 2006

T4283-96055

Summary of content (374 pages)

PAGE 1
HP Storage Essentials 5.
PAGE 2
Legal and notice information © Copyright 2002-2006 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
PAGE 3
Contents About this guide . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . HP technical support . . . . . . . . . . . . . .
PAGE 4
Installing the Java Plug-in on Linux . . . . . . . . . . . . . . . . . . Configurations Required for Discovering EMC CLARiiON Storage Systems . . . . . . . . . . . . . . . . . . Removing the Management Server . . . . . . . . . . . . . . . . . . Porting the Management Server Across Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 . . . . . . . . . . . . . . . . . . .
PAGE 5
Accessing the HP SE Discovery Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selective Discovery Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovery Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovery from HP SIM Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
Discovery from HP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Discovery from HP SE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Discovering Sun StorEdge and QLogic Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Discovery from HP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Discovery from HP SE . . . .
PAGE 7
Discovery from HP SE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Excluding HDS Storage Systems from Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovering HP StorageWorks MSA Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovery from HP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovery from HP SE . . . . . . . . . . . . . . . . . .
PAGE 8
Discovery from HP SE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovering HP NAS Devices on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovery from HP SE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovering NetApp NAS Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovery from HP SIM . . . . . . . . . . . .
PAGE 9
5 Deploying and Managing CIM Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 About Remote CIM Extensions Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying the CIM Extensions to the Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Default Logins for Hosts . . . . . . . . . . . . . . . . . .
PAGE 10
8 Installing the CIM Extension for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 About the CIM Extension for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-UX 11i and 11.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements . . . . . .
PAGE 11
Specific Network Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding the Version of a CIM Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the CIM Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rolling Over the Logs . . . .
PAGE 12
Configuring CIM Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restricting the Users Who Can Discover the Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Port Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the CIM Extension to Listen on a Specific Network Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 13
Changing the Port Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the CIM Extension to Listen on a Specific Network Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding the Version of a CIM Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 14
Switching to Mixed Mode Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step A - Create the APPIQ_USER for the SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . Step B - Provide the Microsoft SQL Server Name and Port Number . . . . . . . . . . . . . . . . . Removing the APPIQ_USER Account for SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting SQL Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 15
Managing Organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Storage Volumes to an Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Organizations . . . . . . . . . . .
PAGE 16
Increasing the Time-out Period and Number of Retries for Switches in Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . “Connection to the Database Server Failed” Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCOM Unable to Communicate with Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplicate Listings for Brocade Switches in Same Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 17
About Swapping Host Bus Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . “Fork Function Failed” Message on AIX Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Known Driver Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Known Device Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 18
11 12 13 14 xviii Time-out Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Retry Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Discovery and Discovery Data Collection/Get Details . Known Device Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. .. .. . . . . .. .. .. .. . . . . .. .. .. .. ... ... ... ... .. .. .. ..
PAGE 19
About this guide This guide provides information about: • Installing the product • Discovering elements • Creating users • Changing the admin password • Installing JReport Designer Intended audience This guide is intended for: • Network Engineers • Administrators • Any one that needs to monitor and/or manage their file servers Prerequisites Prerequisites for using this product include: • Networking • Storage Area Networks (SANs) • The Common Information Model (CIM) Related documentation In addition to th
PAGE 20
Document conventions and symbols Document conventions Table 1 Convention Element Medium blue text: Figure 1 Cross-reference links and e-mail addresses Medium blue, underlined text (http://www.hp.
PAGE 21
TIP: Provides helpful hints and shortcuts. HP technical support Telephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support/.
PAGE 22
xxii
PAGE 23
1 Overview This chapter describes the following: • ”Supported Platforms for Installing Storage Essentials” on page 1 • ”About this Product” on page 4 • ”Software Requirements” on page 5 • ”Web Browser Configuration Requirements” on page 5 Supported Platforms for Installing 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 Storage Essentials integrates tightly with
PAGE 24
Table 2 Roadmap for Installation and Initial Configurations (continued) Step Description Where to Find 2 Install HP Systems Insight Manager. • Microsoft Windows - See ”Installing the Management Server on Microsoft Windows” on page 33. • Linux - See ”Installing the Management Server on Linux” on page 7. For detailed information about installing HP Systems Insight Manager, see the HP Systems Insight Manager Installation and User Guide. Keep in mind you will need to do a custom installation.
PAGE 25
Table 2 Roadmap for Installation and Initial Configurations (continued) Step Description Where to Find 8 Install a CIM Extension on each host (other than the management server) from which you want the management server to be able to obtain information. The CIM Extension gathers information from the operating system and host bus adapters on the host. It then makes the information available to the management server. • IBM AIX - See ”Installing the CIM Extension for IBM AIX” on page 155.
PAGE 26
1If you do not install a CIM Extension on a UNIX host, the management server cannot obtain information from the host. On a Microsoft Windows host without a CIM Extension, the management server can only find information that is gathered from Windows Management Instrumentation. The CIM Extension is required to obtain information from the host bus adapter and manage applications on the Microsoft Windows host.
PAGE 27
• Integrated storage management - Lowers cost of acquiring and managing a heterogeneous storage environment using multiple disparate, point solutions. • Standards-based architecture - Protects customer flexibility and investments with a standards-based interface for managing heterogeneous storage environments. • Storage server, network and subsystem provisioning - Reduces manual processes and risk of downtime due to free-space outages with multi-level storage provisioning.
PAGE 28
Installing Storage Essentials See one of the following depending on the operating system on which you are installing Storage Essentials: • ”Installing the Management Server on Linux” on page 7 • ”Installing the Management Server on Microsoft Windows” on page 33 6 Overview
PAGE 29
2 Installing the Management Server on Linux Follow the steps in this topic to install the management server on Linux. See the following topics if you are installing the management server on another supported operating system: • ”Installing the Management Server on Microsoft Windows” on page 33 Keep in mind the following: • All steps must be completed for the management server to work properly. • For optimal performance, install the management server on a dedicated computer.
PAGE 30
Pre-installation Checklist HP SIM Verify that the following required software is available on your system, and install any that are missing: • SSH - Verify that SSH is installed by entering the following command: # rpm -qa | grep ssh If SSH is not installed, the previous command does not return any results. • SNMP - Verify that SNMP is installed by entering the following command # rpm -qa | grep snmp If SNMP is not installed, the previous command does not return any results.
PAGE 31
• openmotif21 • xorg-x11-deprecated-libs-devel: This package needs to be installed during OS installation. • xorg-x11-deprecated-libs • compat-oracle-rhel4 • compat-libcwait NOTE: The compat-oracle-rhel4 and compat-libcwait packages are not part of OS distribution and can be downloaded from http://oss.oracle.com/projects/compat-oracle/files/RedHat/. The remaining packages are installed by default during a full install, or they can be selected manually during a custom installation.
PAGE 32
• For RHEL, the package name is “xorg-x11-Xvfb” • For SLES, the package name is “XFree86-Xvfb” 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. Verify that the correct DNS suffixes are mentioned in the order of preference in which they need to be appended to hostnames. For example: nameserver 172.168.10.1 nameserver 172.168.10.2 search hp.com 2.
PAGE 33
IMPORTANT: 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 on the management server CD-ROM for system requirements. • Once you start the installation, do not exit.
PAGE 34
• ORA_HOME should have a minimum of 50 GB of free space. Accessing the Linux Host Access the Linux host by doing one of the following: • Using the graphics console on the localhost - Run the following command at the command prompt: # /usr/X11R6/bin/xhost + NOTE: Running the xhost + command is important because non-root users (such as oracle) need to be able to use the X server display for the duration of the installation.
PAGE 35
where is the address of the client from where the Installer script is launched. # export DISPLAY For Example: # DISPLAY=172.168.10.15:0.0 # export DISPLAY Installing the Database To install the database: 1. Access the Linux host and login as user “root” as described in ”Accessing the Linux Host” on page 12. 2. Insert the first Oracle Database CD-ROM and mount it using the following commands: # mkdir -p /mnt/oradisk # mount /dev/cdrom /mnt/oradisk where /dev/cdrom is the CD device. 3.
PAGE 36
9. If you are asked to enter an installation directory, you can select the default, which is /opt/oracle. 10.If you are running Red Hat Enterprise Linux AS 4 or Red Hat Enterprise Linux ES 4, you will be asked to enter the password for oracle user. Enter the password when prompted. 11.Enter “y” when asked to start the Oracle Universal Installer. Text similar to the following may display: CURDIR=/home/oracle tfile=/mnt/cdrom/Disk1 Starting Oracle Installer...
PAGE 37
by the management server when you install the management server software. Click the Next button. Figure 1 Do not Create a New Database The Oracle Universal Installer installs the contents of all three CDs. When all of the files on the first CD (Disk 1) are installed, the Oracle Universal Installer prompts you for the second CD (Disk 2). 13.Unmount Disk 1 and manually eject it. 14.Insert Disk 2 and mount it. Specify the path for Disk 2 and click OK. 15.
PAGE 38
IMPORTANT: The path displayed in the command and in the Setup Privileges dialog box may be different depending on your Oracle home path. Figure 2 Setup Privileges The following is the output of the script. Your output may differ slightly based on the file paths you entered. Running Oracle9 root.sh script... The following environment variables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /opt/oracle/product/9.2.0.
PAGE 39
NOTE: The above message can safely be ignored as the network agent installation is not included in the Oracle installation. IMPORTANT: On some Linux systems, an error message may be shown at the end of the installation. If this happens, click the OK button and manually close the Installer window. Figure 3 Error Message 18.When the script is done running, click OK in the Setup Privileges window. The installer will close automatically. Eject the Oracle Database Disk 3.
PAGE 40
where /mnt/oradisk is your CD-ROM disk drive. 7. The installation is a two step process consisting of patching the Oracle Universal Installer (OUI) and then patching Oracle. Patch installation for OUI is done in silent mode, and output similar to the following displays when the installation begins: Checking installer requirements... Checking operating system version: must be SuSE-7, redhat-2.1AS, redhat-2.1, UnitedLinux-1.0, redhat-3 or SuSE-8 Passed All installer requirements met.
PAGE 41
IMPORTANT: The path displayed in the command and in the Setup Privileges dialog box may be different depending on your Oracle home path. Figure 4 Setup Privileges The following is the output of the script. Your output may differ slightly based on the file paths you entered. Running Oracle9 root.sh script... The following environment variables are set as: ORACLE_HOME= /opt/oracle/product/9.2.0.4 Finished running generic part of root.sh script. Now product-specific root actions will be performed.
PAGE 42
Step 2 - Install the Management Server Install the management server on the same computer as you installed Oracle as described in ”Step 1 - Install the Oracle Database” on page 10. Keep in mind the following: • Refer to the release notes for late breaking information. • Make sure no other programs are running when you install the management server. • When you install the management server on Linux, you must install the software using a POSIX (Portable Operating System Interface) shell, such as sh.
PAGE 43
NOTE: Refer to the Support Matrix for information about supported hardware. 7. Do one of the following: • Click Install if you agree with the pre-installation summary. • Click Previous if you want to modify your selections. The management server is installed. CAUTION: Do not click the Cancel button during the installation. You can always remove an unsatisfactory installation. 8.
PAGE 44
pings the IP address for the host and not the loopback address. If it pings the loopback address, edit the /etc/hosts file and make the appropriate corrections. After verifying that the correct IP is being pinged, uninstall the management server as described in steps 1 through 11 of ”Removing the Management Server” on page 30. Do not remove the Oracle Software. Install the management server as described in ”Step 2 - Install the Management Server” on page 20.
PAGE 45
If you need to stop the process for Oracle, enter the following at the command prompt: # /etc/init.d/dbora stop IMPORTANT: If you are starting the processes manually, start the Oracle process before the process for the management server. 5. If you find your process for the management server has not started, you can start the process by entering the following at the command prompt: # /etc/init.d/appstormanager start If you need to stop the process, enter the following at the command prompt: # /etc/init.
PAGE 46
For more details, see the HP SIM Installation and User Guide. To install HP SIM: 1. Download the HP SIM installation file from http://www.hp.com/go/hpsim. 2. Change the file permission by entering the following command: # chmod 700 HPSIM-Linux_C.05.00.02.00.bin 3. Enter the following command: #./HPSIM-Linux_C.05.00.02.00.bin 4.
PAGE 47
• does not start or end with an underscore (_) To change the password: 1. Verify that the AppStorManager process is stopped. 2. The changePassword utility uses Perl. To set Perl in your path, enter the following command: # . /opt/productname/install/setvars.sh where /opt/productname is the directory containing the software. It is defined by $APPIQ_DIST. 3. Go to the $APPIQ_DIST/install/database/Oracle directory. 4.
PAGE 48
4. Insert the CD-ROM for installing Storage Essentials in the CD-ROM drive of the server running Storage Essentials and mount by using the following commands: # mkdir -p /mnt/HPSIMConnector # mount /dev/cdrom /mnt/HPSIMConnector where /dev/cdrom is the CD device. 5. Start the Connector installer with one of the following commands: • SUSE: # /mnt/HPSIMConnector/SIMConnectorInstall.bin LAX_VM /jre/bin/java • RHEL: # /mnt/HPSIMConnector/SIMConnectorInstall.
PAGE 49
Step 6 - Configure SUSE Linux for Use with Business Tools If you are running the management server on SUSE Linux, and Storage Essentials and HP SIM are on the same machine, you must complete these steps if you intend to use Business Tools. Only the root user can perform these steps. 1. Restart the HP SIM process by entering the following command: # /opt/mx/lbin/hpsim restart server 2. Restart Storage Essentials by entering the following commands: # /etc/init.d/appstormanager stop # /etc/init.
PAGE 50
3. Run the following commands: # cd /.mozilla/plugins # ln -s /opt//jre/plugin/i386/ns7 /libjavaplugin_oji.so . NOTE: Remember the dot at the end of the command. 4. Go to the /usr/sbin/firefox directory. Set the DISPLAY appropriately and open an X-server on your client. 5. Launch Firefox by entering the following command: # /usr/sbin/firefox/firefox 6. Open Firefox Preferences by selecting Edit > Preferences. 7.
PAGE 51
where $JRE_HOME is the directory containing the JRE installation. 3. Set the executable permission of the downloaded file: chmod +x downloaded_file_name 4. In a terminal window, go to the $HOME/.mozilla/plugins directory. Create a plugins directory if it does not exist. 5. Remove any existing links to the Java plug-in in this directory. You may use the rm libjavaplugin_oji.so command in a terminal window to remove an existing symbolic link to the Java plug-in. 6.
PAGE 52
• IP_of_my_management_server is the IP address of the computer running the management server software The management server service needs to be restarted after installing EMC Navisphere CLI. Removing the Management Server To remove the management server from Linux: 1. Access the Linux host and login as user “root” as described in ”Accessing the Linux Host” on page 12. 2.
PAGE 53
b. Run the runInstaller.sh script by entering the following at the command prompt: $ ./runInstaller.sh -ignoreSysPrereqs c. Click Deinstall Products. d. Select all components. e. Click Remove. f. After the removal is complete, click on the Cancel button in the installer window. g. To remove the left over files after Oracle uninstallation, enter the following at the command prompt: # rm -rf where is the directory containing the software, the default value being /opt/oracle.
PAGE 54
5. The dbAdmin tool does the following when the file is imported: a. Removes the APPIQ_SYSTEM account. b. Creates an APPIQ_SYSTEM account. c. Imports data into the APPIQ_SYSTEM account. d. Determines the version of the management server the data is from. e. Applies the upgrade script for the version detected. The upgrade script does not run if the detected version is the same as the latest version. The upgrade script updates sequentially. f. Upgrades and restores the CIM repository that was exported. g.
PAGE 55
3 Installing the Management Server on Microsoft Windows Follow the steps in this section to install the management server on Windows. See the following topics if you are installing the management server on another supported operating system: • ”Installing the Management Server on Linux” on page 7 NOTE: The steps in this section are for installing the management server on Microsoft Windows.
PAGE 56
Deployment Types This product provides two types of deployments: • Single box deployment - HP Systems Insight Manger and HP Storage Essentials are installed on the same server. Follow the instructions in this chapter. • Dual box deployment - HP Systems Insight Manager (SIM) and HP Storage Essentials (SE) are installed on different servers. When you install HP SIM on a different server, skip ”Step 5 - Install HP Systems Insight Manager” on page 40.
PAGE 57
The CMS must have static or dynamic host name resolution. To verify that the server's name can be resolved through DNS: a. Right-click My Computer in the Start menu. b. Select Properties. c. Click the Computer Name tab to see the fully qualified name of the computer under the label Full Computer Name. The fully qualified name of the HP SIM server (for example, computername.domainname.
PAGE 58
• Refer to the Support Matrix on the management server CD-ROM for system requirements. • Once you have started the installation, do not exit out of it. Future installations of the management server database may think you have already installed the software if you exit several minutes into the installation and orauser has already been created. • Install the database on the computer on which you plan to install the management server.
PAGE 59
NOTE: If you are not sure if you have already installed the patch, access the Oracle Universal Installer (Start > Programs > Oracle Installation Products > Universal Installer). In the Oracle Universal Installer, click Installed Products. Then, expand the OraHome tree. The installed products are displayed. Look for the highest patch level. To exit the Oracle Universal Installer, click Close, and then click Exit. When asked if you want to exit, click Yes. To install the Oracle patch: 1.
PAGE 60
Step 3 - Install the Management Server IMPORTANT: Install HP SIM and the SIM Connector before performing a discovery. Keep in mind the following: • Refer to the Support Matrix for operating system requirements on the management server CD-ROM. • Refer to the release notes for late breaking information. • Make sure no other programs are running when you install the management server.
PAGE 61
• Click Install if you agree with the pre-installation summary. • Click Previous if you want to modify your selections. The management server is installed. CAUTION: Do not click the Cancel button during the installation. You can always remove an unsatisfactory installation. 8. When the installation is complete, you are shown the directory containing the management server and the machine ID, which is used by technical support for licenses. You do not need to write down the machine ID.
PAGE 62
Step 5 - Install HP Systems Insight Manager IMPORTANT: The steps in this section are only if you are installing HP Systems Insight Manager (SIM) on the same server as HP SE. If you are installing HP SIM on a different server, skip this section. After you install HP SIM by using the directions provided in the HP SIM documentation, continue the installation steps with ”Step 6 - Install the HP SIM Connector” on page 42.
PAGE 63
• Select defaults for the rest of the options and install. It will take about 15 to 45 minutes to create and initialize the database. 6. Reboot. About Service Account Credentials You are asked for service account credentials during the installation of OpenSSH Services for HP SIM and during a typical installation of HP SIM. The user name and password you provide is for the user that is installing HP SIM, and this user must have administrative privileges.
PAGE 64
Step 6 - Install the HP SIM Connector The HP SIM Connector lets you communicate with HP Systems Insight Manager. Install the HP SIM Connector on the same server running SE. To install the HP SIM Connector: 1. Make sure HP SE is not running. You can stop the service for HP SE (AppStorManager) from the Services window on the server where you installed Storage Essentials. 2. Make sure the HP Systems Insight Manager service is running. 3.
PAGE 65
IMPORTANT: It is very important that the HP Systems Insight Manager service does not access the Oracle database before you are finished with changing the password for the Oracle database. e. Stop the AppStorManager service. AppStorManager cannot be running when you use the Database Admin Utility. f. Use the Database Admin Utility to change the SIM_MANAGER password in the Oracle database, see ”Using the Database Admin Utility to Change the SIM_MANAGER Password” on page 43.
PAGE 66
Step 7 - Browse to HP Systems Insight Manager Home Page 1. Wait until HP Systems Insight Manager (HP SIM) is fully started. HP SIM has fully started when you can bring up the Systems Insight Manager Home page. 2. Start the Storage Essentials (AppStorManager) service and change to 'Automatic.' 3. You should now be able to access HP SIM from a web browser using the URL https://:50000 (for example https://example.domain.com:50000). The host name must be fully qualified. 4.
PAGE 67
session cookies. Click OK to accept changes and exit the window for modifying your Internet options in Internet Explorer. 4. Set stored pages settings: a. From Microsoft Internet Explorer, select Tools > Internet Options > General. b. Click the Settings button in the Temporary Internet section. c. Select the Microsoft default of Automatically. Make sure the option, Every visit to the page, is not selected, since this setting has been known to cause problems. 5.
PAGE 68
Contact your EMC representative for more information about obtaining the Navisphere CLI. Distribution rights for the Navisphere CLI belong to EMC.
PAGE 69
NOTE: You can also use the Oracle DBCA (Database Configuration Assistant) tool to remove OracleServiceAPPIQ. Click Start > Oracle-OraHome92 > Configuration and Management Tools > Database Configuration Assistant. a. Enter the following at a command prompt on the management server: oradim -delete -SID APPIQ b.
PAGE 70
5. The dbAdmin tool does the following when the file is imported: a. Removes the APPIQ_SYSTEM account. b. Creates an APPIQ_SYSTEM account. c. Imports data into the APPIQ_SYSTEM account. d. Determines the version of the management server the data is from. e. Applies the upgrade script for the version detected. The upgrade script does not run if the detected version is the same as the latest version. The upgrade script updates sequentially. f. Upgrades and restores the CIM repository that was exported. g.
PAGE 71
• All files and subdirectories in %MGR_DIST%\JBossandJetty\server\appiq\fsrm • *All files and subdirectories in %MGR_DIST%\JBossandJetty\server\appiq\reports\customTreeNodes • *All files and subdirectories in %MGR_DIST%\JBossandJetty\server\appiq\reports\custom • *All files and subdirectories in %MGR_DIST%\JBossandJetty\server\appiq\reports\definitions\custom *This directory may not exist if you have not used Report Designer to create custom reports.
PAGE 72
• Single box deployment - Upgrade HP SIM on the same server running HP Storage Essentials. Use the procedure for an Oracle database upgrade as defined by HP SIM. This information can be found in the HP SIM documentation. • Dual box deployment - Upgrade HP SIM on a server that is not running Storage Essentials. Refer to the upgrade instructions in the HP SIM documentation. Follow these steps to upgrade HP SIM: 1. Log in to Windows with a user account that is in the Administrators group for the local OS.
PAGE 73
Step 5 - Upgrade the HP SIM Connector IMPORTANT: HP SIM must be running when you upgrade the SIM Connector. 1. Verify that the service for HP Storage Essentials (AppStorManager) is stopped. 2. Verify that the service for HP SIM is running.Wait until you can browse to the Systems Insight Manager home page (https::50000). 3. Put the CD-ROM for installing the management server (Storage Essentials) in the CD-ROM drive of the server running Storage Essentials. 4.
PAGE 74
Step 7 - Remove and Rediscover Certain Elements If you previously discovered the following elements, you must remove and rediscover them as described in this section: • File servers - You must remove its access points. • Brocade (see ”Important Information About Upgrading and Brocade Switches” on page 53), CNT, Cisco, QLogic, and specific models of McDATA switches supported through SMI-S (see the Support Matrix for details on SMI-S compliant McDATA switches.
PAGE 75
Step 8 - Perform Discovery Data Collection/Get Details Perform Discovery Data Collection/Get Details from HP SIM for all elements to repopulate the database. Discovery Data Collection/Get Details is also required to repopulate information for Brocade switches. Click Options > Storage Essentials > Discovery > Run Discovery Data Collection. Then, click Get Details. Important Information About Upgrading and Brocade Switches As mentioned earlier, with new installations of build 5.
PAGE 76
e. After (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)), add the following line: (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.10.1)(PORT = 1521)) where 192.168.10.1 is the IP address of the local host server. Replace 192.168.10.1 with the IP address of your local host. The text should now appear as follows: LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.10.
PAGE 77
4 Discovering NAS Devices, Tape Libraries, Switches and Storage Systems Before you can use the management server, you must make the software aware of the elements on your network. An element is anything on the network that can be detected by the management server, such as a switch. This is done through the discovery process. Discovery obtains a list of discovered elements and information about their management interface and dependencies.
PAGE 78
• ”Overview of Discovery Features” on page 62 • ”Step 1 - Discover Switches” on page 72 • ”Step 2 - Discover Storage Systems, NAS Devices and Tape Libraries” on page 99 • ”Step 3 (Discovery from HP SE Only) - Build the Topology” on page 130 • ”Step 4 - Discovery Data Collection or Get Details” on page 135 • ”Troubleshooting Mode” on page 140 • ”Managing McDATA and EMC Connectrix Switches” on page 141 • ”Assigning a File Extension in Netscape 7” on page 143 • ”Filtering Discovery Groups” on page 143 • ”Movin
PAGE 79
HP SIM. Credentials are passed from HP SIM to HP SE, so if you perform Discovery from HP SIM, the user names and passwords for discovering those elements appear in HP SE. • Multiple entries in SE may result when modifying username and password in HP SIM - If you use Discovery from HP SIM, the user name and passwords for those elements are forwarded HP SE. If you modify a user name for an element in Discovery from HP SIM, the modification is passed to HP SE as a new discovery entry for that element.
PAGE 80
Selective Discovery Filter The Selective Discovery Filter provides the capability to selectively filter the devices that are passed from HP SIM to HP SE for discovery operations. The filter is a file created by the user that contains a list of the IP addresses that should (or should not) be passed to HP SE. The filter does not impact the device discovery operations within HP SIM. It only restricts the data that is sent from HP SIM to HP SE.
PAGE 81
IMPORTANT: Because of subtle differences between discovery from HP SIM and HP SE, HP strongly recommends you do either all of your discovery steps in HP SIM or HP SE. See ”Differences Between HP SE and HP SIM Discovery” on page 56 for more information about the differences between HP SIM and HP SE discovery. Discovery from HP SIM Steps Discovery of switches, storage systems, NAS devices and tape libraries consists of several steps: 1. Discover your switches by using HP Systems Insight Manager.
PAGE 82
• After you discover an EMC Connectrix or McDATA switch, the IP address displayed next to the name of the switch is actually the IP address of the service processor for the switch in the Get Details/Discovery Data Collection screens. To find the IP address of the switch, click the link for the switch in one of the following screens: • Run Discovery Data Collection screen (Options > Storage Essentials > Discovery > Run Discovery Data Collection) for Discovery from HP SIM.
PAGE 83
running Windows, this can be determined by looking in the Services window. EMC Solutions Enabler version 5.1 requires additional steps for discovery. See ”Discovering EMC Solutions Enabler 5.1” on page 103 for more information. NOTE: Before performing any provisioning operations that involve a Brocade switch you must perform Discovery Step 3 for any subset of elements that includes this Brocade switch.
PAGE 84
Use the following table for SE discovery steps. See ”Accessing the Discovery Pages for HP SIM and HP SE” on page 57 if needed. Table 2 HP SE Discovery Steps for Switches, NAS Devices, and Storage Systems Step Description 1 If you have several switches and storage systems that use the same password and user name, set that password and user name as the default. See ”Setting Default User Names and Passwords” on page 63 for more information. 2 Discover your switches.
PAGE 85
This section describes the following: • ”About Entering Credentials for Elements in HP SIM” on page 63 • ”About Discovering Devices Through HP SIM and SNMP” on page 63 • ”Setting Default User Names and Passwords” on page 63 • ”Adding an IP Range for Scanning” on page 65 • ”Adding a Single IP Address or DNS Name for Discovery” on page 66 • ”Modifying a Single IP Address Entry for Discovery” on page 67 • ”Removing Elements from the Addresses to Discover List” on page 68 About Entering Credentials for Element
PAGE 86
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 SE. Any default credential information you set up in regards to SNMP is not passed from HP SIM to HP SE. NOTE: Refer to the documentation that ships with HP SIM for more information. Discovery from HP SE You can specify up to three default user names and passwords.
PAGE 87
Adding an IP Range for Scanning Both types of discovery let you add an IP range for scanning. Discovery from HP SIM Discovery from HP SIM lets you scan an IP range at a set schedule: 1. Select Options > Discovery, which brings you to the Automatic Discover tab for HP SIM discovery. 2. To create a new automatic discovery task, click New. 3. Modify the schedule for automatic discovery if necessary. 4. Enter an IP range in the Ping inclusion field. 5.
PAGE 88
7. In the Password (Optional) field, type a common password for elements in the IP range. 8. In the Verify Password field, retype the password. 9. In the Comment field, type a brief description of the servers. For example, “Servers in Marketing.” 10.Click OK. 11.Click the Start Scanning button on the IP Ranges tab. The management server scans the IP range and populates the Addresses to Discover table on the IP Addresses tab.
PAGE 89
1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The Storage Essentials home page opens in a separate web browser window. From the Storage Essentials home page, click Discovery, then click Setup in the upper-right pane of the Storage Essentials window. 2. Under Discovery Setup, select Step 1 at the top of the screen. 3. On the IP Addresses tab, click the Add Address button. 4. In the IP Address/DNS Name field, type the IP address or DNS name of the device you want to discover. 5.
PAGE 90
3. Click Next. 4. Specify the new settings as specified in the documentation for HP SIM. 5. Click Run Now or Schedule when done. Discovery from HP SE To modify a user name or password for discovery: 1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The Storage Essentials home page opens in a separate web browser window. From the Storage Essentials home page, click Discovery, then click Setup in the upper-right pane of the Storage Essentials window. 2.
PAGE 91
• If a scheduled automatic discovery task includes the deleted element, HP SIM will rediscover the deleted element again during the next discovery. • If HP SE still lists the access point for the element, HP SE rediscovers the element the next time during Discovery Data Collection/Get Details. To remove systems from the HP SIM database: 1. On the HP SIM home page, click Systems in the left pane. 2. Select the elements you want to delete. 3. Click Delete.
PAGE 92
5. Under Initialize contents select Systems loaded from hosts file. Enter the file name and location (for example, c:\ doc.txt) or click Browse to browse to the location of the hosts file. This option reads the contents of the specified file and displays it in the Contents window. 6. If you did not select Empty File, click Initialize Now to load the hosts file. Otherwise, enter the contents of the hosts file in the Contents section. 7.
PAGE 93
Discovery from HP SIM NOTE: a file. Refer to the HP SIM documentation for more information about saving discovery settings to To save discovery settings to a file: 1. Click Options > Discovery on the HP SIM home page menu. 2. Click the Hosts File tab and click the New button. 3.
PAGE 94
The Downloading window appears. 7. Type a name for the *.xml file and select the directory to which you want to save the file. The name of the file is DiscoverySettings.xml by default. IMPORTANT: Netscape 7 assumes the file is an HTML file. If you are running Netscape, make sure the file type is selected to All Files and the file extension is xml.
PAGE 95
Table 3 Discovery Requirements for Switches (continued) Element Discovery Requirements Additional Information Brocade switches (SMI-S*) Enter the IP address/DNS name, user name and password of the Brocade SMI-S proxy server to discover it. The user name (default admin) and password must be for the Admin Account. Note that some SMI-S providers require you to specify the server using its IP address: http://IPADDRESS. See ”Discovering Brocade Switches” on page 75.
PAGE 96
Table 3 Discovery Requirements for Switches (continued) Element Discovery Requirements Additional Information McDATA and EMC Connectrix switches Additional steps are required for discovering these switches, and the steps vary according to your network configuration. See ”Discovering McDATA and EMC Connectrix Switches” on page 86. * SMI-S switches must be removed and rediscovered after upgrading from builds earlier than 4.2.
PAGE 97
Discovering Brocade Switches If you are upgrading to build 5.1 from any build prior to 4.2 of the management server your Brocade switches are discovered using the Brocade Fabric Access API after the upgrade. See ”Important Information About Upgrading and Brocade Switches” on page 53 for upgrade details.
PAGE 98
• You must verify that the Rapid program on the switch is set to 1. Rapid must be set to 1 so that the management server or any Brocade SMI-S agent can communicate with the switch. Be sure to see ”Verifying Brocade Rapid Program Is Set to 1” on page 76 for more information. Note that this requirement also applies to Brocade switches that are configured to use the Fabric Access API provider. • Before performing any provisioning operations that involve a Brocade switch after an upgrade to build 4.2 or 5.
PAGE 99
2. In the Custom Properties field type cimom.brocade.useApi=true to use Fabric Access API (or you can type: cimom.brocade.useApi=false to use SMI-S). If the cimom.brocade.useApi value is not specified the management server uses SMI-S. Note that you must download and install the Brocade SMI-S provider software following the instructions in the brocade_provider.pdf file located on the following FTP site to use Brocade SMI-S: ftp://ftp.compaq.com/pub/products/storageworks/smisproviders/brocade_provid er.
PAGE 100
• User Name for the switch • Password for the switch Refer to the HP SIM documentation for more details. Discovery from HP SE To discover Brocade switches: 1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The Storage Essentials home page opens in a separate web browser window. From the Storage Essentials home page, click Discovery, then click Setup in the upper-right pane of the Storage Essentials window. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4.
PAGE 101
Type the password for the SMI-S proxy server. This field can be left blank if one or more of the following conditions exists: • The proxy server's user name and password are one of the default user names and passwords. • The proxy server does not require authentication. • Fabric Access API Type the corresponding password for the switch.
PAGE 102
This provider communicates with CNT InVsn Enterprise Manager to obtain information about the switch. The provider requires a certain version of InVsn depending on the switch model. See the following table for more information. Table 5 Required Switch Models and InVsn Versions for Discovery Switch Model InVsn Software Version FC/9000 9.0 or later UMD 9.5 or later IMPORTANT: The InVsn credentials are used by the SMI-S provider.
PAGE 103
• IP Address or System name of the primary IP address of the host running the InVsn software you want to discover. See ”Adding an IP Range for Scanning” on page 65 or ”Adding a Single IP Address or DNS Name for Discovery” on page 66 for more information. • Namespace - If the //root/cntfabric namespace for the InVSN software is not already included in the wbemportlist.xml file on the server running HP SIM, add this namespace as described in the HP SIM documentation. • Port number for the InVsn software.
PAGE 104
NOTE: The Cisco MDS 9020 Multilayer Fabric Switch does not support VSANs. Keep in mind the following for Cisco SNMP switches: • When you discover a Cisco SNMP switch, you do not need to provide a password if you discover it in HP SE. HP SIM requires a password. • You can view zones, zone sets and zone aliases on a Cisco switch; however, you cannot use the management server to create, modify or remove them from a Cisco switch.
PAGE 105
• HP SIM does not allow blank passwords. Do one of the following: • Enter anything for the password for Cisco SNMP switches. • A password is required on SMI-S switches. Enter the password. Refer to the HP SIM documentation for more details. Discovery from HP SE To discover a Cisco switch: 1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The Storage Essentials home page opens in a separate web browser window.
PAGE 106
• The management server does not support provisioning for Sun StorEdge and QLogic switches. Only the active zone set and its zone members are reported. • To manage a fabric of Sun StorEdge and/or QLogic switches, every switch in the fabric must be included in the discovery list. If a switch is not included in the discovery list, it may show up as a generic host system. • No ports are reported for uninstalled blades or GBICs. • The default SNMP trap listener port for all Sun StorEdge switches is 162.
PAGE 107
Discovery from HP SE To discover Sun StorEdge or QLogic switches: 1. Click Tools > Storage Essentials > Home > Discovery > Setup. See ”Accessing the Discovery Pages for HP SIM and HP SE” on page 57 if needed. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, type the DNS name or primary IP address of the Sun StorEdge or QLogic switch you want to discover. 6.
PAGE 108
5. Paste the copied text into the Custom Properties field. How you paste the text depends on your Web browser. If you are using Microsoft Explorer or Netscape Navigator, right-click the field and select Paste. 6. Make your changes in the Custom Properties field. Make sure the property is not commented out by removing the hash (#) symbol in front of the property. 7. Set the cimom.snmpTrapListenerPort property to the port you want, as shown in the following example: cimom.snmpTrapListenerPort=162 8.
PAGE 109
Table 6 Discovery Settings for McDATA and Connectrix Switches (continued) Discovery SWAPI setting through a Proxy SNMP setting Through a Proxy Contacting the switch directly Provisioning Limitations The SWAPI setting lets you activate a zone set, in addition to creating, editing, and deleting zones and zone sets. You cannot manage or view information about zone aliases. This SNMP setting through a proxy does not let you manage or access information about zones, zone sets or zone aliases.
PAGE 110
• If you discovered Connectrix Manager or EFC Manager, only enable SNMP trap forwarding to the management server on the Connectrix Manager or EFC Manager, not on the individual switches.Connectrix Manager or EFC Manager should be configured to forward SNMP traps to the IP address of the management server, and the community string should match the user ID you used to discover Connectrix Manager or EFC Manager.
PAGE 111
Step 2 - Verify the Discovery Setting for McDATA and Connectrix Switches is Set to SWAPI By default the discovery settings for McDATA and Connectrix switches is set to SWAPI. If you believe it has been changed to SNMP, you can perform the following steps to change it back to SWAPI. 1. Click Options > Storage Essentials > Manage Product Health. Then, click Advanced in the Disk Space tree. 2. Click Show Default Properties at the bottom of the page. 3. Copy the following property.
PAGE 112
3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, type the IP address or DNS name of the EFC Manager/Connectrix Manager you want to discover. 6. In the User Name field, type the user name for EFC Manager/Connectrix Manager. This field can be left blank if one or more of the following conditions are fulfilled: • The element's user name and password are one of the default user names and passwords. • The element does not require authentication.
PAGE 113
(Discovery from HP SE only) To fix this problem, use the Test button on the discovery screen to check the status of the SWAPI connection. If necessary, re-discover the EFCM to re-establish the SWAPI connection. Once the connection is working, the provisioning operation should succeed. If it continues to fail because the active zone set information is out of date, do a Get Details for this element to update the zoning information.
PAGE 114
• IP address or system name of the EFC Manager/Connectrix Manager you want to discover. See ”Adding an IP Range for Scanning” on page 65 or ”Adding a Single IP Address or DNS Name for Discovery” on page 66 for more information. • User name - The default user name, which is “public” (the read-only community string). This is the user name of the proxy. • HP SIM does not allow blank passwords. Enter anything for the password. See the HP SIM documentation for more detailed information.
PAGE 115
IMPORTANT: To obtain more information about the switch, you need to map the topology and obtain element details. See the topics, ”Building the Topology View” on page 131 and ”Get Details or Discovery Data Collection” on page 136. (Only applies to Discovery from HP SE)Step 3 - Make Sure There Are No Port Conflicts for Receiving SNMP Traps IMPORTANT: This step does not apply to discovery from HP SIM.
PAGE 116
Contacting a McDATA or Connectrix Switch Directly The management server uses SWAPI to discover a McDATA or Connectrix switch by its IP address or DNS name. SWAPI is the default setting. If you want to discover McDATA or Connectrix switches by SNMP, you must change to SNMP before you begin the following steps. See ”(Discovery from HP SE only) Changing the Discovery Settings” on page 96.
PAGE 117
12.To start discovering elements on the network, click the Start Discovery button on the IP Addresses tab. Discovery is complete when the software displays the DISCOVERY COMPLETED message in the Log Messages field. IMPORTANT: To obtain more information about the switch, you need to map the topology and obtain element details. See the topics ”Building the Topology View” on page 131 and ”Get Details or Discovery Data Collection” on page 136.
PAGE 118
(Discovery from HP SE only) Changing the Discovery Settings To change the discovery settings from SWAPI to SNMP or vice versa: 1. Delete all McDATA and Connectrix switches in the application by going to the Get Topology for Discovered Elements table (Tools > Storage Essentials > Home > Discovery > Topology) and selecting the switches you want to delete. Then, click the Delete button. See ”Accessing the Discovery Pages for HP SIM and HP SE” on page 57 if needed. 2.
PAGE 119
(Discovery from SE Only) Excluding McDATA and EMC Connectrix Switches from Discovery IMPORTANT: This step only applies to discovery from SE only. Specific McDATA and Connectrix switches can be excluded from discovery by using system properties. To exclude one or more switches from discovery, you must modify the cimom.mcdata.exclude property. Set the property cimom.mcdata.
PAGE 120
7. Add the Worldwide Names corresponding to the switches you want to exclude from discovery. Separate additional Worldwide Names with a comma, as shown by the following example: cimom.mcdata.exclude=1000080088A07024,1000080088A0D0B6 where 1000080088A07024 and 1000080088A0D0B6 are the Worldwide Names for McDATA and Connectrix switches. 8. When you are done, click Save. While AppStorManager is restarting, users are not able to access the management server.
PAGE 121
The following task statuses are provided by the Task Dashboard: Table 7 Task Status Descriptions Status Description Not Found This task can not be found on this server. Completed This task has been completed successfully. Failed This task failed with an error. Aborted This task has been aborted by the user or other automated actions. In Progress This task is in progress. CPU and disk activities are active on this server. Queued This task is scheduled to be executed in the future.
PAGE 122
• ”Excluding EMC Symmetrix Storage Systems from Discovery” on page 104 • ”Discovering EMC CLARiiON Storage Systems” on page 106 • ”Discovering Engenio Storage Systems” on page 106 • ”Discovering HDS Storage Systems” on page 108 • ”Excluding HDS Storage Systems from Discovery” on page 109 • ”Discovering HP StorageWorks MSA Arrays” on page 110 • ”Discovering HP StorageWorks EVA Arrays” on page 111 • ”Discovering HP StorageWorks XP Arrays” on page 115 • ”Discovering IBM Storage Systems” on page 118 • ”Discover
PAGE 123
Table 8 Discovery Requirements for Storage Systems, Tape Libraries & NAS Devices (continued) Element Discovery Requirements Additional Information Engenio storage systems Can be discovered two ways: See ”Discovering Engenio Storage Systems” on page 106. • Entering the IP address/DNS name, user name and password of a controller for an Engenio storage system. Discovers only the corresponding IP address of the controller.
PAGE 124
Table 8 Discovery Requirements for Storage Systems, Tape Libraries & NAS Devices (continued) Element Discovery Requirements Additional Information HP NAS Devices Discover the device directly. See ”Discovering HP NAS Devices on Windows” on page 125 and ”Discovering HP NAS Devices on Linux” on page 126. NetApp Devices Discover the device directly. See ”Discovering NetApp NAS Devices” on page 127. Sun NAS Devices Discover the server running the SMI-S provider for the Sun NAS Devices.
PAGE 125
2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, the following for the 3PAR storage system you want to discover. where is the IP address or DNS name of the 3PAR storage system you want to discover. 6. Enter the User Name of the storage system. 7. Enter the Password of the storage system. 8. Retype the password in the Verify Password field. 9.
PAGE 126
• [management server name] is the IP address of the management server 3. Add the following line to the /opt/emc/API/symapi/config/netcnfg file: SYMAPI_SERVER - TCPIP 2707 4. Use the following command to start the daemon: /opt/emc/SYMCLI/V5.5.0/bin/symapisrv -service SYMAPI_SERVER start -background 5. Use the following command to stop the daemon: /opt/emc/SYMCLI/V5.5.0/bin/symapisrv stop 6.
PAGE 127
If the cimom.symmetrix.exclude property, the management server discovers and obtains details from all EMC Symmetrix Storage Systems managed by discovered Solutions Enablers.
PAGE 128
Contact your EMC representative for more information about obtaining the Navisphere CLI. Distribution rights for the Navisphere CLI belong to EMC. IMPORTANT: Before you discover your CLARiiON storage systems, you must have already installed all required software components for your CLARiiON storage system, such as the Navisphere Host Agent. Refer to the documentation for your storage system for more information.
PAGE 129
• After discovering Engenio/LSI controllers on an Engenio/LSI array, the array is displayed as having three controllers on the HP SIM All Systems page. Two of these elements are displayed as unmanaged, but one is displayed as the accessible storage system for the array. Discovery from HP SIM To discover Engenio storage systems, provide the following information in HP Systems Insight Manager: • IP address or system name of the controller or proxy you want to discover.
PAGE 130
for the server running HiCommand Device Manager. Do not point to the disk array for the storage system. To obtain information about HDS storage systems, the management server must be able to access the port HiCommand Device Manager uses to listen. By default, HiCommand Device Manager listens on port 2001, and the management server assumes this configuration at discovery time. If HiCommand Device Manager uses a different port, specify this other port when you discover HiCommand Device Manager.
PAGE 131
1. Access the Discovery Setup page (Tools > Storage Essentials > Home > Discovery > Setup). 2. Click the Add Address button. 3. In the IP Address/DNS Name field, type the name of the server and the port HiCommand Device Manager uses to listen separated by a colon, as shown in the following example: proxy2:1234 where • proxy2 is the name of the server running HiCommand Device Manager • 1234 is the port HiCommand Device Manager uses to listen 4.
PAGE 132
2. Click Show Default Properties at the bottom of the page. 3. Copy the following command. How you copy the text depends on your Web browser. If you are using Microsoft Explorer or Netscape Navigator, select the text and then right-click the selected text. Then, select Copy. #cimom.hds.exclude=61038,61037 4. Return to the Advanced page. 5. Paste the copied text into the Custom Properties field. How you paste the text depends on your Web browser.
PAGE 133
1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The HP SE home page opens in a separate web browser window. Click Discovery > Setup in the upper-right pane of the HP SE home page window. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, type the IP address or DNS name of the HP CIMOM you want to discover. 6. Enter the User Name used to access the HP CIMOM. 7.
PAGE 134
IMPORTANT: Provisioning is not supported with the EVA provider. Discovering HP StorageWorks EVA Arrays Using Command View EVA 6.x NOTE: If you have previously discovered EVA arrays by using SMI-S, delete any existing access points and rediscover. For information about deleting access points, see ”Deleting an Element Using System Manager or Chargeback Manager” on page 134.
PAGE 135
11.Click OK. To start discovering elements on the network, click the Start Discovery button on the IP Addresses tab. Discovering HP StorageWorks EVA Arrays Using Command View EVA 4.x Command View EVA 4.x requires the use of the Command View EVA SMI-S provider. IMPORTANT: Specifying a fictitious HBA WWN (such as a WWN of all 1s) when creating an HSG on the EVA 4000 results in a failed provisioning operation. This error originates from the Hewlett-Packard SMI-S provider software.
PAGE 136
• IP address or system name of the HP CIMOM you want to discover. See ”Adding an IP Range for Scanning” on page 65 or ”Adding a Single IP Address or DNS Name for Discovery” on page 66 for more information. • User name for accessing the HP CIMOM • Password for accessing HP CIMOM. Discovery from HP SE To discover HP EVA storage systems: 1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The HP SE home page opens in a separate web browser window.
PAGE 137
If both the managed and unmanaged array are discovered, they need to stay in the same discovery group. They can be moved to other discovery groups, but they must be moved at the same time. When discovering the arrays separately, the array that has already been discovered must be in the Default discovery group.
PAGE 138
1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The HP SE home page opens in a separate web browser window. Click Discovery > Setup in the upper-right pane of the HP SE home page window. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, type the IP address or DNS name of the HP CIMOM you want to discover. 6. Enter the User Name used to access the HP CIMOM. 7.
PAGE 139
Discovery from HP SE by Using Command View XP Advanced Edition To discover HP storage systems by using Command View XP Advanced Edition: 1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The HP SE home page opens in a separate web browser window. Click Discovery > Setup in the upper-right pane of the HP SE home page window. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5.
PAGE 140
2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, type the IP address or DNS name of the XP storage system you want to discover. 6. Enter the User Name used to access the XP storage system. 7. Enter the Password used to access the XP storage system. 8. If you typed a password in the previous step, retype the password in the Verify Password field. 9.
PAGE 141
f. Verifying that the CIM Agent is able to communicate with the ESS devices. NOTE: You do not need to provide the interop namespace because the management server includes the interop namespace for IBM storage systems in its default list. Discovery from HP SIM IMPORTANT: First discover the host running the IBM CIMOM. See ”Adding an IP Range for Scanning” on page 65 or ”Adding a Single IP Address or DNS Name for Discovery” on page 66 for more information.
PAGE 142
10.Do not select the Do Not Authenticate option. 11.Click OK. 12.To start discovering elements on the network, click the Start Discovery button on the IP Addresses tab. Discovering Sun StorEdge 3510 Storage Systems Before you can discover a Sun StorEdge 3510 storage system, you must set up a Sun StorEdge 3510 SMI-S provider and a Sun StorEdge™ Configuration Service. The provider cannot be installed on the same computer as the management server due to a port conflict.
PAGE 143
• IP address or system name of the system running the Sun StorEdge 3510 SMI-S provider you want to discover. See ”Adding an IP Range for Scanning” on page 65 or ”Adding a Single IP Address or DNS Name for Discovery” on page 66 for more information. • User Name of the system running the Sun StorEdge 3510 SMI-S provider. • Password of the Sun StorEdge 3510 SMI-S provider. Refer to the HP SIM documentation for more information about discovering storage systems with HP SIM.
PAGE 144
Discovery from HP SE To discover Sun StorEdge 6920 and 6940 storage systems: 1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The HP SE home page opens in a separate web browser window. Click Discovery > Setup in the upper-right pane of the HP SE home page window. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, type the IP address or DNS name of the storage system you want to discover. 6.
PAGE 145
Discovery from HP SE To discover Sun StorEdge 6130 storage systems: 1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The HP SE home page opens in a separate web browser window. Click Discovery > Setup in the upper-right pane of the HP SE home page window. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, type the IP address or DNS name of the controller or proxy you want to discover. 6.
PAGE 146
1. Click Tools > Storage Essentials > Home on the HP SIM home page menu. The HP SE home page opens in a separate web browser window. Click Discovery > Setup in the upper-right pane of the HP SE window. 2. Select Step 1 at the top of the page. 3. Click the IP Addresses tab. 4. Click the Add Address button. 5. In the IP Address/DNS Name field, enter the IP address or DNS name for the storage system and its namespace.
PAGE 147
• IP address or system name of the HP NAS device to discover. See ”Adding an IP Range for Scanning” on page 65 or ”Adding a Single IP Address or DNS Name for Discovery” on page 66 for more information. • User name of the HP NAS device. You must provide a privileged login. • Password used to access the HP NAS device. Refer to the HP SIM documentation for more information about HP SIM. Discovery from HP SE To discover an HP NAS device on Windows: 1.
PAGE 148
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. Refer to the Installation Guide for information about starting CIM extensions. Discovery from HP SIM To discover an HP NAS device on Linux, provide the following information in HP Insight Manager: • IP address or system name of the HP NAS device to discover.
PAGE 149
cause all NetApp NAS devices to communicate using SSL. See ”Enabling SSL Communication with a NetApp NAS Device” on page 128 for more information. • 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. The management server runs on the same computer running the management server by default.
PAGE 150
12.To start discovering elements on the network, click the Start Discovery button on the IP Addresses tab. Enabling SSL Communication with a NetApp NAS Device 1. Click Options > Storage Essentials > Manage Product Health. Then, click Advanced in the Disk Space tree. 2. Click Show Default Properties at the bottom of the page. 3. Copy the following property: #cimom.providers.netapp.useSSL=true 4. Return to the Advanced page (Options > Storage Essentials > Manage Product Health.
PAGE 151
4. Click the Add Address button. 5. In the IP Address/DNS Name field, type the IP address or DNS name of the server running the SMI-S provider for the Sun NAS Devices you want to discover. 6. Enter the User Name of the CIMOM/provider for the Sun NAS Devices you want to discover. You must provide a privileged login. 7. Enter the Password used to access the CIMOM/provider for the Sun NAS Devices you want to discover. 8. Retype the password in the Verify Password field. 9.
PAGE 152
7. Enter the Password of the system running the tape library. 8. Retype the password in the Verify Password field. 9. In the Comment field (optional), type a comment for additional information. The information typed into this field is displayed under the Comment column in the Addresses to Discover list (Tools > Storage Essentials > Home > Discovery > Setup). 10.Do not select the Do Not Authenticate option. 11.Click OK. 12.
PAGE 153
1. Click the Discovery menu in the upper-right corner of the Store Essentials home page. 2. Click Topology in the upper-right corner. The discovered elements are selected. 3. Select the discovery group from which you want to obtain the topology. If you are obtaining the topology for the first time, make sure All Discovery Groups is selected. You can use discovery groups to break up getting the topology or getting details.
PAGE 154
discovery groups to break up getting the topology or Get Details. For example, you could specify that the management server gets the topology or Get Details for only the elements in Discovery Group 1, thus, saving you time. This feature is sometimes referred to as segmented replication because you can specify getting the topology or Get Details for a segment of the discovered elements.
PAGE 155
• If a scheduled automatic discovery task includes the deleted element, HP SIM will rediscover the deleted element again during the next discovery. • If HP SE still lists the access point for the element, SE rediscovers the element the next time during Discovery Data Collection/Get Details. To remove systems from the SIM database: 1. From the HP SIM home page, click Systems in the left pane. 2. Select the elements you want to delete. 3. Click Delete.
PAGE 156
discover Switch_A. Let's assume Switch_B is also the only path to Switch_D. If you delete 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. An access point is the intersection of the IP address and the provider that discovered the IP address. A provider is software that is used to gather information about an element. • Delete the element. The element may reappear the next time you obtain element details.
PAGE 157
When you are asked if you want to remove the access points and its associated elements, keep in mind these elements will not be deleted if they are accessible from an access point not listed in the Delete Access Points window. For example, assume you selected access point 192.168.10.25 to be deleted. You are then told that switch1 will be deleted along with the access point. Let's assume switch1 is accessible from another access point, 192.168.10.29. When you remove access point 192.168.10.
PAGE 158
• When an element in a given discovery group is updated, its dependent elements are also updated. For example, assume Host_A is the only element in Discovery Group 1. Host_A is connected through a switch and storage system. When you Get Details/Discovery Data Collection for Discovery Group 1, you also obtain details from the switch and storage system. • You can quarantine elements to exclude them from Get Details/Discovery Data Collection.
PAGE 159
4. Select the discovery group from which you want to obtain Get Details/Discovery Data Collection. If you are obtaining Get Details/Discovery Data Collection for the first time, make sure All Discovery Groups is selected. 5. Click the Get Details button. During Get Details/Discovery Data Collection, the software changes its status light from green to red. You can view the progress of gathering details by doing the following: • Discovery from HP SE - Click Discovery > View Logs.
PAGE 160
Solutions Enabler to be refreshed, you must assign the Symmetrix storage systems that use the Solutions Enabler to the cimom.emc.skipRefresh property, as described in the steps in this section. 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. How you copy the text depends on your Web browser.
PAGE 161
When the Force Device Manager Refresh option is selected, the management server refreshes discovered HiCommand Device Manager (proxy server), unless specified. If you do not want a HiCommand Device Manager to be refreshed, you must assign the HDS storage systems that use HiCommand Device Manager to the cimom.HdsSkipRefresh property, as described in the steps in this section. IMPORTANT: Before performing any provisioning operations, you should perform a forced refresh.
PAGE 162
Troubleshooting Mode Troubleshooting Mode can be used to assist you in identifying and resolving host configuration issues during discovery, as described in the following steps: 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.
PAGE 163
(Discovery from HP SE only)When you remove switches from the service processor, you must remove them from the management server as well. See the topic, ”(Discovery from HP SE Only)Removing McDATA and EMC Connectrix Switches” on page 142 for more information about removing switches. When you replace McDATA or EMC Connectrix switches, you add and remove the switches as described previously.
PAGE 164
2. Verify the switches have been removed from the Elements List in Discovery Steps 2 and 3 by doing the following: a. To verify the switches have been removed from the element list in Discovery Step 3, click Tools > Storage Essentials > Home > Discovery > Details. b. To verify the switches have been removed from the element list in Discovery Step 2, click Tools > Storage Essentials > Home > Discovery > Topology. 3. Remove the switches from HP SIM as well.
PAGE 165
When the software completes Get Details/Discovery Data Collection, it displays a message saying Get Details/Discovery Data Collection is complete on the View Logs page. Assigning a File Extension in Netscape 7 Netscape 7 automatically assigns unknown files an HTML extension. To make Netscape 7 recognize the type of file, you must assign a file extension. To assign a MIME type: 1. Click the download file link or button in the software. 2. Click the Advanced button in the lower-left corner. 3.
PAGE 166
Elements in the selected discovery groups are selected on the Discovery Data Collection page for Discovery from HP SIM or Get Details page for Discovery from HP SE. The management server obtains information from the selected elements during Get Details and Discovery Data Collection. To learn how to add an element to a different discovery group, see ”Modifying the Properties of a Discovered Address” on page 132.
PAGE 167
1. Select the check boxes for the elements you want to quarantine on the Get Details/Discovery Data Collection page. 2. Click the Set Quarantine button. 3. When you are asked if you want to quarantine the selected elements, click OK. The elements you quarantine appear with a flag ( Details/Discovery Data Collection page. ) in the Quarantined column on the Get The elements are excluded from discovery until you clear them from quarantine.
PAGE 168
and Master Backup Servers” on page 239 for more information about discovering master backup servers. The Include backup details option gathers the latest information about your backup applications. 3. The management server obtains most of its information from device managers for storage systems with external databases, such as HP, HDS, and EMC storage systems.
PAGE 169
5. View the status of the gathering of element details by looking in the View Logs page. See the topic, ”Viewing Log Messages” on page 98 for more information about the messages viewed in this tab. 6. Verify the topology is displayed correctly by accessing System Manager. Access System Manager by doing the following: • From HP SIM - Select Tools > Storage Essentials > System Manager. • From the HP SE Home page (Tools > Storage Essentials > Home) - Click the button for System Manager in the left pane.
PAGE 170
Details) and then click the Properties tab. The Properties tab can also be accessed by double clicking the switch in System Manager.
PAGE 171
5 Deploying and Managing CIM Extensions This chapter describes the following: • ”About Remote CIM Extensions Management” on page 149 • ”About the CIM Extensions Management Tool” on page 151 About Remote CIM Extensions Management It is possible to install, upgrade, and manage CIM Extensions remotely across any number of hosts. The following operations can be initiated from the management server: • Perform an installation or re-installation of the OpenSSH daemon (sshd) for Windows hosts only.
PAGE 172
• admin is the username • If you are not using a domain, don’t specify the host name when deploying OpenSSH. For example, enter a user name of where • admin is the user name If you are running the management server on Linux, you must manually install OpenSSH on Windows hosts. To install OpenSSH on a Windows host: 1. Copy the cp006690.exe file from the $JBOSS_DIST/plugin/sedeploy directory on the managment server. 2. Move the cp006690.
PAGE 173
1. Create a text file named cxws.default.login with the following format: -credentials : 2. Place the cxws.default.login file in the following directory on the management server: %JBOSS4_DIST%\Extensions\[Platform] where [Platform] is the directory of the host type. 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.
PAGE 174
6. Click the button if you want to edit the entry for a host. 7. Click the button if you want to delete a host from the list. Managing CIM Extensions on Remote Hosts Once you have added all the hosts that you want to manage, you can select any of the actions from the left panel. The following actions are available: • Display host operating system - Attempts to determine the remote operating system.
PAGE 175
NOTE: You can’t use the IP Address field when multiple hosts are listed. The Start Extensions on Custom Port checkbox will start the CIM extension on the specified port. NOTE: When setting up the collection of data from the management server, you must use the port with which you configured the extensions instead of the default port. The Use Custom Credentials checkbox configures the CIM Extensions to use a username and password that you specify.
PAGE 176
154 Deploying and Managing CIM Extensions
PAGE 177
6 Installing the CIM Extension for IBM AIX This chapter describes the following: • ”About the CIM Extension for IBM AIX” on page 155 • ”Prerequisites” on page 156 • ”Verifying SNIA HBA API Support” on page 156 • ”Installing the CIM Extension” on page 157 • ”Setting Up Monitoring” on page 158 • ”Starting the CIM Extension Manually” on page 158 • ”How to Determine if the CIM Extension Is Running” on page 159 • ”Configuring CIM Extensions” on page 159 • ”Stopping the CIM Extension” on page 162 • ”Stopping the
PAGE 178
• tools - The files to stop, start and show the status of the CIM Extension Prerequisites The installation checks for the following. If the installation fails, see ”Fulfilling the Prerequisites” on page 162. AIX 5.1 • Maintenance level 03 or later • bos.rte.libc.5.1.0.36 or later Both AIX 5.1 and 5.2 xlC.rte.5.0.2.1 or later AIX 5.3 • bos.rte.libc 5.3.0.0 • xlC.rte 6.0.0.0 Required Disk Space The CIM Extension for AIX requires 40 MB.
PAGE 179
program, hbatest, lists the name and number for all HBA's that support the SNIA HBA API. In some instances hbatest may report it cannot find an HBA driver even though an HBA driver is installed. Try installing a different version of the HBA driver that is SNIA compliant. To run hbatest: 1. Go to the Aix/tools directory on the CIM Extension CD-ROM. 2. Enter the following at the command prompt:./hbatest The program runs its diagnostics. IBM Adapters FCXXXX SNIA comes from the package devices.common.IBM.fc.
PAGE 180
11.Unmount the CD-ROM by entering the following at the command prompt: # umount /cdrom where /cdrom is the name of the directory where you mounted the CD-ROM 12.Complete the following: • Turn on Monitoring. See ”Setting Up Monitoring” on page 158. • Start the CIM Extension. See ”Starting the CIM Extension Manually” on page 158. • (Optional) On some versions of AIX, the CIM Extension cannot start automatically after the host is rebooted.
PAGE 181
How to Determine if the CIM Extension Is Running You can determine if the CIM Extension is running by entering the following command at the command prompt: # ./status The CIM Extension is running when the following message is displayed: CIM Extension Running: Process ID: 93 where 93 is the process ID running the CIM Extension Configuring CIM Extensions Configuration information is stored in a configuration text file that is read by the CIM Extension on start-up. The file is named cim.extension.
PAGE 182
Discovery > Setup > Add Address). In the IP Address/DNS Name field, type a colon and then the port number after the IP address or DNS name, as shown in the following example: 192.168.1.2:1234 where • 192.168.1.2 is the IP address of the host • 1234 is the new port number If you have already added the host to the discovery list (Tools > Storage Essentials > Home > Discovery > Setup) on the management server, you must remove it and then re-add it.
PAGE 183
If you change the port number, you must make the management server aware of the new port number in the Add Address for Discovery page (Tools > Storage Essentials > Home > Discovery > Setup > Add Address). In the IP Address/DNS Name field, type a colon and then the port number after the IP address or DNS name, as shown in the following example: 192.168.1.2:1234 where • 192.168.1.
PAGE 184
You are shown the version number of the CIM Extension and the date it was built, as shown in the following example: CXWS for mof/cxws/cxws-aix.mof CXWS version xxxx, built on Fri xx-March-xxxx 12:29:49 by dmaltz Stopping the CIM Extension To stop the background process for the CIM Extension, enter the following at the command prompt in the /opt/APPQcime/tools directory: # ./stop Keep in mind the following: • You must have root privileges to stop the CIM Extension.
PAGE 185
• xlC.rte 6.0.0.0* - The C++ runtime. *Go to the IBM Technical Support Web site at the following URL to obtain information about obtaining these file: https://techsupport.services.ibm.com On the Web page do the following: 1. Under the Refine Your Search Section select Tools/Utilities from the Limit by Type drop-down menu. 2. Select AIX from the Limit by Platform or Operating System drop-down menu. 3. Select 5.0 from the Limit by Version drop-down menu. 4.
PAGE 186
6. In the SOFTWARE name, press Esc+4 and select: APPQcime 7. On the same page you selected APPQcime, select “No” for Preview by pressing the tab key. 8. Press ENTER to remove the software.
PAGE 187
7 Installing the CIM Extension for SGI ProPack for Linux This chapter describes the following: • ”About the CIM Extension for SGI ProPack for Linux” on page 165 • ”Prerequisites” on page 165 • ”Verifying SNIA HBA API Support” on page 166 • ”Installing the CIM Extension” on page 166 • ”Starting the CIM Extension” on page 167 • ”How to Determine if the CIM Extension Is Running” on page 169 • ”Configuring CIM Extensions” on page 169 • ”Rolling Over the Logs” on page 171 • ”Stopping the CIM Extension” on page
PAGE 188
• Blowfish • DES • MD5 NOTE: All ProPacks require that pam-devel rpm is installed. Network Port Must Be Open The CIM Extension uses port 4673 by default to communicate with the management server. Verify the network port is open. Refer to the documentation accompanying your Altix host for more information. If you need to use a different port, see ”Permanently Changing the Port a CIM Extension Uses (UNIX Only)” on page 308.
PAGE 189
1. Go to the /Altix directory on the CIM Extensions CD-ROM by entering the following at the command prompt: # cd /cdrom/Altix where /cdrom is the directory where you mounted the CD-ROM. 2. To install the software, do one of the following: IMPORTANT: If you receive a message saying there is not enough room in the temp directory to perform the installation, set the IATEMPDIR variable to another directory. The installation uses this directory to extract the installation files.
PAGE 190
• To configure UNIX CIM Extensions to run behind a firewall, see ”Configuring UNIX CIM Extensions to Run Behind Firewalls” on page 309. To start the CIM Extension, type the following in the /opt/APPQcime/tools directory: 1.
PAGE 191
• When you start the CIM Extension, you can restrict the user accounts that can discover the host. You can also change the port number the CIM Extension uses. See the following topics for more information. You can also access information about these topics by typing the following: ./start -help How to Determine if the CIM Extension Is Running You can determine if the CIM Extension is running by entering the following command at the command prompt: # .
PAGE 192
If you change the port number, you must make the management server aware of the new port number in the Add Address for Discovery page (Tools > Storage Essentials > Home > Discovery > Setup > Add Address). In the IP Address/DNS Name field, type a colon and then the port number after the IP address or DNS name, as shown in the following example: 192.168.1.2:1234 where • 192.168.1.
PAGE 193
discovered as a target. On the System Protocol Settings page, provide the port number for the host under the WBEM section. Discovery from HP SE If you change the port number, you must make the management server aware of the new port number in the Add Address for Discovery page (Tools > Storage Essentials > Home > Discovery > Setup > Add Address). In the IP Address/DNS Name field, type a colon and then the port number after the IP address or DNS name, as shown in the following example: 192.168.1.
PAGE 194
The logging information for the CIM Extension is contained primarily in the cxws.log file, created by default in the /tools directory. The cxws.log file rolls over once it becomes more than 100 MB. The information in cxws.log is moved to cxws.log.1. When the logs roll over again, cxws.log.1 is renamed to cxws.log.2 and the information that is in cxws.log is moved to cxws.log.1. The numbering for the files continues sequentially, for example, cxws.log.
PAGE 195
8 Installing the CIM Extension for HP-UX This chapter describes the following: • ”About the CIM Extension for HP-UX” on page 173 • ”Prerequisites” on page 173 • ”Verifying SNIA HBA API Support” on page 174 • ”Installing the CIM Extension” on page 175 • ”Starting the CIM Extension Manually” on page 176 • ”How to Determine if the CIM Extension Is Running” on page 176 • ”Configuring CIM Extensions” on page 176 • ”Stopping the CIM Extension” on page 181 • ”Rolling Over the Logs” on page 181 • ”Fulfilling the P
PAGE 196
HP-UX 11i and 11.0 Software Requirements Following software driver bundles must be installed on HP-UX 11i and 11.0 hosts. FC SNIA HBA API software is bundled with the driver and is installed at the same time the driver is installed. HP-UX 11i Driver Bundle Version B.11.11.09 PCI/HSC FibreChannel;Supptd HW=A6684A,A6685A,A5158A,A6795A (FibrChanl-00 Bundle). This driver Bundle is automatically selected for installation with the HP-UX 11i Operating Environments. Driver Version = @(#) PATCH_11.11: libtd.
PAGE 197
1. Go to the HPUX/tools directory on the CIM Extension CD-ROM. 2. Enter the following at the command prompt: ./hbatest The program runs its diagnostics. HP SNIA Adapters AXXXXA comes from fileset FC-FCD, FC-TACHYON-TL. Unless separated purposely during installing the operating system, filesets are there by default. To view the location of the library, enter the following at the command prompt: # more /etc/hba.conf The following is displayed: com.hp.fcms32 /usr/lib/libhbaapihp.
PAGE 198
7. Press the Eject button on the CD-ROM drive to take the CD out of the CD-ROM drive. The CIM Extension for HP-UX starts automatically at boot time by using /sbin/rc2.d scripts. The CIM Extension uses port 4673 when it starts automatically after a reboot. Type the following at the command prompt to find the status of the CIM Extension: ./status Starting the CIM Extension Manually The management server can only obtain information from this host when the CIM Extension is running.
PAGE 199
parameters and can be copied into the cim.extension.parameters file and used as a template. Restricting the Users Who Can Discover the Host The -users parameter provides greater security by restricting access. When you use the management server to discover the host, provide a user name that was specified in the -users parameter. For example, assume you want to use the management server to discover a HP-UX host, but you do not want to provide the password to the root account.
PAGE 200
NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. Discovery from HP SIM If you change the port number, you must include the new port number in your discovery. If you have not already done so, discover the host. See ”Adding an IP Range for Scanning” on page 65 or ”Adding a Single IP Address or DNS Name for Discovery” on page 66 for more information.
PAGE 201
NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. The “-on” parameter may include a port specification. In that case, the CIM Extension listens on the indicated port of the indicated NIC, rather than the default port, for example: -on 192.168.2.2:3456 The CIM Extension listens only on the NIC that has the IP address 192.168.2.2 on port 3456.
PAGE 202
Table 12 Parameters for CIM Extensions Parameter Description -user The user defined in this parameter must be a valid user for the host. Only the user needs to be defined. The user name and password are provided from the management server during discovery. The user does not need to have root authority. A colon separated list can be used to specify multiple users.
PAGE 203
• 1234 is the new port Stopping the CIM Extension To stop the CIM Extension, enter the following at the command prompt in the /opt/APPQcime/tools directory, where /opt is the directory into which you installed the CIM Extension: # ./stop Keep in mind the following: • You must have root privileges to stop the CIM Extension. • When you stop the CIM Extension, the management server is unable to gather information about this host.
PAGE 204
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 181. 3. Make sure you are not in the APPQcime directory. As a precaution, go to the root directory. 4. Enter the following at the command prompt: # swremove APPQcime When you see the following message, the CIM Extension has been removed: * Beginning Execution * The execution phase succeeded for hpuxqaX.dnsxxx.com:/".
PAGE 205
9 Installing the CIM Extension for SUSE and Red Hat Linux This chapter describes the following: • ”About the CIM Extension for Red Hat Linux Advanced Server and SUSE Linux” on page 183 • ”Prerequisites” on page 183 • ”Verifying SNIA HBA API Support” on page 184 • ”Installing the CIM Extension” on page 185 • ”Starting the CIM Extension Manually” on page 186 • ”How to Determine if the CIM Extension Is Running” on page 186 • ”Configuring CIM Extensions” on page 186 • ”Stopping the CIM Extension” on page 189 •
PAGE 206
Red Hat Linux Advanced Server 4.0 (Update 4) • libstdc++compat-libstdc++-296-2.96-132.7.2.rpm • libgcc-3.4.5-2.i386.rpm • libgcc-3.4.5-2.x86_64.rpm • compat-libstdc++-33-3.2.3-47.3.i386.rpm • compat-libstdc++-33-3.2.3-47.3.x86_64.rpm • compat-libgcc-296-2.96-132.7.2.i386.rpm SUSE 9 (SP 3) X86_64 • compat-32bit-9-200407011229.x86_64.rpm • liblcms-1.12-55.1.x86_64.rpm • libtiff-3.6.1-38.3.x86_64.rpm • libtiff-32bit-9-200407011229.x86_64.rpm SUSE 9 (SP 3) X86_32 • compat-2004.7.1-1.2.i586.rpm • libtiff-3.6.
PAGE 207
Emulex Adapters SNIA comes from package HBAnyware. To view the library location, enter the following at the command prompt: # more /etc/hba.conf The following is displayed: com.emulex.emulexapilibrary /usr/lib/libemulexhbaapi.so Driver Information for Verifying QLogic SNIA Adapters on Red Hat Linux QLogic SNIA Adapters comes from package qlapi-vX.XXX-rel.tgz found in the QLogic driver. The adapters are installed separately after driver.
PAGE 208
• For 64-bit Linux Itanium Servers: # rpm -idvh APPQcimeIa64.rpm • For all other servers: # rpm -idvh APPQcime.rpm The installation is done when you are returned to the command prompt. Starting the CIM Extension Manually The management server can only obtain information from this host when the CIM Extension is running. Keep in mind the following: • You must have root privileges to run the CIM Extension.
PAGE 209
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 the port is already used, follow these steps to change the port the CIM Extension will access: 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.parameters file in a text editor, and provide the following line: -port 1234 where 1234 is the new port for the CIM Extension 3. Save the file. 4.
PAGE 210
2. Open the cim.extension.parameters file in a text editor, and provide the following line: -on 127.0.0.1,192.168.0.1 NOTE: If you want to configure the CIM Extension to listen on multiple NICs, use a comma to separate multiple addresses. 3. Save the file. 4. Restart the CIM Extension for your changes to take effect. NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted.
PAGE 211
Additional Parameters The following table describes additional parameters that can be specified in the cim.extension.parameters file: Table 13 Parameters for CIM Extensions Parameter Description -user The user defined in this parameter must be a valid user for the host. Only the user needs to be defined. The user name and password are provided from the management server during discovery. The user does not need to have root authority. A colon separated list can be used to specify multiple users.
PAGE 212
• When you stop the CIM Extension, the management server is unable to gather information about this host. Rolling Over the Logs The logging information for the CIM Extension is contained primarily in the cxws.log file, created by default in the /tools directory.The cxws.log file rolls over once it becomes more than 100 MB. The information in cxws.log is moved to cxws.log.1. When the logs roll over again, cxws.log.1 is renamed to cxws.log.2 and the information that is in cxws.
PAGE 213
10 Installing the CIM Extension for OpenVMS This chapter describes the following: • ”About the CIM Extension for OpenVMS” on page 191 • ”Prerequisites” on page 192 • ”Installing the CIM Extension for OpenVMS” on page 193 • ”Starting the CIM Extension Manually” on page 194 • ”Finding the Status of the CIM Extension” on page 195 • ”Manually Starting the CIM Extension to Specify Multiple Users in a Colon-separated List” on page 195 • ”Changing the Port Number” on page 196 • ”Configuring the CIM Extension to Li
PAGE 214
Prerequisites The required prerequisites are listed below: • Supported OpenVMS (Alpha) versions and required ECOs • To verify installed patches, enter the following at the command prompt: $ prod sh prod/full • OVMS alpha 7.3-2 The following patches must be installed in the order specified: • DEC-AXPVMS-VMS732_PCSI-V0300 • DEC-AXPVMS-VMS732_UPDATE-V0600 • DEC-AXPVMS-VMS732_SYS-V1000 • DEC-AXPVMS-VMS732_FIBRE_SCSI-V0900 • OVMS Alpha 8.
PAGE 215
Installing the CIM Extension for OpenVMS This section covers the following CIM Extension installations for OpenVMS: • ”Installing the CIM Extension on a Standalone Host” on page 193 • ”Installing the CIM Extension on a Cluster” on page 194 Installing the CIM Extension on a Standalone Host This section describes how to install the CIM Extension for OpenVMS on standalone hosts. • The CIM Extension on OpenVMS needs to be installed locally on each of the required hosts.
PAGE 216
9. Run the installation script by entering the following command. $ @OVMSINST 10.Press Enter when prompted for confirmation by the PCS as shown in the example below: ********** The following product has been selected: HP AXPVMS APPQCIME V5.0 Layered Product Do you want to continue? [YES] *********** The installation is completed with the default values and the APPQCIME process starts. 11.Verify that the SE Agent process starts properly.
PAGE 217
Finding the Status of the CIM Extension You can check the status of the CIM Extension by entering the following in the sys$common:[opt.appqcime.tools] directory. $ @status The CIM Extension is running when the following message is displayed: CIM Extension is running. Process id :001B0AEE where 001B0AEE is the process ID running the CIM Extension. Restricting the Users Who Can Discover the Host You can restrict the user accounts that can discover the host when the CIM Extension is started.
PAGE 218
Changing the Port Number This section provides instructions on changing the port number used by the CIM Extension for OpenVMS. The CIM Extension uses port 4673 by default. If this port is already in use, use the following command to change the port number the CIM Extension will access: @sys$common:[opt.appqcime.tools]start -port port_number For example, if you are running a J2EE server, such as BEA WebLogic or IBM WebSphere, the J2EE server might already be using the 4673 port. To change the port number: 1.
PAGE 219
NOTE: If you specify a port with the start command, the host can be discovered by any account that has access to the OpenVMS host. Configuring the CIM Extension to Listen on a Specific Network Card You can configure the CIM Extension to listen only on a specific network interface card (NIC) by using the -on command line option in the start command, for example: @sys$common:[opt.appqcime.tools]start -on 192.168.2.2 The CIM Extension listens only on the NIC that has the IP address 192.168.2.2.
PAGE 220
If you have already added the NIC to the discovery list on the management server, you must remove it and then add it again. You cannot have more than one listing of the NIC with different ports. Finding the Version of a CIM Extension You can find the version number of a CIM Extension: 1. Navigate to the sys$common:[opt.appqcime.tools] directory. 2. Type the following at the command prompt: $ @start -version The version number is displayed as shown in the example below. CXWS VERSION: 4.2.0.
PAGE 221
Stopping the CIM Extension To stop the CIM Extension: 1. Log in to the system as a superuser. 2. Navigate to the following directory: sys$common:[opt.appqcime.tools] Where sys$common:[opt] is the directory in which you installed the CIM Extension. 3. Type: $ @stop to stop the CIM Extension. NOTE: Once the CIM Extension is stopped on the host, the management server will not be able to gather information about this host.
PAGE 222
Removing the CIM Extension from OpenVMS This section includes information on removing (uninstalling) the CIM Extension. It covers the following topics: • ”Uninstalling the OpenVMS CIM Extension on a Standalone Host” on page 200 • ”Uninstalling the OpenVMS CIM Extension on a Cluster Host” on page 200 Uninstalling the OpenVMS CIM Extension on a Standalone Host To remove the CIM Extension for OpenVMS on a standalone host: 1. Login as system. 2. Enter the following at the command prompt: $ @sys$common:[opt.
PAGE 223
11 Installing the CIM Extension for HP Tru64 UNIX This chapter describes the following: • ”About the CIM Extension for Tru64 UNIX” on page 201 • ”Prerequisites” on page 201 • ”Installing the CIM Extension” on page 203 • ”Starting the CIM Extension Manually” on page 204 • ”How to Determine if the CIM Extension Is Running” on page 205 • ”Configuring CIM Extensions” on page 205 • ”Finding the Version of a CIM Extension” on page 208 • ”Stopping the CIM Extension” on page 209 • ”Rolling Over the Logs” on page 20
PAGE 224
Also, verify the following before you install the CIM Extension: • ”Software Requirements” on page 202 • ”Required Disk Space” on page 202 • ”SNIA HBA API Support” on page 202 Software Requirements NOTE: You do not need to install the FC-HBA shared libraries if you are running Tru64 UNIX version 5.1B-4. If you are running Tru64 UNIX version 5.1B-3 or version 5.1B-2, you must install one of the following SNIA patches to obtain the FC-HBA shared libraries. • For Tru64 UNIX version 5.
PAGE 225
Installing the CIM Extension IMPORTANT: You must install the CIM Extension for Tru64 in the default directory. You can install the CIM Extension for Tru64 one of two ways: • On a Standalone Host - See ”Installing CIM Extension on a Standalone Host” on page 203. • On a Cluster - See ”Installing the CIM Extension on a Cluster” on page 204. Installing CIM Extension on a Standalone Host To install the CIM Extension using CLI: 1. Login as root. 2.
PAGE 226
Installing the CIM Extension on a Cluster The installation of the CIM Extension on a cluster is similar to the installation of the CIM Extension on a standalone node. However, on a cluster it is required to run the install script on only one node of the cluster. By default the install script (tru64_local_install.sh) starts the CIM Extension automatically on all nodes of the cluster after an installation.
PAGE 227
How to Determine if the CIM Extension Is Running You can determine if the CIM Extension is running by entering the following command at the command prompt: # ./status The CIM Extension is running when the following message is displayed: CIM Extension Running: Process ID: 93 where 93 is the process ID running the CIM Extension Configuring CIM Extensions Configuration information is stored in a configuration text file that is read by the CIM Extension on start-up. The file is named cim.extension.
PAGE 228
NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. Changing the Port Number The CIM Extension uses port 4673 by default. If the port is already used, follow these steps to change the port the CIM Extension will access: 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.
PAGE 229
Configuring the CIM Extension to Listen on a Specific Network Card Follow these steps to configure the CIM Extension to listen on a specific network card (NIC): 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.parameters file in a text editor, and provide the following line: -on 127.0.0.1,192.168.0.1 NOTE: If you want to configure the CIM Extension to listen on multiple NICs, use a comma to separate multiple addresses. 3. Save the file. 4.
PAGE 230
If you have already added the host to the discovery list (Tools > Storage Essentials > Home > Discovery > Setup) on the management server, you must remove it and then re-add it. You cannot have more than one listing of the host with different ports. Additional Parameters The following table describes additional parameters that can be specified in the cim.extension.
PAGE 231
• 4673 is the port used by the CIM extension Stopping the CIM Extension To stop the CIM Extension, enter the following at the command prompt in the /opt/APPQcime/tools directory, where /opt is the directory into which you installed the CIM Extension: # ./stop Keep in mind the following: • You must have root privileges to stop the CIM Extension. • When you stop the CIM Extension, the management server is unable to gather information about this host.
PAGE 232
Ensure that the required patches listed in the prerequisites are present Removing the CIM Extension from Tru64 This section describes the following: • ”Removing the CIM Extension from a Standalone Host” on page 210 • ”Removing the CIM Extension from a Cluster” on page 210 Removing the CIM Extension from a Standalone Host To remove the CIM Extension for Tru64: 1. Login as root. 2. Go to the /opt/APPQcime/scripts directory, where /opt is the directory into which you installed the CIM Extension. 3.
PAGE 233
12 Installing the CIM Extension for SGI IRIX This chapter describes the following: • ”About the CIM Extension for SGI IRIX” on page 211 • ”Prerequisites” on page 211 • ”Verifying SNIA HBA API Support” on page 212 • ”Installing the CIM Extension” on page 212 • ”Starting the CIM Extension” on page 213 • ”How to Determine if the CIM Extension Is Running” on page 213 • ”Configuring CIM Extensions” on page 213 • ”Stopping the CIM Extension” on page 217 • ”Rolling Over the Logs” on page 217 • ”Removing the CIM Ex
PAGE 234
• IRIX version 6.5.20, path required. Contact customer support for the patch. Network Port Must Be Open The CIM Extension uses port 4673 by default to communicate with the management server. Verify the network port is open. Refer to the documentation accompanying your IRIX host for more information. If you need to use a different port, see ”Permanently Changing the Port a CIM Extension Uses (UNIX Only)” on page 308.
PAGE 235
9. Enter the following to restart the ELF files and to exit the installation program: Inst> quit You must start the CIM Extension for the management server to obtain information about the host. See ”Starting the CIM Extension” on page 213 Starting the CIM Extension The management server can only obtain information from this host when the CIM Extension is running. Keep in mind the following: • You must have root privileges to run the CIM Extension.
PAGE 236
2. Open the cim.extension.parameters file in a text editor, and provide the following line: -port 1234 where 1234 is the new port for the CIM Extension 3. Save the file. 4. Restart the CIM Extension for your changes to take effect. NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. Discovery from HP SIM If you change the port number, you must include the new port number in your discovery.
PAGE 237
4. Restart the CIM Extension for your changes to take effect. NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. The “-on” parameter may include a port specification. In that case, the CIM Extension listens on the indicated port of the indicated NIC, rather than the default port, for example: -on 192.168.2.2:3456 The CIM Extension listens only on the NIC that has the IP address 192.168.2.
PAGE 238
Table 2 Parameters for CIM Extensions Parameter Description -user The user defined in this parameter must be a valid user for the host. Only the user needs to be defined. The user name and password are provided from the management server during discovery. The user does not need to have root authority. A colon separated list can be used to specify multiple users.
PAGE 239
1. Go to the /opt/APPQcime/tools directory. 2. Type the following at the command prompt: # ./start -version You are shown the version number of the CIM Extension and the date it was built, as shown in the following example: CXWS for mof/cxws/cxws-irix.mof CXWS version x.x.x.x, built on Fri 12-March-xxxx 12:29:49 by dmaltz where • x.x.x.x is the version of the CIM Extension • xxxx is the year.
PAGE 240
3. Enter the following at the Inst command prompt: Inst> remove 4. When you are asked which subsystem you want to remove, enter the following: APPQcime 5. To begin the removal of the CIM Extension, enter the following at the Inst command prompt: Inst> go The CIM Extension is removed from IRIX. 6.
PAGE 241
13 Installing the CIM Extension for Sun Solaris This chapter describes the following: • ”About the CIM Extension for Solaris” on page 219 • ”Prerequisites” on page 219 • ”Verifying SNIA HBA API Support” on page 220 • ”Installing the CIM Extension” on page 221 • ”Starting the CIM Extension Manually” on page 222 • ”How to Determine if the CIM Extension Is Running” on page 223 • ”Configuring CIM Extensions” on page 223 • ”Stopping the CIM Extension” on page 227 • ”Rolling Over the Logs” on page 227 • ”Removing
PAGE 242
1. SUNWlibC - Sun Workshop Compilers Bundled libC 2. SUNWlibCf - SunSoft WorkShop Bundled libC (cfront version) 3. SUNWlibCx - Sun Workshop Bundled 64-bit libC IMPORTANT: Verify you have the latest patches installed. The patches can be obtained from the Sun Microsystems Web site at http://www.sun.com. You must have the following space: • CIM Extension - The CIM Extension requires 90 MB of disk space. • Logs - Make sure you have 100 MB for log files.
PAGE 243
Driver Information for Verifying SNIA Emulex Adapters The SNIA Library comes from a separate package HBAnyware. If you installed SNIA Emulex adapter, you can find its library by entering the following at the command prompt: # more /etc/hba.conf The following is displayed: com.emulex.emulexapilibrary /usr/lib/libemulexhbaapi.so com.emulex.emulexapilibrary /usr/lib/sparcv9/libemulexhbaapi.so Driver Information for QLogic Adapters The SNIA HBA package comes from a separate package QLSDMLIB.
PAGE 244
• The server must be running sh, ksh or bash shell. C shell is not supported. To install the CIM Extension: 1. Login as root. 2. Go to the Solaris directory on the CIM Extension CD-ROM by entering the following at the command prompt: # cd /cdrom/cdrom0/Solaris where /cdrom/cdrom0 is the name of the CD-ROM drive 3. Enter the following at the command prompt: # pkgadd -d APPQcime.pkg APPQcime The APPQcime package is added. 4.
PAGE 245
How to Determine if the CIM Extension Is Running You can determine if the CIM Extension is running by entering the following command at the command prompt: # ./status The CIM Extension is running when the following message is displayed: CIM Extension Running: Process ID: 93 where 93 is the process ID running the CIM Extension Configuring CIM Extensions Configuration information is stored in a configuration text file that is read by the CIM Extension on start-up. The file is named cim.extension.
PAGE 246
NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. Changing the Port Number The CIM Extension uses port 4673 by default. If the port is already used, follow these steps to change the port the CIM Extension will access: 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.
PAGE 247
Configuring the CIM Extension to Listen on a Specific Network Card Follow these steps to configure the CIM Extension to listen on a specific network card (NIC): 1. Go to the [Installation_Directory]/conf directory. 2. Open the cim.extension.parameters file in a text editor, and provide the following line: -on 127.0.0.1,192.168.0.1 NOTE: If you want to configure the CIM Extension to listen on multiple NICs, use a comma to separate multiple addresses. 3. Save the file. 4.
PAGE 248
If you have already added the host to the discovery list (Tools > Storage Essentials > Home > Discovery > Setup) on the management server, you must remove it and then re-add it. You cannot have more than one listing of the host with different ports. Additional Parameters The following table describes additional parameters that can be specified in the cim.extension.
PAGE 249
Combining Start Commands You can also combine the -users and -port commands as follows: ./start -users myname -port 1234 or ./start -port 1234 -users myname where myname is the user name that must be used to discover this Solaris host 1234 is the new port Stopping the CIM Extension To stop the CIM Extension, enter the following at the command prompt in the /opt/APPQcime/tools directory, where /opt is the directory into which you installed the CIM Extension: # .
PAGE 250
3. Enter the following at the command prompt: # pkgrm APPQcime 4. Enter y when you are asked if you want to remove the CIM Extension. When you see the following message, the CIM Extension has been removed: Removal of was successful.
PAGE 251
14 Installing the CIM Extension for Microsoft Windows This chapter describes the following: • ”About the CIM Extension for Windows” on page 229 • ”Verifying SNIA HBA API Support” on page 229 • ”Upgrading a Host with the Latest CIM Extension” on page 231 • ”Installation Steps” on page 232 • ”Installing the CIM Extension Using the Silent Installation” on page 233 • ”Configuring CIM Extensions” on page 233 • ”Rolling Over the Logs” on page 235 • ”Removing the CIM Extension from Windows” on page 237 NOTE: This
PAGE 252
• If you have not installed the CIM Extension - Go to the Windows\tools directory on the CIM Extension CD-ROM. • If you have installed the CIM Extension - Go to the \CimExtensions\tools directory on the host running the CIM Extension. 2. Enter the following at the command prompt: hbatest.exe The program lists the name and number for all HBA’s that support the SNIA HBA API. 3.
PAGE 253
C:\Program Files\IBM FASt MSJ\ql2xhai2.dll Driver Information for Verifying QLogic Adapters This section provides information for verifying QLogic adapters. If you have QLogic Adapters: When you install the SNIA HBA, it either came with the driver or SANsurfer, the registry setting is most likely in the following location, which varies by release: HKEY_LOCAL_MACHINE\SOFTWARE\SNIA\HBA\QL2XXX Newer drivers points to C:\WINNT\system32\ql2xhai2.dll, but they also have system32\qlsdm.dll available.
PAGE 254
• For hosts that are not in the “Default” discovery group - Restart AppStorManager, which is the service for the management server. IMPORTANT: If you do Get Details/Discovery Data Collection immediately after a Windows host is upgraded without restarting the management server, you will have missing/incorrect data. You will also have missing and/or incorrect data until you finish the steps in this section. To avoid having to restart AppStorManager, see the following options.
PAGE 255
6. Do one of the following: • Click Install if you agree with the pre-installation summary. • Click Previous if you want to modify your selections. The CIM Extension is installed. 7. When you have been told the installation has been successful, click Done to quit the installation. IMPORTANT: Keep in mind that the CIM Extension automatically starts when the system is restarted. The management server can only obtain information from this host when the CIM Extension is running.
PAGE 256
where 1234 is the new port for the CIM Extension 3. Save the file. 4. Restart the CIM Extension for your changes to take effect. NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. Discovery from HP SIM If you change the port number, you must include the new port number in your discovery. If you have not already done so, discover the host.
PAGE 257
Table 4 Parameters for CIM Extensions 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. -agentnic Restricts the CIM Extension on multihomed systems to listen only on the designated IP address.
PAGE 258
NOTE: The CIM Extension looks for parameters in the cim.extension.parameters file whenever it starts, such as when it is started manually or when the host is rebooted. The “-on” parameter may include a port specification. In that case, the CIM Extension listens on the indicated port of the indicated NIC, rather than the default port, for example: -on 192.168.2.2:3456 The CIM Extension listens only on the NIC that has the IP address 192.168.2.2 on port 3456.
PAGE 259
3. From the Currently installed programs list, select Windows CIM Extension. 4. Click the Change/Remove button. 5. When you are told the product is about to be uninstalled, click Uninstall. 6. When the program is done with removing the product, click Done. 7. It is highly recommended you reboot the host. Storage Essentials 5.
PAGE 260
238 Installing the CIM Extension for Microsoft Windows
PAGE 261
15 Discovering Applications, Backup Servers and Hosts IMPORTANT: Information about Systems Insight Manager (SIM), such as discovery instructions, are for SIM version 5.0.
PAGE 262
• (Discovery from HP SE only) If your license lets you discover UNIX and/or Linux hosts, the Test button for discovery reports SUCCESS from any UNIX and/or Linux hosts on which the management server can detect a CIM Extension. The CIM Extension must be running. The management server reports “SUCCESS” even if your license restricts you from discovering certain types of hosts. For example, assume your license lets you discover Solaris hosts but not AIX hosts.
PAGE 263
IMPORTANT: Complete the steps in this section if you want to discover backup applications, such as Veritas NetBackup and HP Data Protector on Windows, HP-UX, and Linux. You can skip this section if you are running Veritas NetBackup and HP Data Protector on Sun Solaris. See the Support Matrix for more information on supported platforms. If you want to manage and monitor your backups from hosts running Windows, HP-UX and Linux, you must modify the cimom.mof.include.
PAGE 264
d. Delete the NetBackup or Data Protector server. e. From HP SIM, delete the NetBackup or Data Protector server from the Systems list. 9. When you are done, click Save. 10.Restart the service for the management server for your changes to take effect. While AppStorManager is restarting, users are not able to access the management server. The AppStorManager service must be running for the management server to monitor elements. 11.
PAGE 265
Discovery from HP SE 1. Discover your hosts as described in this section. 2. Build the topology. See ”Step B - (Discovery from HP SE Only) Build the Topology” on page 246. 3. If you want to view the topology, you can access System Manager. See ”(Optional) Step C (Discovery from HP SE Only)View the Topology” on page 246. 4. Perform Get Details. See ”Step D - Obtain Details” on page 247.
PAGE 266
• If you try to discover a Solaris host with multiple IP address, the management server picks only one IP address for discovery. • To access a Windows-based device, prefix the user name with domain_name\, as shown in the following example. This is required by the Windows login mechanism. IMPORTANT: If you want to use the HP SIM discovery mechanism, you must provide HP SIM with the credentials required by HP SE for HP SE to be successful.
PAGE 267
To access a Windows-based device, prefix the user name with the Windows domain name, as shown in the following example. It is required by the Windows login mechanism. domain_name\username where • domain_name is the domain name of the element • username is the name of the account used to access that element f. In the Password (Optional) field, type the password corresponding to the user name entered in the User Name field. g. Type the password from the previous step in the Verify Password field. h.
PAGE 268
g. In the Comment field, type a brief description of the server. For example, Server Used for Nightly Backups. h. Click OK. 5. To start discovering elements on the network, click the Start Discovery button on the IP Addresses tab. The software discovers the IP addresses selected. During discovery, the following occurs: • The software changes the status light from green to orange. • You are shown the Log Messages page. To view the status of discovery, click Discovery > View Logs.
PAGE 269
1. Click Tools > Storage Essentials > Home > System Manager button in the left pane. 2. When you are asked if you want to trust the signed applet, click Always. The Always option prevents this message from being displayed every time you access System Manager, Capacity Manager, and Performance Manager. The elements are shown connected to each other in the topology. If you see a question mark above a host, the management server cannot obtain additional information about that element.
PAGE 270
connected through a switch and storage system. When you Get Details/Discovery Data Collection for Discovery Group 1, you also obtain details from the switch and storage system. • If the management server unable to obtain information from a UNIX host during Get Details/Discovery Data Collection as a result of a CIM Extension hanging, the management server places the access point where the CIM Extension is located in quarantine.
PAGE 271
Then, set up the configurations for your applications on the management server. Some applications may require you to provide additional discovery information about the application. Finally, perform discovery and then obtain Get Details/Discovery Data Collection. Get Details and Discovery Data Collection takes some time. Perform this step when the network is not busy. More details about the steps mentioned above are provided later.
PAGE 272
entering the following at the command prompt: lsnrctl status. If the listener is not running you can start it by typing lsnrctl start on command line. • Make sure you have all the necessary information before you begin the installation. Read through the following steps before you begin. To create the Oracle user for management server: 1.
PAGE 273
Keep in mind the following: • Before you remove the APPIQ_USER account for an Oracle instance, make sure no processes are running APPIQ_USER for that Oracle instance. The management server uses APPIQ_USER to obtain information about the Oracle database. For example, a process would be using APPIQ_USER if someone was using Performance Manager to view monitoring statistics about that Oracle instance.
PAGE 274
• Discovery from HP SIM - Select Options > Protocol Settings > Storage Essentials > Global Application Discovery Settings. The TNS Listener Port setting applies to all Oracle instances you monitor. 2. To assign a new port, click the Create button for the Oracle Information table. 3. Type the new port number and click OK. 4. If necessary, click the button to remove the old port number. IMPORTANT: Monitoring Oracle 10g and Oracle clusters require an additional step.
PAGE 275
The port can be found in the following code: LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0)) ) ) ) 6. Select ORACLE from the Database Type menu. 7. Click OK. Discovering Oracle Clusters Perform the following steps for each node in the cluster: 1. Install the CIM Extension on each node in the cluster. 2. Create the appiq_user account on each node in the cluster.
PAGE 276
the following directory on the host of the monitored database. Do not look for the listener.ora file on the management server for this information. %ORA_HOME%\network\admin\listener.ora d. In the Server Name field, type the Oracle System Identifier (SID) of the Oracle database you want to monitor. e. In the Port Number field, type the monitored port. If you are not sure of the monitored port, check the listener.ora file of the monitored database application. You can find the listener.
PAGE 277
IMPORTANT: Make sure the Microsoft SQL server database is in “Mixed Mode authentication.” To switch to mixed mode authentication, see ”Switching to Mixed Mode Authentication” on page 254. Switching to Mixed Mode Authentication IMPORTANT: Do not make security changes to your Microsoft SQL Server installation unless you are familiar with the security requirements of your site. Microsoft SQL Server must be running in Mixed Mode Authentication. You can switch to Mixed Mode Authentication as follows: 1.
PAGE 278
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. Run the CreateSQLServerAct.bat script on Microsoft Windows on the computer with the SQL Server database. The script creates a user with login to master and select privilege on data dictionary tables on a managed SQL Server instance. NOTE: You can use a remote SQL Server isql to run this script. 4.
PAGE 279
IMPORTANT: You must provide the host name in the Host IP/DNS Name field. You cannot use localhost or parenthesis. If you have name resolutions issues, your server may be discovered; however, your applications will not be discovered. You can addressed the name resolution issues by adding entries within the hosts file on the management server for the systems in question.
PAGE 280
• Host IP/DNS Name: 192.168.2.10 • Database Server: SQLTEST • Port Number: 1433 • Database Type: SQLSERVER 6. In the Port Number field, type the port that SQL is using. If you do not provide a port number, the management server assumes the SQL server is using port 1433 (default). To determine the correct SQL Port Number that the SQL Server is using, follow these steps: a. Open SQL Server Enterprise Manager. b.
PAGE 281
5. Type the password for the server administrator account. The account for APPIQ_USER is removed. The management server can no longer monitor the SQL Server databases on this host. Deleting SQL Server Information If you do not want the management server to monitor a SQL Server instance, you can remove its information, as described in the following steps: 1. Do one of the following: • Discovery from HP SE - Select Tools > Storage Essentials > Home > Discovery > Setup.
PAGE 282
UNIX on the computer running the Sybase database you want to monitor. The account has create session and select dictionary privileges to be used with the management server. Keep in mind the following: • The script must run under SA user. • Obtain the Sybase server name before you run the script • Create APPIQ_USER account on Sybase Database you want to monitor. • You should have already installed the database for the management server.
PAGE 283
Removing the APPIQ_USER Account for Sybase IMPORTANT: Before you remove the APPIQ_USER account for the Sybase databases on a host, make sure no processes are running APPIQ_USER for that Sybase database. The management server uses APPIQ_USER to obtain information about a Sybase database. (Discovery from HP SE) One of the ways to make sure APPIQ_USER is not being used is to temporarily remove the host running Sybase (Discovery > Topology).
PAGE 284
desktop. Refer to the documentation for HP Systems Insight Manager. Select a target, and then, click Run Now. 2. Click the Create button for the Database Information table. 3. In the Host IP/DNS Name field, type the IP address or DNS name of the host running Sybase. 4. You can leave the Management IP/DNS Name field blank. This field is for Oracle clusters.
PAGE 285
• Discover the application. Adding Microsoft Exchange Domain Controller Access To obtain information about your Microsoft Exchange servers, you must provide the user name and password for at least a primary domain controller, in addition to a DNS name, as described in the following steps. IMPORTANT: The hosts should recognize the management server by name, as a reverse look-up is required by operating system security as well as Microsoft Exchange.
PAGE 286
• Discovery from HP SE - Select Tools > Storage Essentials > Home > Discovery > Setup. Then, click the Applications tab. • Discovery from HP SIM - Select Options > Protocol Settings > Storage Essentials > Global Application Discovery Settings. 2. Click the button, corresponding to the domain controller you want to remove. 3. Perform Get Details/Discovery Data Collection for your changes to take effect.
PAGE 287
• You are shown the Log Messages page. To view the status of discovery, click Discovery > View Logs. Discovery is complete when the software displays the DISCOVERY COMPLETED message in the Log Messages field. Keep in mind the following: • If DNS records for your Microsoft Exchange Servers are outdated or missing, the discovery of Microsoft Exchange may fail because Microsoft Exchange is dependant on Active Directory, which is dependant on DNS.
PAGE 288
Keep in mind the following: • Discovery Data Collection/Get Details takes some time. You might want to perform this process when the network and the managed elements are not busy. • During Get Details/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. It may also take more time to log into the management server during a topology recalculation.
PAGE 289
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. Refer to the topic, “Adding a Discovery Schedule” in the User Guide for information about automating the gathering of Discovery Data Collection. If you run into problems with discovery, see ”Troubleshooting” on page 305. Discovery from HP SE To obtain details: 1.
PAGE 290
1. Select Options > Protocol Settings > Storage Essentials > Global Application Discovery Settings. 2. To assign a new port, click the Create for the Oracle Information table. 3. Type the new port number and click OK. 4. If necessary, click the button to remove the old port number. 5. Verify all elements have been discovered by clicking the Start Discovery button. See ”Troubleshooting Discovery and Discovery Data Collection/Get Details” on page 317 for more information.
PAGE 291
d. In the Verify Password field, retype the password for verification. 5. Click the OK button. 6. Update the database with element changes. See ”Step 1 - Discover Switches” on page 72. See ”Troubleshooting Discovery and Discovery Data Collection/Get Details” on page 317 for more information. Changing the Password for the Managed Database Account The management server connects to database applications through the use of the APPIQ_USER account, an unprivileged account with read-only privileges.
PAGE 292
least one LUN rendered by each controller of the array. Then, you must make the management server aware of that host, as described in the following steps: 1. Install the CIM Extension on a host that has access to the Engenio storage system. 2. Discover that host. 3. Select Optimize > Storage Essentials > Performance Data Collection. 4. Verify the Data Collection tab is displayed. 5. Click the Start button corresponding with the disk drive statistics for an Engenio storage system. 6. Set the date and time.
PAGE 293
Storage Essentials 5.
PAGE 294
272 Discovering Applications, Backup Servers and Hosts
PAGE 295
16 Managing Security IMPORTANT: Depending on your license, role-based security may not be available. See the “List of Features” to determine if you have access to role-based security. The “List of Features” is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials).
PAGE 296
IMPORTANT: Roles only apply to features and elements in HP Storage Essentials. For example, assume you assigned a user to the Help Desk role in Storage Essentials. That user will have “view only” privileges only in Storage Essentials.
PAGE 297
• Users created in HP Systems Insight Manager are automatically placed in the SIMViewOnly role. This role does not allow users to access any of the features listed in Table 7 on page 274. See ”Adding Users” on page 280 for more information. • Users with access to Global Reporter can view all the elements throughout the enterprise, including those on the server running Global Reporter. Grant access to Global Reporter only to those, who should be allowed to view all elements.
PAGE 298
Table 8 Default Role Privileges with Elements (continued) Role Application Host Switch Storage System Tape Library Others Application Administrator Full Control View View View View View Help Desk View View View View View View SIMViewOnly View View View View View View By selecting one of the following options, users belonging to that role are restricted access: • Full Control - Lets you view and modify the record for the element (Asset Management tab) and perform provisioning if
PAGE 299
Organizations can also contain other organizations. An organization contained within another is called a child. The organization containing a child organization is called a parent. In the following figure, the BostonWebHosts organization contains two child organizations, BostonWebHost_Windows and BostonWebHost_Solaris. BostonWebHosts is a parent because it contains two organizations. Figure 1 Parent-Child Hierarchy for Organizations If a child contains organizations, it is also a parent.
PAGE 300
Figure 2 Children in Multiple Organizations When you remove an element from an organization, users belonging to that organization or to one of its parents can no longer access that element if it is not a member of any other organization. For example, assume an element named MyHost was not only a member of BostonWebHost_Solaris, but also had mistakenly became a member of BostonWebHost_Windows.
PAGE 301
access hosts. The reports you e-mail will not contain information about hosts, including the host specific reports. If the users receiving your reports want to be able to view information about hosts, one of the following must happen: • The hosts in question must be added to your organization. • Someone else, who has the hosts in question already in their organization, must send the reports. Planning Your Hierarchy Before you begin creating organizations, plan your hierarchy.
PAGE 302
• ”Viewing the Properties of an Organization” on page 285 Adding Users To access the management server, users must enter a user name and password. Only users belonging to the Domain Administrator role can add users. Keep in mind the following: • Only users belonging to the Domain Administrator role can add users. • On Windows systems - The user name and password should be alpha-numeric. They cannot exceed 256 characters. The user name cannot begin with a number.
PAGE 303
8. Access Storage Essentials through one of the menu options, such as Options > Storage Essentials > Email Settings. 9. In the upper-right corner, select Security > Users. Only users belonging to the Domain Administrator role can modify users. Notice that the users you created in HP Systems Insight Manager are put in the SIMViewOnly Role. This role does not allow them to access any of the features in Storage Essentials. 10.
PAGE 304
7. To change the e-mail address listed, type a new e-mail address in the E-mail field. 8. To change the phone number listed, type the user's new phone number in the Phone field. 9. Change or remove information from the Notes field if necessary. 10.To change the organizations to which the user belongs, select or deselect the organizations from the table in the user interface. The Everything organization is the default organization that lets users access all current and future elements. 11.Click OK.
PAGE 305
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 3 Changing Your User Profile 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 the Save Changes button. Modifying Your User Preferences Use the User Preference tab to modify your user preferences for System Manager, Element Topology, and Event Manager.
PAGE 306
Table 9 Changing User Preferences for Event Manager (continued) If you want... Do the following... Events refreshed automatically Select the option, Refresh events automatically. Then, enter how often in minutes you want events refreshed. Change the number of events displayed on each page Select the number of events to appear on a page from the Number of Events combo box.
PAGE 307
• Access Level - Determines how much access the user has to a type of element, such as hosts, storage systems, switches, and applications. See ”About the Security for the Management Server” on page 273 for more information. • Access to the - Determines which components in the management server the user can access, where is the name of your product. To learn how to edit a role, see the topic, ”Editing Roles” on page 286.
PAGE 308
To add 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, select Security > Roles. 3. Click the New Role button. 4. In the Role Name field, type a name for the role. For example: Quality Assurance. The name can contain spaces, but it cannot be longer than 256 characters. 5. In the Description field, type a description for the role. For example: Role for those in quality assurance.
PAGE 309
• The Role Name field does not accept special characters, except spaces and the following characters: $, -, ^, ., and _ To edit 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, select Security > Roles. 3. Click the Edit button ( ). 4. To edit the name of the role, change the name In the Role Name field. The name can contain spaces, but it cannot be longer than 256 characters. 5.
PAGE 310
The role is deleted. Managing Organizations This section discusses the following topics: • ”Adding an Organization” on page 288 • ”Viewing Organizations” on page 289 • ”Editing Organizations” on page 289 • ”Deleting an Organization” on page 290 • ”Removing Members from an Organization” on page 291 • ”Filtering Organizations” on page 291 Adding an Organization You can create new organizations to restrict access to certain elements.
PAGE 311
5. In the Description field, type a description for the organization. You cannot type more than 1024 characters in the Description field. 6. Click the Add or Remove Members button to determine which elements the user will see. 7. To add elements, expand the Element Types node in the tree. Select the element type that you would like to add. Then, in the right-hand pane, select the elements you would like to add by clicking the appropriate check boxes.
PAGE 312
You can access information about child organizations by clicking their link under the Child Organization column. Editing Organizations See the topic, ”About the Security for the Management Server” on page 273 for more information about roles and organizations. When elements are removed from an organization, users belonging only to that organization are no longer able to access the removed elements. Keep in mind the following: • Depending on your license, role-based security may not be available.
PAGE 313
Deleting an Organization When an organization is removed, users assigned only to that organization are no longer able to access the elements in the removed organization. For example, assume you belong to two organizations, onlyHosts and onlySwitchesandHosts. The organization onlyHosts contains only hosts, and the organization onlySwitchesandHosts contains only switches and hosts.
PAGE 314
• In the Add or Remove Organization Members window, select the element or child organization you want to remove by clicking the appropriate check box. Next, click the Remove button. • Only users belonging to the Domain Administrator role can remove members from an organization. Only active organizations can be edited. Filtering Organizations The management server provides a filtering feature that lets you designate which organizations are active in your view.
PAGE 315
Changing the Password of System Accounts The management server uses the following accounts to access and manage the database for the management server. You should change the passwords to these accounts to prevent unauthorized access. • SYS - Used for the management server database creation and upgrade. Default password: change_on_install • SYSTEM - Used for management server database creation and upgrade, in addition to database import, export and re-initialization.
PAGE 316
b. Stop the AppStorManager service if it is started. c. Enter the following at the command prompt: C:\> mxpassword -m -x MxDBUserPassword=mynewPass where mynewPass is your new password for the database. d. Stop the HP Systems Insight Manager service so that it cannot access the database. It is very important that the HP Systems Insight Manager service does not access the database before you are finished with changing the password for the database. 2. Stop the AppStorManager service. 3.
PAGE 317
When a user attempts to log into the management server, the management server authenticates the user name and password against AD/LDAP for credential verification. If AD/LDAP verifies this user has the correct credentials, the management server allows this user access to the application. Keep in mind the following: • The login-handler.xml file contains configuration information for Active Directory and LDAP. It is important you enable either Active Directory or LDAP. You cannot enable both.
PAGE 318
• UNIX systems: $MGR_DIST/Data/Configuration NOTE: If you want to go back and forth between internal and external (AD/LDAP) authentication, rename the login-handler.xml file before you modify it. This way you can easily switch back to internal authentication by changing the file name back to login-handler.xml. b. In the login-handler.
PAGE 319
7. If you want the password to be saved in the management server database, change the value of the tags to true, as shown in the following example: true Saving the passwords in the management server database lets a user still log into the management server if the management server is changed back to local mode. This, however, is not recommended as it defeats the purpose of externalizing a user's credentials. The login-handler.
PAGE 320
false false DC=domain extension1,DC=domain extension2,DC=COM displayName mail