assume you have rather restrictive filters (prefix-list) in place and accept only 1000 routes from the full internet BGP table. This means your neighbor is sending 200000 prefixes and you discard 199000 of them.
In this situation ORF comes in to optimize the BGP update procedure. Basically your BGP router would send its incoming prefix-list to the neighboring BGP peer. This peer would then apply your inbound prefix-list to its updates before sending the updates and only deliver the 1000 routes you are willing to accept.
So the gain is 199000 prefixes less to send, i.e. faster convergence, and your router has less CPU load with update processing.
Loop detection is for loop detection, whereas prefix-lists can achieve various results. Mainly in conjunction with ORF they block unwanted prefixes. As an example: one would probably not want to accept RFC1918 IP networks or BOGONs or the like. They would not create any loop, but could be harmful for your internal IP routing (AD of eBGP is 20, OSPF f.e. 110).
So ORF does not really address BGP loops, but does allow for efficient update processing.
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...