[HPADM] Re: I cant see a bunch of disks over fiber from a XP

From: daniel parkes (liquidsmail@gmail.com)
Date: Thu May 04 2006 - 10:34:25 EDT


Hy,

No its not a new system, it has been runing for a long time, and drivers are
ok.

I have also noticed that hw path to that disk doesn't have fcparray

it only has:

ext_bus 167 0/0/14/0/0.117.143.255.1 fcpdev CLAIMED INTERFACE FCP
Device Interface

O 5/4/06, Lee J Kendrick <lkendri2@csc.com> wrote:
>
>
>
>
>
> Dan,
>
> I've had this problem a couple of times with an XP. I run the xpinfo
> command with the i switch "xpinfo -i" then an ioscan, occasional I have to
> do this twice. As far as limitations are concerned not 100% sure, if the
> XP has presented them without hitting an XP port limit then the OS should
> see them.
>
> Regards,
> Lee.
>
>
> ----------------------------------------------------------------------------------------
>
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery. NOTE: Regardless of content, this e-mail shall not operate to
> bind CSC to any order or other contract unless pursuant to explicit
> written
> agreement or government initiative expressly permitting the use of e-mail
> for such purpose.
>
> ----------------------------------------------------------------------------------------
>
>
>
>
>
> "daniel parkes"
> <liquidsmail To:
> hpux-admin@DutchWorks.nl
> @gmail.com> cc:
> Sent by: Subject: [HPADM] I cant see
> a bunch of disks over fiber from a XP
> hpux-admin-owner
>
>
> 04/05/2006 12:43
>
>
>
>
>
> Hy,
>
>
> I have a strange problem, i have been asigned 10 disks, from a XP san, but
> i can only see 7 of them, the fc is ok and on-line i can see all the disks
> from other XP sans that i also have connected to the machine, but there
> are
> some difereces with the other disks i have assigned, have a look:
>
> these are the disks i should have 10 and i only have 7:
>
> /dev/rdsk/c168t3d3 d4 03 03 CL1M 01:a3 OPEN-9
> 000505
> /dev/rdsk/c167t3d3 b9 03 03 CL2M 01:a3 OPEN-9
> 000505
> /dev/rdsk/c168t3d1 d4 03 01 CL1M 02:33 OPEN-E
> 000505
> /dev/rdsk/c167t3d1 b9 03 01 CL2M 02:33 OPEN-E
> 000505
> /dev/rdsk/c168t3d2 d4 03 02 CL1M 02:34 OPEN-E
> 000505
> /dev/rdsk/c167t3d2 b9 03 02 CL2M 02:34 OPEN-E
> 000505
> /dev/rdsk/c168t3d4 d4 03 04 CL1M 02:35 OPEN-E*5
> 000505
> /dev/rdsk/c167t3d4 b9 03 04 CL2M 02:35 OPEN-E*5
> 000505
> /dev/rdsk/c168t3d5 d4 03 05 CL1M 02:3a OPEN-E*5
> 000505
> /dev/rdsk/c167t3d5 b9 03 05 CL2M 02:3a OPEN-E*5
> 000505
> /dev/rdsk/c168t3d6 d4 03 06 CL1M 02:3f OPEN-E*4
> 000505
> /dev/rdsk/c167t3d6 b9 03 06 CL2M 02:3f OPEN-E*4
> 000505
> /dev/rdsk/c168t3d7 d4 03 07 CL1M 02:43 OPEN-E*4
> 000505
> /dev/rdsk/c167t3d7 b9 03 07 CL2M 02:43 OPEN-E*4
> 000505
>
>
> as you can see i dont have a lun0 assigned wich usually is the disk
> subsystem, so it gets to lun 7 and it doesnt jump to a new target
>
> and with other disks i have it goes:
>
> /dev/rdsk/c38t0d1 ef 00 01 CL1A 00:00 OPEN-E
> 000510555
> /dev/rdsk/c39t0d1 cd 00 01 CL2A 00:00 OPEN-E
> 000510555
> /dev/rdsk/c38t0d2 ef 00 02 CL1A 00:01 OPEN-E
> 000510555
> /dev/rdsk/c39t0d2 cd 00 02 CL2A 00:01 OPEN-E
> 000510555
> /dev/rdsk/c38t0d4 ef 00 04 CL1A 00:02 OPEN-E*5
> 000510555
> /dev/rdsk/c39t0d4 cd 00 04 CL2A 00:02 OPEN-E*5
> 000510555
> /dev/rdsk/c38t0d3 ef 00 03 CL1A 00:03 OPEN-9
> 000510555
> /dev/rdsk/c39t0d3 cd 00 03 CL2A 00:03 OPEN-9
> 000510555
> /dev/rdsk/c38t0d5 ef 00 05 CL1A 00:09 OPEN-E*5
> 000510555
> /dev/rdsk/c39t0d5 cd 00 05 CL2A 00:09 OPEN-E*5
> 000510555
> /dev/rdsk/c38t0d6 ef 00 06 CL1A 00:10 OPEN-E*4
> 000510555
> /dev/rdsk/c39t0d6 cd 00 06 CL2A 00:10 OPEN-E*4
> 000510555
> /dev/rdsk/c38t0d7 ef 00 07 CL1A 00:16 OPEN-E*4
> 000510555
> /dev/rdsk/c39t0d7 cd 00 07 CL2A 00:16 OPEN-E*4
> 000510555
> /dev/rdsk/c38t1d0 ef 01 08 CL1A 00:1e OPEN-E*3
> 000510555
> /dev/rdsk/c39t1d0 cd 01 08 CL2A 00:1e OPEN-E*3
> 000510555
> /dev/rdsk/c38t1d1 ef 01 09 CL1A 00:23 OPEN-E*4
> 000510555
> /dev/rdsk/c39t1d1 cd 01 09 CL2A 00:23 OPEN-E*4
> 000510555
> /dev/rdsk/c38t1d2 ef 01 0a CL1A 00:29 OPEN-E*8
> 000510555
> /dev/rdsk/c39t1d2 cd 01 0a CL2A 00:29 OPEN-E*8
> 000510555
> /dev/rdsk/c38t2d0 ef 02 10 CL1A 00:57 OPEN-E*8
> 000510555
> /dev/rdsk/c39t2d0 cd 02 10 CL2A 00:57 OPEN-E*8
> 000510555
>
> so i have lun 0 wich is disk subsystem and it jumps targets with out a
> problem, from t0d7 to t1d0
>
> and its subsystem:
>
> disk 195 0/0/6/0/0.117.30.19.0.0.0 sdisk CLAIMED DEVICE
> HP DISK-SUBSYSTEM
> /dev/dsk/c38t0d0 /dev/rdsk/c38t0d0
>
>
>
> any idea if there is any kind of limitation with luns or what is the
> problem?
>
>
>
>

--
             ---> Please post QUESTIONS and SUMMARIES only!! <---
        To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
       Name: hpux-admin@dutchworks.nl     Owner: owner-hpux-admin@dutchworks.nl
 
 Archives:  ftp.dutchworks.nl:/pub/digests/hpux-admin       (FTP, browse only)
            http://www.dutchworks.nl/htbin/hpsysadmin   (Web, browse & search)


This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:52 EDT