Video není dostupné.
Omlouváme se.
VLANs Explained: How Do They Impact Switch Forwarding?
Vložit
- čas přidán 18. 08. 2024
- In this video, we'll explain VLANs and how they impact switch forwarding in simple terms. Learn about VLAN trunking, 802.1Q, access and trunk ports, and VLAN tagging. Perfect for CCNA students and anyone wanting to understand LAN switching!
Video Vs. the Books:
As with all the videos in this playlist, the content mirrors the scope of content in one section of the Cisco Press CCNA Cert Guides, Volumes 1 and 2. In this case:
- Volume 1
- Chapter 8
- Section 1
Chapters
00:00 Intro
01:46 Single Switch VLANs
09:21 Multi-Switch VLANs and VLAN Trunking
17:30 Exam Success
Related Review Videos:
Term Mind Map: VLANs: • Memory Mastery: Mind M...
Review by Interview: VLANs and Trunks: • Interview Review: VLAN...
Links - New Books in 2024
Cisco Makes Minor Updates to the CCNA Blueprint (Version 1.1)
• Cisco Reveals CCNA 200...
Major Updates to the CCNA Books
• Minor CCNA Blueprint U...
Which Blueprint Should You Pursue? (2024)
• Which CCNA Blueprint S...
Product Links
Click the links below if you'd like me to earn a small affiliate sales commission if you buy anything from the publisher!
Ciscopress.com/NewCerts Page (News, Announcements):
click.linksyne...
Wendell’s Website Products page
www.certskills...
Excellent explanation of VLANs basics and VLAN trunking. This is very helpful.
Great job, Wendell!
Hey Gus. Thanks!!
@@networkupskill Hey Wendell, You're welcome!!
oh my this is very informative lesson thank you sir
My pleasure!
Thank you for another video! Have a nice weekend!
Thank you! You too!
Hi Wendell - I agree excellent explanation of vlans - Brilliant video Thanks
Thanks for the great feedback! Good to hear from you again...
@@networkupskill When is the next study video being released thanks Wendell? Hope you enjoyed Cisco live👍
Cisco Live is a joy. "Summer camp for networking nerds" - the nickname - pretty much nails the vibe.
New videos every Wednesday 9AM US Eastern time in June and July is the plan... I try to announce the lineup early each month: www.linkedin.com/posts/wendellodom_ciscolive-ciscochampion-activity-7205980839975813124-25Dj/
Those are the content videos... I don't pre-announce the review videos.
@@networkupskill Thanks so much for the info 👍
Hi Wendell - More study this evening 17/6/24 - Just logged into the CCNA 200 - 301 Network simulator lite - volume 1 - Brilliant😊
Hey Steveo - Yeah, they did a nice job with the Sim! Enjoy your labbing!
@@networkupskill Looking forward to the spanning tree studies 👍
Thank you
You're welcome
A very difficult topic made so easy here .Thanks .
1 question regarding native Vlan .
When switch at the sending side sends a frame over a trunk a vlan header is added to the frame ,(this was the main difference between an access link & trunk link) .now wen at receiving side a switch receives a frame without the TAG how will it differentiate as it doesn’t rely on config for trunk link ,it sees the frame with tag and identifies .
Hi Sana,
You're welcome! :-)
If the receiving port is operating as a trunk (an important distinction), and the arriving frame does not have an 802.1Q tag/header, then it assumes the frame is in the native VLAN.
More generally, when a receiving port is operating as a trunk, then it's obvious how it determines the VLAN to associate w/ incoming frames that arrive w/ 802.1Q tags. The case with no tag is when it relies on the port's native VLAN setting.
Is the "Flag" field in the dot1q encapsulation the "DEI" Field?. Also if SW1 and SW2 are connected via TRUNK - ACCESS instead of TRUNK - TRUNK? What happens then?
On flag and DEI, yes. Thanks, I hadn't noticed, since the discussion didn't mention it.
Well, certainly you wouldn't want to have one switch trunk and the other operate as an access link. But the access switch will discard incoming frames that have 802.1Q headers. Those send by the trunking switch in the native VLAN won't have 802.1Q headers, so the switch operating as an access port will accept the frame and consider it to be in the same VLAN configured as the access VLAN. EG, if the trunk end had native VLAN 2, and the access end used access VLAN 2, then they could successfully communicate in VLAN 2. But if say the VLANs were 2 and 3 in that case, it would cause frames to hop to a new VLAN.
Hi Wendell - Just watching this video again - Just to confirm please that you wouldn't need a separate router if these switches can do L2 & L3? Thanks Stevo
Yes indeed, Stevo - anything that'll perform routing meets the requirement. I like showing a separate router early in the learning path so it's more obvious that routing is required and to get folks thinking about what it's doing.
@@networkupskill Brilliant video though Wendell - Thank you
@@networkupskill Would you know if you are going to be doing any study videos on Spanning tree? Thank you Wendell
Yep! I'm working through the chapters in the CCNA Official Cert Guide, Volume 1, in order, to create a video on the first section from each chapter. The next two videos are from the two chapters on Spanning Tree. I'm also trying to release the videos on Wednesday mornings US Eastern time... so, Spanning Tree on June 19 and 26! Thanks for asking...