Version 103 of the Cisco: UC Ancillary PowerPack adds new Thresholds and Events to the "Cisco: CUBE Trunk Stats" Dynamic Application and a new device icon.
-
Minimum Required SL1 Version: 8.10.0
Before You Install or Upgrade
Ensure that you are running version 8.10.0 or later of SL1 before installing "Cisco: UC Ancillary" PowerPack version 103.
For details on upgrading SL1, see the relevant SL1 Platform Release Notes.
Installation or Upgrade Process
To install version 103 of the Cisco: UC Ancillary PowerPack, perform the following steps:
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.
If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.
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 8.10.0 or later release.
- Download the "Cisco: UC Ancillary" version 103PowerPack 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: UC Ancillary" version 103.
- Click the PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual. button. For details on installing
See the manual Monitoring Cisco Unified Communications Ancillary Devices for instructions on using the new PowerPack.
NOTE: If you are running a version of SL1 that is prior to the upcoming version 8.7.0, you must import and then compile the following MIB files in SL1, in the following order: CISCO-SESS-BORDER-CTRLR-CALL-STATS-MIB, then CISCO-SESS-BORDER-CTRLR-EVENT-MIB.
Features
This release includes the following features:
- An example credential you can use as a template to create SSH/Key credentials to connect to the devices you want to monitor
- Dynamic Applications to discover, model, and monitor performance metrics and/or collect configuration data for ancillary UC devices
- Device Classes for each of the ancillary UC devices that SL1 monitors
- Event Policies that are triggered when ancillary UC devices meet certain status criteria
- A device dashboard that displays host resource and interface information about ancillary UC devices
Enhancements and Issues Addressed
The following enhancements and addressed issues are included this release of the "Cisco: UC Ancillary" PowerPack:
- The following items were added to the "Cisco: CUBE Trunk Stats" Dynamic Application:
- Thresholds:
- "Incoming Calls on Dial Peer High"
- "Outgoing Calls on Dial Peer High"
- Events:
- "Cisco: CUBE Incoming Calls on Dial Peer Exceeded Threshold"
- "Cisco: CUBE Incoming Calls on Dial Peer Back to Normal"
- "Cisco: CUBE Outgoing Calls on Dial Peer Exceeded Threshold"
- "Cisco: CUBE Outgoing Calls on Dial Peer Back to Normal"
- A new SVG icon was added to the Device Classes in the PowerPack for the new user interface. NOTE: This update does not impact the classic SL1 user interface prior to SL1 version 10.1.0. SL1 version 10.1.0 will allow PowerPacks with SVG icons to be installed.
Known Issues
The following known issues affect version 103 of the Cisco: UC Ancillary PowerPack:
-
The PowerPack will not install on SL1 systems configured to be Federal Information Processing Standards (FIPS)-compliant until the new user interface available with SL1 version 8.12.0 and later supports FIPS systems.
- Some of the Dynamic Applications in the PowerPack will not work properly if a monitored router includes the word "Password" in its login banner, because the SSH library thinks the password was not accepted and the router is asking for the password again.