Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Debugging Tips

    You must enable the extension-service traceoptions on the Junos OS device before writing the sample applications.

    In case your application is not able to connect to the Junos service process (jsd):

    1. Check whether jsd is up and running on the Junos OS device using the following command:
      ps aux | grep jsd

      If not, then restart jsd.

    2. If jsd is up, verify the configuration is present on the device using the following CLI command in configuration mode:
      user@device# show system services extension-service
    3. If the configuration is present, verify if jsd is listening on configured port 32767:
      nestat -a | grep 32767

      You should see a matching entry. If you do not, then restart jsd.

    To eliminate any firewall issues, use an on-device application to test.

    In case of notification applications, verify that your client IP source address (the address from which the connect is happening) is added to the list of allowed clients in the jsd notification configuration.

    Ensure that dual Routing Engines on devices running Junos OS have master mode running. We do not support jsd on backup Routing Engines.

    Ensure that the maximum number of notification connections as configured on the device are not exceeded. Use the following command to see the clients:

    netstat -a | grep 1883

    Modified: 2018-02-22