Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[NorthStar] Check Cluster Status shows one node without priority and cluster is unstable

0

0

Article ID: KB36696 KB Last Updated: 22 Apr 2021Version: 1.0
Summary:

When going into net_setup.py, under HA Setting > Check cluster status, output displays FQDN for hostname.  Additionally, the cluster appears in an unstable state.

Symptoms:

Cluster status check is showing two sets of hostnames for each node in the cluster.  The second set is displaying FQDN.  Additionally, even though priority is set for each node, one of the nodes does not have a priority, and the cluster seems unstable.

General HA status

NorthStar HA Status

Host Name	    IPv4		Role			 Version
nos-1	    10.10.10.35		Infrastructure		 5.1.0-20191210_220522_bb37a329b_64.x86_64
nos-2	    10.10.10.37		Active,Coordinator	 5.1.0-20191210_220522_bb37a329b_64.x86_64
nos-1.example.com			   Standby		    5.1.0-20191210_220522_bb37a329b_64.x86_64
nos-3	    10.10.10.39		Standby			 5.1.0-20191210_220522_bb37a329b_64.x86_64
nos-2.example.com			   Infrastructure	    5.1.0-20191210_220522_bb37a329b_64.x86_64
nos-3.example.com			   Infrastructure	    5.1.0-20191210_220522_bb37a329b_64.x86_64

ZooKeeper cluster status:

Host Name	    IPv4		Mode			 Version
nos-1	    10.10.10.35		follower		 3.5.4-beta-7f51e5b68cf2f80176ff944a9ebd2abbc65e7327, built on 05/11/2018 16
nos-3	    10.10.10.39		follower		 3.5.4-beta-7f51e5b68cf2f80176ff944a9ebd2abbc65e7327, built on 05/11/2018 16
nos-2	    10.10.10.37		leader			 3.5.4-beta-7f51e5b68cf2f80176ff944a9ebd2abbc65e7327, built on 05/11/2018 16
Solution:

When setting up a cluster, it is recommended to use only hostname instead of using any fully qualified domain name (FQDN), like nos-1.example.com.  Using FQDN can cause cluster instabilities.

There are 4 places to check for FQDN on NorthStar:

  1. /opt/northstar/data/ha_setup.json
  2. /etc/hosts
  3. /etc/sysconfig/network
  4. hostnamectl
  5. /etc/hostname

If an FQDN exists in any one of these files, edit the file and remove the domain portion of the hostname.  In this example, instead of nos-1.example.com, modify it to read only nos-1.  Once this is modified, restart northstar by issuing the command:

service northstar restart

Repeat the same procedure for all nodes in the cluster.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search