VM Movement Test

This test promptly alerts administrators to the addition, removal, and migration of VMs in vCenter. With the help of this test, administrators can determine the number of VMs that were recently added and/or removed from vCenter and the count of vMotions that recently occurred on vCenter. Moreover, using the detailed diagnosis of the test, administrators can also quickly figure out which VMs were newly added/removed/migrated. When a user complains of being unable to access a VM, administrators can use the detailed diagnosis information to determine the cause of this anomaly – was the VM removed from vCenter at around the time of the complaint? or was the VM being migrated to another vSphere/ESX server when the user complained?

This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick the desired Component type, set Performance as the Test type, choose the test from the disabled tests list, and click on the < button to move the test to the ENABLED TESTS list. Finally, click the Update button.

Target of the test : A vCenter server that manages vSphere 5 servers

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the vCenter server being monitored.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	The host for which this test is to be configured.
Port	Refers to the port at which the specified host listens to.
VC User and VC Password	To connect to vCenter and extract metrics from it, this test should be configured with the name and password of a user with Administrator or Virtual Machine Administrator privileges to vCenter. However, if, owing to security constraints, you are not able to use the credentials of such users for test configuration, then you can configure this test with the credentials of a user with Read-only rights to vCenter. For this purpose, you can assign the ‘Read-only’ role to a local/domain user to vCenter, and then specify name and password of this user against the VC User and VC Password text boxes. The steps for assigning this role to a user on vCenter have been detailed in the Creating a Special Role on vCenter and Assigning the Role to a New User topic under the eG Monitoring Capabilities -> Virtualization and Containers -> Virtualization Technologies -> VMware vSphere ESX node sequence in the eG Enterprise documentation portal Monitoring VMware Infrastructures . vCenter servers terminate user sessions based on timeout periods. The default timeout period is 30 mins. When you stop an agent, sessions currently in use by the agent will remain open for this timeout period until vCenter times out the session. If the agent is restarted within the timeout period, it will open a new set of sessions. If you want the eG agent to close already existing sessions on vCenter before it opens new sessions, then, instead of the ‘Read-only’ user, you can optionally configure the VC User and VC Password parameters with the credentials of a user with permissions to View and Stop Sessions on vCenter. For this purpose, you can create a special role on vCenter, grant the View and Stop Sessions privilege (prior to vCenter 4.1, this was called the View and Terminate Sessions privilege) to this role, and then assign the new role to a local/domain user to vCenter. The steps for assigning this role to a user on vCenter have been detailed in the Creating a Special Role on vCenter and Assigning the Role to a New User topic under the eG Monitoring Capabilities -> Virtualization and Containers -> Virtualization Technologies -> VMware vSphere ESX node sequence in the eG Enterprise documentation portal Monitoring VMware Infrastructures .
Confirm Password	Confirm the password by retyping it in this text box.
SSL	By default, the vCenter server is SSL-enabled. Accordingly, the SSL flag is set to Yes by default. This indicates that the eG agent will communicate with the vCenter server via HTTPS by default.
Webport	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.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise 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
VMs created	Indicates number of VMs that were added to the vCenter server during the last measurement period.	Number	To know which VMs were added recently, use the detailed diagnosis of this measure. The following information will be available as part of detailed diagnosis: The name of the VM that was added; The host to which the VM was added; The cluster to which the host belongs; The resource pool to which the VM belongs; The CPU, memory, and disk space configuration of the VM; The datastore assigned to the VM;
Removed VMs	Indicates the number of VMs that were removed from vCenter during the last measurement period.	Number	To know which VMs were deleted recently, use the detailed diagnosis of this measure. The following information will be available as part of detailed diagnosis: The name of the VM that was removed; The host from which the VM was removed; The cluster to which the host belongs; The resource pool from which the VM was removed; The CPU, memory, and disk space configuration of the removed VM; The datastore that was assigned to the VM;
Total migrations	Indicates the total number of migrations that occurred on vCenter during the last measurement period.	Number	Use the detailed diagnosis of this measure to view the details of all migrations that occurred during the last measurement period. This information includes: The name of the VM that was migrated; The host from which the VM was migrated; The host to which the VM was migrated; The cluster from which the VM was migrated; The cluster to which the VM was migrated; The resource pool from which the VM was migrated; The resource pool to which the VM was migrated; The CPU, memory, and disk space configuration of the migrated VM; The datastore assigned to the VM;