Aruba Central VNA plugin only collects client data.

Products

• Network Observability
• Virtual Network Assurance
• CA Performance Management
• Spectrum

Issue/Introduction

Virtual Network Assurance (VNA) Aruba Central plugin is not collecting data for anything but clients.

In the <VNA_INSTALL_DIR>/wildfly/standalone/log/oc.log

YYYY-MM-DD HH:MM:SS,### ERROR (EE-ManagedThreadFactory-default-Thread-4)  [OC_ACQUISITION] TimHttpFunction 332  Error while sending http request to https://<ARUBA_DOMAIN_URL>/configuration/v2/groups?limit=20&offset=0 : java.net.SocketTimeoutException: Connect timed out
    at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:551)

Environment

DX Netops Virtual Network Assurance all supported versions

Cause

Cannot contact the ARUBA_DOMAIN_URL  from the VNA server which is needed.

Client information is pushed to VNA form Aruba which is why you can see the client information as this is successful

Resolution

Make sure the ARUBA_DOMAIN_URL can be contacted from the VNA server.

curl -kv 'https://<ARUBA_DOMAIN_URL>/configuration/v2/groups?limit=20&offset=0'

If you have a proxy, use the --proxy flag configured accordingly:

-x, --proxy <[protocol://][user:password@]proxyhost[:port]>
              Use the specified HTTP proxy. If the port number is not specified, it is assumed at port 1080.

              This option overrides existing environment variables that set the proxy to use. If there's an environment variable setting a proxy, you can set proxy to "" to override it.

              All  operations that are performed over an HTTP proxy will transparently be converted to HTTP. It means that certain protocol specific operations might not be available. This is not the case
              if you can tunnel through the proxy, as one with the -p, --proxytunnel option.

              User and password that might be provided in the proxy string are URL decoded by curl. This allows you to pass in special characters such as @ by using %40 or pass in a colon with %3a.

              The proxy host can be specified the exact same way as the proxy environment variables, including the protocol prefix (http://) and the embedded user + password.

              From 7.21.7, the proxy string may be specified with a protocol:// prefix to specify alternative proxy protocols. Use socks4://, socks4a://, socks5:// or socks5h:// to  request  the  specific
              SOCKS version to be used. No protocol specified, http:// and all others will be treated as HTTP proxies.

              If this option is used several times, the last one will be used.

Curl is just used for the connection testing (not using any authentication) so a successful connection will return similar to:

< HTTP/1.1 401 Unauthorized
< Date: <date time>
< Content-Type: application/json; charset=utf-8
< Connection: keep-alive
< WWW-Authenticate: Bearer realm="service"
< Content-Length: 78
<
{"error_description":"The access token is missing","error":"invalid_request"}

If the connection only works with the proxy, fill out the proxy settings accordingly and set the proxy to true:

    "USE_PROXY": false,
    "PROXY_IP": "0.0.0.0",
    "PROXY_PORT": 0,
    "PROXY_PROTOCOL": "http",
    "PROXY_USERNAME": "",
    "PROXY_PASSWORD": "",

Additional Information

Aruba Central plugin documentation.