I'm having an issue with my MPLS. I'm not sure the best way to describe it other than an example.
I connect to a website owned by Chrysler. Sometimes it works, oftentimes portions of the site do not respond.
My first step is pinging the remote network. If I get a reply, it is something like wg.random#.dc.chrysler.com. If I don't get a reply, I have to wait 10-15 minutes for another server to reply (wg.random#3.dc.chrysler.com).
When I traceroute during a Request timed out, I make it about 4 or 5 hops outside my MPLS router. My MPLS provider blames it on everyone outside their network.
If I go out my backup ISP provider (Cox fiber), it always works all of the time.
I want to use Cox in 2 situations. The first is when my MPLS goes down (floating static route). The second is to send Chrysler traffic out my Cox interface when MPLS to Chrysler fails.
Because there are a ton of destination servers and a large IP range, is it possible to send traffic headed to Chrysler out my Cox interface while keeping all other traffic flowing through my MPLS network?