DIGITAL Clusters for Windows NT Release Notes Date: March, 1997 Product Versions * DIGITAL Clusters for Windows NT Version 1.1 (Windows NT 4.0 with Service Pack 2) * DIGITAL Clusters for Windows NT Version 1.0 with Clusters Service Pack 2 (Windows NT 3.51 with Service Pack 5) This document provides new and updated information for the DIGITAL Clusters for Windows NT product: * Installation and upgrade notes * New features * Problems resolved since Version 1.0 * Problems and restrictions _______________________________________________________ | Upgrade Note | | If you are upgrading cluster clients to Version 1.0, | | Clusters Service Pack 2, you must run a batch file | | on the CD-ROM. See Section 1.2.1.3. | ------------------------------------------------------- Please retain these instructions for future use. For general information on the DIGITAL Clusters for Windows NT product, visit the web site http://www.windows.digital.com. ============================================================== Contents ============================================================== 1 Installation Notes 1.1 Installing DIGITAL Clusters for Windows NT Version 1.1 1.1.1 New Installations 1.1.1.1 Cluster Servers 1.1.1.2 Cluster Clients 1.1.2 Upgrading from Version 1.0 to Version 1.1 1.1.2.1 Cluster Servers 1.1.2.2 Cluster Clients 1.1.3 HSZ 3.2 Drivers Provided 1.2 Installing DIGITAL Clusters for Windows NT Version 1.0, Clusters Service Pack 2 1.2.1 Upgrading to Clusters Service Pack 2 1.2.1.1 Cluster Servers 1.2.1.2 Files Updated by Service Pack 2 1.2.1.3 Cluster Clients 1.2.2 Installing Version 1.0 1.2.2.1 Cluster Servers 1.2.2.2 Cluster Clients 1.2.3 HSZ 2.71 Drivers Provided 1.2.4 Reinstalling: Use "Join Cluster, Search Clusters in Domain" 1.3 No Support for Checked Versions of Windows NT 1.4 Cluster Names Must Be Unique 2 New Features 2.1 Updated Documentation 2.2 Windows NT 4.0 Support (Version 1.1 Only) 2.3 IP Address Failover for Socket-Based Applications (Version 1.1 Only) 2.4 Enhanced Oracle Support 2.5 Enhanced Microsoft SQL Support 2.6 Web Server Support (Version 1.1 Only) 2.6.1 Setting Up IIS for IP Failover (Version 1.1 Only) 2.7 Lotus Notes Support 2.8 Faster Access to File Shares After a Failover 2.8.1 Faster Access After a Failover 2.8.2 Faster Access to File Shares Outside the Cluster 2.9 Cluster Administrator Enhancements 2.9.1 IP Failover Management (Version 1.1 Only) 2.9.2 SQL Database Management 2.9.3 Oracle Database Management 2.9.4 View Menu 2.9.5 One Instance of Cluster Administrator 2.9.6 Online/Offline Status in Manage Manual Failover Box 2.9.7 Cluster Monitor on Tools Menu 2.10 Managing Log Disks 2.11 Dual HSZ40 RAID Controller Support 2.12 New Cluster Utilities Available 2.12.1 Cluxfer Utility for Manual Failover from Batch File 2.12.2 Cluster Monitor Utility 2.12.3 Cluview Utility 3 Problems Resolved Since Version 1.0 3.1 Cluster Name Client Driver Recognizes Updated Network Bindings 3.2 Microsoft SQL Server 3.2.1 Manual Failover of SQL Databases with Active Connections 3.2.2 SQL Database Problems Resolved 3.3 Oracle Failover Object Problems Resolved 3.4 Mylex Controllers 3.5 Cluster Administrator 3.5.1 Works Correctly After SCSI Adapter Changes 3.5.2 Displays Disk Signature 3.5.3 Prevents Selection of Local and Cluster Buses 3.5.4 Prevents Empty Failover Groups 3.6 Cluster Drive Letters Are Now Seen in Microsoft Office 95 3.7 Large Numbers of Shares Supported 3.8 Hidden Cluster Shares Supported 3.9 DOS Applications Run on Windows NT Clients 4 Problems and Restrictions 4.1 IP Failover Objects 4.1.1 IP Failover Objects for Version 1.1 Only 4.1.2 No IP Failover for File Shares (NetBT Applications) 4.2 Microsoft SQL Server 4.2.1 Stopping the SQL Service Does Not Initiate a Failover 4.2.2 Enroll a Group's SQL Databases Before Manual Failover 4.2.3 Moving SQL Server Objects Within a Failover Group 4.3 Oracle Server 4.3.1 Oracle7 Server Patch for Windows NT 4.0 (Alpha) 4.4 Windows NT Client (Version 1.1) 4.4.1 NetShareEnum Function Not Supported 4.4.2 Viewing Cluster Shares 4.4.3 Application Icons May Not Appear on Slow Networks 4.5 Windows 95 Client 4.5.1 Using Wildcards to Assign Drives in "net use" Commands 4.5.2 Viewing Cluster Shares 4.5.3 Application Icons May Not Appear on Slow Networks 4.6 Diskperf Driver Incompatible with Clusters Software 4.7 IDE Disks Are Not Supported 4.8 Assign Fixed Drive Letters 4.9 Using an Extended LAN 4.10 # Symbol Not Allowed in Directory Names 4.11 Logon Rights Occasionally Granted Improperly 4.12 Effects of Canceling a Clusters Installation 4.13 Using Cluster Administrator 4.13.1 Display Unsynchronized with Cluster Failover Manager Database 4.13.2 Failover Object Names Restricted to 38 Characters 4.14 Defining Share Names 4.15 Lost Delayed Write Popup Boxes 4.16 Disk Administrator Shows Orphaned Disks 4.17 Potential Problem When Using Microsoft Word Version 6.0a Copyright and Trademark Information =========================================================== 1 Installation Notes =========================================================== This section supplements the installation information in your Configuration and Installation Guide. The DIGITAL Clusters for Windows NT CD-ROM provides two versions of the cluster software: * Version 1.1, for Windows NT 4.0 (new) * Version 1.0 for Windows NT 3.51 -- Clusters Service Pack 2 (new) 1.1 Installing DIGITAL Clusters for Windows NT Version 1.1 ----------------------------------------------------------- 1.1.1 New Installations ----------------------- 1.1.1.1 Cluster Servers ----------------------------------- Follow the procedure in Chapter 4 of the Configuration and Installation Guide. Prerequisite: Both servers must be running Windows NT 4.0 with Service Pack 2. 1.1.1.2 Cluster Clients ----------------------- To install Version 1.1 cluster client software on new clients or upgrade Version 1.0 clients, see Chapter 5 of the Configuration and Installation Guide. You can install client software on Windows NT, Windows 95, and Windows for Workgroup systems that need to access the cluster by using the cluster name alias. Clients do not need client software if they plan to access only IP socket-based applications that you set up in IP failover groups on the cluster. In any case, clients can reconnect to a cluster server after a failover by manually specifying the cluster server's name. 1.1.2 Upgrading from Version 1.0 to Version 1.1 ----------------------------------------------- 1.1.2.1 Cluster Servers ----------------------- You can upgrade cluster servers to DIGITAL Clusters for Windows NT Version 1.1 from * Version 1.0 * Version 1.0 with Clusters Service Pack 1 * Version 1.0 with Clusters Service Pack 2 See Chapter 7 of the Configuration and Installation Guide. You upgrade one server at a time to Windows NT 4.0 and DIGITAL Clusters 1.1, while leaving the other server up and running. The upgrade procedure preserves the existing cluster configuration. The procedure allows a Windows NT 3.51 cluster node to coexist with a Windows NT 4.0 cluster node. DIGITAL recommends that you use this configuration only for installation purposes or short-term evaluations. 1.1.2.2 Cluster Clients ----------------------- See Chapter 7 of the Configuration and Installation Guide. 1.1.3 HSZ 3.2 Drivers Provided ------------------------------ The Clusters CD-ROM provides HSZ 3.2 driver files for Windows NT 4.0. Clusters that use DIGITAL RAID subsystems require these files. \Clu1-1nt.40\Hsz_V3.2\Alpha or \Clu1-1nt.40\Hsz_V3.2\Intel ---------------------------- \reggie.exe Registry programs called by the installation \Hszinstl.bat Installation program \Hszdisk.sys HSZ driver 1.2 Installing DIGITAL Clusters for Windows NT Version 1.0 with Clusters Service Pack 2 --------------------------------------------------------------- DIGITAL Clusters 1.0 is for Windows NT 3.51 systems. This section provides notes on installing Version 1.0 and upgrading to the new Clusters Service Pack 2. 1.2.1 Upgrading to Clusters Service Pack 2 ------------------------------------------ Clusters Service Pack 2 provides * All Service Pack 1 features. * Most new features and fixes in DIGITAL Clusters 1.1, except IP address failover capabilities 1.2.1.1 Cluster Servers ----------------------- See Chapter 7 of the Configuration and Installation Guide. Prerequisites: * Windows NT 3.51 with Service Pack 5 * DIGITAL Clusters for Windows NT Version 1.0 with or without Clusters Service Pack 1 Do not upgrade while running applications such as the Cluster Administrator or SQL Server. If you try to install the Clusters Service Pack 2 while running an application, the upgrade will not complete. 1.2.1.2 Files Updated by Service Pack 2 --------------------------------------- In addition to the files listed in Chapter 7, the installation procedure adds the following file to the user's target directory (typically C:\Program Files\Digital\Clusters): cluview.exe 1.2.1.3 Cluster Clients ----------------------- To upgrade clients, see Chapter 7 of the Configuration and Installation Guide. To upgrade a Windows 95 client or Windows for Workgroups client, you must run a batch file on the CD-ROM as instructed in the chapter. The installation procedure is functionally equivalent to uninstalling the Version 1.0 client and installing the Version 1.1 client. 1.2.2 Installing Version 1.0 ---------------------------- If you want to install a new cluster in a Windows NT 3.51 environment rather than upgrading to Windows NT 4.0, you can install DIGITAL Clusters 1.0 and then install Clusters Service Pack 2. 1.2.2.1 Cluster Server ----------------------- See Chapter 4 of the Configuration and Installation Guide. Prerequisite: Both cluster servers must run Window NT 3.51 with Service Pack 5. A copy of Service Pack 5 is provided on the DIGITAL Clusters CD-ROM: \Clu1-0nt.351\nt351sp5 1.2.2.2 Cluster Clients ------------------------- See Chapter 5 of the Configuration and Installation Guide. You can install client software on Windows NT, Windows 95, and Windows for Workgroup systems that need to access the cluster by using the cluster name alias. In any case, clients can reconnect to a cluster server after a failover by manually specifying the cluster server's name. 1.2.3 HSZ 2.71 Drivers Provided ------------------------------ The Clusters CD-ROM provides HSZ 2.71 driver files: \Clu1-0nt.351\Hsz_V2.71 ----------------------- \Renotsp1.doc Release notes for drivers \Clu1-0nt.351\Hsz_V2.71\Alpha or \Clu1-0nt.351\Hsz_V2.71\Intel ---------------------------- \reggie.exe Registry programs called by the installation \Hszinstl.bat Installation program \Hszdisk.sys HSZ driver 1.2.4 Reinstalling: Use "Join Cluster, Search Clusters in Domain" ----------------------------------------------------------------- This note applies to cases where you need to uninstall and reinstall Version 1.0 cluster software on a server. If you want the server to join an existing cluster, choose the "Join Cluster, Search Clusters in Domain" option when reinstalling the cluster software. Do not choose the "Join Cluster" option. If you do, the two cluster servers cannot communicate. This problem does not occur in Version 1.1. 1.3 No Support for Checked Versions of Windows NT --------------------------------------------------- DIGITAL Clusters for Windows NT is not supported on checked (debug) versions of Windows NT, such as the version available with the Windows NT Device Driver Kit (DDK). DIGITAL Clusters for Windows NT must be installed on a release build (retail kit) of Windows NT. * Clusters Version 1.1 requires Windows NT Version 4.0 with NT Service Pack 2. * Clusters Version 1.0 requires Windows NT Version 3.51 with NT Service Pack 4 or NT Service Pack 5. The Clusters Service Pack 2.0 requires NT Service Pack 5. NT Service Pack 5 is provided on the DIGITAL Clusters for Windows NT CD-ROM. 1.4 Cluster Names Must Be Unique ----------------------------------------------- The names you assign to different clusters in the same LAN must be unique within the first eight characters. Otherwise, it is possible for one cluster to see resources owned by another. For example, the names CLUSTER1 and CLUSTER2 are valid; CLUSTER1A and CLUSTER1B are not. ========================================================= 2 New Features ========================================================= This section describes new features since DIGITAL Clusters for Windows NT Version 1.0. The features are available in both Version 1.1 and Version 1.0, Clusters Service Pack 2, unless noted otherwise. * Online documentation * Windows NT 4.0 support (Clusters 1.1 only) * IP address failover support (Clusters 1.1 only) * Enhanced Microsoft SQL support, including o Support for multiple, independent databases o Ability to run an SQL server on each cluster server o More automated setup procedures * Enhanced Oracle support, including o Oracle Server 7.3.2.2 support * Lotus Domino failover support * Faster access to file shares after a failover * Dual HSZ40 RAID controllers support * Cluster administrator enhancements 2.1 Online Documentation ------------------------- This release includes the following updated documentation: * Configuration and Installation Guide (hardcopy and .pdf) * Administrator's Guide (hardcopy and .pdf) * Cluster Administrator online help You can view the online (.pdf) versions of the guides with the free Adobe Acrobat Reader, available from http://www.adobe.com. The .pdf files are in the following directory on the DIGITAL Clusters 1.1 CD-ROM: \DOCS An index is provided for doing full-text searches in Acrobat Reader. If you want to copy the .pdf files from the CD-ROM, copy the full \DOCs folder and keep it together as a unit. 2.2 Windows NT 4.0 Support (Version 1.1 Only) --------------------------------------------- DIGITAL Clusters 1.1 requires the Windows NT 4.0 operating system for cluster servers. If you are upgrading from Version 1.0, you first must upgrade your servers to Windows NT 4.0 with NT Service Pack 2. Follow the upgrade procedure in Chapter 7 of the Configuration and Installation guide. 2.3 IP Failover for Socket-Based Applications (Version 1.1 Only) ----------------------------------------------------- The Cluster Administrator now lets you specify one or more common cluster Internet Protocol (IP) addresses as failover objects. This allows your cluster to support failover capabilities for socket-based applications typically accessed by an IP address. When a group containing an IP address fails over, the IP address migrates to a network adapter on the other cluster server. Clients can continue to access any applications in the group by using the same IP address. The Cluster Administrator lets you * Create, delete, and modify IP failover objects. When you create an IP failover object, you choose which network adapters on a server can enable the IP address. You can choose individual adapters or let the software use any available adapter. * Insert IP failover objects in failover groups. Note: When creating failover groups, DIGITAL recommends that you specify objects in the following order: -- Shared disk object -- IP address object -- Application object * View all IP-enabled network adapters for a server (System View). 2.4 Enhanced Oracle Support ------------------------------------------------------ DIGITAL Clusters software now includes failover support for the Oracle Server 7.3.2.2 and the Oracle Workgroup Server based on the Oracle 7.3 release. DIGITAL Clusters 1.1 software provides IP failover support. Oracle clients can connect to a cluster by using a cluster IP address that you specify in an IP failover object. 2.5 Enhanced Microsoft SQL Server Support ------------------------------------------------------ DIGITAL Clusters software provides significant new features and enhancements for SQL Server environments. Many features are now automated. See Chapter 3 of the Administrator's Guide for details on major changes to SQL management procedures. Here are the some of the new features and enhancements: Support for Multiple, Independent SQL Databases ------------------------------------------------ You can now use multiple SQL databases independent of each other. You can enroll and unenroll databases in failover groups as desired. Cluster software now lets SQL clients connect to a cluster IP address. Clients can connect to a particular group of SQL databases. SQL Failover Support from Both Cluster Servers ---------------------------------------------- You can now run the SQL Server on both cluster servers, each supporting a different group of SQL databases. If one server fails, the other server can take over support for all databases. Automated Configuration of SQL Server Databases ----------------------------------------------- The Cluster Administrator now provides a more automated setup sequence for SQL databases, eliminating many manual SQL command steps. See the Administrator's Guide for details. DIGITAL Clusters 1.1 software provides IP failover support. SQL Server clients can connect to a cluster by using a cluster IP address that you specify in an IP failover object. 2.6 Web Server Support (Version 1.1 Only) -------------------------------------------------- With IP failover support, you can now create failover scripts for web servers such as * Microsoft Internet Information Server (IIS) * Netscape Enterprise Server See the Administrator's Guide for details on installing and configuring these web servers for cluster use. 2.7 Lotus Domino Support -------------------------------------------------- DIGITAL Clusters 1.1 provides IP failover support for the Lotus Domino 4.5 server, including web server support. You can run multiple partitioned Domino servers on each cluster server. DIGITAL Clusters 1.0 supports the Lotus Notes 4.11 server, using pointer files and scripts. Notes 4.11 clients cannot use the cluster alias to connect to the cluster, because Notes requires that the client specify the name of the individual server. See Chapter 4 of the Administrator's Guide for details on installing and configuring Lotus Domino or Lotus Notes servers for cluster use. The Clusters CD-ROM provides sample failover scripts from the guide in the following directories: * \Clu1-1nt.40\Samples\Lotus For Lotus Domino 4.5 on DIGITAL Clusters 1.1 * \Clu1-0nt.351\Samples\Lotus For Lotus Notes 4.11 DIGITAL Clusters 1.0 2.8 Faster Access to File Shares -------------------------------- 2.8.1 Faster Access After a Failover ------------------------------------ You can now access file shares much faster after a failover. Access time has been reduced by a factor of 100 or more. 2.8.2 Faster Access to File Shares Outside the Cluster ------------------------------------------------------ Access to multiple file shares on systems outside the cluster is much faster. The first connection takes approximately the same amount of time as before, but subsequent connections are much faster. 2.9 Cluster Administrator Enhancements ---------------------------------------------------- 2.9.1 IP Failover Management (Version 1.1 Only) -------------------------------------------------------- Dialog Boxes ------------ The following new dialog boxes let you manage IP failover objects: * Create IP Failover Object (Create Menu) Lets you create an IP failover object. You specify an IP address, subnet mask, and one or more network adapters on each server that can be used to enable the address. * Modify IP Failover Object (Modify Menu) Lets you modify the subnet mask for the specified IP address and change the selected network adapters for the address. Note: If you need to modify the specified IP address, delete the IP failover object and create a new one. * Delete IP Failover Object (Delete Menu) Lets you delete an IP address failover object. Views ----- The System View now displays all IP-enabled network adapters for each cluster server. The Class View displays existing IP Failover Objects. The Cluster view displays IP Failover Objects that you have added to failover groups. You can double-click an IP Failover Object in the Class or Cluster View to display the Modify IP Failover Object dialog box. 2.9.2 SQL Database Management ----------------------------- The new Manage SQL Databases dialog box lets you enroll SQL databases in a failover group or unenroll them. You can also deactivate a database prior to moving it from one failover group to another. Views ----- The Class View now displays all available SQL server databases -- enrolled (green icon) and unenrolled (yellow icon). The Cluster View displays SQL server failover objects with their enrolled databases. 2.9.3 Oracle Database Management -------------------------------- The Create and Modify Oracle Failover Object dialog boxes now check that you have entered values for five fields: Oracle Username, Oracle Password, Oracle sid, Oracle sid parameter file, and Oracle database. The Oracle Pipe Name field is now optional, because you can use socket-based IP failover in DIGITAL Clusters 1.1. The new Oracle Listener Name identifies the Oracle TNS Listener associated with the Oracle database. This field is required if you use IP failover. 2.9.4 View Menu Enhancements ---------------------------- On the View menu, a radio button now appears next to the currently selected view (Cluster, Class, or System). To refresh the view, you can now use the F5 accelerator key as well as the Refresh View menu item. 2.9.5 One Instance of Cluster Administrator ------------------------------------------- In this release, only one instance of the Cluster Administrator can run at a time. If the Cluster Administrator is already running and you try to start Clusters again, the Cluster Administrator main window simply pops to the foreground. It is possible to start another instance of the Cluster Administrator when it is first initializing, but DIGITAL does not recommend this. 2.9.6 Online/Offline Status in Manage Manual Failover Box --------------------------------------------------------- The Manage Manual Failover dialog box displays the online/offline status of each failover group. For online groups, the current server for the group is also listed. 2.9.7 Cluster Monitor on Tools Menu ----------------------------------- The Cluster Administrator Tools pull-down menu provides access to the Cluster Monitor utility (fmstat.exe), for monitoring the online/offline status of failover groups. See Appendix A of the Administrator's guide for details. 2.10 Managing Log Disks ----------------------- Manage Log Disk Lists the Available Disks Only ----------------------------------------------- When you choose Manage Log Disk, the Cluster Administrator now lists only those shared disks to which you may successfully assign ownership of the log disk. This differs from Version 1.0, in which all shared disks were listed, even those that were not on line to the same server as the current log disk, and therefore were unavailable to own the log disk. Warning Messages When Removing the Log Disk ------------------------------------------- The Cluster Administrator now displays a warning message in the following situtations: * When you remove the log disk from a failover group. * If the log disk is unavailable at startup. * If you delete the failover group containing the log disk. 2.11 Dual HSZ40 RAID Controller Support -------------------------------------- DIGITAL Clusters for Windows NT now supports the use of dual-redundant HSZ40 RAID controllers in the StorageWorks RAID 410 subsystem, or in any HSZ40-based RAID subsystem. RAID 410 controllers must be configured to work with clusters. See the Configuration and Installation Guide. 2.12 New Cluster Utilities Available ------------------------------------ 2.12.1 Cluxfer Utility for Manual Failover from Batch File --------------------------------------------------------- The new cluxfer command line utility lets you start a manual failover of a cluster failover group from within a batch file or from an application. With this utility, you can transfer a cluster failover group to a specific cluster node. See Appendix A of the Administrator's Guide for details. 2.12.2 Cluster Monitor Utility ------------------------------ Cluster Monitor (fmstat.exe) is a simple cluster status display program that can run on any Windows NT system. Cluster Monitor displays the online/offline status of all failover groups in a cluster as seen from both machines in the cluster. See Appendix A of the Administrator's Guide for details. 2.12.3 Cluview Utility ---------------------- The cluview command line utility lets you display information on cluster servers and resources. The cluview utility is installed with cluster server software in \Program Files\Digital\Cluster. Syntax: cluview [ [-h|-v|-w] \\ClusterName] -h This help message -v Verbose output (slow) Displays connected network shares, FMGroup, and Pipe resources. -w Extremely verbose output (very slow) Displays all resources. Examples: o > cluview Cluster Name Server Names --------------------------------------------------------- \\Engineer \\Eng1 \\Eng2 \\Marketing \\MktOne \\MktTwo o > cluview -v \\Engineer Resource Name Resource Type Connection Point ---------------------------------------------------------- JaneGP FMGroup \\Eng1\JaneGP JohnGP FMGroup \\Eng2\JohnGP cluio3 NetworkShare \\Eng2\cluio3 Share NetworkShare \\Eng1\Share SQLFiles NetworkShare \\Eng1\SQLFiles o > cluview -w \\Engineer Resource Name Resource Type Connection Point ---------------------------------------------------------- _disk_19ea7f6d FMDisk _disk_19ea7f6e FMDisk _disk_377be7b2 FMDisk JaneGP FMGroup \\Eng1\JaneGP JohnGP FMGroup \\Eng2\JohnGP 11.22.11.223 FMIp 11.22.11.224 FMIp Sql Object FMSql FMDisk FMType FMIp FMType FMOracle FMType FMScript FMType FMSql FMType cluio3 NetworkShare \\Eng2\cluio3 Share NetworkShare \\Eng1\Share SQLFiles NetworkShare \\Eng1\SQLFiles Eng1 Nodes Eng2 Nodes Sql Pipe Sql Object Pipe NetworkShare ResourceTypes Nodes ResourceTypes Pipe ResourceTypes FMDisk RXACT FMGroup RXACT FMIp RXACT FmIvp RXACT FMSql RXACT FMTYPE RXACT NetworkShare RXACT Pipe RXACT ============================================================= 3 Problems Resolved Since Version 1.0 ============================================================= This section describes cluster software problems resolved since the Version 1.0 release. 3.1 Cluster Name Client Driver Recognizes Updated Network Bindings --------------------------------------------------------------- If you update your system network bindings, the new Windows NT Cluster Name client driver (cfs.sys) uses your updated values the next time you reboot the system. In Version 1.0, the driver ignored the new binding values. 3.2 Microsoft SQL Server -------------------------------------------------------------- 3.2.1 Manual Failover of SQL Databases with Active Connections ---------------------------------------------------------------- In Version 1.0, manual failover of a group containing an SQL database object with active connections would fail, and the SQL Server process would be unreliable. This problem was fixed in the Version 1.0 Cluster Service Pack 1 release. The cluster software now stops all active SQL client connections to the databases being failed over before performing the failover. 3.2.2 SQL Database Problems Resolved ------------------------------------ The following SQL database problems in Version 1.0 were fixed in the Version 1.0 Clusters Service Pack 1 release: * Error when a database spans multiple disks * Cluster Failover Manager hangs during a system shutdown When SQL databases were active on shared cluster disks, the Cluster Failover Manager process could hang when the system was shutting down. This problem is fixed. 3.3 Oracle Failover Object Problems Resolved -------------------------------------------- The following problems with Oracle failover objects were fixed in the Version 1.0 Clusters Service Pack 1 release: Changing the sid Attribute -------------------------- In Version 1.0, if you changed the sid attribute of an Oracle failover object, the Cluster Administrator appeared to complete the operation but did not propagate the change to the Cluster Failover Manager Database (CFMD). This required you to work around the bug by deleting and recreating the Oracle Failover object. This problem is fixed. Incomplete Oracle Failover Object Not Allowed --------------------------------------------- In Version 1.0, when you created or modified an Oracle Failover Object, the Cluster Administrator issued an error message if you did not provide values for mandatory fields. The Create and Modify screens now require that you enter values for five fields: Oracle Username, Oracle Password, Oracle sid, Oracle sid parameter file, and Oracle database. 3.4 Mylex Controllers ---------------------- In Version 1.0, the Cluster Administrator would sometimes display an incorrect error message on systems with Mylex controllers: "Attempting to insert duplicate SCSI disk" This problem was first fixed in the Version 1.0 Clusters Service Pack 1 release. 3.5 Cluster Administrator ------------------------- 3.5.1 Works Correctly After SCSI Adapter Changes ------------------------------------------------ In Version 1.0, the Cluster Administrator could shut down on startup instead of displaying the Reconfigure Cluster Adapter dialog box. This problem was first fixed in the Version 1.0 Clusters Service Pack 1 release. The Cluster Administrator still issues several low-level error messages after you change a SCSI adapter or modify an IRQ or I/O address. These messages indicate that the log disk is unavailable. You can ignore the messages; after the messages are displayed, the dialog box displays correctly. At that point, verify or correct the information displayed in the dialog box, and select OK. 3.5.2 Displays Disk Signature ----------------------------- The Manage SCSI Adapter Configuration dialog box now displays the disk signature. 3.5.3 Prevents Selection of Local and Cluster Buses --------------------------------------------------- In Version 1.0, the Manage Adapter Configuration or Reconfigure Adapter dialog box permitted you to select a local bus and a cluster bus simultaneously, which made it unclear which bus was associated with the specific adapter information being displayed by the dialog box. This problem was first fixed in the Version 1.0 Clusters Service Pack 1 release. 3.5.4 Prevents Empty Failover Groups ------------------------------------ In Version 1.0, if you modified a failover group and removed all of its failover objects, the Cluster Administrator failed when you selected OK. Now, the Cluster Administrator displays an error message that a group must contain at least one object. 3.6 Cluster Drive Letters Are Now Seen in Microsoft Office 95 ------------------------------------------------------------- In Version 1.0, occasionally an application (particularly Microsoft Office 95) was unable to display drive letters for cluster disks in its Open... dialog box. This problem was first fixed in the Version 1.0 Clusters Service Pack 1 release. 3.7 Large Numbers of Shares Supported ------------------------------------- In Version 1.0, an infinite loop could occur in the process running cns.exe if a large number of cluster shares were defined. This problem could also cause cluster clients to hang when browsing cluster shares. This problem was first fixed in the Version 1.0 Clusters Service Pack 1 release. 3.8 Hidden Cluster Shares Supported ----------------------------------- In Version 1.0, if you created a share on a cluster disk with a share name ending with the dollar sign ($) character, the share was not marked as a cluster share. Therefore, it could not participate in any cluster failover and was inaccessible using the cluster alias. This problem was first fixed in the Version 1.0 Clusters Service Pack 1 release. In addition, when the cluster software places a disk on line and assigns it a drive letter, the software now creates a hidden share based on the drive letter. For example, if disk X: comes on line, the cluster software creates a hidden share called X$. When a disk is placed off line, the hidden share name is removed. This behavior is consistent with Microsoft LAN Manager. 3.9 DOS Applications Run on Windows NT Alpha Clients ----------------------------------------------------- In Version 1.0, after you started one DOS application on a Windows NT Alpha client, you could not run a second DOS application in another window. The second DOS application would hang and prevent further access to cluster shares. This problem was apparent when using some software programs. The problem is fixed. ============================================================== 4 Problems and Restrictions ============================================================== This section describes known problems and restrictions in DIGITAL Clusters for Windows NT Version 1.1 and Version 1.0, Clusters Service Pack 2. 4.1 IP Failover Objects ----------------------- 4.1.1 IP Failover Objects for Version 1.1 Only ---------------------------------------------- You can create an IP failover object only after upgrading both cluster servers to Windows NT 4.0 with Service Pack 2 and DIGITAL Clusters 1.1. If you try to create an IP failover object while one server is unavailable (for example, while upgrading the first server in the Version 1.1 upgrade procedure), the Cluster Administrator displays a warning message. 4.1.2 No IP Failover for File Shares (NetBT Applications) ---------------------------------------------------------- IP failover for file shares and other applications that use NetBIOS over TCP is not currently supported. 4.2 Microsoft SQL Server ------------------------ 4.2.1 Stopping the SQL Service Does Not Initiate a Failover ----------------------------------------------------------- Stopping the SQL service does not initiate a failover. 4.2.2 Enroll a Group's SQL Databases Before Manual Failover ----------------------------------------------------------- Before manually failing over a group in Cluster Administrator, make sure that all SQL databases on the group's disks are enrolled for failover support. If some databases are enrolled and others are not, then the MSSQLServer process will eventually hang. Your unenrolled databases will be marked suspect, because the disks have disappeared. You may also see the following error message when you start or refresh Cluster Administrator: Error from CluFmSqlGetDbInfoArray = -1073741819 4.2.3 Moving SQL Server Objects Within a Failover Group ------------------------------------------------------- In this release, DIGITAL Clusters software automatically adds or removes SQL Server failover objects from the appropriate failover groups when you perform SQL management functions, such as enrolling SQL databases on a shared disk for failover. Generally, you do not need to add or remove SQL Server failover objects from a group. The one exception is when you want to change the order of objects in a group. For example, you may want to move a script failover object after a SQL Server failover object to ensure the script runs correctly. In this case, you can use the Modify Failover Group dialog box to move the SQL Server failover object by removing it from the group, then reinserting the object in the desired sequence. Make sure to place the object back in the group, or the SQL databases will not be available after the next failover. 4.3 Oracle Server ----------------- 4.3.1 Oracle7 Server Patch for Windows NT 4.0 (Alpha) ----------------------------------------------------- At the time of this writing, you need the following Oracle software to run the Oracle7 Server on the Windows NT 4.0 for DIGITAL Alpha platform: * Oracle7 Server V 7.3.2.3.1 for Windows NT 3.51 (Alpha) * Oraspawn.dll replacement image (patch) from Oracle support The next release of Oracle7 Server for the DIGITAL Alpha platform will eliminate the need for the patch. 4.4 Windows NT Client (Version 1.1) ----------------------------------- 4.4.1 NetShareEnum Function Not Supported ----------------------------------------- DIGITAL Clusters for Windows NT does not support the NetShareEnum programming function, which is obsolete for Win32-based applications. Applications that try to use the NetShareEnum function to enumerate cluster shares will not work properly. 4.4.2 Viewing Cluster Shares -------------------------------- The net view \\clustername command does not work properly on Windows NT clients. To view a list of a cluster's shares, use Explorer or File Manager. 4.4.3 Application Icons May Not Appear on Slow Networks -------------------------------------------------------- If there are network delays, Windows Explorer and Network Neighborhood may display a default icon for some applications, rather than the application's own icon. This is a cosmetic problem only, and does not affect access to the applications. 4.5 Windows 95 Clients ---------------------- 4.5.1 Using Wildcards to Assign Drives in "net use" Command ----------------------------------------------------------- If you use a wildcard as follows in a "net use" command to assign a drive letter to a cluster share, Windows Explorer and My Computer will list the drive incorrectly: > net use * \\server-name\share-name The drive will be listed with an incorrect name and as a local drive rather than a remote drive. You can enter "net use" commands without parameters to display the correct information for cluster file shares: > net use \\server-name\share-name 4.5.2 Viewing Cluster Shares ----------------------------- The net view \\clustername command does not work correctly on Windows 95 clients. To view this information, you can use the Network Neighborhood: 1. Double-click on the Network Neighborhood icon. 2. Double-click on the DIGITAL Clusters icon. Clusters are denoted by domain icons. To view the list of a cluster's shares , double-click on its icon. 4.5.3 Application Icons May Not Appear on Slow Networks -------------------------------------------------------- If there are network delays, Windows Explorer and Network Neighborhood may display a default icon for some applications, rather than the application's own icon. This is a cosmetic problem only, and does not affect access to the applications. 4.6 Diskperf Driver Incompatible with Clusters Software ------------------------------------------------------- The diskperf driver is used to collect performance data. The driver gets installed into the SCSI driver chain. However, the disk counters are suppressed when DIGITAL Clusters for Windows NT software is installed. 4.7 IDE Disks Are Not Supported -------------------------------- DIGITAL Clusters for Windows NT environments do not support systems that include IDE disks. The ATDISK.SYS driver used for IDE disks is incompatible with the cluster drivers. Using ATDISK.SYS in a cluster causes the system to fail when booted. 4.8 Assign Fixed Drive Letters ------------------------------- After the Windows NT operating system is installed, it is imperative that the drive letter assigned to the system partition (typically C: or D:) remain constant, because hardcoded references to this drive letter are recorded in the Windows NT Registry. For information on assigning fixed drive letters, see the Configuration and Installation Guide. 4.9 Using an Extended LAN --------------------------- The Cluster Name Server protocol is a LAN protocol. There are some restrictions on using DIGITAL Clusters for Windows NT in an extended LAN with routers, depending on your network protocols. See the Configuration and Installation Guide for details. 4.10 # Symbol Not Allowed in Directory Names ---------------------------------------------- Cluster software does not recognize directory names that include the pound symbol (#). 4.11 Logon Rights Occasionally Granted Improperly ------------------------------------------------ On occasion the Windows NT software improperly grants the "logon as a service" right to a user account, even when the account was created correctly. If this happens, the cluster services will not start. The workaround for this problem is as follows: 1. Open the Services applet in Control Panel. 2. Select the CFMD server. 3. Click on Startup... then click on OK. The software displays the following message: The user is granted log in as a service. At this point, you can start the cluster services. 4.12 Effects of Canceling a Clusters Installation ------------------------------------------------ If you exit prematurely from the Setup program when installing either the cluster server or cluster client software, application files and Registry entries can be left on your system. You must manually delete these files and Registry entries and reboot your system before reinstalling the cluster software. For details, see the Configuration and Installation Guide. 4.13 Using Cluster Administrator ------------------------------- 4.13.1 Display Unsynchronized with Cluster Failover Manager Database ---------------------------------------------------------- It is possible for the Cluster Administrator display to become unsynchronized with the cluster configuration database in the registry. This can happen if you have the Cluster Administrator running on both servers of the cluster and are making changes from both servers. The Cluster Administrator on one server may be unaware of changes propagated to the registry from the Cluster Administrator on the other server. Two workarounds exist for this problem: * If you suspect that the Cluster Administrator is out of synch, choose Refresh from the View menu. * Run the Cluster Administrator on only one server at a time. 4.13.2 Failover Object Names Restricted to 38 Characters -------------------------------------------------------- Failover object names can have a maximum of 38 characters. If you try to add an object with a longer name to a failover group, Cluster Administrator will fail. 4.14 Defining Share Names --------------------------- The DIGITAL Clusters for Windows NT software does not prevent the creation of two file shares with the same name if the shares are on different disks and the disks are on line to different cluster servers. DIGITAL recommends that you do not create two shares with the same name on two servers in the same cluster. 4.15 Lost Delayed Write Popup Boxes ----------------------------------- A failover group can transition from on line to off line while the system is still running. This can occur from a voluntary failover or involuntary failover. During a voluntary failover, a system puts a group off line in a controlled manner in response to a user request. An example of this is a group with failback enabled that is on line on the failover server when the primary server comes back up. The failover server does a voluntary failover to the primary server. During a voluntary failover the following happens: * The shares, if any, are made unavailable. * The file system caches are flushed to disk. * The file system is dismounted if possible. * The disk itself is put off line. Every opportunity is taken in this case to assure that cached file system data is returned to disk prior to the failover. During an involuntary failover, a disk goes off line immediately without a chance for any flushes to occur. This may happen in a network partition (communication lost between the two cluster members) where the offline member resumes ownership of a disk because it thought the other was down. This can occur although efforts are made to prevent it. When ownership of a disk is taken from the on line member, the disk becomes inaccessible immediately without the normal graceful offline behavior. As a result of an involuntary failover, the operating system receives errors when it attempts to write the data in the file system cache to the disk as part of normal background processing. The errors appear as popup boxes, indicating that a "delayed write" was unable to be written. The user can click OK to close these boxes. These warnings indicate that the disk failed over prematurely and that the user's file system I/Os were not written to the disk if they were issued just before, during, and after the disk went off line. Users should verify the state of their files and reissue the client operation when the group finishes failing over to the other server. Although the client file operation must be reissued, file system integrity is maintained. 4.16 Disk Administrator Shows Orphaned Disks After Some Failovers ------------------------------------------------------ The cluster software uses the following methods to dismount files systems for failovers: For voluntary failovers: Conventional or Disconnected For involuntary failovers: Disconnected A conventional dismount is tried first. A conventional dismount will fail if another program (such as File Manager) has locked the volume, or if files remain open on the volume. During a disconnected dismount, the disk data structure is disconnected from the underlying I/O system, but left physically present in the system. When the disk fails back to the system, it is reinstantiated. This guarantees that an old file system state associated with the old disk instance does not interfere with the new file system state on the new disk instance. However, as a side effect, the old disk instance remains visible in Disk Administrator, appearing as a gray box for the remainder of the system up time. This is normal behavior for the mechanism and is harmless. The gray box disappears when the system is rebooted. 4.17 Potential Problem when Using Microsoft Word Version 6.0a ------------------------------------------------------------ If a document in a cluster share is being edited with Microsoft Word and the contents of the document are saved while the share is being failed over from one server to the other, Word can hang or crash. Once the failed server is rebooted, Word puts up one or more message boxes indicating an unrecoverable or serious disk failure. Clicking OK on these boxes eventually results in a protection failure in the Word application itself. If the application hangs, it can be terminated and the system will return to normal. This problem is not caused by DIGITAL Clusters for Windows NT and has been reproduced using Microsoft Word Version 6.0a on systems without DIGITAL Clusters for Windows NT installed. ------------------------------------------------------------- Copyright and Trademark Information Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Copyright Digital Equipment Corporation 1997 All rights reserved. The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital or its affiliated companies. The following are trademarks of Digital Equipment Corporation: AlphaServer, AlphaStation, DIGITAL, Prioris, ServerWORKS, StorageWorks, and the DIGITAL logo. The following are third-party trademarks: Adaptec is a trademark of Adaptec Inc. Intel is a registered trademark of Intel Corporation. Macintosh is a registered trademark of Apple Computer, Inc. Microsoft, MS-DOS, Windows, and Windows 95 are registered trademarks and Windows NT is a trademark of Microsoft Corporation. NetBIOS is a trademark of Micro Computer Systems, Inc. NT is a trademark of Northern Telecom Limited. Oracle and SQL*Net are registered trademarks and Oracle7 is a trademark of Oracle Corporation. OS/2 is a registered trademark of International Business Machines Corporation. SQL Server is a trademark of Sybase, Inc. All other trademarks and registered trademarks are the property of their respective holders.