Table of Contents
Supported Cisco IMC Management Pack Versions
Cisco IMC Management Pack, Release 1.2.1
Cisco IMC Management Pack, Release 1.1.1
Cisco UCS C-Series Management Pack, Release 1.0.1
Upgrading the Management Pack to Release 1.2.1
Known Limitations and Deployment Suggestions
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco IMC Management Pack, Release 1.x
For Microsoft System Center 2012, 2012 SP1 and 2012 R2, Operations Manager
First Published: October, 2013
This document describes system requirements, key features, known issues, and workarounds for Cisco IMC Management Pack, Release 1.x for Microsoft System Center 2012, 2012 SP1 and 2012 R2, Operations Manager. This document also includes current information that became available after the technical documentation was published.
Use these release notes as a supplement with the other documents listed in the documentation roadmap http://www.cisco.com/go/unifiedcomputing/c-series-doc.
Make sure to review other available documentation on Cisco.com to obtain current information on Cisco IMC Management Pack, Release 1.x.
Revision History
Table 1 shows the revision history:
Introduction
Microsoft System Center Operations Manager (SCOM) is a cross-platform data center management server for operating systems and hypervisors. SCOM uses a single interface that shows information about the state, health, and performance of the Cisco Server components. It also provides alerts generated according to the availability, performance, configuration, or the identified security risks.
The Cisco IMC Management Pack is a definition file that contains predefined monitoring settings that enables an agent to monitor a specific service or an application in Operations Manager. These predefined settings allow Operations Manager to automatically detect and begin monitoring services and applications. It addition, the management pack also consists of a knowledge base that contains error and troubleshooting information, alerts, and reports to help you correct the problems detected in Cisco servers.
The management pack allows you visibility into the health, performance and availability of Cisco servers through a single, familiar, and easy-to- use-interface. This management pack allows you to group a set of servers and monitor them as a single entity. The IMC Group State View allows you to see the overall health state of all the groups that you monitor. The management pack contains rules that monitor servers.
System Requirements
This section describes the system requirements to install and configure the Cisco IMC Management Pack.
Operating System
Ensure that the 64-bit version of the following operating systems are installed with the latest service packs:
Key Features
This section briefly describes the key features introduced in Cisco IMC Management Pack. For detailed information about the features listed, see the documents listed in the Related Documentation section.
Cisco IMC Management Pack, Release 1.2.1
- Support for new faults in Cisco IMC releases 2.0(2) and 2.0(3)
- Supports cmdlets for the following operations:
Cisco IMC Management Pack, Release 1.1.1
This section includes the following key features in Release 1.1.1:
Cisco UCS C-Series Management Pack, Release 1.0.1
This section includes the following key features in Release 1.0.1:
- Support for registering multiple Cisco servers simultaneously.
- Support to discover Cisco servers by IP Addresses, IP Range, Combination of both IP Addresses and IP Ranges, and through Subnet Mask.
- Support to group Cisco servers and monitor them together.
- C-Series Group State View to see the overall health state of all the groups that are being monitored.
- Health monitoring, and alerts for each group as well as for each individual server.
- Support for launching Cisco IMC web interface for a server from the management pack.
- Support for launching KVM Console on a server from the management pack.
- Support for auto resolution of faults in System Center Operations Manager, when cleared/acknowledged by the Administrator from the server.
- Support for configuration of faults (Enable/Disable faults, Modify fault severity, and so on) using rules.
- Additional information and recommended actions to be taken for each fault available
- Support to generate alerts for server discovery failure and server fault collection failure.
- Support for monitoring of servers located behind a proxy server. However, the details of proxy server should be configured during discovery to use this feature.
Upgrading the Management Pack
Upgrading the Management Pack to Release 1.2.1
To upgrade Cisco UCS C-Series Management Pack Release 1.0.1 and 1.1.1 to the latest Management Pack, follow these steps:
Step 1 Run the installer of Cisco IMC Management Pack Release 1.2.1 on the Management Server where the previous release of the management pack was installed.
Step 2 When previous installation is detected, click Upgrade. Management pack will be upgraded to Cisco IMC Management Pack Release 1.2.1.
Step 3 Once the installation is complete, check the Update existing IMC instances check box and click Finish.
Step 4 Run the installer of the Cisco IMC Management Pack Release 1.2.1 on each management server where Cisco UCS C-series Management service or Cisco IMC Management service is installed to upgrade the management service to 1.2.1.
Note The Update existing IMC instances check box is checked by default. Upon completing installation, the PowerShell window is displayed where the existing IMC instances in the Cisco IMC Management Pack are updated.
Known Limitations and Deployment Suggestions
- For Release 1.1.1, the Cisco IMC Management Pack has been lab tested with one Cisco UCS Management Service to handle a load of monitoring ~1400 Servers.
- For Release 1.0.1, the Cisco UCS C-Series Management Pack has been lab tested with one Cisco UCS Management Service to handle a load of monitoring ~500 Servers
- For monitoring Cisco servers located in the Gateway Server domain, there should be connectivity from Management Servers to Cisco servers either directly or through a proxy server.
Open Caveats
This section lists the open caveats in Cisco IMC Management Pack, and contains the following topic:
Release 1.2.1
This section lists the open caveats for Release 1.2.1.
Symptom Assuming, the operating system is installed in C:\. While installing management pack, if -a option is used in the command, the binaries and other files are installed in the C:\.
Workaround Use -i option only to install the Management Pack. For example:
msiexec -i "Cisco.IMC.MP.Setup.v1.2.1-x64.msi" -l*v <logfilename>Symptom When installing IMC management pack version 1.2(1) on Windows Server 2012, it fails with the following error message:
Workaround Add installer user directly to a local administrators group, and not as a member of nested groups.
Release 1.1.1
This section lists the open caveats for Release 1.1.1.
Symptom Once the group of Cisco servers is added for monitoring, it might take ~ 6 hours for Cisco server to appear.
Workaround Either wait till the server appears in SCOM or override the object discovery “IMC Discovery” to run at a lower interval than the default 6 hours. Once the server is discovered in SCOM, thereafter normal monitoring of server continues with faults collected every 12 minutes.
Symptom For each of the following faults, two faults display in Cisco IMC:
Workaround None. (This issue is resolved in, Release 1.2.1.)
Symptom Multiple miscellaneous alerts might appear in SCOM when the Management Pack fails to connect the server during the fault collection cycle or inventory collection cycle.The failure can occur due to any of the following:
Workaround Verify all the faults (Ping Failure, Login Failure, Model Validation, Version Validation) are resolved. After the failures are resolved, the server faults from Cisco IMC appear in SCOM. (This issue is resolved in, Release 1.2.1.)
Related Documentation
For more information, you can access related documents from the following link:
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the “Related Documentation” section.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.