Both sides should be in transparent mode , just makes things easier to troubleshoot if you have a problem . In transparent mode all vlans have to manually be created on both sides of the link and the vlan database is not propagated to other switches . the only real difference between server and transparent is that on a server you can create your layer 2 vlans in a single place and all those vlans will get propagated down to all other servers and clients within the same vtp domain so you do not have to create the vlans all over . This becomes a plus if you have a large install where you have dozens of vlans within a domain .
on both sides
vtp mode transparent
to create vlans
vlan X --> do this for every vlan on both sides .
interfaces can be done in a number of ways
switchport encapsulation dot1q
switchport trunk native vlan X -->must match on both sides.
switchport mode dynamic desirable -->other end can be desirable or auto
switchport trunk allowed vlan x
Note: in place of switchport mode dynamic desirable or auto you can use "switchport mode trunk also on both sides.
It would work if you don't set any vtp name because they both use a null domain name. If you didn't set the native trunk then it defaults to vlan 1 so both sides would be vlan 1 as native vlan . As good practice only allow the vlans you actually need across the trunk , "switchport trunk allowed vlan X .
There are advantage of using a switch in a transparent mode:
i) It limits the risk of an administrator error, such as deleting a VLAN accidentally and thus impacting the entire domain
ii) There is no risk from a new switch being introduced into the network with the higher VTP revision number and overwriting the entire domain's VLAN configuration.
iii) it encourages VLANs to be pruned from trunks running to switches that do not have ports in that VLAN, thus making frame flooding more bandwidth-efficient. Manual pruning also has the benefit of reducing the spanning tree diameter.
iv) The extended VLAN range number 1006-4094 can only be configured in this way
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 customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...