June 19, 2011

Monitoring Fedora Core 4 with SCOM 2007 R2 – Part 3

earthIn the part 3 of the Fedora Core 4 discovery pack I will explain the creation of the discovery management pack in detail.

Creating the new MP for Discovery:

  • Open the Authoring Console (please use the newest on. I have used 6.1.7221.49)
  • File –> New and enter the required values
  • File –> Management Pack Properties
  • Select the tab References –> Add Reference
  • Add Reference to Microsoft.Linux.RHEL.4, change the alias to RHEL4 (it’s shorter and easier to use) and a reference to the Microsoft.Unix.Library with the alias Unix. Your reference tab should look like the picture 1 (the picture has another reference to linux but this will be added automaticly with the discovery)
  • Switch to Health Model, select Discovery
  • new Custom Discovery, name Technidata.Fedora.4.Computer.Discovery
    • Target: Microsoft.Linux.RedHat.Computer
    • Discovered Classes: Add class Microsoft.Linux.RHEL.4.Computer
    • Configuration: Browse… and select: Microsoft.Unix.WSMan.TimedEnumerate.Filtered.MatchesRegularExpression.DiscoveryData and add a module id like discovery
    • Press Edit and enter the xml from part 2 into the editor: replace the text between Configuration> and with the XML text […]
    • Close the editor
    • your discovery tab should look like picture 2
  • Do the same with the second xml from part 2
  • Your discovery pack is ready to be imported into your test SCOM environment.
read more
June 3, 2011

Monitoring Fedora Core 4 with SCOM 2007 R2 – Part 2

earthThe creation of the troja management pack is easy. You only have to add to discovery tasks which create the RHEL4 computer object and the operating system object and fills them with some basic informations.

In the authoring console you have the add a reference to the Microsoft.Linux.RHEL.4 MP because we will use the RHEL4 Computer object.

This is the XML code of the first discovery task:

Discovery $Target/Property[Type=”Unix!Microsoft.Unix.Computer”]/NetworkName$ [http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX\_OperatingSystem?\__cimnamespace=root/scx][1] false 300 //*[local-name()=”Caption”] .\*Fedora Core release 4.\* $MPElement[Name=”RHEL4!Microsoft.Linux.RHEL.4.Computer”]$ $MPElement[Name=”Unix!Microsoft.Unix.Computer”]/PrincipalName$ $Target/Property[Type=”Unix!Microsoft.Unix.Computer”]/PrincipalName$ $MPElement[Name=”Unix!Microsoft.Unix.Computer”]/TimeZoneOffset$ $Data///*[local-name()=”CurrentTimeZone”]$
read more
June 2, 2011

Monitoring Fedora Core 4 with SCOM 2007 R2 – Part 1

earthFedora bases upon Red Hat Enterprise linux which is supported by SCOM. Fedora Core 3 was the base of  RHEL 4 and Fedora Core 6 RHEL 5. In this blog posts I will try to convince SCOM that the Fedora 4 based Asterisk telecom system is a RHEL 4.

First we have to install the RHEL4 scom agent manual onto the systems. In this case we had to install the OpenSSL library, too. Additional we add the scom user account to the system.

After that we sign the local created certificate by the scom server and replace it on the Fedora system.

Now we can test the connection from the SCOM server with this winrm command:

winrm enumerate http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_OperatingSystem?__cimnamespace=root/scx -username:scomuser -password:yourpassword -r:https://your.fedora.system:1270/wsman -auth:basic -encoding:UTF-8

The output shows detail information about the OS:

read more