i thought this only set the delivery method directly to netapp? i have autosupport.support.transport https set but i also have mailhost, to/from set and i get all the normal autosupport mails in addition to the https post sent directly to netapp.
--
Daniel Leeds
Manager, Storage Operations
Edmunds, Inc.
1620 26th Street, Suite 400 South
Santa Monica, CA 90404
310-309-4999 desk
310-430-0536 cell
-----Original Message-----
From: owner-toasters@mathworks.com on behalf of Geissler, Norbert
Sent: Tue 2/12/2008 10:05 AM
To: Daniel Keisling; toasters@mathworks.com
Subject: AW: Autosupport failing to mailhost
Hi,
does Exchange 2003 support https connection ?
autosupport.support.transport https
if not, try changing to
option autosupport.support.transport smtp
Good luck,
Norbert Geissler
Siemens AG
Siemens IT Solutions and Services
Global Operations
SIS GO GIO DS G SU1
Otto-Hahn-Ring 6
81739 München
Tel.: +49 (89) 636-48132
Fax: +49 (89) 636-28889
Mobil: +49 (170) 9157829
mailto:norbert.geissler@siemens.com <mailto:norbert.geissler@siemens.com>
Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard Cromme; Vorstand: Peter Löscher, Vorsitzender; Wolfgang Dehen, Heinrich Hiesinger, Joe Kaeser, Erich R. Reinhardt, Hermann Requardt, Siegfried Russwurm, Peter Y. Solmssen; Sitz der Gesellschaft: Berlin und München; Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322
________________________________
Von: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Im Auftrag von Daniel Keisling
Gesendet: Dienstag, 12. Februar 2008 17:23
An: toasters@mathworks.com
Betreff: Autosupport failing to mailhost
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.local
rtpmail01.americas.ppdi.local is alive
My routing table:
Destination Gateway Flags Refs Use Interface
default 172.20.63.254 UGS 4 222239 e0a
127 localhost UGS 0 22236 lo
localhost localhost UH 3 145 lo
172.20.62/23 link#4 UC 0 0 e0a
rtpmail01.americ 0:8:2:28:ee:86 UHL 0 11 e0a
rtpexchbe01.amer 0:8:2:28:ee:86 UHL 0 0 e0a
rtpstore2b 0:a0:98:9:66:53 UHL 0 18112 lo
My autosupport options:
rtpstore2b> options autosupport
autosupport.cifs.verbose off
autosupport.content complete
autosupport.doit DONT
autosupport.enable on
autosupport.from rtpstore2b at rtp.ppdi.com <mailto:rtpstore2b@rtp.ppdi.com>
autosupport.local.nht_data.enable off
autosupport.local.performance_data.enable off
autosupport.mailhost rtpmail01.americas.ppdi.local
autosupport.minimal.subject.id hostname
autosupport.nht_data.enable on
autosupport.noteto
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 at netapp.com <mailto:autosupport@netapp.com>
autosupport.support.transport https
autosupport.support.url support.netapp.com/asupprod/post/1.0/postAsup
autosupport.throttle on
autosupport.to storage at wilm.ppdi.com <mailto:storage@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 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.