<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: VTP server question in Switching</title>
    <link>https://community.cisco.com/t5/switching/vtp-server-question/m-p/3880957#M468285</link>
    <description>&lt;P&gt;Hello Vincent,&lt;/P&gt;
&lt;P&gt;the answer is yes in VTP version 1 and 2 if the one VTP server makes a change and increase the revision number all switches in VTP domain will follow both clients and other VTP servers.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In VTP version 3, there is the concept of primary server and only the primary is allowed to make changes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Actually in VTP version 2 even a VTP client with an higher revision number can update the whole Vlan database!!!&lt;/P&gt;
&lt;P&gt;This is why when connecting a new switch is better to power on it isolated and to make its revision number to become zero by changing VTP domain name and or setting to VTP mode transparent and then back to VTP mode client.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope to help&lt;/P&gt;
&lt;P&gt;Giuseppe&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jun 2019 17:16:24 GMT</pubDate>
    <dc:creator>Giuseppe Larosa</dc:creator>
    <dc:date>2019-06-27T17:16:24Z</dc:date>
    <item>
      <title>VTP server question</title>
      <link>https://community.cisco.com/t5/switching/vtp-server-question/m-p/3880951#M468284</link>
      <description>&lt;P&gt;In regards to vtp server mode, does one switch in server mode update another switch in server mode?&amp;nbsp; the material states that you can create, add, or delete in this mode, but I am not finding about updates.&amp;nbsp; I am curious if I had more than one switch in server mode.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2019 17:06:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/vtp-server-question/m-p/3880951#M468284</guid>
      <dc:creator>vincentgruber8</dc:creator>
      <dc:date>2019-06-27T17:06:33Z</dc:date>
    </item>
    <item>
      <title>Re: VTP server question</title>
      <link>https://community.cisco.com/t5/switching/vtp-server-question/m-p/3880957#M468285</link>
      <description>&lt;P&gt;Hello Vincent,&lt;/P&gt;
&lt;P&gt;the answer is yes in VTP version 1 and 2 if the one VTP server makes a change and increase the revision number all switches in VTP domain will follow both clients and other VTP servers.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In VTP version 3, there is the concept of primary server and only the primary is allowed to make changes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Actually in VTP version 2 even a VTP client with an higher revision number can update the whole Vlan database!!!&lt;/P&gt;
&lt;P&gt;This is why when connecting a new switch is better to power on it isolated and to make its revision number to become zero by changing VTP domain name and or setting to VTP mode transparent and then back to VTP mode client.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope to help&lt;/P&gt;
&lt;P&gt;Giuseppe&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2019 17:16:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/vtp-server-question/m-p/3880957#M468285</guid>
      <dc:creator>Giuseppe Larosa</dc:creator>
      <dc:date>2019-06-27T17:16:24Z</dc:date>
    </item>
    <item>
      <title>Re: VTP server question</title>
      <link>https://community.cisco.com/t5/switching/vtp-server-question/m-p/3880968#M468286</link>
      <description>&lt;BR /&gt;see&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/37e/consolidated_guide/b_37e_consolidated_3850_cg/b_37e_consolidated_3850_cg_chapter_01100111.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/37e/consolidated_guide/b_37e_consolidated_3850_cg/b_37e_consolidated_3850_cg_chapter_01100111.html&lt;/A&gt;</description>
      <pubDate>Thu, 27 Jun 2019 17:40:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/vtp-server-question/m-p/3880968#M468286</guid>
      <dc:creator>Martin L</dc:creator>
      <dc:date>2019-06-27T17:40:14Z</dc:date>
    </item>
    <item>
      <title>Re: VTP server question</title>
      <link>https://community.cisco.com/t5/switching/vtp-server-question/m-p/3881482#M468335</link>
      <description>"Actually in VTP version 2 even a VTP client with an higher revision number can update the whole Vlan database!!!"&lt;BR /&gt;&lt;BR /&gt;I thought that's also true for version 1.(?)</description>
      <pubDate>Fri, 28 Jun 2019 13:37:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/vtp-server-question/m-p/3881482#M468335</guid>
      <dc:creator>Joseph W. Doherty</dc:creator>
      <dc:date>2019-06-28T13:37:54Z</dc:date>
    </item>
    <item>
      <title>Re: VTP server question</title>
      <link>https://community.cisco.com/t5/switching/vtp-server-question/m-p/3881487#M468338</link>
      <description>&lt;P&gt;Hello Joseph,&lt;/P&gt;
&lt;P&gt;&amp;gt;&amp;gt;&lt;/P&gt;
&lt;P&gt;"Actually in VTP version 2 even a VTP client with an higher revision number can update the whole Vlan database!!!"&lt;/P&gt;
&lt;P&gt;I thought that's also true for version 1.(?)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes it is of course true also for VTP version 1. Thanks for your correction.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;
&lt;P&gt;Giuseppe&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jun 2019 13:44:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/vtp-server-question/m-p/3881487#M468338</guid>
      <dc:creator>Giuseppe Larosa</dc:creator>
      <dc:date>2019-06-28T13:44:46Z</dc:date>
    </item>
  </channel>
</rss>

