Greetings all;
I have inherited a bit of a nightmare. We have a site built with a mix of about 45 Catalyst switches of different model/IOS all connecting back to a 3x 3850 stack acting as the core.
I finally got things to a steady state. Segmented VLANs, smaller IP Subnets, all running VTP Server/Client mode and Rapid-PVST with the 3850 core stack as the root and VTP Server. Still, the 3850s I feel are overloaded running a network with upwards of 900 -1200 devices.
We are trying to modernize and have been building up all our new infrastructure based around Meraki gear. I wanted to take all the access switches off of the 3850's and migrate them over to our Meraki MS425 core switches, which are doing all the routing for our VLANs. Once we migrated the uplinks from the 3850 to the Meraki core switches, I started to notice some connectivity issues. Digging deeper, I'm finding that all of the switches adjacent to the Meraki core are reporting Inconsistent VLANs;
000688: .Jul 8 12:36:25: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent on GigabitEthernet1/0/49 VLAN999.
000689: .Jul 8 12:36:25: %SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet1/0/49nconsistent peer vlan.
000690: .Jul 8 12:36:25: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking GigabitEthernet1/0/4Inconsistent local vlan.
And are subsequently blocking VLANs 999 and 1 on the trunks.
The Meraki Core is running RSTP and is the new root. The uplinks between the Meraki and Cisco switches are all configured as 802.1q trunks with VLAN 1 as the native (Except for one switch where we tried making the native VLAN 999 as the native to try and overcome this.
VLAN0999
Spanning tree enabled protocol rstp
Root ID Priority 62439
Address a0cf.5b85.6280
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 62439 (priority 61440 sys-id-ext 999)
Address a0cf.5b85.6280
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Gi1/0/49 Desg BKN*4 128.49 P2p *PVID_Inc
All of the access switches adjacent to the Meraki switches want to be the RSTP root for VLAN 1 and 999 and are breaking the STP on the uplink. However, all the other tagged VLANs, (fortunately the ones with client data) are behaving perfectly fine and understand that the Meraki is the RSTP root.
VLAN0005
Spanning tree enabled protocol rstp
Root ID Priority 32773
Address 001f.c985.3a80
Cost 3008
Port 49 (GigabitEthernet1/0/49)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 49157 (priority 49152 sys-id-ext 5)
Address a0cf.5b85.6280
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
UplinkFast enabled but inactive in rapid-pvst mode
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Gi1/0/38 Desg FWD 3004 128.38 P2p
Gi1/0/49 Root FWD 3004 128.49 P2p
I'm at a loss. I don't know how we are getting BPDUs coming across with a mismatch over a trunk where VLAN 1 is the native on both sides. Am I missing something obvious? This is a manufacturing site so downtime is hard to come by and means lost $$$.
