I'm afraid not. We're finalizing 2.4 right now and this one doesn't have a
satisfactory fix yet. For now, I can give you a workaround to make sure that
the condition method on this modeler plugin returns True so that the plugin
will run on the next modeling sequence.
Let's say your devices are in the /Network/Cisco device class. Run "zendmd" as
the zenoss user and paste in the following code snippet. This will reset the OS
and hardware information for the device.
Code:
for d in dmd.Devices.Network.Cisco.getSubDevices():
d.setOSProductKey("")
d.setHWProductKey("")
commit()
Be sure to hit enter a couple of times after the commit() to be sure that it is
executed. You can then type CTRL-D to exit the zendmd shell. Now you should
re-run the NewDeviceMap for all devices in the Cisco device class. You can do
this with the following command. Again, run as the zenoss user.
zenmodeler run --now --path=/Devices/Network/Cisco --collect=NewDeviceMap
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=34180#34180
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
