I have a Force10 S25 switch in each of my two buildings. One building uses VLAN 200 to work with 10.2.0.0 /16 traffic, the other building uses VLAN 400 for 10.4.0.0 /16 traffic. Our wireless guest network in the VLAN 200 building is segmented off onto VLAN 20 on the network 172.16.20.0 /23.
I am trying to add this VLAN to the Force10 switches in order to allow VLAN 20 to pass guest network traffic from the VLAN 400 building as well, since our ISP connection is located in the VLAN 200 building.
I have been given a lot of conflicting information between tagged and untagged functions of the VLANs. Force10 told me to set all ports that are NOT trunk ports to untagged, and trunk ports to tagged. ProCurves, however, are the opposite, as well as Netgear switches. Having the ports set as untagged for the host connections and tagged for the trunk ports works, but should I switch that setup? Or is Force10 just backwards?
As far as the Guest VLAN goes, if I go to tag the host ports necessary, I get a "Tagged flag mis-matched gig 0/23" message. If I try to untag the ports, it tells me it is already untagged on another VLAN, which makes sense.
I also read that the port needs to be in hybrid mode in order to tag multiple VLANs on it. If I try to put a host port in hybrid mode, it says it can't because it is a layer 2 port. If I try to put a trunk port in hybrid mode, it says it can't because it is a layer 3 port. That leaves no port mode available to enter hybrid mode.
Is my current setup truly backwards? And if so, is it causing the issues with trying to tag multiple VLANs on a port and preventing me from entering hybrid mode on any other ports?
Best Answer
stead of using the untagged command you have to use the no tagged command.