Logging Debug Events in the MD-CLI

The following MD-CLI commands log debug events to an active CLI session.

    configure
        — log
            — log-id [id] string
                — source
                    — debug boolean
                — destination
                    — cli 
                        — max-entries number

The following is an example configuration for debug events that are stored in destination CLI log identifier "7". The log entries wrap at 50 entries (the configured value of max-entries).

(ex)[configure log]
A:admin@node-2# log-id "7"

*(ex)[configure log log-id "7"]
A:admin@node-2# source debug

*(ex)[configure log log-id "7"]
A:admin@node-2# destination cli max-entries 50

*(ex)[configure log log-id "7"]
A:admin@node-2# info
    source {
        debug true
    }
    destination {
        cli {
            max-entries 50
        }
    }

After the commit command is issued to include the log in the running configuration, the following tools command can be executed in the CLI session that is intended to display outputs of the debug events. See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Clear, Show, and Tools Command Reference Guide for more information about the tools command.

[/]
A:admin@node-2# tools perform log subscribe-to log-id "7"

Debug events can be displayed using the show log command and cleared using the clear log command.

[/]
A:admin@node-2# show log log-id "7"
===============================================================================
Event Log 7 log-name 7
===============================================================================
Description : (Not Specified)
Log contents  [size=50   next event=2  (not wrapped)]

---snip---

[/]
A:admin@node-2# clear log log-id "7"

The following is an example of terminating the output of the logs to the CLI session using the unsubscribe-from command.

[/]
A:admin@node-2# tools perform log unsubscribe-from log-id "7"