On Jun 20, 2008, at 8:39 AM, imobrien wrote:
I did a clean install of 2.2, and since then I keep getting the
following errors off my core switch:
Error reading value for "unrouted VLAN 216" on Core (oid .
1.3.6.1.2.1.2.2.1.20.256 is bad)
Off my routers I have been getting the following:
Error reading value for "T1 0/1/0" on C2851 (oid .
1.3.6.1.2.1.2.2.1.16.6 is bad)
Error reading value for "T3 1/0" on 3745 (oid .
1.3.6.1.2.1.2.2.1.16.4 is bad)
Any ideas? It seems to be pulling all of the other data from the
systems with no problems.
This isn't a new error condition. It is just something that wasn't
previously being reported. Now anytime zenperfsnmp tries to poll an
OID that doesn't exist, an event like this will be created. There are
probably two different reasons for the VLAN and T? errors.
unrouted VLANs on Cisco devices don't report error counters, which is
what .1.3.7.1.2.1.2.2.1.20.* is. I would recommend not even monitoring
unrouted VLAN interfaces. You can set this up by adding "^unrouted
VLAN" without the quotes to the zInterfaceMapIgnoreNames zProperty for
the /Network/Router/Cisco device class.
The errors on the T1 and T3 interfaces are referring to the
ifOutOctets counter. This one is a bit less clear cut as I believe
that these interface types should expose this counter. I would
recommend remodeling both of those devices and moving the events to
history. It may be an issue with the SNMP indexes of interfaces on
that switch changing since the last time they were modeled.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
