Release Notes - IR Prognosisgo.prognosis.com/rs/875-KCQ-600/images/prognosis11-0-release-notes.pdfRelease Notes Page 3 Introduction IR Prognosis provides precise performance monitoring

[Type here]

Release Notes Prognosis 11.0

Prognosis 11.0

Page 2

Copyright

Copyright 2000-2016 - Integrated Research Limited (ABN 76 003 588 449). All rights reserved.

This guide is protected by copyright law and international treaties. No part of this document may be reproduced in any form or distributed, and no derivative works such as translations may be made, without prior written permission from Integrated Research. Unauthorized reproduction or distribution of this document or the computer software, or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law.

Date of Issue: 28 June 2016 Product Version: Prognosis 11.0

Trademarks

Prognosis and IR are registered trademarks of Integrated Research Limited.

Other product names mentioned in this manual may be trademarks, registered trademarks and service marks of their respective owners and may not be used for commercial purposes without express permission from their respective owners.

Third Party Software License Notices

Please refer to the Third Party Software License Guide on the Prognosis installation CD or in the Documentation folder of the Prognosis Installation path for details of third party software license notices.

Disclaimer

The information in this guide is published as is and without warranties of any kind, expressed or implied, including those regarding the accuracy or completeness of the information, warranties of merchantability and fitness for a particular purpose, or those arising from a course of dealing, usage or trade practice.

In no event will Integrated Research be liable for any damages whatsoever (including, without limitation, those resulting from lost profits, lost data or business interruption) arising out of the use, inability to use, or the results of this guide.

Release Notes

Page 3

Introduction

IR Prognosis provides precise performance monitoring solutions for business-critical computing environments, including ATM/POS networks, Unified Communications environments, IT infrastructure and web applications.

Prognosis is based on a fault-tolerant, highly-distributed architecture, proven over the years to deliver real-time monitoring and alerting, deep drill-down diagnostics and trend-based historical reporting.

Prognosis users include the world's largest bank, telecommunications, stock exchange, computer hardware manufacturer, internet service provider and major companies in more than 50 countries.

This Release Notes document contains very important information that must be read carefully before attempting to install this new Prognosis version.

Please also read the Readme.txt file on the installation CD for any late-breaking information.

Prognosis 11.0

Page 4

Contents Release Notes .................................................................................................................................................... 1

Introduction ............................................................................................................................................... 3 Important Information ................................................................................................................................ 5 Upgrade Information ................................................................................................................................. 6 New and Changed Features ..................................................................................................................... 8

Common ........................................................................................................................................ 8 Prognosis for Infrastructure ........................................................................................................... 9 Prognosis for Payments .............................................................................................................. 10 Prognosis for Unified Communications ........................................................................................ 11 Prognosis for Contact Center ...................................................................................................... 16 Prognosis Reporting .................................................................................................................... 17

Deprecated Features and Platforms ....................................................................................................... 18 Common ...................................................................................................................................... 18 Prognosis for Infrastructure ......................................................................................................... 18 Prognosis for Payments .............................................................................................................. 18 Prognosis for Unified Communications ........................................................................................ 19

Issues Resolved ..................................................................................................................................... 20 Common ...................................................................................................................................... 20 Prognosis for Infrastructure ......................................................................................................... 21 Prognosis for Payments .............................................................................................................. 22 Prognosis for Unified Communications ........................................................................................ 24 Prognosis for Contact Center ...................................................................................................... 27 Prognosis Reporting .................................................................................................................... 28

Limitations .............................................................................................................................................. 29 Common ...................................................................................................................................... 29 Prognosis for Infrastructure ......................................................................................................... 33 Prognosis for Payments .............................................................................................................. 34 Prognosis for Unified Communications ........................................................................................ 35 Prognosis for Contact Center ...................................................................................................... 41

Known Issues ......................................................................................................................................... 42 Common ...................................................................................................................................... 42 Prognosis for Infrastructure ......................................................................................................... 42 Prognosis for Unified Communications ........................................................................................ 42

Release Notes

Page 5

Important Information The following information consists of last minute updates and details that may affect the Prognosis installation. Please read these details carefully before proceeding.

Possible Prognosis 10.x Failure

If multiple versions of Prognosis 10.x (i.e. a mix of 10.0, 10.1, 10.1.5 or 10.2 servers) are being run in the same environment, the servers at the lower levels of the Prognosis hierarchy may stop running when data is requested from records that are part of a Prognosis ‘Consulting’ solution, or records that were introduced after Prognosis 10.0.

This issue has been rectified in Prognosis 10.3 onwards. A fix for this issue has also been made available in Patch 04 for Prognosis 10.1.5 and Patch 01 for Prognosis 10.2.

If earlier Prognosis versions are being run, it is strongly recommended that they are upgraded to 10.3 or 10.4.

Prognosis 11.0

Page 6

Upgrade Information This section contains valuable information related to upgrading an existing Prognosis installation to the latest version. These notes should be reviewed before proceeding with the upgrade.

10.x Upgrade

Prognosis will be shut down for the upgrade. Therefore, users who are using the Prognosis Web Application will be logged out during this time. Users will need to re-login to the Web Application after completion of the upgrade.

Automatic upgrades

Prognosis 11 only upgrades from the following earlier Prognosis versions:

Prognosis 9.1 service pack 4

Prognosis IP Telephony Manager 9.6.1 update 7

Prognosis 10.0 service pack 1

Prognosis 10.1

Prognosis 10.1.5 patch 4

Prognosis 10.2 patch 1




For Skype for Business, Prognosis 11 only upgrades from the following earlier Prognosis versions:



Skype for Business uses an additional database in Prognosis 11, which is Prognosis MongoDB, on the top level Managing Node to store calls and conference sessions. Customers who would like to see their historical calls and conference sessions information from before the upgrade are required to migrate their data to Prognosis MongoDB. A utility has been created to assist customers with this activity.

Upgrade from Prognosis UC Reporter version 10.x is not entirely automatic. After running the Prognosis upgrade process, an extra step is required to execute the setup UC Reporter command.

In addition, the installation directory cannot be preserved if it is under ‘Program Files’ or ‘Program Files (x86)’. The default directory on the upgrade is ‘Prognosis’ directly under the original drive. The default directory for UC Reporter is ‘Prognosis\Reporter’ under the original drive.

Important Upgrade Notes

There have been important changes to the way that Prognosis handles encryption for passwords and server-to-server communication in Prognosis 11.0. Please refer to the Prognosis 11 Migration Guide, when planning an upgrade to Prognosis 11.0.

Custom dashboards that are created using both .dpy and .dashboard files with 10.4 or earlier may not work after upgrade to 11.0. Extra META.INTERVAL information is needed to handle time zones on Displays and will most likely need to be adjusted and redeployed to the web after the upgrade.

Upgrading to Prognosis 11.0 from an earlier version of Prognosis may fail when databases are running with a name of more than 24 characters. These databases need to be stopped before attempting the upgrade.

Release Notes

Page 7

Upgrading to Prognosis 11.0 from an earlier version of Prognosis may fail due to the lack of necessary permissions. The resolution is to run or execute the Prognosis 11.0 msi with the “Run as administrator” option.

Some folders may be left behind after upgrading from Prognosis IP Telephony Manager 9.6.1. These folders can be removed manually.

In a HP NonStop environment, when upgrading the management server to Prognosis 11.0, the FORCE-LEGACY-CONNECTIONS () setting will need to be removed from the NETWORK configuration on any NonStop servers running Prognosis 10.x, in order to manage them from Prognosis 11.0.

Prognosis 11.0

Page 8

New and Changed Features

Common

Auditing of Prognosis Functions

Prior to Prognosis 11.0, Prognosis had the ability to record details of various operations that had been performed in a text file. The operations included successful and unsuccessful logins from the Prognosis Windows Client and the starting or stopping of Analysts, Thresholds, Databases and Configurations, etc. In Prognosis 11.0, instead of simply writing this Prognosis audit information to a text file, it is now possible to send this audit information out via Syslog. The Prognosis audit information can be formatted as a Syslog message and transmitted via UDP or TCP (optionally using TLS) to an external Syslog server.

FIPS 140-2 Security Compliance

FIPS 140-2 is a statement that is titled "Security Requirements for Cryptographic Modules." It specifies which encryption algorithms and which hashing algorithms can be used and how encryption keys are to be generated and managed.

Prognosis 11.0 is FIPS 140-2 compliant through the use of a FIPS 140-2 certified algorithm. This new feature can be enabled through the Prognosis NETWORK Configuration. For details see the Prognosis Online Help system in the How Prognosis Works > Security > FIPS Encryption section.

Note, FIPS 140-2 is only supported through Prognosis 11.0+ servers.

Single Sign On

In Prognosis 11.0, support for SAML 2.0 Single Sign-On has been added to the Prognosis Web Application. Both ID provider and service provider initiated logins are supported in this release. Role-based security configuration within Prognosis will then refer to SAML users and groups when configuring access to Prognosis functionality.

When Single Sign-On is enabled in Prognosis, it will override any previously configured authentication mechanism. For example, Active Directory or LDAP.

New configuration parameters have been introduced for Single Sign On.

For more information, see the Prognosis Online Help in the How Prognosis Works > Security > Single Sign On section.

Support for Windows 10 in the Prognosis Windows Client

In Prognosis 11.0, the Prognosis Windows Client will now support MS Windows 10. This support also extends back to Prognosis 10.5, as no changes were required to support this version. Note MS Windows 10 is supported for Prognosis Windows Client only and not for any other server component in a production environment.

Release Notes

Page 9

Prognosis for Infrastructure

Distributed Systems (UNIX and Windows)

Support for Red Hat Enterprise Linux 7.2 and CentOS 7.2

Red Hat Enterprise Linux 7.2 and CentOS 7.2 (32 and 64 bit) are now supported for monitoring in Prognosis 11.0.

In Prognosis 10.5, there was a known issue regarding the monitoring of network interfaces in RHEL 7.x, this issue has now been fixed in Prognosis 11.0. See Fixed Issues section for more details.

Support for IBM DB2 10.1 and 10.5

IBM DB2 10.1 and 10.5 are now supported for monitoring in Prognosis 11.0.

Full Support for Oracle 12c Release 1

Oracle 12c Release 1 was first supported in Prognosis 10.5, only on Linux. In Prognosis 11.0, this is now also supported on Windows and Unix.

Support for vSphere 6.0

VMware vSphere 6.0 is now supported for monitoring in Prognosis 11.0. Support for vSphere 6.0 also extends back to Prognosis 10.5 as no changes were required to support this version.

HP NonStop

Support for the latest operating system versions

Support has been verified for the following operating system versions in Prognosis 11.0:

Integrity NonStop J06.20

Support for the latest server models

Support has been added for the following server models in Prognosis 11.0:

Integrity NonStop X – NS7 X1 (2 core) and NS7 X1 (6 core)

Integrity NonStop X – NS3 X1 (1 core) and NS3 X1 (2 core)

In previous Prognosis releases, a special ‘Unknown CPU’ type license key would be required to run Prognosis on these servers. In Prognosis 11.0, these systems are now recognized and supported by Prognosis, such that a special license key is no longer required.

Native Command Server and new Command Server Agent

As part of Prognosis 11.0, the Command Server (IRCMDSRV) has been converted to be natively compiled. As a result of this change, a new executable (IRTACL) has been introduced to act as an agent between IRCMDSRV and TACL. There should be no observable change to Command Server functionality, but a new IRTACL process will be started for each TACL session required by IRCMDSRV. IRTACL is a TNS executable and will be licensed as part of the installation procedure.

Other Natively Compiled Components

In Prognosis 11.0, additional TNS executables havew been converted to be natively compiled. This typically results in lower CPU usage and a smaller memory footprint for these processes. This change affects:

Pathway Collector (STPATH)

Standalone mail client (IRTMAIL)

Prognosis 11.0

Page 10

Prognosis for Payments

Multi-tenant MTS

In Prognosis 11.0, a single instance of Prognosis can now be used to monitor multiple MTS areas running on the same AIX logical partition. This allows support of multi-tenanted MTS environments, such as those hosted by ACI On Demand, as well as on-premises installs where multiple environments (Development, QA, Production) are hosted on the one server.

Access to data from each area can be protected using Prognosis Role-based Security to prevent unauthorized access. Prognosis users can also be presented with a dashboard for a specific area on login. As part of the change, navigation in the web application is now by MTS area, rather than by AIX server.

Note: the latest Prognosis 11.0 Management Server and AIX monitoring agent are not compatible with previous Prognosis versions. Both the Management Server and AIX monitoring agent need to be updated at the same time.

For more information, see the Prognosis Online Help, in the Prognosis For Payments > ACI Money Transfer System section.

Support for Split-mode IIS deployment in MTS

The MTS configuration dialogs now support Prognosis being installed in a split-mode deployment, where the Prognosis Web Application and the Prognosis Management Server are installed on separate machines. Previously, this setup required special procedures to configure MTS views and functions. The standard configuration screens can now be used in these deployments.

In deployments where the Prognosis Web Application and the Prognosis Management Server are on the same machine, this previously required a separate firewall rule that allowed the Management Server to connect to the MTS JASI port on the AIX server. In Prognosis 11.0, this is no longer required.

Note: Due to this change, remote credentials now need to be configured on the AIX server where the monitoring agent runs. These credentials represent an AIX user that can run shell commands on that server. Normally, this would be the user that Prognosis was installed as.

For more information, see the Prognosis Online Help, in the Prognosis For Payments > ACI Money Transfer System section.

Support for ATM Manager Reporting

Before Prognosis 11.0, ATM Manager Reporting was not set up and configured in the base install of Prognosis. A manual procedure was required to set up ATM Manager Reporting. In Prognosis 11.0, ATM Manager Reporting has been re-introduced to the base install. A script called enable_atm_reporting has been provided in the install to enable ATM Manager Reporting if required.

For more information, see the Prognosis Online Help, in the Prognosis For Payments > ATM Manager > ATM Manager Reporting section.

New fields for BASE24-eps Transactions

In Prognosis 11.0, the number of user fields available for BASE24-eps transactions has been increased from 10 to 20. In addition, the following fields will now be populated in the TransactionDetail record: MerchantCategoryCode, CardDataEntryMode, CardDataEntryCapability, CardHolderPresent.

Release Notes

Page 11

Prognosis for Unified Communications

Common

Generic Syslog via TCP and TLS

In the previous version, Prognosis could receive Syslog messages via UDP from a wide variety of devices across multiple platforms. This included computer management and security auditing as well as general information, analysis, and debugging messages. In Prognosis 11.0, Prognosis has been enhanced to also now receive Syslog messages via TCP and TLS.

Avaya

Better cipher support

Prognosis 11.0 has been enhanced to support stronger MAC algorithms and CBC block ciphers as part of the SSH connections which are used for gathering information from Avaya CS1000. The previous version of Prognosis may have had problems with SSH connections resulting in a key error.

Cisco Unified Communications

Support for Cisco Collaboration System release 11.5

Prognosis 11.0 has been tested against:

Cisco Unified Communications Manager 11.5

Cisco Unity Connection 11.5

Cisco Unified Presence 11.5

Cisco Emergency Responder 11.5

Support for CSR 11.5 also extends back to Prognosis 10.4, as no changes were required to support this version.

Support for Jabber Voice Quality

Prognosis 11.0 has been tested against a beta version of Cisco Jabber 11.7 which sends end of call performance and quality information to Cisco Unified Communications Manager, similar to Cisco IP desk phones. Cisco Unified Communications Manager uses these metrics to populate the Cisco Unified Communications Manager Call Management Record (CMR). With this extra information in the latest version of Jabber, Prognosis is now capable of monitoring and reporting on voice quality information for a call with Jabber.

Support for voice quality of call via CMR is available in all previous versions of Prognosis.

Cisco Unified Communications Manager Audit Log via Syslog

Prognosis 11.0 has been enhanced to record configuration changes made to the Cisco Unified Communications Manager system. The new CiscoAuditLog (CAUDITLG) record has been added.

This functionality relies on the Cisco Audit Event Service. This helps to monitor and log any configuration changes to the Cisco Unified Communications Manager system by a user or as a result of user action. These audit log messages are logged under the UC_AUDITLOG Cisco facility with different severity levels. Prognosis acts as a Remote Syslog server to receive this information.

It is necessary to Enable Audit Log and set up Cisco Unified Communications Manager to have the Prognosis Monitoring Server as the Remote Syslog Server. The Audit Event Level should be set to “Informational”. All these settings should be applied to all nodes in the CUCM cluster. Audit Log configuration can be found under the Cisco Unified Serviceability web page.

Prognosis 11.0

Page 12

In addition to the above, the Syslog DB will need to be started for Prognosis to start collecting the audit log information. Users upgrading from the previous version of Prognosis should stop and restart the Syslog DB to ensure that the new CiscoAuditLog record is included in the database collection.

Note there is currently a Cisco TAC case (https://tools.cisco.com/bugsearch/bug/CSCus02985) regarding being unable to export low-level audit log to remote Syslog servers for CUCM 7.1 – 10.5. Fixes have only been provided to 10.5 and above. Therefore, this feature is currently available only for CUCM 10.5 and above.

Enhanced SIP trunk monitoring under Cisco Unified Communications Manager 10 and above

With Cisco Unified Communications Manager version 10 and above, SIP trunk status is available through the web interface instead of just in Syslog. Prognosis 11.0 has been enhanced to gather this information.

The DeviceStatusEnumeratedValue (DEVSTATE) and DeviceStatusString (DEVSTATS) fields in the CallManagerApplianceTrunk (CMATRUNK) record will reflect the actual status of SIP trunk with option ping SIP profile.

The DestinationStatusEnumeratedValue (DSTSTATE) and DeviceStatusString (DstStatS) fields have been added in the CallManagerApplianceTrunkDestination (CMATDEST) record to reflect the status of each individual trunk destination.

This information is aggregated through to the Route Group, Route List and Route Pattern to help provide an understanding of the overall routing status.

While the SIP trunk down condition already exists for trunks, a new threshold condition has been added to warn about SIP trunk status being degraded. Also, the IP trunk report in UC Reporter will also show this new status information.

Note this status information is only available for SIP trunks associated with SIP profile that has option ping enabled. Also, the SIP trunk needs to be configured with Cisco Unified Communications Manager version 10 and above. Status information will stay as “unknown” for older versions or SIP trunks associated with SIP profiles without option ping.

Additional Dialled Number and Release Cause Code Search

New search for calls in the last hour with a particular Release Cause code, or a particular dialed or dialing number have been added to Prognosis 11.0.

It is now possible to type in either of the following into the global search box:

Cisco Number:<dialled Number> e.g. Cisco Number:990020, or

Cisco Release Cause:<release cause code> e.g. Cisco Release Cause:125

URL links will appears on on the search result page that, when clicked, will open a list of calls containing the specified dialed number or release cause code. The resulting display will provide a time slider that can be used to scroll to a time beyond the last hour to look for calls in another period.

Adding Cisco Unified Communication Manager cluster without automatic discovery via Web Application Interface

Prior to Prognosis 11.0, it was only possible to add a Cisco Unified Communication Manager through the Prognosis Web Application when the cluster was online and working. This was due to the fact that all servers within the cluster were automatically discovered and added as part of the overall configuration. The alternative was to add a cluster using the Windows Client when the cluster was offline and not contactable.

With Prognosis 11.0, you can now add a Cisco Unified Communication Manager and its associated subscriber even when they are offline by using the Web Application, instead of only being able to do it via the Windows Client.

https://tools.cisco.com/bugsearch/bug/CSCus02985

Release Notes

Page 13

Better cipher support for command line access to Cisco Unity Connection and Cisco Emergency Responder

Prognosis 11.0 has been enhanced to support stronger MAC algorithms and CBC block ciphers as part of the SSH connections used for gathering information from Cisco Emergency Responder and Cisco Unity Connection. The previous version of Prognosis may have had a problem with SSH connections resulting in a key error.

Microsoft Skype for Business

Conversations List – Completed Calls

Prognosis provides comprehensive data for peer to peer calls, offering a rich view from which to troubleshoot issues with the quality of experience. A replay slider control is used to allow Prognosis users to click or drag through a set of (e.g. 15 minutes) intervals to navigating to and finding the right page to locate the problem call. Furthermore, a series of drill downs can provide filtering; but these do not provide a simple or easy user experience.

To improve the user experience, the Skype for Business Call History page has had a complete overhaul, it is now renamed as the Conversation List page. The new interface provides functional, easy to use filters. The list of calls that pass the filter is now viewed in a paginated display that can be sorted to bring the right call straight to your attention without awkward slider controls.

Key information for each call is ‘bubbled’ up to give insights at a glance and provide a high-level view of calls.

Calls Details Improvements

Similarly, the call details page itself contains comprehensive and valuable data, but it is not presented in an intuitive and consumable fashion. Now, once you locate the call and drill down to it, the audio session details are laid out in a clear and intuitive manner. Rather than hovering over a specific icon or clicking on the right element to dive deeper into the data, the page now uses intuitive controls to expand or reduce information. Even more importantly, relevant and critical information is surfaced effectively with key messages at the top of the page and visual alarms to highlight key values.

Root Cause Analysis – Conference Call

Prognosis can now detect when a Conference Call fails due to AVMCU service being down or stopped. Prognosis will specifically indicate in the Conference Sessions Details Displays, that a particular conference session was terminated due to AVMCU service being down. This now allows Prognosis users to understand the root cause of this particular failure scenario.

Root Cause Analysis – Web Conferencing

Prognosis now detects when Web Conferencing functions, such as White Boarding and Power Point Presentation, fail due to the DataMCU service being down or stopped. Prognosis Web Conferencing Sessions Details display now highlight when a particular Web Conferencing/Presentation session was terminated due to the DataMCU service being down. This allows Prognosis users to identify the root cause of failed sessions in this scenario.

Root Cause Analysis – IM Conference

Prognosis can now detect when an IM Conference fails due to IMMCU or RTCIMMCU service being down or stopped. Prognosis shall specifically indicate in the Conference IM Sessions Details displays, that a particular IM session was terminated due to IMMCU or RTCIMMCU service being down. This shall allow Prognosis users to understand the root cause of this particular failure scenario.

Prognosis 11.0

Page 14

Root Cause Analysis – Client Sign-in failures – Front End Service Down and Registration Events

Prognosis now includes Front End service status information for each failure, as well as client deregistration and reregistration information whenever a client is disconnected due to server or network issue. The reasons for client deregistration and reregistration events are also provided.

This allows Prognosis users to identify easily the operational impact from Front End Services being down, network faults and other issues either preventing user registration or forcing a reregistration.

Client Sign-in failures – Incorrect credential

Prognosis can now inform Prognosis users when a Skype for Business users attempt to login to their Skype for Business environment with incorrect username and/or password.

Additional Key Health Indicator (KHI) Metrics and Alerts Improvements.

Prognosis now gathers additional KHI Metrics from the various Skype for Business Server Roles, including Front End, Mediation, and Edge Servers. Prognosis Alerts have been enhanced to include the new KHI metrics being captured.

Furthermore, Prognosis’ Skype for Business Alerts has been enhanced to provide additional clarity to Prognosis users. The area of improvements focused on providing better clarity as well as accurate conditions for Key Health Indicator (KHI) alerts messaging.

Additionally, a number of alert conditions have been added to provide clarity for Prognosis connectivity error via Windows Management Instrumentation (WMI) to Skype for Business servers.

Windows Event Displays

Prognosis users can now view Skype for Business Windows Event log displays for each Skype for Business site being monitored. This provides additional visibility into Skype for Business events that are occurring in their environment. Prognosis users can now identify events that may cause degradation in their Skype for Business environment performance, and can view historical Events their Skype for Business environments.

Calls by Subnet

A new Subnet dashboard has been provided so that there is visibility on the subnets used in the customer’s environment. This includes the percentage of worst calls information for each subnet. This way a user can quickly identify which of the subnets in their Skype for Business environment is having the most call quality degradation.

Wi-Fi/WLAN Signal Strength

Prognosis now provides wireless LAN (Wi-Fi) signal strength information for each finished Skype for Business call. This information helps Prognosis users troubleshoot or analyze scenarios with client sessions involving wireless connections, in particular, providing assistance determining if call quality degradation occurs due to weak Wi-Fi/WLAN signal strength.

Bandwidth Utilization

Prognosis now provides bandwidth utilization information for each finished Skype for Business call. This information helps Prognosis users troubleshoot or analyze scenarios with client sessions involving wireless connections, in particular, providing assistance determining if call quality degradation occurs due to bandwidth limitation.

The Web reports for Jitter, Packet Loss, and Latency

Prognosis web reports now include additional reports, for jitter, packet loss and latency (round trip). Prognosis users can view these overall performance metrics over the course of time.

Release Notes

Page 15

Immediate Data Delivery for Skype for Business displays

Prognosis users can view a complete set of data as soon as they open Skype for Business Displays. Previously, Prognosis users would need to wait for 30 seconds for the first set of data to be viewable, and longer for the full set of data to be populated on a graph. Now, Prognosis users can see the full set of data and graphs immediately as soon as a Display is open.

Search by user's phone number

Prognosis users can now search for an Enterprise Voice Skype for Business user with their phone or extension number. A number of Displays have been updated to show the phone numbers of the users where it is applicable.

Faster Conference Search

A new conference search database has been introduced to improve the speed of searching for a conference call. This is especially applicable in a large Skype for Business environment where there are a large number of conference calls being made on a regular basis.

Real-time Video metrics

Prognosis now can provide additional information in regard to video while the call is still active.

App Sharing Metrics

Prognosis now provides App Sharing session quality metrics. This information will be shown on a new App Sharing Session Details Display.

Historical Sessions Information

Prognosis users can now view the historical information for various Skype for Business sessions. This includes IM, App Sharing, File Transfer and App Invite information. The previously live Session Summary Display page has been converted to an historical view in order to allow Prognosis users to view this information.

Session Border Controller

Immediate Data Delivery for Live Skype for Business calls and AudioCodes Displays

Prognosis users can view a complete set of data as soon as they open Skype for Business Displays that contain live calls, as well as SBC Summary details for AudioCodes. Previously, Prognosis users would need to wait for 30 seconds for the first set of data to be viewable, and longer for the full set of data to be populated on a graph. Now, Prognosis users can see the full set of data and graphs immediately as soon as a Display is open.

Path Insight

New look Path Insight

In Prognosis 11.0, there is a completely new implementation of Path Insight available under the Prognosis Web Application. The old version which was available as part of the Prognosis Windows Client is no longer supported. Please contact IR Support for information about enabling this new version of Path Insight in your environment after a Prognosis 11 upgrade.

Prognosis 11.0

Page 16

Prognosis for Contact Center

Call Recording Assurance for Verint

Media Integrity

In Prognosis 11.0, a new feature called Media Integrity has been introduced. This feature can validate the physical existence of each media file and its' file size on the call recorders. Also, for a configurable percentage of media files, Prognosis can retrieve the sample and validate that the media does not only contain noise and that it is audio.

Configuration Assurance

In Prognosis 11.0, Configuration Assurance monitors for inconsistent configurations of the Contact Center agent/extension between the Avaya or Cisco voice platform and the call recording platform. Also, it automates the "white" and "blacklist" management which defines who should or should not be recorded.

Release Notes

Page 17

Prognosis Reporting

Unified Communications

The following reporting packages which span across five categories Fault & Availability, Inventory, Quality, Operations, and Capacity have been introduced.

Avaya & Contact Center (40+ Reports)

Cisco & Contact Center (40+ Reports)

Lync 2013 & Skype for Business (11+ Reports)

Prognosis 11.0

Page 18

Deprecated Features and Platforms

Common

Operating Systems

In Prognosis 11.0, support for the following operating systems has been removed from the listed Prognosis server roles:

Windows Server 2008 – from Management Server, Web Application, and off-board Monitoring Server roles.

Note that Windows Server 2008 R2 is still supported in these roles and Windows Server 2008 is still supported in the on-board Monitoring Server role.


Operating Systems

In Prognosis 11.0, monitoring of the following operating system versions is no longer supported:

HP-UX 11iv1

HP-UX 11iv2

Middleware

In Prognosis 11.0, monitoring of the following middleware versions is no longer supported:

IBM DB2 9.1

IBM VIOS 1.5

IBM VIOS 2.1

Java Virtual Machine 6

IBM WebSphere MQ 7.0


Payments Applications

In Prognosis 11.0, the following versions of Payments software are no longer supported:

ACI BASE24-eps 1.7

ACI XPNET 2.1

ACI XPNET 2.2

ACI Money Transfer System 3.x

ACI Postilion Office 4.0

Release Notes

Page 19


Cisco

In Prognosis 11.0, the following versions of Cisco software that are currently supported via running of Prognosis IP Telephony Manager 8.1.2 will be dropped. Please make the appropriate plans to migrate off these versions of Cisco software:

Cisco CallManager 3.x

Cisco Unified CallManager 4.x

Cisco Unity 4.x – 7.x

In the future Prognosis 12.0 release, it is planned that support for Cisco Unfiied Communications Manager 5.x and 6.x will also be deprecated.

Skype for Business – Prognosis Client

In Prognosis 11.0, monitoring or troubleshooting using the Prognosis Windows Client is no longer supported. The next Feature Pack update following the Prognosis 11.0 release will deprecate the ability for users to navigate through troubleshooting pages in the Prognosis Windows Client for Skype for Business monitoring. Therefore, users will now use the Prognosis Web Application when troubleshooting or monitoring a Skype for Business environment. Please make appropriate plans to cater for these changes.

Lync 2010

Prognosis 11.0 is the last version of Prognosis to support the Lync 2010 environment. This intention is in line with Microsoft’s direction, as Microsoft’s “Main Support End Date” for Lync 2010 is planned for December 2016. Customers who choose to remain on Lync 2010 will not be able to upgrade beyond the Prognosis 11.0 release to monitor their Lync 2010 environment.

ServiceNow Integration

In Prognosis 11.0, integration with ServiceNow has been dropped.

Path Insight

In Prognosis 11.0, the previous implementation of Path Insight, which was available in the Prognosis Windows Client, is no longer supported. Please contact IR Support for information about enabling a new version of Path Insight, which is available in the Prognosis Web application, in your environment after a Prognosis 11 upgrade.

Prognosis 11.0

Page 20

Issues Resolved The following items are issues that were raised, both internally and from customer feedback, from the previous Prognosis release that has now been resolved.

Common

Item No. Description

PRN11-18 Command destination 'Shell' not available received when executing a command. Need to restart ircmdsrv to recover.

PRN11-115 You can’t remove a user from a Prognosis role if they have already been removed from Active Directory or LDAP.

PRN11-377 Autosumm does not sync start/stop times to database interval when interval is 24 hours. This caused incorrect availability statistics to be shown in ATM reports.

PRNX-6492

SF-13757

Export to Excel via Web application will fail if it is a display with Web diagram.

PRNX-7127 The timezone in database replay slider changes per interval under the Web Application.

PRNX-7190 Some .svg files do not render properly in Prognosis Live Canvas dashboards.

PRNX-7193 LiveCanvas is missing option to specify collection interval

SEC-80 Updating Prognosis web server so that it is not prone to CSRF attack, and URL sniffing.

SF-12527 Spaces incorrectly interpreted in exported Excel files by Safari and FireFox, shown instead as '%20'

SF12630 SYSREDCY in SBCSUMM record from Acme packet 4500 series should be visible on the SBC welcome display. In addition, The SYSREDCY field is replicated to the dial peer record.

SF-12885 Not all lines appear on multi-line charts in the WebUI when using the associate key to separate data sets.

SF-12887 In a multi-level Prognosis node hierarchy, a monitoring prognosis NSK node is sometimes

not visible to the top managing node despite 'route-to' along the path.

SF-14014 Graphs in the WebUI show no data after moving into the daylight saving period.

SF-14382 Unable to expand Monitoring node in WebUI when on a separate domain.

SF-15852 Live Canvas drill downs attached to images do not work in Firefox

SF-15854 Live Canvas drill down unavailable for images in IE11

SF16364 Export to Excel function is missing for mashups

Release Notes

Page 21


Common


PRN11-135 Reports Central - wrong nodes showing up in Windows/Unix Server performance metrics

Microsoft Windows


PRN11-261

PRNX-7161

MSSQL Collector does not recover from a bad state after connection loss

Linux/Unix


SF-13248 enableprogboot script does not work on RedHat 7

SF-13585 JOBS.USER is not updated if a process' user ID changes after startup

HP NonStop


PRN11-2 Updated packaging not included in PKG folder on NonStop upgrade

PRN11-22 Received error 15 (invalid Prognosis where clause) when drilling down on process name

PRN11-48 NonStop Server Central - Application KPI window reports an error when a collector does not return data

PRN11-364 IRFAX on HP NonStop does not contain the ALERTS configuration

PRN11-633 Measure collector reports error 3203 on J06.20

SF-12600 STDC is crashing with arithmetic overflow trap error.

Prognosis 11.0

Page 22



PRN11-31 MTS Refresh Queues function does not work in a split Web UI and managing node setup

PRN11-33 Queue Filter in MTS config page very slow in IE9

PRN11-44 AIM Dashboard shows open tickets in bottom left window

PRN11-62 MTS configuration doesn’t work when using LDAP login

PRN11-64 Reports Central – No data available for some Postilion reports

PRN11-79 COMExceptions raised when running ATM reports

PRN11-81 Business Insight Transactions lookup tables do not support Postilion

PRN11-83 The where clause in the CheckDuplicateEvent rule in the AtmTicketingAnalyst was incorrect

PRN11-85

SF-12482

PostilionTerminalOverview (POSTTRMO) does not provide terminal information for more than 32,767 terminals

PRN11-86 MTS JASI error messages not handled correctly

PRN11-127 MTS data request intervals are not aligned to 10 seconds

PRN11-128

SF-13672

Response time calculations for BASE24-eps transactions are incorrect as it is double counting extrnl_issq_tim.

PRN11-140

SF-13613

The Card Acceptor Name Location TDE was incorrectly interpreted for some versions of BASE24-eps.

PRN11-262 Prognosis requests too many accounts from MTS

PRN11-380 The size of the ATM Incident Manager database on Windows is too small for some sites

PRN11-431 aimcheckstatus output mentions NonStop which can be misleading when used with other platforms

SF-0000 IST log reader does not correctly handle transaction amounts that end in 0 (after the decimal point).

SF-12477 Two Postilion dashboards do not work and generate 'Error: Chart Item2dduallineStacked is not supported.' error.

SF-12871 Remove reliance on chan_key index for BASE24-eps transaction log reader on Unix

SF-13035 User Defined fields for Transaction Detail and Summary records are empty or corrupt for BASE24-eps transactions on z-series.

SF-13221 Special log reader spawned by irtsvcol fails if prognosis install location has a space in the name.

Release Notes

Page 23


SF-13613 Postilion SQL-sourced timestamp fields do not contain a timezone offset.

SF-13806 PRM SQL query failing when Action Date Key is not a valid date

Prognosis 11.0

Page 24


Common


PRNX-7166 When you drill down to an SBC call leg from a VQ360 display, no data is shown

PRNX-7192 VQ360 page has an error when drilling down from AudioCodes call details.

SF-12736

SF-13338

SNMPv3 config is not applied on Prognosis startup

SF-13066 SBC Voice Quality Summary reports are wrong due to averaging of percentages

SF-13710 Foundation Edition - Prognosis analyst not sending emails when license usage is exceeded

SF-15309 Add AcmeDisconnectCause and AcmeCallType information to SBCCALL record.

Avaya


PRN11-422 Avaya Network Region description is truncated to 16 characters only

PRN11-424 Trunk Ports statistics under the System Capacity page is wrong

PRN11-426 Avaya firmware is not matching 9621 phones and ended up having wrong firmware under the compatibility matrix

PRN11-434 Avaya trunk type of "co" should not have carrier medium.

PRNX-7174 Avaya Firmware Compatibility display has been updated with firmware documentation according to December 14, 2015.

PRNX-7155 Error message in WebUI for missing prompt @SessMgrName, @MonitoringNode or @Filter after drill down from search results.

PRNX-7185 No data is shown on particular drill down to Avaya call details.

PRNX-7201 If you drill down to the SBC Call Details dashboard from a call in the SBC - VQ History dashboard, there is no data displayed.

SF-11627 Avaya Firmware Compatability Display is incorrect for Media Modules.

SF-11952 Avaya Aura Voice Quality report has inaccurate call counts.

SF-13009

SF-13242

Voice streams incorrectly tied to ESS

SF-13065 Avaya Aura System and Session Manager summary reports are wrong due to incorrect databases and records being used.

Release Notes

Page 25


SF-13206 Not all locations are showing up for Avaya CM 6.3 and later versions.

SF-13831 Avaya Trunk Group Utilization Monthly Reports wrong.

SF-13860 SIP phones are displaying as Type '164' instead of the correct version

number of E129

SF-14547 No status information from 6.x media gateways has been logged.

SF16201 Status for all announcement vector steps is always hardcoded to 4 'nonexistent announcement

Cisco


PRN-11 No CTI route point data as CTI route point solution for CUCM 10+

PRN11-87 Add a field PrognosisNode(PRGNNODE) in the CallManagerApplianceService (CMASRVCE) record to help map the IP address retrieved from Cisco as the CallManagerServerName field back to the corresponding Prognosis node names.

PRN11-356 ThreadCount (THRDCNT) field has been added to the CallManagerApplianceProcess (CMAPROC) record.

SF-13015 CmaVideoLocationBwNearMx condition of cmaLocationCAC threshold logs incorrect field value.

SF-13133 Support for overriding the Call Manager Gateway description field in Prognosis records

SF-13628 SBC Welcome display does not work for ASR type CUBE

SF-13705 Unable to add UCM monitoring to a monitoring node from the managing node WebUI.



PRN11-525 Two records (LyncMCUHealth and LYncMediationServerHealth) do not populate the customer field data.

SK-704 Global search keyword should use “Skype” rather than “Lync”.

SK-727 Search in a very large volume environment sometimes did not return data after considerable time has elapsed.

SK-721 In a very large volume environment, some calls or conference sessions may be missing.

SK-309 When no MOS has been provided in live calls, it is shown as “0” rather than empty

Prognosis 11.0

Page 26


SK-901 Skype for Business Server, not contactable alert message due to WMI failures is misleading.

SK-652 Skype for Business packet loss rate percentage is out by a factor of 100.

SK-894 Skype for Business video packet loss rate percentage is out by a factor of 100.

PRNX-5971 On Skype for Business Call Summary dashboard for live calls and conference, Federated calls are classified as Internal calls while the call is active rather than Inbound or Outbound calls.

SK-723 Searching for Skype for Business conference id can only be done in lower case.

SK-172 Sometimes going to VQ360 page from Skype for Business call displays shows no data.

PRN11-447 Prognosis REST API is not working in Prognosis 10.5.1 Feature Pack 11.

Release Notes

Page 27



PB11-24 Add threshold based on a VDN having processed more than X calls in the last Y minutes.

PRN11-415 No recordings are shown in Prognosis if the Verint recording system was upgraded from V9 or V10 to V11.X.

PRNX-7175 Avaya Aura Contact Center Agents display has been updated to have the consistent refresh interval.

PRNX-7184 CRA displays are not filtering alerts for a specific site.

SF-13373 VDN and Vectors do not appear on the AV-PBX display.

SF-13450 Avaya Aura Contact Centre WMI Status display fails with an error in the site panel

SF15249 AEP does not show in ACCSUM record

Prognosis 11.0

Page 28

Prognosis Reporting


PRNX-7170 Windows Non-Interactive login support for ODBC database collections

PRN11-105 Support for non-English platforms support

PRN11-382 Prognosis Reporting now works with the new FIPS 140-2 encryption

PB11-771 Indexing on the Source database can cause deadlocks

PB11-534 ETL to should continue process without errors so we do not suffer any data loss

PB11-431 Prognosis needs to start automatically monitoring the Microsoft SSIS server so that it can be alerted whenever the ETL fails

PB11-296 Dimension enhancement due to growing too quickly within the UCModel which will minimize future memory-related failures during an ETL

PB11-301 Data extraction during an ETL needs to be faster so that the ETL will perform faster

PRNX-1276 Tables may get locked for an extended period of time if ODBC Prognosis Database Collection gets an INSERT error for each interval

Release Notes

Page 29

Limitations Prognosis 11.0 has certain limitations in what it can do due to the method and technology it uses to collect information. The following limitations are known.

Common

Time Synchronisation

All Prognosis servers within the same deployment should be time synchronized. When times are not synchronized between servers within the Prognosis hierarchy, there may be cases where data is not automatically updated on the online displays in both the Windows Client and the Web Application.

Parallel Installation

Prognosis for UC Foundation Edition, including Prognosis VoIP Monitor, must be installed on its own server. No more than one Prognosis installation can be installed on the same server.

Uninstallation

The time remaining shown during an uninstallation of Prognosis can be inaccurate. The time reported is greater than the time actually required.

Unsupported features in the Web Application

When sending Displays to be used as part of the Web Application, there are certain features which are currently not supported. These include:

General

Windows Themes for different colors and fonts are not supported. The Prognosis Web Application has standard background and foreground colors as well as standard fonts.

Status and caption bars for individual windows within a Display are not supported.

Row numbers on the left of tables are not supported.

Cache Intervals in chart presentations are not supported.

Pop-up prompts are not supported.

Drill-downs and links to Database Collections, Database Summaries, Thresholds, Analysts, and Commands are disabled in the Web Application.

Reports are now set up under Report Central and drill-downs from Displays to reports are not supported.

Drill-downs and links to a Database Replay where there is a specific stop time, based on an interval, may not show the expected timing of the Web Application.

Options for clearing the workspace or leaving the workspace unchanged when drilling-down through links etc. are no longer supported. It is necessary to utilize the tab functionality supported on the browser. Only drill-downs from chart legends do not support “Open in new tab”.

The spacing between windows, as well as margins for displaying data inside a window, is different in the Web Application when compared to the Prognosis Windows Client. At times, it will be necessary to resize the windows in a Display to ensure that data remains visible in the Web Application.

Icon color setting, indicating if data is available, is no longer supported.

Sending multiple Displays to the web with the same name, under different directories, will end up having only the last one sent being available.

MIN/MAX are not supported in the Web Application. If a data field MIN/MAX option is selected for a Display, which is sent to the web, only the STD value will be rendered.

Prognosis 11.0

Page 30

Time modes other than ‘Server Time’ are not supported. Data will always be rendered based on server time.

Time Display modes including ‘Time and Mode’, ‘Time and Offset’ and ‘Time, Mode and Offset’ are no longer supported. Time will be rendered as ‘Time Only’ mode in the Wed Application.

Visual alarms on columns are not supported in the Web Application. Displays with visual alarms on columns are converted to have the visual alarm on the cell only.

Charting

Chart Trending is not supported.

Threshold line is not supported.

3D charts are not supported. They will be rendered as 2D charts only.

Stacked ‘Column-Line’ and ‘Line-Line’ charts are not supported.

Stacked line charts are not supported. They will be rendered as stacked area charts.

Line thickness is not supported. All line graphs are drawn with the same line thickness. Line charts with a thin line and a large number of intervals or a large number of lines in the Prognosis Windows Client might not be readable in the Web Application. In this case, please consider reducing the number of items plotted on the line graph.

Charts are always visible under the Web Application. Displays, where chart legends are enlarged to take up the space of the entire window to hide charts, will not be supported.

Chart legends are not resizable in the Web Application. Displays, where chart legends are resized to show limited data in the Prognosis Windows Client, will not display the same way under the Web Application.

Small sparkline style charts without legend and axis labels are not supported in the Web Application.

Spacing for time scales in charts is different between the Prognosis Windows Client and the Web Application. If an ‘Automatic Label’ is not selected, the time scale may be rendered with large overlaps, making the time scale unreadable. Change the time scale to use ‘Automatic Label’ and send to the web again, if necessary.

META Fields

Not all META fields are supported in the Web Application. Support for the following items has been removed, and Displays using these fields will need to be adjusted before they can be sent to the web.

META.CHARTSTARTTIME

META.CHARTENDTIME

META.INTERVALFORMATTED

META.STARTTIME

META.TOTALCOLUMN

META.USERNAME

META.SHORTFIELDNAME in a chart series condition is not supported. Series coloring may not be as expected in the Web Application.

EMPTY Fields

Checking if a field is EMPTY in a where clause via a prompt such as FIELD = #EmptyPrompt is not supported. It will be necessary to adjust the where clause in the dpy file to check for (FIELD = EMPTY AND #EmptyPrompt = EMPTY) explicitly.

Checking if a field is EMPTY in a where clause can be done with either FIELD = EMPTY or FIELD = “EMPTY” under the Prognosis Windows Client. However, only FIELD = EMPTY is supported under the Web Application. FIELD = “EMPTY” will be checking for the literal string “EMPTY” instead.

Release Notes

Page 31

Prompt Substitution

The Web Application is much stricter regarding field and prompt comparison; a prompt must be of the same type as the field. Therefore, a prompt with a value of ‘All’ cannot be used for comparison with an integer field, such as a port number.

Prompts that are not explicitly specified in a drill-down may not be available in the Web Application as part of the URL. If prompts are missing from the URL, it will be necessary to ensure that the prompts are explicitly specified in a drill-down in the display file for IRGUI. Sometimes this will require adding extra user defined fields in order to store temporarily promptly so that they can be passed between multi-level drill-downs.

When a field with the Display option ELAPSED TIME is used as a prompt in the Web Application, it will only be passed as a string in the time format with colons instead of the number of seconds. Therefore, the ELAPSED TIME prompt may not work as expected in the Web Application.

When a field with the Display option TIMESTAMP is used as a prompt in the Web Application, it will only be passed as a string in ISO 8601 format instead of the Prognosis Windows Client format. Therefore, the TIMESTAMP prompt may not work as expected in the Web Application.

Advance packaging where prompts are used to specify field and record names is not supported.

Advance packaging where prompts are used to substitute an entire where clause is not supported.

Web Application

Data shown in the Web Application will be displayed according to the time zone settings of the monitoring server where the information is gathered. In the case where a display contains data from multiple monitoring servers, data will be default to display using UTC. When additional data are being collected from more nodes in the different time zone for a display, data might first be shown under a specific time zone and then flip to show data in UTC.

Default time zone setting is set to UTC to display data from multiple monitoring servers. This is a fixed time offset which is not related to regional time settings and it does not automatically adjust for daylight saving changes.

‘Mashups’ are available for online Displays and reports, but are not available from database replays.

Drill-downs via legends in charts does not support “Open in new tab” browser option.

Change in column width is not retained if the Display is closed or refreshed.

There is no left/right axis indicator show for dual axis charts in the Web Application.

‘Send-to-web’ function is available for displays and database replays, however, for reports further work is needed to be done using the web report function under Prognosis administration before the report can be used and populate with data.

A lot of database processes will be created when starting a replay for HP NonStop data via the Web Application, and it is slow to return data.

Opening a large number of dashboards in quick succession soon after IIS restart, while Prognosis is running, can lead irpqlsrv to consume extra unnecessary memory. Irpqlsrv may terminate itself and restart within a few hours.

The position of an item in the Web Application navigation tree is not preserved if ‘open new tab’ or ‘open in new window’ is used.

Using the back button on the browser will not keep the replay database position on the Web Application.

Administration of Thresholds and Databases via the Web Application may not take into account any specified ‘Node to Run On’.

Bookmarking a URL for the Web Application using IE9 may not work.

Navigation for the Web Application cannot be updated by multiple users simultaneously.

Prognosis 11.0

Page 32

SNMP Traps

Each device that sends SNMP Traps to Prognosis is required to be monitored on a separate Prognosis Monitoring Server. These include the following monitored environments:

Generic SNMP ‘traps in’

Avaya CS1000

Alcatel

Avaya Contact Centre

Avaya IP Office

Prognosis Server Connection

The Prognosis Server Connection may not work when a class C address of x.x.x.255 is used while there is another class B address set up with the right subnet mask.

Windows Client

Commands cannot be started if the user is logged into the Windows Client with a username that starts with “\”.

The tile horizontally and tile vertically options in the Windows Client do not work correctly when the edit mode is turned off.

Memory size settings

The SET MEM-SIZE statement in the PROGNOSIS Configuration can only be set with an executable name instead of symbolic process id.

Adding monitoring across nodes via Web application

When adding systems to be monitored via the web application on a node with an older version of Prognosis, sometimes the system might fail to add or the database/threshold might fail to start as the old system does not necessary support the new feature.

Release Notes

Page 33


Microsoft Windows Operating system description for Windows Servers may not be accurate. When a range of servers is managed, the Welcome To Prognosis Platform Systems Management page is showing all servers as Windows Server 2012 with a different version number, which can be wrong.

HP NonStop Shell commands from Dashboards are not yet supported by the Prognosis Web Application.

Custom Databases, Analysts, and Thresholds are not restarted after an HP NonStop upgrade

Prognosis 11.0

Page 34


ATM Incident Manager

Issuing ATM commands from the Web Application

The Prognosis Web Application can be used to view ATM and ticket status and to open, comment on and change the state of tickets. Currently, however, the ability to manually issue commands to ATMs is limited to ATMs hosted in ACI Postilion. To manually issue commands to ATMs hosted in other applications from Prognosis, it is recommended to use the Windows Client.

Reporting

ATM Manager Reporting is not set up and configured in the base install of Prognosis. To continue receiving ATM availability and service time reports in a 11.x environment, a manual procedure is available to set up ATM Manager Reporting.

PRM

Upgrading from versions prior to version 10.2

When performing a phased upgrade from a Prognosis version prior to version 10.2, PRM data from any older nodes will not be fully visible in the new PRM dashboards released in version 10.2. The dashboards were reorganized in 10.2 around records only introduced in this version. To continue receiving full visibility of the older nodes, it is recommended to retain an older managing server, or use the dashboards distributed with that older version of the newer managing server and Windows client, until the monitoring server can be upgraded to 10.2 or above.

Release Notes

Page 35


Common

Prognosis for Unified Communications does not support the changing of a Prognosis server name by altering parameters in the prgnini file. Although this function may work for other Prognosis products.

Removing a UC monitoring item may not always remove it from the middle panel on the Web Application Administration page.

Data is displayed and collected using the time zone of the Monitoring Server; it is recommended to set the time zone of the Prognosis Monitoring servers to match the time zone of the equipment being monitored and also run related thresholds for that equipment on the same Monitoring servers.

Alcatel-Lucent OmniPCX Enterprise Communication Server

VoIP tickets retrieved from Alcatel-Lucent OmniPCX Enterprise Communication server can sometimes contain values for packets lost that are higher than packets sent/received. In this case, Prognosis will set the packets lost value to unknown and will not supply an MOS value for that VoIP ticket.

Route Pattern (i.e. Dial Plan) is not supported.

Camel-Case Alcatel PBX name causes irAlcatel_PBX.exe high CPU usage and many log errors. Please ensure the PBX name is always entered in upper case.

All devices (phones, PSTN trunks, IP trunks) will have the PBX as their location. Therefore, there will be no sub-tree under the PBX in the network element tree for configuring reporting groups under Reporter.

Calls from Alcatel-Lucent OmniPCX Enterprise Communication server are all treated as successfully completed calls due to CDR tickets not having disconnect cause codes to indicate a reason for disconnection. When used with Reporter:

- Call Failure, Call Failure ratio, Calls Rejected and Grade of Service will always be zero.

- Calls Attempted and Calls Completed will always report the same value.

- Call Failure report and Disconnect Cause Code section in the summary report will contain no data.

- IP Trunks and PSTN trunks are not further classified into subtypes.

Avaya Aura Communications

Prognosis is marking voice stream where Avaya Media Server is involved as “Unknown”. Currently, the IP address of Avaya Media Server is a match and the voice stream associated will be displayed as part of the media server details page, but the voice stream will be marked as type unknown.

Avaya ESS mode activation cannot be monitored. In addition, the Avaya_Alert threshold will pick up all the resources that are not being controlled by the ESS as down.

Unable to monitor server status in an S87xx pair.

Aura Configuration XML files (SIPEntities.XML and EntityLinks.XML) do not get removed. That is:

- When removing System Manager or Session Manager from Prognosis, the SipEntities.XML and EntityLinks.XML remain behind.

- When re-adding a System Manager or Session Manager, the user can upload a new SipEntities.XML and EntityLinks.XML files and it will replace the existing XML files.

- When importing System Manager Configuration to Web Administration, the web form will contain error messages until the XML files are uploaded using Web Administration display.

Prognosis 11.0

Page 36

- When Upgrading from earlier version of Prognosis 10, the SipEntities.XML and EntityLinks.XML files are preserved in under <Prognosis_Home>/Server/Configuration/IPTM/Avaya. However, the Web Administration does not import them into the model, so the Configuration page on the Web Administration shows the red warning: “System Manager Configuration incomplete, please upload SIP Entity and SIP Entity link XML files”.

- Uploading incorrect XML files may remove existing Session Managers from Prognosis Configuration.

Avaya Communication Server 1000

Voice Quality

Only data for degraded voice streams is available. Voice quality data is only present as streams, not Erlangs.

Entities not supported

There is no data presented for:

Route Patterns,

Call Failure Ratios,

Disconnect Cause Codes

Calls Rejected

Incorrect port in the configuration setup

When an incorrect CS1000 PBX port has been set up using the Web Administration page or Windows Client, modifying the port through either interface may not fix the issue. If this occurs, it is recommended to restart the irNORTEL_PBX.exe by:

- Going to the Windows Client,

- Open the PROGNOSIS Configuration document

- Enter the value SET RUN (irNORTEL.exe N), and click start

- Change the value to SET RUN (irNORTEL.exe, Y), and click start.

The collector now should be requesting data using the new port.

Cisco Unified Communications

Upgrade from Cisco Unified Communications 9 to Cisco Collaboration System Release 10

When Cisco Unified Communications Manager and Cisco Unified Presence Server are upgraded from version 9 to10 or 11, the two clusters configured in Prognosis will have to be removed and then re-added as one.

Searching Cisco MGCP gateway interface

A new field ‘ProtocolEnum’ has been added to the CallManagerDevSum (CMGWDEVS) record in Prognosis 10 to distinguish MGCP, SCCP and H323 interfaces. This field is not available in any previous versions of Prognosis, such as IP Telephony Manager version 9.6.1. Therefore, a search of gateway devices will always return the ‘Other’ link which points to the ‘Gateway Details’ instead of the ‘Call Last Hour’ if the gateway is being monitored by IP Telephony Manager version 9.6.1.

Release Notes

Page 37

Instant data on new web application

Instant data in the new Web Application is supported for the top level screens of Cisco Unified Communications Manager (CUCM), Cisco Unity Connection (CUC), Cisco Unified Presence (CUP), Cisco Unified Contact Center Express (UCCX), Cisco Unified Border Element (CUBE), Cisco Unified Computing System (UCS) B and C-series with the following exceptions:

All Displays for Cisco Call Manager version 3.x and 4.x

All Displays for Cisco Unity

CMA – All Clusters Central

CMA – All Server Central

CMA – TelePresence Central

CUC – Cluster Overview

CUC – Ports

CUC – Server Sessions

CUP – SIP Proxy Statistics

Cisco UBE Details

UCS C-Series System Central

Syslog Messages by Cluster

Gateways/Trunks

CPU, memory, DSP resources and environmental statistics are only available on for H323 and SCCP gateways where the associated MIBs are supported, and Prognosis has SNMP connectivity directly to the gateway.

H.323 and Voice Gateways that do not support the IF-MIB (i.e. the IfTable SNMP table) will not have accurate status information and the status of the gateway will default to ‘Down’. If accurate information is required, it will be necessary to enable the IF-MIB.

H.323 gateways that stop responding to SNMP requests will be displayed in Prognosis with the last retrieved status for each interface. In addition, if there has never been a response from SNMP, no count or device details regarding the type of interface available on the H.323 gateway will be provided.

A Voice Gateway (VG) configured as part of a CUCM 5+ cluster that does not respond to SNMP requests will report the correct number of configured devices on the Gateway Central page, but no devices will be listed when drilling-down to the Gateway Details page. The Gateway Details page lists devices that only contain data retrieved via SNMP requests from the Voice Gateway.

No performance data is provided by CUCM 5+ for any MGCP gateway configured on a CUCM 5+ cluster that has never been registered to any CUCM server since the servers started up. The detailed device information will not be available due to lack of performance data from the CUCM servers.

Status of non-gatekeeper controlled inter-cluster trunk or SIP trunk without SIP profile with option ping will be set to ‘Unknown’. Route patterns with all destinations set to these types of the trunk will be ‘Unknown’. Status of route patterns which include other types of destinations will be based only on the destinations with known status.

For physical gateways that have multiple interfaces where some interfaces are H323 while others might be MGCP and SCCP, the logical H323 gateways will show all interfaces on the physical gateway including those which might be actually running another protocol. In addition, Prognosis will only support physical gateways using multiple protocols when the logical gateways entries under the Cisco Unified Communication Manager Configuration Database have different names.

Prognosis 11.0

Page 38

Calls and Voice Quality

Voice quality data for calls rely on Cisco Call Management Records (CMRs), also referred to as Call Detailed Diagnostics Records (CDDRs), being available from the devices involved in a call. However, some devices such as H.323 gateways and SIP trunks do not provide CMRs on the CUCM. Voice quality for a call will be available as long as one of the devices involved in the call provides CMRs. Calls involving only devices with no CMRs will not have voice quality data provided by Prognosis.

CUCM 5+ calls will be put into the ’Unknown’ call category if they involve devices currently not being reported individually by Prognosis such as conference bridges.

The ‘Call by Category’ windows in the Cisco Calls Display and the ‘Voice Quality Distribution’ graph in the Cisco Voice Quality Display for CUCM 5+ plots the CDRs processed by Prognosis per interval. If Prognosis

is set up to use SOAP requests rather than the Billing Application Server for CDR retrieval, there will be a time overhead in the delivery of the CDRs to Prognosis. This is due to the CUCM server having to respond to individual SOAP requests. Occasionally the CUCM server can take longer than one-time interval to reply to a SOAP request resulting in a delay in the processing of CDRs from one interval into the next. Therefore, the Displays may occasionally have an interval showing no data followed by another interval which has twice the normal amount of data. To prevent this from occurring, it is recommended that a Billing Application Server is selected for CDR retrieval. This eliminates unnecessary SOAP requests/responses between the CUCM server and the Prognosis monitoring server.

Any files present in the CDR directory will be processed on Prognosis startup. If there are a large number of files in this directory, it may result in spikes in the Calls and Voice Quality records. This is particularly important when the Billing Application Server mechanism is used, and there has been extended downtime for the Prognosis service.

Phones and extensions

Currently, Prognosis will only be able to obtain CallManagerIpPhoneInformation (RTDEVINF) configuration information and CallManagerIpPhoneQos (RTDEVQOS) real-time call quality information for the various 69xx, 79xx, 89xx, and 99xx series IP phones. This information is obtained through the IP phone web pages including

http://<phone ip address>/DeviceInformationX,

http://<phone ip address>/PortInformationX

http://<phone ip address>/StreamingStatisticsX

Hence population of fields in these two records is only available for IP phones which support and have the web page function enabled. These records are not supported for softphones such as IP communicator or Cisco Jabber.

No SNMP data is provided by CUCM 5+ for phones configured on a CUCM 5+ cluster that has never been registered to any CUCM server since the servers started up. The status of these phones will remain ‘Unknown’ due to lack of SNMP data from the CUCM servers.

Prognosis currently only refreshes the device extension mapping once a day, the dynamics introduced by Extension Mobility will affect the CallManagerApplianceExtensions (CMAEXTN) and CallManagerDeviceExtension (CMDEVEXT) records where extension details are missing or the associated device listed against the extension is not the most up to date. The CallManagerDevice (CMDEV) record will also be affected where the LineInUse (LNSINUSE) field is representing activities on an extension that is no longer associated with the particular device. Calls information as given in Calls Details and Call Details Diagnostic Records will still accurately reflect the device and the extension number used during the call at the time.

Release Notes

Page 39

Cisco Alerts

Cisco Alerts data will only be available when Prognosis can contact and retrieve data from the publisher. There will be no Cisco alerts update when the publisher is down.

Cisco Unified Communication Server version 5.x does not put alerts into subcategories. Therefore, the group field in the Cisco Alerts record will be empty.

Cisco Alerts with descriptions longer than 508 characters will not be displayed in full.

Cisco Call Manager version 3.x and 4.x

Prognosis cannot monitor Microsoft Skype for Business and Cisco Call Manager version 3.x and 4.x from the same Monitoring Server.

Cisco Call Manager version 5+

After adding a new CUCM version 5+ system, it may not show up in the Web Application navigation tree until the browser is refreshed.

Cisco Unified Border Element

Change of CLI user password to be used as part of monitoring for Cisco Unified Border Element won’t be picked up unless the collector is restarted.


MOS values are provided directly by Microsoft and are not calculated using the standard Prognosis MOS formula.

There is no data presented for PSTN trunks and Route Patterns.

There is no active call information in Microsoft Lync 2013 monitoring as the data is no longer available in the Monitoring SQL Server.

There is no Network Hop information available in Microsoft Lync 2010. Therefore, network hop information will not be populated on the Skype for Business Call Details and Skype for Business Conference Session Details dashboards for calls made in Lync 2010 environment.

Prognosis cannot monitor Microsoft Skype for Business and Cisco Call Manager version 3.x and 4.x from the same Monitoring Server.

Prognosis 11 utilizes a new database, MongoDB, to store Skype for Business calls and conference information. For customers who deploy multiple monitoring and managing servers, MongoDB is required to be deployed at the top managing node. Further enhancements to allow the flexibility to store MongoDB on a lower Monitoring node level shall begin immediately following Prognosis 11 release.

Prognosis 11.0

Page 40

Prognosis UC Reporter

Calls

Some call records received by Prognosis UC Reporter may have missing device names if the names are not contained in the original CDR flat files received from the Cisco Cluster. These calls will not be accounted for in the report if the call count is based on the device involved.

Show charts as tables

On the Report Creation Wizard dialog box an option to ‘Show charts as tables’ is provided. This is used to show chart data in table format so that it can be used for further processing by other applications. However, when this option is selected there is a limitation with charts that include ‘Busy hour’ times.

UC Reporter shows time data in charts by converting it into an equivalent decimal number between 0 and 24. For example, if the ‘Busy hour’ time is 12:10 it will be converted to 12.16666 then rounded to 12.17. In the same way, a ‘Busy hour’ time of 12:30 will be converted to 12.5.

When printing the tabular format of these charts, UC Reporter can only use these decimal values instead of being able to provide the “Busy hour’ in the hour:minute format. Bear in mind that this is a decimal value and not an actual time. A ‘Busy hour’ time of 12.17, does not mean 12:17 but actually means 12:10.

Remote SQL requires SQL authentication

Prognosis UC Reporter requires SQL authentication; MS Windows authentication is not supported.

Release Notes

Page 41


Verint and NICE monitoring

Prognosis cannot monitor both the Verint and NICE call recording systems from the same Management Server.

Prognosis 11.0

Page 42

Known Issues The following issues are known at the time of product release and, where available; workarounds have been provided.

Common


PRNX-2966 Prognosis 10 cannot show double byte characters.

PRNX-4769 Deleting a Prognosis SQL database that resides on a remote SQL Server can receive “Failed to connect to the server” errors.

PRNX-5748 Web Snapshots are not deleted after the aging option time has elapsed

PRNX-6009 Upgrading to Prognosis 10.4 from an earlier version of Prognosis may fail when there is database running with a name more than 24 characters. These databases need to be stopped before attempting the upgrade.

PRN11-767 Prognosis upgrades on servers that do not have the Prognosis Windows Client (IRGUI) installed will fail, showing error messages regarding upgrading Prognosis Prompts.



PRNX-4 The OracleColumnOptimizer (ORACBOCO ) record does not populate under the Web Application.

PRNX-2567 NT service details incorrectly show running services as not running on Windows Server 2012.



PRN11-257 Drill down from Avaya Voice Stream to SBC of type other than Oracle/Acme packet 4500 does not work as it is not going to the various display of the correct type

PRN11-595 Skype for Business requires entering the full conference ID when searching for a conference in Conversation List page, as a partial search on conference ID for doesn’t return results.

PRN11-740 Cisco Audit Log display under the Web Application shows no data because it defaults to 24 hours in the future instead of 24 hours in the past. Users need to use the database replay control to rewind back for data

PRN11-762 Voice Quality 360 sometimes does not show the full path when a call made between Skype for Business and Cisco UBE with media-by-pass turn on.

Release Notes

Page 43


PRNX-4140 Voice Quality 360 might not be able to link up to other calls from Avaya where both voice streams between a board and IP Phones are available.

PRNX-7212 Some Skype for Business alerts appear in Alerts Central but not on Skype for Business Open Alert Central.

SK-1002 As a result of Prognosis 11 security enhancements, Prognosis Skype for Business survey feature has been turned off.

Documents

Release Notes - IR Prognosisgo.prognosis.com/rs/875-KCQ-600/images/prognosis11-0-release-notes.pdfRelease Notes Page 3 Introduction IR Prognosis provides precise performance monitoring