Setting up HACMP 6.1 on a two node cluster. The other node works fine and can start properly on STABLE state (VGs varied, FS mounted, Service IP aliased). However, the other node is always stuck on ST_JOINING state. Its taking forever and you can't stop the cluster as well or recover from script... (2 Replies)
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
Hey Admins,
I am running sun cluster 3.2 x86 on Vmware. I m facing an issue from 2 days..
One main node is continuously rebooting..... not sure... whats woring...
I just had change heartbeat timeout values on 1 this node... Now both node are just rebooting itself..seems panic..
Any... (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)
How can we add a shared zfs dataset between 2 zones on a same host. I have sun cluster 3.2 installed in a server which has 2 zones. I want to share a zfs data set between these 2 zones how can we do that ? (7 Replies)
How to change IP on Sun Cluster system?
I have a system based on SunCluster, now I want to change public IP (connect to LAN). I need your support. Thanks so much. (2 Replies)
Hello,
Under ksh I have to run a script on one of the nodes of a Solaris 8 cluster which at some time must execute a command on the alternate node:
# rsh <name> "command"
I have to implement this script on all the clusters of my company (a lot of...).
Fortunately, the names of the two nodes... (11 Replies)
scdpm(1M) System Administration Commands scdpm(1M)NAME
scdpm - manage disk path monitoring daemon
SYNOPSIS
scdpm [-a] {node | all}
scdpm -f filename
scdpm -m {[node | all][:/dev/did/rdsk/]dN | [:/dev/rdsk/]cNtXdY | all}
scdpm -n {node | all}
scdpm -p [-F] {[node | all][:/dev/did/rdsk/]dN | [/dev/rdsk/]cNtXdY | all}
scdpm -u {[node | all][:/dev/did/rdsk/]dN | [/dev/rdsk/]cNtXdY | all}
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 scdpm command manages the disk path monitoring daemon in a cluster. You use this command to monitor and unmonitor disk paths. You can
also use this command to display the status of disk paths or nodes. All of the accessible disk paths in the cluster or on a specific node
are printed on the standard output. You must run this command on a cluster node that is online and in cluster mode.
You can specify either a global disk name or a UNIX path name when you monitor a new disk path. Additionally, you can force the daemon to
reread the entire disk configuration.
You can use this command only in the global zone.
OPTIONS
The following options are supported:
-a
Enables the automatic rebooting of a node when all monitored disk paths fail, provided that the following conditions are met:
o All monitored disk paths on the node fail.
o At least one of the disks is accessible from a different node in the cluster.
You can use this option only in the global zone.
Rebooting the node restarts all resource and device groups that are mastered on that node on another node.
If all monitored disk paths on a node remain inaccessible after the node automatically reboots, the node does not automatically reboot
again. However, if any monitored disk paths become available after the node reboots but then all monitored disk paths again fail, the
node automatically reboots again.
You need solaris.cluster.device.admin role-based access control (RBAC) authorization to use this option. See rbac(5).
-F
If you specify the -F option with the -p option, scdpm also prints the faulty disk paths in the cluster. The -p option prints the cur-
rent status of a node or a specified disk path from all the nodes that are attached to the storage.
-f filename
Reads a list of disk paths to monitor or unmonitor in filename.
You can use this option only in the global zone.
The following example shows the contents of filename.
u schost-1:/dev/did/rdsk/d5
m schost-2:all
Each line in the file must specify whether to monitor or unmonitor the disk path, the node name, and the disk path name. You specify
the m option for monitor and the u option for unmonitor. You must insert a space between the command and the node name. You must also
insert a colon (:) between the node name and the disk path name.
You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5).
-m
Monitors the new disk path that is specified by node:diskpath.
You can use this option only in the global zone.
You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5).
-n
Disables the automatic rebooting of a node when all monitored disk paths fail.
You can use this option only in the global zone.
If all monitored disk paths on the node fail, the node is not rebooted.
You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5).
-p
Prints the current status of a node or a specified disk path from all the nodes that are attached to the storage.
You can use this option only in the global zone.
If you also specify the -F option, scdpm prints the faulty disk paths in the cluster.
Valid status values for a disk path are Ok, Fail, Unmonitored, or Unknown.
The valid status value for a node is Reboot_on_disk_failure. See the description of the -a and the -n options for more information
about the Reboot_on_disk_failure status.
You need solaris.cluster.device.read RBAC authorization to use this option. See rbac(5).
-u
Unmonitors a disk path. The daemon on each node stops monitoring the specified path.
You can use this option only in the global zone.
You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5).
EXAMPLES
Example 1 Monitoring All Disk Paths in the Cluster Infrastructure
The following command forces the daemon to monitor all disk paths in the cluster infrastructure.
# scdpm -m all
Example 2 Monitoring a New Disk Path
The following command monitors a new disk path.All nodes monitor /dev/did/dsk/d3 where this path is valid.
# scdpm -m /dev/did/dsk/d3
Example 3 Monitoring New Disk Paths on a Single Node
The following command monitors new paths on a single node. The daemon on the schost-2 node monitors paths to the /dev/did/dsk/d4 and
/dev/did/dsk/d5 disks.
# scdpm -m schost-2:d4 -m schost-2:d5
Example 4 Printing All Disk Paths and Their Status
The following command prints all disk paths in the cluster and their status.
# scdpm -p
schost-1:reboot_on_disk_failure enabled
schost-2:reboot_on_disk_failure disabled
schost-1:/dev/did/dsk/d4 Ok
schost-1:/dev/did/dsk/d3 Ok
schost-2:/dev/did/dsk/d4 Fail
schost-2:/dev/did/dsk/d3 Ok
schost-2:/dev/did/dsk/d5 Unmonitored
schost-2:/dev/did/dsk/d6 Ok
Example 5 Printing All Failed Disk Paths
The following command prints all of the failed disk paths on the schost-2 node.
# scdpm -p -F all
schost-2:/dev/did/dsk/d4 Fail
Example 6 Printing the Status of All Disk Paths From a Single Node
The following command prints the disk path and the status of all disks that are monitored on the schost-2 node.
# scdpm -p schost-2:all
schost-2:reboot_on_disk_failure disabled
schost-2:/dev/did/dsk/d4 Fail
schost-2:/dev/did/dsk/d3 Ok
EXIT STATUS
The following exit values are returned:
0 The command completed successfully.
1 The command failed completely.
2 The command failed partially.
Note -
The disk path is represented by a node name and a disk name. The node name must be the host name or all. The disk name must be the global
disk name, a UNIX path name, or all. The disk name can be either the full global path name or the disk name: /dev/did/dsk/d3 or d3. The
disk name can also be the full UNIX path name: /dev/rdsk/c0t0d0s0.
Disk path status changes are logged with the syslogd LOG_INFO facility level. All failures are logged with the LOG_ERR facility level.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsczu |
+-----------------------------+-----------------------------+
|Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO Intro(1CL), cldevice(1CL), clnode(1CL), attributes(5)
Sun Cluster System Administration Guide for Solaris OS
Sun Cluster 3.2 22 Jun 2006 scdpm(1M)