Lan switiching:

EX Series: Enterprise ethernet switches

WLAN Products: Controllers, access points and software

QFX Series: Enterprise ethernet switches

Juniper EX-Series is a series of Ethernet network switches designed and manufactured by Juniper
Networks.[1][2][3] These switches run on Juniper's network operating system, JUNOS.[4] Juniper's then
CEO and present Chairman, Scott Kriens said that the product launch marked the beginning of a
transcending chapter in Juniper's history, declaring, "The switch is on". The EX series was launched
12 years after the company's founding in 1996

EX Series

Highly Available, Powerful Ethernet Switches

These carrier-class switching solutions are for converged enterprise branch
offices, campuses, and data centers, as well as for service provider
deployments. They address escalating demands for high availability, unified
communications, mobility, and virtualization within enterprise networks.
Models and platforms
EX2200
The Juniper EX2200 line of 1Gb Ethernet switches are compact gigabit switches. They are small and
energy efficient making them environmentally friendly and great for office use. PoE variants in the
EX2200 family support high-power 802.3at PoE+ (up to 30W/port) on all ports, up to a maximum of

405 Watts, which is the maximum power budget for the switch. The power budget is the lowest of all
EX series PoE switches, and notably insufficient to run high-power Powred Devices (PD's) on all
ports simultaneouslyit supports Juniper's virtual chassis technology. The EX2200-24T/24P has a
data rate of 56 Gbit/s while the EX2200-48T/48P has a data rate of 104 Gbit/s

EX2500
The Juniper EX2500 line of 10Gb Ethernet switches address high-performance server access
requirements with twenty-four 10 GbE SFP+ ports that deliver wire-speed performance and 700
nanosecond latency. The EX2500 Series will support 480 Gigabit per second (Gbit/s) throughput (full
duplex) in a 1 rack-unit (RU) footprint. The EX2500 Series has both power and fan redundancy as
standard features. The EX2500 Series comes with dual, load-sharing power supplies, as well as
redundant, variable-speed fans to protect from single power supply or fan failure.

EX3200 The Juniper 3200 switches are 24-port or 48-port boxes with 10/100/1000 Mbit/s Ethernet ports
supporting power over Ethernet (PoE). They can also support 1G Ethernet and 10G Ethernet uplinks

EX3300 juniper's EX3300 Ethernet switches are cost-effective enterprise access solutions for data center
environments that support converged data, voice, and video. Models come with 24 or 48
10/100/1000BASE-T ports and four GbE/10GbE SFP/SFP+ uplink ports.The EX3300 switches
support IEEE 802.3af Power over Ethernet (PoE) or 802.3at PoE+. Optimized for the data center,
the switches offer front-to-back and back-to-front cooling options, and can be configured with a DC
power supply

EX4200

The Juniper 4200 series is built on modular chassis used for data centers and large corporate
offices. They also come in 24-port and 48-port models and support PoE as well as 1 Gig Ethernet
and 10Gig Ethernet uplinks. They also have a 24-port fiber option. [2] These switches are stackable,
and 10 of them can be linked to create a single virtual switch supporting up to 480 10/100/1000
Ethernet ports, forty 1G Ethernet or twenty 10G Ethernet ports. EX4200 Virtual Chassis can be
expanded by using optical ports and/or ethernet ports (VCE - Virtual Chassis Expansion), thus
allowing to manage device as a single switch even if locations are separated

EX4300
Successor of the EX4200, and similar in functionality/options. Can be used in as a leaf in a leaf and
spine topology with the QFX5100. Also complies to new ECC regulations which appears to be one of
the reasons the EX4200 is being replaced

EX4500
The Juniper EX4500 series consists of models which differ in the direction of the airflow used for
cooling and the support for Converged Enhanced Ethernet. All models are two rack units high and
have forty 10G Ethernet SFP+ ports. Two slots are available which can be used to add four 10G

Ethernet SFP+ ports per slot. The roadmap for these switches includes the ability to stack them
together and with switches of the EX4200 series

EX4600
Fixed platform. Virtual Chassis configuration consisting of up to 10 switches. Backplane 960 Gbit/s.
EX4600 Ethernet Switches offer a compact, highly scalable, high-performance 10GbE solution for
enterprise campus distribution deployments as well as low-density data center top-of-rack
environments.

EX6200
Juniper's EX6200[ Ethernet switch is a scalable, resilient, high-performance wiring closet solution for
campus deployments, or for end-of-row access in the data center.The flexible, 14RU, 10-slot chassis
reserves two slots for holding redundant Switch Fabric Routing Engine (SRE) modules, while eight
slots are dedicated for 48-port 10/100/1000BASE-T line cards.

EX8200
The Juniper 8200 series are core switches for 10G Ethernet backbones that comes in two models.
One has an eight-slot 1.6 Tbit/s chassis that supports up to 64 ports. The other has a sixteen-slot 3.2
Tbit/s chassis that supports up to 128 ports. Separate external routing engine XRE200 can be used
to offload switches REs

EX9200
Juniper's EX9200[9] line of programmable Ethernet switches simplifies the deployment of cloud
applications, server virtualization and rich media collaboration tools in campus and data center core
and aggregation environments.In the campus, the EX9200 enables collaboration and provides
simple and secure access for the delivery of mission-critical applications. In the data center, it
simplifies operations to align the network with fast-changing business requirements.Three EX9200
switches are available:

The EX9204 (4 slots in a 6RU chassis)

The EX9208 (8 slots in an 8RU chassis)

The EX9214 (14 slots in a 16RU chassis)

The EX9200 chassis deliver up to 240 Gbit/s (full duplex) per slot. A pass-through mid-plane design
supports capacity of up to 13.2 Tbit/s for built-in migration to next-generation deployments. Any
combination of GbE, 10GbE and 40GbE interfaces can be used, and the switches include support
for 100GbE cards when available.

2)

QFX is an image editing computer program, developed by Ron Scott a Texan photographer and
software engineer.[1] The first version was released in 1990. At the time of its release, QFX was one
of the most feature-rich image editing applications available on the PC platform (DOS,
later Windows). It was the software of choice for digital artists and image postproduction studios in
the times when 1024x768 truecolor graphics were a luxury, far before Photoshop could have been
considered a serious professional tool.

Present QFX seriesThe first version of QFX was released around 1990. It ran on PCs equipped with AT&T Truevision AT
Vista and Targa ISA bus framebuffer graphics cards. Low end Targa cards were limited to 8 bits, but
most were 24 bit with a hardware alpha channel; Vista cards were 24 bit, and capable of greater
than video resolution. All could capture RGB video.
Early versions of QFX had no brushes; the program was used for image processing and color
correction, rather than image creation, providing basic filters (blur, noise, glow etc.) that were a
collection of MS-DOS programs that could be run from the command line and included in batch files.
This functionality continued with all Targa and Vista versions of the program, and allowed operation
on images with a resolution far greater than the graphics display device. Later Windows releases
introduced an internal scripting facility that pre-dated Photoshop's actions by many years. The early
version ran on both Intel and DEC Alpha processors.
The program was popular with PC-based computer animators, who would often use QFX tools to
composite multiple image layers for single-frame output to a video recorder or film recorder.
In 1991 the new version called Hires QFX priced around 3500 USD, provided additional features
including brushes and expanded support for large image files. In that time the alternatives for
professional digital image editing were over-200k-and-more-USD dedicated workstations
like Quantel's Paintbox, Crossfield or Barco Creator software running on expensive SGI Power
series multiprocessor boxes. QFX was one of the first multiprocessor optimized graphics programs.
When running on dual processor systems, it would split the image in two, running half on each
processor. Could use "all memory" with out use of "memory manages" (QMM per example) through
Motherboard's BIOS, when DOS can not handle more of 16MB!, and let user set the undo levels up
to 999 years before others (aka; Photoshop) keep just one undo. Allow use customs icons for
customs scripts!
The boom of DTP and the rapid advances in PC hardware in the mid-1990s changed the market for
graphics software. Photoshop, windows oriented, less technical and cheaper solution
for anybody proved to be a winning approach. QFX continued adding new features including a
windows-based interface and CMYK handling, but was unable to compete with the lower-priced and
increasingly feature-rich Photoshop.

WLAN Products: Controllers, access points and software

Wireless LAN Controllers JunosV Wireless LAN Controller (JunosV WLC) is a virtual
controller that uses a cloud-based architecture that includes physical access points.
The functionalities available in a physical wireless LAN controller are available on
the JunosV WLC. JunosV WLC Release 9.1 and later support up to 500 Juniper
Networks Wireless LAN Access Points (WLAs). JunosV WLC Release 9.0 supports up
to 256 WLAs.
JunosV WLC supports the following features: Auto-tune Bandwidth control
(Identity based) Admission control (CAC)/Wi-Fi Multimedia (WMM) Guest services
(wireless) Wired authentication Access Control Lists (ACLs) JunosV WLC high
availabilityWLC Controller Clustering
unosV WLC does not support the following features: 4 Copyright 2014, Juniper
Networks, Inc. Installation Guide for JunosV Wireless LAN Controller Changing the
OS (supports only Linux OS) Extra management options Configurable ports
Autonegotiation of port speed WebView
WLA532 Access Point Hardware Overview
The Juniper Networks Wireless LAN Access Point, WLA532 is an indoor mobility access point
that provides enterprise customers, such as those in business, healthcare and education,
with 802.11nbased wireless LAN access in highdensity deployments. The device is a
compact, hexagon-shaped access point (see Figure 1) with dual radios with multiple input
multiple output (MIMO) supporting up to three spatial streams on each radio.

Features Supported by the WLA532 Access Point

Features supported by the access point include:
Up to 450Mbps transmissionWLA532 3x3 spatial stream access point can support data rates of up to 450-Mbps in a 5GHz band with 40-MHz channel bonding and a short-guard interval. On a 2.4-GHz band with 20-MHz channel width, the
access point supports up to 195-Mbps by default with standard guard-interval and supports up to 216.7-Mbps with short
guard-interval.
In-band spectrum monitoring and network spectrum mitigationThe access point supplies in-band RF-detect functionality
to include spectrum analysis to detect and classify the non-IEEE 802.11 sources of interference.
Rate adaptation feature with 3 spatial stream (SS) rates, 2 spatial stream rates and 1 spatial stream ratesThe access
point supports 3 SS, 2 SS and 1 Srates and provides and full support for rate adaptation with 3 SS clients.

Use the following hardware from Juniper Networks to connect the access point and make it
operational:
WLC2 Wireless LAN Controller
WLC200 Wireless LAN Controller
WLC216 Wireless LAN Controller
WLC8 Wireless LAN Controller
WLC800 Wireless LAN Controller
WLC880 Wireless LAN Controller
WLC2800 Wireless LAN Controller

CLASS OF SERVICE Juniper networks.

Overview
When a network experiences congestion and delay, some packets must be
dropped. The Juniper Networks Junos operating system (Junos OS) class of
service (CoS) enables you to divide traffic into classes and offer various levels
of throughput and packet loss when congestion occurs. This allows packet
loss to happen according to rules that you configure.
For interfaces that carry IPv4, IPv6, and MPLS traffic, you can configure the
Junos OS CoS features to provide multiple classes of service for different
applications. On the routing device, you can configure multiple forwarding
classes for transmitting packets, define which packets are placed into each

output queue, schedule the transmission service level for each queue, and
manage congestion using a random early detection (RED) algorithm.
The Junos OS CoS features provide a set of mechanisms that you can use to
provide differentiated services when best-effort traffic delivery is insufficient.
In designing CoS applications, you must give careful consideration to your
service needs, and you must thoroughly plan and design your CoS
configuration to ensure consistency across all routing devices in a CoS
domain. You must also consider all the routing devices and other networking
equipment in the CoS domain to ensure interoperability among all
equipment.
Because Juniper Networks routing devices implement CoS in hardware rather
than in software, you can experiment with and deploy CoS features without
adversely affecting packet forwarding and routing performance.
The standards for Juniper Networks Junos operating system (Junos OS)
class of service (CoS) capabilities are defined in the following RFCs:

RFC 2474, Definition of the Differentiated Services Field in the IPv4

and IPv6 Headers
RFC 2597, Assured Forwarding PHB Group
RFC 2598, An Expedited Forwarding PHB
RFC 2698, A Two Rate Three Color Marker

Understanding Packet Flow

Across a Network
CoS works by examining traffic entering at the edge of your network. The
edge routing devices classify traffic into defined service groups, to provide
the special treatment of traffic across the network. For example, voice traffic
can be sent across certain links, and data traffic can use other links. In
addition, the data traffic streams can be serviced differently along the
network path to ensure that higher-paying customers receive better service.
As the traffic leaves the network at the far edge, you can reclassify the
traffic.

To support CoS, you must configure each routing device in the network.
Generally, each routing device examines the packets that enter it to
determine their CoS settings. These settings then dictate which packets are
first transmitted to the next downstream routing device. In addition, the
routing devices at the edges of the network might be required to alter the
CoS settings of the packets that enter the network from the customer or peer
networks.
In Figure 1, Router A is receiving traffic from a customer network. As each
packet enters, Router A examines the packets current CoS settings and
classifies the traffic into one of the groupings defined by the Internet service
provider (ISP). This definition allows Router A to prioritize its resources for
servicing the traffic streams it is receiving. In addition, Router A might alter
the CoS settings (forwarding class and loss priority) of the packets to better
match the ISPs traffic groups. When Router B receives the packets, it
examines the CoS settings, determines the appropriate traffic group, and
processes the packet according to those settings. It then transmits the
packets to Router C, which performs the same actions. Router D also
examines the packets and determines the appropriate group. Because
Router D sits at the far end of the network, the ISP might decide once again
to alter the CoS settings of the packets before Router D transmits them to
the neighboring network.
Figure 1: Packet Flow Across the Network

Junos CoS Components

1)The Juniper Networks Junos operating system (Junos OS) CoS consists
of many components that you can combine and tune to provide the level of
services required by customers.

The Junos OS CoS components include:

1)Code-point aliasesA code-point alias assigns a name to a pattern of codepoint bits. You can use this name instead of the bit pattern when you
configure other CoS components, such as classifiers, drop-profile maps,
and rewrite rules.
2)ClassifiersPacket classification refers to the examination of an incoming
packet. This function associates the packet with a particular CoS servicing
level. In the Junos OS, classifiers associate incoming packets with a
forwarding class and loss priority and, based on the associated forwarding
class, assign packets to output queues. Two general types of classifiers are
supported:
3)Behavior aggregate or CoS value traffic classifiersA behavior
aggregate (BA) is a method of classification that operates on a packet as it
enters the routing device. The CoS value in the packet header is examined,
and this single field determines the CoS settings applied to the packet. BA
classifiers allow you to set the forwarding class and loss priority of a packet
based on the Differentiated Services code point (DSCP) value, DSCP IPv6
value, IP precedence value, MPLS EXP bits, and IEEE 802.1p value. The
default classifier is based on the IP precedence value.
4)Multifield traffic classifiersA multifield classifier is a second method for
classifying traffic flows. Unlike a behavior aggregate, a multifield classifier
can examine multiple fields in the packet. Examples of some fields that a
multifield classifier can examine include the source and destination address
of the packet as well as the source and destination port numbers of the
packet. With multifield classifiers, you set the forwarding class and loss
priority of a packet based on firewall filter rules.
5)Forwarding classesThe forwarding classes affect the forwarding,
scheduling, and marking policies applied to packets as they transit a routing
device. The forwarding class plus the loss priority define the per-hop
behavior. Four categories of forwarding classes are supported: best effort,
assured forwarding, expedited forwarding, and network control. For Juniper
Networks M Series Multiservice Edge Routers, four forwarding classes are
supported. You can configure up to one each of the four types of forwarding
classes. For M120 and M320 Multiservice Edge Routers, Juniper Networks MX
Series 3D Universal Edge Routers, Juniper Networks T Series Core Routers
and EX Series switches, 16 forwarding classes are supported, so you can
classify packets more granularly. For example, you can configure multiple
classes of expedited forwarding (EF) traffic: EF, EF1, and EF2.
6)Loss prioritiesLoss priorities allow you to set the priority of dropping a
packet. Loss priority affects the scheduling of a packet without affecting the
packets relative ordering. You can use the packet loss priority (PLP) bit as
part of a congestion control strategy. You can use the loss priority setting to
identify packets that have experienced congestion. Typically you mark
packets exceeding some service level with a high loss priority. You set loss

priority by configuring a classifier or a policer. The loss priority is used later

in the workflow to select one of the drop profiles used by RED.
7)Forwarding policy optionsThese options allow you to associate forwarding
classes with next hops. Forwarding policy also allows you to create
classification overrides, which assign forwarding classes to sets of prefixes.
Transmission scheduling and rate controlThese parameters provide you
with a variety of tools to manage traffic flows:
8)QueuingAfter a packet is sent to the outgoing interface on a routing
device, it is queued for transmission on the physical media. The amount of
time a packet is queued on the routing device is determined by the
availability of the outgoing physical media as well as the amount of traffic
using the interface.
9)SchedulersAn individual routing device interface has multiple queues
assigned to store packets. The routing device determines which queue to
service based on a particular method of scheduling. This process often
involves a determination of which type of packet should be transmitted
before another. The Junos OS schedulers allow you to define the priority,
bandwidth, delay buffer size, rate control status, and RED drop profiles to be
applied to a particular queue for packet transmission.
10)Fabric schedulersFor M320 and T Series routers only, fabric schedulers
allow you to identify a packet as high or low priority based on its forwarding
class, and to associate schedulers with the fabric priorities.
11)Policers for traffic classesPolicers allow you to limit traffic of a certain
class to a specified bandwidth and burst size. Packets exceeding the policer
limits can be discarded, or can be assigned to a different forwarding class, a
different loss priority, or both. You define policers with filters that can be
associated with input or output interfaces.
12)Rewrite rulesA rewrite rule sets the appropriate CoS bits in the outgoing
packet. This allows the next downstream routing device to classify the packet
into the appropriate service group. Rewriting, or marking, outbound packets
is useful when the routing device is at the border of a network and must alter
the CoS values to meet the policies of the targeted peer.

CoS Inputs and Outputs Examples

Here are examples of configurations for classifiers, drop-profile maps, and
rewrite rules.
In the following classifier example, packets with EXP bits 000 are assigned to
the data-queue forwarding class with a low loss priority, and packets with EXP
bits 001 are assigned to the data-queue forwarding class with a high loss
priority.
[edit class-of-service]

classifiers {
exp exp_classifier {
forwarding-class data-queue {
loss-priority low code-points 000;
loss-priority high code-points 001;
}
}

}
In the following drop-profile map example, the scheduler includes two dropprofile maps, which specify that packets are evaluated by the low-drop drop
profile if they have a low loss priority and are from any protocol. Packets are
evaluated by the high-drop drop profile if they have a high loss priority and
are from any protocol.
[edit class-of-service]
schedulers {

best-effort {
drop-profile-map loss-priority low protocol any drop-profile lowdrop;
drop-profile-map loss-priority high protocol any drop-profile highdrop;
}

}
In the following rewrite rule example, packets in the be forwarding class
with low loss priority are assigned the EXP bits 000, and packets in
the be forwarding class with high loss priority are assigned the EXP bits 001.
[edit class-of-service]
rewrite-rules {
exp exp-rw {
forwarding-class be {
loss-priority low code-point 000;
loss-priority high code-point 001;
}
}

Packet Flow Through the CoS

Process Configuration Example
The following configuration demonstrates the packet flow through the CoS
process:
[edit class-of-service]
interfaces { # Step 1: Define CoS interfaces.
so-* {
scheduler-map sched1;

unit 0 {
classifiers {
exp exp_classifier;
}
}

}
t3-* {
scheduler-map sched1;
unit 0 {
classifiers {
exp exp_classifier;
}
}
}

}
classifiers { # Step 2: Define classifiers.
exp exp_classifier {
forwarding-class data-queue {
loss-priority low code-points 000;
loss-priority high code-points 001;
}
forwarding-class video-queue {
loss-priority low code-points 010;
loss-priority high code-points 011;
}
forwarding-class voice-queue {
loss-priority low code-points 100;
loss-priority high code-points 101;
}
forwarding-class nc-queue {
loss-priority high code-points 111;
loss-priority low code-points 110;
}

}
drop-profiles { # Step 3: Define drop profiles.
be-red {
fill-level 50 drop-probability 100;
}

}
forwarding-classes { # Step 4: Define queues.
queue 0 data-queue;
queue 1 video-queue;
queue 2 voice-queue;
queue 3 nc-queue;
}
schedulers { # Step 5: Define schedulers.

data-scheduler {
transmit-rate percent 50;
buffer-size percent 50;
priority low;
drop-profile-map loss-priority high protocol any drop-profile bered;
}
video-scheduler {

transmit-rate percent 25;

buffer-size percent 25;
priority strict-high;

}
voice-scheduler {
transmit-rate percent 20;
buffer-size percent 20;
priority high;
}
nc-scheduler {
transmit-rate percent 5;
buffer-size percent 5;
priority high;
}

}
scheduler-maps { # Step 6: Define scheduler maps.
sched1 {
forwarding-class
forwarding-class
forwarding-class
forwarding-class
}

Supported Platforms
M Series
MX Series
PTX Series
T Series

data-queue scheduler data-scheduler;

video-queue scheduler video-scheduler;
voice-queue scheduler voice-scheduler;
nc-queue scheduler nc-scheduler;