[nsp] Stupid QoS Tricks
Luan Nguyen
lmnguyen at cox.net
Tue Nov 18 11:53:03 EST 2003
>From reading CCO and looking on the router:
Router(config-pmap-c)#shape average ?
<8000-154400000> Target Bit Rate (bits per second), the value needs to be
multiple of 8000
percent % of interface bandwidth for Committed information rate
I think whatever you define for 4megabit class-map will be policed with the cir 4000000 statement, but the ip prec 5 will use all the interface bandwidth.
-luan
Router#show policy-map interface
FastEthernet0/0
Service-policy output: voice_traffic_w4megabit_data
Class-map: ipprec5 (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip precedence 5
0 packets, 0 bytes
5 minute rate 0 bps
Traffic Shaping
Target/Average Byte Sustain Excess Interval Increment
Rate Limit bits/int bits/int (ms) (bytes)
100 (%) 0 (ms) 0 (ms)
100000000/100000000 625000 2500000 2500000 25 312500
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
- 0 0 0 0 0 no
Class-map: 4megabit (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: protocol http
police:
cir 4000000 bps, bc 6000000 bytes
conformed 0 packets, 0 bytes; actions:
transmit
exceeded 0 packets, 0 bytes; actions:
drop
conformed 0 bps, exceed 0 bps
Class-map: class-default (match-any)
214 packets, 21427 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
>
> From: "Christopher J. Wolff" <chris at bblabs.com>
> Date: 2003/11/18 Tue AM 01:03:02 EST
> To: <cisco-nsp at puck.nether.net>
> Subject: RE: [nsp] Stupid QoS Tricks
>
> Is the following snippet also an option? Is it safe to ass-ume that packets
> with ipprec 5 can have the entire 4 meg if desired? Thanks!
>
> class-map match-any ipprec5
> match ip precedence 5
>
> policy-map voice_traffic_w4megabit_data
> class ipprec5
> shape average percent 100
> class 4megabit
> police 4000000 6000000 12000000 conform-action transmit exceed-action drop
>
> interface FastEthernet0/1
> service policy input voice_traffic_w4megabit_data
> service policy output voice_traffic_w4megabit_data
>
> -----Original Message-----
> From: Luan Nguyen [mailto:lmnguyen at cox.net]
> Sent: Monday, November 17, 2003 10:11 PM
> To: Christopher J. Wolff; cisco-nsp at puck.nether.net
> Subject: Re: [nsp] Stupid QoS Tricks
>
> Maybe you should try to use Class Based Weighted Fair Queuing. I think that
> is another method of prioritizing queuing that apply to VoIP over Frame
> Relay. In this method you define classes of traffics and assign them an
> absolute bandwidth that they have available during periods of congestion.
> The voice queue will act as a priority queue and be serviced first.
>
> class-map X
> match input-interface LAN
> class-map class-default
> match any
> class-map voice
> match access-group 101
> !
> policy-map WAN
> class voice
> priority Z - Guarantee bandwidth for voice class Any packet with IP
> Precedence = 5 gets assigned to a class that will get a minimum of Z kbps
> class data
> bandwidth 4000
> interface WAN
> bandwidth DS3
> no ip directed-broadcast
> service-policy output WAN
> !
> access-list 101 permit ip any any precedence critical
>
> A link on how to configure CBWFQ:
> http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1830/products_feat
> ure_guide09186a0080087a84.html
>
> Hope that help a little bit. I am not very good at this.
>
> -luan
>
>
> >
> > From: "Christopher J. Wolff" <chris at bblabs.com>
> > Date: 2003/11/17 Mon PM 06:22:46 EST
> > To: <cisco-nsp at puck.nether.net>
> > Subject: [nsp] Stupid QoS Tricks
> >
> > Here's a scenario I could use some guidance on. I've read quite a bit on
> > Cisco's site but didn't find a direct correlation. So here goes.
> >
> > Customer has a DS3, of which 4 meg is provisioned for data. Now customer
> > wants to add VOIP services.
> >
> > Assumptions:
> >
> > - The customers' 4 meg is rate-limited by service policies / policing.
> > - The 4 meg circuit is generally saturated since it is a wi-fi
> free-for-all
> > environment.
> > - There is no VLAN capability on the customer LAN.
> >
> > My initial thought was to apply an ip rtp reserve to the customer
> interface,
> > which I did. However it seems like there should be a better method to
> > guarantee voice traffic while maintaining the customers' data 'partition'.
> > Thank you in advance for your advice.
> >
> > Regards,
> > Christopher J. Wolff, VP, CIO
> > Broadband Laboratories
> > http://www.bblabs.com
> >
> >
> > _______________________________________________
> > cisco-nsp mailing list cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list