• The below command need to be executed post upgrade to improve the metric ingestion performance through Edge Kafka from Deployer Host. Export Kube Config file export KUBECONFIG=<your-Kubeconfigfile-path>.
    metricPartitions=$(kubectl get kt vsa-metrics-raw -o 'jsonpath={..spec.partitions}')
    edgeMetricTopic=$(kubectl get kt -n kafka-edge | grep vsa-metrics-raw | cut -f1 -d' ')
    kubectl patch kt $edgeMetricTopic -n kafka-edge --type='json' -p='[ { "op" : "replace" , "path" : "/spec/partitions" , "value" : '$metricPartitions' } ]'
  • 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, 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.
  • In case, if you have not deleted the alarms as suggested in the Prerequisites for Upgrading VMware Telco Cloud Service Assurance section, perform the following steps from the deployment VM:
    Note: This step is applicable only while preforming upgrade from VMware Telco Cloud Service Assurance 2.1 to VMware Telco Cloud Service Assurance 2.3.
    1. kubectl get pods | grep alerting-rest
    2. kubectl exec -i <alerting-rest-pod-name> –- bash -c "curl -X DELETE http://localhost:8080/omega-alerting/v1/alert"
    3. kubectl scale deployments alerting-rest --replicas=0
    4. kubectl scale deployments alerting-rest --replicas=1
  • 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 VMware Telco Cloud Service Assurance from 2.1 or 2.2 to 2.3, if there are any Remediation Rules configured, then delete the existing Remediation Rules from the VMware Telco Cloud Service Assurance 2.3 UI and recreate the new Rules.
  • After upgrading VMware Telco Cloud Service Assurance from 2.1 or 2.2 to 2.3, if there were any Alerting or Anomaly Rules which were created by the user before upgrade, those definitions will no longer be available post upgrade. Then you must recreate these definitions.
  • After upgrading VMware Telco Cloud Service Assurance from 2.2 to 2.3, you must migrate the VMware Telco Cloud Service Assurance Domain Settings from 2.2 to 2.3. To migrate, follow the steps in Domain Settings Migration from VMware Telco Cloud Service Assurance 2.2 to 2.3 topic.
    Note: This step is required only if you have configured Domain settings (ESM and OI) under Administration in VMware Telco Cloud Service Assurance 2.2.
  • The certificates for the Edge Kafka needs to be regenerated manually for the Cisco ACI and vIMS components post upgrade to 2.3.
  • For regenerating the Kafka-Edge certificates, see Enable TLS for Edge Kafka topic.
    Note: This step is applicable only if Cisco ACI and vIMS are configured as part of VMware Telco Cloud Service Assurance 2.2.
    After you generate the certificates, perform the following steps for Cisco ACI and vIMS.