Saturday Nov 19, 2011

The premier support for Sun Cluster 3.1 ended

In October 2011 the premier support for Sun Cluster 3.1 ended. See details in Oracle Lifetime Support Policy for Oracle and Sun System Software document. There no 'Extended Support' and the 'Sustaining Support Ends' is indefinite.

But for indefinite 'Sustaining Support' I like to point out from the mentioned document (version Sept. 2011) on page 5:

Sustaining Support does NOT include:
* New program updates, fixes, security alerts, general maintenance releases, selected functionality releases and documentation updates or upgrade tools
* Certification with most new third-party products/versions and most new Oracle products
* 24 hour commitment and response guidelines for Severity 1 service requests
*Previously released fixes or updates that Oracle no longer supports

This means Solaris 10 9/10 update9 is the last qualified release for Sun Cluster 3.1. So, Sun Cluster 3.1 is not qualified on Solaris 10 8/11 Update10. Furthermore there is an issue around with SVM patch 145899-06 or higher. This SVM patch is part of Solaris 10 8/11 Update10. The 145899-06 is the first released patch of this number, therefore the support for Sun Cluster 3.1 ends with the previous SVM patches 144622-01 and 139967-02. For details about the known problem with SVM patch 145899-06 please refer to doc 1378828.1.

Further this means you should freeze (no patching, no upgrade) your Sun Cluster 3.1 configuration not later than Solaris 10 9/10 update9. Or even better plan an upgrade to Solaris Cluster 3.3 now to get back to full support.

For general patch updates the 'Critical Patch Update July 2011 for Solaris 10 SPARC' is last working and supported for Sun Cluster 3.1.

Sunday May 07, 2006

Patching to Sun Cluster 3.1 Update4

Patching a Sun Cluster 3.1 on Solaris 8 or Solaris 9 is not always straight forward. Especially if you install the Sun Cluster core patch which is equivalent to Sun Cluster 3.1 8/05 aka Update4 release.

The following patches are equivalent to Sun Cluster 3.1 8/05 aka Update4:
Solaris 9: 117949-12 or higher
Solaris 9_x86: 117909-12 or higher
Solaris 8: 117950-12 or higher

If you install a mentioned SC core patch without to shutdown the whole cluster then patching a node is similar to rolling upgrade. It is also called "Rebooting Patch (Node) procedure". For these procedures it is a requirement to have the -11 revision of the SC core patch installed and active. Active means you need to install -11 revision of the patch and reboot the nodes. If the -11 SC core patch is not installed AND active then you will hit the bug 6210440 and your whole cluster is going down within patch installation. The issue is documented on several places but still many Sun Cluster 3.1 will get affected. Therefore never forget to read the special install instructions of these patches.

Beware if you use TLP (Traffic Light Patchmanagement) only one revision of the SC core patch is in the patchset. If the patchset include the revision -12 or higher then you should have an active -11 SC core patch befor you install the TLP patchset.

It is not necessary to look to the Solaris 10 SC core patches because Sun Cluster 3.1 8/05 is the first release which support Solaris 10. But I like to mention, it is highly recommended to use Solaris 10 1/06 aka Update1 for Sun Cluster 3.1 8/05 on Solaris 10.

Thursday Mar 30, 2006

Quota with Sun Cluster

Do you like to use quota with Sun Cluster 3.1?

First of all take care of the following restrictions:

  • You can use quota only within SUNW.HAStoragePlus resource.

  • You can use it only with a failover filesystem (FFS).

  • Quotas are not working on global mounted filesystems.

To configure the quota you need to add the mount option “quota” or “rq” to the FFS in the /etc/vfstab. Furthermore you need to configure the SUNW.HAStoragePlus for the FFS.

Simple example:

  1. Register the resource type
    # scrgadm -a -t SUNW.HAStoragePlus

  2. Create a resource group
    # scrgadm -a -g FFSq-rg

  3. Add filesystem to vfstab
    # vi /etc/vfstab (on all nodes)
    /dev/md/nfsset/dsk/d0 /dev/md/nfsset/rdsk/d0 /quotafs ufs 2 no logging,rq

  4. Create resource for HAStoragePlus
    # scrgadm -a -j hastp-rs -g FFSq-rg -t SUNW.HAStoragePlus -x FileSystemMountpoint=/quotafs -x AffinityOn=TRUE

  5. Switch the resource group online
    # scrgadm -Z -g FFSq-rg

  6. Configure the quotas
    # touch quotas
    # chmod 600 quotas
    # edquota -v USER
    # quotaon -av

  7. Test the switchover of the resource group
    # scswitch -z -g FFSq-rg -h

After the switch of the filesystem /quotafs the quota will be started automatically from the SUNW.HAStoragePlus resource. To configure your setup of the quota you can refer to the quota manpage.


I'm still mostly blogging around Solaris Cluster and support. Independently if for Sun Microsystems or Oracle. :-)


« July 2016