Jun 15, 2011 12:42 PM
Bad Counter on Device
-
Like (1)
I am new to Zenoss, so please bear with me - I just started with an organization that has a Zenoss 3.1 setup. Part of my initial tasks here are to dig through the monitoring systems and find errors I can fix.
However, I'm constantly coming across these errors (or errors like it):
Bad counter for device 10.3.84.60: \\Network Interface(BASP Virtual Adapter)\\Packets Sent/sec
Bad counter for device 10.3.84.60: \LogicalDisk(\\?\Volume{eebbb153-e36b-11df-85a7-806e6f6e6963})\Free Megabytes
I know I've probably missed giving some information, so please let me know what I can fill in here, and I will do so.
Zenoss | Zenoss 3.1.0 |
OS | Linux (x86_64) 2.6.18 (Linux 2.6.18-194.el5 #1 SMP Fri Apr 2 14:58:14 EDT 2010 x86_64) |
Zope | Zope 2.12.1 |
Python | Python 2.6.2 |
Database | MySQL 5.0.77 (Ver 5.0.77) |
RRD | RRDtool 1.3.9 |
Twisted | Twisted 8.1.0 |
NetSnmp | NetSnmp 5.3.2 |
PyNetSnmp | PyNetSnmp 0.28.14 |
WMI | Wmi 1.3.13 |
Any idea? I'm trying to track down the BASP adapters by getting proper counters in perfmon, but I am at a loss for the bad counters.
Any advice? Things to try?
I found I can't get the BASP adapter to show up in Perfmon, (No WMI counter). See this post: http://forum.broadcom.com/showthread.php?35-Monitoring-BASP-Virtual-Adapter-in-Perfmon
At this point, I'm thinking we have some sort of configuration problem. Can anyone point me to the right documentation? We have these bad counters on a great many of the devices we monitor.
I'm stummped. Does anyone have any suggestions?
Hate to bump this, but has anyone ran into this before? If so, what have you done to resolve this?
I'm fairly certain it is due to a configuration problem, but I don't know where to start.
Working with Zenoss support, we eventually came up with a solution.
Some of the bad counters were due to monitoring devices that really didn't need to be (or couldn't be) monitored. (Eg. BASP adapters have no perfmon counters, so they cannot be monitored properly. The 100MB logical disk that comes on some systems also is not necessary.)
Support suggested those counters get dropped automatically.
Go into: http://zenoss_server:8080/zport/dmd/Events/Status/Wmi/eventClassStatus and click the gear icon in the bottom left. Click Transform.
This is the transform script I used to drop my bad counters. Note, some of these bad counters (I feel) come from someone incorrect WMI monitoring templates (AKA using Exchange 2007 monitoring templates to monitor Exchange 2010).
if evt.summary.startswith("Bad counter for device"):
if evt.summary.endswith("Active Sessions"):
evt._action = "drop"
if "Microsoft Failover Cluster Virtual Adapter" in evt.summary:
evt._action = "drop"
if "SQLServer" in evt.summary:
evt._action = "drop"
if "LogicalDisk" in evt.summary:
evt._action = "drop"
if "Web Service" in evt.summary:
evt._action = "drop"
if "BASP Virtual Adapter" in evt.summary:
evt._action = "drop"
if "MSExchangeTransport Queues" in evt.summary:
evt._action = "drop"
if "SMTP Server" in evt.summary:
evt._action = "drop"
if "MSExchangeIS" in evt.summary:
evt._action = "drop"
if "Paging File" in evt.summary:
evt._action = "drop"
if "Could not read the Windows" in evt.summary:
evt.severity = 5
Modify the script for your needs. This script will only drop events that have the Bad Counters, not other valid alerts.
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||