Cisco UCSM v3.0.1 MP causing errors when service is installed on a SCOM gateway.

I'm testing the new UCSM v3.0.1 management pack with SCOM 2012 R2 UR2 on a gateway server.  The task is to run the UCS service on a SCOM gateway so opening ports in the firewall will not be necessary.

Everything install as it should, no error.  I have a RunAs account created and assigned.  The Cisco UCS monitoring wizard template has been created.  The Cisco UCS system is discovered and shows inventory.

He is the problem, the SCOM event log on the Gateway has 1000's of event id 4508's, error shown below.  I get one error for every server every few minutes.

Any ideas?

Thanks,

-Matt.

Loading managed module type in assembly "Microsoft.Mom.DatabaseQueryModules, Culture="", PublicKeyToken="31bf3856ad364e35", Version="7.0.5000.0"" with type name "Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.GroupCalculationModule" failed with error "The module assembly "Microsoft.Mom.DatabaseQueryModules, Culture="", PublicKeyToken="31bf3856ad364e35", Version="7.0.5000.0"" could not be loaded.  The exception was: \nCould not load file or assembly 'Microsoft.Mom.DatabaseQueryModules, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified..".

This may be because the type or assembly could not be found or the type does not have the MonitoringModuleAttribute.

Workflow: Cisco.Ucsm.ae9ff92459fc4edf9a64e16c37e8b9cc.ServiceProfileReferenceBlade.Discovery

Instance: XXX-ESX-PRD04.xxxxx.local

Instance ID: {2EE8ADF9-B281-F862-FE31-8B042777EAC1}

Management Group: xxxxxxxx

Full Exception Text:

Microsoft.EnterpriseManagement.HealthService.HealthServiceException: The module assembly "Microsoft.Mom.DatabaseQueryModules, Culture="", PublicKeyToken="31bf3856ad364e35", Version="7.0.5000.0"" could not be loaded.  The exception was: \nCould not load file or assembly 'Microsoft.Mom.DatabaseQueryModules, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.. ---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Mom.DatabaseQueryModules, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)

   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)

   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)

   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)

   at System.Reflection.Assembly.Load(String assemblyString)

   at Microsoft.EnterpriseManagement.HealthService.Internal.ManagedHostHelper.LoadModuleType(String moduleAssemblyName, String moduleTypeName)

   --- End of inner exception stack trace ---

   at Microsoft.EnterpriseManagement.HealthService.Internal.ManagedHostHelper.LoadModuleType(String moduleAssemblyName, String moduleTypeName)

   at Microsoft.EnterpriseManagement.HealthService.Internal.ManagedHostHelper.Microsoft.EnterpriseManagement.HealthService.Internal.IManagedHostHelper.LoadAndInitializeModule(String moduleAssemblyName, String moduleTypeName, UInt32 countInputPorts, Boolean doesModuleHaveOutput, String configuration, Byte[] stateBlock, UInt32 stateBlockLength, Object& moduleReference, Object& moduleInputReference, Object& moduleInputBatchedReference)

Hi Matt,

In UCS management pack we show relationship between associated Service Profile and Blade/Rack Unit as a dotted link. This is a reference relationship between two existing elements.

'Microsoft.Mom.DatabaseQueryModules' is used by SCOM to create these relationships. But in SCOM, this assembly is only available on Management Severs and not on Gateway Servers and Agent Managed Computers. As a result, this relationship only works when UCS instance is monitored through a Management Server.

This should not impact the normal functioning of UCS management pack. Just that this relationship (dotted link in Diagram View) will not be visible for UCS instances that are monitored through Agent Managed Computer or Gateway Server.

SCOM tries to create this relationship even for management packs running on Agent Managed Computers or Gateway Servers and hence this error is shown in SCOM event log on these machines.

We have this understanding and will be working on this in our upcoming releases. For now we can ignore these 4508 exceptions.

Thanks,
Jasneet

Thanks for your reply.

Because of the gross number of error events (about a 1000 a day) in the OperationsManager log, it fills up and over writes missing important information.

Any way to suppress these errors.  Telling clients that all those errors should be ignored never goes over well:)

Thanks,

-Matt.

Hi Matt,

We would suggest to disable the discovery of the reference relationship, that should suppress these errors.

But the impact is the relationship between associated Service Profile and Blade/Rack Unit(dotted link in Diagram View) will not be visible for UCS instances for which the reference relationship is disabled.

You can follow the steps below to disable the reference relationship of UCS Instance for which the error is visible in SCOM

Steps to suppress the errors:

1. Open Operations Manager Shell on a Management Server.

2. Execute following commands for every UCS individually.

--> $ucsManagementPack = Get-SCOMManagementPack -DisplayName "<UCS_Instance_Name>"

--> $referenceDiscovery = Get-SCOMDiscovery -ManagementPack $ucsManagementPack | where-object {$_.name -like "*reference*"}

--> Disable-SCOMDiscovery -Discovery $referenceDiscovery -ManagementPack $ucsManagementPack

Thanks,

Amit Kumar

Thank you Amit.  I'll give this a test in our lab environment.

-Matt.