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
QFX5200 System Overview | 18
QFX5200 Switch Description | 18
QFX5200 Hardware | 19
Benefits of QFX5200 Switches | 20
QFX5200-32C Channelization | 21
QFX5200-32C-L Channelization | 21
QFX5200-48Y Channelization | 21
System Software | 21
QFX5200 Hardware Component Overview | 22
QFX5200 Component Redundancy | 23
QFX5200 Field-Replaceable Units | 24
QFX5200 Port Panels | 25
QFX5200-32C and QFX5200-32C-L Port Panel | 25
Network Ports | 26
Channelizing Interfaces | 27
Network Port LEDs | 27
2
QFX5200-48Y Port Panel | 29
Network Ports | 30
Port Groups | 30
Network Port LEDs | 32
QFX5200 Switch Management | 33
QFX5200 Management Panel Overview | 34
QFX5200-32C and QFX5200-32C-L Management Panel | 34
QFX5200-32C and QFX5200-32C-L Management Port and Console Port LEDs | 36
QFX5200-48Y Management Panel | 36
QFX5200-48Y Management Port LEDs | 37
QFX5200 Chassis Status LEDs | 38
QFX5200-32C and QFX5200-32C-L Chassis Status LEDs | 39
iv
QFX5200-48Y Chassis Status LEDs | 41
QFX5200 Cooling System | 43
QFX5200 Cooling System Description | 43
Fan Modules | 44
Do Not Install Components with Different Airflow or Wattage in the Switch | 49
QFX5200-32C and QFX5200-32C-L Fan Module LED | 50
QFX5200 Power System | 52
QFX5200 AC Power Supply Description | 52
QFX5200 AC Power Specifications | 54
QFX5200 Power Cord Specifications | 55
QFX5200 AC Power Supply LEDs | 57
QFX5200 DC Power Supply Description | 59
QFX5200 DC Power Specifications | 61
QFX5200 DC Power Supply LEDs | 62
Site Planning, Preparation, and Specifications
QFX5200 Site Preparation Checklist | 66
Planning a Virtual Chassis Deployment using QFX Devices | 67
Valid Configurations for a QFX Virtual Chassis | 68
Valid Configurations for a QFX5110 Virtual Chassis | 69
Valid Configurations for a QFX5200 Virtual Chassis | 69
VC Deployment Checklist | 69
QFX5200 Site Guidelines and Requirements | 72
QFX5200 Environmental Requirements and Specifications | 73
General Site Guidelines | 75
QFX5200 Grounding Cable and Lug Specifications | 75
QFX5200 Clearance Requirements for Airflow and Hardware Maintenance | 76
QFX5200 Chassis Physical Specifications | 77
Site Electrical Wiring Guidelines | 78
QFX5200 Rack Requirements | 79
QFX5200 Cabinet Requirements | 80
QFX5200 Network Cable and Transceiver Planning | 82
Determining QFX5200 Optical Interface Support | 82
v
Cable Specifications for QSFP+ and QSFP28 Transceivers | 83
Understanding QFX Series Fiber-Optic Cable Signal Loss, Attenuation, and Dispersion | 85
Signal Loss in Multimode and Single-Mode Fiber-Optic Cables | 85
Attenuation and Dispersion in Fiber-Optic Cable | 85
Calculating Power Budget and Power Margin for Fiber-Optic Cables | 86
How to Calculate Power Budget for Fiber-Optic Cable | 87
How to Calculate Power Margin for Fiber-Optic Cable | 87
QFX5200 Management Cable Specifications and Pinouts | 89
Cable Specifications for Console and Management Connections for the QFX Series | 89
RJ-45 Management Port Connector Pinout Information | 90
Console Port Connector Pinouts for the QFX Series | 90
RJ-45 Port, SFP Port, SFP+ Port, QSFP+ Port, and QSFP28 Port Connector Pinout
Information | 91
USB Port Specifications for the QFX Series | 96
Initial Installation and Configuration
3
4
QFX5200 Installation Overview | 99
Overview of Installing the QFX5200 | 99
QFX5200 Installation Safety Guidelines | 100
Unpacking and Mounting the QFX5200 | 100
Unpacking a QFX5200 | 101
Register Products—Mandatory to Validate SLAs | 102
Mounting a QFX5200 in a Rack or Cabinet | 103
Before You Begin Rack Installation | 104
Four Post Installation Procedure for QFX5200-32C or QFX5200-32C-L | 105
Four Post Installation Procedure for QFX5200-48Y | 107
Connecting the QFX5200 to External Devices | 110
vi
Connect a Device to a Network for Out-of-Band Management | 110
Connect a Device to a Management Console Using an RJ-45 Connector | 111
Connecting the QFX5200 to Power | 112
Connect the QFX5200 to Earth Ground | 113
Alternate Method to Ground QFX5200-32C-DC Systems | 115
Connecting AC Power to a QFX5200 | 116
Connecting DC Power to a QFX5200 | 119
Before You Begin | 120
Connecting DC Power to a QFX5200-32C-DC | 121
Connecting DC Power to a QFX5200-48Y | 124
Performing the Initial Software Configuration for QFX5200 Switches | 126
Maintaining Components
Maintaining QFX5200 Cooling System | 130
Removing a Fan Module from a QFX5200 | 130
Installing a Fan Module in a QFX5200 | 132
Maintaining QFX5200 Power System | 133
Removing a Power Supply from a QFX5200 | 134
Installing a Power Supply in a QFX5200 | 136
Maintaining Transceivers and Fiber Optic Cables on QFX5200 | 137
5
6
7
QFX5200-32C-L Time Allowance | 138
Remove a Transceiver | 138
Install a Transceiver | 141
Disconnect a Fiber-Optic Cable | 143
Connect a Fiber-Optic Cable | 144
How to Handle Fiber-Optic Cables | 145
Powering Off a QFX5200 | 146
Troubleshooting Hardware
Troubleshooting the QFX5200 | 152
QFX5200 Troubleshooting Resources Overview | 152
QFX Series Alarm Messages Overview | 153
vii
Chassis Alarm Messages | 153
Contacting Customer Support and Returning the Chassis or Components
Contact Customer Support to Obtain Return Material Authorization | 161
Returning the QFX5200 Chassis or Components | 162
Locating the Serial Number on a QFX5200 Device or Component | 162
Listing the Chassis and Component Details Using the CLI | 163
Locating the Chassis Serial Number ID Label on a QFX5200 | 165
Locating the Serial Number ID Labels on FRU Components | 166
How to Return a Hardware Component to Juniper Networks, Inc. | 166
Guidelines for Packing Hardware Components for Shipment | 167
Packing a QFX5200 Device or Component for Shipping | 168
Packing a QFX5200 Switch for Shipping | 168
Packing QFX5200 Components for Shipping | 169
Safety and Compliance Information
General Safety Guidelines and Warnings | 172
Definitions of Safety Warning Levels | 173
Qualified Personnel Warning | 176
Warning Statement for Norway and Sweden | 177
Fire Safety Requirements | 177
Fire Suppression | 177
Fire Suppression Equipment | 177
Installation Instructions Warning | 179
Chassis and Component Lifting Guidelines | 179
Restricted Access Warning | 181
Ramp Warning | 183
Rack-Mounting and Cabinet-Mounting Warnings | 184
Grounded Equipment Warning | 190
Laser and LED Safety Guidelines and Warnings | 191
General Laser Safety Guidelines | 191
viii
Class 1 Laser Product Warning | 192
Class 1 LED Product Warning | 193
Laser Beam Warning | 194
Radiation from Open Port Apertures Warning | 195
Maintenance and Operational Safety Guidelines and Warnings | 196
Battery Handling Warning | 197
Jewelry Removal Warning | 198
Lightning Activity Warning | 200
Operating Temperature Warning | 201
Product Disposal Warning | 203
General Electrical Safety Guidelines and Warnings | 204
Action to Take After an Electrical Accident | 205
Prevention of Electrostatic Discharge Damage | 206
AC Power Electrical Safety Guidelines | 207
AC Power Disconnection Warning | 209
DC Power Electrical Safety Guidelines | 210
DC Power Copper Conductors Warning | 211
DC Power Disconnection Warning | 212
DC Power Grounding Requirements and Warning | 214
DC Power Wiring Sequence Warning | 216
DC Power Wiring Terminations Warning | 219
Multiple Power Supplies Disconnection Warning | 222
TN Power Warning | 223
Agency Approvals and Compliance Statements for the QFX5200 and QFX5220 | 223
Agency Approvals for the QFX Series | 224
ix
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 QFX5200 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:
The QFX5200 line offers line-rate, low-latency 10/25/40/50/100GbE switches for building large IP fabrics.
QFX5200 Switches are an optimal choice for spine-and-leaf IP fabric deployments as well as metro use
cases.
This topic covers:
QFX5200 Hardware
IN THIS SECTION
QFX5200-32C and QFX5200-32C-L Hardware | 19
QFX5200-48Y Hardware | 20
QFX5200 line of switches offer compact 1 U models that provide a line rate configuration packet
performance, very low latency, and a rich set of Layer 3 features.
QFX5200-32C and QFX5200-32C-L Hardware
The QFX5200-32C and QFX5200-32C-L are compact 1 U standalone switches that provides a line rate
configuration packet performance, very low latency, and a rich set of Layer 3 features. The routing engine
and control plane are driven by the 1.8 Ghz quad-core Intel CPU with 16 GB of memory and two 32 GB
solid-state drives (SSD) for storage. The QFX5200-32C models run standard Junos Operating System (OS);
the QFX5200-32C-L models run Junos OS Evolved.
19
As shown in Figure 1 on page 19, the QFX5200-32C and QFX5200-32C-L are 100 Gigabit Ethernet
top-of-rack switches that support both quad small form-factor pluggable (QSFP+), 100-Gbps QSFP+
(QSFP28) transceivers, and break out cables in the 32 QSFP28 sockets. The ports 0 through 31 can be
configured as either uplinks or as access ports. The QSFP28 ports are configured as 100-Gigabit Ethernet
ports by default, but can also be configured to speeds of 50, 40, 25, or 10-Gigabit Ethernet.
The QFX5200-32C and QFX5200-32C-L comes standard with redundant fans and redundant power
supplies. Switches can be ordered with either ports-to-FRUs or FRUs-to-ports airflow. The QFX5200-32C
is available with AC or DC power supplies; the QFX5200-32C-L is available only with AC power supplies.
Figure 1: QFX5200-32C Port Panel
The QFX5200-32C-L is supported as a standalone switch (Junos OS Evolved Release 18.3R1 and later).
The QFX5200-32C can be used as:
A standalone switch (Junos OS Release 15.1X53-D30 and later).
•
A member in an all QFX5200-32C Virtual Chassis (Junos OS Release 17.3R2 and later).
g050901
•
You can create an all QFX5200-32C Virtual Chassis with up to three members. The QFX5200-32C is
used in all three member roles: primary RE, backup RE, and line card.
A satellite device in a Junos Fusion Provider Edge system (Junos OS Release 18.1R2 and later). A switch
•
in standalone mode must be converted to a satellite device.
QFX5200-48Y Hardware
The QFX5200-48Y is a flexible switch for environments with the need for native 25 Gbps port speeds.
The 48 small form-factor pluggable 28 (SFP28) ports support 10 Gbps or native 25 Gbps speeds, and the
6 QSFP28 support either 40 Gbps or 100 Gbps speeds. The 48 SFP28 default to 10 Gigabit Ethernet and
must be configured in groups of four ports to support 25 Gigabit Ethernet. You can alternate each group
of four ports with either 10 Gbps or 25 Gbps across the 48 ports. For details on configuring the SFP28
ports, see “Port Groups” on page 30.
The 6 QSFP28 ports auto-detect the optic speed of transceivers and set the port speed accordingly. The
six QSFP28 ports can be channelized when configured to 40 Gigabit Ethernet to 4 independent 10 Gigabit
Ethernet ports.
20
The routing engine and control plane of the switch are driven by the 2.20 Ghz quad-core Intel CPU with
16 GB of memory and a 32 GB solid-state drive (SSD) for storage. The QFX5200-48Y provides an aggregate
throughput of 3.6 Tbps (full duplex).
As shown in Figure 2 on page 20, the QFX5200-48Y 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 DCpower supplies.
The QFX5200-48Y is supported on Junos OS Release 18.1R1 and later.
Figure 2: QFX5200-48Y Port Panel
Benefits of QFX5200 Switches
QFX5200 switches offer:
Future proof and investment protection
•
Open and standards based for multi-vendor networks
•
Support for Zero Touch Provisioning (ZTP) for simplified operation
•
QFX5200-32C Channelization
Starting in Junos OS Release 17.3R1, ports are channelized automatically by detecting the cable type. The
mode and number of channels are set based on the channel link status:
When the port is configured for 40-Gigabit Ethernet and a 4x10G breakout cable is detected, the system
•
converts the port into 4 independent 10-Gigabit Ethernet ports
When the port is configured for 100-Gigabit Ethernet and a 2x50G breakout cable is detected, the
•
system converts the port into 2 independent 50-Gigabit Ethernet ports
When the port is configured for 100-Gigabit Ethernet and a 4x25G breakout cable is detected, the
•
system converts the port into 4 independent 25-Gigabit Ethernet ports
QFX5200-32C-L Channelization
21
Starting in Junos OS Evolved Release 18.3R1, ports can be channelized by configuration.
When the port is configured for 40-Gigabit Ethernet and a 4x10G breakout cable is detected, the system
•
converts the port into 4 independent 10-Gigabit Ethernet ports
When the port is configured for 100-Gigabit Ethernet and a 4x25G breakout cable is detected, the
•
system converts the port into 4 independent 25-Gigabit Ethernet ports
QFX5200-48Y Channelization
When one of the 6 QSFP28 ports are configured for 40-Gigabit Ethernet and a 4x10G breakout cable is
detected, the system converts the port into 4 independent 10-Gigabit Ethernet ports. Channelization is
not supported on the 48 SFP28 ports.
System Software
Customers who purchase a QFX5200-32C or QFX5200-48Y may either enable the Junos OS by purchasing
a Junos OS Base Services license. Customers purchasing a QFX5200-32C-L enable Junos OS Evolved by
purchasing a Junos OS Evolved Base Services license.
QFX Series devices use the Junos OS, which provides Layer 2 and Layer 3 switching, routing, and security
services. The Junos image is installed on one of the 32 GB solid state drives.The Junos OS Evolved software
running on the QFX5200-32C-L does not support Layer 2 features.
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.
QFX5200 Hardware Component Overview
The QFX5200 supports the components in listed in alphabetic order.
Table 3: QFX5200 Hardware Components
CLI OutputSpare Juniper Model NumberChassis ModelComponent
22
Chassis
Fan module
QFX5200-32C
QFX5200-32C-L
QFX5200-48Y
QFX5200-32C and
QFX5200-32C-L
QFX5200-48Y
Not available
QFX5200-32C-CHAS
QFX5200-48Y-CHAS
QFX5200-32C-FANAFI (FRUs to ports
airflow)
QFX5200-32C-FANAFO (Ports to FRUs
airflow)
QFX520048Y-FAN-AI (FRUs to ports
airflow)
QFX520048Y-FAN-AO (Ports to FRUs
airflow)
QFX5200-32C-32Q
QFX5200-32C-L
QFX5200-48Y
Fan tray n fan-n Back to Front
Airflow - AFI
Fan tray n fan-n Front to Back
Airflow - AFO
Fan tray n fan-n Back to Front
Airflow - AFI
Fan tray n fan-n Front to Back
Airflow - AFO
Table 3: QFX5200 Hardware Components (continued)
23
CLI OutputSpare Juniper Model NumberChassis ModelComponent
Power supplies
QFX5200-32C and
QFX5200-32C-L
QFX5200-32C
QFX5200-48Y
JPSU-850W-AC-AFI (FRUs to ports
airflow)
JPSU-850W-AC-AFO (Ports to FRUs
airflow)
JPSU-850W-DC-AFI (FRUs to ports
airflow)
JPSU-850W-DC-AFO (Ports to FRUs
airflow)
QFX520048Y-APSU-AI (FRUs to ports
airflow)
QFX520048Y-APSU-AO (Ports to FRUs
airflow)
QFX520048Y-DPSU-AI (FRUs to ports
airflow)
QFX520048Y-DPSU-AO (Ports to FRUs
airflow)
AC AFI 850W PSU
AC AFO 850W PSU
DC AFI 850W PSU
DC AFO 850W PSU
AC AFI 650W PSU
AC AFO 650W PSU
DC AFI 650W PSU
DC AFO 650W PSU
SEE ALSO
QFX5200 Port Panels | 25
QFX5200 Cooling System | 43
QFX5200 Component Redundancy
The following hardware components provide redundancy on a QFX5200 switch:
Power supplies—The QFX5200 switches have one or two power supplies. 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 balances 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—The QFX5200-32C and QFX5200-32C-L switch models have five fan modules. The
•
QFX5200-48Y switch models has six fan modules. If a fan module fails and is unable to keep the QFX5200
switch within the desired temperature thresholds, chassis alarms occur and the QFX5200 switch can
shut down.
QFX5200 Field-Replaceable Units
24
Field-replaceable units (FRUs) are components that you can replace at your site. The QFX5200 device
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 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 24 lists the FRUs for the QFX5200 device and actions to take before removing them.
Table 4: FRUs in a QFX5200 Switch
Required ActionFRU
None.Power supplies
None.Fan modules
Optical transceivers
None. We recommend that you disable the interface using the set interfacesinterface-name disable command before you remove the transceiver. See
“Disconnect a Fiber-Optic Cable” on page 143
NOTE: If you have a Juniper Care service contract, 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.
RELATED DOCUMENTATION
Installing and Removing QFX5200 Hardware Components
QFX5200 Cooling System | 43
QFX5200 Power System | 52
25
QFX5200 Port Panels
IN THIS SECTION
QFX5200-32C and QFX5200-32C-L Port Panel | 25
QFX5200-48Y Port Panel | 29
QFX5200-32C and QFX5200-32C-L Port Panel
IN THIS SECTION
Network Ports | 26
Channelizing Interfaces | 27
Network Port LEDs | 27
The port panel of the QFX5200-32C and QFX5200-32C-L supports port configuration speeds of 100, 50,
40, 25, or 10 Gigabit Ethernet. The QFX5200-32C and QFX500-32C-L uses 28-Gbps quad small-form
factor pluggable plus (QSFP28) sockets that are configured as 100 Gigabit Ethernet ports by default. Any
of the 32 ports 0 through 31 can be configured as uplinks or as access ports.
Figure 3 on page 26 shows the port panel of the QFX5200-32C and QFX5200-32C-L.
Figure 3: QFX5200-32C and QFX5200-32C-L Port Panel
4—1—32 QSFP28 portsRJ45 connection to grand master clock
5—2—Electrostatic discharge (ESD) terminal1 pulse per second (PPS) output connection for
clocking messages
26
3—Output clock at 10 Mhz
This topic describes:
Network Ports
The QFX5200-32C and QFX5200-32C-L network ports, ( 0 to 31) support:
100 Gbps QSFP28 transceivers
•
40 Gbps QSFP+ transceivers
•
100 Gbps active optical cables (AOC)
•
NOTE: For interoperability with other QFX Series switches, ensure auto-negotiation on the
QFX5200-32C is disabled.
40 Gbps AOC
•
QSFP28 direct attach copper (DAC) cables
•
QSFP+ DAC cables
•
(QFX5200-32C only) QSFP+ to QSFP+ direct attach copper break out (DACBO) cables (100 Gbps breaks
•
out to 50 Gbps or 25 Gbps)
(QFX5200-32C only) QSFP+ to SFP+ DACBO cables (40 Gbps breaks out to 10 Gbps)
•
Starting in Junos OS Release 19.3R1, you can also use a QSFP+ to SFP+ adapter (QSA) in the QSFP+ ports
g050236
Bi-coloredLEDs
to provide either 40 Gigabit Ethernet or 4x10 Gigabit Ethernet speeds.
Channelizing Interfaces
For downstream traffic, the QFX5200-32C has 32 physical or 128 logical ports (32 x 4) that can be used
for port channelization. The 100 Gigabit Ethernet ports can be channelized using breakout cables either
to 2 independent downstream 50 Gigabit Ethernet or to 4 independent 25 Gigabit Ethernet ports. The
default 100 Gigabit Ethernet ports can also 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 breakout cables.
The QFX5200-32C ports support auto-channelization starting in Junos OS Release 15.1X53-D230.
The QFX5200-32C-L does not support channelization.
Network Port LEDs
27
The Link/Activity LED configuration for QFX5200-32C and QFX5200-32C-L switches use bi-colored
LEDs. The link LED indicates link activity or a fault. See Table 5 on page 27.
Table 5: QFX5200-32C and QFX5200-32C-L Access Port and Uplink LED Locations
LocationIndicatorsPort Type
QSFP28 and
QSFP+
Speed
Link
Status
Channelization
Figure 4: QFX5200-32C and QFX5200-32C-L Port LEDs
Table 6 on page 28 describes how to interpret the QSFP28 port LEDs.
Table 6: Network Port LEDs on QSFP28 Ports on a QFX5200-32C and QFX5200-32C-L Switch
QFX5200-32C and QFX5200-32C-L DescriptionStateColor
The port is administratively disabled, there is no power, the link is down, or there is a fault.OffUnlit
When configured for 25-Gigabit Ethernet, the LED remains unlit only if all four of the
25-Gigabit Ethernet QSFP+ breakout links are down.
28
Green
steadily
A link is established, but there is no link activity.On
When configured for 25-Gigabit Ethernet, the LED is lit green when at least one of the four
25-Gigabit Ethernet QSFP+ breakout links is established.
A link is established, and there is link activity.Blinking
When configured for 25-Gigabit Ethernet, the LED is lit green when at least one of the four
25-Gigabit Ethernet QSFP+ breakout links is established.
The beacon is enabled on the port.BlinkingAmber
As shown in Table 7 on page 28, there are four bi-color LEDs for each QSFP+ port. The first LED is used
and the remaining LEDs are not used when the interface is configured for 100-Gigabit Ethernet and
connected to a QSFP28 transceiver. All four LEDs are used when the interface is configured for 25-Gigabit
Ethernet and the port is connected using an optical splitter cable or a copper DACBO cable.
Table 7 on page 28 describes how to interpret the QSFP+ LEDs.
Table 7: Network Port Link/Activity LEDs on QSFP+ Ports on a QFX5200-32C and QFX5200-32C-L
DescriptionStateColor
OffUnlit
On steadilyGreen
Blinking
The port is administratively disabled, there is no power, the link is down, or
there is a fault.
NOTE: When configured for 10-Gigabit Ethernet, the LED remains unlit only
if all four of the 10-Gigabit Ethernet SFP+ breakout links are down.
A link is established, but there is no link activity.
NOTE: When configured for 10-Gigabit Ethernet, the LED is lit green when
at least one of the four 10-Gigabit Ethernet SFP+ breakout links is established.
A link is established, and there is link activity.
NOTE: When configured for 10-Gigabit Ethernet, the LED is lit green when
at least one of the four 10-Gigabit Ethernet SFP+ breakout links is established.
Table 7: Network Port Link/Activity LEDs on QSFP+ Ports on a QFX5200-32C and
QFX5200-32C-L (continued)
DescriptionStateColor
All four LEDs blink to indicate the beacon function was enabled on the port.BlinkingAmber
QFX5200-48Y Port Panel
IN THIS SECTION
Network Ports | 30
Port Groups | 30
Network Port LEDs | 32
29
The port panel of the QFX5200-48Y supports port configuration speeds of 100 or 40 Gigabit Ethernet,
and 25 or 10 Gigabit Ethernet. The QFX5200-48Y has 48 small form-factor pluggable 28 (SFP28) ports
(0 through 47) that can be configured as either 10 Gigabit Ethernet or 25 Gigabit Ethernet. The
QFX5200-48Y also has six quad small form-factor pluggable (QSFP28) ports (48 through 53 that can be
configured as either 100 Gigabit Ethernet or 40 Gigabit Ethernet. The SFP28 ports default to 10 Gigabit
Ethernet but can be configured in groups of four ports to 25 Gbps speeds. The QSFP28 ports auto-sense
the speed of inserted optics and configure the port to the appropriate speed for that transceiver. See
Figure 5 on page 30.
Figure 5: Port Panel of QFX5200-48Y
g050900
2
1
564
3
7
4—RJ45 console
Network Ports
30
5—1—2 QSFP28 ports48 SFP28 ports
6—2—USB port4 QSFP28 ports
7—3—System status LEDsRJ45 management port
The QFX5200-48Y ports, (0 to 47) are normally used as access ports. They support:
10 Gbps SFP+ transceivers
•
10 Gbps direct attach copper (DAC) cables
•
25 Gbps SFP28 transceivers
•
25 Gbps SFP28 DAC cables
•
The QFX5200-48Y ports, (48 to 53) are normally used as uplinks. They support:
25 Gbps active optical cables (AOC)
•
40 Gbps QSFP+ transceivers
•
40 Gbps DACBO cables (40 Gbps to 10 Gbps)
•
100 Gbps QSFP28 transceivers
•
100 Gbps AOC
•
Port Groups
The 48 SFP28 ports default to 10 Gigabit Ethernet but can be configured to 25 Gigabit Ethernet by port
groups. The SFP28 ports are divided into 12 port groups, with four contiguous ports in each port group.
Each port group can be configured to either 10 Gbps or 25 Gbps speeds, but mixing port speeds within a
port group is not allowed. See Table 8 on page 31
Loading...
+ 195 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.