Control Node Management
Intended for use with Cassatt Active Response
V5.0.
Cassatt Active Response is designed to require minimal maintenance; since your control nodes are the automatic management system for your Cassatt Active Response environment, you'll want to interrupt control node activities as infrequently as possible.
Whether you are using one control node or two, most procedures you'll perform are standard Linux operations, and most of these are presented within the context of a larger procedure, such as upgrading Cassatt Active Response or performing a backup. I'll list procedures that involve control node operations at the end of this article.
You do need to know a few things about Cassatt Active Response, however—and particularly the optional dual-control node setup—to make sure everything runs smoothly and you don't inadvertently interrupt an automatic Cassatt Active Response function.
Follow these guidelines whenever you perform actions on a control node:
- Whenever possible, use the Controller or a Cassatt-provided command to interact with Cassatt Active Response and the contents of the /cassatt directory.
If you use a shell to edit items in /cassatt, for example, you risk interruption if the active control node needs to fail over to the standby control node. A task that's interrupted could leave behind corrupted files and other debris. Cassatt Active Response commands are designed to accommodate failover, and clean up any tasks that are incomplete when failover occurs.
- Do not run the Controller in more than one browser window on the same computer.
The Cassatt Active Response web application state can become confused across multiple browser windows.
- If you need to start, stop, or restart Cassatt Active Response, use these
cccoreservice commands:
/opt/cassatt/bin/cccoreservice start
If you run this
in a single control node configuration, cccoreservice simply
starts the Cassatt Active Response service on the control node. If you
run it on one of the control nodes in a dual control node
configuration, cccoreservice ensures
that the failover software is running and then starts the
Cassatt Active Response service.
/opt/cassatt/bin/cccoreservice stop
If you run this in a single control node configuration,
cccoreservice stops the Cassatt Active Response
service on the control node. If you
run it on a control node in a dual control node configuration,
cccoreservice disables the
Cassatt Active Response service in the failover software, which prevents
Cassatt Active Response from running on either control node.
/opt/cassatt/bin/cccoreservice restart
If you run this in a single control node configuration, cccoreservice stops
and then restarts the Cassatt Active Response service on the control node. If you run it on a
control node in a dual control node configuration, cccoreservice send
a request to the failover software to restart the Cassatt Active Response service on the currently
active control node.
- To see the status of a control node, use the cccoreservice
status command.
Looking for a control node procedure, or just want to know more about your control nodes? The following list of articles will help you find everything you need to know.
Concepts and general information:
Standard system administration:
Problems and troubleshooting:
Was this article useful? Tell us what you think.
Email infocentral@cassatt.com.
|
