Could you help me understand your question? Generally speaking, physical ports are trunked, not VLANs. Regarding your question about VLANs, the communication will be based on the matched configuration.
If it's originating from VLAN 1 untagged on the core, it will be sent to the untagged VLAN of the connected switch(would be 1 by default if set in trunk mode).
Assuming that both switches are set in trunk mode on the ports connecting them, and you have a traffic originating from VLAN 5 on the core it will be sent out tagged if using the port connecting the 2 switches and received as tagged VLAN 5 on the connected switch (just using VLAN 5 as an example).
I guess my confusion is where the trunk is forwarding all Vlan traffic to an access port which only accepts a single Vlan. Does the trunk port "encapsulate"(for lack of a better word) the the forwarded packets and the access port simply see them as from Vlan1?
By default the trunk ports should carry all VLANs, so it should send the traffic to the right place, however it can be set so that the trunk port only carries specific VLANs, and if it is not in the list it will drop the traffic. Another possibility may be in configuration expectation. I say this because our switches don't have a default allow policy for VLANs (I think Cisco does, if I'm not mistaken). You would need to allow them with ACL configuration for your other ports.
If that's no helpful, you're also welcome to share the running configuration. That may help clarify specifics.
I may have figured this out, hopefully. The access ports on the core switches are set as part of a LAG and that LAG is set to trunk. Can you tell me what the expected behavior is here? If a port is set to "Access", but is a member of a LAG and that LAG is set to trunk, will the port in effect be a trunk?
Dell-DylanJ
4 Operator
•
2.9K Posts
0
December 29th, 2020 07:00
Dell-DylanJ
4 Operator
•
2.9K Posts
0
December 18th, 2020 15:00
Hello,
Could you help me understand your question? Generally speaking, physical ports are trunked, not VLANs. Regarding your question about VLANs, the communication will be based on the matched configuration.
If it's originating from VLAN 1 untagged on the core, it will be sent to the untagged VLAN of the connected switch(would be 1 by default if set in trunk mode).
Assuming that both switches are set in trunk mode on the ports connecting them, and you have a traffic originating from VLAN 5 on the core it will be sent out tagged if using the port connecting the 2 switches and received as tagged VLAN 5 on the connected switch (just using VLAN 5 as an example).
Please let me know if this helps.
djhurt1
1 Rookie
•
26 Posts
0
December 22nd, 2020 07:00
I guess my confusion is where the trunk is forwarding all Vlan traffic to an access port which only accepts a single Vlan. Does the trunk port "encapsulate"(for lack of a better word) the the forwarded packets and the access port simply see them as from Vlan1?
Dell-DylanJ
4 Operator
•
2.9K Posts
0
December 22nd, 2020 14:00
PG 766 gets into VLAN tagging: https://dell.to/3hdkD8Z
djhurt1
1 Rookie
•
26 Posts
0
December 28th, 2020 13:00
I may have figured this out, hopefully. The access ports on the core switches are set as part of a LAG and that LAG is set to trunk. Can you tell me what the expected behavior is here? If a port is set to "Access", but is a member of a LAG and that LAG is set to trunk, will the port in effect be a trunk?