11-25-2024 01:20 PM - edited 11-25-2024 01:23 PM
Hello,
I'm having some troubles with rapid-pvst as randomly some switches are being isolated from the rest of the network for a specific singular VLAN.
The network segment that is interested by the problem is composed by a switch "A" connected to a core switch and a few peripheric switches across the site. There are a lot of VLANS configured, but I'm finding out since a few weeks that sometimes the periferic switches become "isolated" for a specific VLAN that we will call "VLAN 2". Every time I go to search the reason of that I find out that switch "A" blocked the link towards the switch (and the switch have the other ports blocked by itself or the other switches, so VLAN 2 stops communicating with the rest of the network). Initially I was just putting the interface on switch "A" manually in a forwarding state or rebooting the isolated switch to solve immediately the problem (so the link from the peripherical switch and switch "A" will stop to be blocked for VLAN 2 by switch "A"), but now a solution is needed.
The error on the switch "A" is: "Received BPDU with inconsistent peer vlan id 2 on Port-channel3 VLAN4"
Then, the switch blocks the VLAN 2 and 4 on the port channel3. Portchannel3 is the channel that goes towards the peripherical switch, that we can call switch "B". The logs are:
"Blocking Port-channel3 on 2. Inconsistent peer vlan."
"Blocking Port-channel3 on 4. Inconsistent peer vlan."
The port channel2 on switch "A" is in reality one singular port, and the switch "B" on the other end of the cable also has a port channel composed by only one port. This applies to this specific switch connection and all the other switch links towards switch "A".
Documenting myself I found out that it can be a native VLAN mismatch, but there isn't a native VLAN set on the ports, so they are using the default native VLAN. Then checking the configuration I saw that both switches allow on the trunk all of the existing VLANs of the network, no errors are displayed on the ports, the trunk in general is correctly configured.
The problem is always with VLAN 2 and VLAN 4, so the log is always the one reported previously, even if the network has a lot of other VLANS. Also the fact that different switches has the same problem was making me think that this is a problem that resides on switch "A", but I cannot find any helpful log.
All the switches are Cisco and the problem is manifesting randomly since a few weeks maybe once a month on a random switch. No changes were made to the network when the problem manifested itself for the first time, also in the previous month the configuration was the same as always. The switches are not rebooting or having links that change status before the appearing of the log "Received BPDU with inconsistent peer vlan id 2 on Port-channel3 VLAN4" so I'm at a point that thinking about something else is becoming difficult. I don't have physical access to the switches and my capabilities of asking for tests is limited, so if there is some check that I can do by myself that will not cause any disruption I can proceed, otherwise I would need to collect logs or evidence first to justify any tests. Could You kindly give me some suggestions?
Thanks
Solved! Go to Solution.
12-05-2024 09:57 AM
Solved! We had an RSPAN session that was messing with the VLAN ID of BPDUs, removing the RSPAN session (source: VLAN 2, destination: VLAN 4) from all the switches fixed the problem
11-25-2024 01:49 PM
Which IOS is it?
11-25-2024 11:45 PM
Hello,
the peripherical switch has Cisco IOS Software [Denali], Catalyst L3 Switch Software (CAT3K_CAA-UNIVERSALK9- M), Version 16.03.11, RELEASE SOFTWARE (fc2), switch "A" has Cisco IOS Software, s2t54 Software (s2t54-ADVENTERPRISEK9-M), Version 15.5(1)SY8
Thank You
11-25-2024 11:47 PM
Check
1- mode of stp in both SW
2- native vlan in trunk
MHM
11-26-2024 12:58 AM
checked, also on the switches that had problems in the last weeks, the mode is the same for all and the native VLAN used 1
11-26-2024 01:19 AM
can I see show spanning summary from both SW
MHM
11-26-2024 01:27 AM
sure
switch "A":
Switch is in rapid-pvst mode
Root bridge for: VLAN19
EtherChannel misconfig guard is enabled
Extended system ID is enabled
Portfast Default is disabled
Portfast Edge BPDU Guard Default is disabled
Portfast Edge BPDU Filter Default is disabled
Loopguard Default is disabled
Platform PVST Simulation is enabled
PVST Simulation Default is enabled but inactive in rapid-pvst mode
Bridge Assurance is enabled
UplinkFast is disabled
BackboneFast is disabled
Pathcost method used is short
switch "B":
Switch is in rapid-pvst mode
Root bridge for: none
EtherChannel misconfig guard is enabled
Extended system ID is enabled
Portfast Default is disabled
PortFast BPDU Guard Default is disabled
Portfast BPDU Filter Default is disabled
Loopguard Default is disabled
UplinkFast is disabled
BackboneFast is disabled
Configured Pathcost method used is short
11-26-2024 01:33 AM - edited 11-27-2024 10:42 AM
Platform PVST Simulation is enabled <<- this is issue here
you connect SW-B to other SW that run MST
and PVST simulation is enable this make other network have issue
can you check VLAN2 and VLAN4 root is SW-A/B or SW that run MST
MHM
11-26-2024 01:41 AM
Hello @MHM Cisco World
I dont see any no mention of MST, PVST simulation is only applicable between MST and on MST domains
11-26-2024 01:43 AM
check my comment Friend
MHM
11-26-2024 01:52 AM
the root switch for vlan 2 and 4 is the core switch of the network, it is connected to switch "A" and looking at the show spanning summary I can see that is in rapid-pvst mode and PVST Simulation Default is enabled but inactive in rapid-pvst mode
Thanks
11-27-2024 10:42 AM
you need to see whole picture
this issue happened in between SW-A and other SW not between SW-A and SW-B but it effect is seen in SW-B
MHM
11-26-2024 01:09 AM
I read similar behavior here in the community describded as a bug and the solution was put the Native vlan manually on the switch trunk config.
11-26-2024 01:22 AM
thank You, this will surely be a thing that we will try to do
11-26-2024 12:54 AM
Hello
Make sure if you are manually pruning on the stp interconnects they have parity on both side of the connections and you do NOT have either native vlan mis-match ( as as already stated) or have disabled stp for any particular vlan on some of your switches
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide