IBM FlashSystem

IBM FlashSystem

Find answers and share expertise on IBM FlashSystem

 View Only

Announcements for August 2007

By Tony Pearson posted Tue August 28, 2007 08:50 AM

  

Originally posted by: TonyPearson


The proof-of-concept that IBM Haifa research center developed back in 1998 became what we now call the iSCSI protocol.The book iSCSI: The Universal Storage Connection introduces the history as follows:
In the fall of 1999 IBM and Cisco met to discuss the possibility of combining their SCSI-over-TCP/IP efforts. After Cisco saw IBM's demonstration of SCSI over TCP/IP, the two companies agreed to develop a proposal that would be taken to the IETF for standardization.

There are three ways to introduce iSCSI into your data center:

  • Through a gateway, like the IBM System Storage N series gateway, that allows iSCSI-based servers connect to FC-based storage devices
  • Through a SAN switch or director, a FC-based server can access iSCSI-based storage, an iSCSI-based server accessing FC-based storage, or even iSCSI-based servers attaching to iSCSI-based storage.
  • Directly through the storage controller.

IBM has been delivering the first method with its successful IBM System Storage N series gateway products, buttoday we have announced additional support for the second and third methods.Here's a quick recap.

New SAN director blades

Supporting the second method, IBM TotalStorage SAN256B Director is enhanced to deliver iSCSI functionality with a new M48 iSCSI Blade, which includes 16 ports (8 Fibre Channel ports; and 8 Ethernet ports for iSCSI connectivity). We also announced a new Fibre Channel M48 Blade which provides 10 Gbps Fibre Channel Inter Switch Link (ISL) connectivity between SAN256B Directors.

Entry Level Disk Systems

Supporting the third method, IBM introduces new iSCSI-capabable disk systems, including the IBM System Storage DS3300 model using SAS drives, N3300 A10/A20 models and N3600 A10/A20 models supporting use of FC and SATA drives.The DS3000 Express models include frequently requested options, including appropriate host bus adapters (HBA) and cables. Likewise, we have announced hardware features for our IBM N series , such as TCP offload engine (TOE) network interface cards (NIC), HBA and cables.

With support for Boot-over-iSCSI, diskless rack-optimized and blade servers can boot Windows or Linux over Ethernet,eliminating the management hassles with internal disk.

All of this is part of IBM's overall push into the Small and Medium size Business marketplace, making it easier to shop for and buy from IBM and its many IBM Business Partners, easier to deploy and install storage, and easier tomanage the storage once you have it.

technorati tags: , , , , , , , , , , , , , , , , , , , , ,


#StorageAreaNetworks
#PrimaryStorage
#Storage
4 comments
4 views

Permalink

Comments

Thu September 06, 2007 09:19 AM

Mark, Good comments.
The reference to "In the fall of 1999" is directly quoted from the book, perhaps you can forward your comments to the publisher, Addison Wesley, to see if your suggested additions can influence the next revision, if they have one.

Thu August 30, 2007 08:51 AM

"In the fall of 1999 IBM and Cisco met to discuss ..."
You might like to add that HP and Adaptec were also there, indeed Adaptec had an almost product that did SCSI over Ethernet at the time.
SCSI over some network protocol wasn't new, in the late 90's I worked at a small company that had been doing SCSI over UDP and IPX since 1994 and there were others out there, too.
However, iSCSI was a thing who's time had come. I wasn't at the Haifa meeting, though I was at the Pittsburgh iSCSI BOF and all subsequent IPS IETF and interim meetings.
Actually IBM's first iSCSI product caused more harm than good, it was based on a very early unratified version of the specification and left some inter-operability problems behind it. Where the community should thank IBM is when IBM decided to give John Hufferd resposibilities in iSCSI and he became a co-ordinator in the IPS workgroup and a very vocal proponent of making iSCSI useful to the market.
Prior to John's involvement the IPS group was dominated by the research teams of IBM, HP, EMC and Lucent. Their vision of iSCSI was that it wouldn't be useful until 10Gb/S Ethernet was around and that it was an ideal stepping stone from which to design the necessary hardware offloads and RDMA protocols.
Those of use trying to promote the idea of iSCSI in small enterprises without the whizzes and bangs, where even 100Mb/s Ethernet was good enough were drowned out and side-lined until the arrival of John Hufferd.
John saw the best way for iSCSI to succeed was to make it an ubiquitous technology. Microsoft went on board with that and produced their initiator. Those two factors are probably more important than anything else, any one with a Windows server or an XP workstation can deploy a simple iSCSI link in seconds.
The IPS work group has gone on to do good work with regards to RDMA and mapping iSCSI over RDMA. However, without the likes of John and those of us who created and then promoted iSCSI in to the small business space, the IPS efforts would still only be a hypothetical exercise for academics. Or at best, iSCSI would be a very small niche market unheard of by the mainstream.

Wed August 29, 2007 03:12 PM

I would differentiate in the sense that gateways allow for LUN masking- you allocate all the LUNs you want available over iSCSI to the gateway which dictates which iSCSI initiators can see which LUNs.
Thad said, this definitely could be considered a switch- I take back my last comment :)

Wed August 29, 2007 02:45 PM

OSG, if it is a switch, isn't that method 2, a switch that allows iSCSI-based servers accessing FC-based storage? Both Qlogic and Brocade are switch vendors, so I would not really call these gateways.