3HE-21913-AAAA-TQZZA Issue 1 July 2025 © 2025 Nokia. Use subject to Terms available at: www.nokia.com/terms

Collapsed Spine EVPN VXLAN Nokia is committed to diversity and inclusion. We are continuously reviewing our customer documentation and consulting with standards bodies to ensure that terminology is inclusive and aligned with the industry. Our future customer documentation will be updated accordingly. This document includes Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia. This document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a product purchased or licensed...

Collapsed Spine EVPN VXLAN 2 Reference architecture overview 6 4.1 Underlay with IPv6 link-local addressing for point-to-point interfaces 6.3.7 Onboarding nodes in EDA with using a TopoNode Custom Resource .. 48 Use subject to Terms available at: www.nokia.com/terms

Use subject to Terms available at: www.nokia.com/terms

Collapsed Spine EVPN VXLAN Figure 7 Packet flow for Layer 2 tagged and untagged traffic using local bias Figure 8 Packet flow for Layer 2 tagged and untagged traffic exiting via a remote VTEP when local member interface of Ethernet segment is Figure 9 Packet flow between tagged or untagged interfaces across spines 14 Figure 13 Traffic flow for source behind ToR communicating with a destination behind single-active Ethernet segment when packet is hashed to Figure 14 Traffic flow for source behind ToR communicating with a destination behind single-active Ethernet segment when packet is hashed to...

Collapsed Spine EVPN VXLAN Executive summary Nokia Validated Designs (NVDs) is a workstream dedicated to producing validated recommendations to the consumer about Nokia’s portfolio across market segments. NVDs are accomplished with extensive requirement analysis from a multitude of customers along with deep research of the technology development in the industry segment to form the solution’s design. After the design has been compiled, it goes through an intense array of hardware, software, traffic, and failure tests to form the validated design. The resultant design and collateral provide the...

Collapsed Spine EVPN VXLAN This section describes the various components involved in this validated design and the design and technology choices that were made. In general, a collapsed spine design provides the following advantages: • reduction of the required number of devices and capacity of the devices in data centers where the scale-out and size of the data center are known to be limited and the main considerations become cost and power utilization • re-use of legacy Layer 2 switches (even Layer 2 switches of other vendors) as top of rack (ToR) switches in more modern data center designs...

Collapsed Spine EVPN VXLAN Layer 2 untagged interfaces two-way ES-based Link Aggregation Group (LAG) in all-active multihoming mode two-way ES-based LAG in single-active multihoming mode Layer 2 tagged interfaces Layer 3 point-to-point interfaces (exported as EVPN Type-5 routes into the fabric) High-level operational workflow Figure 2 shows a high-level operational workflow for the NVD-based fabric deployment and lifecycle management. The intent-based approach, combined with the prescriptive nature of the validated design and the flexibility of Nokia’s Event Driven Automation (EDA), makes the...

Collapsed Spine EVPN VXLAN • Because EDA as a platform does not need to be reinstalled for new patches or apps, it provides a high degree of flexibility and customizability for modern DC fabric needs. Figure 3 shows a high-level design of the fabric. The topology is a collapsed spine fabric with BGP EVPN as the control plane and VXLAN as the data plane encapsulation method with point-to-point layer 3 links between the two spines. These point-to-point interfaces are configured with IPv6-link local addressing (as shown in Figure 3), with each spine advertising its IPv4 loopback address with an...

Collapsed Spine EVPN VXLAN Figure 4 IPv4 systemO addresses advertised with an IPv6 next-hop Integrated routing and bridging (IRB) interfaces are configured on the spines using a distributed anycast gateway model. These IRB interfaces act as the default gateway for all servers in the fabric. Servers can connect either directly to the spines or to the ToR switches, depending on customer requirement. For routing between VNIs, this design uses an asymmetric routing model (as described in RFC 9135), along with symmetric routing using EVPN Type-5 routes for certain subnets (servers connected via Layer...

Table 1 Platform positioning Note: Alternate platforms can be positioned in the roles shown above based on cost, hardware, and performance requirements. July 2025 Issue 1 Use subject to Terms available at: www.nokia.com/terms

Collapsed Spine EVPN VXLAN Nokia data center portfolio Traffic patterns In this section, we describe common traffic patterns that are validated in the collapsed spine EVPN VXLAN NVD. These traffic patterns include forwarding across Layer 2 tagged and untagged interfaces (singlehomed and multihomed), Layer 3 interfaces, two-way all-active Ethernet segment LAG, and two-way single-active Ethernet segment LAG. Figure 7 and Figure 8 show traffic ingress on a single-homed interface and egress out of an Ethernet segment member interface (either local or remote). In Figure 7, when there is an interface...

VLAN 10-tagged VLAN 30 - tagged VLAN 100-L3 VLAN 10 - untagged VLAN 20 - tagged VLAN 100-L3 _ VLAN 10 - untagged VLAN 40 - tagged Figure 7 Packet flow for Layer 2 tagged and untagged traffic using local bias forwarding spine2 VLAN 10-tagged VLAN 30 - tagged VLAN 100-L3 £> spinel VLAN 10 - untagged VLAN 20 - tagged VLAN 100-L3 _ VLAN 10 - untagged VLAN 40 - tagged Figure 8 Packet flow for Layer 2 tagged and untagged traffic exiting via a remote VTEP when local member interface of Ethernet segment is down on ingress VTEP July 2025 Issue 1 Use subject to Terms available at: www.nokia.com/terms