Hmm, in the traditional way “it works on my netapp” ☺
Even if there’s no fault, that line *should* bring you back the info from the lines starting with NV. See the output in the mail trail below, so if you’re not seeing those lines, then we have a mismatch somehow. Seem your other mails, so I know it’s ;gone away’ for now, but still a little puzzled as to why you’re not seeing Them at all.
`Mark
From: Alexander Griesser AGriesser@anexia-it.com Date: Friday, 10 March 2017 at 23:44 To: Mark Flint mf1@sanger.ac.uk Cc: "toasters@teaparty.net" toasters@teaparty.net Subject: AW: NVMEM discharge FET off?
Hi Mark,
that’s unfortunately also not returning anything:
san01::> system node environment sensors show -name NV* There are no entries matching your query.
san01::> set diag
Warning: These diagnostic commands are for use by NetApp personnel only. Do you want to continue? {y|n}: y
san01::*> system node environment sensors show -name NV* There are no entries matching your query.
Best,
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Mark Flint [mailto:mf1@sanger.ac.uk] Gesendet: Freitag, 3. März 2017 11:27 An: Alexander Griesser AGriesser@anexia-it.com Betreff: Re: NVMEM discharge FET off?
Apologies, it’s NVRAM, about 6 or so pages down the list…… System node environment sensors show –name NV* works fine. cluster1::> system node environment sensors show -name NV* Node Sensor State Value/Units Crit-Low Warn-Low Warn-Hi Crit-Hi ---- --------------------- ------ ----------- -------- -------- ------- ------- cluster1-01 NVRAM Discharge FET normal ON NVRAM Charge FET normal ON NVRAM Batt Pct Capacity normal 78 % 49 52 - - NVRAM Batt Fault normal GOOD NVRAM Power Fault normal GOOD NVRAM Batt Design Cap. normal 2500 mAh - - - - NVRAM Batt Cycle Count normal 46 - - - 251 NVRAM Batt Full Capacity normal 1966 mAh - - - - NVRAM Batt Rem. Capacity normal 503 mAh 279 299 - - NVRAM Batt Current normal 0 mA -901 -1 1201 1501 NVRAM Batt Voltage normal Press <space> to page down, <return> for next line, or 'q' to quit... q 11 entries were displayed.
`Mark
From: Alexander Griesser <AGriesser@anexia-it.commailto:AGriesser@anexia-it.com> Date: Thursday, 2 March 2017 at 11:49 To: Mark Flint <mf1@sanger.ac.ukmailto:mf1@sanger.ac.uk> Cc: "toasters@teaparty.netmailto:toasters@teaparty.net" <toasters@teaparty.netmailto:toasters@teaparty.net> Subject: AW: NVMEM discharge FET off?
Hi,
I couldn’t find entries with „NVMEM“ in the name, but here’s everything that has „BAT“ in its name – is that what we’re looking for?
san01::> system node environment sensors show -name Bat* Node Sensor State Value/Units Crit-Low Warn-Low Warn-Hi Crit-Hi ---- --------------------- ------ ----------- -------- -------- ------- ------- san01n01 Bat Present normal PRESENT Bat Temp normal 24 C 0 5 53 58 Bat Volt normal 8100 mV 5500 5600 8500 8600 Bat Curr normal 0 mA - - 2320 2600 Bat Rem Cap normal 3328 mA*hr - - - - Bat Full Cap normal 3328 mA*hr - - - - Bat Charge Curr normal 0 mA - - 2200 2300 Bat Charge Volt normal 8200 mV - - 8900 9000 Bat Initial FCC normal 3200 mA*hr - - - - Bat Dstg Cycles normal 21 cycles 2 5 - - Bat Power Fault normal GOOD Bat Dcharge FET normal ON Bat Charge FET normal ON Bat Cycle Count normal 4 cycles - - - - san01n02 Bat Present normal PRESENT Bat Temp normal 24 C 0 5 53 58 Bat Volt normal 8100 mV 5500 5600 8500 8600 Bat Curr normal 0 mA - - 2320 2600 Bat Rem Cap normal 3328 mA*hr - - - - Bat Full Cap normal 3328 mA*hr - - - - Bat Charge Curr normal 0 mA - - 2200 2300 Bat Charge Volt normal 8200 mV - - 8900 9000 Bat Initial FCC normal 3200 mA*hr - - - - Bat Dstg Cycles normal 21 cycles 2 5 - - Bat Power Fault normal GOOD Bat Dcharge FET normal ON Bat Charge FET normal ON Bat Cycle Count normal 3 cycles - - - - 28 entries were displayed.
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Mark Flint [mailto:mf1@sanger.ac.uk] Gesendet: Donnerstag, 2. März 2017 12:16 An: Alexander Griesser <AGriesser@anexia-it.commailto:AGriesser@anexia-it.com> Betreff: Re: NVMEM discharge FET off?
Take a look at the output from system sensors, should show you the battery, whether it’s charging or not, And at what voltage
System node environment sensors show
And look for the nvmem battery info
`Mark
From: <toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net> on behalf of Alexander Griesser <AGriesser@anexia-it.commailto:AGriesser@anexia-it.com> Date: Saturday, 25 February 2017 at 20:42 To: "toasters@teaparty.netmailto:toasters@teaparty.net" <toasters@teaparty.netmailto:toasters@teaparty.net> Subject: NVMEM discharge FET off?
Hi,
anyone ever had these?
2/25/2017 19:39:32 san01n01 EMERGENCY nvmem.battery.capLowCrit: The NVMEM battery capacity is critically low (0 cycles). To prevent data loss, the system will shut down in 20 minutes. 2/25/2017 17:43:26 san01n02 EMERGENCY nvmem.battery.discFET.off: The NVMEM battery discharge FET is off. To prevent data loss, the system will shut down in 5 minutes. 2/25/2017 17:32:26 san01n02 ALERT nvmem.battery.FET.off: The NVMEM battery charge FET is off. To prevent data loss, the system will shut down in 24 hours. 2/25/2017 17:29:27 san01n01 EMERGENCY nvmem.battery.capLowCrit: The NVMEM battery capacity is critically low (0 cycles). To prevent data loss, the system will shut down in 20 minutes. 2/25/2017 16:20:52 san01n01 EMERGENCY nvmem.battery.discFET.off: The NVMEM battery discharge FET is off. To prevent data loss, the system will shut down in 5 minutes.
The system did not shut down and all `system health` related commands I’m aware of tell me, that everything is good. This is a brand new AFF A300, but it’s been running since about a month now, so it’s not been powered on today or anything like that which would rectify these messages sometimes.
Best,
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
-- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE. -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.