Skip to main content
NetApp Knowledge Base

One EF600 controller is unresponsive and the alternative controller is in lockdown

  1. Last updated
    Jul 9, 2024
  2. Save as PDF
Views:
225
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:
7/9/2024, 8:44:12 AM

Applies to

  • EF600
  • EF300

Issue

  • One controller (for example, controller A) is unresponsive
  • The alternative controller (controller B) is in Reboot Loop Limit Exceeded with lockdown code 0E LU
controller lockdown
  • Unable to collect Support Data of each controller from SANtricity System Manager

One EF600 controller is unresponsive and the alternative controller is in lockdown

  • Click the Clear Lockdown button on SANtricity System Manager, controller B reboots several times and lockdown again
  • excLogShow from the alternative controller shell shows PCI SERR as reboot reasons
PCI SERR Exception
SERR Summary: 0x80000001
SERR Return Status: 0x00000002
SERR Collection Count: 0x2
   CB3 DMA/XOR  (Unit 0)
VID 0x8086 DID 0x2021 B0:D4:F0
PCI Status = 0x2010
SERR Summary Flags = 0x80000001
   PCI-E Root to PLX9797-1  (Unit 1)
VID 0x8086 DID 0x2030 B100:D0:F0
Bridge Secondary PCI Status = 0x2000
PCI-E XP Uncorrectable Status = 0x00000040
SERR Summary Flags = 0x80000001
SERR probably caused by a bad address.
Processor Global Fatal Error:  4
Processor Global Nonfatal Error: 1
 
IIO C-Stack 0
  LSYSST      : 0x00000002
  LNFERRST    : 0x00400000
 
IIO P-Stack 2
  LSYSST      : 0x00000004
  LFERRST     : 0x00001000
 
Processor reported PCI SERR

 

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.