This post is more than 5 years old
15 Posts
0
1735
May 30th, 2016 07:00
PS4000E with possible failed controller?
I have a PS4000E that I recently upgraded the firmware to 8.1.3. During the upgrade and subsequent reboot, the member would not come online and join the group. However, when we reboot it again, it will.
Currently, it is running on controller 0, and all is well. As a test, I initiated a restart, failing it over to controller 1, and again, it will not rejoin the group. I can ping the members management IP, I can even SSH into it in order to restart it again, back to controller 0. But it will not join the group from controller 1.
I'd really like to resolve this. This has been a very reliable system, but I'm now in a position to have to schedule downtime for the next firmware upgrade because the failover isn't working as it should. My warranty is expired on this array, so I cannot just submit a ticket either.
Suggestions?
RPerrySMM
15 Posts
0
May 31st, 2016 10:00
1. Yes, everything is cabled up correctly. Prior to the upgrade to the latest firmware, failover happened without issue.
2. Yes, both controllers are visible in the GUI.
3. When I SSH to the management IP of the member (not the group), I am connected to the member. I issue the restart command while pinging the management IP. The restart takes place, the failover happens. There is a brief pause in ping while the failover happens. After the restart, the member does not rejoin the group, but I am able to SSH into the member using the management IP. I then issue another restart command to get it to fail back to the working controller.
I'm not sure where to go to get any error logs for why the member will not rejoin the group. This has never happened prior to the firmware upgrade, and so my only suspects are a problem with the firmware on that controller, failed or failing NICs on the controller, or something else that I am missing.
RPerrySMM
15 Posts
0
May 31st, 2016 11:00
No, the support contract has expired. And I agree with verifying the cabling to ensure that the passive controller is actually located on active ports. That will be my next step. Thanks.
RPerrySMM
15 Posts
0
June 1st, 2016 15:00
It has been over 15 months since I was physically present on-site. Somewhere along the line, the 2 NICs from the inactive controller was in fact disconnected. Problem found. Thanks!