Implementing a Cisco Fabric for Spectrum Virtualize Hyperswap Clusters
I wrote this previous post on the general requirements for SAN Design for Spectrum Virtualize Hyperswap and Stretched clusters. In this follow-on post, we'll look at a sample implementation on a Cisco or IBM C-type fabric. While there are several variations on implementation (FCIP vs Fibre-Channel ISL is one example) the basics shown here can be readily adapted to any specific design. This implementation will also show you how to avoid one of the most common errors that IBM SAN Central sees on Hyperswap clusters - where the ISLs on a Cisco private VSAN are allowed to carry traffic for multiple VSANs.
We will implement the below design, where the public fabric is VSAN 6, and the private fabric is VSAN 5. The below diagram is a picture of one of two redundant fabrics. The quorum that is depicted can be either an IP quorum or a third-site quorum. For the purposes of this blog post, VSAN 6 has already been created and has devices in it. We'll be creating VSAN 5, adding the internode ports to it and ensuring that the Port-Channels are configured correctly. We'll also verify that Port-Channel3 on the public side is configured correctly to ensure VSAN 5 stays dedicated as a private fabric. For the examples below, Switch1 is at Failure Domain 1. Switch 2 is at Failure Domain 2.
|Hyperswap SAN Design|
switch1# show interface port-channel3
Admin port mode is auto, trunk mode is auto
Port vsan is 1
Trunk vsans (admin allowed and active) (1,3,5,6)