Update: 802.1q vlan tagging

From: Marco Greene (mweg@sympatico.ca)
Date: Mon Feb 20 2006 - 10:56:48 EST


Hi all,

Sorry that I haven't sent an update to this yet, but I am yet to get it
working and I had some more pressing projects that I had to deal with first.

So here is a more details update and I have done more troubleshooting.

First of all, I have followed the advice of some list members to ensure that
the vlans defined on the my E420R does not have a vlan interface defined
that is the same as the native vlan on the switches involved.

The vlans that I have defined are
ce249001
ce248001
ce247001

The native vlan is 99 and it is defined so that we can manage the switch.

VLAN 249 works fine accross all of the switches from the E420R and the other
VLANs work fine if they are trying to talk to ports on the same switch. I
have also removed the VLANs allowed parameter which included vlans
99,247-249 and then the default ones CISCO tends to put in.

A little bit of network info. I have 5 3500 series CISCO switches that are
connected via trunk ports with dot1q encapsulation. 3 of the switches are
Gigabit switches and the other two are 48 port 10/100 switches with gigabit
uplinks. The last 10/100 switch in the chain is uplinked to a catalyst and
that trunk port is on native vlan 249 as the catalyst has a default route
defined for vlan 249. The other two vlans are not routable and my intention
is that my HP(Windows) based server and the E420R are the only two machines
that can talk on all three vlans.

Now for the kicker...the windows based server seems to work fine on all
three vlans.

Any suggestions, and I will summarize once I get this working.

Thanks,
Marco
mweg@sympatico.ca
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:39:01 EDT