{"id":173,"date":"2011-02-09T16:12:41","date_gmt":"2011-02-09T16:12:41","guid":{"rendered":"http:\/\/gigihfordanama.wordpress.com\/?p=173"},"modified":"2012-08-08T00:14:11","modified_gmt":"2012-08-08T00:14:11","slug":"bgp-both-ibgp-and-ebgp-through-node-and-sublocalnode-inherent-indonesia","status":"publish","type":"post","link":"https:\/\/dosen.unila.ac.id\/gigih\/2011\/02\/09\/bgp-both-ibgp-and-ebgp-through-node-and-sublocalnode-inherent-indonesia\/","title":{"rendered":"BGP both ibgp and ebgp through Node and Sublocalnode INHERENT indonesia"},"content":{"rendered":"

The Border Gateway Protocol<\/strong> (BGP<\/strong>) is the protocol backing the core routing decisions on the Internet<\/a>. It maintains a table of IP networks or ‘prefixes’ which designate network reachability\u00a0 among autonomous systems<\/a> (AS). It is described as a path vector protocol<\/a>. BGP does not use traditional Interior Gateway Protocol<\/a> (IGP<\/strong>) metrics, but makes routing decisions based on path, network policies and\/or rulesets. For this reason, it is more appropriately termed a reachability protocol rather than routing protocol<\/a>.<\/p>\n

BGP was created to replace the Exterior Gateway Protocol<\/a> (EGP<\/strong>) routing protocol to allow fully decentralized routing in order to allow the removal of the NSFNet<\/a> Internet backbone<\/a> network. This allowed the Internet to become a truly decentralized system. Since 1994, version four of the BGP has been in use on the Internet. All previous versions are now obsolete. The major enhancement in version 4 was support of Classless Inter-Domain Routing<\/a> and use of route aggregation<\/a> to decrease the size of routing tables<\/a>. Since January 2006, version 4 is codified in RFC 4271<\/a>, which went through more than 20 drafts based on the earlier RFC 1771<\/a> version 4. RFC 4271<\/a> version corrected a number of errors, clarified ambiguities and brought the RFC much closer to industry practices.When BGP is running inside an autonomous system<\/a> (AS), it is referred to as Internal BGP<\/em> (IBGP <\/em>or Interior Border Gateway Protocol<\/em>). When it runs between autonomous systems, it is called\u00a0 External BGP<\/em> (EBGP<\/em> or Exterior Border Gateway Protocol<\/em>). Routers on the boundary of one AS exchanging information with another AS are called border or edge routers. In the Cisco\u00a0 operating system, IBGP routes have an administrative distance<\/a> of 200, which is less preferred than either external BGP or any interior routing protocol. Other router implementations also prefer EBGP to IGPs<\/a>, and IGPs to IBGP,<\/p>\n

From Wikipedia, the free encyclopedia<\/span><\/div>\n

 <\/p>\n

University Of Lampung as one of maintainer Network INHERENT area Lampung had already implemented this BGP protocol through the neighbor border router and subnode as a partner.\u00a0 We have two external border partner in difference province connected using metro-ethernet technology by PT Telekomunikasi Indonesia that is (UNSRI- Palembang) and (UNJA Jambi).<\/p>\n

And also there 11 partner already joint to Area Lampung as a Localnode, several metode for routing protocol are used;<\/p>\n

1.\u00a0 Static Route (mainly use).<\/p>\n

2.\u00a0 Dynamic with ospf (failed run on metro-e, until now i don’t now why \ud83d\ude41<\/p>\n

3.\u00a0 BGP (using ebgp).<\/p>\n

 <\/p>\n

FYI to whom it may concern, i will share for existing topology and logic connection on our CISCO 7606 series.<\/p>\n

as you imagine that, all of partner using Fibre Optic as media network, here is the logic configuration<\/p>\n

 <\/p>\n

en#sh run<\/p>\n

router ospf 100\u00a0 !!! (this one for internal purpose to distribute using OSPF protocol to Internal Unila)
\nrouter-id 167.205.190.9
\nlog-adjacency-changes
\nredistribute static
\nredistribute bgp 65009 subnets
\nnetwork 167.205.143.0 0.0.0.255 area 0
\n!
\nrouter bgp 65009
\nno synchronization
\nbgp log-neighbor-changes
\nnetwork 167.205.143.0 mask\u00a0 255.255.255.240 !!! (Unila main Network)
\nnetwork 167.205.143.16 mask 255.255.255.248 !!! ( Advertise Sublocalnode Partner)
\nnetwork 167.205.143.24 mask 255.255.255.248 !!! ( Advertise Sublocalnode Partner)
\nnetwork 167.205.143.32 mask 255.255.255.248 !!! ( Advertise Sublocalnode Partner)
\nnetwork 167.205.143.40 mask 255.255.255.248 !!! ( Advertise Sublocalnode Partner)
\nnetwork 167.205.143.48 mask 255.255.255.248 !!! ( Advertise Sublocalnode Partner)
\nnetwork 167.205.143.56 mask 255.255.255.248 !!! ( Advertise Sublocalnode Partner)
\nnetwork 167.205.143.64 mask 255.255.255.248 !!! ( Advertise Sublocalnode Partner)
\nnetwork 167.205.143.72 mask 255.255.255.248 !!! ( Advertise Sublocalnode Partner)
\nnetwork 167.205.143.80 mask 255.255.255.248 !!! ( Advertise Sublocalnode Partner)
\nnetwork 167.205.143.88 mask 255.255.255.248 !!! ( Advertise Sublocalnode Partner)
\nnetwork 167.205.180.24 mask 255.255.255.252 !!! ( Advertise Sublocalnode Partner)<\/p>\n

redistribute connected !!! (To Share routing information)
\nredistribute ospf 100 route-map DENY_PRIVATE_ADDRESS (To share ospf protocol)
\nneighbor 167.205.182.118 remote-as 65009 !!! (EBGP for Sublocalnode UPBJJ Lampung)
\nneighbor 167.205.182.118 next-hop-self !!! (Distributed to UPBJJ)<\/p>\n

neighbor 167.205.190.8 update-source Loopback0\u00a0 !!! (Loopback IP)
\nneighbor 167.205.191.173 remote-as 65011\u00a0 !!!(UNSRI- PALEMBANG)
\nneighbor 167.205.191.173 description UNSRI !!!(UNSRI- PALEMBANG)
\nneighbor 167.205.191.173 ebgp-multihop 255 !!!(UNSRI- PALEMBANG)
\nneighbor 167.205.191.173 soft-reconfiguration inbound !!!(UNSRI- PALEMBANG)
\nneighbor 167.205.191.178 remote-as 65012 !!!( UNJA-JAMBI)
\nneighbor 167.205.191.178 description JAMBI !!!( UNJA-JAMBI)
\nneighbor 167.205.191.178 ebgp-multihop 255 !!!( UNJA-JAMBI)
\nneighbor 167.205.191.178 soft-reconfiguration inbound !!!( UNJA-JAMBI)
\nmaximum-paths 4
\nno auto-summary<\/p>\n

ip classless
\nip route 167.205.143.32 255.255.255.248 167.205.182.110
\nip route 167.205.143.40 255.255.255.248 167.205.182.114
\nip route 167.205.143.48 255.255.255.248 167.205.182.118
\nip route 167.205.189.64 255.255.255.248 167.205.189.66
\nip route 167.205.190.8 255.255.255.255 167.205.189.64
\nip route 167.205.190.8 255.255.255.255 167.205.189.66
\nip route 167.205.190.8 255.255.255.255 167.205.189.68
\nip route 167.205.190.8 255.255.255.255 167.205.189.70
\nip route 167.205.190.11 255.255.255.255 167.205.191.173
\nip route 167.205.190.12 255.255.255.255 167.205.191.178<\/p>\n

interface GigabitEthernet1\/42
\ndescription to “SWITCH METRO ETHERNET\u00a0 TELKOM”
\nno ip address
\n!
\ninterface GigabitEthernet1\/42.2510
\ndescription TEKNOKRAT
\nencapsulation dot1Q 2510
\nip address 167.205.182.105 255.255.255.252
\n!
\ninterface GigabitEthernet1\/42.2511
\ndescription AMIK MASTER
\nencapsulation dot1Q 2511
\nip address 167.205.182.97 255.255.255.252
\n!
\ninterface GigabitEthernet1\/42.2512
\ndescription UBL
\nencapsulation dot1Q 2512
\nip address 167.205.182.109 255.255.255.252
\n!
\ninterface GigabitEthernet1\/42.2513
\ndescription STIBUN
\nencapsulation dot1Q 2513
\nip address 167.205.182.101 255.255.255.252
\n!
\ninterface GigabitEthernet1\/42.2515
\ndescription STKIP-M-KOBUM
\nencapsulation dot1Q 2515
\nip address 167.205.185.13 255.255.255.252
\n!
\ninterface GigabitEthernet1\/42.2516
\ndescription upbjj
\nencapsulation dot1Q 2516
\nip address 167.205.182.117 255.255.255.252
\n!
\ninterface GigabitEthernet1\/42.2550
\ndescription TEKNOKRAT
\nencapsulation dot1Q 2550
\nip address 167.205.185.1 255.255.255.252
\n!
\ninterface GigabitEthernet1\/42.2551
\ndescription STIE-SATUNUSA
\nencapsulation dot1Q 2551
\nip address 167.205.185.5 255.255.255.252
\n!
\ninterface GigabitEthernet1\/42.2552
\ndescription STMIK-TUNASBANGSA
\nencapsulation dot1Q 2552
\nip address 167.205.185.9 255.255.255.252
\n!
\ninterface GigabitEthernet1\/42.2553
\ndescription STIBA-YUNISDA
\nencapsulation dot1Q 2553
\nip address 167.205.185.165 255.255.255.252
\n!
\ninterface GigabitEthernet1\/42.2572
\ndescription DARMAJAYA
\nencapsulation dot1Q 2572
\nip address 167.205.182.113 255.255.255.252
\n!<\/p>\n","protected":false},"excerpt":{"rendered":"

The Border Gateway Protocol (BGP) is the protocol backing the core routing decisions on the Internet. It maintains a table of IP networks or ‘prefixes’ which designate network reachability\u00a0 among autonomous systems (AS). It is described as a path vector protocol. BGP does not use traditional Interior Gateway Protocol (IGP) metrics, but makes routing decisions … Continue reading “BGP both ibgp and ebgp through Node and Sublocalnode INHERENT indonesia”<\/span><\/a><\/p>\n","protected":false},"author":25,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1348,5],"tags":[],"class_list":["post-173","post","type-post","status-publish","format-standard","hentry","category-kiat-sukses-menjadi-seorang-network-engineer-2","category-old-post-dari-unilanet"],"_links":{"self":[{"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/posts\/173"}],"collection":[{"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/users\/25"}],"replies":[{"embeddable":true,"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/comments?post=173"}],"version-history":[{"count":0,"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/posts\/173\/revisions"}],"wp:attachment":[{"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/media?parent=173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/categories?post=173"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/tags?post=173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}