Well, first, make sure the dns lookup for the device that you provide 
goes to the right place. Then, try just entering the IP yourself in the 
Add Device page. See if using that page with discovery set to none works.

Otherwise, I'm at a loss - it's "just worked" for me, though I haven't 
used AutoDiscover, so if that's the issue, it could well be doing 
something else like trying SNMP to figure out what the device is.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University



macscr wrote, On 4/27/2009 12:58 PM:
> Yes i did try those. The /Ping device class comes with the system by default, 
> which i tried. Still gives the same error. It also appears that it still 
> keeps trying to add the device (according to the browser, the page is still 
> loading). I basically have to restart the zenoss appliance to get it to even 
> stop so can visit the dashboard again to see whats going on.
> 
> EDIT: even though it stalled out a few more times and gave those errors, it 
> appears that it finally added, but the ip associated with the hostname i gave 
> is not related at all. No idea where it even got the IP. And i dont even see 
> where i can edit the IP associated with the device. 
> 
> Either way though, the process you guys are describing is not working 
> correctly on my system. Any ideas what i should be looking for?
> 
> 
> 
> 
> -------------------- m2f --------------------
> 
> Read this topic online here:
> http://forums.zenoss.com/viewtopic.php?p=33914#33914
> 
> -------------------- m2f --------------------
> 
> 
> 
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to