After upgraded VNA to 23.3.13, data from the Velocloud plugin stopped.
Self monitoring data is still populating in DX NetOps Performance Management.
In the <VNA Installation Directory>/wildfly/standalone/log/oc.log an error similar to the following is seen:
YYYY-MM-DD HH:MM:SS,### WARN (EE-ManagedThreadFactory-default-Thread-5) [OC_ACQUISITION] TimHttpHelper 723 Error connecting to https://hostname:port/portal/rest/enterpriseProxy/getEnterpriseProxyUsers: {"error":{"code":-32603,"message":"user type [ENTERPRISE_USER] not allowed to method [enterpriseProxy/getEnterpriseProxyUsers]"}}
YYYY-MM-DD HH:1MM:SS,### ERROR (EE-ManagedThreadFactory-default-Thread-5) [OC_ACQUISITION] TimHttpFunction 332 Error while sending http request to https://hostname:port/portal/rest/enterpriseProxy/getEnterpriseProxyUsers : java.io.IOException: Server returned HTTP response code: 400 for URL: https://hostname:port/portal/rest/enterpriseProxy/getEnterpriseProxyUsers
at java.base/jdk.internal.reflect.GeneratedConstructorAccessor221.newInstance(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481)
at java.base/sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:2078)
at java.base/sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:2073)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:569)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:2072)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1630)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1610)
~~~~~~~
DX NetOps Virtual Network Assurance (VNA): 23.3.13
Defect: DE155169
This issue has been resolved in DX NetOps Virtual Network Assurance 24.3.2:
Symptom: The VeloCloud plug-in has broken token authentication. No relevant errors in the logs, but data collection is failing.
Resolution: With this fix, the wrong error check has been removed, an additional check for json type has been added, and the entire class has been refactored.
(24.3.2, DE155169, 91476782,35844989)
It is recommended to keep version current to take advantage of the latest features and fixes.
VNA Fixed issues are under Performance Management Resolved Issues at the time this article was written.