Support Support Downloads Knowledge Base Juniper Support Portal 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

What does "Did not receive identification string x.x.x.x" mean?



Article ID: KB17217 KB Last Updated: 05 Mar 2017Version: 5.0

When using a Junos Space appliance to connect to Junos device, configuration information could be left on the device even though the device is deleted from the Junos Space appliance.  This article describes the error message and the resolution to it.


Even though the host is not configured in Service Now or Network Application Platform, these messages are being logged on the Junos devices every 15 seconds.

Apr 10 04:32:06  router1-RE0 sshd[65423]: Did not receive identification string from
Apr 10 04:32:21  router1-RE0 sshd[65425]: Did not receive identification string from
Apr 10 04:32:36  router1-RE0 sshd[65427]: Did not receive identification string from
Apr 10 04:32:51  router1-RE0 sshd[65429]: Did not receive identification string from
Apr 10 04:33:06  router1-RE0 sshd[65431]: Did not receive identification string from

(note that is the Junos Space IP address)


The message indicates that the device is configured for outbound-ssh towards the Junos Space appliance, and yet the Junos Space appliance does not know about the device itself.

The following sample configuration would be seen in the device :

lab@router1> show configuration system services   
outbound-ssh {
    client 00089BBC96BF {
        device-id 3928B3;
        secret "xxxxxxxxxxxxxxxxxxxxxxxxxxxx"; ## SECRET-DATA
        services netconf; port 7804;

(note that is the Junos Space IP address)

It is safe to remove this configuration from the Junos device if there is no longer a connection required to Junos Space.

If the message continues to appear when configured (and in-sync) on Junos Space AND the device has the correct corresponding configuration (similar to the example above), then delete the device within Junos Space and re-add it.  This should remove the error message and clear the state.

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