Symptom
EVC enabled for different bridge-domains, we may see this kind of logs and vlan goes to inconsistent state
*Dec 28 07:48:57.404: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 70 on vlan 69.
In device which generated above log, bridge domain 69 with VLAN 69 is configured but bridge domain 70 with VLAN 70 is not configured.
This happens for packets recieved with different VLAN tags, punt to random bridge domains on ASR.
Conditions
Running ASR1K with EVC and STP enabled
Workaround
Option 1: allow only VLANs associated with bridge domains on peer device, so BPDUs for vlans which bridge domain is not configured for, won't reach to ASR.
Option 2: disable STP on ASR1K.
Further Problem Description
If you see this issue on any release other than Everest, this is not your bug.
You may see the issue on 16.3.x happens on bridge-domain 1, VLAN 1:
%SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 9 on vlan 1.
Then it stops after blocking interface on VLAN 1.
Business Unit confirms VLAN 1 for ASR1k should be considered as native VLAN. By default, STP in non-configured EFP received on ASR1k will be punt and handled with VALN 1. VLAN 1 should not be configured for customer's traffic use in OTV. This is the correct configuration:
service instance 1 ethernet
encapsulation untagged
With this configuration, STP packets with unknown VLAN tags will be punted to this service instance.
Business Unit asks not to use VLAN 1 for traffic on ASR1K 16.x
For fixed versions for this bug, statement under "Further Problem Description:" applies.
