Okay, I just got off the phone with a vendor and I have a better handle on what they're actually proposing. Here's the scoop:
They offer a couple of different variations of the MPLS solution. The first solution requires that we readdress our entire network to match their addressing scheme. This allows our branches to have any-to-any connectivity. Our routers do not need to be aware of MPLS. The vendor's network accepts frame relay encapsulated connections so our routers still think they're using frame relay. To make use of the multiple priorities within their network we use CAR or route-maps or whatever to set the TOS in the IP headers. Since each branch router will have only a single exit point, a single static route will suffice and no routing protocol is needed. Because of the readdressing issue we're just not interested in that variation. The second solution allows us to keep our existing addressing and they emulate our current frame relay PVCs within their network. This does not allow us to have any-to-any connectivity but it still allows us to use multiple priorities within their cloud. As expected, we'd need to continue to run our IGP of choice. Another downside is that their list pricing is roughly twice what we're paying for our frame network. :-) Not much incentive there! Still, it's an interesting thought and it could be useful to companies who want to use VoIP but have a lot of locations. They need to bring that pricing down, though. At that price point there's no way we'd even consider them. John >>> "Joseph Brunner" 2/27/02 11:09:20 AM >>> i was pitched this very thing recently by wcom and qwest.. basically it is only as secure as your carriers.. if some "f*cks up" and imports something into your VRF, either a default, another vpn, or whatever you security is finished.. plug banks are supposed to encrypt over IPSEC, so why bother running MPLS (come one how much diff-serv can do you on frac T-1's anyway) if you are just going to IPSEC the packets between pix's or vpn concentrators anyway.. MPLS right now for 100 sites, just can't be trusted. I used to work for ISP's, everyone there was a perp.. trust my vpn security to some loser ISP. No thanks read this http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/mxinf_ds.htm Joseph Brunner ASN 21572 MortgageIT MITLending New York, NY 10038 (212) 651 - 7695 Voice (212) 651 - 7795 Fax -----Original Message----- From: John Neiberger [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 27, 2002 12:24 PM To: [EMAIL PROTECTED] Subject: MPLS in the Enterprise [7:36670] Okay, I'm about to show how clueless I am when it comes to MPLS.... I've been getting calls from multiple providers lately all trying to suggest that I migrate our 100-site frame relay network to their MPLS network, suggesting that we'll have any-to-any connectivity and the ability to prioritize traffic classes within the MPLS network. Are any of you doing something like this? I'm going to read up on it but I'm having trouble visualizing it. Does this basically turn our network into a giant multipoint network? Do our branch routers need to be aware of MPLS or do providers make this transparent somehow? How does this affect routing? It seems that if we have any-to-any connectivity then the branch routers don't even need to run a routing protocol; every router would have one exit point to get to any destination. But, how would the MPLS cloud know where to route packets? The more I think about it it seems like our branch routers would have to participate in MPLS to provide the necessary destination info for the MPLS cloud. See how clueless I am? Ugh... Time to do some studying on this. Since we already do a little video conferencing over IP and are working on getting VoIP working, it might be beneficial to get away from the frame relay network. But since I don't understand this new technology, I don't know if it's a viable solution for us or not. Off to CCO I go! Thanks, John Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=36681&t=36670 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
