Re: [c-nsp] CDP interoperability

2013-05-01 Thread Aivars
Well, I tried it my lab. switchport trunk allowed vlan has no impact on CDP, VTP, LACP, STP etc. They are still sent in vlan 1 even if it is not allowed on trunk. http://www.cisco.com/en/US/docs/switches/lan/catalyst2940/software/release/12.1_19_ea1/configuration/guide/swvlan.html#wp1150302

Re: [c-nsp] CDP interoperability

2012-12-10 Thread Peter Rathlev
On Mon, 2012-12-10 at 19:42 +0100, Andriy Bilous wrote: > Seen the same with CDP on ISR G2 with 15.0M - they've sent CDP frames > in every subinterface. It IS annoying. I tried playing around a little and discovered that the neighbor will see all the subinterfaces regardless of their encapsulation

Re: [c-nsp] CDP interoperability

2012-12-10 Thread Andriy Bilous
Seen the same with CDP on ISR G2 with 15.0M - they've sent CDP frames in every subinterface. It IS annoying. Won't surprise me if that was an actual feature request to get something obscure and ugly working in CiscoWorks or Prime. =) On Mon, Dec 10, 2012 at 5:57 PM, Peter Rathlev wrote: > On M

Re: [c-nsp] CDP interoperability

2012-12-10 Thread Phil Mayers
On 10/12/12 16:57, Peter Rathlev wrote: On Mon, 2012-12-10 at 17:54 +0200, Saku Ytti wrote: Luckily I think Cisco won't tag LLDP so maybe you can migrate there. A Sup720 running SXI with subinterfaces will send LLDP frames in each VLAN it seems, or at least that's what a neighboring 3560 seems

Re: [c-nsp] CDP interoperability

2012-12-10 Thread Peter Rathlev
On Mon, 2012-12-10 at 17:54 +0200, Saku Ytti wrote: > Luckily I think Cisco won't tag LLDP so maybe you can migrate there. A Sup720 running SXI with subinterfaces will send LLDP frames in each VLAN it seems, or at least that's what a neighboring 3560 seems to think: Switch1#show lldp nei Capabi

Re: [c-nsp] CDP interoperability

2012-12-10 Thread Adam Vitkovsky
> Cisco thinks - this is expected behavior. I believe it's the expected behavior that the XR box won't accept an arbitrary marked frame without any efp matching the designation adam ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.ne

Re: [c-nsp] CDP interoperability

2012-12-10 Thread Phil Mayers
On 10/12/12 15:48, harbor235 wrote: Aivars, Best practice would be to remove VLAN 1 from the list of trunked VLANs. Irrelevant. CDP still uses tag number "1", even if the vlan isn't on the trunk. ___ cisco-nsp mailing list cisco-nsp@puck.nether.ne

Re: [c-nsp] CDP interoperability

2012-12-10 Thread Saku Ytti
On (2012-12-10 17:39 +0200), Aivars wrote: > vlan native on a trunk port, CDPs are sent with dot1q tag "1". vlan > dot1q tag native will also do the same trick. > > What do you guys think? Is this a bug or a feature? Should it remain > as it is? I've always viewed it as bug. Luckily I th

Re: [c-nsp] CDP interoperability

2012-12-10 Thread Phil Mayers
On 10/12/12 15:39, Aivars wrote: Hi, I thought that CDP essence is to help understand what device you have at the other end of the wire no matter what. You just plug one Well... not really. For starters, if you have a non-CDP-aware layer2 device between 3 or more cisco devices, the w

Re: [c-nsp] CDP interoperability

2012-12-10 Thread harbor235
Aivars, Best practice would be to remove VLAN 1 from the list of trunked VLANs. Mike On Mon, Dec 10, 2012 at 10:39 AM, Aivars wrote: > Hi, > > I thought that CDP essence is to help understand what device you > have at the other end of the wire no matter what. You just plug one > end

[c-nsp] CDP interoperability

2012-12-10 Thread Aivars
Hi, I thought that CDP essence is to help understand what device you have at the other end of the wire no matter what. You just plug one end of the cable into one box and the other end into another and you get your CDP neighbors. Besides other side usage like in IP phone communication