Citrix SCOM Management Pack for XenServer Reference Guide

Summary

The "Citrix MPXS Agent" service is not running.

Causes

A service can stop for many reasons, including:

• The service was stopped by an administrator.

• The service encountered an exception that stopped it.

• The service was improperly configured, which prevented it from starting.

• Another service, that this service is dependent on, was stopped.

Resolutions

Start the service from the “Actions” pane.

Additional

The topology and the health state of your XenServer environment that is managed by this proxy will not be properly updated if the service is not running.

External

For more information, see the “Citrix XenServer Management Pack User’s Guide”.

Summary

The utilization of a CPU core on a server is high.

Causes

The server may be highly utilized.

Resolutions

Check whether the utilization of other CPU cores is high or the average CPU utilization of a server is high for longer periods of time. If yes, this indicates an overloaded server, so consider migrating some of the virtual machines to other servers.

Additional

Occasional utilization peaks of individual CPU cores are okay as long as the average CPU utilization on a server is not higher than 80%. The average server’s CPU utilization higher than 80% with a high frequency of CPU core utilization spikes typically indicates an overloaded server.

External

For more information on how to migrate virtual machines to other servers, see the “Citrix XenServer Administrator’s Guide”.

Summary

The utilization of a CPU core on a server is high.

Configuration

The following configuration parameters are customizable:

• IntervalSeconds - The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

• NumberOfSamples - The number of event occurrences before monitor state changes will be triggered (the default value is set to 3).

• Threshold - The value that defines the warning threshold to be used in the comparison (the default value is set to 85 percentage).

Causes

The server may be highly utilized.

Resolutions

Check whether the utilization of other CPU cores is high or the average CPU utilization of a server is high for longer periods of time. If yes, this indicates an overloaded server, so consider migrating some of the virtual machines to other servers.

Additional

Occasional utilization peaks of individual CPU cores are okay as long as the average CPU utilization on a server is not higher than 80%. The average server’s CPU utilization higher than 80% with a high frequency of CPU core utilization spikes typically indicates an overloaded server.

External

For more information on how to migrate virtual machines to other servers, see the “Citrix XenServer Administrator’s Guide”.

Summary

The utilization of a local storage on a server is high.

Causes

Local storage on the server may be highly utilized.

Resolutions

Consider the following solutions to reduce the utilization of a local storage:

• Check whether you can increase space allocated to the local storage.

• Check whether you can move or remove some of the content from the local storage.

Additional

Highly utilized local storage with thin provisioned virtual hard disks means that virtual machines can run out of disk space when they write information to their local disks. It also means you might not be able to copy additional virtual machines to this storage.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on storage.

Summary

One or more newly configured connections to the pool master have failed.

Causes

A connection to the pool master can fail for the following reasons:

• The connection information may be wrong.

• The connection information may be out of date because the authentication information has changed after the connections were configured and before the discovery. The pool might have obtained a new pool master or an administrator might have changed the authentication information.

Resolutions

Start the configuration tool on the proxy. You can test the connection using the “Test” button. Update the connection information until all connections pass the test.

Additional

A connection is treated as newly configured until the pool is discovered. The pool cannot be discovered while the connection to the pool master is broken.

This monitor only changes the color of a diagram icon, while the “XenServer MP proxy connections to new pools” rule sends alert for every failed connection.

External

For more information, see the “Citrix XenServer Management Pack User’s Guide”.

Summary

The read (inbound) traffic on a server’s network card is high.

Causes

The read (inbound) traffic on a server’s network card can be high for many reasons, including:

• Reading activity from the shared storage may be high.

• Virtual machines may cause an intensive network read activity.

Resolutions

Consider the following solutions to reduce the read (inbound) traffic:

• Check whether the read traffic is high for longer periods of time.

• Check whether the read traffic is high on individual or all network cards.

• Check whether the read traffic is related to a specific virtual machine or is a cumulative result of all virtual machines.

• Check whether you can redirect some of the read traffic to other network cards on a server.

Additional

High read (inbound) network traffic can be a result of a virtual machine activity or a server activity when reading from the shared storage.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The read (inbound) traffic on a server’s network card is high.

Configuration

The following configuration parameters are customizable:

• IntervalSeconds - The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

• NumberOfSamples - The number of event occurrences before monitor state changes will be triggered (the default value is set to 3).

• Threshold - The value that defines the warning threshold to be used in the comparison (the default value is set to 500 Mbps).

Causes

The read (inbound) traffic on a server’s network card can be high for many reasons, including:

• Reading activity from the shared storage may be high.

• Virtual machines may cause an intensive network read activity.

Resolutions

Consider the following solutions to reduce the read (inbound) traffic:

• Check whether the read traffic is high for longer periods of time.

• Check whether the read traffic is high on individual or all network cards.

• Check whether the read traffic is related to a specific virtual machine or is a cumulative result of all virtual machines.

• Check whether you can redirect some of the read traffic to other network cards on a server.

Additional

High read (inbound) network traffic can be a result of a virtual machine activity or a server activity when reading from the shared storage.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The write (outbound) traffic on a server’s network card is high.

Causes

A network card may have a high amount of write (outbound) traffic on the server.

Resolutions

Consider the following solutions to reduce the write (outbound) traffic:

• Check whether the write traffic is high for longer periods of time.

• Check whether the write traffic is high on individual or all network cards.

• Check whether the write traffic is related to a specific virtual machine or is a cumulative result of all virtual machines.

• Check whether you can redirect some of the write traffic to other network cards on the server.

Additional

High write (outbound) network traffic can be a result of a virtual machine activity or the server activity when writing to the shared storage.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The write (outbound) traffic on a server’s network card is high.

Configuration

The following configuration parameters are customizable:

• IntervalSeconds - The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

• NumberOfSamples - The number of event occurrences before monitor state changes will be triggered (the default value is set to 3).

• Threshold - The value that defines the warning threshold to be used in the comparison (the default value is set to 500 Mbps).

Causes

A network card may have a high amount of write (outbound) traffic on the server.

Resolutions

Consider the following solutions to reduce the write (outbound) traffic:

• Check whether the write traffic is high for longer periods of time.

• Check whether the write traffic is high on individual or all network cards.

• Check whether the write traffic is related to a specific virtual machine or is a cumulative result of all virtual machines.

• Check whether you can redirect some of the write traffic to other network cards on the server.

Additional

High write (outbound) network traffic can be a result of a virtual machine activity or the server activity when writing to the shared storage.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The average CPU utilization across all servers in a pool is high.

Causes

A number of servers in the pool may experience high CPU utilization.

Resolutions

Check whether the CPU utilization on the pool is high for longer periods of time. If yes, this may indicate the overloaded pool, so consider migrating some of the virtual machines to other pools or adding a new server to the pool.

Additional

Occasional utilization peaks of the CPU utilization on the pool are okay as long as the average CPU utilization on the pool is not more than 80%. The CPU utilization on the pool higher than 80% with high frequency of CPU utilization spikes typically indicates an overloaded pool.

External

For information on how to migrate virtual machines to other pools, see the “Citrix XenServer Administrator’s Guide”.

Summary

The average memory utilization across all servers in a pool is high.

Causes

A number of servers in the pool may experience high memory utilization.

Resolutions

Check whether the average memory utilization on the pool is high for longer periods of time. If yes, this may indicate the overloaded pool and starting subsequent virtual machines on the pool might not be possible. Consider migrating some of the virtual machines to other pools or adding a new server to the pool.

Additional

If virtual machines are configured with the fixed amount of memory, high memory utilization in the pool can prevent starting additional virtual machines. However, if Dynamic Memory Control (DMC) feature is enabled, it might still be possible to start additional virtual machines.

External

For information on how to configure and manage virtual machine memory settings, see the “Citrix XenServer Administrator’s Guide”, the section on configuring virtual machine memory.

Summary

The average utilization across all shared storage units in a pool is high.

Causes

Several shared storage units in the pool are experiencing high utilization.

Resolutions

Consider the following solutions to reduce the shared storage utilization in the pool:

• Check whether you can increase space allocated to the individual shared storage unit.

• Check whether you can move or remove some of the content from the individual shared storage unit.

Additional

Highly utilized shared storage with thin provisioned virtual hard disks means that virtual machines can run out of disk space when they write information to their local disks. It also means you might not be able to copy additional virtual machines to the shared storage.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on storage.

Summary

Connection to the pool master is not available.

Causes

The pool master that is configured for the pool cannot be contacted and the failover pool master could not be determined.

Resolutions

Consider the following solutions to enable the connection to the pool master:

• Check whether the pool master is operational.

• Check whether a failover pool master is available and operational.

• Check whether the connection to this pool passes the test in the XenServer MP configuration tool by using the “Test” button. Update the connection information until the connection passes the test.

Additional

When Citrix XenServer MP fails to connect to the configured pool master, it tries to determine the failover master for the pool. If the original pool master cannot be contacted and the failover pool master cannot be determined, the alert is raised.

It is possible that the pool master election is currently in effect and the connection to the pool is only temporarily down. In such case, the alert of the “XenServer pool master changed” monitor soon follows and the connection to the pool is resumed.

External

For more information, see the “Citrix XenServer Management Pack User’s Guide”.

Summary

The number of offline servers in a pool is high.

Causes

The number of offline servers in a pool can be high for many reasons, including:

• A lot of servers may be in the maintenance mode.

• A network connectivity problem may exist between the pool master and the pool members.

• Pool members may have been shut down or have stopped responding.

Resolutions

Consider the following solutions to reduce the number of offline servers in the pool:

• Check whether you can ping the unavailable servers.

• Check whether the unavailable servers have been shut down and start them.

• Check whether the unavailable servers have stopped responding and reboot them.

• Check your network configuration.

Additional

The pool master keeps track of all pool members and their availability. It immediately detects if pool members cannot be contacted and managed.

External

For more information on unusual behavior, application failures, or other issues with servers, see the “Citrix XenServer Administrator’s Guide”, the troubleshooting section.

Summary

The percentage of offline servers in a pool is high.

Causes

The percentage of offline servers in a pool can be high for many reasons, including:

• A lot of servers may be in the maintenance mode.

• A network connectivity problem may exist between the pool master and the pool members.

• The pool members may have been shut down or have stopped responding.

Resolutions

Consider the following solutions to reduce the percentage of offline servers in the pool:

• Check whether you can ping the unavailable servers.

• Check whether the servers have been shut down and start them.

• Check whether the servers have stopped responding and reboot them.

• Check your network configuration.

Additional

The pool master keeps track of all pool members and their availability. It immediately detects if pool members cannot be contacted and managed.

External

For more information on unusual behavior, application failures, or other issues with servers, see the “Citrix XenServer Administrator’s Guide”, the troubleshooting section.

Summary

A new pool master has been configured or elected.

Causes

A pool master can change for many reasons, including:

• A new pool master may have been configured by the administrator.

• The pool master failover may have occurred.

Resolutions

Check the following to determine why the pool master has changed:

• Check whether a new pool master has been configured.

• Check whether the pool master failover has occurred.

Additional

Citrix XenServer MP has detected the pool master change and has successfully connected to a new pool master. Try to determine whether the pool master change was planned or was a result of a failure.

External

For more information on issues with pool masters, see the “Citrix XenServer Administrator’s Guide”, the troubleshooting section.

Summary

The average local storage utilization on a server is high.

Causes

Local storage on the server may be highly utilized.

Resolutions

Consider the following solutions to reduce the local storage utilization:

• Check whether you can increase the space allocated to the local storage.

• Check whether you can move or remove some of the content from the local storage.

Additional

Highly utilized local storage with thin provisioned virtual hard disks means that virtual machines can run out of disk space when they write information to their local disks.

It also means you might not be able to copy additional virtual machines to the local storage.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on storage.

Summary

A pool master has detected that the server cannot be contacted and managed.

Causes

A server can be unavailable for many reasons, including:

• The server may be in the maintenance mode.

• A network connectivity problem may exist between the pool master and a pool member.

• The server may have been shut down or has stopped responding.

Resolutions

Consider the following solutions to make the server available:

• Check whether the server unavailability has been planned.

• Check whether you can ping the server.

• Check whether the server has been shut down and start it.

• Check whether the server has stopped responding and reboot it.

• Check your network configuration.

Additional

The pool master has detected that the pool member server cannot be contacted and therefore cannot be managed. Along with the pool member server affected, this alert also lists VMs that were running on the server at the time of last successful check.

External

For more information on unusual behavior, application failures, or other issues with servers, see the “Citrix XenServer Administrator’s Guide”, the troubleshooting section.

Summary

The average CPU utilization of a server is high.

Causes

The server may be overloaded.

Resolutions

Check whether the average CPU utilization on the server is high for longer periods of time. If yes, consider migrating some of the virtual machines to other servers.

Additional

Occasional average CPU utilization peaks are okay as long as the long term average CPU utilization on the server is not more than 80%. The long term CPU utilization of more than 80% typically indicates the overloaded server.

External

For information on how to migrate virtual machines to other servers, see the “Citrix XenServer Administrator’s Guide”.

Summary

The average CPU utilization of a server is high.

Configuration

The following configuration parameters are customizable:

• IntervalSeconds - The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

• NumberOfSamples - The number of event occurrences before monitor state changes will be triggered (the default value is set to 3).

• Threshold - The value that defines the warning threshold to be used in the comparison (the default value is set to 85 percentage).

Causes

The server may be overloaded.

Resolutions

Check whether the average CPU utilization on the server is high for longer periods of time. If yes, consider migrating some of the virtual machines to other servers.

Additional

Occasional average CPU utilization peaks are okay as long as the long term average CPU utilization on the server is not more than 80%. The long term CPU utilization of more than 80% typically indicates the overloaded server.

External

For information on how to migrate virtual machines to other servers, see the “Citrix XenServer Administrator’s Guide”.

Summary

The average network read (inbound) traffic across all network cards is high.

Causes

All network cards are experiencing high read (inbound) traffic on the server.

Resolutions

Consider the following solutions to reduce the read (inbound) traffic:

• Check whether the average read traffic on the server is high for longer periods of time.

• Check whether the read traffic is high on individual or all network cards.

• Check whether the read traffic is related to a specific virtual machine or is a cumulative result of all virtual machines.

• Check whether you can redirect some of the read traffic by migrating virtual machines to other servers.

Additional

High read (inbound) network traffic can be a result of the virtual machine or server activity when reading from the shared storage.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The average network read (inbound) traffic across all network cards is high.

Configuration

The following configuration parameters are customizable:

• IntervalSeconds - The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

• NumberOfSamples - The number of event occurrences before monitor state changes will be triggered (the default value is set to 3).

• Threshold - The value that defines the warning threshold to be used in the comparison (the default value is set to 500 Mbps).

Causes

All network cards are experiencing high read (inbound) traffic on the server.

Resolutions

Consider the following solutions to reduce the read (inbound) traffic:

• Check whether the average read traffic on the server is high for longer periods of time.

• Check whether the read traffic is high on individual or all network cards.

• Check whether the read traffic is related to a specific virtual machine or is a cumulative result of all virtual machines.

• Check whether you can redirect some of the read traffic by migrating virtual machines to other servers.

Additional

High read (inbound) network traffic can be a result of the virtual machine or server activity when reading from the shared storage.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The average network write (outbound) traffic across all network cards is high.

Causes

All network cards are experiencing high write (outbound) trafficon the server.

Resolutions

Consider the following solutions to reduce the write (outbound) traffic:

• Check whether the average write traffic on the server is high for longer periods of time.

• Check whether the write traffic is high on individual or all network cards.

• Check whether the write traffic is related to the specific virtual machine or is a cumulative result of all virtual machines.

• Check whether you can redirect some of the write traffic by migrating virtual machines to other servers.

Additional

High write (outbound) network traffic can be a result of the virtual machine or server activity when reading from the shared storage.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The average network write (outbound) traffic across all network cards is high.

Configuration

The following configuration parameters are customizable:

• IntervalSeconds - The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

• NumberOfSamples - The number of event occurrences before monitor state changes will be triggered (the default value is set to 3).

• Threshold - The value that defines the warning threshold to be used in the comparison (the default value is set to 500 Mbps).

Causes

All network cards are experiencing high write (outbound) trafficon the server.

Resolutions

Consider the following solutions to reduce the write (outbound) traffic:

• Check whether the average write traffic on the server is high for longer periods of time.

• Check whether the write traffic is high on individual or all network cards.

• Check whether the write traffic is related to the specific virtual machine or is a cumulative result of all virtual machines.

• Check whether you can redirect some of the write traffic by migrating virtual machines to other servers.

Additional

High write (outbound) network traffic can be a result of the virtual machine or server activity when reading from the shared storage.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The memory utilization of a server is high.

Causes

Server’s memory may be highly utilized.

Resolutions

Check whether the memory utilization on the server is high for longer periods of time. This may indicate the overloaded server and starting subsequent virtual machines on the server might not be possible. Consider migrating some of the virtual machines to other servers.

Additional

If virtual machines are configured with the fixed amount of memory, high memory utilization on the server can prevent starting additional virtual machines. However, if Dynamic Memory Control (DMC) feature is enabled, it might still be possible to start additional virtual machines.

External

For more information on how to configure and manage virtual machine memory settings, see the “Citrix XenServer Administrator’s Guide”, the section on configuring virtual machine memory.

Summary

The utilization of a shared storage is high.

Causes

The shared storage may be highly utilized.

Resolutions

Consider the following solutions to reduce the utilization of the shared storage:

• Check whether you can increase space allocated to the shared storage.

• Check whether you can move or remove some of the content from the shared storage.

Additional

Highly utilized shared storage with thin provisioned virtual hard disks means that virtual machines can run out of disk space when they write the information to their local disks. It also means you might not be able to copy additional virtual machines to this storage.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on storage.

Summary

The average CPU utilization on a virtual machine is high.

Causes

The virtual machine may be highly utilized.

Resolutions

Consider the following solutions to reduce the average CPU utilization:

• Check whether the average CPU utilization on the virtual machine is high for longer periods of time. If yes, consider adding more CPUs to it or migrate it to a more powerful server.

• Check whether an application running on a virtual machine is unnecessarily consuming resources.

Additional

Occasional average CPU utilization peaks are okay as long as the long term average CPU utilization on a virtual machine is not more than 80%. The long term CPU utilization of more than 80% typically indicates an overloaded virtual machine.

External

For more information on how to add more CPUs to the virtual machine or how to migrate virtual machines to other servers, see the “Citrix XenServer Administrator’s Guide”.

Summary

The average CPU utilization on a virtual machine is high.

Configuration

The following configuration parameters are customizable:

• IntervalSeconds - The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

• NumberOfSamples - The number of event occurrences before monitor state changes will be triggered (the default value is set to 3).

• Threshold - The value that defines the warning threshold to be used in the comparison (the default value is set to 85 percentage).

Causes

The virtual machine may be highly utilized.

Resolutions

Consider the following solutions to reduce the average CPU utilization:

• Check whether the average CPU utilization on the virtual machine is high for longer periods of time. If yes, consider adding more CPUs to it or migrate it to a more powerful server.

• Check whether an application running on a virtual machine is unnecessarily consuming resources.

Additional

Occasional average CPU utilization peaks are okay as long as the long term average CPU utilization on a virtual machine is not more than 80%. The long term CPU utilization of more than 80% typically indicates an overloaded virtual machine.

External

For more information on how to add more CPUs to the virtual machine or how to migrate virtual machines to other servers, see the “Citrix XenServer Administrator’s Guide”.

Summary

The average read (inbound) traffic across all network cards on a virtual machine is high.

Causes

Applications running on the virtual machine may cause an intensive network read activity.

Resolutions

Consider the following solutions to reduce the average read (inbound) traffic:

• Check whether the read traffic is high for longer periods of time. If yes, consider adding additional network cards to the virtual machine.

• Check whether the read traffic is high on individual or all virtual machine’s network cards. Consider better utilizing all virtual machine’s network cards.

• Check what applications are running on the virtual machine. Configure them to use all available network cards if possible.

Additional

High read (inbound) network traffic can be a result of a high read activity of applications running on the virtual machine.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The average read (inbound) traffic across all network cards on a virtual machine is high.

Configuration

The following configuration parameters are customizable:

• IntervalSeconds - The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

• NumberOfSamples - The number of event occurrences before monitor state changes will be triggered (the default value is set to 3).

• Threshold - The value that defines the warning threshold to be used in the comparison (the default value is set to 500 Mbps).

Causes

Applications running on the virtual machine may cause an intensive network read activity.

Resolutions

Consider the following solutions to reduce the average read (inbound) traffic:

• Check whether the read traffic is high for longer periods of time. If yes, consider adding additional network cards to the virtual machine.

• Check whether the read traffic is high on individual or all virtual machine’s network cards. Consider better utilizing all virtual machine’s network cards.

• Check what applications are running on the virtual machine. Configure them to use all available network cards if possible.

Additional

High read (inbound) network traffic can be a result of a high read activity of applications running on the virtual machine.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The average write (outbound) traffic across all network cards on a virtual machine is high.

Causes

Applications running on the virtual machine may cause an intensive network write (outbound) activity.

Resolutions

Consider the following solutions to reduce the average write (outbound) traffic:

• Check whether the write traffic is high for longer periods of time. If yes, consider adding additional network cards to the virtual machine.

• Check whether the write traffic is high on individual or all virtual machine’s network cards. Consider better utilization of all virtual machine’s network cards.

• Check what applications are running on the virtual machine. Configure them to use all available network cards if possible.

Additional

High write (outbound) network traffic can be a result of a high write activity of applications running on the virtual machine.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The average write (outbound) traffic across all network cards on a virtual machine is high.

Configuration

The following configuration parameters are customizable:

• IntervalSeconds - The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

• NumberOfSamples - The number of event occurrences before monitor state changes will be triggered (the default value is set to 3).

• Threshold - The value that defines the warning threshold to be used in the comparison (the default value is set to 500 Mbps).

Causes

Applications running on the virtual machine may cause an intensive network write (outbound) activity.

Resolutions

Consider the following solutions to reduce the average write (outbound) traffic:

• Check whether the write traffic is high for longer periods of time. If yes, consider adding additional network cards to the virtual machine.

• Check whether the write traffic is high on individual or all virtual machine’s network cards. Consider better utilization of all virtual machine’s network cards.

• Check what applications are running on the virtual machine. Configure them to use all available network cards if possible.

Additional

High write (outbound) network traffic can be a result of a high write activity of applications running on the virtual machine.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The memory utilization of a virtual machine is high.

Causes

Virtual machine’s memory may be highly utilized.

Resolutions

Consider the following solutions to reduce the memory utilization:

• Check whether the memory utilization on the virtual machine is high for longer periods of time. This may indicate the overloaded virtual machine and application performance on that virtual machine might suffer. Consider adding more memory to the virtual machine.

• Check whether an application running on a virtual machine is unnecessarily consuming resources.

Additional

Consider enabling Dynamic Memory Control (DMC) feature on the virtual machine to be able to assign more memory to it while the server dynamically manages its actual size.

External

For more information on how to configure and manage virtual machine memory settings, see the “Citrix XenServer Administrator’s Guide”, the section on configuring virtual machine memory.

Summary

The utilization of CPU on a virtual machine is high.

Causes

The virtual machine may be highly utilized.

Resolutions

Consider the following solutions to reduce the utilization of CPU:

• Check whether the utilization of other CPUs is high or if the average CPU utilization of the virtual machine is high for longer periods of time. This may indicate the overloaded virtual machine, so consider adding more CPUs to it or migrate it to a more powerful server.

• Check whether an application running on a virtual machine is unnecessarily consuming resources.

Additional

Occasional utilization peaks of individual CPUs are okay as long as the average CPU utilization of the virtual machine is not more than 80%. The average virtual machine’s CPU utilization higher than 80% with high frequency of CPU utilization spikes typically indicates the overloaded virtual machine.

External

For more information on how to add more CPUs to the virtual machine or how to migrate virtual machines to other servers, see the “Citrix XenServer Administrator’s Guide”.

Summary

The utilization of CPU on a virtual machine is high.

Configuration

The following configuration parameters are customizable:

• IntervalSeconds - The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

• NumberOfSamples - The number of event occurrences before monitor state changes will be triggered (the default value is set to 3).

• Threshold - The value that defines the warning threshold to be used in the comparison (the default value is set to 85 percentage).

Causes

The virtual machine may be highly utilized.

Resolutions

Consider the following solutions to reduce the utilization of CPU:

• Check whether the utilization of other CPUs is high or if the average CPU utilization of the virtual machine is high for longer periods of time. This may indicate the overloaded virtual machine, so consider adding more CPUs to it or migrate it to a more powerful server.

• Check whether an application running on a virtual machine is unnecessarily consuming resources.

Additional

Occasional utilization peaks of individual CPUs are okay as long as the average CPU utilization of the virtual machine is not more than 80%. The average virtual machine’s CPU utilization higher than 80% with high frequency of CPU utilization spikes typically indicates the overloaded virtual machine.

External

For more information on how to add more CPUs to the virtual machine or how to migrate virtual machines to other servers, see the “Citrix XenServer Administrator’s Guide”.

Summary

The read (inbound) traffic on a virtual machine’s network card is high.

Causes

Applications running on the virtual machine may cause an intensive network read activity.

Resolutions

Consider the following solutions to reduce the read (inbound) traffic:

• Check whether the read traffic is high for longer periods of time.

• Check whether the read traffic is high on individual or all virtual machine’s network cards.

• Check what applications are running on the virtual machine.

• Check whether you can redirect some of the read traffic to other network cards on the virtual machine.

Additional

High read (inbound) network traffic can be a result of a high read activity of applications running on the virtual machine.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The read (inbound) traffic on a virtual machine’s network card is high.

Configuration

The following configuration parameters are customizable:

• IntervalSeconds - The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

• NumberOfSamples - The number of event occurrences before monitor state changes will be triggered (the default value is set to 3).

• Threshold - The value that defines the warning threshold to be used in the comparison (the default value is set to 500 Mbps).

Causes

Applications running on the virtual machine may cause an intensive network read activity.

Resolutions

Consider the following solutions to reduce the read (inbound) traffic:

• Check whether the read traffic is high for longer periods of time.

• Check whether the read traffic is high on individual or all virtual machine’s network cards.

• Check what applications are running on the virtual machine.

• Check whether you can redirect some of the read traffic to other network cards on the virtual machine.

Additional

High read (inbound) network traffic can be a result of a high read activity of applications running on the virtual machine.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The write (outbound) traffic on a virtual machine’s network card is high.

Causes

Applications running on the virtual machine may cause an intensive network write activity.

Resolutions

Consider the following solutions to reduce the write (outbound) traffic:

• Check whether the write traffic is high for longer periods of time.

• Check whether the write traffic is high on individual or all virtual machine’s network cards.

• Check what applications are running on the virtual machine.

• Check whether you can redirect some of the write traffic to other network cards on the virtual machine.

Additional

High write (outbound) network traffic can be a result of a high write activity of applications running on the virtual machine.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

The write (outbound) traffic on a virtual machine’s network card is high.

Configuration

The following configuration parameters are customizable:

• IntervalSeconds - The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

• NumberOfSamples - The number of event occurrences before monitor state changes will be triggered (the default value is set to 3).

• Threshold - The value that defines the warning threshold to be used in the comparison (the default value is set to 500 Mbps).

Causes

Applications running on the virtual machine may cause an intensive network write activity.

Resolutions

Consider the following solutions to reduce the write (outbound) traffic:

• Check whether the write traffic is high for longer periods of time.

• Check whether the write traffic is high on individual or all virtual machine’s network cards.

• Check what applications are running on the virtual machine.

• Check whether you can redirect some of the write traffic to other network cards on the virtual machine.

Additional

High write (outbound) network traffic can be a result of a high write activity of applications running on the virtual machine.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on networking.

Summary

This rule collects the utilization of an individual CPU core on a server. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the utilization of an individual local storage on a server. The information is collected and is exposed to one or more views and reports.

Summary

One or more newly configured connections to the pool master have failed.

Causes

A connection to the pool master can fail for many reasons, including:

• The connection information may be wrong.

• The connection information may be out of date because the authentication information has changed after the connections were configured and before the discovery. The pool might have obtained a new pool master or an administrator might have changed the authentication information.

Resolutions

Start the configuration tool on the proxy. You can test the connection using the “Test” button. Update the connection information until all connections pass the test.

Additional

The connection is treated as newly configured until the pool is discovered. The pool cannot be discovered while the connection to the pool master is broken.

This rule sends alerts for every failed connection and the “XenServer MP proxy connections to new pools” monitor changes the color of a diagram icon.

External

For more information, see the “Citrix XenServer Management Pack User’s Guide”.

Summary

This rule collects the read (inbound) traffic of a network card on a server. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the write (outbound) traffic of a network card on a server. The information is collected and is exposed to one or more views and reports.

Summary

The number of servers in a pool has changed.

Causes

One or more servers have been added to or removed from the pool.

Resolutions

Check whether this configuration change was planned and authorized or not.

Summary

The number of shared storage units in a pool has changed.

Causes

One or more shared storage units have been added to or removed from the pool.

Resolutions

Check whether this configuration change was planned and authorized or not.

Additional

If the shared storage is removed from the pool, the virtual machines that are configured to use it stop working.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on storage.

Summary

This rule collects the average utilization of all online servers in a pool. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the average memory utilization of all online servers in a pool. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the average shared storage utilization in a pool. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the number of offline servers in a pool. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the percentage of offline servers in a pool. The information is collected and is exposed to one or more views and reports.

Summary

The number of virtual machines running on a server has changed.

Causes

The number of running virtual machines can change for many reasons, including:

• One or more running virtual machines may have been migrated to or from this server.

• One or more virtual machines may have been started or stopped on the server.

Resolutions

Check whether this configuration change was planned and authorized or not.

Additional

Virtual machine migration can be triggered either manually or automatically by the high-availability feature (HA). Manual migration is typically not problematic. Automatic migration triggered by the HA feature, however, indicates an issue with the server that was originally hosting the virtual machine.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on high availability.

Summary

This rule collects the average local storage utilization on a server. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the average CPU utilization on a server. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the average network read (inbound) traffic across all network cards on a server. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the average network write (outbound) traffic across all network cards on a server. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the memory utilization on a server. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the utilization of an individual shared storage. The information is collected and is exposed to one or more views and reports.

Summary

A virtual machine has changed the server on which it is running.

Causes

Virtual machine migration has been performed either manually or automatically by the high-availability (HA) feature.

Resolutions

Check whether the server that was previously hosting the virtual machine is in a healthy state.

Additional

Virtual machine migration can be triggered either manually or automatically by the high-availability feature (HA). Manual migration is typically not problematic. Automatic migration triggered by the HA feature, however, indicates an issue with the server that was originally hosting the virtual machine.

External

For more information, see the “Citrix XenServer Administrator’s Guide”, the section on high availability.

Summary

This rule collects the average CPU utilization on a virtual machine. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the average read (inbound) traffic across all network cards on a virtual machine. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the average write (outbound) traffic across all network cards on a virtual machine. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the memory utilization of a virtual machine. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the utilization of an individual CPU on a virtual machine. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the read (inbound) traffic of a network card on a virtual machine. The information is collected and is exposed to one or more views and reports.

Summary

This rule collects the write (outbound) traffic of a network card on a virtual machine. The information is collected and is exposed to one or more views and reports.