Loading ...
Loading ...
Loading ...
Monitor the System
394
Insight Managed 28-Port and 52-Port Gigabit Ethernet Smart Cloud Switches
console log. Messages logged to a collector or relay through syslog support the same
format as well.
The following example shows the standard format for a log message:
<14>2017-09-02 16:35:40 10.131.12.183-1 UNKN[2176789276]:
main_login.c(179) 3855 %% HTTP Session 19 initiated for user admin
connected from 10.27.64.122
The number contained in the angle brackets represents the message priority, which is
derived from the following values:
Priority = (facility value × 8) + severity level.
The facility value is usually 1, which means it is a user-level message. Therefore, to
determine the severity level of the message, subtract 8 from the number in the angle
brackets. The sample log message shows a severity level of 6 (informational). For more
information about the severity of a log message, see Manage the Server Log on
page 396.
The message was generated on September 2, 2017, at 5:35:40 p.m. by the switch with
an IP address of 10.131.12.183. The component that generated the message is
unknown, but it came from line 179 of the main_login.c file. This is the 3,855th
message logged since the switch was last booted. The message indicates that the
administrator logged on to the HTTP management interface from a host with an IP
address of 10.27.64.122.
10. To refresh the page with the latest information about the switch, click the Refresh button.
11. To clear the messages from the buffered log in the memory, click the Clear button.
Message Log Format
This topic applies to the format of all logged messages that are displayed for the message
log, persistent log, or console log.
Messages logged to a collector or relay through syslog use an identical format:
• <15>2017-09-02 05:34:05 0.0.0.0-1 MSTP[2110]: mspt_api.c(318)
237%% Interface 12 transitioned to root state on message age timer
expiry.
This example indicates a message with severity 7 (15 mod 8) (debug) on a switch and
generated by component MSTP running in thread ID 2110 on September 2, 2017, at
05:34:05 a.m. 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.
• <15>2017-09-02 06:24:15 STK0 MSTP[2110]: mspt_api.c(318) 237%%
Interface 12 transitioned to root state on message age timer
expiry.
This 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 2110 on
September 2, 2017, at 06:24:15 a.m. by line 318 of file mstp_api.c. This is the 237th
Loading ...
Loading ...
Loading ...