I worked with this for 3 hours Friday, then for a couple more over the weekend and even asked an expert but the device is so new I can’t find many who are using it yet.
I am running SWOS 1.2
This is a midpoint location where we are bringing in a backhaul on port 1 and sending it further down the line on port 2, something a plain switch can do. But I also want to do this:
Feed a backhaul into port 1
Have port 2 replicate that backhaul so it can be sent on down the line.
Get VLAN 450 data out on port 5, and of course feed untagged data from back into port 5 and have it go back out port 1 &2 on VLAN 450.
Get VLAN 9 data out on port 4, and of course feed untagged data from back into port 4 and have it go back out port 1 &2 on VLAN 9.
The backhaul is, I guess, considered a trunk and currently has several VLANs running on it.
The most I can get the 250GS to do is give me either nothing or VLAN1 out port 5.
I was following another thread that was very similar and I tried what was recommended there and it did not work.
I hope that as we get more familiar we can all contribute more examples such as this!
Make sure all the vlans are defined on the VLANs tab and the ports checked in.
On the VLAN tab, I have:
All ports have VLAN “Strict”
For untagged ports under Ingress, add the default vlan id and check “Force VLAN ID”
Trunk ports have Egress “add if missing”
Untagged ports have Egress “always strip”.
On the forwarding tab, make sure the ports that can talk to each other are checked in.
Your upstream switch is trunking using dot1q and not ISL, correct?
(This is where a text based config file would come in handy)
I will give that a try today.
I agree about the text based config file.
I already ran into the issue about not being able to “clone” switches via the backup/restore. I have to do a bunch of these.
When you say the trunk does not pass transparently, are you referring to vlan tagged traffic destined for the next switch?
What traffic is not passing and how do you know?
If you have more VLANs downstream than are shown in the VLANs tab you posted, they all need to be config’d in the first switch. Just add them in the VLANs tab and check port 1 and 2 as they are trunk ports.
If some vlans end at the first switch, you can leave port 2 unchecked, obviously.
I usually put them in every switch, just to make it easy to turn a port up in the future.
The trunks won’t pass traffic for vlans they don’t know about.
Then again, if you are expecting port 2 to mirror port 1, remember, it is a switch, not a hub.
On the 493, port 1 is WAN, ports2-6 are a switch group bridged to vlan10, ports 7-8 a switch group bridged to vlan20, and ether9 is by itself with just vlan10,20,30,50 on it.
The computers on VLAN10 cant talk to each other (Even the ones plugged into the router if I have this setup plugged in. If I disabled vlan10 on the 493, the wired computers can talk again.
