Linux on 390 Port <[email protected]> wrote on 06/24/2010 12:24:38 PM:
> Alan Altmark/Endicott/i...@ibmus > Sent by: Linux on 390 Port <[email protected]> > > 06/24/2010 12:24 PM > > Please respond to > Linux on 390 Port <[email protected]> > > To > > [email protected] > > cc > > Subject > > Re: Shared fcp between two linux guests > > On Thursday, 06/24/2010 at 10:59 EDT, Richard Troth <[email protected]> > wrote: > > > > NPIV is not turned on at the lpar level, but it is turned on at the > SAN > > > level. > > > > If you're sharing the same physical FCP adapter(s) between the two > > Linux guests, then you probably need NPIV (at the LPAR level). > > > > I cannot imagine how your other Linux guests are able to share a LUN > > if the storage frame sees the same Linux-side WWPN (FCP WWPN). Since > > you indicated that your SuSE guests *can* share a LUN between them, I > > have to ask if they are using different physical FCP adapters or if > > there is NPIV in play for the FCP adapter(s) they are using. What's > > the deal there? > > > > The only time I have been able to share a LUN, the storage frame has > > always seen different "HBA-side" WWPNs, whether physically different > > FCP adapters or with NPIV. > > > > Try reversing the order in qhich the guests are brought up to test > things. > > > > > Jun 21 15:36:52 tdcrac02 kernel: zfcp: The adapter 0.0.8001 reported > the > > > following characteristics: > > > Jun 21 15:36:52 tdcrac02 kernel: zfcp: Switched fabric fibrechannel > > > network detected at adapter 0.0.8001. > > > Jun 21 15:36:52 tdcrac02 kernel: zfcp: unit erp failed on unit > > > 0x0020000000000000 on port 0x5001738001820141 on adapter 0.0.8001 > > If this is an older machine without NPIV, that "unit erp" error has been > seen when the guest was not authorized using the LUN Access Control > program. > > 'erp' is 'error recovery program'. The device driver gets failures at the > LUN, port, and unit levels (I think). Perhaps Ray Higgs can shed some > light on it. > > Alan Altmark > z/VM Development > IBM Endicott > > ---------------------------------------------------------------------- > 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 more information on Linux on System z, visit > http://wiki.linuxvm.org/ LUN Access Control is not available for z10. I'd use san_disc to investigate. Go through the example in the manpage. If you do not get what you expect from port_list, there is probably a zoning problem. Use the brocade switch console to address this. If you do not get what you expect from report_luns, then there is a lun masking problem. Use the XIV management tools to address. Sometimes getting LUN numbers correct can be difficult because of all of the zeros. Did you mean 0x0002 instead of 0x0020? Regards, Ray Higgs System z FCP Development Bld. 706, B24 2455 South Road Poughkeepsie, NY 12601 (845) 435-8666, T/L 295-8666 [email protected] ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
