T1600G-52TS: CPU rising threshold and network crash

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

T1600G-52TS: CPU rising threshold and network crash

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
T1600G-52TS: CPU rising threshold and network crash
T1600G-52TS: CPU rising threshold and network crash
2019-12-03 08:29:02
Hardware Version: V3
Firmware Version: 3.0.0 Build 20180212 Rel.56119(s)

Hi,

Our customer have a problem in his network which is based on six T1600G-52TS switches.

Some days the switches cpu goes up to 90% and the newtork crashes resulting in a force reboot of all the switches, and the situation returns to normal state.

We have already applied loopback detection, broadcast storm control, removed the STP redundant links but the situation remains the same.


We did some internal tests with three types of switches: T1600G-52TS, T1700G-28TQ, T1700X-16TS.
All three had factory settings.

We first connected the switches to the network and to a PC. Then only a PC, leaving the network disconnected.
In both cases we launched an angry ip scanner on the default range.

We tried to launch the scan both from the PCs connected directly to the switches and from those connected to the network but the result does not change.
In both tests the T1600G-52TS reached 75% of CPU while the T1700G-28TQ and the T1700X-16TS remained on 8-10% of cpu.

 

Is there a problem with T1600G series?

  0      
  0      
#1
Options
2 Reply
Re:T1600G-52TS: CPU rising threshold and network crash
2019-12-04 01:45:18
It seems that T1600G-52TS V3 supports port mirror and it can mirror the packets that pass CPU. Maybe you can use port mirror function and choose the source as CPU, then check what packets pass CPU.
  0  
  0  
#5
Options
Re:T1600G-52TS: CPU rising threshold and network crash
2019-12-04 09:57:39

@MaxVec 

I would directly contact your local support, if you can reproduce it easily. I am not sure something will be fixed on v3, while tplink has v4 already, but you can try. 

  0  
  0  
#6
Options