|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Cluster Reference Manual Oracle Solaris Cluster 4.0|
- add, change or update raw-disk device group configuration
scconf -a -D type=rawdisk, [generic_options] [,globaldev=gdev1,globaldev=gdev1,…] [,localonly=true]
scconf -a -D type=rawdisk, [generic_options] [,globaldev=gdev1,globaldev=gdev1,…] [,localonly=true | false]
scconf -c -D name=diskgroup,autogen=true
scconf -r -D device_service_name [,nodelist=node[:node]…] [,globaldev=gdev1,…]
Note - Oracle Solaris Cluster software includes an object-oriented command set. Although Oracle Solaris Cluster software still supports the original command set, Oracle Solaris Cluster procedural documentation uses only the object-oriented command set. For more information about the object-oriented command set, see the Intro(1CL) man page.
The following information is specific to the scconf command. To use the equivalent object-oriented commands, see the cldevicegroup(1CL) man page.
The scconf_dg_rawdisk utility adds, changes or updates raw-disk device group configuration
A raw disk is a disk that is not being used as part of a volume manager volume or metadevice. Raw-disk device groups allow you to define a set of disks within a disk device group.
At system boot, by default, a raw-disk device group is created for every Disk ID pseudo driver (DID) device in the configuration. By convention, the raw-disk device group names are assigned at initialization and are derived from the DID names. For every node added to a raw-disk disk device group, the scconf utility verifies that every device in the group is physically ported to the node.
The scconf -a (add) command can be used to create a raw-disk device group with multiple disk devices configured in it. A raw-disk device group is created for every disk device in the cluster at boot time.
Before you can add a new raw-disk device group, devices to be used in the new group must be removed from the device group created at boot time. Then a new raw-disk device group can be created containing these devices. This is accomplished by creating a list of these devices in the globaldev option of scconf along with a potential primary node preference list in the nodelist option. If the device group already exists, only new nodes and global devices will be added and nodes or devices which are part of an existing device group will be ignored.
If the preferenced sub-option is not given with the-a option to create a new device group, then it is, by default, false. However, if the preferenced sub-option is specified for the existing device group with a value of true or false, an error is returned. This is done in order to maintain the existing nodelist preference state.
If a device group should be mastered by only a particular node then it should be configured with the otheroption set to localonly=true. Only one node can be specified in the node list to create a localonly device group.
The scconf -c (change) command is used to change the order of the potential primary node preference, to enable or disable failback, to set the desired number of secondaries, and to add more global devices to the device group.
If you want to change the order of node preference list, then all the nodes currently existing in the device group must be specified in the nodelist. In addition, if you are changing the order of node preference, you must also set the preferenced sub-option to true.
If the preferenced sub-option is not specified with the change, the already established true or false setting is used.
New nodes cannot be added using the change form of the command. Change option can also be used for changing a device group to localonly device group and vice-versa. To change a device group to a localonly device group, set otheroption to localonly=true. Specify localonly=false to set it back to not the localonly device group. nodelist must already be set to a list of one node, or an error results. It is legal to specify a nodelist with the change form of the command, when you set localonly to true. This is, however, redundant, since the list can only contain the single node that is already configured. It would be an error to specify any other than the node that is already configured.
The scconf -r (remove) command can be used to remove the nodes, global devices, and the device group name from the cluster device-group configuration. If nodes or global devices are specified with the device-group name, they are removed from the device group first. After the last device and node are removed from the device group, the device group is also removed from cluster configuration. If only the name of the device group is given (no nodes or devices at all), the entire device group is removed.
If a raw-disk device name is registered in a raw-disk device group, then it cannot be registered in a Solaris Volume Manager device group.
See the scconf(1M) man page for the list of supported generic options.
The following action options are used to describe the actions performed by the command. Only one action option is allowed in the command.
The following action options are supported:
Add a new raw-disk device group to the cluster configuration. You can also use this option to change the device group configuration.
Change the ordering of the node preference list, change preference and failback policy, change the desired number of secondaries, and also add more devices to the device group with the globaldev option. It is also used to set a device group as local only.
Remove the raw-disk device group name from the cluster.
The autogen flag is an indicator of the scconf command. This command does not list devices with the autogen property unless the -v command line option is used. When a device is used with the change form of the scconf command, the device's autogen property is reset, or set to false, unless autogen=true is also specified.
Example 1 Using scconf Commands
The following scconf commands create a raw-disk device group, change the order of the potential primary nodes, change preference and failback policy, change the desired number of secondaries, and remove the raw-disk device group from the cluster configuration.
host1# scconf -a -D type=rawdisk,name=rawdisk_groupname, nodelist=host1:host2:host3,preferenced=false,failback=enabled, numsecondaries=,globaldev=d1,globaldev=d2 host1# scconf -a -D type=rawdisk,name=rawdisk_groupname, nodelist=host1,globaldev=d1,globaldev=d2,localonly=true, globaldev=d1,globaldev=d2 host1# scconf -c -D name=rawdisk_groupname, nodelist=host3:host2:host1,preferenced=true,failback=disabled, numsecondaries=2,globaldev=d4,globaldev=d5 host1# scconf -c -D name=rawdisk_groupname,localonly=true host1# scconf -r -D name=rawdisk_groupname host1# scconf -r -D name=rawdisk_groupname,nodelist=host1,host2
See attributes(5) for descriptions of the following attributes: