IBM System Storage CIM Agent for the DS Open API 5.2 README ---------------------------------------------------------------- Contents 1.0 ABOUT THIS README FILE 1.1 Who should read this readme file 1.2 Where to find more information 1.3 How to get help 2.0 CONTENTS OF THE CIM AGENT PACKAGE 3.0 LAST-MINUTE TECHNICAL UPDATES 4.0 SERVICE LOCATION PROTOCOL INSTALLATION --------------------------------------------------------------- 1.0 ABOUT THIS README FILE This readme file tells you where to obtain information about the IBM System Storage CIM Agent for the DS Open API 5.2 and how to get help. 1.1 Who should read this readme file This readme file is intended for system administrators who are familiar with the system environment and will install and configure the CIM Agent. 1.2 Where to find more information See the "IBM System Storage CIM Agent for the DS Open API 5.2 Installation and Configuration Guide" for complete information about installing and configuring the IBM System Storage CIM Agent for the DS Open API. You can find the guide in the doc directory at the root of the CIM Agent CD. The Adobe Acrobat Reader version 4.0 or later is required to read this document. The Adobe Acrobat Reader can be downloaded from the following Web site: http://www.adobe.com/support/downloads/main.html 1.3 How to get help * Administrative or non-technical support: 1-877-426-6006 (Listen to voice prompts) You can call this number if you have questions about hardware or software orders, hardware maintenance, services contracts of entitlement, invoices, or commercial, state, or local support operations. * Business Partner Support Operations: 1-800-426-9990 * Federal Government Support Operations: 1-800-333-6705 --------------------------------------------------------------- 2.0 CONTENTS OF THE CIM AGENT PACKAGE _uninst - Contains uninstallation program bin - Contains user scripts certificate - Contains SSL certificates and keys config - Contains configuration files java - Contains the Java Runtime Environment lib - Contains various xml, java libraries license - Contains license agreement files log - Contains logs mof - Contains CIM 2.11 + IBM MOF files pegasus - Contains internal Pegasus CIMOM files slp - Contains SLP ssl - Contains SSL startup - Contains startup scripts used by the installer --------------------------------------------------------------- 3.0 LAST-MINUTE TECHNICAL UPDATES * If you are upgrading from 5.2.0.674, you MUST remove all devices using dscimcli rmdev before upgrading, and then add them back after upgrading. We have encoded the device password so that it is no longer easily readable. This means that if you have old configuration files, the CIM Agent will attempt to authenticate to the device with the wrong password, possibly locking out the account. We suggest you do a clean uninstall of all previous versions before installing this one. * When removing devices using dscimcli rmdev, do not make any configuration changes on the device and do not issue additional rmdev commands in parallel. * If you have two DS6000's configured to a single SMC and one is operating successfully and one is not, the one that is failed will not show up in dscimcli. * You will need an xlC library for the CIM Agent to run properly on AIX. See installation documentation for details. * On AIX versions 5300-02 and earlier, there is a defect in the operating system that may prevent the CIM Agent from properly loading the shared libraries. To prevent this, upgrade your operating system to 5300-03 or later. To retrieve the level of your operating system, issue oslevel -r. * The default heap size is set in the provider configuration to be 512 MB. If you are configuring the CIM Agent to manage a large number of objects (greater than 10,000), you may need to increase the heap size. A maximum heap size of 1024 MB is supported. If you need to increase the heap beyond 1024 MB, you may have to adjust the LDR_CNTRL environment variable in config/envConf. This is not an officially supported operation and should only be done if you fully understand how to adjust the LDR_CNTRL environment variable. To adjust the heap size, issue the following command while the CIM Agent is running: dscimcli chconfig -jvmarg "-Xmsm -Xmxm" where is the initial minimum heap size and is the maximum heap size, in MB. The CIM Agent must be restarted for this change to take effect. For more information on memory and heap management in AIX, see http://www-128.ibm.com/developerworks/eserver/articles/aix4java1.html * Note that if you use dscimcli mkdev to add a device and you use the wrong password three times, the account will be blocked. * IBMTSDS_Volume.ExtentStatus currently does not reflect whether or not it is currently mapped to a host (In-Band Access Granted). * There is no error checking when you add ip2 for ESS. In other words, if you're not careful, and the primary and secondary IP's that you add in dscimcli mkdev are from different ESS's, the CIM Agent will accept it and use the primary IP. If the primary IP fails, it will fail over to the secondary IP even though it is on a different ESS or may be invalid. * When you create or delete a FlashCopy (UnSyncAssoc) relationship for ESS, you will receive duplicate events for the creation and deletion of IBMTSDS_StorageSynchronized. NEW FEATURES IN THIS RELEASE: * The CIM Agent now comes preinstalled on the HMC of DS8000 at Release 2.4 of the firmware or later and can be installed on the SMC of the DS6000/ * New functionality to explicitly manage VolumeGroups (see VolumeGroup.mof) * Added new associations IBMTSDS_PrimordialToExtentPool, IBMTSDS_DiskExtentToExtentPool, and IBMTSDS_SHWIDToSPC * Added BulkFormat property to Manifest classes to show what order the statistics will be returned by GetStatisticsCollection * Improved performance in Masking and Mapping ISSUES FIXED SINCE LAST RELEASE: * CIM Agent now registers with SLP with the correct port number even if it is modified by the user. * ExposePaths properly creates StorageHardwareID as a side effect if it did not previously exist. * Fixed performance statistic values * Fixed growing niClient.log * Removed "interop" instance of CIM_Namespace (there is only root/ibm) * Fixed PrimordialStoragePool, ArraySite, and Array capacities to use decimal instead of binary values --------------------------------------------------------------- 4.0 SERVICE LOCATION PROTOCOL INSTALLATION -- AIX -- If a Service Location Protocol AIX service (daemon) was detected on the system at the time of installation of the IBM System Storage CIM Agent for DS Open API, the Service Location Protocol files included with the IBM System Storage CIM Agent for DS Open API will be copied to disk. However, the Service Location Protocol associated with these files will not be installed as a AIX service. In the event you uninstall the product associated with the Service Location Protocol, the Service Location Protocol AIX Service will be uninstalled. You can establish a new Service Location Protocol AIX Service by launching the following commands: 1. cp /startup/dsslpd /etc/rc.dsslpd 2. append the following entry at the end of the /etc/inittab file: dsslpd:/etc/rc.dsslpd>/dev/console2>&1 where is the directory where the IBM System Storage CIM Agent for the DS Open API is installed. -- LINUX -- If a Service Location Protocol Linux service was detected on the system at the time of installation of the IBM System Storage CIM Agent for DS Open API, the Service Location Protocol files included with the IBM System Storage CIM Agent for DS Open API will be copied to disk. However, the Service Location Protocol associated with these files will not be installed as a Linux service. In the event you uninstall the product associated with the Service Location Protocol, the Service Location Protocol Linux Service will be uninstalled. You can establish a new Service Location Protocol Linux Service by launching the following command: 1. cp /startup/dsslpd /etc/init.d/dsslpd 2. /sbin/chkconfig -add dsslpd where is the directory where the IBM System Storage CIM Agent for the DS Open API is installed. -- WINDOWS -- If a Service Location Protocol Windows service was detected on the system at the time of installation of the IBM System Storage CIM Agent for DS Open API, the Service Location Protocol files included with the IBM System Storage CIM Agent for DS Open API will be copied to disk. However, the Service Location Protocol associated with these files will not be installed as a Windows service. In the event you uninstall the product associated with the Service Location Protocol, the Service Location Protocol Windows Service will be uninstalled. You can establish a new Service Location Protocol Windows Service by launching the following command: "\slp\bin\slpd -install" where is the directory where the IBM System Storage CIM Agent for the DS Open API is installed. --------------------------------------------------------------- (c) Copyright 2006 International Business Machines Corp. All rights reserved. Note to U.S. Government Users Restricted Rights--Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.