JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
A support escalation at Maple Coast Retail describes: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. Where should the Junos operator look first for decisive evidence?
This check may help with another root cause, for example: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. It does not test the first failed condition; start with: Verify outer IPv4 reachability, tunnel encapsulation family, IPv6 tunnel addressing and effective path MTU using appropriately sized probes.
Verify outer IPv4 reachability, tunnel encapsulation family, IPv6 tunnel addressing and effective path MTU using appropriately sized probes. A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient.
That evidence could be normal while the reported defect persists. It is aimed at: A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. Instead inspect: Verify outer IPv4 reachability, tunnel encapsulation family, IPv6 tunnel addressing and effective path MTU using appropriately sized probes.
The check diagnoses a different layer of service. Its source issue 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. The relevant initial check is: Verify outer IPv4 reachability, tunnel encapsulation family, IPv6 tunnel addressing and effective path MTU using appropriately sized probes.
During a Junos network change at Cedar Coast Telecom, the engineer observes: 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. Which remediation most directly fixes the described problem?
Correct the GRE tunnel source and destination to reachable outer transport addresses and enable the intended tunnel interface and routed reachability. The case-specific reason is: GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint. A direct acceptance test is: Outer GRE packets arrive at the actual remote endpoint and inner packets emerge on the correct tunnel interface with approved routes.
The other action is relevant when A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. The current case instead requires: Correct the GRE tunnel source and destination to reachable outer transport addresses and enable the intended tunnel interface and routed reachability. The distinction is: GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint.
This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint.
This action may apply to a different problem, for example: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. It does not repair the stated failure boundary. The case-specific reason is: GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint.
The Junos team at Cedar Coast Telecom needs a success criterion for this defect: 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. Which observed result most precisely confirms the intended repair?
Outer GRE packets arrive at the actual remote endpoint and inner packets emerge on the correct tunnel interface with approved routes. GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint.
The observation confirms a different component's behavior. Its source context is: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. In this case the success criterion is: Outer GRE packets arrive at the actual remote endpoint and inner packets emerge on the correct tunnel interface with approved routes.
That check proves something else, such as: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. It could pass while the stated problem remains. The targeted evidence here is: Outer GRE packets arrive at the actual remote endpoint and inner packets emerge on the correct tunnel interface with approved routes.
This would be valid for another situation: A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. It does not establish that the failing boundary in this scenario works; verify: Outer GRE packets arrive at the actual remote endpoint and inner packets emerge on the correct tunnel interface with approved routes.
While analyzing a service failure at Cedar Coast Telecom, the following is observed: 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. Which mechanism best explains the underlying control-plane or forwarding behavior?
That principle belongs to a different service stage: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. The directly relevant mechanism is: GRE encapsulates an inner packet in an outer IP header addressed to the configured remote endpoint; a stale destination sends outer packets to the wrong device.
GRE encapsulates an inner packet in an outer IP header addressed to the configured remote endpoint; a stale destination sends outer packets to the wrong device. The key distinction is: GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint. Accordingly the remedy is: Correct the GRE tunnel source and destination to reachable outer transport addresses and enable the intended tunnel interface and routed reachability.
The statement can be true when A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. But it does not explain the reported failure. Here: GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint.
That principle belongs to a different service stage: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. The directly relevant mechanism is: GRE encapsulates an inner packet in an outer IP header addressed to the configured remote endpoint; a stale destination sends outer packets to the wrong device.
The following provider defect remains uncorrected at Cedar Coast Telecom: 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. What is the most direct service or security risk of leaving it unresolved?
That consequence is more closely associated with another deficiency, such as: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. The described fault instead exposes: Packets can be sent to an obsolete encapsulation endpoint and disappear despite normal reachability between unrelated router interfaces.
Packets can be sent to an obsolete encapsulation endpoint and disappear despite normal reachability between unrelated router interfaces. The direct mitigation is: Correct the GRE tunnel source and destination to reachable outer transport addresses and enable the intended tunnel interface and routed reachability.
The concern could occur elsewhere when A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. For the stated scenario, the immediate risk is: Packets can be sent to an obsolete encapsulation endpoint and disappear despite normal reachability between unrelated router interfaces.
That consequence is more closely associated with another deficiency, such as: 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 described fault instead exposes: Packets can be sent to an obsolete encapsulation endpoint and disappear despite normal reachability between unrelated router interfaces.
A support escalation at Cedar Coast Telecom describes: 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. Where should the Junos operator look first for decisive evidence?
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 check diagnoses a different layer of service. Its source issue is: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. The relevant initial check is: Inspect tunnel endpoint addresses and underlay routes, then capture GRE protocol 47 traffic at both intended endpoints.
This check may help with another root cause, for example: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. 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.
That evidence could be normal while the reported defect persists. It is aimed at: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. Instead inspect: Inspect tunnel endpoint addresses and underlay routes, then capture GRE protocol 47 traffic at both intended endpoints.
The provider operations team at ValleyCross Fiber reports: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. Which implementation decision best corrects the cause?
Correct the GRE tunnel source and destination to reachable outer transport addresses and enable the intended tunnel interface and routed reachability. The case-specific reason is: GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint. A direct acceptance test is: Outer GRE packets arrive at the actual remote endpoint and inner packets emerge on the correct tunnel interface with approved routes.
This action may apply to a different problem, for example: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. It does not repair the stated failure boundary. The case-specific reason is: GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint.
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: Correct the GRE tunnel source and destination to reachable outer transport addresses and enable the intended tunnel interface and routed reachability. The distinction is: GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint.
This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint.
During a post-change check at ValleyCross Fiber, the original condition was: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. What evidence would validate the corrected behavior?
This would be valid for another situation: 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 establish that the failing boundary in this scenario works; verify: Outer GRE packets arrive at the actual remote endpoint and inner packets emerge on the correct tunnel interface with approved routes.
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: Outer GRE packets arrive at the actual remote endpoint and inner packets emerge on the correct tunnel interface with approved routes.
Outer GRE packets arrive at the actual remote endpoint and inner packets emerge on the correct tunnel interface with approved routes. GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint.
That check proves something else, such as: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. It could pass while the stated problem remains. The targeted evidence here is: Outer GRE packets arrive at the actual remote endpoint and inner packets emerge on the correct tunnel interface with approved routes.
At ValleyCross Fiber, an engineer is asked to explain this case: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. Which underlying routing or switching principle accounts for the appropriate solution?
GRE encapsulates an inner packet in an outer IP header addressed to the configured remote endpoint; a stale destination sends outer packets to the wrong device. The key distinction is: GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint. Accordingly the remedy is: Correct the GRE tunnel source and destination to reachable outer transport addresses and enable the intended tunnel interface and routed reachability.
That principle belongs to a different service stage: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. The directly relevant mechanism is: GRE encapsulates an inner packet in an outer IP header addressed to the configured remote endpoint; a stale destination sends outer packets to the wrong device.
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 encapsulates an inner packet in an outer IP header addressed to the configured remote endpoint; a stale destination sends outer packets to the wrong device.
The statement can be true when An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. But it does not explain the reported failure. Here: GRE forwarding depends first on outer IP endpoint reachability; modifying the inner IGP metric does not fix an unreachable tunnel endpoint.
A risk assessment at ValleyCross Fiber identifies: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. Which practical consequence is most specifically tied to this failure?
The concern could occur elsewhere when A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. For the stated scenario, the immediate risk is: Packets can be sent to an obsolete encapsulation endpoint and disappear despite normal reachability between unrelated router interfaces.
Packets can be sent to an obsolete encapsulation endpoint and disappear despite normal reachability between unrelated router interfaces. The direct mitigation is: Correct the GRE tunnel source and destination to reachable outer transport addresses and enable the intended tunnel interface and routed reachability.
The concern could occur elsewhere when A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. For the stated scenario, the immediate risk is: Packets can be sent to an obsolete encapsulation endpoint and disappear despite normal reachability between unrelated router interfaces.
The concern could occur elsewhere when An edge has working IPv4 defaults but no IPv6 path to a remote subnet after the customer's IPv6 handoff is enabled. For the stated scenario, the immediate risk is: Packets can be sent to an obsolete encapsulation endpoint and disappear despite normal reachability between unrelated router interfaces.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.