that happened because no vlan could be created on this as it was set as a vtp client. Changed it to a server , added vlan 783 and changed back to client and voila!
On Tue, Aug 21, 2012 at 12:23 PM, Maureen Maina <[email protected]> wrote: > > Hi , > Actually , funny thing is the native vlan was missing on the client > device.the "show int trunk" command showed it was trunking and the native > was 783 but on the list of vlans active and not pruned on the trunk , it > was missing:-) > Thanks guys! > > > On Tue, Aug 21, 2012 at 11:19 AM, Bal Birdy <[email protected]>wrote: > >> As a minimum - >> >> 1. VTP Domain name should be manual set the same on all switches >> 2. The VTP version should be the same >> 3. VTP Passwords the same (if used) >> >> That's it. Then VTP revision comes into play i.e. higher rvision number >> overried. >> >> On Tue, Aug 21, 2012 at 5:43 PM, Maureen Maina <[email protected]> wrote: >> >>> Hi All, >>> I had a scenario whereby 2 (3560 and 3560)switches weren't sharing vtp >>> info >>> over a l2 etherchannel.1 was a server and the other a a client. >>> Tried the following: >>> *trunk was up, tried bouncing the port-channel >>> *the client wouldnt learn the domain name like I expected so I changed it >>> to the domain of the server manually >>> *added a vlan on the server to trigger a vtp update >>> >>> anything else i might have done? >>> >>> Regards, >>> Mo >>> _______________________________________________ >>> For more information regarding industry leading CCIE Lab training, >>> please visit www.ipexpert.com >>> >>> Are you a CCNP or CCIE and looking for a job? Check out >>> www.PlatinumPlacement.com >>> >>> http://onlinestudylist.com/mailman/listinfo/ccie_rs >>> >> >> > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://onlinestudylist.com/mailman/listinfo/ccie_rs
