Hi DanielVery good point. I have done a bit more digging and find this article on the NOW site:https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb13968 So it does indeed look like that this autosupport.support.transport setting only applies to mail for netapp and that addresses in your autosupport.to should indeed always be sent via smtp. I think this must have changed sometime around 7.0.Looking at the error you see, Autosupport cannot connect to host rtpmail01.americas.ppdi.local (Network comm problem) for message: USER_TRIGGERED (TEST) it does sound like some device is blocking a connection between the filer and exchange server.At this stage I would make a packet trace on the filer as follows:pktt start all -d / -i rtpmail01.americas.ppdi.localoptions autosupport.doit TESTWait for the error message thenpktt stop allI don't know how well you know TCP; If you send me the trace I would be happy to look at it; what you will be interested in seeing isa) whether any attempt at all is made to connect to the exchange serverb) if so is it to port 80 (http), port 443 (https) or smtp (25)c) If you see a bunch of SYN's with no replies or a reply of a RST ACK then there is most likely a firewall blocking the path.SMTP is plain text so if there is a SMTP connection which goes wrong somewhere you are quite likely to see an error telling you what's wrong which you could then share with your Exchange admin.Hope this helps -- let us know your findings,cheers,KennethSubject: RE: Autosupport failing to mailhostDate: Tue, 12 Feb 2008 13:07:52 -0600From: daniel.keisling@austin.ppdi.comTo: kheal@hotmail.com; toasters@mathworks.com
Does the autosupport.support.transport option only use smtp or https when delivering to NetApp? In this case (https), it works fine. NetApp is receiving my autosupports.
What's not working is local mail to me. I tried this on another filer at another site (except for the mailhost (another Exchange 2003 server), all the autosupport settings are the same) and the email to my local account came immediately, as well as a notification from NetApp. The log even said:
Feb 12 14:11:57 EST [wilstore2a: asup.smtp.sent:notice]: Cluster Notification mail sent: Cluster Notification from wilstore2a (USER_TRIGGERED (testing_from_wilstore)) INFO
This was definitely sent via smtp, yet the autosupport.support.transport is set to https. Daniel
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Kenneth HealSent: Tuesday, February 12, 2008 12:33 PMTo: Daniel Keisling; toasters@mathworks.comSubject: RE: Autosupport failing to mailhost
Hi DanielI see a line which saysautosupport.support.transport httpsWhich means the filer will use https to send autosupports, and not smtp.Can you tryoptions autosupport.support.transport smtpAnd see if the mails go through?cheersKennethKenneth HealDatabasement BVThe Netherlands
Subject: Autosupport failing to mailhostDate: Tue, 12 Feb 2008 10:22:51 -0600From: daniel.keisling@austin.ppdi.comTo: toasters@mathworks.com
Hello,
From what seems out of the blue, Autosupport emails are no longer able to be sent to my mailhost (Exchange 2003 on the same subnet):
"Autosupport cannot connect to host rtpmail01.americas.ppdi.local (Network comm problem) for message: USER_TRIGGERED (TEST)"
This message will be thrown until the message is eventually dropped. My Exchange administrator does not see any connections coming from the filer to send this email. I can ping the mailhost with no problem:
rtpstore2b> ping rtpmail01.americas.ppdi.localrtpmail01.americas.ppdi.local is alive My routing table:
Destination Gateway Flags Refs Use Interfacedefault 172.20.63.254 UGS 4 222239 e0a127 localhost UGS 0 22236 lolocalhost localhost UH 3 145 lo172.20.62/23 link#4 UC 0 0 e0artpmail01.americ 0:8:2:28:ee:86 UHL 0 11 e0artpexchbe01.amer 0:8:2:28:ee:86 UHL 0 0 e0artpstore2b 0:a0:98:9:66:53 UHL 0 18112 lo My autosupport options:
rtpstore2b> options autosupportautosupport.cifs.verbose offautosupport.content completeautosupport.doit DONTautosupport.enable onautosupport.from rtpstore2b at rtp.ppdi.comautosupport.local.nht_data.enable offautosupport.local.performance_data.enable offautosupport.mailhost rtpmail01.americas.ppdi.localautosupport.minimal.subject.id hostnameautosupport.nht_data.enable onautosupport.notetoautosupport.performance_data.enable onautosupport.retry.count 15 (value might be overwritten in takeover)autosupport.retry.interval 4m (value might be overwritten in takeover)autosupport.support.enable onautosupport.support.proxyautosupport.support.to autosupport at netapp.comautosupport.support.transport httpsautosupport.support.url support.netapp.com/asupprod/post/1.0/postAsupautosupport.throttle onautosupport.to storage at wilm.ppdi.com (I've replaced the @'s with 'at')
I have no problems with my SSH session, so I don't know how this could be a network cable/connection problem. Are there any debugging steps I can do? Has anyone seen this before? It has definitely worked in the past. This is DOT 7.2.2 on a FAS3040.
TIA,
Daniel
______________________________________________________________________This email transmission and any documents, files or previous emailmessages attached to it may contain information that is confidential orlegally privileged. If you are not the intended recipient or a personresponsible for delivering this transmission to the intended recipient,you are hereby notified that you must not read this transmission andthat any disclosure, copying, printing, distribution or use of thistransmission is strictly prohibited. If you have received this transmissionin error, please immediately notify the sender by telephone or return emailand delete the original transmission and its attachments without readingor saving in any manner.
Express yourself instantly with MSN Messenger! MSN Messenger ______________________________________________________________________ This email transmission and any documents, files or previous email messages attached to it may contain information that is confidential or legally privileged. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution or use of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify the sender by telephone or return email and delete the original transmission and its attachments without reading or saving in any manner.
_________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/