跳转到主内容

AutoSupport for ONTAP 9 over SMTP 错误消息: 421.3.2 服务不可用

Views:
3
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core<a>用于</a><a>转换</a><a>的ASUP SMTP </a>
Last Updated:

适用场景

  • ONTAP 9
  • AutoSupport
  • 传输 SMTP

问题描述

  • AutoSupport 无法通过 SMTP 发送。
  • 我未收到发送到 SMTP 帐户的 AutoSupport 消息
ONTAP 中的错误:
  • 查看 AutoSupport 历史记录:

::>system autosupport history show -node <node_name>  -fields node,seq-num,status,error,destination

- 或 -

  • 检查特定序列

::> system autosupport history show -seq-num 270 -instance

Node: Node-01 AutoSupport
Sequence Number: 270
Destination for This AutoSupport: smtp
Trigger Event: callhome.invoke
Time of Last Update: 12/24/2015 00:42:51
Status of Delivery: transmission-failed
Delivery Attempts: 15
AutoSupport Subject: USER_TRIGGERED (TEST:Testing from NODE1)
Delivery URI: mailto:admins@example.com
Last Error: weird server reply

Notifyd 中的错误:
  • 如何查看 notifyd . log :

::> node run -node (node name) -command rdfile /etc/log/mlog/notifyd.log

(category: 1620:538:deliver) (emittime: 12/24/2020 00:42:51) (message:   Trying 10.0.0.1:25...)
(category: 1620:538:deliver) (emittime: 12/24/2020 00:42:51) (message: Connected to exchange.com (10.0.0.1) port 25 (#0))
(category: 1620:538:deliver) (emittime: 12/24/2020 00:42:51) (message: Marked for [keep alive]: SMTP default)
(category: 1620:538:deliver) (emittime: 12/24/2020 00:42:51) (message: SMTP 0x809c4ff state change from STOP to SERVERGREET)
(category: 1620:538:deliver) (emittime: 12/24/2020 00:42:51) (message: 421 4.3.2 Service not available)
(category: 1620:538:deliver) (emittime: 12/24/2020 00:42:51) (message: Got unexpected smtp-server response: 421)
(category: 1620:538:deliver) (emittime: 12/24/2020 00:42:51) (message: multi_done)
(category: 1620:538:deliver) (emittime: 12/24/2020 00:42:51) (message: Marked for [closure]: SMTP done with bad status)
(category: 1620:538:deliver) (emittime: 12/24/2020 00:42:51) (message: Closing connection 0)
(category: 1620:538:deliver) (emittime: 12/24/2020 00:42:51) (message: Failed to transmit smtp asup 538,
curl error: Weird server reply)

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.