Sun announces the availability of Solaris Cluster 3.2 11/09, the best high availability platform for the Solaris OS with new innovative features, addressing your high availability needs for end -to-end business solutions in a virtualized or traditional environment.
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Hi,
Is it possible to have a Solaris cluster of 2 nodes at SITE-A using SVM and creating metaset using say 2 LUNs (on SAN). Then replicating these 2 LUNs to remote site SITE-B via storage based replication and then using these LUNs by importing them as a metaset on a server at SITE-B which is... (0 Replies)
Hi All,
i have 2 zone
1- Oracle DB Primary Server
2- Oracle DB Secondary Server
i make script do r sync between this 2 zones
but i am planning to do is
make Solaris cluster between this zones
if the primary Server field the secondary server up and running automatically without any... (1 Reply)
Hi,
I am trying to install Solaris cluster with Solaris10 and Cluster suite 3.2 2/08. After going through customer configuration in "scinstall" utility, I am facing a problem.
At the time of selecting 2nd node's file system type, I am giving input as /globaldevices which is very much part of... (9 Replies)
Hi All ,
I have two Solaris boxes of UltraAX-i2 and Sun-Fire-V240,
Is it possible to cluster those boxes?
Waiting for your reply,
Thanks
Parshuram (2 Replies)
Simple question:
After applying a cluster patch to a sun solaris box I am left with a root volume 81% full. I could run through the hassle of resizing the slices which is way too much work for a Ultra 5 running DNS only.
Is there a way to clean up the /var/sadm/pkg area, aka dump the save info. (5 Replies)
scgdevs(1M) System Administration Commands scgdevs(1M)NAME
scgdevs - global devices namespace administration script
SYNOPSIS
/usr/cluster/bin/scgdevs
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 scgdevs command manages the global devices namespace. The global devices namespace is mounted under the /global directory and consists
of a set of logical links to physical devices. As the /dev/global directory is visible to each node of the cluster, each physical device is
visible across the cluster. This fact means that any disk, tape, or CD-ROM that is added to the global-devices namespace can be accessed
from any node in the cluster.
The scgdevs command enables you to attach new global devices (for example, tape drives, CD-ROM drives, and disk drives) to the global-
devices namespace without requiring a system reboot. You must run the devfsadm command before you run the scgdevs command.
Alternatively, you can perform a reconfiguration reboot to rebuild the global namespace and attach new global devices. See the boot(1M) man
page for more information about reconfiguration reboots.
You must run this command from a node that is a current cluster member. If you run this command from a node that is not a cluster member,
the command exits with an error code and leaves the system state unchanged.
You can use this command only in the global zone.
You need solaris.cluster.system.modify RBAC authorization to use this command. See the rbac(5) man page.
You must also be able to assume a role to which the Sun Cluster Commands rights profile has been assigned to use this command. Authorized
users can issue privileged Sun Cluster commands on the command line from the pfsh, pfcsh, or pfksh profile shell. A profile shell is a spe-
cial kind of shell that enables you to access privileged Sun Cluster commands that are assigned to the Sun Cluster Commands rights profile.
A profile shell is launched when you run the su command to assume a role. You can also use the pfexec command to issue privileged Sun Clus-
ter commands.
EXIT STATUS
The following exit values are returned:
0 The command completed successfully.
nonzero An error occurred. Error messages are displayed on the standard output.
FILES
/devices Device nodes directory
/global/.devices Global devices nodes directory
/dev/md/shared Solaris Volume Manager metaset directory
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsczu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO pfcsh(1), pfexec(1), pfksh(1), pfsh(1), Intro(1CL), cldevice(1CL), boot(1M), devfsadm(1M), su(1M), did(7)
Sun Cluster System Administration Guide for Solaris OS
NOTES
The scgdevs command, called from the local node, will perform its work on remote nodes asynchronously. Therefore, command completion on the
local node does not necessarily mean that the command has completed its work clusterwide.
This document does not constitute an API. The /global/.devices directory and the /devices directory might not exist or might have different
contents or interpretations in a future release. The existence of this notice does not imply that any other documentation that lacks this
notice constitutes an API. This interface should be considered an unstable interface.
Sun Cluster 3.2 10 Apr 2006 scgdevs(1M)