• If you upload any reference data csv file for any of the events, topology or metrics enrichment streams, before the upgrade then you must re-upload the reference file post upgrade. After this, you must stop and start the Topology and Events Collector from the Administration > Configuration > Collectors and Connectors > Smarts Integrations Details section of the Smarts Integration Broker.
  • Post upgrade once all the VMware Telco Cloud Service Assurance applications are recconciled succesfully, Stop and Start the Topology Collector from the Administration > Configuration > Collectors and Connectors > Smarts Integrations Details section of the Smarts Integration Broker.
  • Post upgrade, anomaly definitions are in disabled state. You can right click and select Edit option and click Next. Click Next in the subsequent pages. In the last page, click Save.Anomaly deifinition gets enabled.
  • Post upgrade, if there are any custom dashboards reports in Grafana for which the reports are not generated, then below additional steps needs to be followed:
    1. Launch VMware Telco Cloud Service Assurance.
    2. Navigate to Dashboard and Reports.
    3. Select the desired custom report. Click Share dashboard or Panel.
    4. Click Export.
    5. Click Save to file, and ensure that JSON file is downloaded.
    6. Open the JSON file, and modify the Datasource value of the Panel for which the report is not getting generated as follows:
      The following code snippet needs to be modified from: 
      "panels": [
    {
      "datasource": {
        "type": "prometheus",
        "uid": "Xgab12KIk"
      },
      to 
      "panels": [
    {
      "datasource": <DataSource-Name>,
...
...
      Note: The DataSource-Name is the datasource used for the respective Panels in the given custom dashboard.
    7. For importing the JSON file, mouse hover on the Dashboard icon in the left pane and select Import.
    8. Click Upload JSON file and upload the modified JSON file from your machine.
    9. To verify, go to custom dashboard section, where report must be populated with the custom data.
  • For NCM Reports, if the subnets are added in the NCM server-side configuration, then no changes are required. Otherwise, add the modified Grafana and ncm-proxy Node IPs in the NCM server-side configuration. For more information, see the NCM Server-Side Configuration topic.
  • After upgrading or migrating VMware Telco Cloud Service Assurance from older version to VMware Telco Cloud Service Assurance 2.4, the custom catalog metrics that you have created in the older version will not be available in VMware Telco Cloud Service Assurance 2.4 due to the vsa_catalog schema changes. You can create the customized catalog metrics again in the VMware Telco Cloud Service Assurance 2.4 Catalog UI.
Note: There will not be any default enrichment definitions shown in the VMware Telco Cloud Service Assurance UI after upgrading to 2.4. If any customizations are done to default enrichment definitions in the previous releases, only in this case, after the upgrade the default enrichment definitions names are changed as given in the following list.
  • metric-stream will be changed to metric-definition
  • event-stream will be changed to event-definition
  • topo-stream will be changed to topo-definition