Viewing the error event log

You can view the error event log by using the SAN Volume Controller command-line interface (CLI) or the SAN Volume Controller Console.

Perform the following steps to view the full contents of each error-event log entry using the CLI:

Dump the contents of the error log to a file.
1. Issue the svctask dumperrlog command to create a dump file that contains the current error-event log data.
2. Issue the svcinfo lserrlogdumps command to determine the name of the dump file that you have just created.
3. Issue the secure copy command (scp) to copy the dump file to the IBM® System Storage® Productivity Center.
View the file with a text viewer after the dump file is extracted from the cluster.

Figure 1 shows an example of an error-event log entry that might be displayed:

Figure 1. Example of an error-event log entry

Error Log Entry 21
  Node Identifier       : node3
  Object Type           : adaptor
  Object ID             : 1
  Sequence Number       : 174
  Root Sequence Number  : 174
  First Error Timestamp : Tue Aug 23 16:02:18 2005
                        : Epoch + 1051027338 
  Last Error Timestamp  : Tue Aug 23 16:02:18 2005
                        : Epoch + 1051027338 
  Error Count           : 1
  Error ID              : 73003 : More/Less fibre channel ports operational
  Error Code            : 1060 : Fibre Channel ports not operational
  Status Flag           : UNFIXED
  Type Flag             : ERROR CAT 1

02 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

You can also view the error event log using the SAN Volume Controller Console. The error event log contains a large number of entries, but by using this method of viewing the log you can select only the type of information that you need. For example, if you are repairing a fault, you might only want to select Show unfixed errors.

Figure 2 shows an example of an error-event log summary that is displayed when you select the type of information that you want.

Figure 2. Example of an error-event log summary This figure shows an example of an error-event log summary.

Details of each listed error can be displayed by clicking on the sequence number of any record. The Type field contains an icon and a text message to indicate the cause of the log entry. Table 1 describes the meaning of the information in the type field.

Table 1. Descriptions of log entry icons
Icon	Description
	The error icon indicates that this log entry requires service activity. Select Run Maintenance Procedures from the Service and Maintenance menu to start the repair activity.
	The fixed icon indicates that a problem existed, but it has now been resolved. It might have been resolved as a result of service activity, or it might have been resolved as a result of some other action, for example, powering on a missing node.
	The warn icon indicates that some condition has occurred that might have been caused by a temporary problem or by a problem that is external to the SAN Volume Controller, such as an error in a RAID controller. If a specified number of these events occurs in 25 hours, the warning converts to an error. No service action is required on the SAN Volume Controller for this log entry.
	The info icon indicates that the log entry provides information about a configuration change or the state of a command. In some cases, the SAN Volume Controller user might need to take some action based on this information.