toasters

toasters@lists.teaparty.net

13513 discussions

Upgraded to 9.1P1 now receiving snapmirror failed emails
by Chris Hague 29 Mar '17

29 Mar '17

Hi All, This is my first post, so please be gentle. Not sure if the screen grabs will work or not (resent without screengrabs) and I hope I have removed any IP addresses etc. Basically we upgraded our 8.3.2 CDOT systems to 9.1P1 at the weekend (1 x Fas 2552 & 2 x FAS8040) We then started getting the below email on every snapmirror update; -----Original Message----- From: Sent: 25 March 2017 14:07 To: Subject: ukhc3-ntap-b: smc.snapmir.update.fail [LOG_ERR] Filer: ukhc3-ntap-b Time: Sat, Mar 25 14:07:01 2017 +0000 Severity: LOG_ERR Message: smc.snapmir.update.fail: Snapmirror update from source volume 'ntap-cl1-svmcifs:v_ukliss_cifs_sclive_t4r2mv' to destination volume 'ukliss-ntap-cl1-svmcifs_DR:mv_ukliss_cifs_sclive_t4r2' failed with error 'Note=Scheduled update operation is queued.'. Relationship UUID '18916a2e-9dae-11e6-b319-00a098a01c55'. Description: This message occurs when a scheduled SnapMirror(R) transfer fails. Action: Check the snapmirror_error log in the destination filer and take action accordingly. Source: sm_logger_main Index: 3572349 [Note: This email message is sent using a deprecated event routing mechanism. For information, search the knowledgebase of the NetApp support web site for "convert existing event configurations in Data ONTAP 9.0."] -------------------------- Yet, when checking the relationships, all appears ok and state is healthy. Snapmirror_error log shows these "delete failed" errors; Sun Mar 26 08:05:01 BST 2017 ScheduledUpdate[Mar 26 08:05:00]:18916a2e-9dae-11e6-b319-00a098a01c55 Operation-Uuid=46f5c6a8-2c4d-4bf5-aa7c-cf85563d0897 Group=none Operation-Cookie=0 sm_rpm_snaplist_delete:6682 Workflow ID [114] Snapshot "snapmirror.c677ecdf-3df5-11e6-86a9-00a098a01c55_2158347364.2017-03-26_070500" delete failed Sun Mar 26 08:05:01 BST 2017 ScheduledUpdate[Mar 26 08:05:00]:098469ee-0e4d-11e7-b319-00a098a01c55 Operation-Uuid=7e139dd9-25b1-474e-9b5c-6c8ce39a88cf Group=none Operation-Cookie=0 sm_rpm_snaplist_delete:6682 Workflow ID [112] Snapshot "snapmirror.30446395-2d51-11e6-86a9-00a098a01c55_2158347374.2017-03-26_040500" delete failed Sun Mar 26 08:05:03 BST 2017 ScheduledUpdate[Mar 26 08:05:00]:f2b650fe-a011-11e6-b319-00a098a01c55 Operation-Uuid=bfd58d04-5839-4dd8-9764-5bd5690b219b Group=none Operation-Cookie=0 sm_rpm_snaplist_delete:6682 Workflow ID [113] Snapshot "snapmirror.c677ecdf-3df5-11e6-86a9-00a098a01c55_2158347365.2017-03-26_070500" delete failed Sun Mar 26 09:05:01 BST 2017 ScheduledUpdate[Mar 26 09:05:00]:18916a2e-9dae-11e6-b319-00a098a01c55 Operation-Uuid=3b53334a-8550-4f32-890c-f456af8ea6d5 Group=none Operation-Cookie=0 sm_rpm_snaplist_delete:6682 Workflow ID [120] Snapshot "snapmirror.c677ecdf-3df5-11e6-86a9-00a098a01c55_2158347364.2017-03-26_080500" delete failed Sun Mar 26 09:05:03 BST 2017 ScheduledUpdate[Mar 26 09:05:00]:f2b650fe-a011-11e6-b319-00a098a01c55 Operation-Uuid=baa2cbbb-86b1-49e0-96a2-250973362b7b Group=none Operation-Cookie=0 sm_rpm_snaplist_delete:6682 Workflow ID [119] Snapshot "snapmirror.c677ecdf-3df5-11e6-86a9-00a098a01c55_2158347365.2017-03-26_080500" delete failed This is confirmed by doing a snap list; ukhc3::> snap list mv_ukliss_cifs_scarchive_t4r2 snapmirror.c677ecdf-3df5-11e6-86a9-00a098a01c55_2158347365.2017-03-26_080500 3.16MB 0% 0% snapmirror.c677ecdf-3df5-11e6-86a9-00a098a01c55_2158347365.2017-03-26_090500 2.93MB 0% 0% But the audit log confirms they are being deleted an hour later (confirmed time and zone all correct); Sun Mar 26 09:05:00 BST 2017 ScheduledUpdate[Mar 26 09:05:00]:18916a2e-9dae-11e6-b319-00a098a01c55 Operation-Uuid=3b53334a-8550-4f32-890c-f456af8ea6d5 Group=none Operation-Cookie=0 action=Info sm_rpm_snaplist_delete([120]): Snapshot snapmirror.c677ecdf-3df5-11e6-86a9-00a098a01c55_2158347364.2017-03-26_070500 deleted. Sun Mar 26 09:05:00 BST 2017 ScheduledUpdate[Mar 26 09:05:00]:18916a2e-9dae-11e6-b319-00a098a01c55 Operation-Uuid=3b53334a-8550-4f32-890c-f456af8ea6d5 Group=none Operation-Cookie=0 action=Info snapshot(s) up to snapmirror.c677ecdf-3df5-11e6-86a9-00a098a01c55_2158347364.2017-03-26_090500 will be selected for transfer. Sun Mar 26 09:05:00 BST 2017 ScheduledUpdate[Mar 26 09:05:00]:18916a2e-9dae-11e6-b319-00a098a01c55 Operation-Uuid=3b53334a-8550-4f32-890c-f456af8ea6d5 Group=none Operation-Cookie=0 action=Transfer_snapshots (1 of 1 log entries): snapmirror.c677ecdf-3df5-11e6-86a9-00a098a01c55_2158347364.2017-03-26_090500 Sun Mar 26 09:05:00 BST 2017 ScheduledUpdate[Mar 26 09:05:00]:f2b650fe-a011-11e6-b319-00a098a01c55 Operation-Uuid=baa2cbbb-86b1-49e0-96a2-250973362b7b Group=none Operation-Cookie=0 action=Info sm_rpm_snaplist_delete([119]): Snapshot snapmirror.c677ecdf-3df5-11e6-86a9-00a098a01c55_2158347365.2017-03-26_070500 deleted. Relationship is also healthy in oCUM (screengrab removed) However, this line is present in the snapmirror audit log; Sun Mar 26 07:05:00 BST 2017 CreateSnapshotDest[Mar 26 07:05:00]:18916a2e-9dae-11e6-b319-00a098a01c55 Operation-Uuid=93851169-93b6-4067-abfb-9948c09920c8 Group=none Operation-Cookie=0 action=End source=ntap-cl1-svmcifs:v_ukliss_cifs_sclive_t4r2mv destination=ukliss-ntap-cl1-svmcifs_DR:mv_ukliss_cifs_sclive_t4r2 status=Success Note=Scheduled update operation is queued. Success but queued? Just to see if it was an issue with the upgrade I have created multiple test relationships; Local Aggr1 to aggr2 In reverse Between the 2552 & the 8040's Between the 8040's but getting the same issue - (received same email as above) Indeed at this point I have come to the conclusion that we have hit the bug: 1042534 http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1042534 Has anyone else experienced this? Or can offer up some useful advice as to our next steps. Currently this system is only partially in production as a mv target, so the email spam is not too bad, but we plan to add many relationships very soon. Kind Regards, Chris.

1 0

cDOT 8.2.x, NDMP & NetBackup 7.7.3?
by John Stoffel 28 Mar '17

28 Mar '17

Hi all, Planning an upgrade of Netbackup to 7.7.3 to hopefully get us some proper NDMP support at the SVM level in cDOT 8.2.3P6. Any takers? Or should we try to jump to Netbackup 8.x instead? John

1 1

nuisance "Ports Down" alerts in the 9.0 OnCommand dashboard?
by Rue, Randy 28 Mar '17

28 Mar '17

Hi All, We upgraded to 9.0 and now get red alerts in the dashboard for every unused Ethernet port. This is apparently a known bug and has multiple "Feature Enhancement Requests" tied to it, but we since upgraded to 9.1 and it's still there. Vendor doesn't seem to know of any workaround. Others have this problem: https://community.netapp.com/t5/Data-ONTAP-Discussions/OnTap-9-1-OnCommand-… Anyone else had this problem, and more to the point, any luck in solving it? We'd like to avoid the annoyance of ignoring these alarms, and the risk of the clutter/noise masking any other issues. - randy

4 3

AW: NVMEM discharge FET off?
by Alexander Griesser 13 Mar '17

13 Mar '17

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(a)anexia-it.com<mailto:AGriesser@anexia-it.com> Web: http://www.anexia-it.com<http://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(a)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(a)anexia-it.com<mailto:AGriesser@anexia-it.com>> Date: Thursday, 2 March 2017 at 11:49 To: Mark Flint <mf1(a)sanger.ac.uk<mailto:mf1@sanger.ac.uk>> Cc: "toasters(a)teaparty.net<mailto:toasters@teaparty.net>" <toasters(a)teaparty.net<mailto: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(a)anexia-it.com<mailto:AGriesser@anexia-it.com> Web: http://www.anexia-it.com<http://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(a)anexia-it.com<mailto: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(a)teaparty.net<mailto:toasters-bounces@teaparty.net>> on behalf of Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>> Date: Saturday, 25 February 2017 at 20:42 To: "toasters(a)teaparty.net<mailto:toasters@teaparty.net>" <toasters(a)teaparty.net<mailto: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(a)anexia-it.com<mailto:AGriesser@anexia-it.com> Web: http://www.anexia-it.com<http://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.

2 1

AW: NVMEM discharge FET off?
by Alexander Griesser 13 Mar '17

13 Mar '17

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(a)anexia-it.com<mailto:AGriesser@anexia-it.com> Web: http://www.anexia-it.com<http://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(a)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(a)teaparty.net<mailto:toasters-bounces@teaparty.net>> on behalf of Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>> Date: Saturday, 25 February 2017 at 20:42 To: "toasters(a)teaparty.net<mailto:toasters@teaparty.net>" <toasters(a)teaparty.net<mailto: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(a)anexia-it.com<mailto:AGriesser@anexia-it.com> Web: http://www.anexia-it.com<http://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.

3 4

OSSV "systemstate" recover on Windows box
by Mr. John W. Miller 10 Mar '17

10 Mar '17

Greetings, I know how to do a SystemState recover using data backed up by OSSV. (Windows box) I want to know how OSSV is accomplishing the recover. When I do the recover, the OSSV client software says: "The machine will need restarting to complete the restore of 462 file(s)." I reboot the machine and "magic" stuff happens. I want to know: 1. where, on my Windows box, does OSSV store the recovered files 2. what is the "magic" stuff that happens when I reboot the windows box Is there a document somewhere that explains the details of this process? thanks -john miller

1 0

Measurable effects of read_realloc?
by Ehrenwald, Ian 08 Mar '17

08 Mar '17

Hello Is there a way within an SVM (cDOT 8.3.2P5) to observe the results of setting read_realloc to “on” in Oracle database flexvols? I told my DBAs that I’d be enabling this option on a couple eligible flexvols per day to see if we’d benefit from it, and we all are curious to see if it has benefited us. What sort of measurable things would someone see? Decreased latency and increased throughput after a couple weeks of heavy read load? I have OCUM/OCPM and LogicMonitor to view filer-side stats, and my DBAs have OEM to view stats coming from Oracle. Thanks for any hints. -- Ian Ehrenwald Senior Infrastructure Engineer Hachette Book Group, Inc. 1.617.263.1948 / ian.ehrenwald(a)hbgusa.com This may contain confidential material. If you are not an intended recipient, please notify the sender, delete immediately, and understand that no disclosure or reliance on the information herein is permitted. Hachette Book Group may monitor email to and from our network.

3 2

MacOS Sierra and the red bang
by Carl Howell 07 Mar '17

07 Mar '17

Ever since MacOS Sierra came out, we've had quite a few complaints of users getting access denied while accessing CIFS shares on all of our 7-Mode(8.1.4P9) filers. I've seen this behavior myself where you connect to a share and many if not all of the folders will have a red bang on them. Sometimes the red bangs will just disappear, and sometimes you have to reboot/reconnect your Mac to get them to disappear. Has anybody else seen this or have a recommendation on how to resolve this? Thanks, --Carl

2 1

WAFL paper
by Rhodes, Richard L. 07 Mar '17

07 Mar '17

Found a link to this. Algorithms and Data Structures for Efficient Free Space Reclamation in WAFL https://www.usenix.org/system/files/conference/fast17/fast17-kesavan.pdf Rick ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.

1 0

NVMEM discharge FET off?
by Alexander Griesser 25 Feb '17

25 Feb '17

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(a)anexia-it.com<mailto:AGriesser@anexia-it.com> Web: http://www.anexia-it.com<http://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

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters