AppNeta is integrated with DX NetOps Virtual Network Assurance (VNA) using the AppNeta plugin.
VNA is integrated with DX NetOps Performance Management Portal and Data Aggregator.
Data from the AppNeta plugin was visible in reports but no longer is.
In the VNA oc.log file we see errors like this.
ERROR (EE-ManagedThreadFactory-default-Thread-3479) [OC_ACQUISITION] TimHttpFunction 301 Error while sending http request to https://<hostName>/api/v3/path/data?from=1702570200568&api_key=v3&limit=500&page=1 : java.io.IOException: Server returned HTTP response code: 400 for URL: https://<hostName>/api/v3/path/data?from=1702570200568&api_key=v3&limit=500&page=1
All supported DX NetOps releases
All supported DX NetOps Virtual Network Assurance (VNA) releases
All supported DX NetOps Performance Management releases
The VNA host is not synchronized for time. As a result, the requests for data from AppNeta were sent with times in the future. This caused AppNeta to reject the requests.
The "timedatectl status" command will show the problem when run on the VNA host. In this case we saw:
timedatectl status
Local time: Wed 2023-12-13 11:12:40 MST
Universal time: Wed 2023-12-13 18:12:40 UTC
RTC time: Wed 2023-12-13 18:02:02
Time zone: America/Phoenix (MST, -0700)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no
The lack of time synchronization will cause this. Time synchronization on the VNA host is a requirement.
Set up a time synchronization tool on the VNA host. Restart the VNA wildfly service.
The steps from the Portal Verify Time Synchronization documentation topic could be used to resolve this following those steps on the VNA host.