‭BGP DATA STRUCTURE‬

‭1.‬ ‭BGP Neighbor table‬

‭2.‬ ‭BGP table‬
‭3.‬ ‭IP routing Table‬

‭BGP Neighbor Table‬

‭BGP Table‬

‭●‬ N ‭ ext hop 0.0.0.0 - My router originate this prefix‬‭(Probably learned via EIGRP, OSPF‬
‭and injected into BGP or network statement)‬
‭●‬ ‭Under Path ONLY have entry “i” - This prefix live in our AS‬
‭●‬ ‭Left side i - route learned via iBGP neighbor‬
 ‭●‬ C ‭ onsider‬‭1st entry above,‬‭our AS is connected to AS 65004 which is connected to other‬
‭AS 65003 and‬‭network‬‭9.9.9.9/32‬‭originated in AS 65003‬‭(rightmost AS)‬
‭●‬ ‭r-RIB Failure‬‭-‬
‭○‬ ‭Most common reason are,‬‭there is another route with‬‭better AD‬‭,‬
‭○‬ ‭Due to memory limitation cannot add new route to routing table,‬
‭○‬ ‭Administrative limit has reached on how many routes can be learned in particular‬
‭VRF.‬

‭These routes will not be put in the routing table nor will be advertised to neighbors.‬

‭̀‬

‭IP Routing table‬

‭ GP Neighbor States‬
B
‭»‬‭Idle‬‭: The‬‭BGP process‬‭is either‬‭administratively‬‭down or awaiting‬‭the‬‭next retry‬‭attempt.‬
‭»‬‭Connect‬‭: The BGP process is‬‭waiting for the TCP‬‭connection to be completed‬‭.‬
‭»‬‭Active‬‭: The‬‭TCP connection failed‬‭, Connect-Retry‬‭timer running, listening for incoming TCP‬
‭connection.‬
‭»‬‭Opensent‬‭: The TCP connection exists, and a BGP‬‭Open‬‭message has been sent‬‭to the peer,‬
‭but‬‭the matching‬‭Open message has not yet been received‬‭from the other router.‬
‭»‬‭Openconfirm‬‭: An‬‭Open message has been both sent‬‭to and received‬‭from the other router.‬
‭»‬‭Established‬‭: All‬‭neighbor parameters match‬‭, the‬‭neighbor relationship works, and the‬‭peers‬
‭can now exchange Update‬‭messages.‬

‭The overall process works as follows:‬

‭●‬ ‭A‬‭router tries to establish a TCP connection‬‭with‬‭the IP address listed on a neighbor‬
‭command,‬‭using‬‭well-known‬‭destination port 179‬‭.‬