attachments/cfuller/media/windows-live-writer/integrating-operations-manager-2012-netw_726b/clip_image001_thumb.png

How do I integrate Operations Manager 2012 Network Devices into Service Manager 2012 as Configuration Items? [#SCSM, #SCOM, #SYSCTR]

During a recent client meeting the request was made that we integrate network devices which we monitor with Operations Manager 2012 into Service Manager 2012 as Configuration Items (CI’s). In theory this sounds easy – Operations Manager 2012 can monitor a variety of network devices out of the box and those become entities. We know that Operations Manager can synchronize with Service Manager to provide these entities (such as Windows Computers) and make them available to Service Manager. As always however, the devil is in the details.

From a high level these were the steps required (identified by Pete Zerger in http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/87781/Default.aspx):

(1) find out what the correct class name is for the network device.

(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).

More detailed steps:

(1) Finding out what the correct class name is for network devices

For this one, Oskar Landman to the rescue at: http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/81851/Default.aspx 

Oskar’s article was written about Service Manager 2010 and Operations Manager 2007 R2 but the ideas almost all still apply.

Finding the class name for network devices: using the Discovered Inventory view in the Monitoring pane showed the results below from my home lab. (My network devices are emulated using the Jalasoft product which Kevin Holman recommended in http://blogs.technet.com/b/kevinholman/archive/2012/02/17/test-demo-opsmgr-2012-network-monitoring-with-jalasoft-s-network-device-simulator.aspx). This shows that “Network Device” is what I care about for these network devices in Operations Manager.

clip_image001

ServiceManagerNetworkDevice03

On OpsMgr 2012 using PowerShell:

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

clip_image002

Indicates that I need to add the class for System.NetworkDevice and it’s included in the System.Library management pack.

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

From a variety of trial and error I found that I needed the following management packs to get my lab environment to synchronize these network devices as CI’s:

 

  • System.NetworkManagement.Library

Which depends on:

  • Microsoft.SystemCenter.DataWarehouse.Library
  • Microsoft.SystemCenter.OperationsManager.Library

During my testing I also ended up adding:

  • NetworkManagementLibrary.
  • System Image Library

Not all of these may be required, but for this blog post I was not able to test further restricting the required list of management packs. The management packs which were required were added from the OpsMgr 2012 RTM media in the ManagementPacks folder.

During my testing, I added the management packs below which I believe were required. Below is a screenshot of recently added management packs from the Service Manager UI:

clip_image012

The Network Management Library dependencies in Service Manager are shown below:

image

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

This is part of where things got interesting. For an OpsMgr guy, understanding how to launch the Service Manager Shell and load the required cmdlets was non-intuitive. here’s the process I ended up using. Additionally, the cmdlets and syntax has changed since Service Manager 2010.

Open the Service Manager Command Shell:

clip_image004

Cd \

Cd “C:\program files\Microsoft System Center 2012\Service Manager\Powershell\Microsoft.EnterpriseManagement.ServiceManager.Cmdlets”

Import-module .\Microsoft.EnterpriseManagement.ServiceManager.Cmdlets.psd1

To display what’s currently on the allow list in Service Manager 2012:

Get-SCSMAllowList

To add to the allow list in Service Manager 2012:

Add-SCSMAllowListClass  System.Networkdevice

Once this was added the list had the System.NetworkDevice as shown below:

clip_image006

(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".

In Service Manager, changed the connector for Operations Manager CI’s:

image

To include the new management pack:

ServiceManagerNetworkDevice02

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

In Service Manager in the Configuration Items view, I created a folder called “Network Devices”. Within this I created two views – the first containing all CI’s to see what existed in the Service Manager CI list and a second designed to only show the appropriate network devices. The All CI’s view looks like the following below:

image

The Network Devices view was defined based on the class “Network Device” in Service Manager:

clip_image008

The results of this view are shown below where the same three network devices from Operations Manager are now appearing as CI’s in Service Manager:

clip_image010

There are also a significant number of fields which are shown for the network device including: Access Mode, Certification, Location, Model, Port Number, Primary Owner Contact, Primary Owner Name, Virtual Community Suffix, SNMP Agent Address, SNMP Version, Supports SNMP, MIB2 System Name, System Object ID and Vendor.

clip_image014

As expected these network devices also integrated correctly into Service Manager such as in the example below where a network device is being added to an emergency change request.

clip_image001

I owe huge thanks to both Chris Ross for his insights on this topic and to Pete Zerger and Oskar Landman for blazing the trail required to build the foundation to making this feasible for an OpsMgr geek such as myself!

Additional recommended reading on this topic:

Pete Zerger’s article on including non-Windows devices from Operations Manager into the Service Manager CMDB: http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/87781/Default.aspx)

Oskar Landman’s article on configuring the SCOM CI connector in System Center Service Manager 2010: http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/81851/Default.aspx

 

UPDATE on 2/14/2013: I had an incorrect piece in here that Oskar pointed out to me and I have updated. I originally listed Add-SCSMAllowClassList but the correct one is actually Add-SCSMAllowListClass. Thank you Oskar for pointing this out!

Leave a Reply