From: Evans, Steve (steve.evans@Fiserv.com)
Date: Wed Nov 08 2006 - 12:50:03 EST
And the answer is... tdlist (and fcdlist). James Perry pointed me in
the right direction, and I have his response below. Richard Aranas had
a close guess, which helped me dig deeper. Thanks to everyone else who
responded. By looking at the tdlist script, I was able to come up with
the following for an fcpdev device (which is what I was 1st looking for
- fcparray and fcpmux are handled a bit differently as is arbitrated
loop). Since tdlist has no inputs and goes through all of your hardware
(read ioscan x 15), I'll probably add it to my script. If anyone is
interested in it, let me know, and I'll send it to you after these mods.
The following maps from hardware path to N_Port_id, so going the other
way and getting other info should be quite easy:
Hardware path:
0/0/12/0/0.1.28.255.0.0.0
^ ^ ^ ^
| | | |-- Target
| | |---- Interface
| |----------- Area
|------------- Domain ID
N_Port_id:
0x011c00
^ ^^^^
| ||||- Hex target
| |||-- Hex interface
| ||--- Hex port number }__ Together for area
| |---- Hex blade / card number }
|------ Hex domain ID
Domain ID converts directly between N_Port and HW Path.
The blade and port number are separate (ie this is blade 1, port 15),
but taken together, they are the area in the HW Path.
01=1 Domain
1c=28 Area
0=0 Interface
0=0 Target
tdlist output:
/dev/td3 0/0/12/0/0.1.28.255.0.0.0 fcpdev 0x011c00
CLAIMED DEVICE STK 9840 /dev/rmt/54m /dev/rmt/54mnb
/dev/rmt/c74t0d0BESTn /dev/rmt/c74t0d0D3480b
>From Mr. Perry:
Steve,
Use the /opt/fcms/bin/fcdlist and /opt/fcms/bin/tdlist (one for FCD
cards other for the older TD FC cards). This will show 2 lines of the
format:
</dev for FC card> <Device hw path> <card type> <N_Port_ID of device>
<Status> <vendor / device info> <dev path 1> ... <device path
N>
So for and error like:
vmunix: 0/2/1/0/4/0: Device at device id 0x610613 has disappeared from
Name Server GPN_FT
vmunix: (FCP type) response, or its 'Port World-Wide Name' has changed.
vmunix: device id = loop id, for private loop devices
vmunix: device id = nport ID, for fabric/public-loop devices
vmunix: System won't be able to see LUNs behind this port.
I can find the devices from the output of the fcdlist command:
/dev/fcd0 0/2/1/0/4/0.97.6.255.1.3.1 fcd_vbus 0x610613
CLAIMED DEVICE HP Ultrium 1-SCSI /dev/rmt/20m /dev/rmt/20mnb
/dev/rmt/c26t3d1BESTn
/dev/fcd0 0/2/1/0/4/0.97.6.255.1.3.2 fcd_vbus 0x610613
CLAIMED DEVICE HP Ultrium 1-SCSI /dev/rmt/21m /dev/rmt/21mnb
/dev/rmt/c26t3d2BESTn
In these 2 drives are connected through the bridge that has the nport_id
of 0x610613. But to answer your question, there is not a single
N_Port_id -> specific device mapping as you wanted. The N_Port_id is
the port of the initiator linked to the FC interface that connects to
the SAN fabric. For tape drives on a FC bridge, the N_Port_id is that
of the bridge, not each drive. For mass storage, it is the FC port of
the storage array. This list though does give to device mapping for the
N-Port ID. You will still need to traverse the devices in the list to
get status, but this should give you a good start.
Steve Evans
UNIX Systems Administrator
Fiserv - Norcross Center, Midori Building
5335 Triangle Parkway
Norcross, GA 30092
w - 678.245.7220
c - 404.242.0098
--
---> 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:54 EDT