-
Interdomain routing protocol
-
use TCP port 179 to establish connections with BGP neighbors.
-
iBGP for internal neibour, within the same AS.
-
eBGP for external neibour, usually the enterprise - service provider.
By default, BGP will select only one path to reach the des, unless admin specifies it to max paths.
When the path is selected, then BGP puts the selected one into the routing table and propagates to its neighbors.
CLI is:
$show ip bgp
the algorithm looks like this:
-
if next_hop !is accessible: drop path
-
if path isInternal == TRUE and isSync == True and Path isInIGP: drop path
-
if toR1_Weight > toR2_Weight: select R1
4.~ 11. (to be continued...)
AS300 R ------- R AS100 R ------- R AS400
R
|
|
|
R
AS200
eBGP exchanges routes between ASs. And it is commonly used between enterprises and their service providers.
AS100 AS200 AS300
R1 R2 R3
R
/ \
peer peer
/ iBGP \
R --- peer --- R
AS500
it is a term that describes the peering between BGP neighbors in the same AS. It is usually used in transit ASs. Transit ASs means to forward traffic from one external AS to another AS.
If the transit AS does not use above mentioned iBGP, then it will be bothering to set up to let Router be into IGB via Redistribution, and the into another eBGP router also using Redistribution.
USA R iBGP Core R JP
IGP IGP
R R
R R
Africa
IGP
-
Use confederation (結盟) to reduce BGP Peering Overhead.
-
Use Route Reflectors to reduce BGP Peering Overhead.
-
Use MED to influence Inbound Traffic.
-
Use Weight to influnce Outbound Traffic's path from a router which is configed locally.
to use PBR to change the addr ot the IP packets based on policy.