"NSX-T latency collector not configured" error message under Accounts and Data Sources page in VCF Operations for Networks

Products

• VCF Operations for Networks

Issue/Introduction

• Under alerts in VCF Operation for Networks, we see below critical alert : 
  
   
  
  
• For the impacted NSX-T data source, checkbox for "Enable latency metric collection" is enabled.
  
  
• In Collector VM logs under path  /var/log/arkin/collector/ , we see below entries that indicate "Latency Collector Mismatch"
  
  

  ####-##-##T##:##:29.843Z INFO impl.dataprovider.AbstractDPOperationsManager DataProviderManager::healthCheck getHealthStatus:514 DPHealthStatus: dpId {
    dataProviderIdentifier: "NSXT_FQDN"
    customerId: ###40
  }
  healthReport {
    health: HEALTHY
    healthMessage: ""
    healthErrorCode: "SUCCEEDED"
    healthPayload: "{"NSXT_NOTIFICATION_WEBHOOK_STATUS":"","NSX_LATENCY_STATUS":""}"
  }
  lastCollectionTime: ########59728
  dpStats {
  }
  lastConfigCollectionTime: ########64037
  lastScheduledConfigTaskRunTime: -1
  .
   maxMetricTaskSuccessTS: ########59728.
   DPTaskGroupStatusList: [DPTaskGroupStatus
  {
  collectedDataType=CONFIG
  taskGroupExecStatus=HEALTHY
  taskGroupErrorCode=SUCCEEDED
  taskGroupErrorMsg=
  maxTS=########64037
  maxSuccessTS=########64037
  minTS=########27060
  totalTasks=19
  taskStatusList=[DPTaskStatus
  {
          taskId='com.vnera.dataproviders.core.impl.vmware.nsxt.tasks.NSXTLatencyStateWatcher'
          collectedDataType=CONFIG
          taskExecType=SCHEDULED
          isSuccess=false
          timestamp=########96615
          errorCode='NSXT_LATENCY_COLLECTOR_MISMATCH'
          errorMessage='com.vnera.dataproviders.core.impl.vmware.nsx.utils.StateWatcherException: Latency collector is not configured correctly
          at com.vnera.dataproviders.core.impl.vmware.nsxt.tasks.NSXTLatencyStateWatcher.process(NSXTLatencyStateWatcher.java:99)
          at com.vnera.dataproviders.core.impl.vmware.nsxt.tasks.NSXTLatencyStateWatcher.doRun(NSXTLatencyStateWatcher.java:78)
          at com.vnera.dataproviders.core.common.impl.dataprovider.tasks.AbstractTask.run(AbstractTask.java:165)
          at com.vnera.dataproviders.tasker.Tasker_ScheduledTaskWrapper.run(Tasker.java:486)
          at com.google.common.util.concurrent.MoreExecutors_ScheduledListeningDecorator_NeverSuccessfulListenableFutureTask.run(MoreExecutors.java:678)
          at java.base/java.util.concurrent.Executors_RunnableAdapter.call(Executors.java:539)
          at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
          at java.base/java.util.concurrent.ScheduledThreadPoolExecutor_ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
          at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
          at java.base/java.util.concurrent.ThreadPoolExecutor_Worker.run(ThreadPoolExecutor.java:635)
          at java.base/java.lang.Thread.run(Thread.java:840)
  '
          taskData={timeTaken=77, healthMsgPayload=, healthMsgPayloadKey=NSX_LATENCY_STATUS}
  }

Environment

VCF Operations for Networks 6.14

Resolution

Toggle Data Collection checkbox for the impacted data source to re-establish the connection with VCF Operations for Networks. 

To do so, navigate under Settings -> Accounts and Data Sources -> Data Collection -> Disable. Please give it few minutes ( ~ 5-10 mins) before enabling data collection setting again. 

Additional Information

• Observe the environment for possible recurrence, for a period of time which could be up to 48 hours.  This period of time can vary with a number of factors, mainly related to the size and scope of the customer environment.
  
  
• If the issue recurs before the expiration of the 48 hour observation period, please open a Support case with Broadcom using the instructions at Creating and managing Broadcom support cases then upload both the baseline and the fresh log bundles to the case using the instructions at Uploading files to cases on the Broadcom Support Portal.