The release notes cover the following topics:

• About VMware Telco Cloud Operations
• What's New in this Release
• Known Issues
• Resolved Issues

About VMware Telco Cloud Operations

VMware Telco Cloud Operations is a real-time automated service assurance solution designed to bridge the gap between the virtual and physical worlds. It provides holistic monitoring and network management across all layers for rapid insights, lowers costs, and improved customer experience. Powered by Machine Learning (ML) capabilities, VMware Telco Cloud Operations automatically establishes dynamic performance baselines, identifies anomalies, and alerts operators when abnormal behavior is detected.

VMware Telco Cloud Operations simplifies the approach to data extraction, enrichment, and analysis of network data across multi-vendor environments into actionable notifications and alerts to manage the growing business needs of Telco in an SDN environment.

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

What's New in this Release

The VMware Telco Cloud Operations v1.0.1 introduces the following enhancements:

• User Interface Enhancements:

  • SDWAN Connectivity map type created for VGateway.

  • SDWAN Connectivity map type created for VEdge

• VeloCloud v4.0 Support:

  • VeloCloud 4.0.0 is supported. All functionalities used in earlier versions are supported in the VeloCloud 4.0.0 version.

• MnR 7.0 Support:

  • MnR Core version is upgraded to 7.0. All features used in version 6.8u5 are supported in 7.0.

• Deployment Enhancements:

  • Two installation modes available: UI based or automated using deploy-tool.

Note: Before installing version 1.0.1 of VMware Telco Cloud Operations you must install version 1.0 (version 1.0.1 is a patch to version 1.0).

For information about system requirements, hardware requirements, patch installation, and sizing guidelines, see the VMware Telco Cloud Operations Deployment Guide.

Resolved Issues

• SD-WAN report for Jitter (Tx v/s Rx) panel may not render correctly due to issues in the report query. ​

  To populate the reports correctly, add a space in the query condition.

• When you select VeloCloud Orchestrator or Velocloud Tenant in the topology map, IPMultiMediaSubSystem Connectivity Map or SDN Physical Connectivity map appear by default. 

Known Issues

• A possible cause for the deployment to fail is when you use the automated deployment tool.

  When you deploy VMware Telco Cloud Operations using the automated deployment tool, the deployment of the worker node may fail with the error: Failed to send data.

  Workaround: Modify the VCENTER_IP configuration parameter in the deploy.settings file to use the fully qualified domain name (FQDN). For more information about modifying the deploy.settings file, see the VMware Telco Cloud Operations Deployment Guide.

• VMware Telco Cloud Operations v1.0 does not support integration to SAM server that has the CAS authentication setup for EDAA API.

  Workaround: Install a new SAM on a different path and start a new EDAA instance (Tomcat server) on a different port (port 1), without CAS authentication. The new EDAA instance points to the same SAM presentation server that the MnR integrates with using EDAA on a default port with CAS authentication.

  VMware Telco Cloud Operations connects to SAM-PRES using EDAA:port-1 without CAS authentication and MnR connects to the same SAM-PRES using EDAA:portdefault with CAS authentication.

  Note:
  You must modify the following lines in the server.xml file of the new SAM installation, to point to the new server ports.

  a. Server port="9005" shutdown="SHUTDOWN"
  b. Connector port="8090" protocol="HTTP/1.1"

  And, to start the Tomcat server, run the command ./sm_tomcat --output &

• When the number of hops of connectivity is increased, you may experience performance issues in the topology maps.

  There might be performance issues in the rendering of  Redundancy Group, MPLS, Metro-E, and SDN connectivity map types in the Map Explorer view. This issue is observed on deployments with a complex topology where the topology maps may stop working when the number of hops of connectivity is increased.

• When you create a Metrics Collector with incorrect inputs for Smart Assurance, it indicates that the collector is running, even though the connection is not established.

  When you provide an incorrect input during collector configuration, the collector appears to have started but it does not start. Verify the log to check the actual collector status.

• VMware Telco Cloud Operations v1.0 does not support the SAM server with broker authentication, Edge Kafka authentication, and Smarts EDAA authentication. However, it exposes database ports for debugging purpose.

  For a workaround, see the Security Recommendation section in the VMware Telco Cloud Operations Deployment Guide.

• The Containment, Browse detail, Notification Acknowledge/Unacknowledge does not work when the primary Tomcat server fails in a Smart Assurance HA environment.

  In a Smart Assurance Failover deployment, when the primary Tomcat fails, the UI operations including the Notification Acknowledgement, Containment, Browse Detail, and Domain Managers fail.

  Workaround: When the primary Tomcat instance fails in a Smart Assurance failover environment, then you can manually point the VMware Telco Cloud Operations to a secondary Tomcat instance and restart the collectors.
  Procedure:

  1. Go to https://IPaddress of the Control Plane Node:1081.
  2. Navigate to SAM Config.
  3. Edit the EDAA value, to point to the secondary SAM.
  4. Update the Configs.
  5. Restart smarts-event-data-smarts-sam and smarts-topology-data-smarts-sam collectors in the VMware Telco Cloud Operations UI > Administration > Data Collectors.
• Broker failover is not supported in VMware Telco Cloud Operations v1.0.

  Primary Broker fails in the Smart Assurance failover environment.

  Workaround: Currently when a Broker (multi-broker) failover happens in Smart Assurance, then it requires a manual intervention where you need to log in to VMware Telco Cloud Operations and change the Broker IP address to point to the new Broker IP.
  Procedure:

  1. Go to https://IPaddress of the Control Plane Node:1081.
  2. Navigate to SAM Config.
  3. Edit the Broker value, to point to the new Active Broker.
  4. Update the Configs.
  5. Restart smarts-event-data-smarts-sam and smarts-topology-data-smarts-sam collectors in the VMware Telco Cloud Operations UI > Administration > Data Collectors.
• The deployment will fail when a node uses an IPv6 address rather than an IPv4 address.

  An error message appears when a deployment fails.

• The progress bar appears unchanged during the VMware Telco Cloud Operations installation or uninstallation.

  The progress bar appears unchanged when a user deploys a patch installation/uninstallation or applies a patch.

  In some cases during both patch installation and uninstallation the patch progress bar is not updating dynamically. In such scenarios, refresh the web page to get the updated status of the patch deployment

• Any notifications in VMware Telco Cloud Operations have the serial number column with one empty row under the Audit Log tab.

  In an Elasticsearch database, a zero value is not saved and displays an empty row.

• The time stamp displayed for the Notifications in the Notification Log View and in the Notification Browse > Details are different.

  The time stamp displayed for the Notifications  (for example: Last Notify, Last Clear, etc) are different in the Notification Log View when compared to the displayed in the Notification > Browse Detail > Details windows.

• The timestamps for LastNotify and LastClear do not update for Notifications generated before the patch deployment.​

  If there are any Notifications which are generated before the patch deployment, unless there is a change in a Notification, the Last Notify and Last Clear values are not getting updated.

  For any new Notifications that are generated post patch deployment these values will be populated. This is applicable only for patch deployment.

  Note: This issue is applicable only for 1.0.1 patch upgrade and not applicable for 1.0.1 OVA based deployment.