SHIFT

--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools


Sidebar

Sponsor:

Would you like to sponsor this site?
Or buy me a beer?:


Recently Changed Pages:

View All Pages
View All Q Pages


View All Tags


Sign up for Q to post comments.





WIKI Disclaimer: As with most other things on the Internet, the content on this wiki is not supported. It was contributed by me and is published “as is”. It has worked for me, and might work for you.
Also note that any view or statement expressed anywhere on this site are strictly mine and not the opinions or views of my employer.


Terms And Conditions for Q users


Pages with comments

PageDateDiscussionTags
2019/06/22 10:36 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 3 Comments
2017/04/20 15:28 1 Comment
2017/04/20 15:23 1 Comment
2017/04/19 14:44 1 Comment
2017/04/17 20:10 1 Comment
2017/04/17 20:07 1 Comment
2017/04/17 19:58 1 Comment
2017/04/17 19:52 1 Comment

View All Comments

netappautosupport81

NetApp AutoSupport

After our upgrade from ontap 7.3.4 to 8.1 NetApp/IBM had a little surprise for us… autosupport stopped working! Now let's get this straight. You need autosupport. If a disk fails, the filer communicates to NetApp/IBM and there you go, depending on your contract you get a new disk delivered. And that's just one of the benefits, they also check for configuration errors and if you have an issue they will always ask you to provide an autosupport. Or, as they call it, an asup ;) . So you need this, and after some checking it turned out that ontap 8.1 dropped support for smtp as transport method, and only supported https. So that meant configuring a proxy that didn't require authentication etc. I keep the configuration listed here as a reference for myself, but maybe someone else also has a use for it:

filer01> options autosupport
autosupport.cifs.verbose     off
autosupport.content          complete   (value might be overwritten in takeover)
autosupport.doit             USER_TRIGGERED (test1601)
autosupport.enable           on         (value might be overwritten in takeover)
autosupport.from             filer01_ @ _getshifting.com (value might be overwritten in takeover)
autosupport.local_collection on         (value might be overwritten in takeover)
autosupport.mailhost         172.16.100.150 (value might be overwritten in takeover)
autosupport.max_http_size    10485760   (value might be overwritten in takeover)
autosupport.max_smtp_size    5242880    (value might be overwritten in takeover)
autosupport.minimal.subject.id hostname   (value might be overwritten in takeover)
autosupport.nht_data.enable  on         (value might be overwritten in takeover)
autosupport.noteto                      (value might be overwritten in takeover)
autosupport.partner.to                  (value might be overwritten in takeover)
autosupport.payload_format   7z         (value might be overwritten in takeover)
autosupport.performance_data.doit DONT
autosupport.performance_data.enable on         (value might be overwritten in takeover)
autosupport.periodic.tx_window 1h         (value might be overwritten in takeover)
autosupport.retry.count      15         (value might be overwritten in takeover)
autosupport.retry.interval   4m         (value might be overwritten in takeover)
autosupport.support.enable   on         (value might be overwritten in takeover)
autosupport.support.proxy    172.16.150.100:80 (value might be overwritten in takeover)
autosupport.support.put_url  eccgw01.boulder.ibm.com/support/electronic/nas (value might be overwritten in takeover)
autosupport.support.to       callhome@de.ibm.com (value might be overwritten in takeover)
autosupport.support.transport https      (value might be overwritten in takeover)
autosupport.support.url      eccgw01.boulder.ibm.com/support/electronic/nas (value might be overwritten in takeover)
autosupport.throttle         on         (value might be overwritten in takeover)
autosupport.to               sjoerd_ @ _getshifting.com (value might be overwritten in takeover)
autosupport.validate_digital_certificate on         (value might be overwritten in takeover)

Note that email is still used to send an copy from the autosupport to the “autosupport.to” address and that IBM/NetApp confirms receiving your autosupport test as well to the same email address:

Test AutoSupport

Trigger an autosupport test:

filer01> options autosupport.doit test1601

After a while you'll get a confirmation from IBM (since it is an Nseries (rebranded netapp)):

This is an auto-generated email from IBM,  [Please DO NOT reply.]

SYSTEM ID : 01XXXXX703
HOSTNAME : null
HA Group Notification from filer01 (USER_TRIGGERED (test1601)) INFO IBM automatically acknowledges any AutoSupport with the word USER_TRIGGERED in the subject line.
This acknowledgement is sent to the "autosupport.to" e-mail recipient(s).

 IBM NSERIES RELEASE 2.0 TEAM

Further Troubleshooting

In a case I had once I received these commands for further troubleshooting. They will give you more information with detailed information:

autosupport history show -detail
autosupport history show
autosupport history show -delivery
You could leave a comment if you were logged in.
netappautosupport81.txt · Last modified: 2014/02/14 16:34 by sjoerd