Chatee ahora con Soporte
Chat con el soporte

Foglight for VMware 5.6.15.1 - User and Reference Guide

Using Foglight for VMware
Introducing the Virtual Infrastructure Navigation Basics Interacting with Foglight for VMware VMware Performance Agent Configuration
Reference
Views
VMware Alarms Views VMware Explorer Views VMware Modeler Views VMware VirtualCenters Views VMware Environment Views Other Views
Rules
Agent Rules Cluster Rules Datacenter Rules Datastore Rules Resource Pool Rules ESX Server Rules VirtualCenter Rules Virtual Machine Rules VMW Stale Data Management Rule Virtual Switch Rules
Appendix: Alarm Messages

Using Foglight for VMware

This introduces you to the VMware® virtual infrastructure and provides you with essential foundational information.
For more detailed information about VMware virtualization products and solutions, consult the appropriate VMware documentation.
•
Introducing the Virtual Infrastructure
•
Navigation Basics
•
Interacting with Foglight for VMware
•
VMware Performance Agent Configuration

Introducing the Virtual Infrastructure

VMware® Virtual Infrastructure 3 (VI3) or vSphere® 4 provides an innovative mechanism for organizing and viewing any virtual infrastructure built on its platform. Using a unique combination of physical and logical components, this mechanism effectively and efficiently fulfills VMware’s vision of the modern virtual infrastructure.
Foglight™ for VMware accommodates customers of all sizes that leverage VMware’s virtualization platform by examining and enhancing VMware’s eminently knowledgeable view of the virtual world.
The following figure highlights the components or objects that make up a typical VI3 or vSphere 4 implementation. The figure makes a clear distinction between objects that exist in the physical world and those that are considered to be virtual.
Figure 1. VMware VirtualCenter Server infrastructure
The VMware VirtualCenter Server or the VMware vCenter Server allows for the configuration of a hierarchical organizational structure that resides primarily within the virtual domain. This enables an organization to easily configure physical VMware ESX Servers and virtual machines to reside in logical groups that dictate the various aspects of the virtual infrastructure (like physical object location, resource allocations and limitations for virtual machines, and high availability settings for physical and virtual components).

Object Roles

Before we get too far into discussing the layout and capabilities of Foglight™ for VMware, we must understand the different roles the various physical and virtual objects play within the overall virtual infrastructure.
The VirtualCenter (or vCenter®) Server and VMware® ESX® Servers provide the physical foundation for the VI3 or vSphere® 4 infrastructure.
Virtual machines on the other hand are classified as virtual components for the purpose of management and monitoring, even though they have many of the same characteristics (like direct network and storage access) as physical systems. At any given time, a virtual machine must be contained within a single VMware ESX Server. The particular ESX Server in which a given virtual machine is contained may change of course over the lifetime of the virtual machine through the use of unique VMware technologies such as VMware vSphere® vMotion® or VMware vSphere® High Availability (VMware HA).

Physical Objects

The physical objects within the VMware virtual infrastructure are those with which you can physically interact. The virtual components or objects that make up the virtual environment cannot exist without the presence of underlying physical components.
A VMware ESX® Server is an example of a physical component.
To have Foglight for VMware monitor a virtual infrastructure, the virtual infrastructure must consist of at least one VirtualCenter (or vCenter) Server that is used to manage the virtual infrastructure and at least one ESX Server that is used to run virtual machines.
 
* 
NOTE: Each ESX Server that is used to run virtual machines must have its own managing VirtualCenter Agent installed on it.
ESX Server Hosts
An ESX Server Host is the single physical component required to begin building a virtual infrastructure. An ESX Server provides a hypervisor based architecture for controlling and managing resources for the virtual machines that run on it. The virtual machines running on the host share the resources it provides. Should resources become over-committed, the ESX Server hypervisor determines which virtual machines have priority access to the shared resources (based on manual virtual machine configurations) and distributes the available resources accordingly.
Each ESX Server is managed by a single VirtualCenter (or vCenter) Server instance, and can be configured to exist logically within either a datacenter or cluster virtual object within the overall virtual infrastructure.
VMware VirtualCenter Server or VMware vCenter Server
 
* 
NOTE: For the rest of this document, VirtualCenter is used to indicate either VirtualCenter or vCenter.
Although a VirtualCenter Server can technically exist as a virtual machine, it is considered a physical component within the VMware virtual infrastructure.
VMware’s VirtualCenter is the software tool used to manage virtual environments that are built on the VMware virtualization platform. VirtualCenter creates a hierarchical structure of virtual objects that enables a system administrator to logically lay out his virtual infrastructure configuration. VirtualCenter also introduces other advanced VMware functionality such as Distributed Resource Scheduling (DRS), VMotion, and High Availability (HA) that can be used to enhance the benefits of a virtual infrastructure.
VirtualCenter provides a robust WSDL that Foglight for VMware leverages to capture and manipulate key characteristics and performance metrics of the various object types and objects found within the virtual infrastructure configuration. Each VirtualCenter instance that is to be monitored using this product must have a VMware Performance Agent configured for it that points to the Web service interface. As mentioned in the Installing the Virtualization Management Capabilities guide, this agent can be installed on the VirtualCenter Server itself because all of the required components for the proper operation of the agent come pre-configured.
A single VirtualCenter Server can monitor approximately 100 VMware ESX Servers and 1500 virtual machines before performance and scalability challenges demand the introduction of a second VirtualCenter Server. Multiple VirtualCenter instances can be disbursed geographically to localize the management of large, distributed VI3 or vSphere 4 implementations.
Herramientas de autoservicio
Base de conocimientos
Notificaciones y alertas
Soporte de productos
Descargas de software
Documentación técnica
Foros de usuarios
Tutoriales en video
Aviso de actualizaciones de páginas web (RSS)
Comuníquese con nosotros
Obtenga asistencia con las licencias
Soporte Técnico
Ver todos
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación