Currently you cannot stop VTP information on a trunk port. That information goes out on VLAN 1, which is one of the default VLANs ineligible for pruning.
When you have a trunk connection between two VTP domains, the border switches in each domain just ignore VTP announcements from the other domain. So if you have a trunk port that's showing a VTP domain mismatch, that's just the switch's way of telling you it's a border switch.
If you want to make sure no one can connect to your border switch and make changes to VLANs in one of the domains, you can associate a password with the domain. Then if announcements in the same domain don't share the same password the information gets dropped.
If you want to completely eliminate the mismatch on the connection between VTP domains, the only way I can think of is to make that link a non-trunking Layer 3 connection instead.
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...