nerdexam
Cisco

300-510 · Question #176

Refer to the exhibit. MPLS traffic from 192.168.4.0/24 to 192.168.5.0/24 is failing to pass over the link from R4 to R2. The engineer verified that: - Cisco Express Forwarding is enabled on all…

The correct answer is B. On router R2, configure the mpls ip command on the s0/0/4 interface. MPLS requires the 'mpls ip' command to be configured on each individual interface that needs to participate in MPLS label distribution and forwarding. CEF is enabled globally, OSPF provides full reachability, and the R1-R2 link works for MPLS, confirming the overall MPLS…

MPLS and Segment Routing

Question

Refer to the exhibit. MPLS traffic from 192.168.4.0/24 to 192.168.5.0/24 is failing to pass over the link from R4 to R2. The engineer verified that:

  • Cisco Express Forwarding is enabled on all routers.
  • All routers reach all networks via OSPF.
  • MPLS traffic from 192.168.1.0/24 to 192.168.3.0/24 is passing

normally over the link from R1 to R2. Which action resolves the issue?

Exhibits

300-510 question #176 exhibit 1
300-510 question #176 exhibit 2

Options

  • AOn router R4, remove the mpls ip command on the s/0/0/2 interface.
  • BOn router R2, configure the mpls ip command on the s0/0/4 interface.
  • COn router R4, configure the mpls label protocol Idp command on all serial interfaces.
  • DOn router R2, configure the mpls label protocol Idp command on the interface.

How the community answered

(54 responses)
  • A
    4% (2)
  • B
    83% (45)
  • C
    11% (6)
  • D
    2% (1)

Explanation

MPLS requires the 'mpls ip' command to be configured on each individual interface that needs to participate in MPLS label distribution and forwarding. CEF is enabled globally, OSPF provides full reachability, and the R1-R2 link works for MPLS, confirming the overall MPLS infrastructure is functional. The fact that only the R4-R2 path fails for MPLS traffic, combined with the clue that traffic from 192.168.1.0/24 to 192.168.3.0/24 works over R1-R2, indicates that R2's interface s0/0/4 (the interface connecting toward R4) is missing the 'mpls ip' command. Without it, LDP does not run on that interface and MPLS forwarding is not enabled, causing MPLS traffic from R4 to be dropped at R2.

Topics

#MPLS#LDP#Interface Configuration#Troubleshooting

Community Discussion

No community discussion yet for this question.

Full 300-510 Practice