Probable Cause Analysis in various deployment environments

This topic describes how Probable Cause Analysis works in different kinds of deployment environments.

Probable Cause Analysis in a scalable deployment environment

In a scalable deployment environment, events are propagated from local BMC ProactiveNet Servers to a central BMC ProactiveNet Server. If you want to perform Probable Cause Analysis on all the events in the environment, perform Probable Cause Analysis on the central BMC ProactiveNet Server.

Limitations of Probable Cause Analysis in a scalable environment

Data for the intelligent events on the local servers is not propagated to the master BMC ProactiveNet Server. This causes the propagated intelligent events to be treated as external events. This data loss causes Probable Cause Analysis on the master BMC ProactiveNet Server to lose accuracy because no data correlation is available on the master BMC ProactiveNet Server.

Probable Cause Analysis in a virtual environment

BMC Proactivenet handles Probable Cause Analysis differently for system resource issues on VMware ESX host servers or virtual machines. When Probable Cause Analysis is requested for a system resource-related event on an ESX host or a virtual machine, BMC ProactiveNet takes into account the issues with all the virtual machines running on that host server, as well as issues with the ESX host server itself.

How Probable Cause Analysis handles vMotion events

In addition to considering system resource events, Probable Cause Analysis also displays relevant virtual machine migration events for the host of the event for which Probable Cause Analysis is requested, if that event is on the virtual machine or on the ESX host server.

When Probable Cause Analysis is requested for a vMotion event, BMC ProactiveNet displays all the system resource issues on the VMware ESX host server from which the virtual machine is moved.