I have a question on how to influence my outbound traffic. I have 3 providers and let say i have 3 /24 networks. For the purpose of the config, i want one /24 going on my first ISP and the 2nd /24 going to the 2nd and 3rd /24 to my 3rd isp. And still when one isp goes down still the other /24 from the down isp will now go the 2nd isp and so on. Here is a sample of my diagram.
Do you know the prefixes that you want to send to each bgp router? Ie, you say /24 network, so do you know that you want say 192.168.0.0/24 to go to ISPa, 192.168.1.0/24 to ISPb, 192.168.2.0/24 to ISPc???
Or do you not know the prefixes for the remote networks?
Since you are taking full routes to net then you wont be able to be specific what routes go to which ISP etc..so I reckon your best way forward here would be for each core router to advertise default into your core, and each internal router will use closest core exit point.
At the core exit points you can config a route-map for each isp peer, so that routes 188.8.131.52 to 127.255.255.255 use ISPa and routes 184.108.40.206 to 254.255.255.255 use ISPb on core1 and on core2 config similiar so that 220.127.116.11 to 127.255.255.255 routes use ISPc and routes 18.104.22.168 to 254.255.255.255 use ISPb.
You can do this using access-lists and route-maps by setting the weights.
From the question, it sounds like your requirement is to have traffic sourced from a certain subnet (one of the 3 you mention) to use a certain ISP connection.
The solution provided by LR does not address this. It addreses what would be a requirement for load sharing outbound traffic to the Internet, dividing outbound traffic across 3 ISPs based on the destination address.
Dividing the oubtound traffic across 3 ISP based on the source, which is my network (3 /24).
Another thing, my diagram shows i have a router connected to each ISP and then connected to my core routers. Is it the same configuration on local preference if i remove all routers connected to my ISP and directly connect my ISP to the core routers ?
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 customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...