{"id":317,"date":"2010-01-12T20:46:59","date_gmt":"2010-01-12T20:46:59","guid":{"rendered":"http:\/\/mccltd.net\/blog\/?p=317"},"modified":"2010-01-12T21:17:59","modified_gmt":"2010-01-12T21:17:59","slug":"vtp-version-3","status":"publish","type":"post","link":"http:\/\/darenmatthews.com\/blog\/?p=317","title":{"rendered":"VTP Version 3"},"content":{"rendered":"<p class=\"pB1_Body1\">An aide-memoir, cum cliff-notes:<\/p>\n<p class=\"pB1_Body1\">VTP version 3 differs from earlier VTP versions in that it does not directly handle VLANs. VTP version 3 is a protocol that is only responsible for distributing a list of opaque databases (somewhat like like LDAP!) over an administrative domain. When enabled, VTP version 3 provides these enhancements to previous VTP versions:<!--more--><\/p>\n<p class=\"pBu1_Bullet1\">\u2022<img loading=\"lazy\" src=\"http:\/\/www.cisco.com\/en\/US\/i\/templates\/blank.gif\" border=\"0\" alt=\"\" width=\"19\" height=\"2\" \/>Support for extended VLANs.<\/p>\n<p class=\"pBu1_Bullet1\">\u2022<img loading=\"lazy\" src=\"http:\/\/www.cisco.com\/en\/US\/i\/templates\/blank.gif\" border=\"0\" alt=\"\" width=\"19\" height=\"2\" \/>Support for the creation and advertising of private VLANs. (NICE!!)<\/p>\n<p class=\"pBu1_Bullet1\">\u2022<img loading=\"lazy\" src=\"http:\/\/www.cisco.com\/en\/US\/i\/templates\/blank.gif\" border=\"0\" alt=\"\" width=\"19\" height=\"2\" \/>Support for VLAN instances and MST mapping propagation instances. (good &#8211; I like MST very much)<\/p>\n<p class=\"pBu1_Bullet1\">\u2022<img loading=\"lazy\" src=\"http:\/\/www.cisco.com\/en\/US\/i\/templates\/blank.gif\" border=\"0\" alt=\"\" width=\"19\" height=\"2\" \/>Improved server authentication. (MD5)<\/p>\n<p class=\"pBu1_Bullet1\">\u2022<img loading=\"lazy\" src=\"http:\/\/www.cisco.com\/en\/US\/i\/templates\/blank.gif\" border=\"0\" alt=\"\" width=\"19\" height=\"2\" \/>Protection from the &#8220;wrong&#8221; database accidentally being inserted into a VTP domain. (a major shortcoming of previous versions)<\/p>\n<p class=\"pBu1_Bullet1\">\u2022<img loading=\"lazy\" src=\"http:\/\/www.cisco.com\/en\/US\/i\/templates\/blank.gif\" border=\"0\" alt=\"\" width=\"19\" height=\"2\" \/>Interaction with VTP version 1 and VTP version 2. (as one would hope \/ expect)<\/p>\n<p class=\"pBu1_Bullet1\">\u2022<img loading=\"lazy\" src=\"http:\/\/www.cisco.com\/en\/US\/i\/templates\/blank.gif\" border=\"0\" alt=\"\" width=\"19\" height=\"2\" \/>Ability to be configured on a per-port basis.\u00a0 ( I guess this helps the previously mention backward-compatability with V1 and 2).\u00a0 I&#8217;d like to test this &#8211; just to see it in action and do some debugging \/ packet sniffing. When I do, I&#8217;ll post a wireshark capture on this blog.<\/p>\n<p class=\"pBu1_Bullet1\"><span class=\"content\"><\/p>\n<h3 class=\"p_H_Head3\">Limitations of Version 3:<\/h3>\n<p><a name=\"wp1042136\"><\/a><\/p>\n<p class=\"pB1_Body1\">The limitations of VTP version 3 are as follows:<\/p>\n<p><a name=\"wp1042137\"><\/a><\/p>\n<p class=\"pBu1_Bullet1\">\u2022<img loading=\"lazy\" src=\"http:\/\/www.cisco.com\/en\/US\/i\/templates\/blank.gif\" border=\"0\" alt=\"\" width=\"19\" height=\"2\" \/>Two VTP version 3 regions can communicate only over a VTP version 1 and VTP version 2 region in transparent mode.<\/p>\n<p><a name=\"wp1045003\"><\/a><\/p>\n<p class=\"pBu1_Bullet1\">\u2022<img loading=\"lazy\" src=\"http:\/\/www.cisco.com\/en\/US\/i\/templates\/blank.gif\" border=\"0\" alt=\"\" width=\"19\" height=\"2\" \/>Leaving a server in a VTP version 2 region so that it will receive its VTP information from a VTP version\u00a03 region could cause a problem. If a configuration change occurs in the VTP version 1 and VTP version 2 region, the revision of the database may become higher than the one that is generated by the VTP version 3 region, and the updates from the VTP version 3 region may be ignored.<\/p>\n<p><\/span><\/p>\n<p class=\"pBu1_Bullet1\"><a rel=\"attachment wp-att-324\" href=\"http:\/\/darenmatthews.com\/blog\/?attachment_id=324\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-324\" title=\"vtp v3\" src=\"http:\/\/darenmatthews.com\/blog\/wp-content\/uploads\/2010\/01\/vtp-v31.jpg\" alt=\"vtp v3\" width=\"548\" height=\"233\" srcset=\"http:\/\/darenmatthews.com\/blog\/wp-content\/uploads\/2010\/01\/vtp-v31.jpg 548w, http:\/\/darenmatthews.com\/blog\/wp-content\/uploads\/2010\/01\/vtp-v31-300x127.jpg 300w\" sizes=\"(max-width: 548px) 100vw, 548px\" \/><\/a><\/p>\n<p class=\"pBu1_Bullet1\">\n<div id=\"_mcePaste\" style=\"overflow: hidden; position: absolute; left: -10000px; top: 294px; width: 1px; height: 1px;\">Long story short:\u00a0 Some time ago,\u00a0 when I first became aware of version 3,\u00a0 I looked it up on cisco.com, liked it and made a mental note to add this to my lab notes and do some testing.<\/div>\n","protected":false},"excerpt":{"rendered":"<p>An aide-memoir, cum cliff-notes: VTP version 3 differs from earlier VTP versions in that it does not directly handle VLANs. VTP version 3 is a protocol that is only responsible for distributing a list of opaque databases (somewhat like like LDAP!) over an administrative domain. When enabled, VTP version 3 provides these enhancements to previous [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[83],"tags":[],"_links":{"self":[{"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/317"}],"collection":[{"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=317"}],"version-history":[{"count":15,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/317\/revisions"}],"predecessor-version":[{"id":334,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/317\/revisions\/334"}],"wp:attachment":[{"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=317"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=317"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=317"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}