Unable to discover Switches

will_forster
Tera Guru

I am able to discover switches in our servicenow dev envionment however i have the exact same configuration on TEST but when a shazam probe is sent out it is missing the snmp credentials on the output xml.

IN DEV it includes the following line i require.

 

 <parameter name="credential_id" value="<ip_address_credential><parameter name="10.10.10.10" value="ebd2aed51b4cd2909ff899b2b24bcbb5"/></ip_address_credential>"/>

 

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<parameters>
<parameter name="port_probe_spec" value="<portprobes><portprobe><name>wmi</name><scanner>GenericTCP</scanner><description>Windows WMI</description><conditional>false</conditional><service><name>epmap</name><port>135</port><type>TCP</type></service></portprobe><portprobe><name>snmp</name><scanner>SNMP</scanner><description>Simple Network Management Protocol</description><conditional>false</conditional><service><name>snmp</name><port>161</port><type>UDP</type></service></portprobe><portprobe><name>ssh</name><scanner>SSH</scanner><description>Secure Shell Login</description><conditional>false</conditional><service><name>ssh</name><port>22</port><type>TCP</type></service></portprobe><portprobe><name>http</name><scanner>HTTP</scanner><description>Web Servers</description><conditional>false</conditional><service><name>http</name><port>80</port><type>TCP</type></service><service><name>https</name><port>443</port><type>TCP</type></service></portprobe><portprobe><name>wins</name><scanner>NBT</scanner><description>WINS Name Resolver</description><conditional>true</conditional><service><name>ms-nb-ns</name><port>137</port><type>UDP</type></service></portprobe><portprobe><name>dns</name><scanner>DNS</scanner><description>Domain Name Resolver</description><conditional>true</conditional><service><name>dns</name><port>53</port><type>TCP/UDP</type></service></portprobe><portprobe><name>slp</name><scanner>SLP</scanner><description>Service Location Protocol</description><conditional>false</conditional><service><name>slp</name><port>427</port><type>TCP/UDP</type></service></portprobe><portprobe><name>wbem</name><scanner>GenericTCP</scanner><description>WBEM (CIM)</description><conditional>false</conditional><serviceRegistryQuery querierClassname='SLPQuery'><serviceType>service:wbem</serviceType></serviceRegistryQuery><service><name>wbem_https</name><port>5989</port><type>TCP</type></service></portprobe><portprobe><name>vmapp</name><scanner>BannerTCP</scanner><description>vCenter Server Appliance Web user interface HTTPS</description><conditional>false</conditional><service><name>vmapp_https</name><port>5480</port><type>TCP</type></service><service><name>vmapp6_https</name><port>9443</port><type>TCP</type></service></portprobe><portprobe><name>winrm</name><scanner>HTTP</scanner><description>Windows Remote Management/HTTP</description><conditional>false</conditional><service><name>winrm</name><port>5985</port><type>TCP</type></service></portprobe><portprobe><name>winrm_ssl</name><scanner>HTTPS</scanner><description>Windows Remote Management/HTTPS</description><conditional>false</conditional><service><name>winrm_ssl</name><port>5986</port><type>TCP</type></service></portprobe><portprobe><name>esxi</name><scanner>BannerTCP</scanner><description>ESXi Server Appliance web user interface</description><conditional>false</conditional><service><name>ESXi</name><port>902</port><type>TCP</type></service></portprobe></portprobes>"/>
<parameter name="mid_selector_details" value="{"mode":"specific_mid"}"/>
<parameter name="used_by_runbook" value="true"/>
<parameter name="debug" value="false"/>
<parameter name="glide.xmlhelper.trim.enable" value="true"/>
<textnode_parameter name="range">{"meta":[["10.18.93.36"]]}</textnode_parameter>
<parameter name="range_index" value="0"/>
<parameter name="shazzam_probes" value="1"/>
<parameter name="HTTP_waitForResponseMS" value="5000"/>
<parameter name="json_ranges" value="true"/>
<parameter name="probe" value="eb95df760ab301550015543188996362"/>
<parameter name="TLS_keepOriginalCertificate" value="false"/>
<parameter name="mid.discovery.max_payload_size" value="-1"/>
<parameter name="GenericTCP_waitForConnectMS" value="3000"/>
<parameter name="used_by_discovery" value="true"/>
<textnode_parameter name="full_range">{"meta":[["10.18.93.36"]]}</textnode_parameter>
<textnode_parameter name="mid_range">{"meta":[["10.18.93.36"]]}</textnode_parameter>
<parameter name="probe_name" value="Shazzam"/>
</parameters>
1 ACCEPTED SOLUTION

will_forster
Tera Guru

Hi.

This is now resolved !

For some reason a VAST number of switches were not getting SNMP credentials they needed.
Instead it was defaulting to UNIX Probes !
Building an SNMP only Behavior and applying it to the schedule resolved this issue.

View solution in original post

10 REPLIES 10

switched on and using quick discovery.

 

update

 

its discovering devices now but a fraction of the amount compared to DEV

sorry didnt get you. what was 'switched on' ? I was referring to not use 'public' SNMP credential.

sorry i meant it was switched off and using custom snmp v3 credentials

Community Alums
Not applicable

Hi, 

 

1)please check if snmp port is open on port 161 on Shazzam probe input payload. 
2) check MID server Ip ranges are correctly assigned 

3)check if snmp  credentials are applied to all mid Servers or specific mid server 

 

Regards, 

srinija

will_forster
Tera Guru

because no credentials are being captured in the XML payload no SNMP Probes are being sent out to classify anything