Hi,
that was not my point. From provider point of view it is IMHO pretty bad
idea to leave cdp turned on customer-facing interfaces. Reasons:
1., letting customer know what kind of equipment you are using, what ip
adresses you are using and also your naming convention.
2., customer can change the
On 6/4/2010 4:17 AM, Jan Gregor wrote:
4., with badly configured vfi you will display your entire topology to
customer (and customer topology to all your devices, see point 2)
Maybe reasons why CDP is disabled on uni ports by default? :)
I think the idea was, much like windows/mac/etc
Jeremy over at Packetlife has a really good article on ways to make a switch
invisible.
http://packetlife.net/blog/2010/apr/15/invisible-catalyst-switch/
On Fri, Jun 4, 2010 at 9:00 AM, Jeff Kell jeff-k...@utc.edu wrote:
On 6/4/2010 4:17 AM, Jan Gregor wrote:
4., with badly configured vfi
Made my day :). CCNA, doing it wrong :).
BTW, letting CDP turned on towards the customer is really the way to get
your logs pretty large pretty fast when you bump into a bad guy.
Jan
On 06/02/2010 06:37 AM, Octavio Alvarez wrote:
On Fri, 28 May 2010 16:41:16 -0700, Rick Kunkel
or just correct the native vlans?
On 02-Jun-2010, at 8:59 PM, Jan Gregor wrote:
Made my day :). CCNA, doing it wrong :).
BTW, letting CDP turned on towards the customer is really the way to get
your logs pretty large pretty fast when you bump into a bad guy.
Jan
On 06/02/2010 06:37
The message relates to a trunk.
If you connect two vanilla ports together, with a Cisco on each end,
it will automagically try to negotiate a trunk (unless switchport
nonegotiate). With that accomplished, if the native port on the ends
doesn't match (switchport access vlan xxx), that will
@puck.nether.net
Subject: Re: [c-nsp] NATIVE_VLAN_MISMATCH
or just correct the native vlans?
On 02-Jun-2010, at 8:59 PM, Jan Gregor wrote:
Made my day :). CCNA, doing it wrong :).
BTW, letting CDP turned on towards the customer is really the way to get
your logs pretty large pretty fast when you bump
On Fri, 28 May 2010 16:41:16 -0700, Rick Kunkel kun...@w-link.net wrote:
I've connected a switch of mine to a provider's switch, and I'm getting
CDP-4-NATIVE_VLAN_MISMATCH warnings... but everything works fine.
Is this just a harmless warning? I'm not doing any VLANs with them.
Their
On Fri, 28 May 2010, Rick Kunkel wrote:
Heya folks...
I've connected a switch of mine to a provider's switch, and I'm getting
CDP-4-NATIVE_VLAN_MISMATCH warnings... but everything works fine.
Is this just a harmless warning? I'm not doing any VLANs with them. Their
connection is going
Heya folks...
I've connected a switch of mine to a provider's switch, and I'm getting
CDP-4-NATIVE_VLAN_MISMATCH warnings... but everything works fine.
Is this just a harmless warning? I'm not doing any VLANs with them.
Their connection is going into a 3550 that has just had the nvram
The warning will go away if you disable CDP.
-k
On Fri, May 28, 2010 at 6:41 PM, Rick Kunkel kun...@w-link.net wrote:
Heya folks...
I've connected a switch of mine to a provider's switch, and I'm getting
CDP-4-NATIVE_VLAN_MISMATCH warnings... but everything works fine.
Is this just a
Well, you said the 3550 has had its nvram erased and is running a default
config, so all of its switch ports are in vlan 1. I am guessing the other
switch has its port in a different vlan. Even if both ports are in access
mode, CDP will generate native vlan mismatches if their configured access
12 matches
Mail list logo
