Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring the Show Commands

 

Because there are numerous show commands, but only certain ones that each user cares about, it is up to the user to configure the most frequently used show commands in a special IP/MPLSView file. This will allow quick access to these commands via the IP/MPLSView client or browser interface. The default list of commands contains just a few to get you started.

On the IP/MPLSView server, navigate to $WANDL_HOME/db/config where WANDL_HOME is the installation directory (usually /u/wandl). There are two command files: shownodecmds and showvpncmds. The shownodecmds contains general router show commands. The showvpncmds file contains vpn-specific show commands.

With any editor, open the shownodecmds text file. (For VPN-related show commands, open the showvpncmds text file.) It will contain sections like the following:

#Cisco
#Juniper

Each section’s header line includes the hardware vendor, the heading, and the word “comment.” Within the section, each line contains the hardware vendor, the command “name,” and command string.

To add additional show commands, simply copy one of the lines in the same section, and edit just the show command “name” and “command string”. Note that for the command string, you can add multiple parameters as __PARAM1__, __PARAM2__, etc. For these parameterized commands, the user will be prompted to enter in a parameter value when the show command is executed. After you are finished editing the file, save and exit.

Now, if you right-click on a node in the Map window and select Run CLI, you should see your newly entered options listed in the Run CLI Commands Window.

Note that the files in the directory /u/wandl/db/cmdtemplate contain templates specifying which commands to issue immediately after logging in and before running any additional commands and the file /u/wandl/db/config/hardwaretypemapping.csv contains a mapping of recognized device models with their vendors. See Device Library on page 350 for instructions to modify these file via the graphical interface.