Application Examples 2
Making VLAN Connections
VLANs can be based on port groups, or each data frame can be explicitly tagged to identify the VLAN group to which it belongs. When using port-based VLANs, ports can either be assigned to one specific group or to all groups. Port-based VLANs are suitable for small networks. A single switch can be easily configured to support several VLAN groups for various organizational entities (such as Finance and Marketing).
When you expand port-based VLANs across several switches, you need to make a separate connection for each VLAN group. This approach is, however, inconsistent with the Spanning Tree Protocol, which can easily segregate ports that belong to the same VLAN. When VLANs cross separate switches, you need to use VLAN tagging. This allows you to assign multiple VLAN groups to the “trunk” ports (that is, tagged ports) connecting different switches.
| OmniStack |
| 6300-24 |
1000=Green 10/100=Yellow | |
Link/ | Power |
Act | Console |
FDX | Diag |
Link/ | BPS |
Act |
FDX | |
Untagged Ports | Tagged Port |
Finance
VLAN 2
Testing
VLAN 3
VLAN 4
| VLAN |
VLAN | aware |
unaware | switch |
switch | |
| R&D |
Marketing
Finance
Testing
VLAN 2 
VLAN 3
Figure 2-4. Making VLAN Connections
Note: When connecting to a switch that does not support IEEE 802.1Q VLAN tags, use untagged ports.
