exam questions

Exam JN0-664 All Questions

View all questions & answers for the JN0-664 exam

Exam JN0-664 topic 1 question 52 discussion

Actual exam question from Juniper's JN0-664
Question #: 52
Topic #: 1
[All JN0-664 Questions]

Click the Exhibit button.

Referring to the exhibit, a working L3VPN exists that connects VPN-A sites. CoS is configured correctly to match on the MPLS EXP bits of the LSP. but when traffic is sent from Site-1 to Site-2. PE-2 is not classifying the traffic correctly.
What should you do to solve the problem?

  • A. Configure VPN prefix mapping for the PE-1_to_PE-2 LSP.
  • B. Set a static CoS value for the PE-1_to_PE-2 LSP.
  • C. Configure the explicit-null statement on PE-2.
  • D. Configure the explicit-null statement on PE-1.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
antigel8
Highly Voted 9 months, 3 weeks ago
Selected Answer: C
Ultimate Hop Popping (UHP) must be configured on the egress LSR to keep the EXP bit along the LSP. So configuration is needed on PE-2 in this case.
upvoted 5 times
albert1687
2 months, 4 weeks ago
Option D is Correct: “Configure the explicit-null statement on PE-1.” Here’s why: • Configuring explicit-null on PE-1 (the ingress PE) tells the network to not use PHP. • Instead of popping the top label, P-1 will replace it with label 0 (explicit-null), and send it to PE-2. • This preserves the EXP bits in that top label, so PE-2 can read and classify traffic based on those bits. ⸻ Now what about PE-2 and UHP? You’re correct that PE-2 must be capable of processing that explicit-null label. But: • PE-2 already handles label 0 (explicit-null) by default. • You don’t need to configure explicit-null on PE-2—you just need to ensure PE-1 requests it during label distribution (e.g., via LDP or RSVP). So while you could say UHP behavior is relevant at the egress (PE-2), the trigger to keep the label till PE-2 comes from the ingress PE — hence the config is on PE-1.
upvoted 1 times
...
...
pxlx
Most Recent 1 week, 6 days ago
Selected Answer: D
RSVP-TE LSP UHP behavior is configured on the ingress router's mpls section.
upvoted 1 times
...
pxlx
1 week, 6 days ago
Selected Answer: D
RSVP-TE LSP UHP behavior is configured on the ingress router's mpls section.
upvoted 1 times
...
Penieljacobpaul
2 months, 2 weeks ago
Selected Answer: C
The issue arises because the Penultimate Hop Popping (PHP) removes the transport label before reaching PE-2, causing the loss of MPLS EXP bits used for classification. Configuring explicit-null on PE-2 ensures the transport label is retained until PE-2 receives it, preserving the EXP bits for proper CoS classification. Answer: C. Configure the explicit-null statement on PE-2.
upvoted 1 times
...
albert1687
2 months, 4 weeks ago
Selected Answer: D
• By default, PHP (Penultimate Hop Popping) removes the top MPLS label at the penultimate router (P-1), before the packet reaches PE-2. • This causes loss of EXP bits from the outer label, preventing PE-2 from classifying the traffic based on them. • Using explicit-null on PE-1 ensures the outer MPLS label is preserved, but with label value 0 (IPv4 explicit-null), so that EXP bits reach PE-2. • PE-2 can then read the EXP bits and classify the traffic correctly
upvoted 1 times
...
fukJUNIPER
9 months, 1 week ago
Selected Answer: C
The QoS is on the label and the second-to-last router on the LSP should keep the label on instead of having it arrived popped
upvoted 1 times
...
StargateCommand
1 year ago
Selected Answer: C
Explicit-null should be configured on PE-2
upvoted 4 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...