QoS Problem ( nt getting same DSCP marking at diff.. vpls customer sites

Unanswered Question
Dec 30th, 2007

Hi we are having 3 locations A , B & C

we are providing l2 vpls service to customer .

customer is connected to our mpls cloud via EoSDH on my mpls switch on locations A , B & C.

customer is marking his traffic with DSCP bit XX from Location A when customer checking the traffic

at location B via packet sniffer ethereal they are not getting the same DSCP Tagging .

can anyone help me to find out the possible cause of this .

As far as i know in VPLS services there is limitation of provide multi-QoS.

But here in this case i m only trusting DSCP on the Lastmile port as well as on the trunks connected from my switches to my PEs .

so customer tagging should reach from location A to Location B .

Here we go:

CPE-A------CPE-A-SW--------SP-SW-A----PE-A======MPLS CLOUD=====PE-B------SP-SW-B-------CPE-B-SW-------CPE-B

here :CPE-A = customer router

CPE-A-SW = 4500

SP-SW-A = 4500

PE-A = 7600

PE-B = 7600

SP-SW-B = 3500

CPE-B-SW = 4500

CPE-B = customer router

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
mchin345 Fri, 01/04/2008 - 07:26

In your switch use show mls qos int x/x stat" on the exit interface to see if packets were correctly marked

bhartispbase Mon, 01/07/2008 - 04:02

I m getting blew output on the trunk interface connected to my PE on both the switches.

SP-SW-A#sh qos interface GigabitEthernet4/3

QoS is enabled globally

Port QoS is enabled

Administrative Port Trust State: 'dscp'

Operational Port Trust State: 'dscp'

Trust device: none

Default DSCP: 0 Default CoS: 0

Appliance trust: none

Tx-Queue Bandwidth ShapeRate Priority QueueSize

(bps) (bps) (packets)

1 250000000 disabled N/A 2336

2 250000000 disabled N/A 2336

3 250000000 disabled normal 2336

4 250000000 disabled N/A 2336

SP-SW-B#sh mls qos interface GigabitEthernet0/2 statistics

GigabitEthernet0/2

Ingress

dscp: incoming no_change classified policed dropped (in bytes)

Others: 0 0 0 0 0

Egress

dscp: incoming no_change classified policed dropped (in bytes)

Others: 0 n/a n/a 0 0

WRED drop counts:

qid thresh1 thresh2 FreeQ

1 : 0 0 1024

2 : 0 0 1024

3 : 0 0 1024

4 : 0 0 1024

mheusing Wed, 01/09/2008 - 02:13

Hi,

Are the CPE-A-SW and CPE-B-SW ports set to trusted? The default setting on all LAN switches is not to trust and thus any port with default settings will result in CoS=DSCP=0.

Regards, Martin

Actions

This Discussion