Allied Telesis AT-S39 - Manual (Page 135)

AT-S39 User’s Guide
135
Non-802.1Q
Compliant
Multiple VLANs
Non-802.1Q Multiple VLAN configuration is appropriate when the device
connected to the uplink port is non-802.1Q compatible, meaning that
the device cannot handle tagged packets.
When Non-802.1Q Multiple VLANs is selected, the AT-S39 software
configures all ports on that switch as Client VLANs except for one user-
specified port that is designated as an Uplink VLAN (also referred to as
management VLAN).
Each Client VLAN on the switch is configured as an untagged port and
the user-specified Uplink VLAN is also configured as an untagged port
that specifies all Client VLAN ports as untagged members.
Designating untagged ports in more than one VLAN at a time is what
makes this configuration non-802.1Q compliant.
Upon selecting the Non-802.1Q Multiple VLANs, you are asked to specify
the Uplink VLAN port. After specifying this port, all of the ports on the
switch are automatically configured.
For example, if your switch supports 26 ports and you selected Non-
802.1Q Multiple VLANs , you would be asked to specify the Uplink VLAN
port. If you selected 15, the VLANs would be configured as shown in the
Table 9 example. In this example, ports 1 to14 and 16 to 26 are
configured as untagged Client VLANs and port 15, the Uplink VLAN is
configured as an untagged member that includes all Client VLAN ports
as members.
Caution
The non-802.1Q-Compliant Multiple VLAN mode does not protect
the switch from VLAN leakages. If the switch receives a packet on the
uplink port containing a destination MAC address that is not in the
MAC address table, the switch will broadcast the packet out all
ports, except the uplink port. This means that all end nodes on the
switch will receive the packet.
Note
Procedures for configuring multiple VLANs can be found in
Multiple VLAN Configuration on page 156.
Table 9 Non-802.1Q Compliant Multiple VLANs Example
VLAN Name VID Untagged Port Tagged Port
Client_VLAN_1 1 1,15
Client_VLAN_2 2 2,15