Preview Tool

Cisco Bug: CSCuq62728 - Modelling Loose Hop LSP in MATE

Last Modified

Oct 27, 2017

Products (1)

  • Cisco WAN Automation Engine (WAE)

Known Affected Releases


Description (partial)

When using loose hops to the L1/L2 routers with dynamic to fill in those gaps on both ends.  I've seen this same issue when my LSP's are within the same ISIS area and just using completely dynamic LSP's and when I'm crossing L1/L2 boundaries like in this case.

Tunnel Config
explicit-path name loosetoBBRs
 index 10 next-address loose ipv4 unicast  index 20 next-address loose ipv4 unicast !

interface tunnel-te8000
 description To acr22cpocmo
 ipv4 unnumbered Loopback14
 logging events lsp-status insufficient-bandwidth  priority 3 3  destination  fast-reroute  record-route  affinity 0x0 mask 0x0  path-option 10 explicit name loosetoBBRs  logging events link-status

RP/0/RSP0/CPU0:acr13cpocmo#sho mpls traffic-eng tunnels 8000

Name: tunnel-te8000  Destination:
    Admin:    up Oper:   up   Path:  valid   Signalling: connected

    path option 10,  type explicit loosetoBBRs (Basis for Setup, path weight 3110)
    G-PID: 0x0800 (derived from egress interface properties)
    Bandwidth Requested: 0 kbps  CT0
    Creation Time: Tue Aug 19 21:32:34 2014 (19:32:17 ago)
  Config Parameters:
    Bandwidth:        0 kbps (CT0) Priority:  3  3 Affinity: 0x0/0x0
    Metric Type: TE (default)
    Hop-limit: disabled
    AutoRoute: disabled  LockDown: disabled   Policy class: not set
    Forwarding-Adjacency: disabled
    Loadshare:          0 equal loadshares
    Auto-bw: disabled
    Fast Reroute: Enabled, Protection Desired: Any
    Path Protection: Not Enabled
    Soft Preemption: Disabled
    Tunnel has been up for: 18:56:33 (since Tue Aug 19 22:08:18 UTC 2014)
    Current LSP:
      Uptime: 18:56:33 (since Tue Aug 19 22:08:18 UTC 2014)
    Reopt. LSP:
      Last Failure:
        LSP not signalled, identical to the [CURRENT] LSP
        Date/Time: Wed Aug 20 17:04:21 UTC 2014 [00:00:30 ago]

  Path info (IS-IS default level-1):
  Node hop count: 5
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.