"Received BPDU with inconsistent peer" when adding VLAN

[jmandersson]

Hi Experts,

Any thought of my this problem?

We have stacked 3650 access switches connected to a VSS via a port-channels. For historical reasons we have vlan 1000 as the native vlan on these uplinks. When we ad new vlan's to the access switch it seems that they go untagged for a while and therefor trigger "Received BPDU with inconsistent peer"

Here are some loggs from the VSS when adding vlan 401 and 403 to the access switch:

First we add the vlans add SVI's to the VSS, no problem:

004963: Jun 30 10:29:48.751 CET: %LINK-SW1-3-UPDOWN: Interface Vlan402, changed state to up
004964: Jun 30 10:29:48.759 CET: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface Vlan402, changed state to up
004965: Jun 30 10:29:55.887 CET: %LINK-SW1-3-UPDOWN: Interface Vlan403, changed state to up
004966: Jun 30 10:29:55.895 CET: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface Vlan403, changed state to up

Then we add the same vlans to the access switches, in this case two different stacks connected via Po115 and Po116:

004968: Jun 30 11:15:25.842 CET: %SPANTREE-SW1-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 401 on Port-channel115 VLAN1000.
004969: Jun 30 11:15:25.842 CET: %SPANTREE-SW1-2-BLOCK_PVID_PEER: Blocking Port-channel115 on VLAN0401. Inconsistent peer vlan.
004970: Jun 30 11:15:25.842 CET: %SPANTREE-SW1-2-BLOCK_PVID_LOCAL: Blocking Port-channel115 on VLAN1000. Inconsistent local vlan.
004971: Jun 30 11:15:27.826 CET: %SPANTREE-SW1-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 401 on Port-channel116 VLAN1000.
004972: Jun 30 11:15:27.826 CET: %SPANTREE-SW1-2-BLOCK_PVID_PEER: Blocking Port-channel116 on VLAN0401. Inconsistent peer vlan.
004973: Jun 30 11:15:27.826 CET: %SPANTREE-SW1-2-BLOCK_PVID_LOCAL: Blocking Port-channel116 on VLAN1000. Inconsistent local vlan.
004974: Jun 30 11:15:40.842 CET: %SPANTREE-SW1-2-UNBLOCK_CONSIST_PORT: Unblocking Port-channel115 on VLAN0401. Port consistency restored.
004975: Jun 30 11:15:40.842 CET: %SPANTREE-SW1-2-UNBLOCK_CONSIST_PORT: Unblocking Port-channel115 on VLAN1000. Port consistency restored.
004976: Jun 30 11:15:42.826 CET: %SPANTREE-SW1-2-UNBLOCK_CONSIST_PORT: Unblocking Port-channel116 on VLAN0401. Port consistency restored.
004977: Jun 30 11:15:42.826 CET: %SPANTREE-SW1-2-UNBLOCK_CONSIST_PORT: Unblocking Port-channel116 on VLAN1000. Port consistency restored.
004978: Jun 30 11:16:08.054 CET: %SPANTREE-SW1-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 403 on Port-channel116 VLAN1000.
004979: Jun 30 11:16:08.058 CET: %SPANTREE-SW1-2-BLOCK_PVID_PEER: Blocking Port-channel116 on VLAN0403. Inconsistent peer vlan.
004980: Jun 30 11:16:08.058 CET: %SPANTREE-SW1-2-BLOCK_PVID_LOCAL: Blocking Port-channel116 on VLAN1000. Inconsistent local vlan.
004981: Jun 30 11:16:23.054 CET: %SPANTREE-SW1-2-UNBLOCK_CONSIST_PORT: Unblocking Port-channel116 on VLAN0403. Port consistency restored.
004982: Jun 30 11:16:23.058 CET: %SPANTREE-SW1-2-UNBLOCK_CONSIST_PORT: Unblocking Port-channel116 on VLAN1000. Port consistency restored.

Regards,
Johan

[Mark Malone]

Miss configuration on trunk

Error Message

%SPANTREE-2-RECV_PVID_ERR : Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars].

Explanation : The specified interface has received an SSTP BPDU that is tagged with a VLAN ID that does not match the VLAN ID on which the BPDU was received. This condition occurs when the native VLAN is not consistently configured on both ends of a 802.1Q trunk.

Recommended Action : Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. Once this inconsistency is corrected, spanning tree will automatically unblock the interfaces as appropriate.

[jmandersson]

Hi Mark, thanks for taking interest in my problem.

No, I don't think it's a configuration misstake. Take a look at the config below.

The problem occurs when we add a vlan to the access switch, the  interface configuration stays the same all the time.  

VSS side		3650-stack side
interface Port-channel115		interface Port-channel1
description ACCESS		description UPLINK
switchport		switchport trunk native vlan 1000
switchport trunk native vlan 1000		switchport trunk allowed vlan 1-1000,3001-3032
switchport trunk allowed vlan 1-1000,3001-3032		switchport mode trunk
switchport mode trunk		switchport nonegotiate
switchport nonegotiate		ip arp inspection trust
storm-control broadcast level 4.00		storm-control broadcast level pps 1k
spanning-tree guard root		storm-control action trap
end		ip dhcp snooping trust
interface GigabitEthernet1/1/15		interface GigabitEthernet1/1/1
description ACCESS		description UPLINK-1
switchport		switchport trunk native vlan 1000
switchport trunk native vlan 1000		switchport trunk allowed vlan 1-1000,3001-3032
switchport trunk allowed vlan 1-1000,3001-3032		switchport mode trunk
switchport mode trunk		switchport nonegotiate
switchport nonegotiate		ip arp inspection trust
storm-control broadcast level 4.00		storm-control broadcast level pps 1k
channel-group 115 mode active		storm-control action trap
service-policy type lan-queuing output XX		channel-group 1 mode active
		service-policy output XX
interface GigabitEthernet2/1/15		ip dhcp snooping trust
description ACCESS
switchport		interface GigabitEthernet2/1/1
switchport trunk native vlan 1000		description UPLINK-2
switchport trunk allowed vlan 1-1000,3001-3032		switchport trunk native vlan 1000
switchport mode trunk		switchport trunk allowed vlan 1-1000,3001-3032
switchport nonegotiate		switchport mode trunk
storm-control broadcast level 4.00		switchport nonegotiate
channel-group 115 mode active		ip arp inspection trust
service-policy type lan-queuing output XX		storm-control broadcast level pps 1k
		storm-control action trap
		channel-group 1 mode active
		service-policy output XX
		ip dhcp snooping trust

These two logs are regardning the same vlan:

004968: Jun 30 11:15:25.842 CET: %SPANTREE-SW1-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 401 on Port-channel115 VLAN1000

004974: Jun 30 11:15:40.842 CET: %SPANTREE-SW1-2-UNBLOCK_CONSIST_PORT: Unblocking Port-channel115 on VLAN0401. Port consistency restored

It's exactly 15s between them and there are no configuration made during that time. And this is not a one time thing, it happens every time we add a vlan to the access switch

Thanks again,

Johan

[Mark Malone]

hi are you using vtp or is everything set to transparent , just , if you add the vlan to the vss do you get the same problem as when you add it to the access switch , usually the vss is the vtp server and the vlan would need to be propagated at layer 2 either way , just trying to rule out the actual access switch as being the issue, if the problem exists when doing it at the vss as well it could be something to do with the stp setup or could be a bug on the access switch as you have above your config is matching each side of the trunk for the native vlan , what ios version is the 3650 running on

[jmandersson]

Hi again,

On access switch: vtp mode off

On VSS: vtp mode transparent
 

And yes, this just happens when we add vlans to the accesss switch, not to the VSS..

We are running the access switches on 3.6.1E. Well, I wouldn't be surprised if we have run into a bug, but a can't find anything relevant on the Bug Search Tool.

Thanks,

Johan

[Mark Malone]

Ye checked your release guide below not seeing anything for stp/vlan bugs but that does not mean its not 1 just may not have been found./triggered, just 1 last thing i would check before upgrading or checking with TAC if you shut down 1 link to the vss and add a vlan then does it happen as well , if its a direct connection and its still the same i would be nearly certain its an ios issue

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3650/software/release/3e/release_notes/OL3264701.html

[jmandersson]

Great suggestion, I will close one link in the bundle and then add a vlan and see what's happening.

Thanks

[Robert Falconer]

Is vlan 1000 actually created in the vlan database on both VSS and the 3650s? I ran into a similar problem where the native vlan wasn't actually created in the vlan database on the 3650s when they connected to Nexus 7Ks. Not VSS but similar in that it's multi-chassis etherchannel.

I don't remember exactly what the error was but I had to create the native vlan on the 3650s. On  3750x units, you don't have the requirement to actually define the native vlan if it was non-1, which is what I had used as a standard prior to 3650s.

[jmandersson]

Hi Robert, thanks for taking interest in my problem.

Yes, I'm 100% sure that vlan id 1000 exists on both side, it's in use since the switches was put in production.

Thanks

[jmandersson]

Hi Mark,

I've tried with one of the link in the bundle in shutdown, and the problem did not happened.

Back to two links in the bundle: One other interesting thing I noticed was that if I delete the vlan (no vlan 2) and then add it again (vlan 2), the are no problem. If add a new vlan (vlan 3) then the problem is there again.

I really can't see any configuration that could solve this, so I'll guess I have to open a TAC-case regarding this.

[Mark Malone]

yes that's strange alright , very good discussion on pvid native vlan issues with pvst here below and how exactly the check is performed by the devices when on a trunk connection. sounds like from reading your issue and the detailed description from Aninda and Peter that something is going wrong with the checks when the 3650 is dual connected to the vss as your config is ok for the native vlan on each trunk end

https://supportforums.cisco.com/discussion/11884396/cdp-and-native-vlans

[wavess]

Mark.  

Same problem, but the native VLAN is consistently configured on both ends of the trunk.  

interface GigabitEthernet1/0/10
description UPLINK TO M-AC-1
switchport trunk allowed vlan 71,72,74
switchport trunk native vlan 74
switchport mode trunk
switchport nonegotiate
switchport voice vlan 72

other side:

interface GigabitEthernet1/0/48
description DIRECTLY CONNECTED TO M-AC-2 - CISCO C1000 SWITCH
switchport trunk native vlan 74
switchport trunk allowed vlan 71,72,74
switchport mode trunk
switchport nonegotiate
switchport voice vlan 72
spanning-tree portfast

output:

020034: Jul 15 10:02:28: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 71 on GigabitEthernet1/0/10 VLAN74.
020035: Jul 15 10:02:28: %SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet1/0/10 on VLAN0071. Inconsistent peer vlan.
020036: Jul 15 10:02:28: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking GigabitEthernet1/0/10 on VLAN0074. Inconsistent local vlan.
020037: Jul 15 10:02:28: %SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet1/0/10 on VLAN0072. Inconsistent peer vlan.
020038: Jul 15 10:02:30: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/10, changed state to up
020039: Jul 15 10:02:31: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/10, changed state to up
020040: Jul 15 10:02:43: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet1/0/10 on VLAN0071. Port consistency restored.
020041: Jul 15 10:02:43: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet1/0/10 on VLAN0074. Port consistency restored.
020042: Jul 15 10:02:43: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet1/0/10 on VLAN0072. Port consistency restored.
020043: Jul 15 10:08:21: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/10, changed state to down
020044: Jul 15 10:08:22: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/10, changed state to down

[MHM Cisco World]

Add new post it better to make all read and answer you.

[jmandersson]

This problem is now solved, it was a software defect in 3.6.1.E.
TAC could not present a BUG-id for it, but claimed it should be resolved in 3.7.1.E together with other LACP updates.

Regards,

Johan

[jaschandra]

Simply add native vlan to uplink. This will resolve it.