Skip to main content

IT Sanity

Search This Blog

I'm Back

October 09, 2012

Get link
Facebook
X
Pinterest
Email
Other Apps

After much time away, I'm picking up where I left off...which is to say...just starting. More Posts to soon follow.

Get link
Facebook
X
Pinterest
Email
Other Apps

Comments

Post a Comment

Popular Posts

Hyper-V Template for Zabbix

Well after after a few false starts I have my template for Hyper-V working in Zabbix. The template will auto discover virtual machines running on a Hyper-V 3.0 server. Template will monitor status, CPU Usage, Memory usage, and uptime. I have tested with Zabbix 2.0 and Windows 2012 Server and Hyper-V Server 2012. Still working on Windows 2008 R2. Link to zabbix template: Hyper-V Zabix Template Link to powershell script: HyperV_Status.ps1 You will need to install the Power Shell script to the Hyper-V Server and update the Zabbix Agent configuration. Settings for zabbix_agentd.conf: UserParameter=hyperv.discover,powershell.exe -file "C:\Program Files\Zabbix\HyperV_Status.ps1" UserParameter=hyperv.check[*],powershell.exe -file "C:\Program Files\Zabbix\HyperV_Status.ps1" $1 "$2" Example of CPU Usage Graph

Windows Disk Monitor for Zabbix

With a Windows 2012 Cluster Microsoft introduced a new file system - CSVFS. I found that currently the zabbix agent does not return this file system when using the vfs.fs.discovery low level discovery for the file system. Additionally the low level discovery will not work on volumes that have been mapped to a directory instead of a driver letter. So I've written a powershell script that handles finding file system and monitoring for drive capacity and free space: param( [Parameter(Mandatory=$False)] [string]$QueryName, [string]$FSName ) if ($QueryName -eq '') { $colItems = gwmi win32_volume | select Name,FileSystem write-host "{" write-host " `"data`":[" write-host foreach ($objItem in $colItems) { $objItem.Name = $objItem.Name -replace "\\\\\?\\Volume{","Volume-" ...

CIFS Performance Tunning on NetApp

After getting our NetApp up and running we've been pushing files to it as fast as we can. But found that when copying files to the NetApp we occasionally got file timeouts and transfer errors. At first it was thought that this was a WAN or VPN issue. But after troubleshooting we found that NetApp's CIFS settings need some adjustments. The first setting is the cifs tcp window size. The default value is set to 17520. A lot of people on the NetApp community boards recommend setting the value to 64240 (basically the largest windows allows). This works well with older versions of Windows (2003 or earlier), but can be a different story for newer versions of Windows as Microsoft did away with TCP windows setting. My finding are to start with the high value and then lower the value if testing shows the connection performance suffering. Additionally increasing the negotiated buffer can increase performance if you have OnTap version 7 or higher. To set the cifs settin...

Powered by Blogger