How does a switch distinguish one Vlan from another if trunking is not involved ?
For Example: Switch A is connected to Switch B via a X-over cable. I place two ports at either end of the X-over cable into VLAN 2. I place one PC on switch A in VLAN 2 and one PC in switch B in VLAN 2. The result is that they can communicate. If I place one of the PC's into VLAN 1 then they cannot communicate. Is there a tagging mechanism involved here even though trunking isn't being used ?
Has anyone got an example of the frame format for Ethernet for this scenario ?
Devices connected to an access port (versus a trunk port) do not receive VLAN information.
FOr example, if you connected port 1 from switch A (which happens to be in VLAN 100) via crossover to another switch port 1 (which happens to be in VLAN 200), neither switch would know anything about the VLANs on the other switch.
Tags are added on the ingress to an access port, and stripped at the egress from an access port.
Traffic going from one port to another in the same VLAN (on the same switch) is not tagged (I believe).
If you connected an "dumb" (unmanaged) switch into a port that is associated with a VLAN on the host switch, then all of the extended ports will also appear in the VLAN of the host switch's outbound trunk.
The short version is that VLANs do not come into play for things plugged into an access port.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...