toasters March 2017

toasters@lists.teaparty.net

21 participants
13 discussions

AW: X1144A - No link
by Alexander Griesser 03 Apr '17

03 Apr '17

Hi Mike, Thanks, I had a similar issue with 1G copper SFPs in the past – but that doesn’t seem to apply here since the 40G ports are on an expansion slot and do not seem to be CNA capable: *> cna_flash update all NOTE: The flash update will take up to 30 minutes per update. (Current 2 chip(s) in the system) Do not interrupt power during the update, or you risk flash image corruption. Version (5.0.2) is the same in flash and file No update of flash is needed for port 0e. Version (5.0.2) is the same in flash and file No update of flash is needed for port 0g. -> While the expansion ports are in slot 2. Also, the upgrade to Ontap 9.1 did not solve the issue – will check the cables now when I’m in the datacenter. 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: Mike Gossett [mailto:cmgossett@gmail.com] Gesendet: Samstag, 28. Januar 2017 00:58 An: Alexander Griesser <AGriesser(a)anexia-it.com> Cc: tmac <tmacmd(a)gmail.com>; toasters(a)teaparty.net Betreff: Re: X1144A - No link Just a thought- I noticed that on a FAS2554, when trying to use 1G SFPs (copper) in the UTA ports, I had similar issues. I ended up having to apply a firmware update to the UTA2 system, IIRC, from maintenance mode. I have nothing that leads me to believe that is the case here, but it sounds somewhat close. The updated firmware was actually on the system with the code it shipped with, but needed to be manually applied. If all else fails, there's always a support ticket :) HTH Mike On Fri, Jan 27, 2017 at 7:39 AM, Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>> wrote: Those are optical cables, that got shipped with the card and the transceivers. According to HWU, those are the transceivers: << pic removed >> They look exactly like these and HWU calls them X65402. The connector looks exactly like the MPO connector which can also be seen in HWU and hast he cable number X66200-2 – so this is what I got: X1144A Adapter X65402 Transceivers X66200-2 Cables Should all play well with 9.1RC2 on the AFF-A300. Since 9.1 has already been released, I’ll upgrade this system to 9.1 and see if that changes anything – maybe there’s a reason why they call it RC ☺ 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: tmac [mailto:tmacmd@gmail.com<mailto:tmacmd@gmail.com>] Gesendet: Freitag, 27. Januar 2017 14:34 An: Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>> Cc: toasters(a)teaparty.net<mailto:toasters@teaparty.net> Betreff: Re: X1144A - No link OK, a little confused now. Are you trying to use copper or optical? According to HWU, the X1144A as QSFP+ slots and the cable ends look identical to the SAS cables. The NetApp end should be any supported copper cable with a QSFP+ end or an optical transciever (X65402A, mfg 332-00389). The optical transciver will have the QSFP+ going into the filer and exposing the MPO end for your optical cable Since it looks like you are trying to use Optical, are you *sure* the optical transcivers are the right ones for that card? --tmac Tim McCarthy, Principal Consultant Proud Member of the #NetAppATeam<https://twitter.com/NetAppATeam> I Blog at TMACsRack<https://tmacsrack.wordpress.com/> On Fri, Jan 27, 2017 at 8:14 AM, Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>> wrote: That’s the 2-port 40G card with QSFPs and those funny new cables, no breakout cables. http://cdn3.bigcommerce.com/s-uiigcj2/product_images/uploaded_images/mtp-ca… 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: tmac [mailto:tmacmd@gmail.com<mailto:tmacmd@gmail.com>] Gesendet: Freitag, 27. Januar 2017 13:40 An: Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>> Cc: toasters(a)teaparty.net<mailto:toasters@teaparty.net> Betreff: Re: X1144A - No link Curious...are you using it as a two-port 40Gb card or using the breakout cable? --tmac Tim McCarthy, Principal Consultant Proud Member of the #NetAppATeam<https://twitter.com/NetAppATeam> I Blog at TMACsRack<https://tmacsrack.wordpress.com/> On Fri, Jan 27, 2017 at 7:13 AM, Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>> wrote: Good question – I’m using the QSFPs and the cables that came with the cards, so I’m positive that those should be supported. But I’m trying to find out. 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: tmac [mailto:tmacmd@gmail.com<mailto:tmacmd@gmail.com>] Gesendet: Freitag, 27. Januar 2017 13:04 An: Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>> Cc: toasters(a)teaparty.net<mailto:toasters@teaparty.net> Betreff: Re: X1144A - No link what is the cable that you are using? Anything supported? [Inline image 1][Inline image 2] --tmac Tim McCarthy, Principal Consultant Proud Member of the #NetAppATeam<https://twitter.com/NetAppATeam> I Blog at TMACsRack<https://tmacsrack.wordpress.com/> On Fri, Jan 27, 2017 at 5:16 AM, Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>> wrote: Hi, I’ve just installed those fancy X1144A cards in one of our AFF300 systems and it seems they’re getting recognized properly, but I’m not able to get a link on them. sysconfig says: slot 2: 40 Gigabit Ethernet Controller XL710 QSFP+ e2a MAC Address: 3c:fd:fe:a2:90:c8 (auto-unknown-down) e2e MAC Address: 3c:fd:fe:a2:90:c9 (auto-unknown-down) SAN01::> net port show -port e2* (network port show) Node: SAN01-01 Speed(Mbps) Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status --------- ------------ ---------------- ---- ---- ----------- -------- e2a Default - down 1500 auto/10 - e2e Default - down 1500 auto/10 - Node: SAN01-02 Speed(Mbps) Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status --------- ------------ ---------------- ---- ---- ----------- -------- e2a Default - down 1500 auto/10 - e2e Default - down 1500 auto/10 - 4 entries were displayed. For testing purposes, I did connect e2a on node1 to e2a on node 2 and I already tried exchanging the QSFPs and cables, but still no dice. Any idea what could be wrong here? According to HWU, the minimum required OS version is 9.1RC2, which is exactly what is installed currently: SAN01::> version NetApp Release 9.1RC2: Thu Nov 24 08:59:46 UTC 2016 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 _______________________________________________ Toasters mailing list Toasters(a)teaparty.net<mailto:Toasters@teaparty.net> http://www.teaparty.net/mailman/listinfo/toasters _______________________________________________ Toasters mailing list Toasters(a)teaparty.net<mailto:Toasters@teaparty.net> http://www.teaparty.net/mailman/listinfo/toasters

4 4

Upgraded to 9.1P1 now receiving snapmirror failed emails
by Chris Hague 01 Apr '17

01 Apr '17

Hi All, This is my first post, so please be gentle. Not sure if the screen grabs will work or not 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 [cid:image001.png@01D2A616.5C0DB820] 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; [cid:image012.jpg@01D2A61B.D7A63ED0] Indeed at this point I have come to the same conclusion that we have hit the bug: 1042534 http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1042534 [cid:image006.png@01D2A611.FF15CF80] [cid:image007.png@01D2A611.FF15CF80] 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.

3 2

Franken-Filers: FAS2240-2 to FAS2552, DS4246 to FAS2554
by Stephen Stocke 31 Mar '17

31 Mar '17

Hi All At the end of a current migration and controller upgrade project I'll have some spare FAS2240-2 arrays (with disks) and a spare DS4246 hybrid shelf. I'll also have a pile of FAS255X controllers. Is there any reason that I can't just swap the FAS2240 controller modules for the FAS255X modules and install CDOT on the zeroed disks? What about swapping the IOM6's from the DS4246 and making a FAS2554? All this kit is under support and fully licensed but I'm not too concerned about long-term support. I just want to make use of this gear to run CDOT 9.x in a dev/test lab. Thanks Steve

1 0

FAS2552 -> FAS8200 migration
by Chris Good 29 Mar '17

29 Mar '17

Folks, Currently we have a FAS2552 switchless cluster running 9.1. We're planning an upgrade to FAS8200 and considering our migration options. Netapp themselves aren't being terribly forthcoming on the best route to do this. I had hoped that upgrading from a FAS25xx would be a common thing with a reference workflow to go with it. Maybe things are complicated somewhat because the FAS2552 runs ADP and the FAS8200 doesn't. Has anyone been through a similar process or have any recommendations for a route to achieve this? Thanks, Chris

7 14

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

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 March 2017