vCloud Usage Meter is unable to collect NSX Service Insertion usage with NSX 4.0.0.1
search cancel

vCloud Usage Meter is unable to collect NSX Service Insertion usage with NSX 4.0.0.1

book

Article ID: 319141

calendar_today

Updated On:

Products

VMware Aria Suite VMware NSX Networking

Issue/Introduction

Symptoms:

When using vCloud Usage Meter 4.4/4.5 with NSX 4.0.0.1, the feature usage collection for NSX Service Insertion fails with NSX-T API End Point returning Error 404 as shown below:

Feature detector PacketInspectionDetector raised exception com.vmware.um.collector.UnexpectedResponseCode: API endpoint api/v1/serviceinsertion/sections on server 25 returned HTTP status 404


This will cause the collection status for NSX 4.0.0.1 to show as "Incomplete collection":
image.png


Example log output in /opt/vmware/cloudusagemetering/var/logs/nsxt_error.log:
2022-06-14 08:38:30.586 ERROR — [NSX-T collector thread] c.vmware.um.nsxtcollector.NSXTCollector : Feature detector PacketInspectionDetector raised exception com.vmware.um.collector.UnexpectedResponseCode: API endpoint api/v1/serviceinsertion/sections on server 25 returned HTTP status 404
com.vmware.um.collector.UnexpectedResponseCode: API endpoint api/v1/serviceinsertion/sections on server 25 returned HTTP status 404
at com.vmware.um.collector.http.RequestBuilder.getResponse(RequestBuilder.java:211)
at com.vmware.um.collector.http.RequestBuilder.as(RequestBuilder.java:244)
at com.vmware.um.nsxtcollector.api.Client.fetchAll(Client.java:85)
at com.vmware.um.nsxtcollector.detectors.PacketInspectionDetector.detect(PacketInspectionDetector.java:245)
at com.vmware.um.nsxtcollector.NSXTCollector.collect(NSXTCollector.java:175)
at com.vmware.um.nsxtcollector.NSXTCollector.collect(NSXTCollector.java:34)
at com.vmware.um.collector.CollectionHelper.collectFromServer(CollectionHelper.java:1014)
at com.vmware.um.collector.CollectionHelper.collectFromServersWithReporting(CollectionHelper.java:1170)
at com.vmware.um.collector.CollectionHelper.collectWithReporting(CollectionHelper.java:990)
at com.vmware.um.collector.CollectionHelper.lambda$start$9(CollectionHelper.java:1518)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)




The issue is not observed when using vCloud Usage Meter 4.4/4.5 with NSX 3.x.


Environment

VMware NSX-T Data Center
VMware vCloud Usage Meter 4.x

Resolution

This is a known issue affecting VMware NSX-T Data Center 4.0.0.1.

Currently, there is no resolution.

Workaround:

Users can disregard the error message and continue to submit the usage data file.

While the collection status for NSX 4.0.0.1 shows as "Incomplete collection" because of the Error 404, the resulting usage file will still contain usage data for rest of NSX features except for NSX Service Insertion. Failure to collect NSX Service Insertion usage will not affect reporting of other NSX features. Since usage data for the rest of NSX features are collected successfully, users can still use and submit the usage data collection file.