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

[EOL/EOE] When will an NSM failover occur?

0

0

Article ID: KB13214 KB Last Updated: 18 Oct 2020Version: 3.0
Summary:
Note: A product listed in this article has either reached hardware End of Life (EOL) OR software End of Engineering (EOE).  Refer to End of Life Products & Milestones for the EOL, EOE, and End of Support (EOS) dates.
NSM will failover to the secondary server if no heartbeats are received
Symptoms:
NSM will failover too quickly if communication with the NSM peer is lost.
Solution:
The following heartbeat information is in the haSvr.cfg file by default:

highAvail.heartbeatInterval 15
highAvail.timeoutHeartbeats 4


This means that the configuration will failover if 4 NSM heartbeats are missed, over the span of 60 seconds. Therefore, NSM will failover over to the secondary server, if the primary is down for more than 1 minute. These are the default values. Heartbeats are only exchanged if there is no data exchanged between the two cluster members.

This can be configured during installation of NSM.
 
Modification History:
2020-10-18: Tagged article for EOL/EOE.
 
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