High ping when managing a TZ300 appliance

brunogabriel

Basiclly there is no traffic in the network.

Ping goes to 600ms when I am logged into administrator.

There is any logs I could look up for diagnostics?

CPU/RAM are stable at 60%.

shiprasahu93

Hello @brunogabriel,

While you are performing ping tests are you connected directly to the SonicWall interface or through a switch?

What is the firmware on the firewall and since when are you facing this issue? Did you make any firmware upgrade or configuration changes after which you started having this problem?

Here are a few KB articles that should be helpful.

https://www.sonicwall.com/support/knowledge-base/troubleshooting-network-throughput-latency-and-bandwidth-issues-with-a-sonicwall-utm/170504563958424/

https://www.sonicwall.com/support/knowledge-base/core-cpu-diagnostics-tools-in-sonicwall-appliances/170502966601815/

https://www.sonicwall.com/support/knowledge-base/how-can-i-troubleshoot-core-0-spikes-or-high-utilization/170503645180339/

Thanks!

brunogabriel

https://community.sonicwall.com/technology-and-support/discussion/comment/2031#Comment_2031

@shiprasahu93 Thought a switch.

The problem started from nothing actually.

It happened since firmware 6.5.3.x, no I'm on 6.5.4.6.

shiprasahu93

@brunogabriel,

I would suggest testing once by directly plugging a computer to the SonicWall's X0 interface. To avoid any port issues, please configure a static IP on any unused port and test from there as well by connecting a computer directly.

Also, are you seeing this high latency just for internet traffic like while pinging 8.8.8.8 or even the firewall IP address?

Thanks!

brunogabriel

Just to the firewall IP address.

shiprasahu93

@brunogabriel,

Were you able to test this on X0 or any other free interface by connecting a computer directly to the interface?

Thanks!

brunogabriel

Not yet, as soon as possible, I will test it.

shiprasahu93

Sure, keep us posted!

brunogabriel

Running iPerf on the network LAN -> LAN, it could be a pysical problem? @shiprasahu93

shiprasahu93

@brunogabriel,

I wanted to remove the switch from the network to eliminate such issues. Is it possible that there is some kind of multicast/broadcast storm going on the LAN switch?

Were you not able to test with directly connecting to the SonicWall?

Thanks!

brunogabriel

https://community.sonicwall.com/technology-and-support/discussion/comment/2209#Comment_2209

Sorry! I did test directly thought WAN, same behavior.

I'm testing to see if there is a higher broadcast, there is any KB for that?

shiprasahu93

I was actually talking about the storm on the switch. But you can check the interface statistics under MANAGE | Network | Interfaces to see if it looks extremely high for X0.

Thanks!

brunogabriel

Hasan

Hi,

I am facing a similar problem. When we ping the LAN interface of Sonicwall (Nsa 2650), I am getting a latency jump. Usually, the LAN network should have latency <1 m/s. But in our case, the latency jumps from 0 to 45~86 m/s. Due to this our peer-to-peer connection users facing slowness issues with 1Gbps pipe. We connected the laptop directly to the LAN port and we have the similar issue.

64 bytes from 192.168.189.2: icmp_seq=31 ttl=63 time=44.4 ms

64 bytes from 192.168.189.2: icmp_seq=32 ttl=63 time=1.06 ms

64 bytes from 192.168.189.2: icmp_seq=33 ttl=63 time=0.208 ms

64 bytes from 192.168.189.2: icmp_seq=34 ttl=63 time=5.82 ms

64 bytes from 192.168.189.2: icmp_seq=35 ttl=63 time=0.223 ms

64 bytes from 192.168.189.2: icmp_seq=36 ttl=63 time=0.292 ms

64 bytes from 192.168.189.2: icmp_seq=37 ttl=63 time=13.8 ms

64 bytes from 192.168.189.2: icmp_seq=38 ttl=63 time=0.265 ms

64 bytes from 192.168.189.2: icmp_seq=39 ttl=63 time=0.214 ms

64 bytes from 192.168.189.2: icmp_seq=40 ttl=63 time=0.300 ms

64 bytes from 192.168.189.2: icmp_seq=41 ttl=63 time=32.7 ms

64 bytes from 192.168.189.2: icmp_seq=42 ttl=63 time=0.327 ms

64 bytes from 192.168.189.2: icmp_seq=43 ttl=63 time=0.220 ms

64 bytes from 192.168.189.2: icmp_seq=44 ttl=63 time=48.3 ms

64 bytes from 192.168.189.2: icmp_seq=45 ttl=63 time=0.202 ms

64 bytes from 192.168.189.2: icmp_seq=46 ttl=63 time=1.75 ms

64 bytes from 192.168.189.2: icmp_seq=47 ttl=63 time=23.3 ms

64 bytes from 192.168.189.2: icmp_seq=48 ttl=63 time=0.394 ms

64 bytes from 192.168.189.2: icmp_seq=49 ttl=63 time=0.237 ms

64 bytes from 192.168.189.2: icmp_seq=50 ttl=63 time=20.1 ms

64 bytes from 192.168.189.2: icmp_seq=51 ttl=63 time=0.256 ms

64 bytes from 192.168.189.2: icmp_seq=52 ttl=63 time=0.376 ms

64 bytes from 192.168.189.2: icmp_seq=53 ttl=63 time=10.0 ms

64 bytes from 192.168.189.2: icmp_seq=54 ttl=63 time=2.38 ms

64 bytes from 192.168.189.2: icmp_seq=55 ttl=63 time=1.39 ms

Please let me know if someone encountered this issue and found the solution.

Best, Hasan

Arkwright

What is happening on the firewall at this time? Check CPU and interface graphs whilst pinging.

TKWITS

@Hasan Are you running the latest firmware?

kalu25

https://community.sonicwall.com/technology-and-support/discussion/comment/2212#Comment_2212

The comment suggests analyzing interface stats in MANAGE | Network | Interfaces for excessive activity on X0 to address the network storm issue on the switch. Monitoring these statistical data can assist in identifying and mitigating potential problems. It's a practical way to ensure network efficiency and cope with disruptions caused by abnormal activity. thank you mam...