HA Clusters Quick Links

Download

Download the latest Open High Availability Cluster source

Participate

Join the OpenSolaris HA Clusters discussions

Contribute

Contribute to Open High Availability Cluster

Translation for this page
EnglishDeutschEspañolFrançais日本語한국어PortuguesePусский简体中文繁體中文

Solaris Cluster Express 12/08 Release Notes

 These release notes contain additions, changes, and corrections to information in the Sun Cluster 3.2 documentation as they apply to Solaris™ Cluster Express and Solaris Cluster Express, Geographic Edition with the Open HA Cluster project. Information in the Sun Cluster 3.2 documentation set is valid with code that is provided in Solaris Cluster Express and Solaris Cluster Express, Geographic Edition, and the Open HA Cluster project, unless otherwise stated here.

• Support Changes
• New Features
• Restrictions and Requirements
• Known Issues and Workarounds

Support Changes

Solaris OS - Solaris Cluster Express now runs on Solaris Express Community Edition Build 101a.

back to top

New Features

Solaris Cluster Express

 Solaris Cluster Express has no new features at this time.

back to top

Restrictions and Requirements

 Solaris Cluster Express has no restrictions and no requirements at this time.

back to top

Known Issues and Workarounds

The following entries describe workarounds to unresolved Solaris Cluster Express and Solaris Cluster Express, Geographic Edition bugs. These workarounds will be removed from these Release Notes as fixes become available in updated versions of the Solaris Cluster Express and Solaris Cluster Express, Geographic Edition code.

[zh_CN]:result of "system requirements checking" is wrong (6495984)

Problem Summary: When you use the Java Enterprise System (JES) Installer to install Sun Cluster, the software that checks the system requirements incorrectly reports that the swap space is 0MB in the Simplified Chinese and Traditional Chinese locales.

Workaround: Ignore this reported information.

 In these locales, you can run the following command to determine the correct swap space:

# df -h | grep swap

Required steps if Solaris secure by default option is enabled need documentation (6558275)

Problem Summary: During installation of Solaris Express, the setting of a restricted network profile disables external access to two network services that Solaris Cluster Express functionality uses:

• The remote procedure call (RPC) communication service, which is required for cluster communication
• The Sun Java™ Web Console service, which is required to use the Cluster Manager GUI

Workaround: Restore external access to RPC communication and optionally to the Sun Java Web Console.

1. Use the following commands to restore external access to RPC communication:
   # svccfg
    svc:> select network/rpc/bind
    svc:/network/rpc/bind> setprop config/local_only=false
    svc:/network/rpc/bind> quit
    # svcadm refresh network/rpc/bind:default
    # svcprop network/rpc/bind:default | grep local_only
    The output of the last command should show that the local_only property is now set to false.
2. (Optional) Use the following commands to restore external access to the Sun Java Web Console:
   # svccfg
    svc:> select system/webconsole
    svc:/system/webconsole> setprop options/tcp_listen=true
    svc:/system/webconsole> quit
    # /usr/sbin/smcwebserver restart
    # netstat -a | grep 6789
    The output of the last command should return an entry for 6789, which is the port number used to connect to the Sun Java Web Console.

Multiple DATS tests are either uninitiated or unresolved (6571388)

Problem Summary: Some Data Service Automated Test Suite (DATS) tests might fail as UNINITIATED or UNRESOLVED because a resource group that is being queried is not yet fully online. This problem is caused by a timing issue.

Workaround: No workaround is currently available.

callers of meta_getdnp_bydevid() should do so correctly (6725904)

Problem Summary: Because the code in meta_set.c does not now correctly handle, under some conditions, the meta_getdnp_bydevid() function's returning NULL, the metainit command produces a segmentation fault and core dump.

Workaround: No workaround is currently available.

Unable to Run DATS due to server connection closed Error (6778938)

Problem Summary: Because the dtcc.c function issues a server connection closed error, you cannot run Data Services Automated Test Suite (DATS) tests.

Workaround: No workaround is currently available.