logmgr monitor
Logs are not monitored by default.
Privileged EXEC mode
If the logs are generated using the debug commands, you must use the exact module names and sub-module names as listed in the log manager hierarchy.
If the logs are generated using distributed
logger (dlogger), the modules and sub-modules must be specified based on the mapping
of distributed logger modules to log manager displayed in the show dlogger module filter
lm-map command output.
This command enables the monitoring mode and simultaneously blocks the command line interface. You must press Ctrl+C to cancel the monitoring mode.
Monitoring the real-time updates to the logs is applicable only on local units.
The following example displays real-time updates to the specific logs.
device# logmgr monitor infra:stacking:all:all ==> /logmgr/logs//infra/stacking_low_tmp.log <== Jun 02 22:36:08:026672:info:infra:stacking:1:283283157943040: T=7m39.4: Election, I cc4e.248b.a8a8 was alone --> active, ID=1, pri=128, 2U(1-2), A=u1, nbr#=1 1,reason: u2: port-up, Jun 02 22:36:08:921219:debug:infra:stacking:1:283871568462592: Detect stack unit 2 has different startup config flash, will synchronize it Jun 02 22:36:08:921496:debug:infra:stacking:1:283871568462592: T=7m40.3: Synchronize webauth files to u2 Jun 02 22:36:10:906739:info:infra:stacking:1:285465001329408: T=7m42.3: Election, I cc4e.248b.a8a8 was active, no change, ID=1, pri=128, 2U(1-2), A=u1, nbr#=1 1,reason: u1: stk-po-chg, Jun 02 22:36:11:937383:debug:infra:stacking:1:286401304199936: T=7m43.3: Synchronize startup config to u2 Jun 02 22:37:11:627414:info:infra:stacking:1:331356726887168: T=8m43.0: Assigned unit 2 to be standby ==> /logmgr/logs//infra/stacking_low_tmp.log <== Jun 02 23:31:29:779689:debug:infra:stacking:1:2405005592101632: T=1h3m1.1: Unit 1 loses all neighbors. Jun 02 23:31:29:784160:debug:infra:stacking:1:2405005592101632: T=1h3m1.1: Active unit 1 deletes u2 but keeps its static config.
| Release version | Command history |
|---|---|
| 09.0.00 | This command was introduced. |