The Network Layer

Using the tests mapped to this layer, know whether the RHEV hypervisor is available over the network or not, and promptly detect network interfaces that are down, slow, or are using bandwidth excessively. Since the Network test mapped to this layer has already been discussed in the Network Test of the Unix and Windows Servers, let us take a look at the Network - RHEV test alone.

Figure 1 : Figure 2.4: The tests mapped to the Network layer

Network - RHEV Test

This test auto-discovers the network interfaces supposed by the RHEV server and reports the current status and speed of every discovered interface, and the errors encountered by each. This way, the test sheds light on the slow, error-prone, and congested (in terms of level of network traffic) network interfaces on the hypervisor.

Target of the Test: A RHEV Hypervisor

Agent running the test: A remote agent

Output of the test: One set of results for every network interface supported by the RHEV hypervisor being monitored.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.

Host

The host for which the test is to be configured.

RHEL MGR Host,
RHEL MGR Port,
RHEL MGR Domain,
RHEL MGR User
RHEL MGR Password

To auto-discover the VMs on a target RHEV hypervisor and obtain the outside view of the performance of each VM, the eG agent needs to connect to the RHEV Manager that manages the target RHEV hypervisor. To enable the eG agent to obtain the outside view, you need to configure the test with the following:

  • RHEL MGR Host - The IP address/host name of the RHEV manager that the eG agent should connect to.
  • RHEL MGR Port - The port number at which the said RHEV manager listens.
  • RHEL MGR Domain - The domain to which the RHEV manager belongs.
  • RHEL MGR User and RHEL MGR Password - The credentials of a user with read-only access to the Restful API on the RHEV manager. To know how to create a read-only role and assign it to a user, follow the steps detailed in Configuring the eG Agent to use the RESTful APIs on the RHEV Manager to Obtain the “Outside View”.

If the RHEV hypervisor being monitored was discovered via an RHEV manager, then the IP address, port number, domain name, and user credentials of the RHEV manager used for discovery will be automatically displayed against the respective parameters.

If the RHEV hypervisor being monitored was not discovered via an RHEV manager, but you still want to use an RHEV manager for obtaining the outside view, then, you can select any IP address of your choice from the RHEL MGR host list. By default, this list will be populated with the IP addresses/host names of all the RHEV managers that were configured for the purpose of discovering the RHEV hypervisors. If you select an RHEL MGR host from this list, then the corresponding port number, domain name, and user credentials will be automatically displayed against the respective parameters.

On the other hand, if the RHEV manager that you want to use for metrics collection is not available in the RHEL MGR Host list, then, you can configure an RHEV manager on-the-fly by picking the Other option from the RHEL MGR Host list.  An ADD THE RHEV MANAGER DETAILS window will then pop up. Refer to Configuring an RHEV Manager to Use for Monitoring the RHEV Hypervisor to know how to add an RHEV manager using this window. Once the RHEV manager is added, its IP address, port number, domain name and user credentials will be displayed against the corresponding parameters.

Confirm Password

Confirm the RHEL MGR Password by retyping it here.

SSL

If the RHEV manager to which the eG agent should connect is SSL-enabled, then set this flag to Yes. If not, set it to No.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Status

Indicates the current status of this network interface.

 

If the network interface is up and running, then the value of this measure will be Up. On the other hand, if the network interface is currently non-operational, then this measure will report the value Down.

The numeric values that correspond to the measure values mentioned above are as follows:

Measure Value Numeric Value
Up 1
Down 0

Note:

By default, this measure reports one of the Measure Values listed in the table above. The graph of this measure however will represent network interface status using the numeric equivalents - ‘0’ or '1’.

Speed

Indicates the current speed of this network interface.

Mbps

Compare the value of this measure across interfaces to determine the slowest interface.

Network data transmitted

Indicates the rate at which data is transmitted over this network interface.

Mbps

A high rate of incoming and outgoing data could indicate that the network interface is experiencing high levels of network traffic. 

Network data received

Indicates the rate at which data is received over this network interface.

Mbps

Errors during transmission

Indicates the number of errors that occurred when data was transmitted over this interface.

Number

Ideally, the value of both these measures should be 0. Comparing the value of each of these measures across interfaces will introduce you to the error-prone interfaces.

Errors during reception

Indicates the number of errors that occurred when data was received over this interface.

Number