Rabu, 30 Mei 2012

PR Jarkom Review Router Static


Reviews Router Statis




ROUTER1:

Router>ena
Router#conf t
Router(config)#int fa0/0
Router(config-if)#ip add 172.16.3.1 255.255.255.0
Router(config-if)#no shut

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
Router(config-if)#exit
Router(config)#int ser2/0
Router(config-if)#ip add 172.16.2.1 255.255.255.0
Router(config-if)#no shut

%LINK-5-CHANGED: Interface Serial2/0, changed state to down
Router(config-if)#exit
Router(config)#ip route 192.168.0.0 255.255.252.0 ser2/0
Router(config)#ip route 172.16.1.0 255.255.255.0 ser2/0
Router(config)#exit

ROUTER2:

Router>ena
Router#conf t
Router(config)#int fa0/0
Router(config-if)#ip add 172.16.1.1 255.255.255.0
Router(config-if)#no shut

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
Router(config-if)#exit
Router(config)#int ser3/0
Router(config-if)#ip add 172.16.2.2 255.255.255.0
Router(config-if)#clock rate 64000
Router(config-if)#no shut

Router(config-if)#
%LINK-5-CHANGED: Interface Serial3/0, changed state to up
Router(config-if)#exit
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/0, changed state to up
Router(config)#int ser2/0
Router(config-if)#ip add 192.168.1.2 255.255.255.0
Router(config-if)#clock rate 64000
Router(config-if)#no shut

%LINK-5-CHANGED: Interface Serial2/0, changed state to down
Router(config-if)#exit
Router(config)#
Router#conf t
Router(config)#ip route 172.16.3.0 255.255.255.0 ser3/0
Router(config)#ip route 192.168.2.0 255.255.255.0 ser2/0
Router(config)#exit

ROUTER3

Router>ena
Router#conf t
Router(config)#int fa0/0
Router(config-if)#ip add 192.168.2.1 255.255.255.0
Router(config-if)#no shut

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
Router(config-if)#exit
Router(config)#int ser3/0
Router(config-if)#ip add 192.168.1.1 255.255.255.0
Router(config-if)#no shut

%LINK-5-CHANGED: Interface Serial3/0, changed state to up
Router(config-if)#exit
Router(config)#
Router#conf t
Router(config)#ip route 172.16.0.0 255.255.252.0 ser3/0
Router(config)#exit
Router Summeryzation 

Terdapat 3 route statis pada router 2 yaitu:
  • 192.168.1.0 255.255.255.0 ser2/0
  • 192.168.2.0 255.255.255.0 ser2/0
  • 172.16.1.0 255.255.255.0 ser2/0
diringkas menjadi:
ip route 192.168.0.0 255.255.252.0 ser2/0
ip route 172.16.1.0 255.255.255.0 ser2/0
=>yang dapat diringkas apabila depannya sama yaitu: 192.168.1.0 dan 192.168.2.0
cara perhitungannya:

IP
Binery
192.168.1.0
11000000.10101000.00000001.00000000
192.168.2.0
11000000.10101000.00000010.00000000
Network
11000000.10101000.00000000.00000000 = 192.168.0.0
Subnet Mask
11111111.11111111.11111100.00000000 = 255.255.252.0

Terdapat 3 route static pada router 3, yaitu:
  • ip route 172.16.1.0 255.255.255.0 ser2/0
  • ip route 172.16.2.0 255.255.255.0 ser2/0
  • ip route 172.16.3.0 255.255.255.0 ser2/0
diringkas menjadi:
ip route 172.16.0.0 255.255.252.0 ser2/0
cara perhitungannya:
IP
Binery
172.16.1.0
10101100.00010000.00000001.00000000
172.16.2.0
10101100.00010000.00000010.00000000
172.16.3.0
10101100.00010000.00000011.00000000



hasil CMD:

Packet Tracer PC Command Line 1.0
PC>ping 192.168.2.2

Pinging 192.168.2.2 with 32 bytes of data:

Request timed out.
Reply from 192.168.2.2: bytes=32 time=187ms TTL=125
Reply from 192.168.2.2: bytes=32 time=187ms TTL=125
Reply from 192.168.2.2: bytes=32 time=174ms TTL=125

Ping statistics for 192.168.2.2:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 174ms, Maximum = 187ms, Average = 182ms

PC>ping 172.16.2.2

Pinging 172.16.2.2 with 32 bytes of data:

Reply from 172.16.2.2: bytes=32 time=94ms TTL=254
Reply from 172.16.2.2: bytes=32 time=94ms TTL=254
Reply from 172.16.2.2: bytes=32 time=78ms TTL=254
Reply from 172.16.2.2: bytes=32 time=93ms TTL=254

Ping statistics for 172.16.2.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 78ms, Maximum = 94ms, Average = 89ms

PC>ping 172.16.2.1

Pinging 172.16.2.1 with 32 bytes of data:

Reply from 172.16.2.1: bytes=32 time=63ms TTL=255
Reply from 172.16.2.1: bytes=32 time=62ms TTL=255
Reply from 172.16.2.1: bytes=32 time=62ms TTL=255
Reply from 172.16.2.1: bytes=32 time=49ms TTL=255

Ping statistics for 172.16.2.1:
 Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
 Minimum = 49ms, Maximum = 63ms, Average = 59ms

PC>ping 172.16.1.2

Pinging 172.16.1.2 with 32 bytes of data:

Reply from 172.16.1.2: bytes=32 time=93ms TTL=254
Reply from 172.16.1.2: bytes=32 time=94ms TTL=254
Reply from 172.16.1.2: bytes=32 time=94ms TTL=254
Reply from 172.16.1.2: bytes=32 time=93ms TTL=254

Ping statistics for 172.16.1.2: 
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: 
Minimum = 93ms, Maximum = 94ms, Average = 93ms

PC>ping 172.16.1.1

Pinging 172.16.1.1 with 32 bytes of data:

Reply from 172.16.1.1: bytes=32 time=94ms TTL=254
Reply from 172.16.1.1: bytes=32 time=93ms TTL=254
Reply from 172.16.1.1: bytes=32 time=94ms TTL=254
Reply from 172.16.1.1: bytes=32 time=78ms TTL=254

Ping statistics for 172.16.1.1: 
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: 
Minimum = 78ms, Maximum = 94ms, Average = 89ms

PC>ping 172.16.2.1

Pinging 172.16.2.1 with 32 bytes of data:

Reply from 172.16.2.1: bytes=32 time=62ms TTL=255
Reply from 172.16.2.1: bytes=32 time=63ms TTL=255
Reply from 172.16.2.1: bytes=32 time=47ms TTL=255
Reply from 172.16.2.1: bytes=32 time=62ms TTL=255

Ping statistics for 172.16.2.1: 
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: 
Minimum = 47ms, Maximum = 63ms, Average = 58ms

PC>ping 172.16.2.2

Pinging 172.16.2.2 with 32 bytes of data:

Reply from 172.16.2.2: bytes=32 time=93ms TTL=254
Reply from 172.16.2.2: bytes=32 time=94ms TTL=254
Reply from 172.16.2.2: bytes=32 time=94ms TTL=254
Reply from 172.16.2.2: bytes=32 time=93ms TTL=254

Ping statistics for 172.16.2.2: 
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: 
Minimum = 93ms, Maximum = 94ms, Average = 93ms

PC>ping 172.16.3.1

Pinging 172.16.3.1 with 32 bytes of data:

Reply from 172.16.3.1: bytes=32 time=63ms TTL=255
Reply from 172.16.3.1: bytes=32 time=58ms TTL=255
Reply from 172.16.3.1: bytes=32 time=63ms TTL=255
Reply from 172.16.3.1: bytes=32 time=47ms TTL=255

Ping statistics for 172.16.3.1: 
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: 
Minimum = 47ms, Maximum = 63ms, Average = 57ms

PC>ping 172.16.3.2

Pinging 172.16.3.2 with 32 bytes of data:

Reply from 172.16.3.2: bytes=32 time=0ms TTL=128
Reply from 172.16.3.2: bytes=32 time=15ms TTL=128
Reply from 172.16.3.2: bytes=32 time=16ms TTL=128
Reply from 172.16.3.2: bytes=32 time=16ms TTL=128

Ping statistics for 172.16.3.2: 
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: 
Minimum = 0ms, Maximum = 16ms, Average = 11ms


Tampilan Pengujian :



















Diposting oleh di

Tidak ada komentar:

Posting Komentar

Langganan: Posting Komentar (Atom)