UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
1228 views

NW6.5Sp8-iscsi->SLES11SP = The network disk vanishes

NW65sp8(iniciator)---iscssi-->sles11sp1(target)
Create "testvol" in the iscsi.

From the User WS (XP_sp3+nw4.91sp5 client) log in to the Netware and map:
g: = \\grad\workvolume
u:=\\grad\testvol

This is OK.
Run copy large files (*.iso). from g: -> u:
after some times (2...7 min) drive "U:" vanishes from the WS...And need recconect and run copy again...

At this time on the server I do not see any messages on an error.

Please, help me.

This is info aboout my NLM:
TCPIP.NLM 6.82.02 30 Sep 2009
TCP.NLM 6.82.06 23 Dec 2009
WS2_32.NLM 6.24.01 14 Feb 2008
WSPIP.NLM* 6.24 4 Dec 2007
IOCTL.NLM 1.06.05 30 Sep 2008
ISCSIHAM.HAM* 1.06.05 30 Sep 2008
ISCSILIB.NLM 1.06.05 30 Sep 2008
ISCSINIT.NLM 1.06.05 5 Feb 2009
ISCSINRM.NLM* 1.06.05 14 Oct 2008
ISCSIXML.NLM* 1.06.05 30 Sep 2008
NSS.NLM 3.27.03 7 Jun 2010

Serg
Labels (1)
0 Likes
7 Replies
Absent Member.
Absent Member.

after some times (2...7 min) drive "U:" vanishes from the WS...And need recconect and run copy again...

... reconnect from the WS to U: ? That is, iSCSI itself is still apparently OK, connected and working? Then you have a workstation/network issue, not a NW/iSCSI one. Maybe a lan trace of the failure will show who is disconnecting and why.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Absent Member.
Absent Member.

ataubman;2172889 wrote:
... reconnect from the WS to U: ? That is, iSCSI itself is still apparently OK, connected and working? Then you have a workstation/network issue, not a NW/iSCSI one. Maybe a lan trace of the failure will show who is disconnecting and why.


"That is, iSCSI itself is still apparently OK, connected and working?" - at this time on the Server i see:
1) monitor | General Information | Current disk requests up to 1000 +/-2...
2) From WS access to the other mapped disk - to slowly.. (if work without iscsi mapped disk - all OK)
3) In the NRM - iscsi - Freen... and tcpdump eth0( sles11sp1) show too many iscsis packets between sles<--->nw
This my enviroment:
sles11sp1(raid-10 adaptec with 4 sata 1T hd)_[eth0]<----------->[e1000_02]NW[e1000_01]<---->SWitch<----WS

If i use iscsi NLMs from NOVELL: Downloads - TCPIP for NW65SP8 29012010 - have this problem again....
What is TCP SET options recomended for work with iscsi on NW65sp8 as iniciator ?

Serg
0 Likes
Absent Member.
Absent Member.

skoltogyan;2172939 wrote:
"That is, iSCSI itself is still apparently OK, connected and working?" - at this time on the Server i see:
1) monitor | General Information | Current disk requests up to 1000 +/-2...
2) From WS access to the other mapped disk - to slowly.. (if work without iscsi mapped disk - all OK)
3) In the NRM - iscsi - Freen... and tcpdump eth0( sles11sp1) show too many iscsis packets between sles<--->nw
This my enviroment:
sles11sp1(raid-10 adaptec with 4 sata 1T hd)_[eth0]<----------->[e1000_02]NW[e1000_01]<---->SWitch<----WS

If i use iscsi NLMs from NOVELL: Downloads - TCPIP for NW65SP8 29012010 - have this problem again....
What is TCP SET options recomended for work with iscsi on NW65sp8 as iniciator ?

Serg


+ add.
about "2) From WS access to the other mapped disk - to slowly.. (if work without iscsi mapped disk - all OK)
"
When Freez access(from the WS) to the mapped iscsi disk - freez access and to the other mapped netware disks.
But NRM -work.
At this time tcpdump on the sles11sp1(iscsi target) is:
https://gw.ami.ua/i.zip
only after ioff.ncf server back to the normal state
0 Likes
Absent Member.
Absent Member.

skoltogyan;2172956 wrote:
+ add.
about "2) From WS access to the other mapped disk - to slowly.. (if work without iscsi mapped disk - all OK)
"
When Freez access(from the WS) to the mapped iscsi disk - freez access and to the other mapped netware disks.
But NRM -work.
At this time tcpdump on the sles11sp1(iscsi target) is:
https://gw.ami.ua/i.zip
only after ioff.ncf server back to the normal state


+add+1:
When "Freez" - at this time:
"Total cache buffers" chnaged from 476000 to 340000... and at this time copy from WS to Server STOP (freeze).
From this time - any access to the Server volumes(nss) - impossible..

Only after ioff.ncf "Total cache buffers" back to the 476000.... and only after this users can access to the volumes again...

"Original cache buffers" = 916313
Use only 1 processor.


Serg
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Serg,

On 03.02.2012 10:06, skoltogyan wrote:
>
> skoltogyan;2172956 Wrote:
>> + add.
>> about "2) From WS access to the other mapped disk - to slowly.. (if
>> work without iscsi mapped disk - all OK)
>> "
>> When Freez access(from the WS) to the mapped iscsi disk - freez access
>> and to the other mapped netware disks.
>> But NRM -work.
>> At this time tcpdump on the sles11sp1(iscsi target) is:
>> https://gw.ami.ua/i.zip
>> only after ioff.ncf server back to the normal state

>
> +add+1:
> When "Freez" - at this time:
> "Total cache buffers" chnaged from 476000 to 340000... and at this time
> copy from WS to Server STOP (freeze).
> From this time - any access to the Server volumes(nss) - impossible..
>
> Only after ioff.ncf "Total cache buffers" back to the 476000.... and
> only after this users can access to the volumes again...
>
> "Original cache buffers" = 916313
> Use only 1 processor.



What you see here is a classical problem. Your storage is too slow,
which unfortunately is "normal" for Netware iSCSI. Your workstation is
using a GB connection, right? The "freez" you see is not really a
freeze, it *will* recover on it's own, but it seems frozen when the
Netware file cache is full. Your workstation writes the data faster to
the server than the disk (iscsi) can write. I'm afraid there's nothing
you can do, sorry. 😞

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Absent Member.
Absent Member.

mrosen;2172982 wrote:
Serg,

On 03.02.2012 10:06, skoltogyan wrote:
>
> skoltogyan;2172956 Wrote:
>> + add.
>> about "2) From WS access to the other mapped disk - to slowly.. (if
>> work without iscsi mapped disk - all OK)
>> "
>> When Freez access(from the WS) to the mapped iscsi disk - freez access
>> and to the other mapped netware disks.
>> But NRM -work.
>> At this time tcpdump on the sles11sp1(iscsi target) is:
>> https://gw.ami.ua/i.zip
>> only after ioff.ncf server back to the normal state

>
> +add+1:
> When "Freez" - at this time:
> "Total cache buffers" chnaged from 476000 to 340000... and at this time
> copy from WS to Server STOP (freeze).
> From this time - any access to the Server volumes(nss) - impossible..
>
> Only after ioff.ncf "Total cache buffers" back to the 476000.... and
> only after this users can access to the volumes again...
>
> "Original cache buffers" = 916313
> Use only 1 processor.



What you see here is a classical problem. Your storage is too slow,
which unfortunately is "normal" for Netware iSCSI. Your workstation is
using a GB connection, right? The "freez" you see is not really a
freeze, it *will* recover on it's own, but it seems frozen when the
Netware file cache is full. Your workstation writes the data faster to
the server than the disk (iscsi) can write. I'm afraid there's nothing
you can do, sorry. 😞

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
Untitled Document


This is configuration:

WS(intelPro100)<--100Mb--->Switch(HP)<---1G--->(E1000)NW65SP8(E1000)<-----1G--->(RTL8111/8168)

Everywhere it is used autoneg.

How to reconfigure NCP and NSS, what the system didn't give the chance to station to send the following packet while the accepted data physically isn't written down on a disk?

Serg
0 Likes
Absent Member.
Absent Member.

skoltogyan;2172609 wrote:
NW65sp8(iniciator)---iscssi-->sles11sp1(target)
Create "testvol" in the iscsi.

From the User WS (XP_sp3+nw4.91sp5 client) log in to the Netware and map:
g: = \\grad\workvolume
u:=\\grad\testvol

This is OK.
Run copy large files (*.iso). from g: -> u:
after some times (2...7 min) drive "U:" vanishes from the WS...And need recconect and run copy again...

At this time on the server I do not see any messages on an error.

Please, help me.

This is info aboout my NLM:
TCPIP.NLM 6.82.02 30 Sep 2009
TCP.NLM 6.82.06 23 Dec 2009
WS2_32.NLM 6.24.01 14 Feb 2008
WSPIP.NLM* 6.24 4 Dec 2007
IOCTL.NLM 1.06.05 30 Sep 2008
ISCSIHAM.HAM* 1.06.05 30 Sep 2008
ISCSILIB.NLM 1.06.05 30 Sep 2008
ISCSINIT.NLM 1.06.05 5 Feb 2009
ISCSINRM.NLM* 1.06.05 14 Oct 2008
ISCSIXML.NLM* 1.06.05 30 Sep 2008
NSS.NLM 3.27.03 7 Jun 2010

Serg


After Enable Cache for Write in the Adaptec Raid controller - iscsis work as need with iscs* modules from NW65sp7.

Serg
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.