Product SiteDocumentation Site

OpenNMS 1.8.2

Release Notes

Release Notes for OpenNMS Version 1.8.2

Edition 1

Tarus Balog

OpenNMS Community Documentation Team

Matt Brozowski

OpenNMS Community Documentation Team

David Hustace

OpenNMS Community Documentation Team

Benjamin Reed

OpenNMS Community Documentation Team

Mike Danko

OpenNMS Community Documentation Team

Legal Notice

Copyright © 2010 The OpenNMS Group, Inc.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts and with no Back-Cover Texts. A copy of the license is available at http://www.gnu.org/copyleft/fdl.html
OpenNMS is the creation of numerous people and organizations, operating under the umbrella of the OpenNMS project. The original code base was developed and published under the GPL by the Oculan Corporation until 2002, when the project administration was passed on to Tarus Balog.
The current corporate sponsor of OpenNMS is The OpenNMS Group, which also owns the OpenNMS Trademark.
Original Code base for OpenNMS version 1.0.0 © 1999-2001 Oculan Corporation.
Mapping Code © 2003 Networked Knowledge Systems, Inc.
ScriptD code © 2003 Tavve Software Company.
Java® and Solaris® are registered trademarks of Oracle and/or its affiliates in the United States and other countries.
Linux® is a registered trademark of Linux Torvalds in the United States and other countries.
Red Hat, Red Hat Linux, Red Hat Enterprise Linux, and Fedora are trademarks of Red Hat, Inc., registered in the United States and other countries.
Mandriva® is a registered trademark of Mandriva S.A. in the United States and other countries.
SuSE® is a registered trademark of Novell, Inc. in the United States and other countries.
Windows®, Windows Server®, Windows XP®, Windows Vista®, and Windows 2000® are registered trademarks of Microsoft Corporation in the United States and other countries.
Apple®, Tiger®, Leopard®, Snow Leopard®, and Mac OS® are registered trademarks of Apple, Inc. in the United States and other countries.
Ubuntu® is a registered trademark of Canonical Ltd.
PostgreSQL® is a registered trademark of the PostgreSQL Global Development Group.
All other trademarks are property of their respective owners.
Please send any omissions or corrections to this document to Tarus Balog
Abstract
This book details the release notes for OpenNMS version 1.8.2.

Preface
1. Document Conventions
1.1. Typographic Conventions
1.2. Pull-quote Conventions
1.3. Notes and Warnings
2. We Need Feedback!
1. Overview
1.1. Major New Features
1.2. Minor New Features
2. Requirements
2.1. Supported Platforms
2.1.1. Fully Supported Platforms
2.1.2. Unsupported Platforms
3. Bugs and Issues
3.1. Bugs Fixed in OpenNMS 1.8.2
3.2. Open Bugs and Issues
4. Changes for OpenNMS Users
4.1. Changes since 1.8.1
5. Changes for OpenNMS Administrators
5.1. Changes since 1.8.1
6. Changes for OpenNMS Developers
6.1. Changes since 1.8.1
7. Changes to OpenNMS for Specific Audiences
7.1. Changes since 1.8.1
A. Revision History
B. OpenNMS Release History
Index

Preface

1. Document Conventions

This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.

1.1. Typographic Conventions

Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
Mono-spaced Bold
Used to highlight system input, including shell commands, file names and paths. Also used to highlight keycaps and key combinations. For example:
To see the contents of the file my_next_bestselling_novel in your current working directory, enter the cat my_next_bestselling_novel command at the shell prompt and press Enter to execute the command.
The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold and all distinguishable thanks to context.
Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example:
Press Enter to execute the command.
Press Ctrl+Alt+F1 to switch to the first virtual terminal. Press Ctrl+Alt+F7 to return to your X-Windows session.
The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with each set pressed simultaneously).
If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in mono-spaced bold. For example:
File-related classes include filesystem for file systems, file for files, and dir for directories. Each class has its own associated set of permissions.
Proportional Bold
This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
Choose SystemPreferencesMouse from the main menu bar to launch Mouse Preferences. In the Buttons tab, click the Left-handed mouse check box and click Close to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
To insert a special character into a gedit file, choose ApplicationsAccessoriesCharacter Map from the main menu bar. Next, choose SearchFind… from the Character Map menu bar, type the name of the character in the Search field and click Next. The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the Copy button. Now switch back to your document and choose EditPaste from the gedit menu bar.
The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context.
Mono-spaced Bold Italic or Proportional Bold Italic
Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
To connect to a remote machine using ssh, type ssh username@domain.name at a shell prompt. If the remote machine is example.com and your username on that machine is john, type ssh john@example.com.
The mount -o remount file-system command remounts the named file system. For example, to remount the /home file system, the command is mount -o remount /home.
To see the version of a currently installed package, use the rpm -q package command. It will return a result as follows: package-version-release.
Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
Publican is a DocBook publishing system.

1.2. Pull-quote Conventions

Terminal output and source code listings are set off visually from the surrounding text.
Output sent to a terminal is set in mono-spaced roman and presented thus:
books        Desktop   documentation  drafts  mss    photos   stuff  svn
books_tests  Desktop1  downloads      images  notes  scripts  svgs
Source-code listings are also set in mono-spaced roman but add syntax highlighting as follows:
package org.jboss.book.jca.ex1;

import javax.naming.InitialContext;

public class ExClient
{
   public static void main(String args[]) 
       throws Exception
   {
      InitialContext iniCtx = new InitialContext();
      Object         ref    = iniCtx.lookup("EchoBean");
      EchoHome       home   = (EchoHome) ref;
      Echo           echo   = home.create();

      System.out.println("Created Echo");

      System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));
   }
}

1.3. Notes and Warnings

Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.

Note

Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.

Important

Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' won't cause data loss but may cause irritation and frustration.

Warning

Warnings should not be ignored. Ignoring warnings will most likely cause data loss.

2. We Need Feedback!

If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you. Please submit a report in our Bugzilla system: http://bugzilla.opennms.org.
Make sure to file against the problems in this manual against the Documentation component of the OpenNMS product, and to mention the identifier of this book: Release_Notes
If you prefer to not use Bugzilla, or have a concern which requires a different level of feedback, you can also:
  • Subscribe to one of the many OpenNMS Email Discussion Lists
  • Chat with us on IRC at irc.freenode.net in the #opennms channel.
  • Call, Write, Skype or Fax The OpenNMS Group's Commercial Support. Details for contacting The OpenNMS Group, Inc. can be found at the Contact Us Form on their website.

Chapter 1. Overview

This document outlines changes introduced with OpenNMS 1.8.2.

1.1. Major New Features

No Major new features have been added in 1.8.2.

1.2. Minor New Features

Many minor new features have been added to OpenNMS 1.8.2. All minor features additions are listed below as well as associated with their target audiences later in this manual.
  • It is now possible to schedule an outage for a node or interface directly from their respective UIs.
  • Linkd is now able to walk IpCidrRouteTable and InetCidrRouteTable as well as IpRouteTable for determining node links.
  • You can now configure the number of outages to show on the front page of the web UI.
  • A standalone tool for importing Spectrum traps is available in the opennms-tools directory of the OpenNMS source.
  • A standalone tool for parsing collection logs and providing stats on average collection time is available in the opennms-tools directory of the OpenNMS source.
  • It is now possible to pause and resume all remote pollers in the distributed poller status UI.
  • You can now populate asset data based on information retrieved from SNMP when provisioning a node.
  • New events and configurations for Junos devices were added.
  • Queued now gathers RRD queue statistics by default.

Chapter 2. Requirements

2.1. Supported Platforms

OpenNMS is written almost entirely in Java, and should be able to run on any system that supports the Sun Java Virtual Machine -- OpenNMS 1.3.x and higher requires Java 5 or higher. There are requirements for other programs such as PostgreSQL and Perl, but the JDK is the key requirement as most of the other packages can be compiled from source.

2.1.1. Fully Supported Platforms

The following systems are supported out-of-the-box with native installation packages.
RPM-Based Distributions (Using YUM)
Red Hat Enterprise Linux 3 and later
CentOS 3 and later
Fedora Core 4 and later (including 64-bit)
SuSE Linux 9 and 10 (Using the YUM repository through YAST)
Other RPM-based Distributions
Mandriva Linux 2007 and later (Using URPMI)
Debian and Ubuntu Linux
Debian Etch and later
Ubuntu 6.10 and later
Oracle Solaris
Solaris 10 SPARC
Solaris 10 x86
Apple Mac OS
Mac OS X 10.4 and later (via Fink)
Microsoft Windows Operating System
Windows Server operating system
Windows 2000 operating system and later

Non-UNIX-like Operating Systems

Note that while it is technically possible to install on FAT32, NTFS is the only officially supported filesystem for Windows installs. Additionally, while Windows is supported, OpenNMS is much more heavily tested (and easier to maintain) on UNIX, and it is recommended that unless you have a specific reason to go with Windows, that you use one of the supported UNIX-based operating systems.

2.1.2. Unsupported Platforms

OpenNMS 1.3.7 and up require Java 5 (a 1.5 JDK) and PostgreSQL 7.4 or higher. In addition, for native RRD support (as opposed to the builtin Java-based JRobin round-robin database), RRDTool 1.2 is required.
Any operating system that can support these dependencies should be able to run OpenNMS. However, since many older distributions do not support packages for these applications it will be much harder to get them installed, and so they are not officially supported.
A number of distributions that used to be supported are still able to run OpenNMS but are not officially supported.
Gentoo
Gentoo ebuilds used to be available but are no longer officially maintained, as no Gentoo packager volunteers keep them up-to-date.
Red Hat Linux
While Red hat Linux 7, 8, and 9 (and potentially even others might still work, they have long gone untested and are not recommended for production use.
SuSE Linux
Versions 8 and earlier
Oracle Solaris
Solaris 9 and earlier

Chapter 3. Bugs and Issues

As always, the OpenNMS community and development team have done their best to add new features and eliminate existing bugs. Prior to taking any action with installing or upgrading OpenNMS, check the links to the known issues listed for this release as bugs may have been reported or reopened after the distribution of the Release Notes document.

3.1. Bugs Fixed in OpenNMS 1.8.2

The current list of fixed bugs for this version can be found in the OpenNMS Bugzilla System. Bugzilla Query for FIXED status in OpenNMS 1.8.2

3.2. Open Bugs and Issues

The current list of unresolved issues for the 1.8.2 release can also be found in the OpenNMS Bugzilla System. Confirmed bugs and issues targeted for the next OpenNMS release.

Chapter 4. Changes for OpenNMS Users

OpenNMS Users are people who use the OpenNMS application on a regular basis for the purposes of maintaining a functional network. Users make use of the Web UI, and notifications, and are mostly data focused in their tasks.

4.1. Changes since 1.8.1

The following changes for OpenNMS Users have have gone into effect since OpenNMS 1.8.1
Features, Enhancements, and Bug Fixes for Users
Feature: Outage Scheduling
It is now possible to schedule an outage for a node or interface directly from their respective UI's. (Bug #1225)
Bug Fix: Notification Editing
Editing a notification's name in the GUI now works again. (Bug #3570)
Bug Fix: Custom Resource Performance Reporting
The custom resource performance report link now gives you a custom resource performance report, instead of a standard one. (Bug #3573)
Bug Fixes: Maps
Browser history buttons now work properly in maps again. (Bug #3734)
A bug where saving maps could cause duplicates to be created was fixed. (Bug #3997)
Bug Fixes: Node Labels
If you had a "." in a node label, maps would not populate their name properly. (Bug #3995)
A bug was fixed in the code for editing node labels where it would previously cause a database handle leak (and eventually, errors accessing the database) in OpenNMS. (Bug #3991)
Bug Fixes: Distributed Polling
It is now possible to pause and resume all remote pollers in the distributed poller status UI. (Bug #4026)
Clarifications have been made in the Distributed Poller status legend.. (Bug #4027)
Bug Fix: Thresholding
A resource filter with a negative look behind now renders properly in the UI. (Bug #3726)
The thresholding for low memory now takes cached memory into account on Linux. (Bug #2910)
Bug Fix: Front Page UI
A regression from 1.6 where the "nodes with outages" box on the front page would show inconsistent results was fixed. (Bug #3981)

Chapter 5. Changes for OpenNMS Administrators

OpenNMS Administrators are people who are ultimately responsible for the operation and maintenance of an OpenNMS system. OpenNMS Administrators are responsible for adding new features and higher level tasks which require admin access to the Web UI and often command line access to the OpenNMS server they administrate.

5.1. Changes since 1.8.1

The following changes for OpenNMS Administrators have have gone into effect since OpenNMS 1.8.1
Features, Enhancements, and Bug Fixes for Administrators
Feature: Improved Network Topology Discovery (linkd)
Linkd is now able to walk IpCidrRouteTable and InetCidrRouteTable as well as IpRouteTable for determining node links. (Bug #3773)
Feature: UI Options
You can now configure the number of outages to show on the front page of the web UI. (Bug #3982)
Features: New Tools
A standalone tool for importing Spectrum traps is available in the opennms-tools directory of the OpenNMS source. (Bug #4025)
A standalone tool for parsing collection logs and providing stats on average collection time is available in the opennms-tools directory of the OpenNMS source. (Bug #4033)
Feature: Asset Information
You can now populate asset data based on information retrieved from SNMP when provisioning a node. (Bug #4028)
Feature: Queued Statistic Gathering
Queued now gathers RRD queue statistics by default. (Bug #4030)
Bug Fix: Topology (Linkd)
A bug in linkd that would prevent many nodes to fail to have proper links was fixed. (Bug #3989)
Bug Fix: RANCID Provisioning
A typo in the RANCID property used in opennms.properties was fixed. Please double-check your configuration after upgrading. (Bug #4004)
Bug Fix: Node Provisioning
In some cases, code that handles new nodes could generate an inconsistent NodeGainedService event. (Bug #4022)

Chapter 6. Changes for OpenNMS Developers

OpenNMS Developers are people who use the OpenNMS application on a regular basis for the purposes of maintaining a functional network.

6.1. Changes since 1.8.1

The following changes for OpenNMS Users have have gone into effect since OpenNMS 1.8.1
No new changes for developers have been reported.

Chapter 7. Changes to OpenNMS for Specific Audiences

Some new features, enhancements, and bug fixes don't always apply to all users of an OpenNMS system, but rather are intended for specific audiences, such as users of a particular managed device type.

7.1. Changes since 1.8.1

The following specific-audience changes have have gone into effect since OpenNMS 1.8.1
Features, Enhancements, and Bug Fixes
Feature: One
New events and configurations for Junos devices were added. (Bug #4029)

Revision History

Revision History
Revision 0Thu Aug 5 2010Mike Danko
Initial creation of book by publican

OpenNMS Release History

Revision History
Revision 1.8.2Thu Aug 10 2010 
Release 1.8.2 is the third in the 1.8 series of production-ready OpenNMS releases.
The codename for 1.8.2 is Spotted Sandpiper.
Revision 1.8.1Not Reported 
Release 1.8.1 is the second in the 1.8 series of production-ready OpenNMS releases.
The codename for 1.8.1 is Lady Gould.
Revision 1.8.0Not Reported 
Release 1.8.0 is the first in the 1.8 series of production-ready OpenNMS releases.
The codename for 1.8.1 is Cardinal.
Revision 1.7.92Not Reported 
Release 1.7.92 is the third release candidate in the 1.8 series. It represents what will eventually become OpenNMS 1.8.0 when it is declared stable.
The codename for 1.7.92 is Fria.
Revision 1.7.91Not Reported 
Release 1.7.91 is the second release candidate in the 1.8 series. It represents what will eventually become OpenNMS 1.8.0 when it is declared stable.
The codename for 1.7.91 is JFGI.
Revision 1.7.90Not Reported 
Release 1.7.91 is the first release candidate in the 1.8 series. It represents what will eventually become OpenNMS 1.8.0 when it is declared stable.
The codename for 1.7.90 is Born Slippy.
Revision 1.7.10Not Reported 
Release 1.7.10 is the latest in a series of development releases of OpenNMS. This represents what will eventually become OpenNMS 1.8.0 when it is declared feature-complete and stable.
The codename for 1.7.10 is Bebop.
Revision 1.7.9Not Reported 
Release 1.7.9 is the latest in a series of development releases of OpenNMS. This represents what will eventually become OpenNMS 1.8.0 when it is declared feature-complete and stable.
The codename for 1.7.9 is Jack.
Revision 1.7.8Not Reported 
Release 1.7.8 is the latest in a series of development releases of OpenNMS. This represents what will eventually become OpenNMS 1.8.0 when it is declared feature-complete and stable.
The codename for 1.7.8 is Serenity.
Revision 1.7.7Not Reported 
Release 1.7.7 is the latest in a series of development releases of OpenNMS. This represents what will eventually become OpenNMS 1.8.0 when it is declared feature-complete and stable.
The codename for 1.7.7 is Clyde.
Revision 1.7.6Not Reported 
Release 1.7.6 is the latest in a series of development releases of OpenNMS. This represents what will eventually become OpenNMS 1.8.0 when it is declared feature-complete and stable.
The codename for 1.7.6 is Orange Chicken.
Revision 1.7.5Not Reported 
Release 1.7.5 is the latest in a series of development releases of OpenNMS. This represents what will eventually become OpenNMS 1.8.0 when it is declared feature-complete and stable.
The codename for 1.7.5 is ShamWow!.
Revision 1.7.4Not Reported 
Release 1.7.4 is the latest in a series of development releases of OpenNMS. This represents what will eventually become OpenNMS 1.8.0 when it is declared feature-complete and stable.
The codename for 1.7.4 is eels.
Revision 1.7.3Not Reported 
Release 1.7.3 is the latest in a series of development releases of OpenNMS. This represents what will eventually become OpenNMS 1.8.0 when it is declared feature-complete and stable.
The codename for 1.7.3 is auto-tune.
Revision 1.7.2Not Reported 
Release 1.7.2 is the latest in a series of development releases of OpenNMS. This represents what will eventually become OpenNMS 1.8.0 when it is declared feature-complete and stable.
The codename for 1.7.2 is culpa.
Revision 1.7.1Not Reported 
Release 1.7.1 is the latest in a series of development releases of OpenNMS. This represents what will eventually become OpenNMS 1.8.0 when it is declared feature-complete and stable.
The codename for 1.7.1 is Oops We Did It Again.
Revision 1.7.3Not Reported 
Release 1.7.0 is the latest in a series of development releases of OpenNMS. This represents what will eventually become OpenNMS 1.8.0 when it is declared feature-complete and stable.
The codename for 1.7.0 is GIRAFFES!.
Revision 1.6.10Not Reported 
Release 1.6.10 is a minor feature release in the 1.6 series.
The codename for 1.6.10 is Cowboy.
Revision 1.6.9Not Reported 
Release 1.6.9 is a minor feature release in the 1.6 series.
The codename for 1.6.9 is Bauer.
Revision 1.6.8Not Reported 
Release 1.6.8 is a minor feature release in the 1.6 series.
The codename for 1.6.8 is Easy Button.
Revision 1.6.7Not Reported 
Release 1.6.7 is a minor feature release in the 1.6 series.
The codename for 1.6.7 is Bonnie.
Revision 1.6.6Not Reported 
Release 1.6.6 is a bugfix release in the 1.6 series. It is a recommended upgrade for all users.
The codename for 1.6.6 is Helmethead.
Revision 1.6.5Not Reported 
Release 1.6.5 is a small bugfix release in the 1.6 series. It is a recommended upgrade for all users.
The codename for 1.6.5 is Eastern Conference Finals.
Revision 1.6.4Not Reported 
Release 1.6.4 continues the 1.6 series with a fix for a showstopper exception in OpenNMS 1.6.3. It is a strongly recommended upgrade for all users.
The codename for 1.6.4 is mea.
Revision 1.6.3Not Reported 
Release 1.6.3 continues the 1.6 series with a small set of bug fixes and minor feature enhancements. It is a recommended upgrade for all users.
The codename for 1.6.3 is waterfall.
Revision 1.6.2Not Reported 
Release 1.6.2 continues the 1.6 series with a small set of bug fixes and minor feature enhancements. It is a recommended upgrade for all users.
The codename for 1.6.2 is software mercenaries.
Revision 1.6.1Not Reported 
Release 1.6.1 continues the 1.6 series with a small set of bug fixes and minor feature enhancements. It is a recommended upgrade for all users.
The codename for 1.6.1 is bamboo army.
Revision 1.6.0Not Reported 
Release 1.6.0 is the first stable release in the OpenNMS 1.6 series.

Index

F

feedback1
contact information for this manual, We Need Feedback!