The following options are listed in least likely to disrupt system services to mostly intrusive process.

Option #1: Non-reboot method

# devfsadm -Cv

# vxdctl init

# vxdctl initdmp

# vxdctl enable

Option #2: Non-reboot method

1. Rename 'info' files in /etc/vx Example:

# mv /etc/vx/array.info /etc/vx/old_array.info

# mv /etc/vx/disk.info /etc/vx/old_disk.info

# mv /etc/vx/jbod.info /etc/vx/old_jbod.info

# mv /etc/vx/dmppolicy.info /etc/vx/old_dmppolicy.info (if present)

2. Remove the affected device tree entries from the /dev/vx/dmp and /dev/vx/rdmp. DO NOT remove the rootdisk or rootmirror from these two directories. All device entries within the /dev/vx/dmp and /dev/vx/rdmp directories can be removed EXCEPT the rootdisk or rootmirror device.

3.

# devfsadm -Cv

# vxconfigd -k (freeze cluster before running if in high availability (HA) cluster)

# vxdctl init

# vxdctl initdmp

# vxdctl enable Option

#3: Reboot method - To fully update device tree perform the following procedure.

To reset invalid device entries remove all entries except the rootdisk, rootmirror, or any of the 'rootdg' devices from /dev/dsk, /dev/rdsk, /dev/vx/dmp, and /dev/vx/rdmp directories. Again, do not remove the bootdisk, bootmirror, or 'rootdg' devices from any of these directories. IMPORTANT: If the boot disk or boot mirror device tree entries are removed the system will not boot and the operating system will need to be re-installed. Lastly, rename the 'array.info', 'disk.info', 'jbod.info', and 'dmppolicy.info' (if present) files located in the /etc/vx directory. Once this is done perform reconfiguration reboot. See below.

# mv /etc/vx/array.info /etc/vx/old_array.info

# mv /etc/vx/disk.info /etc/vx/old_disk.info

# mv /etc/vx/jbod.info /etc/vx/old_jbod.info

# mv /etc/vx/dmppolicy.info /etc/vx/old_dmppolicy.info (if present)

Once all the above items have been addressed perform a reconfiguration reboot.

# touch /reconfigure

# shutdown -i6 -y -g0