Unsolved
This post is more than 5 years old
2 Posts
0
1633
October 11th, 2018 08:00
PS6210 Unexpected login failure code
A few days ago we received about 40 Errors in about 30 seconds with the message:
7.4.3 iSCSI login to target ___from initiator ___ failed for the following reason:
7.4.42 Unexpected login failure code.
This was followed a few minutes later by:
28.3.29 Active control module cannot communicate with secondary control module. Failover cannot occur.
33.3.0 Communication link between control modules has shut down.
28.3.20 Control module was removed from array.
28.4.50 Control module in slot 1 is not functioning or not installed.
Within a minute of those messages, the control modules come back up and everything appears to be working properly again. The installed firmware is version 7.1.7. Does anyone have any ideas about what is at fault here and what needs to be done to address this? Thanks.
0 events found
dwilliam62
6 Operator
•
1.5K Posts
•
6.4K Points
0
October 11th, 2018 09:00
Hello,
Re: 1. That usually is an issue with the server not array. What OS's are you connecting to the group with?
Re: 2. CM One of those CMs is likely bad. It could either be the active or passive. When the passive can't access the active, it will restart itself to see if that resolves it. That's the removed messages are referring to.
If it then connects to the active controller it will show a good / synced status with it.
That firmware is pretty old,. I would suggest upgrading to at least 9.1.x or better yet 10.0.1.
I suspect you will need to replace a controller in the end.
Regards,
Don
aitcome
2 Posts
0
October 11th, 2018 10:00
We are connecting from Server 2012 VMs. Based on the fact that we haven't really had issues until now, we were thinking these error messages were all related but it sounds like you don't think they necessarily are. Is there something that we might be able to look at that would let us rule out the PS6210 as the source of the Unexpected login errors?
dwilliam62
6 Operator
•
1.5K Posts
•
6.4K Points
0
October 11th, 2018 13:00
Hello,
I suspect the timing of the messages is coincidental. The passive controller isn't involved in the login process.
It would take a Wireshark trace to decode what the actual error is to get an idea if it's array or server. I will say almost exclusively it's the server in these cases.
If you have support on this group I would suggest opening a case to get the controller replaced and upgrade to current EQL firmware. Then see if the login messages going away. If not work with support on resolving that error. I presume that after the error the server logs in OK?
Regards,
Don