Issue between cisco 2960 100M and 1Gb

[respinfo1]

Hi,

I did have some old 2960 100Mb switches (10 of them)(WS-C2960+48TC-S) and an old 3com 100Mb.
Tree months ago i did buy 3 switches 2960 1Gb (WS-C2960L-48PS-LL) to replace some of the old one.

I remake my vlan, trunk and stuff on my new 1Gb switch and i did begin to have some spikes in my internal networks at this moment (see attachment).

are this switch compatible between them ?

I thought may be PVST and PVST+ or not PVST (for the 3com) might have been not compatible between them. I dunno,i am a noob in matter or PVST, MST,...i just know vlan.
here is the spanning tree summary of these switchs (99.15, 99.16,99.17 are 1Gb , 99.7 is an old 2960 100Mb):

I added a attachment to show you the spikes in my LAN with a ping plotter program.

ip with 0.x are in the vlan 1 (0.63 and 0.64 are a wifi bridge, 0.1 is my main router connected directly on 99.16)
ip with 99.x are in the vlan 99 my mgt vlan.

99.17
Wed Oct 02 2019 11:53:52 GMT+0200 (Ora legale dell’Europa centrale)
===================================================================================
#show spanning-tree summary
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 Edge BPDU Guard Default is disabled
Portfast Edge BPDU Filter Default is disabled
Loopguard Default is disabled
PVST Simulation Default is enabled but inactive in rapid-pvst mode
Bridge Assurance is enabled
UplinkFast is disabled
BackboneFast is disabled
Configured Pathcost method used is short

Name Blocking Listening Learning Forwarding STP Active
---------------------- -------- --------- -------- ---------- ----------
VLAN0001 0 0 0 1 1
VLAN0010 0 0 0 1 1
VLAN0011 0 0 0 1 1
VLAN0040 0 0 0 1 1
VLAN0060 0 0 0 1 1
VLAN0099 0 0 0 1 1
---------------------- -------- --------- -------- ---------- ----------
6 vlans 0 0 0 6 6

--------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------
99.16
Wed Oct 02 2019 11:53:36 GMT+0200 (Ora legale dell’Europa centrale)
===================================================================================
#show spanning-tree summary
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 Edge BPDU Guard Default is disabled
Portfast Edge BPDU Filter Default is disabled
Loopguard Default is disabled
PVST Simulation Default is enabled but inactive in rapid-pvst mode
Bridge Assurance is enabled
UplinkFast is disabled
BackboneFast is disabled
Configured Pathcost method used is short

Name Blocking Listening Learning Forwarding STP Active
---------------------- -------- --------- -------- ---------- ----------
VLAN0001 0 0 0 13 13
VLAN0010 0 0 0 14 14
VLAN0011 0 0 0 12 12
VLAN0040 0 0 0 12 12
VLAN0060 0 0 0 15 15
VLAN0099 0 0 0 11 11
---------------------- -------- --------- -------- ---------- ----------
6 vlans 0 0 0 77 77

--------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------
99.15
Wed Oct 02 2019 11:53:44 GMT+0200 (Ora legale dell’Europa centrale)
===================================================================================
#show spanning-tree summary
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 Edge BPDU Guard Default is disabled
Portfast Edge BPDU Filter Default is disabled
Loopguard Default is disabled
PVST Simulation Default is enabled but inactive in rapid-pvst mode
Bridge Assurance is enabled
UplinkFast is disabled
BackboneFast is disabled
Configured Pathcost method used is short

Name Blocking Listening Learning Forwarding STP Active
---------------------- -------- --------- -------- ---------- ----------
VLAN0001 1 0 0 5 6
VLAN0010 0 0 0 26 26
VLAN0011 0 0 0 5 5
VLAN0040 0 0 0 3 3
VLAN0060 0 0 0 3 3
VLAN0099 0 0 0 3 3
---------------------- -------- --------- -------- ---------- ----------
6 vlans 1 0 0 45 46

------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------
99.7

2960-48p->show spanning-tree summary
Switch is in pvst mode
Root bridge for: VLAN0041
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
EtherChannel misconfig guard is enabled
UplinkFast is disabled
BackboneFast is disabled
Configured Pathcost method used is short

Name Blocking Listening Learning Forwarding STP Active
---------------------- -------- --------- -------- ---------- ----------
VLAN0001 0 0 0 2 2
VLAN0010 0 0 0 27 27
VLAN0011 0 0 0 4 4
VLAN0040 0 0 0 2 2
VLAN0041 0 0 0 2 2
VLAN0060 0 0 0 2 2
VLAN0099 0 0 0 2 2
---------------------- -------- --------- -------- ---------- ----------
7 vlans 0 0 0 41 41
2960-48p>

If this is not a problem how can i sort my problem of spikes ?

The spikes (very high latency) bloked all the network and vlan on them at the same time for 1 to 5-10 seconds sometimes.
I am trying wireshark, it is very difficult to handle for me at the moment

Thanks for helping,

Loïc

[cmarva]

if you believe your problem is with spanning tree, I would do a "sho span vlan x detail" for all vlans and that should point you to where the topo changes are coming from. If there was a major problem you'd most likely see messages in the log, like inconsistent port or something like that. 

[respinfo1]

Hi,

Not seeing any "inconsistent port" in my log but i notice that the 2960 100Mb runs ieee (VLAN0001 is executing the ieee compatible Spanning Tree protocol) and the 2960 1Gb runs RSTP (VLAN0001 is executing the rstp compatible Spanning Tree protocol)

I don't know if they are compatible, after searching it seems they are the same things, RSTP is a form of IEEE (In 2001, the IEEE introduced Rapid Spanning Tree Protocol (RSTP))

log:

------------------------------------------------------------------------
2960 100Mb log:

show span vlan 1 detail

VLAN0001 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 1, address 5cfc.6647.fc00
Configured hello time 2, max age 20, forward delay 15
Current root has priority 32769, address 0025.46ab.f980
Root port is 49 (GigabitEthernet0/1), cost of root path is 23
Topology change flag not set, detected flag not set
Number of topology changes 23 last change occurred 2d03h ago
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300

Port 5 (FastEthernet0/5) of VLAN0001 is designated forwarding
Port path cost 19, Port priority 128, Port Identifier 128.5.
Designated root has priority 32769, address 0025.46ab.f980
Designated bridge has priority 32769, address 5cfc.6647.fc00
Designated port id is 128.5, designated path cost 23
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 397430, received 0

Port 49 (GigabitEthernet0/1) of VLAN0001 is root forwarding
Port path cost 4, Port priority 128, Port Identifier 128.49.
Designated root has priority 32769, address 0025.46ab.f980
Designated bridge has priority 32769, address 7018.a7f6.4f00
Designated port id is 128.39, designated path cost 19
Timers: message age 2, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 34, received 999834

------------------------------------------------------------------------
2960 1Gb log:

Wed Oct 02 2019 14:33:59 GMT+0200 (Ora legale dell’Europa centrale)
===================================================================================
#show span vlan 1 detail
VLAN0001 is executing the rstp compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 1, address 7018.a772.db80
Configured hello time 2, max age 20, forward delay 15, transmit hold-count 6
Current root has priority 32769, address 0025.46ab.f980
Root port is 48 (GigabitEthernet0/48), cost of root path is 23
Topology change flag not set, detected flag not set
Number of topology changes 355 last change occurred 02:38:47 ago
from GigabitEthernet0/48
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300

Port 34 (GigabitEthernet0/34) of VLAN0001 is designated forwarding
Port path cost 4, Port priority 128, Port Identifier 128.34.
Designated root has priority 32769, address 0025.46ab.f980
Designated bridge has priority 32769, address 7018.a772.db80
Designated port id is 128.34, designated path cost 23
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 10
Link type is point-to-point by default
BPDU: sent 570144, received 0

Port 35 (GigabitEthernet0/35) of VLAN0001 is designated forwarding
Port path cost 19, Port priority 128, Port Identifier 128.35.
Designated root has priority 32769, address 0025.46ab.f980
Designated bridge has priority 32769, address 7018.a772.db80
Designated port id is 128.35, designated path cost 23
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 53099, received 0

Port 36 (GigabitEthernet0/36) of VLAN0001 is designated forwarding
Port path cost 4, Port priority 128, Port Identifier 128.36.
Designated root has priority 32769, address 0025.46ab.f980
Designated bridge has priority 32769, address 7018.a772.db80
Designated port id is 128.36, designated path cost 23
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 4801, received 0

Port 44 (GigabitEthernet0/44) of VLAN0001 is designated forwarding
Port path cost 4, Port priority 128, Port Identifier 128.44.
Designated root has priority 32769, address 0025.46ab.f980
Designated bridge has priority 32769, address 7018.a772.db80
Designated port id is 128.44, designated path cost 23
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 10
Link type is point-to-point by default
BPDU: sent 570118, received 0

Port 45 (GigabitEthernet0/45) of VLAN0001 is designated forwarding
Port path cost 4, Port priority 128, Port Identifier 128.45.
Designated root has priority 32769, address 0025.46ab.f980
Designated bridge has priority 32769, address 7018.a772.db80
Designated port id is 128.45, designated path cost 23
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 10
Link type is point-to-point by default
BPDU: sent 570120, received 0

Port 48 (GigabitEthernet0/48) of VLAN0001 is root forwarding
Port path cost 4, Port priority 128, Port Identifier 128.48.
Designated root has priority 32769, address 0025.46ab.f980
Designated bridge has priority 32769, address 7018.a7f6.4f00
Designated port id is 128.33, designated path cost 19
Timers: message age 16, forward delay 0, hold 0
Number of transitions to forwarding state: 2
Link type is point-to-point by default
BPDU: sent 354, received 568441