Requested Bandwidth Unavailable Event

LSP Event

Requested Bandwidth Unavailable

Sample Output 1

user@R1> show mpls lsp extensive

[...Output truncated...]

10.0.0.6

  From: 10.0.0.1, State: Dn, ActiveRoute: 0, LSPname: R1-to-R6

  ActivePath: (none)

  LoadBalance: Random

  Encoding type: Packet, Switching type: Packet, GPID: IPv4

  Primary                    State: Dn, No-decrement-ttl

    Bandwidth: 100Mbps 

   14 Jan 21 15:43:39 Requested bandwidth unavailable[3 times]

   13 Jan 21 15:43:21 Deselected as active

   12 Jan 21 15:43:21 Requested bandwidth unavailable

   11 Jan 21 15:43:21 Clear Call

   10 Jan 21 15:42:32 Selected as active path

    9 Jan 21 15:42:32 Record Route:  10.1.12.2 10.1.26.2

    8 Jan 21 15:42:32 Up

[...Output truncated...]

Sample Output 2:

user@R1> show mpls lsp extensive

10.0.0.6

  From: 10.0.0.1, State: Dn, ActiveRoute: 0, LSPname: R1-to-R6

  ActivePath: (none)

  LoadBalance: Random

  Encoding type: Packet, Switching type: Packet, GPID: IPv4

  Primary                    State: Dn, No-decrement-ttl

    Bandwidth: 100Mbps 

   31 Jan 21 15:47:40 10.1.12.2: Requested bandwidth unavailable[2 times]

   30 Jan 21 15:47:37 Originate Call

   29 Jan 21 15:47:37 Clear Call

   28 Jan 21 15:47:37 Deselected as active

   27 Jan 21 15:45:12 Record Route:  10.1.12.2 10.1.26.2

   26 Jan 21 15:45:12 Up

[...Output truncated...]

What It Means

This LSP event indicates that a router could not supply the requested bandwidth. Sample Output 1 was generated by the ingress router, while Sample Output 2 was generated by router 10.1.12.1, since the IP address precedes the LSP event.

Cause

This LSP event is caused by the LSP requesting bandwidth that is not available in a router along the paths to the egress router.

Action

Lower the bandwidth assignment of the ingress LSP below the amount of bandwidth available along the path to the egress router, or traffic-engineer other LSPs off the path that you want the ingress LSP to follow, freeing up the necessary bandwidth.