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

[SRX] Meaning of mastership log message "failed to send RE info/keepalive: errno=65, total=20 in the last 20 sec"

0

0

Article ID: KB29225 KB Last Updated: 10 Aug 2014Version: 1.0
Summary:

This article clarifies the meaning of reoccurring message "failed to send RE info/keepalive: errno=65, total=20 in the last 20 sec" that can be found in /var/log/mastership file. The messages are harmless and can be ignored on SRX platform.

Symptoms:

The following messages are seen in /var/log/mastership file:


Feb 16 14:38:14 failed to send RE info/keepalive: errno=65, total=20 in the last 20 sec
Feb 16 14:38:27 failed to receive keepalives from other RE for the last 340 sec
Feb 16 14:38:35 failed to send RE info/keepalive: errno=65, total=20 in the last 20 sec
Feb 16 14:38:48 failed to receive keepalives from other RE for the last 360 sec
Feb 16 14:38:50 ORE not booted reconnect flag TRUE
Feb 16 14:38:50 event = E_NO_IPC, state = master, param = 0x0x0
Feb 16 14:38:50 currentAction = A_WARN1
Feb 16 14:38:50 Currentstate master NextState master reason_code 0
Feb 16 14:38:50 new state = master
Feb 16 14:38:56 failed to send RE info/keepalive: errno=65, total=20 in the last 20 sec
Feb 16 14:39:11 failed to receive keepalives from other RE for the last 20 sec
Feb 16 14:39:17 failed to send RE info/keepalive: errno=65, total=20 in the last 20 sec
Feb 16 14:39:32 failed to receive keepalives from other RE for the last 40 sec
Cause:

These messages are harmless, because they indicate that the Master Routing Engine is trying to connect to a backup Routing Engine. In SRX, there is no backup Routing Engine in the same chassis (if there is one, its purpose is to have dual control links, but not to back up primary RE). Instead, SRX relies on the primary/secondary RG0 concept for RE redundancy.


Solution:

The messages are harmless and can be ignored on SRX platform.

Related Links

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