- Bronze, 100 points or more
We are switching from an Internet VPN (GRE tunnels) WAN to the Sprint MPLS network. We are using EIGRP across it, as this was the simplest thing for the conversion. We have an OC-3 link at the Data Center on a 7606, and various T1/NxT1-PPP/DS3 links at the remote sites.
We are adding a second OC-3, using a second 7606. The initial turn up shows that the routes we receive on it have (mostly) identical metrics (the OC-3's are on separate PEs but in the same MPLS POP).
While we want to use both OC-3s (we will need to soon), we do NOT want to "load balance" (i.e. automatically) across them, especially not the VoIP traffic.
What we would like to do is, "direct" Group A remotes to come in via PE1 and Group B via PE2. We will periodically adjust membership in the Groups to roughly balance the load.
The SP has suggested SOO as a way to do this, but I'm not sure that's correct. I *do* think we will need SOO at some point, we are going to have a "backdoor" link to our DR site 1Q07, but I don't think SOO will do wat we want.
I looked around a bit and see that I can "set extcommunity rt" in a route map (found while looking at SOO), but my knowledge of MPLS and BGP is limited (the SP does use BGP in the MPLS WAN, of course). But "route target" surely sounds like it may apply.
Can someone give me a brief explanation of route target(ing) and/or any other suggestion by which we can accomplish this. The SP will not support multiple VRFs (I don't think) nor multiple EIGRP instances.
Thanks for the help!