I really don't see congestion on the links. Not what I would suspect to be congestion. But shouldn't the return traffic be just as important as the traffic towards the servers, or more important since it is the data we are really concerned about?
Our two Data centers are the same way, they are connected by a Metro Ethernet connection and traffic is prioritized towards the one data center, but not the other one. Again shouldn't the priority be bi directional?
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
#1 QoS can be a very good thing! "Or .. bidirectional?" Unsure why you preface an "or", but bidirectional, ideally, should be used.
#2 Depends on the device and protocol. Often Cisco devices will mark some. If not, you can mark. (Also, you might need to provide [configure] "special" treatment even if the device auto marks.)
#3 The ideal is to mark (and verify) as early is possible. But it's not required to use QoS. (You can do QoS without markings.)
#4 Cores often don't mark, at that point within the network, they often "trust". Cannot say what impact ". . . everything is getting set to Default as it goes across the switch."
BTW, QoS markings are just a "shortcut" when looking at frames/packets for QoS processing. QoS markings aren't required to provide QoS treatments and QoS markings (alone) don't often guarantee QoS treatment.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...