Skip to main content
NetApp Knowledge Base

Cannot access SANtricity System Manager intermittently

  1. Last updated
    Feb 13, 2025
  2. Save as PDF
Views:
2,289
Visibility:
Public
Votes:
3
Category:
e-series-systems
Specialty:
esg
Last Updated:
2/13/2025, 2:41:58 PM

Applies to

  • E2800
  • E5700
  • SG5760
  • SANtricity System Manager

Issue

  • When attempting to access the SANtricity System Manager web-based GUI, the user encounters below errors:

Your client browser cannot communicate with the storage array to complete this operation. Possible causes include network issues, inability to communicate with the controller, or loss of power to the storage array. Check these causes and retry the operation.

Data could not be loaded from the storage array. One possible cause is the object on which you were performing the operation no longer exists. Other possible causes include network issues, inability to communicate with the controller, or loss of power to the storage array. Check these causes and then retry the operation.

  • When attempting to generate a support bundle, the user may encounter:

Unable to collect support data due to reservation request failure. You may retry the operation. (Web Server 422)

The element Could not be found. It may have been deleted by another storage management application.  (Web Server 404)

  • When attempting to access the SANtricity System Manager web-based GUI, the user may see a Please Wait icon:

Screen Shot 2022-01-31 at 3.37.21 PM.png

Review WEB-SERVER-TRACE.LOG
2024-02-09 09:42:49,127 ERROR [SMMonitorTask-2445] trace [LoggingJdkHandler.java:32] [requestId=0, deviceId=N/A] [devmgr.versioned.sam.advanced.gathersupportdata.GatherSupportDataForService handleError] Unable to collect support data due to reservation request failure.
 
You may retry the operation.
Caller+0     at smmonitor.logging.LoggingJdkHandler.publish(LoggingJdkHandler.java:32)
Caller+1     at java.logging/java.util.logging.Logger.log(Logger.java:979)
Caller+2     at devmgr.trace.TraceComponent.printToOutput(TraceComponent.java:856)
Caller+3     at devmgr.trace.TraceComponent.println(TraceComponent.java:551)
Caller+4     at devmgr.versioned.sam.advanced.gathersupportdata.GatherSupportDataForService.handleError(GatherSupportDataForService.java:136)
2024-02-09 09:43:39,272 ERROR [jetty-2806967] c.n.e.a.r.p.e.ExceptionHandler [ExceptionHandler.java:167] [requestId=cbb731e6-ed4e-4507-b727-8435d39a238d, deviceId=N/A]
 
Exception in resource.
Wrapped by: java.lang.Exception: Error sending SYMbol procedure bindToController (2) to EOS : Connection timed out (Connection timed out)SSH to working controller

 

 

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.