YYYY-MM-DDTHH:MM:SS invocation-vmomi-executor-2 operationID=wcp-licenseRefreshMonitor INFO server.core.management.vmomi.SystemManagementServiceMoImpl searchAssets:
AssetSearchSpecByIdentifiersImpl
assetIdentifiers: [{instanceId: host-XXXXXX, scopeId: f7de4314-XXXXXX-XXXXXX-XXXXXX-ae70d26753a0}]
scopeId: f7de4314-XXXXXX-XXXXXX-XXXXXX-ae70d26753a0
YYYY-MM-DDTHH:MM:SS invocation-vmomi-executor-2 operationID=wcp-licenseRefreshMonitor ERROR server.core.management.vmomi.SystemManagementServiceMoImpl Assets not found: [host-XXXXXX-f7de4314-XXXXXX-XXXXXX-XXXXXX-ae70d26753a0]
com.vmware.cis.license.embedded.server.core.management.exception.NotFoundException: Assets not found: [host-XXXXXX-f7de4314-XXXXXX-XXXXXX-XXXXXX-ae70d26753a0]
at com.vmware.cis.license.embedded.server.core.management.helpers.impl.AssetValidatorImpl.validateAllAssetsFound(AssetValidatorImpl.java:123) ~[license-embedded-server-core-8.0.3.jar:?]
at com.vmware.cis.license.embedded.server.core.management.impl.SystemManagerImpl.queryAssetsByInstanceIds(SystemManagerImpl.java:997) ~[license-embedded-server-core-8.0.3.jar:?]
at com.vmware.cis.license.embedded.server.core.management.impl.SystemManagerImpl.queryAssetsByIdentifiers(SystemManagerImpl.java:934) ~[license-embedded-server-core-8.0.3.jar:?]
YYYY-MM-DDTHH:MM:SS info vpxd[05537] [Originator@6876 sub=IO.Http opID=m5v3uv51-110567-auto-2dbd-h5:70027850-4c] Ignore user agent secondary error; (null), N7Vmacore17CanceledExceptionE(Operation was canceled)
--> [context]zKq7AVECAQAAAAnecgEsdnB4ZAAAMxxTbGlidm1hY29yZS5zbwAA/hdCAB8/QwC+m0oAEeJHAXNAIWxpYnZtb21pLnNvAAEWcSEBhGkeAf5pHgHYah4BN0QeAQpsHoI+2ksBdnB4ZACCDeJLAYKeEUwBgj8VTAGCjilMAYJuLEwBgpfBSwGCj+9LAQHX2hqDYMRVAWxpYnZpbS10eXBlcy5zbwCCWr3XAYI7RTEBghqIMQGCzKExAYLSQyMCgmt9IwKCwt8dAYJO4R0BgiUNHwGD6780AYJtFYICAU11HIKk718CguyggAKCN7GAAoIrxH8CghqbgAIABOw3ABdFOAC7D1EEsI4AbGlicHRocmVhZC5zby4wAAXf+g9saWJjLnNvLjYA[/context]
YYYY-MM-DDTHH:MM:SS info vpxd[05537] [Originator@6876 sub=Vmomi opID=m5v3uv51-110567-auto-2dbd-h5:70027850-4c] Creating SOAP stub adapter for /vpxa on esxi01.sample.domain:443
YYYY-MM-DDTHH:MM:SS info vpxd[05409] [Originator@6876 sub=vpxLro opID=m5v3uv51-2dbn-h5:70027418-d7] [VpxLRO] -- FINISH lro-2829431
YYYY-MM-DDTHH:MM:SS info vpxd[05481] [Originator@6876 sub=HostDlfDownloader opID=m5v3uv51-110567-auto-2dbd-h5:70027850-4c-HostDLFDownload-46684082] Downloading Dlfs for Host 'VMware ESX Server', Version: '7.0', File Version: '7.0.5.0' Dlf Directory Location: '/etc/vmware-vpx//licenses/site//VMware ESX Server/7.0/7.0.5.0'
YYYY-MM-DDTHH:MM:SS warning vpxd[05481] [Originator@6876 sub=NfcLib opID=m5v3uv51-110567-auto-2dbd-h5:70027850-4c-HostDLFDownload-46684082] [NFC WARNING]Plain-text connection is deprecated; use SSL to connect to NFC server
-->
YYYY-MM-DDTHH:MM:SS error vpxd[05481] [Originator@6876 sub=NfcLib opID=m5v3uv51-110567-auto-2dbd-h5:70027850-4c-HostDLFDownload-46684082] [NFC ERROR]NfcNewAuthdConnectionEx: Failed to connect: Error reading from vmware-authd socket. Reason: Connection reset by peer
-->
YYYY-MM-DDTHH:MM:SS error vpxd[05481] [Originator@6876 sub=NfcLib opID=m5v3uv51-110567-auto-2dbd-h5:70027850-4c-HostDLFDownload-46684082] [NFC ERROR]NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Error reading from vmware-authd socket. Reason: Connection reset by peer
-->
YYYY-MM-DDTHH:MM:SS error vpxd[05481] [Originator@6876 sub=NfcLib opID=m5v3uv51-110567-auto-2dbd-h5:70027850-4c-HostDLFDownload-46684082] [NFC ERROR]NfcEstablishAuthCnxToServer: Failed to create new AuthD connection: Error reading from vmware-authd socket. Reason: Connection reset by peer
-->
YYYY-MM-DDTHH:MM:SS error vpxd[05481] [Originator@6876 sub=NfcLib opID=m5v3uv51-110567-auto-2dbd-h5:70027850-4c-HostDLFDownload-46684082] [NFC ERROR]Nfc_BindAndEstablishAuthdCnx3: Failed to create a connection with server esxi01.sample.domain: Error reading from vmware-authd socket. Reason: Connection reset by peer
-->
YYYY-MM-DDTHH:MM:SS error vpxd[05481] [Originator@6876 sub=vpxNfcClient opID=m5v3uv51-110567-auto-2dbd-h5:70027850-4c-HostDLFDownload-46684082] Unable to connect to NFC server: Error reading from vmware-authd socket. Reason: Connection reset by peer
YYYY-MM-DDTHH:MM:SS error vpxd[05481] [Originator@6876 sub=HostDlfDownloader opID=m5v3uv51-110567-auto-2dbd-h5:70027850-4c-HostDLFDownload-46684082] DownloadDlfs got an exception: Fault cause: vim.fault.HostConnectFault
-->
YYYY-MM-DDTHH:MM:SS error vpxd[05481] [Originator@6876 sub=licenseClient opID=m5v3uv51-110567-auto-2dbd-h5:70027850-4c-HostDLFDownload-46684082] Failed to download DLF: [vim.HostSystem:host-XXXXXX,esxi01.sample.domain], N5Vmomi5Fault17NotEnoughLicenses9ExceptionE(Fault cause: vmodl.fault.NotEnoughLicenses
VMware vCenter Server
VMware vSphere ESXi
Port 902 is crucial for communication between vSphere components such as vCenter Server, ESXi hosts, and vSphere Client.
If port 902 is blocked by a firewall, you may encounter issues such as failed connections to the vSphere Web Client, inability to manage hosts, backup or issues with VM console access.
To resolve issues caused by port 902 being blocked, follow these steps:
Example command to test connectivity: telnet <vCenter_Server_IP> 902
On the ESXi Host, ensure the firewall is allowing traffic on port 902. You can check this by using the ESXi CLI: esxcli network firewall ruleset list
On the vCenter Server, verify that port 902 is allowed through the server’s firewall. The firewall may need to be adjusted to ensure proper communication.
Ensure that any intermediary network devices (such as routers or firewalls between the vCenter Server and ESXi hosts) allow traffic on both UDP and TCP port 902. If these devices block the port, it can disrupt communication and service access.
Ensure that DNS resolution is working correctly. If DNS is not functioning, the ESXi hosts or vCenter Server may be unable to resolve each other’s names, affecting the use of port 902. You can test DNS resolution with the nslookup or dig command to confirm that all hostnames are properly resolving to the correct IP addresses.