Original subtitles

In this lab we are going to continue configuring our campus and network

we've been asked to use both ADP or Cisco Discovery Protocol and Alo DP or link player Discovery Protocol

to verify links.

So we need to check the links between the devices and confirm that the links are correctly configured.

Per the diagram we need to verify which ports of forwarding and blocking in spanning tree.

And then we need to optimize spanning tree with core one being the root of four odd villains and core

to being the root for even villains.

So have a look at this topology package trace and makes this easy which links are currently blocking

in spanning tree.

Can you see which ports are blocking notice on call one of these ports or blocking and spanning tree

on access 1.

This port is blocking in spanning tree Now think about to the problem.

If a large amount of traffic was sent from many pieces in VLAN 10 on this access switch to this server.

How would the traffic flow traffic would have to go across this uplink to Core 2 and then use this single

gigabit 123 link to call 1 to get to the server.

Now imagine that you had many servers here as well as many pieces on switch 2 and switch 3 trying to

get to a group of servers on the left hand side let's say they were moving large files.

How would the traffic flow so traffic from all of these pieces in VLAN 10 20 and 30 would end up going

via CO 2 and then going across the single link to core one to get to these servers.

These links are being blocked by spending tree so no traffic will go from VLAN 20 to call 1 all the

traffic will go to court to get to the servers on the left hand side.

That's going to be a problem because we're gonna have a bottleneck or an issue on gigabit 1 0 twenty

three this is a gigabit port but all of these uplinks are also gigabit ports and pieces are sending

traffic at gig speeds so if you have 100 pieces sending traffic to multiple servers of this gigabit

once there are 23 link is going to be oversaturated.

In other words there's gonna be too much traffic for that single link.

So we want to optimize our spending tree and this topology and ensure that core 1 is the route for villains

and court 2 is the root for even villains.

In other words call 1 will be the root for villain 1 villain 10 and villains 30 CO 2 will be the root

for villain 20 and villain 100.

So we're going to split traffic across the course switches.

You also need to configure ether channel on the core switches so that we don't have one of these links

blocking both of these ports should be forwarding so to do that we're going to use ether channel.

We also need to configure IP addresses on the core switches to enable into VLAN routing.

Here are the IP addresses of call 1.

Here are the IP addresses of Core 2 and you need to configure IP addresses on the access switches in

VLAN 1 in the next lab.

After this we'll configure IP addresses in the pieces and verify connectivity in our campus network

to ensure that things are working right.

So this is a big lab.

Are you able to do it yourself.

Download the attached package to trace a file and try and configure the lab yourself or you can watch

me in the next video complete to this lab.

Best way to learn is to try things so try it.

If you get stuck.

Have a look at to the videos to help you.