NetApp - Storage Nuts & Bolts

NetApp & 10GbE support - VMware Support Matrix

Although, Fibre Channel continues to dominate with respect to ESX server deployments, IP is seen some very high growth rates in this space.

Over the past several months we've gotten several requests for 10GbE support. The challenge was that although we have had 10GbE capability within our arrays for some time now, from an ESX perspective, VMware didn't support 10GbE connectivity from the VMkernel to the back-end storage device. The only VMware support that existed was for "front-end" connectivity, from the VM(s) out to the network.

As most folks are aware, with the introduction of ESX 3.5U1 VMware announced support for 10GbE back-end connectivity (VMkernel to storage array). What does this mean?

Am I supported?

The fact that VMware announced support for 10GbE does not mean any array with 10GbE NICs will be supported. The array must be on VMware's Suport Matrix for 10GbE connectivity.

Rule of Thumb: If the Array uses a 10GbE interface to connect to an ESX server(s), regardless of the negotiated speed, the array needs to be on VMware's Support Matrix.

Based on yesterday's update of VMware's support matrix ,we're now listed  for 10GbE storage connectivity to VMkernel. Although, we can run same version of ONTAP across the product line, each HW platform needs to be separately qualified.

As it stands right now, it looks like we're the only vendor on the matrix able to receive VMware support and we're working quickly in expanding support to include other arrays that will benefit from it.

Windows 2008 and Hyper-V Part II

In the previous entry I discussed the different OS versions and  requirements for enabling the Hyper-V role. In this post, and given that Microsoft recommends Windows 2008 Server Core for Hyper-V deployment, i'm going to discuss it.

Windows 2008 and Hyper-V - Part I

I've spend an enormous time over the years with VMware's robust solution but it's time to dedicate time to other virtualization solutions as well because some of them are very deserving. Hyper-V's an example of that and frankly so is XenSever. That said, in the next few blog entries I'll be talking about Hyper-V, its components and Hyper-V on NetApp.

The BT Consolidation Story

Two years ago, Michael Crader, the head of Windows Consolidation for BT kicked-off a very ambitious project to consolidate more than 3000 Window servers.

Back in 2006, BT was facing exploding costs thru its power consumption of close of 0.7% of UK's power production. BT also had severe problems by failing to maintaining its SLA given that backups were taking days (96 hours to be exact) and new server deployment could take six weeks among other things.

Is the Future of Fibre Channel, Ethernet (FCoE)?

A title like this one four years ago would have been joked at. However, today, given the industry buzz, hype, and genuine excitement that FCoE (Fibre Channel over Ethernet) has generated, it seems as a very reasonable assumption and one that will, most likely, come to fruition given the support FCoE has garnered support from pretty much everyone in the industry.

What is FCoE?   

Fibre Channel over Ethernet or FCoE, is a new protocol (rather transport) undergoing standardization at the T11 committee. FCoE  transports Fibre Channel frames over Ethernet by encapsulating FC frames. Although the standard is not expected to be ratified until the end of 2008, the expectation is that no spec changes will occur between now and the then.