EvntAgnt log is recorded in the application event log:
→This event does not have any influence on the system, not on SNMP services. Thus no measurement is required.
Source: EvntAgnt
ID: 1003
Description: TraceFileName parameter not located in registry; Default trace file used is .
Source: EvntAgnt
ID: 1015
Description: TraceLevel parameter not located in registry; Default trace level used is 32.
SCSI control error appears in the system event log:
→There is sometimes a case that SCSI control error that has a source of sraq160 appears in the system event log. This symptom occurs when the processing speed of HDDs is slower than the request from the operating system, and the process will be continued properly by the retry function. Since this does not affect any operations, check the detailed data as described below and ignore that log if the data is either “f0030004” or “f0030015”.
However, if the SCSI control error in the detailed data above repeatedly shows either “f0030004” or “f0030015” (more than 10 times a week as an indication), the HDD failure can be occurring. Contact your maintenance service company.
The srabid error log is recorded in the system event log at system startup:
→The following log may be recorded in the system event log at system startup, but there is no problem for operation.
Source: srabid
Type: Error
ID: 300
Description: | CPU board dump harvest failed. |
| Status from Common Code: ErrDumpDoesntExist (0x8123). |
Source: | srabid |
Type: | Error |
ID: | 300 |
Description: | CPU board dump harvest failed. |
| Status from Common Code: ErrMagic (0x8188). |