Auto update of the agent status
The Smart Agent that is installed on the same host as that of RSCD agent regularly notifies the status information about the RSCD agent to the Application Server. You can use this information to troubleshoot the connectivity or other issues with the RSCD agent before running the patching, provisioning, and other jobs.
The Smart Agent contains the built in heartbeat task for conveying the status information. By default, heartbeats are sent after every 5 minutes.
When you deploy and start the Smart Agent, the following events occur after the heartbeat task is initiated:
- The Smart Agent sends the heartbeat request to the Smart Hub. The request contains the status of the RSCD agent along with timestamp.
- After receiving the heartbeat request from the Smart Agent, the Smart Hub performs the following tasks:
- Verifies whether the RSCD agent state is changed. If the state of the RSCD agent is changed, it stores this information to be shared with the Application Server later.
- Verifies whether the server is still active or decommissioned. If the server is decommissioned, it responds to the heartbeat request with SA-1104 error code.
The Application Server processes the request received from the Smart Hub and updates the status of the RSCD and Smart Agent.
The following codes are used to represent different states:Code
Description
SA-1100
The state of the RSCD agent is changed.
SA-1101
The state of the Smart Agent is changed.
SA-1102
The state of RSCD Agent and Smart Agent is changed.
SA-1103
The server state is not changed.
SA-1104
The server is decommissioned.
The Smart Hub also regularly monitors the heartbeat requests from the Smart Agent. If no request is received from the Smart Agent as scheduled, it stores this information to be shared later with the Application Server. When the Application Server retrieves this information, it updates the Smart Agent properties. For more information about these properties, see Properties-of-the-Smart-Agent-and-Smart-Hub.