Connecting HP-UX to FC Comstar Target / Nexenta
Post date: Dec 24, 2013 1:09:13 AM
So I was playing around with my IA64 HP-UX servers trying to get it to connect to my Nexenta CE based fibre channel SAN and was having troubles.
# fcmsutil /dev/fcd0
Vendor ID is = 0x1077
Device ID is = 0x2312
PCI Sub-system Vendor ID is = 0x103C
PCI Sub-system ID is = 0x12BA
PCI Mode = PCI-X 133 MHz
ISP Code version = 3.3.175
ISP Chip version = 3
Topology = PRIVATE_LOOP
Link Speed = 2Gb
Local N_Port_id is = 0x000001
Previous N_Port_id is = 0x000001
Local Loop_id is = 125
N_Port Node World Wide Name = 0x50060b0000331891
N_Port Port World Wide Name = 0x50060b0000331890
Switch Port World Wide Name = N/A
Switch Node World Wide Name = N/A
N_Port Symbolic Port Name = hpux1_fcd0
N_Port Symbolic Node Name = hpux1_HP-UX_B.11.31
Driver state = ONLINE
Hardware Path is = 0/4/1/0
Maximum Frame Size = 2048
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
TYPE = PFC
NPIV Supported = NO
Driver Version = @(#) fcd B.11.31.1311 Nov 5 2013
# fcmsutil /dev/fcd0 get remote all
Target N_Port_id is = 0x0000ef
Target Loop_id is = 0
Target Port World Wide Name = 0x2103001b326e962a
Target port is in invalid state
and on Nexenta..
root@nexenta:/volumes# fcadm remote-port -p 2103001B326E962A -l
Remote Port WWN: 50060b0000331890
Active FC4 Types:
SCSI Target: unknown
Port Symbolic Name:
Node WWN: 50060b0000331891
Link Error Statistics:
Link Failure Count: 0
Loss of Sync Count: 0
Loss of Signal Count: 0
Primitive Seq Protocol Error Count: 0
Invalid Tx Word Count: 0
Invalid CRC Count: 0
I tried many things wasting many hours - tried in both FCAL and Fabric connections (hard and soft zoning) but this is as far as I have gotten. HP-UX will not detect the LUN and just shows target as "Target port is in invalid state". Since this is a hobby I always seem to google last. I mean, this is just supposed to work and if it doesn't, I didn't think I'd find much in the way of information on it anyway. I did end up finding this gem of a mailing list post though.
[prev in list] [next in list] [prev in thread] [next in thread]
List: opensolaris-storage-discuss Subject: Re: [storage-discuss] COMSTAR and AIX, HP-UX/PA support From: Albert Chin <opensolaris-storage-discuss () mlists ! thewrittenword ! com> Date: 2009-09-22 6:17:02 Message-ID: 20090922100911.GB13517 () songoku ! il ! thewrittenword ! com [Download message RAW]
On Fri, Sep 18, 2009 at 04:01:02PM -0400, Peter Cudhea wrote:
> Were you able to make progress with this? Based on a quick scan of the
> code, you may need to look at the following links:
> 1) SCMD_WRITE_VERIFY. I am not an expert in this area of the code,
> but it looks like you could add support for SCMD_WRITE_VERIFY to the
> following routine. You may also need to modify the code that calls
> this routine.
Haven't started yet. Will probably start in two weeks.
> Would you be willing to open an RFE in category solaris/storage_sw/sbd
> that details the requirement for the SCMD_WRITE_VERIFY command and
> perhaps how to test it? Or would you like to have a sponsor so that
> you can put back the change yourself? We cannot test all the
> initiators out there, and simple changes like this that allow us to be
> compatible with an important class of initiators are worth doing.
I don't have a problem with this but our current solution is simply a
hack, treating SCMD_WRITE_G1 like SCMD_WRITE_VERIFY (which basically
makes SCMD_WRITE_VERIFY just a WRITE with no VERIFY). I'll see if we
have time to produce a "correct" version that fully supports VERIFY.
And, if we do, we would like to push the code back upstream. When we
have something, I'll ping.
> 2) Including the port number in the SendTargets response. Looks like it is
> already handled:
albert chin (email@example.com)
storage-discuss mailing list
Annnnnnd then nothing of interesting value...
So I'm considering just shelving the whole HP-UX cluster until I either find a use for it or get a proper SP. I mean I am trying real hard to find a use for them but for now, in my basement, Itanium is dead.
---EDIT--- 2013-12-23 10:54PM
I configured the iSCSI initiator and added the iqn into the initiator group in Nexenta and now it seems the LUN is showing up in ioscan... I don't understand how only adding the IQN into the initiator group on the Nexenta fixed it - the WNN was in there and it didn't work... oh well!
H/W Path Class Description
0/4/1 slot PCI Slot
0/4/1/0 fc HP A6826-60001 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1)
0/4/1/0.8 fcp FCP Protocol Adapter
0/4/1/0.8.0.255.0 ext_bus FCP Device Interface
0/4/1/0.8.0.255.0.0.0 disk NEXENTA COMSTAR
255/0 iscsi iSCSI Virtual Node
255/0/0.0 ext_bus iSCSI-SCSI Protocol Interface
255/0/0.0.0.0 disk NEXENTA COMSTAR
Now to play - Long live the Itanium!