Seq no:time stamp: %facility-severity-MNEMONIC:description So is the difference that logging monitor logs are in the syntax of a syslog syntax i.e. If logging monitor 7 is set, then it would also log the debug outputs, right. I would have done it, but packet tracer doesn't accept logging monitor command. The output generated in that telnet session would be shown thanks to terminal monitor command, and in the back end logging monitor what would it be doing at this time. both terminal monitor and logging monitor turned on in a telnet session. So if logging monitor is tuned on, too, which is disabled by default on vty lines, just like terminal monitor, what would happen? So "debug ip icmp" with terminal monitor turned on in telnet session, would show the output. Logging monitor command doesn't work in packet tracer, right. So the severity level of terminal display can be different from the severity level of messages sent to a syslog server, different from the severity level of messages sent to the logging buffer, and different from the severity level of messages sent to the console. The function of logging monitor is to be able to control the severity level of messages displayed to a terminal session. Terminal monitor enables the display (and terminal no monitor disables the display).
By default a terminal session does not display syslog messages.
The function of terminal monitor is to enable the display of syslog messages on a terminal session (vty session).
Or if I were checking on the operation of an access list where some of the entries included the log parameter, I might use terminal monitor to be able to see what the access list was logging. If I were troubleshooting an issue about one of the interfaces which was not working correctly I might use terminal monitor to see log messages indicating when the interface state changed to down, or back to up. While looking at debug output is certainly one use of terminal monitor it is not the only use for terminal monitor.
0 kommentar(er)
