|
|
|
<br />
= iBGPEBGP vs eBGPIBGP =
{| class="wikitable"
|-
! eBGPEBGP !! iBGPIBGP
|-
| peeringPeering is between two different AS || Peering is between same AS
|-
| Routes learned from eBGP peer will be advertised to other peers (EBGP or IBGP) || routesRoutes learned from IBGP peer will not be advertised to other IBGP peers but, can be advertised to an EBGP peer.
|-
| By default, EBGP peers are set with TTL = 1, which means neighbors are assumed to be directly connected.<br />We canCan change this behavior for EBGP by using command “neighbor x.x.x.x ebgp-multihop <TTL>”. <br />Multihop is the term used in EBGP only.|| For IBGP peers dont need to be directly connected.
|-
| routesRoutes have administrative distanceAD of 20 || whereasRoutes IBGPhave hasAD of 200
|-
| Next hop remains unchanged when route is advertised to IBGP peer.<br />It is changed when it ison advertised to EBGP peer by default.<br />This default behavior of IBGP can be changed by the command “neighbor x.x.x.x next-hop-self”;<br /> this changes the next hop, while advertising, as a local route.routers || Next-hop IP will not be changed when adv prefixes to another IBGP.
|}
|