[Info-vax] Main cabinet fault indicator on an MSA1000

[Stephen Hoffman]

On 2018-08-22 17:39:36 +0000, Rich Jordan said:

>      thanks for replying.  Its the chassis fault light, not the one on 
> each of the MSA controllers.  Both controllers are showing good status 
> after the onsite went through and deleted all the alerts from our 
> testing.
>      We did dump the eventlog via CLI from both controllers prior to 
> the onsite clearing all the alerts; assuming the eventlogs are the same 
> thing the controllers will display via the buttons, there should be no 
> more faults logged (though I'll check again today to make sure no new 
> ones).
> 
>      I will pass along the possibility of doing a POST via the buttons 
> when they are at end of day.  Thing is that is still the controllers 
> doing POST, so I don't know if it will have any impact on the chassis 
> fault indicator, if it POSTS the SAN switches or EMU or SCSI 
> interfaces, etc.  If there's any docs on that one beyond 'it lights up 
> amber when a fault is detected in one or more subsystems' I haven't 
> been able to find it.  I won't be surprised it it does take a full 
> power cycle to make it go away.
>      Hopefully don't lose another piece of kit when we cycle it...


A chassis fault wouldn't surprise me, then.  Manual POST on the MSA 
controller(s) present in the chassis probably won't clear a chassis 
fault.

Though I would be interested in knowing if that manual POST sequence 
even works.  Not that I'd be inclined to try that on a production box.

Power-cycling the chassis — the whole array — might clear the fault, on 
the off chance it was a power glitch or ilk, and something in the 
chassis got stuck in a weird state.

Or it's bad hardware, and it might not come back short of swappage.

Given the vintage of this gear, power-cycling the chassis might also 
trigger new problems with the chassis or with the HDDs.  Have spare 
parts available, etc.



-- 
Pure Personal Opinion | HoffmanLabs LLC