This site will be decommissioned on December 31st 2024. After that date content will be available at techdocs.broadcom.com.

VMware Telco Cloud Service Assurance 2.3.0 | 09 JAN 2024

Check for additions and updates to these release notes.

About VMware Telco Cloud Service Assurance

VMware Telco Cloud Service Assurance is a real-time automated service assurance solution designed to holistically monitor and manage complex virtual and physical infrastructure and services end to end, from mobile core to the RAN to the edge. From a single pane of glass, VMware Telco Cloud Service Assurance provides cross‑domain, multi‑layer, automated assurance in a multi‑vendor and multi‑cloud environment. It provides operational intelligence to reduce complexity, perform rapid root cause analysis and see how problems impact services and customers across all layers lowering costs and improved customer experience.

For information about setting up and using VMware Telco Cloud Service Assurance, see the VMware Telco Cloud Service Assurance Documentation.

Contents of the VMware Telco Cloud Service Assurance 2.3.0.2 Patch

The VMware Telco Cloud Service Assurance 2.3.0.2 patch contains the following binary:

  • VMware Telco Cloud Service Assurance patch binary.

VMware Telco Cloud Service Assurance Patch Deployment

For VMware Telco Cloud Service Assurance Patch deployment, see Deployment of Patch in the VMware Telco Cloud Service Assurance Deployment Guide.

Fixed Issues

  • Post upgrade to 2.3, intermittent OpenSearch exception observed in VMware Telco Cloud Service Assurance UI.

    Intermittently on the VMware Telco Cloud Service Assurance UI OpenSearch exception [type=search_phase_execution_exception, reason=all shards failed] appears, post VMware Telco Cloud Service Assurance upgrade .

    This has been fixed by deleting and recreating index for task in the ElasticSearch DB.

  • Enrichment jobs are not running in dark site environment

    In the dark site environment, online XML schema validation is failing.

    The issue has been resolved by enabling the schema validation through locally available xsd files which are generated by the sprint application during the dependency resolution.

check-circle-line exclamation-circle-line close-line
Scroll to top icon