This may sound like a silly question but what I am attempting to do is enable Ping Only as a starting method of monitoring devices. Now, this may be because I do not understand enough about how Zenoss works but it appears to not be doing it on devices as of right now. But when I look in Networks on the autodiscovered devices I see that there are devices there that are being pinged and attempted on monitoring through SNMP but I really am only interested in monitoring at the very basic level of ping or some other TCP connectivity test ALL devices that I have in /devices.
The thing is that I need to start here. I am more towards monitoring Network Devices, not servers. So I want to start as a proof of concept on the very basic use of Ping to test connectivity before I move onto SNMP querying. Why? Because I will have to do a lot of Mib customization since these are not Cisco devices. Does that make sense? Does it monitor via ping all devices in /Devices, or do you have to enable that? Ryan W. Davis - Network Systems Analyst Data Network Planning and Support - Division of IT (http://iatservices.missouri.edu/) University of Missouri (http://www.missouri.edu/) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Duncan McGreggor Sent: Monday, February 05, 2007 11:35 PM To: General discussion of using zenoss system Subject: Re: [zenoss-users] Ping-only, Portscan-only monitoring On Feb 5, 2007, at 8:31 PM, Davis, Ryan W. wrote: > Okay, so is the Admin Guide 1.1 the same as the Admin Guide 3.2 you > are > speaking of? I looked through the admin guide on the website and was > unable to find a version number besides 1.1 to compare. You have the right version number ;-) Erik was referring to the *section* of the Admin Guide, though -- not the version number. > As for the portscan. I am kind of confused right now as to the actions > made by the portscan function. Is there a similar "ping" function that > you can put in zTransportProperties? Will it invoke the zenPing > module? > If not does this portscan function do a full portscan every time? > If so > this might seriously set of some IPS devices we have scattered > throughout our network. > > All I am looking for is to begin with simple icmp echo-reply > functionality at first to verify ICMP connectivity. Later on I will > move > onto SNMP polling but since we are a non-Cisco shop it is going to > take > a lot of Mib loading to get everything situated. I may have misinterpreted what you are asking, but maybe this will clarify: * the portscan functionality is for "modeling" or "discovering" services running on your network, and shouldn't be run very frequently (e.g., only when your network changes) * Zenoss does not use portscan for host availability checking -- it uses zenping for that Again, please forgive if I have misunderstood your question. d _______________________________________________ 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
