We have a pair of ICX 6610 stacked and both of them are running version 08.0.30tT7f3 (latest).
We are facing a very strange behavior with these boxes. The latency for all IPs configured in it, when we ping, returns with high latency even locally.
Below you can find two examples of the problem that we are facing.
########################## marceloaraujo@CT-REDES-02[19:55][~]: ping 126.96.36.199 PING 188.8.131.52 (184.108.40.206) 56(84) bytes of data. 64 bytes from 220.127.116.11: icmp_seq=1 ttl=60 time=90.6 ms 64 bytes from 18.104.22.168: icmp_seq=2 ttl=60 time=230 ms 64 bytes from 22.214.171.124: icmp_seq=3 ttl=60 time=1.69 ms 64 bytes from 126.96.36.199: icmp_seq=4 ttl=60 time=3.59 ms 64 bytes from 188.8.131.52: icmp_seq=5 ttl=60 time=0.753 ms
PING 184.108.40.206 (220.127.116.11) 56(84) bytes of data. 64 bytes from 18.104.22.168: icmp_seq=1 ttl=60 time=1.00 ms 64 bytes from 22.214.171.124: icmp_seq=2 ttl=60 time=1.49 ms 64 bytes from 126.96.36.199: icmp_seq=3 ttl=60 time=121 ms 64 bytes from 188.8.131.52: icmp_seq=4 ttl=60 time=106 ms
Another strange thing is the CPU usage. The 1 second statistic show us spikes, may be this is the reason of latency.
I wouldn't test latency by pinging the ICX itself as we do not prioritize replying to ping. Do you still see latency spikes pinging through the ICX? With that said, if you are seeing CPU spikes, that could certainly lead to issues if the ICX is overwhelmed momentarily. I would search for any kind of control traffic that could be hitting the CPU or any logs that might show some kind of trigger at moment of CPU spike. Your best best may be to open a support case and have our TAC team try to help track it down.
Ben Beck, RCNA, RCNI, Principal Technical Support Engineer support.ruckuswireless.com/contact-us
Same issue with a stack of two ICX6610s. Happened after crypto key generate for SSH use... Showing CPU tasks before reloading appl and tmr were the only ones causing the high CPU. Basically all network traffic was dropping... Uptime was less than 14 days on the stack.
Since the only change I made was generating the crypto keys for SSH, I zeroize'd that out... Similar network load testing and it's not happening now. Not sure what the deal is. Anyone else have this issue or have a resolution?
Copyright (c) 1996-2016 Brocade Communications Systems, Inc. All rights reserved.
UNIT 1: compiled on Feb 13 2019 at 18:30:50 labeled as FCXR08030t
(10545807 bytes) from Primary FCXR08030t.bin
SW: Version 08.0.30tT7f3
UNIT 2: compiled on Feb 13 2019 at 18:30:50 labeled as FCXR08030t