[c-nsp] QoS for MetroEthernet

[Pavel Skovajsa]

Hi Omar,

No you definively should not take any special considerations for Metro
link - you are the end customer the service is transparent to you - it
moves packets back and forth.

Therefore it is hard to tell what is the actual problem. It is easy to
troubleshoot though - sniff it:
a) sniff the SQL activity with Serial link
b) sniff the SQL activity with Metro link
c) compare and find out what types of packets do not get on the other side.

There could be number of things that can go wrong - like service
provider maximum MTU, certain TOS values being dropped etc. etc.

-pavel

p.s. For sniffing we usually use Wireshark.



On Sun, Jan 31, 2010 at 5:31 PM, omar parihuana
<omar.parihuana at gmail.com> wrote:
> Hello,
>
> I'm facing a strange problem I think that is a QoS configuration, I've tried
> some conf without success. The situation is as follows:
>
> Actually I have a 1Mbps Serial link between two remote branchs and one
> application in particular: a SQL client/server application that works fine.
> (there are other apps but is not relevant now). We've contracted a
> MetroEthernet Link at 1Mbps between the same branchs (in order to replace
> the current serial link) In each site I put a router after migrate the SQL
> app didn't work (it got suck for  a long time). Therefore I decided raise a
> GRE tunnel between both sites, applied QoS conf, adjust the tcp mss without
> success, all working well (additional apps and voice traffic) but SQL app
> didn't work.  I don't know what's happenning with this app, but if you have
> faced the same problem, or I need take special considerations for
> MetroEthernel Link please your comments will be appreciated.
>
> I paste my conf:
>
> !
> !
> policy-map child13
>  class VOIP-TRAFFIC
>  priority 200
>  class DATA-IMPORTANT
>  bandwidth percent 60
>  class class-default
>  fair-queue
> policy-map tunnel13
>  class class-default
>  shape average 1024000
>  service-policy child13
> !
> !
> !
> interface Tunnel13
>  bandwidth 1000
>  ip address 10.1.13.1 255.255.255.0
>  ip tcp adjust-mss 1440
>  load-interval 30
>  qos pre-classify
>  tunnel source 172.21.1.17
>  tunnel destination 172.21.1.19
>  service-policy output tunnel13
> !
> interface FastEthernet0/0
>  description LAN interface
>  ip address 172.16.96.6 255.255.252.0
>  no ip unreachables
>  no ip proxy-arp
>  load-interval 30
>  speed 100
>  full-duplex
> !
> interface FastEthernet0/1
>  description MAN interface
>  bandwidth 3000
>  ip address 172.21.1.17 255.255.255.248
>  no ip proxy-arp
>  load-interval 30
>  speed 100
>  full-duplex
>
>
> --
> Omar E.P.T
> -----------------
> Certified Networking Professionals make better Connections!
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>