JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
A support escalation at Crestpoint Research describes: An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. Where should the Junos operator look first for decisive evidence?
This check may help with another root cause, for example: A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. It does not test the first failed condition; start with: Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.
That evidence could be normal while the reported defect persists. It is aimed at: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. Instead inspect: Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.
Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC. LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.
This check may help with another root cause, for example: A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. It does not test the first failed condition; start with: Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.
During a Junos network change at Eastvale MetroNet, the engineer observes: An explicitly constrained MPLS LSP should avoid one core link, but its RSVP-TE signaling never completes because a transit hop lacks appropriate resources. Which remediation most directly fixes the described problem?
The other action is relevant when An MPLS service fails for one destination though IGP adjacencies and transport IP routes are stable; the team needs to identify the first broken label operation. The current case instead requires: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint. The distinction is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.
That would address a separate configuration fault: An MPLS service ingress forwards plain IP over a core link instead of imposing the transport label despite a valid route to the remote egress. This stem identifies a different cause, corrected by: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.
This action may apply to a different problem, for example: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. It does not repair the stated failure boundary. The case-specific reason is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.
Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint. The case-specific reason is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem. A direct acceptance test is: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
The Junos team at Eastvale MetroNet needs a success criterion for this defect: An explicitly constrained MPLS LSP should avoid one core link, but its RSVP-TE signaling never completes because a transit hop lacks appropriate resources. Which observed result most precisely confirms the intended repair?
The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding. The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.
That check proves something else, such as: An MPLS service ingress forwards plain IP over a core link instead of imposing the transport label despite a valid route to the remote egress. It could pass while the stated problem remains. The targeted evidence here is: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
This would be valid for another situation: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. It does not establish that the failing boundary in this scenario works; verify: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
The observation confirms a different component's behavior. Its source context is: A provider replaces an MPLS transit router and packets fail at the next hop because the local forwarding table has an invalid outgoing label operation. In this case the success criterion is: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
While analyzing a service failure at Eastvale MetroNet, the following is observed: An explicitly constrained MPLS LSP should avoid one core link, but its RSVP-TE signaling never completes because a transit hop lacks appropriate resources. Which mechanism best explains the underlying control-plane or forwarding behavior?
This explains a separate protocol behavior: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. In the current facts, the controlling mechanism is: RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling.
The statement can be true when A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. But it does not explain the reported failure. Here: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.
That principle belongs to a different service stage: An MPLS service fails for one destination though IGP adjacencies and transport IP routes are stable; the team needs to identify the first broken label operation. The directly relevant mechanism is: RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling.
RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling. The key distinction is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem. Accordingly the remedy is: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.
The following provider defect remains uncorrected at Eastvale MetroNet: An explicitly constrained MPLS LSP should avoid one core link, but its RSVP-TE signaling never completes because a transit hop lacks appropriate resources. What is the most direct service or security risk of leaving it unresolved?
It is a risk in another topology or protocol state: A provider expects a preplanned backup RSVP path to protect traffic but a primary transport failure causes prolonged loss. Here the most direct failure path is: An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.
An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP. The direct mitigation is: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.
That consequence is more closely associated with another deficiency, such as: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. The described fault instead exposes: An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.
It is a risk in another topology or protocol state: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. Here the most direct failure path is: An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.
A support escalation at Eastvale MetroNet describes: An explicitly constrained MPLS LSP should avoid one core link, but its RSVP-TE signaling never completes because a transit hop lacks appropriate resources. Where should the Junos operator look first for decisive evidence?
Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop. The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.
This check may help with another root cause, for example: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. It does not test the first failed condition; start with: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.
That evidence could be normal while the reported defect persists. It is aimed at: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. Instead inspect: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.
The check diagnoses a different layer of service. Its source issue is: A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. The relevant initial check is: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.
The provider operations team at Bridgeway Cloud reports: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. Which implementation decision best corrects the cause?
This action may apply to a different problem, for example: An engineer assumes that seeing a label in a protocol database means it must already be programmed into the forwarding plane. It does not repair the stated failure boundary. The case-specific reason is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.
Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint. The case-specific reason is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem. A direct acceptance test is: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
That would address a separate configuration fault: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. This stem identifies a different cause, corrected by: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.
This action may apply to a different problem, for example: A transport egress receives an extra MPLS label that an upstream design expected the penultimate hop to remove. It does not repair the stated failure boundary. The case-specific reason is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.
During a post-change check at Bridgeway Cloud, the original condition was: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. What evidence would validate the corrected behavior?
This would be valid for another situation: A provider replaces an MPLS transit router and packets fail at the next hop because the local forwarding table has an invalid outgoing label operation. It does not establish that the failing boundary in this scenario works; verify: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
The observation confirms a different component's behavior. Its source context is: A provider expects a preplanned backup RSVP path to protect traffic but a primary transport failure causes prolonged loss. In this case the success criterion is: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
That check proves something else, such as: A provider sees an implicit-null binding from the egress but its transit operator misreads that as a request to forward a literal implicit-null label in data traffic. It could pass while the stated problem remains. The targeted evidence here is: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding. The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.
At Bridgeway Cloud, an engineer is asked to explain this case: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. Which underlying routing or switching principle accounts for the appropriate solution?
That principle belongs to a different service stage: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. The directly relevant mechanism is: RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling.
RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling. The key distinction is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem. Accordingly the remedy is: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.
The statement can be true when A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. But it does not explain the reported failure. Here: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.
That principle belongs to a different service stage: A provider's MPLS QoS troubleshooting treats the three-bit traffic class as though it were the forwarding label value. The directly relevant mechanism is: RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling.
A risk assessment at Bridgeway Cloud identifies: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. Which practical consequence is most specifically tied to this failure?
That consequence is more closely associated with another deficiency, such as: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. The described fault instead exposes: An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.
An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP. The direct mitigation is: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.
The concern could occur elsewhere when An engineer assumes that seeing a label in a protocol database means it must already be programmed into the forwarding plane. For the stated scenario, the immediate risk is: An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.
That consequence is more closely associated with another deficiency, such as: A transit LSR receives a labeled frame but sends a packet bearing the same incoming label to the next hop when the downstream binding expects another label. The described fault instead exposes: An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.
The on-call engineer at Bridgeway Cloud receives this fault report: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. What initial check best isolates the actual failing protocol stage?
Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop. The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.
The check diagnoses a different layer of service. Its source issue is: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. The relevant initial check is: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.
This check may help with another root cause, for example: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. It does not test the first failed condition; start with: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.
That evidence could be normal while the reported defect persists. It is aimed at: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. Instead inspect: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.
Please check your mailbox for a message from support@examlabs.com and follow the directions.