direwolfe Absent Member.
Absent Member.
3386 views

iSCSI connection "degraded", MSA P2000, NW 6.5 sp7

We are trying to connect to a new HP MSA P2000 from Netware 6.5 sp 7 version and isci list below.
The MSA sees the incoming host fine, but the host doesn't attach to any volume on the target. The connection is dropped. PING is possible. The connection is a dedicated GB network switch with a dual port NIC form the server to four iscsi ports on the enclosure. connecting directly was no different.

We've tried in remote manager and in the CLI. Remote manager attempts at least give more logging, like these:

iSCSI Initiator
0 [!] [CON0:18] watchdog closing socket (123) degraded connection
1 [!] [CON0:19] watchdog closing socket (48) degraded connection
2 [!] [CON0:20] watchdog closing socket (125) degraded connection
3 [!] [CON0:21] watchdog closing socket (106) degraded connection

I16000016
0 [!] [CON0:22] WSARECV rc=10038
1 [!] [CON0:22] login_command failed rc=0xFFFFFFFF
2 [!] [CON0:22] login_command failed rc=0xFFFFFFFF
3 [!] [CON0:22] login_security_none failed rc=0xFFFFFFFF
4 [!] [CON0:22] WSARECV rc=10038
5 [!] [CON0:22] login_command failed rc=0xFFFFFFFF
6 [!] [CON0:22] login_command failed rc=0xFFFFFFFF
7 [!] [CON0:22] login_security_none failed rc=0xFFFFFFFF
8 [!] [CON0:22] WSARECV rc=10038
9 [!] [CON0:22] login_command failed rc=0xFFFFFFFF
10 [!] [CON0:22] login_command failed rc=0xFFFFFFFF
11 [!] [CON0:22] login_security_none failed rc=0xFFFFFFFF
12 [!] [CON0:22] WSARECV rc=10038
13 [!] [CON0:22] login_command failed rc=0xFFFFFFFF
14 [!] [CON0:22] login_command failed rc=0xFFFFFFFF
15 [!] [CON0:22] login_security_none failed rc=0xFFFFFFFF
16 [!] [CON0:22] WSARECV rc=10038
17 [!] [CON0:22] login_command failed rc=0xFFFFFFFF
18 [!] [CON0:22] login_command failed rc=0xFFFFFFFF
19 [!] [CON0:22] login_security_none failed rc=0xFFFFFFFF
20 [!] [CON0:22] WSARECV rc=10038



Initiator Reconnect
0 [!] [CON0:18] watchdog closing socket (123) degraded connection
1 [CON0:18] Err = 10038, bytesRX = 0
2 [CON0:18] reschedule_work [idstring="connection_rx_thread"]
3 [CON0:18] reschedule_work, threadState = 0x20
4 [CON0:18] reschedule_work process nop-out
5 [CON0:18] create_reschedule_work_thread, state= 0x20
6 [CON0:18] connection recovery started thname=Rework [CON0:18]
7 [CON0:18] [Addr:192.168.100.10 Conn:0 ID=12000012] reconnect started
8 [CON0:18] reschedule_work_thread() started
9 [CON0:18] reschedule_work_thread connection_reset
10 [CON0:18] entering reconnect state machine
11 [CON0:18] RECONNECT indicator=0 [mark=005C6DF4] factor=1 pass=0
12 [CON0:18] icmp_ping got response [mark=005C6DF4] [Addr:192.168.100.10]
13 [CON0:18] RECONNECT indicator=1 [mark=005C6DF4] factor=1 pass=1
14 [CON0:18] execute login using socket=127 [mark=005C6DF4] [Addr:192.168.100.10]
15 [CON0:18] login failed class=2 detail=3 err=-1 [mark=005C6DF5]
16 [CON0:18] RECONNECT indicator=0 [mark=005C6E2B] factor=3 pass=2
17 [CON0:18] icmp_ping got response [mark=005C6E2B] [Addr:192.168.100.10]
18 [CON0:18] RECONNECT indicator=1 [mark=005C6E2B] factor=1 pass=3
19 [CON0:18] execute login using socket=20 [mark=005C6E2B] [Addr:192.168.100.10]
20 [CON0:18] login failed class=2 detail=3 err=-1 [mark=005C6E2B]




Novell Open Enterprise Server, NetWare 6.5
Support Pack Revision 07
(C) Copyright 1983-2007 Novell Inc. All Rights Reserved. Patent Pending.
Server Version 5.70.07 September 18, 2007
Novell eDirectory Version 8.7.3.9 SMP
NDS Version 10553.73 October 9, 2006

SMITH_01:iscsi list
"InitiatorName"="iqn.1984-08.com.novell:smithtst.svt.smith."
"InitiatorAlias"="SmithTst"
"AuthMethod"="None"
"HeaderDigest"="None"
"DataDigest"="None"
"MaxConnections"="4"
"InitialR2T"="Yes"
"ImmediateData"="Yes"
"MaxRecvDataSegmentLength"="131072"
"MaxBurstLength"="131072"
"FirstBurstLength"="131072"
"DefaultTime2Wait"="2"
"DefaultTime2Retain"="20"
"MaxOutstandingR2T"="1"
"DataPDUInOrder"="Yes"
"DataSequenceInOrder"="Yes"
"ErrorRecoveryLevel"="0"

Do you have any helpful hints, or obvious miscues to point out?

The only docs I find referring to "watchdog" are for NCPCON in OESlinux.
I don't have Manage NCP Services as an option in Remote Manager.

SMITH_01:m ncp*
NCP.NLM
Loaded from on Feb 25, 2011 2:13:03 pm
(Address Space = OS)
NetWare Core Protocol (NCP) Engine
Version 5.61 July 20, 2007
Copyright 1984-2007 Novell, Inc. All rights reserved.
NCPNLM32.NLM
Loaded from [SYS:SYSTEM\] on Feb 25, 2011 2:13:05 pm
(Address Space = OS)
NetWare NWNCP Runtime Library
Version 6.01.01 September 18, 2007
(C) Copyright 1995-2007, Novell, Inc. All rights reserved.
Patent Pending--Novell, Inc.
NCPIPX.NLM
Loaded from on Feb 25, 2011 2:13:06 pm
(Address Space = OS)
Novell NCP/IPX Stack NLM
Version 5.60 April 25, 2006
Copyright 1996-2006 Novell, Inc. All rights reserved.
Labels (1)
0 Likes
7 Replies
Bob-O-Rama
Visitor.

Re: iSCSI connection "degraded", MSA P2000, NW 6.5 sp7

Hi,

Did you see this thread and this one as well regarding a similar issue...

Also the log entries "WSARECV rc=10038" indicate a basic socket connectivity issue. So this may be a generic issue of the initiator cannot talk to the target. Could be the format of the target name is wrong, DNS cannot resolve the name to an address, or the other end is not accepting the connection.

Of course the generic advice of upgrading to SP8 and post SP8 patches is, of course, always advices so you are not fighting bugs.

-- Bob
0 Likes
direwolfe Absent Member.
Absent Member.

Re: iSCSI connection "degraded", MSA P2000, NW 6.5 sp7

I did see both of those. they both get a little further than we do, since the MSA device never shows up on our side.
The MSA does see our initiator and add it as Host with default mappings. Your other advice is good, I know.

Bob-O-Rama;2080661 wrote:
Hi,

Did you see this thread and this one as well regarding a similar issue...

Also the log entries "WSARECV rc=10038" indicate a basic socket connectivity issue. So this may be a generic issue of the initiator cannot talk to the target. Could be the format of the target name is wrong, DNS cannot resolve the name to an address, or the other end is not accepting the connection.

Of course the generic advice of upgrading to SP8 and post SP8 patches is, of course, always advices so you are not fighting bugs.

-- Bob
0 Likes
direwolfe Absent Member.
Absent Member.

Re: iSCSI connection "degraded", MSA P2000, NW 6.5 sp7

Updated nw6.5 SP8
ISCSI Update for NW65SP8 1.06.05

Novell Open Enterprise Server, NetWare 6.5
Support Pack Revision 08
(C) Copyright 1983-2008 Novell Inc. All Rights Reserved. Patent Pending.
Server Version 5.70.08 October 3, 2008
Novell eDirectory Version 8.7.3.10 SMP
NDS Version 10554.34 April 23, 2008
0 Likes
jgray Absent Member.
Absent Member.

Re: iSCSI connection "degraded", MSA P2000, NW 6.5 sp7

What happens know that you have upgraded o SP8?

jgray
0 Likes
direwolfe Absent Member.
Absent Member.

Re: iSCSI connection "degraded", MSA P2000, NW 6.5 sp7

jgray;2081712 wrote:
What happens know that you have upgraded o SP8?

jgray


Results are the same as far as behavior of NRM or console commands. Logging seems to come much slower, but look slike these:

iSCSI Initiator
0 [!] [CON0:5] deinit_handle_winsock socket already closed.
1 [!] ham_abort_io obj=8D4247E0 hdl=5000005)
2 [!] Special HACB Starving wk: [CON0:9] hacb: 8F7E5E68 currentTime: 2AC5B0 hacb_state_change_time: 2AC10D
3 [!] [CON0:9] watchdog closing socket (191) degraded connection
4 [!] Special HACB Starving wk: [CON0:8] hacb: 8F7E46E8 currentTime: 2ACEE4 hacb_state_change_time: 2AC096
5 [!] [CON0:8] watchdog closing socket (158) degraded connection
6 [!] Special HACB Starving wk: [CON0:7] hacb: 8F7E1E48 currentTime: 2AD819 hacb_state_change_time: 2AC032
7 [!] [CON0:7] watchdog closing socket (108) degraded connection
8 [!] Special HACB Starving wk: [CON0:6] hacb: 8F7E06C8 currentTime: 2AE14D hacb_state_change_time: 2A9763
9 [!] [CON0:6] watchdog closing socket (130) degraded connection

853 [CON0:6] RECONNECT indicator=0 [mark=002AE977] factor=3 pass=76
854 [CON0:6] icmp_ping got response [mark=002AE977] [Addr:192.168.100.12]
855 [CON0:6] RECONNECT indicator=1 [mark=002AE977] factor=1 pass=77
856 [CON0:6] execute login using socket=145 [mark=002AE977] [Addr:192.168.100.12]
857 [CON0:6] login failed class=2 detail=3 err=-1 [mark=002AE977]
858 [CON0:6] RECONNECT indicator=0 [mark=002AE9AD] factor=3 pass=78
859 [CON0:6] icmp_ping got response [mark=002AE9AD] [Addr:192.168.100.12]
860 [CON0:6] RECONNECT indicator=1 [mark=002AE9AD] factor=1 pass=79
861 [CON0:6] execute login using socket=170 [mark=002AE9AD] [Addr:192.168.100.12]
862 [CON0:6] login failed class=2 detail=3 err=-1 [mark=002AE9AD]
863 [CON0:6] RECONNECT indicator=0 [mark=002AE9E4] factor=3 pass=80
864 [!] [CON0:6] no login response in allotted time 4320 seconds [mark=002AE9E4]
865 [CON0:6] RECONNECT indicator=2 [mark=002AE9E4] factor=1 pass=81
866 [!] [CON0:6] has failed to reconnect - destroy session [mark=002AE9E4]
867 [!] [CON0:6] reschedule_work_thread being destroyed [mark=002AE9E4]

23 [!](21) ExecuteHACB hacb=27E4D100 rc=TRANSPORT_PROTOCOL_ERROR_AT_DEVICE
24 [!] iscsiham_freeze_or_thaw_queue lanhandle=06000006 pObj=8F7E0080 thawflag=1
25 [!] ScanEvent MakeLUNList rc=1
26 [!] Receive_HACB hacb=8D472720 hatype=HAM_HACB
27 [!] Receive_HACB hacb=86249120 hatype=HAM_HACB
28 [!](3) AEN HACB recievied hacb=86249120 parm0=0x00000020
29 [!] Receive_HACB hacb=8D472A20 hatype=HAM_HACB
30 [!] Receive_HACB hacb=8D472A20 hatype=HAM_HACB
31 [!] Receive_HACB hacb=8624C020 hatype=HAM_HACB
32 [!](3) AEN HACB recievied hacb=8624C020 parm0=0x00000020
0 Likes
jgray Absent Member.
Absent Member.

Re: iSCSI connection "degraded", MSA P2000, NW 6.5 sp7

What NICs are you using?

jgray
0 Likes
direwolfe Absent Member.
Absent Member.

Re: iSCSI connection "degraded", MSA P2000, NW 6.5 sp7

jgray;2085851 wrote:
What NICs are you using?

jgray


HP NC-Series Intel N1E Ethernet driver
Driver Name N1000E.LAN
Driver Version 10.47 October 6, 2007
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.