Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
So let's look at optimizing spending three Packet Tracer once again makes this easy.
We can see that these ports are blocking in spanning tree and so is this port to confirm that On Call
1 we can use the command shows spanning tree various v lines will be shown with this command he has
VLAN one we can see that port gigabit 1 0 23 is forwarding 24 blocking 1 0 1 is forwarding but 2 and
3 are blocking for VLAN 1 for VLAN 10 The result is the same VLAN 20 result is the same.
Same is true for violent 30 and a villain 100 again.
The problem is if lots of pieces in the access layer want to send traffic to lots of servers over here
in the network all of their traffic has to go via court too and then it's going to be sent across the
single gigabit 1 0 23 link to the servers that's not an optimal way of doing it now and a lot of cases
access switches have multiple villains and you can improve the performance by sending some traffic using
this uplink and some traffic using this uplink after the moment no user traffic uses this uplink at
all because of this port of blocking no traffic uses this uplink because of this port is blocking no
traffic uses this uplink because this port is blocking and the same is true about gigabit 1 0 24 the
only traffic that is permitted out of a spanning tree port and accepted in on a spending tree port are
network protocols such as CBP Alo DP spanning tree and a few others normal user traffic cannot use any
of these links effectively and logically those ports have been disconnected from the network so those
links are therefore redundancy but we are wasting the bandwidth on those links so let's optimize these
spanning three network we've been told that call 1 should be the route for Ord v lands and co 2 the
route for even v lands now in the exam it will be more clear than that but let's assume that our order
v lands or VLAN 1 10 and 30 and or even v lands are 20 and 100.
So on call 1 spanning tree v land 1 route primary you can do it that way or you can specify priority
and specify a priority.
I'd like to use the property of zero event lowers the spending tree property to the lowest possible
number in the exam it'll be more clear about which option you should use.
So for VLAN 1 tenant 30 I'm gonna make this switch the route.
Notice how the colors have changed all ports are now forwarding they green ways before they went to
Green on court to for those v lands we want to have that switch as the backup route you want to keep
your core switches as routes so spanning tree V Line 1 priority notice it needs to be in multiples of
four thousand and ninety six so for V Line one V Line Chen and a villain 30 we going to make that switch
the backup route so now when we look at call 1 show spending treat villain one.
Notice the switch is the root to switch for villain one.
It has a property of one.
The reason why it's a property of one is that the property is determined by the actual property plus
the V land.
No notice properties 0 plus extended system my D so 0 plus 1 is 1 giving the local switch a property
of 1 and the switch is the root.
So that's the property of the root switch.
When we look at the ports.
Notice all ports of forwarding.
What about the second switch core to show spanning tree VLAN 1 what you'll notice is all ports of forwarding
except for gigabit.
1 0 24.
Now the indicators in packet tracer are green because it's not showing us the output for all v lands
the V lands do differ.
So as an example back on call 1 show spanning tree VLAN 20.
Notice a lot of ports are still blocking on the switch.
So call 1 is not the route for VLAN 20.
Another switch is the route for VLAN 20 if we have a look on code to show spanning tree v land 20 the
switches the router for or backed a villain a villain 20 and it has all ports forwarding so packet tracer
and a real switch will not show Amber or orange.
If you're using pervy land spanning tree and a trunk port is blocking on some v lands and not on other
v lands.
Okay sir show run pipe include spending tree events the configuration of thus far under the switch show
run pipe include spending tree that's our configuration notice we can specify all the V lands in one
go my doing the following so we want the switch to be the route for v lands twenty and V lands one hundred
suspending TV Land twenty and one hundred property zero on the side spanning tree v land twenty one
hundred property four thousand and ninety six.
It's good practice to have your core switches being root switches and backup routes for other v lands
so show spanning tree v land twenty notice it's still going through different states previously however
we had a lot of blocking ports for VLAN 20 on call one that will hopefully now improve and there you
go.
The only port that's blocking is gigabit 1 0 24 for that villain.
All other ports are forwarding so that's much better.
We've been able to optimize spanning tree by making call one the route for some v lands and court to
the route for other v lands.
That means that if we had v VLAN 10 and 20 connected to the switch V Line 10 traffic would take this
uplink a v land 20 traffic would take this uplink and on the switch the land 10 would go to call 1 v
land 20 would go to court 2 and on the switch v land 30 would go to call 1 v land 20 would go to court
2 we still have a problem however because the links between the two switches are still blocking.
So again show spanning tree v land twenty notice on call 1 this port is blocking for veal and 20 and
it's blocking for v land 100 hundred on the side show spending tree v land 1 port 24 is blocking for
v land 1 for v land 10 and for v land 30 we want to combine or join these two links in an ether channel
to get better throughput.
So that's what we're gonna do in the next video.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.