This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Mar /April 2000OpenNMS Announced & Code released10 OcuLAN employees50 contributors
Sept 2004 OpenNMS group lunched3 staff 16 contributors
Jan 1999Steve Gilles & Brian WeaverPrototype Bluebird
May 2002OcuLAN forks OpenNMSTarus Balog becomes Maintainer (Sortova Consulting)
2009 over 100 OpenNMS group customers4000 complete downloads / month6 staff35 core developers (OGP)
• We've been around since 1999 and were registered on Sourceforge in March of 2000 (by comparison NetSaint, the first name of Nag ios, was registered just two months earlier).
Community and GovernanceCommunity and Governance• User community
— There are around 1000 people subscribed to the discuss list, but when I (Tarus Balog) teach classes I find that less than 10% of the people in the class actually use the discuss list, somy guess is that the active user community is probable closer to 10,000 people.
• Developer Community— We have 35 developers with commit access to the repository.
• Assets— Liscence GPL— The IPR is owned by The OpenNMS Group, Inc. — OpenNMS Trademark owned by The OpenNMS Group
• Governance— The community is managed by The Order of the Green Polo.— All active OGP members have a vote on the direction of the
project, but there is no charter and no one restricts what can and can't go into OpenNMS, as long as it is good.
— For example, the OTRS integration that Jonathin Sartin(Ocado/Truephone) did was pretty much on his own.
• Foundation— We would like to create a foundation
separate to the OpenNMS Group when sponsorship is available to do so.
Opennms.comOpennms.com OpenNMSOpenNMS Group IncGroup Inc• Mission
— The OpenNMS Group is a services company dedicated to promoting the OpenNMS Project.
• Market Proposition— The main market proposition is that Network Management Platforms are expensive to buy and even more
expensive to deploy.— The open source nature of OpenNMS allows one to get rid of the software licensing cost associated with
solutions and since it is more flexible it can also reduce deployment time while providing more custom functionality (i.e. the solution can be made to fit the business and not the other way around).
• Revenue Sources— Revenues are based on support subscriptions, custom development, consulting and training (in that order).
• OpenNMS Group— Privately owned— Tarus Balog - CEO— David Hustace – President— Matt Brozowski – CTO (Chief Architect)— Benjamin Reed – Infrastructure and packaging— Jeff Gehlbach – Customer Service
• Preferred strategic business models— In country partner for delivery e.g.;
– Antonio Russo http://www.opennms.it– Craig Gallen www.entimoss.com
— Package solution for Equipment vendors— OpenNMS Group provide 2nd / 3rd level support
Problem Management Work FlowProblem Management Work Flow• Event Collection
— OpenNMS can record all event occurrences
• Alarm Correlation— OpenNMS uses an Alarm Mechanism to convert
configurable 'alarm raising traps' or 'alarm clearing traps' into a manageable alarm cycle. On first receiving a trap, an alarm is raised. subsequent traps are counted against the alarm. A clearing trap clears the alarm ready for a new raise event.. This is the simplest use of the alarm list. However, user configured 'automations' can process the alarm list for more sophisticated analysis. In addition, OpenNMSleverage's the Jboss Rules correlation engine for more sophisticated down stream alarm suppressing.
• User Notifications and scheduled escalation— OpenNMS supports multiple users and an Notification
escalation mechanism between users. If a severe event is detected (such as a major alarm), this generates a Notification which is escalated over time through a list of users if it is not acknowledged. The system can also generate external paging, emails or instant messaging messages to attract attention to a notification.
• Trouble ticket integration— If the basic escalation mechanism is not enough,
OpenNMS also has a Trouble ticket interface for integrating with a number of trouble ticket systems including open source trouble ticket implementations, RT and OTRS.
Performance and SLA ManagementPerformance and SLA Management• Performance Data Collection and Management
— Like other network management tools such as Nagios or Cricket, OpenNMS stores performance data in RRD files. It can use RRDTool to do the collection, but the preferred library is Jrobin which is a Java implementation of RRD.
— OpenNMS has MIBS already installed for most large vendors equipment but users can add their own configurations. The user community often share this work and experience of new equipment.
— However unlike these tools, all of the scheduling of data collection is controlled by a Java process entirely within OpenNMS which makes the solution very scalable.
— Data can be collected from a variety of sources; SNMP polling and trap management, Ascii Syslog messages, TL1, JMX. there is also an integration with Nagios to allow the use of Nagios plugins. OpenNMS has also been integrated with Snort.
• Data visualisation— OpenNMS presents performance data as graphs. These
graphs can also be exported in the form of performance reports.
— Threshold events. OpenNMS can generate Threshold crossing alarms based on changes in the data. OpenNMSalso performs synthetic transactions to test the availability ofservices on nodes. This can be done centrally or through a distributed collection of remote rollers as described above.
• Service Quality Management— SLA Alarms can be escalated based upon threshold crossing
events. Every performance data collection point can be assigned a lo/high threshold with hysteresis to avoid ‘bouncing’ alarms
— All OpenNMS configuration is via a set of XML files contained within one directory. Many of these configurations are also exposed through the user interface. Configuration includes scan rates, Trap to event/alarm mapping, Mib management etc.
• Network Discovery — Given an IP address range, OpenNMS can self
discover the elements and services in a network. OpenNMS automatically associates ports with nodes. The default naming of a node in the database will be populated with the name of the device discovered by an SNMP scan of the device.
• Configuration Interfaces— An external event driven XML interface can also be
used to populate and change the Network Inventory. This interface is used by Swisscom to synchronise OpenNMS with their expanding European Wifi hotspot network.
• Integration— Numerous points of integration for paging, alarm
OpenNMSOpenNMS Extension PointsExtension Points• Service Detector API
— detection of services (Capsd Plugin API being deprecated)— Java Interface (org.opennms.netmgt.provision.ServiceDetector.java)
• Service Monitor API — Poller Plugin API for monitoring detected services— Java Interface (org.opennms.netmgt.poller.ServiceMonitor.java)
• Service Collector API — Collectd Plugin API for creating performance data collectors— Java Interface (org.opennms.netmgt.collectd.ServiceCollector.java)
• Service Thresholder API— Plugin API for creating Thresholders of detected services— Java Interface (org.opennms.netmgt.threshd.ServiceThresholder.java)
• Notification Strategy API — Plugin API for creating new notification methods— Java Interface (org.opennms.netmgt.notifd.NotificationStrategy.java)
• Acknowledgment Reader API — Plugin API for reading replies to notifications)— Java Interface (org.opennms.netmgt.ackd.AckReader.java)
• Provision Adapter API — Plugin API for integrating CMS, EMS, Inventory systems, etc— Java Interface (org.opennms.netmgt.provision.ProvisioningAdapter.java)
creates events when a performance metric exceeds preset values. High, Hi rearm, Low, Low rearm, Relative Change
Eventd receives and writes all of the event information.The eventd process listens on port 5817, so other processes, even those external to OpenNMS, can send events to the system
eventd
Xmlrpcd allows events to be sent from OpenNMSto a remote system via XML-RPC
Actiond is used to generate java actions based on events received. actiond is triggered by the "autoaction" tag on an event <autoaction>Scriptd similar to Actiond, generates external actions based on events.
Passive
Statusd
‘Passive nodes’ are used to represent services or resources managed by another agent. The event translator and passive status deamon allow events to be mapped to these nodes
allows OpenNMS to receive syslog datagrams
Vacuumd
Trigger, evaluation, action automations processing of alarm table
User NotificationsUser Notifications• OpenNMS uses notifications to make
users aware of an event. Common notification methods are email and paging, but notification mechanisms also exist for
— XMPP (Jabber, an instant messaging protocol),
— arbitrary external programs — SNMP traps can be sent, and — arbitrary HTTP GETs/POSTs can be made to
a web site.
• Scheduling on call— A notification can be sent to users, groups, or
roles configured in OpenNMS, as well as to arbitrary email addresses, if needed. A delay can be introduced before sending a notification, and one or more escalations can be added in case a notification isn't acknowledged within a configurable period of time
— destination path specifies the "who", "when", and "how" of the notification
Discoveryd ICMP pings the prescribed device ranges to find new devices, it then passes a suspect node event to capsd for further processing
Capsd is responsible for discovering all the services to be monitored on a device
suspect Nodeevent
Linkd is layer 2 iso/osi model network topology discovery daemon..iso.org.dod.internet.mgmt.mib-2.ip.ipNetToMediaTable.iso.org.dod.internet.mgmt.mib-2.dot1dBridge.dot1dBase.iso.org.dod.internet.mgmt.mib-2.dot1dBridge.dot1dStp
Gathers and stores data from various sources, including SNMP, JMX, HTTP and NSClient
Handles all service polling and recording of response times using synthetic transactions
If device supports SNMP,
Capsd sets up configuration for topology discovery, polling and data gathering based upon discovered services
When using the Importer Service, the Discovery and Capsd services are disabled. Instead of ping sweeps by the Discovery service, OpenNMS is told about nodes and interfaces in an XML export from a provisioning system.
Internet search services Monitoring search engines
New Edge Networks http://www.newedgenetworks.com/
IP VPN network provider (Brunelli, M. 2005) (Balog, T. 2007b) Providing customer service stats Nodes: 12278 Interfaces: 67738 Services: 569188 (300,000 data points every five minutes)
Removing Chinese Walls in NPIRemoving Chinese Walls in NPI• New product Introduction• Very costly for firms to understand
users' needs deeply and well – ‘sticky information’
— Manufacturer cannot expect to get a solution right first time (von Hippel, E. 2001b)
— Product consultants used as front end to marketing - 'ethnographic' study of user needs (von Hippel, E. 2001b),
— How users apply OSS tools is often tacit knowledge - i.e. knowledge that they carry in their heads and is, therefore, difficult to access (Polanyi, M. 1967)
— Risk that solution meets the letter of the specification, but may still fail to appreciate the underlying requirements (Chapman, C. B. et al. 2003 p271 ff)
• Learning from prototypes — Looking at machine tools - process by
which users and manufacturers learnt from using prototypes was more intentional than just 'trial and error'.Rather, users exhibited a form of complex pattern matching (which von Hippel termed 'Templating') (von Hippel, E. & Tyre, M. J. 1995)
Open Source enables Network effectsOpen Source enables Network effects• OSS industry – Network Effects
— Each component depends on all other components— Common interfaces allow components to be
deployed— High value components depend upon commodity
functionality (e.g. data collection)
• (Ghosh, R. A. 2005a) suggests that one approach to network effects is to try to abstract the network externalities from specific products by identifying the features of the technology that provides the network effect and ensuring that its use is not limited to one product or service.
• (Ghosh, R. A. 2005a) argues that to be successful this strategy requires reference
• implementations to augment - if not, perhaps, replace - the formal specification of the standard . When such a reference implementation is available under an open source licence, it may achieve the same economic effect as an open standard, even without the institutional processes of standard setting