Chapter 50. Getting started with TIPC

Procedure

1. Create the /etc/modules-load.d/tipc.conf file with the following content:

   tipc

   Copy to Clipboard

2. Restart the systemd-modules-load service to load the module without rebooting the system:

   # systemctl start systemd-modules-load

   Copy to Clipboard

Procedure

1. Optional: Set a unique node identity, such as a UUID or the node’s host name:

   # tipc node set identity host_name

   Copy to Clipboard

   The identity can be any unique string consisting of a maximum 16 letters and numbers.

   You cannot set or change an identity after this step.

2. Add a bearer. For example, to use Ethernet as media and enp0s1 device as physical bearer device, enter:

   # tipc bearer enable media eth device enp1s0

   Copy to Clipboard
3. Optional: For redundancy and better performance, attach further bearers using the command from the previous step. You can configure up to three bearers, but not more than two on the same media.
4. Repeat all previous steps on each node that should join the TIPC network.

Verification

1. Display the link status for cluster members:

   # tipc link list
   broadcast-link: up
   5254006b74be:enp1s0-525400df55d1:enp1s0: up

   Copy to Clipboard

   This output indicates that the link between bearer enp1s0 on node 5254006b74be and bearer enp1s0 on node 525400df55d1 is up.

2. Display the TIPC publishing table:

   # tipc nametable show
   Type       Lower      Upper      Scope    Port       Node
   0          1795222054 1795222054 cluster  0          5254006b74be
   0          3741353223 3741353223 cluster  0          525400df55d1
   1          1          1          node     2399405586 5254006b74be
   2          3741353223 3741353223 node     0          5254006b74be

   Copy to Clipboard
   • The two entries with service type 0 indicate that two nodes are members of this cluster.
   • The entry with service type 1 represents the built-in topology service tracking service.
   • The entry with service type 2 displays the link as seen from the issuing node. The range limit 3741353223 represents the peer endpoint’s address (a unique 32-bit hash value based on the node identity) in decimal format.