BGP: Difference between revisions
→Introduction
Line 4:
=Introduction=
;Protocol Specifications:
BGP is needed for redundancy of servers. BGP is not used for providing redundancy to users for internet access.▼
<center>
{| class="wikitable"
|-
|Protocol Type || Path vector
|-
|Peering mechanism || Manual peering between neighbors
|-
|eBGP AD || 20
|-
|iBGP AD || 200
|-
|Rights || Open standard
|-
|Supported protocols || IPv4, IPv6
|-
|Transport || TCP/179
|-
|Update mode || Only triggered
|-
|Timers || Hello (60 sec)
|-
|Authentication || None, MD5
|-
|Specifications || RFC 4271
|}
</center>
<br />▼
* Usage applications
▲ BGP is needed for redundancy of servers. BGP is not used for providing redundancy to users for internet access.
Customer connected to multiple Internet service providers (ISPs).
Service provider networks (Transit autonomous system).
Network cores of very large enterprise networks (distribution or core layer)as a backup or redundant routing protocol due to its stability.
* Customer's Network will become a Transit Autonomous system if ISP traffic passes through your AS.
* Session Establishment facts
Line 11 ⟶ 46:
TCP port 179 is used.
Only one session remains if both connection attempts succeed.
▲<br />
* Without tuning behaves like RIP, considers AS as a Hop.
* BGP is an advanced Path Vector Protocol and has following advantages:
Reliable updates (using TCP)
Triggered updates only
Line 22 ⟶ 55:
Scalable to massive networks
Updates are Incremental and Triggered
==BGP States==
Line 31 ⟶ 63:
OpenConfirm Response received
Established Adjacency established
== BGP Messages ==
Line 38 ⟶ 69:
Keepalive Sent every 60 seconds
Notification Always indicate something is wrong
== BGP Tables ==
Line 45 ⟶ 75:
BGP Table List of All BGP Routes(Can be Huge)
Routing Table List of Best Routes
=BGP Route selection criteria<ref>www.accenture.com</ref>=
| |||