Couple of things here.  Even having applied the patch and run zenmigrate and 
restarted Zenoss, I don't see the extra option under zProperties for networks.  
What I DO see is that the command line alternative, zendisc, now has a 
--snmp-strict-discovery flag which possibly does achieve the right effect.

Like Matt, my background is in NetView / OpenView which automatically runs a 
new node discovery process periodically.  I don't believe Zenoss does that.  If 
you want a "periodic discovery" then you need to create a script using zendisc 
and stick it into cron.  

Finding the right zendisc parameters I am also finding problematical (Zenoss 
2.3.2).  The --walk option is supposed to walk everything but only seems to go 
to the next set of routers often (even with zAutoDiscover set to True).  I have 
some subnets subnetted to 28 bits so I have used the --subnets parameter but 
that doesn't seem to have the right effect.  The --assign-devclass-script 
parameter looks ideal to address Matt's concerns about automatically allocating 
devices to device classes - but if you read the code in zendisc.py it says this 
is broken and - indeed - it doesn't seem to work.

However, for devices that HAVE been discovered (aka already in the Zenoss 
CMDB), then the zenmodeler process will run all the assigned collector plugins 
- zenmodeler runs every 12 hours by default.  This is the equivalent of the 
NetView / OpenView Configuration poll but it does rather more.

To address the "how do I automatically allocate new devices to device classes" 
question, I have crafted a solution and documented it at 
http://www.zenoss.com/Members/jcurry/auto_disco_paper.pdf/view 
It is very early days for this so I would appreciate feedback but it seems to 
be having the right effect so far.

BTW - the other enticing red herring for auto-allocation to device classes is 
to configure zProperties for the Hardware Model (which is typically the OID 
automatically picked up by the SNMP data collector plugin).  There are 
zProperties to set zDeviceClass, zDeviceGroup and zSystem but the 2.3.2 
Administration Guide says these are for future use and they certainly don't 
seem to work for me.

Feedback on  the paper to me please at [email protected] and to the 
forum here.

Cheers,
Jane

PS. Please note we will be away from Feb 16 - March 16 so please bear with me - 
I'm not simply ignoring any feedback!




-------------------- m2f --------------------

Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=31231#31231

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to