AimBetter communicates every 5 seconds with the server via a ping command. The success of the ping and the time taken (latency) are monitored to assess the health of network connections to the server. Note that this metric deals only with communications between the server and AimBetter, not between the server and users
The server is not responding or missing packets.
Lost packets alert indicates that communications with the SQL server either get no response or only partial response. As well as delays experienced by users, there is a possible loss of data. If the server is not responding, all traffic between the user and the server will halt. If missing packets, there will be an effect on application functionality and performance. The main effect on performance comes from packet retries which can significantly load the level of network traffic. As well, queries will have to wait for data, thus increasing the possibility of blocks, and deadlocks, and will elevate page file activity as buffer pool space is locked.
Expected behavior :
The server should respond to every ping. AimBetter will raise an alert if 12 pings in sequence fail
1- Network load Priority: Medium
When the volume of network traffic exceeds the capacity of the network infrastructure to handle it, the network load might be high. When this happens, packets may be dropped or lost in transit.
Check current traffic and which applications use most of it.
- Using a network monitoring tool, you should check how much traffic flows through your network and which applications or devices use the most bandwidth. Take into account that most monitoring tools help pinpoint when a problem starts, with which you can’t compare time frames.
- Review your network logs to see if there are any unusual patterns. This might take considerable time.
Recommended action :
Check network traffic loads with a network analyzer. If possible, move high-volume traffic (e.g, remote storage, backups) onto a secondary network.
2- Incorrect network settings Priority: Medium
Look for our network utilization article regarding inefficient network structure.
3- Large data transfer load in the network. Priority: Medium
When data is transmitted across a network, it is broken down into packets that are transmitted individually and then reassembled at the destination. If the volume of data transfer is too large, it can potentially result in packet loss.
Actively follow the data transmission amount in parallel to packet loss.
- Using a network monitoring tool, you should check how much traffic flows through your network. Take into account that most monitoring tools help pinpoint when a problem starts, with which you can’t compare time frames.
- Measure the amount of bandwidth being used during the data transfer. When it’s large, it might cause packet loss. You probably have to use a monitoring tool for that.
- Monitor and analyze the data transfer load in parallel to packet loss recurrence. You can do an initiated test for that issue in order to identify the maximum data transfer rate possible using the network. You probably will need a help of an expert IT professional.
Recommended action :
If possible, move high-volume traffic (e.g., remote storage, backups) onto a secondary network, or reschedule to periods of low SQL demand
In addition, you should increase the network bandwidth and correction mechanisms to optimize the transfer process.
4- The connection is lost Priority: Medium
Once the connection is lost, it will immediately cause a packet loss. In cases of complete disconnection, when 12 packets have been lost in succession.
It might happen because of a network failure (router, bridge, other hardware) or a server crash /power-off.
Check the physical environment. Look for network failures or check for a shutdown of the server.
- Look for network latency or failed hardware. You can read more in our Network Latency article.
- If the firewall or security settings are too restrictive, they can block network traffic, causing lost connections and packet loss. You will need the help of an expert IT to check it.
- Check if the server is up. For that, you must have the correct permissions.
Recommended action :
In case of a server crash, restart and investigate the cause of the crash. In case of network failure, replace faulty components and restore network functionality.