Pada lab ini kita akan mencoba melakukan peering IBGP dan EBGP Peering pada router cisco menggunakan physical interface. Berikut topologi yang akan kita gunakan pada lab ini
 |
| Gambar 1 Topologi jaringan BGP |
R1(config)#int e0/0 R1(config-if)#no sh R1(config-if)#ip add 12.12.12.1 255.255.255.0 R1(config-if)#int lo0 R1(config-if)#ip add 1.1.1.1 255.255.255.255 R1(config-if)#router bgp 12 R1(config-router)#neighbor 12.12.12.2 remote-as 12 R1(config-router)#network 1.1.1.1 mask 255.255.255.255
R2(config)#int e0/0 R2(config-if)#no sh R2(config-if)#ip add 12.12.12.2 255.255.255.0 R2(config-if)#int lo0 R2(config-if)#ip add 2.2.2.2 255.255.255.255 R2(config-if)#router bgp 12 R2(config-router)#neighbor 12.12.12.1 remote-as 12 R2(config-router)#network 2.2.2.2 mask 255.255.255.255
Sesaat setelah mengkonfigurasi IBGP Peering pada R1 dan R2, akan ada peringatan bahwa adjacency sudah terbentuk
R2(config-router)#*Oct 25 14:44:52.011: %BGP-5-ADJCHANGE: neighbor 12.12.12.1 Up
Sekarang kita coba lihat tabel routing pada R1 dan R2. Pastikan masing-masing router sudah memiliki informasi tentang remote networknya masing-masing
R1(config-router)#do sh ip ro1.0.0.0/32 is subnetted, 1 subnets C 1.1.1.1 is directly connected, Loopback0 2.0.0.0/32 is subnetted, 1 subnets B 2.2.2.2 [200/0] via 12.12.12.2, 00:01:33 12.0.0.0/8 is variably subnetted, 2 subnets, 2 masks C 12.12.12.0/24 is directly connected, Ethernet0/0
R2(config-router)#do sh ip ro 1.0.0.0/32 is subnetted, 1 subnets B 1.1.1.1 [200/0] via 12.12.12.1, 00:01:55 2.0.0.0/32 is subnetted, 1 subnets C 2.2.2.2 is directly connected, Loopback0 12.0.0.0/8 is variably subnetted, 2 subnets, 2 masks C 12.12.12.0/24 is directly connected, Ethernet0/0
Perhatikan bahwa R1 sudah memiliki informasi tentang 2.2.2.2, begitu juga dengan R2 yang sudah memiliki informasi tentang 1.1.1.1. Untuk lebih memastikan kita coba lakukan ping dari R1 ke 2.2.2.2
R1(config-router)#do ping 2.2.2.2Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Oke R1 sudah bisa ping ke 1.1.1.1, artinya kita sudah berhasil konfigurasi IBGP Peering. Lanjut kita konfig EBGP antara R2 dan R3
R2(config)#int e0/1R2(config-if)#no sh R2(config-if)#ip add 23.23.23.2 255.255.255.0 R2(config-if)#router bgp 12 R2(config-router)#neighbor 23.23.23.3 remote-as 3 R2(config-router)#network 23.23.23.0 mask 255.255.255.0
Oke kita coba cek apakah R2 dan R3 sudah adjacency atau belumR3(config)#int e0/0 R3(config-if)#no sh R3(config-if)#ip add 23.23.23.3 255.255.255.0 R3(config-if)#int lo0 R3(config-if)#ip add 3.3.3.3 255.255.255.255 R3(config-if)#router bgp 3 R3(config-router)#neighbor 23.23.23.2 remote-as 12 R3(config-router)#network 3.3.3.3 mask 255.255.255.255
Sip, R2 sudah adjacency dengan R3. Sekarang kita coba lihat tabel routing di R3R2#show ip bgp summary BGP router identifier 2.2.2.2, local AS number 12 BGP table version is 5, main routing table version 5 4 network entries using 480 bytes of memory 4 path entries using 208 bytes of memory 3/3 BGP path/bestpath attribute entries using 372 bytes of memory 1 BGP AS-PATH entries using 24 bytes of memory 0 BGP route-map cache entries using 0 bytes of memory 0 BGP filter-list cache entries using 0 bytes of memory BGP using 1084 total bytes of memory BGP activity 4/0 prefixes, 4/0 paths, scan interval 60 secs Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 12.12.12.1 4 12 14 14 5 0 0 00:08:51 1 23.23.23.3 4 3 8 10 5 0 0 00:04:15 1
Juozz R3 sudah tau tentang 1.1.1.1 dan 2.2.2.2, gimana dengan R2?R3(config-router)#do sh ip ro 1.0.0.0/32 is subnetted, 1 subnets B 1.1.1.1 [20/0] via 23.23.23.2, 00:05:16 2.0.0.0/32 is subnetted, 1 subnets B 2.2.2.2 [20/0] via 23.23.23.2, 00:05:16 3.0.0.0/32 is subnetted, 1 subnets C 3.3.3.3 is directly connected, Loopback0 23.0.0.0/8 is variably subnetted, 2 subnets, 2 masks C 23.23.23.0/24 is directly connected, Ethernet0/0
Nice, R2 juga udah tau tentang 1.1.1.1 dan 3.3.3.3., lanjut R1 gimana ya kira2?R2#sh ip ro 1.0.0.0/32 is subnetted, 1 subnets B 1.1.1.1 [200/0] via 12.12.12.1, 00:10:29 2.0.0.0/32 is subnetted, 1 subnets C 2.2.2.2 is directly connected, Loopback0 3.0.0.0/32 is subnetted, 1 subnets B 3.3.3.3 [20/0] via 23.23.23.3, 00:05:52 12.0.0.0/8 is variably subnetted, 2 subnets, 2 masks C 12.12.12.0/24 is directly connected, Ethernet0/0 23.0.0.0/8 is variably subnetted, 2 subnets, 2 masks C 23.23.23.0/24 is directly connected, Ethernet0/1
R1(config-router)#do sh ip ro 1.0.0.0/32 is subnetted, 1 subnets C 1.1.1.1 is directly connected, Loopback0 2.0.0.0/32 is subnetted, 1 subnets B 2.2.2.2 [200/0] via 12.12.12.2, 00:11:26 3.0.0.0/32 is subnetted, 1 subnets B 3.3.3.3 [200/0] via 23.23.23.3, 00:04:07 12.0.0.0/8 is variably subnetted, 2 subnets, 2 masks C 12.12.12.0/24 is directly connected, Ethernet0/0 23.0.0.0/24 is subnetted, 1 subnets B 23.23.23.0 [200/0] via 12.12.12.2, 00:04:12
Luar biasa,.. pertama konfig udah langsung jalan.. eits jangan seneng dulu... coba lakukan ping deh..
R1(config-router)#do ping 3.3.3.3Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 3.3.3.3, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
Tuh kan bener.. makanya aku bilang jangan seneng dulu.. kog gak bisa? karena R3 belum tau informasi tentang 12.12.12.0/24. Oke sekarang kita advertise dulu
Coba lihat lagi tabel routing di R3, pastikan R3 sudah mengenali 12.12.12.0/24R2(config)#router bgp 12R2(config-router)#net 12.12.12.0 mask 255.255.255.0
oke jozz dah.. coba ping lagiR3(config-router)#do sh ip ro 1.0.0.0/32 is subnetted, 1 subnets B 1.1.1.1 [20/0] via 23.23.23.2, 00:08:57 2.0.0.0/32 is subnetted, 1 subnets B 2.2.2.2 [20/0] via 23.23.23.2, 00:08:57 3.0.0.0/32 is subnetted, 1 subnets C 3.3.3.3 is directly connected, Loopback0 12.0.0.0/24 is subnetted, 1 subnets B 12.12.12.0 [20/0] via 23.23.23.2, 00:00:03 23.0.0.0/8 is variably subnetted, 2 subnets, 2 masks C 23.23.23.0/24 is directly connected, Ethernet0/0
Oke jozzz kan udah bisa ping...R1(config-router)#do ping 3.3.3.3 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 3.3.3.3, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Tidak ada komentar:
Posting Komentar
Komentar