The following System Center Operations Manager Management Packs are available for download from Cisco:
Cisco UCS Management Pack Suite for Microsoft System Center 2012, Operations Manager (version 4.1.2)
(Above link requires cisco.com login)
Video documentation links:
Details related to previous versions of Cisco UCS Manager and IMC Management Packs are as follows:
Cisco UCS Manager Management Pack v3.1.2 for Microsoft System Center 2012 - Operations Manager:
Cisco IMC Management Pack v1.2(1) for Microsoft System Center 2012 - Operations Manager:
External customers - For any issues, contact Cisco TAC (highly recommended for quick resolution) or add a discussion to the Cisco Developed Integrations sub-space on Cisco UCS Communities. Send your suggestions for new features to firstname.lastname@example.org.
Internal (Cisco) customers and employees - Contact us at email@example.com for support questions and firstname.lastname@example.org for roadmap questions, new feature requests and feedback.
do you have a date for supporting windows server 2012 r2 and system center operation manager 2012 r2?
We posted UCSM MP 2.6.2 today with support for SCOM 2012 R2 and Windows 2012 R2.
Are any of the UCSM MP versions backwards compatible with SCOM 2007 (non-R2)?
No Rachelle, it is not supported by Cisco UCSM SCOM Management Pack versions...
I noticed in the release notes that CSCul24411 had been fixed. I just deployed 2.6.2 on a freshly built SCOM 2012 R2 server running on Server 2012 and am getting the 19900 error in SCOM with associated details below:
Could not load file or assembly 'file:///C:\Windows\TEMP\1xpbmjao.dll' or one of its dependencies.
I am getting a "The page could not be loaded. Please review the errors and try again." error when trying to run the "Add Monitoring Wizard" to configure the MP 2.6.2 version. The error mentions something about a proxy; however there is no proxy between the OM server and the UCS Manager environment we are trying to monitor. One other item of note is that we are running Operations Manager 2012 R2 Update 2. The error details are:
Date: 5/28/2014 4:16:34 PM
Application: Operations Manager
Application Version: 7.1.10226.0
Microsoft.EnterpriseManagement.Internal.UI.Authoring.Extensibility.UISDKException: The page could not be loaded. Please review the errors and try again. ---> Microsoft.EnterpriseManagement.Internal.UI.Authoring.Extensibility.UISDKException: The page could not be loaded. Please review the errors and try again. ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.Collections.Generic.List`1.get_Item(Int32 index)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Common.MPHelper.GetDefaultManagementPack(ManagementGroup group)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)
--- End of inner exception stack trace ---
at Microsoft.EnterpriseManagement.ConsoleFramework.WizardFramework.AddPage(Page page)
at Microsoft.EnterpriseManagement.Internal.UI.Authoring.Extensibility.PageManagerBase.AttachToFramework(IPageFramework pageFramework, Boolean readOnly)
Microsoft.EnterpriseManagement.Internal.UI.Authoring.Extensibility.UISDKException: The page could not be loaded. Please review the errors and try again. ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Such error could be observed when "Default Management Pack" is missing from the Management Server where the "Add Monitoring Wizard" is being used to add a Cisco UCS Domain.
This Management Pack (Default Management Pack) is installed as a part of Operations Manager installation (Management Packs Installed with Operations Manager).
Please go to "Administration --> Management Packs" and verify if the "Default Management Pack" is missing. If yes, please import the "Default Managment Pack" and try to add Cisco UCS Domain again.
Thank you. While the Management Pack was not deleted it appeared to be corrupt or modified. You pointed me in the right direction and was able to resolve my issue. I did go ahead and actually delete it and then reimported it from media. That fixed my issue. Thanks again for the reply!
Is anyone else seeing a memory leak with this MP? As soon as I configure the run-as account (i.e. as soon as monitoring is initiated) I see the System Center Management Service Host Process consume about 3MB of memory per second. This contunies until the process crashes out (at about 15GB).
I am running SCOM 2012 R2 and the Management Pack is 2.6.2
I also am seeing this occur.
I just upgraded to Update Rollup 2 (7.1.10226.1015) for SCOM 2012 R2 and the issue persists.
I am having the same issue. I have verified that the SCOM action account and the Cisco action account both have full access to the local SCOM server, and that they have permissions to read/write from c:\windows\temp. I've run a trace debug on the SCOM side, but get nothing back but this same error. Does the product team have any guidance on this issue? What steps can I troubleshoot before the probeaction script gets to this point?
I'm running the 2.6.2. version of the MP.
Please try the following:
I identified the issue - the error was from a different management server than the one the Cisco UCS Manager service was installed on - I had assumed the workflow would run on the same management server. After updating permissions on the MS where the errors were generated from, this issue went away and discovery is proceeding as expected. Is there a way to specify which management server the UCS workflows run against?
In v2.6.2 of Management Pack, workflows are designed to get load balanced by the Management Servers, therefore you will find the workflows executing from other Management Servers as well (depending upon the load on the servers). But the connection to UCS Domain will be made from the Cisco UCS Management Service only, where the UCS Domain has been added.
Feature to target the Management Pack workflows to the same machine where the UCS Management Service (which monitors the UCS Domain) is running is being targeted in our future release...
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: