search cancel

VNA Viptela Event and Alarm API requests to port 8443 show timeout against wrong port 443

book

Article ID: 214603

calendar_today

Updated On:

Products

CA Spectrum DX NetOps CA Virtual Network Assurance

Issue/Introduction

VNA Viptela plugins are configured to use https against port 8443.

There are no issues gathering Inventory or Data using that configuration but no Events or Alarms from Viptela are seen in Spectrum.

In the oc.log file we see the following requests for Events (same messages seen for Alarm requests) go out to the correct port 8443.

2021-04-18 10:47:20,523 INFO  (EE-ManagedThreadFactory-default-Thread-10) Viptela_bc7d5383-47b2-44fc-8254-6191c8d11c4a=Notification Poll [OC_SCRIPTING] Logger$info$0 -1  Fetching URL : https://<ViptelaHost>:8443/dataservice/event?query={"query":{"condition":"AND","rules":[{"value":["2021-04-18T10:11:00","2021-04-18T10:47:00"],"field":"entry_time","type":"date","operator":"between"}]},"size":10000}

The response received next is a timeout error using port 443 which is the wrong port.

2021-04-18 10:47:40,549 ERROR (EE-ManagedThreadFactory-default-Thread-10) Viptela_bc7d5383-47b2-44fc-8254-6191c8d11c4a=Notification Poll [OC_ACQUISITION] TimProcessFunction 182  Failed to invoke plugin ViptelaHttpFunction from ViptelaHttpFunction Acquisition Events: java.lang.reflect.InvocationTargetException
...
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to <ViptelaHost>:443 [/<ViptelaHost>] failed: connect timed out
...
Caused by: java.net.SocketTimeoutException: connect timed out

Cause

A code defect results in the configured port being ignored when the Event and Alarm requests are processed before being sent to Viptela.

As a result it drops and ignores the provided port 8443, substituting it with the default SSL port 443.

Environment

All supported DX NetOps Virtual Network Assurance releases older than r21.2.1.

Resolution

This is being resolved via defect DE502369.

There is no workaround available.

Code change is available in r21.2.1 and newer releases which fixes this problem. Upgrade to resolve this.