On Apr 30, 2009, at 7:25 PM, scratchspace wrote:
> I have several servers with aliased IP addresses for DNS, Sendmail,  
> etc. This allows the services to be moved to other servers if needed  
> for capacity without DNS record changes.
>
> During discovery, these host IP addresses were picked up as if they  
> were full hosts. While I'd argue that ZenOSS should have been able  
> to figure this out given the common MAC addr, this is tolerable  
> behavior.
>
> For these virtual IP address, I un-bound the Linux device template,  
> and bound appropriate templates (DigMonitor), or added specific IP  
> Service monitors. I also deleted all of the profiled information on  
> the OS tab, as I don't want multiple alerts when the primary host  
> has a disk space issue for example.
>
> Unfortunately every night this information magically re-appears. I  
> even tried locking each item from updates, but this setting is  
> blatantly ignored, or so it seems.
>
> An additional annoyance is that Apache is detected under OS  
> Processes as "/usr/sbin/httpd" and "httpd". The latter is always in  
> an error status, and this annoyance is preventing me from going into  
> production with ZenOSS.
>
> Can someone explain how to disable this auto-remodeling of the  
> devices. Any ideas why the second erroneous httpd process appears?

I'm surprised that these devices were discovered as separate devices.  
Normally the zenoss.snmp.InterfaceMap would find all of the IP  
addresses of the first devices when it was discovered, and the second  
two would be skipped since they were already in the system.

This issue aside, you can prevent Zenoss from remodeling devices in a  
couple of ways. The first, and probably best option for you would be  
to "lock" the device from updates. This will keep any modeling from  
changing it. The second option would be to remove any plugins from  
zCollectorPlugins that you didn't want running for the device. This  
would allow you to selectively disable the InterfaceMap or HRSWRunMap  
(for processes.)
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to