topic Re: iSCSI to SAN Connection in Operating System - HP-UX

iSCSI to SAN Connection

Scott Frye_1 — Thu, 14 Apr 2005 12:27:22 GMT

HP9000 (11i) connecting to EMC Clariion CX600 via a Cicso 6500. Has anyone been able to get iSCSI to work with a similar configuration?

Thanks

Scott

Re: iSCSI to SAN Connection

Florian Heigl (new acc) — Thu, 21 Apr 2005 09:15:06 GMT

I don't have the hardware :(

Do You use Ciscos or HPs iSCSI software?

Re: iSCSI to SAN Connection

Scott Frye_1 — Fri, 15 Jul 2005 06:48:43 GMT

We have installed HP's software

Re: iSCSI to SAN Connection

marie-noelle jeanson_1 — Fri, 15 Jul 2005 07:20:02 GMT

Scott,

The support matrix for targets supported by the iSCSI software is available at http://docs.hp.com/en/6065/iSCSI_SM_2004-11-19.htm .

Regards,

Marie-Noelle

Re: iSCSI to SAN Connection

Scott Frye_1 — Fri, 15 Jul 2005 07:23:02 GMT

Woops, I need to change that and state we are using an Cisco MDS9509 switch.

Thanks for the link though, it validates we are using the correct equipment.

Re: iSCSI to SAN Connection

Alain Lavelanet_1 — Wed, 20 Jul 2005 13:36:38 GMT

Where is it failing I had lots of little issues to get over. First of all forget ioscan check /dev/rdsk for c255tXdX devices to see if your iscsi disk is connected. Then add it into a new volume group manually SAM doesn't really like iscsi disks yet. after you get it in a logical volume you can use sam for file system moutning if you want. and remember to make sure you have a fstab.iscsi entry to mount it at boot up. And make sure you have the newest patch bundles installed. I used the HP iscsi stuff for 11i and cisco for 11.00

Re: iSCSI to SAN Connection

Scott Frye_1 — Thu, 21 Jul 2005 05:48:54 GMT

I don't see anything under /dev/rdsk. We've followed the configuration guide from HP (I'm attaching so you can see). Our problem is when we run an iscsiutil -p -O to display operational targets, we don't see anything. Our MDS9509 is not using CHAP. We have not started the SLP on our server. We just can't seem to make a connection. Also, we saw in our syslog:

"chifm vmunix: 255/0: Invalid iSCSI Name format (iqn.chifmiscsi.test) received from the target."

chifm is the name of our server. We then changed the target name to iqn.chifmiscsitest and rebooted the server. Now we see:

"chifm vmunix: 255/0: Invalid iSCSI Name format (iqn.cmaxdrplanning) received from the target."

which we can't understand why cmaxdrplanning is not showing up.

Any input would be appreciated.

Thanks

Scott

Re: iSCSI to SAN Connection

marie-noelle jeanson_1 — Thu, 21 Jul 2005 10:17:20 GMT

Scott,

As explained in the iSCSI support guide, Chapter 4, iqn.chifmiscsi.test is not a valid iqn name.
An iqn name is expected in the form iqn.1986-03.com.hp:hpfcs214.2000853943, where 1986-03 is a date in format yyyy-mm, com.hp is the reversed domain name of the naming authority, :hpfcs214 is an optional string that must comply with a character set and length boundaries that the
owner of the domain name deems appropriate (and must be preceeded by a colon).

Marie.

Re: iSCSI to SAN Connection

Scott Frye_1 — Thu, 21 Jul 2005 12:56:09 GMT

Just to make sure I understand this properly. We took the default iqn initiator name but on the switch our target is iqn.chifmiscsitest. Are you saying the switch target and the iqn initiator should be the same name or just the same format?

Thanks

scott

Re: iSCSI to SAN Connection

marie-noelle jeanson_1 — Thu, 21 Jul 2005 14:14:21 GMT

Scott,

Just the same format. Each address must be unique, and follow the predefined format. In your case, you would use something like iqn.1992.04.com.emc:1123581321355.

Marie.

Re: iSCSI to SAN Connection

Scott Frye_1 — Fri, 22 Jul 2005 15:23:02 GMT

We made the target name using the iqn format and it still didn't work. We called HP support and are working with them. I'm wondering if it isn't on the switch side...

Re: iSCSI to SAN Connection

Florian Heigl (new acc) — Mon, 25 Jul 2005 02:05:13 GMT

it might easily be some problem in the communication from host to switch.

thanks for the manuals, I'm just reading through it. my stomach says Your initiator just didn't manage the login.

I don't know it the 6500 follows regular IOS syntax, but You could give it a shot...

look if there's a 'debug iscsi '

Re: iSCSI to SAN Connection

Florian Heigl (new acc) — Mon, 25 Jul 2005 02:06:25 GMT

hmm...

"The iSCSI Software Initiator validates iSCSI Names. If a target reports a Target Name in an "iqn",
"eui" or "naa" format, but it does not comply with the iSCSI Name format rules, or if a Target Name
contains a prohibited character, iSCSI Login negotiation will fail and the target will not be seen by
the HP-UX host."

did You go through the troubleshooting steps?

Re: iSCSI to SAN Connection

Scott Frye_1 — Mon, 25 Jul 2005 07:02:14 GMT

We've gone through the trouble shooting steps. HP has walked us through the installation. HP is committed to making this work.

Stay tuned...