Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 6 results
    • Dynamic capacity expansion over asynchronous remote volume mirroring results in failed drives and failed volumes
      https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/Dynamic_capacity_expansion_over_asynchronous_remote_volume_mirroring_results_in_failed_drives_and_failed_volumes
      When performing one of the following reconfigure operations on a volume group containing ARVM mirrors with PI enabled and a controller that supports multicore, the reconfigure operation can result in ...When performing one of the following reconfigure operations on a volume group containing ARVM mirrors with PI enabled and a controller that supports multicore, the reconfigure operation can result in PI Reftag errors that lead to failed drives, failed volumes and failed reconfigure operations. Due to the volume failure during reconfiguration, the only way to recover is to delete the volume group.
    • E-Series 5700 controller panic with PCI SERR exception to PLX 8748 switch
      https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E-Series_5700_controller_panic_with_PCI_SERR_exception_to_PLX_8748_switch
      Controller reboots with the following PCI SERR (System Error) exception logged in excLogShow command. The command is available in state-capture-data file as part of support bundle and AutoSupport coll...Controller reboots with the following PCI SERR (System Error) exception logged in excLogShow command. The command is available in state-capture-data file as part of support bundle and AutoSupport collections. PCI SERR Exception PCI-E Root Port to PLX 8748 PCI Switch (Unit 3) PCI-E AER Uncorrectable Status = 0x00004000 PCI-E AER Root Error Status = 0x00000057 PLX PCI Switch to SAS Drive Side2 (Unit 12) ERROR: PCI CFG ACCESS FAILED FOR BDF[68,0,0], 0x1000:0x0097
    • E-series ASUP delivery failure when using proxy server on santricity OS 11.50.2
      https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E-series_ASUP_delivery_failure_when_using_proxy_server_on_santricity_OS_11.50.2
      Applies to Santricity OS 11.50.2 (11.50.00.00) EF280 E2800 EF570 E5700 Issue Getting java.unknownHostNameException error for support.netapp.com when performing ASUP test for HTTP/HTTPS using proxy via...Applies to Santricity OS 11.50.2 (11.50.00.00) EF280 E2800 EF570 E5700 Issue Getting java.unknownHostNameException error for support.netapp.com when performing ASUP test for HTTP/HTTPS using proxy via Santricity Storage Manager GUI Proxy IP and port are verified and correct. Proxy or firewall have the controller management IP address allowed.
    • E-Series Web Server not starting
      https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/E-Series_Web_Server_not_starting
      Dec 06 13:55:41 eos-a start[6523]: at com.loem.aa.webserver.server.WebServer.<init>(WebServer.java:159) Dec 06 13:55:41 eos-a start[6523]: at com.loem.aa.webserver.server.WebServer.init(WebServer.java...Dec 06 13:55:41 eos-a start[6523]: at com.loem.aa.webserver.server.WebServer.<init>(WebServer.java:159) Dec 06 13:55:41 eos-a start[6523]: at com.loem.aa.webserver.server.WebServer.init(WebServer.java:239) Dec 06 13:55:41 eos-a start[6523]: at com.loem.aa.webserver.server.WebServer.init(WebServer.java:227) Dec 06 13:55:41 eos-a start[6523]: at com.loem.aa.webserver.Main.main(Main.java:110) Dec 06 13:55:43 eos-a start[6523]: keytool error: java.io.IOException: No space left on device
    • Amber light on Fiber Channel port
      https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/Amber_light_on_Fiber_Channel_port
      Applies to E5760 Issue After a controller replacement, the amber light on a Fibre Channel port on the controller turns on.
    • Data could not be loaded from SANtricity System Manager (SAM)
      https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/Data_could_not_be_loaded_from_SANtricity_System_Manager_SAM
      Logging into SAM via web browser (IE, FireFox or Chrome), the following error is displayed: Data could not be loaded from the storage array. One possible cause is the object on which you were performi...Logging into SAM via web browser (IE, FireFox or Chrome), the following error is displayed: 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. Controller A and B are no longer accessible through StorageGRID System Manager > Nodes > Tab SANtricity System Mananger not possible