Scribd
Upload
55 views

Week 3 - ClayNet - Static Routing

This document provides instructions for a lab experiment on network virtualization using the ClayNet platform. The objectives are to understand the building blocks of ClayNet, create a simple client-server network topology using routers, switches and hosts, and learn about static IP routing. Tasks include creating the given topology in ClayNet, configuring IP addresses and gateways, setting up routing tables on the routers, verifying connectivity by pinging and using Wireshark to observe traffic. Observations of ping results, tracepath outputs and the impact of cutting a network link are to be recorded.

Uploaded by

vih
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
55 views

Week 3 - ClayNet - Static Routing

This document provides instructions for a lab experiment on network virtualization using the ClayNet platform. The objectives are to understand the building blocks of ClayNet, create a simple client-server network topology using routers, switches and hosts, and learn about static IP routing. Tasks include creating the given topology in ClayNet, configuring IP addresses and gateways, setting up routing tables on the routers, verifying connectivity by pinging and using Wireshark to observe traffic. Observations of ping results, tracepath outputs and the impact of cutting a network link are to be recorded.

Uploaded by

vih
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Week #3

Understand the building blocks and usage of ClayNet Network Virtualization


platform with reference to OSI Layer.

Objectives of the Lab:


• Understand the building blocks of ClayNet.
• Build a simple client-server network using routers, switches, and network hosts.
• To learn the static IP routing behavior such as default and static routes and routing tables.
• Use common network utilities to verify LAN operation and analyze data traffic.

Prerequisites:
This lab assumes some understanding of the building blocks of communication networks
and basic client-server architecture.

Topology 1:
Create a topology in ClayNet, as shown in following figure.

Important Instructions:
To access ClayNet, type 10.1.10.10:9000 in browser. Login credentials will be provided by the
faculty incharges.

Execution Tasks:

Task 1: Understand the network and compute components available in ClayNet.


Task 2: Drag and drop the necessary components to create the given topology. Provide the
names for compute, select OS (Ubuntu 16.04 – Lite or Ubuntu 16.04 – CLI) and RAM (512 MB)
as shown below.
Task 3: Drag and drop the Routers and set the IP addresses for all the necessary router ports.
(You can also set them later by right clicking on the router icon and selecting ‘Device
Configuration’.)

Task 4: Go to connection manager and select appropriate Source, Source ports, Target and
Target ports and save the connection.

Task 5: To deploy the topology, save the topology first and deploy it by clicking ‘Deploy’
button available on the top. (Note: It will take few seconds or even minutes to deploy the
topology for the first time).
Task 5: Go to ‘Remote Desktop’ by right clicking on client and server icons and set the IP
addresses accordingly. Also add the gateway address. (Login: user - test, password - test)
Client:
IP Address ---> 10.10.10.2 Gateway ---> 10.10.10.1
Server:
IP Address ---> 30.30.30.2 Gateway ---> 30.30.30.1
Task 6: From client, ping to server 30.30.30.2. Ping will not be successful and Router1 will
reply with ‘Destination host unreachable’.

Task 7: Set up the following routing table entries for Routers 1 & 2.
Routers Destination Next hop gateway Via
Router 1 30.30.30.0 20.20.20.2 Direct
Router 2 10.10.10.0 20.20.20.1 Direct
Steps to add the routing table entries:
Step 1: Login to Router1 by right clicking on Router icon and selecting ‘Console Access’. (Type
‘Enter’ key once to get into Login screen. Username - test, Password- test@12345)
Step 2: Display the routing table to view all static routes using the command.
show route summary -s active data

Note in routing table of Router1 that there is no route to reach the destination network
30.30.30.0/24. Go to configure mode and start configuring the router for all the possible routes.
Step 3: Configure a static route in Router1 for destination 30.30.30.0/24 with next-hop gateway
as 20.20.20.2, which is the IP address of Router2.
Step 4: Check routing table again and verify that the route is added.

Step 5: Repeat the steps 3 & 4 to configure a static route in Router2 for destination
10.10.10.0/24 with next-hop gateway as 20.20.20.1, which is the IP address of Router1.
Task 8: Now Ping will be successful as all the required routers are now configured. Observe the
TTL getting decremented by 2 because two hops/routers are in between. Also keep the Wireshark
ready for observation.
Task 9: Also observe the output of tracepath -n 30.30.30.2 command on Client.

Record these observations in your notebook. Upload the following screenshots in Edmodo.
1) Pinging
2) Wireshark capture

Topology 2: (Mandatory)
• Create and deploy the topology as show above.
• Appropriately configure static routing entries in all three routers, so that server is
reachable from client desktop.

Observations Required:
• How many hops will client take to reach the server?
• Observe the RTT and justify your observation.
• While pinging, cut the link between Router1 and Router3. What will happen now?

Record these observations in your notebook. Upload the following screenshots in Edmodo.
1) Pinging
2) Wireshark capture

You might also like