There are many logs that record error and status information.
Examine the following logs: daemon log, SDR configuration log, external hardware daemon communication log, S1 communication log, hardware monitor log, and SP hardware log.
This file contains the daemon's error information. This file is located on the control workstation in /var/adm/SPlogs/spmon/s70d/s70d.frame.log.ddd for the s70 daemon where ddd is the Julian date, and frame is the frame number of the server.
This log file contains information from the SDR configuration command SDR_config. The SDR_config command is automatically run under these conditions:
If SDR_config detects system configuration problems, error messages are written to the file located on the control workstation in: /var/adm/SPlogs/sdr/SDR_config.log.
This file contains information on data sent to, and received from, the server's service processor. This file must be created manually on the control workstation as /var/adm/SPlogs/spmon/s70d/s70d.frame.sami_dump for the s70 daemon, where frame is the frame number of the server.
This log file contains informational, error and debug information. Examples of informational messages are timestamps for when the daemon started or stopped. An example of an error is the failure of the daemon to open a file. An example of debug information (enabled by the hmadm command), is a list of commands sent from the System Monitor (hardmon) to external hardware daemon.
For the s70 daemon, create this log whenever the s70 hardware appears to not be communicating with the s70 daemon. Issue this command:
hmadm -d sami setd
Issue this command to stop the log:
hmadm -d sami cleard
This log file contains information on data sent to, and received from, the server's serial port. This file must be created manually on the control workstation. This file is located in: /var/adm/SPlogs/spmon/s70d/s70d.frame.s1data_dump, where frame is the frame number of the server.
Create this log whenever the s70 hardware serial interface appears to not be communicating with the s70 daemon. Issue this command:
hmadm -d s1data setd
Issue this command to stop the log:
hmadm -d s1data cleard
This log file contains informational, error, and debug information. Examples of informational messages are timestamps for when daemons are started or stopped. An example of an error is a communication error between the System monitor (hardmon) an external hardware daemon. An example of debug information (enabled by the hmadm command), is a list of requests sent from the System monitor (hardmon) to an external hardware daemon. This file is located on the control workstation. The file is located in: /var/adm/SPlogs/spmon/hmlogfile.ddd, where ddd is the Julian date.
This log file contains information generated by system daemons, including hardware errors. SP hardware problems have a resource name of sphwlog. This file is located on the control workstation in: /var/adm/SPlogs/SPdaemon.log.