During a recent conversation on Configuration Manager 2012 SP1 with Unix/Linux agents it was discussed that Unix/Linux agents cannot currently be added to Service Manager as Configuration Items (CI’s). That’s ok, we can use Operations Manager’s connector to create CI’s for Unix/Linux agents from Operations Manager. Here’s the steps required:

 

(1) Find out what the correct class name is for the Unix/Linux system.

(2) Import the management pack that contains that class definition into SM.

(3) Use the powershell cmdlet to add the class to the whitelist.

(4) Edit the properties of the CI connector and put a checkmark in the box before your MP name so it will sync it and then hit "Sync Now".

(5) Create a new view under Configuration Items that shows any CI object of that class type (so you can see them).

 

Step 1: What is the correct class name?

 

This server was monitored by Operations Manager and is shown below from the Unix/Linux Computers view from the Administration pane.

image

And from the UNIX/Linux Computers view in the Monitoring pane.

image

To determine what management packs were added for these objects, I used a PowerShell script which lists all objects matching the content of solaris as shown below:

Get-SCOMClass | Where-object {$_.Displayname –match “solaris”}

 13

 

Step 2: Importing the management packs

In Service Manager we add management packs as required. To determine these we add the management pack which contains the system (in my case this was a Solaris 10 Operating System).  The final list of additionally required management packs is shown below which was determined by attempting to add the Solaris 10 Operating System and tracking back through dependencies / adding the dependencies from the bottom level as they were identified:

  • WS-Management Library
  • Microsoft System Center Operations Manager Library
  • UNIX/Linux Core Library
  • Solaris Operating System Library
  • Data Warehouse Library
  • Microsoft Generic Report Library
  • Solaris 10 Operating System

 10

Step 3: Adding to the whitelist

The PowerShell command for this is shown below:

Add-SCSMAllowListClass Microsoft.Solaris.10.computer

 15

Bonus tip:

The following trick from Maarten Goet who mentioned that you can do an add of all entities to the allowed list in Service Manager so you don’t have to individually add classes to the whitelist. The syntax is:

 

Add-SCSMAllowListClass system.entity

 19

 

Step 4: Changing what the connector syncs

Added the Solaris related classes to sync as part of the connector to Operations Manager.

11

Step 5: Create a new view

The final step was to create a new view for all Unix Computers which show the server synchronized from Operations Manager (cloud-sol.cloud.pvt).

 16

This class appears as expected within service manager and includes key information such as the name, IP address, architecture, agent version and SSH port number which Operations Manager is using to communicate with the system.

 17

These fields can be added to the view as shown below.

 18

Summary: Adding Unix/Linux computers as CI’s from Operations Manager follows the same process which is used to add other CI’s from Operations Manager and works as expected.

 

Previous blog posts on similar topics:

Adding Network Devices: https://www.catapultsystems.com/cfuller/archive/2012/07/13/how-do-i-integrate-operations-manager-2012-network-devices-into-service-manager-2012-as-configuration-items-[scsm-scom-sysctr].aspx

SQL databases: https://www.catapultsystems.com/cfuller/archive/2012/08/10/how-do-i-integrate-sql-databases-into-service-manager-2012-as-configuration-items-[scsm-scom-sysctr-sql].aspx

VMWare servers: https://www.catapultsystems.com/cfuller/archive/2012/07/13/how-do-i-integrate-operations-manager-2012-network-devices-into-service-manager-2012-as-configuration-items-[scsm-scom-sysctr].aspx