pm(1) - f14

1powerman(1)                        powerman                        powerman(1)
2
3
4

NAME

6       powerman - power on/off nodes
7

SYNOPSIS

9       pm [-options] -action [targets] [-action [targets] ...]
10

DESCRIPTION

12       powerman  provides power management in a data center or compute cluster
13       environment.  It performs operations such as power on, power  off,  and
14       power  cycle  via  remote power controller (RPC) devices.  Target host‐
15       names are mapped to plugs on RPC devices in powerman.conf(5).
16

OPTIONS

18       -1, --on targets
19              Power ON targets.
20
21       -0, --off targets
22              Power OFF targets.
23
24       -c, --cycle targets
25              Power cycle targets.
26
27       -r, --reset targets
28              Assert hardware reset for targets (if implemented by RPC).
29
30       -f, --flash targets
31              Turn beacon ON for targets (if implemented by RPC).
32
33       -u, --unflash targets
34              Turn beacon OFF for targets (if implemented by RPC).
35
36       -l, --list
37              List available targets.  If possible, output will be  compressed
38              into a host range (see TARGET SPECIFICATION below).
39
40       -q, --query-all
41              Query  plug  status of all targets.  Status is not cached;  each
42              time this option is  used,  powermand  queries  the  appropriate
43              RPC's.   Targets  connected to RPC's that could not be contacted
44              (e.g. due to network failure) are reported as status  "unknown".
45              If possible, output will be compressed into host ranges.
46
47       -Q, --query targets
48              Query plug status of specific targets.
49
50       -n, --soft-all
51              Query  soft power status of all targets (if implemented by RPC).
52              In this context, a node in the OFF state could be ON at the plug
53              but operating in standby power mode.
54
55       -N, --soft targets
56              Query  soft  power status of specific targets (if implemented by
57              RPC).
58
59       -b, --beacon-all
60              Query beacon status of all targets (if implemented by RPC).
61
62       -B, --beacon targets
63              Query beacon status of specific targets (if implemented by RPC).
64
65       -t, --temp-all
66              Query node temperature of all targets (if implemented  by  RPC).
67              Temperature  information  is  not interpreted by powerman and is
68              reported as received from the RPC on one line per  target,  pre‐
69              fixed by target name.
70
71       -P, --temp targets
72              Query  node  temperature  of specific targets (if implemented by
73              RPC).
74
75       -h, --help
76              Display option summary.
77
78       -L, --license
79              Show powerman license information.
80
81       -h, --server-host host[:port]
82              Connect to a powerman daemon on non-default host and  optionally
83              port.
84
85       -V, --version
86              Display the powerman version number and exit.
87
88       -D, --device
89              Displays RPC status information.  If targets are specified, only
90              RPC's matching the target list are displayed.
91
92       -T, --telemetry
93              Causes RPC telemetry information to be displayed as commands are
94              processed.  Useful for debugging device scripts.
95
96       -x, --exprange
97              Expand host ranges in query responses.
98
99       -g, --genders
100              If  configured  with  the  genders(3) package, this option tells
101              powerman that targets are genders attributes that  map  to  node
102              names rather than the node names themselves.
103

TARGET SPECIFICATION

105       powerman  target hostnames may be specified as comma separated or space
106       separated hostnames or host ranges.  Host ranges  are  of  the  general
107       form:  prefix[n-m,l-k,...],  where  n  <  m  and l < k, etc., This form
108       should not be confused with regular expression character classes  (also
109       denoted  by  ``[]'').  For  example, foo[19] does not represent foo1 or
110       foo9, but rather represents a degenerate range: foo19.
111
112       This range syntax is meant only as a convenience  on  clusters  with  a
113       prefixNN  naming  convention  and specification of ranges should not be
114       considered necessary -- the list foo1,foo9 could be specified as  such,
115       or by the range foo[1,9].
116
117       Some examples of powerman targets follows:
118
119       Power on hosts bar,baz,foo01,foo02,...,foo05
120           powerman --on bar baz foo[01-05]
121
122       Power on hosts bar,foo7,foo9,foo10
123           powerman --on bar,foo[7,9-10]
124
125       Power on foo0,foo4,foo5
126           powerman --on foo[0,4-5]
127
128       As a reminder to the reader, some shells will interpret brackets ([ and
129       ]) for pattern matching.  Depending on your shell, it may be  necessary
130       to  enclose ranged lists within quotes.  For example, in tcsh, the last
131       example above should be executed as:
132           powerman --on "foo[0,4-5]"
133
134

FILES

136       /usr/bin/powerman
137       /usr/bin/pm
138
139

ORIGIN

141       PowerMan was originally developed by Andrew  Uselton  on  LLNL's  Linux
142       clusters.  This software is open source and distributed under the terms
143       of the GNU GPL.
144
145