In 1965, Gordon Moore predicted that engineers would be able to double the number of components on a microchip every two years.  Known as Moore’s law, his prediction has come true – processors are continuing to become faster each year while the components are becoming smaller and smaller.  In the footprint of the original ENIAC computer, we can today fit thousands of CPUs that offer a trillion more computes per seconds at a fraction of the cost.  This continued trend is allowing server manufactures to shrink the footprint of the typical x86 blade server allowing more I/O expansion, more CPUs and more memory.  Will this continued trend allow blade servers to gain market share, or could it possibly be the end of rack servers?  My vision of the next generation data center could answer that question. 

Before I begin, I want to emphasize that although I work for Dell, these ideas that I’ve come up with through my experience in the blade server market and from discussions with industry peers.  They are my personal visions and do not reflect those of Dell nor are the ideas mentioned below limited to Dell products and technology. 

The First Evolution of the Blade Server – Less I/O Expansion
Last November I wrote an article of my first vision of “The Blade Server of the Future” on CRN.com.  In the article, I described two future evolutions of the blade server.  The first was the integration of a shared storage environment (below).  While the image depicts the HP BladeSystem C7000 modified with storage, my idea stems from the increase of onboard NICs driving a lot of the individual blade traffic.  With 10Gb / CNA technologies being introduced as a standard offering, and with 40Gb Ethernet around the corner, the additional mezzanine cards and I/O expansion found on today’s blade server technology may not be required in the near future.  The space freed up from the removal of the un-needed I/O bays could be used for something like an integrated storage area network, or perhaps for PCI expansion.

The Next Evolution of the Blade Server – External I/O Expansion
PCI expansion is another possible evolution within the blade server market.  As CPUs continue to shrink, the internal real estate of blade servers increase, allowing for more memory expansion.  However, as more memory is added, less room for I/O cards is available.  While I mention that additional I/O may not be needed on blade servers with the standardization of large onboard Ethernet NICs, the reality is that as you cram more into a blade server, the more I/O will be required.  I believe we’ll see external I/O expansion become standard in future evolutions of blade servers.  Users of RISC technologies will be quick to identify that external I/O is nothing new and in fact, even in the x86 space has been an option through Xsigo.com however my vision is that the external capability would be an industry standard like USB or HDMI.  While the idea of a standardized external I/O capability like shown in the image below is probably more of a dream than a reality, it leads to my long term vision of where blade servers will eventually evolve to.

The Future of the Blade Server – Modular Everything
Blade servers rely on connectivity to the outside world through a mid-plane and I/O modules.  They are containerized within the chassis that houses them allowing them to be an ecosystem for compute resources.  What if we took the idea of how the blades connect to the blade chassis and extended it to an entire rack?  Imagine having a shelf of blade servers that docked directly to a rack midplane (aka a “rackplane”).  In fact, anything could be designed with this connectivity: storage trays, PCIe trays, power trays.  What ever technology you need, be it compute power, storage or I/O could be added as needed.   The beauty of this design is that the compute nodes could communicate with the storage nodes at “line speed” without the need for point-to-point cabling because they are all tied into the “rackplane”.  Here’s what I think it would look like:

On the front side of the modular rack, a user would have the option to plug in whatever is needed.  For servers, I envision half-size blade servers housed in a 1 or 2U shelf.  The shelf could hold any number of servers, but I would expect that a shelf of 8 – 12 servers would be ideal.  Keep in mind, in this vision, all we need are CPUs and memory inside of a “blade server” so the physical footprint of the future blade server could be the size of today’s full-length PCIe card.  Each of the shelves, whether they are servers, storage or compute, would have docking connectors similar to what we see on today’s blade servers but on a much larger scale.  On the back side of the modular rack, you would have the option to add in battery protection (UPS), cooling and of course, I/O connectivity to your data center core fabrics. 

One of the most obvious disadvantages of this design is that if you had a problem with your “RackPlane”, it would take a lot of resources off line.  While that would be the case, I would expect that the design would have multiple rackplanes in place that would be serviceable.  Of course, if the racks were stacked side-by-side with other racks, that could pose a problem – but hey, I’m just envisioning the future, I’m not designing it…

What are your thoughts on this?  Am I totally crazy, or do you think we could see this in the next 10 years?  I’d love your thoughts, comments or arguments.   Thanks for reading.

Kevin Houston is the founder and Editor-in-Chief of BladesMadeSimple.com.  He has over 14 plus years of experience in the x86 server marketplace.  Since 1997 Kevin has worked at several resellers in the Atlanta area, and has a vast array of competitive x86 server knowledge and certifications as well as an in-depth understanding of VMware and Citrix virtualization.    Kevin works for Dell as a Server Sales Engineer covering the Global 500 market.

If you are a reader of BladesMadeSimple, you are no stranger to Dell’s Network Daughter Card (NDC), but if it is a new term for you, let me give you the basics. Up until now, blade servers came with network interface cards (NICs) pre-installed as part of the motherboard.  Most servers came standard with Dual-port 1Gb Ethernet NICs on the motherboard, so if you invested into a 10Gb Ethernet (10GbE) or other converged technologies, the onboard NICs were stuck at 1Gb Ethernet.  As technology advanced and 10Gb Ethernet became more prevalent in the data center, blade servers entered the market with 10GbE standard on the motherboard.  If, however, you weren’t implementing 10GbE then you found yourself paying for technology that you couldn’t use.  Basically, what ever came standard on the motherboard is what you were stuck with – until now.

 Dell has broken the long-standing design concept of embedding the LAN onto the motherboard (aka LOM) and replaced it with a small, removable mezzanine card called a Network Daughter Card, or NDC.  The NDC provides the buyer with a flexibility of choosing what they want ( 4 x 1GbE, 2 x 10GbE or 2 x Converged Network Adapter.)  This innovation is exciting to me, as it not only provides a possible upgrade path to future technologies, but it also changes the way we look at server technology.  No longer does the on-board NIC have to be integrated onto the motherboard, but it can be a removable card that can be easily replaced or upgraded.  In a few years when this is standard architecture on every x86 server, remember where you saw it first.

But wait – there’s more.  In addition the NDC is the first adapter to offer the industry’s first network partitioning, or “NPAR” scheme that makes it possible to split the 10GbE pipe while working with any of the Dell PowerEdge M1000e 10GbE Ethernet Switch Modules.  So, what’s the big deal about NPAR?  Let me explain.

With the increased amount of virtualization in the data center, combined with an increase in data and cloud computing, the network’s efficiency is becoming compromised driving many organizations to embrace a 10GbE network.  While moving to a more robust 10GbE environment may be ideal for an organization, it also brings challenges like ensuring that the appropriate bandwidth for all resources is available in both the physical and virtual environments.  This is where NPAR comes in.  Network Partitioning allows for administrators to split up  the 10GbE pipes on the NDC into 4 separate partitions or physical functions and allocate bandwidth and resources as needed.  Each of the four partitions is an actual PCI Express function that appears in the blade server’s system ROM, O/S or virtual O/S as a separate physical NIC. 

Each partition can support networking features such as:

• TCP checksum offload
• Large send offload
• Transparent Packet Aggregation (TPA)
• Multiqueue receive-side scaling
• VM queue (VMQ) feature of the Microsoft® Hyper-V™ hypervisor
• Internet SCSI (iSCSI) HBA
• Fibre Channel over Ethernet (FCoE) HBA.

Administrators can enable/disable any of the features per partition and they configure a partition to run iSCSI, FCoE, and TCP/ IP Offload Engine (TOE) simultaneously.

Each of the four partitions per port (8 per NDC) can be set up with a specific size and a specific weight.  In the example shown on the above, you see that Physical Port 1 has 4 partitions:

• Partition 1 (red) = 2Gbps, running as an iSCSI HBA on Microsoft Windows Server 2008 R2
• Partition 2 (orange) = 2Gbps, running as an FCoE HBA on Microsoft Windows Server 2008 R2
• Partition 3 (green) = 1Gbps, running TOE on on Microsoft Windows Server 2008 R2
• Partition 4 (blue) = 5Gbps, running as a Layer 2 NIC on Microsoft Windows Server 2008 R2

Each partition’s “Maximum Bandwidth” can be set to any increment of 100Mbps (or .1Gbps) up to 10000 Mbps or 10 Gbps.  Also, note, this is for send/transmit only.  The receive direction bandwidth is always 10 Gbps.

Furthermore, admins can configure the weighting of each partition to provide increased bandwidth presence when an application requires it.  In the example above, Physical Port 2 has the “Relative Bandwidth Weight” on all 4 partitions set for an equal weight at 25% – giving each port equal weight.  If, however VMkernel NIC 1 (red) needed to have more weight, or priority, over the other NICs, we could set the weight to 100% giving that port top priority.

If you are feeling really adventurous, you can oversubscribe a port.  This is accomplished by setting the 4 partitions of that single port to having a Maximum Bandwidth setting of more than 100%.  This allows each of the partitions to take as much bandwidth as allowed as their individual traffic flow needs change – based on the Relative Bandwidth Weight assigned.  Take a look at the following:

The example above shows each of the four partitions’ Maximum Bandwidth (shown in .1 increments so 10 = 1 Gbps)

• Partition 1 = 1 Gbps
• Partition 2 = 1 Gbps
• Partition 3 = 8 Gbps
• Partition 4 = 8 Gpbs

Total for all 4 partitions = 18 Gbps, which means the port is 80% (8 Gbps) oversubscribed.

Some additional rules to note from the NPAR User’s Manual:

• For Microsoft Windows Server, you can have the Ethernet Protocol enabled on all, some, or none of the four partitions on an individual port.
• For Linux OSs, the Ethernet protocol will always be enabled (even if disabled in Dell Unified Server Configuration screen).
• A maximum of two iSCSI Offload Protocols (HBA) can be enabled over any of the four available partitions of a single port. For simplicity, it is recommended to always using the first two partitions of a port for any offload protocols.
• For Microsoft Windows Server , the Ethernet protocol does not have to be enabled for the iSCSI offload protocol to be enabled and used on a specific partition.

For more information on the Network Partitioning capabilities of the Dell Network Daughter Card, check out the white paper at: Dell Broadcom NPAR White Paper

Kevin Houston is the founder of BladesMadeSimple.com.  He has over 14 plus years of experience in the x86 server marketplace.  Since 1997 Kevin has worked at several resellers in the Atlanta area, and has a vast array of competitive x86 server knowledge and certifications as well as an in-depth understanding of VMware and Citrix virtualization.    Kevin works for Dell as a Server Sales Engineer covering the Global 500 market.

I’ve learned over the years that it is very easy to focus on the feeds and speeds of a server while overlooking features that truly differentiate.  When you take a look under the covers, a server’s CPU and memory are going to be equal to the competition, so the innovation that goes into the server is where the focus should be.  On Dell’s community blog, Rob Bradfield, a Senior Blade Server Product Line Consultant in Dell’s Enterprise Product Group, discusses some of the innovation and reliability that goes into Dell blade servers.  I encourage you to take a look at Rob’s blog post at http://dell.to/mXE7iJ.

I also want to highlight some other innovations that Dell is offering on certain blade servers:

Network Daughter Card (NDC) – unlike the network interface cards built into the blade server motherboard, the NDC is a daughter card that offers choices of 4 x 1Gb NICs, 10Gb NICs or CNA.  The NDC is a new feature and not offered on every blade server, but for more info, check out this earlier blog post I wrote: http://bladesmadesimple.com/2011/05/a-review-of-the-dell-poweredge-m710-hd-blade-server/

Network Interface Card Partitioning  (NPAR) – this is a feature found on certain blade server models that allows you to divide up the onboard 10Gb NICs into “virtual NICs”.  The cool thing is this can be performed without a specific network I/O module so you don’t have to worry about being locked into any specific I/O module and without the use of any CPU overhead or specialized software.   Read more about this at http://bladesmadesimple.com/2011/04/dellapril5announcements/.

Let me put these innovative features into a real life scenario (note – this is simply an example and doesn’t confirm or deny any future product release from Dell.)  Imagine today you invest into a blade server with a 10Gb NDC using NPAR to split up the 10Gb pipe into smaller 1Gb virtual NICs. and 10Gb capable Ethernet I/O Module and in 18 months, a 40Gb Ethernet Switch module comes out.  You could theoretically replace the NDC and the Ethernet module with the 40Gb flavor (if/when it ever is available)

The next time you choose a server, look beyond the speeds and feeds and look at the innovation, the reliability and the value the server can offer.

Kevin Houston is the founder of BladesMadeSimple.com.  He has over 14 plus years of experience in the x86 server marketplace.  Since 1997 Kevin has worked at several resellers in the Atlanta area, and has a vast array of competitive x86 server knowledge and certifications as well as an in-depth understanding of VMware and Citrix virtualization.    Kevin works for Dell as a Server Sales Engineer covering the Global 500 market.

Dell announced today a refresh of the PowerEdge M910 blade server based on the Intel Xeon E7 processor.  The M910 is a full-height blade that can hold 512GB of RAM across 32 DIMMs.   The refreshed M910 blade server will also feature Dell’s FlexMem bridge that enables users to use all 32 DIMM slots with only 2 CPUs.  You can read more about the M910 blade server in an earlier blog post of mine here.

According to the Dell  press release issued today, the systems being refreshed with the Intel Xeon E7 processor, which include the PowerEdge M910 blade server  as well as the PowerEdge R910 and R810, offer customers substantial performance gains including;

• Up to 38 percent improvement in Oracle application server and database performance over previous generation Xeon 7500 “Nehalem-EX” based servers *.
• Up to 18:1 server consolidation ratio over four socket dual core processor based systems offering up to 93 percent lower operation costs resulting in a one year return on investment**.
• Up to 34 percent improvement in SQL database virtualization performance and 49 percent higher performance per watt with the combination of Xeon E7 processors and new Low Voltage memory (LV RDIMM) offerings***.

According to Dell, the new Intel Xeon E7 CPUs will be shipping this week.

NIC Partitioning (NPAR)

Dell is also announcing the addition of a Converged Network Adapter (CNA) for the M710HD’s network daughter card, or NDC.  I wrote about the NDC in this post, but as a recap,  it’s a removable card that provides the blade server’s LOM (LAN on Motherboard) network adapter.  Previously Dell offered a 4 port Gigabit Ethernet card, but this 2nd offering opens the ability for users with the M710HD to upgrade to a fully converged 10Gb infrastructure.  This card is also the first adapter to offer the industry’s first “network partitioning” or NPAR scheme that makes it possible to split the 10GbE pipe with granularity free of any fabric vendor lock-in.  NPAR enables optimal use of physical network links allowing each 10GbE port to be carved up into multiple physical 1GbE NICs without the use of software and without any CPU overhead.  For example, each 10GbE port can be divided into up to four multiple physical NICs totaling 10Gb offering more flexibility.  The NPAR scheme is handled by the Unified Server Configurator, enabled by the Lifecycle Controller that is embedded on the server.  For more information on the Unified Server Configurator, check out Dell’s website:
http://content.dell.com/us/en/enterprise/d/solutions/unified-server-configurator.aspx

*Oracle: Based on Dell and Oracle testing performed in March 2011 running an industry-standard SPEC Java Enterprise benchmark . SPEC® is a registered trademark of the Standard Performance Evaluation Corporation.  Actual performance will vary based on configuration, usage and manufacturing variability.

**Consolidation: Up to 18:1 server consolidation performance with return on investment in about one year” claim estimated based on comparison between 4S MP Intel® Xeon® processor 7041 (dual-core with Intel® HyperThreading Technology, 4M cache, 3.00GHz, 800MHz FSB, formerly code named Paxville) and 4S Intel® Xeon® processor E7-4870 (30M cache, 2.40GHz, 6.4GT/s Intel® QPI, code named Westmere-EX) based servers. Calculation includes analysis based on performance, power, cooling, electricity rates, operating system annual license costs and estimated server costs. This assumes 42U racks, $0.10 per kWh, cooling costs are 2x the server power consumption costs, operating system license cost of $900/year per server, per server cost of $36,000 based on estimated list prices, and estimated server utilization rates. All dollar figures are approximate. Estimated SPECint*_rate_base2006 performance and power results are measured for Intel® Xeon® processor E7-4870 and estimated for Intel Xeon processor 7041 based servers. Platform power was measured during the steady state window of the benchmark run and at idle. Performance gain compared to baseline was 18x (truncated).

***Based on the DVD Store 2 benchmark testing  performed by Dell Labs in March 2011.  Actual performance and power draw will vary based on configuration, usage and manufacturing variability.

Updated 1/27/2011
Dell quietly announced the addition of a 10 Gigabit Ethernet (10GbE) switch module, known as the M8428-k.  This blade module advertises 600 ns low-latency, wire-speed,  10GbE performance, Fibre Channel over Ethernet (FCoE) switching, and low-latency 8 Gb Fibre Channel (FC) switching and connectivity.
In this era of virtualization in the datacenter, CPU and RAM capabilities on servers are no longer the bottleneck, but instead it is the servers’ I/O.  Technology vendors are now offering 10Gb Ethernet options which helps to reduce the traditional Ethernet I/O bottleneck.  In fact, many vendors have begun to offer a convergence of networking allowing both Ethernet and Storage commands to travel down a single converged pipe.  These devices, known as converged network switches have been around since Cisco first introduced their Nexus product a couple of years ago.  The design of the original converged switch took a single 10Gb cable to a Top of Rack (ToR) switch in which the Ethernet traffic and the fibre storage traffic was separated.

Over the past 9 months we’ve seen a surge of a new generation of converged switches, that does not require a ToR switch, but instead splits the Ethernet and Fibre traffic out of a single module within a blade chassis.  The advantages of this approach are: it frees up blade server mezzanine (expansion card) slots and it also requires fewer modules within a blade chassis therefore freeing up space for additional future fabrics.  In late December 2010, Dell announced their next generation converged module, called the M8428-k Converged 10GbE Switch Module.  The M8428-k has 28 ports: 16 internal and 12 external.  The 12 external ports are made up of:

*8 ports of 10 Gigabit Ethernet (GbE) speed and Data Center Bridging (DCB). 
*4 Fibre Channel ports: that support 2, 4, and 8 Gbps full duplex

The 16 internal ports (one per Dell M1000e Server bay) supports DCB and Fibre Channel over Ethernet (FCoE).  One last point to make, the module comes with all ports activated.  This is an advantage over some competitors that offer upgrade licenses to activate additional ports.

UPDATE – Currently the only compatible blade server mezzanine Converged Network Adapter (CNA) is the BR1741M-k.  This card provides FCoE connectivity from blade server to the M8428-k Converged Switch Module.  You can read more about this card on this Dell site.

For more information ont he Dell M8428-k Converged 10GbE Switch Module, visit Dell.com.

I wanted to post a few more rumours before I head out to HP in Houston for “HP Blades and Infrastructure Software Tech Day 2010″ so it’s not to appear that I got the info from HP. NOTE: this is purely speculation, I have no definitive information from HP so this may be false info.

First off – the HP Rumour:
I’ve caught wind of a secret that may be truth, may be fiction, but I hope to find out for sure from the HP blade team in Houston.  The rumour is that HP’s development team currently has a Cisco Nexus Blade Switch Module for the HP BladeSystem in their lab, and they are currently testing it out.

Now, this seems far fetched, especially with the news of Cisco severing partner ties with HP, however, it seems that news tidbit was talking only about products sold with the HP label, but made by Cisco (OEM.)   HP will continue to sell Cisco Catalyst switches for the HP BladeSystem and even Cisco branded Nexus switches with HP part numbers (see this HP site for details.)  I have some doubt about this rumour of a Cisco Nexus Switch that would go inside the HP BladeSystem simply because I am 99% sure that HP is announcing a Flex10 type of BladeSystem switch that will allow converged traffic to be split out, with the Ethernet traffic going to the Ethernet fabric and the Fibre traffic going to the Fibre fabric (check out this rumour blog I posted a few days ago for details.)  Guess only time will tell.

The IBM Rumour:
I posted a few days ago a rumour blog that discusses the rumour of HP’s next generation adding Converged Network Adapters (CNA) to the motherboard on the blades (in lieu of the 1GB or Flex10 NICs), well, now I’ve uncovered a rumour that IBM is planning on following later this year with blades that will also have CNA’s on the motherboard.  This is huge!  Let me explain why. 

The design of IBM’s BladeCenter E and BladeCenter H have the 1Gb NICs onboard each blade server hard-wired to I/O Bays 1 and 2 – meaning only Ethernet modules can be used in these bays (see the image to the left for details.)  However, I/O Bays 1 and 2 are for ”standard form factor I/O modules” while I/O Bays are for “high speed form factor I/O modules”.  This means that I/O Bays 1 and 2 can not handle “high speed” traffic, i.e. converged traffic. 

 This means that IF IBM comes out with a blade server that has a CNA on the motherboard, either:

 a) the blade’s CNA will have to route to I/O Bays 7-10
OR
b) IBM’s going to have to come out with a new BladeCenter chassis that allows the high speed converged traffic from the CNAs to connect to a high speed switch module in Bays 1 and 2.

So let’s think about this.  If IBM (and HP for that matter) does put CNA’s on the motherboard, is there a need for additional mezzanine/daughter cards?  This means the blade servers could have more real estate for memory, or more processors.   If there’s no extra daughter cards, then there’s no need for additional I/O module bays.  This means the blade chassis could be smaller and use less power – something every customer would like to have.

I can really see the blade market moving toward this type of design (not surprising very similar to Cisco’s UCS design) – one where only a pair of redundant “modules” are needed to split converged traffic to their respective fabrics.  Maybe it’s all a pipe dream, but when it comes true in 18 months, you can say you heard it here first.

Thanks for reading.  Let me know your thoughts – leave your comments below.

I’ve recently posted some rumours about IBM’s upcoming announcements in their blade server line, now it is time to let you know some rumours I’m hearing about HP.   NOTE: this is purely speculation, I have no definitive information from HP so this may be false info.  That being said – here we go:

Rumour #1:  Integration of “CNA” like devices on the motherboard. 
As you may be aware, with the introduction of the “G6″, or Generation 6, of HP’s blade servers, HP added “FlexNICs” onto the servers’ motherboards instead of the 2 x 1Gb NICs that are standard on most of the competition’s blades.  FlexNICs allow for the user to carve up a 10Gb NIC into 4 virtual NICs when using the Flex-10 Modules inside the chassis.  (For a detailed description of Flex-10 technology, check out this HP video.)  The idea behind Flex-10 is that you have 10Gb connectivity that allows you to do more with fewer NICs. 

SO – what’s next?  Rumour has it that the “G7″ servers, expected to be announced on March 16, will have an integrated CNA or Converged Network Adapter.  With a CNA on the motherboard, both the ethernet and the fibre traffic will have a single integrated device to travel over.  This is a VERY cool idea because this announcement could lead to a blade server that can eliminate the additional daughter card or mezzanine expansion slots therefore freeing up valueable real estate for newer Intel CPU architecture.

Rumour #2: Next generation Flex-10 Modules will separate Fibre and Network traffic.

Today, HP’s Flex-10 ONLY allows handles Ethernet traffic.  There is no support for FCoE (Fibre Channel over Ethernet) so if you have a Fibre network, then you’ll also have to add a Fibre Switch into your BladeSystem chassis design. If HP does put in a CNA onto their next generation blade servers that carry Fibre and Ethernet traffic, wouldn’t it make sense there would need to be a module that would fit in the BladeSystem chassis that would allow for the storage and Ethernet traffic to exit? 

I’m hearing that a new version of the Flex-10 Module is coming, very soon, that will allow for the Ethernet AND the Fibre traffic to exit out the switch. (The image to the right shows what it could look like.)  The switch would allow for 4 of the uplink ports to go to the Ethernet fabric and the other 4 ports of the 8 port Next Generation Flex-10 switch to either be dedicated to a Fibre fabric OR used for additional 4 ports to the Ethernet fabric. 

If this rumour is accurate, it could shake up things in the blade server world.  Cisco UCS uses 10Gb Data Center Ethernet (Ethernet plus FCoE); IBM BladeCenter has the ability to do a 10Gb plus Fibre switch fabric (like HP) or it can use a 10Gb Enhanced Ethernet plus FCoE (like Cisco) however no one currently has a device to split the Ethernet and Fibre traffic at the blade chassis.  If this rumour is true, then we should see it announced around the same time as the G7 blade server (March 16).

That’s all for now.  As I come across more rumours, or information about new announcements, I’ll let you know.

By now I’m sure you’ve read, heard or seen Tweeted the announcement that Cisco, EMC and VMware have come together and created the Virtual Computing Environment coalition .   So what does this announcement really mean?  Here are my thoughts:

Greater Cooperation and Compatibility
Since these 3 top IT giants are working together, I expect to see greater cooperation between all three vendors, which will lead to understanding between what each vendor is offering.  More important, though, is we’ll be able to have reference architecturethat can be a starting point to designing a robust datacenter.  This will help to validate that an “optimized datacenter” is a solution that every customer should consider.

Technology Validation
With the introduction of the Xeon 5500 processor from Intel earlier this year and the announcement of the Nehalem EX coming early in Q1 2010, the ability to add more and more virtual machines onto a single host server is becoming more prevalent.  No longer is the processor or memory the bottleneck – now it’s the I/O.  With the introduction of Converged Network Adapters (CNAs), servers now have access to  Converged Enhanced Ethernet (CEE) or DataCenter Ethernet (DCE) providing up to 10Gb of bandwidth running at 80% efficiency with lossless packets.  With this lossless ethernet, I/O is no longer the bottleneck.

VMware offers the top selling virtualization software, so it makes sense they would be a good fit for this solution.

Cisco has a Unified Computing System that offers up the ability to combine a server running a CNA to a Interconnect switch that allows the data to be split out into ethernet and storage traffic.  It also has a building block design to allow for ease of adding new servers – a key messaging in the Coalition announcement.

EMCoffers a storage platform that will enable the storage traffic from the Cisco UCS 6120XP Interconnect Switch and they have a vested interest in VMware and Cisco, so this marriage of the 3 top IT vendors is a great fit.

Announcement of Vblock™ Infrastructure Packages
According to the announcement, the Vblock Infrastructure Package “will provide customers with a fundamentally better approach to streamlining and optimizing IT strategies around private clouds.”  The packages will be fully integrated, tested, validated, and that combine best-in-class virtualization, networking, computing, storage, security, and management technologies from Cisco, EMC and VMware with end-to-end vendor accountability.  My thought on these packages is that they are really nothing new.  Cisco’s UCS has been around, VMware vSphere has been around and EMC’s storage has been around.  The biggest message from this announcement is that there will soon be  “bundles” that will simplify customers solutions.  Will that take away from Solution Providers’ abilities to implement unique solutions?  I don’t think so.  Although this new announcement does not provide any new product, it does mark the beginning of an interesting relationship between 3 top IT giants and I think this announcement will definitely be an industry change – it will be interesting to see what follows.

UPDATE – click here check out a 3D model of the vBlocks Architecture.

According to IBM’s System x and BladeCenter x86 Server Blog, the IBM BladeCenter HS22 server has posted the best SPECweb2005 score ever from a blade server.  With a SPECweb2005 supermetric score of 75,155, IBM has reached a benchmark seen by no other blade yet to-date.  The SPECweb2005 benchmark is designed to be a neutral, equal benchmark for evaluting the peformance of web servers.  According to the IBM blog, the score is derived from three different workloads measured:

• SPECweb2005_Banking – 109,200 simultaneous sessions
• SPECweb2005_Ecommerce – 134,472 simultaneous sessions
• SPECweb2005_Support – 64,064 simultaneous sessions

The HS22 achieved these results using two Quad-Core Intel Xeon Processor X5570 (2.93GHz with 256KB L2 cache per core and 8MB L3 cache per processor—2 processors/8 cores/8 threads). The HS22 was also configured with 96GB of memory, the Red Hat Enterprise Linux® 5.4 operating system, IBM J9 Java® Virtual Machine, 64-bit Accoria Rock Web Server 1.4.9 (x86_64) HTTPS software, and Accoria Rock JSP/Servlet Container 1.3.2 (x86_64).

It’s important to note that these results have not yet been “approved” by SPEC, the group who posts the results, but as soon as they are, they’ll be published at at http://www.spec.org/osg/web2005

The IBM HS22 is IBM’s most popular blade server with the following specs:

• up to  2 x Intel 5500 Processors
• 12 memory slots for a current maximum of 96Gb of RAM
• 2 hot swap hard drive slots capable of running RAID 1 (SAS or SATA)
• 2 PCI Express connectors for I/O expansion cards (NICs, Fibre HBAs, 10Gb Ethernet, CNA, etc)
• Internal USB slot for running VMware ESXi
• Remote management
• Redundant connectivity

I’ve gotten a lot of response from my first post, “REVEALED: IBM’s Nexus 4000 Switch: 4001I” and more information is coming out quickly so I decided to post a part 2. IBM officially announced the switch on October 20, 2009, so here’s some additional information:

• The Nexus 4001I Switch for the IBM BladeCenter is part # 46M6071 and has a list price of $12,999 (U.S.) each
• In order for the Nexus 4001I switch for the IBM BladeCenter to connect to an upstream FCoE switch, an additional software purchase is required. This item will be part # strong>49Y9983, “Software Upgrade License for Cisco Nexus 4001I.” This license upgrade allows for the Nexus 4001I to handle FCoE traffic. It has a U.S. list price of $3,899
• The Cisco Nexus 4001I for the IBM BladeCenter will be compatible with the following blade server expansion cards
  • 2/4 Port Ethernet Expansion Card, part # 44W4479
  • NetXen 10Gb Ethernet Expansion Card, part # 39Y9271
  • Broadcom 2-port 10Gb Ethernet Exp. Card, part # 44W4466
  • Broadcom 4-port 10Gb Ethernet Exp. Card, part # 44W4465
  • Broadcom 10 Gb Gen 2 2-port Ethernet Exp. Card, part # 46M6168
  • Broadcom 10 Gb Gen 2 4-port Ethernet Exp. Card, part # 46M6164
  • QLogic 2-port 10Gb Converged Network Adapter, part # 42C1830
• (UPDATED 10/22/09) The newly announced Emulex Virtual Adapter WILL NOT work with the Nexus 4001I IN VIRTUAL NIC (vNIC) mode.  It will work in pNIC mode according to IBM.

The Cisco Nexus 4001I switch for the IBM BladeCenter is a new approach to getting converged network traffic. As I posted a few weeks ago in my post, “How IBM’s BladeCenter works with Cisco Nexus 5000” before the Nexus 4001I was announced, in order to get your blade servers to communicate with a Cisco Nexus 5000, you had to use a CNA,and a 10Gb Pass-Thru Module as shown on the left. The pass-thru module used in that solution requires for a direct connection to be made from the pass-thru module to the Cisco Nexus 5000 for every blade server that requires connectivity. This means for 14 blade servers, 14 connections are required to the Cisco Nexus 5000. This solution definitely works – it just eats up 14 Nexus 5000 ports. At $4,999 list (U.S.), plus the cost of the GBICs, the “pass-thru” scenario may be a good solution for budget conscious environments.

In comparison, with the IBM Nexus 4001I switch, we now can have as few as 1 uplink to the Cisco Nexus 5000 from the Nexus 4001I switch. This allows you to have more open ports on the Cisco Nexus 5000 for connections to other IBM Bladecenters with Nexus 4001I switches, or to allow connectivity from your rack based servers with CNAs.

Bottom line: the Cisco Nexus 4001I switch will reduce your port requirements on your Cisco Nexus 5000 or Nexus 7000 switch by allowing up to 14 servers to uplink via 1 port on the Nexus 4001I.

For more details on the IBM Nexus 4001I switch, I encourage you to go to the newly released IBM Redbook for the Nexus 4001I Switch.