[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

LSP General Events

Problem

This table provides the links and commands for general label-switched path (LSP) error events that might occur in the output of the show mpls lsp extensive command. Various network configurations demonstrate LSP error events. Descriptions typically include sample output of the LSP event, an explanation of what the event means, the possible cause of the event, and any possible actions that you can take. (See Table 7.)

Solution

Table 7: LSP General Events

Understanding LSP General Events Tasks

Possible Action or Command
Displaying General LSP Error Events

show mpls lsp extensive
  1. Admission Control Failure Event

Not applicable.
  1. Explicit Route: Bad Loose Route Event

Check the LSP configuration at the [edit protocols mpls] hierarchy level.

  1. Explicit Route: Bad Strict Route Event

Examine the strict hop address, remove the no-cspf statement, or examine the path and verify that RSVP is enabled on each interface.

  1. Explicit Route: Format Error Event

Analyze this event, and refer to events on either side to determine the appropriate action.

  1. Explicit Route: Wrong Delivery Event

Take appropriate action:

  • Include the loopback (lo0) interface at the [edit protocols isis] hierarchy level.
  • Change the definition of the strict path at the [edit protocols mpls path path-name] hierarchy level.
  • Verify the validity of all IP addresses listed in the named path referenced by the LSP hop by hop.
  1. Invalid Destination Address Event

Verify that the LSP destination address is not the local router’s loopback address, and check that the addresses on the local router are correctly configured.

  1. Invalid Filter for Policing Event

Not available.
  1. MPLS Graceful Restart: Recovery Failed Event

Check the MPLS logs for more details about the failure.
  1. MPLS Label Allocation Failure Event

Include interfaces at the [edit protocols mpls] hierarchy level, or include the family mpls statement at the [edit interfaces type-fpc/pic/port] hierarchy level.

  1. Non-RSVP Capable Router Detected Event

Configure the router in question with RSVP.
  1. No Route Toward Destination Event

Enable RSVP on the transit router’s egress interface, or examine the IP configuration of the relevant router.

  1. PathErr Received Event

Not available.
  1. Path MTU Change Event

Not available.
  1. Path Name Undefined or Disabled Event

Define the named path.
  1. Requested Bandwidth Unavailable Event

Lower the bandwidth of the ingress LSP or traffic-engineer other LSPs off the path.

  1. Requested Bandwidth Unavailable: Re-optimized Path

Provision more bandwidth for the LSP or lower the bandwidth of the ingress LSP or traffic-engineer other LSPs off the path.

  1. Routing Loop Detected Event

Examine the strict hop addresses or examine the path in the ERO to determine the cause of the loop.

  1. RSVP Error, Subcode 1: Bad Session Destination Address Event

Not available.
  1. RSVP Error, Subcode 4: Protocol Shutdown Event

Check the RSVP configuration on the router in question.
  1. RSVP Error, Subcode 6: No Non-lsp Route Event

Find the node with the error and confirm that the ERO route to the next hop takes an LSP next hop. Also, you can configure strict hops to avert the problem. For information about configuring strict hops, see the JUNOS MPLS Applications Configuration Guide.

  1. TTL Expired Event

Not available.
  1. Tunnel Local Repaired Event

Not available.
  1. Unknown Object Class Event

Not available.
  1.  Unknown Object Type Event

Not available.
  1. Unsupported Traffic Class Event

Not available.
[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]