Storage area network scaling top five tips

Channel takeaway: Storage area network (SAN) scaling doesn't have to be difficult for VARs. By keeping a few guidelines in mind, adding another fabric to the SAN can be a hassle-free process. Check out these five suggestions to keep the SAN scaling process running smoothly.

If you're currently reviewing your

    Requires Free Membership to View

SAN topology with an eye toward scaling beyond a single fabric, there are a variety of technologies and products that can help you accomplish your goal. There are also a few pitfalls to watch out for, both during the initial assessment and the actual deployment. Here are a few things to keep in mind:

Even if you are not planning on combining devices from different fabrics, some upfront planning now can reduce, if not eliminate, future interoperability challenges. Remember that:

  • Routing is not just a technology for spanning distances. It can be equally of use in a local environment, for example, segmentation of physically interconnected SAN islands and protocol conversion to support iSCSI-enabled servers.
  • Plan and design for growth, maintenance and diagnostic of your storage network.
  • Use SRM tools to keep track of and monitor the health and status of your storage network, including performance and resource usage. Change control and management software can help to proactively determine and isolate problems before they occur.
  • Utilize unique, descriptive naming and addressing conventions including domain IDs. This is helpful regardless of if you are merging fabrics or keeping them isolated.
  • Enable domain ID lockdown to insure unique domain IDs on switches, particularly for FICON cascade, that also require fabric binding security.
  • Isolate traffic and workload with segmentation, zoning, LUN masking and mapping.

Read the rest of Schulz's tip at SearchStorage.com.

About the author: Greg Schulz is a senior analyst with the independent storage analysis firm, The Evaluator Group Inc. Greg has 25 years of IT experience as a consultant, end user, storage and storage networking vendor, and industry analyst. Greg has worked with Unix, Windows, IBM Mainframe, OpenVMS and other hardware/software environments. In addition to being an analyst, Greg is also the author and illustrator of Resilient Storage Networks, Greg has contributed material to Storage Magazine. Greg holds both a computer science and software engineering degree from the University of St. Thomas.

This was first published in May 2007

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
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
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.