(UCMDB SUPPORT TIP) - Meaning of Error in Host resources and applications by SNMP for Scanner-based
During vCenter Server Discovery by SNMP, the following error or similar is seen in the communication log :
<log start="" severity="debug">Failed to run tcp discovery by snmp
Traceback (most recent call last):
File "snmp_dis_all", line 167, in DiscoveryMain
File "Dis_TCP", line 287, in discoverTCP
Exception: No TCP information is available
This technote considers its meaning.
This exception usually means that the TCP port device doesn’t respond to the MIB and is often down to a vendor issue.
If the vendor wants to expose it they can, but if they don’t, SNMP discovery cannot do this.
Because no TCP ports can be discovered, no software or signatures can be matched.
The easy way around this is to run the manual VMWare Topology By VIM job specifying the system specifically (see the Discovery and Integration Content Guide). This will use the VIM protocol which is installed on all VMWare systems by default. Permissions need to be given (see guide again for which permissions) before it can be discovered.
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Please hit the Kudo botton, if you find this post useful.