350-501 · Question #132
In an MPLS VPN environment, the QoS making over the MPLS backbone must be different from the one that is received from the customer. The forwarding on the egress PE is based on the marking that is…
The correct answer is A. MPLS explicit null with pipe mode. To ensure QoS marking over the MPLS backbone differs from the customer's and the egress PE forwards based on the ingress PE's marking, MPLS explicit null with pipe mode must be used.
Question
In an MPLS VPN environment, the QoS making over the MPLS backbone must be different from the one that is received from the customer. The forwarding on the egress PE is based on the marking that is set by the ingress PE. Which null label and QoS mode can achieve this?
Options
- AMPLS explicit null with pipe mode
- BMPLS implicit null with short pipe mode
- CMPLS implicit null with uniform mode
- DMPLS explicit null with uniform mode
- EMPLS explicit null with short pipe mode
- FMPLS implicit null with pipe mode
How the community answered
(49 responses)- A71% (35)
- B6% (3)
- C2% (1)
- D14% (7)
- E2% (1)
- F4% (2)
Why each option
To ensure QoS marking over the MPLS backbone differs from the customer's and the egress PE forwards based on the ingress PE's marking, MPLS explicit null with pipe mode must be used.
MPLS implicit null (PHP) causes the MPLS label, and thus its EXP value, to be popped at the penultimate hop, preventing the egress PE from directly using the ingress PE's MPLS EXP marking for forwarding.
Implicit null (PHP) removes the MPLS EXP before the egress PE, and uniform mode propagates the customer's QoS marking, which contradicts the requirement for different backbone marking.
Uniform mode QoS propagates the customer's QoS marking into the MPLS backbone, which goes against the requirement for the backbone marking to be different.
While explicit null preserves the EXP to the egress PE, short pipe mode might still copy the IP DSCP to MPLS EXP at push, or it might not provide the full independent QoS handling required for the egress PE to forward solely based on the ingress PE's marking.
MPLS implicit null (PHP) causes the MPLS label, and thus its EXP value, to be popped at the penultimate hop, preventing the egress PE from directly using the ingress PE's MPLS EXP marking for forwarding.
Concept tested: MPLS QoS modes and null label behavior
Source: https://www.cisco.com/c/en/us/td/docs/ios/mpls/configuration/guide/12_4t/t_mplsqos.html
Topics
Community Discussion
No community discussion yet for this question.