Proactive Network Monitoring: Threshold-Crossing Metrics for Problem Identification

Threshold-Crossing Metrics for Problem Identification

Question

As part of a new network design, you are helping the Network Management Team to develop a proactive report to identify places in the network where problems may happen.

The network management tool can poll the network devices only via SNMP GET operations.

Which two threshold-crossing metrics should you include in this report? (Choose two.)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E. F.

BF.

The two threshold-crossing metrics that should be included in the proactive report are CPU utilization and link bandwidth utilization.

  1. CPU Utilization: High CPU utilization can be an indication of various network problems such as routing protocol flaps, high traffic volume, or even an attack. By monitoring the CPU utilization of network devices, the network management team can proactively identify potential problems before they occur. The SNMP GET operation can be used to retrieve the CPU utilization of network devices.

  2. Link Bandwidth Utilization: Link bandwidth utilization is a critical metric to monitor in a network, as it can affect the performance of applications and services that rely on the network. By monitoring the link bandwidth utilization, the network management team can identify congested links and take proactive steps to avoid potential issues. The SNMP GET operation can be used to retrieve the link bandwidth utilization of network devices.

The other options listed are not as relevant to network performance and do not provide sufficient information to proactively identify potential problems. Packet loss and IP reachability may indicate network problems, but they are not necessarily threshold-crossing metrics. Heat dissipation and energy consumption are more related to the physical environment of the network devices and are not directly relevant to network performance.