topic Re: New LUN not visible... in Operating System - HP-UX

New LUN not visible...

Simon Galton — Fri, 03 Jan 2003 16:10:43 GMT

This may not be the correct forum, but please bear with me... :)

We just configured our 9th LUN on a va7400. We connected a newly installed K370 running 64-bit 11i and an A6685A FC HBA to our Brocade switch.

Note the ioscan output -- you can see that it sees LUN 0, but not LUN 8 -- any advice?

# ioscan -f
Class I H/W Path Driver S/W State H/W Type Description
=============================================================================
bc 0 root CLAIMED BUS_NEXUS
bc 1 8 ccio CLAIMED BUS_NEXUS I/O Adapter
bc 2 10 ccio CLAIMED BUS_NEXUS I/O Adapter
ext_bus 0 10/0 c720 CLAIMED INTERFACE GSC built-in Fa
st/Wide SCSI Interface
target 0 10/0.0 tgt CLAIMED DEVICE
disk 0 10/0.0.0 sdisk CLAIMED DEVICE OSS OSS-550
0
target 1 10/0.5 tgt CLAIMED DEVICE
disk 1 10/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST31820
3LC
target 2 10/0.6 tgt CLAIMED DEVICE
disk 2 10/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST31820
3LC
target 3 10/0.7 tgt CLAIMED DEVICE
ctl 0 10/0.7.0 sctl CLAIMED DEVICE Initiator
bc 3 10/4 bc CLAIMED BUS_NEXUS Bus Converter
tty 0 10/4/0 mux2 CLAIMED INTERFACE MUX
lan 0 10/4/8 btlan1 CLAIMED INTERFACE HP HP-PB 100 Ba
se TX card
ba 0 10/8 GSCtoPCI CLAIMED BUS_NEXUS GSCtoPCI Bridge
fc 0 10/8/1/0 td CLAIMED INTERFACE HP Tachyon TL/T
S Fibre Channel Mass Storage Adapter
fcp 0 10/8/1/0.2 fcp CLAIMED INTERFACE FCP Domain
ext_bus 1 10/8/1/0.2.17.255.0 fcpdev CLAIMED INTERFACE FCP D
evice Interface
target 4 10/8/1/0.2.17.255.0.0 tgt CLAIMED DEVICE
disk 4 10/8/1/0.2.17.255.0.0.0 sdisk CLAIMED DEVICE HP
A6189A
ext_bus 4 10/8/1/0.2.18.255.0 fcpdev CLAIMED INTERFACE FCP D
evice Interface
target 5 10/8/1/0.2.18.255.0.0 tgt CLAIMED DEVICE
disk 5 10/8/1/0.2.18.255.0.0.0 sdisk CLAIMED DEVICE HP
A6189A
bc 4 10/16 bc CLAIMED BUS_NEXUS Bus Converter
processor 0 32 processor CLAIMED PROCESSOR Processor
processor 1 34 processor CLAIMED PROCESSOR Processor
processor 2 36 processor CLAIMED PROCESSOR Processor
processor 3 38 processor CLAIMED PROCESSOR Processor
processor 4 44 processor CLAIMED PROCESSOR Processor
processor 5 46 processor CLAIMED PROCESSOR Processor
memory 0 49 memory CLAIMED MEMORY Memory

Re: New LUN not visible...

Hai Nguyen_1 — Fri, 03 Jan 2003 16:20:11 GMT

Simon,

Try running:

# ioscan -fnC disk

which will detect the new disk.

Hai

Re: New LUN not visible...

Jose Mosquera — Fri, 03 Jan 2003 16:24:28 GMT

Hi,

Pls use ioscan -fnC disk

Re: New LUN not visible...

Paul Sperry — Fri, 03 Jan 2003 16:27:36 GMT

try
ioscan -fun -C disk

Re: New LUN not visible...

David Bell_1 — Fri, 03 Jan 2003 16:28:31 GMT

Simon,

Take a look at the firmware for the K-Class. The fibre channel card you're using A6685A is not supported in the expansion slot of the Core I/O. It should be installed in an HP-HSC expansion slot. This is noted on the firmware update.

Please take a look at a previous post which discusses this. Mostly, be sure your firmware, SAM/Obam, WSIO SCSI, and LVM patches are up to date.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x1e9f93e260b0d611abdb0090277a778c,00.html

HTH,

Dave

Re: New LUN not visible...

Simon Galton — Fri, 03 Jan 2003 16:29:56 GMT

I'll give ioscan -fnC disk another go...

Well, here's the output, and the new LUN still does not appear:

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 0 10/0.0.0 sdisk CLAIMED DEVICE OSS OSS-5500 /dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 10/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST318203LC /dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 2 10/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST318203LC /dev/dsk/c0t6d0 /dev/rdsk/c0t6d0
disk 4 10/8/1/0.2.17.255.0.0.0 sdisk CLAIMED DEVICE HP
A6189A /dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
disk 5 10/8/1/0.2.18.255.0.0.0 sdisk CLAIMED DEVICE HP
A6189A /dev/dsk/c4t0d0 /dev/rdsk/c4t0d0

Re: New LUN not visible...

David Bell_1 — Fri, 03 Jan 2003 16:33:47 GMT

Simon,

One other note:

If you're using Secure LUN Manager with your VA Array, be sure the appropriate permissions have been entered in the Security Table.

HTH,

Dave

Re: New LUN not visible...

Simon Galton — Fri, 03 Jan 2003 16:33:51 GMT

Dave -- interesting, I did not find this during my forum searches, nor in the printed docs with the card.

My vendor did not mention this incompatibility with the core i/o board.

We're patched and firmwared to the hilt, but this may be a showstopper!

Hmm... We need this up and running for Monday. Sigh...

Re: New LUN not visible...

Sridhar Bhaskarla — Fri, 03 Jan 2003 16:38:24 GMT

Hi,

I don't have much experience with VA7400 but did face problems on Hitachi arrays where the it would not see LUNs of more than 8 due to incorrect host mode settings.

Try change the LUN id to less than 8 (say 2 or anything that is not yet configured) and see if it works.

-Sri

Re: New LUN not visible...

David Bell_1 — Fri, 03 Jan 2003 16:41:28 GMT

Simon,

I have had this working on a K-570 running HP-UX 10.20. The card was located in the same slot. The problems I experienced were many, however, we did get it running. The primary problem was the fact that we couldn't run Command View SDM on the HP-UX 10.20 OS so the array couldn't be properly interrogated. Apparently, the ARMServer is part of the Command View SDM bundle. Without it, you are left to the OS determining what the Array is. Once a file system was installed on the LUNS, most of the ioscan, SAM, and other issues went away.

Check your Secure LUN Manager configuration as well as your Brocade for Zoning. If Command View SDM is not installed on this host, I would install it. You may be able to make this work where it resides, I simply wanted you to be aware of the note in the firmware update file. It references something about if you're using a "graphics" card, however, I was informed it is NOT supported in this slot.

HTH,

Dave

Re: New LUN not visible...

Hai Nguyen_1 — Fri, 03 Jan 2003 16:57:32 GMT

Simon,

Have you yet configured a FIRST, small LUN on va7400? Its sole purpose is for the computer to be able to detect and communicate with the array.

If not, follow the va7400 manual to create it.

Hai

Re: New LUN not visible...

Eugeny Brychkov — Fri, 03 Jan 2003 17:21:34 GMT

Simon,
please attach to your next reply:
- 'armdsp -a ' output;
- 'armsecure -r -f sectbl.txt -p

' file sectbl.txt - current contents of security table. Please note that if you have VA security turned on then newly created LUN will receive '0' permission (no access) until you'll allow access it fron VA security table;
- 'armhost -r -f hosttbl.txt ' file hosttbl.txt - current contents of host behavuor table
Eugeny

Re: New LUN not visible...

Simon Galton — Fri, 03 Jan 2003 17:47:50 GMT

Here's the requested outputs (in one file).

Re: New LUN not visible...

Eugeny Brychkov — Fri, 03 Jan 2003 18:10:14 GMT

Simon,
here what do I see from outputs:
- fimrware should be update to controller:HP18, battery:4.3 (call HP);
- if you have only hpux hosts you can set default host port behavior to hpux 'armmgr -B' and do not use host behavior table;
- from security table I se you use different WWNs for one HBA (node WWN and port WWN). For easiness please use same WWNs in both tables (either node or port);
- LUN 8 will be allowed write access only through HBA having node/port WWN = 50060b00001de1af. All other hosts and HBAs will be unable to see this LUN;
- HBA with WWN = 50060b00001de1af is installed in Windows2000 server: it's not hpux HBA (see host behavior table), and as soon as default VA behavior is w2k this host should be w2k.
So you should check to have correct WWNs:
a) host behavior table/default behavior for controllers;
b) security table.
Please get back to me with your findings and thoughts
Eugeny

Re: New LUN not visible...

Simon Galton — Fri, 03 Jan 2003 18:34:17 GMT

Firmware -- will probably do the update in the summer...

Hosts -- management station is Win2K (sigh)

50060b00001de1af -- is the Tachlite card.

If security is removed, the host can see LUNs 0-7, but not my new LUN 8.

HP just mentions that it may be the HSC card slot.

Re: New LUN not visible...

Eugeny Brychkov — Fri, 03 Jan 2003 19:17:37 GMT

I checked ioscan output again and see that you will NOT be able to see LUN 8 because VA uses Target addressing mode instead Volume set addressing mode.
disk 4 10/8/1/0.2.17.255.0.0.0 sdisk CLAIMED DEVICE HP A6189A
In this mode device can have only 8 LUNs (0..7). In Volume set aggressing mode path will be (in fabric)
disk 4 10/8/1/0.2.17.0.x.y.z sdisk CLAIMED DEVICE HP A6189A
where VA LUN#=z+8*y+128*x, so LUN 8 will be '0.1.0'. This is your problem.
Could you please attach supportshow from the brocade(s) to your next reply?
Eugeny

Re: New LUN not visible...

Simon Galton — Wed, 15 Jan 2003 19:18:51 GMT

Right. Good stuff in these replies, and we've now got it licked.

The problem was the HSC slot. We used the one on the CORE I/O board. This is unsupported. Installing the HBA in an HSC expansion I/O board completely solved the problem.

I have a new problem, now, but it is unrelated! :( :)

Thanks to all.

Simon