Agents Administration - Tests
 

Default Parameters for NutAHVStorageTest

Nutanix combines compute(CPU) resources with storage resources delivered via SSDs and directly-attached (DAS) SATA HDD media drives. The VMs operating on the Nutanix Acropolis hypervisor use these aggregated storage resources for their operations. The lack of adequate, well-tuned storage resources can therefore severely impair VM operations and availability. To avoid this, a Nutanix administrator has to continuously measure overall storage performance and accurately determine the following:

  • How is the I/O load on the storage?

  • Is the storage processing I/O requests quickly?

  • Is too much bandwidth being consumed when processing I/O?

  • Is the AHV sized with adequate storage resources? If not, what type of storage is running short of space - the SSDs? or the SATA HDDs?

This test helps administrators monitor overall storage health and rapidly leads them to the problem areas by providing quick and accurate answers to the aforesaid.

This page depicts the default parameters that need to be configured for the NutAHVStorageTest.

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • 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 Monitoring Nutanix Acropolis document for details on how to use this page.

  • Confirm the password by retyping it in the CONFIRM PASSWORD text box.

  • 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.

  • By default, the Nutanix Prism server listens on port 9440, which appears in the WEBPORT parameter. This implies that while monitoring a Nutanix Acropolis server via the Prism server, the eG agent connects to port 9440.

  • The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.