Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Data Center Fabric Reference Design Testing Summary

 

Table 1 summarizes the hardware and software components tested in the Data Center Fabric validated topology. It is provided for reference purposes only.

For a summary of hardware and software combinations that can be used to create this architecture, see Hardware and Software Summary.

Table 1: Data Center Fabric Reference Design Hardware and Software Summary

Device

Hardware

Interfaces

Software

Spine Devices

Three QFX10002 switches, one QFX10016 switch

See Spine Device Interface Summary.

Junos OS Release 17.3R1-S1 or later

Leaf Devices

QFX5100 switches (Leaf 2 and Leaf 3)

QFX5100 Virtual Chassis (up to 10 member switches - Leaf 1)

QFX5110 switches (Leaf 4 - Leaf 6)

QFX5200 switches (Leaf 7- Leaf 9)

QFX10002 switches (Leaf 10 - Leaf 12)

Additional virtual devices used as leaf devices for scalability testing

See Leaf Device Interface Summary.

Junos OS Release 17.3R1-S1 or later

You can configure QFX5100 switches as a Virtual Chassis, and then use the Virtual Chassis as a leaf device in an overlay. This option enables you to provide more access ports for your leaf devices. The configuration for Leaf 1 in a VLAN-aware centrally-routed bridging overlay in a default instance is included here for reference purposes.

Configure leaf device switches as a Virtual Chassis.

  1. (Optional) Configure Leaf 1 as a Virtual Chassis.Note

    This step is applicable only for Leaf 1 and shows that you can have a leaf device that consists of multiple switches bundled as a Virtual Chassis. In this case, Leaf 1 is the only Virtual Chassis in the example topology but could be extrapolated in your data center based on your needs.

    Leaf 1:

  2. In operational command mode, enable the VCP ports for the Virtual Chassis.

For more information about configuring a Virtual Chassis for QFX5100 switches, see: Configuring a QFX Series Virtual Chassis. For more information about the centrally-routed bridging overlay service model, see: Configuring a VLAN-Aware Centrally-Routed Bridging Overlay in the Default Instance.