Solved: How to check that autosupport collection has completed?

aborzenkov · ‎2013-02-07

Fri Feb 8 09:36:46 MSK [sapdr:cf.misc.operatorGiveback:info]: Failover monitor: giveback initiated by operator

Fri Feb 8 09:36:46 MSK [sapdr:asup.general.cfoveto.nopart:notice]: AutoSupport vetoed giveback because an AutoSupport message for the down partner node was not yet collected.

Fri Feb 8 09:36:46 MSK [sapdr:cf.rsrc.givebackVeto:error]: Failover monitor: autosupport: giveback cancelled due to active state

So - how can I check that autosupport has completed? I do not like blindly typing "cf giveback" over and over again.

ASHWINPAWARTESL · ‎2013-02-08

you can check the status....

toaster>autosupport history show

Seq                                    Attempt Last
Num   Destination Status               Count   Update
----- ----------- -------------------- ------- --------------------
287
      smtp        ignore               1       2/8/2013 10:01:22
      http        queued               -       2/8/2013 09:45:37
      noteto      ignore               1       2/8/2013 10:01:22
          ...............

To check the current status of log collection, run this command:

toaster> autosupport manifest show -seq-num 287

          AutoSupport    Collected
Sequence Body Filename Size        Status    Error
--------- -------------- ----------- --------- -----------
287
          SYSCONFIG-A.txt     1.76KB completed
          OPTIONS.txt        21.65KB completed
          software_image.xml 7.58KB completed
          NFSSTAT-D.txt            - working
          LUN-HIST.txt             - working
          ACP-STATS.txt            - requested
          STORAGE-SHELF.txt        - requested
          STORAGE-TAPE.txt         - requested

...........................................

if you do - man autosupport, it has quite a lot information.

View solution in original post

ASHWINPAWARTESL · ‎2013-02-08

I found a kb on this issue.

AutoSupport capability to veto givebacks
https://kb.netapp.com/support/index?page=content&id=2015986

Workaround:

Allow the AutoSupport veto timer to elapse.

-OR-

Disable, and then re-enable AutoSupport on the (takeover) node. For example:

Filer (takeover)> options autosupport.enable off
Filer (takeover)> cf giveback
Filer (takeover)> options autosupport.enable on

ASHWINPAWARTESL · ‎2013-02-08

you can check the status....

toaster>autosupport history show

Seq                                    Attempt Last
Num   Destination Status               Count   Update
----- ----------- -------------------- ------- --------------------
287
      smtp        ignore               1       2/8/2013 10:01:22
      http        queued               -       2/8/2013 09:45:37
      noteto      ignore               1       2/8/2013 10:01:22
          ...............

To check the current status of log collection, run this command:

toaster> autosupport manifest show -seq-num 287

          AutoSupport    Collected
Sequence Body Filename Size        Status    Error
--------- -------------- ----------- --------- -----------
287
          SYSCONFIG-A.txt     1.76KB completed
          OPTIONS.txt        21.65KB completed
          software_image.xml 7.58KB completed
          NFSSTAT-D.txt            - working
          LUN-HIST.txt             - working
          ACP-STATS.txt            - requested
          STORAGE-SHELF.txt        - requested
          STORAGE-TAPE.txt         - requested

...........................................

if you do - man autosupport, it has quite a lot information.

aborzenkov · ‎2013-02-11

Thank you!