Quantcast
Channel: IEOC - INE's Online Community
Viewing all articles
Browse latest Browse all 10744

TE tunnel with specific BW requirement doesn't come up.

$
0
0

Hello,

I have this setup:

PE1 router is connected to P1 router via single 1G Intf. P1 router is in turn connected to the P2 router via 8xSTM-1, and finally P2 is connected to PE2 via single 1G Intf

PE1--P1==P2--PE2

Now, this is how PE1 is seeing P1's MPLS-TE topology tree:

 

pe1#sh isis database verbose p1

  Metric: 10         IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.77
    Neighbor IP Address: 192.168.10.78
    Physical BW: 155520 kbits/sec
    Reservable Global Pool BW: 0 kbits/sec
    Global Pool BW Unreserved:
      [0]:        0 kbits/sec, [1]:        0 kbits/sec
      [2]:        0 kbits/sec, [3]:        0 kbits/sec
      [4]:        0 kbits/sec, [5]:        0 kbits/sec
      Devil:        0 kbits/sec, [7]:        0 kbits/sec


  Metric: 10         IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.81
    Neighbor IP Address: 192.168.10.82
    Physical BW: 155520 kbits/sec
    Reservable Global Pool BW: 0 kbits/sec
    Global Pool BW Unreserved:
      [0]:        0 kbits/sec, [1]:        0 kbits/sec
      [2]:        0 kbits/sec, [3]:        0 kbits/sec
      [4]:        0 kbits/sec, [5]:        0 kbits/sec
      Devil:        0 kbits/sec, [7]:        0 kbits/sec


  Metric: 10         IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.93
    Neighbor IP Address: 192.168.10.94
    Physical BW: 155520 kbits/sec
    Reservable Global Pool BW: 0 kbits/sec
    Global Pool BW Unreserved:
      [0]:        0 kbits/sec, [1]:        0 kbits/sec
      [2]:        0 kbits/sec, [3]:        0 kbits/sec
      [4]:        0 kbits/sec, [5]:        0 kbits/sec
      Devil:        0 kbits/sec, [7]:        0 kbits/sec


  Metric: 10         IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.85
    Neighbor IP Address: 192.168.10.86
    Physical BW: 155520 kbits/sec
    Reservable Global Pool BW: 0 kbits/sec
    Global Pool BW Unreserved:
      [0]:        0 kbits/sec, [1]:        0 kbits/sec
      [2]:        0 kbits/sec, [3]:        0 kbits/sec
      [4]:        0 kbits/sec, [5]:        0 kbits/sec
      Devil:        0 kbits/sec, [7]:        0 kbits/sec


  Metric: 13000      IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.15.61
    Neighbor IP Address: 192.168.15.62
    Physical BW: 1000000 kbits/sec
    Reservable Global Pool BW: 145000 kbits/sec
    Global Pool BW Unreserved:
      [0]:   145000 kbits/sec, [1]:   145000 kbits/sec
      [2]:   145000 kbits/sec, [3]:   145000 kbits/sec
      [4]:   145000 kbits/sec, [5]:   145000 kbits/sec
      Devil:   145000 kbits/sec, [7]:    15000 kbits/sec


  Metric: 13000      IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.189
    Neighbor IP Address: 192.168.10.190
    Physical BW: 1000000 kbits/sec
    Reservable Global Pool BW: 145000 kbits/sec
    Global Pool BW Unreserved:
      [0]:   145000 kbits/sec, [1]:   145000 kbits/sec
      [2]:   145000 kbits/sec, [3]:   145000 kbits/sec
      [4]:   145000 kbits/sec, [5]:   145000 kbits/sec
      Devil:   145000 kbits/sec, [7]:     5000 kbits/sec


  Metric: 10         IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.245
    Neighbor IP Address: 192.168.10.246
    Physical BW: 1000000 kbits/sec
    Reservable Global Pool BW: 145000 kbits/sec
    Global Pool BW Unreserved:
      [0]:   145000 kbits/sec, [1]:   145000 kbits/sec
      [2]:   145000 kbits/sec, [3]:   145000 kbits/sec
      [4]:   145000 kbits/sec, [5]:   145000 kbits/sec
      Devil:   145000 kbits/sec, [7]:    10000 kbits/sec

  Metric: 13000      IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.161
    Neighbor IP Address: 192.168.10.162
    Physical BW: 1000000 kbits/sec
    Reservable Global Pool BW: 145000 kbits/sec
    Global Pool BW Unreserved:
      [0]:   145000 kbits/sec, [1]:   145000 kbits/sec
      [2]:   145000 kbits/sec, [3]:   145000 kbits/sec
      [4]:   145000 kbits/sec, [5]:   145000 kbits/sec
      Devil:   145000 kbits/sec, [7]:   145000 kbits/sec

As you see, 5 STM-1 with metric of 10 and 3 STM-1 with metric of 13000.

I'm trying to build up a TE tunnel with a BW of 125M from PE1 toward PE2:

pe1#sh run int tu12

Building configuration...

Current configuration : 319 bytes
!
interface Tunnel12
 ip unnumbered Loopback0
 tunnel source Loopback0
 tunnel destination 2.2.2.2
 tunnel mode mpls traffic-eng
 tunnel mpls traffic-eng priority 7 7
 tunnel mpls traffic-eng bandwidth  125000
 tunnel mpls traffic-eng path-option 1 dynamic
 tunnel mpls traffic-eng path-selection metric te
end

However, the tunnel doesn't come up because of this:

pe1#sh mpls traffic-eng tunnels tunnel 12
Name: pe1                 (Tunnel12) Destination: 2.2.2.2
  Status:
    Admin: up         Oper: down   Path: not valid   Signalling: Down
    path option 1, type dynamic

  Config Parameters:
    Bandwidth: 125000   kbps (Global)  Priority: 7  7   Affinity: 0x0/0xFFFF
    Metric Type: TE (interface)
    AutoRoute:  disabled  LockDown: disabled  Loadshare: 125000   bw-based
    auto-bw: disabled

  Shortest Unconstrained Path Info:
    Path Weight: 2010 (TE)
    Explicit Route: 192.168.10.17 192.168.10.246 192.168.50.74 2.2.2.2
  History:
    Tunnel:
      Time since created: 17 hours, 25 minutes
      Time since path change: 6 seconds
    Prior LSP:
      ID: path option 1 [6410]
      Removal Trigger: path error


Jan 21 12:25:18 CLT: Outgoing Path:
Jan 21 12:25:18 CLT:   version:1 flags:0000 cksum:DCAB ttl:255 reserved:0 length:212
Jan 21 12:25:18 CLT:  SESSION              type 7 length 16:
Jan 21 12:25:18 CLT:   Tun Dest:   2.2.2.2  Tun ID: 12  Ext Tun ID: 1.1.1.1
Jan 21 12:25:18 CLT:  HOP                  type 1 length 12:
Jan 21 12:25:18 CLT:   Hop Addr: 192.168.10.18 LIH: 0x36000418
Jan 21 12:25:18 CLT:  TIME_VALUES          type 1 length 8 :
Jan 21 12:25:18 CLT:   Refresh Period (msec): 30000
Jan 21 12:25:18 CLT:  EXPLICIT_ROUTE       type 1 length 36:
Jan 21 12:25:18 CLT:   192.168.10.17 (Strict IPv4 Prefix, 8 bytes, /32)
Jan 21 12:25:18 CLT:   192.168.10.162 (Strict IPv4 Prefix, 8 bytes, /32)
Jan 21 12:25:18 CLT:   192.168.50.74 (Strict IPv4 Prefix, 8 bytes, /32)
Jan 21 12:25:18 CLT:   2.2.2.2 (Strict IPv4 Prefix, 8 bytes, /32)
Jan 21 12:25:18 CLT:  LABEL_REQUEST        type 1 length 8 :
Jan 21 12:25:18 CLT:   Layer 3 protocol ID: 2048
Jan 21 12:25:18 CLT:  SESSION_ATTRIBUTE    type 7 length 28:
Jan 21 12:25:18 CLT:   Setup Prio: 7, Holding Prio: 7
Jan 21 12:25:18 CLT:   Flags: SE Style
Jan 21 12:25:18 CLT:   Session Name: pe1
Jan 21 12:25:18 CLT:  SENDER_TEMPLATE      type 7 length 12:
Jan 21 12:25:18 CLT:   Tun Sender: 1.1.1.1  LSP ID: 6412
Jan 21 12:25:18 CLT:  SENDER_TSPEC         type 2 length 36:
Jan 21 12:25:18 CLT:   version=0, length in words=7
Jan 21 12:25:18 CLT:   Token bucket fragment (service_id=1, length=6 words
Jan 21 12:25:18 CLT:     parameter id=127, flags=0, parameter length=5
Jan 21 12:25:18 CLT:     average rate=15625000 bytes/sec, burst depth=1000 bytes
Jan 21 12:25:18 CLT:     peak rate   =15625000 bytes/sec
Jan 21 12:25:18 CLT:     min unit=0 bytes, max pkt size=2147483647 bytes
Jan 21 12:25:18 CLT:  ADSPEC               type 2 length 48:
Jan 21 12:25:18 CLT:  version=0  length in words=10
Jan 21 12:25:18 CLT:  General Parameters  break bit=0  service length=8
Jan 21 12:25:18 CLT:                                          IS Hops:1
Jan 21 12:25:18 CLT:               Minimum Path Bandwidth (bytes/sec):125000000
Jan 21 12:25:18 CLT:                      Path Latency (microseconds):0
Jan 21 12:25:18 CLT:                                         Path MTU:1600
Jan 21 12:25:18 CLT:  Controlled Load Service  break bit=0  service length=0

Jan 21 12:25:18 CLT: Incoming PathError:
Jan 21 12:25:18 CLT:   version:1 flags:0001 cksum:0000 ttl:255 reserved:0 length:132
Jan 21 12:25:18 CLT:  SESSION              type 7 length 16:
Jan 21 12:25:18 CLT:   Tun Dest:   2.2.2.2  Tun ID: 12  Ext Tun ID: 1.1.1.1
Jan 21 12:25:18 CLT:  ERROR_SPEC           type 1 length 12:
Jan 21 12:25:18 CLT:   Error Node: 192.168.10.17
Jan 21 12:25:18 CLT:   Error Code: 24 (Routing Problem)
Jan 21 12:25:18 CLT:   Error Value: 0x5  (No route available toward destination)
Jan 21 12:25:18 CLT:   Flags: 0x0
Jan 21 12:25:18 CLT:  SENDER_TEMPLATE      type 7 length 12:
Jan 21 12:25:18 CLT:   Tun Sender: 1.1.1.1  LSP ID: 6412
Jan 21 12:25:18 CLT:  SENDER_TSPEC         type 2 length 36:
Jan 21 12:25:18 CLT:   version=0, length in words=7
Jan 21 12:25:18 CLT:   Token bucket fragment (service_id=1, length=6 words
Jan 21 12:25:18 CLT:     parameter id=127, flags=0, parameter length=5
Jan 21 12:25:18 CLT:     average rate=15625000 bytes/sec, burst depth=1000 bytes
Jan 21 12:25:18 CLT:     peak rate   =15625000 bytes/sec
Jan 21 12:25:18 CLT:     min unit=0 bytes, max pkt size=2147483647 bytes
Jan 21 12:25:18 CLT:  ADSPEC               type 2 length 48:
Jan 21 12:25:18 CLT:  version=0  length in words=10
Jan 21 12:25:18 CLT:  General Parameters  break bit=0  service length=8
Jan 21 12:25:18 CLT:                                          IS Hops:1
Jan 21 12:25:18 CLT:               Minimum Path Bandwidth (bytes/sec):125000000
Jan 21 12:25:18 CLT:                      Path Latency (microseconds):0
Jan 21 12:25:18 CLT:                                         Path MTU:1600
Jan 21 12:25:18 CLT:  Controlled Load Service  break bit=0  service length=0

Jan 21 12:25:18 CLT: Outgoing PathTear:
Jan 21 12:25:18 CLT:   version:1 flags:0000 cksum:E674 ttl:255 reserved:0 length:132
Jan 21 12:25:18 CLT:  SESSION              type 7 length 16:
Jan 21 12:25:18 CLT:   Tun Dest:   2.2.2.2  Tun ID: 12  Ext Tun ID: 1.1.1.1
Jan 21 12:25:18 CLT:  HOP                  type 1 length 12:
Jan 21 12:25:18 CLT:   Hop Addr: 192.168.10.18 LIH: 0x36000418
Jan 21 12:25:18 CLT:  SENDER_TEMPLATE      type 7 length 12:
Jan 21 12:25:18 CLT:   Tun Sender: 1.1.1.1  LSP ID: 6412
Jan 21 12:25:18 CLT:  SENDER_TSPEC         type 2 length 36:
Jan 21 12:25:18 CLT:   version=0, length in words=7
Jan 21 12:25:18 CLT:   Token bucket fragment (service_id=1, length=6 words
Jan 21 12:25:18 CLT:     parameter id=127, flags=0, parameter length=5
Jan 21 12:25:18 CLT:     average rate=15625000 bytes/sec, burst depth=1000 bytes
Jan 21 12:25:18 CLT:     peak rate   =15625000 bytes/sec
Jan 21 12:25:18 CLT:     min unit=0 bytes, max pkt size=2147483647 bytes
Jan 21 12:25:18 CLT:  ADSPEC               type 2 length 48:
Jan 21 12:25:18 CLT:  version=0  length in words=10
Jan 21 12:25:18 CLT:  General Parameters  break bit=0  service length=8
Jan 21 12:25:18 CLT:                                          IS Hops:0
Jan 21 12:25:18 CLT:               Minimum Path Bandwidth (bytes/sec):2147483647
Jan 21 12:25:18 CLT:                      Path Latency (microseconds):0
Jan 21 12:25:18 CLT:                                         Path MTU:-1
Jan 21 12:25:18 CLT:  Controlled Load Service  break bit=0  service length=0

However, you can see that P1=P2 connections has an interface which is 192.168.10.161 that can accomodate this BW requirement.

Do anyone has any idea?


Viewing all articles
Browse latest Browse all 10744

Trending Articles