God Damn you make it so simple. What an awesome teacher. I've never seen a video like this that would've take me ages to understand. Thanks boss!!! Keep up the good work...
It was stated that VTP must be off or in transparent mode to use PVLANs. This is correct, but incomplete. The new version of VTP, VTP v3, will allow PVLANs with VTP running normally. It does not need to be in transparent mode.
In a realsitic scenario I have maybe 50 Switches. Most VLANs are "normal" VLANs, a few are PVLANs. - Is the Promiscious Port the same port as my normal Uplink-Trunk on the switch? - Do I have to create the same PVLAN-conifg on every switche exactly the same? - What if I untag eg VLAN152 (from the video) on another switch as normal access port? Can I access from there the "isolated" host an the PVLAN-switch (and vice versa)? - This leads to the question, do I have to create for each PVLAN a own interface on the router? Or only for the primary VLAN? - Is this whole concept based on Q-in-Q tag-stacking? Or how does eg SW48 know that VLAN152 on SW15 is an isolated secondary-PVLAN?
Excellent didactics. Finally digging the concept of private VLANs 🙏🏻🙄 So far I'd imagined them as parallely arranged VLANs separated by Metainfo. Seeing the subdivided structure pVs make perfect sense now. Scrapping my VLAN concept, starting from scratch (once again😅).
Hello! What is the main purpose of using private VLAN? How is it different from creating other VLANs in a database vlan of a switch and assigning that port a specific vlan?
You can use the same subnet. If you create multiple VLAN's you need to create multiple subnets. With private VLAN's you can have one subnet with multiple private VLAN's.
Why did we need to create two Isolated Vlans? Isn't it that one Isolated Vlan would have been enough? What would be a good use case to have more than one Isolated VLAN?
Thanks so much! Please check out the following link where we have an entire CCNA Packet Tracer product containing PT files and video walkthroughs for multiple CCNA Labs: www.kwtrain.com/store/VHaC4F7M All the best in your studies.
God Damn you make it so simple. What an awesome teacher. I've never seen a video like this that would've take me ages to understand. Thanks boss!!! Keep up the good work...
I watched several pvlan videos, not a single one but yours explained the benifit of limiting the broadcasts.. Thank you.
Best!! I'm a CCIE Enterprise and I'm only 24
Wtf im 24 too but I wank in a rented basement. How much you make?
Your a damn good teacher. I've purchased one of your video in past off Udemy. Can't thank you enough for all you do to teach us Cisco.
Why should we use private VLANs instead of using different VLANs on these ports? Will it reduce CPU usage?
It was stated that VTP must be off or in transparent mode to use PVLANs. This is correct, but incomplete. The new version of VTP, VTP v3, will allow PVLANs with VTP running normally. It does not need to be in transparent mode.
Very good way to covey how private vlans work! Benn struggling to understand this for a bit until now.
Dear Kevin,
Please make video on CCNA security. Share link if you already have.
Regards
Best I have seen so far.
Agreed
In a realsitic scenario I have maybe 50 Switches. Most VLANs are "normal" VLANs, a few are PVLANs.
- Is the Promiscious Port the same port as my normal Uplink-Trunk on the switch?
- Do I have to create the same PVLAN-conifg on every switche exactly the same?
- What if I untag eg VLAN152 (from the video) on another switch as normal access port? Can I access from there the "isolated" host an the PVLAN-switch (and vice versa)?
- This leads to the question, do I have to create for each PVLAN a own interface on the router? Or only for the primary VLAN?
- Is this whole concept based on Q-in-Q tag-stacking? Or how does eg SW48 know that VLAN152 on SW15 is an isolated secondary-PVLAN?
Excellent video. Pretty much explains everything I didn't understand about private VLANs.
Excellent didactics. Finally digging the concept of private VLANs 🙏🏻🙄
So far I'd imagined them as parallely arranged VLANs separated by Metainfo. Seeing the subdivided structure pVs make perfect sense now. Scrapping my VLAN concept, starting from scratch (once again😅).
Thanks Kevin! Awesome video with a perfect structure, as usual!
Hello! What is the main purpose of using private VLAN? How is it different from creating other VLANs in a database vlan of a switch and assigning that port a specific vlan?
You can use the same subnet. If you create multiple VLAN's you need to create multiple subnets. With private VLAN's you can have one subnet with multiple private VLAN's.
Thankyou Kevin for your videos.
Hi kevin Wallace. Great jobs and great videos. I am always watching your video mate
Why did we need to create two Isolated Vlans? Isn't it that one Isolated Vlan would have been enough? What would be a good use case to have more than one Isolated VLAN?
Kevin, I clicked the like button at the beginning of the Video ;)
Thanks for the video, well said.
Well put together. Thank you for such excellent content. 👏
Another great video Kevin. Short and straight to the point. Very easy to understand thanks to your clear explanation.
very nice Concept!
Thanks so much Prince of Network ❤️
What's the point of creating more than one Isolated VLAN? No host inside the Isolated VLAN can communicate with any host inside this VLAN anyway.
maybe some other subnet or some policy specific for that isolated vlan, but yeah mostly you have one private vlan
That's my question. This seems to make things harder to troubleshoot than individual VLANs with explicit rules.
@10:42 why is the ports column in sh vlan private-vlan blank? Switch ports were assigned to these private vlans.
Thank you Kevin I'd like to see more videos, also will you be making any packet tracer labs for CCNA? thank you
Thanks so much! Please check out the following link where we have an entire CCNA Packet Tracer product containing PT files and video walkthroughs for multiple CCNA Labs: www.kwtrain.com/store/VHaC4F7M All the best in your studies.
Thank you!
Great as usual
Do you know if there's a way to expand the pvlan config to a switch that doesn't support pvlan? Does works with both vlan and pvlan traffic?