JN0-683 Practice Questions

In a typical BGP-based IP fabric (Clos architecture), leaf and spine switches are directly connected. A single point-to-point EBGP session is established over each of these links, which is a simple and scalable design. If each device in the fabric uses a unique AS number (a common design choice), a leaf switch will learn routes to a given destination from multiple spines, each with a different AS path. To enable Equal-Cost Multi-Path (ECMP) and load-balance traffic across all spines, the multipath multiple-as statement is required on the leaf switches. This command allows BGP to consider paths through different autonomous systems as equal for multipathing.

A. If all leaf devices use the same AS, BGP loop prevention will cause routes to be dropped unless as-override or allow-as in is configured.

D. EBGP is the primary routing protocol used for reachability within the IP fabric (between leaf and spine nodes), not just for external connectivity.

1. Juniper Networks TechLibrary. (2024). EVPN-VXLAN Campus Architectures. "Configure BGP in the Core and Distribution Layers". The guide states, "To enable load balancing, include the multipath multiple-as statement... This statement allows the device to load-balance traffic across multiple BGP paths that are in different autonomous systems (ASs)."

2. Juniper Networks TechLibrary. (2024). BGP User Guide. "Examples: Configuring BGP for an IP Fabric". The examples consistently show a single EBGP session between directly connected leaf and spine peers and the use of multipath multiple-as for ECMP.

The fundamental operation of VXLAN is to extend Layer 2 segments over a Layer 3 network. The source VTEP (VXLAN Tunnel Endpoint) encapsulates the original Layer 2 Ethernet frame from a virtual or physical machine into a VXLAN header, which is then placed in a UDP/IP packet for transport. The VXLAN header contains a 24-bit VNI, but it does not contain a field for a VLAN ID. The original frame, including its VLAN tag (if present), is treated as the payload and is encapsulated in its entirety.

B. The VNI and VLAN ID are independent identifiers. While a VLAN is often mapped to a VNI, their numerical values do not need to match.

D. The VNI is a 24-bit value, which allows for up to 16,777,216 (2^24) unique segments, not a 16-bit value.

1. Juniper Networks Documentation, "Understanding VXLAN Encapsulation," EVPN Feature Guide. It states, "A VTEP encapsulates the Ethernet frame in a VXLAN, UDP, and IP header." and shows the packet format where the original L2 frame is the payload.

2. IETF RFC 7348, "Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks," Section 4, "Format of the VXLAN Header." This document defines the VNI as a 24-bit field and shows the encapsulation process where the "Inner MAC Frame" (the original L2 frame) is the payload.

3. Juniper Networks Documentation, "VXLAN Constraints on QFX Series and EX Series Switches," Feature Explorer. This document specifies, "VXLAN network identifier (VNI) — A 24-bit identifier that uniquely identifies a VXLAN."

In a Clos IP fabric the underlay routing is typically provided by EBGP sessions directly between physically connected leaf and spine switches; since EBGP distributes all required reachability, no separate IGP is needed. Each leaf switch therefore establishes an EBGP session to every spine (full-mesh leaf-to-spine); leaves do not peer with one another.

A. EBGP eliminates the need for an auxiliary IGP; adjacencies are formed directly.

D. Leaf-to-leaf EBGP sessions are unnecessary; communication is relayed through the spine layer.

1. Juniper Networks Day One “Building IP Fabrics with EBGP,” Chap. 3, “Leaf/Spine Peering Model,” pp. 23-25, 2021.

2. Juniper Networks TechLibrary, “EBGP IP Clos Fabric Design,” Section ‘Underlay Routing Overview’, para. 1-2, 2022.

In a multi-tenant environment using VRF instances, the Route Distinguisher (RD) is the property used to keep routing information for each tenant separate and unique. The RD is a 64-bit value that is prepended to each non-unique IPv4 or IPv6 prefix advertised by a tenant, creating a globally unique VPN-IP prefix. This allows multiple tenants to use the same overlapping IP address spaces without causing conflicts in the BGP control plane. The RD ensures that BGP can distinguish the routes belonging to one VRF from the identical routes of another VRF.

A. The VRF target community (Route Target) is a BGP extended community that controls the import and export of routes into and out of a VRF's routing table, effectively defining routing policy, not uniqueness.

B. The routing instance type (e.g., vrf) defines the characteristics and purpose of the routing table but does not, by itself, make the routes within it unique across the network.

C. The VRF table label is a forwarding-plane mechanism used in MPLS environments to direct traffic to the correct VRF on a PE router, not a control-plane mechanism for ensuring route uniqueness.

1. Juniper Networks Documentation. (2023). Understanding Route Distinguishers and VPN Route Targets. Junos OS, BGP User Guide. See the section "Route Distinguishers."

2. Juniper Networks Documentation. (2023). Configuring VRF Routing Instances. Junos OS, Routing Protocols and Policies Configuration Guide. See the section "route-distinguisher."

3. RFC 4364. (2006). BGP/MPLS IP Virtual Private Networks (VPNs). Section 4.2, "The VPN-IPv4 Address Family."

The Junos Telemetry Interface (JTI) provides multiple ways to stream data. For high-frequency (every five seconds) reporting of interface traffic statistics, native sensors are the most appropriate and efficient method. Native sensors are compiled into the Junos kernel and push data directly from the line card's forwarding ASIC, minimizing CPU impact on the Routing Engine. This push-based model is ideal for collecting granular, time-sensitive data like per-interface counters, as requested in the scenario. Using native sensors via UDP is the default and most performant method for this use case.

A. gNMI

gNMI is a transport protocol for telemetry, not the data source itself. It can be used to stream data from native sensors or OpenConfig models, but "Native Sensors" is the more specific answer.

B. SNMP

SNMP is a poll-based protocol. Polling every five seconds for numerous interfaces would create significant CPU load on the device and is less scalable and efficient than JTI's push model.

D. OpenConfig

OpenConfig provides standardized data models for telemetry. While it can be used to model interface statistics, "Native Sensors" refers to the high-performance, Junos-specific data source itself.

1. Juniper Networks Documentation, Junos Telemetry Interface User Guide, "Sensor Support". "Junos Telemetry Interface supports two sources for data: Native (Junos-specific) sensors... Native sensors export data for Junos-specific parameters, such as RPD statistics and forwarding engine statistics."

2. Juniper Networks Documentation, Junos Telemetry Interface User Guide, "Understanding the Junos Telemetry Interface". "For native sensors, data is streamed directly from the system software or hardware, such as the line card forwarding ASIC, to the collection server. This method results in more efficient delivery of telemetry data."

The VXLAN Network Identifier (VNI) provides the Layer 2 broadcast domain extension across the IP fabric. The VLAN ID is locally significant to each VTEP (leaf switch). Traffic from server1 enters leaf1 on VLAN 100, which is mapped to VNI 1000. The traffic is encapsulated and sent to leaf2. Leaf2 receives the packet for VNI 1000 and maps it to its locally configured VLAN, which is VLAN 200. The frame is then forwarded to server2 within the VLAN 200 broadcast domain.

A. Traffic will not be dropped on leaf2 because there is a valid mapping from VNI 1000 to VLAN 200, allowing the frame to be processed and forwarded.

B. Leaf2 maps VNI 1000 to its local VLAN 200, not VLAN 100. The VLAN ID from the ingress VTEP is not carried in the VXLAN header.

D. Traffic will not be dropped on leaf1 because it has a valid configuration to map VLAN 100 to VNI 1000 and encapsulate the traffic for the overlay.

1. Juniper Networks TechLibrary

"EVPN-VXLAN Reference Architecture"

Section: VLAN-Aware Service. "In a VLAN-aware service

each VLAN is mapped to its own VNI. However

the VLAN ID does not have to be the same on each VTEP. For example

you can have VLAN 100 mapped to VNI 1000 on one VTEP and VLAN 200 mapped to VNI 1000 on another VTEP."

2. Juniper Networks Day One+

"Data Center Fundamentals"

Chapter 4: EVPN-VXLAN

Section: VLAN-Aware Ethernet Service. "With a VLAN-aware service

you can use different VLAN identifiers on different Ethernet segments (VTEPs) and map them to the same VNI."

In an EVPN-VXLAN fabric, connectivity to external networks is provided by a border gateway function. This function can reside on the spine devices (in a centrally-routed bridging model) or on dedicated leaf devices, known as border leaf devices (in an edge-routed bridging model). A collapsed fabric architecture is a common spine-leaf design where placing the border gateway function on specific border leaf devices is a valid and frequently used implementation pattern for external connectivity.

A. Inter-spine links are not used in a standard Clos-based spine-leaf fabric topology, which aims for non-blocking, predictable performance between leaf devices.

C. Using Virtual Chassis (VC) at the leaf layer is generally not recommended for high resiliency as it creates a single control plane, making it a single point of failure. ESI-LAG is preferred.

B. EVPN-VXLAN is a standards-based technology that supports multi-vendor interoperability; there is no requirement that all spine devices must be from a single vendor.

1. Juniper Networks. (2021). Data Center Fabric Design and Implementation Guide. "Border Gateway Routing," p. 21. This guide discusses the role of border leaf devices for connecting the data center to the outside world.

2. Juniper Networks. (2023). EVPN-VXLAN Campus Architectures. "Core-Distribution Layer," p. 10. Describes collapsed core designs where border gateway functions are integrated.

3. Juniper Networks. (2023). EVPN Multihoming Overview. This document explains that ESI-LAG provides higher resiliency than MC-LAG or Virtual Chassis in data center fabrics.

In an IP fabric using EBGP between leaf and spine devices, a route advertised from one leaf to a spine and then to another leaf will be rejected by the second leaf. This is due to the standard BGP loop prevention mechanism, where a router discards routes that contain its own Autonomous System (AS) number in the ASPATH. To resolve this, you can either configure as-override on the spine devices, which replaces the originating leaf's AS with its own, or configure loops (e.g., loops 2) on the leaf devices to permit them to accept routes containing their own AS in the path.

B. A next-hop self policy is used to change the BGP next-hop attribute, typically for IBGP peering, and does not address the ASPATH loop prevention issue.

D. The multipath multiple-as command enables ECMP load balancing across paths with different AS numbers but does not fix the underlying problem of the route being hidden due to loop prevention.

1. Juniper Networks Documentation, "Example: Configuring a BGP IP Fabric," Data Center Fabric Design and Implementation Guide. This guide explicitly states, "To allow the leaf devices to install routes advertised from other leaf devices, you must configure either the as-override statement on the spine devices or the loops statement on the leaf devices."

2. Juniper Networks Documentation, "as-override (Protocols BGP)," BGP Feature Guide. The documentation explains that as-override allows a provider edge (PE) device to "change the AS number of the customer edge (CE) device with its own AS number."

3. Juniper Networks Documentation, "loops (Protocols BGP)," BGP Feature Guide. This document describes the loops statement as a way to "detect routing loops by checking the AS path for the local AS number" and allowing a route to be accepted if the AS number appears fewer times than the configured value.

For Zero Touch Provisioning (ZTP) to provide a unique configuration to each of the 100 devices, the DHCP server must be able to uniquely identify each device and assign it specific network parameters. The server's configuration file will contain a static mapping for each device, using the device's hardware MAC address as the unique identifier. This mapping assigns a specific management IP address to that MAC address, along with other DHCP options like the location of the configuration file. Therefore, the MAC address and the intended management IP for each device are essential components to configure on the DHCP server.

A. The IP address of the FTP server is a necessary DHCP option, but the MAC and IP address are the core components for uniquely identifying and addressing each switch.

C. The MAC address of the FTP server is irrelevant; network communication to the server uses its IP address, not its MAC address, across network segments.

1. Juniper Networks TechLibrary. (2023). Software Installation and Upgrade Guide. "Understanding Zero Touch Provisioning". The documentation shows a sample dhcpd.conf file where each device entry is defined by a host block containing hardware ethernet ; and fixed-address ;.

2. Juniper Networks Day One+. (2021). Zero Touch Provisioning (ZTP). "DHCP Server Configuration". This guide explicitly states, "The DHCP server needs to be configured with the MAC address of the device and the IP address that should be assigned to the device." (Chapter 3).

To convert a VXLAN Layer 2 gateway to a Layer 3 gateway, you must enable routing for the VNI. This is achieved by associating an Integrated Routing and Bridging (IRB) interface with the bridge domain that corresponds to the VNI. The command set bridge-domains routing-interface irb. performs this association. This configuration links the Layer 2 forwarding domain (the bridge-domain) to a Layer 3 routing interface (the IRB), allowing the router to perform routing for traffic arriving in that VNI.

A. This command enables ISIS on the IRB interface. While the IRB may participate in a routing protocol, this command does not create the essential link between the L2 bridge-domain and the L3 interface.

B. This command uses the vlans stanza. While functionally similar, modern EVPN-VXLAN configurations on MX Series typically use the bridge-domains stanza for service-provider style configurations.

D. This command enables OSPF on the IRB interface. This is for exchanging routing information with other routers, not for enabling the L3 gateway function for the VNI itself.

1. Juniper Networks Documentation. (2023). Configuring a VXLAN Layer 3 Gateway. Junos OS, Feature Guides. See the section "Configuring a VXLAN Layer 3 Gateway," Step 5.

2. Juniper Networks Documentation. (2023). Example: Configuring a Centrally-Routed Bridging Overlay. Junos OS, Feature Guides. This example shows the use of set bridge-domains VLAN-100 routing-interface irb.100.

3. Juniper Networks Documentation. (2023). routing-interface (Bridge Domain). Junos OS, Routing Protocols and Policies Command Reference.