Thanks for the reply Rick. I'll talk with the storage team about pursuing NPIV. In the meantime, does anyone know if there is a way to present the storage so that it is recognized by the Host LUN # and not the LDEV #?
VR, Justin Sollenberger -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Rick Troth Sent: Thursday, July 10, 2014 3:48 PM To: [email protected] Subject: Re: LUN connection problem SLES11 SP3 Really glad you found the problem and got things working. On 07/10/2014 03:10 PM, Sollenberger, Justin W CIV DISA (US) wrote: > The issue was that the LUN id needed to add it on the server did not > match what we had to use in the past. Past LUN's were added using the > LDEV. The problem with that is that duplicates can exist because of > multiple host groups within the array. In this case LUN 0x0041 was a > duplicate and was recognized as 0x0141 instead. If they were > recognized by the assigned Host LUN # that wouldn't be an issue since > those can't be duplicated within an array/host group. I assume this > is expected behavior when you are not using NPIV? Is there a way to > anticipate how they will be recognized on the servers? This makes sense when NPIV is not part of the story. All of your FCP adapters (subchannels) on a given physical FCP port look like the same host. Think TCP/IP, compare WWPN to an IP address ... a given host can have programs listening on various ports. But two programs on the same port ... just doesn't work. The Linux system is more like a "client" than a server in the SAN game, but please excuse the verbiage. Think of the 0x0041 like a TCP port. The storage system needs to distinguish 0x0041 from 0x0141 since both LUNs are used by the same "host" WWPN. NPIV changes this in that each subchannel behind the one FCP port has its own WWPN (looks like a unique host). I confess that NPIV will mean additional effort, but if I were in your situation then I'd try it going forward (any additional FCP adapters you might add). Should you ever want to share a LUN across systems in the same CEC (whether same LPAR or not), there's no way to do it without NPIV. But with NPIV, you can share a LUN much like you can share DASD on FICON. -- Rick Troth Senior Software Developer Velocity Software Inc. Mountain View, CA 94041 Main: (877) 964-8867 Direct: (614) 594-9768 [email protected] <mailto:[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/ ---------------------------------------------------------------------- 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/
smime.p7s
Description: S/MIME cryptographic signature
