Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

MPLS Tunnel Extraction

MPLS Tunnel Extraction retrieves the actual placement of the tunnel and the status (up or down) of the LSP paths by parsing the output of the tunnel_path command:

Juniper:

Cisco:

This feature shows the exact network view of tunnel paths. This is useful if the LSPs can be dynamic (as opposed to explicit). NorthStar Planner will display the current status and routing of the LSP tunnels within the defined network.

  1. To use this feature, you must specify a directory that contains the output of these commands, one file per router. With your network model already open, select File > Import Data to access the Import Wizard. Click Next > to go to the second page of the wizard.
  2. First, under Import Type, click on the drop-down selection box to choose Tunnel Path. Then, specify the import directory for the Tunnel Path directory. Note that there is also a directory for Transit Tunnels. This is used to collect additional information for Fast Reroute.
  3. Click Browse to open up a Directory Chooser window. Navigate to the directory that contains the files and click Select.
    Figure 1: Importing Tunnel Paths Into Existing Network ModelImporting Tunnel Paths Into Existing Network Model
  4. Click Next > to begin the extraction.
    Note:

    In order to see the Tunnel Path import type option inside the Import Wizard, a network model should already be opened. You will be importing the tunnel path information into this network model.

    This should generate a NorthStar Planner format file of the tunnel paths and status called tunnelpath.runcode, where runcode is the file extension of your network model. This will also be automatically loaded into the network model.

  5. When the import action is complete, click Finish to close the wizard.
  6. As a result of the import of tunnel paths, the tunnel path information as well as tunnel status can be seen from Network > Elements > Tunnels.
    Figure 2: Imported TunnelsImported Tunnels
  7. The status can be seen in the Misc field of the Properties tab:

    • LIVE_STAT=UP: The tunnel is up.

    • LIVE_STAT=DOWN: The tunnel is down.

    • LIVE_STAT=MISSING: The status of the tunnel has not been collected. LIVE_STAT does not get updated when importing tunnel path files, so the status is always MISSING.

    The path can be seen from the Current_Route column of the Tunnels table. Select a tunnel and click Show Path to view the tunnel graphically on the Standard Map.

Command Line Tunnel Path: rdjpath

The program /u/wandl/bin/rdjpath can be used to automate the tunnel info extraction. The command line options are as follows: /u/wandl/bin/rdjpath -r runcode tunnel_path_dir

Substitute the runcode with the same file extension used by your network project and tunnel_path_dir with the directory containing the tunnel path files collected from the router.

The resulting file, tunnelpath.runcode can be imported into the network via /u/wandl/bin/bbdsgn, option M. MPLSView, 3. Read MPLS Tunnel Path. This can also be automated via input trace file.

Note:

The tunnel path file must be in UNIX format.

Command Line Tunnel Traffic (Juniper only): convjtraf

The program /u/wandl/bin/convjtraf can be used to extract the tunnel traffic data from Juniper routers. The command line options are as follows:

The resulting file can be imported into the network via File > Load Network Files > Tunnel Traffic > t_trafficload.