corosync-cfgtool - Man Page

An administrative tool for corosync.

Synopsis

corosync-cfgtool [[-i IP_address] [-b] -s] [-R] [-L] [-k nodeid] [-a nodeid] [-h] [-H]

Description

corosync-cfgtool A tool for displaying and configuring active parameters within corosync.

Options

-i

Finds only information about the specified interface IP address or link id with -s.

-s

Displays the status of the current links on this node for UDP/UDPU, with extended status for KNET. After each link, the nodes on that link are displayed in order with their status, for example there are 3 nodes with KNET transportation: LINK ID 0:
   id     = 192.168.100.80
   status:
       node 0: link enabled: 1     link connected: 1
       node 1: link enabled: 1     link connected: 1
       node 2: link enabled: 1     link connected: 1

-b

Displays the brief status of the current links on this node (KNET only) when used with "-s". If any interfaces are faulty, 1 is returned by the binary. If all interfaces are active 0 is returned to the shell. After each link, the nodes on that link are displayed in order with their status encoded into a single digit, or characters 'n', 'd' and '?' with special meaning. 1=link enabled, 2=link connected, So a 3 in a node position indicates that the link is both enabled and connected. Status represented by character 'n' is used for localhost link. Character '?' means that Crosync was unable to get status of link from knet (log should contain more information). Character 'd' shouldn't appear and it means that Corosync was unable to configure a link and it is result of some error which should have been logged.

The output will be: LINK ID 0:
   id     = 192.168.100.80
   status = 333

-R

Tell all instances of corosync in this cluster to reload corosync.conf.

-L

Tell corosync to reopen all logging files. In contrast to other subcommands, nothing is displayed on terminal if call is successful.

-k

Kill a node identified by node id.

-a

Display the IP address(es) of a node.

-h

Print basic usage.

-H

Shutdown corosync cleanly on this node.

See Also

corosync_overview(7),

Author

Angus Salkeld

Info

2020-02-10