Private VLANs

Ғылым және технология

Understanding Private VLANs
We can separate layer-2 traffic with VLANs, but sometimes that’s not enough. Sometimes we need more segmentation, and that’s where Private VLANs come in.
Private VLANs are VLANs within VLANs. One VLAN is the primary VLAN (which is where shared devices go) and the rest are secondary VLANs.
Devices in secondary VLANs cannot talk to devices in other secondary VLANs. Yet, the entire system still retains a single logical subnet, and can have a shared (AKA ‘promiscuous’) gateway.
Secondary VLANs may be ‘community’ or ‘isolated’. Devices in a community VLAN can talk to each other, but not to other secondary VLANs. Devices in isolated VLANs cannot talk to anything except for promiscuous devices.
How does trunking affect this? That depends if your switches are all PVLAN aware or not. If not, you may need to configure a ‘promiscuous private vlan trunk’ or an ‘isolated private vlan trunk’.
A big thank you to Patreon supporters! You can download the lab files here:
networkdirection.net/labsandq...
If you’re studying for the exam, consider The CCNP Switch Foundation guide (affiliate): click.linksynergy.com/link?id...
Overview of this video:
0:00 Introduction
0:43 Classic VLANs
1:18 The Need for Private VLANs
2:16 PVLAN Overview
3:15 Promiscuous Ports
4:20 Community VLANs
5:10 Isolated VLANs
5:47 Configuration
9:27 Trunking
LET'S CONNECT
🌏 / networkdirection
🌏 / netwrkdirection
🌏 / networkdirection
🌏 www.networkdirection.net

Пікірлер: 29

  • @ARUNVerma
    @ARUNVerma6 ай бұрын

    This is how even way complex thing can be boiled down and pour into a cup as soup . hats off Sir

  • @Nerrad1900
    @Nerrad19005 жыл бұрын

    great stuff again, making complicated protocols easy. love this channel

  • @francescogalli4033
    @francescogalli40335 жыл бұрын

    Argument by argument you are helping me understanding complex networking (ccna point of view) Thanks, i love your videos ✌🏻👏🏻👏🏻

  • @droidcrasher
    @droidcrasher5 жыл бұрын

    GREAT WORK! Great Explanations! Keep it up!

  • @NetworkDirection

    @NetworkDirection

    5 жыл бұрын

    Thanks, glad it’s all making sense!

  • @charlespearl2793
    @charlespearl27935 жыл бұрын

    Great explanation and video.

  • @NetworkDirection

    @NetworkDirection

    5 жыл бұрын

    Thanks!

  • @NetworkDirection
    @NetworkDirection5 жыл бұрын

    Full article here: networkdirection.net/articles/routingandswitching/private-vlans/ Downloadable lab here: networkdirection.net/labsandquizzes/labs/pvlan-lab-1/

  • @luismiparra
    @luismiparra5 жыл бұрын

    Thanks for the video. :)

  • @NetworkDirection

    @NetworkDirection

    5 жыл бұрын

    You're very welcome. Hope you liked it

  • @Devgrusome
    @Devgrusome5 жыл бұрын

    Random comment for a video like this... But I was wondering if you could do any Palo Alto NGFW stuff soon, if you can!?

  • @NetworkDirection

    @NetworkDirection

    5 жыл бұрын

    Thanks for the suggestion. Unfortunately I don’t have any Palo Alto to use to build up some content

  • @gjbm1782
    @gjbm17823 жыл бұрын

    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?

  • @rendog311rendog2
    @rendog311rendog25 жыл бұрын

    hey great video and thanks for your efort but why are configuring the host ports in two ways? is one better or newer then the other or just for demonstration?

  • @NetworkDirection

    @NetworkDirection

    5 жыл бұрын

    Do you mean community and isolated? I used both here for demonstration. You can use one, the other, or both. Neither is better or newer than the other. They serve different purposes, depending on what you need to achieve.

  • @rendog311rendog2

    @rendog311rendog2

    5 жыл бұрын

    Network Direction but you said at 6:22 that you are gone use 1x primary vlan and 2x community vlan. maybe I‘m wrong, my english is not that good..

  • @NetworkDirection

    @NetworkDirection

    5 жыл бұрын

    Yes, you're right! I did say two community VLANs. I was thinking of a lab I did where I used an isolated VLAN. One community VLAN for each customer, and the primary VLAN to tie it all together. The Primary ports need to be 'promiscuous' so hosts in the secondary vlans can reach them.

  • @rendog311rendog2

    @rendog311rendog2

    5 жыл бұрын

    Network Direction ouu ok now is everything clear, I was just wondering 😅 thanks man for time and keep up the great work!

  • @NetworkDirection

    @NetworkDirection

    5 жыл бұрын

    Glad to help!

  • @landro3552
    @landro35525 жыл бұрын

    Hey man could you please do a video on Wi-Fi channel and Frequencies, MHz, GHz and stuff like that? Please I really need this these days bro . Much appreciated

  • @NetworkDirection

    @NetworkDirection

    5 жыл бұрын

    Thanks for the suggestion. I'm going to be honest here, WiFi is not my strong point at the moment. Mostly I've been focusing on a weird hybrid of Enterprise, data centre, and the smallest dash of service provider. If I start branching out into WiFi, I will definitely add something here.

  • @landro3552

    @landro3552

    5 жыл бұрын

    @@NetworkDirection Ok man , things about servers would be great too. Keep em coming

  • @rahimhaleem
    @rahimhaleem5 жыл бұрын

    If you have private VLAN support on both switches then which VLAN ID do you allow on trunk links between them? is it only primary VLAN ID or you allow primary, community and isolated VLAN ID as well over trunk links?

  • @NetworkDirection

    @NetworkDirection

    5 жыл бұрын

    Allow all the vlans that you want to trunk. So Primary, and whichever secondaries that you need (you don't have to do them all, it depends on what you're trying to achieve)

  • @ThelongWatches
    @ThelongWatchesАй бұрын

    Is this same concept with Q in Q vlan?

  • @445Matty
    @445Matty5 жыл бұрын

    How about the other side - does the port have the same commands?

  • @NetworkDirection

    @NetworkDirection

    5 жыл бұрын

    Do you mean if you have two switches with a trunk link? If they're both PVLAN speakers, then yes, the same commands. If they're not PVLAN aware, then the other side is configured as normal.

  • @rahimhaleem
    @rahimhaleem5 жыл бұрын

    Trunking concept is not clear, could you please give a practical example for trunking with configuration?

  • @NetworkDirection

    @NetworkDirection

    5 жыл бұрын

    Maybe this will help: www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/12-2/31sga/configuration/guide/config/pvlans.html#wp1130380

Келесі