Dynamic Multi-Pathing 7.4.1 Administrator's Guide - Linux
- Understanding DMP
- Setting up DMP to manage native devices
- About setting up DMP to manage native devices
- Displaying the native multi-pathing configuration
- Migrating LVM volume groups to DMP
- Migrating to DMP from EMC PowerPath
- Migrating to DMP from Hitachi Data Link Manager (HDLM)
- Migrating to DMP from Linux Device Mapper Multipath
- Using Dynamic Multi-Pathing (DMP) devices with Oracle Automatic Storage Management (ASM)
- Enabling Dynamic Multi-Pathing (DMP) devices for use with Oracle Automatic Storage Management (ASM)
- Removing Dynamic Multi-Pathing (DMP) devices from the listing of Oracle Automatic Storage Management (ASM) disks
- Migrating Oracle Automatic Storage Management (ASM) disk groups on operating system devices to Dynamic Multi-Pathing (DMP) devices
- Adding DMP devices to an existing LVM volume group or creating a new LVM volume group
- Removing DMP support for native devices
- Administering DMP
- About enabling and disabling I/O for controllers and storage processors
- About displaying DMP database information
- Displaying the paths to a disk
- Setting customized names for DMP nodes
- Administering DMP using the vxdmpadm utility
- Retrieving information about a DMP node
- Displaying consolidated information about the DMP nodes
- Displaying the members of a LUN group
- Displaying paths controlled by a DMP node, controller, enclosure, or array port
- Displaying information about controllers
- Displaying information about enclosures
- Displaying information about array ports
- User-friendly CLI outputs for ALUA arrays
- Displaying information about devices controlled by third-party drivers
- Displaying extended device attributes
- Suppressing or including devices from VxVM control
- Gathering and displaying I/O statistics
- Setting the attributes of the paths to an enclosure
- Displaying the redundancy level of a device or enclosure
- Specifying the minimum number of active paths
- Displaying the I/O policy
- Specifying the I/O policy
- Disabling I/O for paths, controllers, array ports, or DMP nodes
- Enabling I/O for paths, controllers, array ports, or DMP nodes
- Renaming an enclosure
- Configuring the response to I/O failures
- Configuring the I/O throttling mechanism
- Configuring Subpaths Failover Groups (SFG)
- Configuring Low Impact Path Probing (LIPP)
- Displaying recovery option values
- Configuring DMP path restoration policies
- Stopping the DMP path restoration thread
- Displaying the status of the DMP path restoration thread
- Configuring Array Policy Modules
- Administering disks
- About disk management
- Discovering and configuring newly added disk devices
- Partial device discovery
- About discovering disks and dynamically adding disk arrays
- About third-party driver coexistence
- How to administer the Device Discovery Layer
- Listing all the devices including iSCSI
- Listing all the Host Bus Adapters including iSCSI
- Listing the ports configured on a Host Bus Adapter
- Listing the targets configured from a Host Bus Adapter or a port
- Listing the devices configured from a Host Bus Adapter and target
- Getting or setting the iSCSI operational parameters
- Listing all supported disk arrays
- Excluding support for a disk array library
- Re-including support for an excluded disk array library
- Listing excluded disk arrays
- Listing disks claimed in the DISKS category
- Displaying details about an Array Support Library
- Adding unsupported disk arrays to the DISKS category
- Removing disks from the DISKS category
- Foreign devices
- Changing the disk device naming scheme
- Discovering the association between enclosure-based disk names and OS-based disk names
- Dynamic Reconfiguration of devices
- About online Dynamic Reconfiguration
- Reconfiguring a LUN online that is under DMP control using the Dynamic Reconfiguration tool
- Manually reconfiguring a LUN online that is under DMP control
- Overview of manually reconfiguring a LUN
- Manually removing LUNs dynamically from an existing target ID
- Manually adding new LUNs dynamically to a new target ID
- About detecting target ID reuse if the operating system device tree is not cleaned up
- Scanning an operating system device tree after adding or removing LUNs
- Manually cleaning up the operating system device tree after removing LUNs
- Changing the characteristics of a LUN from the array side
- Upgrading the array controller firmware online
- Reformatting NVMe devices manually
- Event monitoring
- Performance monitoring and tuning
- About tuning Dynamic Multi-Pathing (DMP) with templates
- DMP tuning templates
- Example DMP tuning template
- Tuning a DMP host with a configuration attribute template
- Managing the DMP configuration files
- Resetting the DMP tunable parameters and attributes to the default values
- DMP tunable parameters and attributes that are supported for templates
- DMP tunable parameters
- Appendix A. DMP troubleshooting
- Appendix B. Reference
Migrating Oracle Automatic Storage Management (ASM) disk groups on operating system devices to Dynamic Multi-Pathing (DMP) devices
When an existing ASM disk group uses operating system native devices as disks, you can migrate these devices to Dynamic Multi-Pathing control. If the OS devices are controlled by other multi-pathing drivers, this operation requires system downtime to migrate the devices to DMP control.
Plan for system downtime for the following procedure.
After this procedure, the ASM disk group uses the migrated DMP devices as its disks.
"From ASM" indicates that you perform the step as the user running the ASM instance.
"As root user" indicates that you perform the step as the root user.
To migrate an ASM disk group from operating system devices to DMP devices
- Stop the applications and shut down the database.
- From ASM, identify the ASM disk group that you want to migrate, and identify the disks under its control.
- From ASM, dismount the ASM disk group.
- If the devices are controlled by other multi-pathing drivers, migrate the devices to DMP control. Perform these steps as root user.
Migrate from PowerPath or Device Mapper Multipath.
- As root user, use the raw command to remove the raw devices that were created for the particular OS devices.
- As root user, enable DMP support for the ASM disk group identified in step 2.
# vxdmpraw enable username groupname mode [devicename ...]
where username represents the ASM user running the ASM instance, groupname represents the UNIX/Linux groupname of the specified user-id, and mode represents the permissions to set on the device. If you specify one or more devicenames, DMP support for ASM is enabled for those devices. If you do not specify a devicename, DMP support is enabled for all devices in the system that have an ASM signature.
- From ASM, set ASM_DISKSTRING as appropriate. The preferred setting is
/dev/vx/rdmp/* - From ASM, confirm that the devices are available to ASM.
- From ASM, mount the ASM disk groups. The disk groups are mounted on DMP devices.
Example: To migrate an ASM disk group from operating system devices to DMP devices
- From ASM, identify the ASM disk group that you want to migrate, and identify the disks under its control.
SQL> select name, state from v$asm_diskgroup; NAME STATE ------------------------------ ----------- ASM_DG1 MOUNTED
SQL> select path , header_status from v$asm_disk where header_status='MEMBER'; NAME PATH HEADER_STATUS ------------------------------------------- ASM_DG1_0000 /dev/vx/rdmp/sda MEMBER ASM_DG1_0001 /dev/vx/rdmp/sdc MEMBER ASM_DG1_0002 /dev/vx/rdmp/sdd MEMBER
- From ASM, dismount the ASM disk group.
SQL> alter diskgroup ASM_DG1 dismount; Diskgroup altered. SQL> select name , state from v$asm_diskgroup; NAME STATE ------------------------------ ----------- ASM_DG1 DISMOUNTED
- If the devices are controlled by other multi-pathing drivers, migrate the devices to DMP control. Perform these steps as root user.
- As root user, enable DMP support for the ASM disk group identified in step 2, in one of the following ways:
To migrate selected ASM diskgroups, use the vxdmpadm command to determine the DMP nodes that correspond to the OS devices.
# vxdmpadm getdmpnode nodename=sdd NAME STATE ENCLR-TYPE PATHS ENBL DSBL ENCLR-NAME ========================================================== EVA4k6k0_0 ENABLED EVA4K6K 4 4 0 EVA4k6k0
Use the device name in the command below:
# vxdmpraw enable oracle dba 660 eva4k6k0_0 \ eva4k6k0_9 emc_clariion0_243If you do not specify a devicename, DMP support is enabled for all devices in the disk group that have an ASM signature. For example:
# vxdmpraw enable oracle dba 660
- From ASM, set ASM_DISKSTRING.
SQL> alter system set ASM_DISKSTRING='/dev/vx/rdmp/*'; System altered. SQL> show parameter ASM_DISKSTRING; NAME TYPE VALUE -------------------------- --------- ------------------- asm_diskstring string /dev/vx/rdmp/*
- From ASM, confirm that the devices are available to ASM.
SQL> select path , header_status from v$asm_disk where header_status='MEMBER';
NAME PATH HEADER_STATUS --------------------------------------------------- /dev/vx/rdmp/emc_clariion0_243 MEMBER /dev/vx/rdmp/eva4k6k4k0_0 MEMBER /dev/vx/rdmp/eva4k6k0_1 MEMBER - From ASM, mount the ASM disk groups. The disk groups are mounted on DMP devices.
SQL> alter diskgroup ASM_DG1 mount; Diskgroup altered. SQL> select name, state from v$asm_diskgroup; NAME STATE ------------------------------ ----------- ASM_DG1 MOUNTED
SQL> select path , header_status from v$asm_disk where header_status='MEMBER'; NAME PATH HEADER_STATUS ---------------------------------------------------------- ASM_DG1_0002 /dev/vx/rdmp/emc_clariion0_243 MEMBER ASM_DG1_0000 /dev/vx/rdmp/eva4k6k0_1 MEMBER ASM_DG1_0001 /dev/vx/rdmp/eva4k6k0_9 MEMBER