Agents Administration - Tests
 

Default Parameters for XenGPUProfiles_cf

For each profile applied on the physical GPU of the NVIDIA GRID, this test helps adminsitrators to figure out the number of physical GPUs in the NVIDIA GRID and the number of vGPUs that can be provisioned from the physical GPUs. In addition, this test accurately pinpoints the number of virtual machines/desktops that can still be utilized on the NVIDIA GRID thus enabling administrators plan the capacity of their environment prior to the exhaustion of critical GPU resources!

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

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

  • To enable the eG agent to connect to the XenServer API for collecting statistics of interest, this test should login to the XenServer as a valid user. Provide the name of such a user in the XEN USER text box. By default, the root user is authorized to execute the test. If for some reason you prefer not to use the root user's credentials, you can create a new user on the XenServer host for this purpose.

    The steps for creating a new user on the XenServer host are detailed below:

    1. Login to the host on which the XenServer is installed, as the root user.

    2. From the /usr/sbin directory, execute the following commands to create a new user and assign a password to him/her:

      3. useradd {UserName}

      passwd {Password}

    3. The following messages then appear:

      Changing password for user

      New UNIX password:

      BAD PASSWORD: it is based on a dictionary word

    4. You will then be prompted to retype the password:

      Retype new UNIX password::{password}

    5. Confirm the password by retyping it in the space provided.

  • The password of the specified XEN USER needs to be mentioned in the XEN PASSWORD text box.

  • By default, in most virtualized environments, vCenter listens on port 80 (if not SSL-enabeld) or on port 443 (if SSL-enabled) only. This implies that while monitoring vCenter, the eG agent, by default, connects to port 80 or 443, depending upon the SSL-enabled status of vCenter - i.e., if vCenter is not SSL-enabled (i.e., if the SSL flag above is set to No), then the eG agent connects to vCenter using port 80 by default, and if vCenter is SSL-enabled ((i.e., if the SSL flag is set to Yes), then the agent-vCenter communication occurs via port 443 by default. Accordingly, the WEBPORT parameter is set to default by default.

    In some environments however, the default ports 80 or 443 might not apply. In such a case, against the WEBPORT parameter, you can specify the exact port at which vCenter in your environment listens, so that the eG agent communicates with that port for collecting metrics from vCenter.

  • By default, the Xen Server is not SSL-enabled. This indicates that by default, the eG agent communicates with the XenServer using HTTP. Accordingly, the SSL flag is set to No by default. If you configure the XenServer to use SSL, then make sure that the SSL flag is set to Yes, so that the eG agent communicates with the XenServer using HTTPS. Note that a default SSL certificate comes bundled with every XenServer installation. If you want the eG agent to use this default certificate for communicating with an SSL-enabled XenServer, then no additional configuration is required. However, if you do not want to use the default certificate, then you can generate a self-signed certificate for use by the XenServer. In such a case, you need to explicitly follow the broad steps given below to enable the eG agent to communicate with the XenServer via HTTPS:

    1. Obtain the server-certificate for the XenServer

    2. Import the server-certificate into the local certificate store of the eG agent

  • Once the above value is provided, click on the Update button to register the changes made.