Tom -- What I read from what you posted is that the storage side must be servicing all paths. That's a legit requirement.
There is then the question of what VM does with those four paths. Does it perform some kind of rotation, spreading the I/O load? Or do the other paths serve only for fail-over? (I should know this.) But VM would not bring the paths online unless the storage system responded. Do a 'q edev addr details' and you'll know if they're up. -- R; <>< Rick Troth Velocity Software http://www.velocitysoftware.com/ On Wed, Mar 2, 2011 at 10:22, Tom Huegel <tehue...@gmail.com> wrote: > Someone posed this question to me recently and after reading everything I > can find I have become confused. > > I thought I'd through it out here and see if anyone has a good answer. > > This is to support z/LINUX guests. > > edevice 0200 type fba attr scsi fcp_dev F610, > wwpn 50060E80058D2110 lun 0038000000000000, > fcp_dev F510 wwpn 50060E80058D2130 lun 0038000000000000, > fcp_dev F410 wwpn 50060E80058D2120 lun 0038000000000000, > fcp_dev F310 wwpn 50060E80058D2100 lun 0038000000000000 > > (I disagree with the next statement, I think the Multi-pathing takes place > outside of the control unit.) > > · Documentation indicated that, despite being able to define > Multi-pathing for “attr scsi” Emulated FBA Devices, the Storage Subsystem > has to be capable of supporting this Multi-pathing for this to be effective. > > · Does the z/VM support Multi-pathing in this configuration?
