Markus Bäker

Often I receive questions about how to install the connector. Here is a short step by step installation instruction:

1. Download the latest release (http://www.mbaeker.de/downloads/SCOM2Nagios_1.5.zip)
2. Extract the archive
3. Copy the “Release” folder to c:\
4. rename it to scom2nagios
5. Copy the “processing.xml” from documentation to c:\scom2nagios
6. Start an administrative command shell
7. change to c:\scom2nagios (cd /d c:\scom2nagios)
8. start the Service Installer with "%systemroot%\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe" Nagios-SCOMConnector.exe (see the 1. screenshoot)
   
9. Register the connector to SCOM with Nagios-SCOMConnector.exe InstallConnector
10. Edit Nagios-SCOMConnector.exe.config and change the ncsaPath (2. screenshoot)
    
11. Edit the service “KIT Nagios Connector” to Restart on Failure (3. Screenshoot)
    
12. Select the connector in the OpsMgr Console (Administration –> Product Connectos –> Internal Connector, 4. Screenshoot)
    
13. Right click the conenctor and select Properties (Screenshot 5)
    
14. Add a suitable subscription to the connector to send alerts to it.
    

Hi, I had a question where you can find the settings for the automatic forwarded alerts to nagios in SCOM. You can find it here:

1. Administration Pane

2. Product Connectors –> Internal Connectors

3. Select the Nagios Connector

4. Properties

5. There you can add or edit subscription (the wizard is like the Notification Subscription Wizard)

Here is a screenshoot:

Wie bereits angekündigt, ist mein SCOM vs. Icinga Artikel jetzt auch auf Computerwoche online erschienen:

Microsofts System Center Operations Manager und der Nagios-Ableger Icinga sind verbreitete IT-Monitoring-Lösungen. Hier eine Gegenüberstellung der beiden Werkzeuge.

http://www.computerwoche.de/software/software-infrastruktur/2366841/

Nach zwei erfolgreichen Vorträgen zum Thema Icinga und SCOM in Karlsruhe und Markdorf ist jetzt auch der entsprechende Artikel in der Computerwoche veröffentlicht worden. Wer ihn verpasst hat, kann ihn auch hier finden: http://www.its-technidata.de/de/News-Archiv/Seiten/MicrosoftSCOMversusOpenSource.aspx

Demnächst erscheint er wahrscheinlich auch nochmal auf Computerwoche.de und  Tecchannel.de.

Find the newest version on top of: http://www.mbaeker.de/tag/scom2nagios/

Released a new Version of the SCOM2Nagios Connector. Changes:

1.4

* NEW: variables for processing instruction
* NEW: change case of output (upper/lower)
* BUG: no crash if scom connection is lost
* BUG: no longer needs fullpath in config

Example:

<instruction>
<input field=”path” compare=”containsIgnoreCase”>mcscom</input>
<output field=”host” case=”upper”>$path</output>
</instruction>

If path contains mcscom than replace the host in the output with the upper case of the ObjectFullPath variable of the input alert.

Possible replacement variables:

path, netbios, fullname, severity, state, name, description, alertid

Download: SCOM2Nagios (784)

Find the newest version on top of: http://www.mbaeker.de/tag/scom2nagios/

I have uploaded a release of the Nagios Connector 1.3. You can read about the changes in this post:

http://www.mbaeker.de/2009/10/preinfo-nagios2scom-1-3/
I have only made some short and fast tests. So be cautious.

Download: SCOM2Nagios (141)

If you not only want to connect OpsMgr to Nagios with my connector but other management systems to OpsMgr than the OpenUMR can perhaps help you.

It does more than just creating  alerts in SCOM: it even creates the correct objects for the alerts.

More infos: http://openumr.codeplex.com/

The new version is released here: http://www.mbaeker.de/category/tools/scom2nagios/

The next release will address two feature requests:

1. Possibility to change the hostname (you don’t use fqdn host names in nagios…)
2. Possibility to use more than one service in nagios (you want to separate the alerts for dns and acitve directory)

I will try to solve both by using “processing instructions”. This instructions will use the scom alert as an input filter and the nagios alert as the object to manipulate.

This instructions are defined in a xml file:

<?xml version=’1.0′ encoding=’ISO-8859-1′?>
<instructions>

<!–
field:
scom: path (of monitoringobject), fullname (of monitoringobject), severity, state, name (of alert), description
nagios: text, host, service, state

compare:
contains, containsIgnoreCase, equals, equalIgnoreCase

–>

<instruction>

<input field=”path” compare=”contains”>DNS</input>
<output field=”service”>DNS</output>
</instruction>

<instruction>
<input field=”state” compare=”equals”>255</input>
<output field=”text”>Everything is OK </output>
</instruction>

</instructions>

What do you think about this feature?

The main code is ready. It even compiles without problems… Next step is testing – but currently I have no operations manager test system with a connected nagios…

Find the newest version on top of: http://www.mbaeker.de/tag/scom2nagios/

Attached is the new version of the SCOM2Nagios Connector.

There is just one small thing changed:

You can now define the OK message in config file. So no more german status messages in your nagios

And thanks to Thomas Karatzoglou we now have an english installation instruction in the file.

Download Link: SCOM2Nagios (253)

FB_Addon_TelNo{ height:15px !important; white-space: nowrap !important; background-color: #0ff0ff;}

Find the newest version on top of: http://www.mbaeker.de/category/tools/scom2nagios/

Anbei die Version 1.1 des Nagios Connectors. Er beinhaltet nur geringe Änderungen:

• Ausgabe der Versionsnummer in der Logdatei
• Detailliertere Logausgaben
• Fehler beim zweiten Nagios Server: er wurde in jedem Fall aufgerufen

Download: SCOM2Nagios_1.1