Differences

This shows you the differences between two versions of the page.

--- icnd1:trunking_and_vlans [2024/04/28 11:27]
114.119.138.183 old revision restored (2023/11/14 10:52)
+++ icnd1:trunking_and_vlans [2024/05/14 11:56] (current)
114.119.137.174 old revision restored (2023/12/01 02:20)
@@ Line 1: / Line 1: @@
 ====== Trunking and VLANs ======
-VLANs create separate broadcast domains and isolates traffic to it's own VLAN. Switches will not forward traffic out ports that aren't in their VLAN. Basically, traffic from VLAN 10 cannot reach VLAN 20. Makes grouping traffic pretty easy. For example you may group ACCOUNTING and IT machines into different VLANs.
+VLANs create separate broadcast domains and isolates traffic to it's own VLAN. Switches will not forward traffic out ports that aren't in their VLAN. Basically, traffic from VLAN 10 cannot reach VLAN 20.
-Trunking is the act of carrying data from multiple VLANs over a medium. So a trunk port is a port capable of carrying traffic from specified/any VLANs. This is useful if in a multi-switch environment or inter-vlan routing.
+Trunking carries data from multiple VLANs over a medium. So a trunk port is a port capable of carrying traffic from specified/any VLANs. This is useful if in a multi-switch environment or inter-vlan routing / RoAS w/out a Layer3 Switch.
+===== Notes =====
+ISL is largely unsupported
+.1Q is the IEEE standard and most used. Frames are tagged with a VLAN ID field
+<code>switchport trunk encapsulation isl|dot1q</code>
 ===== Configuration =====

Abrer_Wiki