Release Notes for Cisco UCS Management Pack, Release 3.x for Microsoft System Center 2012, 2012 SP1 and 2012 R2 Operations Manager

Management and Gateway Servers

System requirement for Management Server and Gateway Server are as per the Microsoft recommendations mentioned in the following page:

http://technet.microsoft.com/en-us/library/hh205990.aspx

Operations Manager Windows Agents

System requirement for Windows agents (trusted or untrusted boundary) running Cisco UCS Management Service is as follows:

Hardware

• Processor Architecture: 64-bit with Quad-core or higher
• Memory: 8 GB or higher

Operating System

UCS management service must be installed only on the Windows Agents running 64-bit versions of the following operating systems:

• Windows Server 2008 R2
• Windows Server 2008 R2 SP1
• Windows Server 2012
• Windows Server 2012 R2

Note All the above operating systems must be installed with the latest patch updates.

Software

The following software components must be installed before installing UCS management service on Windows agents:

• Windows PowerShell 2.0 or higher
• .NET Framework 4 or higher

Release 3.1(2) adds support for the following:

• Added power state change notification for blade and rack servers
• Enhanced PowerShell Cmdlets to support Cisco UCS domains in a single management pack
• Support to create Run As Account with more secure distribution policy while adding a new UCS domain instance
• Added Product Knowledge for UCS Manager login failure alert
• Added Occur field (Number of Occurrences of UCS fault) in alert description

Release 3.1(1) adds support for the following:

• Supports UCS Mini.
• PowerShell cmdlets for adding or updating UCS instances in Operations Manager.
• PowerShell cmdlets for managing discoveries and monitors.
• Supports Proxy server.
• Encrypted proxy password.
• Support to upgrade existing UCS instances after upgrading the management pack.
• Increase in the organization hierarchy discovery from root level to level 3.

Release 3.0(2) adds support for the following:

Supports no new features as this is a bug fix release.

Release 3.0(1) adds support for the following:

• One monitor per UCS Domain fault.
• Knowledge articles in monitors containing the details of the faults and recommended action.
• Supports installation of Cisco UCS Management Service on Management Servers, Windows Agents (trusted or un-trusted domain boundary) and Gateway Servers.
• Event based discovery for on-demand execution of object discovery.
• Support for real time UCS monitoring
• Dedicated Service Machine for UCS Domain Monitoring.
• KVM Console launch on a Service Profile, Blade Server, or Rack Unit.
• Run-As Account association in the Add Monitoring Wizard simplifies the overall process to start monitoring a UCS Domain.
• More secure account distribution.
• Tech Support utility facilitates collecting logs for diagnosing an issue.

Resolved caveats in Release 3.1(2)

CSCut47645

Description: When you add a UCS domain from the Add Monitoring wizard on a new installation of Cisco UCS Manager management pack or when you upgrade to version 3.1.1, the following error occurs:

“Processing the template failed. See inner exception for details.

Cannot resolve identifier SCLibrary!Microsoft.SystemCenter.RootManagementServer in the context of management pack <mpname>. Unknown alias: SCLibrary”

First affected version: Release 3.1(1)

• CSCur13912

Description: The Cisco UCS Manager management pack version 3.0(1) fails to install on Windows Server 2012. The following error is displayed.

You must have administrator privileges to install Cisco UCS Management Pack (v3.0)

First affected version: Release 3.0(1)

• CSCur59737

Description: SCOM management pack is unable to handle flapping fault conditions correctly.

First affected version: Release 3.0(1)

Resolved caveats in Release 3.1(1)

• CSCur41719

Description : Add a UCS domain using Add Monitoring wizard. The Test Connection shows a success message. But an authentication failure event appears in Management Pack Events after you add the UCS Domain for monitoring in the Cisco UCS Manager management pack.

First affected version : Release 3.0(1)

Resolved caveats in Release 3.0(2)

• CSCuq85468

Description : When you try to install the package as an administrator, the following error message is displayed:

You must have administrator privileges to install Cisco UCS Management Pack (v3.0).

First affected version : Release 3.0(1)

• CSCuq80741

Description : When you select the Machine Type as an Agent Managed Computer (Trusted Boundary) or Agent Managed Computer (un-trusted Boundary) on the General Information page of the Add Monitoring wizard, it takes a long time to populate the Service Machine drop down menu, and until then the dialog box remains unresponsive.

First affected version : Release 3.0(1)

• CSCuq96134

Description : Faults F1007, F1008, F1009 & F1010 do not appear in the operations console even when available in Cisco UCS Manager.

First affected version : Release 3.0(1)

Open Caveats in Release 3.1(1)

• CSCus07678

Symptom : Faults F0209 & F1236 appear on the Cisco UCS Manager GUI, but do not appear on Operations Manager Console.

Conditions : This symptom is observed for all instances of Fault F0209 & F1236 which appear in the Cisco UCS Manager.

Workaround : None.

• CSCur96136

Symptom : Not all organizations in UCS Manager are shown on Operations Console.

Conditions : This issue is seen when there are multiple organizations with the same name. For instance, organizations with name ‘test’ are at different levels in the organization hierarchy or organizations with name ‘test’ and ‘Test’ are in the same level.

Workaround : Ensure that Organization names in Cisco UCS Manager are unique.

Open Caveats in Release 3.0(1)

• CSCup61422

Symptom : Health Service of the Operations Manager Windows Agent restarts periodically when managing UCS domain.

Conditions : This issue occurs when the user uses the MP as is, where the monitors related to all the critical and major faults are enabled by default, to monitor a UCS domain comprising more than 40 servers.

Workaround : We recommend that the users come up with a list of faults that they want to monitor and take action on, through the Operations Manager, and enable only the corresponding object discoveries and monitors.

The users also need to increase the private bytes threshold to a higher value till the Health Service restarts stop.

To see the list of important faults to be monitored, read the UCS Monitoring Handbook available at the following URL: https://communities.cisco.com/docs/DOC-37197

If you choose to enable only monitors related to these faults then the private bytes threshold must be set to 400MB to avoid Health Service restarts.

An alternate workaround for this issue could be to use the management server itself for monitoring the UCS domain.

• CSCuq24178

Symptom : When the user tries to acknowledge more than five UCS faults, only these five faults get acknowledged. The remaining faults stay in the ‘UCS Acknowledged’ state.

Conditions : This occurs when the default number of command processes executed in response to the alert notification is set to 5.

Workaround : Acknowledge the faults in a batch of five, or modify the registry to increase the limit as mentioned in the following URL: http://blogs.technet.com/b/cliveeastwood/archive/2008/04/16/some-more-command-notification-tricks-and-tips.aspx.

• CSCuq78612

Symptom : Periodic events with ID 4508 appear in the Operation Manager event log.This event appears due to the missing assembly module Microsoft.Mom.DatabaseQueryModules, which is required by the workflow: Cisco.Ucsm.<uuid>.ServiceProfileReferenceBlade.Discover. This workflow discovers the association between the service profile and the Physical Blade/Rack Unit in the UCS domain, and a dotted line is visible on the diagram view between the related service profile and the Physical Blade/Rack Unit.

Conditions : This error occurs only on UCS domains monitored by the Cisco UCS Management Service installed on the gateway server and Agent Managed Computer (trusted and un-trusted domain boundary). The error is not displayed on UCS domains monitored from the management server.

Workaround : Disable the discovery of the reference relationship (Cisco.Ucsm.<uuid>.ServiceProfileReferenceBlade.Discover).

However, due to this action, the relationship between the associated service profile and blade/rack unit (dotted link in the Diagram View) is not visible for UCS instances for which the reference relationship is disabled.

Complete the following steps to disable the reference relationship of UCS Instance for which the error is visible in Operations Manager:

Step 1 Open Operations Manager Shell on a Management Server.

Step 2 Use the following commands for every UCS individually:

a. $ucsManagementPack = Get- -DisplayName "<UCS_Instance_Name>"

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

c. Disable-SCOMDiscovery -Discovery $referenceDiscovery -ManagementPack $ucsManagementPack

• CSCuq77915

Symptom : Management Pack binaries and other files are installed under C:\cisco (on the assumption that the Operating System is installed on C:\).

Conditions: This symptom occurs when the -a option is used in the command to install the Management Pack as shown below:

msiexec -a "Cisco.Ucsm.MP.2012.v3.0.1-x64.msi" -l*v <logfilename>

Workaround : Using -a option is not supported; use only the -i option to install the Management Pack as shown below:

msiexec -i "Cisco.Ucsm.MP.2012.v3.0.1-x64.msi" -l*v <logfilename>

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Release Notes for Cisco UCS Management Pack, Release 3.x
© 2015 Cisco Systems, Inc. All rights reserved.