[HPADM] 2nd fibre channel path
From: Vidal, Ignacio - (Arg) (ignacio.vidal_at_telmex.com)
Date: 08/27/05
- Previous message: Jeff Cleverley: "[HPADM] SUMMARY -- nfs hang due to stad or lockd?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 26 Aug 2005 19:38:33 -0300 To: <hpux-admin@DutchWorks.nl>
Good evening:
I've just installed a 2nd path to an L2000 database server connected to
a SAN and I've got a question because I found some "problems" when
configuring HPUX.
The server had the 1st path installed some months ago, and is connected
to an EVA5000 through a Brocade2800 FC switch.
All components are working OK.
After I added the 2nd path, and run ioscan on the server (previous
configuration of SAN zones, and added the host FCA to EVA
configuration), I only can see the following:
# ioscan
H/W Path Class
Description
========================================================================
=
root
0 ioa System Bus
Adapter (582)
0/0 ba Local PCI
Bus Adapter (782)
0/0/0/0 lan HP PCI
10/100Base-TX Core
0/0/1/0 ext_bus SCSI C896
Fast Wide LVD
(.... I'll reach the disks...)
Here comes the 2nd added path disks:
0/4 ba Local PCI
Bus Adapter (782)
0/4/0/0 fc HP Tachyon
TL/TS Fibre Channel Mass Storage Adapter
0/4/0/0.1 fcp FCP Domain
0/4/0/0.1.16.0.0 ext_bus FCP Array
Interface
0/4/0/0.1.16.0.0.0 target
0/4/0/0.1.16.0.0.0.0 ctl COMPAQ
HSV110 (C)COMPAQ
0/4/0/0.1.16.0.0.1 target
0/4/0/0.1.16.0.0.1.0 ctl COMPAQ
HSV110 (C)COMPAQ
... there are more
0/5 ba Local PCI
Bus Adapter (782)
0/6 ba Local PCI
Bus Adapter (782)
Here comes the 1st added path disks:
0/7 ba Local PCI
Bus Adapter (782)
0/7/0/0 fc HP Tachyon
TL/TS Fibre Channel Mass Storage Adapter
0/7/0/0.1 fcp FCP Domain
0/7/0/0.1.18.0.0 ext_bus FCP Array
Interface
0/7/0/0.1.18.0.0.0 target
0/7/0/0.1.18.0.0.0.0 ctl COMPAQ
HSV110 (C)COMPAQ
0/7/0/0.1.18.0.0.0.1 hsx COMPAQ
HSV110 (C)COMPAQ
0/7/0/0.1.18.0.0.0.2 hsx COMPAQ
HSV110 (C)COMPAQ
0/7/0/0.1.18.0.0.0.3 hsx COMPAQ
HSV110 (C)COMPAQ
... there are more
8 memory Memory
160 processor Processor
162 processor Processor
164 processor Processor
166 processor Processor
And here are secure path devices:
255 ba
255/0 ext_bus HSV110
(C)COMPAQ 0x50001FE150019090
255/0.0 target
255/0.0.0 disk HSV110
(C)COMPAQ
255/0.0.1 disk HSV110
(C)COMPAQ
255/0.0.2 disk HSV110
(C)COMPAQ
... there are more
#
My question is: Why cannot I see "hsx-like" devices under 0/4/* hardware
path? (as I find under HW path 0/7/*)
I think that's why in spmgr's output I only see devices only on td1
(/dev/td1 adapter), like this one:
TGT/LUN Device WWLUN_ID H/W_Path
#_Paths
0/ 0 c14t0d0 6005-08B4-0001-1C49-0000-D000-03CB-0000
2
255/0.0.0
Controller Path_Instance HBA Preferred?
Path_Status
P5849D5AAP302J no
c10t0d1 td1 no
Active
Controller Path_Instance HBA Preferred?
Path_Status
P5849D5AAP3035 no
c12t0d1 td1 no
Standby
I would like to see a "td0" HBA in spmgr's output.
Well, I'll appreciate any suggestion very much.
Thanks in advance!
Ignacio
--
---> 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)
- Previous message: Jeff Cleverley: "[HPADM] SUMMARY -- nfs hang due to stad or lockd?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
