12610 NVDIMM ultracap capacitance discharged

[ACLHelpdesk]

Can anyone help with this "12610 NVDIMM ultracap capacitance discharged" on s CS500 SAN

Thanks

[sbhat09]

Hello @ACLHelpdesk,

If it is feasible, you can try to shutdown, powerdrain the system and restart.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.

[ACLHelpdesk]

Thank you Srinivas 

We will try that

[ACLHelpdesk]

@sbhat09 

Hi again,

We discussed powering down / rebooting the system and this is not an option for the customer.
> We have a replacement controller on its way to replace the old one,
are you able to share any possible issues replacing the controller? ie Firmware issues

Also the Warning (12610 NVDIMM ultra cap capacitance discharged) showed up on an event log a few days ago indicating that a 7day timer had started until power down. but diagnostics are currently showing nothing??
was this warning a red hearing

Many thanks for your help

Ciaran

[Mahesh202]

Hi ACLHelpdesk

I would not suggest you Shutdown/Restart, or power drain the system, that is not a solution.

The NVDIMM firmware periodically measures the remaining PowerGEM capacitance and raises a flag to software if it is deemed insufficient to guarantee a save and restore cycle in the event of system power loss. (Note: Software only sees that the flag has been asserted and does not know/control the capacitance threshold.)

The capacitance measurement process is susceptible to inherent random measurement error. Any given measurement could be randomly off to the degree that it crosses the threshold and raises the flag. The subsequent measurement does not see the same error and clears the flag, so the software reports it is now OK.

If you are running 5.2.1.300 or later Contains the fix then the controller needs to be replaced.

Hope this helps.!!

Regards
Mahesh.

[ACLHelpdesk]

@Mahesh202 

Thank you for your reply Mahesh we really appreciate it!

So Just to insure we understand correctly

On older versions a false warning may be flagged but if the warning is flagged on  5.2.1.300 (or above) its not likely to be false and therefore the controller needs to be replaced.

Can er also ask is there any other alternative to replacing the whole controller?

Many Thanks

Ciaran

[Mahesh202]

Hi Ciaran

Yes, that's the correct understanding. Prior to, The arrays which are running with newer versions after Nimble version 5.2.1.300 are less likely to have false alerts.
Considering the nimble support logs and frequency of the alerts may conclude the need for replacement. 

There is no alternative to replacing the controller

Regards
Mahesh