How can I manipulate incoming traffic from a specific prefix from my ISP to come through my other ISP to elevate the traffic on my 1 peer router?
I have the following setup:
I noticed that traffic for a prefix from ISP-A 22.214.171.124/16 (streaming) is congesting my WAN interface on Rtr-A. I would like to be able to push the traffic "INBOUND" from 206.160.170./16 through ISP-B/RTR-B. I know that I can manipulate the "localpref" to do the outbound traffic, but want to do this for only this prefix, which this prefix is part of ISP-A AS.
enable net flow and determine which /24s of the /16 are causing highest utilization and then you should be able to receive those on different routers by using AS path using community in a routing policy that can essentially load balance your traffic.
There are a few ways to solve this problem. With out knowing a bit more about your configuration i'll just throw out a few ideas.
1) you can use conditional advertisements, remove the prefix in question from ISB-A and advertise it through ISP-B. With conditional advertisements you still maintain failover capabilities as the prefix will be advertised through the other ISP in the event of a failure if configured correctly.
2) AS prepending, append the AS a few times to make the inbound routes less desirable through ISP-A.
The supernet 126.96.36.199/16 is owned and advertised by AS 1239
ROUTER1#show ip ro 188.8.131.52 Routing entry for 184.108.40.206/16, supernet Known via "bgp 65001", distance 20, metric 0 Tag 1239, type external Last update from xxx.xxx.xx.77 7w0d ago Routing Descriptor Blocks: * xxx.xxx.xx.77, from xxx.xxx.xx.77, 7w0d ago Route metric is 0, traffic share count is 1 AS Hops 1 Route tag 1239
ROUTER1#show ip bgp 220.127.116.11 BGP routing table entry for 18.104.22.168/16, version 20423274 Paths: (1 available, best #1, table Default-IP-Routing-Table) Advertised to update-groups: 1 1239 xxx.xxx.xx.77 from xxx.xxx.xx.77 (xxx.xxx.xxx.121) Origin IGP, metric 0, localpref 200, valid, external, best Community: 81199227 81200104 81200107
-As at this time I have the localpref set for 200 for the routes received from AS 1239 at this time on Router 1 and localpref set for 150 for the routes received from AS 30263 on Router 2.
As noted from Router 2 the following output for 22.214.171.124:
ROUTER2#show ip ro 126.96.36.199
Routing entry for 188.8.131.52/16, supernet
Known via "bgp 65001", distance 200, metric 0
Tag 1239, type internal
Last update from xxx.xxx.xx.77 3w0d ago
Routing Descriptor Blocks:
* xxx.xxx.xx.77, from 10.255.1.1, 3w0d ago
Route metric is 0, traffic share count is 1
AS Hops 1
Route tag 1239
ROUTER2#show ip bgp 184.108.40.206
BGP routing table entry for 220.127.116.11/16, version 116873587
Paths: (3 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
xxx.xxx.xx.77 (metric 19200) from 10.255.1.1 (10.1.10.11)
Origin IGP, metric 0, localpref 200, valid, internal, best
-- The issue is that the traffic from this particular prefix is high BW and I would like to move it through Router 2
- I understand if I change the local pref then this will change the direction of going out through Rtr 1 - By adding an additional line to the Route-map and filtering it to the specific prefix correct to set the pref lower through Rtr 1
-But In order to make the "incoming" prefer Router 2 - just for that 1 prefix 18.104.22.168/16 is not possible?
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 custome...