Managing Float IPs in a Logsign Cluster

Managing Float IPs in a Logsign Cluster

A float IP is a shared address for a cluster service, such as the Logsign user interface or syslog collection. You define the float IP once and assign it to the servers that can hold it. One of these servers holds the address at a time. If that server has a problem, another assigned server takes over the address.

Add a float IP and assign it to servers

  1. Open Settings > System > Cluster and select the Float IPs tab.
  2. Click Float IP. In the New Float IP window, enter the Name, IP, Netmask and Interface values, then click Save. For Interface, use the network interface name on the servers that will hold the address (for example, ens18).
  3. Select the Servers tab. Click Edit on each server that can hold the float IP. In the float IP list, select the float IP and click Add Float IP.
  4. Click Save Plan.
  5. Connect to the master node over SSH and apply the cluster plan with the following command:
/opt/logsign-venv/bin/logsign-python /opt/logsign-maintenance/cluster.py apply_plan

Change an existing float IP

The Float IPs list does not have an edit button. To change a float IP, add it again with the same name and the new values.

  1. On the Float IPs tab, click Float IP.
  2. Enter the existing Name exactly as it appears in the list.
  3. Enter all of the IP, Netmask and Interface values, including the values that do not change, then click Save.
  4. Apply the cluster plan from the master node with the apply_plan command above.

Logsign replaces the float IP with the new values. The servers that already hold this float IP also get the new values. Servers that do not have this float IP assigned do not change.

Verify the change

On the server that currently holds the float IP, run the following command:

ip -4 addr show

Find the float IP address in the output and check its prefix length. For example, if you changed the netmask from 255.255.255.224 to 255.255.255.0, the address must show /24. Then make sure that the log sources can reach the address. Do this check for each float IP that you changed.

If the old netmask stays on an earlier version

On earlier Logsign versions, a change on the Float IPs tab does not reach the servers that hold the float IP. The Float IPs list shows the new value, but the server keeps the old netmask. A log source whose address falls outside the old range, or on its broadcast address, can then fail to send logs. To correct this without an upgrade:

  1. Open the Config Plan tab.
  2. Find the float IP under each server that holds it. The path is servers.<server IP>.float_ips.<float IP name>.netmask.
  3. Set this value to the same netmask that the Float IPs tab shows. Change only the servers that hold this float IP.
  4. Save the plan.
  5. Run the apply_plan command on the master node.
  6. Verify the change with ip -4 addr show as described above.

If the apply_plan command stops with an error, or the address still shows the old prefix, contact Logsign Support.

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more
Become a Certified Logsign User/Administrator
Sign-up for Logsign Academy and take the courses to learn about Logsign USO Platform in detail. Enjoy the courses, and get your badges and certificates. In these courses, you'll learn how to use Logsign in your work and add value to your career.
Visit Our Blog
Our Logsign USO Platform illustrate our expertise. So do the blog. Through our blog posts, deepen your knowledge on various SecOps topics or get updated about important news & modern approaches for cybersecurity. Get into the habit of reading valuable information provided by Logsign. Be a step ahead.