General VNA Troubleshooting
search cancel

General VNA Troubleshooting

book

Article ID: 371303

calendar_today

Updated On:

Products

CA Virtual Network Assurance

Issue/Introduction

This article covers general VNA health, scaling and log collection

Resolution

1. Confirm both mysql and wildfly are running\healthy 

systemctl status mysl

systemctl status wildfly

2. Confirm VNA Swagger Page is accessible:

http(s)://vnaHostname:8080(8443)/vna
 
3.  CPU Allocation:
  • General guidance is 1 core per configured Engine + 1
  • 3-5 Engines per VNA Instance
  • There are many factors that determine CPU and memory allocation the Dx NetOPs Sizer should be used to assist with this confguration.

4.  VNA (Wildfly) Memory Allocation:

  • Run top and check the java process (which is used by Wildfly)
  • If the RES column is using the total number allocated within the standalone.conf (articleid:196838) it is time to consider allocating more memory to VNA

Logs:

Dx NetOps Virtual Network Assurance Logs