If the error should be analyzed, a diagnostic application is invoked and the error isanalyzed. No testing is done if the diagnostics determine that the error requires aservice action. Instead, it sends a message to your console, or to all systemgroups. The message contains the SRN. Running diagnostics in this mode is similarto using the diag -c, -e, -d device command.To activate the automatic error log analysis feature on systems running AIX as theoperating system, log in as root user (or use CE login) and type the followingcommand:/usr/lpp/diagnostics/bin/diagela ENABLETo disable the automatic error log analysis feature on systems running AIX, log inas root user (or use CE login) and type the following command:/usr/lpp/diagnostics/bin/diagela DISABLEThe diagela program can also be enabled and disabled using the PeriodicDiagnostic Service Aid.Error log analysisThis section provides information on error log analysis.v Error log analysis is the analysis of the AIX error log entries.v Error log analysis is part of the diagnostic applications. The analysis is started byselecting a device from the Diagnostic Selection menu and then using the diagcommand or selecting the Run Error Log Analysis task.v Error log analysis is only performed when running online diagnostics.v Error log analysis is not performed when running standalone diagnostics.v Error log analysis only reports problems if the errors have reached definedthresholds. Thresholds can be from 1 to 100, depending on the error.v Permanent errors do not necessarily mean a part should be replaced.v Automatic Error Log Analysis (diagela) provides the capability to do error loganalysis whenever a permanent hardware error is logged.Log repair actionThe diagnostics perform error log analysis on most resources. The default time forerror log analysis is seven days; however, this time can be changed from 1 to 60days using the Display or Change Diagnostic Run Time Options task.To prevent false problems from being reported when error log analysis is run, repairactions need to be logged whenever a FRU is replaced. A repair action can belogged by using the Log Repair Action task or by running diagnostics in systemverification mode.The Log Repair Action task lists all resources. Replaced resources can be selectedfrom the list, and when Commit (F7 key) is selected, a repair action is logged foreach selected resource.Tasks (service aids)These are tasks that might be available to the JS20 blade server:v Add Resource to Resource Listv AIX Shell Promptv Analyze Adapter Internal Logv Automatic Error Log Analysis and NotificationChapter 8. General AIX and xSeries standalone diagnostic information 63
