VLAN Trunk not working as expected

[cwachs]

My computer is tagging VLAN5. It is how I connect to all my radios in the field which use VLAN5 on the management IP. I know that is working properly. However, I will try your suggestion of deleting (not just turning off) the other VLAN5 I have.

[cwachs]

Deleting the old VLAN5 interface worked. If I just disabled it and changed the default to 5, it failed. If I deleted it and then changed the default to 5, it worked. I did not expect that behavior but at least it is fixed and I can catch the 2nd half of the football game!

[adairw]

cool. interesting management technique but sounds like a pain. glad it's working.

[cwachs]

Well, the purpose was to prevent anyone from plugging into any hardware and getting access, especially to management IPs. Though we don't run a DHCP server on the management side, if you did any amount of work, you could probably figure out our subnet. This adds an additional level of protection. Not all of our switches have 100% physical protection.

However, it can be annoying at times. :-)

Thanks for your help!

[sirhc]

Deleting the old VLAN5 interface worked. If I just disabled it and changed the default to 5, it failed. If I deleted it and then changed the default to 5, it worked. I did not expect that behavior but at least it is fixed and I can catch the 2nd half of the football game!

This probably is and is not a bug. It is a bug in that it lets you change the default VLAN ID to an ID in another VLAN even if it is disabled.

In reality it should force you to delete any VLAN enabled or disabled before you can assign that ID to the default VLAN or any VLAN for that matter.

I will ask Eric to change this in the next release that you many NOT use an ID already used in another VLAN even if that VLAN is disabled.