First Look at OpsLogix’s VMware Management Pack (beta)–Part II

After taking a first look at OpsLogix’s VMware Management Pack I’ve released I’ve missed something that I usually test with such core MPs like this one. That test is to bring the discovered objects from SCOM to SCSM as Configuration Items. It is not something hard to do and I’ve described the process before here but nevertheless I think it will good to see it visually in this blog post.

First you need to import OpsLogix IMP –Base Library MP and OpsLogix IMP – VMWare MP in Service Manager.

image

But before actually importing these two you need to import also their dependencies:

image

image

In my case I’ve needed to import Operations Manager Internal Library, System Center Visualization Library and System Center Image Library. All management packs can be found in the SCOM installation in the Management Packs folder. Keep in mind that for the System Center Visualization Library the MPB file have to be imported:

image 

After successful import you need to configure your Operations Manager CI connector in SCOM to sync the VMWare MP:

image

Next we need to put some classes in the SCSM allow list in order to sync the instances for that classes. The classes we will find in SCOM Discovered Inventory View:

image

Now that we know the display names of the classes we can easily find their internal names with PowerShell.

image

You need to start Operations Manager cmdlet and execute the following commands:

  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Cluster"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Datacenter"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Datastore"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware ESX Server"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Network"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Resource Pool"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware vCenter"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Virtual Machine"}

Basically we need the following classes:

  • OpsLogix.IMP.VMWare.Cluster
  • OpsLogix.IMP.VMWare.Datacenter
  • OpsLogix.IMP.VMWare.Datastore
  • OpsLogix.IMP.VMWare.ESXServer
  • OpsLogix.IMP.VMWare.Network
  • OpsLogix.IMP.VMWare.ResourcePool
  • OpsLogix.IMP.VMWare.vCenter
  • OpsLogix.IMP.VMWare.VirtualMachine

Now that we have the internal names of the classes we can easily put them in SCSM allow list again with PowerShell:

image

I am using the built-in SCSM PowerShell cmdlets and executing these commands:

  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.Cluster
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.Datacenter
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.Datastore
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.ESXServer
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.Network
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.ResourcePool
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.vCenter
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.VirtualMachine

To verify that the classes are added to the allowed sync list you can use: Get-SCSMAllowList

Next you need to force sync on your Operations Manager CI connector. After the connector syncs successful you can create several views to check if the instances of these classes are synced:

image

image

image

image

image

image

image

The beta of the MP does not discover a lot of properties for the objects but I am hoping this will be changed in the final version or some of the next ones as proper and rich CMDB is important.

Extend CI class in Service Manager 2012

Stefan Koell wrote a guide on how to extend CI class in SCSM 2012. SCSM 2012 provides basic Configuration Manager Database that can be easily customized to meet your needs. This guide will show in some easy steps how you can leverage that easy customization. Read the full article here.

SCOM Configuration Item Connector in SCSM is stuck at 100 % and events with ID 34081 are logged in Operations Manager Log

Not so while ago I was challenged with this issue:

SYMPTOMS

  • Events logged in Operations Manager log on System Center Service Manager server:

Log Name:      Operations Manager
Source:        Operations Manager Connector
Date:         
<DATE>
Event ID:      34081
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      scsmserver.contoso.com
Description:
Connector Name=SCOM CI Connector, Id=<GUID>
Encountered unexpected exception of type Object reference not set to an instance of an object. during synchronization. The synchronization will resume on the next scheduled time.
Message: %3.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
<System>
<Provider Name=”Operations Manager Connector” />
<EventID Qualifiers=”49152″>34081</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=”
<DATE>” />
<EventRecordID>1845675</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>scsmserver.contoso.com</Computer>
<Security />
  </System>
  <EventData>
    <Data>Name=SCOM CI Connector, Id=<GUID></Data>
<Data>Object reference not set to an instance of an object.</Data>
  </EventData>
</Event>

———————–

Log Name:      Operations Manager
Source:        Operations Manager Connector
Date:         
<DATE>
Event ID:      34081
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     scsmserver.contoso.com
Description:
Connector Name=SCOM CI Connector, Id=<GUID>
Encountered unexpected exception of type NullReferenceException during synchronization. The synchronization will resume on the next scheduled time.
Message: Object reference not set to an instance of an object..
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
<System>
<Provider Name=”Operations Manager Connector” />
<EventID Qualifiers=”49152″>34081</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=”
<DATE>” />
<EventRecordID>1845677</EventRecordID>
    <Channel>Operations Manager</Channel>
   <Computer>scsmserver.contoso.com</Computer>
<Security />
  </System>
  <EventData>
<Data>Name=SCOM CI Connector, Id=<GUID></Data>
<Data>NullReferenceException</Data>
    <Data>Object reference not set to an instance of an object.</Data>
  </EventData>
</Event>
———————–

Log Name:      Operations Manager
Source:        Operations Manager Connector
Date:         
<DATE>
Event ID:      34081
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      scsmserver.contoso.com
Description:
Connector <SCSM Management Group Name>
Encountered unexpected exception of type OMConnector.<GUID>_SyncRule during synchronization. The synchronization will resume on the next scheduled time.
Message: System Center Operations Manager Synchronization Workflow (internal).
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
<System>
<Provider Name=”Operations Manager Connector” />
<EventID Qualifiers=”49152″>34081</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=”
<DATE>” />
<EventRecordID>1845678</EventRecordID>
    <Channel>Operations Manager</Channel>
<Computer>scsmserver.contoso.com</Computer>
<Security />
  </System>
  <EventData>
<Data><SCSM Management Group Name></Data>
<Data>OMConnector.<GUID>_SyncRule</Data>
<Data>System Center Operations Manager Synchronization Workflow (internal)</Data>
<Data><GUID></Data>
<Data>CI Sync with connector BME Id <GUID> to server scsmserver.contoso.com, Source Domain\User = <SCOM CI Connector Account></Data>
<Data>Object reference not set to an instance of an object.</Data>
</EventData>
</Event>

Note: The text has been modified to hide custom data.

  • SCOM CI Connector is stuck at 100% without finish date and finishes after next schedule synchronization date is start. When next scheduled synchronization date starts the SCOM CI Connector finishes with error.

CAUSE

  • You change SCOM CI Connector configuration by refreshing the synchronized management packs and one of the synced management pack is a custom unsealed management pack. That custom management pack was modified in SCOM but its version number was never changed and the modified version was not imported in SCSM. As result SCOM and SCSM have the same version number of this custom unsealed management pack but the management packs have different code in them.

RESOLUTION

  • Disable the unsealed custom management pack from syncing and save the SCOM CI Connector configuration. Synchronize the connector to test.
  • Delete the unsealed management pack from SCSM. Export the unsealed custom management pack from SCOM and import it in SCSM. Refresh the management packs in the SCOM CI Connector, select for synchronization the unsealed custom management pack and save the configuration. Synchronize the connector to test.

Adding Network Device monitored by SCOM in SCSM CMDB as CI

If you are using Operations Manager with Service Manager you probably sync the CMDB of SCSM with configuration items discovered by SCOM. This can be achieved by a series of steps that have to be executed in order to implement this solution. Cameron Fuller wrote a post on how to do that for Network Devices but the principal applies to almost any other Configuration items discovered by SCOM. Read the full article here.