CN File
CN File
CN File
LIST OF EXPERIMENTS
Procedure:
To implement this practical following network topology is required to be configured
using the commands learned in previous practical.
After configuring the given network, a packet should be ping from any one
machine to another.
Router(config)#hostname router0
router0(config)#interface fastethernet 0/0
router0(config-if)#ip address 192.168.1.1 255.255.255.0
router0(config-if)#description router0 fastethernet 0/0
router0(config-if)#no shutdown
router0(config)#exit
%SYS-5-CONFIG_I: Configured from console by console router0#show
running-config
Building configuration...
PROCEDURE:
Switch>enable
Switch#configure terminal
Switch(config)#hostname CustomerSwitch
Switch(config)#hostname CustomerSwitch
CustomerSwitch(config-line)#password cisco
CustomerSwitch(config-line)#login
CustomerSwitch(config-line)#exit
CustomerSwitch(config-line)#password cisco
CustomerSwitch(config-line)#login
CustomerSwitch(config-line)#exit
b. Click the Check Results button at the bottom of this instruction window to check your
work.
CustomerSwitch(config)#end
CustomerSwitch#ping 209.165.201.10
Procedure:
PROCEDURE:
Step 1: Test connectivity using ping from a host computer and a router.
Click N-Host, click the Desktop tab, and then click Command Prompt. From the Command
Prompt window, ping the Cisco server at www.cisco.com.
Packet Tracer PC Command Line 1.0
PC>ping www.cisco.com
Pinging 64.100.1.185 with 32 bytes of data:
Request timed out.
Reply from 64.100.1.185: bytes=32 time=185ms TTL=123
Reply from 64.100.1.185: bytes=32 time=281ms TTL=123
Reply from 64.100.1.185: bytes=32 time=287ms TTL=123
Ping statistics for 64.100.1.185:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 185ms, Maximum = 287ms, Average = 251ms
PC>
From the output, you can see that N-Host was able to obtain an IP address for the Cisco server.
The IP address was obtained using (DNS). Also notice that the first ping failed. This failure is
most likely due to lack of ARP convergence between the source and destination. If you repeat the
ping, you will notice that all pings succeed.
From the Command Prompt window on N-Host, ping E-Host at 192.168.4.10. The pings fail. If
you do not want to wait for all four unsuccessful ping attempts, press Ctrl+C to abort the
command, as shown below.
PC>ping 192.168.4.10
Pinging 192.168.4.10 with 32 bytes of data:
Request timed out.
Request timed out.
Ping statistics for 192.168.4.10:
Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),
Control-C
^C
PC>
Click the N-Branch router, and then click the CLI tab. Press Enter to get the router prompt. From
the router prompt,
ping the Cisco server at www.cisco.com.
N-Branch>ping www.cisco.com
Translating "www.cisco.com"...domain server (64.100.1.242)
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 64.100.1.185, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 210/211/213 ms
N-Branch>
As you can see, the ping output on a router is different from a PC host. Notice that the N-Branch
router resolved the domain name to the same IP address that N-Host used to send its pings. Also
notice that the first ping fails, which is indicated by a period (.), and that the next four pings
succeed, as shown with an exclamation point (!).
From the CLI tab on N-Branch, ping E-Host at 192.168.4.10. Again, the pings fail. To not wait
for all the failures, press Ctrl+C.
N-Branch>ping 192.168.4.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.4.10, timeout is 2 seconds:
...
Success rate is 0 percent (0/4)
N-Branch>
Step 2: Test connectivity using traceroute from a host computer and a router.
a. Click N-Host, click the Desktop tab, and then click Command Prompt. From the Command
Prompt
window, trace the route to the Cisco server at www.cisco.com.
PC>tracert www.cisco.com
Tracing route to 64.100.1.185 over a maximum of 30 hops:
1 92 ms 77 ms 86 ms 192.168.1.1
2 91 ms 164 ms 84 ms 64.100.1.101
3 135 ms 168 ms 151 ms 64.100.1.6
4 185 ms 261 ms 161 ms 64.100.1.34
5 257 ms 280 ms 224 ms 64.100.1.62
6 310 ms 375 ms 298 ms 64.100.1.185
Trace complete.
PC>
The above output shows that you can successfully trace a route all the way to the Cisco server at
64.100.1.185. Each
hop in the path is a router responding three times to trace messages from N-Host. The trace
continues until the
destination for the trace (64.100.1.185) responds three times.
From the Command Prompt window on N-Host, trace a route to E-Host at 192.168.4.10. The
trace fails, but notice
that the tracert command traces up to 30 hops. If you do not want to wait for all 30 attempts to
time out, press
Ctrl+C.
PC>tracert 192.168.4.10
Tracing route to 192.168.4.10 over a maximum of 30 hops:
1 103 ms 45 ms 91 ms 192.168.1.1
2 56 ms 110 ms 125 ms 64.100.1.101
3 174 ms 195 ms 134 ms 64.100.1.6
4 246 ms 183 ms 179 ms 64.100.1.34
5 217 ms 285 ms 226 ms 64.100.1.62
6 246 ms 276 ms 245 ms 64.100.1.154
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10
Control-C
^C
PC>
The tracert command can be helpful in finding the potential source of a problem. The last device
to respond was 64.100.1.154, so you would start troubleshooting by determining which device is
configured with the IP address 64.100.1.154. The source of the problem might not be that device,
but the trace has given you a starting point, whereas a ping simply tells you that the destination is
either reachable or unreachable.
Click the N-Branch router, and then click the CLI tab. Press Enter to get the router prompt. From
the router prompt, trace the route to the Cisco server at www.cisco.com.
N-Branch>traceroute www.cisco.com
Translating "www.cisco.com"...domain server (64.100.1.242)
Type escape sequence to abort.
Tracing the route to 64.100.1.185
1 64.100.1.101 60 msec 32 msec 59 msec
2 64.100.1.6 98 msec 65 msec 65 msec
3 64.100.1.34 138 msec 147 msec 147 msec
4 64.100.1.62 189 msec 148 msec 145 msec
5 64.100.1.185 219 msec 229 msec 293 msec
N-Branch>
As you can see, traceroute output on a router is very similar to the output on a PC host. The only
difference is that on a PC host, the IP address is listed after the three millisecond outputs.
From the CLI tab on N-Branch, trace the route to E-Host at 192.168.4.10. The trace fails at the
same IP address as it failed when tracing from N-Host. Again, you can use Ctrl+C to abort the
command.
N-Branch>traceroute 192.168.4.10
Type escape sequence to abort.
Tracing the route to 192.168.4.10
1 64.100.1.101 41 msec 19 msec 32 msec
2 64.100.1.6 33 msec 92 msec 117 msec
3 64.100.1.34 98 msec 102 msec 102 msec
4 64.100.1.62 166 msec 172 msec 156 msec
5 64.100.1.154 157 msec 223 msec 240 msec
6***
7***
8***
9
N-Branch>
Topology Diagram:
PROCEDURE :
Step 2: Send an HTTP request from an inside host to an outside web server.
Click Customer PC. Click the Desktop tab and then Web Browser. In the URL field, type the web
address for the ISP server (www.ispserver.com). Make sure that you are in Simulation mode, and
then click Go.
In the event list, notice that Customer PC queues a DNS request and sends out an ARP request.
You can view the contents of the ARP request by either clicking on the packet in the topology or
clicking on the packet color under Info in the Event List window.
In the PDU Information at Device: Customer PC window, which IP address is Customer PC
attempting to find a MAC address for? ______________________
In the Event List window, click Capture/Forward twice. Which device answers the ARP request
from Customer PC?
Which MAC address is placed inside the ARP reply?
________________________________________________________________
In the Event List window, click Capture/Forward twice. Customer PC accepts the ARP replay
and then builds another packet. What is the protocol for this new packet? If you click Outbound
PDU Details for this packet, you can see the details of the protocol. _________
In the Event List window, click Capture/Forward twice. Click the packet at the
www.customerserver.com server.
Then click the Outbound PDU Details tab. Scroll down to the bottom to see the Application
Layer data. What is the
IP address for the ISP server?
________________________________________________________________
In the Event List window, click Capture/Forward twice. Customer PC now formulates another
ARP request. Why?
________________________________________________________________
In the Event List window, click Capture/Forward 10 times until Customer PC formulates an
HTTP request packet.
Customer PC finally has enough information to request a web page from the ISP server.
In the Event List window, click Capture/Forward three times. Click the packet at Customer
Router to examine the contents. Customer Router is a NAT border router. What is the inside local
address and the inside global address for
Customer PC?
________________________________________________________________
In the Event List window, click Capture/Forward seven times until the HTTP reply reaches
Customer Router.
Examine the contents of the HTTP reply and notice that the inside local and global addresses
have changed again as the packet is forwarded on to Customer PC.
Step 3: Send an HTTP request from an outside host to an inside web server.
Customer Server provides web services to the public (outside addresses) through the domain
name www.customerserver.com. Follow a process similar to Step 2 to observe an HTTP request
on ISP Workstation.
a. Click ISP Workstation. Click the Desktop tab, and then Web Browser. In the URL field, type
the Customer Server web address (www.customerserver.com). Make sure that you are in
Simulation mode, and then click Go.
b. You can either click Auto Capture/Play or Capture/Forward to step through each stage of the
process. The same ARP and DNS processes occur before the ISP Workstation can formulate an
HTTP request.
c. When the HTTP request arrives at Customer Router, check the packet contents. What is the
inside local address? What is the inside global address?
EXPERIMENT- 11
RIP
Procedure:
1. Develop a Topology shown in figure given below.
3. Configure all Routers
4. Implement RIP protocols in Router to configure Network.
Router0 configuration.....
router0>
router0>en
router0#confi
gt
Enter configuration commands, one per line. End
with CNTL/Z. router0(config)#router rip
router0(config‐router)#net 10.0.0.0
router0(config‐router)# router0(config‐
router)#end
%SYS‐5‐CONFIG_I: Configured from
console by console router0#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
Router>enabl
e
Router#config
t
Enter configuration commands, one per line. End
with CNTL/Z. Router(config)#int lo0
Router>
Router>en
Router#con t
"con t" Router#co t
% Ambiguous command:
"co t" Router#conf t
Enter configuration commands, one per line. End
with CNTL/Z. Router(config)#router rip
Router(config‐router)#net
10.0.0.0 Router(config‐router)#
Router(config‐router)#
Router(config‐router)#end
%SYS‐5‐CONFIG_I: Configured from
console by console Router#
Router2 Configuration.....
Router#wr
Building configuration...
[OK]
Router
#
Router
#
Router
#
%LINEPROTO‐5‐UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to
up
Router con0 is now available
Router3 Configuration.......
Continue with configuration dialog? [yes/no]: no
Press RETURN to get
started! Router>
Router>en
Router#config
t
Enter configuration commands, one per line. End
with CNTL/Z. Router(config)#int lo0
%LINK‐5‐CHANGED: Interface Loopback0, changed state to up
%LINEPROTO‐5‐UPDOWN: Line protocol on Interface Loopback0, changed state
to up Router(config‐if)#int f0/0
Router(config‐if)#ip address 10.1.34.2 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)#
Router(config‐if)#int f0/1
Router(config‐if)#ip address 10.1.14.2
255.255.255.0 Router(config‐if)#no shut
%LINK‐5‐CHANGED: Interface FastEthernet0/1, changed state to up
%LINEPROTO‐5‐UPDOWN: Line protocol on Interface FastEthernet0/1, changed
state to up Router(config‐if)#end
%SYS‐5‐CONFIG_I: Configured from
console by console Router#wr
Building configuration...
[OK]
Router#
Router#
Router#show ip route
Router(config‐router)#end
%SYS‐5‐CONFIG_I: Configured from
console by console Router#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 10.0.0.0/24 is
subnetted, 7 subnets
R 10.1.1.0 [120/1] via 10.1.14.1, 00:00:09, FastEthernet0/1
R 10.1.2.0 [120/2] via 10.1.34.1, 00:00:14, FastEthernet0/0
[120/2] via 10.1.14.1, 00:00:09, FastEthernet0/1
R 10.1.3.0 [120/1] via 10.1.34.1, 00:00:14, FastEthernet0/0
R 10.1.12.0 [120/1] via 10.1.14.1, 00:00:09, FastEthernet0/1
C 10.1.14.0 is directly connected, FastEthernet0/1
R 10.1.23.0 [120/1] via 10.1.34.1, 00:00:14, FastEthernet0/0
C 10.1.34.0 is directly connected,
FastEthernet0/0 Router#