BGP: Difference between revisions

;Protocol Specifications:

<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.