Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 22 results
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E-Series_controller_in_lockdown_state_OE_L7_due_to_sub-model_identifier_mismatch
      Applies to All E-Series storage systems Issue Following a controller replacement, the controller shows 7segment code: OE L7. This code refers to sub-model identifier mismatch when compared to the surv...Applies to All E-Series storage systems Issue Following a controller replacement, the controller shows 7segment code: OE L7. This code refers to sub-model identifier mismatch when compared to the surviving controller.
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E-Series_controller_in_lockdown_state_OE_Lt_after_encountering_configuration_issues_during_startup
      Applies to All E-Series Hardware Platforms All E-Series Controller Firmware Issue Controller is locked down with a 7-segment LED code of OE Lt Alternate controller is typically also in lock down with ...Applies to All E-Series Hardware Platforms All E-Series Controller Firmware Issue Controller is locked down with a 7-segment LED code of OE Lt Alternate controller is typically also in lock down with code of OE LF or OE Lt but may be something else GUI may display alarm for "Storage Array in Recovery Mode'
    • https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E_Series_controller_in_lockdown_state_OE_LU_after_hitting_Start_of_Day_SOD_reboot_limit
      Applies to NetApp E-Series Issue Controller is locked down with a 7-segment LED code of OE LU This lockdown mechanism is used to avoid the hardware being worn from excessive boot sequences that fail I...Applies to NetApp E-Series Issue Controller is locked down with a 7-segment LED code of OE LU This lockdown mechanism is used to avoid the hardware being worn from excessive boot sequences that fail It also helps reduce software risks that could result from continuous boot cycles
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E-Series_controller_lockdown_with_0E_L3_due_to_faulty_HIC
      PCI DEVICE 0 NOT FOUND: Host-side Fibre Device=0 Function=3 ClassCode=0xc0400 ParentBridge=PCI-E Root Port to Host Card PCI DEVICE 0 NOT FOUND: Host-side Fibre Device=0 Function=2 ClassCode=0xc0400 Pa...PCI DEVICE 0 NOT FOUND: Host-side Fibre Device=0 Function=3 ClassCode=0xc0400 ParentBridge=PCI-E Root Port to Host Card PCI DEVICE 0 NOT FOUND: Host-side Fibre Device=0 Function=2 ClassCode=0xc0400 ParentBridge=PCI-E Root Port to Host Card PCI DEVICE 0 NOT FOUND: Host-side Fibre Device=0 Function=1 ClassCode=0xc0400 ParentBridge=PCI-E Root Port to Host Card PCI DEVICE 0 NOT FOUND: Host-side Fibre Device=0 Function=0 ClassCode=0xc0400 ParentBridge=PCI-E Root Port to Host Card
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/Controller_in_lockdown_state_displaying_0E___L0_in_7-segment_display
      Controller is locked down with a 7-segment LED code of either OE L0 or 06 L0 on the back of controller. The codes indicate the controller is locked down due to hardware mismatch. Condition: This contr...Controller is locked down with a 7-segment LED code of either OE L0 or 06 L0 on the back of controller. The codes indicate the controller is locked down due to hardware mismatch. Condition: This controller is paired with an invalid device in its alternate controller slot. Replace the in correct controller canister device with a matching The following error messages may be displayed in the boot sequence (console output) and the debug queue logs:
    • https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E-Series_controller_in_lockdown_state_OE_LC_due_to_a_persistent_cache_backup_configuration_error
      Applies to All E-Series Hardware Platforms All E-Series Controller Firmware Issue One or both controllers are in lockdown with seven segment code OE LC.
    • https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E-Series_how_to_download_SANtricity_OS_to_a_controller_in_lockdown_state
      Applies to NetApp E-Series SANtricity System Manager Description This article describes the procedure to use upgrade SANtricity OS of an E-Series controller in Lockdown state.
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E-Series_controller_in_lockdown_state_OE_LH_due_to_controller_firmware_mismatch
      Applies to E- Series Controllers Issue One or both controllers could have 7 segment code: OE LH.
    • https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/locks_down_with_status_of_Memory_Parity_Error_and_7-segment_code_sequence_OE_L2_CF_dx
      Controller locks down with 7-segment LED display code of "OE L2 CF dx". SANtricity System Manager or support bundle reports controller in "Memory Parity Error" status.
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E_Series_Legacy_controller_locks_down_with_status_of_Memory_Parity_Error_and_7_segment_code_sequence
      Controller locks down with LED code of OE L2 CF dx (x: location of the cache DIMM). This code translates to persistent processor/cache DIMM ECC errors. SANtricity System Manager or support bundle repo...Controller locks down with LED code of OE L2 CF dx (x: location of the cache DIMM). This code translates to persistent processor/cache DIMM ECC errors. SANtricity System Manager or support bundle reports controller in Memory parity error status. Status: Memory parity error Major event log and exception log if available (excLogShow) indicate the controller encountered correctable memory ECC errors before it failed. Description: Recoverable error in processor memory detected/corrected
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/Controller_encountered_hardware_issues_on_Cache_DIMM__Cf_Cx_Component_Failure_Cache_DIMM
      Applies to All E-Series hardware platforms. Issue One or both controllers has detected: CF Cx Operational failure of Cache DIMM. x being the location for when there are separate processor and data cac...Applies to All E-Series hardware platforms. Issue One or both controllers has detected: CF Cx Operational failure of Cache DIMM. x being the location for when there are separate processor and data cache memory systems.