Reporting › Troubleshooting › SNMP Queries Using Investigations › Situation 1-- Server Incident › Analyze the SNMP Performance Data › Server Response Time or Server Connection Time Incidents Analysis

Server Response Time or Server Connection Time Incidents Analysis

For Server Response Time or Server Connection Time incidents, the server is slower to respond than normal to requests by the clients.

CPU

Review the CPU utilization for the server. If it is high, near 70 to 100 percent, then check the processes consuming the CPU. If there is a process consuming all the CPU, it is slower to respond. This might be caused by too many concurrent users or a large CPU load by the process. To reduce CPU utilization, you can restart the process. This would terminate any work done by the users. If the process is non-critical, stop the process. If the CPU utilization is low, then CPU is not an issue with this incident.

Memory

Review the memory utilization for the server; if it exceeds 70 percent, check the processes consuming memory. Slow response might be caused by too many concurrent users or a memory leak with the process. To reduce memory utilization, restart the process. If the process is non-critical, stop the process. If both CPU and memory are low, then typical hardware constraints are not an issue.

Interface Statistics

If both the memory and the CPU utilization are fine for the server, then it is possible the NICs are experiencing issues making the server response appear slower. Check the Interface statistics. First ensure that all the interfaces are listed properly and are connected. Verify that both the interface speeds and the IP Addresses for the NICs are reported correctly. Duplex mismatch errors would inhibit the ability of the interface to send and receive data. Duplex mismatch errors, cable problems, or CRC errors would indicate a problem with the NIC and its connectivity through the discards and errors fields.

Disk Space

Check the capacity of the drives. Servers slow down because of limited capacity for the data. If the server is out of disk space, its ability to process data is degraded. Additional other considerations require access to the server to check for fragmentation or I/O errors with bad segments. If any given drive has less than 10-15% free space, this can also be a problem for applications with large working data sets.