ONTAP 9 ASUP SMTP Send fail / Switching to HTTP

[kobusventer]

Hi everyone. 

I am sitting in a very awkward situation. I upgraded a storage system from ONTAP 9.7 to ONTAP 9.11, in steps. During the last upgrade from 9.10 to 9.11, ASUP "break" on the one node. The last automated ASUP sent was a waring on ONTAP 9.10 that the software is near its EOS date. Before the upgrade ASUP was working fine, AND ASUP is working fine on the second node.

Error:

Failed to transmit smtp asup 2711, curl error: Timeout was reached)

SO -

No problem on the SMTP server

No network coms error - I can log in via both nodes management ports (residing HOME on e0M)

Both nodes cannot ping the SMTP server. (I assume that they can ping the default gateway as I am able to log into the MGMT ports?)

Support suggested the normal thing - check SMTP server, etc etc. NO solution yet. 

Fact is - this was working PRIOR to the upgrade. 

Any ideas? 

Then on HTTP/S

The Customer make use of firewalls and a proxy - I assume I should create a HTTP proxy for the management vfiler? The documentation is not very clear on this. I already applied for firwall access to the NA support IP, and is in the process to apply for wiferwall access to the PROXY server as well.

Is this the correct way of doing it?

Create HTTP proxy service on vserver (Customer use port 80)

Change ASUP transport to HTTP

regards

Kobus

[Ontapforrum]

Could you share the output of these commands?
::> autosupport history show -instance
::> node run -node <node name> -command rdfile /etc/log/mlog/notifyd.log

Troubleshoot AutoSupport message delivery over SMTP:
https://docs.netapp.com/us-en/ontap/system-admin/troubleshoot-autosupport-delivery-smtp-task.html

ONTAP AutoSupport (Transport SMTP) Resolution Guide - NetApp Knowledge Base

Related:

Receive asup.smtp.drop error message during Ontap version upgrade - NetApp Knowledge Base

[kobusventer]

Hi, please see attached. The "related" issue is not applicable, as the systems was upgraded during December. Since that time, I am uploading the ASUPs weekly. Everything inside the SMTP troubleshooting guide was done. I removed any references to the system names from the log files. Please also note that the notify.log file was downloaded from spi. 

Regards

Kobus

[Ontapforrum · Accepted solution]

I see following errors in the notifyd logs:
(emittime: 12/28/2022 02:14:02) (message: connect to 165.143.128.26 port 25 failed: Operation timed out)

Wed Dec 28 2022 02:41:56 +02:00 [kern_notifyd:info:1641] (category: 1641:2616:deliver) (emittime: 12/28/2022 01:34:11) (message: Failed to transmit smtp asup 2616, curl error: Timeout was reached)
Wed Dec 28 2022 02:46:00 +02:00 [kern_notifyd:info:1641] 0x80c124c00: 0: ERR: Autosupport::Delivery: Unable to retrieve the FQDN of node, using the hostname in connection request sent to SMTP mailhost

I also see number these errors:

0000002e.01199edd 0254eb23 Wed Dec 28 2022 01:06:05 +02:00 [kern_notifyd:info:1641] asup_pack_archive asup[1641:2616] Error adding cm-stats-hourly-data-07.tar: Payload size needs to be increased

These messages occur when the transport payload size exceeds the set value (5MB SMTP). (Please see all 3 options mentioned)

AutoSupport Notifyd  log - Error adding  (file): Payload size needs to be increased - NetApp Knowledge Base

Also check - if the port 25 blocked? Is Node able to reach out to DNS server ?

Check this kb:
Unable to send autosupport with "The system will drop the message."
https://mysupport.netapp.com/site/article?lang=en&page=%2FAdvice_and_Troubleshooting%2FData_Storage_Software%2FONTAP_OS%2FUnable_to_send_autosupport_w...

https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/AutoSupport_sends_failure

Also check this kb:
https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/AutoSupport_delivery_fails_due_to_DNS_-_Couldn't_resolve_host_in_ONTAP...

[kobusventer]

Hi. This was NOT the solution. The issue "magically" disappeared after the system, was upgraded 9.12.1. Remember - I said that the issue occurred during the upgrade from 9.10 to 9.11. So - this thread can be marked as resolved by a system upgrade. Again - NO settings was changed during or after the initial upgrade, nor during the last to 9.12. Thanks for everyone's suggestions and support.

[kobusventer]

This is now resolved. The issue "magically" disappeared after the system, was upgraded 9.12.1.