The ip service has to be accessible when Zenoss tries to model it, or it
needs to be locked, otherwise the modeler determines that ip service
isn't on that server and removes it. Do you usually have the IP services
down at a certain time? It may coincide with Zenoss's 12 hr remodel
cycle. In which case locking would be the right thing to do.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
captainmish wrote:
Hello
I have a few servers to monitor, and want to monitor some ip services on these.
I add the services and they work fine for a while, but are eventually deleted.
After some reading, it seems that they are deleted on a remodel. How can I stop
this from happening?
I have tried to lock the services, so this seems like it will work, but I would
like to know why I need to lock them in the first place. Do I need to add
something to the servers' snmp configs to say I want this monitored? Is zenoss
attempting a connection to the actual port on the server (which is what I
assumed), or is there some snmp that gives it this info?
Cheers,
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=18914#18914
-------------------- 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
