No SNMP port 161 detected for Discovery SchedulesIssue No SNMP port 161 detected for discovery run via Discovery Schedules. As a result, the discovery unable to classify the CI for SNMP devices. Shazzam input -> no 161<result active="true" alive="true" ip_address="xx.xx.xxx.xxx"><scanner name="HTTPS" port="5986" portprobe="winrm_ssl" protocol="tcp" result="timed_out" service="winrm_ssl"/><scanner name="BannerTCP" port="22" portprobe="ssh" protocol="tcp" result="open" service="ssh"><banner_text>SSH-2.0-OpenSSH_5.3 </banner_text><banner_bytes>.53.53.48.2d.32.2e.30.2d.4f.70.65.6e.53.53.48.5f.35.2e.33.0d.0a.</banner_bytes></scanner><scanner name="BannerTCP" port="5480" portprobe="vmapp" protocol="tcp" result="refused" service="vmapp_https"/><scanner name="BannerTCP" port="9443" portprobe="vmapp" protocol="tcp" result="refused" service="vmapp6_https"/><scanner name="BannerTCP" port="902" portprobe="esxi" protocol="tcp" result="refused" service="ESXi"/><scanner name="NBT" port="137" portprobe="wins" protocol="udp" result="refused" service="ms-nb-ns"/><scanner name="GenericTCP" port="135" portprobe="wmi" protocol="tcp" result="refused" service="epmap"/><scanner name="SLP" port="427" portprobe="slp" protocol="udp" result="refused" service="slp"/><scanner name="GenericTCP" port="5989" portprobe="wbem" protocol="tcp" result="refused" service="wbem_https"/><scanner name="DNS" port="53" portprobe="dns" protocol="udp" result="unresolved" service="dns"/><scanner name="HTTP" port="443" portprobe="http" protocol="tcp" result="open" service="https"/></result> Quick discovery detects port 161 and able to classify the CI. Shazzam input with 161 open<result active="true" alive="true" ip_address="xx.xx.xxx.xxx"><scanner name="SNMP" port="161" portprobe="snmp" protocol="udp" result="open" service="snmp"><snmp_version>3</snmp_version></scanner><scanner name="HTTPS" port="5986" portprobe="winrm_ssl" protocol="tcp" result="io_error" service="winrm_ssl"><error_msg>IOException - The remote computer refused the network connection. </error_msg></scanner><scanner name="BannerTCP" port="22" portprobe="ssh" protocol="tcp" result="open" service="ssh"><banner_text>SSH-2.0-OpenSSH_5.3 </banner_text><banner_bytes>.53.53.48.2d.32.2e.30.2d.4f.70.65.6e.53.53.48.5f.35.2e.33.0d.0a.</banner_bytes></scanner><scanner name="BannerTCP" port="5480" portprobe="vmapp" protocol="tcp" result="refused" service="vmapp_https"/><scanner name="BannerTCP" port="9443" portprobe="vmapp" protocol="tcp" result="refused" service="vmapp6_https"/><scanner name="BannerTCP" port="902" portprobe="esxi" protocol="tcp" result="refused" service="ESXi"/><scanner name="NBT" port="137" portprobe="wins" protocol="udp" result="refused" service="ms-nb-ns"/><scanner name="GenericTCP" port="135" portprobe="wmi" protocol="tcp" result="refused" service="epmap"/><scanner name="SLP" port="427" portprobe="slp" protocol="udp" result="refused" service="slp"/><scanner name="DNS" port="53" portprobe="dns" protocol="udp" result="unresolved" service="dns"/><scanner name="GenericTCP" port="5989" portprobe="wbem" protocol="tcp" result="refused" service="wbem_https"/><scanner name="HTTP" port="443" portprobe="http" protocol="tcp" result="open" service="https"/></result>CauseDiscovery schedule has a field "Use SNMP version" set to 'v1/v2c'ResolutionIn the discovery schedule, set the field "Use SNMP version" to 'All'