VCF Operations for Networks instance unavailable to enable net flow on vCenter data source
search cancel

VCF Operations for Networks instance unavailable to enable net flow on vCenter data source

book

Article ID: 450302

calendar_today

Updated On:

Products

VCF Operations for Networks

Issue/Introduction

  • You add the vCenter data source and it gets added successfully but within 2-3 minutes the vCenter instance name is missing and NetFlow is disabled

  • In the Collector logs under /var/log/arkin/collector/ you see the following error for the vCenter data source

2026-07-21T19:56:06.141Z ERROR collector 61511 [netw@4413 class="customrequest.handler.VCCustomRequestHandler" thread="collector-process-msg-exec-1449
" method="getVCFExpiryInMillis" line="713"] Could not fetch expiry for VC ####: #########################, returning 0.
2026-07-21T19:56:06.141Z INFO collector 61511 [netw@4413 class="customrequest.handler.VCCustomRequestHandler" thread="collector-process-msg-exec-1449"
 method="fetchVCLicenseInfo" line="650"] VC ####: #########################, IP: https://#########.###.##.##:443/sdk, vcLicenseInfo:
editionKey: "vc.standard.instance"
expirationTime: 0
capacity: 1
name: "vCenter Server 8 Standard"
productVersion: "8.0"

and

2026-07-21T19:56:04.395Z WARNING collector 61511 [netw@4413 class="core.common.DataProviderFactory" thread="collector-process-msg-exec-1449" method="v
alidateCredentials" line="512"] Connection validation for VCENTER initiated with config: tags:{"enableDsAssociatedTags":false,"tagsValues":[{"tagKey":
"vcfManaged","tagValue":"true"}]}
VC_URL:https://############.###.##.##:443/sdk
VC_USER:#############@vsphere.local
VC_PWD:_______
nickName:############.###.##.##
_colectorId:######################

OpState:INACTIVE
vcfManaged:true
VALIDATE_ON_SUBMIT:true
restrictions:CAESGQoJCgU1LjEuMBAAEgwKBTUuMS4wEP_s4gQSGgoLCgU1LjUuMBDspFESCwoFNS41LjAQ3p1_EhwKDAoFNi4wLjAQ_aCYARIMCgU2LjAuMBCcp84B
dpId:VCENTER_############.###.##.##
ENCRYPTED_CONFIG:true
force.certificate.validation:true
2026-07-21T19:56:04.395Z INFO collector 61511 [netw@4413 class="configutils.vcenter.VCenterDPOperationalConfigReader" thread="collector-process-msg-ex
ec-1449" method="getIntValue" line="28"] Using read.timeout.millis: 90000 from "VCENTER.op.config".
Jul 21, 2026 7:56:04 PM org.bouncycastle.jsse.provider.ProvTlsClient notifyAlertRaised
INFO: [client #34293 @41fe18e6] raised fatal(2) certificate_unknown(46) alert: Failed to read record
org.bouncycastle.tls.TlsFatalAlert: certificate_unknown(46)
        at org.bouncycastle.jsse.provider.ProvSSLSocketDirect.checkServerTrusted(ProvSSLSocketDirect.java:136)
        at org.bouncycastle.jsse.provider.ProvTlsClient$1.notifyServerCertificate(ProvTlsClient.java:385)
        at org.bouncycastle.tls.TlsUtils.processServerCertificate(TlsUtils.java:4923)
        at org.bouncycastle.tls.TlsClientProtocol.handleServerCertificate(TlsClientProtocol.java:799)
        at org.bouncycastle.tls.TlsClientProtocol.handleHandshakeMessage(TlsClientProtocol.java:689)
        at org.bouncycastle.tls.TlsProtocol.processHandshakeQueue(TlsProtocol.java:715)
        at org.bouncycastle.tls.TlsProtocol.processRecord(TlsProtocol.java:591)
        at org.bouncycastle.tls.RecordStream.readRecord(RecordStream.java:247)
        at org.bouncycastle.tls.TlsProtocol.safeReadRecord(TlsProtocol.java:870)
        at org.bouncycastle.tls.TlsProtocol.blockForHandshake(TlsProtocol.java:427)
        at org.bouncycastle.tls.TlsClientProtocol.connect(TlsClientProtocol.java:88)
        at org.bouncycastle.jsse.provider.ProvSSLSocketDirect.startHandshake(ProvSSLSocketDirect.java:431)
        at org.bouncycastle.jsse.provider.ProvSSLSocketDirect.startHandshake(ProvSSLSocketDirect.java:412)
        at java.base/sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:589)
        at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:187)
        at java.base/sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1479)
        at java.base/sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1442)
        at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:220)
        at com.vmware.yavijava.vim25.ws.WSClient.post(WSClient.java:228)
        at com.vmware.yavijava.vim25.ws.WSClient.invoke(WSClient.java:129)

Environment

VCF Operations for Networks 9.1.0.0

Cause

  • VCF Operations for Networks v9.0 licensing is based on at least 1 licensed vCenter v9.0 data source configured within VCF Operations for Networks GUI.
  • If VCF Operations for Networks v9.0 is upgraded (stand-alone) or deployed without a vCenter v9.0 licensed with 9.0 SKU as a data source, the monitoring will no longer function after 90 days evaluation until you have at least one vCenter v9.0 licensed with VCF 9.0 license SKU.

 

Resolution

As described in the tech doc VCF Operations for networks License, at least one (1) vCenter data source must have valid 9.0 licenses applied for VCF Operations for Networks to be fully licensed.

 

1. You must upgrade your vCenter data source to version 9.0 so that the VCF 9.0 licenses allocated to the vCenter are applied to Operations for Networks.

    Or

2. As a workaround, you may add a tiny VCF 9.x vCenter with no workloads and a valid license as a data source to VCF Operations for Networks to enable you to continue to monitor your vCenter v8.x and other data sources.

Powered by Wolken Software