IBM System Storage SAN Volume Controller Console Readme for Windows 2003 ---------------------------------------------------------------- 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 SAN Volume Controller CONSOLE PACKAGE 3.0 LAST-MINUTE TECHNICAL UPDATES 4.0 PREREQUISITE FOR INSTALLING THE SAN Volume Controller CONSOLE 5.0 FREQUENTLY ASKED QUESTIIONS 6.0 NOTICES 7.0 TRADEMARKS --------------------------------------------------------------- 1.0 ABOUT THIS README FILE This readme file tells you where to obtain information about the IBM(R) System Storage(TM) SAN Volume Controller Console and how to get help. It also lists the contents of the installation package for the Windows(R) 2003 host system. This readme file particularly calls your attention to the prerequisite for installing the SAN Volume Controller Console. It also describes the last-minute technical updates, if any. 1.1 Who should read this readme file This readme file is intended for system administrators who are familiar with the Windows 2003 environment and will install and configure the SAN Volume Controller Console. 1.2 Where to find more information See the section of the "IBM System Storage Virtualization Family SAN Volume Controller Configuration Guide" entitled "Installing the IBM SAN Volume Controller Console for Windows" for complete information about installing and configuring the SAN Volume Controller Console. You can find the guide in the doc directory at the root of the SAN Volume Controller Console installation CD-ROM. 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 nontechnical 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 SAN VOLUME CONTROLLER CONSOLE PACKAGE temp - Temporary use, has synchronization file cimom - Contains the Common Information Model (CIM) executables console - Contains the web server, web pages related executables logs - Contains installation logs _uninst - Contains uninstallation program _jvm - Contains uninstaller Java virtual machine --------------------------------------------------------------- 3.0 LAST-MINUTE TECHNICAL UPDATES The following Defects have been fixed in this version. 32385 - Pegasus handle leak fixes 30823 - GUI performance improvement for vdisk listing 30397 - FCCG DETACH_ALL perf tuning 30283 - fix for synchronous cluster initialization. 30310 - Fix for offline cluster Return Code 30308 - Fix for indication exception issue 30070 - Perf fixes 29574.NF - Detach Pair RC = 5 if pairs don't exist 30250 - return RC=5 when element name is entered 30158 - perf stats delete temp files 1 29461 - uint32 casting of hwlayer return codes caused -#'s values to be returned as huge numbers 29574 - Detach Pair RC = 5 if pairs don't exist 30054 - GUI CS Diagram changes 29302 - TPC-WI 1043, removing additional CIM State checks for Copy Services operations 30014 - RC Perf 29446 - GUI create multiple vdisks with prefix fix 29445 - GUI list hosts with 0 ports fix 29474 - GUI Preferred Node Selection panel fix 29336 - GUI Remove Restore Configuraiton Panel 29744 - GUI Combo Box display for cloned copy Sets 30000 - regression fix 28922 - Deleting Offline Nodes 29882 - perf fix 29526 - missing vdisk fix 29528 - forced deletion of FCMap 29305 - preparing FC in idle status fix 29306 - stop FC in idle status fix 29734 - Fracture RC CG + allowAccess fails for disconnected states --------------------------------------------------------------- 4.0 PREREQUISITE FOR INSTALLING THE SAN VOLUME CONTROLLER CONSOLE You must install the PuTTY open source ssh client software before you install the SAN Volume Controller Console. After you have installed PuTTY, you must run puttygen.exe to generate SSH2 RSA public and private ssh keys. The SAN Volume Controller Console installation program will check for the prerequisite PuTTY installation and will prompt you for the location and name of the private ssh key. See the section of the "IBM System Storage Virtualization Family SAN Volume Controller Configuration Guide" entitled "Installing the IBM SAN Volume Controller Console for Windows" for detailed instructions. You can find this Guide in the doc directory at the root of the SAN Volume Controller Console installation CD-ROM. --------------------------------------------------------------- 5.0 FREQUENTLY ASKED QUESTIONS 1) How do I collect trace logs? In order to collect usable logs, the cimom configuration must be modified to allow for higher logging. This logging will Significantly and adversly effect performance, so do not use these settings for anything but problem determination. A) Configuring Tracing - stop the CIM Agent service by opening the windows service manager and selecting the IBM System Storage SAN Volume Controller Pegasus Server and stopping it. - edit svcconsole/cimom/config/provider.configuration file from the location of your install. the default values are: loglevel = error preferredslpregip = tracecomponents = CIM tracemask = entryexit change the values to the following: loglevel = info preferredslpregip = tracecomponents = all tracemask = all NOTE: do NOT leave trailing blanks after the info or all settings as this will cause failure of the cimom - start the CIM Agent service - execute svcconsole/console/embeddedWAS/profiles/SVCProfile/bin/enableConsoleTrace.bat B) Run Reproduction C) Collect the following log files to send to support: cimom/pegasus/log/* cimom/pegasus/logs/* cimom/log/* console/embeddedWAS/profiles/SVCProfile/logs/server1/* D) Stop the CIM Agent service, reset the provider.configuration to defaults(above), and restart the CIM Agent Service. 2) My CIM Agent service won't start A) Verify that you do not have IBM Director installed on the Master Console. If you need IBM Director, please see FAQ #3, otherwise uninstall Director, and reinstall the CIM Agent. B) Verify that you have a valid certificate. The certificate will be located in svcconsole/cimom/certificate. If there are no files listed in this directory please see FAQ #4. C) Verify the provider.configuration file in the svcconsole\cimom\config directory has no trailing blanks. 3) I have Director installed on my Windows 2003 Server. Can I install a 4.2.1 CIM agent? The 4.2.1 CIM agent currently cannot install on a Windows server when Director is running. Below are instructions for temporarily shutting down Director while the CIM agent is installing. A) Right-click My Computer -> Manage -> Services and Applications -> Services and stop IBM Director WMI CIM Server and IBM Director Agent CIM Listener B) Install the CIM agent. In the step where you set the ports, you must choose something other than 5988 and 5989 (Note the port selected for later use). The CIM agent will allow you to specify 5988 and 5989 because Director is stopped, but if you use those ports, Director will not work when it is restarted. C) Go back to Services and start the Director services that you stopped in step 1 D) Verify Director is still working by going to the Director install directory and running the following command, making sure it gives output that looks similar to the following: C:\Program Files\Common Files\IBM\icc\cimom\bin>CLI ei -n root/ibmsd IBM_DirectorAgent path= IBMPSG_DirectorAgent.IdentifyingNumber="520161208 520000000",Name="IBM Director Core Services", ProductName="IBM Director Core Services",Vendor="IBM",Version="5.20" //Instance of Class IBMPSG_DirectorAgent instance of class IBMPSG_DirectorAgent { uint16 Architecture = 1; string BuildNumber = "V7YT44AUS"; string Caption; string Description; string ElementName; string IdentifyingNumber = "520161208 520000000"; datetime InstallDate; string Name = "IBM Director Core Services"; uint16 OperationalStatus[]; string ProductName = "IBM Director Core Services"; string Status = "OK"; string StatusDescriptions[]; string UniqueSystemID = "7f0e55ea49b40374"; string Vendor = "IBM"; string Version = "5.20"; }; 4) How do I generate an SSL Certificate? Make sure that the CIM Agent Service (IBM System Storage SAN Volume Controller Pegasus Server) is stopped. From a DOS prompt, go to the svcconsole\cimom\config directory and run envConf.bat, followed by "mkcertificate ssl". Then run the following: cimconfig -s sslCertificateFilePath="%SVCAGENT_HOME%\certificate\ssl.cert" -p cimconfig -s sslKeyFilePath="%SVCAGENT_HOME$\certificate\ssl.key" -p This ssl certificate is valid for 365 days by default. Start up the CIM Agent Service. If you still cannot start the cimserver, check the svcconsole\cimom\pegasus\cimserver_planned.conf file and verify that the ssl parameters are EXACT. -------------------------------------------------------------- 6.0 NOTICES & TRADMARKS See notices.txt See non_ibm_license.txt -------------------------------------------------------------- (c) Copyright 2008 International Business Machines Corporation. All rights reserved. Note to U.S. Government Users Restricted Rights--Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.