IBM Netfinity Availability Extensions for Microsoft Cluster Service README File for Service Pack 3 CONTENTS ________ 1.0 Changes From Previous Version. 2.0 Installation and Uninstall of the Service Pack. 3.0 Installation notes. 4.0 Operating Procedures. 5.0 Trouble Shooting 6.0 Trademarks and Notices. 1.0 Changes From Previous Version. __________________________________ a) This Service Pack fixes the listed defects and makes the following changes: 1. Defect 15121: Node reboots itself after running Cluster Resource command. 2. Defect 15211: After a reboot, resources would not come online until they were moved to another node. 3. Defect 15242: Cluster shutdown and rebooted. Problem occurred after the chkdsk utility was run against the IBM NAE quorum device. This fix moves IBM NAE quorum disk data so it does not conflict with the disk FAT tables and reserved disk sectors for this use. It also disables the automatic running of chkdsk for the NAE quorum disk when a node is rebooted. When this service pack is applied, this disabling is done automatically for the configured NAE quorum disk using the Windows NT "chkntfs.exe" utility. This fix also addresses defect 15503 which is a duplicate instance of the problem. 4. Defect 15251: A node rebooted itself after running for a long period of time. Corrects a problem with writing a trace record. 5. Defect 15394: IBM Cluster System Management GUI program got a Dr.Watson error and the cluster nodes shut down. 6. Defect 15502: Corrects a problem where the IBM Cluster Systems Management GUI would hang or not refresh its status correctly. 7. Additional Serviceability items to aid problem determination. - Logging Node reboots and resource failures to the NT Event Log - Additional logging to the IBM internal use only log files - Improved data gathering utilities 8. Provides additional utilities to aid installation and problem determination. 9. Provides the Windows NT Registry Checkpointing (replication) function for IBM NAE cluster nodes. 2.0 Installation and Uninstall of the ServicePack. __________________________________________________ This service pack cannot be applied in a rolling upgrade manner. Cluster services must be stopped on all nodes before applying this update. To minimize the time that the cluster is unavailable, cluster services on each node can be restarted as soon as that node's update to ServicePack3 has been completed. This service pack can be applied to any previous version of IBM NAE, regardless of which service packs have previously been applied. Previously applied service packs do not need to be removed before applying ServicePack3. Any IBM NAE diagnostic updates should be removed prior to applying this service pack. Also, note the steps below if the IBM NAE Hot Fix for ADSM has been applied to your systems. a) To install ServicePack3, perform the following steps on each node. 1. Uninstall any Netfinity Availability Extensions diagnostic patches that have been applied, using the instructions supplied with those diagnostic patches. 2. Update the executable and DLL files. 2.1 Stop all cluster services on the node and close the Event Viewer if it is open. The services to be stopped include CHSchedulerService, CHAlertService, Cluster Service, IBMCS, and SCHEDSRV. 2.2 Copy the ServicePack self-extracting file (CHR1SP3.exe) to any directory on the node. 2.3 Enter "CHR1SP3" This will cause the current files to be backed up and the new files to be installed. 3. IMPORTANT! If the IBM NAE Cluster Hot Fix for ADSM was installed, it must be removed after ServicePack3 is installed. To remove the IBM NAE Hot Fix for ADSM, perform the following steps: 3.1 Stop all ADSM Services on the node. 3.2 Locate the path where ADSM was installed. Typically this is C:\Program Files\IBM\ADSM 3.3 Change directory to the ...\ADSM\baclient subdirectory in that path. 3.4 In the \baclient subdirectory there should be a file named "clusapi.dll". Rename this file using the following command: "ren clusapi.dll clusapi.dll.HotFix" 4. Reboot the node. b) To uninstall ServicePack3, perform the following steps on each node. 1. Stop all cluster services on the node and close the Event Viewer if it is open. The services to be stopped include CHSchedulerService, CHAlertService, Cluster Service, IBMCS, and SCHEDSRV. 2. Change to the %CS_INSTALL_DIR%\bin directory. 3. Enter "ApplyService -uninstall" This will remove the service pack files and restore the previous version. Uninstall will rename the ApplyService.exe program to ApplyService.exe.V130. If there is another file named ApplyService.exe in the install directory at that time, that file should not be deleted. It is required to uninstall a previously installed service pack. If the original version of the product is going to be uninstalled, the service packs should be uninstalled first. 4. To reenable the automatic running of chkdsk for the NAE quorum disk, the following command must be entered on each node: "chkntfs /D" This command changes the chkdsk settings back to their original default values. 5. If the IBM NAE Hot Fix for ADSM was removed when ServicePack3 was installed, then it might have to be re-enabled. This is only necessary if you are returning to an IBM NAE level earlier than ServicePack1b. If you are running at ServicePack1b or later, then the IBM NAE Hot Fix for ADSM should be left disabled. To re-enable the IBM NAE Hot Fix for ADSM, perform the following steps: 5.1 Stop all ADSM Services on the node. 5.2 Locate the path where ADSM was installed. Typically this is C:\Program Files\IBM\ADSM 5.3 Change directory to the ...\ADSM\baclient subdirectory in that path. 5.4 In the \baclient subdirectory there should be a file named "clusapi.dll.HotFix". Rename this file using the following command: "ren clusapi.dll.HotFix clusapi.dll" 3.0 Installation Notes ______________________ This Readme only covers the installation of the IBM Netfinity Availability Extensions for Microsoft Cluster Service. Contact the IBM Service and Support team to verify that all the latest support levels are installed for all pre-requisite hardware, software, and firmware. a) Symplicity Storage Manager (SYMSM) Version 7.01 is now available. The new version and instructions for upgrading from SYMSM 6.22 are available from the IBM Service and Support team. 4.0 Operating Procedures. _________________________ a) Nodes in the cluster should be powered up one at a time and allowed to boot completely to the NT logon screen before powering up successive nodes. b) Ensure that both fibre channel controllers are brought online and set to dual-active mode before powering up and restarting NT on any node in the cluster. c) After a failure event that affects several nodes, the resource groups will be moved automatically to surviving nodes. Operations personnel may want to review the assignment of groups to nodes and make manual adjustments to achieve more optimal load balancing across the cluster. d) If the IBM Cluster Systems Management GUI program is open and displaying the status of cluster resources, it is good practice to manually cause a screen refresh before taking actions on resources. This ensures that the very latest status is seen before initiating new actions. e) To shutdown a node gracefully, the IBMCS service should be stopped before shutting down Windows NT. This allows resources to be moved and IBMCS processes to terminate normally. If Windows NT is shut down first, error messages may appear as IBMCS processes are terminated by Windows NT. When nodes are then rebooted, chkdsk may be invoked automatically. If that occurs, the cluster administrator should verify that resource groups were brought on-line correctly. If not, then the resource groups should be brought on-line manually. f) The NAE quorum disk is intended for use only by the NAE program. Files should not be copied to this disk nor should chkdsk be run against the disk. Doing so may cause cluster nodes to be shut down. 5.0 Trouble Shooting ____________________ a) There are three utilities provided to aid in trouble shooting: CHVersion CHVersion is a utility that displays the version number of IBM NAE on all the nodes in the cluster. This is useful in determining if all nodes are at the same level of code. The command syntax is the following: CHVersion [node name 1] [node name 2] [other node names...] [/help] Usage: - Recommended usage is "CHVersion". - If no parameters are specified, the version numbers of all configured nodes will be displayed. - If one or more node names are specified, the version numbers of only those nodes will be displayed. - If /help is specified, the command syntax options will be displayed. CHCollectClusterData and CHCollectLocalData CHCollectClusterData and CHCollectLocalData are utilities that collect information for Service and Support personnel when a problem has occurred. CHCollectClusterData is a replacement for the CHDG.cmd utility. CHCollectLocalData replaces the "cstrc dmp dmp" command for collecting local node trace files. The command syntax is the following: CHCollectClusterData Usage: - This utility takes no parameters. This command is issued from one node in the cluster. CHCollectLocalData Usage: - This utility takes no parameters. This command is issued from every node in the cluster CHCollectClusterData works in conjunction with CHCollectLocalData which collects the files above that must be collected locally on each node. CHCollectClusterData collects all the individual node information files and also gathers the information for the cluster in general. If CHCollectLocalData has not been run on a particular node, CHCollectClusterData will prompt the user to run that utility before proceding. This helps ensure that all of the data required for proper IBM NAE support is collected. CHCollectClusterData places the individual node information files in separate subdirectories for each node. b) When the cluster information that was gathered by CHCollectClusterData needs to be sent to IBM Service and support, an FTP server has been set up to make this transmittal easier. The following is information about this FTP server: FTP server name: chftp.austin.ibm.com FTP server IP Address: 192.35.232.169 Contact the IBM Service and Support personnel for access. Once access has been given, each CUSTOMER USERID has access to a directory on the CHFTP server. Within these directories, full authority to WRITE/READ/EXECUTE has been provided. This means that directories can be created and PUT, GET, MPUT or MGET of files under the area assigned to that USERID. When putting files on the site, select "bin" or "ascii" mode! "ZIP" files are type "bin". The FTP site can be accessed from outside IBM into the system CHFTP by issuing the following command(s) in a MS-DOS window: "ftp chftp.austin.ibm.com" or "ftp 192.35.232.169" Most standard FTP programs should support this capability. Once access has been obtained to the system the following prompt will appear "Login:" and prompt for the USERID. After typing in the USERID, a password prompt will appear "Password:" and prompt for the PASSWORD. If successful, a default "Welcome" screen including warnings of unauthorized use as well as IBM Confidential data being the responsibility of the user will appear. Any standard FTP command can now be used: ls, pwd, cd, mkdir, mget, mput, get, put and so on. 6.0 Trademarks and Notices __________________________ The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM Netfinity Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation. Any other company, product, and service names may be trademarks or service marks of others. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. Copyright (C) 2000 IBM Corporation. All rights reserved. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.