Juniper JN0-364 Questions & Answers

Configure the same intended OSPF area and compatible interface parameters on both ends of the link. Its normal acceptance signal would be the pair establishes the expected OSPF adjacency with matching area assignment and reachable learned prefixes. Here the deciding check is different: the receiving area's LSDB and route table show intended inter-area reachability without copying the source area's full topology.

Apply a scoped OSPF export policy to originate only the approved active source prefix and confirm the receiving routers learn it. Its normal acceptance signal would be the approved external route is advertised with the intended type and metric while unapproved routes are not redistributed. Here the deciding check is different: the receiving area's LSDB and route table show intended inter-area reachability without copying the source area's full topology.

Align prefix-SID advertisements and SRGB interpretation on the participating routers and verify labels assigned for the FEC. This addresses segment routing prefix SID, but the reported symptoms arise from OSPF area LSA propagation. For this case, verify instead that the receiving area's LSDB and route table show intended inter-area reachability without copying the source area's full topology.

Internal BGP best paths prefer the approved egress due to the intended local-preference values. That establishes BGP local preference rather than a repaired graceful restart peer assistance path. The reported failure still requires this evidence: during a controlled routing restart, participating neighbors retain forwarding state only for the permitted grace interval and then converge correctly.

This measurement tests GRES preserves forwarding not protocols; it cannot distinguish success from failure for the observed graceful restart peer assistance condition. Graceful restart depends on protocol restart and helper behavior; it is not identical to copying live routing protocol state to a backup Routing Engine.

The same virtual gateway remains reachable when the active VRRP router is failed in a controlled test. That establishes VRRP virtual gateway failover rather than a repaired graceful restart peer assistance path. The reported failure still requires this evidence: during a controlled routing restart, participating neighbors retain forwarding state only for the permitted grace interval and then converge correctly.

Check downstream label advertisement, selected next hop, and label binding installation before activating the LSP path. That could help in a case involving LDP label binding completeness. This failure instead depends on BGP communities and routing policy; BGP communities provide policy metadata for grouping routes; they have no forwarding effect unless a matching policy interprets them.

Apply an approved outbound AS-path prepend policy on the less-preferred advertised path and validate what peers receive. That could help in a case involving AS-path prepend inbound influence. This failure instead depends on BGP communities and routing policy; BGP communities provide policy metadata for grouping routes; they have no forwarding effect unless a matching policy interprets them.

Configure the appropriate EBGP multihop reachability and neighbor addressing, then verify session setup on the intended loopback endpoints. Its normal acceptance signal would be the intended multi-hop peer establishes while IP reachability and any required loopback-source configuration are correct. Here the deciding check is different: advertised routes carry the intended community and the relevant neighbor policy matches those routes as designed.

LACP aggregates only compatible negotiated member links; physical Up state alone does not prove active bundle participation. Those conditions do not account for the specific IS-IS TLV reachability problem reported by Ridgefield Carrier.

On an IS-IS broadcast LAN the DIS originates pseudonode LSPs and may be re-elected when priority changes; the process differs from OSPF DR behavior. That describes IS-IS LAN designated intermediate system, whereas the observed symptoms are caused by IS-IS TLV reachability; it does not predict the reported behavior.

This principle matters when troubleshooting IS-IS L1 and L2 reachability, but using it here mistakes a different failure mode for IS-IS TLV reachability. The relevant distinction is: IS-IS uses TLVs inside its PDUs to encode prefix and protocol capabilities; adjacency alone is not proof of expected reachability advertisements.

Adjust the RSVP-TE bandwidth request or planned constraint-capable path and validate reservation availability. This addresses RSVP path bandwidth admission, but the reported symptoms arise from RSVP PATH and RESV signaling. For this case, verify instead that the LSP shows a completed RSVP reservation and an operational signaled path through intended hops.

Verify full label stack ordering and bottom-of-stack indication on the encapsulated service path. This addresses MPLS label stack bottom bit, but the reported symptoms arise from RSVP PATH and RESV signaling. For this case, verify instead that the LSP shows a completed RSVP reservation and an operational signaled path through intended hops.

Set and test a coherent MED policy between comparable paths, acknowledging peer AS comparison behavior and upstream policies. This addresses BGP MED neighbor consideration, but the reported symptoms arise from RSVP PATH and RESV signaling. For this case, verify instead that the LSP shows a completed RSVP reservation and an operational signaled path through intended hops.

The control protects IS-IS NET and system ID. It does not establish the ongoing equal-cost forwarding flow hashing behavior required in this network. Equal routing candidates do not prove the forwarding engine is using ECMP; Junos load-balancing policy and flow hashing determine installed next hops.

The control protects generated route qualified next hop. It does not establish the ongoing equal-cost forwarding flow hashing behavior required in this network. Equal routing candidates do not prove the forwarding engine is using ECMP; Junos load-balancing policy and flow hashing determine installed next hops.

This is a useful guard against filter-based forwarding table selection, but it is not scoped to the observed equal-cost forwarding flow hashing failure. An appropriate test would show that the forwarding table contains the intended next-hop set and several independent flows distribute across healthy equal-cost paths.

This principle matters when troubleshooting MPLS label forwarding table mismatch, but using it here mistakes a different failure mode for LDP transport address reachability. The relevant distinction is: LDP discovery and session setup are distinct; a transport TCP connection must be reachable after hello discovery.

Access ports and trunk ports have different VLAN tagging and membership behaviors; link-up state does not make the modes equivalent. That describes VLAN access trunk distinction, whereas the observed symptoms are caused by LDP transport address reachability; it does not predict the reported behavior.

LDP supplies label bindings for eligible FECs; IP reachability without a usable label binding does not prove labeled forwarding. Those conditions do not account for the specific LDP transport address reachability problem reported by Deltawood Hosting.

Validate next-hop address scope and outbound interface for static IPv6 routes during deployment. That ongoing check is for IPv6 static next-hop scope; it would not reliably detect recurrence of IPv6 over IPv4 tunnel underlay. An IPv6-over-IPv4 tunnel depends on the IPv4 underlay that transports encapsulated packets; overlay route presence cannot replace underlay connectivity.

Test forwarding, bridge MAC state, and protocol-neighbor continuity separately during redundant Routing Engine failover drills. The monitored boundary differs from IPv6 over IPv4 tunnel underlay, so the original weakness might reappear unnoticed. An IPv6-over-IPv4 tunnel depends on the IPv4 underlay that transports encapsulated packets; overlay route presence cannot replace underlay connectivity.

This is a useful guard against IPv6 neighbor discovery filtering, but it is not scoped to the observed IPv6 over IPv4 tunnel underlay failure. An appropriate test would show that both IPv4 endpoint paths are reachable and IPv6 packets traverse the encapsulated link end to end.

The intended LSP is admitted on a path satisfying its bandwidth constraints without oversubscribing reserved resources. That establishes RSVP path bandwidth admission rather than a repaired MSTP region consistency path. The reported failure still requires this evidence: adjacent devices report matching MST region configuration and VLANs map to the same intended instances.

This measurement tests RSTP alternate port reconvergence; it cannot distinguish success from failure for the observed MSTP region consistency condition. MSTP region identity depends on consistent name, revision, and VLAN mapping; mismatches create region boundaries.

Each VLAN's spanning-tree state selects its planned root and forwarding ports without creating a cross-VLAN loop. It would validate a separate VSTP per-VLAN root choice operation, not the change needed here. Confirm instead that adjacent devices report matching MST region configuration and VLANs map to the same intended instances.

Although BGP MED neighbor consideration needs this consideration, the failure at issue has a different cause. BGP import policy governs received routes and export policy governs outbound advertisements; changing the wrong direction cannot enforce the intended boundary.

An IPv6-over-IPv4 tunnel depends on the IPv4 underlay that transports encapsulated packets; overlay route presence cannot replace underlay connectivity. That describes IPv6 over IPv4 tunnel underlay, whereas the observed symptoms are caused by BGP import export control; it does not predict the reported behavior.

This principle matters when troubleshooting EBGP multihop reachability, but using it here mistakes a different failure mode for BGP import export control. The relevant distinction is: BGP import policy governs received routes and export policy governs outbound advertisements; changing the wrong direction cannot enforce the intended boundary.

Compare OSPF area IDs at both ends of every new inter-router link before production cutover. That ongoing check is for OSPF area identity mismatch; it would not reliably detect recurrence of provider bridging MTU overhead. Provider tag stacking adds frame overhead; an unchanged link MTU may reject frames that previously fitted untagged.

Validate tag behavior, allowed VLAN membership, and connected device expectations at port provisioning. That ongoing check is for VLAN access trunk distinction; it would not reliably detect recurrence of provider bridging MTU overhead. Provider tag stacking adds frame overhead; an unchanged link MTU may reject frames that previously fitted untagged.

Monitor high-frequency MAC moves and correlate them with spanning-tree and bridge-interface events. The monitored boundary differs from provider bridging MTU overhead, so the original weakness might reappear unnoticed. Provider tag stacking adds frame overhead; an unchanged link MTU may reject frames that previously fitted untagged.