Ok, I may not be 100% clear on what your asking but I think I have the general idea.
Here's what I've learned so far about Zenoss and monitoring ports. There seems to be 2 ways to do it. With snmp and the zenoss.snmp.IpServiceMap and with a portscan using zenoss.portscan.IpServiceMap. You'll need to look in the zProperties of the device/class you are using and make sure you are using the collector plugin you want. I'm not 100% sure on the functional differences between the plugins but I'm guessing the snmp one trusts that snmp really knows that the port is open and the portscan one does a real tcp check. (someone should correct me if the snmp one does a tcp check as well) Anyway if your not using snmp for modeling on the device then you don't want to use the snmp collector. I believe it is used by default. If you are using snmp then once you add it to your services and tell it to monitor you should be able to remodel the device and have it show up. If the one plugin is not working you might try the other. Either way the device needs to be remodeled in order to pickup the port to be monitored. Also, since Zenoss uses this modeling behavor the port has to be there when you model the device otherwise it won't believe that you want to really monitor a port that isn't active. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=16826#16826 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
