From: Cassidy D. Smith (csmith@plannetconsulting.com)
Date: Wed Feb 05 2003 - 03:57:55 GMT-3
I am not sure if this will help you, however you may give it a shot. There
seems to be some "flaky" vlan behavior when you leave the ports in "auto"
mode for determining if they should be trunk or access ports. See if
locking down the ports help you. Use the interface commands: SWITCHPORT MODE
ACCESS or SWITCHPORT MODE TRUNK and see if that helps you. I was having
similar problems, there seemed to be some correlation between router
interfaces that were configured for bridging (DLSW config), I suspect the
presence of BPDU's may be partly the trigger for the ports to "block".
However when I looked for blocked ports I could not find any evidence of
any. So locking the port down and see if it resolves your problem like it
did for my 3550-24.
Casey
P.S. Please let us know if this helped you.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Ted McDermott
Sent: Tuesday, February 04, 2003 7:47 PM
To: ccielab@groupstudy.com
Subject: Mystery: Certain VLAN Numbers Work on Cat 3550
All,
I connect two Caat 3550-12G's running
c3550-i5q3l2-mz.121-9.EA1c.bin IOS.
I defined respective physical GigE ports of each
Cat3550 with "switchport access VLAN 612" and then
with a definition for interface VLAN612 with an IP
address.
I cannot figure out why the ports won't go active with
certain VLAN numbers (like 612, 611 or 620), but will
with others (614, 615, 616), even though I can't find
the "bad" VLAN numbers defined anywhere else in the
entire network.
Any ideas, folks, would be greatly appreciated.
Thanks,
Ted
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:10 GMT-3