Since we're on the topic of SAN ... What Mark said is true. While Alan points out correctly that the (virtual or real) WWPN follows the subchannel, if you connect Linux directly to the SAN, you'll still have to tell Linux which WWPN+LUN pair(s) to use. My conclusion after careful analysis: hemorrhoid. (In layman's terms, that's a pain in the you-know-where.) Even with spiffy discovery tools, this is still a silly way to do it in numbers larger than a box of donuts.
Storage is much more effectively managed by the host (in this case, the hypervisor, VM/CP). EDEV allows such management. EDEV presents its own demands, but it makes MANAGING storage a lot easier than twiddling WWPNs and LUN numbers and attaching FCP adapters. -- R; <>< On Thu, Jun 25, 2009 at 15:59, Mark Post<[email protected]> wrote: >>>> On 6/25/2009 at 3:55 PM, Alan Altmark <[email protected]> wrote: > -snip- >> It doesn't matter what user ID is used. The NPIV WWPN is assigned to the >> subchannel. ATTACH the sc to whatever guest you want. (The old >> userid-based LUN Access Control authorization scheme is long gone.) > > True, but having to configure another guest with the WWPN and LUN information > is a pain in the neck. It's easier if you're running on the same guest so > you can have that config information "right there." > > > Mark Post > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
