An engineer noticed that PE3 is failing to accept IPv6 traffic information from PE1. The engineer confirmed that both PE3 and PE1 routers are configured accurately with IPv6 protocol. To eliminate…

Question

Options

• ADisable 6PVE that provides local IPv6 reachability over MPLS.
• BConfigure 6PE that provides global IPv6 reachability over IPv4 MPLS
• CAllow PE routers use the MP-iBGP extensions in the IPv6 network configuration to exchange
• DConfigure 6PE forwarding between 6PE routers based on the IPv6 header

• A
  16% (5)
• B
  72% (23)
• C
  9% (3)
• D
  3% (1)

Explanation

6PE (6 Provider Edge) must be configured because it is the technology specifically designed to enable IPv6 routing information to be exchanged and forwarded across an existing IPv4 MPLS backbone - without it, PE routers cannot share IPv6 prefixes with each other even if IPv6 is locally enabled. 6PE uses MP-BGP (Multiprotocol BGP) to carry IPv6 routes between PE routers and uses MPLS labels to forward IPv6 traffic across the IPv4 core.

Why the distractors are wrong:

• A is wrong on two counts: "6PVE" is not a real standard, and disabling any feature would worsen reachability, not fix it.
• C is partially true - MP-iBGP extensions are part of how 6PE works - but this option is incomplete and doesn't address the full solution; enabling 6PE (B) inherently configures the necessary MP-BGP extensions.
• D is wrong because 6PE forwarding does not use the IPv6 header for switching decisions through the core - it uses MPLS labels assigned at the ingress PE, with the IPv6 header only relevant at the edge.

Memory tip: Think of 6PE as a tunnel disguise - it dresses IPv6 traffic in MPLS labels so it can travel through an IPv4 core undetected. "No 6PE = No IPv6 visibility between PEs," regardless of local IPv6 config.

No community discussion yet for this question.