Add VLAN to trunk causes switch to drop

[Terren_Crider]

Hi all, I've got two switches separated by about 7 miles of fiber and an Internet link at each site. I need a certain number of VLANs to extend between the sites for HA purposes. VLANs: tagged 243, 923-925, 927, 1000, untagged 4040 All of these VLANs span the trunk no problem except for 927. When I apply 927 the distant switch drops. When I remove 927, it comes back. Spantree is applied and enabled at the HA site, but not the main site. Where do I need to look to solve this problem?

[Terren_Crider]

I've opened a GTAC case. The Avaya MAC is only showing up on one uplink interface and a disabled port with nothing connected.

[Terren_Crider]

Update: one of the MACs that was in the Multiple BPDU message belongs to an Avaya device. Compass shows me that MAC on the uplink port between the main site switch and another switch with the Address Type MAC and Filter ID 927. Also, this MAC is on tg.11.3 of the HA site switch with the Address Type BPDU, Filter ID 927, and VLAN ID 927.

[Jeremy_Gibbs]

Does this number keep going up:

Disputed BPDU Count - 2209

[Terren_Crider]

2296 this morning.

[Terren_Crider]

I administratively set the second interface on the HA site switch to disable. Then I applied 927 to the trunk to the main interface with the same result. I feel like this isn't necessarily a spantree problem (it still could be). Here's the log buffer for the event: <165>Apr 4 15:36:11 10.40.40.253 LinkTrap[11]Interface tg.11.2 is Down. (This is when I admin down'd the port) <165>Apr 4 15:36:40 10.40.40.253 Spantree[11]Receive Event: Multiple BPDU sources received on Port = tg.11.1, BPDU Bridge MAC = cc:f9:54:27:0e:3d Port = 2309 Prior Bridge MAC = 20:b3:99:57:d4:e8 Port = 338 <165>Apr 4 15:36:40 10.40.40.253 LinkTrap[11]Interface vlan.0.1000 is Down. <165>Apr 4 15:36:40 10.40.40.253 LinkTrap[11]Interface vlan.0.4040 is Down. <165>Apr 4 15:36:40 10.40.40.253 OSPF[11]Router global: OSPF: NBR 10.40.40.251 transitioned from FULL to DOWN <165>Apr 4 15:36:40 10.40.40.253 OSPF[11]Router global: OSPF: NBR 10.40.40.252 transitioned from FULL to DOWN <164>Apr 4 15:36:40 10.40.40.253 OSPF[11]Router global: OSPF: invalid route discarded - dest 127.0.0.0 <164>Apr 4 15:36:41 10.40.40.253 Emanate[11.SNMPagent]Sr_send_inform: invalid transport <165>Apr 4 15:36:53 10.40.40.253 LinkTrap[11]Interface vlan.0.1000 is Up. <165>Apr 4 15:36:53 10.40.40.253 LinkTrap[11]Interface vlan.0.4040 is Up. <164>Apr 4 15:36:54 10.40.40.253 OSPF[11]Router global: OSPF: Packet dropped - vlan.0.4040 cfg error - src ip 10.40.40.251 - BAD PACKET <165>Apr 4 15:36:55 10.40.40.253 OSPF[11]Router global: OSPF: NBR 10.40.40.252 transitioned from LOADING to FULL <165>Apr 4 15:37:03 10.40.40.253 OSPF[11]Router global: OSPF: NBR 10.40.40.251 transitioned from LOADING to FULL <164>Apr 4 15:37:08 10.40.40.253 OSPF[11]Router global: OSPF: invalid route discarded - dest 127.0.0.0 <165>Apr 4 15:37:09 10.40.40.253 Spantree[11]Multiple BPDU sources received condition has been cleared for Port = tg.11.1