Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

News

7/27/2009
03:13 PM
George Crump
George Crump
Commentary
50%
50%

Unifying The Infrastructure

We've spent the last several entries discussing the unification of storage and there is one aspect of unification that I have not discussed; unifying the infrastructure. I do currently have a series of videos currently running with Information Week on FCoE so in this entry I'll just touc

We've spent the last several entries discussing the unification of storage and there is one aspect of unification that I have not discussed; unifying the infrastructure. I do currently have a series of videos currently running with Information Week on FCoE so in this entry I'll just touch on the high points.Companies like Brocade, Cisco, Emulex and QLogic have all brought FCoE products to the market. Some are a little more aggressive with their enthusiasm than others. While some are hinting at a broad sweeping changeout, IT does not typically happen that way, especially at the infrastructure level. Infrastructure unification via FCoE is likely to happen a rack at a time. While there are a few corner cases, most data centers are not going to rip out their current fibre cable infrastructure for a new one. The exception being if you are building a new data center from scratch. It is critical that the supplier you choose for FCoE remains fully committed to standard fibre channel (FC).

There will be servers that already have existing separate fibre and IP connections within existing racks that you may need to upgrade either the IP or fibre performance to. Replacing the whole rack's cable management to upgrade the performance of one server may not be worth the effort. Additionally it is possible that these servers will need more performance that 10GBE connection can provide, and you may want the flexibility to move to 16GB FC for example.

Second, don't expect much from FCoE in this first iteration other than a reduced number of cables and potentially lowering the total cost of network interface cards (NICs). The reduced number of cables should lead to simplified cable management in the data center. Cable management, as we discussed in our four part series "Climbing out of the Spaghetti", in today's data center has risen almost to an art form. Any reduction in the number of cables is a huge step into bringing that process under control.

The other benefit of FCoE is a reduced number of NIC cards, although initially these may cost almost as much as the individual cards that go in servers; as is always the case the cost of these cards will come down over time. Price is not be the key factor here, heat is. By reducing the number of slots occupied by cards you increase airflow which should reduce heat and as a result power and cooling costs.

FCoE gets particularly interesting as companies begin to leverage some of the capabilities of the standard that will allow advanced integrated topology management and the ability to begin to imbed NIC level Quality of Service (QoS), which will be particularly helpful in virtual environments.

More on the need for NIC QoS and managing the IO Blender of Virtualization in our next entry.

Track us on Twitter: http://twitter.com/storageswiss

Subscribe to our RSS feed.

George Crump is founder of Storage Switzerland, an analyst firm focused on the virtualization and storage marketplaces. It provides strategic consulting and analysis to storage users, suppliers, and integrators. An industry veteran of more than 25 years, Crump has held engineering and sales positions at various IT industry manufacturers and integrators. Prior to Storage Switzerland, he was CTO at one of the nation's largest integrators.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.