cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2108
Views
5
Helpful
23
Replies

2811 Router-QOS with BT RADMUX

fathar
Level 1
Level 1

Hi Guys,

I am connecting two WAN Sites A & B via 4Mb Metro ethernet connection. On Site A, FE0/0 is connected to Site B. FE0/1 is connected to user PC and F0/2 is connected to BT RADMUX Voice system which is communicating with another BT RADMUX at Site B. Now customer want to make sure that this 4mb BW is distributed evenly b/w PC at F0/2 and BT RADMUX at F0/3. What is the best qos strategy to use to guarentee 2MB BW for each connection? ALso please let me know if there is any special settings to be required on router for BT RADMUX VOice system as I am not able to get good quality voice at the moment.

Many Thanks

23 Replies 23

Good morning...

So are you experiencing poor voice comms at the moment ? From what I can see, there is no congestion on the link as such...

Paresh

Hi,

It appears as if the router is not the issue here. You mentioned that there was a switch at the second site. There is a possibility that the switch is the issue here. What sort of switch is it ?

Paresh

Yeah Site B is using Cisco Swith 4506. BT Voice system is connected to one of FE port on this switch. The switch connects with SIte B Router, which is connected with SIte A router on F0/0 interface.

Cheers

Is there any chance you could post the switch config for those 2 ports ?

Also, is the voice perfectly clean with no data present ?

Paresh.

Hi Paresh,

Configs below as requested.Yes user claim that voice is clear when use alone.

Many thanks for your support.

Cheers

SITE B ROUTER:

interface GigabitEthernet0/3

desc 4 mb Metro ethernet to Site A

ip address..

no ip redirects

ip pim sparse-mode

duplex full

speed auto

service-policy output shaper

#sh policy-map interface gigabitEthernet 0/3

GigabitEthernet0/3

Service-policy output: Shaper

Class-map: class-default (match-any)

21498828 packets, 10955737425 bytes

5 minute offered rate 1173000 bps, drop rate 0 bps

Match: any

Traffic Shaping

Target/Average Byte Sustain Excess Interval Increment

Rate Limit bits/int bits/int (ms) (bytes)

4000000/4000000 25000 100000 100000 25 12500

Adapt Queue Packets Bytes Packets Bytes Shaping

Active Depth Delayed Delayed Active

- 0 21432631 2317875901 184786 127267321 no

Service-policy : PolOut

Class-map: RADMUX (match-all)

19689385 packets, 10356614450 bytes

5 minute offered rate 1036000 bps, drop rate 0 bps

Match: access-group 10

Queueing

Strict Priority

Output Queue: Conversation 136

Bandwidth 2000 (kbps) Burst 50000 (Bytes)

(pkts matched/bytes matched) 58682/30866732

(total drops/bytes drops) 0/0

Class-map: class-default (match-any)

1809443 packets, 599122975 bytes

5 minute offered rate 136000 bps, drop rate 0 bps

Match: any

SITE B SWITCH:

interface GigabitEthernet3/29

description **BT-RADMUX**

switchport access vlan 25

switchport mode access

speed 100

duplex full

spanning-tree portfast

spanning-tree bpduguard enable

!

sh int g3/29

GigabitEthernet3/29 is up, line protocol is up (connected)

Hardware is Gigabit Ethernet Port, address is 0013.7fe8.f3ac (bia 0013.7fe8.f3

ac)

Description: **BT-RADMUX**

MTU 1500 bytes, BW 100000 Kbit, DLY 10 usec,

reliability 255/255, txload 2/255, rxload 2/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, link type is auto, media type is 10/100/1000-TX

input flow-control is off, output flow-control is off

ARP type: ARPA, ARP Timeout 04:00:00

Last input 5w5d, output never, output hang never

Last clearing of "show interface" counters 00:26:38

Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 1040000 bits/sec, 237 packets/sec

5 minute output rate 1045000 bits/sec, 240 packets/sec

394336 packets input, 208927714 bytes, 0 no buffer

Received 25 broadcasts (0 multicast)

0 runts, 0 giants, 0 throttles

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

0 input packets with dribble condition detected

399665 packets output, 209390771 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

SITE A Router :

interface FastEthernet0/0

desc 4 Mb Metro ethernet

ip address

ip pim sparse-mode

duplex full

speed auto

service-policy output Shaper

interface FastEthernet0/1

description **Data Lan **

ip address

ip pim sparse-mode

ip cgmp

duplex full

speed 100

!

interface FastEthernet0/0/0

desc **BT RADMUX*

switchport access vlan 25

duplex full

speed 100

!

interface Vlan25

ip address ...

# sh policy-map interface fastEthernet 0/0

FastEthernet0/0

Service-policy output: Shaper

Class-map: class-default (match-any)

18557222 packets, 9689119807 bytes

5 minute offered rate 1042000 bps, drop rate 0 bps

Match: any

Traffic Shaping

Target/Average Byte Sustain Excess Interval Increment

Rate Limit bits/int bits/int (ms) (bytes)

4000000/4000000 25000 100000 100000 25 12500

Adapt Queue Packets Bytes Packets Bytes Shaping

Active Depth Delayed Delayed Active

- 0 18557258 1099202372 121 91437 no

Service-policy : PolOut

Class-map: RADMUX (match-all)

18387110 packets, 9671617800 bytes

5 minute offered rate 1036000 bps, drop rate 0 bps

Match: access-group 10

Queueing

Strict Priority

Output Queue: Conversation 136

Bandwidth 2000 (kbps) Burst 50000 (Bytes)

(pkts matched/bytes matched) 49/25774

(total drops/bytes drops) 0/0

Class-map: class-default (match-any)

170112 packets, 17501481 bytes

5 minute offered rate 6000 bps, drop rate 0 bps

Match: any

Could you try changing the Shaper policy so that it looks like:

policy-map Shaper

class class-default

shape average 4000000 16000

service-policy PolOut

Thanks,

Paresh.

Its seems that everything is working fine with existing policy..ther was some problem in BT equipmetn which was causing noice problem and has been resolved..Thanks for all your help..you Deserved 5 :)

I'm happy to see that your problem has been resolved.

Regards,

Paresh