search cancel

NSX-T plugin for Virtual Network Assurance (VNA) is unable to discover all the components from NSX Cluster

book

Article ID: 244084

calendar_today

Updated On:

Products

CA Virtual Network Assurance DX NetOps

Issue/Introduction

NSX-T plugin for VNA is unable to discover all the components from NSX Cluster. It has only discovered Transport Zones however, the following entities should be seen as per document support:

  • Edge Clusters
  • Edge Nodes
  • Transport Nodes
  • T-0 Gateways
  • T-1 Gateways
  • Segments
  • Management Systems

System: NSX-T, Version 3.0.3

Environment

DX NetOps Virtual Network Assurance Release : 21.2
Component : Virtual Network Assurance For CA Spectrum

Cause

The following errors are shown constantly in the gateway.log:

2022-05-18 16:35:07,094 ERROR (Camel (NSXT Plugin-21.2.8-RELEASE) thread #19 - vm://global/plugin/nsxt/PERFORMANCE)  [NSXT_PLUGIN] TransportNodeStats 49  Failed to find entity ID for transport node f21f00b0-1c29-49fc-9f2f-0d554c34b708

 

And see the following in the oc.log:

2022-05-18 16:25:41,880 ERROR (EE-ManagedThreadFactory-default-Thread-8)  [OC_ACQUISITION] TimProcessFunction 182  Failed to invoke plugin NSXTGetTransportNodes from NSXTGetTransportNodes Acquisition TransportNodes: java.lang.reflect.InvocationTargetException

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_322]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_322]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_322]

        at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_322]

        at com.torokina.tim.process.node.function.TimProcessFunction.process(TimProcessFunction.java:149) [oc-simple-acquisition-21.2.8-RELEASE.jar:]

        at com.torokina.tim.process.aop.TimProcessNodeProxy.process(TimProcessNodeProxy.java:115) [oc-simple-acquisition-21.2.8-RELEASE.jar:]

        at com.torokina.tim.process.node.TimProcessNodeList.process(TimProcessNodeList.java:96) [oc-simple-acquisition-21.2.8-RELEASE.jar:]

        at com.torokina.tim.process.node.TimProcessNodeList.process(TimProcessNodeList.java:71) [oc-simple-acquisition-21.2.8-RELEASE.jar:]

        at com.torokina.tim.process.node.acquisition.TimProcessAcquisition.process(TimProcessAcquisition.java:158) [oc-simple-acquisition-21.2.8-RELEASE.jar:]

        at com.torokina.tim.process.aop.TimProcessNodeProxy.process(TimProcessNodeProxy.java:115) [oc-simple-acquisition-21.2.8-RELEASE.jar:]

        at com.torokina.tim.process.node.TimProcessNodeList.process(TimProcessNodeList.java:96) [oc-simple-acquisition-21.2.8-RELEASE.jar:]

        at com.torokina.tim.process.node.TimProcessNodeList.process(TimProcessNodeList.java:71) [oc-simple-acquisition-21.2.8-RELEASE.jar:]

        at com.torokina.tim.process.TimProcessRoot.process(TimProcessRoot.java:160) [oc-simple-acquisition-21.2.8-RELEASE.jar:]

        at com.torokina.tim.process.aop.TimProcessNodeProxy.process(TimProcessNodeProxy.java:115) [oc-simple-acquisition-21.2.8-RELEASE.jar:]

        at com.torokina.tim.process.TimProcessAcquisitionManager.process(TimProcessAcquisitionManager.java:96) [oc-simple-acquisition-21.2.8-RELEASE.jar:]

        at com.ca.oc.ejb.engine.acquisition.InventoryAcquisitionInvoker.invoke(InventoryAcquisitionInvoker.java:107) [oc-ejb-21.2.8-RELEASE.jar:]

        at com.ca.oc.ejb.engine.EngineThreadManager$EngineActionTask.run(EngineThreadManager.java:210) [oc-ejb-21.2.8-RELEASE.jar:]

        at com.ca.oc.ejb.engine.poller.SimpleMonitoredTaskBuilder$SimpleMonitoredTask.lambda$run$0(SimpleMonitoredTaskBuilder.java:133) [oc-ejb-21.2.8-RELEASE.jar:]

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_322]

        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_322]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_322]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_322]

        at java.lang.Thread.run(Thread.java:750) [rt.jar:1.8.0_322]

        at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:227) [jakarta.enterprise.concurrent-1.1.1.jar:]

Caused by: java.lang.NullPointerException: Cannot get property 'vm_deployment_config' on null object

        at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:60) [groovy-2.5.7.jar:2.5.7]

        at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:190) [groovy-2.5.7.jar:2.5.7]

        at org.codehaus.groovy.runtime.callsite.NullCallSite.getProperty(NullCallSite.java:46) [groovy-2.5.7.jar:2.5.7]

        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:298) [groovy-2.5.7.jar:2.5.7]

        at NSXTGetTransportNodes.process(NSXTGetTransportNodes.groovy:156)

        ... 24 more

Broadcom Sustaining has identified a number of bugs such as:

  1. Found a known issue in NSX-T 3.0.3 release:

    • Issue 2723812: In NSX-T Data Center, UI or REST API might not show the latest transport node status.

      Depending on the scale size and the system load, the UI and REST API might not show the latest transport node status.

      Workaround: Reboot the MP proton service.

  2. Slash ('/') is not interpreted correctly (#x2F;) in the item's tooltip. See screenshot below:


  3. Host Nodes and other items list only  one Transport Zone in the the tooltip. Where as we do know it belongs to multiple TZ's.

Resolution

These issues are fixed in VNA release 21.2.12.

Attachments