Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
[+] Expand All
[-] Collapse All

No index entries found.

Related Documentation

    Detailed Procedures

    Run CLI

    The Run CLI feature allows users to run a set of commands on a set of routers in batch.

    1. Right-click on a node on the Map, and choose Run CLI. The Run CLI Commands Window will appear.

      Figure 89: Show Command Window

      Show Command Window
    2. This window allows you to choose a set of routers and a set of commands to run on those routers by checking them from the Devices and Commands sections of the left pane. To narrow down the devices view to a subset of devices of a particular hardware vendor, click the arrow next to Devices. Similarly, to narrow down the commands listed to a subcategory of commands, click the arrow next to Commands. Note however that when changing the view, the previous selections will be lost and only the routers and commands within the current view can be selected.
    3. After selecting the commands to run and the routers to execute them on, click “Collect” to display the collected data in the right pane. Note that certain commands are “parameterized,” meaning that they require the user to specify an additional parameter. Only one such command can be selected at a time, and the user will be prompted to enter in the parameter when collecting the data for that command. When hovering the pointer over a parameterized command in the Commands list, the tooltip will display the parameter, for example, __PARAM1__.
    4. The Output tab displays the results of the command(s) executed. If multiple devices are selected for collection, then the Output window shows shortened results. Click the + icon in the top right corner to display all the results in the Output window.
    5. Alternatively to view the results individually, click the Results tab. Clicking on a row displays the results the command run on the device executed at a particular time. Right-click on a row to run the command again. To save the results for a particular row, click the save button at the lower right of the window and specify a file. To save all the results, click the Save All button to the right of the Save button, and specify a folder in which to save the individual results.

      Figure 90: CLI Results

      CLI Results
    6. To easily access Config, Equipment, Interface, TED Database, Transit Tunnel, and Tunnel Path data, select the “Collected by Task Manager” tab. Then choose the category you want to view after Command Category. Now click a router from the upper left hand list of routers and the collected data for that router will automatically be displayed.
    7. To update the live network for a subset of routers, click those routers in the list. Then click the Update Live... button and check off the data to be collected (Configuration, Interface, Tunnel Path, Transit Tunnel). Select the “Conversion Options” tab to further specify additional collection parameters. A “Scheduling Live Network Collection” task will be submitted and can be viewed from the Task Manager (Admin > Task Manager). For more information on the available options, refer to Scheduling Live Network Collection.

    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, -- General Commands --,comment
    CISCO,Show interface,show interface
    CISCO,Show configuration,show config
    CISCO,Show running,show running
    CISCO,Show ip route,show ip route
    JUNIPER, -- Routing Table Commands -- ,comment
    JUNIPER,Show route summary,show route summary|no-more
    JUNIPER,Show route summary (XML),show route summary|display xml|no-more
    JUNIPER,Show route label-switched-path lspname,show route label-switched-path __PARAM1__ | no-more

    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.

    User CLI Collection Task

    To schedule CLI collection from the Task Manager, go to Admin > Task Manager and click the New Task button. Select the User CLI Collection task.

    Figure 91: User CLI Collection Task

    User CLI Collection Task
    1. Under Collection Directory, select the directory in which to save the show command output.

      If checking “Create time stamp subdirectory”, then a subdirectory will be created in this collection directory, indicating the time, for example, a directory named

    2. Check “Remove data older than ___ days” if you wish to remove old data. The default is 30 days.
    3. Under Device Commands, indicate the command that will prevent pausing the output between screens. For example, indicate “terminal length 0” if collecting for Cisco devices or “set cli screen-length 0” if collecting for Juniper devices. Following this, indicate the show commands to be run.

      Note that only one vendor can be collected at a time, if the commands needed for the vendors are different.

    4. Under Select the router(s) to be collected, indicate the routers to be collected, choosing routers of the right hardware type, which can support the provided commands. The routers can be selected from a given router profile, or selected from the Master Profile, which contains the last used credentials of previously collected devices.
    5. Click Next to enter in the scheduling parameters, and then click Finish to submit the task.
    6. After the task is completed, browse in the File Manager to the Collection Directory (/u/wandl/data/UserCLI/<date> by default) to find one text file per collected router, with the show commands and their output.

    Customized User CLI Collections

    Certain collections have been customized for integration with web reporting. For example, subscriber count information can be collected for ERX devices and then displayed on the web.

    1. For the web to pick up the right directory, the Collection Directory’s subdirectory should be named Subscribers, for example, /u/wandl/data/UserCLI/Subscribers
    2. For the Device Commands, use the following commands (Juniper ERX devices only):
      terminal length 0
      show subscribers
    3. After selecting the devices, click Next. This task can be scheduled on an hourly basis.
    4. Consequently, the data can be viewed on the web from Live Network > Configuration Management > Configuration Management.
    5. For the field, User Collected CLI data, make sure to enter in the correct directory, for example, /u/wandl/data/UserCLI. To change this directory, click the Browse link. Note that you need to login to the web as the admin in order to get access to this Browse link to the right of the directory. Browse for the directory and click the [S] symbol to the left of the directory to select it. Select Change Information.
    6. From the Configuration Management page, select the Subscribers Report. Subscriber count information will be calculated on the fly based on the collected User CLI data. You can browse on the date range to view, and select the data point interval and aggregate method.

      Figure 92: Subscribers Report (ERX)

      Subscribers Report (ERX)
    7. To view individual trending charts, select the flash or Java chart icon. To view the chart on more than one point, select one ore more checkboxes and click Show Selected Chart.

      Figure 93: Subscriber Count

      Subscriber Count

    Direct Router Access and Easy Command Line Interface Operation

    To directly access a router to query the router, right-click on that router on the topology map. From the pop up menu, select Connect to Device and a telnet session window will open.

    Figure 94: Connecting to Router via Telnet Session Window

    Connecting to Router via Telnet Session Window

    Once logged into the router, you can issue router CLI commands to perform various tasks. (This capability is not available in the secure shell/PUTTY versions). The session output can be captured for saving on the client or for printing, or editing and book marking a user’s favorite commands and group them in a functional level as a standard method of procedures.

    1. Right-click on the telnet session window and select Capture to File. A window titled Enter a filename to be saved will open that allows you to save the session’s output in a file in the client.
    2. Select a directory and a filename to save in and click Save.
    3. Right-click on the telnet session window and unselect Capture to File. Then select Capture.... A window will appear that allows you to choose from a list of router commands under different router types and execute those commands on that particular router. If you selected a Cisco router, select Cisco CLI commands. If you selected a Juniper router, then select Juniper CLI commands. An example is shown in the figure below.

      Figure 95: Executing Router Commands Through the Capture Window

      Executing Router Commands Through the Capture Window
    4. Select the router type from the left pane tree. Click on a router command and it will be executed on that router as shown on the Result pane on the right. Alternatively, you may enter a CLI command or select a recently executed command from the drop-down selection on the top right side of the window.
    5. Click on the Edit Router Commands checkbox on the lower left-hand corner of the Capture window to check it. This will allow the user to add/edit/delete customized commands for different types of routers. The right pane will automatically be grayed out to lock any execution on the router.
    6. Right-click on a router type on the left window pane and select New>Command.
    7. A new selection will appear named New cli command as shown in <Link>Figure 96. Right-click on that selection and select Rename. Rename it with the CLI command that you want to add and hit <Enter>. If you wish to group your new commands into a subdirectory, first choose New>Command Set. This will create a folder labelled “New cli set”. Then, right click on top of the newly created folder and select New>Command.

      Figure 96: Creating New Juniper Router Command via Capture Window

      Creating New Juniper Router Command via Capture Window
    8. Uncheck the Edit Router Commands checkbox and run the new command on the router by selecting it on the left tree pane. It should execute as it would if the command was typed directly into the telnet window.

    View Live Tunnel Events and Revisions

    Tunnel Events

    Right-click a node and select View Live>Tunnel Events to view changes in the status (up or down) of the tunnel and recorded route over time. Select from a list of tunnels originating at the selected node on the left pane to view the tunnel events in the right pane. Figure 97:

    Figure 97: Tunnel Event Viewer

    Tunnel Event Viewer

    Tunnel Path Revisions

    To view changes to tunnel paths over time, first schedule a “Scheduling Live Network Collection” task collecting tunnel paths at a regular time interval.

    Once the tunnel path information has been collected, right-click a router on the standard map and select View Live>Tunnel Path Revisions to retrieve the tunnel path revisions. From the list of routers, select the tunnel originating from that router for which you would like to view the tunnel revisions.

    Alternatively, select Network > Elements > Tunnels, right-click on a tunnel, and select Tunnel Path Revisions.

    Figure 98: Tunnel Path Revisions

    Tunnel Path Revisions

    The Recorded Route can be viewed graphically by selecting a revision and clicking the Show Path button. To automate the display on the map when stepping through each of the revisions, click the Animate button. To reload the revision data, click the Reload button and specify to collect the revision information for all days, the last 7 days, or starting from a certain day.

    Modified: 2015-12-29