User Manual
Table Of Contents
- M6100 Web Management User Guide
- Contents
- 1. Getting Started
- 2. Configuring System Information
- 3. Configuring Switching Information
- 4. Routing
- 5. Configuring Quality of Service
- 6. Managing Device Security
- 7. Monitoring the System
- 8. Maintenance
- 9. Help
- A. Default Settings
- B. Configuration Examples
- C. Notification of Compliance
Monitoring the System
507
M6100 Web Management User Guide
Buffered Log Configuration
This log stores messages in memory based upon the settings for message component and
severity. On chassis systems, this log exists only on the top of chassis platform. Other
platforms in the chassis forward their messages to the top of chassis log.
1. A log that is “Disabled” shall not log messages.
A log that is “Enabled” shall log
messages. Enable or Disable logging by selecting the corresponding radio button.
2. Behavior Indicates the behavior of the log when it is full. It can either wrap around or stop
when the log space is filled.
3. Click Update to update the page with the latest information on the switch.
4. Click Clear to clear the buf
fered log in the memory.
Message Log
This help message applies to the format of all logged messages which are displayed for the
message log, persistent log or console log.
Format of the messages
Messages logged to a collector or relay via syslog have an identical format:
• <15>Aug 24 05:34:05 0.0.0.0-1 MSTP[21
10]: mspt_api.c(318) 237 %% Interface 12
transitioned to root state on message age timer expiry.
The above example indicates a message with severity 7(15 mod 8) (debug) on a chassis
and generated by component MSTP running in thread id 2110 on Aug 24 05:34:05 by line
318 of file mstp_api.c. This is the 237th message logged with system IP 0.0.0.0 and
task-id 1.
Format of the messages
• <15>Aug 24 05:34:05 STK0 MSTP[21
10]: mspt_api.c(318) 237 %% Interface 12
transitioned to root state on message age timer expiry.
The above example indicates a user-level message (1) with severity 7 (debug) on a
system that is not a chassis and generated by component MSTP running in thread id










