Skip to main content

Installing OpneNMS on CentOS - using RPM.


As from my previous post. This again is for the IT Team. Was helping them setup and network Monitoring tool.

Here are the step to follow to install OpenNMS.

Step 1: configure the OpenNMS Repository RPM
]# yum install yum-fastestmirror

Step 2: Install the Prerequisite Package: Java
To install java you would download “jdk-7u3-linux-x64.rpm “from http://www.oracle.com/technetwork/java/javase/downloads/jdk-7u3-download-1501626.html  and place it in your current working directory then run bellow command
]$ sudo rpm -ivh jdk-7u3-linux-x64.rpm
Step 2: Install the Prerequisite Package: PostgreSQL
To install PostgreSQL follow bellow commands
]$ sudo yum -y install postgresql-server
]# /etc/init.d/postgresql start
]# /sbin/chkconfig postgresql on
Configure PostgreSQL
Locate the Postgres "data" directory. Often this is /var/lib/pgsql/data and Open /var/lib/pgsql/data/ postgresql.conf in text editor.
]$ vi /var/lib/pgsql/data/postgresql.conf
 Now uncomment/edit bellow lines as shown         
          listen_addresses = 'localhost'
      max_connections = 256
      shared_buffers = 1024
Similarly edit pg_hba.conf file .In the bottom of the file, replace “ident” with “trust” for all.
]# vi /var/lib/pgsql/data/ pg_hba.conf
]# /etc/init.d/postgresql restart
Step 3: Install the Prerequisite Package: jicmp
]# yum install jicmp

Step 4: Install the OpenNMS Repository RPM

To install the latest stable release (opennms-repo-stable-rhel6.noarch) on CentOS , you would run bellow commands
]# yum install opennms
Configure java for OpenNMS (note: after –s give the path where java installed).
]# /opt/opennms/bin/runjava –s /usr/bin/java
]# /opt/opennms/bin/install -dis
Add automatic startup of opennms in your current runlevel
]# /sbin/chkconfig  opennms on
]# /sbin/service opennms start
 To Add a Firewall Exception for OpenNMS
]# vi /etc/sysconfig/iptables
Now add the bellow line for giving exception for port 8980
-A INPUT -m state --state NEW -m tcp -p tcp --dport 8980 -j ACCEPT
]# /sbin/service iptables restart
Now we can connect to the Web UI of opennms with bellow link

And log in as
User: admin
Password: admin

Comments

Popular posts from this blog

Cloudera Manager - Duplicate entry 'zookeeper' for key 'NAME'.

We had recently built a cluster using cloudera API’s and had all the services running on it with Kerberos enabled. Next we had a requirement to add another kafka cluster to our already exsisting cluster in cloudera manager. Since it is a quick task to get the zookeeper and kafka up and running. We decided to get this done using the cloudera manager instead of the API’s. But we faced the Duplicate entry 'zookeeper' for key 'NAME' issue as described in the bug below. https://issues.cloudera.org/browse/DISTRO-790 I have set up two clusters that share a Cloudera Manger. The first I set up with the API and created the services with capital letter names, e.g., ZOOKEEPER, HDFS, HIVE. Now, I add the second cluster using the Wizard. Add Cluster->Select Hosts->Distribute Parcels->Select base HDFS Cluster install On the next page i get SQL errros telling that the services i want to add already exist. I suspect that the check for existing service names does n

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server &quo

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa