Nokia 4A0-D03 - Nokia SR Linux EVPN and Data Center Interconnect

Comprehensive and Detailed 150 to 250 words of Explanation From [SR Linux EVPN and Data Center Interconnect/Course Guide/topics]:

VXLAN provides a Layer 2 overlay over a Layer 3 underlay by encapsulating Ethernet frames in UDP/IP. This allows tenant bridge domains to span a routed IP fabric without requiring the underlay itself to behave like one large Layer 2 network. VXLAN uses a 24-bit VXLAN Network Identifier, which supports approximately 16 million logical overlays, far exceeding the scale of traditional 12-bit VLAN IDs. Because the VXLAN underlay is IP-routed, traffic can benefit from ECMP across equal-cost paths, improving fabric utilization and resiliency. The false statement is B. VXLAN was not originally developed specifically to support EVPN. VXLAN began as a data-plane overlay encapsulation technology, while EVPN later became the preferred control plane for distributing MAC, MAC/IP, multicast, and prefix reachability in VXLAN-based fabrics. In modern data center design, EVPN and VXLAN are commonly paired: VXLAN supplies the encapsulation and VNI-based segmentation, while EVPN supplies scalable control-plane learning and signaling. Reference: VXLAN data plane, EVPN control plane, ECMP underlay, VNI-based tenant isolation.

================

Comprehensive and Detailed 150 to 250 words of Explanation From [SR Linux EVPN and Data Center Interconnect/Course Guide/topics]:

For Layer 2 data center interconnect using an integrated gateway, VPLS 100 on the Nokia 7750 SR represents the WAN-side Layer 2 VPN service. The VPLS requires an EVI because EVPN uses the EVI to identify the L2 service instance in the control plane. It also requires BGP EVPN signaling with the appropriate route targets so the local and remote service instances can import the correct EVPN routes. Because the service is transported across the WAN, the BGP/EVPN instance must be associated with the MPLS transport tunnels toward the remote gateway, dcgw20. A VXLAN instance with a VNI is not configured in the 7750 SR VPLS 100 for this integrated WAN gateway service. The VXLAN/VNI mapping is used inside the SR Linux data center fabric where MAC-VRF services are transported over VXLAN. On the WAN side, the VPLS service is carried using MPLS/EVPN mechanisms, not a VXLAN VNI configured directly under the VPLS. Reference: integrated gateway DCI, L2 EVPN/VPLS interworking, EVI and route-target operation.

================

Comprehensive and Detailed 150 to 250 words of Explanation From [SR Linux EVPN and Data Center Interconnect/Course Guide/topics]:

Ethernet Auto-Discovery per EVI information is used in EVPN multi-homing to advertise that a PE has reachability to a particular Ethernet Segment for a specific EVPN instance. Remote PEs use this information for aliasing, allowing them to forward known unicast traffic toward a multi-homed Ethernet Segment through eligible PEs rather than relying only on the PE that advertised a specific MAC route. In VXLAN-based EVPN, the update also carries information needed by remote peers to select the proper data-plane encapsulation and VNI for the service. The multi-homing behavior advertised with the Ethernet Segment enables remote peers to understand whether the attachment is operating in all-active or single-active mode. Option D is the false statement in this context because route-target handling is a general BGP EVPN import/export mechanism associated with VPN route policy and extended communities; it is not the specific operational function that defines AD per EVI behavior. The AD per EVI route's purpose is Ethernet Segment reachability for an EVI, not route-target-based service identification by itself. Reference: EVPN route type 1, AD per EVI, aliasing and multi-homing signaling.

================

Comprehensive and Detailed 150 to 250 words of Explanation From [SR Linux EVPN and Data Center Interconnect/Course Guide/topics]:

In asymmetric L3 EVPN routing, the ingress PE performs the routing decision and then sends traffic across the overlay in the context of the destination MAC-VRF. The egress PE performs Layer 2 MAC forwarding only toward the destination host. This is why options A and B correctly describe asymmetric data-plane behavior. Asymmetric routing relies heavily on EVPN route type 2 MAC/IP Advertisement routes because the ingress PE must know the destination host's MAC/IP binding and the destination bridge domain information. EVPN route type 5, which advertises IP prefixes, is a symmetric L3 EVPN mechanism and is not mandatory for asymmetric routing. Therefore, option C is false. Option D is treated as correct in this asymmetric-routing model because each PE participating in inter-subnet forwarding needs the destination MAC-VRF context to encapsulate traffic toward the correct L2 VNI. This requirement is one reason asymmetric routing scales less efficiently than symmetric routing: MAC-VRF presence and host reachability information must be broadly available. Symmetric routing improves scale by using an IP-VRF routed VXLAN interface and RT-5 prefix routes instead. Reference: asymmetric L3 EVPN routing, ingress IP/MAC forwarding, egress MAC forwarding, RT-2 versus RT-5 usage.

================

Comprehensive and Detailed 150 to 250 words of Explanation From [SR Linux EVPN and Data Center Interconnect/Course Guide/topics]:

In a decoupled gateway-based DCI design, the data center border leaf and the WAN PE are separate devices. Traffic between them can be identified using VLAN tags, allowing different data center EVPN services to be mapped to corresponding WAN VPN services. This architecture provides a clean operational boundary: the border leaf remains aligned with the data center EVPN/VXLAN fabric, while the WAN PE handles WAN VPN transport, QoS, security policy, and service interconnection. The separation gives a strong demarcation point for troubleshooting and administrative control. Option D is false because the WAN PE does not maintain an MP-BGP EVPN peering session with the data center route reflector. In the decoupled model, the route reflector remains part of the data center EVPN control plane, while the WAN PE exchanges routing or service information with the border leaf through the local handoff model. Direct WAN PE-to-data-center-RR peering would blur the separation that defines the decoupled design and would make the WAN PE part of the data center EVPN overlay control plane, which is not the intended architecture. Reference: decoupled gateway DCI, VLAN handoff, WAN VPN mapping, security/QoS demarcation, route-reflector separation.

================

Comprehensive and Detailed 150 to 250 words of Explanation From [SR Linux EVPN and Data Center Interconnect/Course Guide/topics]:

For Layer 2 all-active EVPN multi-homing on SR Linux, the Ethernet Segment configuration is the control-plane anchor that binds the redundant access attachment to EVPN. The relevant LAG subinterfaces must be associated with the Ethernet Segment so that the PE can advertise the segment correctly and apply split-horizon and aliasing behavior. The Ethernet Segment must also be administratively enabled; otherwise, the PE will not participate properly in ES discovery and DF procedures. The multi-homing mode must be set to all-active to permit forwarding through multiple attached leaf routers and support host-side LAG operation. The false statement is option B. The Ethernet Segment Identifier has a defined structure, and the blanket statement that the 2nd through 7th octets “must not be all zeros” is not a valid requirement as stated. What matters operationally is that the ESI uniquely identifies the same multi-homed Ethernet Segment across participating PEs and is consistently configured where required. The ESI must be non-zero as a meaningful segment identifier, but the specific octet restriction in the option is not the SR Linux all-active configuration rule. Reference: SR Linux L2 EVPN all-active multi-homing, Ethernet Segment configuration, LAG association.

================