0% found this document useful (0 votes)
12 views3 pages

BGP 4

Download as pdf or txt
Download as pdf or txt
Download as pdf or txt
You are on page 1/ 3

‭ here are two kinds of AS numbers: public and private.


T
‭Public AS numbers can be advertised over the Internet.‬
‭Private AS number should not be advertised over the Internet.‬

‭The range for public and private AS numbers is :‬


‭●‬ ‭Public AS numbers 1 – 64495‬
‭●‬ ‭Private AS numbers 64512 – 65534‬
‭The following numbers and ranges are reserved:‬
‭●‬ ‭0, 64496 – 64511, 65535‬
‭When we have a single ISP we can use private AS numbers. If we have different ISPs we need‬
‭to use Public AS Numbers‬

‭Note: BGP does not use multicast but all communication is with unicast pkt.‬

‭ BGP Neighborship‬
e
‭Overview‬
‭» Like any other routing protocol, BGP must also complete three steps to get best routes:‬
‭1.‬ ‭Form neighborship‬
‭2.‬ ‭Exchange topology information‬
‭3.‬ ‭Run a best-path algorithm.‬
‭» BGP forms neighborship using TCP port 179.‬
‭»‬‭BGP neighbors do not need to be on the IP subnet‬‭.‬
‭» To configure eBGP neighbors, use the following commands:‬
router bgp <asn> (global command)‬

neighbor ip-address remote-as <remote-asn> (BGP subcommand)‬

‭» The following‬‭requirements must be met‬‭for routers‬‭to become neighbors:‬


‭●‬ A ‭ ‬‭local router’s ASN‬‭(on the router bgp asn command)‬‭must match‬‭the neighboring‬
‭router’s reference to that ASN with its‬‭
neighbor‬‭ remote-as‬‭ asn‬‭command‬‭.‬
‭●‬ ‭The BGP‬‭router IDs‬‭of the two routers‬‭must not be‬‭the same‬‭.‬
‭●‬ ‭If configured, MD5‬‭authentication‬‭must‬‭pass‬‭.‬
‭●‬ ‭Each router must be part of a TCP connection with the other router, with the‬‭remote‬
‭router’s IP‬‭address used in that TCP connection‬‭match‬‭ing‬‭what the local router‬
‭configures‬‭in a BGP‬‭
neighbor remote-as‬‭command‬‭.‬

‭» The BGP router-ID is elected as follows:‬


‭1.‬ ‭Use configured Value‬ ‭(‭ ‬ gp router-id <rid>‬
b
‭2.‬ ‭Highest‬‭IP address of any‬‭up/up loopback‬‭interface‬
‭3.‬ ‭Highest‬‭IP address of any up/up‬‭non loopback‬‭interface‬

‭» The third requirement for BGP neighborship is the MD5 authentication check.‬

‭eighbor neighbor-ip password <key>‬‭(BGP subcommand)‬


n
‭This command must be configured on both routers and match.‬

‭ ote‬‭: BGP carry password in TCP header (EIGRP and‬‭OSPF carry it in their own header)‬
N
‭0 - you can enter plain text password (it still be md5 hash password)‬
‭7 - You need to put pre-encrypted password‬

‭ GP Update Source and multihop requirement‬


B
‭» The local router tries to form a TCP connection with the IP address defined in the‬‭ neighbor‬
remote-as‬‭command. This TCP connection should form‬‭before BGP messages flow over this‬

‭TCP connection.‬
‭» Router 1st search for connected route in its routing table to reach neighbor. (If direct route not‬
‭found, by default eBGP neighborship will not formed)‬
‭» 2nd The local router then finds the outgoing interface to be used to reach that IP address.‬
‭» The IP address of the‬‭outgoing interface is used‬‭as the source IP address for TCP connection,‬
‭by default.‬
‭» This is true for the other direction as well.‬
‭» What happens when there are two links or redundant Layer 3 paths between the same pair of‬
‭routers?‬
‭» The failure in one link can cause BGP neighborship to fail.‬
‭» There are two solutions to resolve this issue:‬
‭Configure two neighbor commands on each router.‬
‭Use loopback interfaces as the TCP connection endpoints.‬
‭» The use of two neighborship between the same pair of routers can consume bandwidth and‬
‭more memory in the BGP table.‬
‭» To configure eBGP neighborship using loopback interfaces, follow these steps:‬
‭1. Configure an IP address on a loopback interface on each router.‬
‭ . Configure the BGP neighbor command on each router to refer to the other router’s‬
2
‭loopback IP address‬
‭3.‬‭Tell BGP on each router to use the loopback IP‬‭address as the source IP address‬
‭using the‬‭ neighbor update-source <ip-address>‬‭command.‬
‭4. Make sure each router has IP routes so that they can forward packets to the loopback‬
‭interface IP address of the other router.‬
‭5. Configure eBGP multihop using the‬ ‭ neighbor ebgp-multihop‬‭command.‬

‭ By default, when building packets to send to an eBGP peer, IOS sets the IP Time-To-Live‬
»
‭(TTL) field in the IP header to a value of 1.‬
‭» as the packet with TTL value of 1 gets dropped.‬
‭»‬‭TTL value is decremented by 1‬‭before giving the‬‭packet to the loopback interface hence drop‬
‭and eBGP neighbors do not come up‬
‭» To increase TTL value,‬‭use the neighbor‬‭
ebgp-multihop‬‭command‬‭.‬

‭» To verify eBGP neighbors, use the following commands:‬


‭●‬ ‭show ip bgp summary‬
‭●‬ ‭show ip bgp neighbors‬

‭LAB‬

i‭BGP Neighborship Requirements‬


‭» When is iBGP neighborships required?‬
‭» When two Internet-connected routers need to communicate BGP routes to each other‬
‭because these routers may want to forward IP packets to the other Internet-connected router.‬
‭» The neighborship requirements for iBGP are the same as eBGP except for the “asn” value in‬
‭the neighbor remote-as asn command.‬

You might also like