toasters April 2017

toasters@lists.teaparty.net

35 participants
22 discussions

Wafl clean stalling
by Fred Grieco 07 May '17

07 May '17

I had this issue twice now on two different systems. There will be "sudden" high latency, across the board. Oncommand performance manager will have a some disk layout warnings, and tons of latency warnings with no clear shark. Grafana stats will show high "Wall write cleaning" utilization. Sysstat shows slow flushing CPs with a lot of "s" type... Special files. First time (3250 8.2.3p5 cdot) I had to do a takeover just to break the spell, latency and cpu were so bad. Second time was on a fas8080 8.3.1, so a little more robust. In this case, wafl scan stats showed a long, stalled snap create summary (see bottom, outputs on same color several min apart). This is a Snapmirror source, and aborting the sm processes on the dest fixed the problem and eliminated the snap create wafl scan, even though they were completing regularly (though slowly). The only common denominator here is both of these systems use flashpool. Has anyone seen this before? I'm really baffled that the sm abort fixed the issue on the source. I have a case open with support and so far they are saying "lots of Snapmirror processes" but it's really only about 20... Thanks, Fred CPU NFS CIFS HTTP Total Net kB/s Disk kB/s Tape kB/s Cache Cache CP CP Disk OTHER FCP iSCSI FCP kB/s iSCSI kB/s in out read write read write age hit time ty util in out in out 29% 1309 0 0 2644 747 10568 450806 363535 0 0 0s 92% 100% :s 31% 123 1212 0 43230 172098 0 0 18% 278 0 0 2286 435 55557 238412 105938 0 0 0s 94% 100% :s 10% 838 1170 0 47435 103353 0 0 14% 357 0 0 1278 527 13516 110072 20700 0 0 1 94% 100% :s 9% 214 707 0 20912 59405 0 0 17% 506 0 0 3171 611 55294 220118 43358 0 0 0s 93% 100% :s 10% 1052 1613 0 33894 144762 0 0 17% 475 0 0 2025 415 33509 230281 43878 0 0 1 93% 100% :f 14% 587 963 0 20764 109122 0 0 16% 525 0 0 2167 289 4638 78980 62 0 0 1 92% 100% :v 7% 326 1316 0 33645 67102 0 0 24% 766 0 0 2069 681 4712 289509 157377 0 0 0s 94% 93% Zn 16% 289 1014 0 30442 67344 0 0 18% 232 0 0 1518 387 30691 217187 205447 0 0 0s 94% 100% :s 18% 615 671 0 4686 92926 0 0 18% 302 0 0 1830 593 29273 211516 112819 0 0 0s 94% 100% :s 11% 577 951 0 13343 94976 0 0 16% 404 0 0 1381 248 1508 74363 51789 0 0 1s 95% 100% :s 6% 144 833 0 18491 66701 0 0 15% 250 0 0 1437 362 25192 127166 14783 0 0 0s 95% 100% :s 13% 469 718 0 5478 64261 0 0 15% 272 0 0 1315 289 26669 75965 7 0 0 0s 95% 100% :s 5% 488 555 0 9930 56409 0 0 15% 362 0 0 1352 384 9242 126759 56523 0 0 1 92% 100% :s 5% 224 766 0 4169 61645 0 0 17% 393 0 0 1667 527 41316 162630 0 0 0 0s 93% 100% :s 14% 683 591 0 2742 91873 0 0 13% 489 0 0 1847 382 22543 126444 0 0 0 0s 91% 100% :s 10% 416 942 0 13912 98668 0 0 12% 466 0 0 1576 267 1942 125502 22 0 0 >60 92% 100% :s 8% 75 1035 0 25502 105575 0 0 19% 648 0 0 2236 616 12843 180895 7 0 0 1 91% 100% :f 13% 259 1329 0 20573 112682 0 0 17% 589 0 0 2648 732 40612 165832 43495 0 0 1 93% 100% :v 16% 662 1397 0 30105 84571 0 0 13% 298 0 0 1494 224 5258 75630 47 0 0 0s 91% 100% :v 19% 93 1103 0 37230 59553 0 0 25% 961 0 0 2517 611 7662 293316 228741 0 0 0s 95% 93% Zs 24% 70 1486 0 28444 64059 0 0 CPU NFS CIFS HTTP Total Net kB/s Disk kB/s Tape kB/s Cache Cache CP CP Disk OTHER FCP iSCSI FCP kB/s iSCSI kB/s in out read write read write age hit time ty util in out in out 18% 713 0 0 1802 308 4102 139025 138664 0 0 1s 93% 100% :s 17% 106 983 0 12370 67131 0 0 18% 653 0 0 2290 356 3024 175784 114858 0 0 0s 93% 100% :s 17% 103 1534 0 30419 103879 0 0 14% 277 0 0 1117 264 835 96862 48373 0 0 0s 93% 100% :s 16% 168 672 0 12616 68979 0 0 13% 465 0 0 1236 616 1505 56551 19 0 0 0s 94% 100% :s 13% 150 621 0 10984 51964 0 0 13% 363 0 0 1184 359 724 47141 6 0 0 1 93% 100% :s 14% 175 646 0 15597 41360 0 0 16% 394 0 0 1192 330 1622 150649 62399 0 0 0s 93% 100% :s 21% 149 649 0 13094 89017 0 0 16% 1660 0 0 2609 1180 3836 101862 22 0 0 1 88% 100% :s 15% 203 746 0 12464 58093 0 0 15% 2306 0 0 3503 1574 23707 144890 0 0 0 0s 93% 100% :s 17% 442 755 0 11702 95250 0 0 14% 1118 0 0 2256 570 30514 97837 33885 0 0 1 95% 100% :f 10% 612 526 0 9866 54222 0 0 14% 3636 0 0 4489 1649 7360 70514 66 0 0 1 92% 100% :v 7% 238 615 0 10162 56678 0 0 13% 3540 0 0 4277 1615 2594 63757 0 0 0 1s 91% 100% :v 6% 129 608 0 14768 48771 0 0 16% 2842 0 0 4097 1682 20595 137085 22 0 0 1 93% 100% :v 14% 416 839 0 14408 78167 0 0 15% 2544 0 0 3760 1540 37961 125949 0 0 0 0s 94% 100% :v 10% 692 524 0 10924 100674 0 0 26% 2493 0 0 4307 991 9312 275089 153829 0 0 0s 94% 90% Zs 22% 329 1485 0 44023 126413 0 0 16% 1624 0 0 2577 1154 3959 179468 99585 0 0 0s 93% 100% :s 20% 145 808 0 20926 89793 0 0 19% 2543 0 0 4807 2015 59604 258735 76443 0 0 0s 94% 100% :s 17% 1042 1222 0 30911 147132 0 0 18% 3354 0 0 4264 1452 1771 189401 92019 0 0 0s 94% 100% :s 7% 93 817 0 14723 84496 0 0 13% 3561 0 0 4435 1553 1027 99965 47137 0 0 0s 93% 100% :s 6% 101 773 0 10691 82650 0 0 18% 2808 0 0 3998 1687 6156 174923 125 0 0 1 92% 100% :s 14% 216 974 0 19335 117237 0 0 18% 4372 0 0 6370 2245 55867 242723 67036 0 0 0s 94% 100% :s 10% 1019 979 0 19915 133940 0 0 Volume $$$$$$$$$$$$$$$$$$$$$$$$$$: Scan id Type of scan progress 6 active bitmap rearrangement fbn 19501 of 21126 w/ max_chain_len 311362705 snap create summary update block 3 of 2112711363427 block ownership calculation block 6400 of 2112611363428 blocks used summary update block 889 of 21127 Volume $$$$$$$$$$$$$$$$$$$$$$$$$$: Scan id Type of scan progress 6 active bitmap rearrangement fbn 19501 of 21126 w/ max_chain_len 311362705 snap create summary update block 5 of 2112711363427 block ownership calculation block 6500 of 2112611363428 blocks used summary update block 2096 of 21127 Volume $$$$$$$$$$$$$$$$$$$$$$$$$$: Scan id Type of scan progress 6 active bitmap rearrangement fbn 19502 of 21126 w/ max_chain_len 311362705 snap create summary update block 4 of 21127 (fbn 211)11363427 block ownership calculation block 7100 of 2112611363428 blocks used summary update block 2799 of 21127 (fbn 3952) This e-mail and its attachments are intended only for the individual or entity to whom it is addressed and may contain information that is confidential, privileged, inside information,or subject to other restrictions on use or disclosure. Any unauthorized use, dissemination or copying of this transmission or the information in it is prohibited and may be unlawful. If you have received this transmission in error, please notify the senderimmediately by return e-mail, and permanently delete or destroy this e-mail, any attachments, and all copies (digital or paper). Unless expressly stated in this e-mail, nothing in this message should be construed as a digital or electronic signature. For additionalimportant disclaimers and disclosures regarding KCG’s products and services, please click on the following link: http://www.kcg.com/legal/global-disclosures

1 1

Add new ports to interface groups
by Alexander Griesser 28 Apr '17

28 Apr '17

Hey there, I'm currently thinking about upgrading some of my filers from 10G to 40G interfaces. This would involve pulling out the 10G card and inserting the 40G card, so one halt per node is necessary, which isn't really the problem. I'm just a bit unsure of the best way to move my a0a ifgrp to the new ports - I remember that in the past when you wanted to switch the ifgrp to a different portspeed, you had to recreate it completely which is a bit cumbersome due to all the VLANs built on top of it - has that changed? If I issue a takeover of the first system and replace the card, it will probably boot up with a broken ifgrp configuration since it cannot find the physical ports in the ifgrp anymore and I'm looking for the best way to do a physical port upgrade like this now, so if anyone has gone through that already, feedback would be greatly appreciated. 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

4 10

CIFS and AV
by TAYLOR DANIEL 26 Apr '17

26 Apr '17

As we make an increasing push to use CIFS I am interested to know what peoples thoughts and opinions are on scanning data on CIFS shares for viruses etc. Does anyone use the Anti-Virus connector for Clustered Data ONTAP? does it work or have experience with it, and what are the alternatives other than to let the clients use their own AV to deal with potential nasties!

6 5

Sorting output?
by Ehrenwald, Ian 25 Apr '17

25 Apr '17

Hello As far as I can tell, this does not exist but it would be great to sort command output without calling from a script externally and parsing output. I’d love something like: Cluster1::> volume show -vserver MySvm -fields volume,aggregate,size –sort-key size -direction descending We know there is sorting capability already, since the ‘statistics’ command has a –sort-key. Any chance someone could a file a request for enhancement on my (our?) behalf to add sort-key to commands used in typical day-to-day operation? Thanks! -- 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 3

VMWare vswap files
by Chris Hague 25 Apr '17

25 Apr '17

What are everyones thoughts about best practices on separating VMWare vswap files from the VM ? What happens if you have all the vswap's on 1 volume \ datastore and it goes offline?

5 4

vifmgr.lifs.noredundancy
by TAYLOR DANIEL 20 Apr '17

20 Apr '17

Hello, Since the dawn of its inception by another third party we have been getting these messages for both intercluster LIFs: Filer: ntap-a Time: Sun, Apr 16 00:15:05 2017 +0100 Severity: LOG_ALERT Message: vifmgr.lifs.noredundancy: No redundancy in the failover configuration for 1 LIFs assigned to node “ntap-a”. LIFs: uk:ntap_a_intercluster Description: This message occurs when one or more logical interfaces (LIFs) are configured to use a failover policy that implies failover to one or more ports but have no failover targets beyond their home ports. If any affected home port or home node is offline or unavailable, the corresponding LIFs will be operationally down and unable to serve data. Action: Add additional ports to the broadcast domains or failover groups used by the affected LIFs, or modify each LIF's failover policy to include one or more nodes with available failover targets. For example, the “broadcast-domain-wide” failover policy will consider all failover targets in a LIF's failover group. Use the “network interface show -failover” command to review the currently assigned failover targets for each LIF. Source: vifmgr Index: 6740328 [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."] This intercluster LIF is part of an IFGRP which is made up of two vlanned ports, so by definition is redundant. My question, is this a bug in the error reporting or is there some configuration which is not supported here? We have another cluster which is configured with standard vlanned ports per node as opposed to ifgrps and this doesn’t seem to complain. Just not sure if this is a problem or not, or if it’s something we can suppress? Running FAS8040, 9.1P2. Thanks Dan

5 5

7MTT CIFS Question
by Chris Hague 20 Apr '17

20 Apr '17

Hi all, I am soon to be transitioning a large CIFS share (5tb) from 7-Mode to CDOT and during the migration I would like to use the opportunity to split the share into several more manageable volumes. My initial thoughts were to use robocopy, but there are potentially permissions issues. Another method I'm exploring is to use 7MTT to mirror the volume, then once complete, create flexclones, 1 for each of the shares I would like to split out. Then delete the no longer required data from each respective share and vol split before deleting the master. Firstly, am I missing some simpler way of doing this? systemshell maybe? Secondly, if not, then is there a quicker way of deleting 20m files from each of my 6 shares? Maybe an on-filer way of destroying the folders? So far using command line tools (del, rmdir) still take far too long. Many Thanks in advance, Chris.

8 16

cluster mode volume stats since boot
by Mike Thompson 18 Apr '17

18 Apr '17

any way to get volume stats (reads/writes/ops/etc) since system boot or volume move, in cdot 8.2 and above? I used to track all that stuff in a database in the early 8.x days, via 'statistics show -object volume', but that disappeared in 8.2 (or maybe it was 8.1, not sure) looks like you can only display real time volume stats in more recent ontap releases via cli. I used to collect this info hourly, stuff it in a db, and then diff it over time to display activity per-volume, which would tell us if a volume was busy or not, and what type of traffic it was getting, over time. that info is sorely missed from some of our applications, and hence I'm looking for per-volume accumulators. looks like i can get nfs/cifs ops per qtree still, but what i really want is reads and writes (and anything else) per volume. same numbers for aggregates would be useful as well. any ideas?

3 3

Re: Switching to ACP inband connectivity
by tmac 14 Apr '17

14 Apr '17

Yep. internal burt, but a burt none the less. save them from digging it up. Let us know how you make out. I was under a crunch putting a system into production and could not fool around with it any more. Thanks --tmac *Tim McCarthy, **Principal Consultant* *Proud Member of the #NetAppATeam <https://twitter.com/NetAppATeam>* *I Blog at TMACsRack <https://tmacsrack.wordpress.com/>* On Sat, Apr 8, 2017 at 12:29 PM, Alexander Griesser <AGriesser(a)anexia-it.com > wrote: > Alright, thanks – I’m opening a case now, cannot see the details of the > BURT, though, but will refer support to it. > > > > Best, > > > > *Alexander Griesser* > > Head of Systems Operations > > > > ANEXIA Internetdienstleistungs GmbH > > > > E-Mail: AGriesser(a)anexia-it.com > > Web: 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] > *Gesendet:* Samstag, 8. April 2017 14:05 > *An:* Alexander Griesser <AGriesser(a)anexia-it.com> > *Cc:* toasters(a)teaparty.net > *Betreff:* Re: Switching to ACP inband connectivity > > > > I have seen this! Support was unable to reproduce for me. I will dig up a > case number later if you like. > > > > I will give you two options: > > 1. Open a support case with netapp and refer to the BURT 1050364 / Case > 2006580487 > > 2. The ultimate fix that I did was this: > > -> Downgrade *all* IOM firmware to 2.09. Wait for it to stabilize. > > -> Convert to in-band. Wait for it to stabilize and confirm IN-Band > > -> Convert to out-of-band and upgrade to 2.10 firmware. > > -> Wait for it to stabilize and then convert to out-of-band > > > > I got to believe there may be some race condition where the 2.08 -> 2.10 > firmware is not completing 100%. > > If you use the out-of-band, all looks ok, but switch to in-band and not so > much. > > > > The thought is something special happens on 2.09 that fixes everything > allowing the upgrade to 2.10 > > > > If possible, please open a case and refer to the data above. I think it is > in everyones best interest NetApp gets to the bottom of this to fix. > > > > Thanks > > > > > --tmac > > > > *Tim McCarthy, **Principal Consultant* > > *Proud Member of the #NetAppATeam <https://twitter.com/NetAppATeam>* > > *I Blog at **TMACsRack <https://tmacsrack.wordpress.com/>* > > > > > > On Sat, Apr 8, 2017 at 5:55 AM, Alexander Griesser < > AGriesser(a)anexia-it.com> wrote: > > Hey Toasters, > > > > I’ve just upgraded one of my HA-pairs to 9.1P2 and wanted to switch to ACP > inband connectivity following this KB: > > https://kb.netapp.com/support/s/article/ka31A00000012NsQAI/ > in-band-acp-setup-and-support > > > > According to this KB, I should be eligible for the switch: > > > > ::*> storage shelf acp module show -fields module-name,protocol-version, > firmware-version,shelf-serial-number,iom-type,state > > node module-name protocol-version firmware-version shelf-serial-number > iom-type state > > ------- ----------- ---------------- ---------------- ------------------- > -------- ------ > > nodeA 1.22.B 1.2.02.10 02.10 SHJMS1424000060 > iom6 active > > nodeA 1.22.A 1.2.02.10 02.10 SHJMS1424000060 > iom6 active > > nodeA 2.11.A 1.2.02.10 02.10 SHFMS1423000507 > iom6 active > > nodeA 2.11.B 1.2.02.10 02.10 SHFMS1423000507 > iom6 active > > nodeA 2.14.B 1.2.02.10 02.10 SHFMS1423000491 > iom6 active > > nodeA 2.14.A 1.2.02.10 02.10 SHFMS1423000491 > iom6 active > > nodeA 2.12.A 1.2.02.10 02.10 SHFMS1423000493 > iom6 active > > nodeA 2.12.B 1.2.02.10 02.10 SHFMS1423000493 > iom6 active > > nodeA 2.13.A 1.2.02.10 02.10 SHFMS1423000504 > iom6 active > > nodeA 2.13.B 1.2.02.10 02.10 SHFMS1423000504 > iom6 active > > nodeA 1.21.B 1.2.02.10 02.10 SHJMS1424000434 > iom6 active > > nodeA 1.21.A 1.2.02.10 02.10 SHJMS1424000434 > iom6 active > > nodeB > > 1.22.B 1.2.02.10 02.10 SHJMS1424000060 > iom6 active > > nodeB > > 1.22.A 1.2.02.10 02.10 SHJMS1424000060 > iom6 active > > nodeB > > 2.11.A 1.2.02.10 02.10 SHFMS1423000507 > iom6 active > > nodeB > > 2.11.B 1.2.02.10 02.10 SHFMS1423000507 > iom6 active > > nodeB > > 2.14.B 1.2.02.10 02.10 SHFMS1423000491 > iom6 active > > nodeB > > 2.14.A 1.2.02.10 02.10 SHFMS1423000491 > iom6 active > > nodeB > > 2.12.A 1.2.02.10 02.10 SHFMS1423000493 > iom6 active > > nodeB > > 2.12.B 1.2.02.10 02.10 SHFMS1423000493 > iom6 active > > nodeB > > 2.13.A 1.2.02.10 02.10 SHFMS1423000504 > iom6 active > > nodeB > > 2.13.B 1.2.02.10 02.10 SHFMS1423000504 > iom6 active > > nodeB > > 1.21.B 1.2.02.10 02.10 SHJMS1424000434 > iom6 active > > nodeB > > 1.21.A 1.2.02.10 02.10 SHJMS1424000434 > iom6 active > > 24 entries were displayed. > > > > > > The requirements state that the IOM6 modules must be upgraded to 2.09 (I > have 2.10) and ACP firmware must be at least 1.2.2.9 (I have 1.2.2.10). > > So I went ahead and ran this command: > > > > storage shelf acp configure -is-enabled true -channel *in-band* > > > > After a few minutes, I saw this: > > > > ::*> storage shelf acp show > > Node Channel Connectivity > > ------------------ --------------- ---------------------- > > nodeA in-band active > > nodeB in-band active > > 2 entries were displayed. > > > > But when I ran the initial check command again, I saw this output: > > > > ::*> storage shelf acp module show -fields module-name,protocol-version, > firmware-version,shelf-serial-number,iom-type,state > > node module-name protocol-version firmware-version shelf-serial-number > iom-type state > > ------- ----------- ---------------- ---------------- ------------------- > -------- ------------------------ > > nodeA 1.22.B 1.2.02.10 02.10 SHJMS1424000060 > iom6 firmware-update-required > > nodeA 1.22.A 1.2.02.10 02.10 SHJMS1424000060 > iom6 firmware-update-required > > nodeA 2.11.A 1.2.02.10 02.10 SHFMS1423000507 > iom6 firmware-update-required > > nodeA 2.11.B 1.2.02.10 02.10 SHFMS1423000507 > iom6 firmware-update-required > > nodeA 2.14.B 1.2.02.10 02.10 SHFMS1423000491 > iom6 firmware-update-required > > nodeA 2.14.A 1.2.02.10 02.10 SHFMS1423000491 > iom6 firmware-update-required > > nodeA 2.12.A 1.2.02.10 02.10 SHFMS1423000493 > iom6 firmware-update-required > > nodeA 2.12.B 1.2.02.10 02.10 SHFMS1423000493 > iom6 firmware-update-required > > nodeA 2.13.A 1.2.02.10 02.10 SHFMS1423000504 > iom6 firmware-update-required > > nodeA 2.13.B 1.2.02.10 02.10 SHFMS1423000504 > iom6 firmware-update-required > > nodeA 1.21.B 1.2.02.10 02.10 SHJMS1424000434 > iom6 firmware-update-required > > nodeA 1.21.A 1.2.02.10 02.10 SHJMS1424000434 > iom6 firmware-update-required > > nodeB > > 1.22.B 1.2.02.10 02.10 SHJMS1424000060 > iom6 firmware-update-required > > nodeB > > 1.22.A 1.2.02.10 02.10 SHJMS1424000060 > iom6 firmware-update-required > > nodeB > > 2.11.A 1.2.02.10 02.10 SHFMS1423000507 > iom6 firmware-update-required > > nodeB > > 2.11.B 1.2.02.10 02.10 SHFMS1423000507 > iom6 firmware-update-required > > nodeB > > 2.14.B 1.2.02.10 02.10 SHFMS1423000491 > iom6 firmware-update-required > > nodeB > > 2.14.A 1.2.02.10 02.10 SHFMS1423000491 > iom6 firmware-update-required > > nodeB > > 2.12.A 1.2.02.10 02.10 SHFMS1423000493 > iom6 firmware-update-required > > nodeB > > 2.12.B 1.2.02.10 02.10 SHFMS1423000493 > iom6 firmware-update-required > > nodeB > > 2.13.A 1.2.02.10 02.10 SHFMS1423000504 > iom6 firmware-update-required > > nodeB > > 2.13.B 1.2.02.10 02.10 SHFMS1423000504 > iom6 firmware-update-required > > nodeB > > 1.21.B 1.2.02.10 02.10 SHJMS1424000434 > iom6 firmware-update-required > > nodeB > > 1.21.A 1.2.02.10 02.10 SHJMS1424000434 > iom6 firmware-update-required > > 24 entries were displayed. > > > > Out of curiosity, I tried to run the ACP update again: > > > > nodeB> storage download acp > > > > Downloading ACP firmware can take several minutes > > and will not disrupt client access during that time. > > However, normal ACP recovery capabilities will not be > > available while the firmware upgrade is in progress. > > > > Are you sure you want to continue with ACP processor firmware update? y > > [storage download acp] Firmware will not be downloaded to module 2b.14.B > as ACPP state is not active, Current ACPP state is 0x9. > > [storage download acp] Firmware will not be downloaded to module 0a.14.A > as ACPP state is not active, Current ACPP state is 0x9. > > [storage download acp] Firmware will not be downloaded to module 0b.21.B > as ACPP state is not active, Current ACPP state is 0x9. > > [storage download acp] Firmware will not be downloaded to module 0a.13.A > as ACPP state is not active, Current ACPP state is 0x9. > > [storage download acp] Firmware will not be downloaded to module 0a.12.A > as ACPP state is not active, Current ACPP state is 0x9. > > [storage download acp] Firmware will not be downloaded to module 2a.21.A > as ACPP state is not active, Current ACPP state is 0x9. > > [storage download acp] Firmware will not be downloaded to module 2b.12.B > as ACPP state is not active, Current ACPP state is 0x9. > > [storage download acp] Firmware will not be downloaded to module 2b.13.B > as ACPP state is not active, Current ACPP state is 0x9. > > [storage download acp] Firmware will not be downloaded to module 0b.22.B > as ACPP state is not active, Current ACPP state is 0x9. > > [storage download acp] Firmware will not be downloaded to module 2a.22.A > as ACPP state is not active, Current ACPP state is 0x9. > > [storage download acp] Firmware will not be downloaded to module 0a.11.A > as ACPP state is not active, Current ACPP state is 0x9. > > [storage download acp] Firmware will not be downloaded to module 2b.11.B > as ACPP state is not active, Current ACPP state is 0x9. > > nodeB> exit > > > > Eventlog also said, that a FW Upgrade is required: > > > > ::*> event log show -severity infORMATIONAL > > Time Node Severity Event > > ------------------- ---------------- ------------- > --------------------------- > > 4/8/2017 11:41:15 nodeB INFORMATIONAL sfu.firmwareUpToDate: > Firmware is up-to-date on all disk shelves. > > 4/8/2017 11:39:37 nodeA INFORMATIONAL acp.need.firmware.update: > ACP module (NA) needs a firmware upgrade, (disk shelf serial number: > SHFMS1423000507). > > 4/8/2017 11:39:37 nodeA INFORMATIONAL acp.need.firmware.update: > ACP module (NA) needs a firmware upgrade, (disk shelf serial number: > SHFMS1423000504). > > 4/8/2017 11:39:37 nodeA INFORMATIONAL acp.need.firmware.update: > ACP module (NA) needs a firmware upgrade, (disk shelf serial number: > SHFMS1423000491). > > 4/8/2017 11:39:37 nodeA INFORMATIONAL acp.need.firmware.update: > ACP module (NA) needs a firmware upgrade, (disk shelf serial number: > SHFMS1423000493). > > 4/8/2017 11:39:37 nodeA INFORMATIONAL acp.need.firmware.update: > ACP module (NA) needs a firmware upgrade, (disk shelf serial number: > SHJMS1424000060). > > 4/8/2017 11:39:37 nodeA INFORMATIONAL acp.need.firmware.update: > ACP module (NA) needs a firmware upgrade, (disk shelf serial number: > SHJMS1424000434). > > 4/8/2017 11:39:37 nodeB INFORMATIONAL acp.need.firmware.update: > ACP module (NA) needs a firmware upgrade, (disk shelf serial number: > SHFMS1423000493). > > 4/8/2017 11:39:37 nodeB INFORMATIONAL acp.need.firmware.update: > ACP module (NA) needs a firmware upgrade, (disk shelf serial number: > SHFMS1423000504). > > 4/8/2017 11:39:37 nodeB INFORMATIONAL acp.need.firmware.update: > ACP module (NA) needs a firmware upgrade, (disk shelf serial number: > SHFMS1423000507). > > 4/8/2017 11:39:37 nodeB INFORMATIONAL acp.need.firmware.update: > ACP module (NA) needs a firmware upgrade, (disk shelf serial number: > SHFMS1423000491). > > 4/8/2017 11:39:37 nodeB INFORMATIONAL acp.need.firmware.update: > ACP module (NA) needs a firmware upgrade, (disk shelf serial number: > SHJMS1424000434). > > 4/8/2017 11:39:37 nodeB INFORMATIONAL acp.need.firmware.update: > ACP module (NA) needs a firmware upgrade, (disk shelf serial number: > SHJMS1424000060). > > > > I then switched back to OOB connectivity, and all is good again: > > > > ::*> storage shelf acp show > > Node Channel Connectivity > > ------------------ --------------- ---------------------- > > nodeA out-of-band full-connectivity > > nodeB out-of-band full-connectivity > > 2 entries were displayed. > > > > Tried to run the ACP upgrade again, getting this: > > > > nodeB> storage download acp > > > > Downloading ACP firmware can take several minutes > > and will not disrupt client access during that time. > > However, normal ACP recovery capabilities will not be > > available while the firmware upgrade is in progress. > > > > Are you sure you want to continue with ACP processor firmware update? y > > [storage download acp] ACP will check 12 modules for firmware download. > > [storage download acp] ACP module 192.168.0.124 is not eligible for update. > > [storage download acp] ACP module 192.168.0.126 is not eligible for update. > > [storage download acp] ACP module 192.168.0.180 is not eligible for update. > > [storage download acp] ACP module 192.168.0.202 is not eligible for update. > > [storage download acp] ACP module 192.168.0.208 is not eligible for update. > > [storage download acp] ACP module 192.168.0.248 is not eligible for update. > > [storage download acp] ACP module 192.168.1.112 is not eligible for update. > > [storage download acp] ACP module 192.168.1.170 is not eligible for update. > > [storage download acp] ACP module 192.168.1.238 is not eligible for update. > > [storage download acp] ACP module 192.168.2.66 is not eligible for update. > > [storage download acp] ACP module 192.168.3.130 is not eligible for update. > > [storage download acp] ACP module 192.168.3.138 is not eligible for update. > > nodeB> exit > > > > And now I’m back at the starting point. > > Any ideas what’s going on here? Why does it tell me > „firmware-update-required“ when I’m already on the latest versions? > > > > Thanks, > > > > *Alexander Griesser* > > Head of Systems Operations > > > > ANEXIA Internetdienstleistungs GmbH > > > > E-Mail: AGriesser(a)anexia-it.com > > Web: 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 > http://www.teaparty.net/mailman/listinfo/toasters > > >

2 6

Subselect-ish behavior?
by Ehrenwald, Ian 13 Apr '17

13 Apr '17

Conceptually this is what I’d like to do: volume show-footprint -fields total-footprint { volume show -clone-volume true -fields volume } Eg, show the total on disk footprint of all FlexClones. I could have sworn I saw a very brief example of this on Justin Parisi’s blog, taking the output of one command and feeding it into another. At the time, I thought “oh that’s cool” and moved on, but now can’t find reference to it. Either I don’t remember the syntax, it isn’t supported in 8.3.2, or it never happened and I’m slowly going crazy? -- 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.

4 7

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