Encrypted Volume and File System v1.1 Administrator's Guide

where:
v
Indicates that the entry is for an EVFS volume.
volume_path
Specifies the path for the underlying LVM, VxVM, or physical device
file, such as /dev/vg01/lvol5, /dev/vx/dsk/rootdg/vol05,
or /dev/dsk/c2t0d1.
evfs_volume_path
Specifies the absolute pathname for the EVFS volume device file,
such as /dev/evfs/vg01/lvol5,
/dev/evfs/vx/dsk/rootdg/vol05, or
/dev/evfs/dsk/c2t0d1.
user_name.key_name
Specifies the user name and key name pair to use when enabling
the volume.
You must also have a stored passphrase for the private key. See
“Creating Keys for EVFS Volume Owners” (page 44) for more
information.
noauto
Causes EVFS to not automatically enable this volume at system
startup. EVFS will enable this volume when the command evfsvol
enable -p is executed within the EVFS HA package control script.
Step 3d: Preparing EVFS Volumes for Adoptive Nodes
Use the following procedure to prepare the EVFS volumes so you can configure them on the
adoptive nodes:
i. Use the following command to disable encryption and decryption access to the target volume:
evfsvol disable [-k keyname] evfs_volume_path
See “Disabling Encryption/Decryption Access to EVFS Volumes” (page 81) for more
information.
ii. If you are using EVFS volumes created on LVM volumes, use the following vgchange
command to deactivate the LVM volume group on the configuration node:
# vgchange -a n lvolgroup_device_file
For example:
# vgchange -a n /dev/vg02
If you are using EVFS volumes created on VxVM volumes, use the following vxdg command
to deport the VxVM disk group on the configuration node:
# vxdg deport vxvm_group
For example:
# vxdg deport evfsdg
160 Using EVFS with Serviceguard