%CDP-W-NATIVE_VLAN_MISMATCH: Native VLAN mismatch detected on interface gi26.

Hell everyone,
I have a sonicwall firewall with 6 vlan and 3 cisco sg28 switches connected to it, everything is working fine, but I se I have these waring the the log files of all three switches.
I just need to know the best way to resolve this..
the firsrt switch is the "core" switch and the other two are connect to it in a star pattern.
Sonicwall--switch1.101.1----switch 101.10
|
|
switch 101.20
So core switch 101.1 has default vlan set to 100 which is the default lan on the sonicwall that it is connected to. There are no devices in .100
switch 101.10 has devault vlan set to 1
switch 101.20 has default vlan set to 1
switch 101.1 is seeing these warnings..
2147483643
2014-Apr-01 19:33:08
Warning
%CDP-W-NATIVE_VLAN_MISMATCH: Native VLAN mismatch detected on interface gi27.
2147483644
2014-Apr-01 19:30:52
Warning
%CDP-W-NATIVE_VLAN_MISMATCH: Native VLAN mismatch detected on interface gi26.
switch 101.10 is seeing these warnings;
%CDP-W-NATIVE_VLAN_MISMATCH: Native VLAN mismatch detected on interface gi52.
port gi52 is connecting to switch 101.1
switch 101.20 is seeing these warings;
%CDP-W-NATIVE_VLAN_MISMATCH: Native VLAN mismatch detected on interface gi27.
portgi27 is connected to switch 101.1
Thanks!

Hi,
Yes, in this case you can change the native vlan on the that switch with the command (config-if)#switchport trunk native vlan #, there is no need to reboot the switch in order for the change to take effect.
Regards,

Similar Messages

%CDP-W-NATIVE_VLAN_MISMATCH: Native VLAN mismatch detected on interface fa1.

I am getting the following message in my logs on SF300-8
"%CDP-W-NATIVE_VLAN_MISMATCH: Native VLAN mismatch detected on interface fa1."
What is causing the error, see VLAN setup below:

Hi,
Yes, in this case you can change the native vlan on the that switch with the command (config-if)#switchport trunk native vlan #, there is no need to reboot the switch in order for the change to take effect.
Regards,

Native vlan mismatch

Dear all,
I am getting the following message in our VSS.
Sep 2 05:56:18.501: %CDP-SW1-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch
discovered on GigabitEthernet1/2/29 (304), with HQ-DC-CSW-VSS.abc.com
GigabitEthernet2/2/28 (300).
interface GigabitEthernet2/2/28
description *** F5 Load Balancer Port 2 Primary ***
switchport
switchport access vlan 300
switchport mode access
interface GigabitEthernet1/2/29
description *** F5 Load Balancer Port 5 Primary ***
switchport
switchport access vlan 304
switchport mode access
Can anyone explain me how I get this message although g2/2/28 and gi 1/2/29 are access ports.?How to fix this issue?Is this interrupt the network(loop)?
Thanks

Could u try this:
sw1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
sw1(config)#no cdp advertise-v2
regards
Inayath

How one Switch identify the Native vlan mismatch

Dear All,
I am using two cisco L2 switches. Both are connected by a trunk link. Unfortunately I configured different native vlan between two switches. Suddenly I got an error that native vlan mismatch. When I changed the configuration Now it's working fine. My question is that how one switch identify that native vlan mismatch(either by Bpdu, cdp or packet). Please mention which of the following used by switch to identify native Vlan mismatch.
Regards,
Sanjib

Sanjib, Karsten,
It's CDP.
Yes, and STP as well if you run a trunk between the two switches. PVST+ and RPVST+ BPDUs have a TLV in their trailer that carries the VLAN number for which the BPDU was originated. If the BPDU is received in a different VLAN (caused by a native VLAN mismatch), the receiving switch will be able to detect it.
Wireshark 1.12.x will be capable of displaying this TLV field in captured PVST+ and RPVST+ BPDUs. Until 1.12.x is released, you may want to try daily builds from:
http://www.wireshark.org/download/automated/
They already incorporate the enhancement.
Best regards,
Peter

Native Vlan Mismatch on Switch LD connected to

I am running 3 switches each with the same 3 vlans. I also have 2 local directors in failover mode. The primary has interfaces connected to switch one and the secondary has interfaces to switch two. Trunking is disabled on all device ports but enabled on a dedicated fiber connection between the 2 switches
The first vlan is vlan 1 for management
The second is vlan 2 for the gateway side of the local directors
The third is vlan 3 for the server side of the local directors
On the primary switch I am logging CDP messages telling me i have a native vlan mismatch on the 2 local director ports. The secondary switch I dont get these messages.
Any ideas what is going on here and why? Thanks, Art.

You mention above " but trunking is enabled on a dedicated fiber connection between the two switches", therefore trunking is enabled.
Because trunked ports need to be assigned to the same native vlan, I would do a "show trunk" and verify that the port used for trunking on each switch, are assigned to the same native vlan, I've seen the mismatch if the are not. That command above is if your switch is using CatalystOS, otherwise, use this command for NativeOS - sh int fast 0/1 switchport and look for the "trunking native mode vlan" number. They must match on each side. To correct the problem, do set vlan 1 4/10 to assign port 4/10 to vlan 1 which, is your management vlan which I assume you've choosen to be your native vlan.
Hope this helps.

WLC - Native VLAN mismatch

Can anyone tell me or point me in the proper direction for the method to set the native vlan on the WLC? I have a 3750 that is showing a native vlan mismatch going to the 4402.

hello - have a look at this link
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008070ba8f.shtml
explains config for WLC and uplink switch.
hth
andy

Native vlan mismatch error msg from cdp

get this message from my 6509 connects to 3550. but no trunking is set between them. my other ports also have the same settings, with no err msg but have a native vlan unknown status... why???
this 6509 is not set by me.. :(

I do not have enough information from you to say if it is a bug. Past output of
sh ver
sh cdp neigh detail
sh int trunk
sh run int gigx/y or sh run int fas x/y

SG500 LACP trunk mismatch native vlan on individual ports

Hi All,
I have just configured up a sg500 with a lacp trunk to an upstream switch.
I am getting native vlan mismatch on the individual ports of the lacp team.
24-Jan-2013 12:54:48 %CDP-W-NATIVE_VLAN_MISMATCH: Native VLAN mismatch detected on interface gi1/1/24.
24-Jan-2013 12:57:35 %CDP-W-NATIVE_VLAN_MISMATCH: Native VLAN mismatch detected on interface gi1/1/48.
The following is showing the correct native vlan
BH-WS-AC-2#show int switchport port 1
Port : Po1
Port Mode: Trunk
Gvrp Status: disabled
Ingress Filtering: true
Acceptable Frame Type: admitAll
Ingress UnTagged VLAN ( NATIVE ): 2000
Port is member in:
Vlan               Name               Egress rule Port Membership Type
1200               1200                 Tagged           Static
1210            Management              Tagged           Static
1212               1212                 Tagged           Static
2000           Native Vlan             Untagged          Static
But the following shows that the individual ports think they are the default vlan 1.
BH-WS-AC-2#show int switchport gi1/1/48
Port : gi1/1/48
Port Mode: Trunk
Gvrp Status: disabled
Ingress Filtering: true
Acceptable Frame Type: admitAll
Ingress UnTagged VLAN ( NATIVE ): 1
Port is member in:
Vlan               Name               Egress rule Port Membership Type
The following shows the LACP as up:
BH-WS-AC-2#show int Port-Channel 1
Load balancing: src-dst-mac-ip.
Gathering information...
Channel Ports
Po1      Active: gi1/1/24,gi1/1/48
Is this normal behaviour? as i cannot set the native vlan directly on the gi interface due to it being in the trunk.
Simon

Hi Simon, native vlan mismatch is a cosmetic error from CDP. It won't affect services provided the vlans are a member of the ports in question.
You can set the native vlan while it is within the lag. On the SX500 it would be
config t
int po1
switchport trunk native vlan xxxx
The port channel is the same as any other individual port so it's not a problem. 802.1q specifies the native vlan is the untagged member, if you want to get rid of the error, make sure the untagged vlans match up on both sides.
-Tom
Please mark answered for helpful posts

Vlan mismatch error

All,
I have investigated and made sure the speed/duplex have been changed between both devices attached to int-faces.
here is my error.
02-ext-liv FastEthernet0/20 (40).
Feb 20 16:22:18.711 PST: %CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on FastEthernet0/xx
2900 series switch.
What other approach shall I take to pin point the issue since this is only informational on the error log.
-fz
Thanks in advance!

Hi,
The 'error' message is simply because you have used different VLAN IDs on the access ports at either end. CDP discovers this and logs a warning. The message is pretty harmless in itself.
There are a couple of options to get rid of it:
- configure the access port to be the same VLAN on the two switches at either end of the link
--- OR ----
- enable CDP version 1 on your switches. YOu can do this using: 'no cdp advertise-v2'.
The latter option is simpler and you don't really lose much...
Hope that helps - pls rate the post if it does.
Paresh

%CDP-4-NATIVE_VLAN_MISMATCH

Hello,
I have a Cisco 2950 connected to a 3550 through a cross-cable on FastEthernet0/1 and FastEthernet0/4, respectively.
On the 2950, I get the following error message:
%CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on FastEthernet0/1 (0), with switch FastEthernet0/4 (1).
I cannot really figure out how to get rid of this error message, both interfaces are in VLAN1. Also, would this mismatch have any impact on the connectivity between these two devices ?
Thanks for your input in advance.
Regards,
Georg

Georg,
I agree with Fredrik. If both ports are set to switchport mode access and the access VLAN on each port is VLAN 1, then native VLAN mismatch really should have no impact on connectivity.
You may have an unnecessary "switchport trunk native vlan x" command in the configuration of one or both ports, left over from when it may have been configured as a switchport mode trunk. Double-check your config for this. It is not uncommon to have several switchport trunk-related commands remain in the config when the port mode is changed from trunk to access.
Even though the ports are set up for access mode, CDP will communicate any relevant information about the port configurations to other Cisco devices which may be attached to them. If this message is really annoying, you can turn off CDP on just those ports, as Fredrik suggests; but then you would lose the benefit of having CDP exchange other important information between the two switches.
Hope this helps.

Vlan mismatch on a non-trunk port?

I have a 6500, running CatOS 7.6(2), directly connected to a 3500xl (running IOS 12.0(5)) with Cat5. I am *not* trunking between them. Each port is running under a different native VLANs, which I wouldn't think was an issue since they aren't trunking. The connection works fine, and packets flow between them as expected, but my 6500 complains about a native VLAN mismatch on that port. Is this a bug on the CatOS side? The 3500xl doesn't seem to complain about the native vlans being different.

Yes, these are CDP messages:
%CDP-4-NVLANMISMATCH:Native vlan mismatch detected on port 4/39
I am sure the port is not trunking:
Commons_6506_1> show trunk 4/39
Port Mode Encapsulation Status Native vlan
4/39 off dot1q not-trunking 54
Each port is in a different access VLAN. I just thought it odd that the 6500 cared about the native vlans since there was no trunking, and thus, no native vlan (just the active vlan).

Vlan Mismatch WS-C6506 & 2950

Hi guys,
I am having problem. I am not sure about this issue. Recently, I have new switch(2950) plugin into the Core switch. However, it keep generating log every 30 mins on my core switch. any idea about this problem?
2005 Jul 01 22:51:15 GMT+2 +07:00 %CDP-4-NVLANMISMATCH:Native vlan mismatch dete
cted on port 3/22
Core> (enable) show port 3/22
* = Configured MAC Address
Port Name Status Vlan Duplex Speed Type
3/22 2950 connected 210 full 100 100BaseFX MM
Core> (enable) show trunk 3/22
* - indicates vtp domain mismatch
# - indicates dot1q-all-tagged enabled on the port
Port Mode Encapsulation Status Native vlan
3/22 off negotiate not-trunking 210
Port Vlans allowed on trunk
3/22 1-1005,1025-4094
Port Vlans allowed and active in management domain
3/22 210
Port Vlans in spanning tree forwarding state and not pruned
3/22
core#show ver
WS-C6506 Software, Version NmpSW: 7.6(7)
Copyright (c) 1995-2004 by Cisco Systems
NMP S/W compiled on May 6 2004, 23:21:07
System Bootstrap Version: 7.1(1)
System Boot Image File is 'bootflash:cat6000-sup2k8.7-6-7.bin'
System Configuration register is 0x102
Core--->2950
2950#show vla
VLAN Name Status Ports
1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4
Fa0/5, Fa0/6, Fa0/7, Fa0/8
Fa0/9, Fa0/10, Fa0/11, Fa0/12
Fa0/13, Fa0/14, Fa0/15, Fa0/16
Fa0/17, Fa0/18, Fa0/19, Fa0/20
Fa0/21, Fa0/22, Fa0/23, Fa0/24
Fa0/25, Fa0/26
2950#show vtp st
VTP Version : 2
Configuration Revision : 0
Maximum VLANs supported locally : 250
Number of existing VLANs : 5
VTP Operating Mode : Transparent
VTP Domain Name : access
VTP Pruning Mode : Disabled
VTP V2 Mode : Disabled
VTP Traps Generation : Disabled
MD5 digest : 0xB6 0x18 0x3A 0xBA 0xC7 0x54 0x71 0x55
Configuration last modified by 0.0.0.0 at 0-0-00 00:00:00

Hi guys,
Thanks for promptly replied. However I had tried to harded core on 2950 Vlan 210(every interfaces). No luck. The core switch still flooding the log. Correct If I am wrong. Since my 2950 is configured as transparent. It shouldn't broadcast the VLAN info. Am I right? This is not the switch connected to the VLAN 210. I have another switch 210 connected to Core. But it doesn't generate the log.
Core(enable) show vlan
VLAN Name Status IfIndex Mod/Ports, Vlans
1 default active 5 2/23-24
3/9,3/18,3/23-24
4/28,4/38-40
5/9-48
5 ServerFarm active 112 4/1-9,4/11-27,4/29-30,4/
33-37,4/43
5/1-8
20 External active 10 4/10,4/41,4/44-48
30 External2 active 11
80 DMZ active 114 4/42
100 User1 active 12
120 User2 active 13 2/1-21
3/1-8,3/10-17,3/19-21
210 VLAN0210 active 116 2/22
3/22
4/31-32
Core# (enable) show vlan 210
VLAN Name Status IfIndex Mod/Ports, Vlans
210 VLAN0210 active 116 1/1-2
2/22<<
3/22<<
4/31-32
15/1
Core> (enable) show port 2/22
* = Configured MAC Address
Port Name Status Vlan Duplex Speed Type
2/22 SwitchA connected 210 full 100 100BaseFX MM

The old native vlan question....

Topic came up during troubleshooting a 3524XL sw.
I think my understanding of the native vlan concept is wrong.
I thought on a trunk port (Cisco device) that any packet transversing a trunk link (dot1q trunk that is) has a vlan tag applied on the egress port. As an untagged packet arrives on the port (prior to being sent out over the trunk), its is tagged with the native vlan (if its not assocated with any other vlan), then sent out the (egress) the trunked port.
But lately I have been reading that
"A native vlan is the untagged vlan on an 802.1q trunked switchport. The native vlan and management vlan could be the same, but it is better security practice that they aren't. Basically if a switch receives untagged frames on a trunkport, they are assumed to be part of the vlan that are designated on the switchport as the native vlan. Frames egressing a switchport on the native vlan are not tagged. This is the definition however more recent switch software often will allow you to tag all of the frames, even those in the native vlan. This gives some added security and allows the CoS bits to be carried between switches even on the native vlan. Let me know if you need further clarification."
From : https://learningnetwork.cisco.com/thread/8721
So this tells me that you can have a packet transversing a dot1q link w/o a vlan tag...then when it arrives on the other end its put in the vlan that is on that native vlan question. Is this correct?
If so, and a packet can transverse a trunk link w/o a VLAN tag applied, how does a sw detect (ingress) a native vlan mismatch?
Thanks!

Hi,
It's correct, the native vlan is not tagged by default on the trunk link but some platform can make you tag all traffic though even the native vlan.
The native vlan mismatch is detected through cdp.
Regards.
Alain.
Don't forget to rate helpful posts.

Switchport trunk native vlan question...

What am I missing in regards to the following two lines assigned to a sw interface:
switchport trunk native vlan 80
switchport mode trunk
Why assign a VLAN to the port when your trunking it (meaning you allowing all VLANs to pass)?
Thank you.

By default native VLAN is VLAN 1, but can be changed to any No. on the trunk port by command "switchport trunk native vlan #". This will make a new vlan# as native & allow all pkts from this vlan to pass thru trunk untagged.
Native VLANs are used to carry CDP, PAgP & VTP messages. Thus the Frames on native VLAN are untagged. For these messages to propagate between devices, native VLANS must match on both sides of the trunk. In case of native VLAN mismatch on bothsides of the trunk, STP will put the trunk port in err-disabled state.

Native VLAN discrepancy is not reported in LMS 4.0

Hi all,
I have the following problem in LMS 4.0. I see a lot of CDP syslog messages about Native Vlan Mismatch, but the LMS doesn't report it in the disrepancy report. Why?? The similar problem is with TRUNK VLAN Mismatch.
The customer doesn't use VTP in his network. All switches are in the VTP transparent mode.
See the attachment.
Tank you very much
Roman

Moved discussion to Network Management sub-community for quicker response.
Regards,
Pulkit Nagpal
Community Manager- R&S

%CDP-W-NATIVE_VLAN_MISMATCH: Native VLAN mismatch detected on interface gi26.

Similar Messages

Maybe you are looking for