The AutoSupport history output shows multiple transport attempts usingSMTP, HTTP, and HTTPS, with SMTP being re-queued, HTTP ignored, and HTTPS failed. This indicates that AutoSupport is enabled and functioning at the configuration level, but the delivery mechanism is being blocked or restricted by the customer’s network infrastructure.

SMTP failures commonly occur when mail servers block large attachments or require explicit whitelisting of sending systems. Since full AutoSupport messages include large log bundles, mail servers often reject or delay these messages unless the sending nodes are explicitly allowed. Therefore,whitelisting the nodes on the mail serverdirectly addresses the SMTP delivery issue.

Additionally, NetApp installation best practices recommendHTTPS as the preferred AutoSupport transport protocolbecause it bypasses mail server limitations and is more reliable for large payloads. Switching the transport protocol to HTTPS avoids SMTP attachment-size restrictions entirely and ensures successful delivery when outbound HTTPS access is allowed.

Enabling AutoSupport on both nodes is not relevant because the output confirms AutoSupport is already active. Excluding nodes from attachment-size limits is not a supported ONTAP action.

Thus, the two correct actions are tochange the transport protocol to HTTPSandwhitelist the nodes on the mail server.