CPEG 572 Data and Computer Communications

Report No. 04
Name: Deep Patel
Student ID: 1004106

Summary:
The lab-6 is anyalzing and analysis of the RIP protocol.To build the routing
tables routing algorithms are required.

Implementation
1 Create the new project and scenario No_Failure.
2 Select the campus in network scale list.
3 Add ethernet4_slip8_gtwy router and 100BaseT_LAN from the object
palette.
4 Change the configuration of the router as given in the manual.
5 Make three subnet same as Engineering and give name as Research, E-
commerce, and sales.
6 Add two more LaN in the project as shown in the lab manual.
7 Choose the statistics traffic sent in bits/sec, traffic received in bits/sec and
node statistics
8 Run the simulation for 10 minutes and change the global attributes as per
given.
9 Create a duplicatescenario and give the name as failure.
10 Add a failure recovery to the duplicate scenario and add the attributes as
given in manual.
11 Run the simulation and compare the results.
12 Obtain the IP address of the interface and compare the content of routing
table.
Results:

we watched that the reaction time of the bustling system was significantly
higher than the straightforward system. Likewise, the framework balances
out fast contrasted with the bustling system. High thickness links were
extremely useful in upgrading the outcomes. With high thickness links we
get occupied system creating a reaction time as though it were a
straightforward system and it settles truly quick as well. It was evident that
Record server balances out a considerable measure speedier than both the
Database Server and the Internet Server. Second, Database Server change
the minimum. It got to be distinctly obvious that one server supplanting the
three server has the most load, so it CPU Usage is the most and it to some
degree higher than the Internet Server alone

Answers:
1. From the practical I got the graph compared to simple network and busy
network which is following ,the upper section indicate busy network and
bottom graph indicate simple network.

From the HTTP response time for the direct and possessed frameworks,
the essential framework is addressed in blue and the clamoring
framework is addressed in the shading red. The connection of the two
 time deferral would achieve a conclusion that the delay is significantly
less in the clear framework when stood out from the clamoring system.I
have considered four unique circumstances for relationship and they are
depicted in the diagram as underneath: The fundamental plot exhibits the
Ethernet concede time and from the figure we could see obviously that
the deferral in the clamoring framework is higher when diverged from the
essential framework. The accompanying plot shows the time concede
examinations of the TCP delay.I could grasp that the TCP delay for the
clamoring framework is fluctuating at first ata higher rate and after that it
subsides even yet in the meantime at a higher pace. On the other hand the
fundamental framework has a ver low fluctuating start. The clamoring
framework is to some degree fluctuating at the fundamental stage and
after that it starts to an unfaltering state. However in the meantime the
deferment is high here. The essential framework is having a consistent
time responde from the most punctual beginning stage. This could be
seen from the graph.
2. The CPU use in the midst of the Clamoring Framework Circumstance for
the webserver, database server, and record server are as underneath: From
the charts above, plainly Archive server offsets an extensive measure
speedier than both the Database Server and the Web Server. Second,
Database Server waver the base if you look at the degree on the y-center
point.
3. In the wake of rolling out every one of the improvements to the
connections, we have the accompanying outcomes: From the outcomes
above, clearly organize reaction time is substantially speedier and that it
balances out truly quick as well. At the end of the day, the Q4_FastNetwork
is perfect to Straightforward System rather than Occupied System simply
because we utilized high thickness links.

Conclusions:
In the conclusion, from this lab we can characterize the profile that
determines the example of use utilized by the clients of every office in the
organization. At last we cann see the differnec in execution of the system as
we change the situation.we took in the nuts and bolts of planning a system,
mulling over the clients, administrations, and areas of the hosts. We took in
this by utilizing OPNET device which is awesome for reenacting system
frameworks. We likewise, discovered that utilizing high thickness links will
upgrade the system extraordinarily and can even change over the reaction
time of a system to be so quick as though it were a basic system and it
balances out the system quick as well. We likewise saw that utilizing
separate servers for various exercises, for example, Database, records and
web gives better execution of CPU use. Accordingly, one ought to consider
utilizing high thickness links and separate servers for Databases, records and
Web to abstain from over-burdening only one server.