Sun Cluster 3.2 to Sun Cluster 3.1 Commands

 

Sun Cluster 3.2 commands are more granular than Sun Cluster 3.1 commands. A single Sun Cluster 3.1 command may provide output requiring multiple Sun Cluster 3.2 commands. All boxed commands are to be typed on one line.

 

Configuration and Status commands

             

Use

Cluster 3.2

Cluster 3.1

Checking the cluster quorum status: Displays everything including DID information (but not DID status. That requires cldev status) transport status, cluster status, quorum, devices, node status, resource types registered, resource groups configured.

# cluster show

# scstat

Quorum vote and quorum device configuration and status

# clq(uorum) status

 

# scstat -q

List of all global devices with DID numbers

 

# cldev list -v

 

# scdidadm -L

Cluster transport configuration and status

# clintr status

 

# scstat -W

Disk group configuration, including primary hosts and failback status

# cldg show

# scconf -p

Resource group status and current primary node

# clrg status

# scstat -g

Disk group status and current primary node

# cldg status

# scstat -D

Registered resource types and properties

# clrt show

# scrgadm -p

Configuration of resource groups including resources in the group, or of a specified resource group and its properties

# clrg show <resource_group>

# scstat -g <res_ group>

Resource group status

# clrg status

# scrgadm -p

All configured resources

# clrs list -v

# scrgadm -p

Status of configured resources

# clrs status

# scrgadm -p

Disks in a VxVM disk group (on the node that is primary for the disk group)

# vxprint

# vxprint

 

Disks in all SVM disk groups, along with metadevices and soft partitions

# metastat -a

 

# metastat -a

 

 

 

Management commands

 

Use

Cluster 3.2

Cluster 3.1

Shut down cluster and bring all nodes to the PROM

#cluster shutdown -y -g0

 

# scshutdown -y -g0

Register changes to a disk group

 

# cldg sync <disk_group>

# scconf -c -D name=<disk_group>,sync

Bring a resource group online

 

# clrg online -M <resource_group>

 

# scswitch -Z -g <resource_group>

Switch control of a resource group to a different node

# clrg switch -n <destination_node> <resource_group>

 

# scswitch -z -g <resource_group> -h <destination_node>

Switch control of a disk group to a different node

# cldg switch –n <destination_node> <disk_group>

# scswitch -z -D <disk_group> -h <destination_node>

Evacuate all resource groups and disk groups from a specified node. Do this prior to bringing down a node.

# clnode evacuate -n <current_node>

 

# scswitch –S –h <current_node>

 

Configuration commands

Use

Cluster 3.2

Cluster 3.1

Perform initial configuration

# scinstall

 

# scinstall

Perform later installation, including selecting or changing a private network address or configuring a cluster or adding or removing a node:

# clsetup

# scsetup

Register a resource type other than SharedAddress or LogicalHostname

 

# clrt register <resource type>

 

# scrgadm -a -t <resource_type>

Create an instance of a resource group and set properties

# clrg create -n <node1,node2…> -p <property type>=<property of group> <other properties> <name of group>

# scrgadm -a -g <group_name> -h <nodename1,nodename2> -y <property_type=value> …

Create and configure an instance of any resource other a logical hostname or shared address resource and add to a resource group:

clrs create -t <resource type> -g <resource group> -p <property name=value> <other properties> <resource name>

# scrgadm -a -j <resource_name> -g <group_name> -t <resource_type> -x|y <property=value>…

Create an instance of a logical host name resource

# clrslh create -g <resource group> <logical hostname>

# scrgadm -a -L -g <resource_group> -l <hostname> -x <property=value>…

Create an instance of a shared address resource

# clrssa create -g <resource group> <shared address name>

# scrgadm -a -S -g <resource_group> -l <hostname> -x <property=value>…

 

Undo commands

 

Use

Cluster 3.2

Cluster 3.1

Offline a resource group

# clrg offline <resource group>

# scswitch -F -g <res_group>

Disabling a resource

# clrs disable <resource name>

# scswitch -n -j <resource>

Removing a resource

# clrs delete <resource name>

# scrgadm -r -j <resource>

Delete a resource group

# clrg delete <resource group>

# scrgadm -r -g <res_group>

Offline a disk group

# cldg offline <disk_group>

# scswitch -F -D <disk_group>

 

 

Unconfiguring a resource group: This can only be done when all included resources have been deleted, and when all dependent resource groups have been deleted. In order:

 

Removing a SVM disk group:

 

One both nodes, check that /etc/nsswitch.conf has the entry

 

ipnodes: files

 

You cannot have ANYTHING else on this line.

 

Then on the node that is primary for the disk group:

 

(if none is primary then for Sun Cluster 3.2:

 

Cluster3.2# cldg switch -n <node-to-work-from>  <disksetname> 

 

i.e.

 

Cluster3.2# cldg switch -n host01 nfsds

 

OR for Sun Cluster 3.1

 

Cluster3.1# scswitch -z -D <disk_group> -h <node-to-work-from> 

 

i.e.

 

Cluster3.1# scswitch -z -D nfsds -h host01)

 

Unmount any file systems that reside on the disk group, and comment out any related entries in /etc/vfstab.

 

Remove any volumes in order from highest level to lowest level:

 

Locate volumes to remove:

 

# metastat –s nfsds

 

Remove volumes:

 

# metaclear –s nfsds d100

 

Repeat as needed

 

 If necessary delete any mediators

 

# metaset –s nfsds –d –m <node1 node2…>

 

i.e.

 

# metaset –s nfsds –d –m host01 host02

 

Locate the names of the disks in the diskset:

 

# metaset -s nfsds

 

Remove those disks from the diskset:

 

# metaset -s nfsds -d /dev/did/dsk/d6

 

When the last disk is removed, use the -f option to force the removal of the disk:

 

# metaset -s nfsds -f -d /dev/did/dsk/d7

 

Delete the disk set from all nodes:

 

# metaset -s nfsds -f -d -h <node1 node2…>

 

i.e.

 

# metaset -s nfsds -f -d -h host01 host02

 

Hosted by www.Geocities.ws

1