cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3088
Views
3
Helpful
4
Replies

problem with MPLS link bandwidth

Hi,

we have 3 branches connected to headoffice over mpls with the speed of 2 MBPS each, and all were working fine with 30 to 40 users at branch and voip system. but one branch experiancing bandwidth problem as other two are working fine.

when i am pinging from headoffice system to branch router or vice versa the ping time is too high.

but when i connect my laptop to mpls connection at branch by removing the cable from router and ping to HO router , the time is 5 to10 ms

but when i connect it to router and ping from internal netowrk the time is varying between 5 to 300 ms.

thers is no problem with internal network as from internal network  to isp gatway ping time is netween 5 to 20 ms

the config is like below..

HO tunnel config (IP 192.168.12.5)

---------------------------

interface FastEthernet0/1

description " Connection to ISP MPLS"                   

ip address 172.31.3.18 255.255.255.252

duplex full

speed 100

interface Tunnel102

description " Tunnel RYD-NAS "

bandwidth 1024

ip address 10.10.0.10 255.255.255.252

tunnel source 172.31.3.18

tunnel destination 172.31.197.18

router eigrp 200

redistribute ospf 10 metric 512 600 100 100 1500

network 10.10.0.0 0.0.0.3

network 10.10.0.4 0.0.0.3

network 10.10.0.8 0.0.0.3

network 10.10.0.28 0.0.0.3

no auto-summary

router bgp 65412

no synchronization

bgp log-neighbor-changes

bgp redistribute-internal

network 10.10.10.0 mask 255.255.255.0

network 192.168.21.0

network 192.168.31.0

network 192.168.33.0

network 192.168.41.0

redistribute ospf 10 match internal external 1 external 2

neighbor 172.16.16.1 remote-as 29684

neighbor 172.16.16.1 prefix-list only-lan out

neighbor 172.31.3.17 remote-as 65000

neighbor 172.31.3.17 prefix-list only-lan out

no auto-summary

Branch config (IP 192.168.40.5)

--------------------------------

interface FastEthernet0/0.40

encapsulation dot1Q 40

ip address 192.168.40.5 255.255.255.0

interface FastEthernet0/1

ip address 172.31.197.18 255.255.255.252

duplex auto

speed auto

interface Tunnel102

description " Tunnel NAS-RYD "

bandwidth 1024

ip address 10.10.0.9 255.255.255.252

tunnel source 172.31.197.18

tunnel destination 172.31.3.18

router eigrp 200

network 10.10.0.8 0.0.0.3

network 192.168.40.0

network 192.168.41.0

router bgp 65412

no synchronization

bgp log-neighbor-changes

neighbor 172.31.197.17 remote-as 65000

no auto-summary

ping result from head office system to branch router

is there any problem with my config.....ping test.JPG

1 Accepted Solution

Accepted Solutions

Bilal Nawaz
VIP Alumni
VIP Alumni

Hello, it sounds like maybe 2mb is not enough for this branch in particular - maybe someone or something is using bandwidth a little more excessively somehow than the other branches, 30 - 40 people sharing 2mb sounds a little less.

But maybe thats because we all enjoy the super speed broadband at home these days.

Lets look at it this way. All users are going via the router. When you take that cable from the MPLS CE router and plug in to your laptop, it's only you who has that full 2mb bandwidth available. You are not sharing any traffic with anyone else who may be in the branch.

If you are able to 'ping' and there is connectivity as expected, there probably isnt wrong with your config. What if you try connecting to your router, and have your laptop only plugged in to your router.

e.g.

MPLS CE ROUTER ------- YOUR ROUTER ------ YOUR LAPTOP ONLY

Test this and see what kind of latency you get. If its approx 10 - 50 ms its good. That means maybe its something in the LAN that is taking up B/W. If its greater than that, then we know that maybe something is wrong with the router itself.

Have you tried monitoring tools like SNMP and Netflow? This way you can see link utilization, average bandwidth etc... Also with netflow you'll be able to tell if its a particular protocol, source, destination, and how much data has been transfered, which may show the reason for this slowness.

Hope this helps

Please rate useful posts and remember to mark any solved questions as answered. Thank you.

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

View solution in original post

4 Replies 4

Bilal Nawaz
VIP Alumni
VIP Alumni

Hello, it sounds like maybe 2mb is not enough for this branch in particular - maybe someone or something is using bandwidth a little more excessively somehow than the other branches, 30 - 40 people sharing 2mb sounds a little less.

But maybe thats because we all enjoy the super speed broadband at home these days.

Lets look at it this way. All users are going via the router. When you take that cable from the MPLS CE router and plug in to your laptop, it's only you who has that full 2mb bandwidth available. You are not sharing any traffic with anyone else who may be in the branch.

If you are able to 'ping' and there is connectivity as expected, there probably isnt wrong with your config. What if you try connecting to your router, and have your laptop only plugged in to your router.

e.g.

MPLS CE ROUTER ------- YOUR ROUTER ------ YOUR LAPTOP ONLY

Test this and see what kind of latency you get. If its approx 10 - 50 ms its good. That means maybe its something in the LAN that is taking up B/W. If its greater than that, then we know that maybe something is wrong with the router itself.

Have you tried monitoring tools like SNMP and Netflow? This way you can see link utilization, average bandwidth etc... Also with netflow you'll be able to tell if its a particular protocol, source, destination, and how much data has been transfered, which may show the reason for this slowness.

Hope this helps

Please rate useful posts and remember to mark any solved questions as answered. Thank you.

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

Thank you Mr.Bilal,

I am at head office at present and will check after finishing the work here.

hope this will work fine,but we have 2 mbps link for all branch and 6 mb at head office but why this perticular branch giving problem.

anyway i have to test it....

Thankyou once again

Hi mate,

I also suggest you run winmtr for at least 10-20 minutes and post the results; this way you will be able to identify the congested hop.

Hi Florin,

Thank you for the mail,

The issue got solved, the problem was with the PCs connected.

we had the PSTs located at head office, and the PCs were having virus also, so when they are accessing outlook over the network it was consuming all the bandwidth, so the pings were going high and the voice traffice was getting affected.

we shifted the PSTs to local systems and installed new anti virus in all the branch systems.

now the ping time is 5ms, that is good for me..

Thank you all.

Review Cisco Networking for a $25 gift card