X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C76057.425F010A@onstor-exch02.onstor.net>; Tue, 6 Mar 2007 18:23:49 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: autosupport server needs an ip address
Date: Tue, 6 Mar 2007 18:23:49 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02B74EAD@onstor-exch02.onstor.net>
In-Reply-To: <030201c76052$07d45850$0300a8c0@lab.css.glasshouse.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: autosupport server needs an ip address
Thread-Index: AcdgUgc1vuOVpBAiQ2yYRbr3nhzR4gABFWLQ
From: "Eric Barrett" <eric.barrett@onstor.com>
To: "Fred McFadden (Glasshouse)" <fredm@css.glasshouse.com>,
	"dl-cstech" <dl-cstech@onstor.com>

Fred,

This should be an RFE.  (Why didn't we code the command to take a domain
name in the first place...?)

As a hack, he can do this:

1) Run: "dig mx mse3.exchange.ms" [note the 'mx']. Verify that the dig
returned sane MX records for mse3.exchange.ms.

2) If not, try: "dig mx exchange.ms" and verify the records are sane.

3) Set the domain of the SSC to the one in either step (1) or (2),
depending on which worked:
    vsv clear
    system dnsconfigure resolver
       [ add at the beginning the line: "domain exchange.ms" or "domain
mse3.exchange.ms" ]

4) On the ONStor, run: autosupport email server 0.0.0.0

If the domain has no MX records, then this hack won't work.

The reason it should work is that autosupport's default behavior when no
email server is defined is to connect to the mail server defined in the
MX record(s) of the domain to which the system belongs.
=20

-----Original Message-----
From: Fred McFadden (Glasshouse)=20
Sent: Tuesday, March 06, 2007 4:46 PM
To: dl-cstech
Subject: autosupport server needs an ip address

Dave Johnson Strategic Discovery case 4667

He has a smpt server that changes from time to time during maintenance
so
autosupport will not function consistently.=20

I don't see a workaround for him, this is an RFE.=20

Other than inform Dave we have to make this an RFE, any ideas? Thks
-Fred

---------------- Comment: ---------------- The autosupport feature does
not
support dns resolution for SMTP server.  We do not have our own SMTP
server
and our email provider changes the IP continually as their Windows
Exchange
servers go into and out of maintenance.

filer1 F1 diag> autosupport email server mail.mse3.exchange.ms Mail
server
IP address mail.mse3.exchange.ms is invalid. Should be X.X.X.X format.
% Command failure.
filer1 F1 diag> exit
filer1# dig mail.mse3.exchange.ms

; <<>> DiG 2.2 <<>> mail.mse3.exchange.ms ;; res options: init recurs
defnam
dnsrch ;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47814 ;; flags: qr
rd
ra; Ques: 1, Ans: 2, Auth: 0, Addit: 0 ;; QUESTIONS:
;;      mail.mse3.exchange.ms, type =3D A, class =3D IN

;; ANSWERS:
mail.mse3.exchange.ms.  839     A       69.25.50.165
mail.mse3.exchange.ms.  839     A       69.25.50.167

;; Total query time: 10 msec
;; FROM: filer1 to SERVER: default -- 10.192.1.150 ;; WHEN: Tue Mar  6
14:22:14 2007 ;; MSG SIZE  sent: 39  rcvd: 71

filer1#

If I add 69.25.50.165 for instance, it will stop working whenever the
server
is taken offline for maintenance.  Maintenance is usually a day or less
but
if they occur during an alert, we would never get it.

How can we get this to work consistently?

-=3Ddave


