I don't think that technically there is a difference.
Ethernet LAN switches use Transparent Bridging to create the address lookup tables. Transparent bridging technology allows a switch to learn everything that the switch needs to know about the location of nodes on the network without the need for the network administrator to do anything. Transparent bridging has five parts (Learning, flooding, filtering, forwarding and aging).
Initially when the switch gets the first frame of data from a node connected to a switch port. The switch reads the source MAC address and saves the address to the lookup table for this port. (Any future frames destined to this MAC are sent out this port)
Since the switch initially does not know where other nodes reside (the MAC table is not completed yet), the switch sends the frames to all the segments (switch ports). But the switch does not send the frames to the segment (switch port) on which the frames arrived.
The switch ignores frames that travel between nodes on the same segment (switch port). Same segment doesn?t need switching.
After building the full MAC table, the switch by then knows the addresses of all nodes on all segments; the switch sends the frame directly to the specified node on the corresponding switch port according to the MAC table. In case that the nodes are on a different segments (switch ports), the switch must connect the two segments to send the frames.
The switch has a user-configurable timer that erases the MAC entry after a certain length of time of no activity from that node. The erasure frees up valuable memory resources for other entries.
Cisco switches (Only Cisco switches and not the routers ? routers' Ethernet interfaces need to be manually configured to act as Trunks) use the Dynamic Trunk Protocol (DTP) to dynamically learn whether the device on the other end of the cable wants to perform Trunking and, if so, which Trunking protocol to use.
DTP learns whether to trunk based on the DTP mode defined for an interface, Dynamic Trunking Protocol (DTP) manages trunk autonegotiation on LAN ports. DTP supports autonegotiation of both ISL and 802.1Q trunks as follows:
Auto - Create the trunk based on the neighbor request (as the neighbor wishes)
Desirable - Tell the neighbor that it prefers being trunk (i like to trunk) - default
On - Tell the neighbor Trunk regardless the neighbor (forces a trunk and tells the neighbor)
Nonegotiate - Trunk regardless the neighbor (DTP disabled / the neighbor must be configured as ON)
Off - Trunk is not allowed regardless the neighbor (trunk not allowed at all)
ON mode puts the interface into permanent trunking mode and negotiates to convert the neighboring link into a trunk link - The interface becomes a trunk interface if the neighboring interface is set to ON, Auto, Desirable or nonegotiate.
Auto - The interface becomes a trunk interface if the neighboring interface is set to trunk(ON) or desirable mode.
Desirable - The interface becomes a trunk interface if the neighboring interface is set to trunk(ON), desirable, or auto
nonegotiate - Prevents the interface from generating DTP frames. You can use this command only when the interface switchport mode is access or trunk. You must manually configure the neighboring interface as a trunk interface to establish a trunk link.
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...