Using System Monitor and Network Monitor, Chad sees that server S1 is exhibiting connectivity problems. Chad notices that S1 has approximately 4 MB of available memory and average CPU utilization is running at 88 percent.
When Chad investigates the Network Monitor capture, he notices that some network packets sent to S1 during the capture have not been captured. What should Chad do to ensure that the impact of monitoring on S1 is reduced and that all packets sent to the computer are captured?
Explanation
Answer - A - To ensure that the impact of monitoring on S1 is reduced and that all packets sent to the computer are captured, Chad should Run Network Monitor in the dedicated capture mode.
Key takeaway: While using Network Monitor, frames captured from the network are copied to the capture buffer, a reserved storage area in the memory. When the capture buffer overflows, each new frame replaces the oldest frame in the buffer. The elements that determine how quickly the capture buffer will be filled are Capture buffer size, Frame size, Capture filter, and Volume of network traffic.
In addition to customizing Capture buffer size and Frame size to save Capture Buffer space, you can also put Network Monitor into dedicated Capture mode. This mode does not display or update Capture window statistics, reducing the load on the CPU and thereby reducing the chance that packets will be dropped.
