Running Z/VM 6.1 SLES 11 SP1
Here is the var/log/messages from the following command
zlinux1:/dev # lsluns
Scanning for LUNs on adapter 0.0.5400
        at port 0x50050763070342f3:                             >8300
                0x4010400b00000000
        at port 0x500507680110a23a:
                Unable to send the REPORT_LUNS command to LUN.
        at port 0x500507680110a31b:
                Unable to send the REPORT_LUNS command to LUN.
        at port 0x500507680140a23a:
                Unable to send the REPORT_LUNS command to LUN.
        at port 0x500507680140a31b:
                Unable to send the REPORT_LUNS command to LUN.
Scanning for LUNs on adapter 0.0.5401
        at port 0x50050763070342f3:
                0x4010400b00000000                              >8300
        at port 0x500507680110a23a:
                Unable to send the REPORT_LUNS command to LUN.
        at port 0x500507680110a31b:
                Unable to send the REPORT_LUNS command to LUN.
        at port 0x500507680140a23a:
                Unable to send the REPORT_LUNS command to LUN.
        at port 0x500507680140a31b:
                Unable to send the REPORT_LUNS command to LUN.
var/log/messages
Apr 12 15:54:39 zlinux1 kernel: scsi 0:0:2:49409: Direct-Access     IBM  
2145             0000 PQ: 1 ANSI: 4
Apr 12 15:54:39 zlinux1 kernel: scsi 0:0:2:49409: Attached scsi generic 
sg1 type 0
Apr 12 15:54:39 zlinux1 kernel: scsi 0:0:4:49409: Direct-Access     IBM  
2145             0000 PQ: 1 ANSI: 4
Apr 12 15:54:39 zlinux1 kernel: scsi 0:0:4:49409: Attached scsi generic 
sg1 type 0
Apr 12 15:54:39 zlinux1 kernel: scsi 0:0:0:49409: Direct-Access     IBM  
2145             0000 PQ: 1 ANSI: 4
Apr 12 15:54:39 zlinux1 kernel: scsi 0:0:0:49409: Attached scsi generic 
sg1 type 0
Apr 12 15:54:39 zlinux1 kernel: scsi 0:0:3:49409: Direct-Access     IBM  
2145             0000 PQ: 1 ANSI: 4
Apr 12 15:54:39 zlinux1 kernel: scsi 0:0:3:49409: Attached scsi generic 
sg1 type 0
Apr 12 15:54:40 zlinux1 kernel: scsi: unknown device type 30
Apr 12 15:54:40 zlinux1 kernel: scsi 1:0:4:49409: Well-known LUN    IBM  
2107900          .280 PQ: 0 ANSI: 5
Apr 12 15:54:40 zlinux1 kernel: scsi 1:0:4:49409: Attached scsi generic 
sg1 type 30
Apr 12 15:54:40 zlinux1 kernel: scsi 1:0:0:49409: Direct-Access     IBM  
2145             0000 PQ: 1 ANSI: 4
Apr 12 15:54:40 zlinux1 kernel: scsi 1:0:0:49409: Attached scsi generic 
sg1 type 0
Apr 12 15:54:40 zlinux1 kernel: scsi 1:0:2:49409: Direct-Access     IBM  
2145             0000 PQ: 1 ANSI: 4
Apr 12 15:54:40 zlinux1 kernel: scsi 1:0:2:49409: Attached scsi generic 
sg1 type 0
Apr 12 15:54:40 zlinux1 kernel: scsi 1:0:3:49409: Direct-Access     IBM  
2145             0000 PQ: 1 ANSI: 4
Apr 12 15:54:40 zlinux1 kernel: scsi 1:0:3:49409: Attached scsi generic 
sg1 type 0
Apr 12 15:54:41 zlinux1 kernel: scsi 1:0:1:49409: Direct-Access     IBM  
2145             0000 PQ: 1 ANSI: 4
Apr 12 15:54:41 zlinux1 kernel: scsi 1:0:1:49409: Attached scsi generic 
sg1 type 0
 






From:   Raymond Higgs <rayhi...@us.ibm.com>
To:     IBMVM@LISTSERV.UARK.EDU
Date:   04/12/2011 03:11 PM
Subject:        Re: Cannot see SVC disk zLinux
Sent by:        The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>



Terry, 

Anything in /var/log/messages? 

lsluns is just a perl script, so I took a peek...  I have lsluns from 
s390tools-1.11.x-1bb17.20110103.s390x so things maybe different in the 
older versions. 

Since you don't have a lun configured on the 0.0.5401 0x500507680110a31b 
path, lsluns should try to configure lun zero for you.  Then look up the 
new sg device and run 'sg_luns /dev/sgXXX'.  If you have a line like this 
in lsluns: 

 70                 my @output = `sg_luns /dev/$sg_dev 2>/dev/null`; 

I think if you remove the "2>/dev/null", there will be a much better error 
message. 

It seems like my version of lsluns has all of the right error handling, 
but who knows... maybe there is a bug. 

Regards, 

Ray Higgs
System z FCP Development
Bld. 706, B42
2455 South Road
Poughkeepsie, NY 12601
(845) 435-8666,  T/L 295-8666
rayhi...@us.ibm.com 

The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> wrote on 
04/12/2011 04:14:43 PM:

> From: Terry Wilson <terry.wil...@potashcorp.com> 
> To: IBMVM@LISTSERV.UARK.EDU 
> Date: 04/12/2011 04:15 PM 
> Subject: Cannot see SVC disk zLinux 
> Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> 
> 
> -0
> 
> 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
> zlinux1:~ # lsluns -c 0.0.5401 -p 0x50050763070342f3
> Scanning for LUNs on adapter 0.0.5401
>         at port 0x50050763070342f3:
>                 0x4010400b00000000
> zlinux1:~ # lsluns -c 0.0.5401 -p 0x500507680110a31b
> Scanning for LUNs on adapter 0.0.5401
>         at port 0x500507680110a31b:
>                 Unable to send the REPORT_LUNS command to LUN.
> zlinux1:~ # lszfcp -D
> 0.0.5400/0x50050763070342f3/0x4010400b00000000 0:0:1:1074479120
> zlinux1:~ # lsscsi
> [0:0:1:1074479120]disk    IBM      2107900          .280  /dev/sda

Reply via email to