Exam 350-501 All QuestionsBrowse all questions from this exam
Go to Exam
Question 295

Refer to the exhibit. The customer that owns the CE-1, CE-2, and CE-3 routers purchased point-to-point E-Line services from the Carrier Ethernet provider. The service provider is delivering multiplexed UNI at the customer HQ location on PE-1 and untagged UNIs at the PE-2 and PE-3 locations. Additionally, the customer provided these VLAN to EVC mapping requirements:

• EVC 1 between CE-1 and CE-2 must be provisioned with C-VLAN 12 at the HQ location.

• EVC 2 between CE-1 and CE-3 must be provisioned with C-VLAN 13 at the HQ location.

Which configuration must the network engineer implement on the PE routers to provide end-to-end Carrier Ethernet service to the customer?

    Correct Answer: D

    The correct answer is D. The customer requires end-to-end Carrier Ethernet service with specific VLANs provisioned for different EVCs. On PE-1, service instances for VLANs 12 and 13 are correctly defined with 'rewrite ingress tag pop 1 symmetric', which ensures that the VLAN tags are correctly handled in both directions. PE-2 and PE-3 are set to handle untagged traffic, which is appropriate since the endpoints CE-2 and CE-3 use untagged UNIs. The 'symmetric' keyword ensures that the correct tags (12 and 13) are applied for ingress traffic at PE-1 and removed for egress traffic, maintaining end-to-end VLAN consistency.

Discussion
nottoday2077Option: D

This one was bugging me because both B and D work. However figured out the missing piece. B - PE3 is missing the service instance. Would work if the service instance was there. D - PE1 - pops tag > PE2/PE3 egress untagged packet, ingress untagged traffic > PE1 egress tags based on set encapsulation (symmetric). A/C seem to be the same and don't work anyways.

sushil_bhattacharjeeOption: B

Answer: B In my previous comment, I mentioned Answer: D which is wrong. PE1 has to differentiate traffic between CE2 and CE3. Therefore, PE2 and PE3 have to push the tag in the direction of PE1. PE1 can be untagged.

cocopost

Agree. the push is needed. I believe the 10011301 or 10011301 is only locally significant and cannot help to multiplex the packets on the far end . trying to find a reference to confirm that.

cocopost

Answer D: My apologies, I am changing my vote on this. I did a lab today in GNS3. (this reminded me one thing) The lines: xconnect 172.20.20.1 1001201 encapsulation mpls xconnect 172.20.20.1 1001301 encapsulation mpls which appear with different vc-id in PE-2/PE-3 are sufficient to differentiate the traffic between CE2 and CE3. It is not necessary to push a tag in the direction of PE1! VLAN ID rewrite takes effect automatically. Answer D works fine without push. for VLAN-ID rewrite see: https://sites.google.com/site/amitsciscozone/atom/eompls-carrying-one-vlan. Furthermore as pointed out by user nottoday2077, Answer B is missing service instance. Correct answer: D.

cocopost

I labbed it again in GNS3. Answers B and D both work. Both correctly push the vlan tags for PE1 but in different places (D: PE1 rewrite ingres tag pop 1 symmetric) or (B: PE2,PE3, rewrite ingress tag push dot1q 12/13 symmetric) Both B & D are correct.

cocopost

But still answer B is missing a service instance. D is more correct.

12_sdeEQOption: D

answer is D

DUsooOption: D

PE1 should have pop 1 "symmetric "

chstOption: C

I think the correct is "C" "pop 1 symmetric " https://www.cisco.com/c/en/us/td/docs/wireless/asr_901/Configuration/Guide/b_asr901-scg/b_asr901-scg_chapter_01011.pdf

thejag

I think you mean D, at least now that is the one with "pop 1 symmetric" on PE1.

chst

Yes, I meant D

rans3001Option: A

D does not make sense: The traffic sent from CPE2 and CPE3 is not tagged. The symmetric on PE1 means that the service instances will try to remove vlan 12 or vlan 13 when sending traffic to CPE1. C is wrong because the xconnect VC IDs don't match. B The rewrite actions on PE2 and PE3 does not make sense (no vlan tag arrives from CPE2, CPE3, PE1)

rans3001

Correction: The right answer is D because on PE1 is removing vlan tags 12 and 13 at ingress, so the packets are going untagged to CEP2 and CPE3. CPE2 and CPE3 are sending untagged frames, so they are tagged at PE1 with vlan 12 or vlan 13, before being sent to CPE1 (because of symmetric keyword)

sushil_bhattacharjeeOption: D

Answer D: "symmetric". Without "symmetric" word, it will not add VLAN-tag at egress. https://community.cisco.com/t5/networking-knowledge-base/understanding-ethernet-virtual-circuits-evc/ta-p/3108219#:~:text=rewrite%20ingress%20tag%20pop%201%20symmetric%20Since%20the,on.%20The%20rewrite%20ingress%20command%20does%20just%20that.