"What makes a SAN stop"
Join Christopher Poelker, co-author, Storage Area Networks for Dummies, for a lesson on what makes a SAN stop. This lesson explores the things that cause problems in SAN operations.
More about "Lesson 4: What makes a SAN stop"
If you run into problems with your SAN, it can be very difficult to pinpoint the exact cause. It could be something very simple like a pinched cable or a mislabeled cable. Or it could be a greater problem like congestion caused from poor topology design or the way zoning was set up. In this chapter, you'll learn some best practices like proper cable labeling and setup, how to spread out the I/O load evenly and using a maximum of 16 switches per fabric. You'll also get a firm handle on the best naming conventions and tapping into resources for logical design plans. Want to find out the No. 1 culprit for making a SAN stop? View lesson four.
What you'll walk away with:
** An understanding of what causes SAN problems
** How to avoid poor SAN design
** Knowledge of how to prevent equipment problems
** An understanding of other SAN issues
Get the Lesson 4
After reading SAN School lessons 1-4, take the first SAN School quiz.
About Christopher Poelker:
Christopher Poelker is a storage architect at Hitachi Data Systems. Prior to Hitachi, Chris was a lead storage architect/senior systems architect for Compaq Computer, Inc., in New York. While at Compaq, Chris built the sales/service engagement model for Compaq StorageWorks, and trained most of the company's VAR's, Channel's and Compaq ES/PS contacts on StorageWorks. Chris' certifications include: MCSE, MCT (Microsoft Trainer), MASE (Compaq Master ASE Storage Architect), and A+ certified (PC Technician).
Back to the SAN School table of contents.
This was first published in May 2005