Halaman

Minggu, 23 Juni 2013

Laporan Praktikum 
Lab 5.6.1: Basic RIP Configuration

Nama  : Markhamah Tri Utami
NIM    : 12 615 056  

Tujuan Praktikum 
-   Mahasiswa dapat mengetahui bagaimana cara  Verify RIP routing using show dan debug commands
-   Mahasiswa dapat melakukan observasi tentang RIP processing using the debug ip rip command.

Pendahuluan
Karakteristik RIPv1:
- RIPv1 merupakan distance vector routing protocol
- Max hop count:15. 16 -> unreachable
- Classful routing protocol
- Update dikirim secara broadcast(255.255.255.255)
- Periode update: 30s
- Paket yang dikirim berjenis UDP dengan nomor port 520
- Dapat mengirimkan paket update RIPv1 dan menerima paket update RIPv1 & v2
- Mendukung equal cost load balancing. Secara default adalah 4 path, sedang max path: 6
- Menjalankan auto-summary secara default
Langkah Praktikum
Topology Diagram



R1(config)#router rip
R1(config-router)#network 192.168.1.0
R1(config-router)#network 192.168.2.0
R1(config-router)#
R1#copy run start
Configure RIP on the R2 router using the router rip and network commands.
R2(config)#router rip
R2(config-router)#network 192.168.2.0
R2(config-router)#network 192.168.3.0
R2(config-router)#network 192.168.4.0
R2(config-router)#end
Configure RIP on the R3 router using the router rip and network commands.
R3(config)#router rip
R3(config-router)#network 192.168.4.0
R3(config-router)#network 192.168.5.0
R3(config-router)#end

R1#debug ip rip
Discontinue the debug output with the undebug all command.
R1#undebug all

Langkah Pertama
                  Konfigurasi skenario B hampir sama 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. 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".
Langkah Kedua

 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,  PC1 ke PC2, PC1 ke PC3

Hasil Praktikum

Setelah konfigurasi telah dilakukan seperti inilah hasilnya :
     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
    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
  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
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 protocols
    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