Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
888 views

iscsi and wsock6i abends

Apologies for cross posting, but I am trying to save you pain !

Don't run Winsock 6i.

You will find that unloading named abends your server.
You will find that migrating a cluster resource abends the server you are
migrating from.

Don't ask me how I found out. 😞

Coredump with Novell Tech Support now. I have asked them to pull the patch.

Cheers
Ian
Labels (2)
0 Likes
5 Replies
Anonymous_User Absent Member.
Absent Member.

Re: iscsi and wsock6i abends

ianb@nospam.com schrieb:
> Apologies for cross posting, but I am trying to save you pain !
>
> Don't run Winsock 6i.
>
> You will find that unloading named abends your server.
> You will find that migrating a cluster resource abends the server you are
> migrating from.


Thank you. I was just going to give the latest winsock and iscsi patches
a try. (I'm looking for significant performance gains for iscsi.)

Georg
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iscsi and wsock6i abends

> Thank you. I was just going to give the latest winsock and iscsi patches
> a try. (I'm looking for significant performance gains for iscsi.)
>
> Georg


Georg,

I have been working with the iSCSI on Netware developer on an incident I
opened 9 months ago.

Can you give us an overview of what you have and what performance you are
currently getting - and how you measured it.

Thanks,
Ian
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iscsi and wsock6i abends

ianb@nospam.com schrieb:
>
> I have been working with the iSCSI on Netware developer on an incident I
> opened 9 months ago.
>
> Can you give us an overview of what you have and what performance you are
> currently getting - and how you measured it.


Sanrad V-Switch 2000 connected via FC to Infortrend SATA-Enclosures.
Dedicated GigaBit Network for iSCSI.

Very simple testing method: I care what performance i get at the
workstation level.

OES Netware Initiator 18MB/sec. via Client
OES Linux Initiator (Cisco) 32MB/sec. via Client
OES Linux Initiator (Cisco) 64MB/sec. via Console

OES Netware local SCSI disk 32MB/sec. via Client

via Client: I copy several GB of data from the Server (which has its
disks connected by iSCSI, Volumes are NSS) to the local workstation
disk. The workstation is connected by GigaBit Network. (during
production hours)
The workstation Nic is a normal PCI-card. I don't expect more
performance with such a setup than around 30MB/sec.

via Console: I cp several GB of data to a local ReiserFS (single U320
73GB scsi disk)

Georg

PS: Servers are Standard P4 3Ghz, 2-4GB RAM, Broadcom and Intel Nics (PCI-X)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iscsi and wsock6i abends

Hi,

Well it seems the Wsock6i issue was self inflicted - I was running the
modules before they were packaged with an installer, and I can only assume
I missed copying one as I tried again and could not reproduce the "named
unload" abend. I haven't checked it on clustering yet so stay tuned !


With your performance testing, use big files (like ghost images) so you
avoid file system overhead - you want to max the disk channel to test
iSCSI rather than your NSS tuning. 🙂 This will make it consistent.

I would try the following:

Netware 6.5 SP5
post SP5 server.exe
post SP5 NSS update
post SP5 iSCSI update
Wsock6i

SET nagle on
SET minshall on
SET delayed ack on
SET TCP MAXIMUM INITIAL RECEIVE WINDOW=64 (as per iscsi patch).

The best I see on my test box is 32MB/sec - that is with dpmeterm which
runs on the initiator directly.

I wish I could get 18MB/Min on my production system....

Also - have you looked at Jumbo frames ? The 32MB was with jumbos.

Cheers
Ian



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iscsi and wsock6i abends

ianb@nospam.com schrieb:
> Hi,
>
> Well it seems the Wsock6i issue was self inflicted - I was running the
> modules before they were packaged with an installer, and I can only assume
> I missed copying one as I tried again and could not reproduce the "named
> unload" abend. I haven't checked it on clustering yet so stay tuned !


Ok.

> With your performance testing, use big files (like ghost images) so you
> avoid file system overhead - you want to max the disk channel to test
> iSCSI rather than your NSS tuning. 🙂 This will make it consistent.


Actually i was doing the 'benchmark' with ghost images.

> I would try the following:
>
> Netware 6.5 SP5
> post SP5 server.exe
> post SP5 NSS update
> post SP5 iSCSI update
> Wsock6i
>
> SET nagle on
> SET minshall on
> SET delayed ack on
> SET TCP MAXIMUM INITIAL RECEIVE WINDOW=64 (as per iscsi patch).


I'll give it a try.

> The best I see on my test box is 32MB/sec - that is with dpmeterm which
> runs on the initiator directly.


I can easily sustain a 50MB/sec stream with the linux initiator (OES
SP2) to an SDLT600 drive. No way to achieve the same with the Netware
initiator. We'll see if your recommendations help...

> I wish I could get 18MB/Min on my production system....


but 18MB/Sec.(!) is still not enough/acceptable.

> Also - have you looked at Jumbo frames ? The 32MB was with jumbos.


Yes. But i had not the time to do it. AFAIK enabling Jumbo Frames (all
involved devices should be ok with them) does require some form of restart.

Regards,
Georg
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.