Open Source Management Options September 30Th, 2008 Jane Curry Skills 1St Ltd

Total Page:16

File Type:pdf, Size:1020Kb

Open Source Management Options September 30Th, 2008 Jane Curry Skills 1St Ltd Open Source Management Options September 30th, 2008 Jane Curry Skills 1st Ltd www.skills-1st.co.uk Jane Curry Skills 1st Ltd 2 Cedar Chase Taplow Maidenhead SL6 0EU 01628 782565 [email protected] 1 Synopsis Nuts and bolts network and systems management is currently unfashionable. The emphasis is far more on processes that implement service management, driven by methodologies and best practices such as the Information Technology Infrastructure Library (ITIL). Nonetheless, all service management disciplines ultimately rely on a way to determine some of the following characteristics of systems and networks: ● Configuration management ● Availability management ● Problem management ● Performance management ● Change management ● Security management The commercial marketplace for systems and network management offerings tend to be dominated by the big four ± IBM, HP, CA and BMC. Each have large, modular offerings which tend to be very expensive. Each has grown their portfolio by buying up other companies and then performing some level of integration between their respective branded products. One can argue that the resulting offerings tend to be ªmarketechturesº rather than architectures. This paper looks at Open Source software that addresses the same requirements. Offerings from Netdisco, Cacti and The Dude are examined briefly, followed by an in- depth analysis of Nagios, OpenNMS and Zenoss. This paper is aimed at two audiences. For a discussion on systems management selection processes and an overview of three main open source contenders, read the first few chapters. The last few chapters then provide a product comparison. For those who want lots more detail on Nagios, OpenNMS and Zenoss, the middle sections provide in-depth discussions with plenty of screenshots. 2 Table of Contents 1 Defining ªSystems Managementº....................................................................................5 1.1 Jargon and processes................................................................................................5 1.2 ªSystems Managementº for this paper....................................................................6 2 Systems management tools.............................................................................................6 2.1 Choosing systems management tools......................................................................7 2.2 The advantages of Open Source...............................................................................8 3 Open Source management offerings...............................................................................8 4 Criteria for Open Source management tool selection.................................................10 4.1 General requirements.............................................................................................10 4.1.1 Mandatory Requirements...............................................................................10 4.1.2 Desirable Requirements..................................................................................10 4.2 Defining network and systems ªmanagementº.....................................................11 4.2.1 Network management.....................................................................................11 4.2.2 Systems management......................................................................................12 4.3 What is out-of-scope?..............................................................................................13 5 A quick look at Cacti, The Dude and netdisco..............................................................14 5.1 Cacti.........................................................................................................................14 5.2 netdisco....................................................................................................................17 5.3 The Dude..................................................................................................................20 6 Nagios..............................................................................................................................21 6.1 Configuration ± Discovery and topology................................................................22 6.2 Availability monitoring...........................................................................................27 6.3 Problem management.............................................................................................32 6.3.1 Event console....................................................................................................33 6.3.2 Internally generated events............................................................................37 6.3.3 SNMP TRAP reception and configuration.....................................................39 6.3.4 Nagios notifications ........................................................................................39 6.3.5 Automatic responses to events ± event handlers..........................................41 6.4 Performance management......................................................................................42 6.5 Nagios summary.....................................................................................................45 7 OpenNMS........................................................................................................................46 7.1 Configuration ± Discovery and topology................................................................47 7.1.1 Interface discovery...........................................................................................47 7.1.2 Service discovery..............................................................................................48 7.1.3 Topology mapping and displays......................................................................51 7.2 Availability monitoring...........................................................................................53 7.3 Problem management.............................................................................................59 7.3.1 Event console....................................................................................................59 7.3.2 Internally generated events............................................................................62 7.3.3 SNMP TRAP reception and configuration.....................................................65 7.3.4 Alarms, notifications and automations..........................................................69 3 7.4 Performance management......................................................................................76 7.4.1 Defining data collections.................................................................................76 7.4.2 Displaying performance data..........................................................................85 7.4.3 Thresholding....................................................................................................91 7.5 Managing OpenNMS..............................................................................................97 7.6 OpenNMS summary...............................................................................................98 8 Zenoss..............................................................................................................................98 8.1 Configuration ± Discovery and topology..............................................................100 8.1.1 Zenoss discovery.............................................................................................100 8.1.2 Zenoss topology maps....................................................................................107 8.2 Availability monitoring........................................................................................108 8.2.1 Basic reachability availability......................................................................108 8.2.2 Availability monitoring of services - TCP / UDP ports and windows services ...................................................................................................................................110 8.2.3 Process availability monitoring....................................................................113 8.2.4 Running commands on devices.....................................................................120 8.3 Problem management...........................................................................................121 8.3.1 Event console.................................................................................................122 8.3.2 Internally generated events..........................................................................123 8.3.3 SNMP TRAP reception and configuration...................................................125 8.3.4 email / pager alerting....................................................................................126 8.3.5 Event automations.........................................................................................131 8.4 Performance management....................................................................................132 8.4.1 Defining data collection, thresholding and graphs.....................................132 8.4.2 Displaying performance data graphs...........................................................138 8.5 Zenoss summary....................................................................................................141 9 Comparison of Nagios, OpenNMS and Zenoss...........................................................142
Recommended publications
  • The World's First Enterprise-Grade Open Source Network Management
    The World’s First Enterprise-grade Open Source Network Management Platform OpenNMS is the world’s first enterprise-grade Event Management and Notifications network management application developed under the open-source model. It is a free OpenNMS is event driven, and the system has software alternative to commercial products such the ability to generate internal events, such as a as Hewlett-Packard’s OpenView, IBM’s Netcool loss of a service, as well as to receive external and Tivoli, and CA Unicenter. events, such as SNMP Traps. Each event can be fed into a robust notification system that can Because OpenNMS is open source software, there send e-mails, pages, text messages, pop-ups are no software license costs. Since the software and even instant messages via XMPP (Jabber). code can be freely modified, OpenNMS can also Notices can be acknowledged, automatically be changed to fit the way the organization works, resolved and escalated. instead of having to change processes and procedures to fit the software. OpenNMS was designed from Day One to be able to monitor tens of thousands of interfaces. The ultimate goal for the software is to become the de facto network management platform. OpenNMS is focused on four main areas: • Automated Discovery • Event Management and Notifications • Service Level Monitoring • Performance Data Collection In addition, OpenNMS includes an event translator that can take an event and turn it Automated Discovery into another event. Fields in the original event It would be very difcult to configure by hand can then be parsed and used to access external thousands of devices, thus OpenNMS was databases (such as a customer or inventory designed to automate the process of network system) and a new enriched event created.
    [Show full text]
  • Mysql Enterprise Monitor 2.0 Mysql Enterprise Monitor 2.0 Manual
    MySQL Enterprise Monitor 2.0 MySQL Enterprise Monitor 2.0 Manual Copyright © 2005, 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
    [Show full text]
  • Whats New Opennms 2019
    www.opennms.co.uk Whats New OpenNMS 2019 Dr Craig Gallen, Director Entimoss Ltd (OpenNMS UK) Associate Lecturer Solent University Craig Gallen Email : [email protected] : [email protected] : [email protected] Mobile: +44 (0) 7789 938012 Craig © OpenNMS / Entimoss 2014 entimOSS limited Company registered in England and Wales No. 06402040 Contents www.opennms.co.uk OpenNMS Project Overview OpenNMS Functional Overview Future directions © OpenNMS / Entimoss 2012 slide - 1 Converged Virtualised Services www.opennms.co.uk End user Services (Apps) are a mash-up of web services accessed through standard and Application proprietary protocols; Access Network Cloud • HTTP, REST, SOAP, Space JSON, RSS, • Open Data / RDF etc. • ‘Internet of things’ URI URI URI Service 1 Services hosted in Virtualised Service 3 Service 2 VM ‘Cloud’ designed to VM scale through addition Infrastructure VM of VM resources And applications VM VM VM VM VM VM ‘cloud bursting’ VM VM VM ‘cloud brokering’ Underlying physical infrastructure Physical •Commodity hardware •Geographical Diversity Infrastructure •Rapid Churn •Network Connectivity Core Network Cloud © OpenNMS / Entimoss 2012 slide - 2 Moving to Virtualised Networks www.opennms.co.uk You May Have Heard Of • Software defined Networking • Research / Data Centre • Open Flow • Network Functions Virtualisation • Service providers – ETSI • TM Forum ZOOM • Zero-touch Orchestration, Operations and Management (ZOOM) • ETSI’s vision for Network Functions Virtualisation — http://www.telco2research.com/articles/WP_telco2-network-functions-virtualisation-NFV-vs-software-defined-networking- SDN_Summary © OpenNMS / Entimoss 2012 slide - 3 OSGi – facilitates integration into Open Daylight SDN/SFV controller www.opennms.co.uk © OpenNMS / Entimoss 2012 slide - 4 OpenNMS futures www.opennms.co.uk © OpenNMS / Entimoss 2012 slide - 5 The OpenNMS Project www.opennms.co.uk • OpenNMS — Open Network Management System — OpenNMS is the world's first Enterprise and Carrier grade network management platform developed under the open source model.
    [Show full text]
  • Architecture of Network Management Tools for Heterogeneous System
    (IJCSIS) International Journal of Computer Science and Information Security, Vol. 6, No. 3, 2009 Architecture of Network Management Tools for Heterogeneous System Rosilah Hassan, Rozilawati Razali, Shima Mohseni, Ola Mohamad and Zahian Ismail Department of Computer Science, Faculty of Information Science and Technology Universiti Kebangsaan Malaysia, Bangi, Selangor, Malaysia . Human: where human manager defines the policy and organization approaches. Abstract— Managing heterogeneous network systems is Methodology: defines the architectural a difficult task because each of these networks has its own curious management system. These networks framework and the functions to be usually are constructed on independent management performed. protocols which are not compatible with each other. Instrumentation: the actual operational This results in the coexistence of many management aspects that establish the procedures, systems with different managing functions and services methods and algorithms for data collection, across enterprises. Incompatibility of different processing and reporting, and analysis of management systems makes management of whole problems, their repair, prediction or system a very complex and often complicated job. forecasting of service levels and probable Ideally, it is necessary to implement centralized meta- level management across distributed heterogeneous improvements to enhance performance. systems and their underlying supporting network systems where the information flow and guidance is S&NM aims to provide network
    [Show full text]
  • Opennms Provisioning
    OpenNMS Provisioning OpenNMS version 1.8.0 The OpenNMS Group, Inc. 220 Chatham Business Drive, Suite 220 Pittsboro, NC 27312 T +1 919 533-0160 F Work Fax Phone [email protected] http://www.opennms.com The OpenNMS Group, Inc. Provisioning 5 Summary 5 Concepts 5 OpenNMS Provisioning Terminology 5 Entity 6 Foreign Source and Foreign ID 6 Foreign Source Definition 6 Import Requisition 6 Auto Discovery 6 Directed Discovery 6 Enhanced Directed Discovery 7 Policy Based Discovery 7 Addressing Scalability 7 Parallelization and Non-Blocking I/O 7 Provisioning Policies 7 The Default Foreign Source Definition 8 Getting Started 8 Provisioning the SNMP Configuration 8 Automatic Discovery 9 Separation of Concerns 9 Enhanced Directed Discovery 10 Understanding the Process 10 Import Handlers 12 File Handler 12 HTTP Handler 12 DNS Handler 12 DNS Import Examples: 12 Simple 12 Using a Regular Expression Filter 12 DNS Setup 13 Configuration 13 OpenNMS Provisioning 1 The OpenNMS Group, Inc. Configuration Reload 13 Provisioning Examples 14 Basic Provisioning 14 Defining the Nodes via the Web-UI 14 Import the Nodes 16 Adding a Node 16 Changing a Node 17 Deleting a Node 17 Deleting all the Nodes 18 Advanced Provisioning Example 19 Service Detection 20 Applying a New Foreign Source Definition 20 Provisioning with Policies 21 New Import Capabilities 23 Provisiond Configuration 23 Provisioning Asset Data 24 External Requisition Sources 25 Provisioning Nodes from DNS 25 Adapters 27 DDNS Adapter 27 RANCID Adapter 27 Maps (soon to be moved to Mapd) 27 WiMax-Link (soon to be moved to Linkd) 27 Integrating with Provisiond 28 Provisioning Groups of Nodes 28 Example 28 Step 1 (Create a Foreign Source) 28 Step 2 (Update the SNMP configuration) 29 Step 3 (Create/Update the Requisition) 29 Adding a Node to a Current Requisition 29 Provisioning Single Nodes (Quick Add Node) 30 Fine Grained Provisioning Using “provision.pl” 31 First, Create a new Provisioning Group 31 OpenNMS Provisioning 2 The OpenNMS Group, Inc.
    [Show full text]
  • Opennms Release Notes
    OpenNMS Release Notes Cumulative Release History Copyright © 2004-2012 Tarus Balog, Matt Brozowski, David Hustace, Benjamin Reed 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 Preface ................................................................................................................................... vi 1. Introduction ......................................................................................................................... 1 1.1. Release 1.12.9 ........................................................................................................... 1 1.2. Release 1.12.8 ........................................................................................................... 1 1.3. Release 1.12.7 ........................................................................................................... 1 1.4. Release 1.12.6 ........................................................................................................... 1 1.5. Release 1.12.5 ........................................................................................................... 1 1.6. Release 1.12.4 ........................................................................................................... 1 1.7. Release
    [Show full text]
  • Assessing the Impact of Lack of Network Documentation in Higher Learning Institutions: Case of University of Dodoma
    The University of Dodoma University of Dodoma Institutional Repository http://repository.udom.ac.tz Information and Communication Technology Master Dissertations 2014 Assessing the impact of lack of network documentation in higher learning institutions: Case of University of Dodoma Kachemela, Seif J The University of Dodoma Kachemela, J. S. (2014). Assessing the impact of lack of network documentation in higher learning institutions: Case of University of Dodoma (Master's dissertation). The University of Dodoma, Dodoma. http://hdl.handle.net/20.500.12661/1352 Downloaded from UDOM Institutional Repository at The University of Dodoma, an open access institutional repository. ASSESSING THE IMPACT OF LACK OF NETWORK DOCUMENTATION IN HIGHER LEARNING INSTITUTIONS: CASE OF UNIVERSITY OF DODOMA By Seif J. Kachemela Dissertation Submitted in Partial Fulfillment of the Requirements for the Degree of Master of Science in Computer Science of the University of Dodoma The University of Dodoma October, 2014 CERTIFICATION The undersigned certify that they have read and hereby recommend for acceptance by the University of Dodoma a dissertation entitled “Assessing the severity of the technological impact of lack of network documentation in higher learning institutions: Case of University of Dodoma”, in partial fulfillment of the requirements for the degree of Master of Science in Computer Science of the University of Dodoma. ………………………..……. Dr. Leonard. J. MseIle (SUPERVISOR) ………………………………. Prof. Justinian Anatory (SUPERVISOR) Date……………………………….. i DECLARATION AND COPYRIGHT I, Seif J. Kachemela, declare that this dissertation is my own original work and that it has not been presented and will not be presented to any other University for a similar or any other degree award.
    [Show full text]
  • W.Chinthaka Prasanna Senanayaka 15/1A, Perera Mw
    GSoC 2011 – OpenNMS project proposal Create a maven archetype for creating GWT based XML configuration management and implement three of them W.Chinthaka Prasanna Senanayaka 15/1A, Perera Mw, Meethotamulla, Wellampitiya, Colombo, Sri Lanka. Tel. No. +94718443972 E-mail: [email protected] / [email protected] Personal Details Name: Wahalatantrige Chinthaka Prasanna Senanayaka (W.C.P. Senanayaka) University: University of Kelaniya, Sri Lanka. Course: B.Sc. in Management and Information Technology (3rd year, Special) Email address: [email protected] Physical address: 15/1 A, Perera Mw, Meethotamulla, Wellampitiya, Colombo, Sri Lanka. Phone numbers: +94718443972 Web page: http://chinthakarobotikka.blogspot.com/ IM contacts: Skype: chinthakas87 IRC nick: chinthakas Availability: 1. I can spend on GSoC OpenNMS project, 5–7 hours per day practically. 2. As GSoC time plan I can start and end the project, and I will continue the contact with OpenNMS projects. 3. Other factors affects my availability are university examinations (I have examinations on 2011/04/23, 2011/04/30, 2011/05/02. And before the next semester exams come, GSoC will be finished). 1 GSoC 2011 – OpenNMS project proposal Starting date delays: no delays. Background Information Education background: Did Mathematics, Physics for Advance Level examination. Then I entered to University and now I am in 3rd year special batch. Software development background: I have worked at H’Senid Software International Pvt Ltd (mobile software development, as an undergraduate trainee software engineer). Computer languages: C, JAVA, VB (VB.NET and VB script), PHP (HTML, Javascript), ASP.NET (average), and Scala (average) Other Java compliant tools: Spring, Hibernate, Vaardin Software: Linux – Ubuntu, MySQL, Flash, SQL SERVER Software design using UML (just started learning BPMN) Other: Maven, special interest in open source Why I am interested in OpenNMS: 1.
    [Show full text]
  • Opennms Meridian Release Notes
    OpenNMS Meridian Release Notes Copyright (c) 2016-2019 The OpenNMS Group, Inc. OpenNMS Meridian v2017.1.26, Last updated 2020-09-01 19:13:44 UTC Table of Contents OpenNMS Meridian Development Team . 1 OpenNMS Meridian 2017 . 1 System Requirements. 1 What’s New in Meridian 2017 . 1 Release Meridian-2017.1.26 . 6 Release Meridian-2017.1.25 . 7 Release Meridian-2017.1.24 . 7 Release Meridian-2017.1.23 . 7 Release Meridian-2017.1.22 . 8 Release Meridian-2017.1.21 . 8 Release Meridian-2017.1.20 . 8 Release Meridian-2017.1.19 . 8 Release Meridian-2017.1.18 . 9 Release Meridian-2017.1.17 . 9 Release Meridian-2017.1.16 . 9 Release Meridian-2017.1.15 . 10 Release Meridian-2017.1.14 . 10 Release Meridian-2017.1.13 . 10 Release Meridian-2017.1.12 . 11 Release Meridian-2017.1.11 . 11 Release Meridian-2017.1.10 . 11 Release Meridian-2017.1.9 . 14 Release Meridian-2017.1.8 . 14 Release Meridian-2017.1.7 . 15 Release Meridian-2017.1.6 . 16 Release Meridian-2017.1.5 . 16 Release Meridian-2017.1.4 . 16 Release Meridian-2017.1.3 . 17 Release Meridian-2017.1.2 . 17 Release Meridian-2017.1.1 . 18 Release Meridian-2017.1.0 . 19 OpenNMS Meridian Development Team Tarus Balog <[email protected]> David Hustace <[email protected]> Benjamin Reed <[email protected]> Copyright © 2004-2020 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.
    [Show full text]
  • V3.5 IP Address Management Software
    GestióIP IPAM v3.5 IP address management software Documentation v1.11 www.gestioip.net GestióIP Copyright © Marc Uebel 2021 Documentation GestióIP IPAM v3.5 Table of Contents 1 Introduction......................................................................................................................................7 2 Use....................................................................................................................................................8 2.1 Access.......................................................................................................................................8 2.2 Show networks..........................................................................................................................8 2.2.1 Root networks.................................................................................................................10 2.3 Show hosts..............................................................................................................................11 2.3.1 Host list view..................................................................................................................11 2.3.2 Host overview.................................................................................................................13 2.3.3 Host status view..............................................................................................................13 2.3.4 Host check.......................................................................................................................14
    [Show full text]
  • Developers Guide
    Developers Guide Copyright (c) 2015-2019 The OpenNMS Group, Inc. OpenNMS Meridian 2019.1.23, Last updated 2021-09-07 21:58:30 UTC Table of Contents 1. Setup a development system . 1 1.1. Operating System / Environment . 1 1.2. Installation . 1 1.3. Tooling. 3 1.4. Useful links. 3 1.4.1. General . 3 1.4.2. Installation / Setup . 3 2. Topology . 4 2.1. Info Panel Items . 4 2.1.1. Programmatic . 4 2.1.2. Scriptable . 5 2.2. GraphML . 9 2.2.1. Create/Update/Delete GraphML Topology. 10 2.2.2. Supported Attributes . 11 2.2.3. Focus Strategies . 12 2.2.4. Icons . 12 2.2.5. Vertex Status Provider . 13 2.2.6. Edge Status Provider . 13 2.2.7. Layers . 14 2.2.8. Breadcrumbs . 16 2.3. Topologies Updates. 20 2.3.1. OnmsTopologyUpdater . 20 2.3.2. OnmsTopologyRef. 20 2.3.3. OnmsTopologyMessage . 21 2.3.4. OnmsTopologyProtocol . 21 2.3.5. TopologyMessageStatus. 21 2.3.6. OnmsTopology. 21 2.3.7. OnmsTopologyVertex. 21 2.3.8. OnmsTopologyEdge . 21 2.3.9. OnmsTopologyPort . 22 2.3.10. OnmsTopologyConsumer . 22 3. CORS Support . 23 3.1. Why do I need CORS support?. 23 3.2. How can I enable CORS support? . 23 3.3. How can I configure CORS support? . 23 4. ReST API . 24 4.1. ReST URL. 24 4.2. Authentication. 24 4.3. Data format . 24 4.4. Standard Parameters . 24 4.5. Standard filter examples . 25 4.6. HTTP Return Codes . 26 4.7. Identifying Resources .
    [Show full text]
  • Systems Monitoring Shootout Finding Your Way in the Maze of Monitoring Tools
    Systems Monitoring Shootout Finding your way in the Maze of Monitoring tools Kris Buytaert Tom De Cooman Inuits Inuits [email protected] [email protected] Frederic Descamps Bart Verwilst Inuits Inuits [email protected] [email protected] Abstract serving, do you want to know about the internal state of your JBoss, or be triggered if the OOM killer will start The open source market is getting overcrowded with working soon? . As you see, there are several ways of different Network Monitoring solutions, and not with- monitoring depending on the level of detail. out reason: monitoring your infrastructure is becoming more important each day. You have to know what’s go- In our monitoring tool, we add hosts. This host can be ing on for your boss, your customers, and for yourself. any device we would like to monitor. Next we need to define what parameter on the host we would like to Nagios started the evolution, but today OpenNMS, check, how we are going to get the data, and at which Zabix, Zenoss, GroundWorks, Hyperic, and different point we’d consider the values not within normal lim- others are showing up in the market. its anymore. The result is called a check. There are several ways to ‘get’ the required data. Most monitor- Do you want light-weight, or feature-full? How far do ing tools can use SNMP as a way to gather the required you want to go with your monitoring, just on an OS data. Either the tool itself performs an SNMP-get, or it level, or do you want to dig into your applications, do receives data via an SNMP-trap.
    [Show full text]