Local and remote tool scripts

To write the local and remote tool scripts for CLI-based server tools, you must know the capabilities of the particular CLI-capable Domain Manager (MPLS Manager, VMware Smart Assurance Network Protocol Manager for EIGRP, VMware Smart Assurance Network Protocol Manager for IS-IS, and so on) through which the source network device is to be accessed. You must also know the class objects that can be obtained from the source network device.

Because the MPLS Topology Server, not the Global Manager, holds the CLI device-access objects that carry the login credentials, the completion of an LSP Ping request must involve the MPLS Topology Server. Furthermore, because the command line for an LSP Ping request requires an LSP destination address and the corresponding netmask, and because the MPLS Topology Server can determine the corresponding netmask and the Global Manager cannot, the completion of an LSP Ping request must involve the MPLS Topology Server.

The local tool script for the LSP Ping server tool is LSPPing.asl. The remote tool script for the LSP ping server tool is pinglsp-ondemand.asl.

• LSPPing.asl starts a GA_Driver to invoke pinglsp-ondemand.asl on the MPLS Topology Server, and to obtain the ping test results.

• pinglsp-ondemand.asl performs the following tasks:

  • Constructs the ping command for the source Cisco or Juniper network device.

  • Uses the Generic-Telnet-Driver (ACT_PerlScript) to telnet to the source network device and to invoke the ping command from the device.

  • Starts a GA_Driver to obtain the ping test results.

    The ping test results are first saved to a text file and then read by the GA_Driver.