search cancel

No performance poll data from Viptela plugin in DX Netops Virtual Network Assurance

book

Article ID: 216719

calendar_today

Updated On:

Products

CA Virtual Network Assurance

Issue/Introduction

No performance poll data from Viptela plugin in DX Netops Virtual Network Assurance, this was after an issue with vManage that required it to be restarted.

Inventory polling appears to be happening fine, but no performance data is seen.

Looking at a parse of the /opt/CA/VNA/wildfly/standalone/log/oc.log using "grep _Poll_ oc.log" we can see that the performance polls stop but the Inventory Polls continue.

The Performance polls seems to stop after a timeout also seen in the oc.log:

YYYY-DD-MM HH:MM:SS,### WARN  (EE-ManagedScheduledExecutorService-default-Thread-9) Viptela_UUID=Performance Poll [OC_CORE] SimpleMonitoredTaskBuilder$SimpleMonitoredTask 174  Timeout occurs for monitored task of engine=Viptela_UUID thread=Performance Poll, timeout value = 1800000: java.util.concurrent.TimeoutException
 at java.util.concurrent.FutureTask.get(FutureTask.java:205) [rt.jar:1.8.0_292]
 at com.ca.oc.ejb.engine.poller.SimpleMonitoredTaskBuilder$SimpleMonitoredTask.run(SimpleMonitoredTaskBuilder.java:162) [oc-ejb-20.2.5-RELEASE.jar:]
 at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledScheduledRunnable.run(ControlPointUtils.java:158) [wildfly-ee-17.0.1.Final.jar:17.0.1.Final]
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_292]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_292]
 at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141) [javax.enterprise.concurrent-1.0.jar:]
 at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$101(ManagedScheduledThreadPoolExecutor.java:383) [javax.enterprise.concurrent-1.0.jar:]
 at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:532) [javax.enterprise.concurrent-1.0.jar:]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_292]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_292]
 at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_292]
 at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) [javax.enterprise.concurrent-1.0.jar:]


Environment

Release : 20.2, 21.2.1

Component : Virtual Network Assurance For CA Performance Management

Cause

Defect: DE505250 

Resolution

The fix for this issue is currently targeted for DX Netops Virtual Network Assurance 21.2.2

Note that this is subject to change and there are no release dates that can be provided at this time.

At this time the workaround is to restart the wildfly service on the DX Netops Virtual Network Assurance server:

service wildfly stop
service wildfly start

This will restart the VNA performance poller.

Additional Information

If the performance poll cannot regularly complete within 30 minutes, you can increase the time out per:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-netops/20-2/release-notes/new-features-and-enhancements.html

Poll Time Configuration:

The default timeout value for a poll in the engine of any plug-in is 30 minutes. If a poll requires more than the default value, you can configure the sdn_poll_timeout_minutes parameter in the /etc/VNA.cfg file. The unit for the parameter value is minutes. After you configure this parameter, restart DX NetOps Virtual Network Assurance.