Managing Logs

The switch may generate messages in response to events, faults, or errors occurring on the platform as well as changes in configuration or other occurrences. These messages are stored both locally on the platform and forwarded to one or more centralized points of collection for monitoring purposes as well as long term archival storage. Local and remote configuration of the logging capability includes filtering of messages logged or forwarded based on severity and generating component.

The in‐memory log stores messages in memory based upon the settings for message component and severity. On stackable systems, this log exists only on the management unit. Other platforms in the stack forward their messages to the management unit log. Access to in‐memory logs on other than the management unit is not supported.

Buffered Log Configuration

The buffered log stores messages in memory based upon the settings for message component and severity. Use the Buffered Log Configuration page to set the administrative status and behavior of logs in the system buffer.

To access the Buffered Log Configuration page, click System > Log > Buffered Log Configuration in the navigation menu.

buffered_log_config

Buffered Log Configuration Fields

Field	Description
Admin Status	Determines whether to log messages. Enable: Enables system logging. Disable: Prevents the system from logging messages.
Behavior	Indicates the behavior of the log when it is full. Wrap: When the buffer is full, the oldest log messages are deleted as the system logs new messages. Stop on Full: When the buffer is full, the system stops logging new messages and preserves all existing log messages.

Field

Description

Admin Status

Determines whether to log messages.

Enable: Enables system logging.
Disable: Prevents the system from logging messages.

Behavior

Indicates the behavior of the log when it is full.

Wrap: When the buffer is full, the oldest log messages are deleted as the system logs new messages.
Stop on Full: When the buffer is full, the system stops logging new messages and preserves all existing log messages.

If you change the buffered log settings, click Submit to apply the changes to the system. To preserve the changes after a system reboot, you must perform a save.

Buffered Log

Use the Buffered Log page to view the log messages in the system buffer. The newest messages are displayed at the bottom of the page. To access the Buffered Log page, click System > Log > Buffered Log in the navigation menu.

buffered_logs

Buffered Log Fields

Field	Description
Total Number of Messages	Shows the number of buffered messages the system has logged. Only the 128 most recent entries are displayed on the page.

The rest of the page displays the buffered log messages. The following example shows a log message for a nonstacking system:

<15>Aug 24 05:34:05 STK0 MSTP[2110]: mspt_api.c(318) 237 %% Interface 12 transitioned to root state on message age timer expiry

This log message has a severity level of 7 (15 mod 8), which is a debug message. The system is not stacked (STK0). The message was generated by the MSTP component running in thread ID 2110. The message was generated on August 24 05:34:05 by line 318 of file mstp_api.c. This is the 237th message logged.

The following example shows a log message generated on a system that supports stacking:

<15>Aug 24 05:34:05 0.0.0.01 MSTP[2110]: mspt_api.c(318) 237 %% Interface 12 transitioned to root state on message age timer expiry

This log message has a severity level of 7 (15 mod 8), which is a debug message. The message was generated by the MSTP component running in thread id 2110. The message was generated on August 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 unit number 1.

Click Refresh to update the screen and associated messages.

Command Logger Configuration

Use the Command Logger Configuration page to enable the system to log all CLI commands issued on the system. The command log messages are interleaved with the other system logs messages.

To access the Command Logger Configuration page, click System > Log > Command Logger Configuration in the navigation menu.

command_logger

Command Logger Configuration Fields

Field	Description
Admin Mode	This field determines whether to log CLI commands in the system log file. Enable: The system logs CLI commands. The commands appear in messages on the Buffered Log page. Disable: This system does not log CLI commands.

Field

Description

Admin Mode

This field determines whether to log CLI commands in the system log file.

Enable: The system logs CLI commands. The commands appear in messages on the Buffered Log page.
Disable: This system does not log CLI commands.

If you change the administrative mode, click Submit to apply the change to the system.

Console Log Configuration

Use the Console Log Configuration page to control logging to any serial device attached to the switch.

To access the Console Log Configuration page, click System > Log > Console Log Configuration in the navigation menu.

console_log

Console Log Configuration Fields

Field	Description
Admin Status	From the menu, select whether to enable or disable console logging. The default is disabled. Enabled: Prints log messages to the device attached to the switch serial port. Disabled: Log messages do not print to the device attached to the switch serial port.
Severity Filter	Use the menu to select the severity of the logs to print to the console. Logs with the severity level you select and all logs of greater severity print. The default severity level is Alert(1). The severity can be one of the following levels: Emergency (0): The highest level warning level. If the device is down or not functioning properly, an emergency log is saved to the device. Alert (1): The second highest warning level. An alert log is saved if there is a serious device malfunction, such as all device features being down. Critical (2): The third highest warning level. A critical log is saved if a critical device malfunction occurs, for example, two device ports are not functioning, while the rest of the device ports remain functional. Error (3): A device error has occurred, such as if a port is offline. Warning (4): The lowest level of a device warning. Notice (5): Provides the network administrators with device information. Informational (6): Provides device information. Debug (7): Provides detailed information about the log. Debugging should only be entered by qualified support personnel.

Field

Description

Admin Status

From the menu, select whether to enable or disable console logging. The default is disabled.

Enabled: Prints log messages to the device attached to the switch serial port.
Disabled: Log messages do not print to the device attached to the switch serial port.

Severity Filter

Use the menu to select the severity of the logs to print to the console. Logs with the severity level you select and all logs of greater severity print. The default severity level is Alert(1). The severity can be one of the following levels:

Emergency (0): The highest level warning level. If the device is down or not functioning properly, an emergency log is saved to the device.
Alert (1): The second highest warning level. An alert log is saved if there is a serious device malfunction, such as all device features being down.
Critical (2): The third highest warning level. A critical log is saved if a critical device malfunction occurs, for example, two device ports are not functioning, while the rest of the device ports remain functional.
Error (3): A device error has occurred, such as if a port is offline.
Warning (4): The lowest level of a device warning.
Notice (5): Provides the network administrators with device information.
Informational (6): Provides device information.
Debug (7): Provides detailed information about the log. Debugging should only be entered by qualified support personnel.

Event Log

Use the Event Log page to display the event log, which is used to hold error messages for catastrophic events. After the event is logged and the updated log is saved in flash memory, the switch will be reset. The log can hold at least 2,000 entries (the actual number depends on the platform and OS), and is erased when an attempt is made to add an entry after it is full. The event log is preserved across system resets.

To access the Event Log page, click System > Log > Event Log in the navigation menu.

event_log

Event Log Fields

Field	Description
Entry	The number of the entry within the event log. The most recent entry is first.
Type	Displays Event for every task performed on the node.
Filename	The TejNOS-EN source code filename identifying the code that detected the event.
Line	The line number within the source file of the code that detected the event.
Task ID	The OS‐assigned ID of the task reporting the event.
Code	The event code passed to the event log handler by the code reporting the event.
Time	The time the event occurred, measured from the previous reset.

Click Refresh to update the screen and associated messages.

Hosts Log Configuration

Use the Host Log Configuration page to configure remote logging hosts where the switch can send logs. To access the Host Log Configuration page, click System > Log > Host Log Configuration in the navigation menu.

host_log_config

After you add a logging host, the screen displays additional fields indicated in the figure below:

host_log_config2

Host Log Configuration Fields

Field	Description
Host	Select a host from the list of hosts that have been configured to receive log messages. Select Add to add a new host, or select the IP address of an existing host to view or change the settings.
IP Address or Hostname	Enter the IP address or hostname of the host configured for syslog.
IP Address Type	Select the form of the address entered above: IPv4: The address is specified in standard dot notation. DNS: The address is specified as a host name.
Status	Shows whether the remote logging host is currently active.
Port	Identifies the port on the host to which syslog messages are sent. The default port is 514. Specify the port in the text field.
Severity Filter	Use the menu to select the severity of the logs to send to the logging host. Logs with the selected severity level and all logs of greater severity are sent to the host. The default severity level is Alert(1). The severity can be one of the following levels: Emergency (0): The highest level warning level. If the device is down or not functioning properly, an emergency log is saved to the device. Alert (1): The second highest warning level. An alert log is saved if there is a serious device malfunction, such as all device features being down. Critical (2): The third highest warning level. A critical log is saved if a critical device malfunction occurs, for example, two device ports are not functioning, while the rest of the device ports remain functional. Error (3): A device error has occurred, such as if a port is offline. Warning (4): The lowest level of a device warning. Notice (5): Provides the network administrators with device information. Informational (6): Provides device information. Debug (7): Provides detailed information about the log. Debugging should only be entered by qualified support personnel.

Adding a Remote Logging Host

Use the following procedures to add, configure, or delete a remote logging host.

From the Host field, select Add to add a new host, or select the IP address of an existing host to configure the host. If you are adding a new host, enter the IP address of the host in the IP Address field and click Submit. The screen refreshes, and additional fields appear.
In the Port field, type the port number on the remote host to which logs should be sent.
Select the severity level of the logs to send to the remote host.
Click Submit to apply the changes to the system.

Deleting a Remote Logging Host

To delete a remote logging host from the configured list, select the IP address of the host from the Host field, and then click Delete.

Persistent Log Configuration

The persistent log is stored in persistent storage, which means that the log messages are retained across a switch reboot.

NOTE: Some platforms do not support persistent logging. If your system does not support persistent logging, links to the Persistent Log Configuration and Persistent Log page are not present in the navigation menu.

The first log type is the system startup log. The system startup log stores the first N messages received after system reboot. This log always has the log full operation attribute set to stop on full and can store up to 32 messages.
The second log type is the system operation log. The system operation log stores the last N messages received during system operation. This log always has the log full operation attribute set to overwrite. This log can store up to 1000 messages.

Either the system startup log or the system operation log stores a message received by the log subsystem that meets the storage criteria, but not both. In other words, on system startup, if the startup log is configured, it stores messages up to its limit. The operation log, if configured, then begins to store the messages.

The system keeps up to three versions of the persistent logs, named <FILE>1.txt, <FILE>2.txt, and <FILE>3.txt. Upon system startup, <FILE>3.txt is removed, <FILE>2.txt is renamed <FILE>3.txt, <FILE>1.txt is renamed <FILE>2.txt, <FILE>1.txt is created and logging begins into <FILE>1.txt. (Replace <FILE> in the above example to specify olog for the operation log and slog for the startup log.)

The local persistent logs can be retrieved through the Web or CLI, or through xmodem over the local serial cable. To access the Persistent Log Configuration page, click System > Log > Persistent Log Configuration in the navigation menu.

persistent_log_config

Persistent Log Configuration Fields

Field	Description
Admin Status	Select whether to enable or disable persistent logging. The default is disabled. Enabled: Prints log messages to the device attached to the switch serial port. Disabled: Log messages do not print to the device attached to the switch serial port.
Severity Filter	Use the menu to select the severity of the logs to print to the console. Logs with the severity level you select and all logs of greater severity print. The default severity level is Alert(1). The severity can be one of the following levels: Emergency (0): The highest level warning level. If the device is down or not functioning properly, an emergency log is saved to the device. Alert (1): The second highest warning level. An alert log is saved if there is a serious device malfunction, such as all device features being down. Critical (2): The third highest warning level. A critical log is saved if a critical device malfunction occurs, for example, two device ports are not functioning, while the rest of the device ports remain functional. Error (3): A device error has occurred, such as if a port is offline. Warning (4): The lowest level of a device warning. Notice (5): Provides the network administrators with device information. Informational (6): Provides device information. Debug (7): Provides detailed information about the log. Debugging should only be entered by qualified support personnel.

Field

Description

Admin Status

Select whether to enable or disable persistent logging. The default is disabled.

Enabled: Prints log messages to the device attached to the switch serial port.
Disabled: Log messages do not print to the device attached to the switch serial port.

Severity Filter

Emergency (0): The highest level warning level. If the device is down or not functioning properly, an emergency log is saved to the device.
Alert (1): The second highest warning level. An alert log is saved if there is a serious device malfunction, such as all device features being down.
Critical (2): The third highest warning level. A critical log is saved if a critical device malfunction occurs, for example, two device ports are not functioning, while the rest of the device ports remain functional.
Error (3): A device error has occurred, such as if a port is offline.
Warning (4): The lowest level of a device warning.
Notice (5): Provides the network administrators with device information.
Informational (6): Provides device information.
Debug (7): Provides detailed information about the log. Debugging should only be entered by qualified support personnel.

Persistent Log

Use the Persistent Log page to view the persistent log messages.

To access the Persistent Log page, click System > Log > Persistent Log in the navigation menu.

persistent_logs

Persistent Log Fields

Field	Description
Total Number of Messages	Shows the number of persistent messages the system has logged.

The rest of the page displays the log messages. The following example shows a log message for a non-stacking system:

<15>Aug 24 05:34:05 STK0 MSTP[2110]: mspt_api.c(318) 237 %% Interface 12 transitioned to root state on message age timer expiry

Syslog Configuration

Use the Syslog Configuration page to allow the switch to send log messages to the remote logging hosts configured on the system. To access the Syslog Configuration page, click System > Log > Syslog Configuration in the navigation menu.

syslog_config

Syslog Configuration Fields

Field	Description
Admin Status	Specifies whether to send log messages to the remote syslog hosts configured on the switch: Enable: Messages will be sent to all configured hosts (syslog collectors or relays) using the values configured for each host. Disable: Stops logging to all syslog hosts. Disable means no messages will be sent to any collector/relay.
Local UDP Port	Specifies the port on the switch from which syslog messages are sent. The default port is 514.
Messages Received	The number of messages received by the log process. This includes messages that are dropped or ignored.
Messages Dropped	The number of messages that could not be processed due to error or lack of resources.
Messages Relayed	The number of messages forwarded by the syslog function to a syslog host. Messages forwarded to multiple hosts are counted once for each host.

If you make any changes to the page, click Submit to apply the change to the system.