An engineer needs to ensure that a core router can forward MPLS packets without checking the IP header. Which forwarding mechanism should be enabled?
Trap 1: Link Fragmentation and Interleaving (LFI)
Link Fragmentation and Interleaving (LFI) is used to reduce delay on low-speed links by fragmenting large packets. It does not relate to MPLS forwarding or label-based switching.
Trap 2: Per-packet load balancing
Per-packet load balancing distributes packets across multiple paths on a per-packet basis, but it does not enable label-based forwarding or eliminate IP lookups in MPLS.
Trap 3: Penultimate Hop Popping (PHP)
Penultimate Hop Popping (PHP) is an optimization where the penultimate router pops the label before sending to the egress. However, it is not the underlying forwarding mechanism; CEF is still needed for label switching.
- A
Link Fragmentation and Interleaving (LFI)
Why wrong: Link Fragmentation and Interleaving (LFI) is used to reduce delay on low-speed links by fragmenting large packets. It does not relate to MPLS forwarding or label-based switching.
- B
CEF switching
CEF switching is correct because it is the required switching mechanism for MPLS. With CEF, routers maintain LFIB entries to forward MPLS packets by label, avoiding IP header inspection.
- C
Per-packet load balancing
Why wrong: Per-packet load balancing distributes packets across multiple paths on a per-packet basis, but it does not enable label-based forwarding or eliminate IP lookups in MPLS.
- D
Penultimate Hop Popping (PHP)
Why wrong: Penultimate Hop Popping (PHP) is an optimization where the penultimate router pops the label before sending to the egress. However, it is not the underlying forwarding mechanism; CEF is still needed for label switching.