Contoso Labs-Storage Purchasing (SAS config)

Contoso Labs-Storage Purchasing (SAS config)

  • Comments 4
  • Likes

Contoso Labs Series - Table of Contents

Now that we've got our JBODs and our file servers, we need to tackle an underappreciated aspect of this solution: The SAS connectivity itself.

How Many?

After discussing our configuration and layout with folks inside of Microsoft with serious experience in Storage Spaces, we learned that having as much connectivity to our JBODs as possible was going to be the ideal configuration. Our planned SOFS cluster was 3 file servers with full connectivity to 3 JBODs. Each JBOD has dual controllers, each controller with 3 SAS ports. That meant we could provide full dual-path access from each server, to each JBOD, for a total of 18 connections.

In practical terms, that meant we needed six external SAS ports in each file server. That started limiting our options for SAS controllers. There are many 2-port cards out there, and a smaller selection of 4-port ones. No one makes a 6-port card. That meant we were definitely going to need to commit both of our PCIe slots to SAS controllers. We briefly considered a 4-port and a 2-port card, but decided that consistency and symmetry were useful here. One driver, and losing a card loses 1 path to each JBOD, instead of potentially losing all access to 1 of them. We chose cards from LSI for our solution.

LSI

We selected LSI 9206-16e cards for our SAS connectivity. These cards checked all the right boxes for us.

  • They're certified for use with Storage Spaces.
  • They have 4 external SAS ports each.
  • DataON supports them with their JBODs.
  • They're half-height PCIe cards, which means they work in both slots of our servers.

The only drawback we could find with using these cards is that they have SFF-8644 connectors on them. These are lesser-used small form factor connectors than the more well-known SFF-8088 type you might be familiar with on most SAS equipment. The smaller size means 4 ports can fit comfortably on a half-height card, where the larger SFF-8088's would be too large. That meant getting specialized cabling, a minor hassle at worst.

Now that we have all the pieces of our storage puzzle identified, we can build out some file server clusters and get down to business, right? Well, not quite yet. When time comes to put everything together, we'll have a lot more information about our storage configuration, and some information about how it's all working. Next up, we'll circle back to our purchasing decisions, specifically the network gear.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Hi, Carmen!

    You've choose DNS-1600 JBOD, but it has only two In-ports per controller (third is Out-port just for expansion chaining). So, only two host can be connected to single JBOD using dual-path connection.
    Can you, please, explain, how would you connect three servers to these JBODs?

  • @Dmitry Interesting that you caught that! Since these devices are straightforward SAS JBODs, the Out-port can be used as another direct SAS connection to an HBA, just as the other two ports are. We confirmed that this works and is supported with DataON before we made the purchase. After wiring it up with straight connections, everything works perfectly.

  • Thanks for clarification, Carmen!
    We're using hardware from Supermicro, which used to have one In- and two Out-ports.
    Unfortunately our supplier can't say for sure that connecting HBAs to Out ports will work at all :(
    Will ask them again more insistently. Hopefully, it will work...

    Really looking forward to the next posts, especially about storage spaces design and tests!

  • @Demonixed - In theory, for the device to work and be certified, any "Out" port should work just fine. Of course, if your vendor hasn't tested it and won't support it, that'd make me very nervous for production purposes. That's why I make sure to check with DataON before we purchased.