Extreme Networks ExtremeWare XOS Command Reference Manual page 324

Commands for Status Monitoring and Statistics
Dates are suppressed altogether by specifying . Dates are displayed as by default.
none mm-dd-yyyy
Severity. A four-letter abbreviation of the severity of the event can be output by specifying
severity
or suppressed by specifying . The default setting is . The abbreviations
on severity off severity on
are: Crit, Erro, Warn, Noti, Info, Summ, Verb, and Data. These correspond to: Critical, Error, Warning,
Notice, Informational, Debug-Summary, Debug-Verbose, and Debug-Data.
Event Names. Event names can be output as the component name only by specifying e
vent-name
and as component and subcomponent name with condition mnemonic by specifying
component
, or suppressed by specifying . The default setting is
event-name condition event-name none
to specify the complete name of the events.
event-name condition
Process Name. For providing detailed information to technical support, the (internal) ExtremeWare
XOS task names of the applications detecting the events can be displayed by specifying .
process-name
The default setting is off.
Process Slot. For providing detailed information to technical support, the slot from which the logged
message was generated can be displayed by specifying . The default setting is off.
process-slot
Process ID. For providing detailed information to technical support, the (internal) ExtremeWare XOS
task identifiers of the applications detecting the events can be displayed by specifying . The
process-id
default setting is off.
Source Line. For providing detailed information to technical support, the application source file
names and line numbers detecting the events can be displayed by specifying s . The default
ource-line
setting is off.
Example
In the following example, the switch generates the identical event from the component SNTP, using
three different formats.
Using the default format for the session target, an example log message might appear as:
05/29/2003 12:15:25.00 <Warn:SNTP.RslvSrvrFail> The SNTP server parameter value
(TheWrongServer.example.com) can not be resolved.
If you set the current session format using the following command:
configure log target session format timestamp seconds date mm-dd-yyyy event-name
component
The same example would appear as:
05/29/2003 12:16:36 <Warn:SNTP> The SNTP server parameter value
(TheWrongServer.example.com) can not be resolved.
To provide some detailed information to technical support, you set the current session format using the
following command:
configure log target session format timestamp hundredths date mmm-dd event-name
condition source-line process-name
The same example would appear as:
May 29 12:17:20.11 SNTP: <Warn:SNTP.RslvSrvrFail> tSntpc: (sntpcLib.c:606) The SNTP
server parameter value (TheWrongServer.example.com) can not be resolved.
324 ExtremeWare XOS 11.0 Command Reference Guide