We have installed a Cisco UCS Management Pack in SCOM, i addition to other Windows 2008 Management Packs. SCOM is collecting health/availability information without any issues. We have sucessfully installed a SCOM adapter in our vCOPS 5.0 instance. While we see the Windows Server managed by SCOM as resources in vCOPS, we do not see the UCS as a resource. Has anyone been able to get Cisco UCS Information into vCOPS via SCOM using the SCOM Adapter?
i just saw this maybe its still helpfull.
page 24
Add a Top-Level Resource Kind
By default, the MS SCOM adapter recognizes the
Microsoft.Windows.Computer
and
Microsoft.SQLServer.DBEngine
top-level resource kinds. You can configure additional top-level resource
kinds.
Prerequisites
Install the MS SCOM adapter. See
Chapter 2, “Installing the Microsoft SCOM Adapter,”
on page 13.
Procedure
1 Run the
discoverySQL
query for your database type.
The query returns all MS SCOM entities, their types, and identifiers.
2 Find the entity to become a top-level resource kind and make a note of the value in the RESKIND
column.
3 Edit the
scom.properties
file and add the value from the RESKIND column to the comma-separated list
in the
topLevelResourceKinds
property.
4 Save your changes and close the
scom.properties
file.
If the UCS MP isn't already in an existing relationship on the SCOM side with the microsoft.windows.computer (or other resource/object related to microsoft.windows.computer), you're going to have to figure out a way to do it within vCOps. The challenge there is not necessarily getting the UCS MPs to get imported in to vCOps, it's also going to be building the relationships between the UCS MP blade objects and vCOps Hosts. I personally haven't tried importing data from the SCOM UCS MP, but I would think this relationship will be your challenge. On the data collection side, you may need to modify the scom discovery/collection scripts if the UCS MP creates object types that aren't discovered by default. How that relationship is made will depend if sufficient identifiers are pulled in from the UCS blades and VM Hosts to 'make' that 1-to-1 association/relationship via relationship sql script (preferable).
You could also manually define those relationships in the Custom UI GUI, but I recommend against that since it's simply not efficient for larger environment. If you have no other choice, though, you certainly could.
