Note: This is expected behaviour of Network monitoring/OpenNms module to monitor the different services status for managed devices.

This article provides a work-around for correcting the error condition.

Traffic can be seen on different services ports from the Junos Space application. Traffic can be monitored through tcpdump utility by running below command. 

Example: fro MS-RDP port. 

[root@space-005056a9ffe6 ~]# tcpdump -nn -vv -i any port 3389 

13:28:11.215987 IP x.x.x.x.44661 > x.x.x.x.3389: Flags [S], seq 3743099396, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0

13:28:11.249853 IP x.x.x.x.41060 > x.x.x.x.3389: Flags [S], seq 2835671149, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0

The Following procedure will help you to disable the service detector/monitor from OpenNMS. 

Step 1: Disable the opennms from UI.

Administration --> Application --> Network management platform Manage Services --> Stop Service

Step 2: To take a backup of the files 

[root@space-005056a9ffe6 ~]# cd /opt/opennms/etc/  
[root@space-005056a9ffe6 etc]# cp /opt/opennms/etc/foreign-sources/space.xml /opt/opennms/etc/foreign-sources/space.xml.org
[root@space-005056a9ffe6 etc]# cp /opt/opennms/etc/poller-configuration.xml /opt/opennms/etc/poller-configuration.xml.org
[root@space-005056a9ffe6 etc]# cp /opt/opennms/etc/capsd-configuration.xml /opt/opennms/etc/capsd-configuration.xml.org

Please note: capsd-configuration.xml file will be present only on 20.3R1 and below release. poller-configuration.xml will be present on 21.1R1 and later JunosSpace release. So we need to make the changes as per current JunosSpace release. 
 

Step 3: Verify the permission and ownership of each file before editing 

[root@space-005056a9ffe6 etc]# ll -rth /opt/opennms/etc/poller-configuration.xml
-rw-r----- 1 opennms opennms 20K Dec 16 2022 /opt/opennms/etc/poller-configuration.xml

[root@space-005056a9ffe6 etc]# ll -rth /opt/opennms/etc/foreign-sources/space.xml
-rw-rw-r-- 1 opennms opennms 5.0K Jan 30 05:52 /opt/opennms/etc/foreign-sources/space.xml

[root@space-005056a9ffe6 etc]# ll -rth /opt/opennms/etc/capsd-configuration.xml
-rw-rw-r-- 1 opennms opennms 5.0K Jan 30 05:52 /opt/opennms/etc/capsd-configuration.xml

Example for MS-RDP service.

Step 4: Comment the MS-RDP in two files as below or you can remove the line if you don't wanted to monitor the service

a) # vi /opt/opennms/etc/foreign-sources/space.xml
<!-- <detector name="MS-RDP" class="org.opennms.netmgt.provision.detector.simple.TcpDetector"> --> 

b) # vi /opt/opennms/etc/poller-configuration.xml
Status is on set it off or remove the line
<service name="MS-RDP" interval="300000" user-defined="false" status="off">

<!-- monitor service="MS-RDP" class-name="org.opennms.netmgt.poller.monitors.TcpMonitor"/>-->

  or below lines can be removed.

<service name="MS-RDP" interval="300000" user-defined="false" status="on">
<monitor service="MS-RDP" class-name="org.opennms.netmgt.poller.monitors.TcpMonitor"/>

c) /opt/opennms/etc/capsd-configuration.xml
<!-- <protocol-plugin protocol="MS-RDP" class name="org.opennms.netmgt.capsd.plugins.DnsPlugin" scan="off">
        <property key="port" value="3389" />
        <property key="timeout" value="5000" />
        <property key="retry" value="1" />
        <property key="lookup" value="localhost" />
     </protocol-plugin> --> 

d) Save all the files correctly and make sure permissions/ownership are correct. You can verify the same file with below command 

[root@space-005056a9ffe6 etc]# ll -rth /opt/opennms/etc/poller-configuration.xml
-rw-r----- 1 opennms opennms 20K Dec 16 2022 /opt/opennms/etc/poller-configuration.xml

[root@space-005056a9ffe6 etc]# ll -rth /opt/opennms/etc/foreign-sources/space.xml
-rw-rw-r-- 1 opennms opennms 5.0K Jan 30 05:52 /opt/opennms/etc/foreign-sources/space.xml

[root@space-005056a9ffe6 etc]# ll -rth /opt/opennms/etc/capsd-configuration.xml
-rw-rw-r-- 1 opennms opennms 5.0K Jan 30 05:52 /opt/opennms/etc/capsd-configuration.xml

Step 5: Enable the opennms from UI.

 Administration --> Application --> Manage Services --> Start Service 

Step 6: Take the tcpdump for 1 day to verify the any specific service query to managed devices.

# cd /home/admin
# tcpdump -nn -vv -i any port 3389 >> jtac.txt

Note : If you face any issues, please contact JUNIPER JTAC Support for assistance.