From: ALL From_NJ (all.from.nj@gmail.com)
Date: Sat Feb 28 2009 - 01:19:33 ARST
Jason, you rock man, thanks for keeping at this. Super cool testing ...
(frustrating yes, but I have learned something new!)
OK, in my lab tests this afternoon, I read all of these and then had to test
it myself. I confirmed also that when the VTP domains mismatch, there is no
relaying of VTP info even in transparent mode. Would be nice to add this
caveat / required config to the docs ... although, I would think that most
companies that use this would probably configure the same domain throughout
as a standard config ... of course that is a hope.
After I verified the behavior, I saw this posting from Jason, and decided I
best try it all (since I have the setup still running).
Yes, it is as you all say. A question for the group, how do you set the vtp
domain to null after you have set it to something else? I do not know, but
wish I knew!!!
I copied the config to the flash as a file, erased the start up, deleted the
vlan.dat, and reloaded the switch. This is how I was able to reset the
domain to ' ' (null).
After I completed this test, I then did a config replace and have moved on
(thanks again group for teaching me config replace, it has been a wonderful
asset to me in my lab testing)
Thanks all,
Andrew Lee Lissitz
On Fri, Feb 27, 2009 at 5:20 PM, Jason Morris <mcnever@gmail.com> wrote:
> what, to rest you say?? not quite yet.
>
> In your setup if SW4's vtp domain is null (as in empty, not just set to
> 'null') it will pass vtp traffic for other domains. You only start seeing
> a
> problems when SW4 has a defined vtp domain.
>
> It doesn't really meet the requirements of your original question... but it
> does kind of explain the delta between the documentation and apparent
> reality....
>
> crude output and example below commented with '!'...
>
> my topology was a litter different
>
> SW1-----SW2-----SW3
>
> !---------------------CREATED VLAN ON VTP SERVER (SW1)
> 01:20:00: VTP LOG RUNTIME: Relaying packet received on trunk Fa0/19 - in
> TRANSPARENT MODE (nc = false)
>
> 01:20:00: VTP LOG RUNTIME: Relaying packet received on trunk Fa0/20 - in
> TRANSPARENT MODE (nc = false)
> !---------------------VLAN SHOWS UP ON VTP CLIENT (SW3)
> Cat2#
> Cat2#sho vtp status
> VTP Version : 2
> Configuration Revision : 0
> Maximum VLANs supported locally : 1005
> Number of existing VLANs : 6
> VTP Operating Mode : Transparent
> VTP Domain Name :
> VTP Pruning Mode : Disabled
> VTP V2 Mode : Disabled
> VTP Traps Generation : Disabled
> MD5 digest : 0x3E 0xD9 0x28 0xB6 0xF6 0x0C 0xA7 0x2F
> Configuration last modified by 0.0.0.0 at 0-0-00 00:00:00
> Cat2#conf t
> Enter configuration commands, one per line. End with CNTL/Z.
> Cat2(config)#vtp doma
> Cat2(config)#vtp domain something
> Changing VTP domain name from NULL to something
> Cat2(config)#
> !--------------------------CREATED VLAN ON VTP SERVER (SW1)
> 01:21:16: VTP LOG RUNTIME: Dropping packet received on trunk Fa0/23 - not
> in
> domain ccie
>
> 01:21:16: VTP LOG RUNTIME: Dropping packet received on trunk Fa0/23 - not
> in
> domain ccie
>
> 01:21:27: %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on
> port
> Fa0/19 because of VTP domain mismatch.
> 01:21:27: %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on
> port
> Fa0/20 because of VTP domain mismatch.
>
> !-------------------------- ALAS... NO VLAN ON CLIENT...
>
>
> On Fri, Feb 27, 2009 at 2:11 PM, naveen M S <navin.ms@gmail.com> wrote:
>
> > Thanks Roy. Not only IEWB has this task part of their workbook lab 20,
> but
> > also CCO docs was wrong. Kinda a double-whammy !
> > What surprises me is that the solutions guide for this lab has got it
> > working the following scenario for some reason.
> >
> > SW1--------------SW4-----------------SW2
> > cisco iewb cisco
> > server server client
> > ver2 ver2 ver2
> >
> > In my testing, it is proved that VTP Domain name in the incoming updates
> > *must
> > match* with the one locally configured for the updates to pass from one
> > trunk to another. The VTP mode and VTP version is irrelevant. With that
> we
> > can put this thread to rest.
> >
> > -Naveen.
> >
> >
> > On Fri, Feb 27, 2009 at 10:20 AM, Waterman, Roy <Roy.Waterman@colt.net
> > >wrote:
> >
> > > You are not the only one who thinks this is incorrect.
> > >
> > > Please refer to Tassos's blog post about vtp v2 transparent:
> > >
> > >
> http://ccie-in-3-months.blogspot.com/2008/07/cco-documentation-errors-vt
> > > p-v2.html<
> >
> http://ccie-in-3-months.blogspot.com/2008/07/cco-documentation-errors-vt%0Ap-v2.html
> > >
> > >
> > >
> > > Regards
> > > Roy
> > >
> > >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> > > Hobbs
> > > Sent: 27 February 2009 15:24
> > > To: ALL From_NJ
> > > Cc: Nadeem Ansari; Jason Morris; Pavel Bykov; Daniel Kutchin; Cisco
> > > certification
> > > Subject: Re: VTP Issue
> > >
> > >
> > > As far as I can tell domain name must match. You can debug VTP events
> > > with
> > > this:
> > >
> > > SW2#debug sw-vlan vtp events
> > >
> > > When domain name matches you get this:
> > > 00:08:37: VTP LOG RUNTIME: Relaying packet received on trunk Fa0/13 -
> in
> > > TRANSPARENT MODE (nc = false)
> > >
> > > When domain doesn't match, you get this (version 1 or 2)
> > > 00:09:23: VTP LOG RUNTIME: Dropping packet received on trunk Fa0/13 -
> > > not in domain ccie
> > >
> > > DocCD says this: "Because VTP Version 2 supports only one domain, it
> > > forwards VTP messages in transparent mode without inspecting the
> version
> > > and domain name."
> > >
> > > I don't think this is correct.
> > >
> > > -hth
> > >
> > > On Fri, Feb 27, 2009 at 7:38 AM, ALL From_NJ <all.from.nj@gmail.com>
> > > wrote:
> > >
> > > > As Daniel and Jason mentioned, run SW4 in transparent mode.
> > > >
> > > > It will forward the vtp announcements from peers, while ignoring the
> > > > contents of these announcements.
> > > >
> > > > Here is a helpful link (watch for the ugly word wrap):
> > > >
> > > >
> http://www.cisco.com/en/US/docs/switches/lan/catalyst3560/software/rel
> > > > ease/12.2_44_se/configuration/guide/swvtp.html#wp1205076
> > > >
> > > > HTH,
> > > >
> > > > Andrew
> > > >
> > > >
> > > >
> > > > On Fri, Feb 27, 2009 at 9:10 AM, Nadeem Ansari
> > > > <nadeem.ansari574@gmail.com>wrote:
> > > >
> > > > > It is mendatory for switches to be in same VTP domain across entire
> > > > > topology to propogate the VTP advertisement it does not matter
> > > > > wether they are in Server mode or transparent mode, So Case-4
> > > > > conclusion is correct Regards
> > > > > Nadeem
> > > > > On Fri, Feb 27, 2009 at 7:33 PM, Jason Morris <mcnever@gmail.com>
> > > wrote:
> > > > >
> > > > > > I'm not sure that your Case-4 results are accurate, did you test
> > > > > > it
> > > > with
> > > > > > sw4
> > > > > > in transparent mode? that should allow vtp information to pass
> > > > > > from
> > > > sw1
> > > > > to
> > > > > > sw2
> > > > > >
> > > > > > jason
> > > > > >
> > > > > > On Fri, Feb 27, 2009 at 6:26 AM, Pavel Bykov <slidersv@gmail.com
> >
> > > > wrote:
> > > > > >
> > > > > > > VTP runs in VLAN1, which is not prunnable or removable. Even
> > > > > > > when you remove it administratively from the trunk, in reality
> > > > > > > it will still be operational.
> > > > > > > What is required by vtp is the same domain name and password.
> If
> > > they
> > > > > > match
> > > > > > > then all modes forward messages.
> > > > > > >
> > > > > > > On Fri, Feb 27, 2009 at 10:18 AM, Daniel Kutchin
> > > > > > > <daniel@kutchin.com
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Naveen -
> > > > > > > >
> > > > > > > > For VTP information to be propagated by SW4, following
> > > > > > > > conditions should be met:
> > > > > > > >
> > > > > > > > 1. Domain names must match on all Switches
> > > > > > > > 2. Disable Pruning on SW4 (not quite sure of this)
> > > > > > > > 2. SW4 can be in Transparent mode
> > > > > > > >
> > > > > > > > Debugging will be useful here: "debug sw-vlan vtp events"
> > > > > > > >
> > > > > > > > Also view this Video (you need a CCO Account)
> > > > > > > > http://www.cisco.com/warp/customer/473/vtp_flash/
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > -
> > > > > > > > Daniel
> > > > > > > >
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]
> On
> > > > Behalf
> > > > > > Of
> > > > > > > > naveen M S
> > > > > > > > Sent: Freitag, 27. Februar 2009 09:08
> > > > > > > > To: Cisco certification
> > > > > > > > Subject: Re: VTP Issue
> > > > > > > >
> > > > > > > > Folks,
> > > > > > > >
> > > > > > > > Here is complete results of my experiments. Hope this
> benefits
> > >
> > > > > > > > you.
> > > > > > > >
> > > > > > > > SW1-------SW4--------SW2
> > > > > > > >
> > > > > > > > X,Y,Z = Domain,Mode,Ver
> > > > > > > > Mode 'Any' = client or server or transparent
> > > > > > > >
> > > > > > > > *Case-1)*
> > > > > > > > cisco,Server,2 -------- cisco,Any,2 --------- cisco,Client,2
> > > > > > > >
> > > > > > > > *Result:*
> > > > > > > > Any vlan changes on SW1 is propogated to SW4 and SW2 Note
> that
> > >
> > > > > > > > when both SW1 and SW4 are VTP servers, changes on one server
> > > > > > > > is updated by other server. Also, SW4 does't update Vlan
> > > > > > > > changes while in Transparent mode.
> > > > > > > >
> > > > > > > >
> > > > > > > > *Case-2)*
> > > > > > > > cisco,Server,2 -------- iewb,Any,2 ---------- cisco,Client,2
> > > > > > > >
> > > > > > > > *Result:*
> > > > > > > > Any vlan changes on SW1 is NOT propogated to SW4 and SW2
> > > > > > > >
> > > > > > > >
> > > > > > > > *Case-3)*
> > > > > > > > cisco,Server,1 -------- cisco,Any,1 --------- cisco,Client,1
> > > > > > > >
> > > > > > > > *Result:*
> > > > > > > > Any vlan changes on SW1 is propogated to SW4 and SW2 Note
> that
> > >
> > > > > > > > when both SW1 and SW4 are VTP servers, changes on one server
> > > > > > > > is updated by other server. Also, SW4 does't update Vlan
> > > > > > > > changes while in Transparent mode.
> > > > > > > >
> > > > > > > >
> > > > > > > > *Case-4)*
> > > > > > > > cisco,Server,2 -------- iewb,Any,2 ---------- cisco,Client,2
> > > > > > > >
> > > > > > > > *Result:*
> > > > > > > > Any vlan changes on SW1 is NOT propogated to SW4 and SW2
> > > > > > > >
> > > > > > > >
> > > > > > > > What bothers me is that how to get VTP updates from SW1 to
> SW2
> > >
> > > > > > > > ? My task doesn't allow me to do Q-in-Q or L2protocol
> > > > > > > > tunnelling.
> > > > > > > >
> > > > > > > > All ideas are welcome.
> > > > > > > > Naveen.
> > > > > > > >
> > > > > > > >
> > > > > > > > On Thu, Feb 26, 2009 at 11:05 PM, naveen M S
> > > > > > > > <navin.ms@gmail.com>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > Yes. This is VTP version 2.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Thu, Feb 26, 2009 at 10:58 PM, joshua atterbury <
> > > > > > > > > joshuaatterbury@gmail.com> wrote:
> > > > > > > > >
> > > > > > > > >>
> > > > > > > > >> are you using vtp version 2?
> > > > > > > > >>
> > > > > > > > >> On Fri, Feb 27, 2009 at 5:55 PM, naveen M S
> > > > > > > > >> <navin.ms@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > > >>
> > > > > > > > >>> Folks,
> > > > > > > > >>>
> > > > > > > > >>> Here is my scenario. Seems trivial but can't get it to
> > > > > > > > >>> work.
> > > > > > > > >>>
> > > > > > > > >>> SW1-------SW4-------SW2
> > > > > > > > >>>
> > > > > > > > >>> SW1 : VTP domain = cisco, Mode = server
> > > > > > > > >>> SW2 : VTP domain = cisco, Mode = client
> > > > > > > > >>> SW4 : VTP domain = iewb, Mode = server
> > > > > > > > >>>
> > > > > > > > >>> The 802.1q trunk links are established b/n the 3 switches
> > > > > > > > >>> and
> > > > > vlan
> > > > > > 1
> > > > > > > is
> > > > > > > > >>> native on them.
> > > > > > > > >>>
> > > > > > > > >>> Changes to vlan in SW1 are NOT propogated to SW2. What
> > > > > > > > >>> could be
> > > > > the
> > > > > > > > >>> problem
> > > > > > > > >>> ?
> > > > > > > > >>>
> > > > > > > > >>> *SW1:*
> > > > > > > > >>> interface GigabitEthernet1/0/20
> > > > > > > > >>> switchport trunk encapsulation dot1q
> > > > > > > > >>> switchport mode trunk
> > > > > > > > >>> switchport nonegotiate
> > > > > > > > >>>
> > > > > > > > >>> *SW4:*
> > > > > > > > >>> interface GigabitEthernet1/0/14
> > > > > > > > >>> switchport trunk encapsulation dot1q
> > > > > > > > >>> switchport mode trunk
> > > > > > > > >>> switchport nonegotiate
> > > > > > > > >>> !
> > > > > > > > >>> interface GigabitEthernet1/0/16
> > > > > > > > >>> switchport trunk encapsulation dot1q
> > > > > > > > >>> switchport mode trunk
> > > > > > > > >>> switchport nonegotiate
> > > > > > > > >>>
> > > > > > > > >>> *SW2:*
> > > > > > > > >>> interface GigabitEthernet1/0/19
> > > > > > > > >>> switchport trunk encapsulation dot1q
> > > > > > > > >>> switchport mode trunk
> > > > > > > > >>> switchport nonegotiate
> > > > > > > > >>>
> > > > > > > > >>> Rack1SW1# sh int trunk
> > > > > > > > >>>
> > > > > > > > >>> Port Mode Encapsulation Status
> > > > Native
> > > > > > vlan
> > > > > > > > >>> Gi1/0/20 on 802.1q trunking
> > > 1
> > > > > > > > >>>
> > > > > > > > >>> Rack1SW4# show int trunk
> > > > > > > > >>>
> > > > > > > > >>> Port Mode Encapsulation Status
> > > > Native
> > > > > > vlan
> > > > > > > > >>> Gi1/0/14 on 802.1q trunking
> > > 1
> > > > > > > > >>> Gi1/0/16 on 802.1q trunking
> > > 1
> > > > > > > > >>>
> > > > > > > > >>> Rack1SW2# sh int trunk
> > > > > > > > >>>
> > > > > > > > >>> Port Mode Encapsulation Status
> > > > Native
> > > > > > vlan
> > > > > > > > >>> Gi1/0/19 on 802.1q trunking
> > > 1
> > > > > > > > >>>
> > > > > > > > >>>
> > > > > > > > >>> Blogs and organic groups at http://www.ccie.net
> > > > > > > > >>>
> > > > > > > > >>>
> > > > > > >
> > > >
> ______________________________________________________________________
> > > > _
> > > > > > > > >>> Subscription information may be found at:
> > > > > > > > >>> http://www.groupstudy.com/list/CCIELab.html
> > > > > > > >
> > > > > > > >
> > > > > > > > Blogs and organic groups at http://www.ccie.net
> > > > > > > >
> > > > > > > >
> > > > >
> ____________________________________________________________________
> > > > > ___
> > > > > > > > Subscription information may be found at:
> > > > > > > > http://www.groupstudy.com/list/CCIELab.html
> > > > > > > >
> > > > > > > >
> > > > > > > > Blogs and organic groups at http://www.ccie.net
> > > > > > > >
> > > > > > > >
> > > > >
> ____________________________________________________________________
> > > > > ___
> > > > > > > > Subscription information may be found at:
> > > > > > > > http://www.groupstudy.com/list/CCIELab.html
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Pavel Bykov
> > > > > > > ----------------
> > > > > > > Don't forget to help stopping the braindumps, use of which
> > > > > > > reduces
> > > > > value
> > > > > > of
> > > > > > > your certifications. Sign the petition at
> > > > > http://www.stopbraindumps.com/
> > > > > > >
> > > > > > >
> > > > > > > Blogs and organic groups at http://www.ccie.net
> > > > > > >
> > > > > > >
> > > >
> ______________________________________________________________________
> > > > _
> > > > > > > Subscription information may be found at:
> > > > > > > http://www.groupstudy.com/list/CCIELab.html
> > > > > >
> > > > > >
> > > > > > Blogs and organic groups at http://www.ccie.net
> > > > > >
> > > > > >
> __________________________________________________________________
> > > > > > _____
> > > > > > Subscription information may be found at:
> > > > > > http://www.groupstudy.com/list/CCIELab.html
> > > > >
> > > > >
> > > > > Blogs and organic groups at http://www.ccie.net
> > > > >
> > > > >
> ____________________________________________________________________
> > > > > ___
> > > > > Subscription information may be found at:
> > > > > http://www.groupstudy.com/list/CCIELab.html
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Andrew Lee Lissitz
> > > > all.from.nj@gmail.com
> > > >
> > > >
> > > > Blogs and organic groups at http://www.ccie.net
> > > >
> > > >
> ______________________________________________________________________
> > > > _
> > > > Subscription information may be found at:
> > > > http://www.groupstudy.com/list/CCIELab.html
> > >
> > >
> > > Blogs and organic groups at http://www.ccie.net
> > >
> > > _______________________________________________________________________
> > > Subscription information may be found at:
> > > http://www.groupstudy.com/list/CCIELab.html
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> *************************************************************************************
> > > The message is intended for the named addressee only and may not be
> > > disclosed to or used by anyone else, nor may it be copied in any way.
> > >
> > > The contents of this message and its attachments are confidential and
> may
> > > also be subject to legal privilege. If you are not the named addressee
> > > and/or have received this message in error, please advise us by
> e-mailing
> > > security@colt.net and delete the message and any attachments without
> > > retaining any copies.
> > >
> > > Internet communications are not secure and COLT does not accept
> > > responsibility for this message, its contents nor responsibility for
> any
> > > viruses.
> > >
> > > No contracts can be created or varied on behalf of COLT
> > Telecommunications,
> > > its subsidiaries or affiliates ("COLT") and any other party by email
> > > Communications unless expressly agreed in writing with such other
> party.
> > >
> > > Please note that incoming emails will be automatically scanned to
> > eliminate
> > > potential viruses and unsolicited promotional emails. For more
> > information
> > > refer to www.colt.net or contact us on +44(0)20 7390 3900.
> > >
> > >
> > > Blogs and organic groups at http://www.ccie.net
> > >
> > > _______________________________________________________________________
> > > Subscription information may be found at:
> > > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- Andrew Lee Lissitz all.from.nj@gmail.comBlogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:13 ARST