[{"data":1,"prerenderedAt":122},["ShallowReactive",2],{"post:\u002F2013\u002F01\u002F14\u002Fcheck-for-queued-autosupports\u002F":3},{"post":4,"newer":63,"older":75,"related":85,"series":120},{"id":5,"title":6,"body":7,"canonical":43,"categories":44,"date":46,"description":19,"extension":47,"featured":48,"hero":49,"image":49,"meta":50,"navigation":51,"path":52,"readingTime":53,"seo":54,"series":49,"seriesOrder":49,"sites":55,"source":57,"stem":58,"tags":59,"updated":60,"url":61,"__hash__":62},"blog\u002Fblog\u002F2013\u002F01\u002F14\u002Fcheck-for-queued-autosupports.md","Check for queued autosupports",{"type":8,"value":9,"toc":40},"minimark",[10,14,17,20,31,34],[11,12,13],"p",{},"I’ve always wondered where the autosupports were held on the NetApp, specifically to see if my autosupports are being processed on new client sites. I’m not sure about other releases, but on 8.x releases (they’re most likely in the same location), they’re stored here:",[11,15,16],{},"\\\\{netapp}\\etc$\\log\\autosupport",[11,18,19],{},"NetApp has released some commands in the 8.1.x code line release to check autosupport information.",[21,22,27],"pre",{"className":23,"code":25,"language":26},[24],"language-text","netapp> autosupport\nautosupport destinations\nautosupport history\nautosupport manifest\nautosupport trigger\n","text",[28,29,25],"code",{"__ignoreMap":30},"",[11,32,33],{},"You will get some outputs like this:",[21,35,38],{"className":36,"code":37,"language":26},[24],"netapp> autosupport history show\nSeq                                    Attempt Last\nNum   Destination Status               Count   Update\n----- ----------- -------------------- ------- --------------------\n66\n      smtp        ignore               1       2\u002F6\u002F2013 09:35:46\n      http        sent-successful      1       2\u002F6\u002F2013 09:35:49\n      noteto      ignore               1       2\u002F6\u002F2013 09:35:46\n65\n      smtp        collection-failed    -       2\u002F6\u002F2013 09:34:51\n      http        collection-failed    -       2\u002F6\u002F2013 09:34:51\n      noteto      collection-failed    -       2\u002F6\u002F2013 09:34:51\n",[28,39,37],{"__ignoreMap":30},{"title":30,"searchDepth":41,"depth":41,"links":42},2,[],"techcolumnist",[45],"engineering","2013-01-14T18:34:57Z","md",false,null,{},true,"\u002Fblog\u002F2013\u002F01\u002F14\u002Fcheck-for-queued-autosupports",1,{"title":6,"description":19},[56,43],"lasswell","both","blog\u002F2013\u002F01\u002F14\u002Fcheck-for-queued-autosupports",[],"2024-02-12T03:22:12Z","\u002F2013\u002F01\u002F14\u002Fcheck-for-queued-autosupports\u002F","1Szvl1tx9iGmdQxsaGGxuE-yqW1ghy_U2yxaNmVnGao",{"title":64,"description":65,"date":66,"url":67,"categories":68,"tags":69,"image":49,"readingTime":53,"canonical":43,"sites":74,"series":49,"seriesOrder":49},"SnapManager for Exchange: Backup Tasks","Notes on SnapManager for Exchange backup tasks, and why the task-creation wizard is so frustrating.","2013-02-06T14:40:34Z","\u002F2013\u002F02\u002F06\u002Fsnapmanager-for-exchange-backup-tasks\u002F",[45],[70,71,72,73],"backup","netapp","sme","tasks",[56,43],{"title":76,"description":77,"date":78,"url":79,"categories":80,"tags":81,"image":49,"readingTime":53,"canonical":43,"sites":84,"series":49,"seriesOrder":49},"VMware 5.x, set drives to SSD","Quick post, sometimes VMware doesn’t detect that you have SSD locally and you you need to force it to enable SSD.","2012-11-01T14:48:24Z","\u002F2012\u002F11\u002F01\u002Fvmware-5-x-set-drives-to-ssd\u002F",[45],[82,83],"ssd","vmware",[56,43],[86,99,109],{"title":87,"description":88,"date":89,"url":90,"categories":91,"tags":93,"image":49,"readingTime":97,"canonical":43,"sites":98,"series":49,"seriesOrder":49},"Hyper-V to Talos: Rethinking the Virtualization Stack","Why moving workloads off Hyper-V VMs onto a Talos Kubernetes cluster changed the whole stack, with an inventory script and a VM-to-manifest example.","2026-09-16T14:00:00Z","\u002F2026\u002F09\u002F16\u002Fhyper-v-to-talos-rethinking-the-virtualization-stack\u002F",[45,92],"strategy",[94,95,96],"hyper-v","talos","kubernetes",5,[43],{"title":100,"description":101,"date":102,"url":103,"categories":104,"tags":105,"image":49,"readingTime":107,"canonical":43,"sites":108,"series":49,"seriesOrder":49},"Google Cloud: IAM Least Privilege in Practice, Not Just in Theory","Running least privilege in a real Google Cloud org: finding basic roles, working the IAM recommender, custom roles, temporary access, and service account risk.","2026-09-09T14:00:00Z","\u002F2026\u002F09\u002F09\u002Fgoogle-cloud-iam-least-privilege-in-practice-not-just-in-theory\u002F",[45],[106],"gcloud",6,[43],{"title":110,"description":111,"date":112,"url":113,"categories":114,"tags":115,"image":49,"readingTime":97,"canonical":43,"sites":119,"series":49,"seriesOrder":49},"Windows Management: A Discovery Inventory Nobody Maintains by Hand","Why a self-refreshing Windows inventory built from AD and CIM discovery outlasts a spreadsheet, with the sweep script, staleness report and schedule.","2026-09-02T14:00:00Z","\u002F2026\u002F09\u002F02\u002Fwindows-management-building-a-discovery-inventory-nobody-has-to-maintain-by-hand\u002F",[45,92],[116,117,118],"discovery","windows","active-directory",[43],{"doc":49,"posts":121},[],1790223956075]