Description

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

Symptoms

Space nodes are not synchronized correctly under OpenNMS node list when DR is enabled

A) Under Network Monitoring/OpenNMS node list, JunosSpace nodes will show from the Standby DR hosts entries.

B) Fabric.xml and hosts file will show mismatch entries.

[root@space-005056a9e845 ~]# cd /opt/opennms/etc/imports/
[root@space-005056a9e845 imports]# ll -rth fabric.xml 
-rw-rw-r-- 1 opennms opennms 1.1K Mar 20 02:23 fabric.xml

# ll -rth /etc/hosts

Solution

Note: Only current active DR site JunosSpace nodes will be visible under Network monitoring/ Opennms node list when DR is enabled.
 

If /opt/opennms/etc/imports/fabric.xml file is showing wrong entries or standby DR host entries on the the current Primary DR site while comparing /etc/hosts file then below workaround needs to be followed.

 

Step 1: Manually move fabric.xml file to different folder (/tmp) and restart jboss service on HA nodes. System will automatically regenerate this file again. To restart Jboss service on Multi-node setup follow [Junos Space] How to restart JBOSS

[root@space-005056a9e845 ~]# cd /opt/opennms/etc/imports/ 
[root@space-005056a9e845 imports]# ll -rth fabric.xml 
-rw-rw-r-- 1 opennms opennms 1.1K Mar 20 02:23 fabric.xml

Step 2: Verify the hosts entries are matching with current site under fabric.xml by comparing from /etc/hosts file.


Step 3: Now nodes list should get synchronized correctly


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

Modification History

2024-03-23 : Article Created