Operation Manual

System Log Commands
System Log Commands
24 – 519
● Events at the error level and higher are logged to the MX console.
● Events at the error level and higher are logged to the MX system buffer.
● Trace logging is enabled, and debug-level output is stored in the MX trace buffer.
Access Enabled.
History
Version 1.0 Command introduced.
Version 4.2 Option port added.
Usage Using the command with only enable or disable turns logging on or off for the target at
all levels. For example, entering set log buffer enable with no other keywords turns on logging
to the system buffer of all facilities at all levels. Entering set log buffer disable with no other
keywords turns off all logging to the buffer.
Examples To log only emergency, alert, and critical system events to the console, type the
following command:
MX# set log console severity critical enable
success: change accepted.
See Also
● show log config on page 24-521
● clear log on page 24-517
set log mark
Configures MSS to generate mark messages at regular intervals. The mark messages indicate the
current system time and date. Trapeze Networks can use the mark messages to determine the
approximate time when a system restart or other event causing a system outage occurred.
Syntax set log mark [enable | disable] [severity level]
[interval interval]
Defaults Mark messages are disabled by default. When messages are enabled, MSS generates a
message at the notice level once every 300 seconds by default.
Access Enabled.
History Introduced in MSS Version 4.1.
Examples The following command enables mark messages:
MX# set log mark enable
enable Enables the mark messages.
disable Disables the mark messages.
severity level Log severity at which the messages are logged:
❑ emergency
❑ alert
❑ critical
❑ error
❑ warning
❑ notice
❑ info
❑ debug
interval interval Interval at which MSS generates the mark messages. You can specify from 1 to
2147483647 seconds.