Created on
12-13-2024
08:49 AM
Edited on
04-22-2025
01:42 AM
By
Jean-Philippe_P
Description |
This article describes how to check bandwidth using 'iPerf' if replication fails between primary and follower nodes in an HA /DR setup. |
Scope | FortiSIEM. |
Solution |
In high availability (HA) or disaster recovery (DR) setups, encountering errors like 'Failed to execute AddSuperFollower task on node' typically indicates issues in the communication or synchronization between the nodes, which could be due to a variety of factors such as network issues.
One potential cause for this error is insufficient network bandwidth between the servers, as a reliable and high-speed network is critical for replication and synchronization tasks, especially in a multi-node HA/DR environment. If network performance is suboptimal, it can result in failed tasks like AddSuperFollower or other replication-related errors.
See this FortiSIEM documentation.
On the server machine, run the following command to start iPerf in server mode.
iperf -s
The above command will start the iPerf server and listen on port 5001 by default.
iperf -c IP -t 60
-c, --client host | host%device -t, --time n|0
The output will display the bandwidth between the client and server for each interval, along with other metrics such as Network bandwidth usage.
To temporarily allow TCP traffic on port 5001 through the firewall, use the following command:
sudo firewall-cmd --zone=public --add-port=5001/tcp
This command adds a rule to the public zone, permitting TCP traffic on port 5001 until the next system reboot or firewall reload. To make this change permanent, use the --permanent flag and reload the firewall configuration. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.