This section describes changes to the Sun Cluster command interfaces that might cause user scripts to fail.
Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more information about the object-oriented command set, see the Intro(1CL) man page. For a list of object-oriented commands for common Sun Cluster procedures, see the Sun Cluster Quick Reference.
The following options to the scinstall command have changed in the Sun Cluster 3.2 release:
The -d option has been removed from use with the -i option. The scinstall command no longer performs installation of Sun Cluster software packages. Instead, use the installer command. See How to Install Sun Cluster Framework and Data-Service Software Packages in Sun Cluster Software Installation Guide for Solaris OS for more information.
The -d option is still valid with the -a, -c, and -u options.
The -k option is no longer necessary. It is still provided only for backwards compatibility with user scripts that use this option.
The -M option has been removed from use. Instead, use the appropriate patch management tool for the version of the Solaris OS that your cluster runs. See Patches and Required Firmware Levels for more information.
The -q option of the scconf command has been modified to distinguish between shared local quorum devices (SCSI) and other types of quorum devices (including NetApp NAS devices). Use the name suboption to specify the name of the attached shared-storage device when adding or removing a shared quorum device to or from the cluster. This suboption can also be used with the change form of the command to change the state of a quorum device. The globaldev suboption can still be used for SCSI shared-storage devices, but the name suboption must be used for all other types of shared storage devices. For more information about this change to scconf and working with quorum devices, see scconf(1M), scconf_quorum_dev_netapp_nas(1M), scconf_quorum_dev_netapp_nas(1M), and scconf_quorum_dev_scsi(1M).
It is no longer necessary to modify the Network_resources_used resource property directly. Instead, use the Resource_dependencies property. The RGM automatically updates the Network_resources_used property based on the settings of the Resource_dependencies property. For more information about the current uses of these two resource properties, see r_properties(5).