Post VMware Telco Cloud Service Assurance Upgrade

• In case, if you have not deleted the alarms as suggested in the GUID-6ED64106-260D-4600-BEBB-0F07EEFB0F5E.html#GUID-6ED64106-260D-4600-BEBB-0F07EEFB0F5E__section_fsn_w4g_wyb section, perform the following steps from the deployment VM:
  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
• In case Enrichment streams are not running, perform the following procedure:
  • Navigate to Administration > Configuration > Enrichment and start all the Enrichment streams manually from the VMware Telco Cloud Service Assurance UI.
• 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.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.
• After upgrading VMware Telco Cloud Service Assurance from 2.2 to 2.3, the Kafka must be regenerated for manually for the Cisco ACI and vIMS components. For certificate generation, 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.
  • For Cisco ACI: Update the newly generated certificate location, SCRAM password, and trust store location in the Domain Manager Device Access Settings and Polling and Thresholds window. For more information, see Update Device Access Setting for Kafka topic.
  • For vIMS: Update the newly generated certificate location, SCRAM password, and trust store location in the clientConnect.conf. For more information, see Configuring Edge Kafka and VMware Telco Cloud Service Assurance Data Collector topic.