Posts Tagged

OpenNMS

Monitor the cluster on Fortinet devices. New OID

Updating firmwares from Fortinet v4.0 MR2 to MR3, the “cluster-check” was no more working on OpenNMS. After searching on Fortinet Knowledge base pages I figured out that Fortinet has changed the OID for the cluster checks. This is the new OID:

### cluster is up and running ###
[root@nms2 ~]# snmpwalk -v2c –c public  fwIP 1.3.6.1.4.1.12356.101.13.2.1.1.1
SNMPv2-SMI::enterprises.12356.101.13.2.1.1.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.12356.101.13.2.1.1.1.2 = INTEGER: 2
### cluster is down ###
[root@nms2 ~]# snmpwalk -v2c –c public  fwIP 1.3.6.1.4.1.12356.101.13.2.1.1.1
SNMPv2-SMI::enterprises.12356.101.13.2.1.1.1.1 = INTEGER: 1

To add the new service we just need to add this monitor on the file poller-configuration.xml.

<service name="FortinetCluster" interval="300000"
            user-defined="false" status="on">
            <parameter key="retry" value="1"/>
            <parameter key="timeout" value="3000"/>
            <parameter key="port" value="161"/>
            <parameter key="oid" value="1.3.6.1.4.1.12356.101.13.2.1.1.1"/>
            <parameter key="operator" value="&lt;"/>
            <parameter key="operand" value="3"/>
            <parameter key="walk" value="true"/>
            <parameter key="match-all" value="count"/>
            <parameter key="minimum" value="2"/>
            <parameter key="maximum" value="2"/>
</service>

As a final step the only thing missing is to add this service to the interested nodes (your updated Fortigates).

OUCE 2013, let’s start with a real community.

Welcome back! The distance was about 750 kilometers: 6 hours spent on these impressively fast highways and passed through amazing views like “ZugSpitze” & FernPass. Honestly I have to say it was a good decision this reunion at OUCE 2013.

OUCE means OpenNMS User Conference Europe, and this was the fifth edition. Well at first I thought it was the 3rd or the 2nd official event in the Europe, since it’s still a “work in progress” event, but Markus (a guy involved directly into OpenNMS Group) addressed me to the correct number of times. Compared to the last year it seemed more a “User Conference”, lots of speakers proposed several topics, users were more involved and partecipative to discussions and the number of people seemed to be higher. It was also the first opportunity to talk about the creation of the new OpenNMS Foundation, a no-profit Foundation which will helps OpenNMS to live “autonomously” without the need of OpenNMS Group (the Company). Even if there has not been a deep discussion, as expected, this time I felt like being in a kind of community which seemed to grow!

So what are we waiting for? There’s a good amount of people “involved” and “attracted” by this product, but they’re still missing a good community to support it for “users”. At the moment the only trace of  community  it’s a sort of mailing list in different languages. As I said also to OpenNMS “guys”, I don’t really like it. I get spammed everyday with tons of posts regarding beginners who are not able to install OpenNMS on the most diverse operating systems of the world, updates not working and so on… Following and searching on a mailing list nowadays it is no more up to date. Why don’t we think about a forum/website, just for users? It could also be the start to create a good user documentation to complete the existing “poor” one from OpenNMS Group.

OpenNMS, check email status (MailTransport)

 

Carrying on talking about OpenNMS features, this time I’d like to introduce the service called Mail Transport Monitor, normally abbreviated to MTM. The aim of this service is to monitor the complete functioning of your mail system: sending and receiving e-mails. For this purpose we need an “external” email which should rapidly answer to our request with a so called “echo-reply”, to let us know that everything’s working. Instead of putting an automatic reply rule to your ”free” Gmail/Hotmail/Yahoo (etc..) account, it would be nice to have an automatic service that does this job automatically, without any configuration. These services exists and they’re public (anyone can use them) but unfortunately they’re not so reliable as expected (if you only think at how many emails per seconds they receive, maybe this delay is understandable)

Here you can look at the most famous Echo-Mailer (just a German page on Wikipedia, Google helps you). After many tries, here’s my suggestion: echo@tu-berlin.de and echo@univie.ac.at are the best choices. If you send an email no more frequently than every 2 minutes, you will never have problems with them (since 6-7 months). Now we can have a look on how it’s the configured OpenNMS and this tricky MTM service.

Read More

OpenNMS, how to start.

Before starting to work in a real company,  I didn’t know anything about devices monitoring. When I arrived there the most impressing thing was how much the Team cares about knowing at every time how was the status of all the devices we need to manage. For that reason there were already installed, and properly configured, the most “popular” monitoring softwares like Nagios, Cacti & SmokePing. All of them are complementary each other, with the exception of Nagios that with 3rd part plugins can become more powerful than as it is out of the box.

In order to avoid a continuos switch from these 3 tools, we start a project  for introducing a pretty new  monitoring software called OpenNMS: our original purpose was to use a unique software for monitoring the infrastructure.  During the past 6 months I focused completely into customising and learning this software and I would like to express my experience about it…

Read More