SCC-SCOM2Nagios Connector

Lizenz: 

Copyright (C) 2009 Markus Baeker
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; 
either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; 
without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, see <http://www.gnu.org/licenses/>.

INSTALLATION:
=============

The connector runs as a service on the OpsMgr Server. DotNET 3.0 must be installed!

1.) To install, copy the contents of the "Release" Folder to some local
    directory e.g. c:\scom2nagios, and from a DOS-Window run:

"%systemroot%\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe" Nagios-SCOMConnector.exe

    This will install the connector through the dotNet installer.

2.) Start -> Run -> services.msc

   You should see a new Service called "KIT Nagios Connector", but DON'T start it
   now! Furthermore, you have to register the connector for the OpsMgr. Open
   a DOS-Window and change to the scom2nagios dir (e.g. cd c:\scom2nagios) and
   run:

Nagios-SCOMConnector.exe InstallConnector

=OUTPUT=>

Created Nagios Connector with ID: {038F2550-B6F3-11DD-BBCC-4EF555D89593}

CONFIGURATION:
==============

3.) We have to configure the Nagios Connector for our Nagios Host. Open
    the file Nagios-SCOMConnector.exe.config with NOTEPAD or s.th. like that,
    and look for the following lines:


a.)   <setting name="NagiosHost" serializeAs="String">
        <value>nagios.host.local</value> 
      </setting>

Set "nagios.host.local" to your Nagios Server (either DNS-name or IP)

b.)    <setting name="NagiosPort" serializeAs="String">
        <value>5667</value>
      </setting>

NSCA Port. Normally this value is correct.

c.)    <setting name="ncsaPath" serializeAs="String">
        <value>undef</value>
      </setting>
      <setting name="ncsaConfigFile" serializeAs="String">
        <value>undef.config</value>
      </setting>

You have to set the full path to send_nsca.exe and send_nsca.cfg!
Also you MUST include the filenames! E.g.:

      <setting name="ncsaPath" serializeAs="String">
        <value>C:\scom2nagios\send_nsca.exe</value>
      </setting>
      <setting name="ncsaConfigFile" serializeAs="String">
        <value>C:\scom2nagios\send_nsca.cfg</value>
      </setting>


d.)   <setting name="NagiosHost1" serializeAs="String">
        <value></value>
      </setting>
      <setting name="NagiosPort1" serializeAs="String">
        <value></value>
      </setting>

OPTIONAL: Only set something here, if you want a second Nagios host
to receive the results.

e.)   <setting name="NagiosSCOMService" serializeAs="String">
       <value>p_scom</value>
      </setting>

This parameter sets the "Service Description" Nagios will get from
SCOM to be able to assign its results to the correct host/service.

f.) This section enables more verbose logging:

<add name="DebugLevel"  value="3" />

If you want everything, set this to "4", otherwise set it 
to "0" or "1". The logs can be found in 

C:\Documents and Settings\All Users\Application Data\KIT\

g.) Last configuration step is to modify send_nsca.cfg 
    according to your NSCA installation on the Nagios host.
    The two options are

password=
encryption_method=

For a default NSCA installation on your Nagios host, set them to those
values:

#password=
encryption_method=1

STARTUP:
========

4.) Start the "KIT Nagios Connector" service. Set Recovery options in
    the Recovery Tab of the service, since it might be unstable and
    terminate itself unexpectedly.

OPSMGR-CONFIGURATION:
=====================

You have to define rules for the Connector to receive Alerts
from the Administration Menu. To test the Connector, go 
to the active Alert section, and with a right click, forward
an alert to the Nagios Connector, and see if you get results.

UNINSTALL:
==========

Go to the scom2nagios directory and remove the Connector from the 
OpsMgr Server:

Nagios-SCOMConnector.exe UninstallConnector

And then remove the service, again, with the dotNet installer:

"%systemroot%\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe" -u Nagios-SCOMConnector.exe