I've cleared up another issue which was proving to be a bit of a roadblock (ie, KeyError).
So now I'm back looking at this. I'm still having the same issue. But maybe my question was a bit unclear. Let me try again: When I add a new TCP port to be monitored under /Services/IpService and am sure to enable it, what should the expected effect be vs. all the devices I already have in Zenoss? a) Pure magic. That port will automatically start getting included with the subsequent checks of each device. For those machines where you don't have anything listening on that port, you'll need to drill into the OS settings and disable it. b) Nothing. In order to actually use it, you'll have to go into every machine you want this enabled on (in the OS tab) and add it by hand. Slow and painful, but you'll get there eventually. Of course, if I've completely missed something which the more experienced know about, please share. :) -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=16818#16818 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
