penguinroundup
MIS
are there any known issues with trying to implement VLAN's using Cisco and non-cisco switches? We tried to configure a new VLAN over the weekend using 7 cisco2950 switches and one 48-port gigabit Linksys switch, and it completely blew up in our faces.
We had ALL the ports on ALL the 2950's configured to use the new VLAN, and each switch was patched in to its own port on the Linksys switch (not daisy-chained), each of which was configured to use the new VLAN as well. (see my attempt at a diagram below):
vlan1 (192.168.14.x)
\
Linksys Gb switch-- 2821 router
|||||||
7-cisco2950 switches
|
vlan2 (192.168.12.x)
(approx. 120 pc's)
What's bizarre is that out of 120 workstations patched into the new VLAN, about 45 of them actually got IP addresses and were working fine - the rest couldn't get an IP address or do anything. There was no rhyme or reason to it. The computers that were working were plugged into different switches. We banged our heads against the wall trying to figure it out, and eventually we just put everything back on the native VLAN and it was fine. What on earth were we missing??
We had ALL the ports on ALL the 2950's configured to use the new VLAN, and each switch was patched in to its own port on the Linksys switch (not daisy-chained), each of which was configured to use the new VLAN as well. (see my attempt at a diagram below):
vlan1 (192.168.14.x)
\
Linksys Gb switch-- 2821 router
|||||||
7-cisco2950 switches
|
vlan2 (192.168.12.x)
(approx. 120 pc's)
What's bizarre is that out of 120 workstations patched into the new VLAN, about 45 of them actually got IP addresses and were working fine - the rest couldn't get an IP address or do anything. There was no rhyme or reason to it. The computers that were working were plugged into different switches. We banged our heads against the wall trying to figure it out, and eventually we just put everything back on the native VLAN and it was fine. What on earth were we missing??