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

[Junos Space] Space did not receive a JMB/syslog sent by a device



Article ID: KB30682 KB Last Updated: 07 Jan 2016Version: 1.0

Junos Space did not receive something (JMB/syslog) that a device was supposed to have sent.


In many scenarios, managed devices notify Junos Space of something (that a JMB is generated, asking Junos Space to collect or notify that a commit happened, asking Junos Space to auto-resync NSOR, and so on). This article describes an important daemon on the device that makes the transfer possible. It also describes how Junos Space spawns the daemon on the device.


Whenever a device is discovered in Junos Space, it adds the following config stanza on to the device.

set system syslog file messages any notice
set system syslog file messages authorization info
set system syslog file interactive-commands interactive-commands any
set system syslog file default-log-messages any info
set system syslog file default-log-messages match "(requested 'commit' operation)|(copying configuration to|(commit complete)|ifAdminStatus|(FRU power)|(FRU removal)|(FRU insertion)|(link UP)|transitioned|Transferred|transfer-file|(license add)|(license delete)|(package -X update)|(package -X delete)|(FRU Online)|(FRU Offline)|(plugged in)|(unplugged)|CFMD_CCM_DEFECT| LFMD_3AH | RPD_MPLS_PATH_BFD|(Master Unchanged, Members Changed)|(Master Changed, Members Changed)|(Master Detected, Members Changed)|(vc add)|(vc delete)|(Master detected)|(Master changed)|(Backup detected)|(Backup changed)|(interface vcp-)|(AIS_DATA_AVAILABLE)"
set system syslog file default-log-messages structured-data

In addition to this, there is another important daemon that runs on managed Junos OS devices that actually makes the transfer possible. This daemon consistently monitors default-log-messages and sends syslog notifications to Junos Space if a certain condition (that is committed during discovery) is met. This binary on Junos OS is called syslog-filter and it runs on the managed device until the time Junos Space manages it. If you are troubleshooting certain issues on why Junos Space did not receive something that a device was supposed to send, use the following command to check whether this daemon is running on the device in the first place:

root@custmx% ps auxw | grep filter
root 81693 0.0 0.1 6036 2660 ?? S 7:36AM 0:00.03 /usr/sbin/syslog-filter -X -f default-log-messages

How does Junos Space spawn this daemon? As part of device discovery, Junos Space calls the <get-syslog-events> RPC. This RPC is an asynchronous call that spawns the syslog-filter daemon on the device:

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="">
<!-- hum -->
<!-- hum -->
<!-- hum -->
<!-- hum -->
<!-- hum -->
<!-- hum -->
<!-- hum -->
<!-- hum -->
<!-- hum —>

As you can see, <!—hum—> is like a keepalive message, and it should keep repeating until the device is managed in Junos Space. Though it is hidden and mostly unnoticed, it plays an important role in NSOR, JMB transfer, and so on in Junos Space. The <!--hum--> messages can be seen in the /var/log/jboss/servers/server1/server.log of the Junos Space server. 

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