Examining the LSP Summary Details for Effective Troubleshooting

The LSP Summary page provides a comprehensive and cohesive insight about the configured LSP service. The status of the LSP and the status of connections between the ingress router and egress routers in an LSP are displayed. The LSP status details are shown for the ingress router. You can also view the ingress, egress, and transit LSP information, such as the primary and secondary states. Ingress information is for the sessions that originate from this router, egress information is for sessions that terminate on this router, and transit information is for sessions that transit through this router. Extensive information about LSPs, including all past state history and the reasons why an LSP might have failed, can also be viewed. This page is beneficial to easily resolve RSVP failures in your network topology by quickly analyzing the LSP status and statistics.

1. Select Service View from the View Selector. The workspaces that are applicable to routing and tunnel services are displayed.
2. From the Junos Space user interface, click the Monitor icon in the Connectivity Services Director banner. The functionalities that you can configure in this mode are displayed in the task pane.
3. From the Service View pane, which is the left pane in the window, click the plus sign (+) next to Network Services to expand the tree and display the different service types that you can configure.
4. Click the plus sign (+) beside Tunnel to view services based on protocols and expand the LSPs tree to select an LSP service.
5. Click the LSP Summary tab. The LSP Summary page is displayed.

This widget provides details on LSP configuration details and statistics of traffic transmitted over the LSP.

Operational Status

This monitor displays the working status of the LSP service. The following fields are displayed:

• Name—Name of the LSP service.

• Status—Operational status of the LSP service. A green up arrow indicates the LSP is up, and a red down arrow indicates the LSP is down.

• Type—Topology type of the LSP, such as point-to-point, point-to-multipoint, or full-mesh.

• LSPs Count—Total number of LSPs configured in the service that are in the up and down states.

• BFD—Total number of BFD packets transmitted over the LSP. BFD for RSVP supports unicast IPv4 LSPs. When BFD is configured for an RSVP LSP on the ingress router, it is enabled on the primary path and on all standby secondary paths for that LSP. The source IP address for outgoing BFD packets from the egress side of an MPLS BFD session is based on the outgoing interface IP address.

Status Matrix

This monitor shows the status of connections between the ingress router and egress routers in an LSP. In the tabular view, the egress router, the LSP name, and the LSP status are displayed. From the Ingress list, select the ingress router for the LSP topology. This field is automatically populated for point-to-multipoint LSP topology; you need to select it only for bidirectional P2P LSPs and full-mesh LSPs. From the Egress list, select the output router up to which the LSP runs from an ingress router. This field is applicable for P2P, point-to-multipoint, and full-mesh LSPs.

A green up-arrow in the LSP Status field indicates that the LSP to the destination device is operationally up. A red down-arrow in the LSP Status field indicates that the LSP is down. To filter and sort the display of LSPs, enter the name of the LSP as a match criterion in the Search box and click the Search icon. The page refreshes to display only the LSP names that match with the search term. You can use the paging controls to navigate across multiple pages of LSPs as necessary.

LSP Information

For a destination address that contains LSP names, the corresponding LSP details, such as the name, state, and bandwidth of the LSP, are displayed in this monitor. The following fields are displayed:

• Name— Name of the LSP

• State— State of the LSP handled by this RSVP session: Up, Dn (down), or Restart

• Bandwidth—Specifies the bandwidth in bits per second for the LSP.

• Primary State— State of the LSP that is a primary path: Up, Down, or Restart

• Secondary State— State of the LSP that is a secondary path: Up, Down, or Restart

• Received RRO—(Ingress LSP) Received record route. A series of hops, each with an address followed by a flag. (In most cases, the received record route is the same as the computed explicit route. If Received RRO is different from Computed ERO, there is a topology change in the network, and the route is taking a detour.) The following flags identify the protection capability and status of the downstream node:

  • 0x01—Local protection available. The link downstream from this node is protected by a local repair mechanism. This flag can be set only if the Local protection flag was set in the SESSION_ATTRIBUTE object of the corresponding Path message.

  • 0x02—Local protection in use. A local repair mechanism is in use to maintain this tunnel (usually because of an outage of the link it was routed over previously).

  • 0x03—Combination of 0x01 and 0x02.

  • 0x04—Bandwidth protection. The downstream routing device has a backup path providing the same bandwidth guarantee as the protected LSP for the protected section.

  • 0x08—Node protection. The downstream routing device has a backup path providing protection against link and node failure on the corresponding path section. If the downstream routing device can set up only a link-protection backup path, the Local protection available bit is set but the Node protection bit is cleared.

  • 0x09—Detour is established. Combination of 0x01 and 0x08.

  • 0x10—Preemption pending. The preempting node sets this flag if a pending preemption is in progress for the traffic engine LSP. This flag indicates to the ingress legacy edge router (LER) of this LSP that it should be rerouted.

  • 0xb—Detour is in use. Combination of 0x01, 0x02, and 0x08.

• Total Packets—Total number of packets and Total number of bytes transmitted over the LSP. This counter is reset to zero whenever the LSP path is optimized (for example, during an automatic bandwidth allocation).

• Total Bytes—Total number of bytes transmitted over the LSP. This counter is reset to zero whenever the LSP path is optimized (for example, during an automatic bandwidth allocation).

LSP Traffic

This monitor displays a line chart with the number of packets or bytes on the y-axis and time on the x-axis to denote the LSP bandwidth utilization. From the Time Interval drop-down box, select 1 Hour, 8 Hours, 1 Day, 1 Week, 1 Month, 3 Months, 6 Months, 1 Year, or Custom to specify the duration for which the data polled from devices needs to be displayed. If you select the Custom option, the Time range popup dialog box is displayed. Specify the date from the calendar, and select the Time From (Start time in the 24-hour time format of collection of data), and Time To (End time in the 24-hour time format of collection of data). Click OK to save the settings. Else, click Cancel to discard the configuration. From the Statistics Type drop-down list, select Packets or Bytes to display metrics corresponding to the selected parameter.