JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
The on-call engineer at Cascade Hosting receives this fault report: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. What initial check best isolates the actual failing protocol stage?
This check may help with another root cause, 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 test the first failed condition; start with: Inspect `show route table inet6.0` for the destination, next-hop resolution and IPv6 neighbor state on the intended transit link.
Inspect `show route table inet6.0` for the destination, next-hop resolution and IPv6 neighbor state on the intended transit link. The root fault is IPv6 routing-family reachability, not missing IPv4 inet.0 static configuration.
That evidence could be normal while the reported defect persists. It is aimed at: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. Instead inspect: Inspect `show route table inet6.0` for the destination, next-hop resolution and IPv6 neighbor state on the intended transit link.
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: Inspect `show route table inet6.0` for the destination, next-hop resolution and IPv6 neighbor state on the intended transit link.
The provider operations team at Northshore Utilities reports: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. Which implementation decision best corrects the cause?
This action may apply to a different problem, for example: An edge has working IPv4 defaults but no IPv6 path to a remote subnet after the customer's IPv6 handoff is enabled. It does not repair the stated failure boundary. The case-specific reason is: IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link.
Configure the intended OSPFv3 adjacency for IPv6 on both participating links and verify its IPv6 route advertisements. The case-specific reason is: IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link. A direct acceptance test is: The OSPFv3 neighbor establishes correctly and expected IPv6 prefixes are learned in the IPv6 routing table.
That would address a separate configuration fault: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. This stem identifies a different cause, corrected by: Configure the intended OSPFv3 adjacency for IPv6 on both participating links and verify its IPv6 route advertisements.
This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link.
During a post-change check at Northshore Utilities, the original condition was: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. What evidence would validate the corrected behavior?
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: The OSPFv3 neighbor establishes correctly and expected IPv6 prefixes are learned in the IPv6 routing table.
The observation confirms a different component's behavior. Its source context is: A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. In this case the success criterion is: The OSPFv3 neighbor establishes correctly and expected IPv6 prefixes are learned in the IPv6 routing table.
That check proves something else, such as: 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. It could pass while the stated problem remains. The targeted evidence here is: The OSPFv3 neighbor establishes correctly and expected IPv6 prefixes are learned in the IPv6 routing table.
The OSPFv3 neighbor establishes correctly and expected IPv6 prefixes are learned in the IPv6 routing table. IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link.
At Northshore Utilities, an engineer is asked to explain this case: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. Which underlying routing or switching principle accounts for the appropriate solution?
That principle belongs to a different service stage: An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. The directly relevant mechanism is: OSPFv3 is the OSPF protocol variant used for IPv6 routing in this context; OSPFv2's IPv4 adjacency does not carry IPv6 network reachability.
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: OSPFv3 is the OSPF protocol variant used for IPv6 routing in this context; OSPFv2's IPv4 adjacency does not carry IPv6 network reachability.
The statement can be true when Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. But it does not explain the reported failure. Here: IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link.
OSPFv3 is the OSPF protocol variant used for IPv6 routing in this context; OSPFv2's IPv4 adjacency does not carry IPv6 network reachability. The key distinction is: IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link. Accordingly the remedy is: Configure the intended OSPFv3 adjacency for IPv6 on both participating links and verify its IPv6 route advertisements.
A risk assessment at Northshore Utilities identifies: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. Which practical consequence is most specifically tied to this failure?
That consequence is more closely associated with another deficiency, such as: An edge has working IPv4 defaults but no IPv6 path to a remote subnet after the customer's IPv6 handoff is enabled. The described fault instead exposes: IPv6 destinations remain unreachable while operators are misled by an established IPv4 OSPF adjacency.
It is a risk in another topology or protocol state: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. Here the most direct failure path is: IPv6 destinations remain unreachable while operators are misled by an established IPv4 OSPF adjacency.
IPv6 destinations remain unreachable while operators are misled by an established IPv4 OSPF adjacency. The direct mitigation is: Configure the intended OSPFv3 adjacency for IPv6 on both participating links and verify its IPv6 route advertisements.
That consequence is more closely associated with another deficiency, such as: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. The described fault instead exposes: IPv6 destinations remain unreachable while operators are misled by an established IPv4 OSPF adjacency.
The on-call engineer at Northshore Utilities receives this fault report: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. What initial check best isolates the actual failing protocol stage?
That evidence could be normal while the reported defect persists. It is aimed at: An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. Instead inspect: Inspect OSPFv3 neighbor status and IPv6 route/LSA information separately from OSPFv2 state.
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 OSPFv3 neighbor status and IPv6 route/LSA information separately from OSPFv2 state.
This check may help with another root cause, for example: 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. It does not test the first failed condition; start with: Inspect OSPFv3 neighbor status and IPv6 route/LSA information separately from OSPFv2 state.
Inspect OSPFv3 neighbor status and IPv6 route/LSA information separately from OSPFv2 state. IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link.
A production change request at Brightwood Public Works includes this finding: A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. What should the engineer change to address it?
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: IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link.
Configure the intended OSPFv3 adjacency for IPv6 on both participating links and verify its IPv6 route advertisements. The case-specific reason is: IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link. A direct acceptance test is: The OSPFv3 neighbor establishes correctly and expected IPv6 prefixes are learned in the IPv6 routing table.
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: Configure the intended OSPFv3 adjacency for IPv6 on both participating links and verify its IPv6 route advertisements. The distinction is: IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link.
That would address a separate configuration fault: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. This stem identifies a different cause, corrected by: Configure the intended OSPFv3 adjacency for IPv6 on both participating links and verify its IPv6 route advertisements.
After Brightwood Public Works applies its proposed fix to this problem — A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. — which observation best proves the specific failure has been resolved?
The OSPFv3 neighbor establishes correctly and expected IPv6 prefixes are learned in the IPv6 routing table. IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link.
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: The OSPFv3 neighbor establishes correctly and expected IPv6 prefixes are learned in the IPv6 routing table.
The observation confirms a different component's behavior. Its source context is: A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. In this case the success criterion is: The OSPFv3 neighbor establishes correctly and expected IPv6 prefixes are learned in the IPv6 routing table.
That check proves something else, such as: 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. It could pass while the stated problem remains. The targeted evidence here is: The OSPFv3 neighbor establishes correctly and expected IPv6 prefixes are learned in the IPv6 routing table.
An architecture review at Brightwood Public Works examines the following symptom: A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. What Junos or protocol mechanism is most directly responsible?
The statement can be true when An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. But it does not explain the reported failure. Here: IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link.
OSPFv3 is the OSPF protocol variant used for IPv6 routing in this context; OSPFv2's IPv4 adjacency does not carry IPv6 network reachability. The key distinction is: IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link. Accordingly the remedy is: Configure the intended OSPFv3 adjacency for IPv6 on both participating links and verify its IPv6 route advertisements.
This explains a separate protocol behavior: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. In the current facts, the controlling mechanism is: OSPFv3 is the OSPF protocol variant used for IPv6 routing in this context; OSPFv2's IPv4 adjacency does not carry IPv6 network reachability.
The statement can be true when 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. But it does not explain the reported failure. Here: IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link.
The team at Brightwood Public Works defers a fix for this condition: A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. What failure is most likely if no targeted control is applied?
IPv6 destinations remain unreachable while operators are misled by an established IPv4 OSPF adjacency. The direct mitigation is: Configure the intended OSPFv3 adjacency for IPv6 on both participating links and verify its IPv6 route advertisements.
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: IPv6 destinations remain unreachable while operators are misled by an established IPv4 OSPF adjacency.
It is a risk in another topology or protocol state: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. Here the most direct failure path is: IPv6 destinations remain unreachable while operators are misled by an established IPv4 OSPF adjacency.
The concern could occur elsewhere when Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. For the stated scenario, the immediate risk is: IPv6 destinations remain unreachable while operators are misled by an established IPv4 OSPF adjacency.
During provider troubleshooting at Brightwood Public Works, this symptom is observed: A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. Which targeted inspection should precede remediation?
That evidence could be normal while the reported defect persists. It is aimed at: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. Instead inspect: Inspect OSPFv3 neighbor status and IPv6 route/LSA information separately from OSPFv2 state.
That evidence could be normal while the reported defect persists. It is aimed at: An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. Instead inspect: Inspect OSPFv3 neighbor status and IPv6 route/LSA information separately from OSPFv2 state.
The check diagnoses a different layer of service. Its source issue is: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. The relevant initial check is: Inspect OSPFv3 neighbor status and IPv6 route/LSA information separately from OSPFv2 state.
Inspect OSPFv3 neighbor status and IPv6 route/LSA information separately from OSPFv2 state. IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link.
Please check your mailbox for a message from support@examlabs.com and follow the directions.