Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 9 results
    • 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/Potential_E-Series_system_performance_degradation_during_SSD_internal_NAND_recovery
      Users may experience performance degradation during internal die (NAND) recovery. An SSD drive is composed of many dies (NANDs) that are equal in size. The size of a die (NAND) may vary depending on t...Users may experience performance degradation during internal die (NAND) recovery. An SSD drive is composed of many dies (NANDs) that are equal in size. The size of a die (NAND) may vary depending on the drive model. Drive returned check condition with SENSE data of 1/18/0 and/or 1/18/ff indicate the drive is undergoing an internal recovery (reconstruction) of a die. The drive returned check conditions can be found in the E-Series system event log: Description: Drive returned CHECK CONDITION
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E_Series_controller_reboots_with_DoorBell_Fault_ID__2651_Machine_Check
      Applies to NetApp E-Series E5400 NetApp E-Series E5500 NetApp E-Series E5600 Issue Controller reboots with the following panic string in the exception log (excLogShow): <date>-<time> (IOSched): PANIC:...Applies to NetApp E-Series E5400 NetApp E-Series E5500 NetApp E-Series E5600 Issue Controller reboots with the following panic string in the exception log (excLogShow): <date>-<time> (IOSched): PANIC: clearDoorbell: IOCid:<iocid> Fault TaskExit doorBell: x40002651:, FWVER: <Firmware version>
    • https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/NET_SETUP_ERROR_reported_in_the_Recovery_Guru
      Applies to All E-Series Controllers All E-Series Firmware Issue NET_SETUP_ERROR is reported in the Recovery Guru Indicates an Ethernet configuration conflict, where both controllers have the same subn...Applies to All E-Series Controllers All E-Series Firmware Issue NET_SETUP_ERROR is reported in the Recovery Guru Indicates an Ethernet configuration conflict, where both controllers have the same subnet
    • https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/Incomplete_battery_learn_cycle_reported_in_the_MEL
      Applies to Controller: 26x0 Firmware: 07.80.55.00 Issue The Major Event Log (MEL) contains entries for event type 730F: Incomplete battery learn cycle.
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/Replaced_drive_does_not_start_reconstruction_or_copyback_displays_unassigned
      Applies to NetApp E-Series Issue The replaced drive does not start reconstruction or copyback and displays unassigned.
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/What_are_the_Default_Management_Port_IP_addresses_available_on_E_Series_controllers
      The default management port IP addresses for each controller is shown below: Note: Default IP addresses are in the form 192.168.XXX.10Y, where: Default IP addresses for all platforms running 11.60.2 a...The default management port IP addresses for each controller is shown below: Note: Default IP addresses are in the form 192.168.XXX.10Y, where: Default IP addresses for all platforms running 11.60.2 and later, or EF600 running 11.60 or later: XXX = 128 is the first port and 129 is the second port on a controller. Y = 1 is for controller A and 2 is for controller B. Port 2 on the controllers is reserved for Customer Support use only.
    • https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/Discrete_lines_diagnostic_failure
      Applies to Controller: Any type can be applicable Firmware Version: Any version pre-LSIP200662533 (not yet fixed) is applicable This issue is fixed in CFW 8.20.20.xx+ and 8.25.07.xx+. Issue Discrete l...Applies to Controller: Any type can be applicable Firmware Version: Any version pre-LSIP200662533 (not yet fixed) is applicable This issue is fixed in CFW 8.20.20.xx+ and 8.25.07.xx+. Issue Discrete line diagnostic failure event observed in the MEL. The MEL event 'Discrete lines diagnostic failure' is reported against both controllers, and is then resolved on both within 13 seconds.
    • https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/Controller_encountered_persistent_data_protection_errors_OE__Operational_Error_L4__Persistent_data_protection_errors
      Applies to All E-Series hardware platforms Issue One or both controllers could have 7 segment code: OE L4. There could also be on controller at OE L4 and the alternate at OS SD. OE L4 can be identifie...Applies to All E-Series hardware platforms Issue One or both controllers could have 7 segment code: OE L4. There could also be on controller at OE L4 and the alternate at OS SD. OE L4 can be identified through excLogShow: EXAMPLE: ---- Log Entry #20 OCT-04-2014 08:41:36 PM ---- VDD/HDD PI ERROR THRESHOLD EXCEEDED