We have a private WAN network infrastructure with many circuits all across the country. There is one company that has a lot of sites co-located with us, but they have their own private WAN network. However, they can save money by using our private WAN network. So, essentially I will become their service provider. How do I separate their traffic from our traffic? My idea is to use DMVPN for their sites. Do I need to configure my routers to do the routing for them? What kind of solution or options do I have? Can I use MPLS VPN as one solution? How do I carve out a portion of bandwidth and just dedicated to them? Thank you so much in advance.
with DMVPN you need to route the VPN gateway addresss but not the other companies internal networks. Those would be withing the tunnels.
You could also go for MPLS VPN ... given the proper hardware and software supporting this AND you knowing what you are doing. Don´t underestimate the complexity. It´s not rocket science, but needs proper thoughtful design and understanding of the features and knobs.
Bandwidth "carving" is a QoS related question. Today DiffServ is used and you could use shaping and CBWFQ to give some guarantees. Be aware however that this is not a strict guarantee like a T1, which gives you always exact the same.
Hope this helps
P.S.: Be extremely careful when defining your SLAs ... customers have a tendency to push the SP to the limit of their contract (which you can only find out by trying to push OVER the limit ;-)
Thank you very much Martin to give me some idea. This brings another question. What advantages do MPLS VPN give me over IPsec VPN? We are not going to become a service provider and start taking in customers. Therefore if we go for MPLS, that means expensive hardware upgrade and lenthy network design.
MPLS VPNs have many nice features for a SP taking many customers. In your case I would say you just might have a look at "Multi-VRF" (aka vrf-lite) feature. No MPLS, no expensive hardware and no performance degrading encryption needed, but "clean" separation of IP routing domains.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...