Version 114 of the "Cisco: CUCM Cisco Unified Communications Manager" PowerPack includes compatibility with Python 3 for all Dynamic Applications using snippet argument and specific run book actions.
- Minimum Required SL1 Version: 12.1.2
Before You Install or Upgrade
Ensure that you are running version 12.1.2 or later of SL1 before installing the "Cisco: CUCM Cisco Unified Communications Manager" PowerPack.
For details on upgrading SL1, see the relevant SL1 Platform Release Notes.
Installing the PowerPack
To install version 114 of the "Cisco: CUCM Cisco Unified Communications Manager" PowerPack, perform the following steps:
To install this PowerPack:
- Familiarize yourself with the Known Issues for this release.
- See the Before You Install or Upgrade section. If you have not done so already, upgrade your system to the 12.1.2 or later release.
- Download the "Cisco: CUCM Cisco Unified Communications Manager" version 114 PowerPack from the Support Site to a local computer.
- Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the menu and choose Import PowerPack. When prompted, import "Cisco: CUCM Cisco Unified Communications Manager" version 114.
- Click the button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
For more information about using the PowerPack, see the Monitoring Windows Systems with PowerShell manual.
Upgrading the PowerPack
By default, installing a new version of a PowerPack will overwrite all content in that PowerPack that has already been installed on the target system. You can use the Enable Selective PowerPack Field Protection setting in the Behavior Settings page (System > Settings > Behavior) to prevent the new version of the PowerPack from overwriting local changes for some commonly customized fields.
To upgrade from a previous version of the PowerPack, perform the following steps:
To install this PowerPack:
- Familiarize yourself with the Known Issues for this release.
- See the Before You Install or Upgrade section. If you have not done so already, upgrade your system to the 12.1.2 or later release.
- Download the "Cisco: CUCM Cisco Unified Communications Manager" version 114 PowerPack from the Support Site to a local computer.
- Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the menu and choose Import PowerPack. When prompted, import "Cisco: CUCM Cisco Unified Communications Manager" version 114.
- Click the button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
For more information about using the PowerPack, see the Monitoring Windows Systems with PowerShell manual.
Features
This release includes the following features:
- Dynamic Applications that discover and collect data from all CUCM devices and their children
- Events that address all actions and statuses on CUCM devices
- Device Classes for all types of CUCM devices
- Device Dashboards for all types of CUCM devices
- A sample Basic/Snippet credential for discovering CUCM devices
- A Run Book Action that assigns the CUCM Cluster root device to the "UC.Cluster" Device Class
Enhancements and Addressed Issues
The following enhancements and addressed issues are included in this release:
- All Dynamic Application using snippet arguments are now compatible with Python 3.
- Removed the "CUCM Credential Test" credential tester from this PowerPack.
- The following run book actions (RBA) are now compatible with Python 3 and will continue to function even after SL1 stops supporting Python 2:
- Cisco: CUCM Registration Event
- Cisco: CUCM Root Device Update
- Cisco: CUCM Subscriber Merge
Known Issues
The following known issues affect version 114 of the "Cisco: CUCM Cisco Unified Communications Manager" PowerPack:
- Support for making API calls to all CUCM nodes should improve issues previously experienced with the CUCM Tomcat service. If you still experience issues, perform the previous workarounds of restarting the Tomcat service on the CUCM Publisher, and disabling unneeded CUCM dynamic applications to reduce the number of incoming requests.
- If you attempt to discover a CUCM cluster whose servers have been cloned from a separate CUCM cluster that has also been discovered within the same SL1 stack, the "Cisco: CUCM Subscriber Merge" Dynamic Application may incorrectly attempt to merge subscriber devices with components in another DCM tree. To avoid this, you must manually merge the subscriber server devices with their associated component devices in the correct cluster.
NOTE: The physical device of the CUCM Publisher should not be merged with its associated component device.