Framework Bugs

4132195 - Clusters that include dual-Ultra-2, dual-fas-SunSwift, and dual-Sun StorEdge MultiPack MI-SCSI devices can experience a bug in the fas chip that causes the fas SCSI bus to hang when it is selected by more than one host. This can occur in a number of situations--for example, when a SCSI target device driver is attached or after a dormant detached device is re-attached.

If an active cluster node with SCSI ID target 6 is running while another node using SCSI ID target 7 is rebooted, timeouts or resets might result. Note that Solaris reboots can cause a probe to all possible devices.

To prevent timeouts or resets caused by this bug, remove target 6 (and target 7 if present, and/or any other SCSI ID coinciding with SCSI IDs being used by SunSwift/fas initiators in an MI-SCSI configuration) from both the st.conf and sd.conf files.

4217658 - The public network monitor (PNM) daemon, pnmd, does not perform failover of multicast groups after a network adapter failover occurs. Sun Cluster supports failover of only the default multicast route (224.0.0.0). When a network adapter failover or switchover occurs, the default multicast route is switched to the appropriate adapter, but any client application that had established a multicast group will no longer work. You must restart any client applications in this condition.

4233956 - Cluster fails to come up and displays error messages if IP addresses are not assigned to logical hosts. The error messages might indicate that ifconfig failed. To prevent the problem, make sure all logical hosts have entries in the /etc/hosts files or name service maps indicating their associated IP addresses, before you attempt to bring up the cluster.

4270573 - The confccdssa(1M) command displays error messages and hangs if the disk name you specify contains the default suffix of a subdisk name. Work around the problem by creating disk groups (sc_dg) manually or by renaming any disks that contain a numeric suffix of the format -XX, so that they do not contain the suffix.

4286442 - In a cluster environment with shared single-ended or Differential SCSI devices, the SCSI chain can be broken when a node is powered off incorrectly or when the SCSI cable is disconnected before the bus is quiesced. This can cause data access errors on the node that is still active. Prevent this problem by following instructions exactly as documented in the Sun Enterprise Cluster System Site Preparation, Planning, and Installation Guide and the Sun Enterprise Cluster Hardware Service Manual when powering off a node or disconnecting SCSI cables.

4291427 - In Sun Cluster 2.2 running on Solaris 7, using the scinstall(1M) command to remove the client packages can fail with the following error message:

Patch 108400 is required to be installed by patch 108446it cannot be backed out until patch 108446 is backed out.

This occurs because of dependencies between patches 108446 and 108400. Work around the problem by removing patches 108446 and 108400 manually and then re-starting the package removal process using scinstall.

4296706 - If a connection is lost from a differential SCSI device (A/D1000, A3x00), or if termination is lost due to one cluster node being powered off, the storage device can become inaccessible to the surviving host and the surviving host can panic. Prevent this problem by following instructions exactly as documented in the Sun Enterprise Cluster System Site Preparation, Planning, and Installation Guide and the Sun Enterprise Cluster Hardware Service Manual when powering off a node or disconnecting SCSI cables.

4299187 - The cluster console does not accept non-ascii characters, for example, Japanese characters or French (accented) characters. Work around the problem by inputting such characters through the individual terminal windows on each cluster node, instead of through the cluster console.

4319412 - Killing clustd on the master node panics both the master node and backup node. Prevent or work around the problem by applying a Solstice DiskSuite patch, available from your service provider.

4321549 - Cannot switch over logical host while database instance is running on single-CPU nodes, on clusters using Oracle 8.1.6 and Solstice DiskSuite. Work around the problem by applying patch 108508 (Solaris 2.6) or 108509 (Solaris 7), available from your service provider or from the Sun patch web site, http://sunsolve.sun.com.

4326020 - Layered volumes feature of VERITAS Volume Manager 3.0.x: Problems can occur when you create or switch over a logical host associated with a disk group containing layered volumes. Prevent the problem by installing a Sun Cluster patch. See "Patches" for patch details.

4326276 - Node failover or removal is prevented on clusters using Instant Image 2.0. Because the volume manager is overlaid with the Instant Image sv driver, the Sun Cluster software cannot unmount disk group volumes during failover. Prevent the problem by applying the relevant Sun Cluster and Instant Image patches, available from your service provider or from the Sun patch web site, http://sunsolve.sun.com.