IBM System Storage SAN Volume Controller Console Readme for Windows 2000 & 2003 ---------------------------------------------------------------- Contents 1.0 ABOUT THIS README FILE 1.1 Who should read this readme file 1.2 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 --------------------------------------------------------------- 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) 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 How to get help See http://www-1.ibm.com/support/docview.wss?rs=591&uid=ssg1S1003141 --------------------------------------------------------------- 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 1) If the install procedure reports a failure to migrate user information on an upgrade from 4.1.1 or earlier releases, the user migration procedure can be completed manually by following these instructions (which are also listed in the "SVC V4.3.x Flashes" section of the IBM Support for SAN Volume Controller (2145) web site: In the steps below - is the location where the SVC Console was installed. The default install location is "C:\Program Files\IBM\svcconsole". 1. Continue with the Install procedure to completion and reboot the Master Console as instructed 2. After rebooting, verify that the IBM SAN Volume Controller Pegasus Server Service is running 3. Verify that \users.mof exists. 4. Open a Windows Command Shell (Start->Run->cmd) Change Directory to the support directory: "cd \support" 5. Run the following command: "migrate ..\users.mof CimomIPPort=XXXX CimomProtocol=YYYY CimomPassword=passw0rd" (Where XXXX is the installed CIMOM port e.g. 5999 and YYYY is the Protocol e.g. http or https) User migration using the migrate commands is only possible if a valid users.mof file exists. 1) Offline, unreachable clusters or clusters with invalid or bad SSH keys cause the CIMOM to perform slower. These situations should be corrected as soon as possible, or the cluster should be removed from the list of clusters to bring performance back to normal. 2) Passwords for users in the GUI are now 6-8 characters long. Longer passwords from older systems are still accepted until changed. 3) Superuser no longer needs the password of a user to modify that users password. 4) Setting the Preferred SLP Registration using svcutil or by modifying the provider.configuration file on an SVC Console requires that the input IP exactly match the system IP. This is particularly important for IPv6, as there are multiple possible formats. The svcutil will return the valid possible ip's if the command fails. 5) IPv6 and IPv4 cluster management - the management console should not be run with the a single cluster added under both IPv4 and IPv6 ip's. By default this is not allow. If the cluster is added while it is unreachable or if the customer performs a forced create for migration purposes this will be allowed 6) When migrating from 4.2.0 and earlier versions, clusters will need to be manually re-added with the SVC GUI after the upgrade. 7) In order to install on Turkish version of Windows, the Launchpad can not be used. setup.exe must be manually executed from the command line with the -G checkPrerequisite=no parameter. 8) Install directory path must only contain alpha numeric characters. 9) When migrating the installer will uninstall the current version. It may be necessary to wait for three minutes after the uninstall to allow the Websphere SOAP port to become free. Shutting down the Websphere application prior to starting the upgrade is a proactive way to eliminate this concern. 10) Internet Explorer 7.0 users will need to add the SVC Console to the trusted sites category of the security profile or warnings will occur. 11) Windows 2000 does not support IPv6. Windows 2003 and Internet Explorer 7.0 are required for IPv6. 12) APARs addressed in this release include: IC58723 --------------------------------------------------------------- 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 adversely effect performance, so do not use these settings for anything but problem determination. When gathering debug logs for a defect report, please use the following steps: 1) Turn up the tracing levels by running the following commands: svcutil setloglevel info svcutil settracecomponents all svcutil settracecategories all 2) Reproduce the error 3) Collect the logs with the following command: svcutil collectlogs This will gather up all of the required trace logs and put them into a ZIP file in the current directory.. Once logs have been collected, please perform the following to reset the tracing to normal levels: 1) turn down the log levels by running the following commands: svcutil setloglevel error svcutil settracecomponents CIM svcutil settracecategories entryexit 2) My CIM Agent service won't start A) 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 below. B) Verify the provider.configuration file in the svcconsole\cimom\config directory has no trailing blanks. 3) 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 in this package -------------------------------------------------------------- (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.