Tip

Choosing a class of SAN service: Class 3

Rick Cook

The three most popular classes of service for SANs in a Fibre Channel fabric are 1, 2 and 3. Class 1 is a virtual direct connection through the SAN between the transmitting and receiving devices, class 2 uses packets which are acknowledged transmission (either after each packet or every N packets) and can follow multiple paths through the switch fabric. Class 3 also uses multiple paths but doesn't use the Fibre Channel acknowledgment. Detection and retransmission of corrupted information are handled by a higher-level protocol like IP rather than through Fibre Channel. All three classes are popular because they all serve different needs.

If you're going to do a lot of multicasting, then Class 3 Fibre Channel service is for you. It's a connectionless service using frame switching, like Class 2. However unlike Class 2, Class 3 is designed around a datagram model and Fibre Channel doesn't check for missing or corrupted frames. Flow control and data integrity are handled by a higher-level protocol such as TCP (Transmission Control Protocol). However there is link-level flow control between the fabric and each connected device.

In multicasting, the transmitting device sends the same information to multiple receiving devices. Since the receiving devices do not send back acknowledgments, rejections or other messages, this service cuts the load on the transmitting device considerably. If the higher-level protocol on the receiving device

Requires Free Membership to View

discovers it has a missing or corrupted packet, it can ask for a retransmission of the problem sequence, but that means much less back traffic than in the other classes of service.

The disadvantage of Class 3 service is, of course, the lack of acknowledgments. This is compounded by the fact that in Class 3 service the fabric may occasionally discard some frames when traffic is heavy. The higher-level protocol at the receiving device can ask for a retransmission of the sequence, but that degrades device and fabric throughput.

Additional resources:

.

About the author: Rick Cook has been writing about mass storage since the days when the term meant an 80K floppy disk. The computers he learned on used ferrite cores and magnetic drums. For the last twenty years he has been a freelance writer specializing in storage and other computer issues.


This was first published in December 2000

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.