HP ProLiant DL380G5-WSS 3.7.0 HP StorageWorks HP Scalable NAS File Serving Sof - Page 263

If replication is not running, the output will specify the following in place of the "current sentinel" line: replication is not running and the current sentinel is not defined The rplstatus command includes the following options that can be included in scripts. Only one option can be specified at a time. If an option is specified, the script runs silently without output to stdout. -status If replication is running on the node on which the script is run, the exit value is 0. Otherwise, the exit value is 1 (or 2 in case of error). -sentinel If the node on which the script is run is also the current sentinel, the exit value is 0. Otherwise, the exit value is 1 (or 2 in case of error). The following shell programming example shows the use of the -sentinel option. #rplstatus -sentinel #echo $? #0 //if this node is the current sentinel Replication state transitions and rplcontrol The rplcontrol utility controls the replication state by sending commands (such as start or stop commands) to the cluster or to individual nodes. The commands can be specified either by name (using the -s option) or by a number (using the -c option). IMPORTANT: In general, the system handles sending rplcontrol commands as necessary. Sending an inappropriate command can at best take processing time away from a running replication and at worst cause an undesirable effect. You should use this tool with caution. The individual rplcontrol commands can be used only when replication is in certain states. Some rplcontrol commands also cause the state to change. The following table lists the commands and specifies the state that replication must be in when the command is run. If a command causes the replication state to change, the table also lists the new state. HP Scalable NAS File Serving Software administration guide 263