1Whatsup(1)                          Whatsup                         Whatsup(1)
2
3
4

NAME

6       whatsup - list up and/or down nodes in a cluster
7

SYNOPSIS

9       whatsup [OPTION]... [NODES]...
10

DESCRIPTION

12       whatsup  lists  which  nodes are currently up or down in a cluster.  It
13       determines which nodes are up or down based on information provided  by
14       the  nodeupdown(3)  library.   Configuration  of  backend components or
15       clusterlists for the nodeupdown(3) library may be needed.   Please  see
16       libnodeupdown(3).
17
18       whatsup  will  check  on the status of every node in the cluster unless
19       specific nodes are listed at the  command  line.   If  the  first  node
20       listed  is  "-",  nodes will be read in from standard input.  The nodes
21       can be listed in hostrange format, comma separated lists, or space sep‐
22       arated lists.  See the section below on HOST RANGES for instructions on
23       how to list hosts in hostrange format.  The hostnames  listed  must  be
24       the shortened names of hostnames.
25
26       The  exit value of whatsup depends on the options performed on the com‐
27       mand line.  If the default --updown option is used, the exit value will
28       be 0 if the command succeeds without error.  If the --up option is used
29       and no nodes are specified via the command line or standard input,  the
30       exit  value will be 0 if all cluster nodes are up.  If nodes are speci‐
31       fied via the command line or standard input, the exit value wil be 0 if
32       all the specified nodes are up.  The behavior is similar for the --down
33       option.
34
35

OPTIONS

37       -h, --help
38              Print help and exit
39
40       -v, --version
41              Print version and exit
42
43       -o STRING, --hostname=STRING
44              server hostname (default=localhost)
45
46       -p INT, --port=INT
47              server port (default=8649)
48
49       -b, --updown
50              List both up and down nodes (default)
51
52       -u, --up
53              List only up nodes
54
55       -d, --down
56              List only down nodes
57
58       -t, --count
59              List only node counts
60
61       -q, --hostrange
62              List nodes in hostrange format (default)
63
64       -c, --comma
65              List nodes in comma separated list
66
67       -n, --newline
68              List nodes in newline separated list
69
70       -s, --space
71              List nodes in space separated list
72
73       -m, --module
74              Use a specific backend module for up-down calculations.
75
76       -r, --last-up-time
77              Output last known up time of nodes and their current up or  down
78              state. This option may not be available on some configurations.
79
80       -l, --log
81              Enter  whatsup  logging  mode.   Whatsup will regularly poll the
82              backend tool to calculate up-down state changes and output  them
83              to the appropriate output.
84
85       -f, --log-file
86              Specify  the  log file Whatsup should output logging information
87              to.  If not specified, defaults to stdout.
88
89       -e, --log-poll
90              Specify the length in seconds the log  mode  of  whatsup  should
91              regularly poll.  Default is 30 seconds.
92
93       -M, --monitor
94              Monitor up-down state changes through event monitoring.
95

HOST RANGES

97       As  noted in sections above, whatsup accepts ranges of hostnames in the
98       general form: prefix[n-m,l-k,...], where n < m and l < k, etc.,  as  an
99       alternative  to  explicit lists of hosts.  This form should not be con‐
100       fused with  regular  expression  character  classes  (also  denoted  by
101       ``[]'').  For  example,  foo[19]  does  not represent foo1 or foo9, but
102       rather represents a degenerate range: foo19.
103
104       This range syntax is meant only as a convenience  on  clusters  with  a
105       prefixNN  naming  convention  and specification of ranges should not be
106       considered necessary -- the list foo1,foo9 could be specified as  such,
107       or by the range foo[1,9].
108
109       Some examples of range usage follow:
110
111       List all nodes among foo01,foo02,...,foo05 that are up and down
112           whatsup foo[01-05]
113
114       List all nodes among foo7,foo9,foo10 that are up and down
115           whatsup foo[7,9-10]
116
117       As  a  reminder to the reader, some shells will interpret brackets ('['
118       and ']') for pattern matching.  Depending on your shell, it may be nec‐
119       essary  to  enclose  ranged lists within quotes.  For example, in tcsh,
120       the above two examples should be executed as:
121
122           whatsup "foo[01-05]"
123           whatsup "foo[7,9-10]"
124
125

EXAMPLES

127       List all nodes that are up and down.
128            whatsup
129
130       List all nodes that are down
131            whatsup -d
132
133       List all nodes among foo[0-20] that are down
134            whatsup -d foo[0-20]
135
136       List all nodes that are up and down by their alternate names
137            whatsup -a
138
139       List all nodes among foo[5-25] that are up by their alternate names
140            whatsup -u -a foo[5-25]
141
142       List all nodes that are up in comma separated lists.
143            whatsup -u -c
144
145       List all nodes that are up among the nodes foo2, foo4, and foo8
146            whatsup -u foo2,foo4,foo8
147
148       Only output the number of nodes that are up and down
149            whatsup -t
150
151       Only output the number of up nodes
152            whatsup -u -t
153
154       Only output the number of up nodes among foo[5-25]
155            whatsup -u -t foo[5-25]
156

FILES

158       /usr/bin/whatsup
159

SEE ALSO

161       libnodeupdown(3), nodeupdown.conf(5)
162

ORIGIN

164       Developed by Albert Chu  <chu11@llnl.gov>  on  LLNL's  Linux  clusters.
165       This software is open source and distributed under the terms of the Gnu
166       GPL.
167
168
169
170LLNL                              August 2003                       Whatsup(1)
Impressum