In this topic, you can find information about common issues and workaround for various data collectors in VMware Telco Cloud Operations.

  1. Collector name: smarts-event-data-smarts-sam

    Issue: The Default Notification Console in Notification View is not displayed any/new notifications generated in the configured SAM server.

    Steps to troubleshoot the logs:
    1. Verify whether the collector is running by selecting the status column for the Smarts-event-data-smarts-sam collector under VMware Telco Cloud Operations UI > Administration > Data Collector.
    2. If the Smarts-event-data-smarts-sam collector is not running, start the collector and wait for five minutes to synchronize the events from the SAM server.
    3. If the events are still not updated in Notification Console view, then run the following command on the VMware Telco Cloud Operations control plane node to view the latest log messages from the collector:
      kubectl logs -f `k get pods --selector app=collector-manager,run=smarts-event-data-smarts-sam | awk 'NR>1 {print $1}'` -n vmware-smarts
  2. Collector name: smarts-topology-data-smarts-sam

    Issue: Topology Explorer is not showing any/new instances available in the configured SAM server.

    Steps to troubleshoot the logs:
    1. Verify whether the collector is running by selecting the status column for the Smarts-event-data-smarts-sam, collector under VMware Telco Cloud Operations UI > Administration > Data Collector.
    2. Start the collector Smarts-event-data-smarts-sam, if it is in the stopped state.
    3. If the Topology explorer is still not updated in the UI, then run the following command on the VMware Telco Cloud Operations control plane node to view the latest log messages from the collector:
      kubectl logs -f `k get pods --selector app=collector-manager,run=smarts-topology-data-smarts-sam | awk 'NR>1 {print $1}'` -n vmware-smarts
  3. Collector name: smarts-metrics

    Issue: The metric data from the INCHARGE-AM-PM domain manager is collected, and as a result the corresponding reports are not displaying the new/updated data.

    Steps to troubleshoot the logs:
    1. Verify whether there is a collector instance created with a category smarts-metrics in VMware Telco Cloud Operations UI > Administration > Data Collector and ensure that the collector is in the running state.
    2. To verify the logs from the associated collector, run the following commands where the collector instance name is same as in the VMware Telco Cloud Operations UI > Administration > Data Collector for smarts-metrics category.

      kubectl get pods -n vmware-smarts | grep <Collector instance name shown in the UI> | awk '{print $1}'

      kubectl logs -f <Instance name shown in above command>

      For example:

      kubectl get pods -n vmware-smarts | grep smarts-metric| awk '{print $1}'

      kubectl logs -f smarts-metric-data-1247032619-7574bc75fd-s72s7

  4. Collector name: velocloud-sdwan

    Issue: VeloCloud performance data is not collected and the corresponding reports (SDWAN) are not display any data.

    Steps to troubleshoot the logs:
    1. Verify whether there is a collector instance created with a category velocloud-sdwan in VMware Telco Cloud Operations UI > Administration > Data Collector and ensure that the collector is in the running state.
    2. To verify the logs from the associated collector, run the following command where the collector instance name is same as in the VMware Telco Cloud Operations UI > Administration > Data Collector for the velocloud-sdwan category.

      kubectl get pods -n vmware-smarts | grep <Collector instance name shown in the UI> | awk '{print $1}'

      kubectl logs -f <Instance name shown in above command>

      For example:

      kubectl get pods -n vmware-smarts | grep velocloud-performance| awk '{print $1}'

      kubectl logs -f velocloud-performance-1242133619-7edfw7622-b67sd3

  5. Collector name: viptela-sdwan

    Issue: Viptela performance data is not collected and the corresponding reports (SDWAN) are not display any data.

    Steps to troubleshoot the logs:
    1. Verify whether there is a collector instance created with a category viptela-sdwan in VMware Telco Cloud Operations UI > Administration > Data Collector and ensure that the collector is in the running state.
    2. To verify the logs from the associated collector, run the following command where the collector instance name is same as in the VMware Telco Cloud Operations UI > Administration > Data Collector for the viptela-sdwan category:

      kubectl get pods -n vmware-smarts | grep <Collector instance name shown in the UI> | awk '{print $1}'

      kubectl logs -f <Instance name shown in above command>

      For example:

      kubectl get pods -n vmware-smarts | grep viptela-performance| awk '{print $1}'

      kubectl logs -f viptela-performance-1242133619-7edfw7622-b67sd3