E-Series, SANtricity and Related Plug-ins Discussions

Highlighted

iSCSI Session terminated unexpectedly - E Series

Hi Team,

 

We are receiving many errors in Santricity like below (intermittently):

 

Date/Time: 12/19/18 2:02:46 PM
Sequence number: 122377
Event type: 180D
Event category: Internal
Priority: Informational
Event needs attention: false
Event send alert: false
Event visibility: true
Description: Session terminated unexpectedly
Event specific codes: 0/0/0
Component type: iSCSI Initiator
Component location: iqn.1991-05.com.microsoft:dh325cctvrec05.com
Logged by: Controller in slot A
Raw data:
4d 45 4c 48 03 00 00 00 09 de 01 00 00 00 00 00
0d 18 49 02 56 25 1a 5c 00 00 00 00 00 00 00 00
00 00 00 00 04 00 00 00 19 00 00 00 19 00 00 00
33 00 00 00 69 71 6e 2e 31 39 39 31 2d 30 35 2e
63 6f 6d 2e 6d 69 63 72 6f 73 6f 66 74 3a 64 68
33 32 35 63 63 74 76 72 65 63 30 36 2e 61 72 61
6d 63 6f 2e 63 6f 6d 00 00 00 00 00 00 00 00 00
01 00 00 00 00 00 00 00 00 00 00 00

Date/Time: 12/19/18 2:02:46 PM
Sequence number: 122376
Event type: 180C
Event category: Internal
Priority: Informational
Event needs attention: false
Event send alert: false
Event visibility: true
Description: Connection terminated unexpectedly
Event specific codes: 0/0/0
Component type: iSCSI Initiator
Component location: iqn.1991-05.com.microsoft:dh325cctvrec06.com
Logged by: Controller in slot A
Raw data:
4d 45 4c 48 03 00 00 00 08 de 01 00 00 00 00 00
0c 18 49 02 56 25 1a 5c 00 00 00 00 00 00 00 00
00 00 00 00 04 00 00 00 19 00 00 00 19 00 00 00
33 00 00 00 69 71 6e 2e 31 39 39 31 2d 30 35 2e
63 6f 6d 2e 6d 69 63 72 6f 73 6f 66 74 3a 64 68
33 32 35 63 63 74 76 72 65 63 30 36 2e 61 72 61
6d 63 6f 2e 63 6f 6d 00 00 00 00 00 00 00 00 00
01 00 00 00 00 00 00 00 00 00 00 00

Date/Time: 12/19/18 2:02:49 PM
Sequence number: 122375
Event type: 180D
Event category: Internal
Priority: Informational
Event needs attention: false
Event send alert: false
Event visibility: true
Description: Session terminated unexpectedly
Event specific codes: 0/0/0
Component type: iSCSI Initiator
Component location: iqn.1991-05.com.microsoft:dh325cctvrec03.com
Logged by: Controller in slot B
Raw data:
4d 45 4c 48 03 00 00 00 07 de 01 00 00 00 00 00
0d 18 49 02 59 25 1a 5c 00 00 00 00 00 00 00 00
00 00 00 00 04 00 00 00 19 00 00 00 19 00 00 00
33 00 00 00 69 71 6e 2e 31 39 39 31 2d 30 35 2e
63 6f 6d 2e 6d 69 63 72 6f 73 6f 66 74 3a 64 68
33 32 35 63 63 74 76 72 65 63 30 36 2e 61 72 61
6d 63 6f 2e 63 6f 6d 00 00 00 00 00 00 00 00 00
01 00 00 00 00 00 01 00 00 00 00 00

Date/Time: 12/19/18 2:02:49 PM
Sequence number: 122374
Event type: 180C
Event category: Internal
Priority: Informational
Event needs attention: false
Event send alert: false
Event visibility: true
Description: Connection terminated unexpectedly
Event specific codes: 0/0/0
Component type: iSCSI Initiator
Component location: iqn.1991-05.com.microsoft:dh325cctvrec02.com
Logged by: Controller in slot B
Raw data:
4d 45 4c 48 03 00 00 00 06 de 01 00 00 00 00 00
0c 18 49 02 59 25 1a 5c 00 00 00 00 00 00 00 00
00 00 00 00 04 00 00 00 19 00 00 00 19 00 00 00
33 00 00 00 69 71 6e 2e 31 39 39 31 2d 30 35 2e
63 6f 6d 2e 6d 69 63 72 6f 73 6f 66 74 3a 64 68
33 32 35 63 63 74 76 72 65 63 30 36 2e 61 72 61
6d 63 6f 2e 63 6f 6d 00 00 00 00 00 00 00 00 00
01 00 00 00 00 00 01 00 00 00 00 00
 
 
Which is seriously causing problem. When we created a support case, CO asked us to fix the iSCSI sessions. We fixed iSCSI sessions from some of the hosts (Windows 2016) servers but still receiving these messages from all of the hosts. Where to start looking for more information ?
Can anyone please help.
 
Regards,
Arsalan
1 REPLY 1

Re: iSCSI Session terminated unexpectedly - E Series

Going through Support is the best way forward. Have you provided AutoSupport bundles to Support? They can look through them and see if we see any anomalies on the array side. Have you looked through your Windows server logs to see if anything is wrong there? What about your network configurations and logs? The problem could be with any of these components and essentially you will have to troubleshoot all the pieces involved. A good tool to use would be wireshark if you are familiar with it.

Forums