Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Example: Configuring Data Center Interconnect with Bare Metal Server EVPN Type 5

This example describes how to interconnect data centers with bare metal server (BMS) EVPN type 5 and the Juniper Networks QFX5100 and QFX10002 line of switches.

Requirements

Table 1 lists the hardware and software components used in this example.

Table 1: Solution Hardware and Software Requirements

Device

Hardware

Software

Core Routers

MX480

Junos OS Release 14.2R2.8

Fabric Layer

QFX5100-24Q

Junos OS Release 14.1X53-D27.3

Spine Layer

QFX10002-78Q

Junos OS Release 14.1X53-D27.3

Leaf Devices

QFX5100-48S

Junos OS Release 14.1X53-D27.3

Route Server

QFX10002-78Q

Junos OS Release 14.1X53-D27.3

Servers

IBM Flex and IBMx3750

VMware ESXi 5.1

Overview and Topology

The topology used in this example consists of two MX480 devices as core routers; a series of QFX5100 and QFX10002 devices at the fabric, spine, and leaf layers; a QFX10002-78Q device as a router server; and various bare metal servers (BMS) in the server racks as shown in Figure 1.

Figure 1: BMS EVPN Type 5 Solution TopologyBMS EVPN Type 5 Solution Topology

In this example, the leaf layer uses four QFX5100-48S switches. The spine layer uses four QFX10002-78Q switches. The fabric layer uses four QFX5100-24Q switches. The core layer uses two MX480 routers. A series of servers are attached to the leaf layer to serve as typical data center end hosts.

Table 2 and Table 3 list the IP addressing used in this example.

Table 2: IPv4 Addressing

IPv4 Network Subnets

Network

Fabric to Spine point-to-point (PTP) links

110.100.1.0/24, 110.100.2.0/24,110.100.3.0/24, 110.100.4.0/24

Spine to Leaf PTP links

101.1.0.0/16

Loopback IP range for all VRFs

101.1/16

Inet.0 for route-server

100.100.101.1/24

TOR-1 IRB

1.1.0.0/16

TOR-2 IRB

2.2.0.0/16

TOR-3 IRB

3.3.0.0/16

TOR-4 IRB

4.4.0.0/16

Route server IP addresses

100.100.250.1 and 100.100.250.2

Table 3: IPv6 Addressing

IPv6 Network Subnets

Network

Spine to Leaf PTP links

::ffff.101.1.../127

Loopback IP range for all VRFs

::ffff:100.100.../127

TOR-1 IRB

1001:0:1::1/64

TOR-2 IRB

2001:0:1::1/64

TOR-3 IRB

3001:0:1::1/64

TOR-4 IRB

4001:0:1::1/64

Table 4 lists the AS numbering used in this example.

Table 4: BGP AS Numbering

Device

AS Number

TOR-1

65100

TOR-2

65100

TOR-3

65101

TOR-4

65101

Spine-1

65200

Spine-2

65200

Spine-3

65201

Spine-4

65201

Fabric-1

65300

Fabric-2

65300

Fabric-3

65300

Fabric-4

65300

Configuration

To configure data center interconnect with BMS EVPN type 5, perform these tasks:

CLI Quick Configuration

Configuration Snippets of VRFs on Leaf Towards Spine

To quickly configure the additional elements for the leaf devices, enter the following configuration statements on each device:

Note:

The configuration shown here applies to device Leaf-0.

Leaf-0 Global Configuration

Leaf-0 ECMP Configuration

Leaf-0 BGP Policy Configuration

Customer-1 Leaf-to-Spine

Uplink 40G Configuration for VRF-lite1 (6 x uplinks to Spine1 and Spine2)

Customer Routing Instance Configuration (VRF-1)

####### Spine-2 6 X BGP sessions for multipath #####

####### Spine-1 6 X BGP sessions for multipath #####

VLAN Configuration for VRF-1 (5 VLANs per Customer VRF)

IRB Interface Configuration

Customer-2 Leaf-to-Spine

Uplink 40G Configuration for VRF-lite2 (6 x uplinks to Spine1 and Spine2)

Customer Routing Instance Configuration (VRF-2)

####### Spine-1 6 X BGP sessions for multipath #####

####### Spine-2 6 X BGP sessions for multipath #####

VLAN Configuration for VRF-2 (5 VLANs per Customer VRF)

IRB Interface Configuration (VRF-2)

Leaf-0 Port Configurtion for VRF_lite1 and VRF_lite2

Configure Interfaces Toward Fabric: Two Links to each of Four Fabrics

Configure eBGP Underlay Toward Fabric: Two Links to each of Four Fabrics

Configure eBGP Underlay for Reachability of the Route Servers

Configure EVPN Type-5 Route Server Peering

Configure Global BGP Policies

Configure EVPN Type-5 Import and Export VRF Policies

Configure EVPN Auto-RD and ECMP Load Balancing

Configure Interfaces Toward TORs for VRF_lite1

### Toward TOR-1 ###

### Toward TOR-2 ###

Configure Interfaces Toward TORs for VRF_lite2

### Toward TOR-1 ###

### Toward TOR-2 ###

Configure VRF_lite1 Routing Instances

########### EVPN Type-5-specific Configuration to Enable Type-5 ###

Configure VRF_lite1 Routing Instances

########### EVPN Type-5-specific Configuration to Enable Type-5 ###

Configure Interfaces for Fabric Toward Spine

Configure ECMP and Fast Reroute

Configure eBGP Underlay Toward POD1 Spines

Configure eBGP Underlay Toward POD2 Spines

Verification

Verifying eBPG Sessions to Spine-1 and Spine-2 for VRF_lite1

Purpose

The top of rack (TOR) switches establish eBGP sessions to Spine-1 and Spine-2 devices using VRF_lite1. This verifies that the sessions are active.

Action

Verify sessions for VRF_lite1:

Meaning

The eBPG sessions for VRF_lite1 are all established and functioning correctly.

Verifying eBPG Sessions to Spine-1 and Spine-2 for VRF_lite2

Purpose

The top of rack (TOR) switches establish eBGP sessions to Spine-1 and Spine-2 devices using VRF_lite2. This verifies that the sessions are active.

Action

Verify sessions for VRF_lite2:

Meaning

The eBPG sessions for VRF_lite2 are all established and functioning correctly.

Verify the Type-5 Inter-pod Routes Received from TOR-3 on TOR-1 for VRF-lite1

Purpose

Each TOR switch must receive EVPN Type-5 inter-pod route information for VRF_lite1.This verifies that the information is present.

Action

Verify route information from TOR-3 for VRF_lite1:

Verify the Type-5 Inter-pod Forwarding Table Information Received from TOR-3 on TOR-1 for VRF-lite1

Purpose

Each TOR switch must receive EVPN Type-5 inter-pod forwarding table information for VRF_lite1.This verifies that the information is present.

Action

Verify forwarding table information from TOR-3 for VRF_lite1:

Verify the Type-5 Inter-pod Routes Received from TOR-2 on TOR-1 for VRF-lite1

Purpose

Each TOR switch must receive EVPN Type-5 inter-pod route information for VRF_lite1. This verifies that the information is present.

Action

Verify route information from TOR-2 for VRF_lite1:

Verify the Type-5 Inter-pod Forwarding Table Information Received from TOR-2 on TOR-1 for VRF-lite1

Purpose

Each TOR switch must receive EVPN Type-5 inter-pod forwarding table information for VRF_lite1.This verifies that the information is present.

Action

Verify forwarding table information from TOR-2 for VRF_lite1:

Verify the Type-5 Inter-pod Routes Received from TOR-3 on TOR-1 for VRF-lite2

Purpose

Each TOR switch must receive EVPN Type-5 inter-pod route information for VRF_lite2.This verifies that the information is present.

Action

Verify route information from TOR-3 for VRF_lite2:

Verify the Type-5 Inter-pod Forwarding Table Information Received from TOR-3 on TOR-1 for VRF-lite2

Purpose

Each TOR switch must receive EVPN Type-5 inter-pod forwarding table information for VRF_lite2.This verifies that the information is present.

Action

Verify forwarding table information from TOR-3 for VRF_lite2:

Verify the Type-5 Inter-pod Routes Received from TOR-2 on TOR-1 for VRF-lite2

Purpose

Each TOR switch must receive EVPN Type-5 inter-pod route information for VRF_lite2. This verifies that the information is present.

Action

Verify route information from TOR-2 for VRF_lite2:

Verify the Type-5 Inter-pod Forwarding Table Information Received from TOR-2 on TOR-1 for VRF-lite2

Purpose

Each TOR switch must receive EVPN Type-5 inter-pod forwarding table information for VRF_lite2. This verifies that the information is present.

Action

Verify forwarding table information from TOR-2 for VRF_lite2:

Verify Traffic Load Balancing

Purpose

Multiple paths exist between devices and it is most efficient to load balance among the operational links. This step verifies the process.

Action

Verify forwarding table information from TOR-2 for VRF_lite2:

Verify SPINE-1 eBGP Session Toward the Route Server

Purpose

The eBGP underlay must establish sessions to the route server. This step verifies the process.

Action

Verify eBGP Toward Route Server:

Verify SPINE-1 eBGP Session Toward the Route Server

Purpose

The eBGP underlay must establish sessions to the route server. This step verifies the process.

Action

Verify eBGP Toward Route Server:

Verify SPINE-1 eBGP Session Toward Fabric Devices with IPv6 Tunneling over IPv4

Purpose

The eBGP underlay must establish sessions fabric devices. This step verifies the process.

Action

Verify eBGP Toward Fabric:

Verify SPINE-1 VRF_lite1 (Customer 1) BGP Sessions Toward TOR

Purpose

The BGP sessions for VRF_lite1 must be up toward the TOR. This step verifies the process.

Action

Verify BGP for VRF_lite1Toward TOR:

Verify SPINE-1 VRF_lite2 (Customer 2) BGP Sessions Toward TOR

Purpose

The BGP sessions for VRF_lite2 must be up toward the TOR. This step verifies the process.

Action

Verify BGP for VRF_lite2Toward TOR:

Verify SPINE-1 EVPN Type 5 Route Learned from TOR-3 with VXLAN Information

Purpose

The Spine-1 device must learn EVPN Type 5 routes from TOR-3 (inter-pod) containing VXLAN infommation. This step verifies the process.

Action

Verify EVPN Type 5 route learned from TOR-3 with VXLAN information:

Verify SPINE-1 EVPN Type 5 Forwarding Table Next-Hop Type for VRF_Lite1

Purpose

The EVPN Type 5 Forwarding Table Next-Hop Type with Unilist with Comp Next-Hops. This step verifies the process.

Action

Verify EVPN Type 5 forwarding table next-hop:

Verify SPINE-1 EVPN Type-5 Routes Learned from TOR-2 with Inet only (no VXLAN info )

Purpose

The Spine-1 device must learn EVPN Type 5 routes from TOR-2 (inter-pod) without VXLAN information. This step verifies the process.

Action

Verify EVPN Type 5 route learned from TOR-2 without VXLAN information:

Verify SPINE-1 Intra-pod Route to TOR-2 Uses Unicast Next-Hop

Purpose

The Spine-1 Intrapod Route to TOR-2 Must Use the Unicast Next-Hop. This step verifies the process.

Action

Verify the Spine-1 intrapod route to TOR-2 uses unicast next-hop:

Verify Fabric-1 Interfaces

Purpose

The Fabric-1 Intrapod interfaces must be configured properly. This step verifies the process.

Action

Verify the cloud-Fabric-sw01 interfaces are configured properly:

Verify Fabric-1 BGP Sessions

Purpose

The Fabric-1 BGP sessions must be configured properly. This step verifies the process.

Action

Verify the cloud-Fabric-sw01 BGP sessions:

Verify BGP Scaling on TOR-3

Purpose

The TOR-3 BGP sessions must be configured properly and appear and TOR-3. This step verifies the process.

Action

Verify the TOR-4 BGP sessions:

Verify Fabric-1 BGP Sessions

Purpose

The Fabric-1 BGP sessions must be configured properly. This step verifies the process.

Action

Verify the cloud-Fabric-sw01 BGP sessions:

Verify BGP Scaling on SPINE-1

Purpose

The SPINE-1 BGP sessions must be configured properly. This step verifies the process.

Action

Verify the SPINE-1 BGP sessions: