 | ||
| About intra-system communications | ||
|---|---|---|
| Prev | About communications, membership, and data protection in the cluster | Next |
| ||
| About intra-system communications | ||
|---|---|---|
| Prev | About communications, membership, and data protection in the cluster | Next |
Within a system, the VCS engine (HAD) uses a VCS-specific communication protocol known as Inter Process Messaging (IPM) to communicate with the GUI, the command line, and the agents. The following illustration shows basic communication on a single VCS system. Note that agents only communicate with HAD and never communicate with each other.
Click the thumbnail above to view full-sized image.
The following illustration depicts communication from a single agent to HAD.
Click the thumbnail above to view full-sized image.
The agent uses the agent framework, which is compiled into the agent itself. For each resource type configured in a cluster, an agent runs on each cluster system. The agent handles all resources of that type. The engine passes commands to the agent and the agent returns the status of command execution. For example, an agent is commanded to bring a resource online. The agent responds back with the success (or failure) of the operation. Once the resource is online, the agent communicates with the engine only if this status changes.