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.

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

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.

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".

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.

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.

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.

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.

Then modify your notificationCommands.

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.

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.

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)

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.

Knoppix 5 supports write access for NTFS partitions using libntfs and fuse. While preliminary results show generally good stability and a low likelihood of data corruption on the NTFS partition, these libraries are still beta and there is risk of data loss and disk corruption (back up your data first). Knoppix (and the Linux kernel) can read NTFS partitions just fine, the danger is only present when attempting to write to it.

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.

edit] Q: "Can you please add a password feature?" A: The core developers ? which includes those with long-term experience with well-known names/brands in computer security ? believe that each app should do one thing well, and leave other concerns to other apps. Especially "tricky", critical concerns like data security. In this case, GnuCash would do a poor job of being a good security application.

Yes. A client can use as many different services as it needs. To code such a client, simply include the header files for all the RPC interfaces used, and code each call the same way you would if using that interface in isolation.

Yes. A server can provide service on multiple interfaces simultaneously. A common example is a server that exports an application interface and a management interface. To code such an application, repeat the calls to rpc_server_register_if(), rpc_ep_register(), (and rpc_ns_binding_export() if you do that sort of thing in your server) for each interface, before calling rpc_server_listen().

Yes, Klir protects customer data through a combination of secure communications, authentication, and data center security solutions. Klir Analytics is secured with a combination of internal policies and network security measures. Internal policies that safeguard the hosted application include the following: strict rights management, limited physical access, high availability, database backups and archives.

The Patient Management ToolTM* (PMT) is an online, interactive assessment and reporting system that helps implement GWTG. It provides patient-specific guideline information and enables each institution to track its adherence to the guidelines individually as well as against national benchmarks over time. The PMT enables the clinician to collect and collate relevant information to make better guideline-based decisions.