Hi Neale,
that's correct.
I remember having seen at least two different symptoms. The first is what
you've observed, the second is "unknown device type 31". Both indicate that
LUN masking on the ESS is not properly set up (or Linux configuration
errors, e.g. wrong LUN used).
Best regards / Freundliche Gr��e
Raimund Schr�der
--
Dr. Raimund Schr�der
Linux for zSeries Development
Tel.: +49-(0)7031-16-2365, FAX: -3456
IBM Deutschland Entwicklung GmbH
|---------+----------------------------------->
| | "Ferguson, Neale" |
| | <[EMAIL PROTECTED]|
| | AG-USA.com> |
| | Sent by: Linux on 390 |
| | Port |
| | <[EMAIL PROTECTED]|
| | > |
| | |
| | |
| | 27.08.2003 18:55 |
| | Please respond to Linux |
| | on 390 Port |
| | |
|---------+----------------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: SCSI problem
|
|
|
>-------------------------------------------------------------------------------------------------------------------------------|
Thanks.
When I plug in "random" LUN values I get quite different messages than when
I use the value provided by the SAN admin. Does this indicate that the LUN
exists but, for whatever reason, is not allowed to communicate with me?
Neale
-----Original Message-----
Hi Neale,
you've received device check conditions (ASC/ASCQ says "Logical unit not
supported", see http://www.arkeia.com/resources/scsi_rsc.html).
Please verify your SAN configuration. Double-check whether your hosts on
the Shark box are properly configured (allow access to the correct WWPNs of
the FCP CHPIDs) and whether you've chosen the right LUNs in your zfcp
configuration.
