by OpenNMS to collect data from the network elements from southbound interface. A majority of the data processing functions including certain performance reports still rely on SNMP MIB to data from devices being managed. Current versions of OpenNMS also have support for data collection using HTTP and JMX (Java Management Extensions). The HTTP data collector can collect metrics for generating a performance report that gives the application ability to collect data from ele- ments without having to implement the SNMP agent. A dedicated JMX agent should be running on the device to be monitored, for OpenNMS to collect data using JMX. The main configuration file for data collection is collectd- configuration.xml. There are many more daemon processes like OpenNMS.Eventd that is con- cerned with writing and receiving all the event information, OpenNMS.Trapd to handle asynchronous trap information, and OpenNMS.Threshd process to manage threshold settings. These processes use numerous open source products like joesnmp for SNMP data collection, log4j for event generation, postgresql as DBMS inter- face, and (JRobin) RRDTool to store graph data, just to name a few. OpenNMS got a Gold Award for "Product Excellence in 2007" in the Network Management Platform category, against competing products like OpenView of HP NMS Products (Hewlett-Packard) and Tivoli of IBM. This is a major achievement for an open source product when competing with some of the best NMS products available in the telecom industry. OpenNMS application and source can be downloaded from sourceforge.net and the product Web site is www.opennms.org. 13.3 AdventNet Web NMS AdventNet is a framework for building customized network and element man- agement solutions. It provides a variety of fault, configuration, performance, and security functionalities as part of network monitoring and offers inventory manage- ment and provisioning services. Being a framework, it supports multiple adapters for interfacing with northbound GUI applications, southbound network element