MPLS and RSVP Configuration: Potential Causes for LSP Traffic Issue

Potential Causes for LSP Traffic Issue

Prev Question Next Question

Question

You have configured MPLS and RSVP in your network using all of the Junos defaults. You have established an LSP in your network, which is reporting a status of

"Up", but no traffic is using it. Which two statements reflect potential causes for this issue? (Choose two)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

CD

MPLS (Multiprotocol Label Switching) and RSVP (Resource Reservation Protocol) are used to provide Quality of Service (QoS) and traffic engineering capabilities in a network. In this scenario, an LSP (Label Switched Path) has been configured and is reporting a status of "Up", but no traffic is using it. Two potential causes for this issue could be:

A. The LSP egress address is a physical interface address: If the LSP egress address is a physical interface address instead of a loopback address, it could cause issues. This is because physical interface addresses are not stable and can change when the interface goes down or when the device reboots. This could result in traffic being dropped or misrouted. It is recommended to use a loopback address as the LSP egress address to ensure stability.

B. Family MPLS was omitted from the router configurations: If the family MPLS was omitted from the router configurations, it would prevent the router from being able to forward MPLS traffic. This would cause traffic to be dropped or misrouted, and prevent it from using the LSP that has been established.

C. No BGP routes are being advertised from the remote neighbor: If the remote neighbor is not advertising any BGP routes, it could cause issues with traffic using the LSP. BGP routes are required for traffic to be forwarded along the LSP. If no BGP routes are being advertised, traffic will be dropped or misrouted.

D. The LSP egress address does not match the BGP next-hop address: If the LSP egress address does not match the BGP next-hop address, it could cause issues with traffic using the LSP. The BGP next-hop address is used to forward traffic to the egress point of the LSP. If it does not match the LSP egress address, traffic will be dropped or misrouted.

Out of the four options, options A and B are the potential causes for this issue. Option A relates to the stability of the LSP egress address, and option B relates to the ability of the router to forward MPLS traffic. Options C and D are not related to the issue of traffic not using the LSP, although they could cause other issues with MPLS and BGP routing.