EF/E-Series, SANtricity and Related Plug-ins

Event occurred: Fri, 12 Mar 2021 00:56:38 +0000 Event Message: An ASUP message could not be delivere

robc

I get the below Event intermittently is there a reason for such events and can this be ignored.

 

Event occurred: Fri, 12 Mar 2021 00:56:38 +0000 Event Message: An ASUP message could not be delivered A from the array management host eos-b to NetApp ASUP https gateway https://protect-eu.mimecast.com/s/__eYC4xYOHB770jsOKibV?domain=support.netapp.com.

 

 

1 ACCEPTED SOLUTION

ahmadm

I do not have weekly AutoSupports yet that would contain the necessary logs to investigate an ASUP delivery issue for the March 12th event.

 

I checked out the ASUP history for both systems, and both systems appear to be sending ASUPs normally.

For array HSL-NetApp-01, the most recent failure was in January. Based on the AutoSupport logs from that timeframe, It was likely an intermittent connection issue that resulted in the failure. The fact that it also affected multiple ASUP types within a two minute period confirms the likelihood of an intermitten connection problem (likely network related) back then.

 

721942500038:

 

2021-01-03 00:52:54,347 ERROR [ASUPLFTWorker-1] trace [ASUPHTTPClient.java:752] [requestId=0, deviceId=N/A] Socket read/write failed.
Caller+0 at smmonitor.asup.ASUPHTTPClient.dispatchASUPMessage(ASUPHTTPClient.java:752)
Caller+1 at smmonitor.asup.ASUPTask.dispatchLFTChunk(ASUPTask.java:1557)
Caller+2 at smmonitor.asup.ASUPTask.doTaskOperation(ASUPTask.java:1360)
Caller+3 at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:1273)
Caller+4 at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:38)
java.net.SocketException: Connection reset

 

1/3/21 00:52:55 UTC -> Priority:INFO, ASUP Message Type:DBM Backup, ASUP Task Type:Delivery, Status:FAILED, Storage Array:HSL-NetApp-01, SAID:6D039EA00002A361000000005E29241A, Chassis Serial Number:721942500038, Thread ID:4,405,448, Delivery Method:HTTPS, Sequence Number:754, Delivery URI:support.netapp.com/put/AsupPut/, AutoSupport Decompressed Size:N/A, Total Collection Time:N/A, Message:AutoSupport message dispatch failed.

 

1/3/21 00:54:08 UTC -> Priority:CRITICAL, ASUP Message Type:Daily Schedule, ASUP Task Type:Delivery, Status:FAILED, Storage Array:HSL-NetApp-01, SAID:6D039EA00002A361000000005E29241A, Chassis Serial Number:721942500038, Thread ID:4,405,442, Delivery Method:HTTPS, Sequence Number:754, Delivery URI:support.netapp.com/put/AsupPut/, AutoSupport Decompressed Size:N/A, Total Collection Time:N/A, Message:IO error occurred during AutoSupport message delivery.

 

For array HSL-DR-NetApp-01, the most recent failure was couple days ago (3/10). Prior to this failure, the last failure related message was in January. The failure from 3/10 appear to have been due to a connection time out while we were performing an ASUP onDemand poll, so there may have been also an intermittent communication issue as result of either a network problem or the back-end ASUP server.


721942500287:

 

2021-03-10 02:05:06,750 INFO [SMMonitorTask-4272] trace [ASUPHTTPClient.java:1025] [requestId=0, deviceId=N/A] Connecting to HTTPS server: support.netapp.com:443, IP 216.240.21.18
2021-03-10 02:07:13,966 ERROR [SMMonitorTask-4272] trace [ASUPHTTPClient.java:752] [requestId=0, deviceId=N/A] Socket read/write failed.
Caller+0 at smmonitor.asup.ASUPHTTPClient.dispatchASUPMessage(ASUPHTTPClient.java:752)
Caller+1 at smmonitor.asup.ASUPTask.dispatchAODMessage(ASUPTask.java:2160)
Caller+2 at smmonitor.asup.ASUPTask.doTaskOperation(ASUPTask.java:1381)
Caller+3 at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:1273)
Caller+4 at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:38)
java.net.ConnectException: Connection timed out (Connection timed out)


Based on those incidents and low reoccurrence, I suspect that there was either some intermittent network related connection problem or something the back-end ASUP server.

 

If you notice that the frequency is increasing lately, then I probably suggest opening a support case so we can discuss further and discuss the possibility of a network related issue and try to track down with our ASUP back-end team whether there were some intermittent issue on the ASUP server then. But overall, I think your ASUP deliveries are functioning pretty normal and all the different ASUP types we have for this platform are being delivered as scheduled.

View solution in original post

3 REPLIES 3

ahmadm

Hi robc,

 

This event indicates an AutoSupport message could not be delivered. This could be a result of delivery failure for any of the AutoSupport triggered messages (i.e daily, weekly, configuration backup (DBM Backup), critical, ASUP OnDemand). Such failures can be intermittent as result of communication issues, but resolve on the retry attempt.

 

In normal conditions, you should not see the alert or at least very rarely. If you are receiving the alert periodically, It is best to engage NetApp support to review the logs and determine the root cause behind it.

 

Additionally, if you want to share the serial number of your E-Series system here, I can possibly check if it is something we will be able to provide some quick guidance on.

ahmadm

I do not have weekly AutoSupports yet that would contain the necessary logs to investigate an ASUP delivery issue for the March 12th event.

 

I checked out the ASUP history for both systems, and both systems appear to be sending ASUPs normally.

For array HSL-NetApp-01, the most recent failure was in January. Based on the AutoSupport logs from that timeframe, It was likely an intermittent connection issue that resulted in the failure. The fact that it also affected multiple ASUP types within a two minute period confirms the likelihood of an intermitten connection problem (likely network related) back then.

 

721942500038:

 

2021-01-03 00:52:54,347 ERROR [ASUPLFTWorker-1] trace [ASUPHTTPClient.java:752] [requestId=0, deviceId=N/A] Socket read/write failed.
Caller+0 at smmonitor.asup.ASUPHTTPClient.dispatchASUPMessage(ASUPHTTPClient.java:752)
Caller+1 at smmonitor.asup.ASUPTask.dispatchLFTChunk(ASUPTask.java:1557)
Caller+2 at smmonitor.asup.ASUPTask.doTaskOperation(ASUPTask.java:1360)
Caller+3 at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:1273)
Caller+4 at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:38)
java.net.SocketException: Connection reset

 

1/3/21 00:52:55 UTC -> Priority:INFO, ASUP Message Type:DBM Backup, ASUP Task Type:Delivery, Status:FAILED, Storage Array:HSL-NetApp-01, SAID:6D039EA00002A361000000005E29241A, Chassis Serial Number:721942500038, Thread ID:4,405,448, Delivery Method:HTTPS, Sequence Number:754, Delivery URI:support.netapp.com/put/AsupPut/, AutoSupport Decompressed Size:N/A, Total Collection Time:N/A, Message:AutoSupport message dispatch failed.

 

1/3/21 00:54:08 UTC -> Priority:CRITICAL, ASUP Message Type:Daily Schedule, ASUP Task Type:Delivery, Status:FAILED, Storage Array:HSL-NetApp-01, SAID:6D039EA00002A361000000005E29241A, Chassis Serial Number:721942500038, Thread ID:4,405,442, Delivery Method:HTTPS, Sequence Number:754, Delivery URI:support.netapp.com/put/AsupPut/, AutoSupport Decompressed Size:N/A, Total Collection Time:N/A, Message:IO error occurred during AutoSupport message delivery.

 

For array HSL-DR-NetApp-01, the most recent failure was couple days ago (3/10). Prior to this failure, the last failure related message was in January. The failure from 3/10 appear to have been due to a connection time out while we were performing an ASUP onDemand poll, so there may have been also an intermittent communication issue as result of either a network problem or the back-end ASUP server.


721942500287:

 

2021-03-10 02:05:06,750 INFO [SMMonitorTask-4272] trace [ASUPHTTPClient.java:1025] [requestId=0, deviceId=N/A] Connecting to HTTPS server: support.netapp.com:443, IP 216.240.21.18
2021-03-10 02:07:13,966 ERROR [SMMonitorTask-4272] trace [ASUPHTTPClient.java:752] [requestId=0, deviceId=N/A] Socket read/write failed.
Caller+0 at smmonitor.asup.ASUPHTTPClient.dispatchASUPMessage(ASUPHTTPClient.java:752)
Caller+1 at smmonitor.asup.ASUPTask.dispatchAODMessage(ASUPTask.java:2160)
Caller+2 at smmonitor.asup.ASUPTask.doTaskOperation(ASUPTask.java:1381)
Caller+3 at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:1273)
Caller+4 at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:38)
java.net.ConnectException: Connection timed out (Connection timed out)


Based on those incidents and low reoccurrence, I suspect that there was either some intermittent network related connection problem or something the back-end ASUP server.

 

If you notice that the frequency is increasing lately, then I probably suggest opening a support case so we can discuss further and discuss the possibility of a network related issue and try to track down with our ASUP back-end team whether there were some intermittent issue on the ASUP server then. But overall, I think your ASUP deliveries are functioning pretty normal and all the different ASUP types we have for this platform are being delivered as scheduled.

View solution in original post

robc
Thanks for the response
serial numbers are as follows; and they are running 11.50.3R2 and R1 
721942500038
721942500287
 

 

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public