tiebreaker software CLI doesn't start and remain on the root

Dawood — Thu, 12 Dec 2019 09:31:30 GMT

I'm already install tibreaker for metrocluster, but failed to start, it supposed to open CLI

NetApp MetroCluster Tiebreaker :>

does anyone have the same issue in the past? access is already "root" an remains on root

Re: tiebreaker software CLI doesn't start and remain on the root

wareer — Thu, 09 Jan 2025 02:35:15 GMT

You must be aware of the following additional requirements:

The Tiebreaker software is installed on a third site, which allows the software to distinguish between an inter-switch link (ISL) failure (when inter-site links are down) and a site failure. Your host system must meet certain requirements before you can install or upgrade the Tiebreaker software to monitor the MetroCluster configuration.
You must have "root" privileges to install MetroCluster Tiebreaker software and the dependant packages.
You can only use one MetroCluster Tiebreaker monitor per MetroCluster configuration to avoid any conflict with multiple Tiebreaker monitors.
When selecting the Network Time Protocol (NTP) source for the Tiebreaker software, you must use a local NTP source. The Tiebreaker software should not use the same source as the MetroCluster sites that the Tiebreaker software monitors.

Disk capacity: 8 GB

Firewall:

Direct access for setting up AutoSupport messages
SSH (port 22/TCP), HTTPS (port 443/TCP), and ping (ICMP)

Use the command to see if the service is running: systemctl status netapp-metrocluster-tiebreaker-software
If not, run the systemctl start netapp-metrocluster-tiebreaker-software command to make it run
If the service is not shown, try reinstalling Tiebreaker

topic Re: tiebreaker software CLI doesn't start and remain on the root in ONTAP Discussions

tiebreaker software CLI doesn't start and remain on the root

Re: tiebreaker software CLI doesn't start and remain on the root