.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.47.16.
.TH PACEMAKER "8" "January 2021" "Pacemaker 2.0.5" "System Administration Utilities"
.SH NAME
Pacemaker \- Part of the Pacemaker cluster resource manager
.SH SYNOPSIS
crm_simulate <data source> <operation> [options]
.SH DESCRIPTION
crm_simulate \- simulate a Pacemaker cluster's response to events
.SH OPTIONS
.SS "Help Options:"
.TP
\fB\-h\fR, \fB\-\-help\fR
Show help options
.TP
\fB\-\-help\-all\fR
Show all help options
.TP
\fB\-\-help\-operations\fR
Show operations options
.TP
\fB\-\-help\-synthetic\fR
Show synthetic cluster event options
.TP
\fB\-\-help\-output\fR
Show output options
.TP
\fB\-\-help\-source\fR
Show data source options
.SS "Operations:"
.TP
\fB\-R\fR, \fB\-\-run\fR
Determine cluster's response to the given configuration and status
.TP
\fB\-S\fR, \fB\-\-simulate\fR
Simulate transition's execution and display resulting cluster status
.TP
\fB\-X\fR, \fB\-\-in\-place\fR
Simulate transition's execution and store result back to input file
.TP
\fB\-s\fR, \fB\-\-show\-scores\fR
Show allocation scores
.TP
\fB\-U\fR, \fB\-\-show\-utilization\fR
Show utilization information
.TP
\fB\-P\fR, \fB\-\-profile\fR
Run all tests in the named directory to create profiling data
.TP
\fB\-N\fR, \fB\-\-repeat\fR=\fI\,N\/\fR
With \fB\-\-profile\fR, repeat each test N times and print timings
.TP
\fB\-j\fR, \fB\-\-pending\fR
Display pending state if 'record\-pending' is enabled
.SS "Synthetic Cluster Events:"
.TP
\fB\-u\fR, \fB\-\-node\-up\fR=\fI\,NODE\/\fR
Bring a node online
.TP
\fB\-d\fR, \fB\-\-node\-down\fR=\fI\,NODE\/\fR
Take a node offline
.TP
\fB\-f\fR, \fB\-\-node\-fail\fR=\fI\,NODE\/\fR
Mark a node as failed
.TP
\fB\-i\fR, \fB\-\-op\-inject\fR=\fI\,OPSPEC\/\fR
Generate a failure for the cluster to react to in the simulation.
See `Operation Specification` help for more information.
.TP
\fB\-F\fR, \fB\-\-op\-fail\fR=\fI\,OPSPEC\/\fR
If the specified task occurs during the simulation, have it fail with return code ${rc}.
The transition will normally stop at the failed action.
Save the result with \fB\-\-save\-output\fR and re\-run with \fB\-\-xml\-file\fR.
See `Operation Specification` help for more information.
.TP
\fB\-t\fR, \fB\-\-set\-datetime\fR=\fI\,DATETIME\/\fR
Set date/time (ISO 8601 format, see https://en.wikipedia.org/wiki/ISO_8601)
.TP
\fB\-q\fR, \fB\-\-quorum\fR=\fI\,QUORUM\/\fR
Specify a value for quorum
.TP
\fB\-w\fR, \fB\-\-watchdog\fR=\fI\,DEVICE\/\fR
Assume a watchdog device is active
.TP
\fB\-g\fR, \fB\-\-ticket\-grant\fR=\fI\,TICKET\/\fR
Grant a ticket
.TP
\fB\-r\fR, \fB\-\-ticket\-revoke\fR=\fI\,TICKET\/\fR
Revoke a ticket
.TP
\fB\-b\fR, \fB\-\-ticket\-standby\fR=\fI\,TICKET\/\fR
Make a ticket standby
.TP
\fB\-e\fR, \fB\-\-ticket\-activate\fR=\fI\,TICKET\/\fR
Activate a ticket
.SS "Output Options:"
.TP
\fB\-I\fR, \fB\-\-save\-input\fR=\fI\,FILE\/\fR
Save the input configuration to the named file
.TP
\fB\-O\fR, \fB\-\-save\-output\fR=\fI\,FILE\/\fR
Save the output configuration to the named file
.TP
\fB\-G\fR, \fB\-\-save\-graph\fR=\fI\,FILE\/\fR
Save the transition graph (XML format) to the named file
.TP
\fB\-D\fR, \fB\-\-save\-dotfile\fR=\fI\,FILE\/\fR
Save the transition graph (DOT format) to the named file
.TP
\fB\-a\fR, \fB\-\-all\-actions\fR
Display all possible actions in DOT graph (even if not part of transition)
.SS "Data Source:"
.TP
\fB\-L\fR, \fB\-\-live\-check\fR
Connect to CIB manager and use the current CIB contents as input
.TP
\fB\-x\fR, \fB\-\-xml\-file\fR=\fI\,FILE\/\fR
Retrieve XML from the named file
.TP
\fB\-p\fR, \fB\-\-xml\-pipe\fR
Retrieve XML from stdin
.SS "Application Options:"
.TP
\-$, \fB\-\-version\fR
Display software version and exit
.TP
\fB\-V\fR, \fB\-\-verbose\fR
Increase debug output (may be specified multiple times)
.TP
\fB\-Q\fR, \fB\-\-quiet\fR
Display only essential output
.SH OPERATION SPECIFICATION
The OPSPEC in any command line option is of the form ${resource}_${task}_${interval_in_ms}@${node}=${rc} memcached_monitor_20000@bart.example.com=7, for example).  ${rc} is an OCF return code.  For more information on these return codes, refer to https://clusterlabs.org/pacemaker/doc/en\-US/Pacemaker/2.0/html/Pacemaker_Administration/s\-ocf\-return\-codes.html
.SH EXAMPLES
Pretend a recurring monitor action found memcached stopped on node fred.example.com and, during recovery, that the memcached stop action failed:
.IP
crm_simulate \-LS \-\-op\-inject memcached:0_monitor_20000@bart.example.com=7 \-\-op\-fail memcached:0_stop_0@fred.example.com=1 \-\-save\-output /tmp/memcached\-test.xml
.PP
Now see what the reaction to the stop failed would be:
.IP
crm_simulate \-S \-\-xml\-file /tmp/memcached\-test.xml
.SH AUTHOR
Written by Andrew Beekhof