Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Reference Manual Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

### scconf_dg_svm

- change Solaris Volume Manager device group configuration.

### Synopsis

    scconf -c -D [generic_options]

## Description

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.

A Solaris Volume Manager device group is defined by a name, the nodes upon which this group can be accessed, a global list of devices in the disk set, and a set of properties used to control actions such as potential primary preference and failback behavior.

For Solaris Volume Manager device groups, only one disk set can be assigned to a device group, and the group name must always match the name of the disk set itself.

In Solaris Volume Manager, a multi-hosted or shared device is a grouping of two or more hosts and disk drives that are accessible by all hosts, and that have the same device names on all hosts. This identical device naming requirement is achieved by using the raw disk devices to form the disk set. The device ID pseudo driver (DID) allows multi-hosted devices to have consistent names across the cluster. Only hosts already configured as part of a disk set itself can be configured into the `nodelist` of a Solaris Volume Manager device group. At the time drives are added to a shared disk set, they must not belong to any other shared disk set.

The Solaris Volume Manager `metaset` command creates the disk set, which also initially creates and registers it as a Solaris Volume Manager device group. Next, you must use the `scconf` command to set the node preference list, the `preferenced`, `failback` and `numsecondaries` sub-options.

If you want to change the order of node preference list or the failback mode, you must specify all the nodes that currently exist in the device group 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 you do not specify the `preferenced` sub-option with the “change” form of the command, the already established `true` or `false` setting is used.

You cannot use the `scconf` command to remove the Solaris Volume Manager device group from the cluster configuration. Use the Solaris Volume Manager `metaset` command instead. You remove a device group by removing the Solaris Volume Manager disk set.

## Options

See `scconf`(1M) for the list of supported generic options. See `metaset`(1M) for the list of `metaset` related commands to create and remove disk sets and device groups.

Only one action option is allowed in the command. The following action options are supported.

`-c`

  Change the ordering of the node preference list, change preference and failback policy, and change the desired number of secondaries.

## Examples

Example 1 Creating and Registering a Disk Set

The following `metaset` commands create the disk set `diskset` and register the disk set as a Solaris Volume Manager device group.

Next, the `scconf` command is used to specify the order of the potential primary nodes for the device group, change the preferenced and failback options, and change the desired number of secondaries.

    host1# metaset -s diskset1 -a -h host1 host2
    host1# scconf -c -D name=diskset1,nodelist=host2:host1,
    preferenced=true,failback=disabled,numsecondaries=1

## Attributes

See `attributes`(5) for descriptions of the following attributes:

ATTRIBUTE TYPE | ATTRIBUTE VALUE
--- | ---
Availability | ha-cluster/system/core
Interface Stability | Evolving

## See Also

`Intro`(1CL), `cldevicegroup`(1CL), `scconf`(1M), `metaset`(1M)

Copyright © 2000, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |