This post is about extending your OSPF routing domain through a VRF in a MPLS backbone. If you are unfamiliar with the MPLS side of things check the previous post out. This post only focuses on the PE/CE side of things, it assumes that a working MPLS backbone has been set up.
Then you have the choice of if you plan on using the MPLS link as a primary link or as a backup.
Here is a step by step example of how to set up a very simple MPLS-VPN. Like last time I am doing this entirely in GNS3 using 2691s running 12.4(25d).
Just a bit of a discussion on the previous post.
Why would you use this, on a slightly more serious note than before – in all honesty I think you probably wouldn’t. But the point is it gives you the same kind of per-flow control that a lot of people seem to be looking forward to getting from SDN. It seems silly to me, but hey, if you want it, you can get it now.
The other point, is that by using MPLS-TE you only need to define the flow at its ingress point into the MPLS network. Using straight up vanilla PBR and you would have to configure all the links in the path.
Potentially in a very large scale data centre, you could – but I don’t see it happening. A more practical use case would be a large-scale MPLS WAN. If you have a large non-hierarchical WAN. Possibly you have a large number of links for redundancy but the layout does not use a nice campus-style 3 layer design due to geographic or optical fibre constraints. Due to the layout you will end up with some links completely underused – you could potentially tweak your per-link IGP metrics – but this might not even work depending on the topology.
Potentially you might have specific services that are bandwidth intensive – say, CCTV with offsite storage? Remote office data centre backups? Services that can be easily defined and may not be highly user-interactive so some added latency won’t be an issue.
But realistically, if you are that constrained for bandwidth, I think you will have other issues. Also remember if you are using all your redundant links – then they are no longer redundant links. It should be unnecessary for me to say that, but I often hear people complaining about spanning-tree blocked links, standby firewalls or backup Internet links complaining that they aren’t getting any use out of paid for resources. Well you are, it’s there if the primary breaks. If you use both (more than 50% anyway) and one breaks – then performance will degrade – which is not so good.
So the point of this post is to define a per-flow explicit path. Rather than just routing it one way or another using MPLS-TE, route some traffic one way and some another using some Policy Based Routing.
Here is a step by step configuration example to configure a specific path using MPLS-TE tunnels.
This was originally going to be a post about MPLS Fast Reroute. However two things happened, one the post became excessively long and two, I realised none of my simulated routers support MPLS FRR. Also, the Cisco Feature Navigator is lying to me again (FRR is supported on a 6500, FN claims this isn’t so.)