clvxvm(1CL) (Sun Cluster Reference Manual for Solaris OS)

Sun Cluster Reference Manual for Solaris OS

clvxvm(1CL)

NAME

clvxvm – configure Veritas Volume Manager for Sun Cluster

Synopsis

/usr/cluster/bin/clvxvm  -V

/usr/cluster/bin/clvxvm  [subcommand] -?

/usr/cluster/bin/clvxvm  subcommand -v

/usr/cluster/bin/clvxvm encapsulate

/usr/cluster/bin/clvxvm initialize

Description

The clvxvm utility initializes Veritas Volume Manager (VxVM) on a Sun Cluster node and optionally performs root-disk encapsulation. There is no short form of this command name.

You can only use this utility with VxVM versions 4.1 or later. For older versions of VxVM, instead use the scvxinstall(1M) utility.

The general form of this command is as follows:

clvxvm [subcommand] [options]

You can omit subcommand only if options specifies the -? option or the -V option.

Each option of this command has a long form and a short form. Both forms of each option are given with the description of the option in the OPTIONS section of this man page.

You can only use this command from a node that is booted in cluster mode. All nodes in the cluster configuration must be current cluster members. All nodes must be added to the node authentication list.

You can use this command only in the global zone.

SUBCOMMANDS

The following subcommands are supported:

encapsulate

Encapsulates the root disk and performs other Sun Cluster-specific tasks.

The encapsulate subcommand performs the following tasks:

Verifies that the current node is booted in cluster mode and that all other cluster nodes are running in cluster mode.
Verifies that the user is superuser.
Enforces a cluster-wide value for the vxio major number by modifying the node's /etc/name_to_major file, if necessary. This task ensures that the vxio number is the same on all cluster nodes.
Runs several VxVM commands to prepare for root-disk encapsulation.
Modifies the global-devices entry in the /etc/vfstab file that is specified for the /global/.devices/node@n file system, where n is the node ID number. The clvxvm utility replaces the existing device path /dev/did/{r}dsk with /dev/{r}dsk. This change ensures that VxVM recognizes that the global-devices file system resides on the root disk.
Twice reboots each node that is running clvxvm. The first reboot allows VxVM to complete the encapsulation process. The second reboot resumes normal operation. The clvxvm utility includes a synchronization mechanism to ensure that the utility reboots only one node at a time, to prevent loss of quorum.
Unmounts the global-devices file system. The file system is automatically remounted after the encapsulation process is complete.
Recreates the special files for the root-disk volumes with a unique minor number on each node.

This subcommand expects that VxVM packages and licenses are already installed and that the VxVM configuration daemon is successfully enabled on this node.

Each root disk that you encapsulate must have at least two free (unassigned) partitions.

Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand.

initialize

Initializes VxVM and performs other Sun Cluster-specific tasks.

The initialize subcommand performs the following tasks:

Verifies that the current node is booted in cluster mode and that all other cluster nodes are running in cluster mode.
Verifies that the user is superuser.
Enforces a cluster-wide value for the vxio major number by modifying the node's /etc/name_to_major file, if necessary. This task ensures that the vxio number is the same on all cluster nodes.
Instructs the user to reboot the node to resume operation with the new vxio major number in effect, in case the number had to be changed.

This subcommand expects that VxVM packages and licenses are already installed and that the VxVM configuration daemon is successfully enabled on this node.

Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand.

Options

The following options are supported:

-? ---help

Displays help information.

You can use this option either alone or with a subcommand.

If you use this option alone, the list of available subcommands is printed.
If you use this option with a subcommand, the usage options for that subcommand are printed.

When you use this option, no other processing is performed.

-V ---version

Displays the version of the command.

Do not specify this option with subcommands, operands, or other options. The subcommands, operands, or other options are ignored. The -V option only displays the version of the command. No other operations are performed.

-v ---verbose

Displays verbose information to standard output.

You can use this option with any form of the command.

Operands

No form of this command accepts an operand.

Exit Status

The complete set of exit status codes for all commands in this command set are listed on the Intro(1CL) man page.

This command returns the following exit status codes:

0 CL_NOERR: No error
1 CL_ENOMEM: Not enough swap space
3 CL_EINVAL: Invalid argument
6 CL_EACCESS: Permission denied
35 CL_EIO: I/O error

Examples

Example 1 Initializing VxVM on a Cluster Node

The following example shows how to initialize VxVM the cluster node from which the command is issued.

# clvxvm initialize

Example 2 Initializing VxVM on a Cluster Node and Encapsulating the Root Disk

The following example shows how to initialize VxVM and encapsulate the root disk on the cluster node from which the command is issued.

# clvxvm encapsulate

Attributes

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

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWsczu
Interface Stability	Evolving

Files

/var/cluster/cmvxvm/*: Location of temporary files that are used by the clvxvm utility.
/var/cluster/logs/install/clvxvm.log.pid: Log file that is created by the scvxinstall utility.

Notes

The superuser can run any forms of this command.

Any user can also run this command with the following options:

-? (help) option
-V (version) option

To run this command with other subcommands, users other than superuser require RBAC authorizations. See the following table.

Subcommand	RBAC Authorization
`encapsulate`	`solaris.cluster.modify`
`initialize`	`solaris.cluster.modify`

Sun Cluster 3.2 Last Revised 19 Jul 2006