When I try to enable it on my Cat 2924XL running IOS 12.0(5)WC5a I receive "VLAN 1003 ring number missing" and "VLAN 1005 bridge number missing" error messages.
I have read somewhere that to move from ver 1 to ver 2 it is enough just enable v2 mode on one VTP server and the rest of my network will change automatically. Is this correct? If yes, are there some trunk outages during the change process?
VTP Version 2 (V2) is not much different than VTP Version 1 (V1). The major difference is that VTP V2 introduces the support for Token Ring VLANs. If you are using Token Ring VLANs, you need to enable VTP V2. Otherwise, there is no reason to use VTP V2.
Version-Dependent Transparent ModeIn VTP version 1, a VTP transparent switch inspects VTP messages for the domain name and version and forwards a message only if the version and domain name match. Since only one domain is supported in the supervisor engine software, VTP version 2 forwards VTP messages in transparent mode, without checking the version.
This description is not clear to me:
Does the V2 transparent mode switch check the domain name or not?
And a general question:
Is the domain name match necessary for trunk to work?
I.e., when I'm having two switches each in a different VTP domain do I have to configure trunk nonegotiate? Or is it possible to use trunk negotiaition (i.e. VTP is not involved in trunk negotiation, there is just DTP used)?
When you configure a switch as VTP transparent, you must configure VLAN information manually on the switch. A VTP-transparent switch does not advertise VLAN information to other switches and will ignore VTP updates from VTP clients and servers.
VTP transparent switch DOES forward VTP updates. But there is a difference between VTP v1 and v2: In VTP v1 the domain name must match with the domain name configured on the transparent switch. VTP v2 transparent switch doesn't check the domain name.
Regarding the trunk:
If you configure nonegotiation on the trunk it works OK even while switches involved are in different VTP domains. It is also possible to have different VLAN sets on both trunk sides. If the switch receives a frame which is tagged for VLAN is doesn't know the frame is just discarded and no error message goes to syslog. You can detect this VLAN set misconfiguration via Logical Discrepancy Report in CiscoWorks.
I'm not sure if trunk works this way while trunk negotiation is enabled - I don't have two Cat4000 in my lab. But I suppose yes.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...