David,
If you have a cisco where the config hasn't changed you should use --
force to make it remodel. KeyErrors may be an issue as well.
-EAD
On Jan 19, 2007, at 5:33 PM, David Carmean wrote:
Sorry, I was unclear. I has trying to figure out why a value I set
for an existing, stock zProperty was not "working" even after
remodeling.
I think the answer is that I needed to use the --force switch in a
manual
zenmodeler run; either that or these KeyErrors I reported caused
the remodels
to fail.
On Thu, Jan 18, 2007 at 05:57:56PM -0500, Ian McCracken wrote:
Check out the final part of these instructions on the wiki:
http://dev.zenoss.org/trac/wiki/HowToAddAZProperty
You just need to write and run a migrate script to take care of the
devices you've already got.
David Carmean wrote:
I've added a zInterfaceMapIgnoreNames regexp to ignore Cisco
unrouted
VLANs, but this is only taking effect for new device additions or
if I
manually re-collect configuration info for a device. (I did this
two
weeks ago.)
I was hopeing a manual zenmodeler run starting at the node where
I applied
this property would go through and remove all of the unrouted VLAN
interfaces in that subtree, but it hasn't.
I've got at least 200 devices that I need to make this change
for. What
am I missing?
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
--
David Carmean Network Appliance, Inc
Infosystems Architect, 495 E. Java Drive
Java (Sunnyvale) Engineering Lab Services Sunnyvale, CA 94089
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
