no `rate-limit` on 1720/12.2(4)T3!?

[randal]

I was doing some QoS work on a customer 1720 earlier today to prioritize their voip traffic (always terminates on 66.239.20.0/24). Setup the policy & class maps, applied them to the internal & external interfaces appropriately then went to configure rate-limiting on their s0 ... and the command doesn't exist? WTF? The VoIP traffic enjoys jitter and such when the line is under load, so I'm thinking that is the cause. Any insight would be appreciated.

!
class-map match-all voice
match access-group 101
!
!
policy-map HollySugar
class voice
priority 96
class class-default
fair-queue
!
!
interface FastEthernet0
description Connected to HollySugarLAN
ip address XXXXXXXXXXXX 255.255.255.0
ip nat inside
no ip route-cache
no keepalive
speed auto
full-duplex
service-policy output HollySugar
bridge-group 1
!
interface Serial0
description **XXXXXXXX**
ip address XXXXXXXXXXXX 255.255.255.252
ip access-group FilterInboundv2 in
ip access-group FilterOutbound out
ip nat outside
encapsulation ppp
service-policy output HollySugar
!
!
access-list 101 permit ip any 66.239.20.0 0.0.0.255
access-list 101 permit ip 66.239.20.0 0.0.0.255 any
!

thanks!

 

[randal]

whoop, just noticed that this is c1700-y-mz.122-4.T3.bin ... not in the IOS. I should have checked that first.

 

[spidey07]

you really shouldn't need rate-limit for voice. just stick it in the priority Q.

Also depending on the line speed you probably should be doing some fragmentation and interleave.

 

[randal]

The problem is that it is a shared T1 in an executive-suites style environment - they have ~15 users running across a 16/8 data/pots channelized T1. Their 1mbps link gets saturated for portions of a second whenever anybody pops open a heavy webpage or downloads a not-small email, resulting in the VoIP becoming hit or miss. Because of that, I was going to setup the inbound rate-limits on s0 to provide the requisite bandwidth, then another rate-limit on the $everything_else traffic. That has worked out pretty well in the past, but in this case I don't have that tool available. I do have the policy setup on both the fa0 & s0 interfaces though, but it is outbound only and doesn't stop the T1 from getting saturated :-/

Also, I thought LFI only worked on MLPPP, not standard PPP - are there other methods than `ppp multilink interleave` etc. for non-linked ppp connections? Edit: Google tells me that I can run mppp with a single T1 in the multi-link group. First time for everything, eh?