— This is the process monitoring facility. It is i used as a general mech to initiate restarts and failureaction scripts for some cluster f/w daemons, and for most app daemons and app fault monitors. FF panic rule holdsgood.
— This is the public Network mgt daemon, and manages n/w status info received from the local IPMP(
) running on each node in the cluster. It is automatically restarted by
if it dies.
— multi-threaded DPM daemon runs on each node. DPM daemon is started by an rc script when a nodeboots. It montiors the availability of logical path that is visible thru various multipath drivers (MPxIO), HDLM,Powerpath, etc. Automatically restarted by
if it dies.
Validating basic cluster config
) cmd validates the cluster configuration:
is the repository where it stores the reports generated.
Disk Path Monitoring
scdpm -p all:all
prints all disk paths in the cluster and their status
checks the cluster installation status — package revisions, patches applied, etc.Cluster release file:
Shuting down cluster
scshutdown -y -g 30
Booting nodes in non-cluster mode
Placing node in maintenance mode
scconf -c -q node=,maintstate
Reset the maintenance mode by rebooting the node or running
scconf -c -q reset
By placing a node in a cluster in maintenance mode, we reduce the number of reqd. quorumvotes and ensure that cluster operation is not disrupted as a result thereof).Sunplex or Sun Cluster Manager is available on
VxVM Rootdg requirements for Sun Cluster
major number has to be identical on all nodes of the cluster (check for
installed on all nodes physically connected to shared storage — on non-storage nodes, yvxvm can be used toencapsulate and mirror the boot disk. If not using VxVM on a non-storage node, use SVM. All is required in such acase is the
major number be identical to all other nodes of the cluster (add an entry in
file).VxVM license is reqd. on all nodes not connected to a A5x00 StorEdge array.Std rootdg created on all nodes where vxVM is installed. Options to initialize rootdg on each node are:Encap boot disk so it can be mirroered. Preserve all data and creating volumes inside rootdg to encap
If disk has more than 5 slices on it, it cannot be encap'ed.Initialize other local disks into rootdg.Unique volume name and minor number across the nodes for the
file system ifthe boot disk is encap'ed — the
file system must be on devices with a unique nameoneach node, because it's mounted on each node for the same reason. The normal Solaris OS
logicredates global fs and still demands that each device have a unique major/minor number. VxVM doesn't supportchanging minor numbers of individual volumes. The entire disk group has to be re-minored.Use the following command:
vxdg [ -g diskgroup ] [ -f ] reminor [diskgroup ] new-base-minor
reminor Changes the base minor number for a disk group, and renumbers all devices inthe disk group to a range starting at that number. If the device for a volume is open,then the old device number remains in effect until the system is rebooted or until thedisk group is deported and re-imported.Also, if you close an open volume, then the user can execute vxdg reminor again tocause the renumbering to take effect without rebooting or reimporting.A new device number may also overlap with a temporary renumbering for a volume device.This also requires a reboot or reimport for the new device numbering to take effect. Atemporary renumbering can happen in the following situations:when two volumes (for example, volumes in two different disk groups) share the samepermanently assigned device number, in which case one of the volumes is renumberedtemporarily to use an alternate device number;or when the persistent device number for a volume was changed, but the active devicenumber could not be changed to match.