Note
This command and its syntax is common to both the User Executable and Privilege Executable configuration modes.logging monitor {<0-7>|alerts|critical|debugging|emergencies|errors|informational|notifications|warnings}
logging monitor {<0-7>|alerts|critical|debugging|emergencies|errors|informational|notifications|warnings}
monitor | Sets the terminal lines logging levels. The logging severity levels can
be set from 0 - 7. The system configures default settings, if no logging
severity level is specified.
Note: Before configuring
the message logging level, ensure logging module is enabled. To enable
message logging, in the device‘s configuration mode, execute the logging
> on command. Message logging can also be enabled on a profile. All
devices using the profile will have message logging
enabled.
|
ap510-133B38(config-device-94-9B-2C-13-3B-38)#logging on
ap510-133B38>logging monitor debugging
ap510-133B38>show logging Logging module: enabled Aggregation time: disabled Console logging: level warnings Monitor logging: disabled Buffered logging: level warnings Syslog logging: level warnings Facility: local7 Log Buffer (103 bytes): Aug 23 13:01:21 2019: %USER-3-ERR: Unspec[1824]: Unable to send message to subscribe for event rim_up. ap510-133B38>
no (user executable 'no' commands | Resets terminal lines logging levels in the User Executable context |
no (privi executable 'no' commands |
Resets terminal lines logging levels in the Privi Executable context |