Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

ONTAP: AutoSupport fails to send messages due to error HTTP/1.1 302 Moved Temporarily

Views:
234
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • HTTP
  • HTTPS
  • AutoSupport

Issue

NetApp controller is failing to send All or particular messages. In this case it was failing to send a failed disk message

 

Check Autosupoprt History
  • Cluster::>autosupport history show

             Seq                                    Attempt  Percent  Last
Node         Num   Destination Status               Count    Complete Update
------------ ----- ----------- -------------------- -------- -------- --------
node01      1680   http       transmission-failed  15       -        5/28/2020 02:20:53

 

  • Use the "system autosupport history show -seq-num ### -instance" command to review the specific sequence and the Last Error is Unknown error.  

Cluster::> system autosupport history show -seq-num 1680 -instance

                            Node: node01
     AutoSupport Sequence Number: 1680
Destination for This AutoSupport: http
                   Trigger Event: callhome.sdsk.fault
             Time of Last Update: 5/28/2020 02:20:53
              Status of Delivery: transmission-failed
               Delivery Attempts: 15
             AutoSupport Subject: SPARE DISK FAILED Shelf 0, Bay 0, Model [X357_S16433T8ATE]
                    Delivery URI: support.netapp.com/put/AsupPut/
                      Last Error: Unknown error  
              Time of Generation: 5/28/2020 00:01:51
     AutoSupport Compressed Size: 131.4KB
                Percent Complete: -
                  Rate of Upload: -
       Time Remaining for Upload: 0s
   AutoSupport Decompressed Size: 476.0KB
      Total Collection Time (ms): 6257


The detailed error messages can be determined by viewing the errors logged by notifyd.log  in the AutoSupport subsystem by reviewing the /mroot/etc/log/mlog/notifyd.log

How to review notifyd.log


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

Example output:

(message: HTTP 1.1 or later with persistent connection, pipelining supported)
(message: HTTP/1.1 302 Moved Temporarily)
(message: Date: Thurs, 28 May 2020 13:56:06 GMT)
(message: Marked for [closure]: Connection: close used)
(message: Connection: close)
(message: Via: HTTPS/1.1 mcn-websense-cg.opm.gov)
(message: Location: http://172.26.23.40:15871/cgi-bin/blockpage.cgi?ws-session=1465034389)
(message: Content-Length: 0)
(message:
(message: STATE: PERFORM => DONE handle 0x809d98008; line 1986 (connection #1))
(message: multi_done)
(message: Closing connection 1)
(message: The cache now contains 0 members)
(message: TLSv1.2 (OUT), TLS alert, Client hello (1):)
(message: Expire cleared)
(message: deliver_http_asup: HTTP PUT request failed, code: 302, chunk: 0 of 0)

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support