I've been playing around with PFR and trying to get an understanding of what I'm supposed to be seeing. I have a 4 router setup: 1 "ISP", 2 Border routers, and an internal router (MC). I have a loopback configured on ISP router 188.8.131.52. My BR1 is configured for a max-xmit-utilization of 2 percent and BR2 is just left at default. The MC has BR1 configured for throughput and delay and BR2 the same. BGP peering to ISP from both BRs and BRs to MC is iBGP.
What I had seen this morning was that pinging 184.108.40.206 from the MC with a large size and high repeat count allows for the MC to notice that it's OOP. I was under the impression that OER changes the routing table by either changing local pref or prepending AS numbers. What I had seen was the the MC changed it's local-pref for the 220.127.116.11 route to 5000 to BR1 and changed the route out to BR2. This was fine, but the return traffic from the ISP was coming back through BR1. It didn't seem like the MC changed anything at the BRs. Any ideas? Shouldn't I be seeing the change on the AS path at the ISP router? (this was in gns)
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
John, I've never used PfR's inbound load balancing, but recall it requires extra config beyond what's needed for outbound load balancing. Are you sure you're properly configured for inbound load balancing?
I think that by default PFR is used for influencing the outbound traffic.
In order to influence the inbound traffic there is a feature BGP inbound optimization
"The PfR BGP Inbound Optimization feature introduced the ability to support inside prefixes. Using BGP, PfR can select inside prefixes to support best entrance selection for traffic that originates from prefixes outside an autonomous system destined for prefixes inside the autonomous system. Company networks advertise the inside prefixes over the Internet using an Internet service provider (ISP) and receive advertisements for outside prefixes from an ISP."
This was for outbound traffic from the perspective of the MC to the loopback at the "ISP". The ISP is peered with ebgp and the BRs are peered with the MC with ibgp. I attached a diagram that I probably should have attached earlier
The problem that I have is that I was seeing the MC with a local pref of 5000. I was under the impression that the MC is supposed to make the change at the BRs. I also thought that I would see the bgp table on the ISP (18.104.22.168) with a prepended path from BR1 after it did the switchover to BR2, but that didn't happen.
This was fine, but the return traffic from the ISP was coming back through BR1. It didn't seem like the MC changed anything at the BRs.
I understood from your initial post that you saw that PFR changed the local pref of the ISP's loopback ( 22.214.171.124 ) to 5000 (which is the default value for the local pref, but also for the tag used on static routes ) and your issue was related to the traffic coming from the ISP to the 'client' ( which is the inbound traffic ).
As far as I know PFR influence the BGP preference only using local pref ( outbound ), and also by default it doesnt do anything regarding the incoming traffic.
Did I undestood well your issue, or was regarding the fact that you want to see prepended the ISP prefix in the 'client' network ?
The MC changed it's local pref to the 126.96.36.199 prefix to 5000 in its bgp table to point to BR2. The ISP still showed it's return route to the MC subnet through BR1, so in essence it was looping. Does that make sense? I'm going to play with it some more tonight after work and see if I can make any sense of it.
Oh...after reading your message...so you're saying that the MC was doing it's job by changing the path outbound but it doesn't change anyone's routing table on the outside of the network...I think I get it. I think ....
Yes. The main job of the PFR is to measure the performance of the local network - from the persepctive of the border routers - to reach the destination. So it will influence the outgoing traffic based on some defined parameters.
It seams that there is feature , that will influence also the incoming traffic : PfR BGP inbound optimization, which will do prepending on the prefixes advertised.
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...