Category guides

Sever Room Cooling

Practically every SME site I visit that has air conditioning in their comms room or server closet has it running as low as it goes – usually 18°C.  But why?

According to a friendly air conditioning engineer, the IT guys just like to ‘feel’ the cooling when they walk in.  But does running server rooms ‘cold’ have any merit, or is it just money being wasted?

One the one hand, it’s well known that some electronic components (such as capacitors) last longer at lower temperatures – and fan bearings are similarly affected.

But the flip side is that simply running air conditioners flat-out costs, since as well as moving the heat generated by the servers, the systems are moving heat from the surrounding building fabric.  By running server rooms slightly higher than the surrounding building ambient, some of the heat load generated will be sunk into the building fabric, saving money on both parts of the thermal load.

Safe Range

Server quickspecs provide operating temperature ranges, usually 5 to 35°C or more, and a quick look at the DRAC temperature thresholds on a PowerEdge server shows that system board ambient is considered normal up to 42°C, and critical only at 47°C.

Dell and HP just don’t ask for the ambient temperature history in assessing warranty claims – so it seems that within the stated range, reliability isn’t materially affected.  It’s worth noting that the infamous (but out-dated) Google study of disks also found that higher temperatures gave, if anything, longer disk life, and since then disks have moved to fluid bearings that have far greater reliability than their predecessors.

Air conditioners add massively to the electricity bill (and carbon footprint) and excess cooling also dehumidifies the air more (due to the lower coil temperature), and this in turn leaves the environment more vulnerable to electrostatic discharge (which is bad!).

Set Points

The more something provides heating or cooling, the more it costs to run.  So what temperature set point will minimise cost?

Personally, I use a set point a few degrees higher than the surrounding building ambient, so that the comms room coolers are moving only the heat load generated by the equipment (rather than some too from the surrounding building).

For a typical SME or branch office comms room, with a single high-wall mounted cooler, directing the air flow over the front of the rack will generate savings by making use of the front-to-back cooling of the equipment (creating a so-called ‘hot aisle’ at the rear), because the overall ambient can be further increased without affecting the internal temperatures of the servers, thereby sinking much of the heat load to the surrounding building fabric:

Running the air conditioner fans at maximum speed maximises the coiling coil temperature at any particular load and therefore minimises dehumidification.

Working with What’s There

Another consideration is the types of systems installed.

Older R407C systems use at least 30% more electricity and dehumidify more than DC-inverter R410a systems (because of the simple on-off design).

DC-inverters meanwhile tend to be are most efficient running at about 80% stated load capacity.

For Example

Say a comms room had a 5kW R407C system, two 6kW R410a systems, and an electrical load (which can be checked via the UPS management cards) of about 9kW.  In this case, setting the two R410a systems to 25°C and the R407C to 27°C might work well, as the R407C system would ‘kick in’ only if one of the R410a systems packed up (because the 9kW electrical load cannot be moved completely by one of the 6kW R410a systems, resulting in a rise in the ambient temperature).

Because of our friends at VMware, often now I find the cooling systems are way over specified.  In the above example, electrical load might have been reduced to only 3kW and then the R407C system wouldn’t be needed at all, and a 25°C/27°C set point split between the two R410a systems.

As with everything, to maintain a reliable infrastructure monitoring is the key.  Option boards are available for Daikin systems (for example) to connect to environmental monitoring equipment such as APC’s NetBotz range.  Alternatively, a temperature sensor can be simply attached with a cable tie to the air conditioner outlets, and alarms configured on the environment monitor accordingly after some period of observation.

Server Room Air Conditioning Quick Tips

  • Understand what you’re dealing with – the electric load (which usually equals the thermal load), the air conditioner type, and their cooling capacity.
  • Minimise the use of R407C air conditioners.
  • Create hot isles – direct cooled air across the front of the racks as this is what the servers ‘breath’.  Cooling at the rear of the rack is essentially wasted.
  • Don’t use comms room air conditioners to cool the building – remove only the heat generated by the equipment.
  • Focus on server internal temperatures rather than room temperatures – a 25°C ambient as recorded via the server system board sensors is absolutely fine.
  • Be mindful of how quickly and how much temperatures will rise in the event of incoming mains power failure, as UPS shutdown policies may need to be revised (UPS run time could result in overheating, in the absence of any cooling).  This can be tested by shutting down the air conditioners and observing the rate of rise.
  • Try to work out the overall room air flow, watching out for hot-spots.  Server racks are cooled front-to-back and can therefore benefit from the use of blanking plates in the racks between servers and of course wire mesh doors, but comms equipment tends to be cooled side-to-side.  Internal division of racks (with side panels) can therefore be advantageous.
  • Work out a way of monitoring the health of installed air conditioners and generating alarms when necessary.
VN:D [1.9.13_1145]
Rating: 3.0/5 (1 vote cast)
VN:F [1.9.13_1145]
Rating: 0 (from 0 votes)

How to upgrade ESXi to 4.1 Update 1 (U1)

Patching and updating free-licensed ESXi is a little more difficult since vmware withdrew the neat host update utility, but thankfully it’s still pretty easy.  With 4.1 Update 1 recently released, now is probably the time to catch up on patching for those that haven’t yet attempted this without the host update utility.

What’s Fixed in 4.1 Update 1 (build 348481)

Quite a lot, in short.  Notably some fixes for Windows Server 2008 R2 guests, support for new guests such as Ubuntu 10.10, and a new tunable for NFS that resolves large file creation time-out (no fix for the similar NFS large file delete time-out, but watch this space).  Scalability is also up to 160 processors.

Full detail in vmware’s release notes.

Prerequisites

  • vmware vCLI (which is installed on Windows, and note needs a reboot after installation)
  • vmware ESXi update package ZIP file, which can be downloaded from the downloads section of vmware.com after registration

Update Process

The update process is exactly the same as general 4.1 host patching, but this time only one patch needs to be applied, ESXi410-Update01:

After the update, the vSphere client also needs to be updated, but that is handled automatically when attempting connection.

See Also

VN:F [1.9.13_1145]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.13_1145]
Rating: 0 (from 0 votes)

ZBox HD-AD01 On Heat

Until XMBC released a port for Apple’s nifty TV2, Zotac’s ZBox HD-AD01 was a decent and cheap way to deliver HD content to a TV via HDMI, amongst other uses (micro NFS server for example).  Small and quiet it is; cool running it isn’t.

Today my box stopped dead after a playing flash based content for about an hour – its case uncomfortably hot and inside its SSD properly cooking.

Re-engineering the ZBox

For some reason the air holes there are on the box are cited amongst many more closed off holes:

With the system board removed, these blanks can be easily drilled out with a 3mm bit, taking care to avoid WiFi antenna and case clips, and then all holes opened up and cleaned up with a 3.5mm bit:

It’s a similar story at the base of the unit:

Again a significant increase in the ventilation can easily be achieved:

The end result is at least double the overall ventilation ‘free area’ for convection cooling.  The CPU fan grill holes are similarly restrictive and can be opened up a little with a 3mm bit.

Finally, because of the curved profile of the base, the system sits far too close to whatever it’s on or mounted to, so extra feet or another method of spacing is needed.

Running Vertical

My overall idea is to convection cool the system with it vertically mounted.  Even with the bigger holes, the system simply shouldn’t (in my opinion) be mounted horizontally because of the lack of cooling that results.

The Result

Fortunately the system survived the earlier overheating, so some catching up on iPlayer exercised the diddy AMD system, and after a few hours running at near 100% the system temperature was reported as 32°C and the CPU 72°C – comfortably within its 95°C design maximum.

VN:F [1.9.13_1145]
Rating: 0.0/5 (0 votes cast)
VN:D [1.9.13_1145]
Rating: +1 (from 1 vote)

How to Patch ESXi 4.1

Since the introduction of 4.1, vmware have withdrawn the host update utility, presumably as a gentle nudge for those on the free version to at least buy the frankly bargain-priced Essentials pack.

But the free licensed version still has a place, particularly for home labs.  I tend to use it also on machines I’m repurposing to run as NFS servers to act as datastores for DR and archive purposes, since the performance charting with datastore latency numbers and built-in health monitoring are extremely useful.

Since vmware have just released the first round of patches for ESXi 4.1, taking the build number to 320092, here’s a quick guide on how to patch ESXi 4.1 using vihostupdate.pl.  And fortunately, this release continues to run just fine on HP’s ML115 G5.

What’s Fixed in build 320092

Finding the Patches

Go to vmware’s download page and search for patches and updates to ESXi 4.1:

At time of writing, only one patch is available, ESXi410-201010001, which is about 200MB.

Applying the Patches

As ever, the host needs to be in maintenance mode, which means stopping all VMs.  You therefore need the patch ZIP file (no need to unpack it) on a physical Windows based PC along with the vmware vCLI.

The update process itself is pretty straightforward, although you might not think that from the 94-page vmware update guide.  Basically:

  • List out the updates in the package using vihostupdate.pl -l
  • Apply each update to the ESXi host, using vihostupdate.pl -i
  • Restart the host

 

I’ve put a detailed step-by-step, with screenhosts, in the peacon blog wiki

Whilst updating from a PC over a wireless LAN should be OK, it is always preferable to use a wired connection in case the connection should be disturbed part way through the update process.

Rolling Back

There’s always the possibility that for whatever reason the patch process won’t work.  Whenever a host is patched, the last version is maintained by ESXi and can be restored by pressing shift-R at the initial boot loader screen (with the white progress bar at the bottom) providing an option to roll back:

Simply press Y and then Enter to boot the old version when prompted.

VN:D [1.9.13_1145]
Rating: 5.0/5 (1 vote cast)
VN:D [1.9.13_1145]
Rating: +1 (from 1 vote)

How to Install NginX

NginX is great web server and reverse proxy, but with so many compile time options and dependencies it can be a pain to get it properly installed on Linux.  There is a Windows port, which has worked well enough for me for the last six months, but its faster on Linux and of course doesn’t then carry the weight of Windows behind it.  With ever increasingly memory pressure on my ESXi box, reducing memory load is important to me so I’ve moved my reverse proxy on to a Turnkey Linux Core VM, which is basically Ubuntu with a bunch of handy web management tools built right in.  It’s incredibly light – top suggests 64MB would be sufficient.

Standard Repositories

Many distributes have NginX available right from their usual installers – for example apt-get install nginx on Debian or Ubuntu.  But those versions tend to be pretty out-of-date and therefore lack much functionality, and have generally been built with default options, which means no SSL support.  Building from source of course gives full control over the install and means the latest versions can be used.

The NginX official notes list package dependencies as:

  • libc6 (>= 2.4)
  • libpcre3 (>= 7.7)
  • libssl0.9.8 (>= 0.9.8f-5)
  • zlib1g (>= 1:1.1.4)
  • lsb-base (>= 3.2-14)

The issue is that some of the standard packages available via (for example) apt-get can be too old.  For TurnKey Linux Core, a newer version of pcre is needed and last time I checked on Debian, libssl wasn’t up to spec either.

Installing Nginx on TurnKey Linux Core

The great thing about the TurnKey Linux Core base is that there is a browser based file manager available via https://server-ip:12321/, so importing and editing nginx.conf is a doddle as well as extracting logs periodically.

For my build the requirements for NginX itself are pretty straightforward – basically SSL support and the latest NginX stable (0.7.67 at time of writing).  Ubuntu’s libpcre3 module is too old, but pcre-8.10 can be installed straight from source.  I’ve set out a full step by step guide in the wiki – hopefully this guide will save you some time!

VN:F [1.9.13_1145]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.13_1145]
Rating: 0 (from 0 votes)

Copyright © Peacon Ltd, 2010, 2011
virtualisation blog by James Pearce

If you find the content of this blog useful, please consider donating just a pound towards the costs:

WordPress Appliance - Powered by TurnKey Linux