Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. and/or its affiliates in
the United States and other countries. All other trademarks may be 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.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OShas 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 tothe terms and conditions of the End User License Agreement (“EULA”) posted at
http://www.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that
To obtain the most current version of all Juniper Networks®technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
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 http://www.juniper.net/books.
Supported Platforms
For the features described in this document, the following platforms are supported:
•
QFabric System
•
QFX Series
Documentation Conventions
Table 1 on page xvi defines notice icons used in this guide.
Represents names of configuration
statements, commands, files, and
directories;configurationhierarchylevels;
or labels on routing platform
components.
About the Documentation
ExamplesDescriptionConvention
•
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 variables.< > (angle brackets)
| (pipe symbol)
# (pound sign)
[ ] (square brackets)
Indention and braces ( { } )
; (semicolon)
GUI Conventions
Bold text like this
Indicatesa choice between the mutually
exclusivekeywordsor variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
same line as the configurationstatement
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.
Representsgraphicaluser interface (GUI)
items you click or select.
broadcast | multicast
(string1 | string2 | string3)
rsvp { # Required for dynamic MPLS onlyIndicates a comment specified on the
community name members [
community-ids ]
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
•
In the Logical Interfaces box, select
All Interfaces.
•
To cancel the configuration, click
Cancel.
> (bold right angle bracket)
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can provide feedback by using either of the following
methods:
•
Online feedback rating system—On any page of the Juniper Networks TechLibrary site
at http://www.juniper.net/techpubs/index.html,simply click the stars to ratethe content,
and use the pop-up form to provide us with information about your experience.
Alternately, you can use the online feedback form at
http://www.juniper.net/techpubs/feedback/.
Separates levels in a hierarchy of menu
selections.
In the configuration editor hierarchy,
select Protocols>Ospf.
E-mail—Sendyourcomments 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 availablethrough the Juniper NetworksTechnical Assistance
Center (JTAC). If you are a customer with an active J-Care or Partner Support Service
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
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:
Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
•
Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
•
Search technical bulletins for relevant hardware and software notifications:
http://kb.juniper.net/InfoCenter/
•
Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
•
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlementby productserial number,use our Serial Number Entitlement
(SNE) Tool: https://entitlementsearch.juniper.net/entitlementsearch/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
•
Use the Case Management tool in the CSC at http://www.juniper.net/cm/.
•
Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
Understanding Redundancy of QFX3500 Device Components and
Functionality on page 7
•
Understanding QFX Series Virtual Chassis on page 8
•
Understanding QFX Series Virtual Chassis Components on page 11
QFX3500 Device Overview
The Juniper Networks QFX3500 device is a high-speed, multipurpose switch especially
designed for next-generation data centers. The QFX3500 can be configured as a
standalone switch, a Node device in a QFabric system, or as a member of a QFX Virtual
Chassis.
Forty-eight 10-Gbps access ports in the device use small form-factor pluggable plus
(SFP+) transceivers and operate by default as 10-Gigabit Ethernet interfaces. Optionally,
you can choose to configure up to 12 of the ports as 2-Gbps, 4-Gbps, or 8-Gbps
Fibre Channel (FC) interfaces, and up to 36 of the ports as 1-Gigabit Ethernet interfaces.
When used as a standalone switch, four 40-Gbps uplink ports in the device use quad
small form-factor pluggable plus (QSFP+) to four SFP+ copper breakout cables to
support an additional 15 10-Gigabit Ethernet interfaces.
QFX3500 devices can function as a Fibre Channel over Ethernet (FCoE)-FC gateway or
as an FCoE transit switch. FCoE is a method of supporting converged FC and Ethernet
traffic on a data center bridging (DCB) network by encapsulating unmodified FC frames
in Ethernet to transport the FC frames over the physical Ethernet network.
In a QFabric system, a QFX3500 device functions as a Node device, connected to a
QFabric system through 40-Gbps uplink ports to a Juniper Networks QFX3008-I or
QFX3600-I Interconnect device. Together, the QFX3500 Node devices and QFX3008-I
or QFX3600-I Interconnect devices form a multistage, nonblocking switch fabric that
provides a high-performance, low-latency, unified interconnect solution for
next-generation data centers.
TheQFX3500 Node devices and Interconnect devices are connectedto Juniper Networks
QFX3100 Director devices in an out-of-band management network through Juniper
NetworksEX4200 Ethernet Switches.The QFX3100 Directordevices present the QFabric
system devices as a single network entity, which enables simplified management of your
data center using the Junos OS command-line interface (CLI).
In a QFX Virtual Chassis, the QFX3500 device can participate with other QFX3500 devices
and QFX3600 devices in a ring topology with up to 10 members.
In a QFX5100 Virtual Chassis Fabric, the QFX3500 device can participate as a leaf device.
Up to a total of 20 devices can participate in the QFX5100 Virtual Chassis Fabric.
•
Software on page 4
•
Hardware on page 4
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 the QFX3500
device’s 8-gigabyte (GB) internal flash drive. The same Junos OS code base that runs
on QFX3500 devices also runs on all Juniper Networks EX Series switches, and J Series,
M Series, MX Series, and T Series routers.
Hardware
For more information about which features are supported on QFX Series devices, see
Feature Explorer.
When the QFX3500 device is operating as a standalone switch, 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.
When a QFX Series device operates as part of a QFabric system, all the devices in the
data center fabric are managed through the Administrator software installed on the
QFX3100 Director devices. Each device in a QFabric system is interconnected in a single
control plane and management network, using the redundant management ports on
each device.
The compact QFX3500 device is 1 rack unit (1 U) in size and designed to fit in
industry-standard 19-inch rack-mount enclosures. See Figure 1 on page 5 and
Figure 2 on page 5 and “Chassis Physical Specifications for a QFX3500 Chassis” on
page 17.
NOTE: The standard mounting configuration for the QFX3500 device uses
a two rail mounting system. The QFX3500-RB-ACRB device model uses a
four rail mounting system for installations that need to recess the switch or
need to mount the port (rear) end of the switch forward.
The front panel of the QFX3500 chassis has an LCD panel that displays the device
hostname and the number of active alarms. See “Front Panel of a QFX3500 Device” on
page 19. The rear panel has 48 10-Gbps access ports and 4 40-Gbps uplink ports. See
“Rear Panel of a QFX3500 Device” on page 20.
SFP+ Access Ports
The QFX3500 device has 48 access ports (0 through 47) that support small form-factor
pluggable plus (SFP+) and small form-factor pluggable (SFP) transceivers, as well as
SFP+ direct attach copper cables, also known as Twinax cables. See “Determining
Interface Support for the QFX3500 Device” on page 59.
•
Up to 48 of the access ports can be used for SFP+ transceivers or SFP+ direct attach
copper cables. You can use 10-Gigabit Ethernet SFP+ transceivers and SFP+ direct
attach copper cables in any access port. You can use 2-Gbps, 4-Gbps, or 8-Gbps
Fibre Channel SFP+ transceivers in ports 0 through 5 and ports 42 through 47.
NOTE: If you use Fibre Channel SFP+ transceivers in ports 0 through 5 or
ports 42 through 47, you must configure the entire block of ports as
Fibre Channel ports. For example, if you use a Fibre Channel SFP+
transceiver in any of the ports 0 through 5, then ports 0 through 5 must be
configured as Fibre Channel ports. If you use a Fibre Channel SFP+
transceiverin any of the ports 42 through 47, then ports 42 through 47 must
be configured as Fibre Channel ports. You then cannot use
10-Gigabit Ethernet SFP+ transceivers in these ports.
Up to 36 of the access ports can be used for SFP transceivers. Gigabit Ethernet SFP
transceivers can be used in ports 6 through 41.
Figure 3 on page 6 shows the location of the SFP+ access ports, including the ports that
can be used with Fibre Channel SFP+ transceiversand Gigabit Ethernet SFP transceivers.
Figure 3: SFP+ Access Port Locations
CAUTION: Do not place a copper transceiver in an access port directly
above or below another copper transceiver. Internal damage to the access
ports and device can occur. Because of this limitation, a maximum of 18
copper transceivers can be installed in ports 6 through 41. We recommend
using only the top row of access ports for copper transceivers.
QSFP+ Uplink Ports
The QFX3500 devicehas fouruplink ports (Q0 through Q3) thatsupport up tofour QSFP+
transceivers, as well as QSFP+ DAC or DAC breakout cables. See “Determining Interface
Support for the QFX3500 Device” on page 59.
When the QFX3500 device is used as part of a QFabric system, these uplink ports are
used to connect the QFX3500 Node device to QFX3008-I or QFX3600-I Interconnect
devices. See Connecting a QFX3500 Node Device to a QFX3008-I Interconnect Device orConnecting a QFX3500 Node Device to a QFX3600-I Interconnect Device.
When the QFX3500 device is used as a standalone switch, these uplink ports are
configuredby default as 15 10-Gigabit Ethernet interfaces.Another option for these ports
is to configure one or more of the ports as 40-Gigabit Ethernet interfaces.
Figure 4 on page 7 shows the location of the QSFP+ uplink ports and the default
10-Gigabit Ethernet interface numbering.
NOTE: Port Q0 is unique in that the number of 10-Gigabit Ethernet interfaces
supported varies by Junos OS release. In some Junos OS releases, port 00
has a reserved port and in other releasesthe port is available. See the topics
on Channelizing Interfaces or Configuring the Port Type, for your specific
release.
The QSFP+ uplink ports are supported in Junos OS Release 11.2 and later. To
configure the ports as 40-Gigabit Ethernet interfaces, you must be using
Junos OS Release 12.2X50-D20 or later.
Figure 4: QSFP+ Uplink Port Locations
Chapter 1: System Overview
Related
Documentation
Field-Replaceable Units in a QFX3500 Device on page 18•
• Site Preparation Checklist for a QFX3500 Device on page 45
• Access Port and Uplink Port LEDs on a QFX3500 Device on page 21
• Installing and Removing QFX3500 Device Hardware Components on page 121
Understanding Redundancy of QFX3500 Device Components and Functionality
The following hardware components provide redundancy on a QFX3500 device:
•
Power supplies—The QFX3500 device has one or two power supplies. Each power
supply provides power to all components in the device. 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.
•
Cooling system—The QFX3500 device has two fan trays. Additional cooling is provided
by two fan modules on the management board. If a fan module on a fan tray or
management board fails and is unable to keep the QFX3500 device within the desired
CAUTION: Do not connect feed A and feed B to the same power supply
temperature thresholds, chassis alarms occur and the QFX3500 device may shut
down.
Related
Documentation
AC Power Supply for a QFX3500, QFX3600, or QFX3600-I Device on page 35•
• DC Power Supply for a QFX3500, QFX3600, or QFX3600-I Device on page 37
• Cooling System and Airflow for a QFX3500 Device on page 29
Understanding QFX Series Virtual Chassis
This topic discusses QFX Series Virtual Chassis. A QFX Series Virtual Chassis is a supported
combination of interconnected QFX3500, QFX3600, QFX5100, QFX5110, and EX4300
switches operating as one logical device and managed as a single chassis. Switches in
a Virtual Chassis are called members of the Virtual Chassis.
This topic does not discuss Virtual Chassis Fabric (VCF). For informationon understanding
VCF, see Virtual Chassis Fabric Overview.
This topic includes:
•
QFX Virtual Chassis Overview on page 8
•
QFX5110 Switches in a Virtual Chassis on page 9
•
QFX5100 Switches in a Virtual Chassis on page 10
•
QFX3500 and QFX3600 Switches in a Virtual Chassis on page 11
•
EX4300 Switches in a QFX Series Virtual Chassis on page 11
QFX Virtual Chassis Overview
A QFX Series Virtual Chassis is a flexible, scaling switch solution for supported
combinationsof QFX3500, QFX3600,QFX5100,and QFX5110 switches. EX4300 switches
can also be included in some configurations of a QFX Series Virtual Chassis..
In a QFX Series Virtual Chassis, you can interconnect up to ten standalone switches in
the following combinations into one logical device, and manage the logical device as a
single chassis:
•
QFX5110 switches or a combination of QFX5110 and QFX5100 switches (a non-mixed
Virtual Chassis)
•
QFX5100 switches (a non-mixed Virtual Chassis)
•
QFX5100 switches with any combinationof QFX3500, QFX3600,or EX4300 switches
(a mixed mode Virtual Chassis)
•
QFX3500switches or QFX3600 switches, or a combination of QFX3500 and QFX3600
switches (a non-mixed Virtual Chassis)
•
QFX3500 or QFX3600 switches with EX4300 switches, or a combination of all three
types of switches (a mixed mode Virtual Chassis)
The advantages of connecting multiple switches into a Virtual Chassis include
better-managed bandwidth at a networklayer, simplified configurationand maintenance
because multiple devices can be managed as a single device, increased fault tolerance
and high availability(HA) because a Virtual Chassis can remain active and network traffic
can be redirected to other member switches when a single member switch fails, and a
flatter, simplified Layer 2 network topology that minimizes or eliminates the need for
loop prevention protocols such as Spanning Tree Protocol (STP).
You set up a Virtual Chassis by configuring Virtual Chassis ports (VCPs) on the member
switches, and interconnecting the switches using the VCPs . VCPs are responsible for
passing all data and control traffic between member switches in theVirtual Chassis. The
following ports on QFX Series switches that support Virtual Chassis can be configured
into VCPs to form a QFX Series Virtual Chassis:
•
Any 100-Gbps or 40-Gbps QSFP28 ports on QFX5110 switches
•
Any non-channelized 40-Gbps QSFP+ ports on QFX3500, QFX3600, QFX5100, or
QFX5110 switches
•
Any fixed 10-Gbps SFP+ ports on QFX Series switches with these ports
See EX4300 Switches Hardware Overview for details on the ports on an EX4300 switch
that can be configured into VCPs in a QFX Series Virtual Chassis.
You can increase VCP bandwidth between member switches by configuring multiple
interfaces between the same two switches into VCPs. When multiple VCPs interconnect
the same two member switches, a Link Aggregation Group (LAG) or bundle is
automatically formed when the VCPs are on interfaces supporting identical speeds. For
example, if you have two 40-Gbps QSFP+ interfaces configured as VCPs between
member switches, a LAG with two member links with 80Gbps of total bandwidth is
formed. However, 10-Gbps SFP+ and 40-Gbps QSFP+ interfaces configured as VCPs
will not become members of the same VCP LAG.
QFX5110 Switches in a Virtual Chassis
Starting in Junos OS Release 17.3R1, Virtual Chassis is supported on QFX5110 switches.
You can interconnect up to ten QFX5110 switches or a combination of QFX5110 and
QFX5100 switches intoa QFX5110 Virtual Chassis. All switches can run the same software
image, and you do not need to configure mixed mode.
The following QFX5110 and QFX5100 switches are supported in a QFX5110 Virtual Chassis:
Starting in Junos OS Release 13.2X51-D20, Virtual Chassis is supported on QFX5100
switches.You can interconnect up to ten switches into a QFX5100 Virtual Chassis that
can include any combination of QFX5100, QFX3500, QFX3600, and EX4300 switches.
NOTE: In Junos OS release13.2X51-D20, you can interconnect only up to four
QFX5100-96S switches in a non-mixed QFX5100 Virtual Chassis. Starting
in Junos OS release 13.2X51-D25, you can configure up to ten QFX5100-96S
switches into a mixed or non-mixed QFX Series Virtual Chassis.
The following QFX5100 switches are supported in a non-mixed QFX5100 Virtual Chassis
or a mixed QFX5100 Virtual Chassis (QFX5100 switches with QFX3500, QFX3600, or
EX4300 switches):
•
QFX5100-24Q
•
QFX5100-48S
•
QFX5100-48T
•
QFX5100-96S
NOTE: QFX5100-24Q switches should be configured as the Routing Engine
role members in a mixed QFX5100 Virtual Chassis.
QFX5100 switches can also be part of a QFX5110 Virtual Chassis, which can include a
combination of up to ten QFX5110 and QFX5100 switches. For a QFX5100 switch to
participatein a QFX5110 Virtual Chassis, the switchmust 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 master and backup Routing Engine roles,
and QFX5100 switches only in the linecard role.
The following QFX5100 switches are supported in a QFX5110 Virtual Chassis:
•
QFX5100-24Q
•
QFX5100-48S
•
QFX5100-96S
CAUTION: A QFX5100 switch running a Junos OS software image with
“-qfx-5-” in the package filename must first be upgraded to a Junos OS
software image with “-qfx-5e-” in the package filename before it can be
added to a QFX5110 Virtual Chassis or VCF. See Upgrading a QFX5100 Switchwith a USB Device to Join a QFX5110 Virtual Chassis or Virtual Chassis Fabric.