Last Modified June 9, 1998 Welcome to StorageWorks Command Console (SWCC). Thank you for purchasing our products. This document covers Version 2.0A of SWCC. It summarizes features and operational information not covered elsewhere in the product documentation. For installation information, please see "DIGITAL StorageWorks Command Console Getting Started". This README.TXT file is divided into nine main sections: 1. INSTALLATION NOTES A. Before Installing the RA200 Agent on OpenVMS B. Before Installing SWCC 2.0 Agents on DIGITAL UNIX C. Client Installation claims System Files are out-of-Date, Even After Installing New Files D. Installation over a Running Version of SWCC Agent (Windows NT) Files are Read Only or Error -37 E. Stand-Alone Installations F. SWCC 1.1B Client will not work if Version 2.0 Client was Already Installed G. Unzipping the Web Installation Kits 2. UNINSTALL NOTES A. Configuration File Deleted on Re-installation or Upgrade B. SWCC Agent Uninstall does not Remove Program Group or Icons (Windows NT 3.51) C. SWCC Client Uninstall does not remove AsyncEventService Entries D. SWCC HS* Agent has two Uninstall Methods (Windows NT 4.0) 3. ADOBE ACROBAT READER 4. HSZ CONTROLLERS A. Clarifications 1. False Restart Message on Agent Installation 2. Reduced Striped Mirrorset Shown as Reconstructing 3. Storage Window Corruption While Deleting a Virtual Disk B. Operating Constraints 1. Code Load not Supported 2. Controllers not Visible in Multiple-Bus Failover Mode C. Avoiding Problem Situations 1. Application Errors When Restarting Agent 2. Cache Policy not shown in Controller Properties Sheet 3. Character Limit on Maximum Cached Transfer Quantity Entry 4. Communication Failure on Power Up with Low Batteries 5. Error Message on Exiting Storage Window 6. Error on First Attempt to Make a Connection 7. Exiting from the HSZ Storage Window in Windows 95 8. HSZ Agent Upgrade SWCC 1.1b to SWCC 2.0 (OpenVMS Only) 9. Inappropriate Error Messages on Device Delete 10. Incorrect Capacity Shown in Add Virtual Disk Wizard 11. No Agent Notification Causes Invalid or Missing Fault Displays 12. Operating Parameters of Partition Virtual Disks 13. Storage Window Corruption After Making and Removing Space Device 5. HS* AGENT INTERACTION 6. RA200 CONTROLLER, BEFORE RUNNING THE RA200 AGENT A. Enable StorageWorks Fault Management B. Firmware Update 1. RA200 Firmware Loader (Version 3.10A) Release Notes for 8x00 Machines 2. Upgrading Controllers in an Alpha System 3. Upgrading Controllers in an Intel System 4. Specifying Command-Line Parameters 7. CLIENTS A. Known Problems 1. Authorization Error When Adding the Server to the SWCC Navigation Tree 2. OpenVMS Agent will not Start After New Install Under Multinet (HSD, HSJ, and HSZ Agents) 3. Windows 95 SWCC Installation Problem 8. TROUBLESHOOTING CONNECTION AND ACCESS PROBLEMS A. Dynamic IP Address Allocation, such as DHCP, not Supported B. WINS not Supported C. Access Denied Problem 1. Check Client Lists 2. Multiple Agents 3. HSZ Agent and Mixed or Upper-case Node Names 4. Aliases not Checked 5. Rule of Thumb and Testing D. RA200 Agent in Navigation Tree But It Cannot Connect E. Add New System Using IP Address Crashes F. "No Agent Running" Errors G. OpenVMS, Multinet, and getservbyname Failures 9. GLOSSARY A. Applet Manager B. Applet 1. INSTALLATION NOTES ---------------------------- Install SWCC 2.0 Client Software before installing a controller Client, such as HSG80. A. Before Installing the RA200 Agent on OpenVMS ---------------------------- The RA200 Agent requires the SYS$DRDRIVER driver. Before installing the RA200 Agent, install the SYS$DRDRIVER driver from the following TIMA kits: ALPDRIV09_071 for V7.1-1H1 ALPDRIV18_062 for V6.2-1H3 To obtain the TIMA kits, go to the following Web site: http://www.service.digital.com The file, SYS$DRDRIVER.EXE, is the OpenVMS Alpha device driver for the KZESC, KZPSC, and KZPAC backplane RAID controllers. This driver is required for the support of StorageWorks Command Console. The driver will create a new device unit, DRMc0:, for each controller. This unit serves as a communication point for the SWCC agent to allow it to perform its configuration and monitoring functions. Refer questions to your DIGITAL Customer Service Representative. B. Before Installing SWCC 2.0 Agents on DIGITAL UNIX ---------------------------- SWCC 2.0 will malfunction if a SWCC 1.x DIGITAL UNIX Agent was uninstalled after a SWCC 2.0 DIGITAL UNIX Agent had been installed. The 1.x uninstall removed the entries from the system SERVICES file that the 2.0 Agent needed to run. Either uninstall your 1.x Agents before installing a 2.0 Agent or run the script fix_service.sh from the directory where your 2.0 Agent was installed. SWCC will not work even if the 2.0 Agent is for a different controller than the 1.x Agent that you are uninstalling. For example, a RA200 DIGITAL UNIX Agent will no longer work if you uninstall a 1.x HSZ Agent. If you uninstall your 1.x Agent before you install your 2.0 Agent, you may lose all of your 1.x configuration data. Please see "Upgrading a SWCC 1.x DIGITAL UNIX Agent to SWCC 2.0" in Section D of this file. To safely upgrade, save your client.ini, storage.ini, and notify.ini files to another directory that will not be deleted. To reuse these files after completing the 2.0 Agent installation, copy the client.ini and notify.ini files to the new directory (/usr/opt/SWCC200/etc). Create a storage.ini file with the convert script. The convert script is located in the following directory: /usr/opt/SWCC200/scripts The SWCC 2.0 DIGITAL UNIX Agent install will attempt to retain configuration data from a SWCC 1.x Agent. The configuration data may not be retained in all cases because the 1.x Agents have different install mechanisms. C. Client Installation claims System Files are out-of-Date, Even After Installing New Files ---------------------------- SWCC 2.0 Client software requires at least version 2.20.0.0 of Microsoft's OLEAUT32.DLL file. If the version installed is older than 2.20.0.0, the SWCC installation will show a dialog box with the following information: * Systems files are out-of-date. * It will install new system files. * To rerun the installation after the system reboots. With some versions of OLEAUT32.DLL, the version check will fail and InstallSHIELD will not overwrite with the newer file. This action will cause the install to always say that the system files need to be updated and to never allow you to install SWCC. To fix this, ensure that a proper version of OLEAUT32.DLL was installed by installing a clean version of the operating system. D. Installation over a Running Version of SWCC Agent (Windows NT) Files are Read Only or Error -37 ---------------------------- The SWCC Windows NT Agent runs as a service. Attempting to install the Agent, while a version is running, will fail. Before installing, stop the existing Agent(s). If the Agent is running, InstallSHIELD will do the following: * Complain about read only files * Not copy the files in the kit over the existing files * Stop with an error -37 To stop the Agents, go into Control Panel | Services, select the appropriate Agent, and click the Stop button. The service for the HS* Agent is steam. If the install has failed with an error -37, it will not be possible to uninstall the Agent. First stop the Agent, and then install again. E. Stand-Alone Installations ---------------------------- After doing a stand-alone install of the HSZ or RA200 Client, restart Command Console (if you have it running) before adding or accessing a system with that type of controller. Command Console will then recognize the installation. F. SWCC 1.1B Client will not work if Version 2.0 Client was Already Installed ---------------------------- SWCC 1.1b will malfunction if you already have SWCC 2.0 on a Windows NT operating system. The Asynchronous Event Service that comes with SWCC 2.0 uses the same port as SWCC 1.1b. SWCC 1.1b can be removed without impacting SWCC or ServerWorks 3.3. Perform the following to solve this: 1. Uninstall SWCC 1.1b. Ignore the error box that appears. 2. Reboot the computer. The integration for SWCC 1.1b will have been removed. 3. Integrate SWCC 2.0 with ServerWorks 3.3 by referencing "Getting Started". G. Unzipping the Web Installation Kits ---------------------------- The Web installation kits are provided as zip files. To unzip them you will need an unzip utility that supports long file names and directory structures. These kits must be unzipped on the operating system that they are targeted for. For instance, unzip SWCC20DUNIX.ZIP on a DIGITAL UNIX system. The following versions of unzip have been used to successfully expand the kits: DIGITAL UNIX Info-ZIP unzip 5.32 DIGITAL OpenVMS Info-ZIP unzip 5.32 (Alpha and VAX) Microsoft Windows NT Info-ZIP unzip 5.32 (Alpha and Intel) Winzip 6.3 (Intel native, Alpha via emulation) Microsoft Windows 95 Info-ZIP unzip 5.32 Winzip 6.3 Always indicate that the unzip utility should retain the directory structure (default for Info-ZIP unzip). To obtain Info-ZIP unzip for any platform, go to the following Web site: http://www.cdrom.com/pub/infozip 2. UNINSTALL NOTES ---------------------------- A. Configuration File Deleted on Re-installation or Upgrade ---------------------------- Save a copy of the current swcc2.mdb file to another directory if you intend to re-install or upgrade Client. If you uninstall the program, you will delete the swcc2.mdb file. This file contains your configuration of host systems and storage subsystems used in the Navigation Tree window display. To reinstate your current Navigation Tree window configuration after installing a new version of SWCC, copy your saved swcc2.mdb file back to the directory where you installed SWCC. B. SWCC Agent Uninstall does not remove Program Group or Icons (Windows NT 3.51) ---------------------------- The SWCC Agent uninstall programs do not remove the program group or icons after uninstalling from a Windows NT 3.51 system. After the uninstall is complete, the icons may be removed manually. C. SWCC Client Uninstall does not Remove AsyncEventService Entries ---------------------------- Before uninstalling StorageWorks Command Console (but not individual controller Clients), first remove the AsyncEventService entries. Under Windows 95, go into Control Panel | Async Event Service and uncheck "Automatic startup on boot". Under Windows NT, change to the directory where SWCC was installed and run the following command: AsyncEventService -remove Then uninstall the SWCC Client. Failing to remove the service will cause the system to report that a service failed to start every time the system is booted. D. SWCC HS* Agent has two Uninstall Methods (Windows NT 4.0) ---------------------------- Under Windows NT 4.0, the HS* Agent adds an uninstall icon to the HSZ Agent entry in the Start Menu. There is also an entry under Control Panel | Add/Remove Programs. Do not use Control Panel | Add/Remove Programs to uninstall the HS* Agent. Use the entry HSZ NT Agent | Uninstall HSZ NT Agent under the Start | Programs menu. Using Control Panel to remove the HSZ Agent will leave the Agent registered as a service. 3. ADOBE ACROBAT READER ---------------------------- The following is a list of the files included on the SWCC web site and the SWCC 2.0 disk. These files contain "Getting Started" in .PDF format, which is viewed with Adobe Acrobat Reader. DIGITAL UNIX acroread.osf.301.tar.gz (tar image) Hewlett-Packard UNIX acroread.hpux.301.tar.gz (tar image) IBM AIX acroread.aix.301.tar.gz (tar image) SGI acroread.irix.301.tar.gz (tar image) SUN OS acroread.sunos.301.tar.gz (tar image) Windows NT Alpha acread20.exe (a self extracting file) Windows NT Intel ar32e301.exe (a self extracting file) 4. HSZ CONTROLLERS ---------------------------- A. Clarifications ---------------------------- 1. False Restart Message on Agent Installation (HSZ Controllers) ---------------------------- The installation program may prompt you with a message indicating Agent must be "restarted", even though it has not been completely installed. This message may appear if you had installed a Windows NT Agent and then modified more than one configuration parameter. Ignore this message. Respond to the subsequent prompt, "Would you like to start Agent service now?", by answering "Yes". 2. Reduced Striped Mirrorset Shown as Reconstructing (HSZ Controllers) ---------------------------- A reduced striped mirrorset may be shown as GOOD in the virtual disk properties sheets. Ignore the "GOOD" statement in the disk properties sheet. The correct icon is displayed. 3. Storage Window Corruption While Deleting a Virtual Disk (HSZ Controllers) ---------------------------- If you confirm the deletion of a RAID-based (Redundant Array of Independent Disks) virtual disk, the program may display a "Subsystem Connection Status" window. This window may be blank for several seconds until the "Subsystem Connection Status" window disappears. B. Operating Constraints ---------------------------- 1. Code Load Not Supported (HSZ Controllers) ---------------------------- Version 2.0 does not support the controller software upgrade function. Do not use the menu for upgrading your controller's software. 2. Controllers Not Visible in Multiple Bus Failover Mode (HSZ Controllers) ---------------------------- The controller icons are not displayed in the Storage Window if you set your controllers to the multiple bus failover mode using the Command Line Interface (CLI) window and utilizing Command Console to view your subsystem. You also cannot view or modify the controller properties sheets in multiple bus failover mode. Client does not support the HSZ70 controller multiple bus failover mode. C. Avoiding Problem Situations ---------------------------- 1. Application Errors When Restarting Agent (HSZ Controllers) ---------------------------- An "application error" error may occur when attempting to restart Agent after changing its configuration files. The following may be the cause: * The client.ini file must end with a carriage return. If another character terminates the file, it may cause an application error. * The storage.ini file must not end with a carriage return. If a carriage return terminates the file, it may cause an application error. 2. Cache Policy Not Shown in Controller Properties Sheet (HSZ Controllers) ---------------------------- The controller cache policy might not be properly shown in the controller properties sheet or the field may be blank. Use a CLI Window to obtain the cache policy setting. 3. Character Limit on Maximum Cached Transfer Quantity Entry (HSZ Controllers) ---------------------------- Client may terminate with an error if more than four characters are in the maximum cached transfer entry field in the Advanced Options dialogue box, which was accessed when creating virtual disks. The range of acceptable entries is 1-1024. 4. Communications Failure on Power Up with Low Batteries (HSZ Controllers) ---------------------------- The controller may produce an invalid cache error if the battery in your cache is discharged when you power on the controller. The error may prevent communication with the controller if you use Client as your controller interface. In this case, the controller status bar in Client changes to yellow, and the program displays a window containing error information. Confirm that Client has the proper communication parameters. If Client is configured properly for your controller, you must exit Client and clear the error with the "CLEAR ERRORS INVALID_CACHE" command from a normal controller maintenance terminal before you can use the controller. See your controller documentation for instructions on use of the "CLEAR ERRORS INVALID_CACHE" command. After you have cleared the invalid cache error, you can use either a normal maintenance terminal or Client as your controller interface. You can obtain current status by viewing the subsystem in question. 5. Error Message on Exiting Storage Window (HSZ Controllers) ---------------------------- When you exit a Storage Window, you may see an "Illegal Operation Error" message. Ignore this message. 6. Error on First Attempt to Make a Connection (HSZ Controllers) ---------------------------- A system error, such as a "Command Execution Error", may occur on your first attempt to make a network connection using the Storage Window. If this happens, try the connection again. 7. Exiting from the HSZ Storage Window in Windows 95 (HSZ Controllers) ---------------------------- You will encounter a general protection fault if you click "File", and then click "Exit and Return" in the HSZ storage window. When the error window appears, click the Details button. The program will display the following message: "HSZ window caused a general protection fault in module user.exe." To avoid this error, click the closure button in the upper-right corner of the open window. 8. HSZ Agent Upgrade SWCC 1.1b to SWCC 2.0 (OpenVMS Only) (HSZ Controllers) ---------------------------- Before you install SWCC 2.0 for the HSZ Agent, you must uninstall SWCC 1.1b and delete CHANGE_REGISTER.COM from the SYS$SYSDEVICE:[SWCC$AGENT] directory. SWCC 1.1b is incompatible with SWCC 2.0. Furthermore, if you interrupt the installation of SWCC 2.0, neither SWCC 2.0 nor SWCC 1.1b will work. 9. Inappropriate Error Message on Device Delete (HSZ Controllers) ---------------------------- If you select a disk and then chose Device/Delete, the program may display a dialog box, asking "Are you sure?" If you choose the "NO" option, the dialog box displays "Nothing selected to delete!" Ignore this message. 10. Incorrect Capacity Shown in Add Virtual Disk Wizard (HSZ Controllers) ---------------------------- An error message may appear if you specify a capacity greater than the available disk capacity in step 3 of the Add Virtual Disk Wizard. The correct capacity will be displayed if you return to step 2 and then to step 3 of the Wizard. You will see the same error message when you return to step 4, even though the correct capacity is shown. To complete your virtual disk, exit the Wizard and attempt to recreate the virtual disk. 11. No Agent Notification Causes Invalid or Missing Fault Displays (HSZ Controllers) ---------------------------- For some faults, Agent does not send Client immediate notification of status changes. Client usually displays fault information it has last received; however, it may not display the most current status during the following three situations: * The OTHER controller fails or is shut down. * A cache battery on either controller fails or goes low. * A cache module fails. Click the View Subsystems button for the current status of a subsystem. 12. Operating Parameters of Partition Virtual Disks (HSZ Controllers) ---------------------------- Partition virtual disks on a container are closely related. They share the same target and operating parameters of the container. If you change the information for one partition on the container, you change it for all the partitions on that container. 13. Storage Window Corruption After Making and Removing Spare Device (HSZ Controllers) ---------------------------- Some information in the Storage Window may become corrupt if you select a disk, make it a spare, and remove the device as a spare (using either menu or context menu options). To reconstruct the window, exit the window and open a new one. 5. HS* AGENT INTERACTION ---------------------------- When you install a HSZ20/40/50/70 on the same system as a HSZ22, the SWCC Agent installation for the HS* controllers mistakes the HSZ22 for a HSZ20. The installation procedure then adds an entry into the configuration file for a HSZ20. There are two ways to handle this situation: * Avoid the problem - Power down the HSZ22 subsystem during the HS* Agent installation. After the installation, power on the HSZ22 subsystem and reboot the system. * Repair the problem - During the installation of the HSZ* Agent, delete the erroneous entry. The installation procedure runs the Agent configuration utility. The second screen of the configuration utility lists the subsystems found during the installation. The HSZ22 entry can be identified by the drive used to access the subsystem, serial number, or firmware version. Use the Delete button to remove the entry. 6. RA200 CONTROLLER, BEFORE RUNNING THE RA200 AGENT ---------------------------- A. Enable StorageWorks Fault Management ---------------------------- Before running the RA200 Agent, verify that StorageWorks Fault Management is enabled for each KZPAC and KZPSC controller that you want to manage with SWCC. You must enable StorageWorks Fault Management by using the standalone RAID Configuration Utility (RCU) so StorageWorks Command Console can support this controller. To enable StorageWorks Fault Management, perform the following: 1. Run the RAID Configuration Utility (RCU). 2. From the "Main Menu" of the RCU, highlight the "Controller Setup" option by using the arrow keys. Then press Enter. The "Edit/View Parameters" menu appears. 3. If necessary, use the arrow keys to highlight "Hardware Parameters". Then press Enter. The "Hardware Parameters" screen appears. 4. Use the arrow keys to highlight "StorageWorks Fault Management". If this parameter is displayed as "Disabled", press Enter to change the setting to "Enabled". 5. Press Esc to return to the "Edit/View Parameters" screen. Press Esc again. If you made no parameter changes, the "Main Menu" appears. 6. If you changed a controller setting, the RCU will prompt you to save the altered controller configuration. Use the arrow keys to highlight "Yes", then press Enter. The "Main Menu" appears. For the complete instructions on using the RCU, please refer to the manual, "RAID Array 230/Plus Subsystem RAID Configuration Utility - User's Guide", part number AA-R07GA-TE. B. Firmware Update ---------------------------- Before running the RA200 Agent, you must first upgrade your RA200 controller firmware to Version 2.49. The firmware is available on the SWCC Web page or from the SWCC CD-ROM. Download the upgrade from the following Web page: http://www.service.digital.com/sms/swcc The SWCC 2.0 distribution contains firmware v2.49 for the RA 230/230+. The Web firmware distribution consists of two zip files (fw249axp.zip or fw249x86.zip). On the CD-ROM, the unzipped files are in the directories \kzpxc\fw\alpha and \kzpxc\fw\intel. The firmware update program must be run from an MS-DOS bootable floppy for an Intel system. For an Alpha system, the ARC (or AlphaBIOS) console must be used with either an MS-DOS formatted floppy or the SWCC CD-ROM (only supported on some Alpha consoles). The SWCC CD-ROM and Web page contain the following directories and files: \KZPXC\Intel readme.txt Ra200fl.exe Firmware download program for Intel Ra200rcu.exe RCU program for Intel SWXCRFWP.249 Revision 249 firmware for RA 230/230+ \KZPXC\Alpha readme.txt Ra200fl.exe Firmware download program for Alpha Ra200rcu.exe RCU program for Alpha Ra200srl.exe Serial RCU for Alpha Swxcrfwp.249 Revision 249 firmware for RA 230/230+ NOTE: If you mount the above directories from the SWCC CD-ROM onto an OpenVMS system, the directories will appear to be empty. This occurs because the OpenVMS system cannot read the directories. However, these files are not intended to be used except from the system console. NOTE: For complete installation instructions, please refer to the manual, "RAID Array 230/Plus Subsystem RAID Configuration Utility - User's Guide", part number AA-R07GA-TE Appendix A. Please read the following section, "RA200 Firmware Loader (Version 3.10A) Release Notes for 8x00 Machines". 1. RA200 Firmware Loader (Version 3.10A) Release Notes for 8x00 Machines ---------------------------- Please read the introductory paragraphs in "Firmware Update". Version 3.10A of the RA200fl utility is the only version that should be used on the 8x00 machines. If your 8x00 machine is capable of executing the AlphaBIOS console (Windows NT based systems), then version 3.10A of the RA200fl utility can be executed from a CD-ROM or a floppy. If your 8x00 machine has a SRM console (DIGITAL UNIX and OpenVMS based systems), then version 3.10A of the RA200fl utility can only be executed from a floppy. The following is the procedure for running RA200fl from a floppy on SRM console based 8x00 systems: 1. Type the following at the SRM console to enable the ARC emulation code: set arc_enable on Press ENTER. 2. Type the following at the SRM console to re-initialize the system: init Press ENTER. The system re-initializes. 3. Type the following at the SRM console: Set mode advanced Press ENTER. 4. Type the following at the SRM console to obtain the name of the floppy: sho dev floppy Press ENTER. Assume the command returns the floppy's name as dva0. 5. Type the following command at the SRM console (replace dva0 with the name that you obtained in step 4): run fat:ra200fl.exe -d dva0 -p 0 -s "swxcrfwp.249" 6. Press ENTER. The computer loads new firmware on the first RA200 in Hose 0. 7. Type the following command on one line at the SRM console (replace dva0 with the name that you obtained in step 4). It has been split onto two lines for documentation purposes. run fat:ra200fl.exe -d dva0 -p 1 -s "swxcrfwp.249 swxcrfwp.249 swxcrfwp.249" 8. Press ENTER. The computer loads new firmware on the first three RA200 controllers in Hose 1. You must run the "fat:ra200fl" command for each hose that has RA200 controllers installed to update the firmware. Change the number following the -p to specify the different hoses. The -v option is not available when running from the SRM console at this time. This may be supported at a latter date. If you do not have a floppy drive and you have a SRM console based 8x00 system, you will have to remove your RA200 controller from your 8x00 system, move it to a different system, and upgrade the firmware there. Please read the following sections: "Upgrading Controllers in an Alpha system" and "Upgrading Controllers in an Intel system". 2. Upgrading Controllers in an Alpha system ---------------------------- Please read the introductory paragraphs in "Firmware Update" before performing the following steps: 1. On some systems you will be able to upgrade the RA230 or RA230/Plus firmware from the SWCC CD-ROM. Start the ARC (or AlphaBIOS) console on your system. Refer to your system documentation for this procedure. At the ARC menu select "run program" (run maintenance utility on AlphaBIOS). At the "program to run" prompt enter: cdrom:\kzpxc\fw\alpha\ra200fl You may need to replace "cdrom" with the actual path to the CD-ROM device, for example "scsi(0)cdrom(4)fdisk(0)". If you do not have the SWCC CD-ROM or if you are using a system that does not understand the above command, you will need to create a floppy with the firmware upgrade utility and firmware image. 2. Obtain an MS-DOS formatted floppy. If you have the SWCC CD-ROM, copy the files from \kzpxc\fw\alpha onto the floppy. If you obtained SWCC from the web, unzip the file onto the floppy. Please see the documentation for your unzip utility for how to specify an output disk and directory. You should unzip the files into the top level of the floppy, for example "a:". 3. Start the ARC (or AlphaBIOS) console on your system. Refer to your system documentation for this procedure. At the ARC menu, select "run program" (run maintenance utility on AlphaBIOS). At the "program to run" prompt, enter the following: a:\ra200fl For information on how to run the RA200fl, please see "RAID Array 230/Plus Subsystem RAID Configuration Utility - User's Guide" part number AA-R07GA-TE Appendix A. Instructions for running the RA200 are also included on the SWCC CD-ROM. 4. Please follow the steps listed in the next section, "Specifying Command-Line Parameters". 3. Upgrading Controllers in an Intel system ---------------------------- Please read the introductory paragraphs in "Firmware Update" before performing the following steps: 1. You will need an MS-DOS bootable floppy to upgrade the controllers. The easiest way to create this is to make a disk copy of the RAID Array 230/Plus RAID Configuration Utility for an Intel floppy diskette. This diskette should have accompanied your controller. If you cannot locate this floppy, you can create a bootable diskette on an MS-DOS or Windows 95 system using the "format/s" command. Please refer to your MS-DOS or Windows 95 documentation for creating a bootable floppy. If you have the SWCC CD-ROM, perform the following: a. Copy the files from \kzpxc\fw\intel to the bootable floppy that you have created. If you obtained SWCC from the web, unzip the file onto the bootable floppy. b. Select YES when asked if you wish to replace the existing files. c. Please see the documentation for your unzip utility for specifying an output disk and directory. d. Unzip the files into the top level of the floppy, for example "a:\". 2. Boot your system from the floppy you have created. If you have created the floppy by copying your RAID Array 230/Plus RAID Configuration Utility floppy, then follow the instructions in the "RAID Array 230/Plus Subsystem RAID Configuration Utility - User's Guide" part number AA-R07GA-TE, Appendix A. If you created a bootable floppy, you will not be given the option of reading the readme file when the system boots. Follow the instructions in the "RAID Array 230/Plus Subsystem RAID Configuration Utility - User's Guide" as if you answered no to the prompt, asking if you wish to see the readme file. Instructions for running the firmware update program are also on the SWCC CD-ROM. 3. Please follow the steps listed in "Specifying Command-Line Parameters". 4. Specifying Command-Line Parameters ---------------------------- Please read the introductory paragraphs of "Firmware Update". To upgrade the firmware, you must first shut down the operating system. There are two ways to specify command-line parameters for the firmware download utility: * An explicit name for the downloaded image for each controller in the system, up to four controllers * The -v option when the same image was used for each controller in the system With different RA200 controllers, specify the firmware for each. At the console, run the RA200FL.EXE program, contained on the CD-ROM. Type at the prompt, RA200FL.EXE xxxx yyyy zzzz aaaa where xxxx yyyy zzzz aaaa are firmware image names, for example, SWXCRFWP.249. Dummy parameters can be specified if you do not wish to load the firmware for a specific controller. Leaving yyyy in the command above would cause the second controller's firmware to stay the same. As an option, you can type, RA200FL.EXE -v xxxx where xxxx is the revision of the firmware, for example, 249. This will use the same firmware image for each controller in the system. To run the RAID Configuration Utility (RCU), please refer to the manual, "RAID Array 230/Plus Subsystem RAID Configuration Utility - User's Guide", part number AA-R07GA-TE, Chapter 1. Contact your DIGITAL sales representative for additional copies of the manual. 7. CLIENTS ---------------------------- A. Known Problems ---------------------------- 1. Authorization Error When Adding the Server to the SWCC Navigation Tree ---------------------------- SWCC 2.0 includes support for different SWCC Agents. Each Agent supports a different subset of DIGITAL StorageWorks' storage subsystems. Each Agent maintains its list of authorized Client nodes. If you have more than one type of subsystem installed or attached to a server, you must keep the list of authorized Clients in sync so that every Client listed in an Agent's Client list is also listed in every other Agent's Client list with at least "Overview Status" access rights. If a Client is missing from one of the Agent's authorized Client list, that Client will receive an authorization error when attempting to add the server to the SWCC Navigation Tree. 2. OpenVMS Agent will not Start After New Install Under Multinet (HSJ, HSD, and HSZ Agents) ---------------------------- On an OpenVMS cluster running the Multinet TCP/IP stack, the command procedure SWCC_CONFIG.COM will only update the services database of each system disk's first node. Before trying to start the Agent, enter the following command to update the services database of the other nodes that share the system disk: $ @MULTINET:INSTALL_DATABASES Rebooting the system will also achieve the same result. 3. Windows 95 SWCC Installation Problem ---------------------------- When you run SWCC on Windows 95, the operating system will gradually increase its use of memory, especially when SWCC opens and closes a large number of sockets. Microsoft has released an updated version of kernel32.dll that corrects this situation. This file is available from the following web site: http://www.microsoft.com/windows95/info/krnlupd.htm The following is the name of the file: kernel32.dll version 4.00.951 (7/29/97, 337016 bytes) or later NOTE: Microsoft may not support the Kernel32 update on all versions of Windows95. Check Microsoft's Web page to determine if it is supported for your operating system revision and language kit. Do not install the kernel32 update unless Microsoft supports it. 8. TROUBLESHOOTING CONNECTION AND ACCESS PROBLEMS ---------------------------- This section documents known connection problems and suggests some solutions. SWCC is a TCP/IP socket-based application. As a result, SWCC requires that each node running a SWCC Client or Agent must have access to a valid hosts file or Domain Name Service (DNS) server. The valid hosts file must include at least the system itself and any other systems running a SWCC Client or Agent that it will connect to. There are several references in the following sections to gethostname, gethostbyaddr, and hostent. For more information, please see your system documentation (DUNIX man pages), programming environment documentation (VC++ Books Online), or a good book on TCP/IP application programming. A. Dynamic IP Address Allocation, such as DHCP, not Supported ---------------------------- SWCC will not work properly if the Client or Agent systems are obtaining an IP address dynamically. This means the Dynamic Host Configuration Protocol (DHCP) is not supported. RAS servers and IP tunneling servers are not supported unless they can be configured not to allocate IP addresses dynamically. B. WINS not Supported ---------------------------- WINS is a name resolution service available for Windows NT and Windows 95. SWCC does not support WINS. Each system using SWCC must have access to either a DNS server or a valid hosts file. C. Access Denied Problem ---------------------------- This section covers some of the most common reasons for a Client to receive an "Access Denied" message when it attempts to add an Agent system to the navigation tree. 1. Check Client Lists ---------------------------- The Client is probably not in the authorized Client list for the Agent. Please see the section in the "Getting Started" guide on configuring the appropriate Agent. 2. Multiple Agents ---------------------------- If the Agent system is running multiple SWCC Agents (for example, to support different controller types) then the Client system must be authorized for ALL of the Agents. If the Client system is missing from any Agent's authorized Client list, then that Agent cannot be added to the navigation tree. 3. HSZ Agent and Mixed or Upper-case Node Names ---------------------------- The HSZ Agent does not handle mixed case node names properly. The case of the node name in the Client authorization list must match the case returned by the DNS server or hosts file. The Windows NT configuration utility for the HSZ Agent forces node names to be entered in lower case. If the actual node name contains upper-case letters, the authorization check against the Client list will fail. Manually edit the Client authorization list to change the node name to the correct case. The Client authorization list is a file named "client.ini". It can be found in the sub-directory "etc" under the directory where the HSZ Agent was installed (d:\steam\etc for example, or /usr/opt/SWCC200/etc on a DIGITAL UNIX system). CAUTION: Verify the last entry in the client.ini file ends in a (CR/LF on NT, LF on UNIX, etc.). 4. Aliases not Checked ---------------------------- When SWCC Agents scan the Client authorization list, they do not check aliases. The entry in the Client authorization list must match that returned by a gethostbyaddr call in the hostent h_name field. SWCC will not walk the hostent alias list to check if an alias may match the Client authorization list. 5. Rule of Thumb and Testing ---------------------------- Generally, the entry in the Client authorization list for an Agent must match what gethostbyaddr() will return in the hostent h_name field when gethostbyaddr() is executed on the Agent system. If hosts files are not exactly the same on all systems, the h_name returned may vary on different Agent systems. For example, xxx.xxx.xxx.xxx client.somewhere.com client will return client.somewhere.com in the h_name field, but xxx.xxx.xxx.xxx client client.somewhere.com will return Client in the h_name field. In some situations, you can configure the way a system uses DNS and its local hosts file. Please refer to your system documentation to find how your system is configured. Some systems may be configured to do the following: * Check its local hosts file first, then go to DNS * Go to DNS first, then check its local hosts file * Ignore DNS even if configured * Ignore the local hosts file The best way to verify what needs to be used for a Client name in the Client authorization list is to write a program that runs on the Agent system and prints the h_name field returned by gethostbyaddr(). Remember, the dynamic IP address allocation is not supported. D. RA200 in Navigation Tree But It Cannot Connect ---------------------------- You may have difficulty connecting to a RA230/230+ subsystem that is shown in the navigation tree of the SWCC Client. The connection may fail if the case of the host name for the Client, as configured on the Client system, does not match the case in the DNS server or Agent system hosts file. If you are in doubt as to how the Agent system resolves the IP address, please refer to the previous section, "Rule of Thumb and Testing". To fix this situation, verify that the TCP/IP node name in the TCP/IP protocol configuration DNS section matches exactly what a nslookup for the Client's IP address returns when run on the Agent system. This situation can also be caused when the Client or Agent are using DHCP or other dynamic allocation schemes to obtain an IP address. Dynamic IP address allocation is not supported. More detail: When you use the "Add System" menu item in SWCC to add an Agent system containing a RA230/230+ controller, SWCC sends an "Are you there?" type of message to the Agent system on port spagent2. The Agent will perform the gethostbyaddr command based on the source IP address of the "Are you there?" packet. It will then check the returned node name against the authorized Client list. If it is found, the Agent returns a message to the Client with a list of subsystems. The Client then adds the subsystems to the navigation tree. When you double click on the subsystem in the navigation tree, the RA200 Client sends a packet to the Agent containing the Client node name and a port number to use for further communications. The Client node name is obtained from a gethostname call performed on the Client system by the RA200 Client. The Agent removes the Client node name and port name from that packet, and it attempts to open a socket using that information. If the case of the Client node name does not match what the Agent's DNS server or hosts file specifies, the attempt to open the socket will fail and the Client's connection attempt will time out. This situation usually occurs when the Windows NT or Windows 95 Client does not have a proper TCP/IP configuration. The node name used for the TCP/IP configuration must match the case used in the DNS server or in the hosts files. The most common failure is that the node name is upper-case and the domain name is lower-case when the DNS server wants the entire name to be lower-case. It may take some effort to fix the system's configuration. The best approach is the following: 1. Write a small program for the Client system (Windows NT or 95) that returns the output from gethostname(). 2. Write another small program on the Agent system that attempts to open a socket using that node name. 3. Try different versions on the Client node name until the connection works. 4. Modify the Client configuration until gethostname() returns the value you verified the Agent system could use to connect. or Modify the Agent system's configuration (perhaps by adding an alias to the hosts file) so the value that the Client system gethostname() returns will not fail when the Agent system attempts to use it in a socket connect. Remember, dynamic IP address allocation is not supported. E. Add New System Using IP Address Crashes ---------------------------- The SWCC Client may crash when the you attempt to add a system using the Agent system's IP address rather than the Agent system's node name. This occurs when the Client system does not have a DNS server configured that knows the Agent system, and the Agent system is not in the Client system's hosts file. To correct this situation, add the Agent system to the hosts file on the Client system. If you receive an "Invalid host" or "Host not known" error when you attempt to connect to an Agent system, the solution is NOT to try the IP address. Fix your DNS server configuration, or if that is correct, confirm the DNS server knows the Agent system. If you are not using DNS, make sure the Agent system is in the Client system's hosts file. Remember, WINS is not supported by SWCC. F. "No Agent Running" Errors ---------------------------- When trying to add a new system to the navigation tree, you may receive an error, stating "No Agent running on specified system." This message can appear for several reasons. The error message most likely occurred as a result of the following: * Wrong system name was entered. * Agents were not installed on the entered system. * Agents were installed on a system that stopped functioning. * The specific Client required to support the Agents, running on the Agent system, was not installed. For example, if the Agent system only has a HSZ70 Agent and the Client system only has RA200 support, this error message will appear. NOTE: When Client support is missing, it is usually because the unzip from the Client kit did not retain the kit's directory names. To check if Client support for an Agent had been installed, look at the following registry key: HKEY_LOCAL_MACHINE\Software\DigitalEguipmentCorporation\AppletManager You should see a series of keys for supported products. * Port names and numbers in the services file may be missing or may not match between Client and Agent. This may occur if the default value for a SWCC port was already in use. There is a list of port numbers and their default values in the Getting Started guide, Appendix A under System Requirements, Network Port Assignments. If you change the network card on a computer running Windows 95, your services file may be deleted and replaced by the version on the Windows 95 distribution kit. In this case, you will need to add the entries required for SWCC. For a list of the ports and their defaults, please see the "Getting Started" guide, Appendix A, System Requirements, Add System Error - Windows 95 Service file. G. OpenVMS, Multinet, and getservbyname Failures ---------------------------- The configuration program may fail to properly add service entries on OpenVMS, using Multinet for the TCP stack. Multinet keeps service ports in the file MULTINET:HOSTS.LOCAL. For this file to be available to the running network stack, it must be compiled and the results loaded into the dynamic Multinet database. Directions for compiling and loading this file are listed in this section. The configuration programs for the various OpenVMS SWCC Agents append the required entries to MULTINET:HOSTS.LOCAL and then compile it. If the compile fails, no error is generated. Try the following steps if the Agent reports a getservbyname failure after it runs the configuration files (SYS$MANAGER:SWCC_CONFIG.COM or SYS$MANAGER:RA200CONFIG.COM): 1. Verify that the required entries are in the file MULTINET:HOSTS.LOCAL. There should be an entry SERVICE : TCP : 4998 : SPGUI :, plus entries for some combination of SPAGENT, SPAGENT2, and CCAGENT. 2. Compile the HOSTS.LOCAL file by typing the following: MULTINET HOST_TABLE COMPILE If the compile does not succeed, you will need to fix the HOSTS.LOCAL file until it does compile successfully. 3. Load the compiled database by typing the following: @MULTINET:INSTALL_DATABASES Be careful loading the database on a running system. It may be necessary to stop and restart Multinet. Please refer to your Multinet documentation for more details. 9. GLOSSARY ---------------------------- A. Applet Manager ---------------------------- Applet Manger is the top window that shows the navigation tree in StorageWorks Command Console. Applet Manager performs the following: * Keeps track of the tools for each subsystem type * Maintains a database of the systems and subsystems that will be scanned when Command Console is started * Maintains a list of who and/or what to page when a subsystem fails * Updates the navigation tree and storage window with the latest status from the Asynchronous Event Service (AES). For a definition of AES, please refer to the section in Getting Started, "Asynchronous Event Service". B. Applet ---------------------------- An Applet is a small program.