3.1.4 Network monitoring examples

This subsection explains how to monitor network performance.

Organization of this subsection

(1) Overview

You can monitor network information to check the response time of system functionality.

Continuous monitoring of network data traffic allows you to plan network reconfiguration or expansion.

The following table lists and describes the principal records and fields related to monitoring of the network performance.

Table 3‒6: Principal fields related to network monitoring
Record	Field	Description (example)
`PI_NETI`	`Bytes Total/sec`	The amount of data sent and received per second. In an environment that always uses an NIC, if the value of this field frequently falls below the threshold (the larger the value, the better), the NIC might be a bottleneck.^#
`PI_NETI`	`Bytes Sent/sec`	The amount of data sent per second. In an environment that always uses an NIC, if the value of this field frequently falls below the threshold (the larger the value, the better), the NIC might be a bottleneck.^#
`PI`	`Bytes Rcvd/sec`	The amount of data received per second. Compare the number of bytes that the server receives from the network to the total bandwidth of the NIC (the maximum amount of data that can be transferred per unit of time over the network). If the number of bytes is equal to or greater than 50% of the total bandwidth, the network connection might be a bottleneck.

#: If the value of this field is large, a large amount of data has been transferred successfully.

You can use the Network Received alarm provided by the monitoring templates to monitor the bandwidth of a network interface card.

You can monitor network traffic by using an alarm to monitor the bandwidth of a network interface card (NIC).

If the data traffic continues to be at or above the threshold, you might need to upgrade the NIC or the physical network.