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/J-series] Syslog messages are generated on the screen when the failover of the '0' redundancy-group in the chassis cluster is initiated

0

0

Article ID: KB25710 KB Last Updated: 04 Sep 2012Version: 1.0
Summary:
This article describes the issue of syslog messages being generated on the console screen, when the failover of the 0 redundancy-group in the chassis cluster is initiated.
Symptoms:
After the failover of the 0 redundancy-group is performed, the following syslog messages are generated on the console screen:
Message from syslogd@juniper at Feb 15 22:31:04 ...
juniper node0.fpc5 RDP: Remote side closed connection: rdp.(fpc5:1098).(serverRouter:chassis)

Message from syslogd@juniper at Feb 15 22:31:04 ...
juniper node0.fpc4 RDP: Remote side closed connection: rdp.(fpc4:61514).(serverRouter:chassis)

Message from syslogd@juniper at Feb 15 22:31:04 ...
juniper node0.fpc0 RDP: Remote side closed connection: rdp.(fpc0:17480).(serverRouter:chassis)

Message from syslogd@juniper at Feb 15 22:31:05 ...
juniper node0.fpc4 RDP: Remote side reset connection: rdp.(fpc4:61515).(252706817:pfe)

Message from syslogd@juniper at Feb 15 22:31:06 ...
juniper node0.fpc5 RDP: Remote side reset connection: rdp.(fpc5:1099).(252706817:pfe)

Message from syslogd@juniper at Feb 15 22:31:07 ...
juniper node0.fpc0 RDP: Remote side reset connection: rdp.(fpc0:17481).(252706817:pfe)
The following image illustrates the syslog messages:


Cause:
The routing protocol process (RPD) controls the routing protocols that run on the router/firewall. This process starts all the configured routing protocols and handles all the routing messages. It maintains one or more routing tables, which consolidate the routing information that is learned from all routing protocols. The above mentioned messages, which are generated on the console session, states that the routing-engine [control plane(RG0)] has become active on the other node.

RG0 is the control plane, to which you are connected; so failing this over to the other node will disconnect the session, if you are logged in via SSH or telnet through a revenue port; but after a couple of seconds, you should be able to re-connect to the other node. If you are connected via the serial console or the fxp0 interface, then your session should not disconnect; but you will then be managing the passive node.

These messages are due to the following syslog user configuration:

Solution:
You can de-activate the syslog user configuration to prevent these messages from being generated:
# deactivate system syslog user *
# commit
Note: It is recommended to retain the 'syslog user (any emergency) configuration and ignore these informational messages, as they might show certain useful information to the user.

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