Zenoss 2.4.1 on SuSE 10.3. It appears impossible to monitor udp services for a device. If you try and activate a udp service, either by using the Add IpService drop-down from a node's os tab, or by unticking the Monitored tab against a devices services and choosing a udp service and then using the drop down to select Monitoring and clicking the radio button to Enable, you get the same result - your action is ignored. You end up with either your configuration of the udp service ignored, or possibly with the service listed but no green/red (or even grey) bubble against it's status (the latter scenario may be prior to Zenoss 2.4).
Looking at the code, it would appear to be impossible to monitor udp. $ZENHOME/Products/DataCollector/plugins/zenoss/snmp/IpServiceMap.py is the collector plugin enabled by default for servers and this appears to work fine - it collects tcp services by asking for the MIB-2 tcptable 1.3.6.1.2.1.6.13.1.1 - the final .1 is getting the state of a tcp service. udp service collection also uses MIB-2 to get 1.3.6.1.2.1.7.5.1.1 - the final .1 gets the address that a udp service is running on. These tables only return values for those ports that actually have tcp / udp services active and they both seem to work correctly. Note that the IpServiceMap.py collector plugin in $ZENHOME/Products/DataCollector/plugins/zenoss/portscan ONLY appears to address TCP services, not UDP - this portscan collector plugin is not activated by default for a server. So, data collection works for tcp and udp with the snmp IpServiceMap data collector. However, look at $ZENHOME/Products/ZenModel/IpService.py . This is where the class for IpService is defined with its attributes and methods. Here we find a method called cantMonitor which can prevent monitoring being activated. It returns "False" if the protocol is udp or if there is only 1 address being monitored and that is 127.0.0.1. I believe it is this that is preventing monitoring of any udp services. I have not tried modifying this code yet. Does anyone know why this cantMonitor method inhibits udp monitoring (I have to assume there was a good reason at some time)???? Anyone tried changing it?? Any advice gratefully received. Cheers, Jane -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=36716#36716 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
