MPLS TE Bandwidth

Dear community members,
I am CCNP R&S and i have some trouble in understanding mpls TE tunnel. My question is if the bandwith is reserved over the tunnel will that bandwidth be usable for other data over that link or not ? e.g. if the reserved bandwidth on the link is configured to be 10Mbps and currently the data for which the tunnel is reserved is only 5Mbps. where will be that remaining 5Mbps ?
Thank you
Best Regards
Abdul Basit

Hello abdulbasitkhan,
The RSVP Bandwidth Reservation is done in control plane only ( not actual bandwidth reservation) so any traffic can utilize the underlying interfaces and compete with the TE tunnel traffic normally.
For your example:
My question is lets bandwidth is available and the requested bandwidth for the tunnel is 10Mbps but the data that initiated the tunnel is much less than 10Mbps, so here again will the remaining bandwidth can't be reused by other data over the link as RSVP reserved it ?
Yes, the other data can normally use the remaining Mbps and competes with the TE tunnel data
I hope that i answered your question

Similar Messages

MPLS TE Bandwidth and Priority

Hi everybody
Hopefully, everyone is doing great. I stumbled upon the following link on MPLS TE bandwidth and priority:
http://blog.ipexpert.com/2009/05/27/mpls-te-bandwidth-and-priority/
it was a very good read. But I am left with one question. How does R2 decide which tunnel to drop? In the example, R2 drops tunnel 1, but how does R2 decide which one to drop?
Thanks and have a great sunday

Hi Thanveer
I hope you are doing fine. Here is what i found in a book ( traffic engineering with MPLS by Eric, Ajay, great book, still reading it)
There are two priorities:
1) set up priority
2) hold prioritity
Based on the book the code works this way
Imagine we have two tunnels already established and are passing through R3
t1, set up priority 6 hold priority 5
t2 set up priority 6 hold priority 4
Let say R3 just receives a RSVP path request for a new tunnel, lets call it tunnel 3 with set up priority 4 hold priority 6. This tunnel requires a bandwidth which R3 can not accommodate without dropping one of the established tunnels.
Router will take t3's set up priority ( 4) and compares it against the current established tunnel's hold priorities where lower the number means higher the priority. In our example, set up priority of tunnel 3 is 4 and R3 compares it against both hold priorities of established tunnels. R3 then concludes it has to drop t1 to accommodate t3 ( set up priority of tunnel3 is higher than the hold priority of tunnel1)
++++++++++++++++++++++++++++++++++++++++++++++++++++++
what is not cleared is how will router 3 behave if all the established tunnels have same hold priority i.e 4 and a request for a new tunnel i.e t3 comes with the set up priority of 4?
Not sure if R3 just randomly picks any established tunnel and drops it or there is some move involved process that R3 goes through to decide which tunnel gets dropped.
Lets hope somebody way smarter than me might chime in :)
Have a great weekend

URGENT: QoS Design on Data Center MPLS - MediaNet Question...

Hello,
I am posting this in hopes I can get some guidance from anyone who has done this in the field. We have a large enterprise customer with 21 sites all around the world, they have Verizon MPLS and are experiencing QoS related issues on their WAN regarding Video/Voice. We have proposed remediating their network acccording to the Enterprise QoS SRND 3.3 and the new MediaNet SRND to account for Video and TP QoS (
http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND_40/QoSCampus_40.html )
Here is the problem/question that was proposed in our presales meeting and I honestly don't know where to look for an answer... I am not asking for anyone to design a solution for me, just merely point me in the right direction:
The Data Center has a ~40MB MPLS Connection ( full mesh ) into the cloud ( Verizon )
Site A has a 8MB connection
Site B has a 4MB connection
I know on the Service policy and the interfaces at SiteA and SiteB I can assign "Bandwidth xxxx" and use ~95% of the bandwidth to do queuing and shaping/policing ect. I am not concerned with SiteA and SiteB, that I think I can handle...
Question was posed from the customer, "How can we ensure at the DataCenter level the 40MB MPLS is "chopped" up so that only 8MB of the total speed goes to SiteA ALONG with an attached QoS policy designed for that specific site, as well as ensure only 4MB goes to SiteB with an attached QoS policy.
So I am looking for a way to allocate bandwith per site on the DC 40MB connection going into the cloud ( so that SiteB cannot use more than 4MB ) and attach a MediaNet specific QoS Service policy to that site. The customer does not have seperate MPLS circuits for each site, they all come into the DC on 40MB shared ethernet connection ( no VC, or dedicated circuits to other sites ).
Any thoughts on if this is possible?
Thanks!
Alex

This is an example I have seen and I hope that is useful to you.
Site A
Subnet: 172.16.1.0/24
Site B
Subnet:172.16.2.0/24
HeadOffice:
ip access-list extended Site_A
permit ip any 172.16.1.0 0.0.0.255
ip access-list extended Site_B
permit ip any 172.16.2.0 0.0.0.255
class-map match-any Site_A
match access-group name Site_A
class-map match-any Site_B
match access-group name Site_B
policy-map To_Spokes
class Site_A
shape average 8000000
service-policy Sub_Policy(Optional)
class Site_B
shape average 4000000
service-policy Sub_Policy(Optional)
class class-default
shape average 28000000
service-policy Sub_Policy(Optional)
Interface G0/0
Description To MPLS cloud
bandwidth 40000000
service-policy output To_Spokes
interface G0/1
Description To HeadOffice
bandwidth 40000000
service-policy output To_Spokes
It would be greatly appreciated if someone can correct this or improve it as I am still learning.
Please see the netflow graph from one of our routers using a similar policy as above.

Design validation for Internet over MPLS

We have a Network on MPLS backbone with dual service provider.
There are 50 spoke location.
DC and DR location
Topology is hub and spoke with all sites accessing data hosted at primary DC.
ALso in case of disaster all the spoke sites will connect to DR site.
Servers at DR site are on unique IP and failover from DC to DR is taken care by BGP routing intelligence.
Aim is to give controlled internet access to all the spoke sites from DC and incase of failure internet should be available from DR site.
As per our design architecture we are planning to upgrade the last mile bandwidth and MPLS port of all spoke sites and central site MPLS port bandwidth to give integrated access on the same last mile for all the locations.
Both types of traffic private and public will ride on the same MPLS bancbone and come to the primary DC site CE router.
At CE router we will segreggate the traffic meant for datacentre and internet cloud.
We will also deploy firewall and separate internet router and proxy server for the proposed internet connectivity to control the spoke sites traffic.
Is this a good design.
Pls suggest with configuration on how are we going to achiecve this
Also currently we are using BGP between CE-PE --- it should take care of the global routing meant for Internet traffic by flooding default route across all the spoke sites
Pls fins the existing architecute attahced.
Any inputs on the same will be appreciated.
Regards

As per your post you are looking for the solution to route internet via DC and on failure via DR.
To do this you can inject default routes from both DC and DR. in doing this all the PE's in SP1 and SP2 will have 2 defaults in the VRF table for you. But only 1 would be installed based on regular BGP path selection process.
To manipulate and select default from DC you can change any BGP path attribute and make the DC default favourable over DR default.
I did not understand where you are doing PBR, but anyway PBR will work in sync with CEF without putting any load on you CPU since IOS 12.0. So you can run PBR whereever you are running it.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_c/fqcprt1/qcfpbr.htm
To answer is this a good design or not, more inputs would be required as the current diagram is insufficient with legends, and the logic behind the creation of 3 vlans in the diagram is not explained in the post.
Its not clear which site are you designating as spoke site, as the remote sites box has dual routers and dual connections.
Since a good design of a network is more of what your data flow and business needs are and then based upon it, the technical design should meet the requirements put forth and scale as well at the same time. Here if you agree we dont have any of those inputs as well.
HTH-Cheers,
Swaroop

Internet Consolidation architecture

We have a Network on MPLS backbone with dual service provider.
There are 50 spoke location.
DC and DR location
Topology is hub and spoke with all sites accessing data hosted at primary DC.
ALso in case of disaster all the spoke sites will connect to DR site.
Servers at DR site are on unique IP and failover from DC to DR is taken care by BGP routing intelligence.
Aim is to give controlled internet access to all the spoke sites from DC and incase of failure internet should be available from DR site.
As per our design architecture we are planning to upgrade the last mile bandwidth and MPLS port of all spoke sites and central site MPLS port bandwidth to give integrated access on the same last mile for all the locations.
Both types of traffic private and public will ride on the same MPLS bancbone and come to the primary DC site CE router.
At CE router we will segreggate the traffic meant for datacentre and internet cloud.
We will also deploy firewall and separate internet router and proxy server for the proposed internet connectivity to control the spoke sites traffic.
Is this a good design.
Pls suggest with configuration on how are we going to achiecve this
Also currently we are using BGP between CE-PE --- it should take care of the global routing meant for Internet traffic by flooding default route across all the spoke sites
Pls find the existing architecute attahced.
Any inputs on the same will be appreciated.
Rgds

I think the design is fine. Following links may help you
http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/products_feature_guide09186a0080226103.html
http://www.cisco.com/en/US/netsol/ns587/networking_solutions_white_paper09186a008009d67f.shtml

WAAS Redirect Issues

I'm trying to setup a simple WAAS setup with a Manager, Core and Edge device. The core and edge devices are seperated across an MPLS cloud. The redirect is configured on the CE routers so I don't believe the MPLS is the problem.
The Manager can see both the Core and Edge devices but no acceleration is happening. When I check the wccp status on the core I see both LAN and WAN inetrfaces are redirecting packets but the edge router is only showing redirects on the LAN.
The edge router is a Cisco 2821 with a WAAS Services Module. The router is connected to the MPLS cloud by an ATM interface. (Config Below).
service timestamps debug datetime
service timestamps log datetime
service password-encryption
hostname xxxxxxxxxxx
boot-start-marker
boot-end-marker
logging buffered 10000 debugging
aaa new-model
aaa authentication login default group tacacs+ local
aaa authentication login conmethod group tacacs+ enable
aaa authentication enable default group tacacs+ enable
aaa authorization exec default group tacacs+ local
aaa authorization network default group tacacs+
aaa authorization network noauthor none
aaa session-id common
resource policy
clock timezone GMT 0
clock summer-time BST recurring last Sun Mar 2:00 last Sun Oct 2:00
ip wccp 61
ip wccp 62
ip telnet source-interface GigabitEthernet0/0
ip cef
interface Loopback0
description MPLS ATM Loopback Address
ip address 10.0.0.5 255.255.255.255
interface GigabitEthernet0/0
description London Corp LAN
ip address 53.253.7.250 255.255.255.0
ip access-group dealersubnets in
ip wccp 61 redirect in
duplex auto
speed auto
interface ATM0/3/0
no ip address
no atm ilmi-keepalive
dsl operating-mode auto
interface ATM0/3/0.1 point-to-point
description MPLS WAN
bandwidth 2000
ip unnumbered Loopback0
ip wccp 62 redirect in
no snmp trap link-status
pvc 0/38
vbr-nrt 248 248
encapsulation aal5mux ppp Virtual-Template100
interface Integrated-Service-Engine1/0
ip address 192.168.1.9 255.255.255.252
ip wccp redirect exclude in
service-module ip address 192.168.1.10 255.255.255.252
service-module ip default-gateway 192.168.1.9
no keepalive
interface Virtual-Template100
ip unnumbered Loopback0
no peer default ip address
router bgp 64527
no synchronization
bgp log-neighbor-changes
network 10.0.0.5 mask 255.255.255.255
network 53.253.7.0 mask 255.255.255.0
network 192.168.1.8 mask 255.255.255.252
neighbor x.x.x.x remote-as 2856
neighbor x.x.x.x ebgp-multihop 3
neighbor x.x.x.x update-source Loopback0
no auto-summary
ip route 0.0.0.0 0.0.0.0 x.x.x.x
no ip http server
no ip http secure-server
ip tacacs source-interface GigabitEthernet0/0
access-list 120 permit tcp any any log
If anyone can help me with this I would be most greatful as I need to get WAAS working ASAP.
The IOS version is c2800nm-spservicesk9-mz.124-9.T2.bin and the WAAS module is running 4.0.3.b.9
Thanks

I have implemented the above config and the wccp redirect on tcp 61 and 62 is now working. WAAS is now seeing traffic and optimising.
Why do you think that wccp want work on the atm interface?

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

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 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 Sizing - Enterprise Bandwidth Usage by Application

Hello Everyone,
In an effort to estimate bandwidth usage on an MPLS upgrade and rollout we have been tasked with determining what bandwidth is required without use of baseline measurements on live data.
Would anyone have a table or chart of applicaitons and their associated bandwidth requirements?
For example
SAP
Salesforce.com SAAS
desktop video conferencing
Email with attachments
etc
Thank you for your help,
Matthew

yeah... you bet, i considered all the options with access to the network.
Here is the scoop - Network is on 200 locations (MPLS), and I need to estimate for future applications.
I really really really wish for a chart that tells me BW per user per App...
dreaming?

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

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

Problems setting up MPLS

A Chairde,
Am having problems setting up MPLS between a AS5350 and 7609 , I have used commands stated in this link, enable MPLS incrementally on a network.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/switch_c/xcprt4/xcdtagc.pdf
The commands below are added to each router, and some troubleshooting.
7609
ip cef distributed
interface Loopback0
ip address 192.168.254.1 255.255.255.255
tag-switching advertise-tags
interface GigabitEthernet3/12
ip address 192.168.230.162 255.255.255.248
mpls label protocol tdp
tag-switching ip
AS5350
ip cef
mpls label protocol tdp
tag-switching advertise-tags
interface Loopback0
ip address 192.168.254.2 255.255.255.255
interface FastEthernet0/0
ip address 192.168.230.161 255.255.255.248
duplex auto
speed auto
mpls ip
h323-gateway voip interface
h323-gateway voip id cnibhco111 ipaddr 192.168.230.129 1719
h323-gateway voip h323-id cnibhco112
h323-gateway voip tech-prefix 71401
h323-gateway voip tech-prefix 0030
h323-gateway voip bind srcaddr 192.168.230.161
ip rsvp bandwidth 64 64
cnibhco112#sh tag-switching tdp neighbor
Peer TDP Ident: 192.168.254.1:0; Local TDP Ident 192.168.230.161:0
TCP connection: 192.168.254.1.49842 - 192.168.230.161.711
State: Oper; PIEs sent/rcvd: 18/23; Downstream
Up time: 00:12:54
TDP discovery sources:
FastEthernet0/0, Src IP addr: 192.168.230.162
Addresses bound to peer TDP Ident:
192.168.100.17 192.168.100.25 159.107.212.49 172.16.8.81
192.168.230.130 192.168.230.77 192.168.230.81 192.168.254.1
192.168.210.6 192.168.127.6 192.168.210.106 192.168.127.66
192.168.127.138 192.168.210.146 192.168.210.142 192.168.210.122
192.168.210.17 192.168.230.140 192.168.230.26 192.168.230.74
192.168.230.10 192.168.230.14 192.168.127.130 192.168.127.142
192.168.230.6 192.168.230.70 192.168.230.34 192.168.210.178
192.168.200.25 192.168.210.126 192.168.232.1 192.168.231.1
192.168.200.17 192.168.210.102 190.168.200.245 190.168.200.225
190.168.201.241 192.168.230.98 192.168.210.14 190.168.201.201
190.168.201.209 192.168.210.162 192.168.210.210 190.168.201.205
192.168.230.38 190.168.200.249 190.168.200.217 190.168.200.253
192.168.230.162
cnibhco112#
cnibhco112#sh tag-switching forwarding-table 192.168.254.1 detail
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
cnibhco112#traceroute 192.168.254.1
Type escape sequence to abort.
Tracing the route to 192.168.254.1
1 192.168.230.162 0 msec 0 msec *
cnibhco112#traceroute 192.168.230.162
Type escape sequence to abort.
Tracing the route to 192.168.230.162
1 192.168.230.162 0 msec 0 msec *
cnibhco112#

Ro,
Thanks for the respone, have been playin, with MPLS for last few hours.
The routing between the loopbacks is now working, can PING 7609 Loopback from AS5350 ,and vice versa. (used static routes).
Having problem with TDP / LDP on routers,
mpls label protocol ldp / tdp command works correctly on both routers, but the
tag-switching tdp router-id Loopback0 force
command works on the 7609, but when I add it onto the AS5350 , the command "mpls ldp router-id Loopback0 force" appears on the startup script.
The opposite is true for the 7609 , you add MPLS LDP command, and TAG-SWITCHING command appears instead.
Any Ideas, as different configs of this leave me with forwarding table with both tags added, but not been able to ping the loopbacks !!!
When I can ping bot loopbacks, the OUTGOING TAG , disapears.....
Problem is LOOPBACK Commands on bot routers default to LDP (AS5350) , or TDP (7609). Any Ideas ...
mpls label protocol tdp
tag-switching tdp router-id Loopback0 force
mpls label protocol tdp
mpls ldp router-id Loopback0 force
cnibhco100#sh tag-switching forwarding-table 192.168.254.2 detail
Local Outgoing Prefix Bytes tag Outgoing Next Ho
tag tag or VC or Tunnel Id switched interface
18 17 192.168.254.0/24 0 Gi3/12 192.168.2
MAC/Encaps=14/18, MRU=1500, Tag Stack{17}
00097CA3293000127FCDBA808847 00011000
No output feature configured
Per-packet load-sharing
cnibhco100#traceroute 192.168.254.2
Type escape sequence to abort.
Tracing the route to 192.168.254.2
1 192.168.230.161 [MPLS: Label 17 Exp 0] 0 msec 0 msec 0 msec
2 192.168.230.162 0 msec 0 msec 0 msec
But no PINGING 192.168.254.2
cnibhco112#sh tag-switching forwarding-table 192.168.254.1 detail
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
17 18 192.168.254.0/24 1915668 Fa0/0 192.168.230.162
MAC/Encaps=14/18, MRU=1500, Tag Stack{18}
00127FCDBA8000097CA329308847 00012000
No output feature configured
Per-packet load-sharing
cnibhco100#sh tag-switching forwarding-table 192.168.254.2 detail
Local Outgoing Prefix Bytes tag Outgoing Next Ho
tag tag or VC or Tunnel Id switched interface
18 17 192.168.254.0/24 752551 Gi3/12 192.168.2
MAC/Encaps=14/18, MRU=1500, Tag Stack{17}
00097CA3293000127FCDBA808847 00011000
No output feature configured
Per-packet load-sharing
WHEN BOTH LOCAL AND OUTGOING TAG, CANNOT PING EITHER WAY !!!
HAVE LABEL PROTOCOL AND LOOPBACK FORCE on AS5350
HAVE LABEL PROTOCOL ON 7609
WHEN ADD LOOPBACK FORCE on 7609 , CAN PING BOTH LOOPBACKS,
BUT OUTGOING TAG DISAPEARS
cnibhco112#PING 192.168.254.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.254.2, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
cnibhco112#sh tag-switching forwarding-table 192.168.254.1 detail
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
17 Untagged 192.168.254.0/24 598678 Fa0/0 192.168.230.162
MAC/Encaps=0/0, MRU=1504, Tag Stack{}
No output feature configured
Per-packet load-sharing
cnibhco112#
mpls label protocol tdp
tag-switching tdp router-id Loopback0 force

Urgent help need on configuring MPLS TE

i found that CSPF is not finding other path still there is no bandwith on SPF path and tunnel1 remain down if i down second tunne2 then tunnel 1 comes up not try to use other interfaces which r free with enough bandwidth. all router have MPLS TE and RSVP.
please read all in detail below
my freinds i have one Q. for MPLS TE. i m using 3660 router for MPLS TE on dayanagen simulater. in this lab there is 5 routers with 512 kbp RSVP on each interface all router with MPLS TE. configure are as->
R1 /0 ---R2 /0
R2 ==== R3 have Two interfaces s1/1 and s1/3
R2 /2-----R5 /2 interface connection
R3 ---- R5 int connection
R3 ---- R4 tunnel to R4 from R1,R2 with 300kb each
tunnel1 on R1 to R4 with 300kb rsvp TE
tunnel2 on R1 to R3 with 50kb rsvp TE
tunnel1 on R2 to R4 with 300kb rsvp TE
diagram like that below (ignore ..dots)
R1---R2=====R3----R4
.......I_______I
..........R5
i created tunnels from R1----> R4 with 300Kb.
second R1---->R5 with 50Kbp tunnel
and
on R2---->R4 tunnel with 300kbp.
PROBLEM IS when R1 tunnel go via R2 to R4 it takes s1/1 interface with 300rsvp. means for R2 tunnel should find next interface for same destination R4 becaused there is not enough space.On one of remaining on interfaces on R2 s1/3 or S1/2 but R2-->R4 tunnel remain down. when i down R1---R4 tunnel R2--R4 tunnel comes up on same interface. NOW when i up R2 tunnel first and later R1. then same thing again R1 down and wait for R2 tunnel to go down.then up on same interface. if u see there is still two path r free to go R4 on R2
1. R2 s1/3 ----> s1/3 of R3
2. R2 s1/2 ---->s1/2 of R5 with both 512 kb RSVP
there is using R2 s1/1 for tunnel
why not with help of CSPF it takes other path when 512 link is also free on R2 router to same destination??? its on dyanamips is it can problem with simulater.
it means that on R2 using SPF path for R4 for both tunnel and not trying to find other CSPF path thats why my two interfaces are free with 512kbp RSVP on same router R2. why not CSPF using other remaining path. and down one of tunnel because of there is no space on tht s1/1 interface........
PLZZ ANSER ME I NEVA USE MPLS TE B4
thanks in advance!

sorry m8 for late reply i had sort the problem. it occur because i was using 4 router now when i used TE with 12 router on daynagen it is working fine.
Question
now i have one question. i am trying to use TE with MPLS VPN site to site. as you know site to site MPLS VPN send traffic both way from R1 to R2 and R2 to R1.
but if i create MPLS TE tunnel1 on R1 to destination R2 then all traffic from R1 will go via tunnel1. but traffic from R2 wil go to R1 via normal route becasue tunnels is one way onli can see on R1
that means i have to create tunnels at both end in opposite directions. please reply me.
MPLS VPN site to site between R1 --- R2 have to create tunnels for both direction because tunnel work in on way?
R1 ---->R2 tunnel1
R1<-----R2 tunnel2
thanks

QOs detoriation with increase in bandwidth utilisation

we are the MPLS service provider providing MPLS services in India.we notice that Voice quality detoriates as soon as the bandwdith utilisation of the customer links increase more than 60% of link bandwdith particularly with FTP. we have implemented QOS properly. i am told that qos is ineffective if bandwdith utilisation increases more than 60% of link bandwdith. customer should be adviced to increase the bandwdith. Is it true? please help

Hi
AFAIK if u configure strict priority to your voice traffic (i.e.,LLQ for your voice)it shuldnt affect your voice traffic at all regardless to your bandwidth utilsation since it reserves a particular amount of B/W for your voip traffic which again can be configured manually.
The same you can do under your policy map configurations,hope you are having LLQ in place for your voice otherwise would suggest to look onto that and try out the same.
And when theres no congestion thts your h/w queue is ample enough to serve your traffic the software queues will be bypassed (which are manually configured) and if theres some congestion then your S/W queues kicksin.
so in a ideal customer network with voip and other traffic i would go with llq for voip and cbwfq for other traffic based on the traffic patterns using the DSCP,IP Prec values..
to be more precise you can go for LFI also to slice your packets so that your voip packets dont get backlogged..
regds

MPLS TE Bandwidth

Similar Messages

Maybe you are looking for