






Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
Daisy Chain, Collapsed Backbone Architecture, Subnet, Configure and Run the Simulation, Switch to Next Scenario, Configure and Run the Simulation, Response Time. This lecture also explain other topics than above mentioned related computer network.
Typology: Lecture notes
1 / 10
This page cannot be seen from the preview
Don't miss anything!
This lab compares the application performance of two different network architectures; Daisy Chain and Collapsed Backbone Network. In the case of collapsed backbone data network, there is a core switch in the basement equipment room. The core switch is linked directly to a workgroup switch on each floor. Another option is to link the switches in a daisy chain. In this case the basement core switch is linked directly to the first floor switch, the first floor switch is linked directly to the second floor switch, and so forth.
This lab shows the application latency introduced by connecting building switches in different ways.
An office building has 10 floors, each having many users connected to a 10Base-T workgroup switch. The users share an Oracle server and seven file and print servers in the basement.
In Scenario 1, the switches on each floor are daisy chained to the core switch in the basement. We will see that this daisy chain approach introduces high application latency to users on the highest floor.
In Scenario 2, the daisy chain topology is retained, but the core switch is moved to the fifth floor. We will see that this reduces latency on the highest floor but increases it on the bottom floor.
In Scenario 3, the core switch is kept in the basement, but a collapsed- backbone topology is used, in which the core switch in the basement is linked directly to the workgroup switch on each floor.
Step 1:
Several users are connected to a switch on each of the 10 floors. The users share an Oracle server and 7 File, Print, and Email servers in the basement.
Subnet: A subnet is a container used to create hierarchy of network levels. Double-click on the subnet named “7 File Print & Email Servers” to enter it. Here, we can see the servers clustered together. Right-click in the workspace and select Go To Parent Subnet to go to the upper subnet.
Step 3: View Results View the Oracle Application Response Time for users on Floors 1, 5, and 10.
Note: To toggle the graphs on and off, use the hide or show all graphs button.
Now we have the statistics for users on all floors on the same graph.
Your results should be similar to the graph above.
Users on the top floor report high application response times. So the company decides to reduce the number of hops for the users on upper floors by moving the core switch and the servers to the fifth floor.
The company decides to change the architecture from a Daisy Chain to a Collapsed Backbone network hoping to achieve the same application performance for all the users.