Applies to NetApp E-Series E-series controller repports "Internal configuration database file system corrupted" inside the MEL (Major Event Log), the controller may be in a failed state. Event type: 6...Applies to NetApp E-Series E-series controller repports "Internal configuration database file system corrupted" inside the MEL (Major Event Log), the controller may be in a failed state. Event type: 6105 Event category: Internal Event needs attention: false Event send alert: false Event visibility: true Description: Internal configuration database file system corrupted Event specific codes: 0/0/0 Component type: Controller Component location: Shelf 99, Bay A Logged by: Controller in bay A
Applies to All E-Series Platforms Issue Major Event Log shows "Sense 6/3f/1 = Unit Attention - Microcode has been changed" events when system is already on latest drive firmware and no recent microcod...Applies to All E-Series Platforms Issue Major Event Log shows "Sense 6/3f/1 = Unit Attention - Microcode has been changed" events when system is already on latest drive firmware and no recent microcode changes have happened.
Applies to All E-series controller platforms All E-series firmware revisions An Alert in the Major Event Log(MEL) of the E-series Support data collection. Indicates that there are intermittent problem...Applies to All E-series controller platforms All E-series firmware revisions An Alert in the Major Event Log(MEL) of the E-series Support data collection. Indicates that there are intermittent problems with the Interconnect Module (ICC) ICC problems result in synchronization and communication issues between controllers Example of MEL Event: Description: Discrete lines diagnostic failure Priority: Critical Event Number: 0x2836 Please contact NetApp Technical Support for further assistance.
These events are stored in the configuration database and can be retrieved by the CLI and GUI. Conditions that require logging an event are relatively rare and therefore the MEL is used as a long-term...These events are stored in the configuration database and can be retrieved by the CLI and GUI. Conditions that require logging an event are relatively rare and therefore the MEL is used as a long-term history of the system. Location Information: Each MEL event identifies what device(s) are involved under “Component location” and which controller(s) logged the event under "Logged by"
