OpenNMS presentation

Network Management System

OpenNMS

Muhammad Tahir May 27,2016

Introduction• OpenNMS is the first Enterprise grade network

management platform developed under the open source model

• It provides online services such as websites, various web application, and databases.

• It run a variety of systems on their networks such as business servers with both Windows and Linux, proprietary VoIP systems, backup systems, and Virtualized platforms.

Features

• Fault Management Alarm Filtering Alarm Generation Alarm Handling Clear Correlation Email Alerts Fast Polling ICMP polling Passive Fault Detection SMS Alerts SNMP Trapping SNMP polling

Feature(2)

• Performence Mgmt Availiability monitoring Avg Response time data Bandwidth utilization data Buffer usage data Conditional Alerts Consistent performence level CPU load data Device Disk Space Data Device Fan Monitoring Device Temprature Monitoring Hardware Monitoring Historical logs

Interface Error Data Memory Utilization Network Discard Data Network Discovery Network Latency Data Network Topology Packet loss data Performence data collection Performence report generation Power supply monitoring Syslog Messages Utilization and Error Rates

The Web User Interface

•The Web UI is very straight forward to use•The home page provides a very-high level overview of information available •As shown below

Host Discovery•The very first thing to do is to configure some host to monitor•By default OpenNMS monitore no network nodes at all•Select Admin|Configure Discovery |Add New to add nodes individually to be discoverd•Once completed we will get something like shown in the followoing spcifics table screenshot

Availability•The likely most useful information at this point of time is availabilty of service discovered on the node.•Services are discovered on the nodes network interfaces and listed in the table•When services go down,OpenNMS triggers and (outage) event and the availibilty of the service is affected.•The availibility table before and after a service went down is shown side-by-side in the screenshot that follows

Events and Alarms

•Events can be thought of as immutable records while•Alarms add a mutable lifecycle to the event management subsystem of OpenNMS.

Organizing Users, Groups, and Catagories

• Users: The technical people like the employees of an organization.

• Groups: Can be used to group users by similar work responsibilities or even based on duty schedules. For example, Systems Administrators, Night Technicians, or Routers Maintenance Team can all be perfectly valid groups in OpenNMS.

• Roles: Although duty schedules can be set both on users and groups, Roles are specifically designed to define On Call Schedules for the staff.

Cont....

Catagories Management•Service Level Management Categories (SLM categories) are used to group interfaces and services. •You can see the default SLM categories on the home page (once logged in) in the Availability Over the Past 24 Hours table (aka. the Availability table) in the middle of the page. •Those categories can be configured to your liking and are useful to include in historical availability reports for management.

Catagories Management Cont......

•Surveillance Categories are used to define peruser custom Surveillance Views. •Surveillance views define the scope and layout of a user dashboard with the purpose of providing a quick view of the state of the network (or segment of the network). •Surveillance categories are not configured in XML like SLA categories but can be added, edited, or deleted directly from the Web UI and are stored in the database.

Service assurance through polling

• Polling via classes called monitors is the mechanism OpenNMS uses to assure the availability of network services.

• Various monitors are in charge of polling specific services such as HTTP, POP, or IMAP and custom monitors can be added for less common and more specific monitoring needs.

• It is possible to fine tune exactly how you wish to poll services. • For example, you can define the frequency of polling, the

number of retries before triggering an event, the amount of time to wait for a service response, and responsetime data can also be optionally persisted for later use.

SCHEDULED OUTAGES

• Another important way in which polling services can be configured is via scheduled outages.

• As the name suggests, scheduled outages are specific periods of times when certain devices will be brought down for general maintenance.

• Configuring scheduled outages when you bring nodes down for maintenance is not mandatory.

• However, when scheduled outages are not configured there is no way of knowing the difference between a real outage and a planned outage.

• Outages will be detected as being real thereby triggering events and possibly alarms and notices which in turn will affect the overall availability performance metrics.

Screen Shot