Root Cause and Impact Analysis for VIO
This section provides information on root cause and impact analysis for various events.
Following table lists the root-cause problem diagnosed and the impacted classes.
Class | Root Casue | Event (symptoms) of root cause | Impacted System |
|---|---|---|---|
Host | Down | Down | Hypervisor |
DownOrImpaired | VirtualMachines | ||
Unresponsive | Host | ||
InterfaceLostConnection | Interface | ||
ServiceAffected | ControllerService ComputeService | ||
AtRisk ReducedRedendancy AllComponentsDown | ControllerServiceCluster | ||
Hypervisor | Down | DownOrImpaired | VirtualMachines |
HostLostConnection | Hypervisor | ||
PowerOff | Hypervisor | ||
InterfaceLostConnection | Interface | ||
ServiceAffected | ControllerService ComputeService | ||
AtRisk ReducedRedendancy AllComponentsDown | ControllerServiceCluster | ||
VirtualMachine | Down | DownOrImpaired | VirtualMachine |
ServiceAffected | ControllerService ComputeService | ||
AtRisk ReducedRedendancy AllComponentsDown | ControllerServiceCluster |
The Server Manager provides:
- Impact analysis and diagnosis when a hypervisor server is down. For example, it diagnoses when a VMware hypervisor host goes down (Host Down) and identifies the impact to a virtual machine (Down).
- Impact analysis and diagnosis when a physical switch is down. For example, it diagnoses when a physical switch goes down and identifies the impact to the hypervisor and virtual machines.
- Impact analysis and diagnosis when a hypervisor server is down. For example, it diagnoses when a hypervisor host goes down (Host Down) and identifies the impact to ComputeService or ControllerService (Service Affected).
- Impact analysis and diagnosis when a Virtual Machine is down. For example, it diagnoses when a Virtual Machine goes down (Host Down) and identifies the impact to ComputeService or ControllerService (Service Affected).
- Impact analysis and diagnosis when a Virtual Machine is down. For example, it diagnoses when a Virtual Machine goes down (Host Down) and identifies the impact to ClusterManager (Service Affected).
- Impact analysis and diagnosis when a logical/tap interface is down. For example, it diagnoses when a logical interface goes down (Interface Down) and identifies the impact to a virtual machine (VMLostConnection).
- Impact analysis and diagnosis when a vRouter is down. For example, it diagnoses when a vRouter goes down and identifies the impact to a virtual machine.
- Impact analysis and diagnosis when a virtual interface is down. For example, it diagnoses when the virtual interface of a vRouter or virtual machine goes down and identifies the impact to a virtual machine.
- Impact analysis and diagnosis when the physical interface of the hypervisor is down. For example, it diagnoses when a physical interface goes down and identifies the impact to a virtual machine.
- Impact analysis and diagnosis when a host hosting OpenStack service is down. For example, it diagnoses when a host hosting OpenStack service goes down and identifies the impact to CloudController and VMs.
Physical Hypervisor hosting Host Down

Hypervisor Down

Compute VirtualMachine PoweredOff
