I just tried your suggestion, and it didn't have any effect. My output is below. I guess I'm making a case to state that the only way to truly meet the requirements, as stated, is to keep Cat2 as a server. It satisfies the condition where the "show vtp status" displays the preferred interface, and it continues to act like a client would, in terms of receiving VTP updates.
Cat2(config-if)#vtp int lo1 Cat2(config)#do sh vtp status VTP Version : running VTP2 Configuration Revision : 0 Maximum VLANs supported locally : 1005 Number of existing VLANs : 20 VTP Operating Mode : Server VTP Domain Name : where? VTP Pruning Mode : Disabled VTP V2 Mode : Enabled VTP Traps Generation : Disabled MD5 digest : 0x24 0x76 0x44 0xCA 0x18 0x65 0x13 0xC6 Configuration last modified by 148.48.6.102 at 3-1-93 00:40:51 Local updater ID is 148.48.103.103 on interface Lo1 (preferred interface) Preferred interface name is lo1 Cat2(config)#vtp mode clie Setting device to VTP CLIENT mode. Cat2(config)#do sh vtp status VTP Version : running VTP2 Configuration Revision : 0 Maximum VLANs supported locally : 1005 Number of existing VLANs : 20 VTP Operating Mode : Client VTP Domain Name : where? VTP Pruning Mode : Disabled VTP V2 Mode : Enabled VTP Traps Generation : Disabled MD5 digest : 0x24 0x76 0x44 0xCA 0x18 0x65 0x13 0xC6 Configuration last modified by 148.48.6.102 at 3-1-93 00:40:51 Cat2(config)# On Tue, Jul 14, 2009 at 1:27 PM, Joe Astorino<[email protected]> wrote: > Make sure you are running vtp version 2 > > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
