Sync HP ProLiant Server and BladeSystem CIs from SCOM to SCSM

There is a great article at systemcentercentral.com on how to synchronize CI from SCOM to SCSM. The article shows an example with Dell Management Pack. I followed this article and will show you how to do the same for HP ProLiant Server Management Pack and HP BladeSystem Management Pack. Let first introduce what objects are discovered  trough these two MPs:

  • HP ProLiant Server Management Pack – This management pack discovers properties of all HP ProLiant servers – IP addresses of ILOs, Memory, Disks and etc.
  • HP BladeSystem Management Pack – This MP discovers properties of c3000 and c7000 Enclosures – Names, Onboard Administrators, Device Bays (including server information for blades) and etc.

So here are the steps you can follow to sync your HP CIs from SCOM to SCSM:

1. Lets assume that you imported and configured HP ProLiant Server and HP BladeSystem MPs in SCOM.

2. Next steps is to figure out what information you want to sync.

3. You can find that by going in SCOM console –> Monitoring pane –> Discovered Inventory view.

image

4. Right Click on the middle view and select Change Target Type.

5. Select Items to Target window appears. In Look for field type “hp” and select View all targets.

image

6. Here you can see the friendly names of the different classes and to which Management Pack they belong to.

7. “HP Server” is the main class that holds information for HP Servers and it is located in Hewlett-Packard Servers Core Library MP. Select it and click OK.

Note: You can select any subclass like HP ProLiant Server if you find it more convenient for you.

8. After selecting it in the middle pane you will see information about your HP Servers you have in your environment. This information you want to sync in SCSM.

image

9. Next step is to find the friendly name for enclosures class.

10. Right click on the middle pane again and select Change Target Type.

11. Select Items to Target window appears. In Look for field type “hp” and select View all targets.

image

12. “HP BladeSystem Enclosure” is the main class that holds information for HP Enclosures and it is located in Hewlett-Packard BladeSystem Management Pack. Select it and click OK.

image

13. You will see the information about enclosures you want to sync to SCSM.

14. For HP Enclosures I select one more class “HP BladeSystem Device Bay”.

image

15. This class holds information about blade servers. This is useful if you have have blade servers in the enclosures that do not have operating system and because of that they do not have SCOM agent also. WIhtout SCOM agent you not cannot get any information for them from HP ProLiant Server Management Pack but trough this class you can.

16. Next step is to see the names of the management pack and if they have dependencies.

17. Open SCOM console –> Administration pane –> Management Packs.

18. We found that the the information that we want to sync is contained in two management packs – Hewlett-Packard Servers Core Library and Hewlett-Packard BladeSystem Management Pack.

19. Find them in that view and right click on them Properties.

20. In General tab you under ID you will see thee name of the management pack. In Dependencies tab that you will see which other management pack you should also import in SCSM. If you do not have these MPs in your SCSM environment you will not be able to import the HP Management Packs.

Hewlett-Packard.Servers.Core.Library.mp

image

Hewlett-Packard.ProLiant.Servers.Base.mp

image

Hewlett-Packard.BladeSystem.mp

image

21. Even I do not need to import Hewlett-Packard ProLiant Servers Base Management Pack I will import it because may be later I will want to sync some information from that MP.

22. Next steps is to find the actual names of the classes we want to sync because we only have the friendly names: HP Server, HP BladeSystem Enclosure and HP BladeSystem Device Bay.

23. Open Operations Manager PowerShell and execute the following commands one by one:

  • Get-MonitoringClass | Where-object {$_.DisplayName -match "HP Server"
  • Get-MonitoringClass | Where-object {$_.DisplayName -match "HP BladeSystem Enclosure"
  • Get-MonitoringClass | Where-object {$_.DisplayName -match "HP BladeSystem Device Bay"

24. The commands will find all properties about classes that have these display names. Against property Name you will find the actual names of the classes we need:

  • HewlettPackard.Servers.HPServer
  • HewlettPackard.Servers.BladeSystem.HPBladeSystemEnclosure
  • HewlettPackard.Servers.BladeSystem.HPBladeSystemDeviceBay

25. Now that we have the actual names of the classes we want to sync we have to import the 3 HP management packs in SCSM.

26. Open SCSM console. Navigate to Administration pane –> Management Packs.

27. Click Import from Actions menu. Find the location where you store your MPs select the 3 HP MPs and import them.

28. If the MPs are imported successfully next step is to add the classes we have found to the allowed list of classes for syncing in SCSM.

29. Logon to your SCSM server.

30. Start PowerShell and execute these commands:

  • set-executionpolicy Unrestricted
  • add-pssnapin smcmdletsnapin
  • Add-SCSMAllowListClass –ClassName HewlettPackard.Servers.HPServer
  • Add-SCSMAllowListClass –ClassName HewlettPackard.Servers.BladeSystem.HPBladeSystemEnclosure
  • Add-SCSMAllowListClass –ClassName HewlettPackard.Servers.BladeSystem.HPBladeSystemDeviceBay
  • get-SCSMAllowlist

31. With the last command you will be able to see the HP classes added in the allowed list for sync.

32. Next step is to configure your SCOM CI Connector in SCSM to sync the HP Management Packs.

33. Open SCSM console. Navigate to Administration pane –> Connectors.

34. Find you SCOM CI Connector in the list of connectors and double click on it.

35. The Properties window of that connector will be opened.

36. Select the configuration option for Management Packs.

37. In order to see your newly imported HP Management Packs you have to click Refresh button. When you click Refresh you will be asked for the password of the account that is used to sync management packs between SCOM and SCSM. Enter the password and press OK.

38. When refresh is done the new management packs will appear in the list. Select them and click OK to save settings.

image

39. Wait until next synchronization schedule of SCOM CI Connector to see if synchronization was successful.

40. When synchronization is done you can create views to see the synchronized data in SCSM.

41. Open SCSM console. Navigate to Configuration Items. Create new folder. You can name the folder “HP Devices” or any convenient name for you.

42. Under that folder you can create 3 different views that have different HP classes for Criteria.

image

image

image

Note: This configuration was tested with SCOM 2007 R2 and SCSM 2010 but it should also work for SCOM 2012 and SCSM 2012.

Note: You can sync more classes than the ones described in the article depending on your customers needs. Just add these classes to the allowed for sync list in point 30.

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.