Juniper EX9200 Series Specification sheet

Port Mirroring Analyzers Feature Guide for EX9200
Switches
Release
16.2
Modified: 2016-11-03
Copyright © 2016, Juniper Networks, Inc.

Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, 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.
Port Mirroring Analyzers Feature Guide for EX9200 Switches
Release 16.2
Copyright © 2016, Juniper Networks, Inc.
All rights reserved.
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 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
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of
that EULA.
Copyright © 2016, Juniper Networks, Inc.ii

Table of Contents
AbouttheDocumentation............................................ix
DocumentationandReleaseNotes..................................ix
SupportedPlatforms.............................................ix
UsingtheExamplesinThisManual..................................ix
MergingaFullExample........................................x
MergingaSnippet............................................x
DocumentationConventions.......................................xi
Documentation Feedback........................................xiii
RequestingTechnicalSupport.....................................xiii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
OpeningaCasewithJTAC.....................................xiv
Part 1 Overview
Chapter 1 Understanding Port Mirroring Analyzers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Understanding Port Mirroring Analyzers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
AnalyzerOverview................................................5
StatisticalAnalyzerOverview.......................................5
DefaultAnalyzerOverview.........................................5
Port Mirroring at a Group of Ports Bound to Multiple Statistical
Analyzers ...................................................5
Port Mirroring Analyzer Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Configuration Guidelines for Port Mirroring Analyzers . . . . . . . . . . . . . . . . . . . . 7
Part 2 Configuring Analyzers
Chapter 2 Copy Packets to a Local Interface for Local Monitoring . . . . . . . . . . . . . . . . . 13
Configuring Mirroring on EX9200 Switches to Analyze Traffic (CLI
Procedure) .....................................................13
Configuring an Analyzer for Local Traffic Analysis . . . . . . . . . . . . . . . . . . . . . . 14
Configuring an Analyzer for Remote Traffic Analysis . . . . . . . . . . . . . . . . . . . . 14
Configuring a Statistical Analyzer for Local Traffic Analysis . . . . . . . . . . . . . . 15
Configuring a Statistical Analyzer for Remote Traffic Analysis . . . . . . . . . . . . 16
Binding Statistical Analyzers to Ports Grouped at the FPC Level . . . . . . . . . . . 17
Configuring an Analyzer with Multiple Destinations by Using Next-Hop
Groups ....................................................18
Defining a Next-Hop Group for Layer 2 Mirroring . . . . . . . . . . . . . . . . . . . . . . . 18
Example: Configuring Port Mirroring Analyzers for Local Monitoring of Employee
ResourceUse...................................................19
iiiCopyright © 2016, Juniper Networks, Inc.

Chapter 3 Copy Packets to a VLAN or Bridge Domain for Remote Monitoring . . . . . . . 25
Configuring Mirroring on EX9200 Switches to Analyze Traffic (CLI
Procedure).....................................................25
Configuring an Analyzer for Local Traffic Analysis . . . . . . . . . . . . . . . . . . . . . . 26
Configuring an Analyzer for Remote Traffic Analysis . . . . . . . . . . . . . . . . . . . . 27
Configuring a Statistical Analyzer for Local Traffic Analysis . . . . . . . . . . . . . . 27
Configuring a Statistical Analyzer for Remote Traffic Analysis . . . . . . . . . . . . 28
Binding Statistical Analyzers to Ports Grouped at the FPC Level . . . . . . . . . . 29
Configuring an Analyzer with Multiple Destinations by Using Next-Hop
Groups ....................................................30
Defining a Next-Hop Group for Layer 2 Mirroring . . . . . . . . . . . . . . . . . . . . . . . 31
Example: Configuring Port Mirroring for Remote Monitoring of Employee Resource
Use ...........................................................31
Example: Configuring Mirroring to Multiple Interfaces for Remote Monitoring of
Employee Resource Use on EX9200 Switches . . . . . . . . . . . . . . . . . . . . . . . . 41
Example: Configuring Mirroring for Remote Monitoring of Employee Resource
Use Through a Transit Switch on EX9200 Switches . . . . . . . . . . . . . . . . . . . . 50
Part 3 Configuration Statements and Operational Commands
Chapter4 Configuration Statements .........................................59
egress............................................................59
egress(Analyzer)...................................................60
ingress(vlans).....................................................60
ingress(Analyzer)...................................................61
input(Analyzer)....................................................62
interface(Analyzer).................................................63
no-tag............................................................64
output(Mirroring)..................................................65
vlan (Mirroring) ....................................................66
Chapter5 Operational Commands ...........................................67
showforwarding-optionsanalyzer.....................................68
Copyright © 2016, Juniper Networks, Inc.iv
Port Mirroring Analyzers Feature Guide for EX9200 Switches

List of Figures
Part 2 Configuring Analyzers
Chapter 2 Copy Packets to a Local Interface for Local Monitoring . . . . . . . . . . . . . . . . . 13
Figure 1: Network Topology for Local Port Mirroring Example . . . . . . . . . . . . . . . . . 21
Chapter 3 Copy Packets to a VLAN or Bridge Domain for Remote Monitoring . . . . . . . 25
Figure 2: Network Topology for Remote Port Mirroring and Analysis . . . . . . . . . . . 33
Figure 3: Remote Mirroring Example Network Topology Using Multiple VLAN
Member Interfaces in the Next-Hop Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 4: Network Monitoring for Remote Mirroring Through a Transit Switch . . . . 51
vCopyright © 2016, Juniper Networks, Inc.

Copyright © 2016, Juniper Networks, Inc.vi
Port Mirroring Analyzers Feature Guide for EX9200 Switches

List of Tables
AbouttheDocumentation..........................................ix
Table1:NoticeIcons..................................................xi
Table2:TextandSyntaxConventions...................................xi
Part 1 Overview
Chapter 1 Understanding Port Mirroring Analyzers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table3:AnalyzerTerminology..........................................5
Table 4: Configuration Guidelines for Port Mirroring Analyzers . . . . . . . . . . . . . . . . . 7
Part 3 Configuration Statements and Operational Commands
Chapter5 Operational Commands ...........................................67
Table 5: show forwarding-options analyzer Output Fields . . . . . . . . . . . . . . . . . . 68
viiCopyright © 2016, Juniper Networks, Inc.

Copyright © 2016, Juniper Networks, Inc.viii
Port Mirroring Analyzers Feature Guide for EX9200 Switches

About the Documentation
•Documentation and Release Notes on page ix
•Supported Platforms on page ix
•Using the Examples in This Manual on page ix
•Documentation Conventions on page xi
•Documentation Feedback on page xiii
•Requesting Technical Support on page xiii
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
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:
•EX Series
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.
ixCopyright © 2016, Juniper Networks, Inc.

If the example configuration does not start at the top level of the hierarchy, the example
isasnippet. 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;
}
}
}
}
2. Merge the contents of the file into your routing platform configuration by issuing the
load merge configuration mode command:
[edit]
user@host# load merge /var/tmp/ex-script.conf
load complete
Merging a Snippet
To merge a snippet, follow these steps:
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:
Copyright © 2016, Juniper Networks, Inc.x
Port Mirroring Analyzers Feature Guide for EX9200 Switches

[edit]
user@host# edit system scripts
[edit system scripts]
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 xi defines notice icons used in this guide.
Table 1: Notice Icons
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Indicates a situation that might result in loss of data or hardware damage.Caution
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 xi defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
ExamplesDescriptionConvention
To enter configuration mode, type the
configure command:
user@host> configure
Represents text that you type.Bold text like this
xiCopyright © 2016, Juniper Networks, Inc.
About the Documentation

Table 2: Text and Syntax Conventions (continued)
ExamplesDescriptionConvention
user@host> show chassis alarms
No alarms currently active
Represents output that appears on the
terminal screen.
Fixed-width text like this
•A policy term is a named structure
that defines match conditions and
actions.
•Junos OS CLI User Guide
•RFC 1997, BGP Communities Attribute
•Introduces or emphasizes important
new terms.
•Identifies guide names.
•Identifies RFC and Internet draft titles.
Italic text like this
Configure the machine’s domain name:
[edit]
root@# set system domain-name
domain-name
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
Italic text like this
•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.
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy levels;
or labels on routing platform
components.
Text like this
stub <default-metric metric>;Encloses optional keywords or variables.< > (angle brackets)
broadcast | multicast
(string1 |string2 |string3)
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.
| (pipe symbol)
rsvp { # Required for dynamic MPLS onlyIndicates a comment specified on the
same line as the configuration statement
to which it applies.
# (pound sign)
community name members [
community-ids ]
Encloses a variable for which you can
substitute one or more values.
[ ] (square brackets)
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Identifies a level in the configuration
hierarchy.
Indention and braces ( { } )
Identifies a leaf statement at a
configuration hierarchy level.
; (semicolon)
GUI Conventions
•In the Logical Interfaces box, select
All Interfaces.
•To cancel the configuration, click
Cancel.
Represents graphical user interface (GUI)
items you click or select.
Bold text like this
Copyright © 2016, Juniper Networks, Inc.xii
Port Mirroring Analyzers Feature Guide for EX9200 Switches

Table 2: Text and Syntax Conventions (continued)
ExamplesDescriptionConvention
In the configuration editor hierarchy,
select Protocols>Ospf.
Separates levels in a hierarchy of menu
selections.
>(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 rate the 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/.
•E-mail—Send your comments to [e-mail]. 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 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
http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
•Product warranties—For product warranty information, visit
http://www.juniper.net/support/warranty/.
•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 CSC offerings: http://www.juniper.net/customers/support/
•Search for known bugs: http://www2.juniper.net/kb/
•Find product documentation: http://www.juniper.net/techpubs/
•Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
xiiiCopyright © 2016, Juniper Networks, Inc.
About the Documentation

•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 entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
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).
For international or direct-dial options in countries without toll-free numbers, see
http://www.juniper.net/support/requesting-support.html.
Copyright © 2016, Juniper Networks, Inc.xiv
Port Mirroring Analyzers Feature Guide for EX9200 Switches

PART 1
Overview
•Understanding Port Mirroring Analyzers on page 3
1Copyright © 2016, Juniper Networks, Inc.

Copyright © 2016, Juniper Networks, Inc.2
Port Mirroring Analyzers Feature Guide for EX9200 Switches

CHAPTER 1
Understanding Port Mirroring Analyzers
•Understanding Port Mirroring Analyzers on page 4
3Copyright © 2016, Juniper Networks, Inc.

Understanding Port Mirroring Analyzers
Port mirroring can be used for traffic analysis on routers and switches that, unlike hubs,
do not broadcast packets to every port on the destination device. Port mirroring sends
copies of all packets or policy-based sample packets to local or remote analyzers where
you can monitor and analyze the data.
In the context of port mirroring analyzers, we use the term switching device. The term
indicates that the device (including routers) is performing a switching function.
You can use analyzers on a packet level to help you:
•Monitor network traffic
•Enforce network usage policies
•Enforce file sharing policies
•Identify causes of problems
•Identify stations or applications with heavy or abnormal bandwidth usage
You can configure an analyzer to mirror:
•Bridged packets (Layer 2 packets)
•Routed packets (Layer 3 packets)
Mirrored packets can be copied to either a local interface for local monitoring or a VLAN
or bridge domain for remote monitoring.
The following packets can be copied:
•Packets entering or exiting a port—You can mirror packets entering or exiting ports,
in any combination, for up to 256 ports. For example, you can send copies of the packets
entering some ports and the packets exiting other ports to the same local analyzer
port or analyzer VLAN.
•Packets entering or exiting a VLAN or bridge domain—You can mirror the packets
entering or exiting a VLAN or bridge domain to either a local analyzer port or to an
analyzer VLAN or bridge domain. You can configure multiple VLANs (up to 256 VLANs)
or bridge domains as ingress inputs to an analyzer, including a VLAN range and private
VLANs (PVLANs).
•Policy-based sample packets—You can mirror a policy-based sample of packets that
are entering a port, VLAN, or bridge domain. You configure a firewall filter with a policy
to select the packets to be mirrored. You can send the sample to a port-mirroring
instance or to an analyzer VLAN or bridge domain.
This topic describes:
•Analyzer Overview on page 5
•Statistical Analyzer Overview on page 5
Copyright © 2016, Juniper Networks, Inc.4
Port Mirroring Analyzers Feature Guide for EX9200 Switches

•Default Analyzer Overview on page 5
•Port Mirroring at a Group of Ports Bound to Multiple Statistical Analyzers on page 5
•Port Mirroring Analyzer Terminology on page 5
•Configuration Guidelines for Port Mirroring Analyzers on page 7
Analyzer Overview
You can configure an analyzer to define both the input traffic and the output traffic in
the same analyzer configuration. The input traffic to be analyzed can be either traffic
that enters or traffic that exits an interface or VLAN. The analyzer configuration enables
you to send this traffic to an output interface, instance, next-hop group, VLAN, or bridge
domain. You can configure an analyzer at the [edit forwarding-options analyzer] hierarchy
level.
Statistical Analyzer Overview
You can define a set of mirroring properties, such as mirroring rate and maximum packet
length for traffic, that you can explicitly bind to physical ports on the router or switch.
This set of mirroring properties constitutes a statistical analyzer (also called a nondefault
analyzer). At this level, you can bind a named instance to the physical ports associated
with a specific FPC.
Default Analyzer Overview
You can configure an analyzer without configuring any mirroring properties (such as
mirroring rate or maximum packet length). By default, the mirroring rate is set to 1 and
the maximum packet length is set to the complete length of the packet. These properties
are applied at the global level and need not be bound to a specific FPC.
Port Mirroring at a Group of Ports Bound to Multiple Statistical Analyzers
You can apply up to two statistical analyzers to the same port groups on the switching
device. By applying two different statistical analyzer instances to the same FPC or Packet
Forwarding Engine, you can bind two distinct Layer 2 mirroring specifications to a single
port group. Mirroring properties that are bound to an FPC override any analyzer (default
analyzer) properties bound at the global level on the switching device. Default analyzer
properties are overridden by binding a second analyzer instance on the same port group.
Port Mirroring Analyzer Terminology
Table 3 on page 5 lists some port mirroring analyzer terms and their descriptions.
Table 3: Analyzer Terminology
DescriptionTerm
In a mirroring configuration, the analyzer includes:Analyzer
•The name of the analyzer
•Source (input) ports, VLANs, or bridge domains
5Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Understanding Port Mirroring Analyzers

Table 3: Analyzer Terminology (continued)
DescriptionTerm
•A destination for mirrored packets (either a monitor port, VLAN, or bridge domain)
Interface to which mirrored traffic is sent and to which a protocol analyzer application is
connected.
Analyzer output interface
(Also known as a monitor port)
NOTE: Interfaces used as output for an analyzer must be configured under the
forwarding-options hierarchy level.
Analyzer output interfaces have the following limitations:
•They cannot also be a source port.
•They do not participate in Layer 2 protocols, such as the Spanning Tree Protocol (STP),
when part of a port-mirroring configuration.
•If the bandwidth of the analyzer output interface is not sufficient to handle the traffic
from the source ports, overflow packets are dropped.
VLAN or bridge domain to which mirrored traffic is sent. The mirrored traffic can be used by
a protocol analyzer application. The member interfaces in the monitor VLAN or bridge
domain are spread across the switching devices in your network.
Analyzer VLAN or bridge domain
(Also known as a monitor VLAN
or bridge domain)
An analyzer session whose configuration uses bridge domains for both input and output or
for either input or output.
Bridge-domain-based analyzer
An analyzer with default mirroring parameters. By default, the mirroring rate is 1 and the
maximum packet length is the length of the complete packet.
Default analyzer
An interface on the switching device that is being mirrored. Traffic that is either entering or
exiting this interface is mirrored.
Input interface
(Also known as mirrored ports or
monitored interfaces)
An analyzer that has a link aggregation group (LAG) specified as the input (ingress) interface
in the analyzer configuration.
LAG-based analyzer
An analyzer configuration in which packets are mirrored to a local analyzer port.Local mirroring
A computer running a protocol analyzer application.Monitoring station
An analyzer session configuration that uses the next-hop group as the analyzer output.Analyzer based on next-hop
group
An analyzer session configuration that defines interfaces for both input and output.Port-based analyzer
An application used to examine packets transmitted across a network segment. Also
commonly called a network analyzer, packet sniffer, or probe.
Protocol analyzer application
Functions the same way as local mirroring, except that the mirrored traffic is not copied to
a local analyzer port but is flooded to an analyzer VLAN or bridge domain that you create
specifically for the purpose of receiving mirrored traffic. Mirrored packets have an additional
outer tag of the analyzer VLAN or bridge domain.
Remote mirroring
Copyright © 2016, Juniper Networks, Inc.6
Port Mirroring Analyzers Feature Guide for EX9200 Switches