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

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

In EVPN PE-CE routing, the PE exchanges ordinary IPv4 or IPv6 unicast routing information with the CE. When the PE learns CE prefixes, it imports them into the tenant IP-VRF and advertises them to other EVPN PEs as EVPN route type 5 IP Prefix routes. Conversely, when the PE receives EVPN routes from remote PEs, it can advertise corresponding IPv4/IPv6 BGP updates toward the CE, subject to policy. Import and export policies are essential because they control which customer routes are accepted, which EVPN-learned routes are advertised, and how attributes are modified. Option C is false because iBGP is not the preferred PE-CE model in this context. eBGP is typically preferred between PE and CE because it creates a clean administrative routing boundary between the provider/data-center edge and the customer or external router. Using eBGP also simplifies route policy, loop prevention, and operational separation. The CE does not need to participate in the EVPN overlay; it speaks standard BGP unicast with the PE, while the PE performs the EVPN RT-5 advertisement into the fabric. Reference: EVPN PE-CE BGP routing, eBGP preference, RT-5 prefix advertisement, import/export policy.

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

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

Designated Forwarder election determines which PE forwards BUM traffic from the EVPN overlay toward a multi-homed Ethernet Segment for a given service. In this scenario, all leaf routers share the same DF candidate list for mac-vrf103, but the election configuration is not identical. Leaf1 and Leaf2 use the default algorithm, while Leaf3 and Leaf4 use the preference-based algorithm. Under preference-based DF election, the candidate with the highest configured preference is selected over lower-preference candidates, assuming the candidate list is valid and consistent. The question states that Leaf3 has the higher preference value compared with Leaf4. Therefore, Leaf3 becomes the DF for mac-vrf103. This is the correct outcome because the preference-based election explicitly overrides simple default behavior by assigning operator-defined priority to a PE. In production designs, this is useful when the operator wants deterministic forwarding placement, maintenance control, or service-specific primary-path selection rather than relying only on the default modulo-based DF selection process. Reference: EVPN DF election, preference-based algorithm, MAC-VRF service forwarding.

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

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]:

When Leaf-1 receives an ARP request from Host-1, it learns the source MAC address in the local MAC table and learns the source IP/MAC binding in the proxy ARP table. For EVPN distribution, the relevant control-plane advertisement is an EVPN route type 2 MAC/IP advertisement containing Host-1's MAC and the actual host IP address, 192.168.100.1. This allows remote PEs to populate their EVPN-derived forwarding and proxy ARP state with the correct endpoint binding. Option A is false because advertising the host MAC with the IP address set to 0.0.0.0 does not represent the learned MAC/IP binding required for proxy ARP synchronization. A MAC-only RT-2 advertisement may exist in EVPN contexts, but the question specifically states that Leaf-1 has learned the MAC/IP binding through ARP and is distributing that information. Therefore, the valid advertisement must include the real host IP address. Remote PEs use the MAC/IP route to learn the endpoint, not an all-zero IP placeholder for this proxy ARP learning event. Reference: EVPN RT-2 MAC/IP advertisement, proxy ARP table population, endpoint synchronization.

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

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

In asymmetric EVPN IRB, the ingress PE performs routing from the source subnet into the destination subnet, then forwards the packet across the VXLAN overlay using the destination MAC-VRF/VNI. The egress PE does not perform another IP-VRF lookup for that packet; it performs Layer 2 forwarding in the destination MAC-VRF. In this scenario, Host-2 sends traffic toward Host-1. After the ingress routing decision, the traffic arrives at Leaf-2 in the context of the destination MAC-VRF, mac-vrf-1. Leaf-2 then performs a MAC lookup in mac-vrf-1 and forwards the frame to Host-1. Option D is therefore correct. Option A reverses the forwarding direction and misidentifies the leaf action. Option B incorrectly sends mac-vrf-2 traffic toward the IP-VRF on Leaf-2, even though Leaf-2 is acting as the egress PE for Host-1. Option C is also incorrect because the egress forwarding action is based on the MAC table in the destination MAC-VRF, not an IP-VRF ARP lookup at that stage. Reference: asymmetric L3 EVPN IRB data-plane operation, ingress routing and egress MAC forwarding.

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

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

In active-standby, or single-active, Layer 2 EVPN multi-homing, only one PE is active for the Ethernet Segment and MAC-VRF at a time. Leaf1 and Leaf2 participate in DF election, and the elected DF becomes the active forwarding PE for that service attachment. Because this is not all-active multi-homing, the non-DF must not forward traffic to the host for the protected service. This prevents duplicate frames, incorrect MAC learning, and loops on the access side. The DF accepts traffic from the host and forwards BUM traffic received from remote PEs toward the host-facing segment. Option D is false because it claims that the non-DF can forward unicast traffic from remote PEs to the host. In single-active operation, remote peers must direct traffic to the active PE, and the standby PE remains ready to take over only after DF state changes. This is the operational distinction from all-active multi-homing, where more than one PE may be used for forwarding depending on the traffic type and aliasing behavior. Reference: single-active L2 EVPN multi-homing, DF role, non-DF forwarding suppression.

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

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

An IRB interface is the logical connection point between a Layer 2 MAC-VRF and a Layer 3 IP-VRF. It provides the routed gateway function for hosts in the bridge domain while allowing traffic to move into the routed VRF for inter-subnet forwarding. The correct statement is that when an IRB sub-interface has multiple IP addresses, one can be designated as the primary. This is important because the primary address is used for normal gateway or subnet behavior when more than one address is present on the same routed interface context. Option A is inaccurate because the question is about an IRB sub-interface, not a generic subinterface selection between bridge or routed access modes. Option B is not the defining multi-homing model; EVPN multi-homing is implemented through Ethernet Segment association and MAC-VRF attachment behavior, not by adding multiple IRB subinterfaces for multi-homing. Option D is also wrong because the IRB is the shared logical link between the MAC-VRF and IP-VRF; the design does not require separate IRB subinterfaces on each side as independent constructs. Reference: SR Linux IRB configuration, MAC-VRF to IP-VRF interconnection, primary IP addressing.

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

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

MAC mobility is the EVPN mechanism used when a host MAC moves from one PE to another. The control plane uses a MAC Mobility extended community and sequence number behavior to determine the most recent valid location for the MAC. When a PE locally learns a MAC that was previously learned through EVPN, it advertises the MAC with an incremented sequence number, allowing remote PEs to prefer the newer location. Therefore, option B is wrong because the sequence number is not decremented. Option A is also wrong because the original PE does not advertise the locally learned MAC with a maximum sequence value as a normal mobility procedure. Option D is inaccurate because PEs do not need direct MAC table synchronization; they rely on EVPN control-plane advertisements and withdrawals. The true statement is option C: the originating PE generates a withdraw message after the same locally learned MAC ages out. This withdrawal removes stale reachability from remote PEs and prevents continued forwarding toward a PE that no longer has the host locally attached. Reference: EVPN MAC mobility, sequence-number handling, MAC route withdrawal after aging.

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

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

Aliasing is an EVPN multi-homing mechanism that allows remote PEs to send traffic to any eligible PE attached to the same Ethernet Segment, even if a specific MAC address was learned and advertised by only one of those PEs. This avoids a traffic bottleneck and enables load-sharing in all-active multi-homing designs. The route type used to implement this behavior is the Ethernet Auto-Discovery per EVI route, commonly referred to as AD per EVI. This route tells remote PEs that a given PE has reachability to a specific Ethernet Segment for a specific EVPN instance. When remote PEs receive these advertisements from multiple PEs for the same ESI and EVI, they can treat those PEs as valid next-hops for traffic toward that Ethernet Segment. Ethernet Segment routes support ES discovery and DF election, while IP/MAC routes advertise host MAC and optionally IP binding information. AD per ES routes are used for broader Ethernet Segment-level procedures, but aliasing at the service level relies on AD per EVI reachability. Reference: EVPN route type 1, AD per EVI, aliasing in all-active multi-homing.

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

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]:

A gateway-less DCI design extends the data center EVPN/VXLAN model across the WAN without a distinct gateway function separating the data center fabric from the WAN VPN edge. Because the leaf routers or route reflectors must establish the necessary EVPN control-plane and VXLAN data-plane reachability across data centers, the WAN must provide reachability for those fabric endpoints. This design can simplify service continuity and preserve the EVPN overlay model end-to-end, but it does not provide the clean security and QoS demarcation that exists in a decoupled gateway model. A clear demarcation between a border leaf and a separate gateway/WAN PE is specifically a property of decoupled gateway-based DCI, not gateway-less DCI. The gateway-less model also requires reachability between route reflectors or EVPN control-plane endpoints across sites. Therefore, option A is false because it incorrectly assigns the demarcation benefit to the gateway-less design. Reference: gateway-less DCI, stretched EVPN overlay, route-reflector and leaf reachability requirements.

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

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

An anycast-gateway IRB allows multiple PEs to present the same default-gateway IP address to hosts in the same subnet. This is the mechanism that enables distributed gateway behavior in EVPN fabrics. The same anycast gateway IP may be configured on equivalent IRB subinterfaces across remote PEs participating in the same IP-VRF, allowing hosts to use the nearest leaf as their default gateway without changing their gateway address. SR Linux also associates gateway MAC information with the IRB, including virtual gateway MAC behavior used inside the MAC-VRF forwarding table. Option C is false because the anycast gateway IP is not treated as a normal unique host route that appears in the IP-VRF route table alongside the subnet prefix. The subnet route is installed for the connected network, but the shared anycast gateway address is a gateway function, not a separately advertised host endpoint that should appear as ordinary routed host reachability. Treating the anycast IP as a regular host route would undermine the distributed gateway model and create ambiguous ownership across PEs. Reference: IRB anycast gateway, MAC-VRF/IP-VRF interconnection, distributed default-gateway operation.

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

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

In SR Linux BGP configuration, parameters defined at a more specific hierarchy level can override broader protocol-level settings. Therefore, if a `local-as` value is configured within the BGP group used for EVPN MP-BGP route-reflector sessions, that value overrides the AS number configured directly under the BGP protocol for that group's sessions. Option A is correct. Option B is false because the cluster ID is configured on the route reflector, not on every participating client. The cluster ID identifies the RR cluster and helps prevent route-reflection loops. Option C is false because redundant route reflectors normally operate in parallel rather than as strict primary/backup devices; clients can peer with both for resilience. Option D is misleading because EVPN route reflectors are used to avoid a full mesh of overlay MP-BGP EVPN sessions between leaves, not to replace ordinary underlay eBGP leaf-spine routing sessions. In a clean fabric design, the underlay provides IP reachability, while the EVPN overlay uses MP-BGP sessions, often via route reflectors, to distribute tenant reachability. Reference: SR Linux BGP hierarchy, EVPN route reflector sessions, local-AS override, cluster ID behavior.

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