Wiki code for Release Notes

Hide Line numbers
1: HA Clusters Quick Links
2: 
3: ; [[Download>>http://dlc.sun.com/osol/ohac/downloads/current/]]
4: : Download the latest Open High Availability Cluster source
5: ; [[Participate>>http://opensolaris.org/jive/forum.jspa?forumID=195]]
6: : Join the OpenSolaris HA Clusters discussions
7: ; [[Contribute>>Community Group ha-clusters.contribute]]
8: : Contribute to Open High Availability Cluster
9: 
10: **Translation for this page**
11: English日本語简体中文
12: 
13: = Open HA Cluster 2009.06 Release Notes
14: 
15: These release notes contain additions, changes, and corrections to information in the //[[Open HA Cluster Installation Guide>>http://docs.sun.com/app/docs/doc/820-7821]]// and [[Sun Cluster 3.2 documentation>>http://docs.sun.com/app/docs/prod/sun.cluster32]] as they apply to OpenSolaris and Open HA Cluster software. Information in the Sun Cluster 3.2 documentation set is valid with code that is provided in Open HA Cluster software, unless otherwise stated here.
16: 
17: * [[Support Changes>>#support]]
18: * [[New Features>>#newfeatures]]
19: * [[Restrictions and Requirements>>#restrictions]]
20: * [[Compatibility Issues>>#compatibility]]
21: * [[Known Issues and Workarounds>>#bugs]]
22: 
23: == Support Changes
24: 
25: **Open Solaris** - Open HA Cluster 2009.06 software runs only on OpenSolaris 2009.06 (build 111) software.
26: 
27: **Platforms** - Open HA Cluster 2009.06 software runs on either SPARC based platforms or x86 based platforms. All nodes in a cluster must run on the same platform.
28: 
29: **Data Services** - The following Sun Cluster data services are fully supported in an Open HA Cluster 2009.06 configuration:
30: 
31: * HA-Apache
32: * HA-Apache Tomcat
33: * HA-Containers
34: * HA-DHCP
35: * HA-DNS
36: * HA-Glassfish (but not HA-Sun Java Application Server)
37: * HA-Kerberos
38: * HA-MySQL
39: * HA-NFS
40: * HA-Samba
41: 
42: [[back to top>>#top]]
43: 
44: == New Features
45: 
46:  Open HA Cluster 2009.06 software introduces the following new features.
47: 
48: === Virtual Private Interconnect
49: 
50:  As an alternative to using physical cables between cluster nodes to handle private-network communication, you can now instead configure virtual network interfaces (VNICs) for this purpose. You create VNICs over public-network adapters to transmit the private-network traffic. This configuration also creates an abstraction of having physical adapters handling the public-network traffic to the rest of the cluster. You can optionally configure IPsec for the private-interconnect interface to provide secure TCP/IP communication.
51: 
52: === COMSTAR based iSCSI Storage
53: 
54:  As an alternative to sharing storage between cluster nodes, you can configure a failover ZFS file system on local storage using COMSTAR.
55: 
56: [[back to top>>#top]]
57: 
58: == Restrictions and Requirements
59: 
60: **Feature restrictions** - The following features that are normally available in the Sun Cluster software product are not available in an Open HA Cluster 2009.06 configuration:
61: 
62: * Campus clusters and replication
63: * Closed-source binaries, such as HA-Oracle, Oracle RAC, and HA-Sybase
64: * Cluster Control Panel including cconsole (use the pconsole IPS package instead)
65: * Geographic Edition
66: * NAS quorum devices
67: * scsnapshot
68: * Solaris Containers non-global zones
69: * Sun Cluster Manager GUI, including the data-service wizards (use the clsetup utility or the command line instead)
70: * Sun Cluster module to Sun Management Center
71: * Sun Storage Archive Manager (SAM-QFS)
72: * Telemetry attributes, or system resource monitoring
73: * Upgrade to future releases
74: * Veritas Volume Manager and Veritas File System
75: 
76: **Supported hardware** - The following servers and storage arrays are supported in an Open HA Cluster 2009.06 configuration:
77: 
78: * SPARC based platforms
79: ** Sun SPARC Enterprise M3000 Server
80: ** Sun SPARC Enterprise T5120 Server
81: * x86 based platforms
82: ** Sun Fire x4140 Server
83: ** Sun Fire x4170 Server
84: * Storage arrays
85: ** StorageTek 2540 Array
86: ** Sun Storage J4400 Array (SAS)
87: 
88: **Memory Requirements** - Open HA Cluster 2009.06 software requires the following memory requirements for every cluster node:
89: 
90: * Minimum of 1 Gbyte of physical RAM (2 Gbytes typical)
91: * Minimum of 6 Gbytes of available hard drive space
92: 
93: Actual physical memory and hard drive requirements are determined by the applications that are installed. Consult the application’s documentation or contact the application vendor to calculate additional memory and hard drive requirements.
94: 
95: **Upgrade of OpenSolaris** - A system that is installed with Open HA Cluster software cannot be upgraded to another version of OpenSolaris software while the Open HA Cluster software is still installed. Specifically, you cannot switch the opensolaris.org publisher to pkg.opensolaris.org/dev/ and run the pkg image-update command. This is because the cluster packages are tied to a specific OpenSolaris version. To switch to pkg.opensolaris.org/dev, you must uninstall Open HA Cluster software first.
96: 
97:  This restriction does not apply to SRUs. You can successfully apply OpenSolaris SRUs without first uninstalling Open HA Cluster software.
98: 
99: [[back to top>>#top]]
100: 
101: == Compatibility Issues
102: 
103:  This section describes information about Open HA Cluster 2009.06 compatibility issues.
104: 
105: === iSCSI Initiator Is Not Generating Events When Target Device Is Reconnected (6822867)
106: 
107: **Problem Summary: **The iSCSI initiator code generates events on the first connection to the target device. When the target device node is dead, the access from the initiator fails with ENOENT. When the target device node is available, the access is successful, but the iSCSI initiator code does not generate events on the target device availability. The lack of proper events by iSCSI initiator prevents ZFS autodetect and requires manual intervention to inform ZFS that the device is online.
108: 
109: **Workaround: **Issue an explicit online request for the device.
110: 
111: {{{
112: phys-schost# **zpool online //iscsi_pool_name// //rejoiner_iscsi_device//**
113: }}}
114: 
115:  For example, the following shows the status where ZFS has not detected the device c7t31d0s0, which is not accessible:
116: 
117: {{{
118: phys-schost# **zpool status**
119:   pool: ha_iscsi_pool
120:  state: DEGRADED
121: status: One or more devices could not be opened.  Sufficient replicas exist for
122:         the pool to continue functioning in a degraded state.
123: action: Attach the missing device and online it using ’zpool online’.
124:    see: http://www.sun.com/msg/ZFS-8000-2Q
125:  scrub: none requested
126: config:
127: 
128:         NAME                     STATE     READ WRITE CKSUM
129:         ha_iscsi_pool            DEGRADED     0     0     0
130:           mirror                 DEGRADED     0     0     0
131:             1930536541678814621  UNAVAIL      0     0     0  was /dev/dsk/c7t31d0s0
132:             c7t32d0              ONLINE       0     0     0
133: 
134: }}}
135: 
136:  The following command would explicitly request that the device c7t31d0s0 be made accessible by ZFS:
137: 
138: {{{
139: phys-schost# **zpool online ha_iscsi_pool c7t31d0s0**
140: }}}
141: 
142: [[back to top>>#top]]
143: 
144: === cacaocsc Core Dump Under IPS Packaging (6754753)
145: 
146: **Problem Summary: **Problems with common agent container (cacaocsc) installation might cause a core dump if a command that relies on cacaocsc is issued.
147: 
148: **Workaround: **Check whether a fix to OpenSolaris 2009.06 for this bug is available. If not, do not run the following commands:
149: 
150: * cluster check or cluster list-checks (However, if the node is in noncluster mode, it is safe to use these commands.)
151: * sceventmib (Note that this feature is not officially supported in this release.)
152: * sctelemetry (Note that this feature is not officially supported in this release.)
153: 
154: [[back to top>>#top]]
155: 
156: == Known Issues and Workarounds
157: 
158: The following entries describe workarounds to unresolved Open HA Cluster 2009.06 bugs.
159: 
160: === Cannot Boot a Node After Running clnode remove on x86 (6844029)
161: 
162: **Problem Summary: **After removing an x86 based node from a cluster by using the clnode remove -F command, the node cannot be rebooted. The reboot operation fails with the following errors:
163: 
164: {{{
165: Error: /etc/cluster/ccr/global/infrastructure does not exist
166: UNRECOVERABLE ERROR: /etc/cluster/ccr/infrastructure file is corrupted
167: Please reboot in noncluster mode(boot -x) and Repair
168: Press any key to reboot.
169: }}}
170: 
171: **Workaround: **Reboot the node in noncluster mode by using the GRUB menu to add -x to the kernel boot parameter command. See Step 4 in [["How to Uninstall Open HA Cluster Software">>http://docs.sun.com/app/docs/doc/820-7821/gilpy?a=view]] in the //Open HA Cluster Installation Guide// for instructions to boot an x86 machine into noncluster mode.
172: 
173:  This change does not persist over the system boot. The next time you need to reboot the node, it will attempt to boot into cluster mode unless you again add the -x option to the kernel boot parameter command.
174: 
175: [[back to top>>#top]]
176: 
177: === Node Panicked at Install Time Due to Wrong netmask When Non-Default Network Is Selected (6842823)
178: 
179: **Problem Summary: **If during cluster establishment a private IP address other than the default address is specified, an invalid netmask is configured. This causes the node to panic.
180: 
181: **Workaround: **Use the default IP address for the private interconnect. If you cannot use the default IP address, choose an IP address whose third byte is a number from 0 to 191. For example, the IP address 192.168.191.0 would be acceptable, but 192.168.208.0 would not be acceptable and would trigger this bug.
182: 
183: [[back to top>>#top]]
184: 
185: === Part of Localization Messages Are Not Translated (6842548)
186: 
187: **Problem Summary: **The Open HA Cluster 2009.06 release uses localized user-visible text that was translated for the Sun Cluster 3.2 1/09 release. Some new or modified texts for the OHAC release are not localized and is therefore only available in English. In some cases, displayed text might have a mixture of translated text and English text.
188: 
189: **Workaround: **To view texts in all English, set the LC_MESSAGES environment variable to C.
190: 
191:  In sh, ksh, bash:
192: 
193: {{{
194: # **LC_MESSAGES=C; export LC_MESSAGES**
195: }}}
196: 
197:  In csh:
198: 
199: {{{
200: # **setenv LC_MESSAGES C**
201: }}}
202: 
203: [[back to top>>#top]]
204: 
205: === scinstall Fails on rsh Following "clnode remove" of All Nodes of the Cluster (6841982)
206: 
207: **Problem Summary: **After the clnode remove command is run on all installed nodes of a cluster and the software is reinstalled, the /etc/cluster/remoteconfiguration file does not get reinstalled. The absence of this file prevents the scinstall utility from being able to remotely access other nodes to configure them as cluster nodes.
208: 
209: **Workaround: **Before you start the scinstall utility, run the following command on each node where you previously ran the clnode remove command:
210: 
211: {{{
212: phys-schost# **touch /etc/cluster/remoteconfiguration**
213: }}}
214: 
215: [[back to top>>#top]]
216: 
217: === HAStoragePlus Unable to Import zpool After Pool Is Re-Created (6836718)
218: 
219: **Problem Summary: **When a ZFS storage pool is destroyed and re-created with the same name but with different devices, HAStoragePlus might fail to bring online a resource that contains that ZFS pool. The following failure message is displayed:
220: 
221: {{{
222: 
223: The pool //pool_name// failed to import using cachefile //pool_cachefile_location//
224: }}}
225: 
226: **Workaround: **Use the following command to delete the CCR cache file, then retry the operation:
227: 
228: {{{
229: # **/usr/cluster/lib/sc/hasp_util delete_pool_ccr_cachefile -f ** //pool_name//
230: }}}
231: 
232: [[back to top>>#top]]
233: 
234: === cfgchk Core Dumps With cluster check (6835179 )
235: 
236: **Problem Summary: **Attempts to run the cluster check or cluster list-checks command fails and dumps core. This problem is attributable to the OpenSolaris CR 6754753, cacaoscs core dump under IPS packaging.
237: 
238: **Workaround: **There is no workaround. When CR 6754753 is fixed, apply the SRU that contains the code fix.
239: 
240: [[back to top>>#top]]
241: 
242: === ha-cluster-agent-builder Pulls In Too Many depend Packages (6835118)
243: 
244: **Problem Summary: **When the Agent Builder ha-cluster-agent-builder package group is installed on a non-cluster machine, the many SMF services that are started on the machine expect the machine to be a cluster node. Error messages such as the following are displayed:
245: 
246: {{{
247: NOTICE: Can’t open /etc/cluster/nodeid
248: NOTICE: BOOTING IN NON CLUSTER MODE
249: }}}
250: 
251: **Workaround: **The error messages are safe to ignore. Alternatively, install the Agent Builder group package on a cluster node to use as a development environment.
252: 
253: [[back to top>>#top]]
254: 
255: === colorado: Prevent Cluster Package Contents Installation in Non-Global Zones (6829537)
256: 
257: **Problem Summary: **Open HA Cluster software does not work in ipkg brand non-global zones on OpenSolaris.
258: 
259: **Workaround: **There is no workaround. Do not install Open HA Cluster software in ipkg brand non-global zones. Install Open HA Cluster software only in the global zone.
260: 
261: [[back to top>>#top]]
262: 
263: === NOTICE: softmac: received DL_ERROR_ACK to DL_BIND_ACK; DLPI errno 0x7fffec94, UNIX errno 1 (6822706)
264: 
265: **Problem Summary: **When clprivnet receives probes from softmac, error messages are generated.
266: 
267: **Workaround: **The error messages are safe to ignore. However, clprivnet does not currently work with softmac.
268: 
269: [[back to top>>#top]]
270: 
271: === Slow HAStoragePlus Failover Time Following Hard Node Death in HA-ZFS Over iSCSI Configuration (6817564)
272: 
273: **Problem Summary: **An HAStoragePlus resource that contains a ZFS storage pool and is created on iSCSI devices takes longer than usual to come online during failover. The delay is due to the iSCSI device retry-access timeout, which is around 3 minutes, that occurs if an iSCSI target is not accessible during a zpool import operation.
274: 
275: **Workaround: **There is no workaround to avoid the problem. OpenSolaris CR 6497777 is filed to request code changes that would allow the user to tune the iSCSI device access-retry timeout.
276: 
277: [[back to top>>#top]]
278: 
279: === errors: rcm_daemon[1040]: IP: get_link_resource(clprivnet0) failed (6814991)
280: 
281: **Problem Summary: **During a cluster node reboot, error messages similar to the following might appear:
282: 
283: {{{
284: 
285: Mar  9 11:11:35 phys-schost-1 rcm_daemon[1040]: IP: get_link_resource(clprivnet0) failed
286: Mar  9 11:11:35 phys-schot-1 rcm_daemon[1040]: IP: get_link_resource for clprivnet0 error(object not found)
287: 
288: }}}
289: 
290: **Workaround: **The error messages are safe to ignore.
291: 
292: [[back to top>>#top]]
OpenSolaris

Top Menu

Wiki code for Release Notes

Search

Collectives

Community Group

Project

User Group

Subsites

Community Group ha-clusters Pages
