Thanks a lot for the advice, Kindly bear with me for this mail.
Yes seems that I am a little confused on the TE & VPN parts. My
understanding is that I could offer bandwidth guarantees between two sites
that require connectivity, Something similar to layer 2 techniques. Could
I be enlightened on how I could ensure comitted bandwidth between two
sites that are part of a corporate Intranet on my MPLS core. Assuming a
customer requires VPN connectivity between US & UK with a bandwidth
requirement of 2 Mbps, Is it possible to offer comitted bandwidth of 2
Mbps for this customer. When you mean TE is usually used for providing
aggregate reservations, Do you mean that TE can only offer comitted
bandwidth for all VPN traffic that traverses that particular engineered
path? This solution is for a customer who wants to get rid of all his
Frame Relay circuits & get on with MPLS, which would reduce his
operational overheads. Kindly enlighten me.
I am sorry for confusing you on the Frame Relay access part, What I meant
was, AT&T has an interesting offering built using Cisco BPX switches. They
claim that customers requiring connectivity to multiple circuits can
purchase only a single PVC to the nearest AT&T POP, & get connected to any
number of sites required. They claim that this is possible only because
their core is built on MPLS. So I was confused on how they provide last
mile guarantess. For example if a customer uses a single E1 last mile
stream & connects to two sites over AT&T's MPLS cloud, Wherein each of his
connection requires 1 Mbps of bandwidth, How would the provider restrict
each connection from over utilizing the last mile bandwidth.
Lastly are there any tools from the Cisco family that could offer SLA
reports for MPLS VPN's. Say something like proving to a customer that he
has been getting the promised Class of service in terms of bandwidth etc.
Kindly advice.
With warm regards,
Vinod.
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:21 EDT