Posts Tagged


SLES 11 HAE guide

Since last month I’m studying a nice topic like the “High Availability” on Linux OS. If you have a SLES 11 and a license for High Availability Extension add-on, this guide could be really helpful for a good understanding. The lack of official and well documented procedures it’s really common for these graceless topics, but this one with its 495 pages looks awesome.


It’s a really comprehensive manual accompanied with simple examples and many pictures & screenshots. If you want to get familiar with words like Corosync, OpenAIS, STONITH and other, please give it a try. In case you have previous versions like the HA Extension SP1, most of commands seem to work perfectly. From the release notes of SP2 you can see that big changes to components haven’t been done, and that’s what care most 😉 (especially for enterprises environments)

Thanks SuSE for the great job, that’s why I like this distro for Enterprise purpose! Here the link to the page for the .pdf file.

[Update: the guide has been updated on June 26th 2013!!}

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
SNMPv2-SMI::enterprises.12356. = INTEGER: 1
SNMPv2-SMI::enterprises.12356. = INTEGER: 2
### cluster is down ###
[root@nms2 ~]# snmpwalk -v2c –c public  fwIP
SNMPv2-SMI::enterprises.12356. = 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=""/>
            <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"/>

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