If you think the title makes no sense, read this post and other posts related to the original post.

Although this will automatically put me into the mind-losing group, from the sales and non-technical marketing perspective – note the emphasis – I tend to agree with his “politically incorrect” view of iSCSI. I doubt that any of these critics have ever spent hours – I have, and it wasn’t fun – pitching their solution to the customer only to be asked “Is this NAS thing of yours that SAN thing?”

From the NetApp perspective, I guess that iSCSI indeed is Network-Attached Storage Area Network-kinda Storage. Seriously, in simple terms, it’s just another way to allocate NetApp storage to clients/hosts. Because NetApp filers are versatile (NAS, iSCSI, SAN), they don’t really need to care or argue about this with their prospects and/or customers. (Personally I think there’s a better way to provide a single solution for integrated block and file storage – more about this some other time).

Says Marc Farley:

It does not matter if the network is Fibre Channel or Ethernet (or carrier pigeons), the network is simply a way to transmit information for a storage application.

Well, this is exactly why I do not equal iSCSI with SAN. It does matter. I don’t have anything against accessing my database over FC (as long as I can afford it). And yes, in some cases I would definitively consider recommending Ethernet instead, but I would never recommend or even consider using PTP (Pigeon Transport Protocol). (Not yet, anyway. Maybe one day we’ll have storage-enabled pigeons that will be able to use spooky action at a distance to overcome limitations of PTP v1. Even with PTP v2 we’d still need a good MPIO mechanism for pigeons to prevent Single Point Of Flying, or SPOF – it’s gonna take time.)

When people hear “SAN” many of them will – maybe mistakenly, as this SAN could be Ethernet-based – visualize thin orange cables, low (lower than GbE) latencies, dedicated FC storage switches and the rest of FC-SAN h/w and s/w. I am not saying that Gigabit Ethernet and iSCSI won’t or can’t do, but it’s just not the same. What I am saying, though, is that this isn’t any more PC and/or less confusing than Dave’s opinion.

iSCSIs vendors would like you to think iSCSI is SAN and Ethernet is as good as FC, versatile storage vendors say “whatever you want, pal”, and so on and so forth. It’s (not) that simple! Devil said (not actually, but in a movie): “Consider the source, son!”

If we wanted to be technically correct or very PC from the technical point of view, we couldn’t easily communicate with decision makers and other stakeholders (assuming that everything offered satisfies requirements from the customer’s RFP, why would application owner have to care what’s happening behind that mount point?), which is why occasional technical heresy can be a skill.

P.S. By the way, whatever happened to IP-SAN? It’s been a while since I heard iSCSI vendors using this term. Did it have to go because it had a low-end (as in “Netgear launches dirt-cheap IP SAN” Ouch!) ring to it? That’s too bad, because I kind of like it and it means what it does.


One Response to Is iSCSI NAS SAN?

  1. davehitz says:

    Drink the marketing Kool-Aid. Join the business Dark Side. I am your father, Luke. 🙂

    Seriously, you exactly get my point.

    Interesting that you ask what happened to IP-SAN, because Mr. Pearson over at IBM just did a post arguing that if you run iSCSI over a dedicated, secure network, then you should call it IP-SAN, but if you run it over a general purpose TCP/IP network then you should call it NAS.



Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: