Search
- Filter results by:
- View attachments
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Autosupport_delivery_to_NetApp_via_SMTP_protocol_failsNotifyd log indicates that Autosupports were successfully delivered via SMTP protocol 00000016.000d6924 019fe2a2 Mon May 13 2024 00:24:51 [kern_notifyd:info:2262] Successfully processed smtp ASUP by d...Notifyd log indicates that Autosupports were successfully delivered via SMTP protocol 00000016.000d6924 019fe2a2 Mon May 13 2024 00:24:51 [kern_notifyd:info:2262] Successfully processed smtp ASUP by delivery thread, seq: 79 status: sent-successful 00000016.000d69ed 019ff573 Mon May 13 2024 00:32:52 [kern_notifyd:info:2262] Successfully processed smtp ASUP by delivery thread, seq: 80 status: sent-successful
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Autosupport_in_ONTAP_is_randomly_sending_out_notice_logs_using_SMTP_due_to_a_web_filterNot sending (PERFORMANCE DATA) NOTICE and (USER_TRIGGERED) NOTICE logs In the Active IQ dashboard - Autosupport section you confirm the (PERFORMANCE DATA) NOTICE and (USER_TRIGGERED) NOTICE logs are m...Not sending (PERFORMANCE DATA) NOTICE and (USER_TRIGGERED) NOTICE logs In the Active IQ dashboard - Autosupport section you confirm the (PERFORMANCE DATA) NOTICE and (USER_TRIGGERED) NOTICE logs are missing (aka not reaching NetApp) But you can confirm (MANAGEMENT_LOG) NOTICE and (WEEKLY_LOG) NOTICE Autosupports are being received From the command line Autosupport history show confirms that all logs are sent-successful cluster1::> system node autosupport check show -node node_name
- https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/E-Series_SMTP_AutoSupport_does_not_contain_any_log_files_beside_the_HEADERS_fileApplies to All E-Series platforms SANtricity OS 11.70.1GA SMTP (mail) AutoSupport delivery method Issue E-Series AutoSupport contains none of the expected log files. Only the HEADERS file is displayed...Applies to All E-Series platforms SANtricity OS 11.70.1GA SMTP (mail) AutoSupport delivery method Issue E-Series AutoSupport contains none of the expected log files. Only the HEADERS file is displayed in SmartSolve.
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/AutoSupport_connection_refusedApplies to ONTAP 9 AutoSupport Issue AutoSupport message status shows "transmission-failed" In notifyd.log output, you see: message: connect to 216.240.21.18 port 443 failed: Connection refused
- https://kb.netapp.com/Legacy/ONTAP/7Mode/AutoSupport_message__Exceeded_maximum_raw_capacity_CRITICAL[filer11: raid.disk.tooBig.all.reminder:error]: System raw capacity XXX TB exceeds the XXX TB maximum. Reverting to a Data ONTAP release with a lower maximum capacity causes a panic. When reverting to...[filer11: raid.disk.tooBig.all.reminder:error]: System raw capacity XXX TB exceeds the XXX TB maximum. Reverting to a Data ONTAP release with a lower maximum capacity causes a panic. When reverting to a Data ONTAP release with a lower maximum capacity than the capacity supported by the newer version of Data ONTAP, without removing the added capacity, the filer may panic. Reverting to a Data ONTAP release with a lower maximum capacity.
- https://kb.netapp.com/on-prem/ontap/DM/Encryption/Encryption-KBs/What_will_happen_when_my_Autosupport_Certificate_in_ONTAP_expiresmgmtgwd.certificate.expiring: A digital certificate with Fully Qualified Domain Name (FQDN) AddTrustExternalCARoot, Serial Number 01, Certificate Authority 'AddTrust External CA Root' and type server-...mgmtgwd.certificate.expiring: A digital certificate with Fully Qualified Domain Name (FQDN) AddTrustExternalCARoot, Serial Number 01, Certificate Authority 'AddTrust External CA Root' and type server-ca for Vserver (vserver) will expire in the next (--) day(s). If you are not on a fixed version for Bug 1245418 - EMS expiration warnings are sent for truststore certificates expiring in 30 days you will continue to see the EMS expiration message until you upgrade.
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/AutoSupport_delivery_fails_due_to_DNS_Couldn_t_resolve_host_in_ONTAP_9_and_earlierAutoSupport delivery fails due to DNS servers unable to resolve host in ONTAP 9 and earlier. This article covers some of the common causes and the solution to resolve these issues.
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_perform_a_system_health_check_after_a_Data_ONTAP_upgrade_or_hardware_replacement__Resolution_GuideThe procedure to be followed to perform a system health check after a Data ONTAP upgrade or hardware replacement is described in this article. AutoSupports will need to be triggered from all nodes aft...The procedure to be followed to perform a system health check after a Data ONTAP upgrade or hardware replacement is described in this article. AutoSupports will need to be triggered from all nodes after the upgrade/replacement is complete.
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/HTTPs_AutoSupport_delivery_fails_with_a_PROXYAutoSupport configured with a Proxy Failed to connect to support.netapp.com port 443: Connection refused AutoSupports for one or more nodes fail to reach NetApp due to network timeout. Error: Timeout ...AutoSupport configured with a Proxy Failed to connect to support.netapp.com port 443: Connection refused AutoSupports for one or more nodes fail to reach NetApp due to network timeout. Error: Timeout was reached when connecting to the server Timeout messages in the notifyd logs to the proxy URL ... (message: connect to proxyurl_IP port 8080 failed: Operation timed out) ... (message: Failed to connect to proxyurl port 8080: Operation timed out)
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Autosupport_fails_delivery_with_error_Operation_timed_out_in_ONTAPThis KB provides the reason why Autosupport fails delivery with Operation timed out error in ONTAP and the solution for the issue.
- https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/CHASSIS_POWER_DEGRADED_-_Autosupport_MessageKB provides the cause and solution when the AutoSupport message Chassis Power Supply Degraded is seen.