|
|
|
The vCenter AIM detects the logical and physical relationships between the components in a vSphere environment. The AIM provides a view of the entire virtualized environment and manages the following resource types and properties:
Provides information about the health status of the vCenter Server computer. For example, status and data about CPU, datastore, and memory usage.
Serves as a container for your hosts, virtual machines, resource pools, or clusters. Data centers can represent organizational structures if their virtual configurations meet the requirements of specific departments. You can also use data centers to create isolated virtual environments for testing or organization purposes.
Represents all computing and memory resources of a physical server on which an ESX Server runs.
VMware vSphere lets you enable Fault Tolerance (FT) on a VM defined to a cluster which is configured for High Availability (HA). Fault Tolerance creates a secondary VM on another ESX Server in the cluster. The secondary VM operates in lock-step mode with the primary VM that is executing the workload. If there is a failure, the secondary VM immediately takes over the workload execution from the point of failure. CA Server Automation discovers and manages primary and secondary VMs in a cluster.
Defines partitions of physical computing and memory resources of a single host or a cluster. You can partition any resource pool into smaller resource pools to divide and assign resources to specific groups or for specific purposes. You can also hierarchically organize and nest resource pools.
A vApp is a specific resource pool which treats a collection of VMs as a single unit. vApp uses the Open Virtualization Format (OVF). OVF is a standard to specify and encapsulate all components of a multi-tier application and the operational policies and service levels that are associated with it. CA Server Automation can perform operations on a vApp. An operation on a vApp is propagated to all VMs in the vApp.
Specifies virtualized x86 environments in which guest operating systems and applications can run. When you create a virtual machine, it is assigned to a particular host, cluster, or resource pool, and to a datastore. A virtual machine consumes resources dynamically on its physical host, in the same manner a physical device consumes energy dynamically depending on its workload.
Specifies a virtual representation of combinations of underlying physical storage resources in a data center. Local disks on a server provide the physical storage resources, using SAN disk arrays, and other disk media.
Defines the disk drive in a virtual guest operating system. A virtual disk is a specific file or a set of files that reside on the local host or on a remote file system. The virtual disk behaves like a physical disk drive in an operating system.
Abstracts the configuration of virtual switches from the host to the datacenter level. A vNetwork Distributed Switch operates as a single virtual switch that spans across all hosts in a datacenter which are associated with that switch. vNetwork Distributed Switches consist of distributed port groups which are similarly configured to port groups on standard switches, but extend across multiple hosts. These properties allow virtual machines to maintain a consistent network configuration as they migrate among multiple hosts.
Works like a physical switch. Each ESX Server has its own virtual switches that connect to virtual machines through port groups. These virtual switches also have uplink connections to the physical Ethernet adapters on the ESX server. Virtual machines communicate with the outside world through physical Ethernet adapters connected to virtual switch uplinks.
Specifies a physical Ethernet adapter on an ESX Server.
Specifies a virtual Ethernet adapter on a virtual machine. The guest operating system communicates with the virtual Ethernet adapter through a device driver as if the virtual Ethernet adapter was a physical Ethernet adapter. The virtual Ethernet adapter has its own MAC address, one or more IP addresses, and responds to the standard Ethernet protocol exactly like a physical NIC.
Provide physical information about the CPU, memory, fan, voltage, storage, temperature, and power. Hardware sensors can be accessed in ESX servers through vCenter Server.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |