... {section}
{column:width=25%}
{livesearch:spaceKey=SunCluster}
h5. Contents
{children:all=true}
h5. [Index]
{column}
{column:width=75%}
This page contains the following information:
----
{toc:type=list|style=none|minLevel=5|maxLevel=5|indent=0px}
----
h5. Displays existing device group resources in the Cluster
{panel}
{{*scstat \-D*}}
{panel}
h5. Registering VxVM device groups
{panel}
{{*scconf \-a \-D type=vxvm,name=. \*}}
{{*nodelist=:, \*}}
{{*preferenced=true,failback=enabled*}}
{panel}
* nodelist should contain only nodes that are physically connected to the disks of that device group.
* preferenced=true/false affects whether nodelist indiciates an order of failover preference. On a two\-node cluster, this options is only meaningful if failback is enabled.
* failback=disabled/enabled affects whether a preferred node “takes back” its device group when it joins the cluster. The default value is disabled. When faileback is disabled, preferenced is set to false. If it is enabled, preferenced also must be set to true.
h5. Moving device groups across nodes of a cluster
When VxVM device groups are registered as Sun Cluster resources, NEVER USE {{vxdg}} import/deport commands to change ownership (node\-wise) of the device group. This will cause Sun Cluster to treat device group as failed resource.
Use the following command instead:
{panel}
{{# *scswitch \-z \-D \-h*}}
{panel}
h6. Resyncing device groups
{panel}
{{*scconf \-c \-D name=,sync*}}
{panel}
h6. Changing device group configuration
{panel}
{{*scconf \-c \-D name=,preferenced=,failback=*}}
{panel}
h6. Maintenance mode
{panel}
{{*scswitch \-m \-D*}}
{panel}
{info:Title=Note} all volumes in the device group must be unopened or unmounted (not being used) in order to do that.{info}
h6. To come back out of maintenance mode
{panel}
{{*scswitch \-z \-D \-h*}}
{panel}
h6. Repairing DID device database after replacing JBOD disks
Make sure you know which disk to update ...
{panel}
{{*scdidadm \-l c1t1d0*}}
{panel}
returns {{node1:/dev/rdsk/c1t1d0 /dev/did/rdsk/d7}}
{panel}
{{*scdidadm \-l d7*}}
{panel}
returns {{node1:/dev/rdsk/c1t1d0 /dev/did/rdsk/d7}}
Then use following cmds to update and verify the DID info:
{panel}
{{*scdidadm \-R d7*}}
{{*scdidadm \-l \-o diskid d7*}}
{panel}
returns a large string with disk id.
h6. Replacing a failed disk in a A5200 Array (similar concept with other FC disk arrays)
{panel}
{{*vxdisk list*}} #get the failed disk name
{panel}
{panel}
{{*vxprint \-g dgname*}} #determine state of the volume(s) that might be affected
{panel}
On the hosting node, replace the failed disk:
{panel}
{{*luxadm remove enclosure,position*}}
{{*luxadm insert enclosure,position*}}
{panel}
On either node of the cluster (that hosts the device group):
{panel}
{{*scdidadm \-l c\#t\#d\#*}}
{{*scdidadm \-R d\#*}}
{panel}
On the hosting node:
{panel}
{{*vxdctl enable*}}
{panel}
{{*vxdiskadm*}} #replace failed disk in vxvm
{panel}
{{*vxprint \-g*}}
{{*vxtask list*}} #ensure that resyncing is completed
{panel}
Remove any relocated submirrors/plexes (if hot\-relocation had to move something out of the way):
{panel}
{{*vxunreloc _repaired\-diskname_*}}
{panel}
h6. Solaris Vol Mgr (SDS) in Sun Clustered Env
Preferred method of using Soft partitions is to use single slices to create mirrors and then create volumes (soft partitions) from that (kind of similar to VxVM public region in an initialized disk).
h6. Shared Disksets and Local Disksets
Only disks that are physically located in the multi\-ported storage will be members of shared disksets. Only disks that are in the same diskset operate as a unit; they can be used together to build mirrored volumes, and primary ownership of the diskset transfers as a while from node to node.
Boot disks are the local disksets. This is a pre\-requisite in order to have shared disksets.
h6. Replica management
* Add local replicas manually.
* Put local state db replicas on slice 7 of disks (as a convention) in order to maintain uniformity. Shared disksets have to have replicas on slice 7.
* Spread local replicas evenly across disks and controllers.
* Support for Shared disksets is provided by Pkg {{SUNWmdm}}
h6. Modifying {{/kernel/drv/md.conf}}
{panel}
{{*nmd \=\= max num of volumes (default 128)*}}
{{*md_nsets \=\= max is 32, default 4.*}}
{panel}
h6. Creating shared disksets and mediators
{panel}
{{*scdidadm \-l c1t3d0*}}
{panel}
Returns {{d17}} as DID device
{panel}
{{*scdidadm \-l d17*}}
{{*metaset \-s \-a \-h*}} # creates metaset
{{*metaset \-s \-a \-m*}} # creates mediator
{{*metaset \-s \-s /dev/did/rdsk/d9 /dev/did/rdsk/d17*}}
{{*metaset*}} # returns values
{{*metadb \-s*}}
{{*medstat \-s*}} # reports mediator status
{panel}
Remaining syntax vis\-a\-vis Sun Cluster is identical to that for VxVM.
h6. IPMP and Sun Cluster
IPMP is cluster un\-aware. To work around that, Sun Cluster uses Cluster\-specific public network mgr daemon (pnmd) to integrate IPMP into the cluster.
{{pmnd}} daemon has two capabilities:
* populate CCR with public network adapter status
* facilitate application failover
When {{pnmd}} detects all members of a local IPMP group have failed, it consults a file called {{/var/cluster/run/pnm_callbacks}}. This file contains entries that would have been created by the activation of {{LogicalHostname}} and {{SharedAddress}} resources. It is the job of {{hafoip_ipmp_callback}} to device whether to migrate resources to another node.
{panel}
{{*scstat \-i*}} #view IPMP configuration
{panel}
{column}
{section} |