03-06-2007 12:44 AM - edited 03-03-2019 04:02 PM
Can anybody please explain why routes learned from an iBGP peer aren't propagated to other iBGP peers (hence the need for full mesh or reflectors)?
03-06-2007 12:54 AM
Hi
They aren't propogated under normal circumstances to avoid routing loops. EBGP can use the AS Path in the routing update to ensure that there are not routing loops ie. if the router sees it's own AS in the AS Path it knows there is a potential routing loop and so will not accept the route under normal circumstances.
Because the AS Path does not get changed when routes are exchanged between IBGP peers the router has no way of knowing if there is a potential routing loop.
HTH
Jon
03-06-2007 01:05 AM
Ok, this makes sense. Since an IGP is responsible for forwarding the updates between the iBGP peers, wouldn't it be the IGPs responsiblity to ensure no loops to get to the next AS hop. The only problem I can see with iBGP forwarding updates to other iBGP neighbors is possibly sub-optimal routing to get to the nearest "edge" BGP peer.
03-06-2007 01:13 AM
It can't really be the IGP's responsibility because it is just another bit of IP traffic to the IGP. And the IBGP speaking router stores the updates in a separate table - the BGP table. Only then will it decude whether to install it in the IGP routing table.
Before this the IGP is used merely to transport some tcp traffic between 2 routers.
HTH
Jon
03-06-2007 02:03 AM
Thanks for your help!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: