On 12/19/06, David Carmean <[EMAIL PROTECTED]> wrote:
I ran into an unpleasant side-effect of the way Zenoss chooses RRDTemplates for interfaces, today. I wanted to graph data for Cisco Port-Channel interfaces, so I copied the ethernetCsmacd template and created one named propVirtual, as that's how the Port-Channel interfaces showed up in SNMP. This also picked up the VLAN interfaces, but unfortunately it also picked up "unrouted VLAN" interfaces, for which all the SNMP queries fail with "oid .. is bad". I've since disabled that template. This has caused my status table to fill up and generally crash zenperfsnmp, which I suspect may get cleaned up when I upgrade to 1.0.x tomorrow. It looks like the safest thing to do might be to use local RRDTemplate copies for each such Port-Channel interface I want to monitor, but I don't want to create them by hand each time. Is there any way I can "import" a template into the local propVirtual template for one interface?
David, I ran into this same problem. The solution is as easy as adding "unrouted VLAN" to zInterfaceMapIgnoreNames to the zProperties of /Devices/Network. Recollect the device after this, and your unrouted VLAN interfaces will no longer be monitored. -- Chet Luther [EMAIL PROTECTED] _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
