My configuration is as follows, indicating the native vlan on each trunk interface:
the native vlans are fully tagged across these trunks (except 1003).
when I connect the cisco 9300 across the wireless mesh, I get a PVST vlan mismatch error at my router, disabling vlan 1 and vlan 2527. disconnecting the switch but leaving the wirelss mesh up via poe injector, everything works fine.
This cisco switches are running PVST, and the avaya switches are running RSTP. I have rstp disbaled on the trunk ports.
I'm using vlan 1003 at the router native to the distribution as I want vlan 1 tagged (avaya tags the native vlan, which we need vlan 1 for mgmt. i'm migrating away from this). chose 1003 as I know I wont be using it because of the cisco reservation.
I'm not sure why I'm getting the mismatch error. all the native vlans except 1003 should be fully tagged across these trunks.
I found on the switch connection to the wireless mesh portal it did not have vlan 1 tagged. unsure if this is the culprit or something else as well.
It appears that even though only vlan 1 and 2527 were blocked, it affected all connections on ths core to distribution port channel as reported by operations.
Here are the logs from the router:
%SPANTREE-2-BLOCK_PVID_PEER: Blocking Port-channel7 on VLAN0001. Inconsistent peer vlan.
%SPANTREE-2-BLOCK_PVID_LOCAL: Blocking Port-channel7 on VLAN2527. Inconsistent local vlan.
I'm not keen on changin the native vlan to 1 while we are operating. I know the avaya switches require their management network to be tagged and set as native vlan on the trunk to be accessible.
PVID inconsistency occurs when the BPDU is received on different vlan than where it originated. The most common scenario would be native vlan mismatch on a trunk, but it can happen in other situations.
A PVST BPDU has a TLV for originating VLAN (PVID). This TLV will list the VLAN where the BPDU originated.
Is there any chance that the BPDU arriving at the router has a PVID of VLAN 2527, but has an 802.1q tag for VLAN 1?