Check if zone cluster can be created # cluster show-netprops
to change number of zone clusters use
# cluster set-netprops -p num_zoneclusters=12
Note: 12 zone clusters is the default, values can be customized!

Create config file (zc1config) for zone cluster setup e.g:

Configure zone cluster# clzc configure -f zc1config zc1
Note: If not using the config file the configuration can also be done manually # clzc configure zc1

Check zone configuration# clzc export zc1

Verify zone cluster# clzc verify zc1
Note: The following message is a notice and comes up on several clzc commands
Waiting for zone verify commands to complete on all the nodes of the zone cluster "zc1"...

Install the zone cluster# clzc install zc1
Note: Monitor the consoles of the global zone to see how the install proceed! (The output is different on the nodes) It's very important that all global cluster nodes have installed the same set of ha-cluster packages!

Appendix: To delete a zone cluster do:
# clrg delete -Z zc1 -F +
Note: Zone cluster uninstall can only be done if all resource groups are removed in the zone cluster. The command 'clrg delete -F +' can be used in zone cluster to delete the resource groups recursively.# clzc halt zc1
# clzc uninstall zc1
Note: If clzc command is not successful to uninstall the zone, then run 'zoneadm -z zc1 uninstall -F' on the nodes where zc1 is configured# clzc delete zc1

How the problem occur?
After the installation of Sun Cluster 3.2 1/09 Update2 product with the java installer it's necessary to run the #scinstall command. If choose "Custom" installation instead of "Typical" installation then it's possible to change the default of the netmask of cluster interconnect. The following questions come up within the installation procedure if answering the default netmask question with 'no'.

Example scinstall:
Is it okay to accept the default netmask (yes/no) [yes]? no
Maximum number of nodes anticipated for future growth [64]? 4
Maximum number of private networks anticipated for future growth [10]? Maximum number of virtual clusters expected [12]? 0
What netmask do you want to use [255.255.255.128]? Prevent the issue by answering the virtual clusters question with '1' or other serious consideration to future growth potential if necessary. Do NOT answer the virtual clusters question with '0'!

Example of the whole scinstall log when corrupted ccr occur:

In the /etc/cluster/ccr/global/infrastructure file the error can be found by an empty entry for cluster.properties.private_netmask. Furthermore some other lines are not reflect the correct values for netmask as choosen within scinstall.Wrong infrastructure file:
cluster.state enabled
cluster.properties.cluster_id 0x49F82635
cluster.properties.installmode disabled
cluster.properties.private_net_number 172.16.0.0cluster.properties.cluster_netmask 255.255.248.0cluster.properties.private_netmask
cluster.properties.private_subnet_netmask 255.255.255.248
cluster.properties.private_user_net_number 172.16.4.0
cluster.properties.private_user_netmask 255.255.254.0
cluster.properties.private_maxnodes 6
cluster.properties.private_maxprivnets 10cluster.properties.zoneclusters 0
cluster.properties.auth_joinlist_type sys

Workaround if problem already occured:
1.) Boot all nodes in non-cluster-mode with 'boot -x'
2.) Change the wrong values of /etc/cluster/ccr/global/infrastructure on all nodes. See example above.
3.) Write a new checksum for all infrastructure files on all nodes. Use -o (master file) on the node which is booting up first.
scnode1 # /usr/cluster/lib/sc/ccradm -i /etc/cluster/ccr/global/infrastructure -o
scnode2 # /usr/cluster/lib/sc/ccradm -i /etc/cluster/ccr/global/infrastructure
scnode1 # /usr/cluster/lib/sc/ccradm -i /etc/cluster/ccr/global/infrastructure
scnode2 # /usr/cluster/lib/sc/ccradm -i /etc/cluster/ccr/global/infrastructure
4.) first reboot scnode1 (master infrastructure file) into cluster, then the other nodes.
This is reported in bug 6825948.

Update 17.Jun.2009:
The -33 revision of the Sun Cluster core patch is the first released version which fix this issue at installation time.126106-33 Sun Cluster 3.2: CORE patch for Solaris 10 126107-33 Sun Cluster 3.2: CORE patch for Solaris 10_x86