This post is more than 5 years old
8 Posts
1
3764
Clean Fault condition
Hi, this is my problem:
My customer have two VNX 5300 with 4 DAEs. My job was to add one more DAE to each storage.
For this task I used USM. In the first VNX everything ran ok, the new DAE was installed without troubles.
In the second storage, I conected one SAS cable to the last enclosure (bus 0) and the second SAS cable, by mistake, in another enclosure (bus 1). Inmediately I saw the error and I corrected it but at this time the Unisphere had already detected two new enclosures, one per bus.
In Unisphere, the real enclosure appear with “Fault” and the other “phantom” enclosure appear like “Missing”.
I want to clean this conditions but I don´t know how to do it.
I apreciate any help.
brettesinclair
2 Intern
2 Intern
•
715 Posts
0
January 31st, 2015 04:00
What alerts are displayed ? Do any components have a fault led lit ?
Can you paste up the out out of a getcrus ?
naviseccli -h arrayspaddress getcrus -all
If there's no component failure, check and reseat your lcc cables.
Then remove and reinstall the DAE (as you've described) and finally, if required, reboot the SP's. (make sure your multipathing status is all good)
dynamox
2 Intern
2 Intern
•
20.4K Posts
1
January 28th, 2015 04:00
did you try to restart Unisphere Management server (http://spa/setup)
Ulkan
8 Posts
0
January 28th, 2015 04:00
I will try...thank!!
brettesinclair
2 Intern
2 Intern
•
715 Posts
0
January 28th, 2015 04:00
Restarting the management server on each SP should clear them
Https://spaipaddress/setup
scroll down to "Restart Management Server" and execute. Wait 10mins, verify it's ok then do same for spb
edit : beaten by Dynamox
Ulkan
8 Posts
0
January 31st, 2015 03:00
Well, I did the "Restart Management Server" in each SP...
The "phantom" enclosure that I told you disappeared, but the "F" in my new enclosure is remaining.
I am thinking turn of this DAE, to do a new "Restart Management Server" and reinstall it. Remember that the DAE is new and all its disks are Unbound.
Reboot SP is an option?
What do you think?
Best regards!!
Ulkan
8 Posts
0
January 31st, 2015 05:00
Thank for response Brett@S!!
The nexts days I´ll try to do it and comunicate results.
Thank again!!
Ulkan
8 Posts
0
February 3rd, 2015 15:00
Eureka!!
I detached the DAE, then rebooted SP´s. At this point the fault dissapeared. After that I reintalled the DAE using USM (and cabling in right way) and everything ran ok.
Thank a lot, Brett@s and dynamox!!!
javier
brettesinclair
2 Intern
2 Intern
•
715 Posts
0
February 3rd, 2015 20:00
You're welcome, and thanks for the update
dendoovp
1 Message
0
March 17th, 2015 03:00
Naviseccli –h <IP_address_of_SP-A> remoteconfig –messner –stop (stops the K10 Governor)
Naviseccli –h <IP_address_of_SP_B> remoteconfig –messner -stop
G. Restart Navisphere Manager to verify faults are cleared and event logs are not logging any unknown errors.
5_hole
1 Message
0
September 6th, 2016 12:00
i am having a similiar issue. When i try the above command, i hget http/1.1 405 metho not allowed
kelleg
4.5K Posts
0
September 8th, 2016 09:00
the commands in step #3 should not be used - these can cause the SP to reboot. If you have a DAE still showing in Unisphere, then the other steps should help to remove it. You may need to reboot the Storage Processors (SP's).
glen