Daemon states in Ecosystem Manager are active, standby, passive, or out of service (OOS). Daemon state changes occur in response to a state change request from the Eventconsumer.
When the user requests a state change for a daemon, the Control Master runs the state change control script to make the requested state change.
If the script execution is successful (where the exit code is 0), the Control Master generates a STATE event for the daemon to indicate the state that was achieved. If the script execution fails, the Control Master generates an alert indicating it is unable to change the resource state.
You can request the state change programmatically by using sendevent to send a RQ_STATE event. For example, you can request a state change for the sampleDaemon to standby state (20):
sendevent --et RQ_STATE -r myDaemon --tds DAEMONCOMPONENTS --st 20 -t DAEMON
Please refer to the Teradata Ecosystem Manager User Guide for more information about daemon state changes in the Ecosystem Explorer portlet.
Supported for possible dual systems monitoring and control (DSMC), but all alert functions can be done using sendevent with an Alert type of an event.