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.
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?
I foudn the avaya switch was missing vlan 1 on the connection to the Aruba AP, I've not tested since adding this, but can't attempt the connection during production. as vlan 1 was not the native vlan for either end of the trunk, I don't think this would have caused the issue.
When I place a nortel 450 switch at the location of the 9300, it does not cause this issue. however the nortel 450 tags the pvid by default, which I have not performed on the 9300. The avaya swtiches also tag pvid by default.
Here is the config of the trunk interface on the 9300 to the aruba AP.