cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
403
Views
0
Helpful
2
Replies

Compression is not visible within eg. "sh policy-map" ?

wagnerch
Level 1
Level 1

Hi,

I have configured "rtp header-compression" but when I look at the "show policy-map" I do not see the reduced output traffic (bandwidth consumption). I always see the traffic volume before the compression which is not the reality on the physical link.

So I would need to make all class-definitions without regard to compression and also do not see how much bandwidth is really used by eg. the voice-class, right?

Is this right or is there any solution to see the real bandwidth consumption on the link.

Regards,

Chris

2 Replies 2

jbayuka
Level 5
Level 5

The show interface command should give you a lot of details on the link usage.

You could watch the load, 5 minute input rate/output rate fields before compression and after compression to find

the realistic usage.

I am pasting a sample show interface output below

Router#sh int s0

Serial0 is up, line protocol is up

Hardware is HD64570

Internet address is 192.168.100.2/24

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Encapsulation HDLC, loopback not set, keepalive set (10 sec)

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters 13:32:47

Input queue: 1/75/0 (size/max/drops); Total output drops: 0

Queueing strategy: weighted fair

Output queue: 0/1000/64/0 (size/max total/threshold/drops)

Conversations 0/2/256 (active/max active/max total)

Reserved Conversations 0/0 (allocated/max allocated)

5 minute input rate 3000 bits/sec, 4 packets/sec

5 minute output rate 2000 bits/sec, 4 packets/sec

98631 packets input, 8680095 bytes, 0 no buffer

Received 30857 broadcasts, 0 runts, 0 giants, 0 throttles

2 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

98332 packets output, 8924943 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 output buffer failures, 0 output buffers swapped out

0 carrier transitions

DCD=up DSR=up DTR=up RTS=up CTS=up

Hi,

what I mean is that the compression is not reflected to QoS-commands and there calculations, right ??

Regards,

Chris