Marking errors as fixed

You can use the management GUI to mark errors as fixed in the error log. This action is only necessary if you fix an error without using the online maintenance procedures. The online procedures automatically mark an error as fixed after a successful repair.

1. Launch the management GUI.
2. Click Monitoring > Events.
3. Select the appropriate filtering to view events.
   The information on the Events panel can be filtered three ways:

   Recommended action (default)

   Shows only the alerts that require attention and have an associated fix procedure. Alerts are listed in priority order and should be fixed sequentially by using the available fix procedures. For each problem that is selected, you can:

   • Run a fix procedure.
   • View the properties.

   Unfixed messages and alerts

   Displays only the alerts and messages that are not fixed. For each entry that is selected, you can:

   • Run a fix procedure on any alert with an error code.
   • Mark an event as fixed.
   • Filter the entries to show them by specific minutes, hours, or dates.
   • Reset the date filter.
   • View the properties.

   Show all

   Displays all event types whether they are fixed or unfixed. For each entry that is selected, you can:

   • Run a fix procedure on any alert with an error code.
   • Mark an event as fixed.
   • Filter the entries to show them by specific minutes, hours, or dates.
   • Reset the date filter.
   • View the properties.

   You can also sort events by time or error code. When you sort by error code, the most serious events, those with the lowest numbers, are displayed first. You can select any event that is listed and select Actions > Properties to view details about the event.

4. Click the event and run any associated fix procedure, if applicable. If a fix procedure is not available for the event, ensure that no further action is necessary and select Mark As Fixed from the Action menu.

   This event log entry for this error is now marked as fixed and it is not be used as part of future event logs.