VTP Servers [7:39083]
If I have an existing VTP domain server with many VLANs configured and then add another VTP server does the first server update the new server? No chance of the new server updating the old server and wiping out the VTP database, right? Thanks!! Jeff Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39083&t=39083 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: VTP Servers [7:39083]
Hello, The switches use the VTP database with the highest config-revision. IE: You can be playing with a switch not attached to the network and then attach it to the network and if it's config-revision is higher it will wipe out the other switches. Changing the VTP domain makes the config-revision 0 again. So it is important to make sure the config-revision is 0 before you plug it into a live network if you don't want this switch to overwrite your VLAN databases. I don't recall offhand the 'show vtp ...' command that shows you what the current config-revision value is but it is there. Also, be aware that a VTP CLIENT can send out VTP updates and wipe out your VLAN database config. IE: A quick-fix is not to change from Server to client mode. HTH, Erick --- Jeffrey Reed wrote: > If I have an existing VTP domain server with many > VLANs configured and then > add another VTP server does the first server update > the new server? No > chance of the new server updating the old server and > wiping out the VTP > database, right? > > Thanks!! > > Jeff [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Movies - coverage of the 74th Academy Awards. http://movies.yahoo.com/ Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39085&t=39083 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: VTP Servers [7:39083]
show vtp domain or show vtp status ..i think -Original Message- From: Erick B. [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 21, 2002 3:14 PM To: [EMAIL PROTECTED] Subject: Re: VTP Servers [7:39083] Hello, The switches use the VTP database with the highest config-revision. IE: You can be playing with a switch not attached to the network and then attach it to the network and if it's config-revision is higher it will wipe out the other switches. Changing the VTP domain makes the config-revision 0 again. So it is important to make sure the config-revision is 0 before you plug it into a live network if you don't want this switch to overwrite your VLAN databases. I don't recall offhand the 'show vtp ...' command that shows you what the current config-revision value is but it is there. Also, be aware that a VTP CLIENT can send out VTP updates and wipe out your VLAN database config. IE: A quick-fix is not to change from Server to client mode. HTH, Erick --- Jeffrey Reed wrote: > If I have an existing VTP domain server with many > VLANs configured and then > add another VTP server does the first server update > the new server? No > chance of the new server updating the old server and > wiping out the VTP > database, right? > > Thanks!! > > Jeff [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Movies - coverage of the 74th Academy Awards. http://movies.yahoo.com/ Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39088&t=39083 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: VTP Servers [7:39083]
Almost right. If both servers are in the same VTP domain, the one whose configuration counter is highest will propogate it's VLANs. This means that if you add a server that's been sitting in your lab and it has a higher configuration counter, you will lose the VLANs on your current switch. If the switch is not going to be a core switch, configure it as a VTP client and the world will be a safe place. If it does have a higher configuration counter, change it's VTP domain to a different name and then change it back. It's counter will go back to zero. David -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jeffrey Reed Sent: Thursday, March 21, 2002 2:27 PM To: [EMAIL PROTECTED] Subject: VTP Servers [7:39083] If I have an existing VTP domain server with many VLANs configured and then add another VTP server does the first server update the new server? No chance of the new server updating the old server and wiping out the VTP database, right? Thanks!! Jeff Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39090&t=39083 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: VTP Servers [7:39083]
Careful about the "...configure it as a VTP client and the world will be a safe place." statement. From CCO (all the following text is from CCO - no comments needed): Link (watch wrap): cisco.com/warp/public/473/21.html#How%20a%20newly%20inserted%20switch%20can% 20mess%20up%20a%20network%20? How a Recently-Inserted Switch Can Cause Network Problems This problem occurs when you have a large switched domain, which is all in the same VTP domain, and you want to add one switch in the network. This switch was previously used in the lab and a good VTP domain name was entered. It was configured as a VTP client, and connected to the rest of the network. Then, the ISL link was brought up to the rest of the network. In just a few seconds, the whole network is down. What could have happened? The configuration revision of the switch you inserted was higher than the configuration revision of the VTP domain. Therefore, your recently-introduced switch, with almost no configured VLANs, has erased all VLANs through the VTP domain. This will happen whether the switch is a VTP client or a VTP server. A VTP client can erase VLAN information on a VTP server. You will know that this has happened when many of the ports in your network go into inactive state, but continue to be assigned to a non-existing VLAN. Cheers! Arjen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Ford Sent: March 21, 2002 4:38 PM To: [EMAIL PROTECTED] Subject: RE: VTP Servers [7:39083] Almost right. If both servers are in the same VTP domain, the one whose configuration counter is highest will propogate it's VLANs. This means that if you add a server that's been sitting in your lab and it has a higher configuration counter, you will lose the VLANs on your current switch. If the switch is not going to be a core switch, configure it as a VTP client and the world will be a safe place. If it does have a higher configuration counter, change it's VTP domain to a different name and then change it back. It's counter will go back to zero. David -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jeffrey Reed Sent: Thursday, March 21, 2002 2:27 PM To: [EMAIL PROTECTED] Subject: VTP Servers [7:39083] If I have an existing VTP domain server with many VLANs configured and then add another VTP server does the first server update the new server? No chance of the new server updating the old server and wiping out the VTP database, right? Thanks!! Jeff Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39095&t=39083 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: VTP Servers [7:39083]
Provided you have different VTP domains and passwords, vtp advertisements wont propogate between the two, I always use VTP passwords, so you may want to ensure you have this as well... The domain name is what distinguishs the two Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39097&t=39083 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: VTP Servers [7:39083]
Depending on the type of switch and version of software, changing mode from Server to Client will reset the VTP configuration revision, but not on all, so again the safest way is to confirm the revision before connecting the switch. Regards, Gaz ""Arjen Dragt"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Careful about the "...configure it as a VTP client and the world will be a > safe place." statement. From CCO (all the following text is from CCO - no > comments needed): > > Link (watch wrap): > > cisco.com/warp/public/473/21.html#How%20a%20newly%20inserted%20switch%20can% > 20mess%20up%20a%20network%20? > > > > How a Recently-Inserted Switch Can Cause Network Problems > > This problem occurs when you have a large switched domain, which is all in > the same VTP domain, and you want to add one switch in the network. > > This switch was previously used in the lab and a good VTP domain name was > entered. It was configured as a VTP client, and connected to the rest of the > network. Then, the ISL link was brought up to the rest of the network. In > just a few seconds, the whole network is down. What could have happened? > > The configuration revision of the switch you inserted was higher than the > configuration revision of the VTP domain. Therefore, your > recently-introduced switch, with almost no configured VLANs, has erased all > VLANs through the VTP domain. > > This will happen whether the switch is a VTP client or a VTP server. A VTP > client can erase VLAN information on a VTP server. You will know that this > has happened when many of the ports in your network go into inactive state, > but continue to be assigned to a non-existing VLAN. > > > Cheers! > > Arjen > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > David Ford > Sent: March 21, 2002 4:38 PM > To: [EMAIL PROTECTED] > Subject: RE: VTP Servers [7:39083] > > > Almost right. > > If both servers are in the same VTP domain, the one whose configuration > counter is highest will propogate it's VLANs. This means that if you add a > server that's been sitting in your lab and it has a higher configuration > counter, you will lose the VLANs on your current switch. > > If the switch is not going to be a core switch, configure it as a VTP client > and the world will be a safe place. > > If it does have a higher configuration counter, change it's VTP domain to a > different name and then change it back. It's counter will go back to zero. > > David > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Jeffrey Reed > Sent: Thursday, March 21, 2002 2:27 PM > To: [EMAIL PROTECTED] > Subject: VTP Servers [7:39083] > > > If I have an existing VTP domain server with many VLANs configured and then > add another VTP server does the first server update the new server? No > chance of the new server updating the old server and wiping out the VTP > database, right? > > Thanks!! > > Jeff Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39245&t=39083 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]