01-06-2019 07:30 PM - edited 03-08-2019 04:57 PM
How to configure trunk mode on both switch ports?
what is difference between 802.1Q with trunk ?
Solved! Go to Solution.
01-06-2019 07:57 PM
Hi @eduangelo,
Check what I found on this link:
https://www.cisco.com/c/en/us/support/docs/lan-switching/8021q/17056-741-4.html
Trunks are used to carry traffic that belongs to multiple VLANs between devices over the same link. A device can determine which VLAN the traffic belongs to by its VLAN identifier. The VLAN identifier is a tag that is encapsulated with the data. ISL and 802.1Q are two types of encapsulation that are used to carry data from multiple VLANs over trunk links
...
802.1Q is the IEEE standard for tagging frames on a trunk and supports up to 4096 VLANs. In 802.1Q, the trunking device inserts a 4-byte tag into the original frame and recomputes the frame check sequence (FCS) before the device sends the frame over the trunk link. At the receiving end, the tag is removed and the frame is forwarded to the assigned VLAN. 802.1Q does not tag frames on the native VLAN. It tags all other frames that are transmitted and received on the trunk. When you configure an 802.1Q trunk, you must make sure that you configure the same native VLAN on both sides of the trunk. IEEE 802.1Q defines a single instance of spanning tree that runs on the native VLAN for all the VLANs in the network. This is called Mono Spanning Tree (MST). This lacks the flexibility and load balancing capability of PVST that is available with ISL. However, PVST+ offers the capability to retain multiple spanning tree topologies with 802.1Q trunking.
Regards
01-06-2019 08:12 PM
simply put, with the use of a trunk, you can stretch the same VLANs across multiple physical switches, using a single physical port on both ends. without a trunk you create an access port that can only carry 1 VLAN across between switches.
01-06-2019 08:49 PM
01-07-2019 08:22 AM
01-06-2019 07:57 PM
Hi @eduangelo,
Check what I found on this link:
https://www.cisco.com/c/en/us/support/docs/lan-switching/8021q/17056-741-4.html
Trunks are used to carry traffic that belongs to multiple VLANs between devices over the same link. A device can determine which VLAN the traffic belongs to by its VLAN identifier. The VLAN identifier is a tag that is encapsulated with the data. ISL and 802.1Q are two types of encapsulation that are used to carry data from multiple VLANs over trunk links
...
802.1Q is the IEEE standard for tagging frames on a trunk and supports up to 4096 VLANs. In 802.1Q, the trunking device inserts a 4-byte tag into the original frame and recomputes the frame check sequence (FCS) before the device sends the frame over the trunk link. At the receiving end, the tag is removed and the frame is forwarded to the assigned VLAN. 802.1Q does not tag frames on the native VLAN. It tags all other frames that are transmitted and received on the trunk. When you configure an 802.1Q trunk, you must make sure that you configure the same native VLAN on both sides of the trunk. IEEE 802.1Q defines a single instance of spanning tree that runs on the native VLAN for all the VLANs in the network. This is called Mono Spanning Tree (MST). This lacks the flexibility and load balancing capability of PVST that is available with ISL. However, PVST+ offers the capability to retain multiple spanning tree topologies with 802.1Q trunking.
Regards
01-06-2019 08:12 PM
simply put, with the use of a trunk, you can stretch the same VLANs across multiple physical switches, using a single physical port on both ends. without a trunk you create an access port that can only carry 1 VLAN across between switches.
01-06-2019 08:49 PM
Hi,
ISL and 802.1q is a technology used to form trunk port.
01-07-2019 02:45 AM
01-06-2019 08:50 PM
Hi,
ISL and 802.1 q is a technology used to form trunk port.
01-07-2019 02:43 AM
01-07-2019 08:22 AM
01-07-2019 09:20 AM
Is there a reason you would want to? You need to set up the "encapsulation" command when setting up a trunk and this can be either ISL or 802.1q. This lets a switch know which protocol to use when setting up the trunk.
A trunk can't simpy be "a trunk" as it were, you need a underlying protocol to acheieve this.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide