Manage devices (EX, MX, SRX, QFX) are not properly displaying all interfaces and routing instances under Network Management Platform>Network Monitoring>Node list>Device>Resource Graph.
This behavior occurs because we are monitoring too many interfaces for too many devices based on your Junos Space resources
When the problem is reflected output will be reflected as below:
This should be the expected behavior:
Reduce the amount of data being collected from network monitoring.
1- Go to WebUI->Network management platform->Network monitoring->Node list->Click any Node -> Edit in requisition -> “ Return “ ( Right top corner) -> “Edit Definition”
1.1- Delete all the Unnecessary detectors except ICMP, SNMP, SSH
1.3- Forcefully resync in the Junos Space node using the node ID listed under WebUI->Network management platform->Network monitoring->Node list->Click on any affected node->At the top left corner you'll see a number:
/opt/opennms/bin/send-event.pl uei.opennms.org/internal/capsd/forceRescan -n node-id
Example:
/opt/opennms/bin/send-event.pl uei.opennms.org/internal/capsd/forceRescan -n 2
2- [Only if the problem is persistent] Tune the SNMP config by removing extra data collections that may or may not be needed.
Note: Not all of the files in the data collection file are being used for a single device because we have SYSOID masks defined. That should stop the devices from being asked for unnecessary metrics.
2.2- Go to the Junos Space CLI and use vi /opt/opennms/etc/datacollection-config.xml to edit the file, comment on the lines that say <include-collection dataCollectionGroup=""/> using the comment out syntax <!-- and -->
For example:
<!--include-collection dataCollectionGroup="Acme Packet"/-->
2.3- Restart the Network monitoring from the Network management platform>Administration> Applications>Right click Network management platform>Manage services>Restart network monitoring
2.4- Forcefully resync in the Junos Space node using the node ID listed under WebUI->Network management platform->Network monitoring->Node list->Click on any affected node->At the top left corner you'll see a number:
If the problem is persistent at this point, there could be intermittent communication issues or more resources required such as a Junos Space FMPM node or increasing the available resources of the FMPM node in either case the recommendation is to involve the JTAC team for assistance Click here if any assistance is required.
2024-03-09 : Article Created
2024-12-21: JTAC found a better procedure as a workaround.