scsetup(1m) [opensolaris man page]
scsetup(1M) System Administration Commands scsetup(1M) NAME
scsetup - interactive cluster configuration tool SYNOPSIS
scsetup [-f logfile] DESCRIPTION
Note - 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 infor- mation about the object-oriented command set, see the Intro(1CL) man page. The scsetup command provides the following configuration capabilities, depending on what state the cluster is in when you issue the com- mand: o When you run the scsetup command at post-installation time, the command performs initial setup tasks, such as configuring quorum devices and resetting the installmode property. If you did not use automatic quorum configuration when you created the cluster, run the scsetup command immediately after the cluster is installed. Ensure that all nodes have joined the cluster before you run the scsetup command and reset the installmode property. If you used automatic quorum configuration when you created the cluster, you do not need to run the scsetup command after clus- ter installation. The automatic quorum configuration feature also resets the installmode property of the cluster. o When you run the command during normal cluster operation, the scsetup command provides a menu-driven utility. You can use this utility to perform most ongoing cluster-administration tasks. o When you issue the command from a node that is in noncluster mode, the scsetup utility provides a menu-driven utility for chang- ing and displaying the private IP address range. You must reboot all nodes into noncluster mode before you start this form of the scsetup utility. You can issue the scsetup command from any node in the cluster. You can use this command only in the global zone. OPTIONS
The following options are supported: -f logfile Specifies the name of a log file to which commands can be logged. If you specify this option, most command sets that the scsetup utility generates are run and logged, or only logged, depending on user responses. ATTRIBUTES
See attributes(5) for descriptions of the following attributes. +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cltelemetryattribute(1CL), cldevicegroup(1CL), clnode(1CL), clquorum(1CL), clreslogicalhostname(1CL), clresourcegroup(1CL), clresourcetype(1CL), clressharedaddress(1CL), cluster(1CL), Sun Cluster 3.2 18 Jul 2006 scsetup(1M)
Check Out this Related Man Page
scversions(1M) System Administration Commands scversions(1M) NAME
scversions - Sun Cluster version management SYNOPSIS
scversions [-c] DESCRIPTION
Note - 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 infor- mation about the object-oriented command set, see the Intro(1CL) man page. The scversions command commits the cluster to a new level of functionality after a rolling-upgrade to new Sun Cluster software. With no arguments, the scversions command prints a message indicating whether a commitment is needed. OPERANDS
The following operands are supported: -c Commit the set of nodes that are currently active members of the cluster to the highest possible level of functionality. When you upgrade a node (either through upgrade to a new release of the product or by application of a patch) and boot it back into the cluster, some of the internal protocols on that node might have to run at lower versions in order to cooperate cor- rectly with other nodes in the cluster. When the cluster is in this state, some administrative actions might be disabled and some new functionality introduced in the upgrade might be unavailable. When you run this command once from any node after all nodes are upgraded, the cluster switches to the highest versions of internal protocols possible. Assuming that all nodes have the same Sun Cluster software installed at that time, all new func- tionality becomes available and any administrative restrictions are removed. If a node that has not been upgraded is an active member of the cluster at the time you run the -c option to scversions, the command has no effect because the cluster is already running at the highest possible level of functionality. If a node has not been upgraded and is not an active member of the cluster when you run the -c option to scversions (for exam- ple, if that node is down for maintenance), the internal protocols of the cluster are upgraded to the highest possible ver- sions. You might have to upgrade the node that was not an active member of the cluster to enable it to rejoin the cluster. EXIT STATUS
0 Success non-zero Failure ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
scinstall(1M) Sun Cluster 3.2 17 Aug 2007 scversions(1M)