Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in
the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks
are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right
to change, modify, transfer, or otherwise revise this publication without notice.
The information in this document is current as of the date on the title page.
ii
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related
limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with)
Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement
(“EULA”) posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you
agree to the terms and conditions of that EULA.
Table of Contents
1
About the Documentation | xi
Documentation and Release Notes | xi
Using the Examples in This Manual | xi
Merging a Full Example | xii
Merging a Snippet | xiii
Documentation Conventions | xiii
Documentation Feedback | xvi
Requesting Technical Support | xvi
Self-Help Online Tools and Resources | xvii
Creating a Service Request with JTAC | xvii
iii
Overview
QFX5100 System Overview | 19
QFX5100 Device Hardware Overview | 19
QFX5100 Hardware | 19
System Software | 28
QFX5100 Device Models | 28
Understanding Hardware Redundancy of QFX5100 Device Components and Functionality | 31
Field-Replaceable Units in a QFX5100 Device | 32
QFX5100 Chassis Description and Port Panels | 33
Chassis Physical Specifications for a QFX5100 Device | 34
Port Panel of a QFX5100-24Q Device | 34
Switch Ports | 35
QFabric Systems | 36
Channelizing Interfaces (Non-QFabric) | 36
Virtual Chassis and Virtual Chassis Fabric | 37
Port LEDs | 38
Port Panel of a QFX5100-24Q-AA Device | 39
Port Panel of QFX5100-48S and QFX5100-48SH Devices | 39
Port Panel of QFX5100-48T and QFX5100-48TH Devices | 42
Port Panel of a QFX5100-96S Device | 44
Switch Ports | 44
Channelizing Interfaces | 45
Virtual Chassis and Virtual Chassis Fabric Support | 46
Expansion Modules for QFX5100 Devices | 47
EX4600-EM-8F | 47
QFX-EM-4Q | 49
QFX-PFA-4Q | 50
Access Port and Uplink Port LEDs on a QFX5100 Device | 51
QFX5100 Management Panel | 55
Management Panel of a QFX5100 Device | 55
Management Port LEDs on a QFX5100 Device | 59
Chassis Status LEDs on a QFX5100 Device | 60
iv
QFX5100 Power System | 64
AC Power Supply for a QFX5100 Device | 64
AC Power Specifications for a QFX5100 Device | 67
AC Power Cord Specifications for a QFX5100 Device | 68
AC Power Supply LEDs on a QFX5100 Device | 69
DC Power Supply in a QFX5100 Device | 70
DC Power Specifications for a QFX5100 Device | 72
DC Power Supply LEDs on a QFX5100 Device | 73
QFX5100 Cooling System | 75
Cooling System and Airflow in a QFX5100 Device | 75
Fan Modules | 76
Do Not Install Components with Different Airflow or Wattage in the Switch | 80
Fan Module Status | 81
Fan Module LED on a QFX5100 Device | 82
Clearance Requirements for Airflow and Hardware Maintenance for a QFX5100 Device | 83
Site Planning, Preparation, and Specifications
2
Site Preparation Checklist for a QFX5100 Device | 86
QFX5100 Site Guidelines and Requirements | 88
Environmental Requirements and Specifications for a QFX5100 Device | 88
General Site Guidelines | 90
Site Electrical Wiring Guidelines | 90
Grounding Cable and Lug Specifications for a QFX5100 Device | 91
Rack Requirements for a QFX5100 Device | 92
Cabinet Requirements for a QFX5100 Device | 94
Plan a Virtual Chassis Fabric Deployment | 95
QFX5100 Network Cable and Transceiver Planning | 98
Determining Interface Support for the QFX5100 Device | 98
v
Cable Specifications for QSFP+ and QSFP28 Transceivers | 101
Understanding QFX Series Fiber-Optic Cable Signal Loss, Attenuation, and Dispersion | 103
Signal Loss in Multimode and Single-Mode Fiber-Optic Cables | 103
Attenuation and Dispersion in Fiber-Optic Cable | 104
Calculating Power Budget and Power Margin for Fiber-Optic Cables | 104
How to Calculate Power Budget for Fiber-Optic Cable | 105
How to Calculate Power Margin for Fiber-Optic Cable | 105
QFX5100 Cable and Pinout Specifications | 107
Cable Specifications for Console and Management Connections for the QFX Series | 107
RJ-45 Management Port Connector Pinout Information | 108
Console Port Connector Pinouts for the QFX Series | 109
Copper Cable Specifications for QFX5100-48T and QFX5100-48TH Switches | 109
Register Products—Mandatory to Validate SLAs | 119
Mount a QFX5100 Device in a Rack or Cabinet | 120
Before You Begin Rack Installation | 120
Four-Post Procedure | 122
Connect the QFX5100 to External Devices | 124
vi
Connect a Device to a Network for Out-of-Band Management | 124
Connect a Device to a Management Console Using an RJ-45 Connector | 125
Connect the QFX5100 in a Virtual Chassis or Virtual Chassis Fabric | 127
Connecting QFX Series and EX Series Switches in a QFX Virtual Chassis | 127
Before You Start | 127
Valid Configurations | 128
Cabling QFX3500 Switches in a QFX5100 Virtual Chassis | 129
Cabling QFX3600 Switches in a QFX Virtual Chassis | 131
Cabling a Mixed QFX Virtual Chassis | 132
Connecting a QFX5100 Device in a Virtual Chassis Fabric | 134
Connect the QFX5100 to Power | 137
Connecting Earth Ground to a QFX5100 Device | 138
Connecting AC Power to a QFX5100 Device | 139
Connecting DC Power to a QFX5100 Device | 142
Configure a QFX5100 Device | 148
Configuring a QFX5100 for Junos OS | 148
Configuring QFX10000 Switches for QFX5100-SH and QFX5100-TH as Satellite Devices | 150
Maintaining Components
4
5
Install and Remove QFX5100 Fan Modules | 154
Installing a Fan Module in a QFX5100 Device | 154
Removing a Fan Module from a QFX5100 Device | 155
Install and Remove QFX5100 Power Supplies | 157
Installing a Power Supply in a QFX5100 Device | 158
Removing a Power Supply from a QFX5100 Device | 159
Install and Remove Expansion Modules in a QFX5100-Device | 161
Installing an Expansion Module in a QFX5100 Device | 162
Removing an Expansion Module from a QFX5100 Device | 165
Install and Remove Transceivers and Fiber Optic Cables on QFX5100 Devices | 168
Install a Transceiver | 168
vii
Remove a Transceiver | 171
Connect a Fiber-Optic Cable | 174
Disconnect a Fiber-Optic Cable | 175
How to Handle Fiber-Optic Cables | 176
Power Off a QFX5100 Device | 177
Remove a QFX5100 Device | 180
Installing and Removing QFX5100 Device Hardware Components | 180
Powering Off an Existing QFabric Node Device | 181
Removing a QFX5100 Device from a Rack or Cabinet | 183
Troubleshooting Hardware
Troubleshoot the QFX5100 Device | 187
Alarm Types and Severity Levels | 187
Interface Alarm Messages | 188
Chassis Alarm Messages | 189
Creating an Emergency Boot Device for QFX Series Switches | 194
Recovering the Installation Using an Emergency Boot Device | 196
Contacting Customer Support and Returning the Chassis or Components
6
7
Contact Customer Support to Obtain Return Material Authorization | 199
Return the QFX5100 Chassis or Components | 200
Locating the Serial Number on a QFX5100 Device or Component | 200
Listing the Chassis and Component Details Using the CLI | 201
Locating the Chassis Serial Number ID Label on a QFX5100 Switch | 201
Locating the Serial Number ID Labels on FRU Components | 203
How to Return a Hardware Component to Juniper Networks, Inc. | 203
Guidelines for Packing Hardware Components for Shipment | 204
Safety and Compliance Information
General Safety Guidelines and Warnings | 208
Definitions of Safety Warning Levels | 209
viii
Qualified Personnel Warning | 212
Warning Statement for Norway and Sweden | 213
Fire Safety Requirements | 213
Fire Suppression | 213
Fire Suppression Equipment | 213
Installation Instructions Warning | 215
Chassis and Component Lifting Guidelines | 215
Restricted Access Warning | 217
Ramp Warning | 219
Rack-Mounting and Cabinet-Mounting Warnings | 220
Grounded Equipment Warning | 226
Laser and LED Safety Guidelines and Warnings | 227
General Laser Safety Guidelines | 227
Class 1 Laser Product Warning | 228
Class 1 LED Product Warning | 229
Laser Beam Warning | 230
Radiation from Open Port Apertures Warning | 231
Maintenance and Operational Safety Guidelines and Warnings | 232
Battery Handling Warning | 233
Jewelry Removal Warning | 234
Lightning Activity Warning | 236
Operating Temperature Warning | 237
Product Disposal Warning | 239
General Electrical Safety Guidelines and Warnings | 240
Action to Take After an Electrical Accident | 241
Prevention of Electrostatic Discharge Damage | 242
AC Power Electrical Safety Guidelines | 243
ix
AC Power Disconnection Warning | 245
DC Power Electrical Safety Guidelines | 246
DC Power Copper Conductors Warning | 247
DC Power Disconnection Warning | 248
DC Power Grounding Requirements and Warning | 250
DC Power Wiring Sequence Warning | 252
DC Power Wiring Terminations Warning | 255
Multiple Power Supplies Disconnection Warning | 258
Agency Approvals for the QFX Series | 258
Compliance Statements for EMC Requirements for the QFX Series | 260
Canada | 260
European Community | 261
Israel | 261
Japan | 262
Korea | 262
Taiwan | 262
United States | 263
Nonregulatory Environmental Standards | 263
Statements of Volatility for Juniper Network Devices | 264
TN Power Warning | 267
x
About the Documentation
IN THIS SECTION
Documentation and Release Notes | xi
Using the Examples in This Manual | xi
Documentation Conventions | xiii
Documentation Feedback | xvi
Requesting Technical Support | xvi
Use this guide to plan, install, perform initial software configuration, perform routine maintenance, and to
troubleshoot QFX5100 switches.
xi
After completing the installation and basic configuration procedures covered in this guide, refer to the
Junos OS documentation for further software configuration.
Documentation and Release Notes
To obtain the most current version of all Juniper Networks®technical documentation, see the product
documentation page on the Juniper Networks website at https://www.juniper.net/documentation/.
If the information in the latest release notes differs from the information in the documentation, follow the
product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts.
These books go beyond the technical documentation to explore the nuances of network architecture,
deployment, and administration. The current list can be viewed at https://www.juniper.net/books.
Using the Examples in This Manual
If you want to use the examples in this manual, you can use the load merge or the load merge relative
command. These commands cause the software to merge the incoming configuration into the current
candidate configuration. The example does not become active until you commit the candidate configuration.
If the example configuration contains the top level of the hierarchy (or multiple hierarchies), the example
is a full example. In this case, use the load merge command.
If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In
this case, use the load merge relative command. These procedures are described in the following sections.
Merging a Full Example
To merge a full example, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration example into a text file, save the
file with a name, and copy the file to a directory on your routing platform.
For example, copy the following configuration to a file and name the file ex-script.conf. Copy the
ex-script.conf file to the /var/tmp directory on your routing platform.
system {
scripts {
commit {
file ex-script.xsl;
}
}
}
interfaces {
fxp0 {
disable;
unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
}
xii
2. Merge the contents of the file into your routing platform configuration by issuing the load merge
configuration mode command:
1. From the HTML or PDF version of the manual, copy a configuration snippet into a text file, save the
file with a name, and copy the file to a directory on your routing platform.
For example, copy the following snippet to a file and name the file ex-script-snippet.conf. Copy the
ex-script-snippet.conf file to the /var/tmp directory on your routing platform.
commit {
file ex-script-snippet.xsl; }
2. Move to the hierarchy level that is relevant for this snippet by issuing the following configuration mode
command:
[edit]
user@host# edit system scripts
[edit system scripts]
xiii
3. Merge the contents of the file into your routing platform configuration by issuing the load merge
relative configuration mode command:
[edit system scripts]
user@host# load merge relative /var/tmp/ex-script-snippet.conf
load complete
For more information about the load command, see CLI Explorer.
Documentation Conventions
Table 1 on page xiv defines notice icons used in this guide.
Table 1: Notice Icons
xiv
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Caution
Indicates a situation that might result in loss of data or hardware
damage.
Alerts you to the risk of personal injury or death.Warning
Alerts you to the risk of personal injury from a laser.Laser warning
Indicates helpful information.Tip
Alerts you to a recommended use or implementation.Best practice
Table 2 on page xiv defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
ExamplesDescriptionConvention
Fixed-width text like this
Italic text like this
Represents text that you type.Bold text like this
Represents output that appears on
the terminal screen.
Introduces or emphasizes important
•
new terms.
Identifies guide names.
•
Identifies RFC and Internet draft
•
titles.
To enter configuration mode, type
the configure command:
user@host> configure
user@host> show chassis alarms
No alarms currently active
A policy term is a named structure
•
that defines match conditions and
actions.
Junos OS CLI User Guide
•
RFC 1997, BGP Communities
•
Attribute
Table 2: Text and Syntax Conventions (continued)
xv
ExamplesDescriptionConvention
Italic text like this
Text like this
< > (angle brackets)
| (pipe symbol)
Represents variables (options for
which you substitute a value) in
commands or configuration
statements.
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy
levels; or labels on routing platform
components.
variables.
Indicates a choice between the
mutually exclusive keywords or
variables on either side of the symbol.
The set of choices is often enclosed
in parentheses for clarity.
Configure the machine’s domain
name:
[edit]
root@# set system domain-name
domain-name
To configure a stub area, include
•
the stub statement at the [edit
protocols ospf area area-id]
hierarchy level.
The console port is labeled
•
CONSOLE.
stub <default-metric metric>;Encloses optional keywords or
broadcast | multicast
(string1 | string2 | string3)
# (pound sign)
[ ] (square brackets)
Indention and braces ( { } )
; (semicolon)
GUI Conventions
Indicates a comment specified on the
same line as the configuration
statement to which it applies.
Encloses a variable for which you can
substitute one or more values.
Identifies a level in the configuration
hierarchy.
Identifies a leaf statement at a
configuration hierarchy level.
rsvp { # Required for dynamic MPLS
only
community name members [
community-ids ]
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Table 2: Text and Syntax Conventions (continued)
xvi
ExamplesDescriptionConvention
Bold text like this
> (bold right angle bracket)
Represents graphical user interface
(GUI) items you click or select.
Separates levels in a hierarchy of
menu selections.
In the Logical Interfaces box, select
•
All Interfaces.
To cancel the configuration, click
•
Cancel.
In the configuration editor hierarchy,
select Protocols>Ospf.
Documentation Feedback
We encourage you to provide feedback so that we can improve our documentation. You can use either
of the following methods:
Online feedback system—Click TechLibrary Feedback, on the lower right of any page on the Juniper
•
Networks TechLibrary site, and do one of the following:
Click the thumbs-up icon if the information on the page was helpful to you.
•
Click the thumbs-down icon if the information on the page was not helpful to you or if you have
•
suggestions for improvement, and use the pop-up form to provide feedback.
E-mail—Send your comments to techpubs-comments@juniper.net. Include the document or topic name,
•
URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC).
If you are a customer with an active Juniper Care or Partner Support Services support contract, or are
covered under warranty, and need post-sales technical support, you can access our tools and resources
online or open a case with JTAC.
JTAC policies—For a complete understanding of our JTAC procedures and policies, review the JTAC User
•
Guide located at https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week,
•
365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called
the Customer Support Center (CSC) that provides you with the following features:
Understanding Hardware Redundancy of QFX5100 Device Components and Functionality | 31
Field-Replaceable Units in a QFX5100 Device | 32
QFX5100 Device Hardware Overview
19
IN THIS SECTION
QFX5100 Hardware | 19
System Software | 28
The QFX5100 line of 10/40GbE switches delivers low latency, flexible deployment options, and rich
automation features. QFX5100 Switches build a strong underlay foundation for flexible, high-performance,
standards-based fabrics and routing that improve network reliability and agility.
QFX5100 Hardware
QFX5100 line of switches offer two compact 1 U models and a 2 U model that provide wire-speed packet
performance, very low latency, and rich set of Layer 2 and Layer 3 features. In addition to a high-throughput
Packet Forwarding Engine, the performance of the control plane running on all the QFX5100 switches is
enhanced by the 1.5 Ghz dual-core Intel CPU with 8 GB of memory and 32 GB of solid-state drive (SSD)
storage.
The QFX5100-24Q-AA switch has a 2.5 GHz 4-core Intel CPU with 32 GB of memory and 128 GB of SSD
storage.
The QFX5100 line of switches include both 10GE and 40GE fixed-configurations:
QFX5100-48S
•
As shown in Figure 1 on page 20, the QFX5100-48S is a 10-Gigabit Ethernet Enhanced Small Form-Factor
Pluggable (SFP+) top-of-rack switch with 48 SFP+ ports and 6 Quad SFP+ (QSFP+) ports. Each SFP+
port can operate as a native 10 Gigabit port, when 10 Gbps optics are used. The SFP+ ports can also
run at 1 Gbps, or at 100 Mbps speeds when 1_Gigabit optics are inserted. Each QSFP+ port (48 through
53) can operate as uplink ports or four QSFP+ port (50 through 53) can operate at native 40-Gigabit
speed or as 4 independent 10-Gigabit port speeds. The 6 QSFP+ ports can be used as either access
ports or as uplinks. The QFX5100-48S provides full duplex throughput of 1.44 Tbps. The QFX5100-48S
has a 1 U form factor and comes standard with redundant fans and redundant power supplies. The switch
can be ordered with either ports-to-FRUs or FRUs-to-ports airflow and with AC or DC power supplies.
Figure 1: QFX5100-48S Port Panel
20
The QFX5100-48S can be used as:
A standalone switch.
•
A Node device in a QFabric system.
•
The QFX5100-48S is supported on both the QFX3000-G and QFX3000-M QFabric systems.
A primary, backup, or line card in a QFX Virtual Chassis.
•
A QFX Virtual Chassis allows you to interconnect up to 10 QFX3500, QFX3600, or QFX5100 switches
into one logical device and manage the device as a single chassis using a ring topology.
A line card in a QFX5110 Virtual Chassis.
•
A QFX5110 Virtual Chassis must have a QFX5110-32Q as the primary. Only QFX5110 and select
models of QFX5100 can participate in a QFX5110 Virtual Chassis.
A spine or leaf device in a standard QFX5100 Virtual Chassis Fabric (VCF).
•
VCF uses Virtual Chassis technology to interconnect multiple devices into a single logical device and
manage that device as a single logical device inside of a fabric architecture. VCF architecture supports
up to 20 total devices in a spine and leaf topology. Out of the 20 total devices, you can configure a
maximum of 4 spine devices.
A QFX5100 VCF uses QFX5100 devices as spines or leaf devices. You can also use QFX3500, QFX3600,
and EX4300 models as leaf devices in a QFX5100 VCF.
Whenever possible, configure the QFX5100-24Q as the spine device in a QFX5100 VCF. You can use
the QFX5100-48S as the spine in an all QFX5100-48S VCF or when EX4300 devices are used as leaf
devices.
A leaf device in a QFX5110 VCF.
•
A QFX5110 VCF must have a minimum of two QFX5110-32Q as spine devices. Junos OS Release
17.3R1 or later is required for QFX5110 VCF.
A satellite device in a Junos Fusion system.
•
Junos OS Release 14.2.3 or later is required for Junos Fusion.
QFX5100-48SH
•
As shown in Figure 2 on page 21, the QFX5100-48SH is the same form factor and port configuration
as the QFX5100-48S. The QFX5100-48SH is specifically designed for Junos Fusion and comes
pre-configured with Satellite Network Operational System (SNOS) instead of Juniper Networks Junos
OS. The switch may not be converted to Junos OS without an additional license. The switch can be
ordered with either ports-to-FRUs or FRUs-to-ports airflow and with AC power supplies.
The QFX5100-48SH can only be used as a satellite device in a Junos Fusion system.
Figure 2: QFX5100-48SH Port Panel
21
QFX5100-48T
•
As shown in Figure 3 on page 21, the QFX5100-48T is a tri-speed 100/1000/10GBASE-T top-of-rack
switch with 48 10GBASE-T access ports and 6 QSFP+ ports. Each 40-Gigabit QSFP+ port (48 through
53) can operate either as uplink ports or four QSFP+ ports (50 through 53) can operate at native
40-Gigabit port or be channelized into 4 independent 10 Gigabit ports. The 6 QSFP+ ports can be used
as either access ports or as uplinks. The QFX5100-48T provides full duplex throughput of 720 Gbps.
The QFX5100-48T has a 1 U form factor and comes standard with redundant fans and redundant power
supplies. The switch can be ordered with either ports-to-FRUs or FRUs-to-ports airflow and with AC or
DC power supplies.
Figure 3: QFX5100-48T Port Panel
The QFX5100-48T can be used as:
A standalone switch.
•
A Node device in a QFabric system.
•
The QFX5100-48T is supported on both the QFX3000-G and QFX3000-M QFabric systems.
A primary, backup, or line card in a QFX Virtual Chassis.
•
A QFX Series Virtual Chassis allows you to interconnect up to ten QFX5100, QFX3500, or QFX3600,
switches into one logical device and manage the device as a single chassis using a ring topology.
A line card in a QFX5110 Virtual Chassis.
•
You can configure up to ten QFX5110 and QFX5100 switches into one logical device and manage the
device as a single chassis using a ring topology. In a QFX5110 Virtual Chassis, configure QFX5110-32Q
as the primary and backup. Junos OS Release 17.3R2 or later is required on all members for QFX5110
VCF with QFX5100-48T leaf devices.
A leaf device in a standard QFX5100 Virtual Chassis Fabric (VCF).
•
VCF uses Virtual Chassis technology to interconnect multiple devices into a single logical device and
manage that device as a single logical device inside of a fabric architecture. VCF architecture supports
up to 20 total devices in a spine and leaf topology. Of those 20 devices, four QFX5100 devices can
be configured as spine devices.
22
In a QFX5100 VCF, the QFX5100-48T is always a leaf device and a QFX5100-24Q is the spine device.
A leaf device in a QFX5110 VCF.
•
A QFX5110 VCF must have a minimum of two QFX5110-32Q as spine devices. Junos OS Release
17.3R2 or later is required on all VCF devices for QFX5100-48T leaf devices to operate in a QFX5110
VCF.
A satellite device in a Junos Fusion system.
•
Junos OS Release 14.2.3 or later is required for Junos Fusion.
QFX5100-48TH
•
As shown in Figure 4 on page 23, the QFX5100-48TH is the same form factor and port configuration
as the QFX5100-48T. The QFX5100-48TH is specifically designed for Junos Fusion and comes
pre-configured with Satellite Network Operational System (SNOS) instead of Juniper Networks Junos
OS. The switch may not be converted to Junos OS without an additional license. The switch can be
ordered with either ports-to-FRUs or FRUs-to-ports airflow and with AC power supplies.
The QFX5100-48TH can only be used as a satellite device in a Junos Fusion system.
Figure 4: QFX5100-48THPort Panel
QFX5100-24Q
•
As shown in Figure 5 on page 23, the QFX5100-24Q is a 40-Gigabit Ethernet QSFP+ switch with 24
high-density QSFP+ ports. Each QSFP+ port can operate as a native 40 Gbps port or as 4 independent
10 Gbps ports. The QFX5100-24Q switch has a 1 U form factor and comes standard with redundant
fans and redundant power supplies. The switch can be ordered with either ports-to-FRUs or FRUs-to-ports
airflow and with AC or DC power supplies.
The QFX5100-24Q switch has two module bays for the optional expansion module, QFX-EM-4Q, which
can add a total of 8 additional QSFP+ ports to the chassis. When operating as a standalone switch and
fully populated with QFX-EM-4Q Expansion Modules, the QFX5100-24Q switch is equivalent to 80
10 Gbps interfaces and 4 40-Gbps interfaces. Of these total ports, 104 logical ports are available for
10G port channelization. For full details on the different port channelization modes, see “Port Panel of
a QFX5100-24Q Device” on page 34. All ports on the QFX5100-24Q and QFX-EM-4Q can be configured
as either access ports or as uplinks. The QFX5100-24Q switch provides full duplex throughput of 2.56
Tbps.
23
Figure 5: QFX5100-24Q Port Panel
The QFX5100-24Q can be used as:
A standalone switch.
•
An interconnect device in a QFX3000-M QFabric system.
•
A Node device in a QFabric system.
•
The QFX5100-24Q is supported on both the QFX3000-G and QFX3000-M QFabric systems. A
QFX5100-24Q Node device is equivalent to 80 10-Gbps interfaces and 4 40-Gbps interfaces.
A primary, backup, or line card in a QFX Virtual Chassis.
•
A QFX Series Virtual Chassis allows you to interconnect up to 10 QFX3500, QFX3600, or QFX5100
switches into one logical device and manage the device as a single chassis in a ring topology.
Use QFX5100-24Q switches as the primary and backup in a QFX Virtual Chassis.
A line card in a QFX5110 Virtual Chassis.
•
A QFX5110 Virtual Chassis must have a QFX5110-32Q as the primary. Only QFX5110 switches and
select models of QFX5100 can participate in a QFX5110 Virtual Chassis. Junos OS Release 17.3R1
or later is required for QFX5110 Virtual Chassis.
A spine or leaf device in a standard QFX5100 Virtual Chassis Fabric (VCF).
•
VCF uses Virtual Chassis technology to interconnect multiple devices into a single logical device and
manage that device as a single logical device inside of a fabric architecture. VCF architecture supports
up to 20 total devices in a spine and leaf topology. Out of the 20 total devices, you can configure a
maximum of 4 spine devices.
A QFX5100 VCF uses QFX5100 devices as spines or leaf devices. You can also use QFX3500, QFX3600,
and EX4300 models as leaf devices in a QFX5100 VCF.
Whenever possible, configure the QFX5100-24Q as the spine device in a QFX5100 VCF.
A leaf device in a QFX5110 VCF.
•
A QFX5110 VCF must have a minimum of two QFX5110-32Q as spine devices. Junos OS Release
17.3R1 or later is required for QFX5110 VCF.
24
A satellite device in a Junos Fusion system.
•
Junos OS Release 14.2.3 or later is required for Junos Fusion.
The QFX5100-24Q switch has two bays on the port panel for optional expansion modules. The
QFX5100-24Q supports two expansion modules to increase port density:
QFX-EM-4Q, which provides four additional 40-Gigabit Quad SFP+ (QSFP+) ports. See
•
Figure 6 on page 24.
Figure 6: QFX-EM-4Q Expansion Module
EX4600-EM-8F, which provides eight additional 10-Gigabit Ethernet Enhanced Small Form-Factor
•
Pluggable (SFP+) or four 1-Gigabit Ethernet ports. See Figure 7 on page 25.
CAUTION: Use only the top four ports or the bottom four ports for SFP
transceivers. Because SFP transceivers are larger than SFP+ transceivers, attempting
to stack SFP transceivers can cause internal damage to the module.
Figure 7: EX4600-EM-8F Expansion Module
NOTE: The EX4600-EM-8F is not supported on the QFX5100-24Q running in QFabric
systems.
The QFX5100-24Q is configured for the QFX-EM-4Q by default, but any combination of the two modules
is supported. Expansion modules can be hot-inserted or hot-removed. However, when an EX4600-EM-8F
is inserted instead of the default QFX-EM-4Q, the new configuration causes the interfaces to temporarily
go down. Likewise, when an EX4600-EM-8F is running on the QFX5100-24Q and it is swapped with a
QFX-EM-4Q, the interfaces temporarily go down, which can cause a short disruption in traffic.
25
QFX5100-24Q-AA
•
As shown in Figure 8 on page 26, the QFX5100-24Q-AA is a 1 U, top-of-rack, 40-Gigabit Ethernet
QSFP+ switch with 24 high-density QSFP+ ports. Each QSFP+ port can be configured to support
40-Gigabit Ethernet or as a set of 4 independent 10-Gigabit Ethernet ports. The QFX5100-24Q-AA can
also be configured to support twenty-four 40-Gigabit Ethernet interfaces or ninety-six 10-Gigabit
Ethernet interfaces using breakout cables (channelization mode) with 1280 Gbps output. The switch
can be ordered with either ports-to-FRUs or FRUs-to-ports airflow and with AC or DC power supplies.
The QFX5100-24Q switch provides full duplex throughput of 2.56 Tbps.
The QFX5100-24Q-AA module bay can accommodate a single Packet Flow Accelerator (PFA) double-wide
expansion module (QFX-PFA-4Q) or two single-wide optional expansion modules (two or one each of
QFX-EM-4Q and EX4600-EM-8F). The QFX-PFA-4Q, which features a high-performance
field-programmable gate array (FPGA), provides four additional QSFP+ ports to the chassis. Each
QFX-EM-4Q adds four QSFP+ ports to the chassis and each EX4600-EM-8F adds eight 10-Gigabit SFP+
ports to the chassis. The QFX-EM-4Q ports can also be configured as either access ports or uplink ports,
but only ports 0 and 2 can be channelized using port mode. For full details on the different port
channelization modes, see “Port Panel of a QFX5100-24Q Device” on page 34. All ports on the
QFX5100-24Q and QFX-EM-4Q can be configured as either access ports or uplink ports.
This switch provides the hardware support to enable PTP boundary clocks by using the QFX-PFA-4Q
module. The QFX5100-24Q-AA also supports GPS in and out signals when QFX-PFA-4Q is installed.
The CPU subsystem of this switch includes a 2-port 10-Gigabit Ethernet network interface card (NIC)
to provide a high bandwidth path or to alternate traffic path to guest VMs directly from the Packet
Forwarding Engine.
Figure 8: QFX5100-24Q-AA Port Panel with QFX-PFA-4Q
The QFX5100-24Q-AA can be used as a standalone switch that supports high frequency statistics
collection. Working with Juniper Networks Cloud Analytics Engine, this switch monitors and reports the
workload and application behavior across the physical and virtual infrastructure.
The QFX5100-24Q-AA supports the following expansion modules to increase port density:
QFX-PFA-4Q (double-wide), which provides four additional QSFP+ ports. See Figure 9 on page 26.
•
Figure 9: QFX-PFA-4Q Expansion Module
26
QFX-EM-4Q (single-wide), which provides 4 additional 40-Gigabit Ethernet QSFP+ ports. See
•
Figure 6 on page 24.
EX4600-EM-8F (single-wide), which provides 8 additional 10-Gigabit Ethernet SFP+ ports. See
•
Figure 7 on page 25.
The QFX5100-24Q switch supports the QFX-PFA-4Q and you must take the switch offline before
replacing the expansion module. Any combination of EX4600-EM-8F and QFX-EM-4Q is also supported.
These two expansion modules can be hot-inserted or hot-removed. However, when an EX4600-EM-8F
is inserted instead of a QFX-EM-4Q, the new configuration causes the interfaces to temporarily go
down. Likewise, when an EX4600-EM-8F is running on the QFX5100-24Q and is swapped with a
QFX-EM-4Q, the interfaces temporarily go down, which can cause a short disruption in traffic.
QFX5100-96S
•
As shown in Figure 10 on page 27, the QFX5100-96S switch is a is a 10-Gigabit Ethernet Enhanced
Small Form-Factor Pluggable (SFP+) top-of-rack switch with 96 SFP+ ports and 8 Quad SFP+ (QSFP+)
ports. Each SFP+ port can operate as a native 10 Gigabit port, when 10 Gbps optics are used. The SFP+
ports can also run at 1 Gbps, or at 100 Mbps speeds when 1_Gigabit optics are inserted. QSFP+ ports
96 and 100 can operate at native 40 Gbps speed or can be channelized to 4 independent 10 Gbps port
speeds. The 8 QSFP+ ports can be used as either access ports or as uplinks. The QFX5100-96S switch
has a 2 U form factor and comes standard with redundant fans and redundant power supplies. The switch
can be ordered with either ports-to-FRUs or FRUs-to-ports airflow and with AC or DC power supplies.
Figure 10: QFX5100-96S Port Panel
The QFX5100-96S can be used as:
A standalone switch.
•
A member in a QFX Virtual Chassis.
•
27
A QFX Series Virtual Chassis allows you to interconnect up to ten QFX3500, QFX3600, or QFX5100
switches into one logical device and manage the device as a single chassis in a ring topology.
A spine or leaf device in a Virtual Chassis Fabric (VCF).
•
VCF uses Virtual Chassis technology to interconnect multiple devices into a single logical device and
manage that device as a single logical device inside of a fabric architecture. VCF architecture supports
up to 20 total devices in a spine and leaf topology. Of those 20 devices, 4 QFX5100 devices can be
configured as spine devices.
In a mixed environment with QFX5100-24Q, QFX5100-98S and EX4300, use the QFX5100-24Q as
the spine device and the QFX5100-96S and EX4300 as a leaf devices. You may use the QFX5100-96S
as a spine in an all QFX5100-96S VCF or in a VCF that has a mixture of QFX5100-96S and EX4300.
A line card in a mixed QFX5110 Virtual Chassis.
•
A QFX5110 Virtual Chassis must have a QFX5110-32Q as the primary. Only QFX5110 switches and
select models of QFX5100 switches can participate in a QFX5110 Virtual Chassis. Junos OS Release
17.3R1 or later is required for QFX5110 Virtual Chassis.
A spine or leaf device in a standard QFX5100 Virtual Chassis Fabric (VCF).
•
VCF uses Virtual Chassis technology to interconnect multiple devices into a single logical device and
manage that device as a single logical device inside of a fabric architecture. VCF architecture supports
up to 20 total devices in a spine and leaf topology. Out of the 20 total devices, you can configure a
maximum of 4 spine devices.
A QFX5100 VCF uses QFX5100 devices as spines or leaf devices. You can also use QFX3500, QFX3600,
and EX4300 models as leaf devices in a QFX5100 VCF.
Whenever possible, configure the QFX5100-24Q as the spine device in a QFX5100 VCF.
A leaf device in a QFX5110 VCF.
•
A QFX5110 VCF must have a minimum of two QFX5110-32Q as spine devices. Junos OS Release
17.3R1 or later is required for QFX5110 VCF.
A satellite device in a Junos Fusion system.
•
Junos OS Release 14.2.3 or later is required for Junos Fusion.
System Software
QFX Series devices use the Junos operating system (OS), which provides Layer 2 and Layer 3 switching,
routing, and security services. Junos OS is installed on a QFX5100 switch’s 32-gigabyte (GB) internal solid
state flash drive. The same Junos OS code base that runs on QFX5100 switches also runs on all Juniper
Networks EX Series switches, M Series, MX Series, and T Series routers.
Participation in a QFX5110 Virtual Chassis or a QFX5110 VCF requires the same Junos OS image on all
devices in the Virtual Chassis or VCF. Junos OS 17.3R1 or later is the minimum software release for
QFX5110 Virtual Chassis or QFX5110 VCF.
28
For more information about which features are supported on QFX Series devices, see Feature Explorer.
You manage the switch using the Junos OS command-line interface (CLI), accessible through the console
and out-of-band management ports on the device.
SEE ALSO
Plan a Virtual Chassis Fabric Deployment | 95
QFX5100 Device Models
The QFX5100 switches have 24, 48, or 96 port configurations. The 24 port switches can be expanded to
a maximum of 32 QSFP+ ports using expansion modules. All switches are available with either AC or DC
power supply and with either airflow-in or airflow-out cooling. In legacy switches, or switches with an
LCD, this air flow is called front-to-back and back-to-front.
Table 3 on page 29 lists the ordering numbers for QFX5100 switch product SKUs.
Table 3: QFX5100 Switch Product Numbers
29
Number of
Expansion
ModulesPortsP roduct Numbers
24 QSFP+QFX5100-24Q-AA
expansion
modules and
has 2
expansion
module slots
Power
Supply
Number
of Mgt.
Ports
2ACSupports 3
2AC224 QSFP+QFX5100-24Q-AFI
3AC224 QSFP+QFX5100-24Q-3AFI
2AC224 QSFP+QFX5100-24Q-AFO
3AC224 QSFP+QFX5100-24Q-3AFO
Airflow
Air In
(FRUs-to-ports)
and Air Out
(ports-to-FRUs)