Premium Content

Access "Intelligence belongs in the network and on the switch"

Published: 16 Oct 2012

The low-risk route is through appliances--if they don't work, you can yank 'em. Easy, right? Cisco will put intelligence in its switch. Or I'll just run my Veritas software on my new Brocade switch, right? Well, maybe someday, but I highly doubt a lot of you are going to run to this new paradigm soon. First, let me define what I'm talking about. Today we run virtualization in the form of volume management in the host, (usually Veritas') and LUN masking/mapping in the arrays. We use volume management to carve up physical devices into logical ones. We mirror with it and often replicate with an array-based technology. These are essential functions and perfect examples of "services" that should run in the network--not on the end points. Why? Common repetitive software functions running in the network vs. the host mean far less software. If you're a big shop today, you run different versions of Veritas Volume Manager on your Solaris or Windows boxes, HP/IBM/SGI etc. If those core functions ran in the fabric, you'd support only a handful of platforms--vs. hundreds... Access >>>

Access TechTarget
Premium Content for Free.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

What's Inside


More Premium Content Accessible For Free