Mpio SDD PCM SDD

IBM Power Systems Technical University
October 1822, 2010 Las Vegas, NV
AD07 Working with MPIO, SDDPCM, SDD and SAN boot
John Hock Dan Braden Power Systems Advanced Technical Skills
2010 IBM Corporation
Agenda
Multi-path basics Multi Path I/O (MPIO)
Useful Path
MPIO Commands
priorities
Failed
Path Recovery and path health checking
path management SDD and SDDPCM Multi-path code choices for DS4000, DS5000 and DS3950 SAN Boot
MPIO
How many paths for a LUN?

Paths = (# of paths from server to switch) x (# paths from storage to switch) Here there are potentially 6 paths per LUN But reduced via: LUN masking at the storage Assign LUNs to specific FC adapters at the host, and thru specific ports on the storage Zoning WWPN or SAN switch port zoning 4 paths per LUN are sufficient for availability and reduce CPU overhead for choosing the path Path selection overhead is relatively low MPIO has no practical limits to number of paths Other products have path limits SDDPCM limited to 32 paths per LUN
Server
FC Switch
Storage
Path selection benefits and costs

Path selection algorithms choose a path to hopefully minimize latency added to an IO to send it over the SAN to the storage Latency to send a 4 KB IO over a 8 Gbps SAN link is 4 KB / (8 Gb/s x 0.1 B/b x1048576 KB/GB) = 0.0048 ms Multiple links may be involved, and round trip for an IO As compared to fastest IO service times around 1 ms If the links arent busy, there likely wont be much if any savings Costs of path selection algorithms CPU cycles to choose the best path Memory to keep track of in-flight IOs down each path, or Memory to keep track of IO service times down each path Latency added to the IO to choose the best path
Disk configuration
The disk vendor dictates what multi-path code can be used, supplies the filesets for it and supports it A fileset is loaded to update the ODM to support the storage AIX then recognizes and appropriately configures the disk Without this, disks are configured using a generic ODM definition Performance and error handling may suffer as a result # lsdev Pc disk displays supported storage The multi-path code will be a different fileset Unless using the MPIO thats included with AIX
Multi-path IO with VIO and VSCSI LUNs

Two layers of multi-path code: VIOC and VIOS
VIO Client MPIO
Disks always use MPIO and all IO for a LUN normally goes to one VIOS VIOS uses the multi-path code specified for the disk subsystem
VIO Server
Multi-path code
VIO Server
Multi-path code
Set path priorities for hdisks so half the hdisks use one VIOS and half use the other
Disk Subsystem
Multi-path IO with VIO and NPIV

VIOC has virtual FC adapters (vFC)
VIO Client
Multi-path code
VFC VFC VFC VFC
Potentially
one vFC adapter for every real FC adapter in each VIOC of 64 vFC adapters per real FC adapter recommended
Maximum
VIO Server
VIO Server
VIOC uses multi-path code that the disk subsystem supports IOs for a LUN can go thru both VIOSs
Disk Subsystem
One layer of multi-path code
What is MPIO?
MPIO is an architecture designed by AIX development MPIO is also a commonly used acronym for Multi-Path IO
In this presentation MPIO refers explicitly to the architecture, not the acronym
Why was the MPIO architecture developed?

With the advent of SANs, each disk subsystem vendor wrote their own multi-path code These multi-path code sets were usually incompatible Mixing disk subsystems was usually not supported on the same system, and if they were, they usually required their own FC adapters Integration with AIX IO error handling and recovery Several levels of IO timeouts: basic IO timeout, FC path timeout, etc
MPIO architecture details available to disk subsystem vendors

Compliant code requires a Path Control Module (PCM) for each disk subsystem Default PCMs for SCSI and FC exist on AIX and often used by the vendors Capabilities exist for different path selection algorithms Disk vendors have been moving towards MPIO compliant code
Overview of MPIO Architecture

LUNs show up as an hdisk
Architected No
for 32 K paths
more than 16 is necessary PCMs exist for FC, SCSI may write optional PCMs
PCM: Path Control Module

Default Vendors May
provide commands to manage paths
Allows various algorithms to balance use of paths Full support for multiple paths to rootvg Hdisks can be Available, Defined or non-existent Paths can also be Available, Defined, Missing or non-existent Path status can be enabled, disabled or failed if the path is Available One must get the device layer correct, before working with the path status layer
MPIO support
Storage subsystem family IBM ESS, DS6000, DS8000, DS4000, DS5000, SVC XIV NSeries EMC Symmetrix HDS HP (not EVA) some members of XP family SCSI VIO VSCSI MPIO code SDDPCM Default FC PCM Default FC PCM Default FC PCM HDLM Default FC PCM Default SCSI PCM Default SCSI PCM Multi-path algorithm fail_over, round_robin, load balance, load balance port fail_over, round_robin fail_over, round_robin fail_over, round_robin fail_over, round robin, extended round robin fail_over, round_robin fail_over, round_robin fail_over
10
Non-MPIO multi-path code
Storage subsystem family IBM DS4000 and DS5000 EMC HP HDS Vertias supported storage
Multi-path code RDAC Power Path AutoPath HDLM (older versions) DMP
11
Mixing multi-path code sets

The disk subsystem vendor specifies what multi-path code is supported for their storage
The
disk subsystem vendor supports their storage, the server vendor generally doesnt
You can mix multi-path code compliant with MPIO and even share adapters
Exception
with HP and HDS which require their own adapters
Generally one non-MPIO compliant code set can exist with other MPIO compliant code sets
Except The
that SDD and RDAC can be mixed on the same LPAR
non-MPIO compliant code must be using its own adapters
Devices of a given type use only one multi-path code set

E.G.,
you cant used SDDPCM for one DS8000 and SDD for another DS8000 on the same AIX instance
12
Sharing Fibre Channel Adapter ports

HP and HDS require adapters dedicated to their disk subsystems Disk using MPIO compliant code sets can share adapter ports Its recommended that disk and tape use separate ports
tape and disk devices require incompatible HBA performance settings
13
MPIO Commands
lspath list paths, path status and path attributes for a disk chpath change path status or path attributes
Enable
or disable paths
rmpath delete or change path state

Putting One
a path into the defined mode means it wont be used (from available to defined)
cannot define/delete the last path of a device
mkpath add another path to a device or makes a defined path available

Generally
cfgmgr is used to add new paths
chdev change a devices attributes (not specific to MPIO) cfgmgr add new paths to an hdisk or make defined paths available (not specific to MPIO)
14
Useful MPIO Commands

List status of the paths and the parent device (or adapter) # lspath -Hl <hdisk#> List connection information for a path # lspath -l hdisk2 -F"status parent connection path_status hdisk2 Enabled fscsi0 203900a0b8478dda,f000000000000 Available hdisk2 Enabled fscsi0 201800a0b8478dda,f000000000000 Available hdisk2 Enabled fscsi1 201900a0b8478dda,f000000000000 Available hdisk2 Enabled fscsi1 203800a0b8478dda,f000000000000 Available The connection field contains the storage port WWPN In the case above, all paths go to storage WWPN 203800a0b8478dda List a specific path's attributes # lspath -AEl hdisk2 -p fscsi0 w 203900a0b8478dda,f00000000000
scsi_id
0x30400
SCSI ID
False
node_name 0x200800a0b8478dda FC Node Name False priority

Priority
15
True
Path priorities
A Priority Attribute for paths can be used to specify a preference for path IOs. How it works depends whether the hdisks algorithm attribute is set to fail_over or round_robin. algorithm=fail_over
the the Set
path with the higher priority value handles all the IOs unless there's a path failure. other path(s) will only be used when there is a path failure. the primary path to be used by setting it's priority value to 1, and the next path's priority (in case of path failure) to 2, and so on.
algorithm=round_robin
If
the priority attributes are the same, then IOs go down each path equally.
In
the case of two paths, if you set path As priority to 1 and path Bs to 255, then for every IO going down path A, there will be 255 IOs sent down path B.
To change the path priority of an MPIO device on a VIO client:

#
chpath -l hdisk0
-p vscsi1 -a priority=25
16
Path priorities
# lsattr -El hdisk20 PCM PCM/friend/otherapdisk algorithm fail_over hcheck_interval 60 hcheck_mode nonactive lun_id 0x5000000000000 node_name 0x20060080e517b6ba queue_depth 10 reserve_policy single_path ww_name 0x20160080e517b6ba Path Control Module Algorithm Health Check Interval Health Check Mode Logical Unit Number ID FC Node Name Queue DEPTH Reserve Policy FC World Wide Name False True True True False False True True False
# lspath -l hdisk9 -F"parent connection status path_status" fscsi1 20160080e517b6ba,5000000000000 Enabled Available fscsi1 20170080e517b6ba,5000000000000 Enabled Available # lspath -AEl hdisk9 -p fscsi1 -w"20160080e517b6ba,5000000000000" scsi_id 0x10a00 SCSI ID False node_name 0x20060080e517b6ba FC Node Name False priority 1 Priority True
17
Path priorities why change them?

With VIOCs, send half the IOs to one VIOS and half to the other VIOS
Set
priorities for half the LUNs to use VIOSa and half to use VIOSb both VIOSs CPU and adapters is the only option at the VIOC for VSCSI disks
Uses
algorithm=fail_over
With NSeries have the IOs go the primary controller for the LUN
Set
via the dotpaths script that comes with Nseries filesets
18
Path Health Checking and Recovery Validate Path is Working

For SDDPCM and MPIO compliant disks, two hdisk attributes apply: # lsattr -El hdisk26 hcheck_interval 0 Health Check Interval hcheck_mode nonactive Health Check Mode True
True
hcheck_interval Defines how often the health check is performed on the paths for a device. The attribute supports a range from 0 to 3600 seconds. When a value of 0 is selected (the default), health checking is disabled hcheck_mode Determines which paths should be checked when the health check capability is used: enabled: Sends the healthcheck command down paths with a state of enabled failed: Sends the healthcheck command down paths with a state of failed nonactive: (Default) Sends the healthcheck command down paths that have no active I/O, including paths with a state of failed. If the algorithm selected is failover, then the healthcheck command is also sent on each of the paths that have a state of enabled but have no active IO. If the algorithm selected is round_robin, then the healthcheck command is only sent on paths with a state of failed, because the round_robin algorithm keeps all enabled paths active with IO. Enable path health checking if paths arent normally used, and only for enough LUNs to ensure physical paths are checked Often turning on health checking for a single LUN is sufficient to monitor all physical paths status An error shows up in the error log if a path fails Consider setting up error notification Failed Path Recovery To enable a failed path: # chpath -l hdisk1 -p <parent> -s enable
19
Path management with MPIO

Includes examining, adding, removing, enabling and disabling paths

Adapter failure and replacement VIOS upgrades (VIOS or multi-path code) Cable failure and replacement Storage controller/port failure and repair Paths will not be in use if the adapter has failed, paths will be in the failed state Remove paths with # rmpath l <hdisk> -p <parent> -w <connection> [-d] -d will remove the path, without it the path will changed to Defined Remove the adapter with # rmdev Rdl <fcs#> Replace the adapter cfgmgr Check the paths with lspath Avoid timeouts, application delays or performance impacts and potential error recovery bugs
Adapter replacement

Its better to stop using a path before you know the path will disappear
20
Active/Active vs. Active/Passive Disk Subsystem Controllers

IOs for a LUN can be sent to any storage port with Active/Active controllers LUNs are balanced across controllers for Active/Passive disk subsystems
So
a controller is active for some LUNs, but passive for the others
IOs for a LUN are only be sent to the Active controllers port for disk subsystems with Active/Passive controllers
ESS,
DS6000, and DS8000 have active/active controllers DS4000, DS5000, DS3950, NSeries have active/passive controllers The NSeries passive controller can accept IOs but IO latency is affected The passive controller takes over in the event the active controller or all paths to it fail MPIO recognizes Active/Passive disk subsystems and sends IOs only to the primary controller
Except
under failure conditions, then the active/passive role switches for the affected
LUNs
21
SDD: An Overview
SDD = Subsystem Device Driver Used with IBM ESS, DS6000, DS8000 and the SAN Volume Controller, but is not MPIO compliant.
A
host attachment fileset (populates the ODM) and SDD fileset are both installed attachment: ibm2105.rte devices.sdd.<sdd_version>.rte
Host
SDD:
LUNs show up as vpaths, with an hdisk device for each path

32
paths maximum per LUN, but less are recommended with more than 600 LUNs
One installs SDDPCM or SDD, not both. No support for rootvg, dump or paging devices

One can exclude disks from SDD control using the excludesddcfg command Mirror rootvg across two separate LUNs on different adapters for availability
22
SDD
Load balancing algorithms
fo: rr: lb:
failover round robin load balancing (aka. df or the default) and chooses adapter with fewest in-flight IOs load balancing sequential optimized for sequential IO round robin sequential optimized for sequential IO
lbs: rrs:
The datapath command is used to examine vpaths, adapters, paths, vpath statistics, path statistics, adapter statistics, dynamically change the load balancing algorithm, and other administrative tasks such as adapter replacement, disabling paths, etc. mkvg4vp is used instead of mkvg, and extendvg4vp is used instead of extendvg SDD automatically recovers failed paths that have been repaired via the sddsrv daemon
23
SDDPCM: An Overview
SDDPCM = Subsystem Device Driver Path Control Module SDDPCM is MPIO compliant and can be used with IBM ESS, DS6000, DS8000, DS4000 (most models), DS5000, DS3950 and the SAN Volume Controller
A
host attachment fileset (populates the ODM) and SDDPCM fileset are both installed attachment: devices.fcp.disk.ibm.mpio.rte devices.sddpcm.<version>.rte
Host
SDDPCM:
LUNs show up as hdisks, paths shown with pcmpath or lspath commands

16
paths per LUN supported
Provides a PCM per the MPIO architecture One installs SDDPCM or SDD, not both. SDDPCM is recommended and strategic
24
SDDPCM
Load balancing algorithms
rr lb fo
- round robin - load balancing based on in-flight IOs per adapter - failover policy
lbp
- load balancing port (for ESS, DS6000, DS8000 and SVC only) based on in-flight IOs per adapter and per storage port
The pcmpath command is used to examine hdisks, adapters, paths, hdisk statistics, path statistics, adapter statistics, dynamically change the load balancing algorithm, and other administrative tasks such as adapter replacement, disabling paths SDDPCM automatically recovers failed paths that have been repaired via the pcmserv daemon
MPIO
health checking can also be used, and can be dynamically set via the pcmpath command. This is recommended. Set the hc_interval to a non-zero value for an appropriate number of LUNs to check the physical paths.
25
Path management with SDDPCM and the pcmpath command

# pcmpath query adapter List adapters and status # pcmpath query device List hdisks and paths # pcmpath query port List DS8000/DS6000/SVC ports # pcmpath query devstats List hdisk/path IO statistics # pcmpath query adaptstats List adapter IO statistics # pcmpath query portstats List DS8000/DS6000/SVC port statistics # pcmpath query essmap List rank, LUN ID and more for each hdisk # pcmpath set adapter Disable/enable paths to adapter # pcmpath set device path Disable/enable paths to a hdisk # pcmpath set device algorithm Dynamically change path algorithm # pcmpath set device hc_interval Dynamically change health check interval # pcmpath disable/enable ports Disable/enable paths to a disk port # pcmpath query wwpn Display all FC adapter WWPNs And more SDD offers the similar datapath command
26

# pcmpath query device DEV#: 2 DEVICE NAME: hdisk2 TYPE: 2145 ALGORITHM: Load Balance SERIAL: 600507680190013250000000000000F4 ========================================================================== Path# Adapter/Path Name State Mode Select Errors 0 fscsi0/path0 OPEN NORMAL 40928736 0 1* fscsi0/path1 OPEN NORMAL 16 0 2 fscsi2/path4 OPEN NORMAL 43927751 0 3* fscsi2/path5 OPEN NORMAL 15 0 4 fscsi1/path2 OPEN NORMAL 44357912 0 5* fscsi1/path3 OPEN NORMAL 14 0 6 fscsi3/path6 OPEN NORMAL 43050237 0 7* fscsi3/path7 OPEN NORMAL 14 0
* Indicates path to passive controller 2145 is a SVC which has active/passive nodes for a LUN DS4000, DS5000 and DS3950 also have active/passive controllers IOs will be balanced across paths to the active controller
27

# pcmpath query devstats Total Dual Active and Active/Asymmetrc Devices : 67 DEV#: 2 DEVICE NAME: hdisk2 =============================== Total Read Total Write I/O: 169415657 2849038 SECTOR: 2446703617 318507176 Transfer Size: <= 512 183162 <= 4k 67388759
Active Read 0 0 <= 16K 35609487
Active Write 0 0 <= 64K 46379563
Maximum 20 5888 > 64K 22703724
Maximum value useful for tuning queue depths
28
SDD & SDDPCM: Getting Disks configured correctly

Install the appropriate filesets SDD or SDDPCM for the required disks (and host attachment fileset) If you are using SDDPCM, install the MPIO fileset as well which comes with AIX devices.common.IBM.mpio.rte Host attachment scripts http://www.ibm.com/support/dlsearch.wss?rs=540&q=host+scripts&tc=ST52G7&dc=D410 Reboot or start the sddsrv/pcmsrv daemon smitty disk -> List All Supported Disk Displays disk types for which software support has been installed Or # lsdev -Pc disk | grep -i mpio disk mpioosdisk fcp MPIO Other FC SCSI Disk Drive disk 1750 fcp IBM MPIO FC 1750 disk 2105 fcp IBM MPIO FC 2105 disk 2107 fcp IBM MPIO FC 2107 disk 2145 fcp MPIO FC 2145 disk DS3950 fcp IBM MPIO DS3950 Array Disk disk DS4100 fcp IBM MPIO DS4100 Array Disk disk DS4200 fcp IBM MPIO DS4200 Array Disk disk DS4300 fcp IBM MPIO DS4300 Array Disk disk DS4500 fcp IBM MPIO DS4500 Array Disk disk DS4700 fcp IBM MPIO DS4700 Array Disk disk DS4800 fcp IBM MPIO DS4800 Array Disk disk DS5000 fcp IBM MPIO DS5000 Array Disk disk DS5020 fcp IBM MPIO DS5020 Array Disk
29
Migration from SDD to SDDPCM

Migration from SDD to SDDPCM is fairly straightforward and doesn't require a lot of time. The procedure is documented in the manual: Varyoff your SDD VGs Stop the sddsrv daemon via stopsrc -s sddsrv Remove the SDD devices (both vpaths and hdisks) via instructions below Remove the dpo device Uninstall SDD and the host attachment fileset for SDD Install the host attachment fileset for SDDPCM and SDDPCM Configure the new disks (if you rebooted it's done, else run cfgmgr and startsrc s pcmserv) Varyon your VGs - you're back in business To remove the vpaths and hdisks, use the following inline script: # for i in `lsdev -Cc disk | egrep "vpath|2105" | cut -f1 -d" "` > do > rmdev -dl $i > done Or an even easier method which removes the dpo device, vpaths and hdisks. rmdev -Rdl dpo No exportvg/importvg is needed because LVM keeps track of PVs via PVID Effective queue depths change (and changes to queue_depth will be lost): SDD effective queue depth = # paths for a LUN x queue_depth SDDPCM effective queue depth = queue_depth
30
Multi-path code choices for DS4000/DS5000/DS3950

These disk subsystems might use RDAC, MPIO or SDDPCM
Choices
depend on model and AIX level uses MPIO and is recommended not supported on VIOS yet for these disk subsystems so use MPIO
MPIO is strategic
SDDPCM SDDPCM
SAN cabling/zoning is more flexible with MPIO/SDDPCM than with RDAC

RDAC
requires fcsA be connected to controllerA and fcsB connected to controllerB with no cross connections IO for a LUN goes to its primary controller
These disk subsystem have active/passive controllers

All
Unless the paths to it fail, or the controller fails, then the other controller takes over the LUN
Storage
administrator assigns half the LUNs to each controller vary among models and AIX levels
The manage_disk_drivers command is used to choose the multi-path code

Choices
DS3950, DS5020, DS5100, DS5300 use MPIO/SDDPCM only

31
Multi-path code choices for DS3950, DS4000 and DS5000

# manage_disk_drivers -l Device Present Driver 2810XIV AIX_AAPCM DS4100 AIX_SDDAPPCM DS4200 AIX_SDDAPPCM DS4300 AIX_SDDAPPCM DS4500 AIX_SDDAPPCM DS4700 AIX_SDDAPPCM DS4800 AIX_SDDAPPCM DS3950 AIX_SDDAPPCM DS5020 AIX_SDDAPPCM DS5100/DS5300 AIX_SDDAPPCM DS3500 AIX_AAPCM Driver Options AIX_AAPCM,AIX_non_MPIO AIX_APPCM,AIX_fcparray AIX_APPCM,AIX_fcparray AIX_APPCM,AIX_fcparray AIX_APPCM,AIX_fcparray AIX_APPCM,AIX_fcparray AIX_APPCM,AIX_fcparray AIX_APPCM AIX_APPCM AIX_APPCM AIX_APPCM
To set the driver for use:

# manage_disk_drivers -d <device> -o <driver_option>
AIX_AAPCM - MPIO with active/active controllers AIX_APPCM - MPIO with active/passive controllers AIX_SDDAPPCM - SDDPCM AIX_fcparray - RDAC
32
Other MPIO commands for DS3/4/5000

# mpio_get_config Av
Frame id 0: Storage Subsystem worldwide name: 608e50017be8800004bbc4c7e Controller count: 2 Partition count: 1 Partition 0: Storage Subsystem Name = 'DS-5020' hdisk LUN # Ownership hdisk4 0 A (preferred) hdisk5 1 B (preferred) hdisk6 2 A (preferred) hdisk7 3 B (preferred) hdisk8 4 A (preferred) hdisk9 5 B (preferred)
# sddpcm_get_config Av
User Label Array1_LUN1 Array2_LUN1 Array3_LUN1 Array4_LUN1 Array5_LUN1 Array6_LUN1
33
Storage Area Network Boot

Requirements for SAN Booting System with FC boot capability
Appropriate Disk
microcode (system, FC adapter, disk subsystem and FC switch)
subsystem supporting AIX FC boot
Some older systems dont support FC boot, if in doubt, check the sales manual SAN disk configuration Create the SAN LUNs and assign them to the system's FC adapters WWPNs prior to installing the system
For
non-MPIO configurations, assign one LUN to one WWPN to keep it simple
AIX installation Boot from installation CD or NIM, this runs the install program
When
you do the installation you'll get a list of disks that will be on the SAN for the system the disks for installing rootvg You may want to know the SAN disk volume IDs if you want a specific LUN for rootvg. You should also see the size of the disk, so that's a good clue about which one(s) to use for rootvg.
Choose
34
Storage Area Network Booting: Pros & Cons

The main benefits of SAN rootvg
Performance Availability Ability Ability
< 2 ms write, 5-10 ms read
with built in RAID protection
to easily redeploy disk to FlashCopy the rootvg for backup
SAN rootvg disadvantages

SAN
problems can cause loss of access to rootvg ~ not an issue as app data is on SAN anyway loss of system dump and diagnosis if loss of access to SAN is caused by a kernel bug to change multi-path IO code Not an issue with dual VIOS
Potential Difficult
SAN boot thru VIO with VSCSI is different

SAN
boot thru VIO with NPIV is like SAN boot
35
Changing multi-path IO code for rootvg not so easy

How do you change/update rootvg multi-path code when its in use? Changing from SDD to SDDPCM (or vice versa) requires contacting support if booting from SAN, or:
Move
rootvg to internal SAS disks, e.g., using extendvg, migratepv, reducevg, bosboot and bootlist, or use alt_disk_install the multi-path code rootvg back to SAN versions of AIX require a newer version of SDD or SDDPCM
Change Move
Newer
Follow procedures in the SDD and SDDPCM manual for upgrades of AIX and/or the multi-path code Not an issue when using VIO with dual VIOSs
36
Switch attached fibre channel adapters

Set fscsi dynamic tracking to yes Allows dynamic SAN changes Set FC fabric event error recovery fast_fail to yes if the switches support it Switch fails IOs immediately without timeout if a path goes away Switches without support result in errors in the error log
# lsattr -El attach dyntrk fc_err_recov scsi_id sw_fc_class fscsi0 switch no delayed_fail 0x1c0d00 3
How this adapter is CONNECTED False Dynamic Tracking of FC Devices True FC Fabric Event Error RECOVERY Policy True Adapter SCSI ID False FC Class for Fabric True
# chdev l fscsi0 a dyntrk=yes a fc_err_recov=fast_fail P # shutdown Fr
Virtual FC adapters have these set to yes and fast_fail by default

37
Documentation
Infocenter Multiple Path IO http://publib.boulder.ibm.com/infocenter/aix/v6r1/index.jsp?topic=/com.ibm.aix.baseadmn/doc/ baseadmndita/dm_mpio.htm SDD and SDDPCM Support matrix: www.ibm.com/support/docview.wss?rs=540&uid=ssg1S7001350 Downloads and documentation for SDD www.ibm.com/support/docview.wss?rs=540&context=ST52G7&dc=D430&uid=ssg1S4000065 &loc=en_US&cs=utf-8&lang=en Downloads and documentation for SDDPCM: www.ibm.com/support/docview.wss?rs=540&context=ST52G7&dc=D430&uid=ssg1S4000201 &loc=en_US&cs=utf-8&lang=en
38

Mpio SDD PCM SDD

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Mpio SDD PCM SDD

Hochgeladen von

Copyright:

Verfügbare Formate

IBM Power Systems Technical University

October 1822, 2010 Las Vegas, NV

AD07 Working with MPIO, SDDPCM, SDD and SAN boot

John Hock Dan Braden Power Systems Advanced Technical Skills

2010 IBM Corporation

IBM Power Systems Technical University

Path Recovery and path health checking

2010 IBM Corporation

IBM Power Systems Technical University

How many paths for a LUN?

2010 IBM Corporation

IBM Power Systems Technical University

Path selection benefits and costs

2010 IBM Corporation

IBM Power Systems Technical University

2010 IBM Corporation

IBM Power Systems Technical University

Multi-path IO with VIO and VSCSI LUNs

2010 IBM Corporation

IBM Power Systems Technical University

Multi-path IO with VIO and NPIV

One layer of multi-path code

2010 IBM Corporation

IBM Power Systems Technical University

Why was the MPIO architecture developed?

MPIO architecture details available to disk subsystem vendors

2010 IBM Corporation

IBM Power Systems Technical University

Overview of MPIO Architecture

PCM: Path Control Module

provide commands to manage paths

2010 IBM Corporation

IBM Power Systems Technical University

2010 IBM Corporation

IBM Power Systems Technical University

Non-MPIO multi-path code

2010 IBM Corporation

IBM Power Systems Technical University

Mixing multi-path code sets

with HP and HDS which require their own adapters

that SDD and RDAC can be mixed on the same LPAR

non-MPIO compliant code must be using its own adapters

Devices of a given type use only one multi-path code set

2010 IBM Corporation

IBM Power Systems Technical University

Sharing Fibre Channel Adapter ports

tape and disk devices require incompatible HBA performance settings

2010 IBM Corporation

IBM Power Systems Technical University

rmpath delete or change path state

cannot define/delete the last path of a device

mkpath add another path to a device or makes a defined path available

cfgmgr is used to add new paths

2010 IBM Corporation

IBM Power Systems Technical University

Useful MPIO Commands

node_name 0x200800a0b8478dda FC Node Name False priority

IBM Power Systems Technical University

To change the path priority of an MPIO device on a VIO client:

2010 IBM Corporation

IBM Power Systems Technical University

2010 IBM Corporation