Rabu, 15 Mei 2013

Laporan Praktikum Jaringan Komputer 7


Nama         : Hudda Affandi
Kelas          : 2A
NIM            : 12 615 009

Scenario B 5.6.1: Running RIPv1 with Subnets and Between Classful Networks
Tujuan Praktikum
1.       Mahasiswa dapat mengetahui bagaimana caranya Verify RIP routing using show and debug commands
2.        Mahasiswa melakukan Observe automatic summarization at boundary router and Gather information about RIP processing using the debug ip rip command.

Pendahuluan
Karakteristik RIPv1:
- merupakan distance vector routing protocol
- classful routing protocol
- max hop count:15. 16 -> unreachable
- periodic update: 30s
- update dikirim secara broadcast(255.255.255.255)
- mendukung equal cost load balancing. Secara default adalah 4 path, sedang max path: 6
- menjalankan auto-summary secara default
- paket yang dikirim berjenis UDP dengan nomor port 520
- bisa mengirimkan paket update RIPv1 dan menerima paket update RIPv1 & v2
- AD: 120
Pada saat instalasi, router-router yang menjalankan RIP akan membroadcast paket request kepada router lain yang isinya adalah meminta network-network yang dimiliki router lain. Router lain yang menerima paket request akan mengirimkan respon. Setelah itu mereka baru bertukar-tukaran info network yang dimiliki.
untuk mengaktifkan RIP:
config# router rip
untuk menyertakan directly connected network mana saja yang akan disebar:
config-router# network {classful-network-address | network-address}
Comman “network” punya dua fungsi yaitu:
1. mengaktifkan RIP di interface router yang ip-nya berada pada range classful network yang diinput
2. network yang diinput akan disertakan pada update packet sehingga akan tersebar
Masukkan saja classful network dibandingkan dengan network address karena RIP secara otomatis akan mengclassfulkan network address
Passive interface adalah interface yang hanya akan menerima update dari router lain, tetapi interface ini takkan pernah mengirimkan update. Sehingga, interface ini bisa ditujukan agar tidak menyebarkan update.
untuk mengaktifkan passive interface:
config-router# passive-interface interface-id
untuk menyebarkan static route:
config-router# redistribute static
untuk menyebarkan default route:
config-router# default-information originate
Router akan secara otomatis menjalankan route summarization pada boundary router.
Boundary router adalah router yang interfacenya memiliki ip address yang berbeda secara classful network
Auto-summary berjalan secara default dan tidak dapat di non-aktifkan

Langkah Praktikum
Scenario B: Running RIPv1 with Subnets and Between Classful Networks
Topology Diagram
Gambar 7.1
Addresing Table
Device
Interface
IP Address
Subnet Mask
Default Gateway
R1
Fa0/0
172.30.1.1
255.255.255.0
N/A
S0/0/0
172.30.2.1
255.255.255.0
N/A
R2
Fa0/0
172.30.3.1
255.255.255.0
N/A
S0/0/0
172.30.2.2
255.255.255.0
N/A
S0/0/1
192.168.4.9
255.255.255.252
N/A
R3
Fa0/0
192.168.5.1
255.255.255.0
N/A
S0/0/1
192.168.4.10
255.255.255.252
N/A
PC1
NIC
172.30.1.10
255.255.255.0
172.30.1.1
PC2
NIC
172.30.3.10
255.255.255.0
172.30.3.1
PC3
NIC
192.168.5.10
255.255.255.0
192.168.5.1

Pertama sama seperti saat mengkonfigurasi router pada skenario A, akan tetapi di skenario B ini menyediakan IP yang sudah di subnetting otomatis untuk RIP pada skenario A diganti dengan IP yang sudah di subnetting caranya ada command di router menggunakan perintah "no ip route".
Perintah tersebut berlaku pada ketiga router "no ip route" adalah perintah yang digunakan untuk menghapus "ip route" sebelumnya pada skenario ini kita disuruh menghentikan update ip pada setiap router command yang digunakan "passive-interface fastethernet0/0".

Kedua melakukan test apakah semua sudah terhubung dalam satu jaringan perhatikan gambar berikut :
1.     Melakukan test koneksi pada setiap router apakah sudah terhubung
R1#ping 172.30.2.2 (R2)
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/7/24 ms
R1#ping 192.168.4.9 (R2)
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.4.9, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 10/18/20 ms
R1#ping 192.168.4.10 (R3)
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.4.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 33/38/40 ms

2.     Melakukan test koneksi pada ketiga PC apakah sudah terhubung.
PC1 ke PC2
Gambar 7.2 PC1 ke PC2
PC1 ke PC3
                Gambar 7.3 PC1 ke PC3
Catatan : untuk ping ke PC lain saya tidak masukkan agar mengurangi besarnya ukuran memori file pada saat di upload di blog, gambar di atas sudah mewakili bahwa semua PC sudah terhubung.

Setelah melakukan test koneksi pada semua item ternyata semua sudah terhubung dalam satu jaringan.

Hasil Praktikum
Setelah semua sudah dilakukan seperti inilah hasilnya :
1.      menverifikasi semua routing sudah masuk dan mengetahui informasi pada router dengan menggunakan command "show ip route", "show ip protocols", "debug ip rip".
R1#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

     172.30.0.0/24 is subnetted, 3 subnets
C       172.30.1.0 is directly connected, FastEthernet0/0
C       172.30.2.0 is directly connected, Serial0/0/0
R       172.30.3.0 [120/1] via 172.30.2.2, 00:00:28, Serial0/0/0
R    192.168.4.0/24 [120/1] via 172.30.2.2, 00:00:28, Serial0/0/0
R    192.168.5.0/24 [120/2] via 172.30.2.2, 00:00:28, Serial0/0/0
R1#show ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 1 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 1, receive any version
  Interface             Send  Recv  Triggered RIP  Key-chain
  Serial0/0/0           1     2 1  
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
            172.30.0.0
            192.168.1.0
            192.168.2.0
Passive Interface(s):
            FastEthernet0/0
Routing Information Sources:
            Gateway         Distance      Last Update
            172.30.2.2           120      00:00:18
R1#debug ip rip
RIP protocol debugging is on
R1#RIP: sending  v1 update to 255.255.255.255 via Serial0/0/0 (172.30.2.1)
RIP: build update entries
      network 172.30.1.0 metric 1
RIP: received v1 update from 172.30.2.2 on Serial0/0/0
      172.30.3.0 in 1 hops
      192.168.4.0 in 1 hops
      192.168.5.0 in 2 hops

R2#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

     172.30.0.0/24 is subnetted, 3 subnets
R       172.30.1.0 [120/1] via 172.30.2.1, 00:00:16, Serial0/0/0
C       172.30.2.0 is directly connected, Serial0/0/0
C       172.30.3.0 is directly connected, FastEthernet0/0
     192.168.4.0/30 is subnetted, 1 subnets
C       192.168.4.8 is directly connected, Serial0/0/1
R    192.168.5.0/24 [120/1] via 192.168.4.10, 00:00:15, Serial0/0/1
R2#show ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 20 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 1, receive any version
  Interface             Send  Recv  Triggered RIP  Key-chain
  Serial0/0/1           1     2 1  
  Serial0/0/0           1     2 1  
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
            172.30.0.0
            192.168.2.0
            192.168.3.0
            192.168.4.0
Passive Interface(s):
            FastEthernet0/0
Routing Information Sources:
            Gateway         Distance      Last Update
            172.30.2.1           120      00:00:14
            192.168.4.10         120      00:00:07
R2#debug ip rip
RIP protocol debugging is on
R2#RIP: received v1 update from 192.168.4.10 on Serial0/0/1
      192.168.5.0 in 1 hops
RIP: sending  v1 update to 255.255.255.255 via Serial0/0/1 (192.168.4.9)
RIP: build update entries
      network 172.30.0.0 metric 1
RIP: sending  v1 update to 255.255.255.255 via Serial0/0/0 (172.30.2.2)
RIP: build update entries
      network 172.30.3.0 metric 1
      network 192.168.4.0 metric 1
      network 192.168.5.0 metric 2
RIP: received v1 update from 172.30.2.1 on Serial0/0/0
      172.30.1.0 in 1 hops

R3#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

R    172.30.0.0/16 [120/1] via 192.168.4.9, 00:00:20, Serial0/0/1
     192.168.4.0/30 is subnetted, 1 subnets
C       192.168.4.8 is directly connected, Serial0/0/1
C    192.168.5.0/24 is directly connected, FastEthernet0/0
R3#show ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 27 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 1, receive any version
  Interface             Send  Recv  Triggered RIP  Key-chain
  Serial0/0/1           1     2 1  
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
            192.168.0.0
            192.168.4.0
            192.168.5.0
Passive Interface(s):
            FastEthernet0/0
Routing Information Sources:
            Gateway         Distance      Last Update
            192.168.4.9          120      00:00:01
R3#debug ip rip
RIP protocol debugging is on
R3#RIP: sending  v1 update to 255.255.255.255 via Serial0/0/1 (192.168.4.10)
RIP: build update entries
      network 192.168.5.0 metric 1
RIP: received v1 update from 192.168.4.9 on Serial0/0/1
      172.30.0.0 in 1 hops