Subscribe

Re: Problem with Autosupport

Hi there, I also saw this problem when the losk interface IP address was changed from 127.0.20.1 to 127.0.20.2 in order to get VMware Site Recovery Manager working ! I've raised a call with IBM support (I'm using an Nseries) because if I fix the VMware SRM problem, autosupport and timed options break ! Incidentally, my default route is fine.

Re: Problem with Autosupport

Hi Neil,

I too have had to amend the losk interface IP on our NetApp filers to enable SRM.  As you would expect I am now getting issues with autosupport and timed options.  Did you ever get a response/resolution to your support ticket?

Cheers,

Pete

Re: Problem with Autosupport

HI Pete,

yes I got an answer to my problem, it was down to the way we had registered the filers within SRM. The full answer can be found via the following post: http://communities.netapp.com/message/50685#50685

If for some reason you can't get to it, let me know and I'll cut and paste the contents into this post.

I was pretty pleased with the result, basically you don't have to change the losk interface so autosupport doesn't get broken, you just have to add information about the NFS interface when configuring SRM (even if you aren't using it !!).

Let me know how you get on.

All the best, Neil.

Re: Problem with Autosupport

Hi Neil,

Many thanks...I had seen your other post but obviously misread it   All sorted now although the filer has developed the original problem in this post, gateway is correct so hopefully a reboot will fix it.

Once again many thanks for all your help.

Cheers,

Pete

Problem with Autosupport

All - We had the same issue, 

FAS3240 cluster

8.0.1P2

miafile0X*> Mon Aug  814:09:55 EDT [miafile0X: asup.smtp.host:info]: AutoSupport cannot connect tohost 10.10.X.X (Network is unreachable) for message: HA Group Notificationfrom miafile0X (USER_TRIGGERED (20023731)) INFO

Mon Aug  8 14:09:55 EDT[miafile0X: asup.smtp.retry:info]: AutoSupport mail (HA Group Notification frommiafile0X (USER_TRIGGERED (20023731)) INFO) was not sent for host (0). Thesystem will retry later to send the message

After working with NetApp support for 1 month the only cure was a reboot of the filer.

In spite of checking everything over the 4 weeks or so of this issue, a planned failover to the partner, then a reboot, cleared it all up.

There must have been some hidden routing issue.

Re: Problem with Autosupport

Another one problem with autosupport .

My filer can't send Autosupport "Weekly_log", but standart autosupport messages (for example: about failed disks or Performance Data) sent normally. It affected on "My Autosupport" on NetApp support Web-site. I can't see properties of my system.

In messages file i see that messages:

Sun May 20 00:12:29 UZT [netapp01: asup.general.file.create.failed:error]: AutoSupport file (/etc/log/autosupport/201205200004.0.files/201205200004.0.ems.gz) was unable to be written to the file spool subdirectory.

Sun May 20 00:12:29 UZT [netapp01: asup.general.file.create.failed:error]: AutoSupport file (/etc/log/autosupport/201205200004.0.files/201205200004.0.ems.gz) was unable to be written to the file spool subdirectory.

Sun May 20 00:12:29 UZT [netapp01: asup.general.file.create.failed:error]: AutoSupport file (/etc/log/autosupport/201205200004.0.files/201205200004.0.rc.gz) was unable to be written to the file spool subdirectory.

Sun May 20 00:12:29 UZT [netapp01: asup.general.file.create.failed:error]: AutoSupport file (/etc/log/autosupport/201205200004.0.files/201205200004.0.rc.gz) was unable to be written to the file spool subdirectory.

Sun May 20 00:12:29 UZT [netapp01: asup.general.file.create.failed:error]: AutoSupport file (/etc/log/autosupport/201205200004.0.files/201205200004.0.exports.gz) was unable to be written to the file spool subdirectory.

Sun May 20 00:12:29 UZT [netapp01: asup.general.file.create.failed:error]: AutoSupport file (/etc/log/autosupport/201205200004.0.files/201205200004.0.exports.gz) was unable to be written to the file spool subdirectory.

Sun May 20 00:12:29 UZT [netapp01: asup.general.file.create.failed:error]: AutoSupport file (/etc/log/autosupport/201205200004.0.files/201205200004.0.hosts.gz) was unable to be written to the file spool subdirectory.

Sun May 20 00:12:29 UZT [netapp01: asup.general.file.create.failed:error]: AutoSupport file (/etc/log/autosupport/201205200004.0.files/201205200004.0.hosts.gz) was unable to be written to the file spool subdirectory.

Sun May 20 00:12:29 UZT [netapp01: asup.general.file.create.failed:error]: AutoSupport file (/etc/log/autosupport/201205200004.0.files/201205200004.0.resolv_conf.gz) was unable to be written to the file spool subdirectory.

Here output of some command from filer.

netapp01> df -k /vol/vol0/

Filesystem               total       used      avail capacity  Mounted on

/vol/vol0/          277848424KB 16997756KB 260850668KB       6%  /vol/vol0/

/vol/vol0/.snapshot 69462104KB  2283416KB 67178688KB       3%  /vol/vol0/.snapshot

netapp01> exportfs

/vol/vol0/home  -sec=sys,rw,nosuid

/vol/vol0       -sec=sys,rw=x.x.x.x,anon=0,nosuid

notes: x.x.x.x - IP address of server from which i can mount vol0 for upload disk firmware e.c.t

netapp01> options autosupport

autosupport.cifs.verbose     off       

autosupport.content          complete   (value might be overwritten in takeover)

autosupport.doit             WEEKLY_LOG

autosupport.enable           on         (value might be overwritten in takeover)

autosupport.from             myfiler@mydomain.x (value might be overwritten in takeover)

autosupport.local.nht_data.enable off        (value might be overwritten in takeover)

autosupport.local.performance_data.enable off        (value might be overwritten in takeover)

autosupport.mailhost         x.x.x.x (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       my.mail@mydomain.x (value might be overwritten in takeover)

autosupport.performance_data.doit DONT      

autosupport.performance_data.enable on         (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    off        (value might be overwritten in takeover)

autosupport.support.to       autosupport@netapp.com (value might be overwritten in takeover)

autosupport.support.transport smtp       (value might be overwritten in takeover)

autosupport.support.url      support.netapp.com/asupprod/post/1.0/postAsup (value might be overwritten in takeover)

autosupport.throttle         on         (value might be overwritten in takeover)

autosupport.to               my.mail@mydomain.x (value might be overwritten in takeover)

netapp01>

notes: my.mail@mydomain.x - my corporate e-mail address, x.x.x.x - ip address of our mailhost, myfiler@mydomain.x - address in field "From" in autosupport mail

What is your opinion?

Re: Problem with Autosupport

Re: Problem with Autosupport

Hello, Andrey! Thank you for helping!


netapp01> qtree status vol0

Volume   Tree     Style Oplocks  Status  

-------- -------- ----- -------- ---------

vol0              unix  enabled  normal 


netapp01> qtree security /vol/vol0

/vol/vol0/ has unix security style and oplocks are enabled.


netapp01> options cifs.ntfs_ignore_unix_security_ops

cifs.ntfs_ignore_unix_security_ops off


If It really needed, I will switch it to ON and i will post here about result  this operation.

Re: Problem with Autosupport

This option affects only NTFS security style.

Which version of Data ONTAP are you using?

Re: Problem with Autosupport

netapp01> version

NetApp Release 8.0RC3 7-Mode