What's New in this Version

This page outlines the new features and updates that have been included in this latest release of Prognosis. Further details can be found by clicking on the adjacent 'View' link.

Common

Prognosis Self-Monitoring

Enhancements to Prognosis’ self-monitoring capabilities which enables more timely and accurate detection of issues affecting relevant core services provided by Prognosis.

Key features:

  • New Thresholds and Analysts
  • High Availability health monitoring
  • Customer and Site visual filtering
View

Alert Suppression by Device

Prognosis 11.7 expands on the Alert Suppression feature in supporting the suppression of alerts for devices and their sub-components rather than just the customer or monitoring node name. 

Key features:

  • Scheduled maintenance windows for a device or sub-component
  • Leverage filtering expressions to create a finer suppression definition

Note: all Prognosis servers need to be version 11.7+ and licensed to take advantage of the Alert Suppression feature.

View

CI Mapping

Prognosis 11.7 enhances the CI Mapping feature to allow more control and seamless integration with third-party ITSM ticketing systems by providing the ability to leverage wildcards expressions to group alerts to mapped devices.

Key features:

  • Ability to map any alerts sent via RabbitMQ to third-party ITSM ticketing systems (i.e. ServiceNow)
  • Ability to use wildcards such as (*) & (?) to group alerts for mapped devices
  • Expanded support with the Alert Suppression feature
View

Prognosis Source Node for Alarms

Improvements to the Prognosis alerting systems ability to identify off-board monitored devices. The feature which can be turned on from within the ALERTS Configuration will populate the SOURCE NODE meta value with the device name instead of the Prognosis Monitoring server name which raised the alarm.

Note: all Prognosis servers need to be version 11.7+ to take advantage of this feature.

View

Prognosis for Infrastructure

Applications

VMWare 6.7

Support has been verified for monitoring VMWare 6.7.

Support is verified with a known issue with the VMWare cluster monitoring where the VMWare API does not return valid data causing the cluster level to report 0 and negative CPU usage. Please refer to known issues for further information. 

View

Prognosis for HPE NonStop

Support for IBM MQ 8.1

Support has been verified for monitoring of IBM MQ 8.1 on NonStop J-series and L-series in Prognosis 11.7. 

On installation of Prognosis 11.7, when licensed appropriately, any MQ version 8.1 installation will be detected and configured for monitoring. Some changes were made to this install time detection in 11.7, so for prior Prognosis versions, the collector may need to be manually configured. Please see the manual step instructions for more details. 

View

Support for the latest operating systems

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

  • HPE Integrity NonStop X L19.03
View

Support for the latest NonStop Server models

Support has been added for the NonStop X3 Server models in Prognosis 11.7


Support multiple MQ Instances

IBM has upgraded MQ to version 8.x and started recommending a new configuration to customers which prefers a more segregated configuration to what was recommended in previous versions. Support has been extended to be in line and monitor the new vendor recommendations around configuration.

Some very large customer environments comprise of multiple business units, as each business unit has their own data and processing needs they require their own "Queue Managers" in the MQ configuration (Note: Queue Managers are objects defined within the IBM MQ application). In order to manage the situation where high load from one business unit does not impact the performance of another business unit Queue Managers are configured with logical separation and are assigned resource limits. In previous releases of MQ, the administrator had the ability to define the CPU affinity for each Queue Manager. In the upgrade to MQ 8.x, this capability has been removed.

To achieve the required control over resources, MQ can be configured to run multiple “instances” of the MQ application on each server, and then define CPU affinity for each MQ application instance.

Previous versions of Prognosis are not able to monitor Multiple instances of MQ. The workaround is to install multiple Prognosis instances, each instance dedicated to monitoring individual MQ instances.

Given this workaround may be cumbersome for any configuration greater than a couple of instances, Prognosis 11.7 has been upgraded to support multiple MQ instances running on a single server. 

What’s New or Changed:

  • New syntax (MQINST) added to static conf
  • NSK segment file has a new function to discover the location of MQ installations
  • The startprg routine will not set =_RLD_LIB_PATH for MQ 80
  • Instance name and version added to MQQMGR record

Detailed architectural and deployment changes include:

  • One collector per MQ Queue Manager
  • The first collector has symbolic ID MQSCOL - executable is IRMQSCOL
  • Subsequent Queue Managers have ID MQMCOL##, where ## represents two digits; 01, 02, 03, … using image IRMQSCOL.
  • Every collector process binds with an IBM library, previously, MQ5.3 used Guardian DEFINE =_RLD_LIB_PATH to specify library sub-volume
  • This must not be defined for 11.7 monitoring MQ8.x, 11.7 monitoring MQ8.x obtains sub-volume from new syntax in Static Conf - if missing, it queries PRGNINI
  • Collector (irmqscol) binds to library offering function calls to retrieve required information from MQ
  • Collector owned by MQM group user with read permission on monitored MQ instances
  • Collector must be PROGID’ed
  • Prognosis User won’t have permission to execute processes for MQ
  • OSS environment to issue MQ Commands from installation path, binaries are located at opt/mqm/bin
  • Use dspmq –o all to query state of Queue Managers

Additional deployment considerations include:

  • Customer cannot mix MQ5.3 and MQ8.x instances
  • Multi-instance MQ not available with MQ5.3
  • Queue Manager names must be UNIQUE (case insensitive)
  • Queue Manager names are case sensitive in MQ, not in Prognosis
  • If customer issues “obey mqcstm” in same TACL before starting IRMQSCOL collector, could be problems based on =_RLD_LIB_PATH define
View

Prognosis for Payments

Support for ACI Postilion 5.6    

Support has been verified for monitoring of ACI Postilion 5.6 in Prognosis 11.7. 

Postilion 5.6 has been upgraded with the vendor recommending the use of SQL Server 2014, this change results in the SQL performance counters that Prognosis monitored previously to be no longer available. 

As a response to this change, the Prognosis for SQL Server Monitoring license bundle is now added to the Postilion license bundle. The newer version(s) of SQL contains additional performance counters which are available through the SQL Server monitoring bundle.

The SQL performance counters in Postilion dashboards have been replaced with the more robust and current Prognosis SQL Monitoring functionality. Customers using SQL performance counted via Postilion are advised to contact their IR relationship managers to request the new Postilion license bundle which includes the SQL Server Monitoring license.   

Apart from the monitoring of Postilion SQL Server noted above, application and platform worked without change from previously supported versions. 

View

Prognosis for Unified Communications

Avaya Aura

Avaya 8.1

Support for the latest version of the Avaya Aura Communication Manager, System Manager, Session Manager, Media Server, and Application Enablement Services.

View

Cisco Unified Communications

Cisco Unified SIP Proxy

Prognosis 11.7 has been enhanced to support the Cisco Unified SIP Proxy (CUSP) version 9 and 10, Prognosis offers a solution that will monitor the health of the Cisco Unified SIP Proxy including:

  • Alerts and Traps
  • Connections
  • Licenses
  • Peg Counting Log
  • Call Counts
  • Status

New Prognosis Records for Cisco Unified SIP Proxy:

  • CUSPALRT - This is used to capture alerts send by the CUSP system.

  • CUSPBCK  - This is used to capture the backup history from the CUSP system.
  • CUSPCALL - This is used to capture call statistics from the CUSP system.
  • CUSPCART - This is used to capture the Active Route Table from the CUSP system.
  • CUSPCMDS - This is used to capture the Command Status from the CUSP system.
  • CUSPCPU  - This is used to capture the CUSP CPU usage statistics.
  • CUSPMEM  - This is used to capture the CUSP memory statistics.
  • CUSPIFS  - This is used to capture the CUSP interface usage statistics.
  • CUSPFDST - This is used to capture the CUSP file descriptor statistics.
  • CUSPNTPA - This is used to capture the CUSP NTP associations.
  • CUSPQUST - This is used to capture the CUSP queue Status.
  • CUSPPROC - This is used to capture the CUSP process statistics.
  • CUSPSIST - This is used to capture the CUSP SIP status
  • CUSPSMLS - This is used to capture the CUSP Smart Licensing application and various license-related information
  • CUSPSNST - This is used to capture the CUSP SIP network status
  • CUSPSPCL - This is used to capture the CUSP SIP peg counting log
  • CUSPSSGR - This is used to capture the CUSP radius server group status.
  • CUSPSTAT - This is used to capture the CUSP CLI status.
  • CUSPSUMM - This is used to capture the CUSP CLI summary.
  • CUSPTCPC - This is used to capture the CUSP active TCP connections
  • CUSPTRAP - This provides detailed information about an SNMP v2c trap sent by a CUSP.
  • CUSPVERS - This is used to capture the CUSP software version.

Note: The Cisco Unified SIP Proxy solution is licensed under a new Prognosis license key.

View

Cisco IX 5x00 Video Endpoints

Prognosis 11.7 has been enhanced to support the Cisco IX 5x00 Video Endpoints, Prognosis offers a solution that will monitor the health of the 5x00 series endpoints including:

  • IX Alerts and Traps
  • IX call Connections
  • IX RX and TX data 
  • IX Status

New Prognosis Records for Cisco Telepresence:

  • CTPCALL This is used to capture Cisco IX 5X00 video Endpoint call statistics.
  • CTPCATYP - This is used to capture Cisco IX 5X00 video Endpoint call stream type information for a call.
  • CTPCASTR - This is used to capture Cisco IX 5X00 video Endpoint call stream source information for a call.

Note: The Cisco IX 5x00 video endpoint must be registered to a Cisco Unified Communications Manager.

View

Cisco Unified Computing System 3.x and 4.x

Prognosis 11.7 has been enhanced to support version 3.x through 4.x of the Cisco Unified Computing System through an enhancement to Integrated Management Controller login steps. 

View

Session Border Controllers

AudioCodes 7.x

Prognosis 11.7 support version 7.x of the Mediant Session Border Controllers, MediaPack, and Mediant series of the VoIP gateways.

Key features:

  • Simplified configuration
  • Support to receive Call Detailed Reports (CDR) through RADIUS 
  • Support to receive Syslog alarms
  • Expanded device metrics

Supported AudioCodes Mediant SBCs:

  • 500L
  • 500
  • 800
  • 1000
  • 2600
  • 4000
  • 9030
  • 9080
  • CE, VE and SE (Virtualized)

Supported AudioCodes Media Pack Analog Gateways:

  • 20x
  • 11x
  • 124
  • 1288

View

Oracle 39XX

Added support for the Oracle 39XX Session Border Controllers.

View

Prognosis for Contact Center

Cisco

Cisco UCCE 12.0

Prognosis 11.7 has been enhanced to support version 12.0 of the UCCE platform with the inclusion of monitoring the Cisco Visual Voice Browser.

Note: When upgrading or installing a new version of 11.7 and monitoring UCCE, a new Product license 'CUI' is needed.

View

Cisco UCCX 12.0 

Prognosis 11.7 has been enhanced to support version 12.0 of the UCCX platform with the inclusion of monitoring the Cisco Unified Intelligence Center.

Note: When upgrading or installing a new version of 11.7 and monitoring UCCX, a new Product license 'CUI' is needed.

View

Previous Releases

Provide feedback on this article