Have the Red Hat install up and running in VMware. Ran discovery. I am testing credentials on the discovery tab that I have setup. I cannot get Treadway to discover any servers with the SNMP setup we have. I put in the IP address and public string we use, but will error out on any server I try. I have confirmed that the SNMP string works. I can challenge that against Solarwinds. All ips I am testing are pinagable from the RedHat demo VMware instance as well. I have installed a Windows Credential discovery slave and Active Directory discovery slave as well. Both slaves are showing up as being connected. Any pointers on how I may have screwed up?

Hi Adrian,
What type of server are you trying to discover? When you were setting up the SNMP credentials did you follow the Configuration Guide (page 105, “Setting Up the SNMP Credentials”)?

Can you navigate to the Discovery page, then click on the Credentials button and click on the “SNMP Credentials” tab. Then click the Test link for the relevant credential and enter the IP address for one of the servers that are failing. Does this test succeed? If not what is the error message returned?

Can you confirm which version of Foundation you are using? I am assuming the downloaded Community Edition?

A couple of other bits of information that might be of help to you.

Credential Key Regex
Discovery looks up which credentials it has available by matching the IP of the endpoint it is attempting to contact via a regex shown in the “Key Regex” column. If you have a single network wide credential then ensure you have .* in that field so it is tried every time.

If you are used to using CIDR notation like ’192.168.3.0/24’ or a range like ’192.168.3.0-255’ this may have tripped you up, you would need ’192.168.3.*’ in the Key Regex in this example.

(We can accept both these notations when adding a run to scan, just not for matching credentials)

SNMP Requirements
If you want to do a full discovery of a host via SNMP then we need to get certain key bits of data. I’ve attached a screenshot showing the MIB/OID values we need. (This screen shot is from our next edition so will not be in the version you are currently using – the details are the same)

You will note that getDeviceInfo, getHostInfo and getInterfaceList all have a small red star – we need the values for these three methods to succeed so we can create an inferred Host in our data model. If we only get partial success of these three then the data is listed under the Discovery Access but no further action is taken.

Hopefully that helps you get going. If you haven’t found it the configuration guide Dave is pointing you to is available from the web UI, just click on the green ? and go to Documentation.

Let us know how you get on!

this was handled over the phone,

The issue that Adrian ran into was that we did not have access to one of the required OIDs to create a host.

a little more background:

in order to create a host item in the Tideway datastore we require certain bits of information to validate that it is actually a host at the other end.

When Adrian connected to the target device he was not able to bring back a crucial piece of information from the OID, therefore we did not create the host.

OID stands for Object IDentifier, basically its a way of referencing different parts of a device as if they had phone numbers.

example: the OID .1.3.6.1.2.1.25.2.2.0 tells us how much memory a system has, if a system has no memory its likely not a host.