Quantcast
Channel: VMware Communities : All Content - ESXi
Viewing all articles
Browse latest Browse all 8313

ESXi host not listening on 902

$
0
0

Hi Guys,

 

We have an ESXi 4.1 host that disconnected from VC recently, and can't be re-added.

 

When we try, on the ESX host we get "the specified key, name or identifier already exists", and errors such as these in the VC logs:

 

[VpxNfcClient] Unable to connect to NFC server: Failed to connect to server ServerName.Domain.com:902

Cnx_Connect: Error message: Failed to connect to server ServerName.Domain.com:902

 

Which suggests a FW/comms issue, but when I logon to the ESX host console, and run "esxcli network connections list" it isn't listening on port 902 (networks teams have also confirmed nothing blocking).


I thought that hostd always listened on 902, irrelevant of having a VPXA agent installed, is that correct?

 

It's not listening on port 22 either, and when i try and run "vim-cmd hostsvc/start_remote_tsm", it says "the operation is not allowed in this current state". So I can't SSH to it, but I can connect using VC Client (oddly, in the VC Client, it thinks that both local and remote tech support are enabled!)

 

The box has been bounced numerous times, management agents restarted etc, VC Service restarted and also I have uninstalled VPXA using /opt/vmware/uninstallers/VMware-vpxa-uninstall.sh

 

I am about to rebuild, but would like to know what has happened if anyone has any ideas? And particularly why it's not listening on 902.

 

Many thanks for reading!

 

Dave


Viewing all articles
Browse latest Browse all 8313

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>