Re: Any other compression ideas for PPP Multilink

richreitenauer · ‎07-19-2011

Hi,

I am looking for any other compression methods I can use for my PPP multilink connection. The PPP multilink compression is composed of two T1 lines. There are no slip sec errors or packet errors that I saw recently. R1 is a 1911 and R2 is a 2911. Thanks in advance.

R1 sh compress:

Multilink1

Software compression enabled

uncompressed bytes xmt/rcv 184340310/27355186

compressed bytes xmt/rcv 126395743/14139585

Compressed bytes sent: 126395743 bytes 774 Kbits/sec ratio: 1.458

Compressed bytes recv: 14139585 bytes 86 Kbits/sec ratio: 1.934

1 min avg ratio xmt/rcv 1.265/0.157

5 min avg ratio xmt/rcv 1.054/0.150

10 min avg ratio xmt/rcv 1.027/0.014

no bufs xmt 0 no bufs rcv 0

resyncs 25

Additional Stac Stats:

Transmit bytes: Uncompressed = 36984274 Compressed = 126395743

Received bytes: Compressed = 14283002 Uncompressed = 35517357

R2 sh compress:

Multilink1

Software compression enabled

uncompressed bytes xmt/rcv 23137723/180534252

compressed bytes xmt/rcv 12000991/123708452

Compressed bytes sent: 12000991 bytes 74 Kbits/sec ratio: 1.927

Compressed bytes recv: 123708452 bytes 764 Kbits/sec ratio: 1.459

1 min avg ratio xmt/rcv 0.662/1.272

5 min avg ratio xmt/rcv 0.023/0.045

10 min avg ratio xmt/rcv 0.029/1.032

no bufs xmt 0 no bufs rcv 0

resyncs 24

Additional Stac Stats:

Transmit bytes: Uncompressed = 34331721 Compressed = 12000991

Received bytes: Compressed = 123887322 Uncompressed = 36625933

Here is my config from both routers:

R1:

clock timezone gmt -5

clock summer-time CDT recurring

no network-clock-participate wic 0

!

no ipv6 cef

ip source-route

ip cef

!

no ip domain lookup

multilink bundle-name authenticated

!

controller T1 0/0/0

cablelength long 0db

channel-group 0 timeslots 1-24

!

controller T1 0/0/1

cablelength long 0db

channel-group 0 timeslots 1-24

!

ip ssh version 2

buffers tune automatic

!

interface Multilink1

ip address ip/subnet

ip flow ingress

ip flow egress

compress stac

ppp multilink

ppp multilink group 1

ppp multilink fragment disable

no cdp enable

!

interface GigabitEthernet0/0

ip address

ip helper-address xx.xx.xx.xx

ip directed-broadcast

ip flow ingress

ip flow egress

duplex auto

speed auto

!

interface Serial0/0/0:0

no ip address

encapsulation ppp

ppp multilink

ppp multilink group 1

no fair-queue

!

interface Serial0/0/1:0

no ip address

encapsulation ppp

ppp multilink

ppp multilink group 1

no fair-queue

!

ip forward-protocol nd

!

R2:

clock timezone gmt -5

clock summer-time cdt recurring

no network-clock-participate wic 0

no network-clock-participate wic 1

!

no ipv6 cef

ip source-route

ip cef

!

multilink bundle-name authenticated

!

controller T1 0/0/0

cablelength long 0db

channel-group 0 timeslots 1-24

!

controller T1 0/0/1

clock source internal

cablelength long 0db

channel-group 0 timeslots 1-24

!

buffers tune automatic

!

interface Multilink1

ip address ip/subnet

ip flow ingress

ip flow egress

compress stac

ppp multilink

ppp multilink group 1

ppp multilink fragment disable

no cdp enable

!

interface GigabitEthernet0/0

ip address ip/subnet

ip flow ingress

ip flow egress

duplex auto

speed auto

!

interface Serial0/0/0:0

no ip address

encapsulation ppp

ppp multilink

ppp multilink group 1

no fair-queue

!

interface Serial0/0/1:0

no ip address

encapsulation ppp

ppp multilink

ppp multilink group 1

no fair-queue

andrew.prince · ‎07-19-2011

What's the reasoning for using compression?

richreitenauer · ‎07-19-2011

I received complaints that the link was slow....however, the users are used to a 100 meg link and they were moved to an off site location that is running a 3Mb multilink. I want to cover all bases before mentioning getting another T1 or two to help increase the speed. I came into the position I am in now and the two T1 connections were already ordered...so I have to work with what I got.

I do have WhatsUp Gold running to monitor netflow data.

andrew.prince · ‎07-19-2011

OK - firstly going from 100mbs to 3 mbs will be noticed, and no amount of compression is going to speed things up.

Secondly user perception of slow is open to discussion and interpretation, perhaps you shoyuld ask "what is slow"

Thirdly if the answer to "what is slow" is NOT buisness related then you can forget about it.

Then look at QoS - prioritise what is important/must have for business, and let everything else fight for bandwidth!

HTH>

vmiller · ‎07-19-2011

Just a thought. Before doing more multi link, get some pricing & terms on DS-3 level services, or Metro E.

It might make your life a bit easier.

Joseph W. Doherty · ‎07-19-2011

Disclaimer

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.

Liability Disclaimer

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.

Posting

Along with Andrew, it's rather difficult to make a 3 Mbps circuit work like 100 Mbps.

Andrew also mentioned QoS. For your 3 Mbps, if FIFO queuing is active, minimally replace with fair-queue. This will greatly minimize the impact of one large flow impacting all the others, which isn't difficult to do across 3 Mbps.

The only other compression method that would likely perform even better, is something like WAAS, but don't believe that's an installable option on your 1911. You could, though, use stand-alone appliance, e.g. WAEs. You might want to compare prices of WAEs to upgrading the 1911 to a device that supports WAAS Express.