By default, net-snmp is configured only to allow a really small amount of information to be accessed by the default community name of "public". The easiest way to change this is to find a line like: view systemview included .1.3.6.1.2.1.1

Let's assume that we want to send an alert when hrSystemProcesses exceeds 250. The numeric OID is .1.3.6.1.2.1.25.1.6 . In this case, said collection definition is listed in my "/opt/OpenNMS/etc/ datacollection-config.xml" file. So what we need to do firstly is edit: "/opt/OpenNMS/etc/thresholds.xml". See similar questions...

With OpenNMS 0.9, the concept of a "primary" SNMP interface was added to the database. By default the interface with the lowest IP address is designated as the primary interface for SNMP queries. Also by default, performance data is only collected for that interface. If you would like to collect data on all of the interfaces on the node, you need to make a change to the /opt/OpenNMS/etc/datacollection-config. See similar questions...

First create a certificate keystore for tomcat by executing $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA Restart httpd, tomcat and opennms just to be sure and after what seemed too long, I was prompted for user name and password. It seems only the first time connecting is real slow, subsequent logins are quite speedy. I wanted to add a few comments to this. First, if you want to use a password other than "changeit", add the keystorePass attribute: <Connector className="org.apache. See similar questions...

You must setup the group and create the users. Also make sure that the pg_hba.conf file has the correct security permissions. And then just run psql interactively with these GRANTS for the group access. See similar questions...

OpenNMS, the application, is the first enterprise-grade network management platform to be developed under the open-source model. The goal is for OpenNMS to be a truly distributed, scalable platform for all aspects of the FCAPS network management model, and to make this platform available to both open source and commercial applications. Data Collection - collecting, storing and reporting on network information as well as generating thresholds. See similar questions...

The purpose of this note is to explain in detail how OpenNMS performs SNMP data collection. Knowing how this works is key to troubleshooting SNMP data collection problems. The discovery process in OpenNMS is really simple. We send out a "ping" in order to see if an IP address exists and is responsive (and which IP addresses we try are set in the discovery-configuration.xml file). When that happens, a NewSuspect event is generated. It is also possible to use the send-event. See similar questions...

Please note that we now keep up-to-date release notes on the web site and in the latest RPM packages, they may have information about installation on your particular distribution, or other last-minute things that went into the release. Before asking questions on the list, PLEASE check the release notes and this FAQ thoroughly for information pertaining to your issue. See similar questions...

We use SourceForge mailing lists. You can find links to subscribe as well as view archives on the web at our mailing lists page. Please note: when subscribing, remember the address you used, as you will need to send from that address or your post will be rejected. To unsubscribe, please do not send a message to the list or to the list administrator. Go to the list information page for the list you wish to leave, and enter in your e-mail address at the bottom and edit your options. See similar questions...

OpenNMS is mainly written in Java. The goal for OpenNMS 2.0 is to have a product that will install as a collection of .jar files. icmpd - The 1.4 Java API does not understand ICMP. Since ICMP echo requests ("pings") are the simplest way to test the responsiveness of an IP-based network device, no network management application will be complete without it. The goal is to separate the ICMP functions into their own daemon that OpenNMS will use if present and ignore if not. See similar questions...

Then modify your notificationCommands. See similar questions...

OpenNMS already has configurations to use qpage (http://www.qpage.org). You can see them in $OPENNMS_HOME/etc/notificationCommands.xml. I set up users on onms, then setup the users (with the same name) in /etc/qpage.cf. That's pretty much all I had to do in onms. On the qpage side, you need to configure the pager-ids and the service. The key here is that the number used to send alpha pages is not the pager number but a different number talking something called TAP. See similar questions...

The difficulty with the core of OpenNMS is that these components need to run as root to be able to bind to low-numbered ports or generate network traffic that requires root: Here is an example of the error you will get if you try to startup OpenNMS as a non-root user: 2004-08-28 09:47:14,405 ERROR [main] Discovery: Failed to create ping manager: \ java.net.SocketException: System error creating ICMP socket (1, Operation not permitted) See similar questions...

A Detailed instructions are available in Section 6 of Internet Texoma's How To directory on this site. See similar questions...

Simple Network Management Protocol (SNMP) is a family of protocols that provide a means for monitoring and controlling networked devices. Computer vendors have built into some network devices, including some UPS models, network management capabilities so that you can query their status remotely, as devices are usually referred to as "smart" devices. See similar questions...

If you have no plans on using the Net-SNMP Perl module (see the next question), then any recent version of Net-SNMP or UCD-SNMP should be sufficient with the exception of Net-SNMP 5.1. Net-SNMP 5.1.1 and higher can be used. If you plan on using UCD-SNMP 4.2.3 (provided by Compaq for RedHat 7.2), then you must at least use a newer version of snmptrapd. If you plan on enabling the Net-SNMP Perl module, Net-SNMP v5.1.1 or higher is recommended. This will allow you to use all the features of snmptt. See similar questions...

SNMPTT does not REQUIRE the Perl module, but it is recommended. By enabling the Perl module, you will get the following benefits: Conversion of INTEGER values to enumeration tags (for example: Status is now OK instead of Status is now 1) Ability for traps passed from snmptrapdor loaded from the snmptt.conf files to contain symbolic OIDs such as linkDown and IF-MIB::linkUp Variable syntax, description and enums when converting a MIB file using snmpttconvertmib Unless Net-SNMP 5.1.1 or 5.0.8 / 5. See similar questions...

Install ActiveState ActivePerl and then the ActivePerl .ppm module included in the Net-SNMP binary available from the Net-SNMP web site. If you compiled your own version of Net-SNMP, see the perl/README document for instructions on compiling the Perl modules. Download the Net-SNMP 5.1.2+ source and compile using Cygwin as described in the Net-SNMP README.WIN32 file. See similar questions...

Download the Net-SNMP 5.1.2+ source and compile using MSVC++, MinGW or Cygwin as described in the Net-SNMP README.WIN32 file. This should create a working snmptrapd. See the question: How to I enable the Perl support for UCD-SNMP / Net-SNMP under Windows? Note: Net-SNMP 5.1.2 or higher is recommended if compiling under Windows as it contains the latest Windows specific compiling improvements. See similar questions...

Yes. Solar electricity systems that are tied into public utility systems sell power back to the utility grid in the summer, while still producing smaller amounts of power on cloudy days. In the summer, when electricity use is highest, solar systems generate the most power, thereby offsetting some of the increased demand. The result is less dependence on non-renewable energy and more clean power from the sun. See similar questions...