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 | x
Documentation and Release Notes | x
Using the Examples in This Manual | x
Merging a Full Example | xi
Merging a Snippet | xii
Documentation Conventions | xii
Documentation Feedback | xv
Requesting Technical Support | xv
Self-Help Online Tools and Resources | xvi
Creating a Service Request with JTAC | xvi
iii
Overview
QFX5110 System Overview | 18
QFX5110 Hardware Overview | 18
Benefits of QFX5110 | 18
QFX5110 Models Overview | 19
QFX5110-48S Hardware | 21
QFX5110-32Q Hardware | 22
System Software | 22
QFX5110 Hardware Models | 23
Understanding Hardware Redundancy of QFX5110 Components and Functionality | 24
QFX5110 Field-Replaceable Units | 25
QFX5110 Port Panels | 26
QFX5110-48S Port Panel | 27
Switch Overview | 27
Network Ports | 28
Channelizing Interfaces | 29
Virtual Chassis and Virtual Chassis Fabric | 29
2
QFX5110-32Q Port Panel | 29
Switch Overview | 30
Network Ports | 30
Channelizing Interfaces | 31
Virtual Chassis and Virtual Chassis Fabric | 32
QFX5110 Network Port LEDs | 33
QFX5110 Management Panel | 36
QFX5110 Management Panel Description | 36
QFX5110 Management Port LEDs | 38
QFX5110 Chassis Status LEDs | 39
QFX5110 Cooling System | 42
QFX5110 Cooling System and Airflow Description | 42
iv
Fan Modules | 42
Do Not Install Components with Different Airflow or Wattage in the Switch | 46
QFX5110 Fan Module LED | 47
QFX5110 Power System | 48
QFX5110 AC Power Supply Description | 49
QFX5110 AC Power Specifications | 50
QFX5110 AC Power Cord Specifications | 51
QFX5110 AC Power Supply LEDs | 53
QFX5110 DC Power Supply Description | 54
QFX5110 DC Power Specifications | 56
QFX5110 DC Power Supply LEDs | 56
Site Planning, Preparation, and Specifications
QFX5110 Site Preparation Checklist | 60
QFX5110 Site Guidelines and Requirements | 61
QFX5110 Environmental Requirements and Specifications | 62
General Site Guidelines | 63
Site Electrical Wiring Guidelines | 63
QFX5110 Chassis Grounding Cable and Lug Specifications | 64
QFX5110 Clearance Requirements for Airflow and Hardware Maintenance | 65
QFX5110 Chassis Physical Specifications | 66
QFX5110 Rack Requirements | 67
QFX5110 Deployment in a Virtual Chassis or Virtual Chassis Fabric | 69
Planning a Virtual Chassis Deployment using QFX Devices | 69
Valid Configurations for a QFX Virtual Chassis | 70
Valid Configurations for a QFX5110 Virtual Chassis | 70
Valid Configurations for a QFX5200 Virtual Chassis | 71
VC Deployment Checklist | 71
Virtual Chassis Fabric Hardware Overview | 74
Plan a Virtual Chassis Fabric Deployment | 75
QFX5110 Network Cable and Transceiver Planning | 78
Determining Transceiver Support for the QFX5110 | 78
Cable Specifications for QSFP+ and QSFP28 Transceivers | 79
v
Understanding QFX Series Fiber-Optic Cable Signal Loss, Attenuation, and Dispersion | 81
Signal Loss in Multimode and Single-Mode Fiber-Optic Cables | 81
Attenuation and Dispersion in Fiber-Optic Cable | 82
Calculating Power Budget and Power Margin for Fiber-Optic Cables | 83
How to Calculate Power Budget for Fiber-Optic Cable | 83
How to Calculate Power Margin for Fiber-Optic Cable | 83
QFX5110 Management Cable Specifications and Pinouts | 85
Cable Specifications for Console and Management Connections for the QFX Series | 85
RJ-45 Management Port Connector Pinout Information | 86
Console Port Connector Pinouts for the QFX Series | 87
RJ-45 Port, SFP Port, SFP+ Port, QSFP+ Port, and QSFP28 Port Connector Pinout
Information | 87
USB Port Specifications for the QFX Series | 92
Initial Installation and Configuration
3
4
QFX5110 Installation Overview | 95
Standalone Installation Overview | 95
Virtual Chassis Fabric Installation Overview | 96
QFX5110 Installation Safety Guidelines | 97
Unpacking and Mounting the QFX5110 | 98
Unpacking a QFX5110 | 98
Register Products—Mandatory to Validate SLAs | 99
Mounting a QFX5110 in a Rack | 100
Before You Begin Rack Installation | 100
Connecting the QFX5110 to External Devices | 102
Connect a Device to a Network for Out-of-Band Management | 102
vi
Connect a Device to a Management Console Using an RJ-45 Connector | 103
Connecting the QFX5110 to Power | 104
Connect the QFX5110 to Earth Ground | 105
Alternate Method to Ground QFX5110-48S-DC and QFX5110-32Q-DC Systems | 106
Connecting AC Power to a QFX5110 | 108
Connecting DC Power to a QFX5110 | 111
Connecting the QFX5110 in a Virtual Chassis or Virtual Chassis Fabric | 116
Connecting QFX5110 and QFX5100 Members in a QFX5110 Virtual Chassis | 116
Connecting QFX5110 in a QFX5110 Virtual Chassis Fabric | 117
Configuring a QFX5110 | 119
Maintaining Components
Maintaining QFX5110 Fan Modules | 123
Removing a Fan Module from a QFX5110 | 123
Installing a Fan Module in a QFX5110 | 124
Maintaining QFX5110 Power Supplies | 126
Removing a Power Supply from a QFX5110 | 126
Installing a Power Supply in a QFX5110 | 128
Removing and Installing Transceivers and Fiber-Optic Cables on QFX5110 | 130
5
6
7
Remove a Transceiver | 130
Install a Transceiver | 134
Disconnect a Fiber-Optic Cable | 136
Connect a Fiber-Optic Cable | 137
How to Handle Fiber-Optic Cables | 138
Powering Off a QFX5110 | 139
Removing a QFX5110 from a Rack | 142
Troubleshooting Hardware
Troubleshooting the QFX5110 | 145
QFX5110 Troubleshooting Resources Overview | 145
QFX Series Alarm Messages Overview | 146
vii
Chassis Alarm Messages | 146
Contacting Customer Support and Returning the Chassis or Components
Contact Customer Support to Obtain Return Material Authorization | 153
Returning the QFX5110 Chassis or Components | 154
Locating the Serial Number on a QFX5110 Device or Component | 154
Listing the Chassis and Component Details Using the CLI | 155
Locating the Chassis Serial Number ID Label on a QFX5110 | 156
Locating the Serial Number ID Labels on FRU Components | 156
How to Return a Hardware Component to Juniper Networks, Inc. | 157
Guidelines for Packing Hardware Components for Shipment | 158
Safety and Compliance Information
General Safety Guidelines and Warnings | 162
Definitions of Safety Warning Levels | 163
Qualified Personnel Warning | 166
Warning Statement for Norway and Sweden | 167
Fire Safety Requirements | 167
Fire Suppression | 167
Fire Suppression Equipment | 167
Installation Instructions Warning | 169
Restricted Access Warning | 170
Ramp Warning | 172
Rack-Mounting and Cabinet-Mounting Warnings | 173
Grounded Equipment Warning | 179
Radiation from Open Port Apertures Warning | 180
Laser and LED Safety Guidelines and Warnings for the QFX Series | 181
Class 1M Laser Product Warning | 182
viii
Class 1M Laser Radiation Warning | 182
Unterminated Fiber-Optic Cable Warning | 183
Maintenance and Operational Safety Guidelines and Warnings | 185
Battery Handling Warning | 187
Jewelry Removal Warning | 188
Lightning Activity Warning | 190
Operating Temperature Warning | 191
Product Disposal Warning | 193
General Electrical Safety Guidelines and Warnings | 194
Action to Take After an Electrical Accident | 195
Prevention of Electrostatic Discharge Damage | 196
AC Power Electrical Safety Guidelines | 197
AC Power Disconnection Warning | 199
DC Power Electrical Safety Guidelines | 200
DC Power Disconnection Warning | 201
DC Power Grounding Requirements and Warning | 203
DC Power Wiring Sequence Warning | 205
DC Power Wiring Terminations Warning | 208
Multiple Power Supplies Disconnection Warning | 211
TN Power Warning | 212
QFX5110 Agency Approvals | 212
Agency Approvals for the QFX Series | 212
Compliance Statements for EMC Requirements for the QFX Series | 214
Canada | 214
European Community | 215
Israel | 215
Japan | 215
Korea | 216
ix
Taiwan | 216
United States | 216
Nonregulatory Environmental Standards | 216
Statements of Volatility for Juniper Network Devices | 217
About the Documentation
IN THIS SECTION
Documentation and Release Notes | x
Using the Examples in This Manual | x
Documentation Conventions | xii
Documentation Feedback | xv
Requesting Technical Support | xv
Use this guide to plan, install, perform initial software configuration, perform routine maintenance, and to
troubleshoot QFX5110 switches.
x
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;
}
}
}
}
xi
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]
xii
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 xiii defines notice icons used in this guide.
Table 1: Notice Icons
xiii
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 xiii 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)
xiv
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)
xv
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 QFX5110 Components and Functionality | 24
QFX5110 Field-Replaceable Units | 25
QFX5110 Hardware Overview
18
IN THIS SECTION
Benefits of QFX5110 | 18
QFX5110 Models Overview | 19
QFX5110-48S Hardware | 21
QFX5110-32Q Hardware | 22
System Software | 22
The QFX5110 line of switches delivers low latency, flexible deployment options, and rich automation
features. QFX5110 Switches build a strong underlay foundation for flexible, high-performance,
standards-based fabrics and routing that improve network reliability and agility.
This topic covers:
Benefits of QFX5110
Flexible fabric support—QFX5110 offers multiple fabric options to fit your desired network architecture:
Virtual Chassis (VC), with up to 10 members
•
Virtual Chassis Fabric (VC), which offers a single pane management for up to 20 nodes
•
MC-LAG, which provides dual-homing with reduced complexity related to STP
•
Junos Fusion Datacenter, where QFX5110 can operate as a satellite leaf node for 1 Gigabit, 10
•
Gigabit, 40 Gigabit, or 100 Gigabit connectivity
Overlay options—QFX5110 provides L2 and L3 VXLAN gateway support that works in conjunction with
a robust EVPN control plane to efficiently manage your virtualized workloads. Another option,
OVSDB-VXLAN can be introduced to stitch virtualized and physical workloads.
High density and low latency applications—Powered with high density 10 Gigabit or 40 Gigabit network
ports and four 100G uplinks, the QFX5110 delivers 1.76 Tbps of throughput and a low latency of 550
nS. Your legacy applications continue to be supported by 100 Mbps or 1 Gigabit copper SFP
transceivers.
QFX5110 Models Overview
The QFX5110 line of switches offers two compact 1 U models that are ideal for top-of-rack, QFX Virtual
Chassis, or Virtual Chassis Fabric (VCF) deployments, the 48-port QFX5110-48S and the 32-port
QFX5110-32Q. Performance of the control plane running on all the QFX5110 switches is enhanced by
the 1.8-Ghz quad-core Intel CPU with 16 GB of memory and 64 GB of solid-state drive (SSD) storage.
Both models offer flexible port configurations of 1-Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit
Ethernet, and 100-Gigabit Ethernet.
19
Both models can be ordered with either ports-to-FRUs or FRUs-to-ports airflow and with AC or DC power
supplies.
The QFX5110-32Q can be used as:
A standalone switch (Junos OS Release 17.2R1 and later).
•
A primary, backup, or line card in a QFX5110 Virtual Chassis (Junos OS Release 17.3R1 and later).
•
A QFX5110 Series Virtual Chassis allows you to connect up to 10 QFX5110 or supported QFX5100
switches into one logical device and manage the device as a single chassis using a ring topology. The
following QFX5100 switches are supported in a QFX5110 Virtual Chassis:
QFX5100-24Q
•
QFX5100-48S
•
QFX5100-96S
•
For a QFX5100 switch to participate in a QFX5110 Virtual Chassis, the switch must have the same
software version and image installed as the software running on the QFX5110 switches in the Virtual
Chassis. You do not need to configure mixed mode. In a QFX5110 Virtual Chassis, we recommend to
use QFX5110 switches in the primary and backup Routing Engine roles, and QFX5100 switches only in
the linecard role.
A spine or leaf device in a QFX5110 VCF (Junos OS Release 17.3R1 and later).
•
VCF uses QFX 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. You can configure up
to a total of 20 QFX5110 or QFX5100 devices in a VCF. Out of the 20 total devices, you can configure
a maximum of 4 spine devices. You can use these models in any combination as leaf devices:
QFX5100-24Q
•
QFX5100-48S
•
QFX5100-48T (Junos OS Release 17.3R2 and later)
•
QFX5100-96S
•
QFX5110-48S
•
NOTE: If only QFX5110-48S switches are available, cable and configure the switches as a
QFX5110 Virtual chassis.
20
NOTE: Unike a QFX5100 VCF, EX4300 switches are not supported in the QFX5110 VCF.
The QFX5110-48S can be used as:
A standalone switch (Junos OS Release 15.1X53-D210 and later).
•
A primary, backup, or line card in a QFX5110 Virtual Chassis (Junos OS Release 17.3R1 and later).
•
A QFX5110 Series Virtual Chassis allows you to connect up to 10 QFX5110 or supported QFX5100
switches into one logical device and manage the device as a single chassis using a ring topology. The
following QFX5100 switches are supported in a QFX5110 Virtual Chassis:
QFX5100-24Q
•
QFX5100-48S
•
QFX5100-96S
•
For a QFX5100 switch to participate in a QFX5110 Virtual Chassis, the switch must have the same
software version and image installed as the software running on the QFX5110 switches in the Virtual
Chassis. You do not need to configure mixed mode. In a QFX5110 Virtual Chassis, we recommend to
use QFX5110 switches in the primary and backup Routing Engine roles, and QFX5100 switches only in
the line card role.
A leaf device in a QFX5110 VCF (Junos OS Release 17.3R1 and later).
•
VCF uses QFX 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. You can configure up
to a total of 20 QFX5110 devices in a QFX5110 VCF. Use QFX5110-32Q as the spine devices. You can
g050472
GM
use these models in any combination as leaf devices:
QFX5100-24Q
•
QFX5100-48S
•
QFX5100-48T (Junos OS Release 17.3R2 and later)
•
QFX5100-96S
•
QFX5110-48S
•
NOTE: If only QFX5110-48S switches are available, cable and configure the switches as a
QFX5110 Virtual chassis.
A satellite device in a Junos Fusion Provider Edge system (Junos OS 18.1R2 and later)
•
21
NOTE: The QFX5110-48S does not support channelized ports in a Junos Fusion environment.
QFX5110-48S Hardware
As shown in Figure 1 on page 21, the QFX5110-48S is a 10-Gigabit Ethernet enhanced small form-factor
pluggable plus (SFP+) switch with 48 SFP+ ports and four 100-Gbps quad small form-factor (QSFP) pluggable
solution (QSFP28) ports. Each SFP+ port (0 through 47)can operate as a native 10-Gigabit Ethernet port
or a 1-Gigabit Ethernet port when 1-Gigabit Ethernet optics are inserted.
Each QSFP28 port (48 through 51) can operate as a native 100-Gigabit Ethernet port, a native 40-Gigabit
Ethernet port, or as 4 independent 10-Gigabit ports when using breakout cables. The four QSFP28 ports
can be used as either access ports or as uplinks. The QFX5110-48S provides an aggregate throughput of
960 Gbps. The QFX5110-48S has a 1 U form factor and comes standard with redundant fans and redundant
power supplies.
Figure 1: QFX5110-48S Port Panel
QFX5110-32Q Hardware
g050492
As shown in Figure 2 on page 22, the QFX5110-32Q is a flexible configuration switch allowing either 32
ports of 40-Gigabit Ethernet quad small form-factor pluggable plus (QSFP+) or 20 ports of QSFP+ and 4
ports of high-density 100-Gigabit Ethernet quad small form-factor pluggable solution (QSFP28). Each
QSFP+ port can operate as a native 40-Gigabit Ethernet port, or as four independent 10-Gigabit Ethernet
ports when using breakout cables. The four QSFP28 ports are available either as access ports or as uplinks.
The QFX5110-32Q can be channelized using one of the available system modes. For full details on the
different port channelization modes, see “QFX5110-32Q Port Panel” on page 29. The QFX5110-32Q
switch provides an aggregate throughput of 2.56 Tbps.
Figure 2: QFX5110-32Q Port Panel
22
System Software
QFX Series devices use the Junos operating system (OS), which is installed on a QFX5110 switch’s 64-GB
internal solid-state flash drive. The same Junos OS code base that runs on QFX5110 switches also runs
on all Juniper Networks EX Series switches, and M Series, MX Series, and T Series routers.
The QFX5110-48S switch is supported on Junos OS Release 15.1X53-D210 and later; the QFX5110-32Q
is supported on Junos OS 17.2R1 and later.
Software features are categorized into three tiers: base, premium, and advanced:
Junos OS base features such as Layer 2 and Layer 3 switching, multicast, automation, programmability,
•
Zero Touch Provisioning (ZTP), and basic monitoring are enabled by default from the factory.
Junos OS premium features such as Border Gateway Protocol (BGP), Intermediate System-to-Intermediate
•
System (IS-IS), and Virtual Extensible Local Area Network (VXLAN) require a QFX5K-C1-PFL license on
each QFX5110 switch to use these features.
Junos OS advanced features include Multiprotocol Label Switching (MPLS) in addition to all of the
•
premium features. A QFX5K-C1-AFL license is required on each QFX5110 switch to use these features.
When using QFX5110 switches in a QFX5110 VCF, PFL and AFL licenses are required on the spine device:
leaf devices do not require licensing.
QFX5110 switches employ the security feature, Secure Boot, which is based on the UEFI 2.4 standard.
The BIOS has been hardened and serves as a core root of trust. The BIOS updates, the bootloader, and
the kernel are cryptographically protected. No action is required to implement Secure Boot.
If a premium or advanced feature is configured on the QFX5110 without a valid license, an alarm is raised
and system log (syslog) messages are generated.
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
Virtual Chassis Fabric Hardware Documentation
Virtual Chassis Fabric Overview
23
QFX5110 Hardware Models
The QFX5110 switches have 32 or 48 port configurations. Both switches are available with either AC or
DC power supply and with either airflow-in or airflow-out cooling. All models of the QFX5110, except the
QFX5110-32Q_CHAS, ship with two power supplies and five fans installed by default.
Table 3 on page 23 lists the ordering numbers for QFX5110 hardware-only product SKUs.
Fan modules are not
shipped by default.
Order fan modules
separately.
CAUTION: Mixing different types (AC and DC) of power supplies in the same chassis
is not supported. Mixing different airflow modules in the same chassis is not supported.
Understanding Hardware Redundancy of QFX5110 Components and
Functionality
The following hardware components provide redundancy on a QFX5110:
Power supplies—The QFX5110 can operate with one power supply. However, all QFX5110 switches,
•
except the QFX5110-32Q-CHAS, ship with two power supplies preinstalled for redundancy.. Each power
supply provides power to all components in the switch. If two power supplies are installed, the two
power supplies provide full power redundancy to the device. If one power supply fails or is removed,
the second power supply takes over the electrical load without interruption.
To provide power redundancy to the system, both power supplies must be installed. Connect power
source feed A to one power supply and power source feed B to the second power supply.
CAUTION: Do not connect feed A and feed B to the same power supply input
terminal.
Cooling system—All QFX5110 switches, except the QFX5110-32Q-CHAS, ship with five fan modules
•
installed. If a fan module fails and is unable to keep the QFX5110 within the desired temperature
thresholds, chassis alarms occur and the QFX5110 can shut down.
SEE ALSO
25
QFX5110 Power System | 48
QFX5110 Field-Replaceable Units
Field-replaceable units (FRUs) are components that you can replace at your site. The QFX5110 FRUs are
hot-insertable and hot-removable: you can remove and replace one of them without powering off the
switch or disrupting the switching function.
CAUTION: Replace a failed power supply with a blank panel or new power supply
within one minute of removal to prevent chassis overheating. The switch continues
to operate with only one power supply running. Replace a failed fan module with a
new fan module within one minute of removal to prevent chassis overheating. Do not
operate the switch with missing FRUs for longer than one minute.
Table 4 on page 25 lists the FRUs for the QFX5110 and actions to take before removing them.
Table 4: FRUs in a QFX5110
Required ActionFRU
None.Power supplies
None.Fan modules
Table 4: FRUs in a QFX5110 (continued)
Required ActionFRU
26
Optical transceivers
NOTE: If you have a Juniper Care service contract, you can register any addition, change, or
upgrade of hardware components at
https://www.juniper.net/customers/support/tools/updateinstallbase/. Failure to do so can result
in significant delays if you need replacement parts. This note does not apply if you replace existing
components with the same type of component.
SEE ALSO
Maintaining QFX5110 Fan Modules | 123
Maintaining QFX5110 Power Supplies | 126
Removing and Installing Transceivers and Fiber-Optic Cables on QFX5110 | 130
None. We recommend that you disable the interface using the set interfacesinterface-name disable command before you remove the transceiver. See
“Remove a Transceiver” on page 130.
RELATED DOCUMENTATION
QFX5110 Management Panel | 36
QFX5110 Port Panels | 26
QFX5110 Port Panels
IN THIS SECTION
QFX5110-48S Port Panel | 27
QFX5110-32Q Port Panel | 29
QFX5110 Network Port LEDs | 33
QFX5110-48S Port Panel
IN THIS SECTION
Switch Overview | 27
Network Ports | 28
Channelizing Interfaces | 29
Virtual Chassis and Virtual Chassis Fabric | 29
The port panel of the QFX5110-48S is primarily comprised of 48 small form-factor pluggable plus (SFP+)
and 4 quad small form-factor pluggable solution (QSFP28) ports. It also provides a central location for the
Precision Time Protocol (PTP) connections to a grandmaster clock.
27
This topic describes:
Switch Overview
The port panel of the QFX5110-48S supports 48 logical 10-GbE ports when operating as a standalone
switch. These data ports (0 through 47) support either 1-Gbps or 10-Gbps SFP+ transceivers. You can also
use SFP+ DAC cables and 10-Gbps active optical cables (AOC) in any access port. Starting in Junos OS
Release 18.3R1, the 10-GbE ports also support 100 Mbps.
The remaining 4 QSFP28 ports (48 through 51) support speeds of 40 GbE or 100 GbE. Each port can be
configured as an independent 100-GbE port or as an independent 40-GbE port. These port are usually
used as uplinks or Virtual Chassis Ports (VCP) on QFX5110 Virtual Chassis or Virtual Chassis Fabric (VCF).
In 40-GbE mode, these ports can be channelized using QSFP+ to SFP+ DAC breakout (DACBO) cables.
The port panel also provides PTP connections to a grandmaster clock (requires Junos OS Release 18.1R1).
There are also 10-MHz pulses-per-second (PPS) SubMiniature B (SMB) input and output connections to
measure the timing drift to and from the grandmaster clock.
Figure 3 on page 28 shows the port panel of the QFX5110-48S.
5—2—Output clock at 10 MhzRJ-45 connection to grandmaster clock
6—3—1 pulse per second (PPS) output connection48 SFP+ ports
CAUTION: Do not install 1GbE copper transceivers (such as QFX-SFP-1GE-T) directly
above or below another 1GbE copper transceiver. Use only the top row or bottom
row to avoid damage to the device caused by some types of copper transceivers when
the transceivers are installed above or below each other. However, if you are using
copper transceivers with the OEM part number FCLF8521P2BTL-J1 printed on the
transceiver label, you can install the transceivers in any port with no restrictions. For
devices that support 10GbE copper transceivers, there is no similar restriction.
The QFX5110-48S device ports (0 to 47) support:
10-Gbps SFP+ transceivers
•
1-Gbps SFP transceivers
•
SFP+ direct attach copper (DAC) cables
•
SFP+ active optical cables (AOC)
•
The QFX5110-48S uplink ports (48 to 51) support:
100-Gbps QSFP28 transceivers
•
40-Gbps QSFP+ transceivers
•
100-Gbps AOC
•
40-Gbps AOC (Junos OS 18.3R1 and later)
•
100-Gbps QSFP28 DAC cables
•
40-Gbps QSFP+ DAC cables
•
40-Gbps QSFP+ to SFP+ DACBO cables (40-Gbps breaks out to 10-Gbps for copper connections)
•
40-Gbps AOCBO cables (40-Gbps breaks out to 10-Gbps for fiber connections)
•
Channelizing Interfaces
For downstream traffic, the QFX5110-48S has 4 physical or 16 logical ports that can be used for port
channelization. The default 100-Gigabit Ethernet ports can be configured as 40-Gigabit Ethernet, and in
this configuration can either operate as dedicated 40-Gigabit Ethernet ports or can be channelized to 4
independent 10-Gigabit Ethernet ports using copper or fiber breakout cables.
To channelize the ports, manually configure the port speed using the set chassis fpc slot-number portport-number channel-speed speed command, where the speed can be set to 10-Gigabit Ethernet, 40-Gigabit
Ethernet, or 100-Gigabit Ethernet. The ports do not support auto-channelization.
Virtual Chassis and Virtual Chassis Fabric
29
To connect QFX5110 switches as members in a QFX5110 Virtual Chassis, you need a pair of dedicated
ports on each switch and cables that link each member in the Virtual Chassis into a ring topology. Each
member in the ring has at least one direct Virtual Chassis port (VCP) connection to a upstream and
downstream member. QFX5110 switches are recommended in the primary, backup, or line card role. You
may only mix QFX5100 members with QFX5110 members in a QFX5110 Virtual Chassis; no other QFX
Series or EX Series switches are supported. See “Connecting QFX5110 and QFX5100 Members in a
QFX5110 Virtual Chassis” on page 116 for a a diagram of cabling QFX5110 switches in a ring topology.
To connect a QFX5110 switch as a spine or leaf device in a Virtual Chassis Fabric (VCF), you need a pair
of dedicated ports and cables that link each spine device and leaf device in the VCF. All spine devices have
at least one direct VCP connection to each leaf device in the VCF. See “Connecting QFX5110 in a QFX5110
Virtual Chassis Fabric” on page 117 for a cabling diagram.
QFX5110-32Q Port Panel
IN THIS SECTION
Switch Overview | 30
Network Ports | 30
Channelizing Interfaces | 31
Virtual Chassis and Virtual Chassis Fabric | 32
The port panel of the QFX5110-32Q primarily comprises 28 quad small form-factor pluggable plus (QSFP+)
6
ports and 4 quad small form-factor pluggable solution (QSFP28) ports. The mixture of QSFP+ and QSFP28
ports allows for flexible configuration as either all 40-Gigabit Ethernet ports or a mixture of 40-Gigabit
Ethernet and 100-Gigabit Ethernet for high-speed uplinks. The port panel also provides a central location
for the Precision Time Protocol (PTP) connections to a grandmaster clock.
This topic describes:
Switch Overview
The ports on the QFX5110-32Q support 40-Gbps or 100-Gbps speeds natively. All ports autosense the
type of transceiver and set the port to the corresponding speed. The QSFP+ ports can support channelization
to four independent 10 GbE downstream ports, see “Channelizing Interfaces” on page 31. Although all
network ports can be configured as either uplink or as access ports, best practice is to configure the four
QSFP28 ports (28 through 31) as uplinks to take advantage of the 100-Gbps speeds.
The port panel also provides PTP connections to a grandmaster clock (requires Junos OS Release 18.1R1).
There are also 10-MHz pulses-per-second (PPS) SubMiniature B (SMB) input and output connections to
measure the timing drift to and from the grandmaster clock.
30
Figure 4 on page 30 shows the port panel of the QFX5110-32Q.
Figure 4: QFX5110-32Q Port Panel
4—1—1 pulse per second (PPS) output connectionElectrostatic discharge (ESD) terminal
5—2—28 QSFP+ portsRJ-45 connection to grandmaster clock
6—3—4 QSFP28 portsOutput clock at 10 MHz
Network Ports
The QFX5110-32Q device ports (0 through 27) support:
40-Gbps QSFP+ transceivers
•
QSFP+ direct attach copper (DAC) cables
•
QSFP+ active optical cables (AOC) (Junos OS Release 18.3R1 and later)
•
Loading...
+ 190 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.