******************************************************************************** HiCommand Release Notes HiCommand Version 1.1 Build 33a - November 14, 2001 Copyright 2001, Hitachi Data Systems All rights reserved. ******************************************************************************** This file contains only known problems and documentation errata. Detailed installation and configuration directions are included in the HiCommand Installation Guide in the /HICMD folder of this CD. To view the included user documentation under Solaris you will need to install the Adobe Acrobat reader located in the /sunrs.install directory of this CD. If the system on which you intend to install HiCommand has an installation of Graph-Track, you may need to run the Graph-Track database migration utility included on this CD. This utility, together with explanatory text, is located in the /Windows/Utilities/Graph-Track folder of this CD. A utility is included with this CD for troubleshooting and verifying SNMP connectivity. This utility, together with explanatory text, is located in the /Windows/Utilities/SNMP folder of this CD. ******************************************************************************** KNOWN PROBLEMS UNDER ALL PLATFORMS 1) The InterBase database server used by HiCommand periodically creates and uses temporary files. InterBase creates these temporary files in a directory specified by the InterBase configuration file or by environment variables. A specified temporary directory must exist and must have sufficient free space. If no alternate temporary directory is specified, a default directory must exist on the server's filesystem and have sufficient free space, or InterBase will not run. See the section titled "INTERBASE TEMPORARY FILES" later in this document for more information. 2) There is a known problem with Host management in this release of the HiCommand Web Client. The problem relates to adding LUN security world wide names (WWNs) to existing hosts through the Config|Hosts menu action. If you add a new WWN to an existing host that is currently being used to secure LUNs, HiCommand will appear to use the new WWN to secure all of the LUNs that are currently secured to the host. However, no change to LUN security will actually be made. The work-around for this release is to add the new WWN to the appropriate storage groups manually. To help in this task, you may wish to run the "Storage Utilization by Host" report, which will display a list of all storage groups that are secured by each host. For each storage group secured by the host being modified, click "Properties", then "Secure". Select the host being modified, click "Next", select the new WWN, click "Finish" and then "Confirm". 3) Although highly unlikely under normal operating practices, if a large number of top-level logical groups (more than 500) are defined in HiCommand, the client application will fail to render the Logical View after logging in. If you encounter this situation, use the HiCommand command-line interface (CLI) to consolidate some storage groups so that there are fewer of them. 4) Physical Configuration reports for 9900-family subsystems report shared memory of -1 Mb. This is erroneous and may be ignored. 5) A problem has been observed on a Windows system running the Web Client whereby the user is unable to select a LUN group to convert to a HiCommand storage group in the Convert LUN Groups dialog when this process has been initiated by performing a "Config Check" in the Storage Subsystem Properties dialog. As of this release, we have been unable to determine if this problem is limited to Windows clients, or the nature of the problem. To work around the problem however, be sure to convert LUN groups when prompted at logon rather than initiating the conversion with a Config Check. ******************************************************************************** KNOWN PROBLEMS UNDER SOLARIS 1) When you insert the HiCommand CD into a Solaris system, the Solaris File Manager runs and displays the directory of the CD. If you execute the install.sh script through File Manager by navigating into the 'solaris' directory and double-clicking the install.sh script, a terminal window will open to execute the script. At the end of the installation when you close this terminal window, the HiCommand daemon will stop running. To restart the daemon execute the command: /hicommand.sh start To avoid this problem altogether, execute the installer from a terminal window (with root permissions) with the following command: /cdrom/cdrom0/solaris/install.sh or, for a text-mode installation, the following command: /cdrom/cdrom0/solaris/install.sh -i console 2) If a Solaris installation fails with the message "InterBase Server was not properly installed. Try re-installing InterBase Server..." and a similar message about InterClient not installing properly, you may be trying to use the graphical installation mode without an adequate windowing environment on your system, or without the executable /usr/dt/bin/dtterm in your path. Use the command-line installation mode instead by invoking the installer from a command prompt. For example, /cdrom/cdrom0/solaris/install.sh -i console 3) To use secure-sockets client/server operations for server implementations on Solaris, follow the directions later in this document (in the section titled "SECURE-SOCKETS IMPLEMENTATION ON SOLARIS") rather than the printed end-user documentation included with HiCommand and on this CD. 4) The directory in which the HiCommand log files are created may be relocated by altering the logger.properties configuration file. If a different directory is specified, please ensure it is owned by the "hicmd" user and belongs to the "hicmd" group. Also ensure that the user and the group both have read, write, and execute permissions, and that the "set group ID on execution" bit is set. For example: mkdir myLogDir chown -R hicmd:hicmd myLogDir chmod ug+rwx, g+s myLogDir 5) There is a minor problem using Netscape 4.76 under Solaris to view the HiCommand online help. The first time you use the search mechanism, you will be presented with an error message. Click the OK button and the search mechanism should work normally thereafter. 6) Under Solaris, a Netscape browser window must be open in order to use the online help system. Without a browser window open, when you click "Help | Index" in the Web Client, nothing will happen. ******************************************************************************** KNOWN PROBLEMS UNDER MICROSOFT WINDOWS 1) Long values for the CLASSPATH environment variable can cause the InterClient installer to post an error message and abort. If this happens, uninstall InterClient, shorten the value of the CLASSPATH environment variable, restart (reboot) the computer, then reinstall. 2) During the InterClient installation, users should choose to configure InterServer when asked to do so. InterServer should be configured as a "Service" that runs at "Windows Startup." 3) The InterClient installer occasionally reports an error on Windows 2000 indicating the service could not be installed due to insufficient access privileges. Disregard this message. In all observed cases of this message, the service is in fact installed correctly. 4) If InterClient is uninstalled, a Windows restart (reboot) is required before reinstalling. 5) The InterBase and HiCommandServer services are not started automatically after installation. Either restart (reboot) Windows, or start the services manually from the Control Panel's Services applet. The proper order in which to start these services is: Interbase Server, InterServer, and finally, HiCommandServer. 6) For client operations on fast Intel platforms: a video driver problem has been identified with respect to the NVidea GeForce 2 GTS video card. The symptom is dialog boxes and other user interface panels being displayed that do not contain any visible text (simply an empty gray dialog). If you encounter this problem, simply move the window or dialog off the screen and then pull it back to the center of the screen to force a repaint of the window to be able to see the message. To work around this problem until NVidea provides an updated driver, perform the following steps: a) Shutdown the HiCommand Web Client b) Open the Display control panel c) Under the Settings tab, click on the Advanced button. d) Under the Troubleshooting tab, move the slider bar all the way to the left, towards NONE. e) Save the new setting f) Restart the HiCommand Web Client. ******************************************************************************** HDS 9200 MANAGEMENT PREREQUISITES Version 1.1 of HiCommand supports management of HDS 9200 storage arrays. However, there are several prerequisites for managing 9200s with HiCommand. These include the following: 1) The 9200 subsystem's Ethernet management interface must be configured to use a static IP address. The DAMP management program allows the array to be configured to use DHCP. This option must not be selected. 2) In order to use HiCommand to configure LUN security settings for 9200s, the 9200 LUN Security feature must be purchased and enabled via the DAMP management program. 3) Using the DAMP management program, the 9200 must be configured to use the "M-TID, M-LUN" target ID mode. 4) If the Password Protection program product is installed on the 9200 and enabled, note the user ID and password; it will be needed for HiCommand to discover and manage the subsystem. 5) The 9200 has a facility for reserving logical unit numbers (LUNs) for internal LUs that are not defined on the 9200. These LUNs may not be assigned to storage on the port where these LUNs have been reserved. If you attempt to allocate storage on a port using one of these reserved LUNs, HiCommand will respond with an error message such as "The LUN 03 is already reserved for the non-existing LDEV 0:14 on port 0A." 6) The minimum microcode level for 9200s you intend to manage with HiCommand is 0558. 7) This build of HiCommand 1.1 supports only 9200 storage systems configured with fiber channel ports. 8) Before attempting to manage 9200 subsystem storage with HiCommand, all RAID groups and LUs must be defined using the DAMP management program. 9) In order for HiCommand to work properly, the DAMP management program must not be connected to the 9200 under management. 10) HiCommand Server does not support the use of NAT (Network Address Translation) between the HiCommand Server and 9200 storage subsystems. The reason is that after HiCommand does it's initial discovery of the 9200 using the IP Address provided by the user, it then switches to using the IP Address reported by the 9200 controllers which will not be accessible by HiCommand. The result is that the discovery will fail. ******************************************************************************** SECURE-SOCKETS IMPLEMENTATION ON SOLARIS For secure-socket client operations with a HiCommand Server (through build 30) running on a Solaris platform, perform the following steps: 1) On the server, login as root or open a terminal window and issue the 'su' command to assume root privileges. 2) Change your working directory to the /HiCommandServer directory (e.g. "cd /opt/HiCommand/HiCommandServer"). 3) Execute the HiKeytool.sh shell script to generate a certificate. Select option 1 ("Make KeyPair/Self-Signed Certificate"). During the information gathering phase of the HiKeytool script, if you change the default values for the "Key Password" or the "Key Store Password", you must immediately update the server.properties file after the HiKeytool.sh shell script has completed execution. (See sections 5.2.2 and 5.2.3 in the HiCommand Server Installation and Configuration Guide for more details.) 4) Change your working directory into the "config" subdirectory. (e.g. "cd config"). 5) Edit the server.properties file to: a. change the server.http.secure property to 2 b. change the server.http.chroot property to false 6) Save the file and exit your editor. 7) Using the hicommand.sh script, stop the server (e.g. "/etc/init.d/hicommand.sh stop"). 8) Using the hicommand.sh script, restart the server (e.g. "/etc/init.d/hicommand.sh start"). 9) Use the hicommand.sh script once more to verify that the server is operating in secure mode (e.g. "/etc/init.d/hicommand.sh status"). (The "Security level" line should read "TLS/SSL Secure Socket".) After performing these steps, go to the client system and perform these steps: 1) Launch the web browser (IE 5.5 or later, or Netscape 4.76 or later) and point it at the HiCommand Server (e.g. "http://hcserver:2001"). 2) If you have not previously installed the Java Web Start client deployment application on the client, follow the link labeled "HiCommand Client Installation" and follow the directions to install the client. If you have previously installed Java Web Start on the client, proceed to step 3. 3) On the HiCommand Server home page, click the link labeled "Open the HiCommand Client". Java Web Start will download the HiCommand Web Client and execute it. 4) Log in to the Web Client as the "system" user (the default password is "manager"). 5) After you log in, the HiCommand Web Client should display a dialog indicating that it needs to download one or more files for secure operation. Click OK to download the files. After downloading these files, the client will display a message that the client must be restarted. When you click OK the client will exit. 6) Launch the Web Client again by clicking on the "Open the HiCommand Client" link on the HiCommand home page. 7) Log in to the Web Client again. At this point, note the URL displayed in the client's title bar. It should show that the client is connected securely (i.e. using the "https" protocol as opposed to the "http" protocol). ******************************************************************************** INTERBASE TEMPORARY FILES The InterBase database server periodically creates and uses temporary files. These files are located in the directory specified by either the InterBase configuration file, or by environment variables defined on the server. There are three ways to specify that InterBase should use directories other than the default hard-coded directories. These are: 1) The InterBase configuration file: this file is in the InterBase directory. On Windows systems, the file is named "ibconfig". On Solaris systems, it is named "isc_config". Create an entry in this file in the format: TMP_DIRECTORY size "pathname" 2) Create the environment variable "INTERBASE_TMP" which points to the directory you would like InterBase to use for temporary files. 3) If no entry is found in the configuration file, and no INTERBASE_TMP environment variable exists, InterBase will use the directory pointed to by the system's TMP environment variable. If no entry is found in the configuration file, no INTERBASE_TMP environment variable is defined, and no TMP environment variable is defined, InterBase will use hard-coded directories. These directories are: Windows 2000 C:\WINNT\TEMP Windows NT4 C:\TEMP Solaris /tmp If no other directory is specified by using the methods outlined above, InterBase will attempt to use one of these directories - the appropriate one for the operating system. If this directory does not exist, InterBase will not run. Note also that the directory which InterBase uses for it's temporary files must have sufficient space for creating temporary files - at least 10 to 20 MB available. ********************************************************************************