Adding the additional template solved the problem for me. I removed the broadcast variables from the new template, and things are working nicely.
I'm finding Zenoss to be very helpful--I had actually written my own Zope-and-RRD based network monitor a long time ago, but yours is a lot slicker. Matt -----Original Message----- From: [EMAIL PROTECTED] on behalf of Eric Newton Sent: Wed 9/13/2006 3:27 PM To: General discussion of using zenoss system Cc: Subject: Re: [zenoss-users] zenperfsnmp problem Ok, here are the instructions. It turns out to be fairly easy. Go to your device, select OS, and select one of the serial interfaces you want to monitor. Under "type" you should see something other "ethernetCsmacd". Use your mouse to copy that name. Let's assume the name is "serialInterface". Now select "Devices" from the left-hand side links. Select PerfConf. Select the box next to "ethernetCsmacd" and then press the Copy button at the bottom. Press the "Paste" button that should now be next to the Copy button. This makes "copy of ethernetCsmacd". Select that item. Change the name from "copy of ethernetCsmacd" to your device type. In this example, you would simply use the mouse to paste in the name you copied above (my "serialInterface", but using the name you saw for the interface type). If some of those data sources are not available (broadcast packets may not be available on a serial device, for example), you can make device-specific modifications to this configuration. -Eric Wilbert, Matt (ENV*) wrote: > Eric, > > The interfaces are up, and are shown as up. Should I try your script > anyway? > > Matt > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Eric Newton > Sent: Wednesday, September 13, 2006 1:15 PM > To: General discussion of using zenoss system > Subject: Re: [zenoss-users] zenperfsnmp problem > > Hey Matt, > > By default, Zenoss will not monitor interfaces that are down when the > device is modeled. > > Here's a script that will force all the interfaces to be modeled as up; > > Start the zenoss Data Model Database command-line tool: > > $ zendmd > Welcome to zenoss dmd command shell! > use zhelp() to list commands > >>> d = find('my-device-name') > >>> for i in d.os.interfaces(): > ... i.operStatus = 1 > ... i.adminStatus = 1 > ... > >>> commit() > > Alternatively, you could bring the interfaces up (by using them) and > remodel the device. > > -Eric > > > Wilbert, Matt (ENV*) wrote: > >> Hi, >> >> I have asked about this problem before, but I haven't seemed to be >> > able > >> to get to the bottom of this problem. I have some router devices set >> > up > >> in Zenoss. All their interfaces seem to be modeled when I add them, >> > but > >> I am only getting performance information for Ethernet interfaces--the >> serial interfaces show up in the model, but they no RRD files are >> created for them, and (naturally) they don't show any performance data >> when you select them. >> >> I don't see any errors in the zenperfsnmp log with respect to these >> devices, either immediately after they are created or when they are >> collected. >> >> Do you have any suggestions on how I can get it to recognize the >> > serial > >> interfaces as needing collection? FYI, this is 0.21.1. and the >> collection/graphing for the Ethernet interfaces looks fine. >> >> Matt Wilbert >> _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
<<winmail.dat>>
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
