Please enter search query.
Search <book_title>...
Dynamic Multi-Pathing 7.3.1 Administrator's Guide - AIX
Last Published:
2017-11-03
Product(s):
InfoScale & Storage Foundation (7.3.1)
- 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 IBM Multipath IO (MPIO) or MPIO path control module (PCM)
- 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
- Dynamic Multi-Pathing for the Virtual I/O Server
- About Dynamic Multi-Pathing in a Virtual I/O server
- About the Volume Manager (VxVM) component in a Virtual I/O server
- Configuring Dynamic Multi-Pathing (DMP) on Virtual I/O server
- Configuring Dynamic Multi-Pathing (DMP) pseudo devices as virtual SCSI devices
- Extended attributes in VIO client for a virtual SCSI disk
- 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
- Configuring DMP for SAN booting
- Administering the root volume group (rootvg) under DMP control
- Running the bosboot command when LVM rootvg is enabled for DMP
- Extending an LVM rootvg that is enabled for DMP
- Reducing the native rootvg that is enabled for DMP
- Mirroring the root volume group
- Removing the mirror for the root volume group (rootvg)
- Cloning a LVM rootvg that is enabled for DMP
- Cleaning up the alternate disk volume group when LVM rootvg is enabled for DMP
- Using mksysb when the root volume group is under DMP control
- Upgrading Dynamic Multi-Pathing and AIX on a DMP-enabled rootvg
- Using Storage Foundation in the logical partition (LPAR) with virtual SCSI devices
- Setting up DMP for vSCSI devices in the logical partition (LPAR)
- About disabling DMP for vSCSI devices in the logical partition (LPAR)
- Preparing to install or upgrade Storage Foundation with DMP disabled for vSCSI devices in the logical partition (LPAR)
- Disabling DMP multi-pathing for vSCSI devices in the logical partition (LPAR) after installation or upgrade
- Adding and removing DMP support for vSCSI devices for an array
- How DMP handles I/O for vSCSI devices
- Running alt_disk_install, alt_disk_copy and related commands on the OS device when DMP native support is enabled
- 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
- Manually replacing a host bus adapter online
- Changing the characteristics of a LUN from the array side
- Upgrading the array controller firmware online
- 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
- DMP driver tunables
- Appendix A. DMP troubleshooting
- Appendix B. Reference
Mirroring the root volume group
You may want to create a mirror of the root volume group to add redundancy. For a root volume group that DMP controls, use the operating system commands to create the mirror.
To mirror a root volume group
- Extend the DMP-enabled rootvg to a second DMP device.
See Extending an LVM rootvg that is enabled for DMP.
If the rootvg is already extended over DMP device using the recommended steps, then go to step 2.
- Create the mirror of the root volume group.
# mirrorvg rootvg 0516-1734 mklvcopy: Warning, savebase failed. Please manually run 'savebase' before rebooting. .... 0516-1804 chvg: The quorum change takes effect immediately. 0516-1126 mirrorvg: rootvg successfully mirrored, user should perform bosboot of system to initialize boot records. Then, user must modify bootlist to include: hdisk74 hdisk70.
- As the output of the mirrorvg command indicates, run the savebase command on
/dev/ipldevice. If the savebase command returns a non-zero value, then retry the command on the paths of current boot disk (hdisk70, hdisk72) until it succeeds.# savebase -d /dev/ipldevice
# echo $? 0
- As the output of the mirrorvg command indicates, run the bosboot command to initialize the boot records. If the bosboot command fails on
/dev/ipldevice, then retry the command on the paths of current boot disk until it succeeds.# bosboot -ad /dev/ipldevice A previous bosdebug command has changed characteristics of this boot image. Use bosdebug -L to display what these changes are. bosboot: Boot image is 56863 512 byte blocks. - Include the paths corresponding to the mirror device in the boot list. In this example, hdisk70 and hdisk72 are the original boot disk. Add the paths for hdisk73 and hdisk74.
# bootlist -m normal -o hdisk70 blv=hd5 hdisk72 blv=hd5
# bootlist -m normal hdisk70 hdisk72 hdisk73 hdisk74 blv=hd5
# bootlist -m normal -o hdisk70 blv=hd5 hdisk72 blv=hd5 hdisk73 blv=hd5 hdisk74 blv=hd5
- Verify the rootvg.
# lsvg -p rootvg rootvg: PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION hdisk70 active 39 361 127..05..00..101..128 hdisk73 active 639 361 127..05..00..101..128