Packet Tracer Simulation Lab Layer3 Routing

Johnson Liu

CCIE#11440(R&S, SP)

CCSI#31346

Packet Tracer Simulation Lab

L3 Routing

Agenda Slide

• Setup two Routers with WAN WIC(WAN Interface Card)

• Setup each LAN segment behind both Routers

• Assign WAN IP address between Routers

• Enable Static route in both Routers

• Enable RIP routing protocols

• Enable OSPF routing protocols

3/6/2013 Confidential | Copyright 2012 Trend Micro Inc.

Setup two Routers with WAN WIC(WAN Interface Card)

Router basic configurations


Router>en

Router#conf t

Enter configuration commands, one per line. End with CNTL/Z.

Router(config)#hostname R1

R1(config)#enable secret cisco

R1(config)#line vty 0 4

R1(config-line)#password cisco

R1(config-line)#exit

R1(config)#exit

R1(config)#interface loopback0 => Loopback interface for management

R1(config-if)#ip address 1.1.1.1 255.255.255.255

R1(config-if)#^Z =>(Ctrl-Z)

R1#

%SYS-5-CONFIG_I: Configured from console by console

R1#telnet 1.1.1.1

Trying 1.1.1.1 ...Open

User Access Verification

Password:

R1>en

Password:

R1#

R1#

Assign WAN IP address between Routers

Check interface list and status in brief


R1#sh ip int brief

Interface IP-Address OK? Method Status Protocol

FastEthernet0/0 unassigned YES unset administratively down down


Serial0/0/0 unassigned YES unset administratively down down


Loopback0 1.1.1.1 YES manual up up

Vlan1 unassigned YES unset administratively down down

R1#

Common Leased Line Physical Topology


DCE vs DTE


Routers w/ V.35 Serial cable setup back-to-back connection


Male

V.35

Female

V.35

Serial

(DTE)

Serial

(DCE)

Clock Rate

Check serial interface type in each router


R1#sh controllers s0/0/0

Interface Serial0/0/0

Hardware is PowerQUICC MPC860

DCE V.35, no clock

idb at 0x81081AC4, driver data structure at 0x81084AC0

SCC Registers:

… (omit)

R2#show controllers s0/0/0

Interface Serial0/0/0

Hardware is PowerQUICC MPC860

DTE V.35 clocks stopped.

idb at 0x81081AC4, driver data structure at 0x81084AC0

SCC Registers:

… (omit)

Configure R1 Serial0/0/0


R1>en

Password:

R1#conf t


R1(config)#int s0/0/0

R1(config-if)#no shutdown

%LINK-5-CHANGED: Interface Serial0/0/0, changed state to down

R1(config-if)#clock rate 64000 => Since R1 s0/0/0 is DCE, so it must config clock rate


R1(config-if)#^Z

R1#


R1#sh ip int brief




Serial0/0/0 10.100.1.1 YES manual down down




Configure R2 Serial0/0/0


R2>en

Password:

R2#conf t

R2(config)#int s0/0/0


%LINK-5-CHANGED: Interface Serial0/0/0, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up


R2(config-if)#^Z

R2#


R2#sh ip int brief




Serial0/0/0 10.100.1.2 YES manual up up




Check R1 serial interface status


R1#sh int s0/0/0

Serial0/0/0 is up, line protocol is up (connected)

Hardware is HD64570

Internet address is 10.100.1.1/30

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation HDLC, loopback not set, keepalive set (10 sec)

Last input never, output never, output hang never

Last clearing of "show interface" counters never

… (omit)

R1#ping 10.100.1.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.100.1.2, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 20/20/20 ms

WAN interconnection was ready!


Setup each LAN segment behind Routers

Setup LAN switch & host in both site


Check R1 interface list and status in brief


R1#sh ip int brief








R1#

Configure R1 FastEthernet0/0/0


R1#conf t


R1(config)#int f0/0


%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up


R1(config-if)#^Z

R1#


R1#sh ip int brief


FastEthernet0/0 10.100.2.254 YES manual up up






Configure R2 FastEthernet0/0/0


R2#conf t


R2(config)#int f0/0


%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up


R2(config-if)#^Z

R2#


R2#sh ip int brief


FastEthernet0/0 10.100.3.254 YES manual up up






Configure switches & hosts


Keep switch default configuration without any change, because we use

switch default VLAN 1 only without management SVI and any

dedicated VLAN/Trunk port configuration

Configure host IP Address behind R1 IP Address: 10.100.2.1

Subnet Mask: 255.255.255.0

Default Gateway: 10.100.2.254 (R1 F0/0 IP Address)

Configure host IP Address behind R2 IP Address: 10.100.3.1

Subnet Mask: 255.255.255.0

Default Gateway: 10.100.3.254 (R1 F0/0 IP Address)

Now only R1 can ping PC1, R2 can ping PC2, but PC1 cannot ping

PC2, because R1 and R2 still not have complete routing information

Enable Static route in both Routers

How to test in routers (1/2) ?


When execute ping function in routers under default parameter, it will

use outgoing interface IP address as source IP(ex:R1 s0/0/0), so it will

always works! R1#ping 10.100.3.1 => The host behind R2



!!!!!


That’s because the other router (R2) has WAN(10.100.1.0/30) and

LAN(10.100.1.0/30) routing information so it can route the packet

between these IP networks. R2#sh ip route

Gateway of last resort is not set

2.0.0.0/32 is subnetted, 1 subnets

C 2.2.2.2 is directly connected, Loopback0

10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

C 10.100.1.0/30 is directly connected, Serial0/0/0

C 10.100.3.0/24 is directly connected, FastEthernet0/0

How to test in routers (2/2) ?


You can use extension ping as below to specify any source IP which

owns by this router interface:

R1#ping

Protocol [ip]: => Leave it alone, it means IP protocol

Target IP address: 10.100.3.1

Repeat count [5]:

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: 10.100.2.254 => Using R1 F0/0 IP address as Source IP

Type of service [0]:

Set DF bit in IP header? [no]:

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:



Packet sent with a source address of 10.100.2.254

.....

Success rate is 0 percent (0/5)

So, let’s fix it by static route in both routers !

Configure R1 static route


R1#conf t


R1(config)#ip route 10.100.3.0 255.255.255.0 10.100.1.2

R1(config)#^Z

R1#


R1#sh 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






C 10.100.2.0 is directly connected, FastEthernet0/0

S 10.100.3.0 [1/0] via 10.100.1.2

Configure R2 static route


R2#conf t


R2(config)#ip route 10.100.2.0 255.255.255.0 10.100.1.1

R2(config)#^Z

R2#


R2#sh ip route













S 10.100.2.0/24 [1/0] via 10.100.1.1


Check the routing in Router and host


R1#ping

Protocol [ip]: => Leave it alone, it means IP protocol

Target IP address: 10.100.3.1

Repeat count [5]:

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: 10.100.2.254 => Using R1 F0/0 IP address as Source IP

Type of service [0]:

Set DF bit in IP header? [no]:

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:



Packet sent with a source address of 10.100.2.254

!!!!!


PC>ping 10.100.3.1

Pinging 10.100.3.1 with 32 bytes of data:

Reply from 10.100.3.1: bytes=32 time=101ms TTL=126

Ping statistics for 10.100.3.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 100ms, Maximum = 101ms, Average = 100ms

Enable RIP routing protocols

Clear static route configuration at first


Before we starting to configure RIP protocol, please remove the static

route in both R1 and R2 to ensure our RIP can work for routing

exchange and packet forwarding

R1#sh run

…(omit)

!

ip route 10.100.3.0 255.255.255.0 10.100.1.2

!

…(omit)

R1#conf t


R1(config)#no ip route 10.100.3.0 255.255.255.0 10.100.1.2

R1(config)#^Z

R1#


R1#sh ip route




C 10.100.1.0 is directly connected, Serial0/0/0


Configure RIP protocol


R1#conf t


R1(config)#router rip

R1(config-router)#version 2

R1(config-router)#network 10.0.0.0

R1(config-router)#no auto-summary

R1(config-router)#^Z

R1#

R2#conf t


R2(config)#router rip

R2(config-router)#version 2

R2(config-router)#network 10.0.0.0

R2(config-router)#no auto-summary

R2(config-router)#^Z

R2#

Check R1 & R2 routing table


R1#sh ip route





C 10.100.1.0 is directly connected, Serial0/0/0


R 10.100.3.0 [120/1] via 10.100.1.2, 00:00:26, Serial0/0/0

R2#sh ip route






R 10.100.2.0/24 [120/1] via 10.100.1.1, 00:00:07, Serial0/0/0


Enable OSPF routing protocols

OSPF Topology Design


Check R1 OSPF neighbor and routing table


R1#sh ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface

2.2.2.2 0 FULL/ - 00:00:38 10.100.1.2 Serial0/0/0

R1#sh ip route












O 2.2.2.2 [110/65] via 10.100.1.2, 00:00:31, Serial0/0/0




O IA 10.100.3.0/24 [110/65] via 10.100.1.2, 00:08:39, Serial0/0/0

Check R2 OSPF neighbor and routing table


R2#sh ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface

1.1.1.1 0 FULL/ - 00:00:36 10.100.1.1 Serial0/0/0

R2#sh ip route










O 1.1.1.1 [110/65] via 10.100.1.1, 00:02:13, Serial0/0/0





O IA 10.100.2.0/24 [110/65] via 10.100.1.1, 00:10:06, Serial0/0/0


Q&A


Appendix


PDU Simulation for troubleshooting


Packet Tracer Simulation Lab Layer3 Routing

Technology

Transcript of Packet Tracer Simulation Lab Layer3 Routing