Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation

Solutions

Featured solutions AI Campus and branch Data center WAN Security Service provider Cloud operator Industries
Campus and Branch

Welcome to the NOW Way to Wi-Fi

Take your networking performance to new heights with a modern, cloud-native, AI-Native architecture. Only Juniper can help you unleash the full potential of Wi-Fi 7 with our AI-Native platform for innovation.
Prepare for liftoff
Business intelligence analyst dashboard on virtual screen. Big data Graphs Charts.

AI Data Center Networking

Juniper’s AI data center solution is a quick way to deploy high performing AI training and inference networks that are the most flexible to design and easiest to manage with limited IT resources.
Find out more
Enterprise AI-Native Networking

Enterprise AI‑Native Routing

Juniper's Ai-Native routing solution delivers robust 400GbE and 800GbE capabilities for unmatched performance, reliability, and sustainability at scale.
Explore enterprise routing
Zero trust security

Ops4AI Lab

Visit our lab in Sunnyvale, CA and see our AI data center solution for yourself. You can try out your own model’s functionality and performance, too.
Visit the lab
Enterprise AI-Native Networking

Enterprise AI‑Native Routing

Juniper's Ai-Native routing solution delivers robust 400GbE and 800GbE capabilities for unmatched performance, reliability, and sustainability at scale.
Explore enterprise routing
Higher Education

Shaping Student Experiences: The NOW Way to Build Higher Education Networks

Join Juniper Networks CIO Sharon Mandell and a virtual summit of C-level IT leaders from prestigious institutions as they discuss ongoing efforts to support digital transformation.
Register to attend
Hand on tablet with healthcare overlay of graphics

Security in healthcare

In this IDC Spotlight report, discover how AI networking can automate and strengthen a healthcare ecosystem to defeat criminals and prevent loss. 
Gain insights into ecosystem security
Retail

The Future of In-Store Technologies

Join us for an enlightening webinar with Kevin McCartan, Senior IT Service Delivery Engineer at Musgrave; retail guru Jack Stratten of Insider Trends; and Christian Gilby, Director of Product Marketing at Juniper Networks, as they discuss the future of in-store technologies.
Reserve my spot

Products

Wireless access Wired access SD-WAN / SASE Routing and switching Security Mist AI™ Management software Network operating system Blueprint for AI-Native Acceleration Optics
  • Operations
ACX7020 router

Juniper ACX7020 Cloud Metro Access Router

Legacy networks simply cannot meet the demands of today’s rapidly evolving metro landscape. Unlock a new generation of highly scalable architectures and automated operations with the Juniper ACX7020. 
Learn more
EX4000 Ethernet Switch

Next-gen AI-Native EX4000 line of switches

Lack of AI innovation from your current networking vendor slowing you down? Embrace Juniper’s cloud-native, AI-Native access switches that support every level and layer, across nearly every deployment.
Discover how
The Q and AI text with an image of Bob Friday and Kedar Dhuru.

The Q&AI Podcast

Delivering practical solutions and enriching discussions, this podcast series is a vital resource for those seeking an in-depth exploration of AI's transformative potential.
Catch the latest episode

Services

Services
Services AI Care

Juniper AI Care Services Revolutionize Your Service Experience

Our industry-first AI-Native services couple AIOps with our deep expertise across the full network life cycle. You can move from reactive response to proactive insight and action.
Explore AI Care Services
Services AI Data Center

Juniper AI Data Center Deployment Services Optimize Your AI Model Runs

We use our expertise and validated designs to help design, deploy, validate and tune networks, including GPUs and storage, to get the most from your AI infrastructure operation.
Learn about AI Data Center Deployment Services

Partners

Partners

Support and Documentation

Support and Documentation

Learn

About Juniper Training Events The Feed Resources Technology learning topics Thought leadership and insights
Audience raising hands up while businessman is speaking in training at the office.

Juniper certification and training news

See the latest
Ringing of the bell

All global events

See the latest
AI-native-now

AI-Native NOW event series

Register now
Juniper's Christina Hendrix at the head of a conference table. With the text "The NOW Way to Network" overlayed, with "NOW" emphasizing the "O" in green color.

The NOW Way to Network

Watch the video series
AI Native Now

Executive insights

Dive deep with leading experts and thought leaders on all the topics that matter most to your business, from AI to network security to driving rapid, relevant transformation for your business.
Learn more
A keynote speaker giving a presentation at a conference. There are dozens of people sitting around them. The presentation is displayed via projector on all the walls in the room.

Leadership voices

Juniper Networks’ leaders operate on the front lines of creating the network of the future. Take a look around to see what’s on their minds.
Watch now
Bob Friday and Jessica Garrison speaking

Bob Friday Talks

Join Bob as he ventures into all the knowns -- and -- unknowns -- of AI.
Catch the latest episode
Documentation
Menu
License Guide
Quick Starts
Validated Designs
Home Documentation
QFX5120Data Center
QFX5120 Collapsed Spine with EVPN Multihoming Example: How to Configure a Collapsed Spine Data Center Architecture With EVPN Multihoming

Collapsed Spine with EVPN Multihoming

keyboard_arrow_up
close
keyboard_arrow_left
Collapsed Spine with EVPN Multihoming
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
ON THIS PAGE
keyboard_arrow_right

Optional Configurations: DHCP Relay and Multicast

date_range 19-Dec-24
arrow_backward
arrow_forward

Use these examples to configure optional DHCP relay and multicast forwarding on your collapsed spine data center architecture.

Configure DHCP Relay (Optional)

Requirements

Overview

Use this section to configure the spine switches to relay the DHCP requests to the DHCP server. Enable DHCP relay in a routing instance with the forward-only option. The forward-only option ensures that DHCP packets are forwarded on the switch but that no DHCP server client bindings are created.

Topology

The DHCP server can be located anywhere in the data center or in a different data center. In this case, the DHCP server is connected to one of the ToR switches in DC1 and the IP address of the DHCP server is 192.168.201.10. The DHCP relay topology is shown in Figure 1.

Figure 1: DHCP Relay TopologyDHCP Relay Topology

Configuration

Configure Spine 1

Step-by-Step Procedure

  1. Configure the DHCP relay on the first routing instance.

    content_copy zoom_out_map
    set routing-instances JNPR_1_VRF forwarding-options dhcp-relay forward-only
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay server-group Server_Group1 192.168.201.10
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay group Relay_Group1 active-server-group Server_Group1
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay group Relay_Group1 route-suppression destination
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay group Relay_Group1 interface irb.201
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay group Relay_Group1 interface irb.202
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay group Relay_Group1 interface irb.203

  2. Configure the DHCP relay on the second routing instance.

    content_copy zoom_out_map
    set routing-instances JNPR_2_VRF forwarding-options dhcp-relay forward-only
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay server-group Server_Group1 192.168.201.10
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay group Relay_Group1 active-server-group Server_Group1
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay group Relay_Group1 route-suppression destination
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay group Relay_Group1 interface irb.211
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay group Relay_Group1 interface irb.212
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay group Relay_Group1 interface irb.213

  3. Verify the DHCP relay on Spine 1.

    content_copy zoom_out_map
    user@spine1> show dhcp relay statistics routing-instance JNPR_1_VRF
Packets dropped:
    Total                      50741
    Invalid server address     0
    dhcp-service total         50738

Messages received:
    BOOTREQUEST                3
    DHCPDECLINE                0
    DHCPDISCOVER               1
    DHCPINFORM                 0
    DHCPRELEASE                0
    DHCPREQUEST                2
    DHCPLEASEACTIVE            0
    DHCPLEASEUNASSIGNED        0
    DHCPLEASEUNKNOWN           0
    DHCPLEASEQUERYDONE         0

Messages sent:
    BOOTREPLY                  2
    DHCPOFFER                  0
    DHCPACK                    2
    DHCPNAK                    0
    DHCPFORCERENEW             0
    DHCPLEASEQUERY             0
    DHCPBULKLEASEQUERY         0

Configure Spine 2

Step-by-Step Procedure

  1. Configure the DHCP relay on the first routing instance.

    content_copy zoom_out_map
    set routing-instances JNPR_1_VRF forwarding-options dhcp-relay forward-only
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay forward-only-replies
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay server-group Server_Group1 192.168.201.10
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay group Relay_Group1 active-server-group Server_Group1
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay group Relay_Group1 route-suppression destination
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay group Relay_Group1 interface irb.201
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay group Relay_Group1 interface irb.202
set routing-instances JNPR_1_VRF forwarding-options dhcp-relay group Relay_Group1 interface irb.203

  2. Configure the DHCP relay on the second routing instance.

    content_copy zoom_out_map
    set routing-instances JNPR_2_VRF forwarding-options dhcp-relay forward-only
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay forward-only-replies
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay server-group Server_Group1 192.168.201.10
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay group Relay_Group1 active-server-group Server_Group1
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay group Relay_Group1 route-suppression destination
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay group Relay_Group1 interface irb.211
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay group Relay_Group1 interface irb.212
set routing-instances JNPR_2_VRF forwarding-options dhcp-relay group Relay_Group1 interface irb.213

  3. Verify the DHCP relay on Spine 2.

    content_copy zoom_out_map
    user@spine2> show dhcp relay statistics routing-instance JNPR_1_VRF
Packets dropped:
    Total                      50741
    Invalid server address     0
    dhcp-service total         50738

Messages received:
    BOOTREQUEST                3
    DHCPDECLINE                0
    DHCPDISCOVER               1
    DHCPINFORM                 0
    DHCPRELEASE                0
    DHCPREQUEST                2
    DHCPLEASEACTIVE            0
    DHCPLEASEUNASSIGNED        0
    DHCPLEASEUNKNOWN           0
    DHCPLEASEQUERYDONE         0

Messages sent:
    BOOTREPLY                  2
    DHCPOFFER                  0
    DHCPACK                    2
    DHCPNAK                    0
    DHCPFORCERENEW             0
    DHCPLEASEQUERY             0
    DHCPBULKLEASEQUERY         0

Configure Multicast for Intra-VNI Traffic (Optional)

Requirements

Overview

Use this section to configure your collapsed spine architecture to allow intra-VNI multicast traffic. The multicast source and receivers are part of the same VLAN.

Note:

The collapsed spine architecture with QFX5120 spine switches does not support inter-VNI multicast traffic.

Topology

This section includes the configuration for two multicast groups. The first is multicast group 224.0.0.66. As shown in Figure 2, the multicast source is Endpoint 62. The multicast receiver, Endpoint 61, is connected to ToR 2. Both the source and receiver are in the same VLAN, so traffic between them is intra-VNI multicast traffic.

Figure 2: Multicast Group 224.0.0.66 Topology
Topology

Configuration

Configure Devices

Step-by-Step Procedure

  1. Enable IGMP snooping for all VLANs on both spine switches.

    content_copy zoom_out_map
    set protocols igmp-snooping vlan VLAN-201 immediate-leave
set protocols igmp-snooping vlan VLAN-202 immediate-leave
set protocols igmp-snooping vlan VLAN-211 immediate-leave
set protocols igmp-snooping vlan VLAN-212 immediate-leave

  2. Configure the ToR switches with IGMP snooping for all VLANs.

    content_copy zoom_out_map
    set protocols igmp-snooping vlan VLAN-201 immediate-leave
set protocols igmp-snooping vlan VLAN-201 interface ae1.0 multicast-router-interface
set protocols igmp-snooping vlan VLAN-202 immediate-leave
set protocols igmp-snooping vlan VLAN-202 interface ae1.0 multicast-router-interface
set protocols igmp-snooping vlan VLAN-211 immediate-leave
set protocols igmp-snooping vlan VLAN-211 interface ae1.0 multicast-router-interface 
set protocols igmp-snooping vlan VLAN-212 immediate-leave
set protocols igmp-snooping vlan VLAN-212 interface ae1.0 multicast-router-interface

Verification for Multicast Group 224.0.0.66

Step-by-Step Procedure

  1. Verify IGMP snooping membership on ToR 2.

    content_copy zoom_out_map
    user@tor2> show igmp snooping membership
Instance: default-switch

Vlan: VLAN-201

Learning-Domain: default
Interface: ae1.0, Groups: 0

Vlan: VLAN-202

Learning-Domain: default
Interface: ae1.0, Groups: 0

Learning-Domain: default
Interface: xe-0/2/2.0, Groups: 1
    Group: 225.0.0.66
        Group mode: Exclude
        Source: 0.0.0.0
        Last reported by: 192.168.202.61
        Group timeout:     177 Type: Dynamic

Vlan: VLAN-211

Learning-Domain: default
Interface: ae1.0, Groups: 0

Vlan: VLAN-212

Learning-Domain: default
Interface: ae1.0, Groups: 0

  2. Verify IGMP snooping membership on Spine 1.

    content_copy zoom_out_map
    user@spine1> show igmp snooping evpn membership detail
Instance: default-switch

Vlan: VLAN-201, EVPN-Core-NH: 524301

Learning-Domain: default
Interface: ae2.0, Groups: 0
Interface: ae1.0, Groups: 0

Vlan: VLAN-202, EVPN-Core-NH: 524303

Learning-Domain: default
Interface: ae2.0, Groups: 1
    Group: 225.0.0.66
        Group mode: Exclude
        Source: 0.0.0.0
        Type: Local
Interface: ae1.0, Groups: 0

Vlan: VLAN-211, EVPN-Core-NH: 524307

Learning-Domain: default
Interface: ae2.0, Groups: 0
Interface: ae1.0, Groups: 0

Vlan: VLAN-212, EVPN-Core-NH: 524298

Learning-Domain: default
Interface: ae2.0, Groups: 0
Interface: ae1.0, Groups: 0

  3. Verify IGMP snooping membership on Spine 2.

    content_copy zoom_out_map
    user@spine2> show igmp snooping evpn membership detail
Instance: default-switch

Vlan: VLAN-201, EVPN-Core-NH: 524298

Learning-Domain: default
Interface: ae2.0, Groups: 0
Interface: ae1.0, Groups: 0

Vlan: VLAN-202, EVPN-Core-NH: 524300

Learning-Domain: default
Interface: ae2.0, Groups: 1
    Group: 225.0.0.66
        Group mode: Exclude
        Source: 0.0.0.0
        Type: Remote
Interface: ae1.0, Groups: 0

Vlan: VLAN-211, EVPN-Core-NH: 524304

Learning-Domain: default
Interface: ae2.0, Groups: 0
Interface: ae1.0, Groups: 0

Vlan: VLAN-212, EVPN-Core-NH: 524306

Learning-Domain: default
Interface: ae2.0, Groups: 0
Interface: ae1.0, Groups: 0

  4. Verify the designated forwarder on Spine 1. The output shows that Spine 1 is the designated forwarder for all Ethernet segments.

    content_copy zoom_out_map
    user@spine1> show evpn instance designated-forwarder
Instance: default-switch
  Number of ethernet segments: 12
    ESI: 00:00:00:00:00:00:00:00:01:01
      Designated forwarder: 192.168.255.13
    ESI: 00:00:00:00:00:00:00:00:01:02
      Designated forwarder: 192.168.255.13
    ESI: 00:00:00:00:00:00:00:00:01:11
      Designated forwarder: 192.168.255.13
    ESI: 00:00:00:00:00:00:00:00:01:12
      Designated forwarder: 192.168.255.13

  5. Verify the multicast traffic flow on Spine 1.

    Based on LAG hashing, ToR 1 sends the multicast traffic to Spine 1. The traffic reaches Spine 1 on the AE1 interface. Spine 1 forwards this traffic through AE2 based on IGMP group membership.

    content_copy zoom_out_map
    user@spine1> monitor interface traffic detail
Interface    Link  Input packets        (pps)     Output packets        (pps)
ae1           Up     6742041146    (2946565)             3924          (1)
ae2           Up           2536          (0)       6741411465    (2948357)

  6. Verify the multicast traffic flow on Spine 2.

    Based on LAG hashing, ToR 1 does not send the multicast traffic to Spine 2. Spine 2 receives this traffic from Spine 1 through the overlay, but it drops this traffic and does not forward it to AE2.

    content_copy zoom_out_map
    user@spine2> monitor interface traffic detail
Interface    Link  Input packets        (pps)     Output packets        (pps)
ae1           Up           2547          (0)             3762          (1)
ae2           Up           2462          (0)             3769          (1)

Verification for Multicast Group 224.0.0.65

Step-by-Step Procedure

  1. Verify the designated forwarder on Spine 1. The output shows that Spine 1 is still the designated forwarder for all the Ethernet segments.

    content_copy zoom_out_map
    user@spine1> show evpn instance designated-forwarder
Instance: default-switch
  Number of ethernet segments: 12
    ESI: 00:00:00:00:00:00:00:00:01:01
      Designated forwarder: 192.168.255.13
    ESI: 00:00:00:00:00:00:00:00:01:02
      Designated forwarder: 192.168.255.13
    ESI: 00:00:00:00:00:00:00:00:01:11
      Designated forwarder: 192.168.255.13
    ESI: 00:00:00:00:00:00:00:00:01:12
      Designated forwarder: 192.168.255.13

  2. Verify the multicast traffic flow on Spine 1.

    Based on LAG hashing, ToR 1 does not send the multicast traffic to Spine 1, so there is no incoming traffic for this multicast group on Spine 1. Spine 1 receives the multicast stream from Spine 2 through the overlay. Spine 1 drops the traffic and does not forward it to AE2 because Spine 1 and Spine 2 are part of the same Ethernet segments for AE1 and AE2.

    content_copy zoom_out_map
    user@spine1> monitor interface traffic detail
Interface    Link  Input packets        (pps)     Output packets        (pps)
et-0/0/51     Up           4750    (2947862)             4741          (3)
ae1           Up           1027          (1)             1543          (1)
ae2           Up            991          (0)             1537          (1)

  3. Verify the multicast traffic flow on Spine 2.

    Based on LAG hashing, ToR 1 sends the multicast traffic to Spine 2. Spine 2 is not the designated forwarder for the Ethernet segments, but Spine 2 still forwards this traffic to receivers on AE2 based on the local bias rules for multicast forwarding. See Overview of Selective Multicast Forwarding for more information about the EVPN multicast forwarding rules.

    content_copy zoom_out_map
    user@spine2> monitor interface traffic detail
Interface    Link  Input packets        (pps)     Output packets        (pps)
et-0/0/51     Up           4603          (3)       3458201844    (2948641)
ae1           Up     2985999842    (2948821)             1542          (1)
ae2           Up           1009          (0)       2986000009    (2947024)

    You have successfully configured multicast traffic forwarding on your network.

arrow_backward PREVIOUS Advanced Security and Data Center Interconnect Configurations
NEXT arrow_forward
footer-navigation

© 1999 - 2025 Juniper Networks, Inc. All rights reserved.

Scroll to top