Sun Cluster 2.2 7/00 Release Notes

Sun Cluster Manager Bugs

Running SCM with the HotJava browser - If you choose to use the HotJava browser shipped with your Solaris 2.6 or Solaris 7 operating environment to run SCM, there may be problems such as:

4221612 - Sun Cluster Manager sometimes incorrectly reports that the Sun Cluster HA for Netscape HTTP data service is down when it is actually up. Work around the problem by checking the status of the data service with hareg(1M) or hastat(1M) instead. See the hareg(1M) and hastat(1M) man pages for details.

4312093 - On Solaris 8, you cannot run Sun Cluster Manager as an applet with the Netscape browser and Java Development Toolkit (JDK) version 1.2. Instead, you can either run Sun Cluster Manager as a standalone application, or change the default JDK to version 1.1 (if your cluster is not running any applications that depend upon JDK 1.2).

To run Sun Cluster Manager as a standalone application, follow the detailed instructions in Chapter 2 of the Sun Cluster 2.2 System Administration Guide.

If your cluster is not hosting any applications that depend upon JDK 1.2, you can choose to change the JDK default to version 1.1. Do this by modifying the JAVA_HOME fields in the Sun Cluster Manager start-up script to specify version 1.1:


# cd /opt/SUNWcluster/scmgr/lib
# vi scm_server_start
... 
JAVA_HOME=/usr/java1.1
PATH=${JAVA_HOME}/bin:/bin:/etc:/sbin:/usr/sbin
...

4316289 - Sun Cluster Manager, when invoked from the command line, does not display data services associated with a logical host. Work around the problem by obtaining data service information from the Properties > Registered HA Services menu of the Sun Cluster Manager GUI.

4332639 - Sun Cluster Manager calls the HotJava browser by default, but HotJava is not supported on Solaris 8. Work around the problem on Solaris 8 configurations by specifying the Netscape browser. Use the following command:


# /opt/SUNWcluster/bin/scmgr -b /usr/dt/bin/netscape

4333246 - Sun Cluster Manager displays qfe private network connections as Unknown. Work around the problem by refreshing the cluster view in the Sun Cluster Manager GUI, using the menus Help > Cluster > Refresh Current View.