Here's my attempt, based on becs's example and my own working setup:My setup on the netgear is (using 802.1Q screens):
ports 1-4,sfp1,sfp2, VLAN=1, untagged, pvid=1
ports 5-8, VLAN=10, untagged, pvid=10
ports 9,10, VLAN=10, 400,401,402,403,404, tagged, pvid=10 (trunk ports)
ports 11-14, VLAN=5, untagged, pvid=5
ports 15,16, VLAN=5, tagged, pvid=5
Any pointers on how to replicate this on SwOS 2.0? FYI, this is someone elses design, so I can't answer why things are the way they are, only that it works on the netgear.
In SwOS v2.0 on CSS326 VLAN Mode "enabled" works as the VLAN Mode "strict" on RB260 (CSS106), the membership of the ingress port is important, too.Does the "enabled" VLAN mode in 2.x check to see that the port is a member of the VLAN like the "strict" mode in 1.x, or just that the VLAN is configured on the switch like the "enabled" mode in 1.x?
Yes, your assumption is correct.Since there is not an option in 2.x to specify whether to leave as-is, strip, or add VLAN headers to egressing packets, do packets always egress untagged on a port where the default VLAN ID of the port matches that of the packet, and tagged if the default VLAN ID does not match?
"Port Isolation" checkbox in the VLANs tab specifies whether configuration from Port Isolation menu applies to the particular VLAN.What does the "port isolation" checkbox on the VLANs tab do?
also cannot get management over tagged vlan working. any new docs on it? cmon, many months passed...simple question,
management vlan on a trunk port
i want to use the sfp+ port to send vlan 5,9,11,33,23,43 where management vlan will be 43.
how do i go about setting it up on the switch?
Thanks becs. Turns out that shortly after I posted the question I had remoted into a computer at home and confirmed that I could access the CSS326 remotely via the microwave link trunk. Nice to get the confirmation however.Hello, CSS326 management VLAN with tagged packets worked before and the problems with untagged packets are fixed since SwOS v2.3:What's new in v2.3:
*) fixed "Allow From VLAN" on untagged packets with correct default vlan id;
It seemes that this is wrong, or this is not working correctly. I just have CSS326 and following setup:In SwOS v2.0 on CSS326 VLAN Mode "enabled" works as the VLAN Mode "strict" on RB260 (CSS106), the membership of the ingress port is important, too.
We will consider renaming it to "strict" on CSS326 for better understanding.