VIM status is currently showing as 'degraded' in the manager GUI.

Products

• VMware Telco Cloud Automation

Issue/Introduction

Installed a fresh 3.2 instance and restored the config backups. While all pods are operational, the VIM status is currently showing as 'degraded' in the manager GUI.

Environment

TCA: 3.2

TCP: 5.0

Cause

VIM status synchronization delay or service communication failure following a fresh deployment and configuration restoration.

Resolution

Troubleshooting and resolution steps:

1. Wait 24 Hours: In some fresh TCA 3.2 deployments, the VIM status may require up to 24 hours to fully synchronize and stabilize.

2. Verify Appliance Storage: Ensure there is sufficient free disk space on the TCA Manager (TCAM) and TCA Control Plane (TCACP) appliances.

3. Validate External URL: Confirm the VM external URL is configured as a Fully Qualified Domain Name (FQDN) in the vApp options.

   In vCenter, select the TCAM/TCACP VM.
   
   Navigate to Configure > vApp Options.

4. Restart Messaging Services: Restart the Kafka pods on both the TCAM and TCACP nodes to refresh the messaging bus.
   kubectl get pods -A | grep kafka
kubectl delete pod -n <Namespace> <kafka-pod-name>

5. Restart Application Services: Restart the core application services on the TCAM and TCACP appliances.
   Log in to the TCA and TCACP management port URL 9443 portal with user tca
Restart the application service