Here are my lab notes for MPLS TE per VRF testing. This was built on top of my existing MPLS
TE lab.
- Diagram
- Configuration (Provider Edge only)
- Verification
- Ping & Trace with no TE tunnel
- Ping & Trace with TE tunnel
- VRF BGP Next-Hop & Routing
- Traffic Forwarding to TE Tunnel
- MPLS TE Tunnels Details
- Verification (Additional TE specific commands)
- MPLS Traffic Engineering Topology
- MPLS Traffic Engineering Link Management
- MPLS Traffic Engineering Link Management Advertisements
- MPLS Traffic Engineering Admission Control
- Issues & Concerns
- References
Diagram
Configuration
MPLS TE and RSVP were still enabled from the previous lab. Nothing was changed in that regard.
MPLS TE per VRF configurations were only made on the provider
edge routers. The example shown was from
PE_R05 only. No special configuration was required in the core. TE tunnels were unidirectional (PE5 to PE6 only).
Similar configuration were required on PE6 to allow TE in the opposite direction from PE6 to PE5 (not covered here).
Provider
Edge Router
Create loopback interfaces for TE BGP next-hop, one for each VRF.
interface
Loopback51
description TE NEXT HOP FOR CUSTOMER_A
ip address 5.1.1.1 255.255.255.255
ip ospf 100 area 0
interface
Loopback52
description TE NEXT HOP FOR CUSTOMER_B
ip address 5.2.2.2 255.255.255.255
ip ospf 100 area 0
|
Configuring the BGP next-hop in the VRF to the loopback
interface will rewrite the next-hop address in the BGP NLRI in the outgoing
advertisement. See verification section
for an example.
ip vrf
CUSTOMER_A
rd 2345:1
route-target export 2345:1
route-target import 2345:1
bgp next-hop Loopback51
ip vrf
CUSTOMER_B
rd 2345:2
route-target export 2345:2
route-target import 2345:2
bgp next-hop Loopback52
|
Create two different explicit paths, one for each VRF/Customer.
ip
explicit-path name LSP_PE5_2_PE6_CUSTOMER_A enable
next-address 10.1.1.1
next-address 10.0.0.2
next-address 10.0.0.14
next-address 10.1.1.14
|
ip
explicit-path name LSP_PE5_2_PE6_CUSTOMER_B enable
next-address 10.1.1.5
next-address 10.0.0.5
next-address 10.0.0.10
next-address 10.0.0.13
next-address 10.1.1.10
|
Tunnel1 is for Customer A to PE6. It has an explicit path and 25K reserved bandwidth.
interface
Tunnel1
description TE TO PE6 - CUSTOMER_A
ip unnumbered Loopback0
mpls ip
tunnel mode mpls traffic-eng
tunnel destination 6.6.6.6
tunnel mpls traffic-eng priority 1 1
tunnel mpls traffic-eng bandwidth 25
tunnel mpls traffic-eng path-option 1
explicit name LSP_PE5_2_PE6_CUSTOMER_A
tunnel mpls traffic-eng path-option 2
dynamic
|
Tunnel2 is for Customer B to PE6. It has an explicit path and 25K reserved
bandwidth.
interface
Tunnel2
description TE TO PE6 - CUSTOMER_B
ip unnumbered Loopback0
mpls ip
tunnel mode mpls traffic-eng
tunnel destination 6.6.6.6
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 2 2
tunnel mpls traffic-eng bandwidth 25
tunnel mpls traffic-eng path-option 1
explicit name LSP_PE5_2_PE6_CUSTOMER_B
tunnel mpls traffic-eng path-option 2
dynamic
|
Create static routes. The customer prefixes that had its BGP next-hop rewritten at
the VRF level will need these static routes to forward its traffic over the TE
tunnel.
ip route 6.1.1.1
255.255.255.255 Tunnel1 name CUST_A_TE_2_PE6
ip route
6.2.2.2 255.255.255.255 Tunnel2 name CUST_B_TE_2_PE6
|
Verification (No TE)
Uses the lowest cost path (CE20 → PE5 → P3 → P2 → PE6 → CE21)
Ping (Customer A)
CE_R20#ping
172.16.2.254 source lo100
Type escape
sequence to abort.
Sending 5,
100-byte ICMP Echos to 172.16.2.254, timeout is 2 seconds:
Packet sent
with a source address of 172.16.1.254
!!!!!
Success rate
is 100 percent (5/5), round-trip min/avg/max = 8/8/10 ms
|
Traceroute (Customer A)
CE_R20#traceroute
172.16.2.254 source lo100
Type escape
sequence to abort.
Tracing the
route to 172.16.2.254
VRF info:
(vrf in name/id, vrf out name/id)
1 10.2.2.1 4 msec 4 msec 4 msec
2 10.1.1.5 [MPLS: Labels 324/628 Exp 0] 7
msec 7 msec 9 msec
3 10.0.0.17 [MPLS: Labels 229/628 Exp 0] 26
msec 36 msec 36 msec
4 10.2.2.9 [MPLS: Label 628 Exp 0] 21 msec
19 msec 21 msec
5 10.2.2.10 20 msec * 9 msec
|
Uses the lowest cost path (CE8 → PE5 → P3 → P2 → PE6 → CE10)
Ping (Customer B)
CE_R08#ping
192.168.2.254 source lo100
Type escape
sequence to abort.
Sending 5,
100-byte ICMP Echos to 192.168.2.254, timeout is 2 seconds:
Packet sent
with a source address of 192.168.1.254
!!!!!
Success rate
is 100 percent (5/5), round-trip min/avg/max = 9/9/10 ms
|
Traceroute (Customer B)
CE_R08#traceroute
192.168.2.254 source lo100
Type escape
sequence to abort.
Tracing the
route to 192.168.2.254
VRF info:
(vrf in name/id, vrf out name/id)
1 10.2.2.5 3 msec 5 msec 5 msec
2 10.1.1.5 [MPLS: Labels 328/630 Exp 0] 8
msec 8 msec 8 msec
3 10.0.0.17 [MPLS: Labels 212/630 Exp 0] 33
msec 29 msec 32 msec
4 10.2.2.13 [MPLS: Label 630 Exp 0] 19 msec
19 msec 20 msec
5 10.2.2.14 21 msec * 6 msec
|
Verification (With TE)
Uses the TE explicit path (CE20 → PE5 → P1 →P2 → P4 → PE6 → CE21)
Ping (Customer A)
Ping (Customer A)
CE_R20#ping
172.16.2.254 sou lo100
Type escape
sequence to abort.
Sending 5,
100-byte ICMP Echos to 172.16.2.254, timeout is 2 seconds:
Packet sent
with a source address of 172.16.1.254
!!!!!
Success rate
is 100 percent (5/5), round-trip min/avg/max = 8/8/10 ms
|
Traceroute (Customer A)
CE_R20#tr
172.16.2.254 sou lo100
Type escape
sequence to abort.
Tracing the
route to 172.16.2.254
VRF info:
(vrf in name/id, vrf out name/id)
1 10.2.2.1 4 msec 3 msec 4 msec
2 10.1.1.1 [MPLS: Labels 116/628 Exp 0] 7
msec 6 msec 7 msec
3 10.0.0.2 [MPLS: Labels 228/628 Exp 0] 30
msec 30 msec 32 msec
4 10.0.0.14 [MPLS: Labels 424/628 Exp 0] 29
msec 31 msec 37 msec
5 10.2.2.9 [MPLS: Label 628 Exp 0] 15 msec
15 msec 15 msec
6 10.2.2.10 20 msec * 8 msec
|
MPLS Traceroute (Customer A)
PE_R05#traceroute
mpls traffic-eng tunnel 1
Tracing MPLS
TE Label Switched Path on Tunnel1, timeout is 2 seconds
Codes: '!' -
success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' -
unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC
mapping, 'f' - FEC mismatch,
'M' - malformed request, 'm' - unsupported
tlvs, 'N' - no label entry,
'P' - no rx intf label prot, 'p' -
premature termination of LSP,
'R' - transit router, 'I' - unknown
upstream index,
'l' - Label switched with FEC change, 'd' -
see DDMAP for return code,
'X' - unknown return code, 'x' - return
code 0
Type escape
sequence to abort.
0 10.1.1.2 MRU 9216 [Labels: 116 Exp: 0]
L 1 10.1.1.1
MRU 9216 [Labels: 228 Exp: 0] 6 ms
L 2 10.0.0.2
MRU 9216 [Labels: 424 Exp: 0] 28 ms
L 3 10.0.0.14
MRU 9216 [Labels: implicit-null Exp: 0] 22 ms
! 4 10.1.1.14
22 ms
|
Uses the TE explicit path (CE8 → PE5 → P3 →P1 → P4 → P2 →PE6 → CE10)
Ping (Customer B)
CE_R08#ping
192.168.2.254 sou lo100
Type escape
sequence to abort.
Sending 5,
100-byte ICMP Echos to 192.168.2.254, timeout is 2 seconds:
Packet sent
with a source address of 192.168.1.254
!!!!!
Success rate
is 100 percent (5/5), round-trip min/avg/max = 11/11/12 ms
|
Traceroute (Customer B)
CE_R08#tr
192.168.2.254 sou lo100
Type escape
sequence to abort.
Tracing the
route to 192.168.2.254
VRF info:
(vrf in name/id, vrf out name/id)
1 10.2.2.5 4 msec 5 msec 5 msec
2 10.1.1.5 [MPLS: Labels 326/630 Exp 0] 9
msec 10 msec 12 msec
3 10.0.0.5 [MPLS: Labels 124/630 Exp 0] 22
msec 29 msec 31 msec
4 10.0.0.10 [MPLS: Labels 423/630 Exp 0] 31
msec 30 msec 31 msec
5 10.0.0.13 [MPLS: Labels 223/630 Exp 0] 32
msec 36 msec 32 msec
6 10.2.2.13 [MPLS: Label 630 Exp 0] 20 msec
20 msec 27 msec
7 10.2.2.14 20 msec * 10 msec
|
MPLS Traceroute (Customer B)
PE_R05#traceroute
mpls traffic-eng tunnel 2
Tracing MPLS
TE Label Switched Path on Tunnel2, timeout is 2 seconds
Codes: '!' -
success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' -
unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC
mapping, 'f' - FEC mismatch,
'M' - malformed request, 'm' - unsupported
tlvs, 'N' - no label entry,
'P' - no rx intf label prot, 'p' -
premature termination of LSP,
'R' - transit router, 'I' - unknown upstream
index,
'l' - Label switched with FEC change, 'd' -
see DDMAP for return code,
'X' - unknown return code, 'x' - return
code 0
Type escape
sequence to abort.
0 10.1.1.6 MRU 9216 [Labels: 326 Exp: 0]
L 1 10.1.1.5
MRU 9216 [Labels: 124 Exp: 0] 4 ms
L 2 10.0.0.5
MRU 9216 [Labels: 423 Exp: 0] 5 ms
L 3 10.0.0.10
MRU 9216 [Labels: 223 Exp: 0] 6 ms
L 4 10.0.0.13
MRU 9216 [Labels: implicit-null Exp: 0] 15 ms
! 5 10.1.1.10
22 ms
|
VRF BGP Next-Hop & Routing
When the BGP next-hop is configured in a VRF, it rewrites
the next-hop IP with that of the defined loopback interface for prefixes
advertised to other PE’s (or RR in this case).
This is a required step in forcing traffic in a VRF to a particular TE tunnel.
Here’s a look at the BGP table from the RR’s perspective. The prefix originating from PE5 Customer A:
172.16.1.0/24 has its next-hop changed to 5.1.1.1 whereas for Customer B:
192.168.1.0/24 it has changed to 5.2.2.2.
Note: If using an RR, the new loopback address must be
advertised in the IGP. Otherwise the next-hop
can’t be validated at the RR and will not export these routes to the PEs.
RR_R11#sh ip
bgp vpnv4 all
BGP table
version is 89, local router ID is 11.11.11.11
Status codes:
s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b
backup-path, f RT-Filter,
x best-external, a
additional-path, c RIB-compressed,
Origin codes:
i - IGP, e - EGP, ? - incomplete
RPKI
validation codes: V valid, I invalid, N Not found
Network
Next Hop Metric LocPrf Weight Path
Route
Distinguisher: 2345:1
*>i 172.16.1.0/24
5.1.1.1 0 100
0 65000 i
*>i 172.16.2.0/24 6.1.1.1 0 100
0 65001 i
Route
Distinguisher: 2345:2
*>i 10.2.2.4/30 5.2.2.2 0 100
0 ?
*>i 10.2.2.12/30 6.2.2.2 0 100
0 ?
*>i 192.168.1.0
5.2.2.2 25728256 100
0 ?
*>i 192.168.2.0 6.2.2.2 25728256 100
0 ?
|
Here’s a look from PE5.
Routes sent from PE6 have the next-hop rewritten to its loopback
addresses of 6.1.1.1 and 6.2.2.2.
PE_R05#sh ip
bgp vpnv4 all
BGP table
version is 167, local router ID is 5.5.5.5
Status codes:
s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m
multipath, b backup-path, f RT-Filter,
x best-external, a
additional-path, c RIB-compressed,
Origin codes:
i - IGP, e - EGP, ? - incomplete
RPKI
validation codes: V valid, I invalid, N Not found
Network
Next Hop Metric LocPrf Weight Path
Route
Distinguisher: 2345:1 (default for vrf CUSTOMER_A)
*>
172.16.1.0/24 10.2.2.2 0 0 65000 i
*>i 172.16.2.0/24
6.1.1.1 0 100
0 65001 i
Route
Distinguisher: 2345:2 (default for vrf CUSTOMER_B)
*>
10.2.2.4/30 0.0.0.0 0 32768 ?
*>i 10.2.2.12/30 6.2.2.2 0 100
0 ?
*>
192.168.1.0 10.2.2.6 25728256 32768 ?
*>i 192.168.2.0
6.2.2.2 25728256 100
0 ?
|
Same goes for PE6.
Routes learned from PE5 have the next-hop rewritten to its loopback
addresses of 5.1.1.1 and 5.2.2.2.
PE_R06#sh ip
bgp vpnv4 all
BGP table
version is 128, local router ID is 6.6.6.6
Status codes:
s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m
multipath, b backup-path, f RT-Filter,
x best-external, a
additional-path, c RIB-compressed,
Origin codes:
i - IGP, e - EGP, ? - incomplete
RPKI
validation codes: V valid, I invalid, N Not found
Network
Next Hop Metric LocPrf Weight Path
Route
Distinguisher: 2345:1 (default for vrf CUSTOMER_A)
*>i 172.16.1.0/24
5.1.1.1 0 100
0 65000 i
*>
172.16.2.0/24 10.2.2.10 0 0 65001 i
Route
Distinguisher: 2345:2 (default for vrf CUSTOMER_B)
*>i 10.2.2.4/30 5.2.2.2 0 100
0 ?
*>
10.2.2.12/30 0.0.0.0 0 32768 ?
*>i 192.168.1.0
5.2.2.2 25728256 100
0 ?
*>
192.168.2.0 10.2.2.14 25728256 32768 ?
|
Traffic Forwarding to TE Tunnel
The second step in routing VRF traffic into the TE tunnel is
to create static routes to point to the tunnel.
IP route 6.1.1.1/32 statically configured to the TE tunnel.
PE_R05#sh ip
route 6.1.1.1
Routing entry for 6.1.1.1/32
Known via "static", distance 1, metric 0
(connected)
Routing Descriptor Blocks:
* directly connected, via Tunnel1
Route metric is 0, traffic share count
is 1
|
IP CEF output for 6.1.1.1/32 show it has a VPN label of 524
via Tunnel 1 and use an outgoing label of 116.
PE_R05#sh ip
cef 6.1.1.1 internal
6.1.1.1/32, epoch 2, flags [att], RIB[S], refcnt 7,
per-destination sharing
sources: RIB, RR, LTE
feature space:
IPRM: 0x00048004
Broker: linked, distributed at 1st
priority
LFD: 6.1.1.1/32 1 local label
local label info: global/524
contains path extension list
disposition chain 0x7F058604F970
label switch chain 0x7F058604F8E0
subblocks:
1 RR source [no flags]
non-eos chain implicit-null
ifnums:
Tunnel1(13)
path list 7F0585EB2228, 3 locks,
per-destination, flags 0x49 [shble, rif, hwcn]
path 7F0585EB6E98, share 1/1, type
attached host, for IPv4
MPLS short path extensions: MOI flags =
0x1 label implicit-null
attached to Tunnel1, IP midchain out of Tunnel1
7F057E3FEE00
output chain:
IP midchain out of Tunnel1 7F057E3FEE00
label 116
TAG adj out of GigabitEthernet1.20, addr
10.1.1.1 7F057E3FF1D0
|
MPLS Forwarding table for VPN label 524 is via a LSP tunnel.
PE_R05#sh
mpls forwarding-table labels 524
Local
Outgoing Prefix Bytes Label Outgoing Next Hop
Label
Label or Tunnel Id Switched interface
524 [T] Pop Label
6.1.1.1/32 0 Tu1
point2point
[T] Forwarding through a LSP
tunnel.
View additional labelling info with the 'detail' option
|
IP route 6.2.2.2/32 statically configured to the TE tunnel.
PE_R05#sh ip
route 6.2.2.2
Routing entry for 6.2.2.2/32
Known via "static", distance 1, metric 0
(connected)
Routing Descriptor Blocks:
* directly connected, via Tunnel2
Route metric is 0, traffic share count
is 1
|
IP CEF output for 6.2.2.2/32 show it has a VPN label of 525
via Tunnel 2 and use an outgoing label of 326.
PE_R05#sh ip
cef 6.2.2.2 internal
6.2.2.2/32, epoch 2, flags [att], RIB[S], refcnt 7,
per-destination sharing
sources: RIB, RR, LTE
feature space:
IPRM: 0x00048004
Broker: linked, distributed at 1st
priority
LFD: 6.2.2.2/32 1 local label
local label info: global/525
contains path extension list
disposition chain 0x7F058604FDF0
label switch chain 0x7F058604FCD0
subblocks:
1 RR source [no flags]
non-eos chain implicit-null
ifnums:
Tunnel2(14)
path list 7F0585EB1C88, 3 locks, per-destination,
flags 0x49 [shble, rif, hwcn]
path 7F0585EB6760, share 1/1, type
attached host, for IPv4
MPLS short path extensions: MOI flags =
0x1 label implicit-null
attached to Tunnel2, IP midchain out of Tunnel2
7F057E3FE660
output chain:
IP midchain out of Tunnel2 7F057E3FE660
label 326
TAG adj out of GigabitEthernet1.21, addr
10.1.1.5 7F057E3FF5A0
|
MPLS Forwarding table for VPN label 525 is via a LSP tunnel.
PE_R05#sh
mpls forwarding-table labels 525
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label
Label or Tunnel Id Switched interface
525 [T] Pop Label
6.2.2.2/32 0 Tu2
point2point
[T] Forwarding through a LSP tunnel.
View additional labelling info with the 'detail' option
|
MPLS TE Tunnel Details
Shows operational state, allocated bandwidth, defined
explicit paths and outgoing MPLS labels for the traffic engineering tunnels.
(From PE5)
PE_R05#sh mpls
traffic-eng tunnels
P2P
TUNNELS/LSPs:
Name: TE TO PE6 - CUSTOMER_A (Tunnel1) Destination: 6.6.6.6
Status:
Admin: up
Oper: up Path: valid
Signalling:
connected
path option 1, type explicit LSP_PE5_2_PE6_CUSTOMER_A (Basis for Setup,
path weight 17)
path option 2, type dynamic
Config Parameters:
Bandwidth: 25 kbps (Global) Priority: 1
1 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled
Loadshare: 25 [80000000] bw-based
auto-bw: disabled
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
InLabel
: -
OutLabel : GigabitEthernet1.20, 116
Next Hop : 10.1.1.1
RSVP Signalling Info:
Src 5.5.5.5, Dst 6.6.6.6, Tun_Id 1,
Tun_Instance 878
RSVP Path Info:
My Address: 10.1.1.2
Explicit Route: 10.1.1.1 10.0.0.2 10.0.0.14 10.1.1.14
6.6.6.6
Record
Route: NONE
Tspec: ave rate=25 kbits, burst=1000
bytes, peak rate=25 kbits
RSVP Resv Info:
Record
Route: NONE
Fspec: ave rate=25 kbits, burst=1000
bytes, peak rate=25 kbits
History:
Tunnel:
Time since created: 46 days, 16 hours,
53 minutes
Time since path change: 22 hours, 29
minutes
Number of LSP IDs (Tun_Instances) used:
878
Current LSP: [ID: 878]
Uptime: 22 hours, 29 minutes
Prior LSP: [ID: 877]
ID: path option unknown
Removal Trigger: tunnel shutdown
Name: TE TO PE6 - CUSTOMER_B (Tunnel2) Destination: 6.6.6.6
Status:
Admin: up
Oper: up Path: valid
Signalling:
connected
path option 1, type explicit LSP_PE5_2_PE6_CUSTOMER_B (Basis for Setup,
path weight 14)
path option 2, type dynamic
Config Parameters:
Bandwidth: 25 kbps (Global) Priority: 2
2 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled
Loadshare: 25 [80000000] bw-based
auto-bw: disabled
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
InLabel
: -
OutLabel : GigabitEthernet1.21, 326
Next Hop : 10.1.1.5
RSVP Signalling Info:
Src 5.5.5.5, Dst 6.6.6.6, Tun_Id 2,
Tun_Instance 2255
RSVP Path Info:
My Address: 10.1.1.6
Explicit Route: 10.1.1.5 10.0.0.5 10.0.0.10 10.0.0.13
10.1.1.10 6.6.6.6
Record
Route: NONE
Tspec: ave rate=25 kbits, burst=1000
bytes, peak rate=25 kbits
RSVP Resv Info:
Record
Route: NONE
Fspec: ave rate=25 kbits, burst=1000
bytes, peak rate=25 kbits
History:
Tunnel:
Time since created: 4 days, 15 hours,
47 minutes
Time since path change: 1 hours, 39
minutes
Number of LSP IDs (Tun_Instances) used:
2255
Current LSP: [ID: 2255]
Uptime: 1 hours, 39 minutes
Prior LSP: [ID: 2254]
ID: path option unknown
Removal Trigger: tunnel shutdown
P2MP TUNNELS:
P2MP
SUB-LSPS:
|
(From P1)
P_R01#sh mpls
traffic-eng tunnels
P2P
TUNNELS/LSPs:
LSP Tunnel TE TO PE6 - CUSTOMER_A is signalled,
connection is up
InLabel :
GigabitEthernet1.20, 116
Prev Hop : 10.1.1.2
OutLabel : GigabitEthernet1.10, 228
Next Hop : 10.0.0.2
RSVP Signalling Info:
Src 5.5.5.5, Dst 6.6.6.6, Tun_Id 1,
Tun_Instance 878
RSVP Path Info:
My Address: 10.0.0.1
Explicit Route: 10.0.0.2 10.0.0.14 10.1.1.14 6.6.6.6
Record
Route: NONE
Tspec: ave rate=25 kbits, burst=1000
bytes, peak rate=25 kbits
RSVP Resv Info:
Record
Route: NONE
Fspec: ave rate=25 kbits, burst=1000
bytes, peak rate=25 kbits
LSP Tunnel TE TO PE6 - CUSTOMER_B is signalled,
connection is up
InLabel :
GigabitEthernet1.11, 124
Prev Hop : 10.0.0.6
OutLabel : GigabitEthernet1.12, 423
Next Hop : 10.0.0.10
RSVP Signalling Info:
Src 5.5.5.5, Dst 6.6.6.6, Tun_Id 2,
Tun_Instance 2255
RSVP Path Info:
My Address: 10.0.0.9
Explicit Route: 10.0.0.10 10.0.0.13 10.1.1.10 6.6.6.6
Record
Route: NONE
Tspec: ave rate=25 kbits, burst=1000
bytes, peak rate=25 kbits
RSVP Resv Info:
Record
Route: NONE
Fspec: ave rate=25 kbits, burst=1000
bytes, peak rate=25 kbits
P2MP TUNNELS:
P2MP
SUB-LSPS:
|
Specifying the tunnel interface in the show command also displays the shortest cost TE
path.
PE_R05#sh
mpls traffic-eng tunnels tunnel 1
Name: TE TO
PE6 - CUSTOMER_A (Tunnel1)
Destination: 6.6.6.6
Status:
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type explicit
LSP_PE5_2_PE6_CUSTOMER_A (Basis for Setup, path weight 17)
path option 2, type dynamic
Config Parameters:
Bandwidth: 25 kbps (Global) Priority: 1
1 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled
Loadshare: 25 [80000000] bw-based
auto-bw: disabled
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
InLabel
: -
OutLabel : GigabitEthernet1.20, 116
Next Hop : 10.1.1.1
RSVP Signalling Info:
Src 5.5.5.5, Dst 6.6.6.6, Tun_Id 1,
Tun_Instance 878
RSVP Path Info:
My Address: 10.1.1.2
Explicit Route: 10.1.1.1 10.0.0.2
10.0.0.14 10.1.1.14
6.6.6.6
Record
Route: NONE
Tspec: ave rate=25 kbits, burst=1000
bytes, peak rate=25 kbits
RSVP Resv Info:
Record
Route: NONE
Fspec: ave rate=25 kbits, burst=1000
bytes, peak rate=25 kbits
Shortest Unconstrained Path Info:
Path Weight: 5 (TE)
Explicit Route: 10.1.1.5 10.0.0.17 10.1.1.10 6.6.6.6
History:
Tunnel:
Time since created: 46 days, 16 hours,
57 minutes
Time since path change: 22 hours, 33
minutes
Number of LSP IDs (Tun_Instances) used:
878
Current LSP: [ID: 878]
Uptime: 22 hours, 33 minutes
Prior LSP: [ID: 877]
ID: path option unknown
Removal Trigger: tunnel shutdown
|
MPLS TE Tunnel Verification (additional commands)
MPLS Traffic Engineering Topology
A detailed look at the TE topology table from PE5. Every router in the MPLS TE domain contains a
topology database with link information that shows TE/IGP metrics, RSVP
bandwidth etc.
PE_R05#sh
mpls traffic-eng topology
My_System_id: 5.5.5.5 (ospf 100 area 0)
Signalling
error holddown: 10 sec Global Link Generation 556
IGP Id: 1.1.1.1, MPLS TE Id:1.1.1.1 Router
Node (ospf 100 area 0)
..snip..
link[2]: Point-to-Point, Nbr IGP Id: 2.2.2.2,
nbr_node_id:3, gen:554
frag_id: 8, Intf Address: 10.0.0.1, Nbr
Intf Address: 10.0.0.2
TE metric: 7, IGP metric: 7, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 25 75 0
bw[2]: 0 75 0
bw[3]: 0 75 0
bw[4]: 0 75 0
bw[5]: 0 75 0
bw[6]: 0 75 0
bw[7]: 0 75 0
link[3]: Point-to-Point, Nbr IGP Id: 3.3.3.3,
nbr_node_id:4, gen:554
frag_id: 9, Intf Address: 10.0.0.5, Nbr
Intf Address: 10.0.0.6
TE metric: 2, IGP metric: 2, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 0 100 0
bw[3]: 0 100 0
bw[4]: 0 100 0
bw[5]: 0 100 0
bw[6]: 0 100 0
bw[7]: 0 100 0
link[4]: Point-to-Point, Nbr IGP Id: 4.4.4.4, nbr_node_id:5,
gen:554
frag_id: 10, Intf Address: 10.0.0.9,
Nbr Intf Address: 10.0.0.10
TE metric: 8, IGP metric: 8, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 25 75 0
bw[3]: 0 75 0
bw[4]: 0 75 0
bw[5]: 0 75 0
bw[6]: 0 75 0
bw[7]: 0 75 0
link[5]: Point-to-Point, Nbr IGP Id: 5.5.5.5, nbr_node_id:1,
gen:554
frag_id: 11, Intf Address: 10.1.1.1,
Nbr Intf Address: 10.1.1.2
TE metric: 4, IGP metric: 4, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 0 100 0
bw[3]: 0 100 0
bw[4]: 0 100 0
bw[5]: 0 100 0
bw[6]: 0 100 0
bw[7]: 0 100 0
IGP Id: 2.2.2.2, MPLS TE Id:2.2.2.2 Router
Node (ospf 100 area 0)
..snip..
link[2]: Point-to-Point, Nbr IGP Id: 3.3.3.3,
nbr_node_id:4, gen:555
frag_id: 10, Intf Address: 10.0.0.17,
Nbr Intf Address: 10.0.0.18
TE metric: 3, IGP metric: 3, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 0 100 0
bw[3]:
0 100 0
bw[4]: 0 100 0
bw[5]: 0 100 0
bw[6]: 0 100 0
bw[7]: 0 100 0
link[3]: Point-to-Point, Nbr IGP Id: 4.4.4.4,
nbr_node_id:5, gen:555
frag_id: 9, Intf Address: 10.0.0.13,
Nbr Intf Address: 10.0.0.14
TE metric: 2, IGP metric: 2, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 25 75 0
bw[2]: 0 75 0
bw[3]: 0 75 0
bw[4]: 0 75 0
bw[5]: 0 75 0
bw[6]: 0 75 0
bw[7]: 0 75 0
link[4]: Point-to-Point, Nbr IGP Id: 6.6.6.6,
nbr_node_id:9, gen:555
frag_id: 11, Intf Address: 10.1.1.9,
Nbr Intf Address: 10.1.1.10
TE metric: 1, IGP metric: 1, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 25 75 0
bw[3]: 0 75 0
bw[4]: 0 75 0
bw[5]: 0 75 0
bw[6]: 0 75 0
bw[7]: 0 75 0
link[5]: Point-to-Point, Nbr IGP Id: 1.1.1.1,
nbr_node_id:2, gen:555
frag_id: 8, Intf Address: 10.0.0.2, Nbr
Intf Address: 10.0.0.1
TE metric: 7, IGP metric: 7, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 0 100 0
bw[3]: 0 100 0
bw[4]: 0 100 0
bw[5]: 0 100 0
bw[6]: 0 100 0
bw[7]: 0 100 0
IGP Id: 3.3.3.3, MPLS TE Id:3.3.3.3 Router
Node (ospf 100 area 0)
..snip..
link[1]: Point-to-Point, Nbr IGP Id: 4.4.4.4,
nbr_node_id:5, gen:552
frag_id: 10, Intf Address: 10.0.0.21,
Nbr Intf Address: 10.0.0.22
TE metric: 4, IGP metric: 4, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 0 100 0
bw[3]: 0 100 0
bw[4]: 0 100 0
bw[5]: 0 100 0
bw[6]: 0 100 0
bw[7]: 0 100 0
link[2]: Point-to-Point, Nbr IGP Id: 2.2.2.2,
nbr_node_id:3, gen:552
frag_id: 9, Intf Address: 10.0.0.18,
Nbr Intf Address: 10.0.0.17
TE metric: 3, IGP metric: 3, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 0 100 0
bw[3]: 0 100 0
bw[4]: 0 100 0
bw[5]: 0 100 0
bw[6]: 0 100 0
bw[7]: 0 100 0
link[3]: Point-to-Point, Nbr IGP Id: 5.5.5.5,
nbr_node_id:1, gen:552
frag_id: 12, Intf Address: 10.1.1.5,
Nbr Intf Address: 10.1.1.6
TE metric: 1, IGP metric: 1, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable
Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 0 100 0
bw[3]: 0 100 0
bw[4]: 0 100 0
bw[5]: 0 100 0
bw[6]: 0 100 0
bw[7]: 0 100 0
link[4]: Point-to-Point, Nbr IGP Id: 1.1.1.1,
nbr_node_id:2, gen:552
frag_id: 8, Intf Address: 10.0.0.6, Nbr
Intf Address: 10.0.0.5
TE metric: 2, IGP metric: 2, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]:
25 75 0
bw[3]: 0 75 0
bw[4]: 0 75 0
bw[5]: 0 75 0
bw[6]: 0 75 0
bw[7]: 0 75 0
IGP Id: 4.4.4.4, MPLS TE Id:4.4.4.4 Router
Node (ospf 100 area 0)
..snip..
link[1]: Point-to-Point, Nbr IGP Id: 3.3.3.3,
nbr_node_id:4, gen:553
frag_id: 10, Intf Address: 10.0.0.22,
Nbr Intf Address: 10.0.0.21
TE metric: 4, IGP metric: 4, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 0 100 0
bw[3]: 0 100 0
bw[4]: 0 100 0
bw[5]: 0 100 0
bw[6]: 0 100 0
bw[7]: 0 100 0
link[2]: Point-to-Point, Nbr IGP Id: 6.6.6.6,
nbr_node_id:9, gen:553
frag_id: 12, Intf Address: 10.1.1.13,
Nbr Intf Address: 10.1.1.14
TE metric: 4, IGP metric: 4, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 25 75 0
bw[2]: 0 75 0
bw[3]: 0 75 0
bw[4]: 0 75 0
bw[5]: 0 75 0
bw[6]: 0 75 0
bw[7]: 0 75 0
link[3]: Point-to-Point, Nbr IGP Id: 1.1.1.1,
nbr_node_id:2, gen:553
frag_id: 8, Intf Address: 10.0.0.10,
Nbr Intf Address: 10.0.0.9
TE metric: 8, IGP metric: 8, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 0 100 0
bw[3]: 0 100 0
bw[4]: 0 100 0
bw[5]: 0 100 0
bw[6]: 0 100 0
bw[7]: 0 100 0
link[4]: Point-to-Point, Nbr IGP Id: 2.2.2.2,
nbr_node_id:3, gen:553
frag_id: 9, Intf Address: 10.0.0.14,
Nbr Intf Address: 10.0.0.13
TE metric: 2, IGP metric: 2, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 25 75 0
bw[3]: 0 75 0
bw[4]: 0 75 0
bw[5]:
0 75 0
bw[6]: 0 75 0
bw[7]: 0 75 0
IGP Id: 5.5.5.5, MPLS TE Id:5.5.5.5 Router
Node (ospf 100 area 0)
link[0]: Point-to-Point, Nbr IGP Id: 1.1.1.1,
nbr_node_id:2, gen:550
frag_id: 10, Intf Address: 10.1.1.2,
Nbr Intf Address: 10.1.1.1
TE metric: 4, IGP metric: 4, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 25 75 0
bw[2]: 0 75 0
bw[3]: 0 75 0
bw[4]: 0 75 0
bw[5]: 0 75 0
bw[6]: 0 75 0
bw[7]: 0 75 0
link[1]: Point-to-Point, Nbr IGP Id: 3.3.3.3,
nbr_node_id:4, gen:550
frag_id: 11, Intf Address: 10.1.1.6,
Nbr Intf Address: 10.1.1.5
TE metric: 1, IGP metric: 1, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 25 75 0
bw[3]: 0 75 0
bw[4]: 0 75 0
bw[5]: 0 75 0
bw[6]: 0 75 0
bw[7]: 0 75 0
IGP Id: 6.6.6.6, MPLS TE Id:6.6.6.6 Router
Node (ospf 100 area 0)
link[0]: Point-to-Point, Nbr IGP Id: 2.2.2.2,
nbr_node_id:3, gen:556
frag_id: 10, Intf Address: 10.1.1.10,
Nbr Intf Address: 10.1.1.9
TE metric: 1, IGP metric: 1, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 0 100 0
bw[3]: 0 100 0
bw[4]: 0 100 0
bw[5]: 0 100 0
bw[6]: 0 100 0
bw[7]: 0 100 0
link[1]: Point-to-Point, Nbr IGP Id: 4.4.4.4,
nbr_node_id:5, gen:556
frag_id: 11, Intf Address: 10.1.1.14,
Nbr Intf Address: 10.1.1.13
TE metric: 4, IGP metric: 4, attribute
flags: 0x0
SRLGs: None
physical_bw: 100 (kbps),
max_reservable_bw_global: 100 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 100 0
bw[1]: 0 100 0
bw[2]: 0 100 0
bw[3]: 0 100 0
bw[4]: 0 100 0
bw[5]: 0 100 0
bw[6]: 0 100 0
bw[7]: 0
100 0
..snip..
|
MPLS Traffic Engineering Link Management
Link management summary contains information about TE details
on the IGP, RSVP bandwidth per link and operational status. Outputs are only from PE5 and P1.
(From PE5)
PE_R05#sh
mpls traffic-eng link-management summary
System
Information::
Links Count: 2
Flooding System: enabled
IGP Area ID::
ospf 100 area 0
Flooding Protocol:
OSPF
Flooding Status: data flooded
Periodic Flooding: enabled (every 60 seconds, next in 59
seconds)
Flooded Links:
2
IGP System ID: 5.5.5.5
MPLS TE Router ID: 5.5.5.5
Neighbors:
2
Link ID::
Gi1.20 (10.1.1.2)
Local Intfc ID: 10
Link Status:
SRLGs: None
Intfc Switching Capability
Descriptors:
Default: Intfc Switching Cap psc1, Encoding
ethernet
Link Label Type: Packet
Physical Bandwidth: 100 kbits/sec
Max Res Global BW: 100 kbits/sec (reserved: 0% in,
25% out)
Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100%
out)
MPLS TE Link State: MPLS TE on, RSVP on, admin-up, flooded, allocated
Inbound Admission: reject-huge
Outbound Admission: allow-if-room
Link MTU: IP 9216, MPLS 9216
Admin. Weight: 4 (IGP)
IGP Neighbor Count: 1
Link ID::
Gi1.21 (10.1.1.6)
Local Intfc ID: 11
Link Status:
SRLGs: None
Intfc Switching Capability
Descriptors:
Default: Intfc Switching Cap psc1, Encoding
ethernet
Link Label Type: Packet
Physical Bandwidth: 100 kbits/sec
Max Res Global BW: 100 kbits/sec (reserved: 0% in, 25% out)
Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100%
out)
MPLS TE Link State: MPLS TE on, RSVP on, admin-up, flooded, allocated
Inbound Admission: reject-huge
Outbound Admission: allow-if-room
Link MTU: IP 9216, MPLS 9216
Admin. Weight: 1 (IGP)
IGP Neighbor Count: 1
|
(From P1)
P_R01#sh mpls
traffic-eng link-management summary
System
Information::
Links Count: 6
Flooding System: enabled
IGP Area ID::
ospf 100 area 0
Flooding Protocol:
OSPF
Flooding Status: data flooded
Periodic Flooding: enabled (every 60 seconds, next in 32
seconds)
Flooded Links:
6
IGP System ID: 1.1.1.1
MPLS TE Router ID: 1.1.1.1
Neighbors:
6
Link ID::
Gi1.10 (10.0.0.1)
Local Intfc ID: 8
Link Status:
SRLGs: None
Intfc Switching Capability
Descriptors:
Default: Intfc Switching Cap psc1, Encoding
ethernet
Link Label Type: Packet
Physical Bandwidth: 100 kbits/sec
Max Res Global BW: 100 kbits/sec (reserved: 0% in, 25% out)
Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100%
out)
MPLS TE Link State: MPLS TE on, RSVP on, admin-up, flooded, allocated
Inbound Admission: reject-huge
Outbound Admission: allow-if-room
Link MTU: IP 9216, MPLS 9216
Admin. Weight: 7 (IGP)
IGP Neighbor Count: 1
Link ID::
Gi1.11 (10.0.0.5)
Local Intfc ID: 9
Link Status:
SRLGs: None
Intfc Switching Capability
Descriptors:
Default: Intfc Switching Cap psc1, Encoding
ethernet
Link Label Type: Packet
Physical Bandwidth: 100 kbits/sec
Max Res Global BW: 100 kbits/sec (reserved: 0% in, 0% out)
Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100%
out)
MPLS TE Link State: MPLS TE on, RSVP on, admin-up, flooded
Inbound Admission: reject-huge
Outbound Admission: allow-if-room
Link MTU: IP 9216, MPLS 9216
Admin. Weight: 2 (IGP)
IGP Neighbor Count: 1
Link ID::
Gi1.12 (10.0.0.9)
Local Intfc ID: 10
Link Status:
SRLGs: None
Intfc Switching Capability
Descriptors:
Default: Intfc Switching Cap psc1, Encoding
ethernet
Link Label Type: Packet
Physical Bandwidth: 100 kbits/sec
Max Res Global BW: 100 kbits/sec (reserved: 0% in, 0% out)
Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100%
out)
MPLS TE Link State: MPLS TE on, RSVP on, admin-up, flooded
Inbound Admission: reject-huge
Outbound Admission: allow-if-room
Link MTU: IP 9216, MPLS 9216
Admin. Weight: 8 (IGP)
IGP Neighbor Count: 1
Link ID::
Gi1.20 (10.1.1.1)
Local Intfc ID: 11
Link Status:
SRLGs: None
Intfc Switching Capability
Descriptors:
Default: Intfc
Switching Cap psc1, Encoding ethernet
Link Label Type: Packet
Physical Bandwidth: 100 kbits/sec
Max Res Global BW: 100 kbits/sec (reserved: 0% in, 25% out)
Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100%
out)
MPLS TE Link State: MPLS TE on, RSVP on, admin-up, flooded, allocated
Inbound Admission: reject-huge
Outbound Admission: allow-if-room
Link MTU: IP 9216, MPLS 9216
Admin. Weight: 4 (IGP)
IGP Neighbor Count: 1
..snip..
|
MPLS Traffic Engineering Link Management Advertisements
Link management advertisements shows resource advertisements
for TE interfaces. Tunnel1 reserved 25K
at priority 1 and Tunnel2 at 25K at priority 2, leaving 75K of bandwidth left.
(From PE5)
PE_R05#sh
mpls traffic-eng link-management advertisements
Flooding
Status: ready
Configured
Areas: 1
IGP Area[1]
ID:: ospf 100 area 0
System Information::
Flooding Protocol: OSPF
Header Information::
IGP System ID: 5.5.5.5
MPLS TE Router ID: 5.5.5.5
Flooded Links: 2
Link ID:: 0 (GigabitEthernet1.20)
Link Subnet Type: Point-to-Point
Link IP Address: 10.1.1.2
Neighbor: ID 1.1.1.1, IP 10.1.1.1
TE metric: 4
IGP metric: 4
SRLGs: None
Physical Bandwidth: 100 kbits/sec
Res. Global BW: 100 kbits/sec
Res. Sub BW: 0 kbits/sec
Downstream::
Global
Pool Sub Pool
----------- ----------
Reservable Bandwidth[0]: 100 0 kbits/sec
Reservable Bandwidth[1]: 75
0 kbits/sec
Reservable Bandwidth[2]: 75 0 kbits/sec
Reservable Bandwidth[3]: 75 0 kbits/sec
Reservable Bandwidth[4]: 75 0 kbits/sec
Reservable Bandwidth[5]: 75 0 kbits/sec
Reservable Bandwidth[6]: 75 0 kbits/sec
Reservable Bandwidth[7]: 75 0 kbits/sec
Attribute Flags: 0x00000000
Link ID:: 1
(GigabitEthernet1.21)
Link Subnet Type: Point-to-Point
Link IP Address: 10.1.1.6
Neighbor: ID 3.3.3.3, IP 10.1.1.5
TE metric: 1
IGP metric: 1
SRLGs: None
Physical Bandwidth: 100 kbits/sec
Res. Global BW: 100 kbits/sec
Res. Sub BW: 0 kbits/sec
Downstream::
Global Pool Sub Pool
----------- ----------
Reservable Bandwidth[0]: 100 0 kbits/sec
Reservable Bandwidth[1]: 100 0 kbits/sec
Reservable Bandwidth[2]: 75
0 kbits/sec
Reservable Bandwidth[3]: 75 0 kbits/sec
Reservable Bandwidth[4]: 75 0 kbits/sec
Reservable Bandwidth[5]: 75 0 kbits/sec
Reservable Bandwidth[6]: 75 0 kbits/sec
Reservable Bandwidth[7]: 75 0 kbits/sec
Attribute Flags: 0x00000000
|
(From P1)
Bandwidth reservation of 25K made on P1 → P2 link and P1 → P4 link.
P_R01#sh mpls
traffic-eng link-management advertisements
Flooding
Status: ready
Configured
Areas: 1
IGP Area[1]
ID:: ospf 100 area 0
System Information::
Flooding Protocol: OSPF
Header Information::
IGP System ID: 1.1.1.1
MPLS TE Router ID: 1.1.1.1
Flooded Links: 6
Link ID:: 0
(GigabitEthernet1.10)
Link Subnet Type: Point-to-Point
Link IP Address: 10.0.0.1
Neighbor: ID 2.2.2.2, IP 10.0.0.2
TE metric: 7
IGP metric: 7
SRLGs: None
Physical Bandwidth: 100 kbits/sec
Res. Global BW: 100 kbits/sec
Res. Sub BW: 0 kbits/sec
Downstream::
Global
Pool Sub Pool
----------- ----------
Reservable Bandwidth[0]: 100 0 kbits/sec
Reservable Bandwidth[1]: 75
0 kbits/sec
Reservable Bandwidth[2]: 75 0 kbits/sec
Reservable Bandwidth[3]: 75 0 kbits/sec
Reservable Bandwidth[4]: 75 0 kbits/sec
Reservable Bandwidth[5]: 75 0 kbits/sec
Reservable Bandwidth[6]: 75 0 kbits/sec
Reservable Bandwidth[7]: 75 0 kbits/sec
Attribute Flags: 0x00000000
Link ID:: 1
(GigabitEthernet1.11)
Link Subnet Type: Point-to-Point
Link IP Address: 10.0.0.5
Neighbor: ID 3.3.3.3, IP 10.0.0.6
TE
metric: 2
IGP metric: 2
SRLGs: None
Physical Bandwidth: 100 kbits/sec
Res. Global BW: 100 kbits/sec
Res. Sub BW: 0 kbits/sec
Downstream::
Global
Pool Sub Pool
----------- ----------
Reservable Bandwidth[0]: 100 0 kbits/sec
Reservable Bandwidth[1]: 100 0 kbits/sec
Reservable Bandwidth[2]: 100 0 kbits/sec
Reservable Bandwidth[3]: 100 0 kbits/sec
Reservable Bandwidth[4]: 100 0 kbits/sec
Reservable Bandwidth[5]: 100 0 kbits/sec
Reservable Bandwidth[6]: 100 0 kbits/sec
Reservable Bandwidth[7]: 100 0 kbits/sec
Attribute Flags: 0x00000000
Link ID:: 2
(GigabitEthernet1.12)
Link Subnet Type: Point-to-Point
Link IP Address: 10.0.0.9
Neighbor: ID 4.4.4.4, IP 10.0.0.10
TE metric: 8
IGP metric: 8
SRLGs: None
Physical Bandwidth: 100 kbits/sec
Res. Global BW: 100 kbits/sec
Res. Sub BW: 0 kbits/sec
Downstream::
Global
Pool Sub Pool
----------- ----------
Reservable Bandwidth[0]: 100 0 kbits/sec
Reservable Bandwidth[1]: 100 0 kbits/sec
Reservable Bandwidth[2]: 75
0 kbits/sec
Reservable Bandwidth[3]: 75 0 kbits/sec
Reservable Bandwidth[4]: 75 0 kbits/sec
Reservable Bandwidth[5]: 75 0 kbits/sec
Reservable Bandwidth[6]: 75 0 kbits/sec
Reservable Bandwidth[7]: 75 0 kbits/sec
Attribute Flags: 0x00000000
Link ID:: 3
(GigabitEthernet1.20)
Link Subnet Type: Point-to-Point
Link IP Address: 10.1.1.1
Neighbor: ID 5.5.5.5, IP 10.1.1.2
TE metric: 4
IGP metric: 4
SRLGs: None
Physical Bandwidth: 100 kbits/sec
Res. Global BW: 100 kbits/sec
Res. Sub BW: 0 kbits/sec
Downstream::
Global
Pool Sub Pool
----------- ----------
Reservable Bandwidth[0]: 100 0 kbits/sec
Reservable Bandwidth[1]: 100 0 kbits/sec
Reservable Bandwidth[2]: 100 0 kbits/sec
Reservable Bandwidth[3]: 100 0 kbits/sec
Reservable Bandwidth[4]: 100 0 kbits/sec
Reservable Bandwidth[5]: 100 0 kbits/sec
Reservable Bandwidth[6]: 100 0 kbits/sec
Reservable Bandwidth[7]: 100 0 kbits/sec
Attribute Flags: 0x00000000
..snip..
|
MPLS Traffic Engineering Admission Control
Shows TE LSP admission control information.
Shows TE LSP admission control information.
(From PE5)
PE_R05#sh
mpls traffic-eng link-management admission-control
System
Information::
P2P LSP:
LSPS: 2 (Total Admitted: 705 , Total Deleted: 703 )
P2MP subLSP:
subLSPs: 0 (Total Admitted: 0 , Total Deleted: 0 )
P2P LSP:
LSP ID UP IF DOWN IF
PRIORITY STATE BW (kbps)
5.5.5.5_878->6.6.6.6_ -
Gi1.20 1/1 Resv Admitted
25 RG
5.5.5.5_2253->6.6.6.6 -
Gi1.21 2/2 Resv Admitted
25 RG
P2MP subLSP:
Src->Dst UP IF DOWN IF
PRIORITY STATE BW
(kbps)
|
(From P1)
P_R01#sh mpls
traffic-eng link-management admission-control
System
Information::
P2P LSP:
LSPS: 2 (Total Admitted: 695 , Total Deleted: 693 )
P2MP subLSP:
subLSPs: 0 (Total Admitted: 0 , Total Deleted: 0 )
P2P LSP:
LSP ID UP IF DOWN IF
PRIORITY STATE BW (kbps)
5.5.5.5_878->6.6.6.6_ Gi1.20
Gi1.10 1/1 Resv Admitted
25 RG
5.5.5.5_2255->6.6.6.6 Gi1.11
Gi1.12 2/2 Resv Admitted
25 RG
P2MP subLSP:
Src->Dst UP IF DOWN IF
PRIORITY STATE BW
(kbps)
|
Same sort of information can be shown with the RSVP interface command.
(From PE5)
PE_R05#sh ip
rsvp interface
interface
rsvp allocated i/f max
flow max sub max VRF
Gi1 ena 0 75K 75K
0
Gi1.20
ena 25K 100K 100K
0
Gi1.21
ena 25K 100K 100K
0
|
(From P1)
P_R01#sh ip
rsvp interface
interface rsvp
allocated i/f max
flow max sub max VRF
Gi1 ena 0 75K 75K
0
Gi1.10
ena 25K 100K 100K
0
Gi1.11 ena 0 100K 100K
0
Gi1.12
ena 25K 100K 100K
0
Gi1.20 ena 0 100K 100K
0
Gi1.24 ena 0 100K 100K
0
Gi1.27 ena 0 100K
100K 0
|
Issues/Concerns
Targeted LDP Session
Most of the configuration examples I’ve seen in setting up
Per VRF TE Tunnels shows the tunnels with LDP enabled. However, based on my experience this wasn’t
necessary. It works fine without any
targeted LDP sessions, and from what I’ve read it should only be used when the
tail end of the LSP is not the egress PE.
In my case, I had a TE tunnel from PE to PE so this configuration wasn’t
necessary.
interface
Tunnel1
mpls ip
interface
Tunnel2
mpls ip
|
Here are some of the links to explain the reasons for
Targeted LDP sessions.
RSVP BW Allocation Failure
Make sure the total of all your TE tunnel’s RSVP bandwidth
reservation (e.g., 25K per tunnel) does not exceed the total bandwidth
available on the physical link. Although
this sounds obvious, I ran into issues with a core router not being able to
properly allocate the required bandwidth on the explicit path LSP when I
accidentally had both tunnels RSVP bandwidth set at 100K.
interface
Tunnel1
tunnel mpls
traffic-eng bandwidth 25
interface
Tunnel2
tunnel mpls
traffic-eng bandwidth 25
|
Core router RSVP total bandwidth (100K).
interface
GigabitEthernet1.10
description TO P_R02
mpls traffic-eng tunnels
ip rsvp bandwidth 100
|
One tunnel will always fail to allocate the required
bandwidth and will be operationally down.
PE_R05#sh
mpls traffic-eng tunnels
P2P
TUNNELS/LSPs:
Name: TE TO PE6 - CUSTOMER_A (Tunnel1) Destination: 6.6.6.6
Status:
Admin: up
Oper: up Path: valid
Signalling:
connected
path option 1, type explicit
LSP_PE5_2_PE6_CUSTOMER_A (Basis for Setup, path weight 17)
Config Parameters:
Bandwidth: 100 kbps (Global) Priority: 1
1 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled
Loadshare: 100 [20000000] bw-based
auto-bw: disabled
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
InLabel
: -
OutLabel : GigabitEthernet1.20, 128
Next Hop : 10.1.1.1
RSVP Signalling Info:
Src 5.5.5.5, Dst 6.6.6.6, Tun_Id 1,
Tun_Instance 868
RSVP Path Info:
My Address: 10.1.1.2
Explicit Route: 10.1.1.1 10.0.0.2
10.0.0.14 10.1.1.14
6.6.6.6
Record
Route:
Tspec: ave rate=100 kbits, burst=1000
bytes, peak rate=100 kbits
RSVP Resv Info:
Record
Route: 10.0.0.1 10.0.0.13
10.1.1.13 10.1.1.14
Fspec: ave rate=100 kbits, burst=1000
bytes, peak rate=100 kbits
History:
Tunnel:
Time since created: 43 days, 12 hours,
1 minutes
Time since path change: 17 hours, 30
minutes
Number of LSP IDs (Tun_Instances) used:
868
Current LSP: [ID: 868]
Uptime: 17 hours, 30 minutes
Prior LSP: [ID: 781]
ID: path option unknown
Removal Trigger: configuration changed
Name: TE TO PE6 - CUSTOMER_B (Tunnel2) Destination: 6.6.6.6
Status:
Admin: up Oper: down Path: not valid Signalling: Down
path option 1, type explicit
LSP_PE5_2_PE6_CUSTOMER_B
Config Parameters:
Bandwidth: 100 kbps
(Global) Priority: 2 2
Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: enabled LockDown: disabled Loadshare: 100 [0]
bw-based
auto-bw: disabled
History:
Tunnel:
Time since created: 1 days, 10 hours,
56 minutes
Time since path change: 17 hours, 30
minutes
Number of LSP IDs (Tun_Instances) used:
2228
Prior LSP: [ID: 108]
ID: path option 1 [2228]
Removal Trigger: path error
Last Error: CTRL:: Can't use link 10.0.0.10 on node
4.4.4.4
P2MP TUNNELS:
P2MP
SUB-LSPS:
|
Error messages when bandwidth cannot be allocated.
*Sep 18 2017
23:58:55 UTC: TE-LM-BW: tunnel 5.5.5.5_105->6.6.6.6_2 {7}: Downstream bw hold
request failed
*Sep 18 2017
23:58:56 UTC: TE-LM-BW: tunnel 5.5.5.5_106->6.6.6.6_2 {7}: Downstream bw
hold request failed
*Sep 18 2017
23:58:57 UTC: TE-LM-BW: tunnel 5.5.5.5_107->6.6.6.6_2 {7}: Downstream bw
hold request failed
*Sep 18 2017
23:58:58 UTC: TE-LM-BW: tunnel 5.5.5.5_108->6.6.6.6_2 {7}: Downstream bw
hold request failed
|
After setting the bandwidth reservation from 100K to 50K,
the allocation succeeds.
PE_R05(config)#int
tun1
PE_R05(config-if)#
tunnel mpls traffic-eng bandwidth 50
PE_R05(config-if)#ex
PE_R05(config)#int
tun2
PE_R05(config-if)#
tunnel mpls traffic-eng bandwidth 50
PE_R05(config-if)#^Z
|
*Sep 19 2017
17:37:51 UTC: TE-LM-BW: tunnel 5.5.5.5_869->6.6.6.6_1 {7}: requesting
Downstream bw hold (Global Pool 50 kbits/sec [S]) on link Gi1.23
*Sep 19 2017
17:37:51 UTC: TE-LM-BW: tunnel 5.5.5.5_869->6.6.6.6_1 {7}: Downstream bw
hold request succeeded
|
References
No comments:
Post a Comment