PRO+ Premium Content/Storage magazine

Thank you for joining!
Access your Pro+ Content below.
Vol. 1 No. 12 February 2003

Can Brocade's SilkWorm 12000 take the pain out of expanding your SAN?

When you expand your storage area network (SAN), you'll discover just how well your architecture accommodates growth while preserving performance, availability and manageability. There are at least three critical growth-related abilities your switching architecture should provide: The ability to add ports in a hurry without sacrificing performance and without requiring a fundamental redesign; The ability to scale with little or no downtime; and The ability to abstract and control performance and security parameters. With those requirements in mind, I took a close look at Brocade's SilkWorm 12000, the core switch for users who have settled on the Brocade core/edge architecture or are considering it. Does it meet those tests? Availability through redundancy The SilkWorm 12000 chassis contains two logical 64-port switches, each accommodating up to four 16-port blades. Both switches are supported by a pair of clustered control processors (CPs) running a Linux kernel with Brocade's Fabric OS running as a layered application on each. ...

Access this PRO+ Content for Free!

By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.

You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

Features in this issue

  • Midrange Arrays Inherit High-End Smarts

    Virtualization layers, once a feature of only the most expensive storage subsystems, are beginning to ship with midrange storage systems.

  • Optimize database storage

    by  Jim Booth

    In this article, author and consultant Jim Booth maintains that different database objects may each require their own type of storage to make the database operations run more smoothly. Whether you're dealing with tablespaces, indexes, redo logs or archives -- there's a right and wrong storage choice for each database component. This article explains what they are.

  • Inside the new Symmetrix

    by  Michael Desmond

    Inside the new Symmetrix

Columns in this issue