VM Details - Acropolis Test

This test monitors the amount of the physical server's resources that each guest managed by a Nutanix prism is taking up. Using the metrics reported by this test, administrators can determine which virtual guest is taking up most CPU, which guest is generating the most network traffic, which guest is over-utilizing memory, and which guest is eroding disk space.

Target of the test : A Nutanix Acropolis server

Agent deploying the test : A remote agent

Outputs of the test : One set of results for every VM on the Nutanix Acropolis server monitored.

Configurable parameters for the test
  1. Test period - How often should the test be executed
  2. Host - The host for which the test is to be configured.
  3. port - The port at which the specified host listens. By default, this is NULL.
  4. Prism IP - If the eG manager had discovered the target Nutanix Acropolis server by connecting to the Nutanix Prism, then the IP address of the Nutanix Prism server used for discovering this Nutanix Acropolis server would be automatically displayed against the prism ip parameter; similarly, the prism user and prism password text boxes will be automatically populated with the Prism user credentials, using which Nutanix Acropolis discovery was performed.

     

    If this Nutanix Acropolis server has not been discovered using the Nutanix Prism, but you still want to monitor the Nutanix Acropolis server via the Prism, then select the IP address of the Prism server that you wish to use for monitoring the Nutanix Acropolis server from the prism ip list. By default, this list is populated with the IP address of all Nutanix Prism hosts that were added to the eG Enterprise system at the time of discovery. Upon selection, the PRISM user and prism password that were pre-configured for that Nutanix Prism will be automatically displayed against the respective text boxes.

     

    On the other hand, if the IP address of the Prism server of interest to you is not available in the list, then, you can add the details of the Prism server on-the-fly, by selecting the Other option from the prism ip list. This will invoke the MANAGER DISCOVERY - VIRTUAL PLATFORM SETTINGS page. Refer to the Configuring eG Enterprise to Monitor Nutanix Acropolis topic for details on how to use this page.

  5. Prism user and prism password - If the eG manager had discovered the target Nutanix Acropolis server by connecting to the Nutanix Prism, then the IP address of the Nutanix Prism server used for discovering this Nutanix Acropolis server would be automatically displayed against the prism ip parameter; similarly, the prism user and prism password text boxes will be automatically populated with the Prism user credentials, using which Nutanix Acropolis discovery was performed.

     

    If this Nutanix Acropolis server has not been discovered using the Nutanix Prism, but you still want to monitor the Nutanix Acropolis server via the Prism, then select the IP address of the Prism server that you wish to use for monitoring the Nutanix Acropolis server from the prism ip list. By default, this list is populated with the IP address of all Nutanix Prism hosts that were added to the eG Enterprise system at the time of discovery. Upon selection, the PRISM user and prism password that were pre-configured for that Nutanix Prism will be automatically displayed against the respective text boxes.

    On the other hand, if the IP address of the Prism server of interest to you is not available in the list, then, you can add the details of the Prism server on-the-fly, by selecting the Other option from the prism ip list. This will invoke the MANAGER DISCOVERY - VIRTUAL PLATFORM SETTINGS page. Refer to the Configuring eG Enterprise to Monitor Nutanix Acropolis topic for details on how to use this page.

  6. confirm password - Confirm the password by retyping it here.
  7. ssl - By default, the Nutanix Prism server is SSL-enabled. Accordingly, the SSL flag is set to Yes by default. This indicates that the eG agent will communicate with the Prism server via HTTPS by default.

  8. webport - By default, the Nutanix Prism server listens on port 9440. This implies that while monitoring a Nutanix Acropolis server via the Prism server, the eG agent connects to port 9440.

  9. exclude vms - Administrators of some virtualized environments may not want to monitor some of their less-critical VMs both from ‘outside’ and from ‘inside’. The eG agent in this case can be configured to completely exclude such VMs from its monitoring purview. To achieve this, provide a comma-separated list of VMs to be excluded from monitoring in the exclude vms text box. Instead of VMs, VM name patterns can also be provided here in a comma-separated list. For example, your exclude vms specification can be: *xp,*lin*,win*,vista. Here, the * (asterisk) is used to denote leading and trailing spaces (as the case may be). By default, this parameter is set to none indicating that the eG agent obtains the inside and outside views of all VMs on a virtual host by default. By providing a comma-separated list of VMs/VM name patterns in the exclude vms text box, you can make sure the eG agent stops collecting ‘inside’ and ‘outside’ view metrics for a configured set of VMs.
  10. ignore vms inside view - Administrators of some high security Nutanixe environments might not have permissions to internally monitor one/more VMs. The eG agent can be configured to not obtain the inside view of such ‘inaccessible’ VMs using the ignore vms inside view parameter. Against this parameter, you can provide a comma-separated list of VM names, or VM name patterns, for which the inside view need not be obtained. For instance, your ignore vms inside view specification can be: *xp,*lin*,win*,vista. Here, the * (asterisk) is used to denote leading and trailing spaces (as the case may be). By default, this parameter is set to none indicating that the eG agent obtains the inside view of all VMs on a Nutanix Acropolis server by default.

    Note:

    While performing VM discovery, the eG agent will not discover the operating system of the VMs configured in the ignore vms inside view text box.

  11. ignore winnt - By default, the eG agent does not support the inside view for VMs executing on Windows NT operating systems. Accordingly, the ignore winnt flag is set to Yes by default.
  12. inside view using - By default, this test communicates with every VM remotely and extracts “inside view” metrics. Therefore, by default, the inside view using flag is set to Remote connection to VM (Windows).

    Typically, to establish this remote connection with Windows VMs in particular, eG Enterprise requires that the eG agent be configured with domain administrator privileges. In high-security environments, where the IT staff might have reservations about exposing the credentials of their domain administrators, this approach to extracting “inside view” metrics might not be preferred. In such environments therefore, eG Enterprise provides administrators the option to deploy a piece of software called the eG VM Agent (Windows) on every Windows VM; this VM agent allows the eG agent to collect “inside view” metrics from the Windows VMs without domain administrator rights. Refer to Configuring the eG Agent to Collect Current Hardware Status Metrics for more details on the eG VM Agent. To ensure that the “inside view” of Windows VMs is obtained using the eG VM Agent, set the inside view using flag to eG VM Agent (Windows). Once this is done, you can set the domain, admin user, and admin password parameters to none.

  13. domain, admin user, admin password, and confirm password - By default, this test connects to each virtual guest remotely and attempts to collect “inside view” metrics. In order to obtain a remote connection, the test must be configured with user privileges that allow remote communication with the virtual guests. The first step towards this is to specify the DOMAIN within which the virtual guests reside. The admin user and admin password will change according to the domain specification. Discussed below are the different values that the domain parameter can take, and how they impact the admin user and admin password specifications:

    • If the VMs belong to a single domainIf the guests belong to a specific domain, then specify the name of that domain against the domain parameter. In this case, any administrative user in that domain will have remote access to all the virtual guests. Therefore, an administrator account in the given domain can be provided in the ADMIN USER field and the corresponding password in the ADMIN PASSWORD field. Confirm the password by retyping it in the CONFIRM PASSWORD text box.
    • If the guests do not belong to any domain (as in the case of Linux/Solaris guests) :  In this case, specify “none” in the DOMAIN field, and specify a local administrator account name in the ADMIN USER below.

      Prior to this, you need to ensure that the same local administrator account is available or is explicitly created on each of the virtual machines to be monitored. Then, proceed to provide the password of the ADMIN USER against ADMIN PASSWORD, and confirm the password by retyping it in the CONFIRM PASSWORD text box.

      If key-based authentication is implemented between the eG agent and the SSH daemon of a Linux guest, then, in the admin user text box, enter the name of the user whose <user_home_dir> (on that Linux guest) contains a .ssh directory with the public key file named authorized_keys. The admin password in this case will be the passphrase of the public key; the default public key file that is bundled with the eG agent takes the password eginnovations. Specify this as the admin password if you are using the default private/public key pair that is bundled with the eG agent to implement key-based authentication. On the other hand, if you are generating a new public/private key pair for this purpose, then use the passphrase that you provide while generating the pair. For the detailed procedure on Implementing Key-based Authentication refer to Troubleshooting the Failure of the eG Remote Agent to Connect to or Report Measures for Linux Guests.

    • If the guests belong to different domains - In this case, you might want to provide multiple domain names. If this is done, then, to access the guests in every configured domain, the test should be configured with the required user privileges; this implies that along with multiple DOMAIN names, multiple ADMIN USER names and ADMIN PASSWORDs would also have to be provided. To help administrators provide these user details quickly and easily, the eG administrative interface embeds a special configuration page. To access this page, simply click on the Click here hyperlink that appears just above the parameters of this test in the test configuration page. To know how to use the special page, refer to VM Details - Acropolis Test.
    • If the inside view using flag is set to ‘eG VM Agent (Windows)’ - In this case, the inside view can be obtained without domain administrator privileges. Therefore, set the domain, admin user, and admin password parameters to none.
  14. REPORT BY USER - While monitoring a Nutanix Acropolis server, the REPORT BY USER flag is set to No by default, indicating that by default, the guest operating systems on the Acropolis server are identified using the hostname specified in the operating system. On the other hand, while monitoring Acropolis desktop environments, this flag is set to Yes by default; this implies that in case of VDI servers, by default, the guests will be identified using the login of the user who is accessing the guest OS. In other words, in VDI environments, this test will, by default, report measures for every username_on_virtualmachinename.
  15. REPORT POWERED OS - This flag becomes relevant only if thereport by user flagis set to ‘Yes’.

    If the report powered os flag is set to Yes (which is the default setting), then this test will report measures for even those VMs that do not have any users logged in currently. Such guests will be identified by their virtualmachine name and not by the username_on_virtualmachinename. On the other hand, if the report powered os flag is set to No, then this test will not report measures for those VMs to which no users are logged in currently.      

  16. REPORT POWERED ON - You can set the REPORT POWERED ON status to YES, so that the test reports an additional measure, Is VM powered on?, revealing whether a guest OS is currently running or not. The default status of this flag is set to Yes for a Nutanix Acropolis server. However, the default status of this flag is No in the case of Nutanix Acropolis VDI server; this is because, in such environments, the virtual desktops will be in the powered-off state most of the time.
  17. DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eG suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability
    • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

VM power-on state:

Indicates the current state of the virtual machine.

 

The table below displays the States that can be reported by this measure, and their numeric equivalents:

State Value

Off

0

On

1

Suspended

2

Note:

By default, this measure reports one of the States listed in the table above. The graph of this measure however will represent the VM status using the numeric equivalents - ‘0’ to ‘7’.

Is controller VM

Indicates whether/not this VM is the controller VM

Number

The Nutanix CVM is what runs the Nutanix software and serves all of the I/O operations for the hypervisor and all VMs running on that host. Prism service runs on every CVM with an elected Prism Leader which is responsible for handling HTTP requests.

If this measure reports the value 0, it indicates that the VM is not a controller VM, whereas the value 1 indicates that it is a controller VM.

Current sessions

Indicates the number of sessions that are currently active on the guest.

Number

The value of this measure reveals the guest OS that is currently busy.

The detailed diagnosis of this metric lists the VM name, user of that particular VM, and operating system of VM.

CPU reserved

Indicates the amount of CPU power reserved for this VM.

GHz

 

Virtual CPU utilization

Indicates the percentage of virtual CPU resources used by this VM.

Percent

Compare the value of this measure across VMs to know which VM is using the allocated CPU resources excessively.

Physical CPU utilization

Indicates the percentage of physical CPU that is used by the VM.

Percent

Ideally, a VM should use only a small percentage of the physical CPU resources of the Nutanix Acropolis host. High CPU usage by a VM could cause other VMs to contend for limited CPU resources, thereby adversely impacting the performance of the other VMs and the applications executing on them. 

Virtual CPUs

Indicates the number of virtual CPUs allocated to this VM.

Number

Compare the value of this measure across VMs to know which VM has been allocated the maximum number of virtual CPUs.

Disk capacity

Indicates the total disk capacity available to this VM.

GB

 

Used space

Indicates the amount of disk space used by this VM.

GB

 

Disk space utilization

Indicates the percentage of disk space used by this VM.

Percent

Comparing the value of this measure across VMs will reveal the VM that is consuming too much disk space.

Virtual disks

Indicates the number of virtual disks in the VM.

Number

Use the detailed diagnosis of this measure to view the details of the virtual disks.

Memory reserved capacity

Indicates the amount of memory reserved for this VM.

GB

 

Memory capacity

Indicates the total amount of memory available to this VM.

GB

 

Memory usage

Indicates the amount of allocated memory capacity currently being used by this VM.

GB

 

Free memory

Indicates the amount of free memory available to this VM.

GB

Compare the value of this measure across VMs to know which VM is running out of free memory.

Memory utilization

Indicates the percentage of allocated memory capacity currently being utilized by this VM.

Percent

Compare the value of this measure across VMs to know which VM is using memory excessively.

Percent free memory

Indicates the percentage of free memory available in the VM.

Percent

Compare the value of this measure across VMs to know which VM is running short of free memory.

Network adapters

Indicates the number of network adapters available to this VM.

Number

 

Data received

Indicates the amount of data received by this VM.

GB

 

Data transmitted

Indicates the amount of data transmitted by this VM.

GB

 

Total IOPS

Indicates the number of I/O operations per second (IOPS) on this VM.

Number

This measure is a good indicator of the level of I/O activity on each VM. Compare the value of this measure to know which VM is experiencing an I/O overload.

Read IOPS

Indicates the number of read I/O operations per second on this VM.

Number

 

If the value of the Total IOPS measure is high for a VM, then compare the value of these measures for that VM to know where the bottleneck lies - when reading or writing?

Write IOPS

Indicates the number of write I/O operations per second on this VM.

Number

Total IO latency

Indicates the average I/O latency of this VM.

Seconds

Compare the value of this measure across VMs to know which VM is the slowest in processing I/O requests.

Read IO latency

Indicates the average read I/O latency for this VM.

Seconds

 

If the value of the Total IO latency measure is high for a VM, then compare the value of these measures for that VM to know where the bottleneck lies - when reading or writing?

Write IO latency

Indicates the average write I/O latency for this VM.

Seconds

Total IO bandwidth

Indicates the bandwidth consumed when processing I/O requests to this VM.

KB/Sec

Compare the value of this measure to know which VM is consuming maximum I/O bandwidth.

Read I/O bandwidth

Indicates the amount of bandwidth consumed by this VM when processing read I/O requests.

KB/Sec

If the value of the Total IO bandwidth measure is unusually high for a VM, then compare the value of these measures for that VM to know when maximum bandwidth was consumed - when reading or writing?

Write I/O bandwidth

Indicates the amount of bandwidth consumed by this VM when processing write I/O requests.

KB/Sec