Mark, I should have mentioned the reply from the command zlinux1:~ # lszfcp -D > 0.0.5400/0x50050763070342f3/0x4010400b00000000 0:0:1:1074479120 is from the 8300 storage and works fine. Its all the other WWPN's that are having the problem
From: Mark Post <mp...@novell.com> To: IBMVM@LISTSERV.UARK.EDU Date: 04/12/2011 11:32 PM Subject: Re: Cannot see SVC disk zLinux Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> >>> On 4/12/2011 at 04:14 PM, Terry Wilson<terry.wil...@potashcorp.com> wrote: > Hello, > I am having a problem connecting ZFCP through my SVC. When I issue the > lsluns command it comes back with Unable to send the REPORT_LUNS command > to LUN. Any ideas? > Attached are commands > zlinux1:~ # lszfcp -P ( > 0.0.5400/0x500507680140a23a rport-0:0-0 > 0.0.5400/0x50050763070342f3 rport-0:0-1 > 8300 disk > 0.0.5400/0x500507680110a23a rport-0:0-2 > 0.0.5400/0x500507680140a31b rport-0:0-3 > 0.0.5400/0x500507680110a31b rport-0:0-4 > 0.0.5401/0x500507680110a23a rport-1:0-0 > 0.0.5401/0x500507680140a31b rport-1:0-1 > 0.0.5401/0x500507680110a31b rport-1:0-2 > 0.0.5401/0x500507680140a23a rport-1:0-3 > 0.0.5401/0x50050763070342f3 rport-1:0-4 > 8300 disk > > zlinux1:~ # lszfcp -D > 0.0.5400/0x50050763070342f3/0x4010400b00000000 0:0:1:1074479120 The LUN number (1074479120) looks extremely suspicious. In hexadecimal, it's only 4 characters, so the maximum value would be 64K. Are you sure you were told the correct number by the SAN administrator? I ran into a customer recently where the SAN admin didn't understand that the value he was seeing on the SVC screens was _not_ the LUN, but a serial number. Try configuring LUN 0 and see if things get better. As a starter, try this: zfcp_san_disc -b 0.0.54c00 -p 0x50050763070342f3 -L Mark Post
