z**r
发帖数: 17771 | 1 I have a topology like
CE1----dot1q-----PE1-------MPLS cloud-------------PE2-----dot1q--------CE2
PEs run VPLS over LDP. CE1 is sending dot1q traffic with COS value 2, on the
PE1, I rewrite the MPLS EXP bit to 4 when matching COS 2. So on the CE2, what
COS value am I supposed to see? | v**n
发帖数: 951 | 2 it depends on your configuration and implementation of PE2 吧？
what
【在 z**r 的大作中提到】
: I have a topology like
: CE1----dot1q-----PE1-------MPLS cloud-------------PE2-----dot1q--------CE2
: PEs run VPLS over LDP. CE1 is sending dot1q traffic with COS value 2, on the
: PE1, I rewrite the MPLS EXP bit to 4 when matching COS 2. So on the CE2, what
: COS value am I supposed to see?
| z**r
发帖数: 17771 | 3
agree, but SP does NOT always want to provide classified services based on the
customers' COS. Different customers could have different COS for same kind of
requirement, say voice traffic. However, from SP's perspective, all the voice
traffic from different customers with different COS should be treated the
same. That's why SP might want to remark the EXP bits.
used
I thought 'set mpls exp imposition' setts both tunnel and vc labels, correct
me if I am wrong. sure vc label is not used for core | b******e
发帖数: 66 | 4
label
If you are trusting cos, exp-bit will be automatically copied from cos, you
don't need to remark exp.
How did you set the VC label exp? and what is the point? vc label is not used
for switching.
So on the exgress PE side, after the
the
Not necessarily, depends what QoS mode you want, for short pipe mode, you cos
value is retained, no matter what Exp value you had along the way. For uniform
mode, cos, tunnel exp, vc exp are the same at ingress PE, if for some reason,
tunnel label changed a
【在 z**r 的大作中提到】
:
: agree, but SP does NOT always want to provide classified services based on the
: customers' COS. Different customers could have different COS for same kind of
: requirement, say voice traffic. However, from SP's perspective, all the voice
: traffic from different customers with different COS should be treated the
: same. That's why SP might want to remark the EXP bits.
: used
: I thought 'set mpls exp imposition' setts both tunnel and vc labels, correct
: me if I am wrong. sure vc label is not used for core
| z**r
发帖数: 17771 | 5
agree, but SP does NOT always want to provide classified services based on the
customers' COS. Different customers could have different COS for same kind of
requirement, say voice traffic. However, from SP's perspective, all the voice
traffic from different customers with different COS should be treated the
same. That's why SP might want to remark the EXP bits.
used
I thought 'set mpls exp imposition' setts both tunnel and vc labels, correct
me if I am wrong. sure vc label is not used for core
【在 b******e 的大作中提到】
:
: label
: If you are trusting cos, exp-bit will be automatically copied from cos, you
: don't need to remark exp.
: How did you set the VC label exp? and what is the point? vc label is not used
: for switching.
: So on the exgress PE side, after the
: the
: Not necessarily, depends what QoS mode you want, for short pipe mode, you cos
: value is retained, no matter what Exp value you had along the way. For uniform
| b******e
发帖数: 66 | 6
label
If you are trusting cos, exp-bit will be automatically copied from cos, you
don't need to remark exp.
How did you set the VC label exp? and what is the point? vc label is not used
for switching.
So on the exgress PE side, after the
the
Not necessarily, depends what QoS mode you want, for short pipe mode, you cos
value is retained, no matter what Exp value you had along the way. For uniform
mode, cos, tunnel exp, vc exp are the same at ingress PE, if for some reason,
tunnel label changed a
【在 z**r 的大作中提到】
:
: agree, but SP does NOT always want to provide classified services based on the
: customers' COS. Different customers could have different COS for same kind of
: requirement, say voice traffic. However, from SP's perspective, all the voice
: traffic from different customers with different COS should be treated the
: same. That's why SP might want to remark the EXP bits.
: used
: I thought 'set mpls exp imposition' setts both tunnel and vc labels, correct
: me if I am wrong. sure vc label is not used for core
| z**r
发帖数: 17771 | 7
agree, but SP does NOT always want to provide classified services based on the
customers' COS. Different customers could have different COS for same kind of
requirement, say voice traffic. However, from SP's perspective, all the voice
traffic from different customers with different COS should be treated the
same. That's why SP might want to remark the EXP bits.
used
I thought 'set mpls exp imposition' setts both tunnel and vc labels, correct
me if I am wrong. sure vc label is not used for core
【在 b******e 的大作中提到】
:
: label
: If you are trusting cos, exp-bit will be automatically copied from cos, you
: don't need to remark exp.
: How did you set the VC label exp? and what is the point? vc label is not used
: for switching.
: So on the exgress PE side, after the
: the
: Not necessarily, depends what QoS mode you want, for short pipe mode, you cos
: value is retained, no matter what Exp value you had along the way. For uniform
| b******e
发帖数: 66 | 8 The better question to ask would be:
1)cos is 0, why? 2) cos is 2, why? 3)cos is 4, why?
【在 z**r 的大作中提到】
:
: agree, but SP does NOT always want to provide classified services based on the
: customers' COS. Different customers could have different COS for same kind of
: requirement, say voice traffic. However, from SP's perspective, all the voice
: traffic from different customers with different COS should be treated the
: same. That's why SP might want to remark the EXP bits.
: used
: I thought 'set mpls exp imposition' setts both tunnel and vc labels, correct
: me if I am wrong. sure vc label is not used for core
| z**r
发帖数: 17771 | 9 on the PEs I use mls qos trust cos, and mark the exp-bit for both tunnel label
and vc label, not just the tunnel lable. So on the egress PE side, after the
label disposition, the PE should copy the exp bits (in vc label) back to the
dot1q p bits, right?
the ce facing interface on the pe is just the cheap LAN card interface, which
is even not mpls awareness, but it DOES know mls qos.
If it marks only the topmost label, I would agree with you
QoS
are
【在 b******e 的大作中提到】
: The better question to ask would be:
: 1)cos is 0, why? 2) cos is 2, why? 3)cos is 4, why?
|
|
