cluther wrote: > > > > > > for device in dmd.Devices.getSubDevices(): > > > for interface in device.os.interfaces(): > > > interface.monitor = False > > > > > > commit() > > > > > > > > > Is this inherently more efficient than just creating an empty > > ethernetCsmacd > > template? ( I copy the originals to a new /Devices/tmp organizer > > for safety, > > and then delete the objects from the original. ) > > > > I guess my technique may not live through upgrades. > > > > Wouldn't it be a good idea to lock the above? Won't a re-model set > > them to > > be monitored again? > > > > I think that removing all of the data sources, threshold and graphs > from your ethernetCsmacd template is a better way to go. Modeling the > interfaces won't change their monitored status. > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users
Okay. I've tried removing the data sources, threshold and graphs from the ethernetCsmacd template and it works. Now I have a new problem. I copied the original ethernetCsmacd to the Network class and renamed it to PortMonitor. I moved my test switch into the Devices/Network/Switch class. When I try to bind PortMonitor to my test switch I get a washed out screen with a bar in the middle that doesn't do anything. I am running Zenoss 2.1. David ------------------------ David Hart -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=12120#12120 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
