Benard,

 

I take back my explanation after reading the article.  But the down side to this work-around is you would be dropping your own traffic when there is a chance the isp might have accepted the excess.

 

From: skunkworks-bounces@lists.my.co.ke [mailto:skunkworks-bounces@lists.my.co.ke] On Behalf Of Kevin K. Kamonye
Sent: Thursday, September 15, 2011 12:43 AM
To: Skunkworks Mailing List
Subject: Re: [Skunkworks] Prioritization

 

David,

 

Though they seem to disagree, Tony and Bernard have both provided you with the solution :)

 

In your case, am assuming that your ISP;

 

1. Has sufficient Internet capacity from their upstream,

2. Is rate-limiting you at your subscribed capacity.

 

Now, what Bernard has suggested is mostly effective for up-link(outbound) traffic only. It will not, however, greatly enhance your applications' performance as the return packets via your down-link may still be delayed.

 

To achieve the best results, QoS must be implemented at all points of congestion/bandwidth limitation. You need to talk to your ISP and ask them to shape the down-link traffic for you because your packets are queued on their routers/bandwidth manager before they are released to get to you. 

 

On your end, please follow the guide from Bernard to shape your up-link traffic.

 

R,

On 14 September 2011 22:59, Bernard Wanyama <bwanyama@eis.co.ug> wrote:

Tony,

I beg to differ.

Cisco supports QoS on Ethernet interfaces - using something called
Hierarchical QoS - parent policy to define interface bandwidth and
child policies to prioritise applications.

You can start with the example on the link below:

http://www.networkengineerblog.com/2011/03/qos-hierarchical-class-based-weighted.html

You might have to start with the router and also do something on the ASA

Kind regards,
Bernard


On Mon, Sep 12, 2011 at 3:14 PM, Tony Gacheru <tonygacheru@gmail.com> wrote:
> If your link is terminated on Ethernet to the cisco, then its no use
> prioritizing. The router will never sense congestion on the 100mbps
> interface and therefore not employ QOS. But your ISP should be able to
> prioritize your inbound traffic for you.
>
>
>
> From: skunkworks-bounces@lists.my.co.ke
> [mailto:skunkworks-bounces@lists.my.co.ke] On Behalf Of david aliata
> Sent: Monday, September 12, 2011 1:36 PM
> To: Skunkworks forum
> Subject: [Skunkworks] Prioritization
>
>
>
> Hi Guys,
>
>
>
> For the Cisco gurus.Could someone please give me a lead on how I can
> prioritize and test WebEx, Skype and some two websites on Cisco equipment.
> My set up is such that the link goes to a Cisco
>
>
>
> 1941 router>Cisco ASA 5505>Cisco Catalyst Switch 2960>Computer.
>
>
>
> Thanks!
>

> _______________________________________________
> Skunkworks mailing list
> Skunkworks@lists.my.co.ke
> http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
> ------------
> Skunkworks Rules
> http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
> ------------
> Other services @ http://my.co.ke
>
_______________________________________________
Skunkworks mailing list
Skunkworks@lists.my.co.ke
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
------------
Skunkworks Rules
http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
------------
Other services @ http://my.co.ke



 

--
./Kamonye