How Zendisc operates

FIXME, make sure paragraphs flow and match, they are from different locations. Zendisc is a subclass of zenmodeler and it goes out to discover new network resources. It walks the routing table to discover the network topology and then pings all discovered networks to find active IPs and devices.

Zendisc is not truly a daemon, in the unix sense and should never be running as so. Zendisc is run usually in response to a user interaction, say adding a device, or scanning a network for devices (auto-discovery).

For example, when you go to discover devices on a network, zendisc is run across that network. During that run, zendisc enacts a ping sweep of the network. Modeling is run on each device that replies to the ping-sweep. Eventually, zendisc stops.

How Zenmodeller operates

FIXME, make sure paragraphs flow and match, they are from different locations. ZenModeler iterates over the list of devices in the system and attempts to discover sub-components – such as network interfaces, file systems, process, and IP services – of each device.

ZenModeler is a configuration collection and configuration daemon. It is used for high-performance, automated model population using SNMP, SSH, Telnet, and WMI to collect its information. Zenmodeler works against devices that have been loaded into the DMD.

Modeling is separate and different from monitoring. Modeling is often done when you first add a device, and subsequently twice a day (by default). The daemon does not act like a daemon in the unix sense. Zenmodeler is running all of the time, but it is not doing something most of the time. Again, it re-models twice a day by default, and runs in the background the rest of the day doing nothing.

technology/zenoss/about/zendisc_vs_zenmodeler.txt · Last modified: 04.01.2009 13:34 by nyeates1
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki