6.5.1

4 Select a solution.
The Summary tab displays more information about the solution.
5 To view vService provider information, click Monitor, and click vServices.
Monitoring Agents
The vCenter Solutions Manager displays the vSphere ESX Agent Manager agents that you use to deploy and
manage related agents on ESX/ESXi hosts.
You can use the Solutions Manager to keep track of whether the agents of a solution are working as
expected. Outstanding issues are reected by the solution's ESX Agent Manager status and a list of issues.
When the status of a solution changes, the Solutions Manager updates the ESX Agent Manager summary
status and state. Administrators use this status to track whether the goal state is reached.
The agent health status is indicated by a specic color.
Table 5‑1. ESX Agent Manager health status
Status Description
Red The solution must intervene for the ESX Agent Manager to
proceed. For example, if a virtual machine agent is
powered o manually on a compute resource and the ESX
Agent Manager does not aempt to power on the agent.
The ESX Agent Manager reports this action to the solution,
and the solution alerts the administrator to power on the
agent.
Yellow The ESX Agent Manager is actively working to reach a goal
state. The goal state can be enabled, disabled, or
uninstalled. For example, when a solution is registered, its
status is yellow until the ESX Agent Manager deploys the
solutions agents to all the specied compute resources. A
solution does not need to intervene when the ESX Agent
Manager reports its ESX Agent Manager health status as
yellow.
Green A solution and all its agents have reached the goal state.
Monitoring vServices
A vService is a service or function that a solution provides to virtual machines and vApps. A solution can
provide one or more vServices. These vServices integrate with the platform and are able to change the
environment in which the vApp or virtual machine runs.
A vService is a type of service for a virtual machine and a vApp provided by a vCenter extension. Virtual
machines and vApps can have dependencies on vServices. Each dependency is associated with a vService
type. The vService type must be bound to a particular vCenter extension that implements that vService type.
This vService type is similar to a virtual hardware device. For example, a virtual machine can have a
networking device that at deployment must be connected to a particular network.
The vService Manager allows a solution to connect to operations related to OVF templates:
n
Importing OVF templates. Receive a callback when OVF templates with a vService dependency of a
certain type are imported.
n
Exporting OVF templates. Inserts OVF sections when a virtual machine is exported.
n
OVF environment generation. Inserts OVF sections into the OVF environment at the power-on instance.
The vServices tab in the Solution Manager provides details for each vCenter extension. This information
allows you to monitor vService providers and list the virtual machines or vApps to which they are bound.
vSphere Monitoring and Performance
126 VMware, Inc.