MPLS TE tunnel Bandwidth and ip rsvp bandwidth

I have some questions about how to reserve bandwidth in MPLS TE enviorment.
1. We must IP RSVP bandwidth in all concern interface in MPLS TE enviroment, right?
2. What's the goal of ip rsvp bandwidth?
3. Tunnel MPLS traffic-enginerring bandwitdh XXX, the command define flow bandwidth initiated by head-end, if sending more than XXX flow, how does it work? Drop excessive packet in the flow?
Any point is welcome! Thanks!

Hello,
just today I found some time to read RFCs. and found:
4124 Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering. F. Le Faucheur, Ed.. June 2005. (Format: TXT=79265 bytes) (Status: PROPOSED STANDARD)
4125 Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering. F. Le Faucheur, W. Lai. June 2005. (Format: TXT=22585 bytes) (Status: EXPERIMENTAL)
4126 Max Allocation with Reservation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering & Performance Comparisons. J. Ash. June 2005. (Format: TXT=51232 bytes) (Status: EXPERIMENTAL)
4127 Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering. F. Le Faucheur, Ed.. June 2005. (Format: TXT=23694 bytes) (Status: EXPERIMENTAL)
4128 Bandwidth Constraints Models for Differentiated Services (Diffserv)-aware MPLS Traffic Engineering: Performance Evaluation. W. Lai. June 2005. (Format: TXT=58691, PDF=201138 bytes) (Status: INFORMATIONAL)
4201 Link Bundling in MPLS Traffic Engineering (TE). K. Kompella, Y. Rekhter, L. Berger. October 2005. (Format: TXT=27033 bytes) (Updates RFC3471, RFC3472, RFC3473) (Status: PROPOSED STANDARD)
Basically these standards allow to combine congestion management and MPLS TE. The standard says a router "may allocate ressources" based on the MPLS TE reservations.
So MPLS DiffServ-aware TE can deliver both TE and QoS.
Regards, Martin

Similar Messages

MPLS TE tunnel not coming up - RSVP issue?

Hello,
I have two routers R2 and R5 back to back and I am trying to create an MPLS TE tunnel between them. R2 already has one tunnel up and running to another router R1.
I think my issue is that no RSVP traffic is being sent by R2 or R5. Here is my interface config on R5 and some show commands:
R5#show run int s2/0
Building configuration...
Current configuration : 143 bytes
interface Serial2/0
ip address 192.168.25.5 255.255.255.0
mpls traffic-eng tunnels
fair-queue 64 256 32
ip rsvp bandwidth 1000 1000
end
R5#show ip int brief s2/0
Interface IP-Address OK? Method Status Protocol
Serial2/0 192.168.25.5 YES NVRAM up up
R5#show ip rsvp counters in s2/0
Serial2/0 Recv Xmit Recv Xmit
Path 0 0 Resv 0 0
PathError 0 0 ResvError 0 0
PathTear 0 0 ResvTear 0 0
ResvConfirm 0 0 ResvTearConfirm 0 0
UnknownMsg 0 0 Errors 0 0
R5#
I have mpls traffic-eng tunnels on all routers and interfaces. Here here is my tunnel config on R5 towards R2:
R5#show run int tun 2
Building configuration...
Current configuration : 174 bytes
interface Tunnel2
ip unnumbered Loopback0
tag-switching ip
tunnel destination 10.0.0.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 1 dynamic
end
I also am learning all addresses via OSPF so R5 does have a route (and can ping) 10.0.0.2 (R2's loopback)
Any ideas where this is failing? Why isn't RSVP sending packets?
Thanks,

Here you go. I have made some changes since then but nothing major. Just adding interfaces under the OSPF MPLS traffic-eng to see if that will work. Also, there is a couple tunnels you see that I have not started to work on yet. Tunnel 5 on R2 points to R5. Tunnel 2 on R5 points to R2.
=====================================
R2:
R2# show run
Building configuration...
Current configuration : 1965 bytes
version 12.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname R2
logging buffered 16384 debugging
ip subnet-zero
ip cef
no ip domain-lookup
mpls label protocol ldp
mpls traffic-eng tunnels
tag-switching tdp router-id Loopback0
interface Loopback0
ip address 10.0.0.2 255.255.255.255
interface Tunnel1
ip unnumbered Loopback0
tunnel destination 10.0.0.1
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 1 dynamic
interface Tunnel3
ip unnumbered Loopback0
tag-switching ip
tunnel destination 10.0.0.3
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 1 dynamic
interface Tunnel5
ip unnumbered Loopback0
tunnel destination 10.0.0.5
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 1 dynamic
interface FastEthernet1/0
ip address 205.127.233.242 255.255.254.0
speed 100
full-duplex
interface Serial2/0
ip address 192.168.12.2 255.255.255.0
mpls traffic-eng tunnels
fair-queue 64 256 37
ip rsvp bandwidth 1500 1500
interface Serial2/1
bandwidth 20000
ip address 192.168.25.2 255.255.255.0
mpls traffic-eng tunnels
fair-queue 64 256 37
ip rsvp bandwidth 1000 1000
interface Serial2/2
no ip address
shutdown
interface Serial2/3
no ip address
shutdown
router ospf 1
router-id 10.0.0.2
log-adjacency-changes
network 10.0.0.2 0.0.0.0 area 0
network 192.168.12.0 0.0.0.255 area 0
network 192.168.23.0 0.0.0.255 area 0
network 192.168.25.0 0.0.0.255 area 0
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0
mpls traffic-eng interface Serial2/0 area 0
mpls traffic-eng interface Serial2/1 area 0
mpls traffic-eng interface Loopback0 area 0
ip classless
ip http server
ip pim bidir-enable
call rsvp-sync
mgcp profile default
dial-peer cor custom
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
login
end
R2#
====================================
R5:
R5#show run
Building configuration...
Current configuration : 1492 bytes
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
hostname R5
logging buffered 16384 debugging
ip subnet-zero
no ip domain-lookup
mpls label protocol ldp
mpls traffic-eng tunnels
tag-switching tdp router-id Loopback0
interface Loopback0
ip address 10.0.0.5 255.255.255.255
interface Tunnel2
ip unnumbered Loopback0
tunnel destination 10.0.0.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 1 dynamic
interface Serial2/0
ip address 192.168.25.5 255.255.255.0
mpls traffic-eng tunnels
fair-queue 64 256 32
ip rsvp bandwidth 1000 1000
interface Serial2/1
ip address 192.168.45.5 255.255.255.0
shutdown
mpls traffic-eng tunnels
fair-queue 64 256 37
ip rsvp bandwidth 1000 1000
interface Serial2/2
no ip address
shutdown
fair-queue 64 256 37
ip rsvp bandwidth 10000 10000
interface Serial2/3
no ip address
shutdown
router ospf 1
router-id 10.0.0.5
log-adjacency-changes
network 10.0.0.5 0.0.0.0 area 0
network 192.168.25.0 0.0.0.255 area 0
network 192.168.45.0 0.0.0.255 area 0
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0
mpls traffic-eng interface Serial2/0 area 0
mpls traffic-eng interface Loopback0 area 0
ip classless
ip http server
ip pim bidir-enable
call rsvp-sync
mgcp profile default
dial-peer cor custom
end
R5#
======================================
thanks

Which object in RSVP message carried the value configured by "tunnel mpls traffic-eng bandwidth" command?

Hi Experts,
I configured a simple MPLS TE tunnel in my routers and configured it with "tunnel mpls traffic-eng bandwidth 777" command. The tunnel came up fine. I tried to capture the packets (using GNS capture) going out of tunnel head end interface but I could not find out on which message object the value '777' is carried. Can anyone please explain me exactly in which RSVP/OSPF message the bandwidth value is carried?
Thanks,
Madhu

Hello Madhu,
I think it is FLOWSPEC object, not 100% sure
The FLOWSPEC class is defined in RFC 2210. Cisco IOS Software requests Controlled-Load service when reserving a TE tunnel. The FLOWSPEC format is complex and has many things in it that RSVP for MPLS TE doesn't use.The FLOWSPEC is used in Resv messages—Resv, ResvTear, ResvErr, ResvConf, ResvTearConf. Its only use in MPLS TE is to use the average rate section of the FLOWSPEC to specify the bandwidth desired, in bytes. Not bits. Bytes. So if you configure a tunnel with tunnel mpls traffic-eng 100000 to request 100 Mbps of bandwidth, this gets signalled as 12,500,000 bytes per second (100 Mb is 100,000 Kb is 100,000,000 bits, which is 12,500,000 bytes).
Hope this helps
Regards
Mahesh

What is it "tunnel mpls traffic-eng bandwidth" !!!

Buenas dia, Amigos!
I want to limit the speed of the MPLS Tunnel between two sites. I'm going to create a MPLS tunnel and apply
"tunnel mpls traffic-eng bandwidth X"
Can anybody answer me, it can really limit the speed or only reserve bandwidth?
!Hasta la vista, Amigos!

Hello Oleg,
the command is only used during the tunnel setup and has administrative meaning. It is used by RSVP for reservation of resources. It does not provide any form of rate control over the tunnel.
You need to control how much traffic you put on the tunnel on the tail end router.
Hope to help
Giuseppe

What is the 'tunnel mpls traffic-en bandwidth' ?

Hi
I do not understand about 'mpls tunnel traffic-en bandwidth'
If i want to use the RSVP-TE then i know i have to configure the 'ip rsvp bandwidth ...' and 'tunnel mpls traffic-en bandwidth...'
But why i have to configure them for TE.
RSVP is Resource Reservation Bandwidth so i think that 'ip rsvp bandwidth' checked the available B/W in physical interface for TE and it is not the reality B/W for tunnel.
Is it correct?
Can you teach me them for me 'IP RSVP BANDWIDTH, TUNNEL MPLS TRAFFIC-EN BANDWIDTH'
Thank you

Hello Byung,
the ip rsvp bandwidth specifies the total amount of resources available outbound an interface = total reserveable bandwidth on the link it can even bei higher then effective interface speed.
The other command specifies the amount of bandwidth to be used in the reservation for the specific MPLS TE tunnel and has to be lower then the first one in order for the link to be selected and used for the tunnel. If no suitable path is found the tunnel setup fails.
To be noted the bandwidth associated to an MPLS TE Tunnel is an administrative parameter and does not reflect the effective traffic that can travel over the tunnel.
The Call admission control is performed on the administrative bandwidth parameter not on effective user traffic.
Hope to help
Giuseppe

MPLS-TE Guarantee Bandwidth only for ?

Hello ^_^
Does the MPLS-TE can used in guarantee Bandwidth only for Voice or Video Conference at 3750-ME or 6524ME or 7206 Router ?

Hello Hsin,
if you don't use mpls autoroute announce you can decide what traffic you put in a mesh of MPLS TE tunnels.
This can be done by using static routes or combining them with BGP (using per service next-hop loopbacks).
Then, another matter is the volume of traffic you put over an MPLS TE tunnel: there is no real time effective CAC but CAC is performed on RSVP TE reversations.
In other words if a tunnel declares a bandwidth of 2 Mbps you can still put 20 Mbps of traffic over it!
It is not like it has been on ATM.
Hope to help
Giuseppe

Tunnel - using Tunnel Bandwidth

I have a quick question here what is the purpose of using the Tunnel Bandwidth command for and is it necessary on a point to point connection? Reason why I ask is that we have a point to point connection and a tunnel is riding over this connection. We every now and then I notice high latency on this connection. I noticed that the bandwidth transmit/receive is set up for 8k only while the point-to-point connection is 128k. I'm thinking this is the cause of the latency...your thoughts?

Hi
hope this helps..
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network%20Infrastructure&topic=WAN%2C%20Routing%20and%20Switching&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dddc3e4
regds

Monitoring IPSec Tunnel Bandwidth Utilization

We have a Cisco ASA 5520 supporting multiple VPNs - both remote-access and Lan-to-Lan. We would like to monitor the bandwidth utilization of the IPSec Lan-to-Lan tunnels. How can we do that?
Thanks,
Spr

Hi Spr,
Check out VPNTTG (VPN Tunnel Traffic Grapher) is a software for SNMP monitoring and measuring the traffic load for IPsec (Site-to-Site, Remote Access) and SSL (With Client, Clientless) VPN tunnels on a Cisco ASA. It allows the user to see traffic load on a VPN tunnel over time in graphical form.
Advantage of VPNTTG over other SNMP based monitoring software's is following: Other (commonly used) software's are working with static OID numbers, i.e. whenever tunnel disconnects and reconnects, it gets assigned a new OID number. This means that the historical data, gathered on the connection, is lost each time. However, VPNTTG works with VPN peer's IP address and it stores for each VPN tunnel historical monitoring data into the Database.
For more information about VPNTTG please visit www.vpnttg.com

SNMP per-ipsec tunnel bandwidth monitoring

Whish oid can be used for monitoring bandwidth (bps, kbps...) per ipsec tunnel, assuming there is now logical tunel interface configured?
ios supports CISCO-IPSEC-FLOW-MONITOR-MIB, but cannot find oid in ftp://ftp.cisco.com/pub/mibs/oid/CISCO-IPSEC-FLOW-MONITOR-MIB.oid.
Tnx!

Hi Spr,
Check out VPNTTG (VPN Tunnel Traffic Grapher) is a software for SNMP monitoring and measuring the traffic load for IPsec (Site-to-Site, Remote Access) and SSL (With Client, Clientless) VPN tunnels on a Cisco ASA. It allows the user to see traffic load on a VPN tunnel over time in graphical form.
Advantage of VPNTTG over other SNMP based monitoring software's is following: Other (commonly used) software's are working with static OID numbers, i.e. whenever tunnel disconnects and reconnects, it gets assigned a new OID number. This means that the historical data, gathered on the connection, is lost each time. However, VPNTTG works with VPN peer's IP address and it stores for each VPN tunnel historical monitoring data into the Database.
For more information about VPNTTG please visit www.vpnttg.com

MPLS TE tunnels doesn't come up after BGP arrived at the scene

Hi folks,
I was running a little lab where I had an mpls te tunnel running fine from one router located at the border of the network to the other, I was using ISIS as the IGP. Everything was fine untill I added BGP to the lab and suddenly the tunnel turn down. I want to know if I got to add an additional configuration to my PE routers to succesfully bring up my tunnel like before. My tunnel's explicits path were LSR-PE2 and LSR PE1. My topology looks like this.
                                 LSR
         eBGP         /               \          eBGP
ASx ------------ PE1 ----------------- PE2--------------ASy
                               iBGP
Thanks,
Francis.

Here I leave the configurations and I correct myself about the network topology, I added a pic about the exact topology too. The tunnel is built PE1-R1-R3.
PE1 - R0
clns routing
mpls label protocol ldp
mpls traffic-eng tunnels
interface Loopback0
ip address 10.201.0.0 255.255.255.255
ip router isis
interface Tunnel0
ip unnumbered Loopback0
tunnel destination 10.201.0.3
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng priority 5 5
tunnel mpls traffic-eng bandwidth 1000
tunnel mpls traffic-eng path-option 10 explicit name te
no routing dynamic
interface FastEthernet0/0
bandwidth 100000
ip address 10.200.0.1 255.255.255.252
ip router isis
duplex auto
speed auto
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
ip rsvp bandwidth 75000
ip rsvp resource-provider none
interface FastEthernet1/0
bandwidth 100000
ip address 10.200.0.5 255.255.255.252
ip router isis
duplex auto
speed auto
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
ip rsvp bandwidth 85000
ip rsvp resource-provider none
interface FastEthernet2/0
ip address 190.80.239.1 255.255.255.252
duplex auto
speed auto
router isis
net 49.0123.0000.0000.0000.00
is-type level-1
metric-style wide
mpls traffic-eng router-id Loopback0
mpls traffic-eng level-1
router bgp 6400
no synchronization
bgp log-neighbor-changes
network 190.80.239.0 mask 255.255.255.252
neighbor 10.201.0.4 remote-as 6400
neighbor 10.201.0.4 password cisco
neighbor 10.201.0.4 update-source Loopback0
neighbor 190.80.239.2 remote-as 1630
neighbor 190.80.239.2 password cisco
no auto-summary
ip explicit-path name te enable
next-address 10.201.0.1
next-address 10.201.0.3
mpls ldp router-id Loopback0
LSR- R1
clns routing
mpls label protocol ldp
mpls traffic-eng tunnels
interface Loopback0
ip address 10.201.0.1 255.255.255.255
ip router isis
interface FastEthernet0/0
bandwidth 100000
ip address 10.200.0.6 255.255.255.252
ip router isis
duplex auto
speed auto
mpls label protocol ldp
mpls ip
mpls mtu 1508
mpls traffic-eng tunnels
ip rsvp bandwidth 75000
ip rsvp resource-provider none
interface Serial1/0
bandwidth 1500
ip address 10.200.0.9 255.255.255.252
ip router isis
encapsulation ppp
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
serial restart-delay 0
ip rsvp bandwidth 1200
ip rsvp resource-provider none
interface Ethernet2/0
bandwidth 10000
ip address 10.200.0.13 255.255.255.252
ip router isis
full-duplex
mpls label protocol ldp
mpls ip
mpls mtu 1508
mpls traffic-eng tunnels
ip rsvp bandwidth 7500
ip rsvp resource-provider none
router isis
net 49.0123.0000.0000.0001.00
is-type level-1
metric-style wide
mpls traffic-eng router-id Loopback0
mpls traffic-eng level-1
mpls ldp router-id Loopback0
LSR-R3
ip cef
no ip domain lookup
mpls label protocol ldp
mpls traffic-eng tunnels
interface Loopback0
ip address 10.201.0.3 255.255.255.255
ip router isis
interface Tunnel0
ip unnumbered Loopback0
tunnel destination 10.201.0.0
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng priority 5 5
tunnel mpls traffic-eng bandwidth 1000
tunnel mpls traffic-eng path-option 10 explicit name te
no routing dynamic
interface FastEthernet0/0
bandwidth 100000
ip address 10.200.0.2 255.255.255.252
ip router isis
duplex auto
speed auto
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
ip rsvp bandwidth 75000
ip rsvp resource-provider none
interface Serial1/0
bandwidth 1500
ip address 10.200.0.10 255.255.255.252
ip router isis
encapsulation ppp
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
serial restart-delay 0
isis metric 1677214
ip rsvp bandwidth 1200
interface Ethernet2/0
bandwidth 10000
ip address 10.200.0.14 255.255.255.252
ip router isis
full-duplex
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
ip rsvp bandwidth 7500
ip rsvp resource-provider none
interface FastEthernet3/0
bandwidth 100000
ip address 10.200.0.17 255.255.255.252
ip router isis
duplex auto
speed auto
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
isis metric 1677214
ip rsvp bandwidth 75000
router isis
net 49.0123.0000.0000.0003.00
is-type level-1
metric-style wide
mpls traffic-eng router-id Loopback0
mpls traffic-eng level-1
ip explicit-path name te enable
next-address 10.200.0.13
next-address 10.201.0.0
mpls ldp router-id Loopback0
PE2- R4
ip cef
no ip domain lookup
clns routing
mpls label protocol ldp
mpls traffic-eng tunnels
interface Loopback0
ip address 10.201.0.4 255.255.255.255
ip router isis
interface FastEthernet0/0
bandwidth 10000
ip address 10.200.0.18 255.255.255.252
ip router isis
duplex auto
speed auto
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
ip rsvp bandwidth 75000
interface FastEthernet1/0
ip address 190.80.239.5 255.255.255.252
duplex auto
speed auto
router isis
net 49.0123.0000.0000.0004.00
is-type level-1
metric-style wide
mpls traffic-eng router-id Loopback0
mpls traffic-eng level-1
router bgp 6400
no synchronization
bgp log-neighbor-changes
network 190.80.239.4 mask 255.255.255.252
neighbor 10.201.0.0 remote-as 6400
neighbor 10.201.0.0 password cisco
neighbor 10.201.0.0 update-source Loopback0
neighbor 190.80.239.6 remote-as 36256
neighbor 190.80.239.6 password cisco
no auto-summary
mpls ldp router-id Loopback0

MPLS-TE Tunnel (FRR) Issue

Hi
Need some discussion on MPLS - TE tunnel issue.
One of Tunnel with FRR configured, creates problem after a while affects the traffic running on the link until I shut the tunnel manually.
Configs are ok because same configurations made for different cities to authenticate to a AAA server located in one of city.
following is the generic diagram and complete config for respective links in all 3 cities but the tunnel on link highlighted with RED arrow creates problem after a while not at once until I shut the tunnel,
The Platform is Cisco CISCO7609-S and all links are on 7600-SIP-400 module
interface GigabitEthernet2/2/0
description *** Physical Interface ***
dampening
mtu 9216
ip address x.x.x.x x.x.x.x
no ip redirects
no ip proxy-arp
ip ospf message-digest-key 1 md5 7 xxx
ip ospf network point-to-point
load-interval 30
carrier-delay msec 0
negotiation auto
mpls traffic-eng tunnels
mpls traffic-eng backup-path Tunnel2300
mpls ip
service-policy output egress_policy
hold-queue 4096 in
hold-queue 4096 out
ip rsvp bandwidth percent 95
ip rsvp signalling dscp 48
end
x.x.x.x#sh running-config int tun 1300
Building configuration...
Current configuration : 377 bytes
interface Tunnel1300
description *** Primary Tunnel ***
ip unnumbered Loopback0
shutdown
mpls ip
tunnel destination x.x.x.x
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng path-option 10 explicit name path-1300
tunnel mpls traffic-eng fast-reroute
end
x.x.x.x#sh running-config int tun 2300
Building configuration...
Current configuration : 332 bytes
interface Tunnel2300
description *** Backup Tunnel ***
ip unnumbered Loopback0
shutdown
mpls ip
tunnel destination x.x.x.x
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name path-2300
tunnel mpls traffic-eng record-route
end

Hi,
Issue was figured out, the traffic was dropping dut to EF tagged traffic in the service policy applied under the physical interface.
The limit of EF tagged traffic was defined less as per actual traffic which was causing drop in peak hours

MPLS TE tunnels with DS-TE - step2

Dear Sir!
in Further to my previous thread (MPLS TE tunnels with DS-TE), I'll want to implement this solution:
One of the ways to solve this problem is to use different BGP next-hops for the prefixes (probably VoIP prefixes) that attract the LLQ-bound traffic .
PE1----PE2
Either PE2 would need to change the next-hop from Loo0 to Loo10 (say) and advertise those (VoIP) VPN prefixes (for this VPN) to PE1,
or let PE1 change the next-hop for the relevant prefixes via an import-map within that VRF.
And then you could use the tunnel10's destination to be the Loop10 IP address
Rajiv Asati .
as Rajiv Asati says, because of I've 36x0 routers, which don't support CBTS (Class Based TUnnel selection).
But when I try to make tunnel10's destination to be the Loop10 IP address, then I find that line protocol of this tunnel is DOWN (of course, Lo10-network are in IGP protocol of MPLS TE domain)
when I make
PE1:
interface Tunnel10
description for LLQ
ip unnumbered Loopback0
tunnel destination PE2-lo10-ip
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 0 0
tunnel mpls traffic-eng bandwidth sub-pool 2048
tunnel mpls traffic-eng path-option 1 dynamic
end
sh mpls traf tu Tu10
command I find that:
Shortest Unconstrained Path Info:
Path Weight: UNKNOWN
Explicit Route: UNKNOWN
History:
Tunnel:
Time since created: 9 minutes, 46 seconds
Path Option 1:
Last Error: PCALC:: Destination IP address, PE2-lo10-ip, not found
(of course, Lo10-network are in IGP protocol of MPLS TE domain)
I don't understand - why (can I've for MPLS TE tunnel destination other address that MPLS TE RID)?
Can you suppose what is my possible mistake?
Best regards,
Maxim Denisov

You need to change the next-hop outbound under address-family vpnv4 as follow:
bgp xx
address-family vpnv4
neighbor route-map setNH out
route-map setNH permit 10
match extcommunity 1
set ip next-hop
route-map setNH permit 20
match extcommunity 2
set ip next-hop
route-map setNH permit 30
ip extcommunity-list 1 permit rt
ip extcommunity-list 2 permit rt
Hope this helps,

MPLS TE Tunnel priority

Hi ,
I have a doubt on MPLS TE tunnel selection for LSP. I understood that by using the TE tunnels , suppose if have 3 different path to reach the next hop router. we can set a priority by using the command tunnel mpls traffic-eng priority (set priority) (hold priority).
if i have configured tunnel 1 and i have given tunnel mpls traffic-eng priority 1 1 and the back up tunnel for this is tunnel 2 and the relevant priority is tunnel mpls traffic-eng priority 2 2 , so now the first tunnel is the first best path to reach the desired next hop Ldp ID and if the link associated with that tunnel is down the automatically the back up tunnel with the priority 2 2 should come up.
and i need in rare case if both the links associated with the Tunnel 1 and tunnel are down then the 3rd tunnel should come up. For achieving this is it enough if i create another one tunnel 3 and give the command tunnel mpls traffic-eng priority 3 3.
Or since i have 3 seperate path to reach the next hop router , is it possible to do the load balancing between LSP. if its good to do the load balancing how can we achieve this.
Regards,
Hariharan k

yes, you can configure load balancing, all tunnels toward the same destination appear as equal-cost paths, even when their TE bandwidths are not the same.
config is given below
interface Tunnel0
ip unnumbered Loopback0
tunnel destination a.b.c.d
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 7 7
tunnel mpls traffic-eng path-option 1 explicit path1
interface Tunnel1
ip unnumbered Loopback0
tunnel destination 172.16.0.21
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 7 7
tunnel mpls traffic-eng path-option 1 explicit path2
after this if you run the show ip route command, you will see the two paths listed in routing table.
regards
shivlu jain

MPLS TE tunnel problem

Hi,
i created MPLS TE tunnel between three Cisco 2811 series routers and configured that MPLS TE tunnel will reserve 1Mbps of bandwidth.Then I started to send constant 3 Mbps data flow trough the MPLS TE tunnel (everything looks ok: tunnel is up, bandwidth is reserved, all the data flow entering the tunnel). The problem is that data flow leaving the tunnel at 3Mbps rate. Why tunnel dont limit data rate?????

The tunnel doesn't do rate-limiting. Bandwidth at the tunnel level is only a control plane feature.
You need to configure admission control on the tunnel headend with CAR or some other form of rate limiting if you want to enforce the tunnel reserved bandwidth.
Hope this helps,

IPSEC Tunnel Protection and per-tunnel QOS shaping doesnt do any shaping.

I am having a small brain implosion as to why this will not work.
I have tried the QOS policy on the tunnel interfaces and on the ATM interface. No shaping occurs. The interfaces transmit at their leisure.
Please can someone having a better day than me tell me what I am doing wrong?
Below is the relevant (and standard) config. without the service-policy command applied anywhere. Any help appreciated.
class-map match-any APPSERVERS
match access-group name TERMINALSERVERS
class-map match-any VOICE
match protocol sip
match protocol rtp
match dscp ef
policy-map QOSPOLICY
class VOICE
    priority 100
class APPSERVERS
    bandwidth percent 33
class class-default
    fair-queue 16
policy-map TUNNEL
class class-default
    shape average 350000
service-policy QOSPOLICY
interface Tunnel0
bandwidth 350
ip address 172.20.58.2 255.255.255.0
ip mtu 1420
load-interval 30
qos pre-classify
tunnel source Dialer0
tunnel destination X.X.X.X
tunnel mode ipsec ipv4
tunnel path-mtu-discovery
tunnel protection ipsec profile IPSECPROFILE
interface Tunnel1
bandwidth 350
ip address 172.21.58.2 255.255.255.0
ip mtu 1420
load-interval 30
delay 58000
qos pre-classify
tunnel source Dialer0
tunnel destination Y.Y.Y.Y
tunnel mode ipsec ipv4
tunnel path-mtu-discovery
tunnel protection ipsec profile IPSECPROFILE
interface ATM0/0/0
no ip address
load-interval 30
no atm ilmi-keepalive
interface ATM0/0/0.1 point-to-point
pvc 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1
interface Dialer0
bandwidth 400
ip address negotiated
Thanks,
Paul

Hi mate,
This is an 1841 with 12.4 (20) but Ive tried it on 15.1 on a 1941 also. I get some measure of traffic reduction but I cannot fathom what it is actually doing.
In the lab with the 1841 and a flat shaper I get this:
policy-map SHAPE
class class-default
    shape average 600000
interface Tunnel0
bandwidth 700
service-policy output SHAPE
R1#sh policy-map int
Tunnel0
Service-policy output: SHAPE
    Class-map: class-default (match-any)
      18664 packets, 26423115 bytes
      30 second offered rate 452000 bps, drop rate 0 bps
      Match: any
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 45/0/0
      (pkts output/bytes output) 18659/27808530
      shape (average) cir 600000, bc 2400, be 2400
      target shape rate 600000
R1#sh policy-map int
Tunnel0
Service-policy output: SHAPE
    Class-map: class-default (match-any)
      19044 packets, 26964413 bytes
      30 second offered rate 451000 bps, drop rate 0 bps
      Match: any
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 45/0/0
      (pkts output/bytes output) 19039/28378426
      shape (average) cir 600000, bc 2400, be 2400
      target shape rate 600000
It just holds the data rate around 450 kbps. ??
Here are the types of results I get when the HQoS is applied to the Tunnel interface in the lab:
policy-map QOS
class IP2
    drop
class IP3
    priority 300
class class-default
policy-map TUNNEL
class class-default
    shape average 600000
service-policy QOS
interface Tunnel0
bandwidth 700
service-policy output TUNNEL
R1#sh policy-map int
Tunnel0
Service-policy output: TUNNEL
    Class-map: class-default (match-any)
      14843 packets, 20884436 bytes
      30 second offered rate 362000 bps, drop rate 75000 bps
      Match: any
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 0/3942/0
      (pkts output/bytes output) 14009/15858326
      shape (average) cir 600000, bc 2400, be 2400
      target shape rate 600000
      Service-policy : QOS
        queue stats for all priority classes:
          Queueing
          queue limit 64 packets
          (queue depth/total drops/no-buffer drops) 0/3942/0
          (pkts output/bytes output) 6464/9540288
        Class-map: IP2 (match-all)
          385 packets, 533940 bytes
          30 second offered rate 28000 bps, drop rate 28000 bps
          Match: access-group 102
          drop
        Class-map: IP3 (match-all)
          10411 packets, 14628188 bytes
          30 second offered rate 191000 bps, drop rate 75000 bps
          Match: access-group 103
          Priority: 300 kbps, burst bytes 7500, b/w exceed drops: 3942
        Class-map: class-default (match-any)
          4047 packets, 5722308 bytes
          30 second offered rate 143000 bps, drop rate 0 bps
          Match: any
          queue limit 64 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 7545/6318038
This is after 10 minutes of running transfers to all endpoints to utilise the classes in the policy.
So why dont we see shaping that moves towards the configured values?
Thanks.

MPLS TE tunnel Bandwidth and ip rsvp bandwidth

Similar Messages

Maybe you are looking for