"So, i am not sure that QoS would fit this scenario because the device causing the congestion, is getting the entire pipe. "
The basic CBWFQ example I provided will share bandwidth between flows. If you're currently using FIFO (often the default at DS3), and if your platform supports it, you might try what I suggested and see if it help. BTW, you would want it on egress, both sides.
"how is the bandwidth allocated between the flows? "
That depends on the actual implementation. "True" FQ, without weights, should insure each flow gets a equal proportional guaranteed share of bandwidth. Since some flows don't want their full guaranteed bandwidth, excess is proportionally provided to flows wanting more.
"What determines which connection gets bandwidth and how much? "
The scheduling algorithm.
"For example, are all connections guarenteed bandwidth? "
An equal share yes, absolute share, no.
"What if one connection wants to use all of the link?"
Depends on what other flows want.
4 flows, each wants all bandwidth - each gets 25%
4 flows, each wants half of all bandwidth - each gets 25%
4 flows, each wants 20% of all bandwidth - each gets 20% (20% unused)
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...