I work for a small local ISP and we recently started selling VoIP phone solutions. A hand full of our customers use Adtrans or PBX boxes on site. We generally plug their internal network into one port on the modem, and their Adtran or PBX into another port on the modem. The issue that we are running into is that when the link to the internal network hogs all of the bandwidth, it doesn't allow sufficient bandwidth to the phone system. This of course causes a world of issue for the phones. We don't want to put the phone systems in the internal network because we don't want the phone traffic to be natted either. So our idea is to run a line from the modem, into a switch, and a link from the internal network into the switch, and a link from the phone system into switch. This way we can implement QoS for the phone system port on the switch to be prioritized over the internal network port. The only issue is that i'm not sure how this is best done, if even possible. So my question is this; if i have a 2960 (or another cisco switch) can i make one port prioritize its traffic over another ALWAYs and in a very strict manor?
You can configure a policy map on a physical port that specifies which traffic class to act on. Actions can include trusting the CoS, DSCP, or IP precedence values in the traffic class; setting a specific DSCP or IP precedence value in the traffic class; and specifying the traffic bandwidth limitations for each matched traffic class (policer) and the action to take when the traffic is out of profile (marking).
thanks for the quick response, that being said; can i make a policy map that limits to their bandwidth speed, then set priority to DSCP maked packets of "EF" and have all traffic from the phone system port marked as EF? Does this make sense? So essentially all traffic that arrives on the phone port gets marked EF, then it gets prioritized because of the policy?
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.
(I believe) the 2960 supports ingress polices that allow selective marking of different kinds of traffic and allows selective policing of different kinds of traffic.
The 2960, with QoS enabled, supports four egress queues. One (I also believe) can be defined as a priority queue. Bandwidth ratios can be assigned between the egress queues. Queue shaping is also supported (I also believe).
Lastly (another I believe [I know the 3650/3750s do what I described - but unsure the 2960 supports all their QoS features]), you can "shape" an egress port. (This to create possible congestion, to be managed by QoS, when the downstream supports less than physical port bandwidth.)
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...