Home | History | Annotate | Download | only in man1m
 te
 CDDL HEADER START

 The contents of this file are subject to the terms of the
 Common Development and Distribution License (the "License"). 
 You may not use this file except in compliance with the License.

 You can obtain a copy of the license at CDDL.txt
 or http://www.opensolaris.org/os/licensing.
 See the License for the specific language governing permissions
 and limitations under the License.

 When distributing Covered Code, include this CDDL HEADER in each
 file and include the License file at CDDL.txt.
 If applicable, add the following below this CDDL HEADER, with the
 fields enclosed by brackets "[]" replaced with your own identifying
 information: Portions Copyright [yyyy] [name of copyright owner]

 CDDL HEADER END
 Copyright 2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms
 scversions 1M "17 Aug 2007" "Sun Cluster 3.2" "System Administration Commands"
 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 information 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:


.na
-c
.ad


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 correctly 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 functionality 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 example, if that node is down for maintenance), the internal protocols of the cluster are upgraded to the highest possible versions.
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

.na
0
.ad


Success





.na
non-zero
.ad


Failure




 ATTRIBUTES

See attributes(5) for descriptions of the following attributes:







ATTRIBUTE TYPEATTRIBUTE VALUE
AvailabilitySUNWsczu
Interface StabilityEvolving



 SEE ALSO

scinstall(1M)