Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference

1.4.4 Example of monitoring the network

By monitoring network information, you can check the status of response speeds for system-provided functions. Also, continuous monitoring of the network, such as of the amount of data transfer in the network, can assist in evaluating the network configuration and planning for future expansion.

Organization of this subsection

(1) Overview of network monitoring

(2) Example of a monitoring template for monitoring the network

(1) Overview of network monitoring

Identifying a bottleneck in the network requires examination of various factors, such as hardware, client operations, and data transfer rates between servers and clients.

PFM - RM for Platform provides alarms and reports, such as the Network Received alarm and the Network Data report. To obtain more detailed information on network performance, you must monitor various aspects of the network.

The following table lists and describes the records and fields that are used for monitoring the network.

Table 1-10 Records and fields used for network monitoring

No. Record Field Description of value Interpretation of value

1 PI_NET Total Bytes/sec Amount of data transferred (per second) If NIC is always used to transfer data and this value is often equal to or less than the threshold value, NIC might be causing the bottleneck. When this value is typically greater than the threshold value, a large amount data can be transferred successfully.

2 Rcvd Bytes/sec Amount of data received (per second) If NIC is always used to receive data and this value is often equal to or less than the threshold value, NIC might be causing the bottleneck. When this value is typically greater than the threshold value, a large amount data can be received successfully.

3 Sent Bytes/sec Amount of data sent (per second) If NIC is always used to send data and this value is often equal to or less than the threshold value, NIC might be causing the bottleneck. When this value is typically greater than the threshold value, a large amount data can be sent successfully.

No.	Record	Field	Description of value	Interpretation of value
1	PI_NET	Total Bytes/sec	Amount of data transferred (per second)	If NIC is always used to transfer data and this value is often equal to or less than the threshold value, NIC might be causing the bottleneck. When this value is typically greater than the threshold value, a large amount data can be transferred successfully.
2	Rcvd Bytes/sec	Amount of data received (per second)	If NIC is always used to receive data and this value is often equal to or less than the threshold value, NIC might be causing the bottleneck. When this value is typically greater than the threshold value, a large amount data can be received successfully.
3	Sent Bytes/sec	Amount of data sent (per second)	If NIC is always used to send data and this value is often equal to or less than the threshold value, NIC might be causing the bottleneck. When this value is typically greater than the threshold value, a large amount data can be sent successfully.

(2) Example of a monitoring template for monitoring the network

This subsection describes an example of alarms and reports that are provided as a monitoring template for monitoring the network.

PFM - RM for Platform provides alarms and reports, such as the Network Received alarm and the Network Data report.

(a) Alarms

The following table lists and describes the network-related alarms.

Table 1-11 Examples of alarms related to network monitoring

No. Alarm Record Field Abnormal condition Warning condition Interpretation of value

1 Network Received PI_NET Rcvd Bytes/sec >= 50000^#1 >= 50000^#2 When the amount of data received per second exceeds about 50% of the NIC bandwidth, the system treats it as the warning or abnormal status.
When this value becomes greater than the threshold value set in the warning or abnormal condition, you need to take appropriate action, such as upgrading NIC or the physical network.

#1

Set a value that is about 70% of the NIC bandwidth.

#2

Set a value that is about 50% of the NIC bandwidth.

(b) Reports

The following table lists and describes the network-related reports.

Table 1-12 Examples of reports related to network monitoring

No. Report name Information displayed in the report

1 Network Data Displays the status of communication between networks.

No.	Alarm	Record	Field	Abnormal condition	Warning condition	Interpretation of value
1	Network Received	PI_NET	Rcvd Bytes/sec	>= 50000^#1	>= 50000^#2	When the amount of data received per second exceeds about 50% of the NIC bandwidth, the system treats it as the warning or abnormal status. When this value becomes greater than the threshold value set in the warning or abnormal condition, you need to take appropriate action, such as upgrading NIC or the physical network.

No.	Report name	Information displayed in the report
1	Network Data	Displays the status of communication between networks.

[Contents][Back][Next]

[Trademarks]