Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About jonesl1
08-18-2017
Stats
Member since
04-12-2005
119
Posts
0
Helpful
0
Solutions
03-17-2015
07:31 AM
So ultimately we currently have one of the sites which is having a horrible connection to it's provider via MPLS. We are trying to prevent downtime to this site (and other problem circuits) by implementing a redundant scenario. So our intent is to add a router that has both the serial for the MPLS and an additional cellular card for when MPLS fails (whereas the current router only has the MPLS serial connection). There's nothing within the MPLS cloud preventing it from talking to other remotes, so in that respect it's mesh. However, the devices it needs to talk to typically reside on the central side. So we are merely trying to allow for a redundant connection when the providers connection starts running horrible. It's very intermittent, but continues to happen and the Telco advises that they can't see any problems.....hence this whole project. Ultimately, we are just attempting to use the redundant ASA VPN option for the sites with circuit issues.
... View more
03-17-2015
06:23 AM
Well you are correct in your thinking. I do have multiple other sites that would need to communicate back to that remote site. So I don't really want to advertise it from the central side. However, I guess I don't know how to not distribute it into bgp when I have 'redistribute static' set up in my BGP instance. How do I advertise the other statics, but not that one? I actually have over 100+ remotes. I do appreciate your concern and your regards for not just slapping in a config that partially works. That's what makes you respectable! Thank you!
... View more
03-16-2015
12:50 PM
You ARE AMAZING!!! You are absolutely right. That's exactly what it was. I created a route-map and changed the weight of that single route and sure enough....works GREAT! I do thank you. I guess I obviously won't need that route map nor that weight change once I get the device (new router) on the opposite end like it should be. That sound right?
Again, you have helped me a ton. Sorry I took up the majority of your day trying to hash this out, but I do appreciate all you've done and you'll definitely get the 5 star rating from me! :)
Thanks a ton Jon!
... View more
03-16-2015
12:24 PM
So how would I go about modifying the routes received from the PE to test that? I guess I'm not familiar with that part. It makes sense what you are explaining though.
... View more
03-16-2015
11:17 AM
And you are correct. When I shutdown loopback on Rtr A, central side MPLS doesn't receive the route and DOES failover to ASA. It just doesn't fail back.
... View more
03-16-2015
11:15 AM
Not you at all. :) I'm was just trying to understand the concept and implement into my scenario, hopefully eliminating a lot of the convoluted portions. However, some of those pieces you needed and I wasn't giving them. I do apologize. Routing entry for xx.xxx.1.164/32 Known via "bgp xxxxx", distance 20, metric 0 Tag xxxxx, type external Last update from xx.xxx.253 01:18:48 ago Routing Descriptor Blocks: * xx.xxx.3.253, from xx.xxx.3.253, 01:18:48 ago Route metric is 0, traffic share count is 1 AS Hops 2 Route tag xxxxx MPLS label: none Central site router looks like this: ip route xx.xxx.1.164 255.255.255.255 xx.xxx.2.226 200
... View more
03-16-2015
09:06 AM
On the central side, I'm redistributing Statics, which is where I'm introducing the route.
... View more
03-16-2015
09:02 AM
I'm sorry. I know it's confusing. It's kind of a special case and I'm doing a half test in production. Ultimately here is what I have. I have a router at one of our remote locations and it has a loopback interface on it. This router, we will call Router A. Router A is in production. It has a serial connection to MPLS and then it's local network. His loopback IP address is x.x.1.164. I'm trying to test with another router sitting here at my desk, we'll call router B. This device is set up the same (regarding IP's) as Router A as Router A will eventually be replaced with Router B. Router B's loopback is also x.x.1.164. This router has a cell card and also a Serial connection (however I can't use the serial because I don't have the circuit hear at my desk). Then I have the router at the central side which I'm doing my routing from that I've been trying to work out. So what I was doing was 'shutting down' the loopback on Router A (production) and attempting to get the routes to shift over in order to use the cell card (Router B) through the asa connection. Meanwhile I'm trying to do this while not taking down anything important on the production router, hence the loopback. :) Maybe this makes more sense. That's why I said, when I shutdown the loopback, I was referring to shutting down the loopback on the production router (Router A). I realize that wouldn't make sense after I sent it. :( Sorry about that.
... View more
03-16-2015
08:47 AM
Sorry, I mean just do a shutdown on the loopback interface. I just tried it and it seems like if I shutdown the loopback interface and then look at the central side router (where I'm doing the failover routing also the other end of the MPLS cloud), the bgp route doesn't show up any longer. Once I enable it again, it shows up Does this sound correct?
... View more
03-16-2015
08:37 AM
So if I disable the loopback on the remote router, I guess the serial interface of that remote router will continue to advertise that loopback route via BGP if it's still up (since it's still in the router bgp 12345 instance)?
... View more
03-16-2015
08:15 AM
Yes. No clients, just routing to other networks. So it failed over to the backup link (cellular) and stayed there. I looked at the bgp routes in the router and the bgp route for the remote loopback, which is what I'm pinging, is not there. However, If I remove the static route to the asa with the cost 200, it immediately pops back in the table and shifts back over to the primary route like it should. It's like it's not seeing the BGP route until I remove that static. Yes the BGP routes are covering all the remote networks and I am pinging one of them.
... View more
03-16-2015
08:07 AM
The internal interface of the ASA is just a point to point (255.255.255.252) to which I have connected to the router I'm trying to perform the routes on. For instance: This would be the router: int g0/0 ip address 192.168.10 6 255.255.255.248 int g0/2 ip address 192.168.10.225 255.255.255.252 ASA would have an internal interface of 192.168.10.226. There is no default route assigned on this network. Basically statically mapping each subnet. So right now I'm just routing the loopback IP to test with. Hopefully that makes sense.
... View more
03-16-2015
07:53 AM
Hey Jon! Thanks for responding. So I've tried that and it fails over just fine....very fast actually.....but for some reason I can never get it to fall back. I've waited quite a while to have it fall back over, but its like it won't. I've set my cost on my route to be 200 to make sure that it was >20. Does the backup link HAVE to fail in order for it to fall back? In the production scenario the backup is a cellular link and obviously we want to try and not use that as much as possible and that's why even though the cellular is up, I'd rather fall back to MPLS if its working.
... View more
03-16-2015
06:52 AM
Hello All, Needing some assistance with an IP SLA setup that I'm having some issues wrapping my head around. I have a router that has two connections to a remote site router. One connection from HQ-Rtr has a serial connection to an MPLS cloud using BGP as it's routing protocol. The other connection is an Ethernet connection to an ASA (which uses an IPSEC tunnel to the remote router). Here is what I'd like to do. I'd like to use the MPLS cloud connection as the primary connection. Once it fails, I would want the Ethernet connection to the ASA to kick in. However, I would like it to fall BACK over to the MPLS cloud connection in the event that the Serial connection comes back online. With that said, I know I'll have to use IP SLA to make this work but I'm running into an issue getting it to fall BACK to the primary route. I'm not sure why. I'm basically doing the following: track 1 ip sla 1 reachability ip sla auto discovery ip sla 1 icmp-echo a.a.a.a source-interface Serial1/0 request-data-size 32 ip sla schedule 1 life forever start-time now ip route 1.1.1.0 255.255.255.0 x.x.x.x track 1 (learned via bgp from cloud, metric 20) ip route 1.1.1.0 255.255.255.0 y.y.y.y 25 So, to me.....this says as long as I can ping a.a.a.a from source int s1/0, the route for network 1.1.1.0 should go to x.x.x.x. Then once it fails, it falls over to y.y.y.y. It requires the 25 cost so that it doesn't take precedence over the x.x.x.x route. Am I seeing this correctly so far? Then once x.x.x.x comes back online, it SHOULD fall back over to that one being it has the lower cost route of 20. Is this right? Well regardless it's not working quite as expected so someone had mentioned something about setting another IP SLA up with a 'Boolean and' statement. I'm not 100% sure about this so if anyone can explain this to me and how it would work in the above scenario or why it would be done, then that would help also. Here is what they suggested: track 2 list boolean and object 1 not and to change my routes to look like the following: ------Remove route for x.x.x.x all-together------- ip route 1.1.1.0 255.255.255.0 y.y.y.y track 2 I'm guessing (and I do mean guessing) this says to monitor track 1 and if track 1 is NOT true (false) then apply the route for y.y.y.y? Can someone take a look and help me with the concept, I guess maybe I'm in left field here but I'm struggling a bit on making this work. Thanks in advance,
... View more
Labels:
03-17-2015
So ultimately we currently have one of the sites which is having a
horrible connection to it's provi...
03-17-2015
Well you are correct in your thinking. I do have multiple other sites
that would need to communicate...
03-16-2015
You ARE AMAZING!!! You are absolutely right. That's exactly what it was.
I created a route-map and c...
03-16-2015
So how would I go about modifying the routes received from the PE to
test that? I guess I'm not fami...
03-16-2015
And you are correct. When I shutdown loopback on Rtr A, central side
MPLS doesn't receive the route ...
03-16-2015
Not you at all. :) I'm was just trying to understand the concept and
implement into my scenario, hop...
03-16-2015
On the central side, I'm redistributing Statics, which is where I'm
introducing the route.
03-16-2015
I'm sorry. I know it's confusing. It's kind of a special case and I'm
doing a half test in productio...
03-16-2015
Sorry, I mean just do a shutdown on the loopback interface. I just tried
it and it seems like if I s...
03-16-2015
So if I disable the loopback on the remote router, I guess the serial
interface of that remote route...
03-16-2015
Yes. No clients, just routing to other networks. So it failed over to
the backup link (cellular) and...
03-16-2015
The internal interface of the ASA is just a point to point
(255.255.255.252) to which I have connect...
03-16-2015
Hey Jon! Thanks for responding.So I've tried that and it fails over just
fine....very fast actually....
Public Statistics
| Date Registered | 04-12-2005 07:07 AM |
| Date Last Visited | 08-18-2017 04:03 AM |
| Total Messages Posted | 119 |
