JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
The on-call engineer at ValleyCross Fiber receives this fault report: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. What initial check best isolates the actual failing protocol stage?
This check may help with another root cause, for example: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. It does not test the first failed condition; start with: Inspect tunnel endpoint addresses and underlay routes, then capture GRE protocol 47 traffic at both intended endpoints.
The check diagnoses a different layer of service. Its source issue is: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. The relevant initial check is: Inspect tunnel endpoint addresses and underlay routes, then capture GRE protocol 47 traffic at both intended endpoints.
The check diagnoses a different layer of service. Its source issue is: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. The relevant initial check is: Inspect tunnel endpoint addresses and underlay routes, then capture GRE protocol 47 traffic at both intended endpoints.
Inspect tunnel endpoint addresses and underlay routes, then capture GRE protocol 47 traffic at both intended endpoints. GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint.
The provider operations team at Summit Logistics reports: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. Which implementation decision best corrects the cause?
Reduce the tunnel's effective MTU or apply suitable supported PMTUD/MSS handling so encapsulated packets fit the actual underlay. The case-specific reason is: Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass. A direct acceptance test is: Traffic at realistic payload sizes traverses the GRE path without systematic fragmentation-needed loss or TCP blackhole symptoms.
That would address a separate configuration fault: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. This stem identifies a different cause, corrected by: Reduce the tunnel's effective MTU or apply suitable supported PMTUD/MSS handling so encapsulated packets fit the actual underlay.
This action may apply to a different problem, for example: A GRE tunnel's outer destination route is accidentally learned through the GRE interface itself, causing the tunnel to recursively depend on its own availability. It does not repair the stated failure boundary. The case-specific reason is: Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass.
The other action is relevant when Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. The current case instead requires: Reduce the tunnel's effective MTU or apply suitable supported PMTUD/MSS handling so encapsulated packets fit the actual underlay. The distinction is: Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass.
During a post-change check at Summit Logistics, the original condition was: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. What evidence would validate the corrected behavior?
The observation confirms a different component's behavior. Its source context is: A GRE tunnel's outer destination route is accidentally learned through the GRE interface itself, causing the tunnel to recursively depend on its own availability. In this case the success criterion is: Traffic at realistic payload sizes traverses the GRE path without systematic fragmentation-needed loss or TCP blackhole symptoms.
That check proves something else, such as: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. It could pass while the stated problem remains. The targeted evidence here is: Traffic at realistic payload sizes traverses the GRE path without systematic fragmentation-needed loss or TCP blackhole symptoms.
Traffic at realistic payload sizes traverses the GRE path without systematic fragmentation-needed loss or TCP blackhole symptoms. Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass.
The observation confirms a different component's behavior. Its source context is: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. In this case the success criterion is: Traffic at realistic payload sizes traverses the GRE path without systematic fragmentation-needed loss or TCP blackhole symptoms.
At Summit Logistics, an engineer is asked to explain this case: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. Which underlying routing or switching principle accounts for the appropriate solution?
GRE introduces extra outer IP and encapsulation bytes, reducing effective payload MTU compared with the underlay interface. The key distinction is: Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass. Accordingly the remedy is: Reduce the tunnel's effective MTU or apply suitable supported PMTUD/MSS handling so encapsulated packets fit the actual underlay.
The statement can be true when A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. But it does not explain the reported failure. Here: Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass.
That principle belongs to a different service stage: Two remote routers intend to exchange isolated routes through GRE, but the local tunnel configuration still names the retired remote outer endpoint even though the new endpoint is reachable over the underlay. The directly relevant mechanism is: GRE introduces extra outer IP and encapsulation bytes, reducing effective payload MTU compared with the underlay interface.
This explains a separate protocol behavior: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. In the current facts, the controlling mechanism is: GRE introduces extra outer IP and encapsulation bytes, reducing effective payload MTU compared with the underlay interface.
A risk assessment at Summit Logistics identifies: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. Which practical consequence is most specifically tied to this failure?
It is a risk in another topology or protocol state: Two remote routers intend to exchange isolated routes through GRE, but the local tunnel configuration still names the retired remote outer endpoint even though the new endpoint is reachable over the underlay. Here the most direct failure path is: Large packets can be lost or fragmented repeatedly, affecting real applications while small test packets falsely appear healthy.
Large packets can be lost or fragmented repeatedly, affecting real applications while small test packets falsely appear healthy. The direct mitigation is: Reduce the tunnel's effective MTU or apply suitable supported PMTUD/MSS handling so encapsulated packets fit the actual underlay.
It is a risk in another topology or protocol state: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. Here the most direct failure path is: Large packets can be lost or fragmented repeatedly, affecting real applications while small test packets falsely appear healthy.
It is a risk in another topology or protocol state: A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. Here the most direct failure path is: Large packets can be lost or fragmented repeatedly, affecting real applications while small test packets falsely appear healthy.
The on-call engineer at Summit Logistics receives this fault report: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. What initial check best isolates the actual failing protocol stage?
The check diagnoses a different layer of service. Its source issue is: Two remote routers intend to exchange isolated routes through GRE, but the local tunnel configuration still names the retired remote outer endpoint even though the new endpoint is reachable over the underlay. The relevant initial check is: Measure underlay and tunnel MTUs, send size-controlled probes and inspect ICMP fragmentation-needed or packet captures at tunnel edges.
This check may help with another root cause, for example: A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. It does not test the first failed condition; start with: Measure underlay and tunnel MTUs, send size-controlled probes and inspect ICMP fragmentation-needed or packet captures at tunnel edges.
Measure underlay and tunnel MTUs, send size-controlled probes and inspect ICMP fragmentation-needed or packet captures at tunnel edges. Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass.
The check diagnoses a different layer of service. Its source issue is: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. The relevant initial check is: Measure underlay and tunnel MTUs, send size-controlled probes and inspect ICMP fragmentation-needed or packet captures at tunnel edges.
A production change request at Cedar Coast Telecom includes this finding: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. What should the engineer change to address it?
Reduce the tunnel's effective MTU or apply suitable supported PMTUD/MSS handling so encapsulated packets fit the actual underlay. The case-specific reason is: Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass. A direct acceptance test is: Traffic at realistic payload sizes traverses the GRE path without systematic fragmentation-needed loss or TCP blackhole symptoms.
That would address a separate configuration fault: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. This stem identifies a different cause, corrected by: Reduce the tunnel's effective MTU or apply suitable supported PMTUD/MSS handling so encapsulated packets fit the actual underlay.
That would address a separate configuration fault: A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. This stem identifies a different cause, corrected by: Reduce the tunnel's effective MTU or apply suitable supported PMTUD/MSS handling so encapsulated packets fit the actual underlay.
This action may apply to a different problem, for example: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. It does not repair the stated failure boundary. The case-specific reason is: Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass.
After Cedar Coast Telecom applies its proposed fix to this problem — A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. — which observation best proves the specific failure has been resolved?
The observation confirms a different component's behavior. Its source context is: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. In this case the success criterion is: Traffic at realistic payload sizes traverses the GRE path without systematic fragmentation-needed loss or TCP blackhole symptoms.
Traffic at realistic payload sizes traverses the GRE path without systematic fragmentation-needed loss or TCP blackhole symptoms. Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass.
That check proves something else, such as: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. It could pass while the stated problem remains. The targeted evidence here is: Traffic at realistic payload sizes traverses the GRE path without systematic fragmentation-needed loss or TCP blackhole symptoms.
This would be valid for another situation: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. It does not establish that the failing boundary in this scenario works; verify: Traffic at realistic payload sizes traverses the GRE path without systematic fragmentation-needed loss or TCP blackhole symptoms.
An architecture review at Cedar Coast Telecom examines the following symptom: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. What Junos or protocol mechanism is most directly responsible?
This explains a separate protocol behavior: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. In the current facts, the controlling mechanism is: GRE introduces extra outer IP and encapsulation bytes, reducing effective payload MTU compared with the underlay interface.
This explains a separate protocol behavior: Two remote routers intend to exchange isolated routes through GRE, but the local tunnel configuration still names the retired remote outer endpoint even though the new endpoint is reachable over the underlay. In the current facts, the controlling mechanism is: GRE introduces extra outer IP and encapsulation bytes, reducing effective payload MTU compared with the underlay interface.
GRE introduces extra outer IP and encapsulation bytes, reducing effective payload MTU compared with the underlay interface. The key distinction is: Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass. Accordingly the remedy is: Reduce the tunnel's effective MTU or apply suitable supported PMTUD/MSS handling so encapsulated packets fit the actual underlay.
That principle belongs to a different service stage: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. The directly relevant mechanism is: GRE introduces extra outer IP and encapsulation bytes, reducing effective payload MTU compared with the underlay interface.
The team at Cedar Coast Telecom defers a fix for this condition: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. What failure is most likely if no targeted control is applied?
That consequence is more closely associated with another deficiency, such as: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. The described fault instead exposes: Large packets can be lost or fragmented repeatedly, affecting real applications while small test packets falsely appear healthy.
It is a risk in another topology or protocol state: An edge has working IPv4 defaults but no IPv6 path to a remote subnet after the customer's IPv6 handoff is enabled. Here the most direct failure path is: Large packets can be lost or fragmented repeatedly, affecting real applications while small test packets falsely appear healthy.
Large packets can be lost or fragmented repeatedly, affecting real applications while small test packets falsely appear healthy. The direct mitigation is: Reduce the tunnel's effective MTU or apply suitable supported PMTUD/MSS handling so encapsulated packets fit the actual underlay.
It is a risk in another topology or protocol state: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. Here the most direct failure path is: Large packets can be lost or fragmented repeatedly, affecting real applications while small test packets falsely appear healthy.
During provider troubleshooting at Cedar Coast Telecom, this symptom is observed: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. Which targeted inspection should precede remediation?
Measure underlay and tunnel MTUs, send size-controlled probes and inspect ICMP fragmentation-needed or packet captures at tunnel edges. Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass.
This check may help with another root cause, for example: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. It does not test the first failed condition; start with: Measure underlay and tunnel MTUs, send size-controlled probes and inspect ICMP fragmentation-needed or packet captures at tunnel edges.
This check may help with another root cause, for example: A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. It does not test the first failed condition; start with: Measure underlay and tunnel MTUs, send size-controlled probes and inspect ICMP fragmentation-needed or packet captures at tunnel edges.
That evidence could be normal while the reported defect persists. It is aimed at: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. Instead inspect: Measure underlay and tunnel MTUs, send size-controlled probes and inspect ICMP fragmentation-needed or packet captures at tunnel edges.
Please check your mailbox for a message from support@examlabs.com and follow the directions.