![]() |
![]() |
Subject: | Remote Network Discovery Finding IPs But Not Devices - Zenoss Core |
Author: | Garrett Michael Hayes |
Posted: | 2015-01-13 14:59 |
I'm having a problem with discovery on network segments other than the segment where Zenoss sits.
I did a new install of
Zenoss Core 4.2.5
on CentOS 6
on a virtual guest
under a Win 2012 Hyper-V machine
Used the auto installation script.
Generally speaking it's working as I recall from a previous environment (where I used Zenoss, but did not install/configure it).
The initial install discovered and identified most of the systems I was expecting to see on the network segment where Zenoss sits (10.0.1.0/24)
The problem I'm having is that it doesn't seem to be able to discover anything but IP addresses on remote network segments. We have four remote locations: two reached by site-to-site VPN's, and two reached by Ethernet virtual circuits.
When I add one of those address spaces to Infrastructure | Networks and then do a "Discover Devices" job, Zenoss finds the IPs I expect, but nothing about the devices at those addresses. If I manually add a device pointed to one of those IPs, then Zenoss can model it just fine (provided I've set up SNMP, etc.)
I'm just not sure if there's something blocking Zenoss full discovery, or if I've configured something wrong. Not looking for someon to solve it for me - just maybe a pointer as to where to look for the problem. (And don't bother saying "in the mirror" - that part I already know! [grin])
Subject: | Remote Network Discovery Finding IPs But Not Devices - Zenoss Co |
Author: | [Not Specified] |
Posted: | 2015-01-14 08:12 |
Garrett,
Would start by looking at advanced->jobs and see exactly what is running when you execute the discovery and what the output is. If you need more, you could take the command and execute on cli with verbose enabled to get more information.
Sounds like modeling is either not enabled or default access credentials/community strings are not setup correctly in device class devices are getting added too.
--Rob
Subject: | I never tried doing a |
Author: | [Not Specified] |
Posted: | 2015-01-16 15:47 |
I never tried doing a discovery by adding a network in Infrastructure->Network.
It seems to me what what you want to do is go to Infrastructure->Devices, click the + at the top of the devices pane (not the + at the bottom of the column of device types - i mean the one that looks like a computer monitor with a plus on it), and then choose "Add Multiple Devices".. Then choose button "Autodiscover Devices" and fill in your IP address ranges and SNMP creds.
Subject: | Remote Network Discovery Finding IPs But Not Devices - Zenoss Co |
Author: | Garrett Michael Hayes |
Posted: | 2015-01-16 15:53 |
I guess I'll give that a whirl - the next time we add a new network segment ;)
For the moment, it's about where I want it, so I think this calls for an instance of blind faith and fast feet.
Thanks again for the input!
Subject: | Dpirmann is correct, adding a |
Author: | [Not Specified] |
Posted: | 2015-01-19 07:05 |
Dpirmann is correct, adding a network does not discover a device. As for the question on re-discover, yes zenoss will 'remodel' the devices periodically to see if modeling data has changed.
--ROb
< |
Previous thresholds do not seem to be working |
Next zenup for zenoss 5 |
> |