Firewall rule hit count shows no data on Aria Operations for Networks GUI

Products

• VCF Operations for Networks

Issue/Introduction

Firewall rule hit count shows no data on Aria Operations for Networks GUI

Query: Firewall Rule order by Hit Count when executed on GUI shows No data. Refer to below screenshot:

CSV export also do not show any result or data for Hit count.

In the collector logs under location /var/log/arkin/collector/latest.log you will see below errors and exceptions

 

2025-03-19T15:45:50.846Z ERROR vmware.nsxt.NSXTDPOperationsManager NSXT_<IPorFQDN>_Config_OpMgr-3 scheduleMetricTask:599 Error in scheduling metric task for the NSX-T Entity type=RouterPort
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor_ScheduledFutureTask@309c12dc[Not completed, task = java.util.concurrent.Executors_RunnableAdapter@6460aa00[Wrapped task = com.google.common.util.concurrent.MoreExecutors_ScheduledListeningDecorator_NeverSuccessfulListenableFutureTask@58dbe002[status=PENDING]]] rejected from java.util.concurrent.ScheduledThreadPoolExecutor@
5cbfc40f[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 17664]
        at java.util.concurrent.ThreadPoolExecutor_AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2065) _[_:_]
        at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:833) _[_:_]
        at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:340) _[_:_]
        at java.util.concurrent.ScheduledThreadPoolExecutor.scheduleWithFixedDelay(ScheduledThreadPoolExecutor.java:680) _[_:_]
        at com.google.common.util.concurrent.MoreExecutors_ScheduledListeningDecorator.scheduleWithFixedDelay(MoreExecutors.java:628) _[guava-23.5-jre.jar:_]
        at com.vnera.dataproviders.tasker.Tasker.scheduleTaskWithInitialDelay(Tasker.java:393) _[dataproviders-0.001-SNAPSHOT.jar:_]
        at com.vnera.dataproviders.core.impl.vmware.nsxt.NSXTDPOperationsManager.scheduleMetricTask(NSXTDPOperationsManager.java:589) [dataproviders-0.001-SNAPSHOT.jar:_]
        at com.vnera.dataproviders.core.impl.vmware.nsxt.NSXTDPOperationsManager_NSXTConfigChangeTaskCallback.onSuccess(NSXTDPOperationsManager.java:778) [dataproviders-0.001-SNAPSHOT.jar:_]
        at com.vnera.dataproviders.tasker.Tasker_TaskerCallBack.onSuccess(Tasker.java:144) [dataproviders-0.001-SNAPSHOT.jar:_]
        at com.vnera.dataproviders.tasker.Tasker_ScheduledTaskWrapper.run(Tasker.java:487) [dataproviders-0.001-SNAPSHOT.jar:_]
        at com.google.common.util.concurrent.MoreExecutors_ScheduledListeningDecorator_NeverSuccessfulListenableFutureTask.run(MoreExecutors.java:678) [guava-23.5-jre.jar:_]
        at java.util.concurrent.Executors_RunnableAdapter.call(Executors.java:539) [_:_]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [_:_]
        at java.util.concurrent.ScheduledThreadPoolExecutor_ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [_:_]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [_:_]
        at java.util.concurrent.ThreadPoolExecutor_Worker.run(ThreadPoolExecutor.java:635) [_:_]
        at java.lang.Thread.run(Thread.java:840) [_:_]
2025-03-19T15:45:50.849Z WARN vmware.nsxt.NSXTDPOperationsManager NSXT_<IPorFQDN>_Config_OpMgr-3 scheduleMetricTask:572 Metric Properties Null for MoType: IpfixDfwConfig

 

2025-03-19T15:45:50.812Z ERROR vmware.nsxt.NSXTDPOperationsManager NSXT_<IPorFQDN>_Config_OpMgr-3 scheduleMetricTask:599 Error in scheduling metric task for the NSX-T Entity type=FirewallConfig
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor_ScheduledFutureTask@7e7e1ba7[Not completed, task = java.util.concurrent.Executors_RunnableAdapter@d45128b[Wrapped task = com.google.common.util.concurrent.MoreExecutors_ScheduledListeningDecorator_NeverSuccessfulListenableFutureTask@1f8aef2b[status=PENDING]]] rejected from java.util.concurrent.ScheduledThreadPoolExecutor@5
cbfc40f[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 17664]
        at java.util.concurrent.ThreadPoolExecutor_AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2065) _[_:_]
        at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:833) _[_:_]
        at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:340) _[_:_]
        at java.util.concurrent.ScheduledThreadPoolExecutor.scheduleWithFixedDelay(ScheduledThreadPoolExecutor.java:680) _[_:_]
        at com.google.common.util.concurrent.MoreExecutors_ScheduledListeningDecorator.scheduleWithFixedDelay(MoreExecutors.java:628) _[guava-23.5-jre.jar:_]
        at com.vnera.dataproviders.tasker.Tasker.scheduleTaskWithInitialDelay(Tasker.java:393) _[dataproviders-0.001-SNAPSHOT.jar:_]
        at com.vnera.dataproviders.core.impl.vmware.nsxt.NSXTDPOperationsManager.scheduleMetricTask(NSXTDPOperationsManager.java:589) [dataproviders-0.001-SNAPSHOT.jar:_]
        at com.vnera.dataproviders.core.impl.vmware.nsxt.NSXTDPOperationsManager_NSXTConfigChangeTaskCallback.onSuccess(NSXTDPOperationsManager.java:778) [dataproviders-0.001-SNAPSHOT.jar:_]
        at com.vnera.dataproviders.tasker.Tasker_TaskerCallBack.onSuccess(Tasker.java:144) [dataproviders-0.001-SNAPSHOT.jar:_]
        at com.vnera.dataproviders.tasker.Tasker_ScheduledTaskWrapper.run(Tasker.java:487) [dataproviders-0.001-SNAPSHOT.jar:_]
        at com.google.common.util.concurrent.MoreExecutors_ScheduledListeningDecorator_NeverSuccessfulListenableFutureTask.run(MoreExecutors.java:678) [guava-23.5-jre.jar:_]
        at java.util.concurrent.Executors_RunnableAdapter.call(Executors.java:539) [_:_]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [_:_]
        at java.util.concurrent.ScheduledThreadPoolExecutor_ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [_:_]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [_:_]
        at java.util.concurrent.ThreadPoolExecutor_Worker.run(ThreadPoolExecutor.java:635) [_:_]
        at java.lang.Thread.run(Thread.java:840) [_:_]
2025-03-19T15:45:50.814Z WARN vmware.nsxt.NSXTDPOperationsManager NSXT_<IPorFQDN>_Config_OpMgr-3 scheduleMetricTask:572 Metric Properties Null for MoType: FirewallRule

 

Environment

Aria Operations for Networks 6.14

Cause

Preemptive shutdown for Executor metric collection Thread

Resolution

This issue will be fixed in future version of VCF Aria Operations for Networks

To workaround perform below steps:

1. Stop data collection for the affected Data sources via GUI Toggle:

2. Restart collector services on collector and after services are running properly.

Steps to restart collector services:

SSH to respective collector node where you have both of your NSXT datasources added and login with username support.
Execute below commands: 

ub
cd build-target/collector
./stop-collector.sh

Once above is executed it will trigger stop of the server and this server will be automatically started back.

3. Wait for 5 minutes and then execute below command to see if all services shows running and healthy.

./check-service-health.sh -p -d

 

4. Re-enable Data Collection for the DS via GUI Toggle.

5. Observer for couple of hours and then executing GUI query: 

Firewall Rule order by Hit Count

 

6. You will see that firewall hit count data/metric starts showing on the GUI.

Refer to Screenshot below: