VLANs on a 3COM Superstack III

[Guest]

Archived from groups: comp.dcom.lans.ethernet (More info?)

I recently had some issues where 2 of my 3300 switches in one of my
stacks went bad. I'll refer to that as Stack 6; and I have Stacks 1 -
7 connected through Fiber to a Corebuilder 9000.

I replaced both of the bad switches on Stack 6 and everything seems to
be working properly, with one exception. My defined VLANs don't seem
to work anymore, at least not beyond the stack 6. I have defined a
VLAN that several Ports are connected to. The users whose machines
are in that VLAN and are connected to stack 6 can see each other.
However, they can't see anything outside the VLAN, or anything within
the VLAN that is not directly attached to stack 6, ie other machines
in the VLAN but connected through a different stack.

Can anyone give me any advice at where to look now?

 

[Guest]

Archived from groups: comp.dcom.lans.ethernet (More info?)

In article <a1744e2.0407210828.75d95cd6@posting.google.com>,
graybin@atsva.com (GRaybin) writes:
>I recently had some issues where 2 of my 3300 switches in one of my
>stacks went bad. I'll refer to that as Stack 6; and I have Stacks 1 -
>7 connected through Fiber to a Corebuilder 9000.
>
>I replaced both of the bad switches on Stack 6 and everything seems to
>be working properly, with one exception. My defined VLANs don't seem
>to work anymore, at least not beyond the stack 6. I have defined a
>VLAN that several Ports are connected to. The users whose machines
>are in that VLAN and are connected to stack 6 can see each other.
>However, they can't see anything outside the VLAN, or anything within
>the VLAN that is not directly attached to stack 6, ie other machines
>in the VLAN but connected through a different stack.
>
>Can anyone give me any advice at where to look now?

It is very easy to mess up VLAN tagging on a Superstack. It is
possible to define a port to be a tagged an untagged VLAN member
at the same time. So you should go and check thoroughly the
trunk ports for consistency (e.g. "b p det 25").
BTW it is the VLAN ID that is important, not the Local ID.

--
Manfred Kwiatkowski kwiatkowski@zrz.tu-berlin.de