I like how you snap us back into the scope of ccna for those trying to certify... It's easy to jump around and lose yourself when you are learning this information.
This is incredible information for me. I am desperately trying to scrape together the IOS knowledge as well as the fundamentals at the same time. This is very easily digestible with the walkthrough and structure of the information. Thank you for this!
When I configured inter-vlan routing for (10,20,30) and was able to ping, I thought "bada bing!" This was a fantastic exercise, helped me reinforce some points while studying. Thanks for taking the time to do create this lecture and demonstration.
Crystal Clear brother thank you so much for the clear lecture I was struggling from the CCNA 1 to CCNA 4 today watching your lecture I got it all. best of luck keep up the good work.
thank you for the video and explaining VLANs it's also important to differentiate between broadcast domains and collision domains since VLANs are a layer2 thing
I've been trying to understand VLANs for MONTHS. I work with them on the regular in my job, and it seems like the more I study them the more confused I get, or the more I doubt what I thought I knew. It's a seemingly simple enough concept. I can't wrap my head around it. Here's hoping this video helps!
Man, wish I found you earlier! You made this all make sense so well. I'm half way through CCENT2 so I'll definitely subscribe and dig through your videos! Thanks!
Not a CCNA, but with my basic networking experience from seting up my home network vlans this video was very clear and a great run through. Maybe I should take a few classes. I am trying to setup a more secure segmented home network for wired, wireless, backup server, media server, security, and home automation. It has been pretty fun learning this but definately could use more structured knowledge so I don't leave any holes. Thank You.
Thanks a lot! you are very straight forward .you make learning look like a piece of cake .I'm trying to get my cert by the 23 . I really think you my guy! thanks again!
Woooooow!!! man!!!, thanks a lot!..your job is just espectacular...I got engaged since the very first moment. I will watch all of your videos, and make them essential part of my CCNA exam study prep. Keep up the good work!!!
Hi Do how can I do the same configuration you did in the last example 1 router 2 Switch each Switch three VLANS the addresses from a server part (so far I know how to do) I want to create another such configuration and connect both. (Connecting the routers) but the same server will share the same VLANS. Is it possible?
I think your example of a blackhole vlan is faulty. You described an office with 2 network ports and a computer. Presumably, there's a voip phone as well. So you unplug your computer and plug in a switch. That port would not be in a blackhole vlan because that port was in use by the computer. Now, if this were an unused office then different story. Right?
1) at 36:15 on Switch1 f0/1 was put in Native VLAN 40, but not BLACKHOLE is 100 ? Was f0/4 supposed to be in Native VLAN 40 but not f0/1? 2)Why f0/4 in not listed in both switches after sh vlan br ? Thank you for the great videos!
thanks for the video. its strange to me when u buy the book to study for CCNA, and this kind of explanation u don't see it there. how do u expect to be extremely good on your day 1 at your job. I feel am learning more from youtube then reading a book.
can someone explain why only putting the native vlan into the trunk allows all the other clans over the trunk? usually, I add all the vlans individually for example switchport trunk allowed vlan 5-15
Native vlan is separate from adding specific vlans, or pruning, the trunk links. Native traffic is all traffic that serves management purposes (in most cases and for your ccna). If you don’t specify specific vlans on a trunk link... all vlans are allowed over that link by default. If you did a switch port trunk allowed vlan and added the vlans specified.. then those will be pruned to be the only ones allowed.
Nope. Native vlan is not specifying specific vlan traffic. This traffic doesn’t really get tagged, like SSH traffic for example. - native vlan is set for management traffic in a sense and we tell that link what our native vlan is on the network. if you configure a trunk port using the following, it will allow all vlans. - switchport mode trunk - switchport trunk encapsulation dot1q - switchport trunk native vlan 256 If you configure the following it will restrict only these vlans from communicating: - switchport Mode trunk - switchport trunk encapsulation dot1q - switchport trunk native vlan 256 - switchport trunk allowed vlan 10,20,30 Vlans 10, 20, and 30 would be the only subnets that would be tagged on that link and would allow communications. If you used an IP in vlan 40 on that trunk link, it would not work.
Sorry, I don't have Packet Tracer yet, I have a question. What would happen if I connect the two switches in different interfaces? In the lab they are connected through ports Fa0/4 in each switch. Will the trunk work? REALLY awesome video.
Yes you can use any switchport connecting to another switch as long as you use the correct interface configurations for it to work. Typically, to keep designs and documentation clean, as well as for studying - you would want to try and match up the same ports. Makes life a little easier.
hey man, thanks for the vids. i have ICND1 coming up way too soon and these have been a big help. quick question, is "int f0/2" and "int fa0/2" the same command? thanks!
Yes... but I’m not sure if f0/2 would be acceptable on the exam. It’s been a year since I proctored exams and I’m pretty sure it’ll be “fa” or fastethernet, and it’ll be “Gi” or gigabitEthernet on the exams. Ask the proctor of the exam what short hand is allowed.
@@josephinemchale4763 true, when your in IT, everyone tends to drop their laptops off at your house for repairs, like we're all guaranteed PC repair experts ;-)
ARP is most definitely layer 2. Although it uses logical address, it’s a broadcast at layer two for switches and other nic’s utilizing the tcp/ip stack to understand where things are ‘located’ within the same broadcast domain on the network.