05-06-2022 10:37 PM
Lets say there 2 switches which trunking b/w them. Each switch has 5 devices connected. My question is Can multiple ports can be configured for the same vlan ? I have attached a pic for an example. Sorry for bad drawing
Solved! Go to Solution.
05-06-2022 10:42 PM
05-06-2022 11:34 PM - edited 05-06-2022 11:36 PM
Hi,
Attaches some information about access and also trunk port, about the difference between them, a little about packet flow and also how to configure.
When an interface expects frames with VLAN tags, it is referred to as a ‘tagged port’ or “trunk” port in Cisco terminology - Tagged ports or Trunk ports connect two switches to pass multiple VLAN tags on a single port.
In Short – A switch port that carries multiple VLANs is known as a Trunk port by Cisco and VLANs Tagged ports by other vendors.
So to summarize VLAN tagging vs. Untagging, the terms “Access port” and “Trunk port” are frequently used in the context of the Cisco network.
And other Vendors call it Untagged (Access port) and Tagged (Trunk Port) ports simultaneously.
example 1:
example 2:
.
Ports 1 on both switches (layer2 switch-1, layer2 switch-2) are Untagged port or Access ports.
Sample config
Ports 2 on both switches (layer2 switch-1, layer2 switch-2) are Tagged port or Trunk ports.
Sample config
05-07-2022 12:36 AM
Hello
@mrigankm20 wrote:
Lets say there 2 switches which trunking b/w them. Each switch has 5 devices connected. My question is Can multiple ports can be configured for the same vlan ? I have attached a pic for an example. Sorry for bad drawing
Yes they can
The interconnect between both switch's configure it as a trunk, Then create vlan3 and assign that vlan to the access-ports
Sw1 & Sw2
int x/x
description Link to switch
switchport mode trunk
no shut
Vlan 3
exit
int x/x
description vlan 3 access ports
switchport host
switchport access vlan 3
no shut
05-06-2022 10:42 PM
In the simplest of terms, yes.
By default, all ports are on VLAN 1.
05-06-2022 11:34 PM - edited 05-06-2022 11:36 PM
Hi,
Attaches some information about access and also trunk port, about the difference between them, a little about packet flow and also how to configure.
When an interface expects frames with VLAN tags, it is referred to as a ‘tagged port’ or “trunk” port in Cisco terminology - Tagged ports or Trunk ports connect two switches to pass multiple VLAN tags on a single port.
In Short – A switch port that carries multiple VLANs is known as a Trunk port by Cisco and VLANs Tagged ports by other vendors.
So to summarize VLAN tagging vs. Untagging, the terms “Access port” and “Trunk port” are frequently used in the context of the Cisco network.
And other Vendors call it Untagged (Access port) and Tagged (Trunk Port) ports simultaneously.
example 1:
example 2:
.
Ports 1 on both switches (layer2 switch-1, layer2 switch-2) are Untagged port or Access ports.
Sample config
Ports 2 on both switches (layer2 switch-1, layer2 switch-2) are Tagged port or Trunk ports.
Sample config
05-07-2022 12:36 AM
Hello
@mrigankm20 wrote:
Lets say there 2 switches which trunking b/w them. Each switch has 5 devices connected. My question is Can multiple ports can be configured for the same vlan ? I have attached a pic for an example. Sorry for bad drawing
Yes they can
The interconnect between both switch's configure it as a trunk, Then create vlan3 and assign that vlan to the access-ports
Sw1 & Sw2
int x/x
description Link to switch
switchport mode trunk
no shut
Vlan 3
exit
int x/x
description vlan 3 access ports
switchport host
switchport access vlan 3
no shut
05-07-2022 10:54 AM
As @Leo Laohoo the answer to your question is (usually) "yes". (This also assumes the switches support VLANs.)
One (and the usual) way it might be done, on Cisco switches, is provided by @paul driver and @pman.
Notice in my first sentence I use the term "usually". This because there are a bunch of configurations that need to be set, or if (optionally) set incorrectly, or not supported, might preclude you being able to do this.
For one example, the ".Q" standard defines how frames should be structured to contain tags. Pretty much, any vendor, supporting trunks (also known by other terms in non-Cisco equipment) uses this standard. But, decades ago, Cisco was first (I believe) to the market creating trunking using their own proprietary standard, ISL. That standard and .Q don't work together. Cisco was "slow" to support .Q as it really was most useful for connecting to non-Cisco equipment, which they (Cisco) wasn't interesting much in doing. (NB: generally a non-issue this century, but a case example of a possible issue.)
For another example, even today, Cisco trunks support a "native" (i.e. untagged) VLAN on a trunk with other tagged VLANs. I believe, technically, .Q doesn't expect this, and so, this is an example, you can run into issues (still) between Cisco and non-Cisco switches.
BTW, it's also possible (but generally almost never done) to have VLAN x be VLAN y on another switch.
Again, the simple, and usual answer, to your question is "yes". The forging, though, might show this "yes" might actually be the infamous "it depends" answer.
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