Need some more information.

Version of Zenoss you have running?

List what modeler plugins you have installed?

After your restart did you see the graph update for the high disk usage?

Jay,

Try running the same WMI command with the IP address instead of hostname.

If you get the same successful result, check out the event logs for any failures to connect.

If you see nothing in the event logs try getting a network capture on the Windows server side with Wireshark if you can or Windows NetMon. That should provide a little more information to what exactly is happening and where.

-Rob

Joan,

To change your disk utilization threshold for all devices.

First open one of the devices up, then select the "File Systems" component. This should show you a list of what file systems are being monitored. Just under the file system list you should have a drop down that says "Display". Select "Templates" from that list.

At this point you should be able to figure out what monitoring template this component is using. The default for my localhost under /Devices/Server/Linux component is "/Devices/Server" "FileSystem".

Now, go to the "Advanced" section of Zenoss and the just under the top banner you should have "Monitoring Templates". At the bottom of the screen you should have a "Group By" area, make sure the "Device Class" is selected.

Open the sub-menu for "Server" and you should be able to find "FileSystem". When you click on this you should have the template displayed for file systems. The upper right panel holds the Thresholds settings, double click on "high disk usage". On the panel that opens you should be able to adjust the value of the threshold under "Maximum Value".  example .9 is 90%.

Keep in mind this will change it for all devices utilizing this template. These steps were shown for global change not per device. You do have the ability to reset this template on a device by device level but this WILL get out of control after a few devices. It's best to keep the template management at a global level if possible.

You can use this same method for interfaces.

Hope this helps.

-Rob

Tom,

Can you provide a list of Modeler Plugins you have configured for these two different device types?

-Rob

I urgently need to  monitor 3Com 4500 and 5500 switches. Does anyone monitor 3Com? Where can I find MIBS for 4500 and 5500 and which ones should I use? I would appriciate any help on this because we need to save our skin. Currently we monitoring 240 CI's (Windows, Unix, Linux and Cisco). No problems.

Shane:

It seems sys.exit doesn't matter to the zencommand, I get the same result.

Meaning if the script has the line:

logging.basicConfig(filename=logname, level=logLevel, filemode='w', format=formatString)

Then I get following:

2012-04-01 10:13:15,126 DEBUG zen.zencommand: running '/usr/local/zenoss/scripts/check.py'

2012-04-01 10:13:15,126 DEBUG zen.zencommand: cmd line: '/bin/sh -c exec /usr/local/zenoss/scripts/check.py'

2012-04-01 10:13:15,128 DEBUG zen.zencommand: Process check.py  started

2012-04-01 10:13:15,129 DEBUG zen.zencommand: Next command in 8 seconds

2012-04-01 10:13:15,227 DEBUG zen.zencommand: Received exit code: 1

If I mask the logging.basicConfig with # like this:

#logging.basicConfig(filename=logname, level=logLevel, filemode='w', format=formatString)

I get the following:

2012-04-01 10:13:25,305 DEBUG zen.zencommand: Command: '/bin/sh -c exec /usr/local/zenoss/scripts/check.py'

2012-04-01 10:13:25,306 DEBUG zen.zencommand: Output: 'COMMAND OK|test=1\n'

2012-04-01 10:13:25,306 DEBUG zen.zencommand: Process check.py  stopped (47), 0.07 seconds elapsed

2012-04-01 10:13:25,306 DEBUG zen.zencommand: The result of "/usr/local/zenoss/scripts/check.py" was "'COMMAND OK|test=1\n'"

2012-04-01 10:13:25,307 DEBUG zen.zencommand: Queueing event {'severity': 3, 'performanceData': 'test=1', 'component': '', 'agent': 'zencommand', 'summary': 'COMMAND OK', 'manager': 'zenossu.il.check.com', 'eventKey': 'Check', 'device': '10.1.13.118', 'message': 'COMMAND OK', 'eventClass': '/Cmd/Fail', 'monitor': 'localhost'}

2012-04-01 10:13:25,307 DEBUG zen.zencommand: Total of 1 queued events

2012-04-01 10:13:25,308 DEBUG zen.zencommand: Next command in 9 seconds

2012-04-01 10:13:26,952 DEBUG zen.zencommand: Received exit code: 0

Nop, the graph's are stick.Nothing is changed after zenoss restart.

http://community.zenoss.org/servlet/JiveServlet/downloadImage/2-65674-11870/450-225/pic_new3.JPG

and

http://community.zenoss.org/servlet/JiveServlet/downloadImage/2-65674-11871/450-220/pic_new4.JPG

P.S. Is there any another way to change "high dis k usage" alert's?May be only for single device or... ?

Yes you can change it for that single device and that would be a great check to see if you're changing the correct graph definitions.

Select the File System component and just under the file system list you should have a drop down that says "Display". Select "Templates" from that list.

In the right panel you have the Thresholds setting. At this point you should be able to see if this graph definition is a global or local graph. You should have the option to either Create Local Copy or Delete Local Copy. If the Create Local Copy is enabled any changes you make will impact all other devices utilizing this graph def.

Hope this helps.

-Rob

Also,

You may want to check out my response to http://community.zenoss.org/message/65671#65671

for more information on graphs.