Viewing the error log Analyzing the error log Describing the fields in the error log

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

Steps

To view the full contents of each error log entry it is necessary to perform the following steps:

  1. Use the svctask dumperrlog command to create dump file that contains the current error log data.
  2. Use svcinfo lserrlogdumps to determine the the name of the dump file that you have just created.
  3. Use Secure copy to copy the dump file to the master console.
Result

The file can then be displayed with a text viewer.

Example

Figure 170 shows an example of an error log entry that might be displayed:

Figure 170. Example of an error log entry when you use the command-line interface
Error Log Entry 21
  Node Identifier       : node3
  Object Type           : adaptor
  Object ID             : 1
  Sequence Number       : 174
  Root Sequence Number  : 174
  First Error Timestamp : Tue Apr 22 16:02:18 2003
                        : Epoch + 1051027338 
  Last Error Timestamp  : Tue Apr 22 16:02:18 2003
                        : 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 log using the SAN Volume Controller console. The error 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 171 shows an example of an error log summary that is displayed when you select the type of information that you want.

Figure 171. Example of an Error Log Summary
Example of an Error 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 63 describes the meaning of the information in the type field.

Table 63. Descriptions of Log Entry Icons
Icon Description
The Error icon indicates that this log entry requires service activity. You should select Run Maintenance Procedures from the Service and Maintenance menu to start the repair activity,
The Fixed icon indicates that a problem existed but 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.

Figure 172 shows an example of an error log entry you see when you use the SAN Volume Controller Web interface.

Figure 172. Example of an error log entry when you use the Web interface
Example of an error log entry when you use the Web interface
Related topics Analyzing the error log Describing the fields in the error log

(C) Copyright International Business Machines Corporation 2003, 2004