Sorry to be so long getting back on this.

In general, the modeler appears to be finding all the interfaces that
are present, active or inactive, but zenperfsnmp only appears to be
creating device directories for active Ethernet interfaces.  I am
getting performance information for those Ethernet interfaces, so I
guess I need to know how to get zenperfsnmp to pay attention to the
serial ones.

Thanks,

Matt

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric Newton
Sent: Monday, August 28, 2006 1:15 PM
To: General discussion of using zenoss system
Subject: Re: [zenoss-users] creating missing RRD files

Hi Matt,

zenperfsnmp creates the files when it is told to collect on them.  The 
real question is: why doesn't zenperfsnmp collect on those interfaces?

When the device was modeled, was the interface up?  Zenoss does not 
collect on dead interfaces.
I don't think Zenoss will collect statistics on the loopback interface, 
either.

Do these interfaces have anything else in common?  Are the interfaces 
providing performance details?  Are there any suspicious messages in 
zenperfsnmp.log?

-Eric

Wilbert, Matt (ENV*) wrote:
> I am currently testing zenoss with only a few devices, but I am
finding
> that although Zenoss seems to find all of the interfaces when I add a
> device, it doesn't necessarily create RRD files for all the
interfaces,
> and then (unsurprisingly) I don't get statistics for all of them.
>
> What is the canonical way to create missing RRD files?
>
> Thanks,
>
> Matt
>
> _______________________________________________
> 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



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

Reply via email to