Integration of OpenNMS with Junos Space Network Management Platform
Starting in Junos Space Network Management Platform Release 24.1R1, OpenNMS is not bundled with Junos Space Network Management Platform. You must install OpenNMS on a separate system.
After you integrate Junos Space Network Management Platform with OpenNMS:
-
When you add or delete any device from Junos Space Network Management Platform, the device list gets updated to the OpenNMS database.
-
You can set SNMP v3 OpenNMS IP trap target on devices managed by Space Network Management Platform.
-
The Junos Space Network Management Platform connection to the OpenNMS enables manual synchronization to avoid any discrepancy between Junos Space Network Management Platform and OpenNMS.
-
Integration of OpenNMS with Junos Space Network Management Platform is validated with OpenNMS Horizon (Version: 32.0.6).
You must install, configure and procure the OpenNMS license from the OpenNMS Portal as it is not bundled with the Junos Space Network Management Platform.
For details related to installation and configuration of OpenNMS, see Installation and Configuration of OpenNMS.
To ensure proper integration of OpenNMS with Junos Space Network Management Platform, perform the following procedure on the OpenNMS setup:
To generate the SSL certificate in OpenNMS, see Securing Jetty With HTTPS. This is a sample command to generate the SSL certificate
keytool -alias opennms-jetty -genkeypair -keyalg RSA -keysize 2048 -validity 731 -keystore /opt/opennms/etc/opennms.keystoreNote:To identify the OpenNMS hostname and to get the correct CN entry, run the following sample command (with IP address of the VM where OpenNMS is installed):
nslookup 10.204.250.150 Server: 66.129.233.81 Address: 66.129.233.81#53 Non-authoritative answer: 150.250.204.10.in-addr.arpa name = your-hostname-example.net. Authoritative answers can be found from:
CN :- OpenNMS HostName (Mandatory) Example :- What is your first and last name? (CN Entry) [Unknown]: your-hostname-example.net Is CN=your-hostname-example.net, OU=juniper, O=BND, L=kol, ST=wb, C=IN correct? [no]: yes
It is mandatory to provide OpenNMS hostname as the CN entry.
The OpenNMS host for VM must allow the Junos Space Network Management Platform host IPs to access ports 8980, 8443, and 162 to enable communication between the OpenNMS and Junos Space Network Management Platform.
The following is a sample command to open the ports:
systemctl restart firewalld firewall-cmd --permanent --add-port=8980/tcp firewall-cmd --permanent --add-port=8443/tcp firewall-cmd --zone=public --add-port=162/udp --permanent systemctl reload firewalld
To make changes in the trapd-configuration.xml file, use port 162 for snmpv3 traps and add an entry for snmpv3 trap. For more details, see Managing SNMPv3 Trap Configuration. The following is a sample output:
<trapd-configuration xmlns="http://xmlns.opennms.org/xsd/config/trapd" snmp-trap-address="*" snmp-trap-port="162" new-suspect-on-trap="false" include-raw-message="false" threads="0" queue-size="10000" batch-size="1000" batch-interval="500"> <snmpv3-user security-name="junos_space" security-level="3" auth-passphrase="jnpr123!" auth-protocol="SHA" privacy-passphrase="jnpr123!" privacy-protocol="AES"/> </trapd-configuration>
Starting in Junos Space Network Management Platform Release 24.1R1, Junos Space
Network Management Platform is set to Disable network monitoring for all
devices by default. You must enable Network Monitoring from the
Application Settings or run sh
/var/www/cgi-bin/network_monitoring_status.sh enable command on the
JBoss VIP node.
Log in to the CLI of the Junos Space node on which the VIP or the eth0:0 interface is configured.
The Junos Space Settings Menu is displayed.
Enter 7 at the Junos Space Network Management Platform settings menu prompt to run shell commands.
The following is a sample output:
admin@10.206.41.183's password: Last login: Mon Aug 17 06:17:58 2015 from 10.206.41.42 Welcome to the Junos Space network settings utility. Initializing, please wait Junos Space Settings Menu 1> Change Password 2> Change Network Settings 3> Change Time Options 4> Retrieve Logs 5> Security 6> Expand VM Drive Size 7> (Debug) run shell A> Apply changes Q> Quit R> Redraw Menu Choice [1-7,AQR]: 7
You are prompted to enter the administrator password.
Enter the administrator password.
Integrate OpenNMS server through Junos Space Network Management Platform by running
sh /var/www/cgi-bin/OpenNMS_Setup.shcommand on the JBoss VIP node.The following is a sample output on a cluster environment:
Do you want to start the services automatically after finished applying the Changes for OpenNMS Connection?(y/n):y This is Cluster env, Do all nodes have same password for admin user?(y/n):y This is Cluster env, please enter password for admin user: start to configure OpenNMS in current server
Provide the host and credential details for OpenNMS as per your setup.
Note:The OpenNMS host NameServer returns the information in the nslookup command output.
The DNS of OpenNMS must be same as the CN entry in point 1.
The following is a sample output:
Enter IP of OpenNMS host [Mandatory]: 10.204.250.150 Enter DNS of OpenNMS [Mandatory] : your-hostname-example.net Enter IP of OpenNMS host NameServer [Mandatory]: 66.129.233.81 Enter Port for HTTPS access [8443]: 8443 Enter User name of the OpenNMS admin user [admin]: admin
To enable throttling of sync to OpenNMS:
Note:When throttling is enabled, sync between the Junos Space Network Management Platform and the OpenNMS happens every hour.
It is recommended to have throttling enabled, but it is mandatory when Junos Space Network Management Platform manages more than 1000 devices.
The following is a sample output:
Do you want to enable throttling of sync to OpenNMS (Recommended for very high device count) ? (y/n):y Configuring and checking connectivity to OpenNMS.Please wait.... Credentials are valid.
If you select Y for JBoss restart, services stops and restarts on all the nodes.
After completion, you can log in to the Junos Space Network Management Platform GUI and use Network Monitoring.
Junos Space Network Management Platform provides an option to redirect to OpenNMS application on the Network Monitoring window.
If you select N, you must manually restart JBoss on all the nodes before using Network Monitoring.
Since, OpenNMS is decoupled from Junos Space Network Management Platform, if you want to monitor the Junos Space node(s) through OpenNMS, you must add the node(s) manually. For details, see Monitoring Nodes in the Fabric.
Update the OpenNMS password
Incase the OpenNMS password is modified, run sh
/var/www/cgi-bin/ChangeOpenNMSpassword.sh command on the JBoss VIP node
to update the OpenNMS password .
The following is a sample output:
**WARNING! Upon Completion of OpenNMS Pasword Change, JBoss Services will restart automatically on all the nodes. Do you want to continue?(y/n):y This is Cluster env, Do all nodes have same password for admin user?(y/n):y This is Cluster env, please enter password for admin user: start to configure OpenNMS in current server Enter OpenNMS New admin user password : Credentials are valid. Password Changed Successfully and Server restarting automatically!