Showing posts with label Intel Server System R2208GZ. Show all posts
Showing posts with label Intel Server System R2208GZ. Show all posts

Thursday, 9 May 2013

Repeat after me: SATA does not belong in servers.

One of the very last servers we deployed with SATA drives had yet another failure in it.

There is a new Intel R2208GZ4GC 2U server in place with eight 600GB 10K SAS drives configured in a RAID 6 array already installed and waiting for tax season to slow down for them (they are an accounting firm).

image

Our client recently moved to a new location with the servers now located in a dedicated room in the basement. The little A/C unit in that room was a leftover from the previous occupant that we were not too sure about.

Well, the hot spare in this server, an Intel Server System SR1560SFHS with three 750GB Seagate ES series SATA drives, died about four months ago. Since the system was slated for replacement we left the remaining two in a RAID 1 array alone.

Well, that ended this morning with one of the drives in the pair having gone full stop. This was probably due to the fact that the temp in the room upon arrival this afternoon was close to 90F.

Someone had fired up the A/C unit without realizing that the hose that puts the heat outside was not connected to the back of the unit. Thus all of the heat it was trying to pull out plus its own heat yielded a very high temperature in that room.

Once the hose was affixed to the back of the unit the temperature started to come down.

So, here we are writing this blog post at 2216Hrs on a Wednesday evening after having logged in to check on the progress of the array rebuild and the above was what we saw.

The RAID controller is an Intel RAID Controller SRCSASRB with battery backup.

SATA does not belong in a server when it comes to spindled hard drives. This experience with the blind failure and the dismal rebuild times, during off hours no less, are definitely a part of it.

SAS/SCSI was designed and engineered to run in server environments. SATA was not.

The firmware tweaks that the hard drive vendors have introduced, along with the pretty much failed NCQ effort, to try and mimic a SAS setup within the SATA controller do not come close to the performance, longevity, and stability that SAS drives offer.

By the way, this goes for NearLine SAS drives as well. These drive types are SATA internals with SAS electronics slapped on to the external of the drive. There is a very good reason why the drives are called "NearLine". :)

The cost on 2.5" 10K SAS drives in 300GB and 600GB sizes have come down quite a bit in the last year. The 900GB 10K SAS drives are still relatively expensive per Gigabyte but provide an opportunity for a large aggregate of storage when needed.

Another way to look at it is this: How many RMA efforts have gone in to server setups with SATA drives in them? Compare that with the servers that have SAS setups. In our case, where we have lots of servers deployed, there is virtually no comparison. Over time the SAS drives have completely trumped the SATA drives in all aspects.

Even with 24x7x365 by 4 hour response times most vendors require time wasted on the phone prior to initiating that on-site visit to replace the failed drive. This time is expensive and to some extent a waste.

Oh, and one more thing: If going with parity in an array go RAID 6 with at least eight 10K spindles and make sure the RAID controller has either flash backed cache or a battery backup.

Storage is almost always the weakest point in a server both for hardware failures and I/O bottlenecks. Kill both. Use a wide array of eight spindles or more and make sure the drives 10K SAS.

The risk when using SATA is just not worth the "savings" IMNSHO (in my not so humble opinion).

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Chef de partie in the SMBKitchen
Find out more at
www.thirdtier.net/enterprise-solutions-for-small-business/

Windows Live Writer

Monday, 4 March 2013

We don't like physically moving servers. Period.

Over the years we have learned may lessons. One of the particularly valuable ones is that we prefer to not move a server once it has been in production.

image

This particular server is an Intel Server System R2208GZ4GC 2U that has been online for about 90 days.

The server was moved just recently to their new location.

Things went well after firing the server up and bringing services online but today, after being online this last weekend, we came in to some errors.

The status indicator was blinking red. In the Intel Active System Console indicated that we had two error conditions in place:

  • Warning: Memory Channel G1 disabled due to ECC fail.
  • Critical: Blower 2 not present.

After opening the top we could see the above. We re-seated the fan with nothing happening.

So, since we were going to be removing the air duct to get at the memory we went on to check the fan power connector and sure enough it was loose.

We moved the memory stick into another channel to see if we were having a board issue or the memory was faulty.

When we booted the server up we received the three BIOS POST beeps that indicated faulty memory. Sure enough, the little red light followed the problematic stick. But this time we had two fault conditions.

After a few memory channel swaps to figure things out we ended up with the following:

image

A call into Kingston support and we had an RMA and an advanced swap set up for the problematic sticks. Their support and RMA process has always been consistently good.

In the end it is our preference that once a server has entered service it never gets touched until it is heading for the recycling bin.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Chef de partie in the SMBKitchen
Find out more at
www.thirdtier.net/enterprise-solutions-for-small-business/

Windows Live Writer

Friday, 11 January 2013

Intel Server Systems Remote Management Module 4 (RMM4) Display Resolution

Once the server with the RMM4 has been set up there is an important step that needs to happen to allow the RMM4 to establish a remote KVM over IP session:

image

Make sure the desktop display resolution after installing the graphics driver is set to 1440x900 or 1280x1024 before logging off the desktop the final time.

Otherwise the KVM over IP session will show a black screen after clicking the Launch Console button.

image

This is an especially important step for all servers with an RMM2/3/4!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Windows Live Writer

Wednesday, 6 June 2012

Ordering the Intel Server System R2216GZ4GC or R2216GZ4GCLX

When it comes to ordering Intel Server Systems for our Hyper-V failover clusters we are settling in on the Intel Server System R2208GZ4GC as our mainstay for mid-range clusters and up.

When it comes to ordering the systems the differences between them can sometimes be difficult to pick up on.

In the case of the “LX” suffix we almost got caught as the suffix used to mean redundant power and cooling among a few other added features in Intel Server Systems.

In the case of the Intel Server System R2216GZ4GC or R2216GZ4GCLX we noticed that this was not the case:

image

The “LX” model comes with the added Hardware RAID SAS module and the 10Gbit fibre module.

Since we are not working with fibre in our solutions at this point we will be working with the R2216GZ4GC and adding in the RMS25CB080 among other additions to the configuration.

It pays to pay attention. :)

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Thursday, 31 May 2012

LSI SAS6160 Switch Compatibility List

We are in the process of setting up a number of Intel Server System SR1695GPRX2AC units along with our soon to be two Intel Server System R2208GZ4GC units to one Promise VTrak E610sD RAID subsystem.

Out of the box we are dealing with 3Gbit/Second SAS connections with the VTrak so we are not able to use the more advanced features the SAS Switch offers.

The LSI SAS6160 Switch compatibility list can be found here:

Specifically we are looking for a replacement for the Promise VTrak that will give us access to SAS 6Gbit/Second and the advanced features offered by the SAS Switch.

image

Now, note that the Promise VTrak E610sD requires firmware 3.36.00. Our current unit is at 3.34.00. So, we are on our way to updating the firmware in the Promise before we can draw any conclusions as far as setting things up.

image

As far as a replacement for the Promise the first in the above list is actually a NetApp appliance. We will be looking into their products. We have already been in conversations with IBM over their DS3524 dual controller SAS unit so we shall see where that goes.

For now, we are on the road to bringing a very flexible, high performance, and highly redundant hardware solution online to deliver Hyper-V Failover Clusters as well as a Private Cloud solution.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Wednesday, 30 May 2012

Current Intel Integrated RAID Module Hardware User’s Guide

The direct link to PDF documentation on the Intel Integrated RAID Modules can be found here:

Note that the above links are good as of this writing.

A relatively full list of compatible products can be found on the Intel Ark site:

So, between the Technical Product Specifications, the Ark site, and the Server Configurator we get a pretty good picture on what components we can deploy with our Intel Server Systems.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Friday, 25 May 2012

Thoughts on the Intel Server System R2208GZ4GC Are Excellent So Far

As we go through setting up the Intel Server System R2208GZ4GC we are discovering that there are a lot of features in this server system that we appreciate.

Some are cluster specific:

image

  • Power Restore Delay

We now have a boot delay option in the BIOS. This option is absolutely critical for servers that are configured in a cluster with shared storage.

In a full power out situation the networking and centralized storage systems need to be online prior to the Hyper-V Failover Cluster nodes coming online. Otherwise there can be all sorts of issues.

image

  • Static Boot Order

We can now save the default boot order out of the box. So, when this box gets connected to a Promise VTrak E610sD RAID Subsystem with LUNs configured the 120GB Intel 320 Series SSDs in RAID 1 should still boot after a reboot with no interference.

This has yet to be tested, but we are confident that the feature will work as advertised.

image

  • Reset Static Boot Order

Important Software RAID Consideration

When using the Intel Chipset RAID feature for software driver based RAID on _any_ Intel Server Board _always_ use the Intel ESRT2 (LSI*) Mode.

image

The other option is the consumer chipset version of Intel’s Software RAID stack.

The major catch is that the LSI version can have an Intel or LSI RoC Hardware RAID controller plugged into the server board or PCI-E slot at a later time and have the ESRT2 (LSI*) based RAID set imported with no fuss.

This is not possible with the Intel chipset version.

So far so good. This Intel Server System is the configuration we have been asking for in the Channel for _years_ now to compete with HP, IBM, Dell, and others.

Pound for pound we will now be able to compete apples to apples with the Tier 1 vendors. And, with Intel’s available next business day on-site warranty support we can reach most major markets in Canada and Lower 48.

The Intel Server System R2208GZ4GC 2U will be our primary starting point for any 2 processor Hyper-V Failover Cluster Nodes going forward. It is an awesome product!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer