Autosupport worked fine up until about six weeks ago, no it doesn't. We can't think of anything that changed in the environment.
We can ping the mailserver, I tried telnetting to the mailserver on port 25 to see if it is still relaying, seems to be OK. We weren't seeing any messages at all regarding autosupport in the messages file, an time we tested. We just changed the transport to smtp, from https, and we now get one message, but that's all, see below.
netapp2050a> df -h
Filesystem total used avail capacity Mounted on
/vol/rootvol/ 20GB 197MB 19GB 1% /vol/rootvol/
/vol/rootvol/.snapshot 0TB 0TB 0TB ---% /vol/rootvol/.snapshot
netapp2050a> options autosupport
autosupport.cifs.verbose off
autosupport.content complete
autosupport.doit DONT
autosupport.enable on
autosupport.from netappalert@###.com netappalert@plastipak.com
autosupport.local.nht_data.enable off
autosupport.local.performance_data.enable off
autosupport.mailhost 10.1.1.130
autosupport.minimal.subject.id hostname
autosupport.nht_data.enable on
autosupport.noteto helpdeskteam@###.com<jlalik@plastipak.com,helpdeskteam@plastipak.com>
autosupport.performance_data.enable on
autosupport.retry.count 15 (value might be overwritten in takeover)
autosupport.retry.interval 4m (value might be overwritten in takeover)
autosupport.support.enable on
autosupport.support.proxy
autosupport.support.to autosupport@netapp.com
autosupport.support.transport http
autosupport.support.url support.netapp.com/asupprod/post/1.0/postAsup
autosupport.throttle on
autosupport.to admin@###.com<lkostoff@platipak.com,bblair@plastipak.com>
From the messages file
Wed Jul 23 11:04:38 EDT [netapp2050a: asup.general.drop:error]: Out of messages for autosupport, skipping autosupport: USER_TRIGGERED (test)
The machine is running 7.2.2L1. Does anyone have any ideas?
Sláinte,
David
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life. - Terry Pratchett, Discworld