You must add the lag to the vlan as a single unit.
Unmanaged switch vlan tags.
Can afford to get a 30 switch that can understand vlans.
The sender will send a frame with a vlan tag.
Some switches will drop the frames as garbled some switches will pass them on as they are and some switches will strip the vlan tags.
Here you can see this process in action.
In this case the switch will flood the frame to all other ports configured with vlan 10.
Here are two configuration examples for 802 1q vlan.
For more information see what is a management vlan.
The receiving switch will see the vlan tag and if the vlan is allowed it will forward the frame as required.
You have two options either connect the ap directly to the 3560 or buy a managed switch as said.
So what would happen if one put it in on a trunk.
What happens is when a trunk is confgured a header aka tag which varies in size depending on what encapsulation is used is added to the front of the a frame by doing this the destination knows which vlan it belongs when it arrives.
Simply put the unmanaged switch would not be able to know what vlans it would or would not send over the link that might or might not be a trunk.
A lan can be divided into several vlans logically and only the hosts in a same vlan can communicate with each other.
Well in my mind either the native vlan.
As the following figure shows the switch connects to two different groups.
What an unmanaged switch that doesn t understand vlan tags will do with frames which have vlan tags a trunk link is really undefined.
For example a broadcast may be received on vlan 10.
Vlan virtual local area network is a technology that can solve broadcasting issues.
Vlan 1 is also the management vlan on switches that support management vlans.
Running tags over a dumb switch just amounts to running multiple layer 3 on the layer 2 there is zero lack of.
Neither will it have knowledge of what vlan is the native the only one on the trunk that is not tagged vlan.