Remove /etc/vx/reconfig.d/state.d/install-db fileġ9. Check the revised disk information and import VxVM disk groups as requiredġ7. # vxdisk list | grep udid_mismatch | awk '' | sudo sh -xġ6.
#NDM TECHNOLOGIES UPDATE#
Update UDID for NDM related disks reporting udid_mismatch # symdev -sid SID reset -identity SYMDEV -nopromptħ. Storage Team reset spoof information for EMC NDM migrated devices Ensure no VxVM disk groups are imported and vxconfigd is "not-running".Ĥ. # touch /etc/vx/reconfig.d/state.d/install-dbģ. Disable Veritas Volume Manager (VxVM) from auto-starting: Upgrade InfoScale to 7.4.2.x or higher followed by a reboot of the upgrade host.ġ. To the host and application, there is no change in the device that it is accessing and access to the device is maintained throughout the entire migration process. The path management changes appear as either the addition of paths or the removal of paths to the existing source device. NDM performs the data migration and device ID swap without the host being aware. The device ID contains the device’s unique WWN and other information about it, such as a device identifier that the user has assigned to a device through Solutions Enabler or Unisphere.Īll of this information is copied to the target devices. NDM is able to migrate data and cut over to the target array non-disruptively by both swapping device IDs between the source and target devices and manipulating the paths from the host to both arrays. Two of the underlying processes that ensure that NDM is non-disruptive is the technologies ability to maintain device visibility at all times by spoofing and swapping devices IDs between source and target devices. Manipulation of device IDs and host paths This can then lead to Veritas Volume Manager (VxVM) reporting the udid_mismatch flag once the SYMDEV identity has been reset. To resolve the stale LUN information, the spoofing identity needs to be reset for the NDM migrated EMC SYMDEVs. Once the NDM array migration is complete, the process can result in stale historical information being reported to Veritas Dynamic Multi-Pathing (DMP). The NDM solution leverages VMAX SRDF replication technologies to move the application data from the source EMC storage array to the new target EMC storage array. The DELL/EMC NDM solution is designed to help automate the process of migrating host applications to a PowerMax, VMAX All-Flash, or VMAX3 enterprise storage array with no downtime. "VID, '_', PID, '_', CAB _Serial_No, '_', Lun_Serial_No "Īs a result of clearing/resetting the spoofing information, this leads to the expected VxVM udid_mismatch flag being set, as the true UUID in the kernel differs to what is written on-disk.ĭELL/EMC NDM (Non-Disruptive Migration) overview
#NDM TECHNOLOGIES SERIAL NUMBER#
The UDID structure consists of the Vendor ID (VID), Product ID (PID), Cabinet Serial Number (Cab_Serial_No) and Lun Serial Number (Lun_Serial_No - LSN) : Veritas Volume Manager (VxVM) refers to two UDID values, the UDID value returned by the Device Discovery Layer (DDL) which is the correct (true) UDID value of the LUN, whereas the UDID written on-disk can be from a different source.
#NDM TECHNOLOGIES HOW TO#
This article outlines how to update Veritas Volume Manager (VxVM) UDID content for NDM migrated EMC SYMDEVs using the vxdisk -c updateudid command.
0 kommentar(er)
