E-Series ASUP not delivered despite having the same configuration as alternate controller
- Views:
- 19
- Visibility:
- Public
- Votes:
- 0
- Category:
- e-series-santricity-storage-manager
- Specialty:
- esg
- Last Updated:
Applies to
Issue
- AutoSupport logs are not delivered despite having the same configuration within SANtricity as alernate controller and other working appliances.
- DNS is properly configured.
- Cabling of controller is correct.
- Other E-Series controllers connected to the same switch as affected controller are sending ASUPs as expected.
WEB-SERVER-TRACE-LOG-B.7Zshows:
2026-03-31 00:13:38,802 ERROR [AsupAodWorker-1] trace [ASUPHTTPClient.java:1365] [requestId=0, deviceId=N/A] ASUP Upload Host InetSocketAddress is unresolved.Caller+0 at smmonitor.asup.ASUPHTTPClient.initializeServerAddress(ASUPHTTPClient.java:1365)
Caller+1 at smmonitor.asup.ASUPHTTPClient.<init>(ASUPHTTPClient.java:263)
Caller+2 at smmonitor.asup.ASUPTask.initializeDispatchClient(ASUPTask.java:1772)
Caller+3 at smmonitor.asup.ASUPTask.dispatchAODMessage(ASUPTask.java:2076)
Caller+4 at smmonitor.asup.ASUPTask.doTaskOperation(ASUPTask.java:1372)
java.net.UnknownHostException: support.netapp.com
2026-03-31 00:13:38,803 ERROR [AsupAodWorker-1] trace [ASUPTask.java:1799] [requestId=0, deviceId=N/A] ASUP support bundle dispatch failed with an exception
Caller+0 at smmonitor.asup.ASUPTask.initializeDispatchClient(ASUPTask.java:1799)
Caller+1 at smmonitor.asup.ASUPTask.dispatchAODMessage(ASUPTask.java:2076)
Caller+2 at smmonitor.asup.ASUPTask.doTaskOperation(ASUPTask.java:1372)
Caller+3 at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:1265)
Caller+4 at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:48)
java.net.UnknownHostException: support.netapp.com
No other appliances within the same array can ping the affected controller.- Alternate controller cannot ping affected controller. However, alternate controller can ping any other appliance within the same array.
