Hi All,
Once again another doubt in mind. It is on providing bandwidth & delay
guarantees for MPLS based VPN's. My understanding is that traffic
engineering will do the job which can be achieved using RSVP.
But how will the delay on a per connection (per link) basis be guaranteed.
I also understand that there are many ways to achieve traffic engineering,
Is RSVP a scalable or reccomended method.
Given an example wherein a customer has the following requirement - He
needs two connections to two of his branch offices & one conection to the
Internet with the follwing bandwidth requirements -
Connection to branch A - 512 Kbps
Connection to branch B - 512 Kbps
Connection to the Internet - 1 Mbps
Now If I am to provide him with a single last mile connection using an E1
(2.048 Mbps) circuit into my PE router on which all his connections
terminate. I would also need to control how is bandwidth is allocated
end-end. Now on the Service provider network I will use "traffic
engineering" for guaranteeing bandwidth. But on the Ingress (ie on the
last mile) How will I ensure that Internet traffic is given 1 Mbps
bandwidth, & the other two circuits are allocated 512 Kbps each. Will I
need to use something like CAR at the Ingress, or can MPLS traffic
engineering be extended to the last mile.
In the service provider net, All the backbone routers ie the transit
points, will be running a IBGP mesh, Now will it be advised to terminate
MPLS customers on those routers, which again will need an MBGP exchange.
Or is it adviced to keep the MPLS PE routers seperate from the backbone
routers (Keeping IBGP / EBGP seperate from MBGP).
Kindly advice
With kind regards,
Vinod.
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:20 EDT