I have some sysadmins trying to add Dell storage to a Cisco 9k. They are seeing a lot of latency in storage operations. Dell insists that the problem lies in needing flow control enabled. My question is more general. If the client to the storage is say three hops away from the 9k with the SAN - is there any need to have flow control enabled at all three switches? e.g. [ESX]--Edge SW--Core SW-Cisco 9K-[Dell Storage].
Or would flow control only be relevant at the CIsco 9k to which the Dell storage is attached?
I think the answer is that if the Ethernet port on the Cisco 9k has FC enabled and it received a flow control frame from the Dell - it would pause the next transmission until a free buffer on the Dell. In this cause there would be no need to propagate flow control info to the other switches or the client/the ESX.
In general, if you've experiencing "latency", flow control shouldn't help unless the "latency" is due receiver packet drops and even then, the transmitting device may drop the packets instead, possible even more so. I.e., flow control is going to force more packets into the transmitting device's port queue. Basically, flow control should keep the Dell SAN device from dropping packets it receives, which it cannot keep up with, but in turn, those packets are now queued on the 9K and can drop there. It's possible the 9K might, without tuning, drop more packets than the Dell SAN device would with FC disabled.
If packets are being queued and/or dropped, you want to determine where's that's happening and if that might be mitigated. For example, perhaps the problem is the SAN sending to the client, which I assume (the client) does not have a 10g connection.
In answer to your question, no, you wouldn't want to generally enable Ethernet flow control end-to-end (or generally use it), especially the "ordinary" Ethernet variant which completely blocks the port. Again, it's generally better if you try to eliminate any packet drops and/or better manage port congestion using QoS techniques.
Consider if there's congestion on the edge<>core link and you have a mix of traffic. E.g. traffic to/from the SAN and perhaps VoIP traffic. If the SAN traffic is causing congestion, you don't want to block the VoIP traffic.
I've got a one problem. Me and my friend have the same ISP. I checked my External IP address at WhatIsMyIp.com and my friend do it to. And we saw we have the same External IP.So my question is can 2 routers have the same External IP address?If i'm right 2...
LISP Protocol (Location Identifier Separation Protocol)! - The LISP protocol has become a brilliant stardom with the digital transformation that we are now experiencing. - Today we will talk about the LISP protocol and its advantages and method of p...
SD-Access provides automated end-to-end services (such as segmentation, quality of service, and analytics) for user, device, and application traffic. SD-Access automates user policy so organizations can ensure the appropriate access control and applicati...
Purpose: This document shows you how to create a group-based security policy in Cisco DNA Center.
Security policies determine the types of network traffic permitted or denied between scalable groups. Scalable groups are a critical compo...
Are you an experienced network professional?
If yes, we'd like to understand how we can better organize network management activities in a way that makes sense to you. Your response will help Cisco improve a product feature that could benefit you.&nb...