Error Reporting and Message Logging
Individual file system commands will report application specific errors as part
of their normal output. ERRLOG messages will be generated on the following
events:
■
A physical file system becomes full
A user attempts to overwrite or remove a read-only system file
■
■
File system operation fails
■
Any other catastrophic failure
The 8100fl switch logs system error messages by default. This section dis
cusses how you can control where these messages are stored, how many
messages are kept, what level of severity the messages will be, and how to
turn off logging.
Disabling/Enabling Message Logging
To disable message logging, enter:
ProCurve#no logging terminal
To re-enable message logging if it has been disabled, enter:
ProCurve#logging terminal [all]
To modify the logging settings, instead of specifying all, specify the name of
the process or device from the supported list of logging terminal options.
Specifying Logging Locations
You can specify that system logs be sent to the system console, local logs, or
in a Unix-style syslog format.
When you configure messages to be sent to the console and the logging
process is enabled, the messages are displayed on the console after the
process that generated them has finished. When the logging process is dis
abled, messages are sent only to the console.
The syslog format is compatible with 4.3 Berkeley Standard Distribution
(BSD) Unix.
Performance Monitoring
Error Reporting and Message Logging
19-7