The format for naming a CLI log file is:

CLI-<device vendor>-<device name>.txt

Two example CLI log file names are:


Typically, one of four outcomes is recorded in a CLI log file:

  • Outcome 1: Target device does not support Telnet, SSH1, or SSH2; for a target device named “qa-gw15,” an example of this error is:

    Starting to telnet qa-gw15.
    Error: Unable to connect to remote host qa-gw15 : 
       Connection refused
  • Outcome 2: Target device supports Telnet, SSH1, or SSH2, but the login credentials (username, user password, enable password) are incorrect for the device; for a target device named “,” an example of this error is:

    Starting to telnet
    Error: Unable to login to
  • Outcome 3: Target device does not match any CLI device-access group:

    ***Warning: Missing CLI_AccessSetting for <device name>.
  • Outcome 4: Discovery successfully completes, and the MPLS, VPN, and BGP topology objects that are discovered by probing the device are added to the managed topology; for example:

    Starting to telnet qa-vplsce1.

    If debug tracing is enabled, the following new line of information appears as the first line in the CLI log file:

    Information: running the at <device vendor> (for example, CISCO) : <device name> (for example, qa-gw8).

    To enable debug tracing, set the “debug” flag in the BASEDIR/smarts/conf/mpls-t/perl-cli.conf file to a nonzero value. For example:

    $vars{"debug"} = 1;

    The VMware Smart Assurance MPLS Manager Configuration Guide describes the parameters in the perl-cli.conf file and provides instructions for modifying the parameters.