VIDS

[Dan DeCoursey]

Hello,

I need to get brushed up on VIDS (Procurve/VLAN)

Originally I had 1 LAN so  I  would rename the default VLAN and of course this was VLAN1 on all my switches

then I added a second network  and a 2nd VLAN (VLAN2) all was fine

Then I  constructed a 3rd LAN and installed a new Procurve...this switch only served this new network  so again, I renamed the defualt VLAN and it was now VLAN1 on this new switch

after sometime  I had to provide access to the 3rd network to the users on my original network (vlan1)   so I composed a 3rd vlan on my original switch and it became VLAN3  on this switch  I tagged a ports on this original switch and the new switch   to provide uplink between VLAN1 and VLAN3  but back on the new switch for network 3 is  the 3rdnetowrk VLAN is defined as    VLAN1

I am being told these VIDS must match or some sort of packet based confusion will arise    is that true  ?? 

Since I had  VLAN 1 and 2 already establised  on my  original switch.......... that the new  VLAN would be VLAN 3

so on the new switch  that is dedicated to the 3rd network  I would have had to leave the defualt vlan untouched and create a new VLAN3 and put all ports = untagged to VLAN3    and now  tagged uplink ports  between the 2 switches will operate correctly

ca n this be confirmed ?

[Vince_Whirlwind · Accepted solution]

Yes, ideally you should move everything on your 3rd switch to be on VLAN3, then your first switch will understand where VLAN3's subnet is.

It is possible to bridge VLANs, if you have VLAN3 untagged on a port on Switch1 patched to a port on Switch3 that is untagged in VLAN1, then it works. However, this isn't something you should have in your design.

[Dan DeCoursey]

I guess bridging happens by defualt  ?    since this is how I have  it all working now ( link ports  are untagged)

thanks for the verification  looks like I have  some "redesigning " to do