All language subtitles for 6. Packet Tracer Campus Network Part 2 Answers Part 5 EtherChannel

So let's have a look at spending three to show spending three veal and one notice we see a difference

here we see a port channel.

One thing to notice here is notice ports such as gigabit 1 0 1 and 1 0 2 1 0 3 0 point to point spanning

three links.

Where's the port.

Channel is a shared spanning tree link.

Now for the real world.

Typically once you've put interfaces into the port channel you do the configuration on the port channel.

However if you have problems do the configuration in the port channel and then verify back to the configuration

has also been applied to the physical interfaces.

If it's not applied to the physical interfaces do the config on both the port channel and to the physical

interfaces to ensure that the configuration is correct.

But typically you only need to do the configuration on the port channel so I'll show you that here when

I do the configuration on the physical interface it's not applied to the port channel but configuration

applied to the port channel is pushed it down to physical interfaces.

That's how it should work.

Sometimes in the real world you'll have problems with that to optimize spending tree.

What we want to do on those ports is specify spanning tree link type point to point that we'll make

rapid spending tree converge quicker shared links are typically used down to hosts or to hubs that we've

got switches here.

So we want to make the spanning tree link type point to point to make it converge quicker

so show spanning tree v land one

Now notice I did the configuration on the physical interfaces what I need to do actually is do that

on the port channel so spanning tree link type point to point and then I'll do something similar on

the side interface port.

Channel One spanning tree link type point to point and let's see if that's made a difference.

So show spending tree v land one that looks better notice the port channel is showing us point to point.

OK so this looks good on the side show spanning tree v land one notice on switch to no ports of blocking

previously one of the ports on switch to was blocking for v land one.

In other words previously gigabit 1 0 24 was blocking but it's not blocking at the moment because of

that port is part of the port channel.

Notice also the cost of the port channel is lower than other physical interfaces because this is a better

interface.

It's got 2 gigabit ports that make up the channel rather than just a single gigabit port on the side

show spanning tree v land 10.

Now notice here we don't see VLAN 10 propagated across the port channel.

Again if you have problems like this where configuration is done on the physical interface but is not

shown on the port channel type of these commands on the port channel.

So typically once you put your interfaces in a port channel you do the configuration on the port channel

interface port channel one switch port mode trunk switch port trunk we have to separate encapsulation

first so switch port trunk encapsulation dot one key switch port mode trunk

so notice now the configuration is shown on the port channel

and noticed when I use the command show spending TV Land 10:00 I still don't see the port channel because

on this side we getting an error with inconsistent port channel information we have to configure the

commands on the port channel to interface port.

Channel One switch port trunk encapsulation dot one key switch port mode.

Trunk

so we need to ensure that we have the commands on the port channel as well as on the physical interface.

Once you add your physical interfaces to the port channel you do your configuration on the port channel

rather than on the physical interfaces so let's verify the port channel by using these show interfaces

port.

Channel 1 status command.

Notice we told at the moment that the port channel is not connected.

So what I'll do is shutter the interfaces down.

This is one thing to remember with ported channel.

It's better to make all your changes while the interfaces are shut down and then no shut to them.

Once you've completed your changes.

If you have any inconsistency shutter the interfaces down and bring them up again to double check things.

OK so let's confirm the configuration on switch one that looks good on switch too.

We need to make sure that everything is the same.

So both sides look good there.

This configuration is configured on both sides

and the physical interfaces match that configuration on both sides to show spanning tree v land one

port.

Channel is forwarding so that's good show spanning tree v land one at the moment.

We still have a status of learning that should hopefully go to forwarding very soon.

There you go.

It's forwarding

show ether channel

portal channel shows us that the interfaces are active shows spanning tree v land ten notice now we

can see that a villain 10 is forwarding on the port channel.

Same is true for veal and 20 same is true for VLAN 30 and the same is true for veal and 100 on the side

show spanning tree or veal and 10 still needs to go to forwarding on the side.

So we need to just give it some time but you can see there is an example 100 is forwarding the 1 is

forwarding villain 10 is now forwarding a villain 20 is now forwarding and villain 30 is now forwarding

so on all villains on both sides the switches are forwarding on all ports this is what you want to have

in the core of your network you don't want to have your course switches blocking blocking ports should

be on the access switches so as an example on access one shows spanning tree v land one one of the ports

is blocking and we know which port is blocking its gigabit 1 0 24.

And the reason why is that we've made call 1 the route called 2 is the backup route so this port should

be blocking what about 4 VLAN 10 this port is also blocking a veal and 100 twenty three is blocking

because we made court to the route and we saw the LCD go orange but they've now gone back to Green because

packet tracer has updated the spending tree network so again we can see that the switch is forwarding

on all v lands so as I demonstrated in this video you can have problems if there's a mismatch or mis

configuration between the port channel and the physical interfaces the recommendation is to make sure

that the configuration is the same on both sides make sure that the configuration of both of the logical

interface.

In other words the port channel and the physical interfaces are the same on both sides so make sure

that this matches this but also make sure that this matches the configuration of the port channel on

the same switch as well as on the other switch.

So essentially everything should be a mirror image.

Make sure that this matches this makes sure that this matches this.

If you have problems like I had here shut the physical interfaces down confirm all the configuration

and then no shut the physical interfaces.

Hope that helps you for both the exam and for the real world.