If log messages are not seen during a console session, it could be due to console logging being disabled or the logging level being set too low to display certain log messages.
To resolve this issue, perform these steps:
This is sample output from this command:
Switch#show logSyslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns) Console logging: level debugging, 22 messages logged Monitor logging: level debugging, 0 messages logged Buffer logging: level debugging, 22 messages logged File logging: disabled Trap logging: level informational, 26 message lines loggedLog Buffer (4096 bytes):
In this example, the console logging is set to the highest level (debugging), so all log messages should show up in a console session.
For example, to set the console logging level to informational, issue the logging console informational command.
After this command is issued, only informational level messages show up on the console.
Issuing the show logging command on a CatOS switch will not give any information about logging levels, but rather a log history.
This example output is from the show logging command from a CatOS switch:
Console> (enable) show loggingLogging buffer size: 500 timestamp option: enabledLogging history size: 1Logging console: enabledLogging telnet: disabledLogging server: disabled server facility: LOCAL7 server severity: warnings(4)Facility Default Severity Current Session Severity------------- ----------------------- ------------------------cdp 4 4cops 2 2dtp 5 5earl 2 2filesys 2 2gvrp 2 2ip 2 2kernel 2 2mcast 2 2mgmt 5 5mls 5 5pagp 5 5protfilt 2 2pruning 2 2qos 3 3radius 2 2security 2 2snmp 2 2spantree 2 2sys 5 5tac 2 2tcp 2 2telnet 2 2tftp 2 2udld 4 4vtp 2 20(emergencies) 1(alerts) 2(critical)3(errors) 4(warnings) 5(notifications)6(information) 7(debugging)
To disable console logging, issue the set logging console command.
For example, to set the logging level for spanning-tree to debugging, issue the set logging level spantree 7 command.
This sets the level to debugging only for the current session. If the optional default is added to the command, the level remains at debugging in subsequent sessions.
For more information on the configuration of logging, refer to these documents: