The purpose of the discussion is to explain how to use the CLI tool framework to develop CLI-based server tools such as LSP ping. MPLS Manager’s LSP ping serves as an example throughout the discussion.

Note:

LSP ping is available for Layer 2 and Layer 3 VPNs and is applicable to label switched paths (LSPs) that are constructed by using the Label Distribution Protocol.

The CLI tool framework consists of a Global Manager component and one or more Domain Manager components. The framework is responsible for setting up Telnet, SSH1, or SSH2 command line interface (CLI) connections to devices in the managed network. The connections are set up when running CLI-based server tools.

Server tools are programs that are invoked by a user through a Global Console that is attached to the Global Manager. Upon right-clicking a notification, a topology object, or a map object to display a pop-up menu, a user may invoke any of the server tools that are listed on the menu.

Although most server tools are invoked and executed on the host where the Global Manager is running, CLI-based server tools are different in the sense that they are invoked on the host where the Global Manager is running but executed on the host where an underlying Domain Manager is running. The LSP ping server tools that are described in the VMware Smart Assurance MPLS Management Suite User Guide demonstrate this type of behavior.