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.

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

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

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.

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.

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.

Then modify your notificationCommands.

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.

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.

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.

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)

Author: Will Stranathan (http://www.jguru.com/guru/viewbio.jsp?EID=98224) Question originally posed by Kevin Kovach (http://www.jguru.com/guru/viewbio.jsp?EID=35628 http://java.apache.org/jservssi/ - the JServ JSSI servlet should do the trick. Comments and alternative answers From the tomcat-user mailing list: From: "Craig R. McClanahan" <Craig.McClanahan@eng.sun.com> To: tomcat-user@jakarta.apache.

There are 2 strengths in SSL - 40-bit and 128-bit. These refer to the length of the secret key used for encrypting the session. This key is generated for every SSL session and is used to encrypt the rest of the session. The longer the key the more difficult it is to break the encrypted data. So, 128-bit encryption is much more secure than 40-bit. Most browsers today support 128-bit encryption. There are a few countries which have browsers with only 40-bit support.

SSL supports a number of cryptographic algorithms. During the initial "handshaking" phase, it uses the RSA public key algorithm. For encrypting the data with the session key the following algorithms are used - RC2, RC4, IDEA, DES, triple-DES and MD5 message digest algorithm.

There are several Certificate Authorities that you can buy a SSL certificate from. Whichever CA you choose, the basic procedure will be as follows - Create the Certificate Signing Request. This will require you to provide certain details like location and fully qualified domain name of the server. The first two steps are done from the web server. All servers have these features. While installing the certificate issued by the CA, you will have to specify which web pages are to be on SSL.

How do I configure TLS and the STARTTLS facility? imap-2006 supports SSL and TLS client functionality on UNIX and 32-bit Windows for IMAP, POP3, SMTP, and NNTP; and SSL and TLS server functionality on UNIX for IMAP and POP3. UNIX SSL build requires that a third-party software package, OpenSSL, be installed on the system first. Read imap-2006/docs/SSLBUILD for more information.

First boot KNOPPIX with the memory stick inserted. Got to the KNOPPIX menu, Configuration, Save Configuration. When asked, choose /dev/sda1. When booting type knoppix myconf=scan home=scan at the boot prompt. This is an issue with the Dell BIOS. Simply pull out the power cord from your computer for a few seconds, and your computer should start again. You can also try passing "apm=off" or "apm=real-mode-poweroff" to the kernel during startup.

Yes. However, you will need to configure the JVM to do this. By default, the JVM that JBlitz runs in does not 'trust' private / self generated / test certificates. This is a normal safeguard against accepting content from un-trusted websites etc. Configuring your client VM to accept the returned certificate is outlined in more detail below under the known bugs section.