WS-12-DC issue

[kdsnetworks]

Hi All,
We got a new WS-12-DC firmware 1.5.0 (We got new one to get higher power on the 24v bus)
Any how we had absolutely no issues what so ever running the previous version for last 3 years. We needed a newer version as Prisms AP take a bit more power etc.
Now we have a new problem. When pinging the switch it have a lot of packets drops while the rest of the devices connected via this switch are semi ok ... however, occasionally once in a while all network forwarding would stop for like 1 to 2 minutes. STP is off.
At first event a log did show an excessive pause frames on multiple ports while the packets stop being forwarded. Than we did shutdown flow control on all ports and now we get this crazy unstable pings to the switch as well as occasional packet forwarding pause on all of the ports.

Also what is more wired is that pinging any device with in the switch using the Netonix GUI produces this:

PING 192.168.20.50 (192.168.20.50): 56 data bytes
64 bytes from 192.168.20.50: seq=0 ttl=64 time=0.737 ms
64 bytes from 192.168.20.50: seq=1 ttl=64 time=0.684 ms
64 bytes from 192.168.20.50: seq=2 ttl=64 time=0.671 ms
64 bytes from 192.168.20.50: seq=3 ttl=64 time=5462.271 ms
64 bytes from 192.168.20.50: seq=4 ttl=64 time=4465.043 ms
64 bytes from 192.168.20.50: seq=5 ttl=64 time=3464.342 ms
64 bytes from 192.168.20.50: seq=8 ttl=64 time=463.285 ms
64 bytes from 192.168.20.50: seq=9 ttl=64 time=0.665 ms
64 bytes from 192.168.20.50: seq=10 ttl=64 time=0.631 ms
64 bytes from 192.168.20.50: seq=11 ttl=64 time=0.591 ms
64 bytes from 192.168.20.50: seq=12 ttl=64 time=0.638 ms
64 bytes from 192.168.20.50: seq=13 ttl=64 time=0.602 ms
64 bytes from 192.168.20.50: seq=14 ttl=64 time=4394.215 ms
64 bytes from 192.168.20.50: seq=15 ttl=64 time=3396.410 ms
64 bytes from 192.168.20.50: seq=16 ttl=64 time=2396.305 ms
64 bytes from 192.168.20.50: seq=17 ttl=64 time=1395.985 ms
64 bytes from 192.168.20.50: seq=18 ttl=64 time=382.626 ms
64 bytes from 192.168.20.50: seq=19 ttl=64 time=0.584 ms

However pinging the same device from any other device that is connected to the switch is totally normal.
So something within the switch is acting up.


Thanks for any input.

R