Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

LSPs Missing from the Network Information Table

Problem

One or more label-switched paths (LSPs) are missing from the Tunnel tab in the network information table.

Solution

The topology map on the Topology page is populated from the data in the network information table. If one or more LSPs lack corresponding entries in the table, the paths cannot be highlighted in the topology map. To troubleshoot the problem, you must understand the flow of information from the Path Computation Client (PCC) to the Topology server (also called Toposerver), as illustrated in Figure 1. The LSPs are added to the network information table only if this flow of information is successful. The flow begins with the configuration at the PCC. The PCC sends an LSP Update message to the Path Computation Element (PCE) server through a PCEP session. The PCE server sends this message to the Toposerver through an Advanced Message Queuing Protocol (AMQP) connection.

Figure 1: LSP Information Flow LSP Information Flow

To check these connections, do the following:

  1. Using your server credentials, log in to the primary node of Paragon Automation.

  2. From the primary node, use the following command to obtain the name of the pod in which the PCE server process runs:

  3. Use the following command to log in to the PCE server pod:

    In the command, ns-pceserver-pod-name is the name of the pod that you obtained in Step 2.

  4. Use the following command to view the logs associated with the PCE server:

    In the command, ns-pceserver-pod-name is the name of the pod that you obtained in Step 2. The log prints a message every 15 seconds when it detects that its connection with the PCE server has been lost or was never successfully established. In that case, you can re-synchronize the network model from the Pathfinder page (Configuration > Network Settings > Pathfinder Settings > Advanced Settings) in the GUI. See Synchronize the Network Model for more information on re-synchronizing the network model.

    In the following example log, the connection between the Toposerver and the PCE server is marked as Down:

    Note:

    The logs that you view may differ from the logs in this document. The logs change based on the installed version of Paragon Automation.

  5. Install the netstat utility in the pcep_server container by using the following command; ensure that your system has Internet access:

    Note:

    The netstat utility is not available by default.

    Run the following commands before you install netstat utility:

  6. Use the following command to verify that the PCEP session between the PCC and the PCE server is established through port 4189:

    Following is sample output:

  7. Even if the session is established, it does not necessarily mean that any data was transferred. From the PCE server pod, use the following command to check whether the PCE server discovered any LSPs from the PCC through PCEP:

    Following is sample output:

    In the far right column of the output, you can view the number of LSPs that the PCE server learned. If this number is 0, the PCE server did not receive any LSP information. In that case, check the configuration on the PCC. For information about how to check the configuration on the PCC, see your vendor's documentation for the PCC.