We have tested HP-UX software iSCSI initiator with EMC cx3-20c target. Although HP-UX iSCSI initiator is not supported it works except for the performance problem. We were not able to achieve more then 20MB/s on a iscsi vxfs file system. This is very poor.

Java Jdk 7 For Linux. I could not find any docs regarding iscsi initiator optimization and the only configurable iscsi parameters are authentication related. The iscsi stats are attached, however i am not able to interpret them. The only suspicious parameter is I/O underflows. I would start checking TCP and link-level stats.

The information in this document is based on these software and hardware versions: HP-UX 9000/800. 4 vatican# show iscsi initiator iSCSI Node name is. I believe the current HP-UX iSCSI software initiator supports only one TCP connection per iSCSI session. ISCSI on HP-UX 11.31.

Cprm Decrypter Sony Ericsson. Netstat -s -p tcp snapshots before and after your transfer, then run through Look for things like retransmissions, and retransmission timeouts and out of order segments. Do the same thing with lanadmin -g mibstats before and after and look for errors, discards and _late_ collisions. Also, what sort of system is this, and what is the per-CPU utilization of each CPU while the transfer is taking place? I'm guessing this is a gigabit/s ethernet, but any idea how many I/Os can be outstanding at one time, and of what size? What is the TCP window size being used - you want to get a packet trace starting from when the target is first mounted so you can see the window scaling option if it is present. Play Nostale Files Nostale In Game Client there.

Now it is a year later, and our company is considering installing an EMC clariion that would be used by two servers: an rx3600 and an rx4640, both running HP-UX 11.23 (that's 11i V2) over iSCSI. Can anyone comment on this configuration? Found this HP web site, 'The following third-party storage devices have completed independent interoperability validation under the guidance of HP and have been qualified as interoperable in HP-UX environments.' But it appears that only HP-UX 11iV3 is listed. I haven't found anything that discusses integrity servers running HP-UX iSCSI with Auto Port Aggregation. Would aggregating two ethernet ports work well with iSCSI? Has anyone tried this arrangement, am I doomed to have the same performance issues that Dejan had last year?

Will there still be performance issues (or any other issues) if we attempt to use iSCSI even without aggregating ports for data? We'll keep network traffic separate from data traffic. A few tips for testing: check if immediate_report is 1 (see scsictl man page) and raise your queue_depth a lot above the default 8.

Next: I might sound old and grumpy now, but I think someone should really go ahead and say it aloud. I've been working with CX storage on HP-UX since 2001 now, and used iSCSI for over 5 years. CX series arrays and HP-UX don't go well Hitachi, for example seems to stomp on CX both for availabilty and performance, especially since avoiding all the stupid trespassing issues (ever tuned fcp_max_requests?). ISCSI appears fast on most platforms because of 'aggressive caching', sometimes you got up to 2 minutes of outstanding writes, and I wonder if HP-UX is a bit conservative about those, this might explain the read behaviour mentioned. Personally I'd suggest you just stay away from iSCSI for anything but lab or home networks, even 1gbit FC beats gigabit iSCSI hands down (and thats stuff so old noone still uses it!). You get better availability and the price difference isn't half as high as iSCSI vendors want to make you believe.