Note
This section is only applicable if you are upgrading a system that includes EMC PowerPath disks.
If you are upgrading a system from VxVM 4.0 to VxVM 5.0, which has PowerPath installed, and the Cx600 ASL and its associated Cx600 APM are also installed, you must uninstall both the Cx600 ASL and APM, otherwise the Cx600 will claim the disks and the PowerPath disks will not be identified.
If you are upgrading a system from VxVM 4.0 to VxVM 5.0, which does not have PowerPath installed, but the Cx600 ASL and its APM are both installed, then the Cx600 ASL and its associated APM should not be uninstalled.
In releases of VxVM before 4.1, a combination of DMP subpaths and the controllers of DMP subpaths were usually suppressed to prevent interference between DMP and the EMC PowerPath multipathing driver. Suppression has the effect of hiding these subpaths and their controllers from DMP, and as a result the disks on these subpaths and controllers cannot be seen by VxVM.
VxVM 4.1 and later releases have the ability to discover EMCpower disks, and configure them as autodiscovered disks that DMP recognizes are under the control of a separate multipathing driver. This has the benefit of allowing such disks to reconfigured in cluster-shareable disk groups. Before upgrading to VxVM 5.0, you must remove the suppression of the subpaths and controllers so that DMP can determine the association between EMCpower metadevices and c#t#d#
disk devices.
There are several scenarios where you need to unsuppress DMP subpaths and controllers:
Because emcpower disks are auto-discovered, the powervxvm script should be disabled and removed from the startup script. To remove the powervxvm script, use the command:
Release 4.0 of VxVM provided the vxddladm
addforeign
command to configure foreign disks with default disk offsets for the private and public regions, and to define them as simple disks. A foreign disk must be manually converted to auto:simple
format before upgrading to VxVM 5.0.
Note
If the foreign disk is defined on a slice other than s2
, you must copy the partition entry for that slice to that for s0
and change the tag. If the tag of the original slice is changed, the status of the disk is seen as online:aliased
after the upgrade.
The following example is used to illustrate the procedure. The vxdisk
list
command can be used to display the EMCpower disks that are known to VxVM:
c6t0d12s2 auto:sliced - - online
emcpower10c simple fdisk fdg online
The vxprint
command is used to display information about the disk group, fdg
:
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dm fdisk emcpower10c - 17673456 - - - -
To convert a foreign disk to auto:simple format
vxddladm
command to remove definitions for the foreign devices:
#vxddladm rmforeign blockpath=/dev/dsk/emcpower10c
\charpath=/dev/rdsk/emcpower10c
If you now run the
vxdisk
list
command, the EMCpower disk is no longer displayed:
vxprtvtoc
command to retrieve the partition table entry for the device:
vxedvtoc
command to modify the partition tag and update the VTOC:
# /etc/vx/bin/vxedvtoc -f /tmp/vtoc /dev/rdsk/emcpower10c
# THE NEW PARTITIONING WILL BE AS FOLLOWS:
DO YOU WANT TO WRITE THIS TO THE DISK ? [Y/N] :Y
WRITING THE NEW VTOC TO THE DISK #
vxdisk
list
command to validate the conversion to auto:simple
format:
c6t0d12s2 auto:sliced - - online
emcpower10s2 auto:simple - - online
To display the physical device that is associated with the metadevice, emcpower10s2
, enter the following command:
You can use the vxdisk
list
command to confirm that the disk status is displayed as online:simple
:
In VxVM 4.0, and particularly in prior releases, EMCpower disks could be defined by a persistent disk access record (darec
), and identified as simple disks. If an EMCpower disk is defined with a persistent darec
, it must be manually converted to auto:simple
format before upgrading to VxVM 5.0.
Note
If the defined disk is defined on a slice other than s2
, you must copy the partition entry for that slice to that for s0
and change the tag. If the tag of the original slice is changed, the status of the disk is seen as online:aliased
after the upgrade.
The following example is used to illustrate the procedure. The ls
command shows the mapping of the EMC disks to persistent disk access records:
lrwxrwxrwx 1 root other 36 Sep 24 17:59 /dev/vx/dmp/emcdisk1-> /dev/dsk/c6t0d11s5 lrwxrwxrwx 1 root other 40Sep 24 17:59 /dev/vx/rdmp/emcdisk1-> /dev/dsk/c6t0d11s5
Here the fifth partition of c6t0d11s5
is defined as the persistent disk access record emcdisk1
.
The vxdisk
list
command can be used to display the EMCpower disks that are known to VxVM:
c6t0d12s2 auto:sliced - - online
emcdisk1 simple fdisk fdg online
The vxprint
command is used to display information about the disk group, fdg
:
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dm fdisk emcdisk1 - 17673456 - - - -
To convert a disk with a persistent disk access record to auto:simple format
vxdisk
rm
command to remove the persistent record definitions:
If you now run vxprint
, the EMCpower disk is no longer displayed:
vxprtvtoc
command to retrieve the partition table entry for the device:
vxedvtoc
command to modify the partition tag and update the VTOC:
# /etc/vx/bin/vxedvtoc -f /tmp/hdisk /dev/rdsk/c6t0d11s2
# THE ORIGINAL PARTITIONING IS AS FOLLOWS:
# THE NEW PARTITIONING WILL BE AS FOLLOWS:
vxdisk
list
command to validate the conversion to auto:simple
format:
c6t0d12s2 auto:sliced - - online
emcpower10s2 auto:simple - - online:aliased
To display the physical device that is associated with the metadevice, emcpower10s2
, enter the following command:
You can use the vxdisk
list
command to confirm that the disk status is displayed as online:simple
:
c6t0d12s2 auto:sliced - - online
emcpower10s2 auto:simple fdisk fdg online:aliased
Note To allow DMP to receive correct enquiry data, the common Serial Number (C-bit) Symmetrix Director parameter must be set to enabled.
In VxVM 4.0, and particularly in prior releases, EMCpower disks could be defined by a persistent disk access record (darec) using powervxvm script, and identified as simple disks. If an EMCpower disk is used using powervxvm, it must be manually converted to auto:simple format before upgrading to VxVM 5.0.
Note If there are any controllers or devices that are suppressed from VxVM as powervxvm requirement, then such controllers/disks must be unsuppressed. This is required for Veritas DMP to determine the association between PowerPath metanodes and their subpaths. After the conversion to auto:simple is complete, the powervxvm script is no longer useful, and should be disabled from startup script.
The following example is used to illustrate the procedure. The ls
command shows the mapping of the EMC disks to persistent disk access records:
crw------- 1 root root 260, 76 Feb 7 02:36 emcpower0c
c6t0d12s2 auto:sliced - - online
emcpower0c simple ppdsk01 ppdg online
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dm ppdsk01 emcpower0c - 2094960 - - - -
To convert an EMCpower disk (defined using powervxvm) to auto:simple format
vxdisk rm
command to remove all emcpower disks from VxVM:
If you now run the vxdisk list
command, the EMCpower disk is no longer displayed:
vxprtvtoc
command to retrieve the partition table entry for this device:
# /etc/vx/bin/vxprtvtoc -f /tmp/vtoc /dev/vx/rdmp/emcpower0c
vxedvtoc
command to modify the partition tag and update the VTOC:
# /etc/vx/bin/vxedvtoc -f /tmp/vtoc /dev/vx/rdmp/emcpower0c
# THE ORIGINAL PARTITIONING IS AS FOLLOWS:
# THE NEW PARTITIONING WILL BE AS FOLLOWS:
After upgrading VxVM, use the vxdisk list
command to validate the conversion to auto:simple format:
c6t0d12s2 auto:sliced - - online
emcpower0s2 auto:simple - - online