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) is a modern framework for streaming telemetry data from a Junos device to an external collector. It uses a push model to provide high-frequency, granular data. JTI supports two primary transport protocols for exporting this data. The first is UDP, which provides a simple, connectionless method for streaming. The second, and more commonly used, is gRPC (Google Remote Procedure Call), a high-performance, open-source RPC framework that runs over TCP and provides a reliable, session-based transport for telemetry data.

A. REST (Representational State Transfer) is a pull-based architectural style for APIs, distinct from the push-based streaming model of JTI.

C. SNMP (Simple Network Management Protocol) is a legacy, pull-based protocol. JTI was developed as a modern, more scalable alternative to SNMP.

1. Juniper Networks TechLibrary. (2024). Junos Telemetry Interface User Guide. "Understanding the Junos Telemetry Interface". The overview section explicitly states, "The Junos Telemetry Interface supports two transport protocols to export data: User Datagram Protocol (UDP) and gRPC."

2. Juniper Networks TechLibrary. (2024). Junos OS API, Automation, and Telemetry Library. "Junos Telemetry Interface". This document describes the architecture and states, "Data can be streamed through either UDP or gRPC transport."

The scenario requires a Layer 3 Data Center Interconnect (DCI) because the IP spaces are unique and no Layer 2 bridging is needed. EVPN Type 5 routes (IP Prefix routes) are specifically designed for this purpose, advertising IP prefixes between data centers without requiring MAC address learning across the DCI. To exchange these Type 5 routes, the border leaf nodes (DCI gateways) in each data center must establish an EVPN peering session, typically over an eBGP session across the IP backbone. This allows for efficient and scalable L3 connectivity between the separate routing domains of the data centers.

A. Configure a Type 2 EVPN route for each unique prefix.

Incorrect. Type 2 routes are for MAC/IP advertisements and are used for Layer 2 extension, which is explicitly not required in this scenario.

D. Configure peering for EVPN between all leaf nodes within each data center.

Incorrect. This describes intra-data center peering for the fabric's underlay/overlay, not the inter-data center peering required for DCI.

1. Juniper Networks, "EVPN User Guide". Section: "EVPN-VXLAN DC Interconnect". This guide details DCI models, specifying that for L3-only interconnects, Type 5 routes are used to exchange IP prefixes between border leaf gateways.

2. Juniper Networks, "Technology Deep Dive: Seamless EVPN-VXLAN Data Center Interconnect" (White Paper, 2020). Section: "L3 DCI Gateway Models". This paper explains that Type 5 routes provide a clean and scalable method for extending L3 connectivity between data centers. It also illustrates the eBGP peering between DCI gateway devices.

3. RFC 7432, "BGP MPLS-Based Ethernet VPN". Section 9, "IP Prefix Advertisement". While the RFC covers MPLS, the principles of the EVPN route types are defined here. Type 5 is defined for advertising IP prefixes.

In an EVPN-VXLAN fabric, providing a redundant L3 gateway that conserves IP address space is achieved by implementing an anycast gateway. This involves configuring Integrated Routing and Bridging (IRB) interfaces on multiple PE devices with the exact same IP address and the same MAC address. This configuration makes the multiple physical gateways appear as a single logical gateway to the end hosts. Hosts send traffic to this single logical gateway, and the fabric routes it to the nearest physical PE, providing both redundancy and load balancing without consuming additional IP addresses from the subnet.

A. Using different MAC addresses for the same IP on different PEs would cause MAC address flapping on hosts and connected switches, leading to network instability.

B. A Virtual Gateway Address (VGA) is typically associated with VRRP. While VRRP can be used, the native EVPN anycast gateway feature (same IP/MAC) is more efficient and integrated.

D. Using different IP addresses defeats the purpose of conserving address space and providing a single, seamless default gateway to all hosts in the subnet.

1. Juniper Networks TechLibrary. (2023). Default Gateway in an EVPN-VXLAN Overlay Network. "To enable this feature, you configure the same gateway IP address and MAC address on the IRB interfaces of all the leaf devices that you want to participate in providing default gateway services." Retrieved from https://www.juniper.net/documentation/us/en/software/junos/evpn-vxlan/topics/concept/evpn-vxlan-default-gateway.html

2. Juniper Networks TechLibrary. (2023). Understanding EVPN with VXLAN Data Plane Encapsulation. In the section "Default Gateway," it describes using the same IP and MAC on IRB interfaces across leaf devices for anycast gateway functionality. Retrieved from https://www.juniper.net/documentation/us/en/software/junos/evpn-vxlan/topics/concept/evpn-vxlan-overview.html

The sFlow datagram sent from an agent (the network device) to a collector contains two main types of information: counter samples and flow samples. A flow sample includes the header of a sampled packet. This header contains Layer 2 information, such as source and destination VLAN tags, and Layer 3/4 information. The datagram also includes metadata about the sample itself, such as the agent's address and the specific input and output interface (ifIndex) through which the packet traversed the device.

B. the sending device's serial number: The sFlow agent is identified by its IP address in the datagram, not its hardware serial number.

C. the CRC from the sampled packet: The CRC (Frame Check Sequence) is a Layer 2 trailer field used for error checking and is typically stripped by the hardware before packet processing and sampling occur.

1. Juniper Networks TechLibrary. (2023). Understanding sFlow Technology. "The sFlow agent resides on the switch and packages the following into sFlow datagrams that are sent to the sFlow collector: ... A raw packet header (from the sampled packet). The header contains information such as...source and destination VLANs... The input and output interfaces for the sampled packet."

2. IETF RFC 3176. (September 2001). InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks. Section 3.4, "Flow Samples", describes the inclusion of the input and output interface numbers. Section 3.4.1, "Raw Packet Header", specifies that the beginning of the packet, including L2 headers, is captured.