One of the aspects I really enjoy about my job is that I get to learn from some of the world’s top network and data center design engineers, and I get to hear about technology adoption challenges across the world. If there is a complex network or data center design being worked by our customers, if our customers are under time pressure, or if our customers are facing key business or technical challenges, Cisco Services’ consultants are often called in to help. Globally then, they experience first hand the challenges of deploying advanced technologies. In this blog, in the same spirit as my OpenStack Deployment Challenges blog, I’d like to share their experiences on some of the most common challenges and misconceptions faced by our customers when building Storage Area Networks (SAN). I’ll publish this in 2 parts – so look out for the concluding part next week.
Before continuing, I’d like to thank two of our SAN expert consultants, Barbara Ledda and Wolfgang Lang, for sharing their experiences and challenges.
First, before I start, a caveat: please don’t take this as the definitive list of SAN design challenges! That said, they are some of our “favorite” issues that we see with customers. Let us know if you have a favorite to add to this list, please add a comment in the box below or ping me on Twitter (details below). Now on to the list …..
#1 Don’t assume that your server multi-pathing software is installed or working, or even licensed, or installed but never used/tested by your server team!
Designing a highly resilient SAN network design with built-in redundant paths is a key aim of our consulting team. On the server estate, such design requires that multi-pathing software [e.g. EMC PowerPath, Microsoft I/O (MPIO)] is installed and operational on each server. Such software creates redundant paths to the storage environment (among other capabilities).
However our experience shows that in many cases, the customer doesn’t have this installed or in cases even licensed. In other cases they’ve never tested this capability on their servers. Testing is important – I doubt if anyone is immune to making configuration mistakes when setting up a networking or compute device. We’ve come across this in real life: the first time when failover was required, the customer experienced an outage in the SAN network as a result of mis-configurations in their multipath software.
Therefore Lesson #1 is to make sure your server team are engaged in your SAN design process, and that they have this important software installed and tested, in a position to be able to exploit your advanced SAN design.
#2 Tendency to significantly over-estimate utilization on the SAN network.
You may think that as a hardware vendor, we like customers to over-specify their network. This is not the case – we are always looking for the most cost-effective solution for our customers. We have, in practice, noticed that customers have a tendency to significantly over-estimate the utilization on their SAN network. For example, it’s not uncommon for us to review customer designs were they have specified 16 GB/s links when they will use a maximum of 1 Gbp/s!
As you will be aware, Ethernet LAN network are able to deal with packet loss, and they rely on the upper layer protocols to do so. This is not the same for Fibre Channel networks which require the traffic flows to be lossless in order to avoid I/O disruption and loss to connectivity to storage. Consequently, to avoid any risk of congestion, SAN designers tend to overprovision their SAN.
However over-provisioning of the SAN links is not always the solution, because in many cases, the root cause of the congestion is that some receivers of the traffic flows are “slow drain devices” – that is, they are “slow” in processing the packets. You can read more on this in the whitepaper here.
Hence while over-provisioning is a necessary design technique for SAN, the perception we find is that typically customers think they need 5-10x over provisioning; our consultants’ experience indicates that typically you need only double.
Lesson #2: Get expert help to accurately assess your SAN capacity needs.
That, then, concludes my part 1.
In the meantime, I’d like to hear what are your top SAN design challenges? Let me know via the comments box below or contact me on Twitter and we can discuss with our Cisco Services’ SAN design experts! And finally, look out for my part 2.
Hi Guys, Anybody knows if Cisco address the vulnerability below? Are the CUCM and CUC affected by this vulnerability since they are using Linux OS? Although it is an appliance type where administrators cannot change anything on the OS level but seems...
Hello, We are implementing VXLAN BGP EVPN in our Datacenter. Our VXLAN Fabric consists of two Nexus 9364c Switches (Spines) and four Nexus C93108TC Switches (Leafs). The Leaf switches are forming two pairs of vPC VTEP Switches (Leaf1 with Leaf2...
Looking into using EVPN by watching this video: https://www.youtube.com/watch?v=D9k9_hRdrGc In a very simple topology (6 switches) What is the easiest way to setup EVPN with Anycast Gateway when it comes to the VRF (tenant) aspect? I have one ne...
Been dealing with a possible bad Nexus 3172T switch in a VPC pair. After an upgrade, an uplink port in MEC on the Secondary Nexus connection to the Core failed. Both Primary and Secondary in VPC pair have 2x10G connections to the Core. &nbs...
Hi,We have a local DNS server redirecting domains to my local servers (see below picture)let's say (IPs not real):example1.com goes to 192.168.1.100 an IIS web serverexample2.com goes to 192.168.1.101 a Linux web serverin local network everything is worki...