ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

VNA Tunnel Data Missing - No Viptela Tunnel Data Since Weekend

book

Article ID: 199026

calendar_today

Updated On:

Products

CA Virtual Network Assurance

Issue/Introduction

Over the weekend we lost VNA Viptela performance data on the tunnels. We are currently troubleshooting. The following has been tried:

1. Set VNA gateway to admin down / admin up.
2. Login to Viptela vManage UI manually with service account to ensure password not changed / locked out.
3. Check engine status (Is running)


Cause

Out of memory error seen in gateway.log

2020-09-05 12:39:09,467 INFO (Thread-13498 (ActiveMQ-client-global-threads)) [INVENTORY_SERVICE] InventoryManager 476 Response processing completed for response #770183 2020-09-05 13:18:05,672 WARN (Camel (AWS Plugin-20.2.1-RELEASE) thread #43 - vm://global/plugin/aws/NOTIFICATION) [org.apache.camel.component.vm.VmConsumer] MarkerIgnoringBase 135 Caused by: [java.lang.OutOfMemoryError - Java heap space]: java.lang.OutOfMemoryError: Java heap space

Environment

Release : 20.2 Virtual Network Assurance For CA Performance Management

Resolution

The following can be done to update memory

  • In VNA_HOME/wildfly/bin/standalone.conf file, change VNA_MAX_MEM.  By default it is 4gb
  • Stop wildfly: service wildfly stop / systemctl stop wildfly
  • Start wildfly: service wildfly start / systemctl start wildfly

The memory issues should be resolved and oyu should now hopefully be seeing Viptela data