Subscribe

Problem with Autosupport

Hello, guys.
In our company we have a NetApp FAS 6040 release 8.0RC3 7-Mode.
More recently, there was a problem with configuring autosupport. When you try to change settings, turn off, turn on - nothing happens and mistakes occur:

netapp02> options autosupport      
autosupport.cifs.verbose     off       
option autosupport.content: can not be read, connection problem (code=0xffffffff)
autosupport.content          unknown    (value might be overwritten in takeover)
option autosupport.doit: can not be read, connection problem (code=0xffffffff)
autosupport.doit             unknown   
option autosupport.enable: can not be read, connection problem (code=0xffffffff)
autosupport.enable           unknown    (value might be overwritten in takeover)
option autosupport.from: can not be read, connection problem (code=0xffffffff)
autosupport.from             unknown    (value might be overwritten in takeover)
option autosupport.local.nht_data.enable: can not be read, connection problem (code=0xffffffff)
autosupport.local.nht_data.enable unknown    (value might be overwritten in takeover)
option autosupport.local.performance_data.enable: can not be read, connection problem (code=0xffffffff)
autosupport.local.performance_data.enable unknown    (value might be overwritten in takeover)
option autosupport.mailhost: can not be read, connection problem (code=0xffffffff)
autosupport.mailhost         unknown    (value might be overwritten in takeover)
option autosupport.minimal.subject.id: can not be read, connection problem (code=0xffffffff)
autosupport.minimal.subject.id unknown    (value might be overwritten in takeover)
option autosupport.enable: can not be read, connection problem (code=0xffffffff)
option autosupport.nht_data.enable: can not be read, connection problem (code=0xffffffff)
autosupport.nht_data.enable  unknown    (value might be overwritten in takeover)
option autosupport.enable: can not be read, connection problem (code=0xffffffff)
option autosupport.noteto: can not be read, connection problem (code=0xffffffff)
autosupport.noteto           unknown    (value might be overwritten in takeover)
option autosupport.from: can not be read, connection problem (code=0xffffffff)
option autosupport.partner.to: can not be read, connection problem (code=0xffffffff)
autosupport.partner.to       unknown    (value might be overwritten in takeover)
option autosupport.support.proxy: can not be read, connection problem (code=0xffffffff)
option autosupport.performance_data.doit: can not be read, connection problem (code=0xffffffff)
autosupport.performance_data.doit unknown   
option autosupport.support.transport: can not be read, connection problem (code=0xffffffff)
option autosupport.performance_data.enable: can not be read, connection problem (code=0xffffffff)
autosupport.performance_data.enable unknown    (value might be overwritten in takeover)
option autosupport.retry.count: can not be read, connection problem (code=0xffffffff)
autosupport.retry.count      unknown    (value might be overwritten in takeover)
option autosupport.retry.interval: can not be read, connection problem (code=0xffffffff)
autosupport.retry.interval   unknown    (value might be overwritten in takeover)
option autosupport.support.enable: can not be read, connection problem (code=0xffffffff)
autosupport.support.enable   unknown    (value might be overwritten in takeover)
option autosupport.support.proxy: can not be read, connection problem (code=0xffffffff)
autosupport.support.proxy    unknown    (value might be overwritten in takeover)
option autosupport.support.to: can not be read, connection problem (code=0xffffffff)
autosupport.support.to       unknown    (value might be overwritten in takeover)
option autosupport.support.transport: can not be read, connection problem (code=0xffffffff)
autosupport.support.transport unknown    (value might be overwritten in takeover)
option autosupport.support.url: can not be read, connection problem (code=0xffffffff)
autosupport.support.url      unknown    (value might be overwritten in takeover)
option autosupport.throttle: can not be read, connection problem (code=0xffffffff)
autosupport.throttle         unknown    (value might be overwritten in takeover)
option autosupport.to: can not be read, connection problem (code=0xffffffff)
autosupport.to               unknown    (value might be overwritten in takeover)

All  this only happens on one controller, but a second controller is  operating normally allows you to change settings autosupport as it  should.
Does anyone can offer ideas?

Re: Problem witch Autosupport

Hi ucellcoscom

Please post messages from  /etc/messages

If you don't know how read messages  --->  rdfile /etc/messages  or  \\name_filer\etc$\

Thanks 

Re: Problem witch Autosupport

Thank you for your reply.
Here is the file over the past few days.

Re: Problem witch Autosupport

Hello ucellcoscom

1. Please check next configuration on your filer

autosupport.content [complete | minimal]   - Controls the content in AutoSupport message. Default is complete.
autosupport.doit [message]   - It helps to send AutoSupport message immediately with specified message as subject.It can be used to validate the AutoSupport configuration.
autosupport.sender [ from ]   -Defines the specified user as sender
autosupport.mailhost [host1,..,host5]  -Defines mail host names
autosupport.minimal.subject.id [hostname|systemid]  -Defines the system identification in message title
autosupport.support.transport [http | https | smtp ]   -Defines the AutoSupport message delivery method
autosupport.support.to  - Indicates where AutoSupport notifications to NetApp are sent if autosupport.support.transport is smtp. This is a read-only option.

2.Check to see if the file spool area (located in /etc/log/autosupport on a filer, /logs/autosupport on a NetCache) is full, or if the acls/permissions on the file spool area or the autosupport messages subdirectory (the autosupport message directories have .files as an extension), are blocking access. If the spool area is full, you are free to delete any subdirectories that do not have associated transmission flag files (files with .smtp or .post extensions.)

For additional information please see http://www.wafl.co.uk/autosupport/

Thanks

Re: Problem witch Autosupport

Thank you for your reply.

Under item 1 - see the first post. Commands do not work.

Under item 2:

Filesystem               total       used         avail        capacity  Mounted on
/vol/vol0/               264GB       11GB      253GB       4%          /vol/vol0/

Permission to vol0 nobody changed.

By the way, I found that some commands are also not working. For example:

netapp02> options timed.servers 192.168.55.33
Could not delete timed servers
Could not set timed server 192.168.55.33.

What could this mean?

Re: Problem witch Autosupport

Hello ucellcoscom

Please delete all files and folder /etc/log/autosupport

Thanks

Re: Problem witch Autosupport

Hello ucellcoscom

Please check smtp server settings.On smtp server must be open smtp relay for IP addresses filers.

Thanks

Re: Problem with Autosupport

Did you ever find the fix for this? I'm experiencing the exact same issue and support isn't being too helpful.

Re: Problem with Autosupport

It was a stupid problem. I am very ashamed, but Default Gateway was entered incorrectly.

Re: Problem with Autosupport

Default Gateway settings was wrong.