Accordingly, it can forward it to that particular VLAN. The reason why the frames are tagged before they traverse the trunk is that when it goes to the other side of the trunk, the switch can read that tag and can determine which VLAN the frame belongs to. There is only one native VLAN per trunk and this must match on both the ends of the trunk which are responsible for all the traffic which is untagged. We can use the ping command to see the same. Trunks carry only tagged frames and the purpose is to transfer data from the different VLANs. If a switch receives any specific frame without tag is going to assume that it’s a native VLAN. As for trunk port traffic must be the tagged one and switch use this VLAN information to decide which VLAN it will associate it. So simply when untagged traffic is received by the access port, a switch will associate that traffic from that port with VLAN associated with that port.
Since endpoints don’t understand the concept of VLAN, switch expects to receive untagged traffic on an access port while truck ports supposed to receive the tagged frames. Switch assumes that it belongs to native VLAN and by default, it will send it to native VLAN.Īs we all know the switch has 2 types of ports one is trunk port and the other one is Access port. But there are some cases where we may receive frames without any tag, especially if we are receiving it via HUB as they don’t understand the concept of tagging. So that they can only forward out of the ports. This is to ensure that switch2 should understand that this frame belongs to which VLAN. There is specific traffic coming to switch1 (let’s say 10), so before it sends to the trunk link it will add a tag (frame tagging processing).
Cisco asav change native vlan port software#
Web development, programming languages, Software testing & others Start Your Free Software Development Course
0 kommentar(er)
